All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nathan Bryant <nbryant@optonline.net>
To: kernel list <linux-kernel@vger.kernel.org>,
	David Ford <david+challenge-response@blue-labs.org>
Subject: Re: swsuspend still breaks 3c905, 2.6.7
Date: Tue, 07 Sep 2004 12:09:23 -0400	[thread overview]
Message-ID: <413DDD33.8020007@optonline.net> (raw)

David Ford wrote:
> Suspend and the 3com card becomes useless.  Have to remove the module or 
> reboot. Seems to be a pretty common and long-standing bug with the power 
> management and has been around since at least the middle 2.5.xx 
> kernels.  And it seems it's also in 2.4.x.

Please test the latest 2.6.9-rc1-mm tree; I've got a patch in there for 
this problem.

Nathan

> 
> NETDEV WATCHDOG: eth0: transmit timed out
> eth0: transmit timed out, tx_status ff status ffff.
>   diagnostics: net ffff media ffff dma ffffffff fifo ffff
> eth0: Transmitter encountered 16 collisions -- network cable problem?
> eth0: Interrupt posted but not delivered -- IRQ blocked by another device?
>   Flags; bus-master 1, dirty 0(0) current 16(0)
>   Transmit list ffffffff vs. e4aae200.
> eth0: command 0x3002 did not complete! Status=0xffff
>   0: @e4aae200  length 8000002a status 0000002a
>   1: @e4aae2a0  length 8000002a status 0000002a
>   2: @e4aae340  length 8000002a status 0000002a
>   3: @e4aae3e0  length 8000002a status 0000002a
>   4: @e4aae480  length 8000004c status 0000004c
>   5: @e4aae520  length 8000002a status 0000002a
>   6: @e4aae5c0  length 8000002a status 0000002a
>   7: @e4aae660  length 8000002a status 0000002a
>   8: @e4aae700  length 8000002a status 0000002a
>   9: @e4aae7a0  length 8000004c status 0000004c
>   10: @e4aae840  length 8000002a status 0000002a
>   11: @e4aae8e0  length 8000002a status 0000002a
>   12: @e4aae980  length 8000002a status 0000002a
>   13: @e4aaea20  length 8000002a status 0000002a
>   14: @e4aaeac0  length 8000004c status 8000004c
>   15: @e4aaeb60  length 8000002a status 8000002a
> eth0: command 0x5800 did not complete! Status=0xffff
> eth0: Resetting the Tx ring pointer.
> 
> 
> Chris root # lspci -v -s 2:0.0
> 02:00.0 Ethernet controller: 3Com Corporation 3c905C-TX/TX-M [Tornado] 
> (rev 78)
>         Subsystem: Dell Computer Corporation: Unknown device 00d4
>         Flags: bus master, medium devsel, latency 32, IRQ 11
>         I/O ports at ec80 [size=128]
>         Memory at f8fffc00 (32-bit, non-prefetchable) [size=128]
>         Expansion ROM at f9000000 [disabled] [size=128K]
>         Capabilities: [dc] Power Management version 2
> 
> 
> David
> 

             reply	other threads:[~2004-09-07 16:12 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-09-07 16:09 Nathan Bryant [this message]
  -- strict thread matches above, loose matches on Subject: below --
2004-07-12  3:42 swsuspend still breaks 3c905, 2.6.7 David Ford

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=413DDD33.8020007@optonline.net \
    --to=nbryant@optonline.net \
    --cc=david+challenge-response@blue-labs.org \
    --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.