No networking since July 28! Only w/ Windows

[sean darcy]

Using rawhide as of July 28.

All of a sudden, my ethernet won't come up. No link lights. But this is 
dual-boot machine, and networking works if I boot up Windows XP.

I've got a Realtek integrated card, and the kernel finds it:

lspci -vv

..............

02:03.0 Ethernet controller: Realtek Semiconductor Co., Ltd. 
RTL-8139/8139C/8139C+ (rev 10)

Subsystem: Hewlett-Packard Company Unknown device 2a26

Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B-

Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- 
<MAbort- >SERR- <PERR-

Latency: 64 (8000ns min, 16000ns max)

Interrupt: pin A routed to IRQ 21

Region 0: I/O ports at dc00 [size=256]

Region 1: Memory at fddff000 (32-bit, non-prefetchable) [size=256]

Capabilities: [50] Power Management version 2

Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=375mA PME(D0-,D1+,D2+,D3hot+,D3cold+)

Status: D0 PME-Enable- DSel=0 DScale=0 PME-



But no link light comes on at the linux machine, or at the router.

dmesg | grep eth0

eth0: RealTek RTL8139 at 0xffffc2000064a000, 00:15:f2:77:86:13, IRQ 21

eth0: Identified 8139 chip type 'RTL-8101'

eth0: link up, 100Mbps, full-duplex, lpa 0x45E1

eth0: no IPv6 routers present

NETDEV WATCHDOG: eth0: transmit timed out

eth0: Transmit timeout, status 0d 0000 c07f media 10.

eth0: Tx queue start entry 4 dirty entry 0.

eth0: Tx descriptor 0 is 0008205a. (queue head)

eth0: Tx descriptor 1 is 0008205a.

eth0: Tx descriptor 2 is 00082156.

eth0: Tx descriptor 3 is 0008204e.

eth0: link up, 100Mbps, full-duplex, lpa 0x45E1

Windows gets the dhcp address from the router. Fedora times out. I've tried 
setting Fedora to a static  address, but then I still can't ping anything, 
including the router. OTOH, fedora gives no error about ifup'ing eth0 with a 
static address.

Completely puzzled. Don't know where or whether to file a bug report.

[Andy Green]

Somebody in the thread at some point said:
>  Using rawhide as of July 28.
>  
>  All of a sudden, my ethernet won't come up. No link lights. But this is 
>  dual-boot machine, and networking works if I boot up Windows XP. 
>  Completely puzzled. Don't know where or whether to file a bug
> report. 
Have a look in /proc/interrupts at the number of interrupts related to
your ethernet card, if it is broken out on its own line.

A box here on 2.6.23-rc1 did the same, with 0 interrupts on the IRQ
assigned to the ethernet device, and adding pci=biosirq to the kernel
commandline got it up again.

-Andy

[sean darcy]

Andy Green wrote:
>  Somebody in the thread at some point said:
> > Using rawhide as of July 28.
> >
> > All of a sudden, my ethernet won't come up. No link lights. But this is 
> > dual-boot machine, and networking works if I boot up Windows XP.
>  
> > Completely puzzled. Don't know where or whether to file a bug report.
>  
>  Have a look in /proc/interrupts at the number of interrupts related to
>  your ethernet card, if it is broken out on its own line.
>  
>  A box here on 2.6.23-rc1 did the same, with 0 interrupts on the IRQ
>  assigned to the ethernet device, and adding pci=biosirq to the kernel
>  commandline got it up again.
>  
>  -Andy
>   
Thanks. I'll try that. I'll be gone for 3 days. For now I'm 
simply using Windows :(

sean

[Steven Bakker]

On Tue, 31 Jul 2007 22:03:41 -0400 sean wrote:

>  > A box here on 2.6.23-rc1 did the same, with 0 interrupts on the
> IRQ
>  > assigned to the ethernet device, and adding pci=biosirq to the
>  > kernel commandline got it up again.
>  
>  Thanks. I'll try that. I'll be gone for 3 days. For now I'm 
>  simply using Windows :( 
That's... less than optimal... :-/

Please see bug #249950 [1] and #249857 [2]. These seem related. All of
the mentioned symptoms go away with the 2.6.22.1-41.fc7 kernel that's in
updates-testing now (see also comment #13 of bug #249857 [3]).

[1] https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=249950
[2] https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=249857
[3] https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=249857#13

Hope this helps.

Cheers,
Steven

[Richard Hughes]

On Tue, 2007-07-31 at 13:11 -0400, gmane wrote:
>  
>  Windows gets the dhcp address from the router. Fedora times out. I've
>  tried 
>  setting Fedora to a static  address, but then I still can't ping
>  anything, 
>  including the router. OTOH, fedora gives no error about ifup'ing eth0
>  with a 
>  static address. 
For me 2.6.22.1-33.fc7 does the same thing as you describe, whereas
2.6.22.1-27.fc7 worked flawlessly.

Richard.