On Tue, 2010-09-21 at 20:53 +0100, Tixy wrote: > I'm also seeing this bug when upgrading from 2.6.32-21 to 2.6.32-23. > This is the console output leading up to the first oops... [...] > [ 31.479481] PC is at tcp_setsockopt+0x2c/0x3e0 > [ 31.483947] LR is at tcp_setsockopt+0x30/0x3e0 > [ 31.488411] pc : [<c026da00>] lr : [<c026da04>] psr: 20000013 [...] This is not 2.6.32-23; tcp_setsockopt starts at address c026dd08 in that version. Ben. -- Ben Hutchings Once a job is fouled up, anything done to improve it makes it worse.
Attachment:
signature.asc
Description: This is a digitally signed message part