Skip to contentSkip to conversation

kernel crash debugging

DISCUSSION Robert Hancock 2 participants 2 messages Nov 11, 2005 1 message not in the archive

lore
Share & tools
lore

A message that is not in the archive (sent off-list or not yet received): [email protected]

#1 lore raw
Quoted 4 lines · Lee

Hello,

I am running kernel version '2.6.13-gentoo-r3'

Quoted 8 lines

My hardware is as follows:
- motherboard: Tyan Tiger 230T
- processors: 2 Pentium II 1.13Ghz
- memory: 1.5GB

I have been having intermittent lockups for a while now.

At first, I thought it had something to do with vmware, but this is no occuring with a non-tainted kernel.

First thing I would try with those kind of faults is Memtest86, you could have some bad RAM or bad memory timing settings..

Signature · 3 lines
Robert Hancock      Saskatoon, SK, Canada
To email, remove "nospam" from [email protected]
Home Page: http://www.roberthancock.com/
#2 lore raw
Quoted 7 lines
Quoted 7 lines

I am running kernel version '2.6.13-gentoo-r3'

My hardware is as follows:
- motherboard: Tyan Tiger 230T
- processors: 2 Pentium II 1.13Ghz
- memory: 1.5GB

Quoted 6 lines
Quoted 3 lines

I have been having intermittent lockups for a while now.

At first, I thought it had something to do with vmware, but this is no occuring with a non-tainted kernel.

First thing I would try with those kind of faults is Memtest86, you could have some bad RAM or bad memory timing settings..

I could understand that concept except for one thing:
- with 4k stacks turned on, i have the lockups
- with 4k stacks turned off, i have not had a single lock up at all.

Per an earlier email from '[email protected]', it appears that there is still an execution path in the kernel with is causing a stack overflow.

Signature · 4 lines
Lee
[email protected]

 14:18:50 up 4 days, 19:29,  1 user,  load average: 2.80, 2.72, 2.30