Am Dienstag, 14. September 2004 00:02 schrieb Francois Romieu:
> Hans-Frieder Vogt <hfvogt@xxxxxxxx> :
> > no oops (BUG_ON not triggered)! System boots up as normal, but just after
> > I
> > log in on the console the system freezes, i.e., keyboard does not react
> > any more and the system is not accessible via network.
> - do the keyboard leds or the magic sysrq answer (I assume you boot without
(To be able to exclude any side effect of X, I have booted without X and I
have also removed all graphics driver related modules)
When the system freezes, the keyboard is completely dead, the LEDs do not
react any more and also the sysrq keys do not work.
> - does it make a difference if you boot with the network cable
> unpluged (i.e. fine until pluged then dead when first packet comes in) ?
YES!! With the network cable unplugged, the system does not freeze!
Every 10 seconds, I get now the message:
r8169: eth0: PHY reset until link up
but otherwise everything seems fine.
> > The time from the moment I log in to the time when the system freezes
> > varies, but is in the order of 5s.
> First packet probably. Can you verify this point ?
I think the test with the network cable unplugged supports this assumption.
With network cable unplugged, /proc/interrupts shows 0 interrupts for the
network card, so probably the first interrupt leads to the system freeze.
> > There is no difference whether NAPI is enabled or not.
> I will welcome lspci -vx + gcc version + objdump -S of the r8169 module.
lspci -vx and objdump -S output (gzipped) are attached, gcc version is 3.4.2
(Debian 3.4.2-2), but no visible difference with 3.4.1.
Thanks for your help, Francois.
I will put a few printks into the interrupt routine and hope to be able to
tell you more tomorrow,
Hans-Frieder Vogt e-mail: hfvogt (at) arcor (dot) de
Description: Text document
Description: GNU Zip compressed data