Prev: net/bridge: add support for EtherIP devices
Next: sata_promise unaligned PCI accesses on sparc64
From: Christian Weiske on 24 Sep 2006 05:30
> I put the logs in a tar.bz2 because I didn't want to flood the list with
> a 200k message.

In case the bz2 didn't make it through the list:
http://xml.cweiske.de/dojo%20kernelpanic%20+%20debug.tar.bz2

--
Regards/MfG,
Christian Weiske

From: Christian Weiske on 24 Sep 2006 08:30
Andrew,

> It would be interesting to find out if enabling CONFIG_4KSTACKS makes this
> go away (although I'm not sure why).
So, here are the results from the 4K runs:

Beside one Oops message, I got a "kernel BUG at mm/slab.c:2747!" in log
#1. Call traces as usual.

Further, logs #2 and #3 show funny things; the thing just rebooted. Log
#2 has some oversized ethernet frames before the reboot.



Sorry for the CC, I thought you were subscribed to lkml and removed you.

--
Regards/MfG,
Christian Weiske
From: Christian Weiske on 24 Sep 2006 13:50
Andrew,


> I assume that you have confirmed that the machine doesn't have hardware
> problems? Does it run some earlier kernel OK?
The disks are both fine, they worked in other pcs without problems. The
ide controller card also worked fine, and the motherboard is new -
whatever you can expect with that. Maybe the combination is the problem.

I had some problems after running the machine for some days but I
thought that wasn't a hardware but more a kernel timing problem:
http://bugzilla.kernel.org/show_bug.cgi?id=6969


> And how long does it take to crash?
After starting the yacy daemon, it's about half a minute until the
"possible recursive locking detected" appears, and after one or two
minutes the whole thing crashes.


--
Regards/MfG,
Christian Weiske

From: Nick Piggin on 25 Sep 2006 09:30
Christian Weiske wrote:

>Andrew,
>
>
>
>>I assume that you have confirmed that the machine doesn't have hardware
>>problems? Does it run some earlier kernel OK?
>>
>The disks are both fine, they worked in other pcs without problems. The
>ide controller card also worked fine, and the motherboard is new -
>whatever you can expect with that. Maybe the combination is the problem.
>

Memory, motherboard, and CPU would be possible candidates, in roughly
that order of likelihood. If you can run memtest86+ on it overnight,
that would provide a bit more confidence in all.

Can you try using a different IDE controller to reproduce the panic
on the same system?

>>And how long does it take to crash?
>>
>After starting the yacy daemon, it's about half a minute until the
>"possible recursive locking detected" appears, and after one or two
>minutes the whole thing crashes.
>

I wonder if that does anything unusual apart from use the network?
Can you break it with anything else? a big ftp transfer?

--

Send instant messages to your online friends http://au.messenger.yahoo.com
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo(a)vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
From: Christian Weiske on 25 Sep 2006 14:40
>> I assume that you have confirmed that the machine doesn't have hardware
>> problems? Does it run some earlier kernel OK?
> The disks are both fine, they worked in other pcs without problems. The
> ide controller card also worked fine, and the motherboard is new -
> whatever you can expect with that. Maybe the combination is the problem.

So this is definitely a hardware problem? Which component is most likely
to be the bad one?

--
Regards/MfG,
Christian Weiske

 |  Next  |  Last
Pages: 1 2
Prev: net/bridge: add support for EtherIP devices
Next: sata_promise unaligned PCI accesses on sparc64