public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
* Network error with Intel E1000 Adapter on update 2.4.25 ==> 2.6.3
@ 2004-02-27 12:22 Martin Bene
  2004-02-27 12:38 ` Marc-Christian Petersen
  0 siblings, 1 reply; 7+ messages in thread
From: Martin Bene @ 2004-02-27 12:22 UTC (permalink / raw)
  To: linux-kernel

When trying to update the kernel from 2.4.25 to 2.6.3 I run into a probelm:

While the driver for the onboard Intel E1000 network adapter loads OK, it doesn't seem to find an interrupt for the interface - ifconfig shows:

eth0      Link encap:Ethernet  HWaddr 00:0E:A6:2D:7A:64
          BROADCAST MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)
          Base address:0x9000 Memory:fc000000-fc020000

Trying to configure the infterface results in a frozen system.

Running the system with 2.4.25 kernel works OK and shows 

eth0      Link encap:Ethernet  HWaddr 00:0E:A6:2D:7A:64
          BROADCAST MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)
          Interrupt:18 Base address:0x9000 Memory:fc000000-fc020000

and works OK. 

/proc/interrupts for 2.4.25

           CPU0       CPU1
  0:      19341          0    IO-APIC-edge  timer
  1:          2          0    IO-APIC-edge  keyboard
  2:          0          0          XT-PIC  cascade
  3:          0          0    IO-APIC-edge  serial
  8:          1          0    IO-APIC-edge  rtc
  9:          0          0   IO-APIC-level  acpi
 14:       1591          0    IO-APIC-edge  ide0
 15:       1823          1    IO-APIC-edge  ide1
 18:         57          0   IO-APIC-level  eth0
 22:       2888          0   IO-APIC-level  eth1
 23:          2          0   IO-APIC-level  libata
NMI:          0          0
LOC:      19270      19268
ERR:          0
MIS:          0

/proc/interrupts for 2.6.3
           CPU0       CPU1
  0:     640029          0    IO-APIC-edge  timer
  1:          9          0    IO-APIC-edge  i8042
  2:          0          0          XT-PIC  cascade
  3:          0          0    IO-APIC-edge  serial
  8:          1          0    IO-APIC-edge  rtc
  9:          0          0   IO-APIC-level  acpi
 12:         84          0    IO-APIC-edge  i8042
 14:       1368          0    IO-APIC-edge  ide0
 15:       1316          0    IO-APIC-edge  ide1
 22:       3212          0   IO-APIC-level  eth1
 23:          2          0   IO-APIC-level  libata
NMI:          0          0
LOC:     640020     640019
ERR:          0
MIS:          0

Board is an Asus PC-DL, Intel 875P Chipset, one Xeon 2.8Ghz CPU, Onboard e1000 Network interface. Any idea how I can get the onboard NIC to work?

Thanks, Martin

^ permalink raw reply	[flat|nested] 7+ messages in thread

* Re: Network error with Intel E1000 Adapter on update 2.4.25 ==> 2.6.3
  2004-02-27 12:22 Network error with Intel E1000 Adapter on update 2.4.25 ==> 2.6.3 Martin Bene
@ 2004-02-27 12:38 ` Marc-Christian Petersen
  2004-02-27 17:54   ` Martin Josefsson
  0 siblings, 1 reply; 7+ messages in thread
From: Marc-Christian Petersen @ 2004-02-27 12:38 UTC (permalink / raw)
  To: linux-kernel; +Cc: Martin Bene

On Friday 27 February 2004 13:22, Martin Bene wrote:

Hi Martin,

> When trying to update the kernel from 2.4.25 to 2.6.3 I run into a probelm:
> While the driver for the onboard Intel E1000 network adapter loads OK, it
> doesn't seem to find an interrupt for the interface - ifconfig shows:
> eth0      Link encap:Ethernet  HWaddr 00:0E:A6:2D:7A:64
>           BROADCAST MULTICAST  MTU:1500  Metric:1
>           RX packets:0 errors:0 dropped:0 overruns:0 frame:0
>           TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
>           collisions:0 txqueuelen:1000
>           RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)
>           Base address:0x9000 Memory:fc000000-fc020000
> [ ... ripped the rest ... ]
> Board is an Asus PC-DL, Intel 875P Chipset, one Xeon 2.8Ghz CPU, Onboard
> e1000 Network interface. Any idea how I can get the onboard NIC to work?

full output of /var/log/dmesg || dmesg after bootup might help.

ciao, Marc


^ permalink raw reply	[flat|nested] 7+ messages in thread

* Re: Network error with Intel E1000 Adapter on update 2.4.25 ==> 2.6.3
  2004-02-27 12:38 ` Marc-Christian Petersen
