"Steinar H. Gunderson" <[email protected]> wrote:
>
> On Sat, May 13, 2006 at 07:33:44AM -0700, Andrew Morton wrote:
> > Well if it's the same software lineup on new hardware, one would also
> > suspect that hardware. Is it new?
>
> Yes, it's new. The differences aren't that big, though: The motherboard has
> been changed, and there's an extra sil3114 controller.
>
> > Does it run other kernels OK?
>
> 2.6.15.4 appears to be fine, but I haven't tested it enough to make sure.
> (I'm running 2.6.17-rc4 without swap now, so we'll see.)
>
> > Does it always crash in the same manner?
>
> Yes; consistently and in the same place after about the same amount of time.
ho-hum. Please see if there's anything else you can do to rule out a
hardware failure, then copy [email protected] on the next oops report.
The stack backtrace you have there is a little surprising. Enabling
CONFIG_FRAME_POINTER might help clear it up. Also it'd be worth seeing if
CONFIG_DEBUG_SLAB turns up anything.
Thanks.
-
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/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
