Linux-kernel mailing list archive 1999-23,: Re: 3com 905 card failure again (network crash)

# Re: 3com 905 card failure again (network crash)

Michael Merhej (michael@pmcl.ph.utexas.edu)
Tue, 8 Jun 1999 17:36:26 -0500 (CDT)

- Messages sorted by: [ date ][ thread ][ subject ][ author ]
- Next message: B. James Phillippe: "Re: kernel_thread..."
- Previous message: Richard Gooch: "Re: Devfs, was Re: Migrating to larger numbers"

Its the original 905 purchased about 6 months ago. Its pre 905b-
Boomerang driver, not the Cyclone driver (905b) running at 100MBits.

On Tue, 8 Jun 1999, Martin Moerman Linux Ham wrote:

>
> Can you give us the last digit on the Main chip (asic version)??
> there has been 3 or 4 different versions of 905.
>
> Thnx
> /mamoman
>
> On Tue, 8 Jun 1999, Michael Merhej wrote:
>
> > Does anybody know what this might mean? This started happening with
> > kernel 2.2.9 (kernel 2.2.7 never had this problem). This has happened at
> > least 3 times now where the machine is useable, but the nic and
> > network connection blows up after some random hours of usage. The machine
> > configuration is simple, with only two expansion cards in place - video
> > and nic.
> >
> > Jun 7 20:09:10 web3 kernel: Unable to handle
> > kernel paging request at
> > virtual address ffffff0b
> > Jun 7 20:09:10 web3 kernel: current->tss.cr3 = 00101000, %cr3 = 00101000
> > Jun 7 20:09:10 web3 kernel: *pde = 00257067
> > Jun 7 20:09:10 web3 kernel: *pte = 00000000
> > Jun 7 20:09:10 web3 kernel: Oops: 0000
> > Jun 7 20:09:10 web3 kernel: CPU: 0
> > Jun 7 20:09:10 web3 kernel: EIP: 0010:[<ffffff0b>]
> > Jun 7 20:09:10 web3 kernel: EFLAGS: 00010046
> > Jun 7 20:09:10 web3 kernel: eax: 00000000 ebx: c0226000 ecx: c8afa000
> > edx: c0226000
> > Jun 7 20:09:10 web3 kernel: esi: 0009e200 edi: c0106000 ebp: 00001000
> > esp: c0227fe0
> > Jun 7 20:09:10 web3 kernel: ds: 0018 es: 0018 ss: 0018
> > Jun 7 20:09:10 web3 kernel: Process swapper (pid: 0, process nr: 0,
> > stackpage=c0227000)
> > Jun 7 20:09:10 web3 kernel: Stack: 00000246 00000000 c0228c8d 00000000
> > c0106000 00000000 c020ad3c c01001b1
> > Jun 7 20:09:10 web3 kernel: Call Trace: [get_options+0/116] [L6+0/2]
> > Jun 7 20:09:10 web3 kernel: Code: <1>Unable to handle kernel paging
> > request at virtual address ffffff0b
> > Jun 7 20:09:10 web3 kernel: current->tss.cr3 = 00101000, %cr3 = 00101000
> > Jun 7 20:09:10 web3 kernel: *pde = 00257067
> > Jun 7 20:09:10 web3 kernel: *pte = 00000000
> > Jun 7 20:09:21 web3 kernel: eth0: transmit timed out, tx_status 00 status
> > e601.
> > Jun 7 20:09:21 web3 kernel: eth0: Interrupt posted but not delivered --
> > IRQ blocked by another device?
> > Jun 7 20:09:31 web3 kernel: eth0: transmit timed out, tx_status 00 status
> > e000.
> > Jun 7 20:09:46 web3 kernel: eth0: transmit timed out, tx_status 00 status
> > e000.
> > Jun 7 20:09:51 web3 kernel: eth0: transmit timed out, tx_status 00 status
> > e000.
> >
> >
> > Below is the 3com boot information:
> > Jun 7 16:19:02 web3 kernel: eth0: 3Com 3c905 Boomerang 100baseTx at
> > 0xef00, 00:10:4b:33:51:17, IRQ 9
> > Jun 7 16:19:02 web3 kernel: 8K word-wide RAM 3:5 Rx:Tx split,
> > autoselect/MII interface.
> > Jun 7 16:19:02 web3 kernel: MII transceiver found at address 24, status
> > 786f.
> > Jun 7 16:19:02 web3 kernel: Enabling bus-master transmits and
> > whole-frame receives.
> >
> > Thanks for your time
> >
> >
> >
> > -
> > To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> > the body of a message to majordomo@vger.rutgers.edu
> > Please read the FAQ at http://www.tux.org/lkml/
> >
>

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/

- Next message: B. James Phillippe: "Re: kernel_thread..."
- Previous message: Richard Gooch: "Re: Devfs, was Re: Migrating to larger numbers"