On Wednesday 25 April 2007 11:52:52 Ismail Dönmez wrote: > Hi, > > On Tuesday 24 April 2007 00:23:13 Ismail Dönmez wrote: > > On Tuesday 24 April 2007 00:17:40 Thomas Graf wrote: > > > * Ismail D?nmez <[EMAIL PROTECTED]> 2007-04-23 22:09 > > > > > > > Yes I know the fix is in but I wondered why its creating such > > > > problems with 2.6.18 kernel, guess it depends on some other commits. > > > > > > As long as you apply the complete patch including the additional > > > sanity check for RTN_MAX it should work perfectly fine on 2.6.18. > > > > The sanity check part doesn't seem to apply to 2.6.18. > > > > > I can't think of any connection between the patch and the errors > > > you are seeing. > > > > > > Are you absolutely sure the errors you see are directly connected > > > to applying the patch? > > > > Yes actually I am but I'll re-test and see. Thanks. > > I was able to reproduce the same problem with Linus' GIT tree too. Since I > started to see these after I applied the commit > a0ee18b9b7d3847976c6fb315c06a34fb296de0e to 2.6.18 tree, there is a big > possiblity that the commit is the culprit. > > I attach the relevant dmesg messages. Problem happened after 12 hours of > uptime and and net connection gets stable again after 1-2 minutes.
Ignore this my laptop seems to be totally dying now including wireless card too. Sorry for the noise. Regards, ismail -- Life is a game, and if you aren't in it to win, what the heck are you still doing here? -- Linus Torvalds (talking about open source development)
signature.asc
Description: This is a digitally signed message part.
