Prev: msm: Add gpio register address mapping information.
Next: [PATCH 5/6 v2]kernel:module.c variable 'nowarn' set but not used
From: trouble daemon on 19 Jun 2010 16:30
Kernel hackers,

I consider this to be of rather low priority given the age of the
hardware, so ignore unless you feel like helping a fellow out, thanks!

I have a pair of Dell PowerEdge 4200's (dual 300 SMP, 512mb, SCA
hotswap scsi, have AMI MegaRaid but removed, same problem with or
without). I am using Debian Lenny, but have used etch (and in fact
bootstrap via FAI from etch currently). The 2.6.18 kernel that comes
with etch works fine in etch and Lenny, but when I tried to use the
2.6.26 kernel in Lenny, the kernel starts to panic (see "dmesg pastes"
below for output).

Ultimately, I was wondering if anyone might be able to take a look at
my dmesg's that might have any idea as to what feature might be new in
..26 that could be responsible for the panic. Sadly, it takes about 5
hours to do a clean run of make-kpkg in debian on these machines, and
I am not setup for distcc or cross compile on my x64 machine yet, so
it is a painful experience to recompile over and over to try figure
out what kernel feature it might be that is causing this.

I should note that I have tried one recompile of 2.6.26 (debianized)
to disable the new aic7xxx module and only use the old driver, but to
no avail. I am looking to try the 2.6.34 vanilla kernel next however.


dmesg pastes
---------------------
I have uploaded the panic dmesg to pastebin at (never expires):
http://pastebin.ca/1886636
I have uploaded the working 2.6.18 dmesg to pastbin at (never
expires): http://pastebin.ca/1886641


I think that about does it as far as pastebins go, but feel free to
ask for more information if you think you might have any idea. Since I
am not an LKML subscriber yet, I would please ask that any replies be
sent to this email address directly. Much appreciated for any help in
advance, thanks!



troubled
--
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: trouble daemon on 22 Jun 2010 13:40
Konrad,

> The more worrying is the irqs firring. Try to use the 'irqpoll' parameter as
> it suggests.

Actually, it seems that it was solved with "noapic" kernel option, as was
suggested by Ben in the debian bug report at:

http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=586494

I do thank you for replying though. I am still not sure what exactly changed in
debian between epoch (</joke>) and 2.6.26 though, since the dell's
have been 100% perfect
out of the box in every single debian since circa 2002, when I got them.

I can deal with noapic, but I will try the irqpoll as well. I only noticed that
the dmesg was mentioning it after the noapic solved my problem. One thing I did
notice with noapic though, is that network ping's seem to round down, so I see
lots of "0.000 ms" pings on the local network. I assume that without apic that
the system is just using some sort of timer to poll the nics though.

On a side note, I also saw a 2007 post from Andrew Morton, I think, that was
complaining about noapic and trying to track down where the problem might have
started. Given the approx. 1999 munfacturing date (from what I can tell) of the
PowerEdge 4200 series, and a perfect linux history from at least debian potato
up until 2.6.26, you can bet some money that someone, somewhere out there,
changed yet another feature that required me to use noapic. More specifically,
it worked in 2.6.18 in debian etch/lenny, but broke in the next debian kernel,
2.6.26. ie: the change/problem lies somewhere between 19-26 inclusive
(depending on if my apic issue isn't simply a debian default/tweak
that messed things
up, of course)

Hopefully Andrew high lights on his name! :)

Anyways, thanks and sorry for the wall of text! l8r



troubled
--
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/
 | 
Pages: 1
Prev: msm: Add gpio register address mapping information.
Next: [PATCH 5/6 v2]kernel:module.c variable 'nowarn' set but not used