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 20:50:43 +0100 [thread overview]
Message-ID: <3BDDB312.589D2E04@Synopsys.COM> (raw)
In-Reply-To: <3BDD9FF4.D54DC0C9@Synopsys.COM> <3BDDA4C0.F4391EC@zip.com.au>
PS: The message about '0x3002 did not complete' is gone. I haven't seen
it anymore since I added the 'options 3c59x enable_wol=1'.
But now I get this in my syslog:
Oct 29 20:41:19 bilbo pppd[522]: pppd 2.4.1 started by root, uid 0
Oct 29 20:41:20 bilbo pppd[522]: Sending PADI
Oct 29 20:41:20 bilbo kernel: eth0: Transmit error, Tx status register 90.
Oct 29 20:41:20 bilbo kernel: Flags; bus-master 1, dirty 0(0) current 1(1)
Oct 29 20:41:20 bilbo kernel: Transmit list 00000000 vs. df230200.
Oct 29 20:41:20 bilbo kernel: 0: @df230200 length 80000020 status 80000020
Oct 29 20:41:20 bilbo kernel: 1: @df230240 length 00000000 status 00000000
Oct 29 20:41:20 bilbo kernel: 2: @df230280 length 00000000 status 00000000
Oct 29 20:41:20 bilbo kernel: 3: @df2302c0 length 00000000 status 00000000
Oct 29 20:41:20 bilbo kernel: 4: @df230300 length 00000000 status 00000000
Oct 29 20:41:20 bilbo kernel: 5: @df230340 length 00000000 status 00000000
Oct 29 20:41:20 bilbo kernel: 6: @df230380 length 00000000 status 00000000
Oct 29 20:41:20 bilbo kernel: 7: @df2303c0 length 00000000 status 00000000
Oct 29 20:41:20 bilbo kernel: 8: @df230400 length 00000000 status 00000000
Oct 29 20:41:20 bilbo kernel: 9: @df230440 length 00000000 status 00000000
Oct 29 20:41:20 bilbo kernel: 10: @df230480 length 00000000 status 00000000
Oct 29 20:41:20 bilbo kernel: 11: @df2304c0 length 00000000 status 00000000
Oct 29 20:41:20 bilbo kernel: 12: @df230500 length 00000000 status 00000000
Oct 29 20:41:20 bilbo kernel: 13: @df230540 length 00000000 status 00000000
Oct 29 20:41:20 bilbo kernel: 14: @df230580 length 00000000 status 00000000
Oct 29 20:41:20 bilbo kernel: 15: @df2305c0 length 00000000 status 00000000
Oct 29 20:41:20 bilbo kernel: scsi0: PCI error Interrupt at seqaddr = 0x9
Oct 29 20:41:20 bilbo kernel: scsi0: Data Parity Error Detected during address or write data phase
Oct 29 20:41:20 bilbo kernel: scsi1: PCI error Interrupt at seqaddr = 0x9
Oct 29 20:41:20 bilbo kernel: scsi1: Data Parity Error Detected during address or write data phase
Especially interesting is the message about the SCSI. How is this
related to the 3c59x?
Regards
Harri
next prev parent reply other threads:[~2001-10-29 19:51 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 [this message]
2001-10-29 19:58 ` Andrew Morton
2001-10-29 20:34 ` Harald Dunkel
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=3BDDB312.589D2E04@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox