On Mon, 23 Aug 2004, Bryan O'Donoghue wrote:
> Not a backtrace?
I'm not a guru, but I'm guessing that if EIP is in lalaland, any call
trace will also be gibberish.
> An lsmod would probably show you a module currently in use, for no
> good reason, that's probably the chap who segfaulted.
Eh? lsmod doesnt show you that, does it? It'll show which modules
have references, but that could be a bunch.
> Otherwise a quick dmesg might point in the direction of oops.
Indeed, but call trace (the most useful bit) is stuffed. so..
> It occured to me to add after, I posted, if there's recently been a nic
> added, then there's a possibility of an IRQ conflict etc.
best thing for original poster to do is run memtest86 for a few
Paul Jakma paul at clubi.iepaul at jakma.org Key ID: 64A2FF6A
/* First check any supplied i/o locations. User knows best. <cough> */
- comment from drivers/net/ne.c
Maintained by the ILUG website team. The aim of Linux.ie is to
support and help commercial and private users of Linux in Ireland. You can
display ILUG news in your own webpages, read backend
information to find out how. Networking services kindly provided by HEAnet, server kindly donated by
Dell. Linux is a trademark of Linus Torvalds,
used with permission. No penguins were harmed in the production or maintenance
of this highly praised website. Looking for the
Indian Linux Users' Group? Try here. If you've read all this and aren't a lawyer: you should be!