From: Harald Dunkel <harri@synopsys.COM>
To: Andrew Morton <akpm@zip.com.au>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 3c59x:command 0x3002 did not complete! Status=0xffff
Date: Mon, 29 Oct 2001 21:34:40 +0100 [thread overview]
Message-ID: <3BDDBD60.3540EFCA@Synopsys.COM> (raw)
In-Reply-To: <3BDD9FF4.D54DC0C9@Synopsys.COM> <3BDDA4C0.F4391EC@zip.com.au> <3BDDB312.589D2E04@Synopsys.COM> <3BDDB4E0.C90BFACB@zip.com.au>
Andrew Morton wrote:
>
> The PCI bus is screwed up. I haven't seen this before.
> Is the machine otherwise stable? What's special about bringing
> up PPPoE? Have you tested the machine well against other hosts
> on the LAN?
The eth0 has the address 192.168.1.1 . When I do a ping 192.168.1.2,
then I get an error message, too:
Oct 29 21:28:49 bilbo kernel: scsi0: PCI error Interrupt at seqaddr = 0x8
Oct 29 21:28:49 bilbo kernel: scsi0: Data Parity Error Detected during address or write data phase
Oct 29 21:28:49 bilbo kernel: eth0: Transmit error, Tx status register ff.
Oct 29 21:28:49 bilbo kernel: Flags; bus-master 1, dirty 1(1) current 1(1)
Oct 29 21:28:49 bilbo kernel: Transmit list ffffffff vs. df231240.
Oct 29 21:28:49 bilbo kernel: 0: @df231200 length 8000002a status 8000002a
Oct 29 21:28:49 bilbo kernel: 1: @df231240 length 00000000 status 00000000
Oct 29 21:28:49 bilbo kernel: 2: @df231280 length 00000000 status 00000000
Oct 29 21:28:49 bilbo kernel: 3: @df2312c0 length 00000000 status 00000000
Oct 29 21:28:49 bilbo kernel: 4: @df231300 length 00000000 status 00000000
Oct 29 21:28:49 bilbo kernel: 5: @df231340 length 00000000 status 00000000
Oct 29 21:28:49 bilbo kernel: 6: @df231380 length 00000000 status 00000000
Oct 29 21:28:49 bilbo kernel: 7: @df2313c0 length 00000000 status 00000000
Oct 29 21:28:49 bilbo kernel: 8: @df231400 length 00000000 status 00000000
Oct 29 21:28:49 bilbo kernel: 9: @df231440 length 00000000 status 00000000
Oct 29 21:28:49 bilbo kernel: 10: @df231480 length 00000000 status 00000000
Oct 29 21:28:49 bilbo kernel: 11: @df2314c0 length 00000000 status 00000000
Oct 29 21:28:49 bilbo kernel: 12: @df231500 length 00000000 status 00000000
Oct 29 21:28:49 bilbo kernel: 13: @df231540 length 00000000 status 00000000
Oct 29 21:28:49 bilbo kernel: 14: @df231580 length 00000000 status 00000000
Oct 29 21:28:49 bilbo kernel: 15: @df2315c0 length 00000000 status 00000000
Oct 29 21:28:49 bilbo kernel: eth0: Updating statistics failed, disabling stats as an interrupt source.
Oct 29 21:28:49 bilbo kernel: eth0: Host error, FIFO diagnostic register ffff.
Oct 29 21:28:49 bilbo kernel: eth0: PCI bus error, bus status ffffffff
Oct 29 21:28:49 bilbo kernel: scsi1: PCI error Interrupt at seqaddr = 0x8
Oct 29 21:28:49 bilbo kernel: scsi1: Data Parity Error Detected during address or write data phase
PPPoE was not involved in this. It wasn't even started.
Maybe the NIC is broken?
Regards
Harri
next prev parent reply other threads:[~2001-10-29 20:35 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-29 18:29 3c59x:command 0x3002 did not complete! Status=0xffff Harald Dunkel
2001-10-29 18:49 ` Andrew Morton
2001-10-29 19:16 ` Harald Dunkel
2001-10-29 19:50 ` Harald Dunkel
2001-10-29 19:58 ` Andrew Morton
2001-10-29 20:34 ` Harald Dunkel [this message]
2001-10-29 20:53 ` Tim Walberg
2001-10-29 21:22 ` Harald Dunkel
2001-10-29 21:21 ` Wolfgang Rohdewald
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3BDDBD60.3540EFCA@Synopsys.COM \
--to=harri@synopsys.com \
--cc=akpm@zip.com.au \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.