Messages in this thread |  | | | Date | Thu, 30 Oct 2008 18:45:38 -0600 | | From | Robert Hancock <> | | Subject | Re: 2.6.28-rc2 hates my e1000e |
| |
Jonathan Corbet wrote: > I tried booting -rc2 on my desktop system today. All seems well until > I try to access the net; eth0 doesn't exist anymore. dmesg tells me: > > Oct 30 17:29:38 bike kernel: e1000e: Intel(R) PRO/1000 Network Driver - 0.3.3.3-k6 > Oct 30 17:29:38 bike kernel: e1000e: Copyright (c) 1999-2008 Intel Corporation. > Oct 30 17:29:38 bike kernel: e1000e 0000:00:19.0: PCI INT A -> GSI 21 (level, low) -> IRQ 21 > Oct 30 17:29:38 bike kernel: e1000e 0000:00:19.0: BAR 0: can't reserve mem region [0xfe9e0000-0xfe9fffff] > Oct 30 17:29:38 bike kernel: e1000e 0000:00:19.0: PCI INT A disabled > Oct 30 17:29:38 bike kernel: e1000e: probe of 0000:00:19.0 failed with error -16 > > Here's what lspci thinks of my device: > > 00:19.0 Ethernet controller: Intel Corporation 82566DM-2 Gigabit Network Connection (rev 02) > Subsystem: Dell OptiPlex 755 > Control: I/O+ Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- DisINTx- > Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx- > Interrupt: pin A routed to IRQ 21 > Region 0: Memory at fe9e0000 (32-bit, non-prefetchable) [size=128K] > Region 1: Memory at fe9db000 (32-bit, non-prefetchable) [size=4K] > Region 2: I/O ports at ecc0 [size=32] > Capabilities: [c8] Power Management version 2 > Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA PME(D0+,D1-,D2-,D3hot+,D3cold+) > Status: D0 PME-Enable- DSel=0 DScale=1 PME- > Capabilities: [d0] Message Signalled Interrupts: Mask- 64bit+ Count=1/1 Enable- > Address: 0000000000000000 Data: 0000 > Capabilities: [e0] PCIe advanced features <?> > Kernel modules: e1000e > > Interestingly, under 2.6.27 it reads thus: > > 00:19.0 Ethernet controller: Intel Corporation 82566DM-2 Gigabit Network Connection (rev 02) > Subsystem: Dell OptiPlex 755 > Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- DisINTx+ > Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx- > Latency: 0 > Interrupt: pin A routed to IRQ 4350 > Region 0: Memory at d4200000 (32-bit, non-prefetchable) [size=128K] > Region 1: Memory at d4225000 (32-bit, non-prefetchable) [size=4K] > Region 2: I/O ports at ecc0 [size=32] > Capabilities: [c8] Power Management version 2 > Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA PME(D0+,D1-,D2-,D3hot+,D3cold+) > Status: D0 PME-Enable- DSel=0 DScale=1 PME- > Capabilities: [d0] Message Signalled Interrupts: Mask- 64bit+ Count=1/1 Enable+ > Address: 00000000fee0200c Data: 4181 > Capabilities: [e0] PCIe advanced features <?> > Kernel driver in use: e1000e > > The I/O memory has moved, I have no idea why. I assume that's a feature? > > So...what else can I do to help track this one down?
What's in /proc/iomem? Full dmesg output from boot would also be useful.
|  |