Luigi,
Unless you have a completely different cause I believe the patches I
just posted will fix the issue. If you can test and confirm this that
would be great.
Eric
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More
"Luigi Genoni" <[EMAIL PROTECTED]> writes:
> the message appeared just once, but no crash.
> anyway the load average was really abnormal.
Good. You tested it and it worked!
High load average is interesting, because it has similar causes
as the "No irq handler for vector", but technically they
"Luigi Genoni" <[EMAIL PROTECTED]> writes:
> I tested the patch, but I could not really stress the HW.
> anyway no crash, but load average is somehow abnormal, higher than it should
> be.
Thanks. Did you get any nasty messages about "No irq handler for vector?"
If not then you never even hit
Luigi Genoni [EMAIL PROTECTED] writes:
I tested the patch, but I could not really stress the HW.
anyway no crash, but load average is somehow abnormal, higher than it should
be.
Thanks. Did you get any nasty messages about No irq handler for vector?
If not then you never even hit the
Luigi Genoni [EMAIL PROTECTED] writes:
the message appeared just once, but no crash.
anyway the load average was really abnormal.
Good. You tested it and it worked!
High load average is interesting, because it has similar causes
as the No irq handler for vector, but technically they are
Luigi,
Unless you have a completely different cause I believe the patches I
just posted will fix the issue. If you can test and confirm this that
would be great.
Eric
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More
> Ok. I've finally figured out what is going on. The code is race free but the
> programmer was an
> idiot.
Hi,
Could this IRQ problem account for this bug as well, please? Or is yours
strictly a 2.6.19.x
issue?
http://bugzilla.kernel.org/show_bug.cgi?id=7847
I have a dual P4 Xeon box (HT
Ok. I've finally figured out what is going on. The code is race free but the
programmer was an
idiot.
Hi,
Could this IRQ problem account for this bug as well, please? Or is yours
strictly a 2.6.19.x
issue?
http://bugzilla.kernel.org/show_bug.cgi?id=7847
I have a dual P4 Xeon box (HT
"Luigi Genoni" <[EMAIL PROTECTED]> writes:
> OK,
> willing to test any patch.
Ok. I've finally figured out what is going on. The code is
race free but the programmer was an idiot.
In the local apic there are two relevant registers.
ISR (in service register) describing all of the
interrupts
"Luigi Genoni" <[EMAIL PROTECTED]> writes:
> OK,
> willing to test any patch.
Sure. After I get things working on this end I will copy you,
on any fixes so you can confirm they work for you.
I am still root causing this but I have found a small fix that should
keep the system from going down
<[EMAIL PROTECTED]> writes:
> I have in interesting update, at less I suppose I have.
It was, at least as another data point.
> I do not know very well what happens with irq stuff migrating shared irq, but
> I
> suppose this has something to do with this crash.
The fact the irq was shared
[EMAIL PROTECTED] writes:
I have in interesting update, at less I suppose I have.
It was, at least as another data point.
I do not know very well what happens with irq stuff migrating shared irq, but
I
suppose this has something to do with this crash.
The fact the irq was shared should
Luigi Genoni [EMAIL PROTECTED] writes:
OK,
willing to test any patch.
Sure. After I get things working on this end I will copy you,
on any fixes so you can confirm they work for you.
I am still root causing this but I have found a small fix that should
keep the system from going down when
Luigi Genoni [EMAIL PROTECTED] writes:
OK,
willing to test any patch.
Ok. I've finally figured out what is going on. The code is
race free but the programmer was an idiot.
In the local apic there are two relevant registers.
ISR (in service register) describing all of the
interrupts that the
"Luigi Genoni" <[EMAIL PROTECTED]> writes:
> reproduced.
> it took more or less one hour to reproduce it. I could reproduce it olny
> running also irqbalance 0.55 and commenting out the sleep 1. The message in
> syslog is the same and then, after a few seconds I think, KABOM! system crash
>
reproduced.
it took more or less one hour to reproduce it. I could reproduce it olny
running also irqbalance 0.55 and commenting out the sleep 1. The message
in
syslog is the same and then, after a few seconds I think, KABOM! system
crash
and reboot.
I tested also a similar system that has 4
reproduced.
it took more or less one hour to reproduce it. I could reproduce it olny
running also irqbalance 0.55 and commenting out the sleep 1. The message
in
syslog is the same and then, after a few seconds I think, KABOM! system
crash
and reboot.
I tested also a similar system that has 4
Luigi Genoni [EMAIL PROTECTED] writes:
reproduced.
it took more or less one hour to reproduce it. I could reproduce it olny
running also irqbalance 0.55 and commenting out the sleep 1. The message in
syslog is the same and then, after a few seconds I think, KABOM! system crash
and
"Luigi Genoni" <[EMAIL PROTECTED]> writes:
> (e-mail resent because not delivered using my other e-mail account)
>
> Hi,
> this night a linux server 8 dual core CPU Optern 2600Mhz crashed just after
> giving this message
>
> Jan 22 04:48:28 frey kernel: do_IRQ: 1.98 No irq handler for vector
Ok.
Luigi Genoni [EMAIL PROTECTED] writes:
(e-mail resent because not delivered using my other e-mail account)
Hi,
this night a linux server 8 dual core CPU Optern 2600Mhz crashed just after
giving this message
Jan 22 04:48:28 frey kernel: do_IRQ: 1.98 No irq handler for vector
Ok. This
20 matches
Mail list logo
