This machine experienced another random reboot today, nothing in the logs or on the console etc. This is the 3rd time now since I upgraded from 2.6.11.3. Is there any way to debug something like this? I'm fairly certain it's not hardware-related. Might this have something to do with the st problem? Thanks, -ryan - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
- Follow-Ups:
- Re: Fw: crash on x86_64 - mm related?
- From: Hugh Dickins <[email protected]>
- Re: Fw: crash on x86_64 - mm related?
- References:
- Re: Fw: crash on x86_64 - mm related?
- From: Ryan Richter <[email protected]>
- Re: Fw: crash on x86_64 - mm related?
- From: Kai Makisara <[email protected]>
- Re: Fw: crash on x86_64 - mm related?
- From: Ryan Richter <[email protected]>
- Re: Fw: crash on x86_64 - mm related?
- From: Linus Torvalds <[email protected]>
- Re: Fw: crash on x86_64 - mm related?
- From: Ryan Richter <[email protected]>
- Re: Fw: crash on x86_64 - mm related?
- From: Linus Torvalds <[email protected]>
- Re: Fw: crash on x86_64 - mm related?
- From: Hugh Dickins <[email protected]>
- Re: Fw: crash on x86_64 - mm related?
- From: Ryan Richter <[email protected]>
- Re: Fw: crash on x86_64 - mm related?
- From: Hugh Dickins <[email protected]>
- Re: Fw: crash on x86_64 - mm related?
- Prev by Date: Re: FYI: RAID5 unusably unstable through 2.6.14
- Next by Date: Re: [PATCH 2.6.15] ia64: use i386 dmi_scan.c
- Previous by thread: Re: Fw: crash on x86_64 - mm related?
- Next by thread: Re: Fw: crash on x86_64 - mm related?
- Index(es):