Re: Dell PowerEdge 4200 scsi, worked in 2.6.18, not in 2.6.26 (LOW PRIORITY help request)

[trouble daemon]

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@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/