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:16:46 +0100 [thread overview]
Message-ID: <3BDDAB1E.11F14220@Synopsys.COM> (raw)
In-Reply-To: <3BDD9FF4.D54DC0C9@Synopsys.COM> <3BDDA4C0.F4391EC@zip.com.au>
Hi Andrew,
Andrew Morton wrote:
>
> Harald Dunkel wrote:
> >
> > Hi folks,
> >
> > Does anybody know what this message in kern.log means?
> >
> > eth0: command 0x3002 did not complete! Status=0xffff
> >
>
> There's a function in the driver which issues reset commands to the
> hardware and then spins, waiting for completion. Usually it takes
> a single PCI cycle. In your case it timed out.
>
> It look to me like the NIC is powered down. Could you please
> send me a bunch of info:
>
> - Does the interface actually work after this message, or is
> it dead?
>
A ping to the assigned IP address works. But I cannot get a PPPoE
connection.
> - If the latter, did you warmboot from another OS?
>
I've got just Linux. The problem occurs after a warm boot as
it seems. When I do a power-down reset, then I don't get this
message, but I don't get a connection via PPPoE, either.
> - Does it help if you add the line
>
> options 3c59x enable_wol=1
>
> to /etc/modules.conf? (This is a misnomer - enable_wol
> enables the driver's power management functions).
>
No, this did not help. I found an old EMail with the suggestion
to add enable_wol=0, but this didn't help, either.
The problem came up this morning (12 hours ago). Before the it was
working, AFAICT.
Regards
Harri
next prev parent reply other threads:[~2001-10-29 19:17 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 [this message]
2001-10-29 19:50 ` Harald Dunkel
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=3BDDAB1E.11F14220@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