lkml.org 
[lkml]   [2004]   [May]   [31]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
    /
    Date
    From
    SubjectRe: PROBLEM: network driver causes kernel panic
    On Mon, 31 May 2004 06:18:30 +0000, Casey Tucker wrote:
    [only the relevent fragments]
    >1. Kernel panic when connector removed from eth1
    >
    >2. When i remove the RJ-45 connector from the input jack of eth1 on my
    >machine, kernel panics. Unfortunately, I cannot give the specific output of
    >the crash. I believe the driver is tulip, however not being able to remember
    >which card is which, it may indeed be the natsemi driver.
    ...
    >4. Linux version 2.6.6 (root@whiteguy) (gcc version 3.2.3) #1 Mon May 10
    ...
    >d400-d41f : 0000:00:07.2
    >d800-d87f : 0000:00:0f.0
    > d800-d87f : de2104x
    >dc00-dc1f : 0000:00:10.0
    > dc00-dc1f : EMU10K1
    >e000-e007 : 0000:00:10.1
    >e400-e4ff : 0000:00:13.0
    > e400-e4ff : eth0
    ...
    >00:0f.0 Ethernet controller: Digital Equipment Corporation DECchip 21041
    >[Tulip Pass 3] (rev 21)
    > 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: 32
    > Interrupt: pin A routed to IRQ 11
    > Region 0: I/O ports at d800 [size=128]
    ...
    >00:13.0 Ethernet controller: National Semiconductor Corporation DP83815
    >(MacPhyter) Ethernet Controller
    > Subsystem: Netgear: Unknown device f311
    > 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: 32 (2750ns min, 13000ns max)
    > Interrupt: pin A routed to IRQ 5
    > Region 0: I/O ports at e400 [size=256]

    This confirms that eth1 is a 21041 driven by the de2104x driver.

    I've seen something very similar to Casey's problem, on a PowerMac
    with a built-in 21041. Booting it with no network cable connected
    causes a timer to hit a BUG() in de2104x about a second after
    the device is ifup:d.

    The 2.4 kernel's tulip driver works just fine.

    I reported this last year, but nothing happened.

    A workaround is to use the de4x5 driver instead.
    -
    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to majordomo@vger.kernel.org
    More majordomo info at http://vger.kernel.org/majordomo-info.html
    Please read the FAQ at http://www.tux.org/lkml/

    \
     
     \ /
      Last update: 2005-03-22 14:03    [W:7.398 / U:0.012 seconds]
    ©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site