[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

Re: After latest kernel: 'nobody cared! (screaming interrupt?)'



Norman Elton wrote:

Stephen,

Turns out, there was new firmware from Sun. It's been applied, and we're still having the problem. I've also tried rebooting with "acpi=off", but no luck there either.
There are some module parameters which are related to interrupts
modinfo e1000
parm:           TxIntDelay:Transmit Interrupt Delay
parm:           TxAbsIntDelay:Transmit Absolute Interrupt Delay
parm:           RxIntDelay:Receive Interrupt Delay
parm:           RxAbsIntDelay:Receive Absolute Interrupt Delay
parm:           InterruptThrottleRate:Interrupt Throttling Rate

There is no guidance as what to do with them, but if you still have problems it might be worth a deeper look. The kernel source will have info on these parameters.

John.


Anyone have any other ideas? This is a pretty bizarre error condition.

Thanks,

Norman

On Apr 25, 2006, at 11:54 AM, Stephen John Smoogen wrote:

On 4/25/06, Norman Elton <normelton gmail com> wrote:

Yesterday, I upgraded a server to the latest kernel of RHELv4, and
rebooted. The box seemed to come online without a hitch. After a few
hours, I got this message...


The first thing with these sort of errors.. I check that the box has
the latest firmware from the manufacturer. 9 out of 10 times, the
problem has been fixed in firmware.



--
Stephen J Smoogen.
CSIRT/Linux System Administrator

--
nahant-list mailing list
nahant-list redhat com
https://www.redhat.com/mailman/listinfo/nahant-list


--
nahant-list mailing list
nahant-list redhat com
https://www.redhat.com/mailman/listinfo/nahant-list





--
John Newbigin
Computer Systems Officer
Faculty of Information and Communication Technologies
Swinburne University of Technology
Melbourne, Australia
http://www.ict.swin.edu.au/staff/jnewbigin


[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]