From: Andrew Morton <akpm@zip.com.au>
To: harri@synopsys.com
Cc: linux-kernel@vger.kernel.org
Subject: Re: 3c59x:command 0x3002 did not complete! Status=0xffff
Date: Mon, 29 Oct 2001 11:58:24 -0800 [thread overview]
Message-ID: <3BDDB4E0.C90BFACB@zip.com.au> (raw)
In-Reply-To: <3BDD9FF4.D54DC0C9@Synopsys.COM> <3BDDA4C0.F4391EC@zip.com.au> <3BDDB312.589D2E04@Synopsys.COM>
Harald Dunkel wrote:
>
> 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.
0x90 -> Transmit underrun. The NIC wasn't able to get data
from main memory fast enough. Across PCI.
> ...
> Oct 29 20:41:20 bilbo kernel: scsi0: PCI error Interrupt at seqaddr = 0x9
I wonder what that error is?
>
> Especially interesting is the message about the SCSI. How is this
> related to the 3c59x?
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?
next prev parent reply other threads:[~2001-10-29 20:02 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 [this message]
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=3BDDB4E0.C90BFACB@zip.com.au \
--to=akpm@zip.com.au \
--cc=harri@synopsys.com \
--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