@ 2004-02-27 17:54   ` Martin Josefsson
  0 siblings, 0 replies; 7+ messages in thread
From: Martin Josefsson @ 2004-02-27 17:54 UTC (permalink / raw)
  To: Marc-Christian Petersen; +Cc: linux-kernel, Martin Bene

[-- Attachment #1: Type: text/plain, Size: 1236 bytes --]

On Fri, 2004-02-27 at 13:38, Marc-Christian Petersen wrote:
> On Friday 27 February 2004 13:22, Martin Bene wrote:
> 
> Hi Martin,
> 
> > When trying to update the kernel from 2.4.25 to 2.6.3 I run into a probelm:
> > While the driver for the onboard Intel E1000 network adapter loads OK, it
> > doesn't seem to find an interrupt for the interface - ifconfig shows:
> > eth0      Link encap:Ethernet  HWaddr 00:0E:A6:2D:7A:64
> >           BROADCAST MULTICAST  MTU:1500  Metric:1
> >           RX packets:0 errors:0 dropped:0 overruns:0 frame:0
> >           TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
> >           collisions:0 txqueuelen:1000
> >           RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)
> >           Base address:0x9000 Memory:fc000000-fc020000
> > [ ... ripped the rest ... ]
> > Board is an Asus PC-DL, Intel 875P Chipset, one Xeon 2.8Ghz CPU, Onboard
> > e1000 Network interface. Any idea how I can get the onboard NIC to work?
> 
> full output of /var/log/dmesg || dmesg after bootup might help.

e1000 is known to have problems in 2.6.3

Please try the latest 2.6.3-bk snapshot, it may work better, it has
helped at least one other reporter of e1000 problems in 2.6.3

-- 
/Martin

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

^ permalink raw reply	[flat|nested] 7+ messages in thread

* Re: Network error with Intel E1000 Adapter on update 2.4.25 ==> 2.6.3
@ 2004-02-28 11:52 Martin Bene
  0 siblings, 0 replies; 7+ messages in thread
From: Martin Bene @ 2004-02-28 11:52 UTC (permalink / raw)
  To: linux-kernel

>> When trying to update the kernel from 2.4.25 to 2.6.3 I run 
>> into a probelm:
>> While the driver for the onboard Intel E1000 network adapter 
>> loads OK, it
>> doesn't seem to find an interrupt for the interface - ifconfig shows:
>> eth0      Link encap:Ethernet  HWaddr 00:0E:A6:2D:7A:64
>>           BROADCAST MULTICAST  MTU:1500  Metric:1
>>           RX packets:0 errors:0 dropped:0 overruns:0 frame:0
>>           TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
>>           collisions:0 txqueuelen:1000
>>           RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)
>>           Base address:0x9000 Memory:fc000000-fc020000
>> Board is an Asus PC-DL, Intel 875P Chipset, one Xeon 2.8Ghz 
>> CPU, Onboard
>> e1000 Network interface. Any idea how I can get the onboard 
>> NIC to work?

>full output of /var/log/dmesg || dmesg after bootup might help.

Some more information: 

* Update to 2.6.4-rc1 doesn't help, same situation as before.
* 2.4.25 finds/uses int 18
* Binary search shows that the problem first appears with 2.6.2-bk1; 2.6.2 works OK.

Further search shows that it's the e1000 driver update from 5.2.20 to 5.2.30.1 that breaks things for me. copying the older driver into a newer kernel works.

Hmm, changelog states what looks like a possible candidate: 

*   o Use pdev->irq rather than netdev->irq in preparation for MSI support.

Final information:

Backing out the pdev->irq <-> netdev->irq changes gives me ifconfig output with the correct interrupt listed; unfortunately, 
	ifconfig eth0 up 
still locks the machine, so that doesn't seem to be the only problem.

Bye, Martin

^ permalink raw reply	[flat|nested] 7+ messages in thread

* RE: Network error with Intel E1000 Adapter on update 2.4.25 ==> 2.6.3
@ 2004-03-01 19:00 Feldman, Scott
  0 siblings, 0 replies; 7+ messages in thread
From: Feldman, Scott @ 2004-03-01 19:00 UTC (permalink / raw)
  To: Martin Bene, linux-kernel


> Board is an Asus PC-DL, Intel 875P Chipset, one Xeon 2.8Ghz 
> CPU, Onboard e1000 Network interface. Any idea how I can get 
> the onboard NIC to work?

Martin, give 2.6.4-rc1 a try.  It removes a patch to e1000 that broke a
lot of folks with 875/CSA.

-scott

^ permalink raw reply	[flat|nested] 7+ messages in thread

* Re: Network error with Intel E1000 Adapter on update 2.4.25 ==> 2.6.3
@ 2004-03-02  6:15 Martin Bene
  0 siblings, 0 replies; 7+ messages in thread
From: Martin Bene @ 2004-03-02  6:15 UTC (permalink / raw)
  To: Feldman, Scott, linux-kernel

Hi Scott,

>> Board is an Asus PC-DL, Intel 875P Chipset, one Xeon 2.8Ghz 
>> CPU, Onboard e1000 Network interface. Any idea how I can get 
>> the onboard NIC to work?
>
>Martin, give 2.6.4-rc1 a try.  It removes a patch to e1000 that broke a
>lot of folks with 875/CSA.

Thanks for the hint. Results:

 - Network interface works, no more lockups.
 - ifconfig still doesn't show the interupt being used.
 - /proc/interrupts DOES show the right interrupt.

experimenting with the driver source shows that the interrupt displayed by ifconfig seems to depend on netdev->irq being set; this was removed during the netdev->irq ==> adapter->pdev->irq change. adding the following line corrects ifconfig display:

diff -urN e1000_old/e1000_main.c e1000/e1000_main.c
--- e1000_old/e1000_main.c      Mon Mar  1 09:16:29 2004
+++ e1000/e1000_main.c  Tue Mar  2 07:09:37 2004
@@ -452,6 +452,8 @@
	netdev->poll_controller = e1000_netpoll;
 #endif

+	netdev->irq = pdev->irq;
+
	netdev->mem_start = mmio_start;
	netdev->mem_end = mmio_start + mmio_len;
	netdev->base_addr = adapter->hw.io_base;

Bye, Martin

^ permalink raw reply	[flat|nested] 7+ messages in thread

* RE: Network error with Intel E1000 Adapter on update 2.4.25 ==> 2.6.3
@ 2004-03-02 18:22 Feldman, Scott
  0 siblings, 0 replies; 7+ messages in thread
From: Feldman, Scott @ 2004-03-02 18:22 UTC (permalink / raw)
  To: Martin Bene, linux-kernel

> experimenting with the driver source shows that the interrupt 
> displayed by ifconfig seems to depend on netdev->irq being 
> set; this was removed during the netdev->irq ==> 
> adapter->pdev->irq change. adding the following line corrects 
> ifconfig display:

Caching pdev->irq in netdev->irq is problematic because pdev->irq can
change after registering for MSI interrupts, for example.  netdev->irq
is vestigial from the days of manual irq assignment.

Bottom line is you'll not see the irq with ifconfig, but it'll be there
in /proc and lspci.

-scott

^ permalink raw reply	[flat|nested] 7+ messages in thread

end of thread, other threads:[~2004-03-02 18:22 UTC | newest]

Thread overview: 7+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2004-02-27 12:22 Network error with Intel E1000 Adapter on update 2.4.25 ==> 2.6.3 Martin Bene
2004-02-27 12:38 ` Marc-Christian Petersen
2004-02-27 17:54   ` Martin Josefsson
  -- strict thread matches above, loose matches on Subject: below --
2004-02-28 11:52 Martin Bene
2004-03-01 19:00 Feldman, Scott
2004-03-02  6:15 Martin Bene
2004-03-02 18:22 Feldman, Scott

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox