The decoded oops shows a function trace which does not seem logical; e.g. function A calling function B where this is impossible in the code, as well as same function name appearing more than once. I have seen cases where, due to a memory glitch, the oops is wrong. Therefore, the only information I can trust is the sigbus message which I mentioned, which is outputted with printk. I know that's not a lot, but that's what I got :-( > -----Original Message----- > From: Felipe W Damasio [mailto:felipewd@terra.com.br] > Sent: Tuesday, July 30, 2002 9:19 AM > To: yaelgilad > Cc: kernelnewbies@nl.linux.org > Subject: Re: SIGBUG in unaligned.c > > > On Tue, 30 Jul 2002 12:34:24 +0200 > "yaelgilad" <yaelgilad@myrealbox.com> wrote: > > Y> Your question highlighted a typo in my original question: > Y> "reboot" should have been "boot" > Y> > Y> The crash occurs when I boot (or just turn-on) while packets are > Y> arriving. > Y> > Y> The initial hunch was that I begin to handle packets before > Y> initializations are complete, but the oops does not seem to be around > Y> the driver's code. > > What the decoded oops say? Where is the problem? > > Felipe > -- Kernelnewbies: Help each other learn about the Linux kernel. Archive: http://mail.nl.linux.org/kernelnewbies/ FAQ: http://kernelnewbies.org/faq/
