Decoding stack traces
john at metalab.unc.edu
Fri Oct 24 07:44:00 CDT 2003
Yes! I've been trying to figure this out for months. The latest
frustration is that every time one of my 2550s crashes with this
problem, it refuses to reboot via manual power cycle. Why would the
system not reboot unless there's a hardware issue triggered by the
crash? I opened a ticket with Dell, so we'll see what they come up
Time to start rebuilding kernel rpms with the older gcc.
On Fri, 2003-10-24 at 05:01, jason andrade wrote:
> welcome to what i think is a bug i identified sometime in march and was confirmed
> (i think) by howard owen at cisco. i'm taking a guess though.
> if you search for 'stack trace' in bugzilla you should pick this up or
> alternately for 'broken compiler' or something like that.
> if i am guessing correctly you have a RH 7.X OS (or derived from) on the box
> and you are using gcc-2.96-113. the problem seems to be that -113 produces
> broken kernels which have the above error. kernels built with -112 don't
> exhibit these symptoms. bugzilla has a more indepth explanation of how
> this is broken (by howard).
> the redhat errata kernels used to be ok until they started being produced
> on a system that had the compiler updated. this happened after 2.4.18-27.7.x
> all kernels after that have not been stable under conditions such as high
> network load for us and most of our stuff is back to 2.4.18-27.7.x.
> i don't know whether there is or will be a fix for this.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Size: 189 bytes
Desc: This is a digitally signed message part
Url : http://lists.us.dell.com/pipermail/linux-poweredge/attachments/20031024/f87b9006/attachment.bin
More information about the Linux-PowerEdge