> Rakotomandimby, can you try attached patch?
I tried.
> It would solve the problem
No: (/var/log/message)
Sep 14 18:37:01 kernel: NETDEV WATCHDOG: eth0: transmit timed out
Sep 14 18:37:02 kernel: NETDEV WATCHDOG: eth0: transmit timed out
Sep 14 18:37:02 kernel: NETDEV WATCHDOG: eth0: transmit timed out
I still have to desactivate acpi to have network.
> And please send dmesg, lspci -vvvxxx, cat /proc/interrupts,
Attached.
> 8259A.pl,
root-localhost>>>>./8259A.pl
irq 0: 00, edge
irq 1: 00, edge
irq 2: 00, edge
irq 3: 00, edge
irq 4: 00, edge
irq 5: 00, edge
irq 6: 00, edge
irq 7: 00, edge
irq 8: 0c, edge
irq 9: 0c, edge
irq 10: 0c, level
irq 11: 0c, level
irq 12: 0c, edge
irq 13: 0c, edge
irq 14: 0c, edge
irq 15: 0c, edge
> mptable.
What's that?
(Not found)
> In some cases, we may be able to add workaround. But we need to find
> the cause of problem before it.
Well, my computer is a notebook (CompaQ R4000), with a very restricted
set of settings in the BIOS. I cannot deactivate what Nick Warne told.
Desactivate acpi on a notebook is a bit frustrating :-)
The only solution would be to apply the patch.
I apologize for the delay, but now, if you suggest me a patch I will
apply it immediately.
--
Administration & Formation ? l'administration
de serveurs d?di?s:
http://www.google.fr/search?q=aspo+infogerance+serveur
Rakotomandimby Mihamina <[email protected]> writes:
> Well, my computer is a notebook (CompaQ R4000), with a very restricted
> set of settings in the BIOS. I cannot deactivate what Nick Warne told.
> Desactivate acpi on a notebook is a bit frustrating :-)
> The only solution would be to apply the patch.
This seems not edge/level triggered problem. Probably, IRQ routing or
somethig. Since I don't know ATI chipset at all, I'm not
helpful man. Sorry.
--
OGAWA Hirofumi <[email protected]>