From: Paul Collins <paul@briny.ondioline.org>
To: Michael Buesch <mb@bu3sch.de>
Cc: bcm43xx-dev@lists.berlios.de, netdev@vger.kernel.org
Subject: bcm43xx: "transmit timed out" and apparent hang with "preemptible periodic work" patches
Date: Mon, 26 Jun 2006 12:28:03 +1000 [thread overview]
Message-ID: <87ac80ps5o.fsf@briny.internal.ondioline.org> (raw)
With the bcm43xx periodic work patches that recently made it into
Linus's tree, my PowerBook does not survive running overnight.
Yesterday I reverted
91769e7dd9cef7988dc4280f74ed168351beb5b8 [PATCH] bcm43xx: preemptible periodic work
78ff56a06edc3407996173daf63e48f6b90c7062 [PATCH] bcm43xx: redesign locking
and it was still alive this morning.
The following is logged, but that may not be all since the screen was
turned off and kern.log was marked for no-fsync.
Jun 24 06:53:41 briny kernel: NETDEV WATCHDOG: eth1: transmit timed out
Jun 24 06:53:41 briny kernel: bcm43xx: Controller RESET (TX timeout) ...
Jun 24 06:53:41 briny kernel: bcm43xx: Chip ID 0x4306, rev 0x3
Jun 24 06:53:41 briny kernel: bcm43xx: Number of cores: 5
Jun 24 06:53:41 briny kernel: bcm43xx: Core 0: ID 0x800, rev 0x4, vendor 0x4243, enabled
Jun 24 06:53:41 briny kernel: bcm43xx: Core 1: ID 0x812, rev 0x5, vendor 0x4243, disabled
Jun 24 06:53:41 briny kernel: bcm43xx: Core 2: ID 0x80d, rev 0x2, vendor 0x4243, enabled
Jun 24 06:53:41 briny kernel: bcm43xx: Core 3: ID 0x807, rev 0x2, vendor 0x4243, disabled
Jun 24 06:53:41 briny kernel: bcm43xx: Core 4: ID 0x804, rev 0x9, vendor 0x4243, enabled
Jun 24 06:53:41 briny kernel: bcm43xx: PHY connected
Jun 24 06:53:41 briny kernel: bcm43xx: Detected PHY: Version: 2, Type 2, Revision 2
Jun 24 06:53:41 briny kernel: bcm43xx: Detected Radio: ID: 2205017f (Manuf: 17f Ver: 2050 Rev: 2)
Jun 24 06:53:41 briny kernel: bcm43xx: Radio turned off
Jun 24 06:53:41 briny kernel: bcm43xx: Radio turned off
Jun 24 06:53:41 briny kernel: bcm43xx: Controller restarted
Config options:
CONFIG_BCM43XX=m
CONFIG_BCM43XX_DEBUG=y
CONFIG_BCM43XX_DMA=y
CONFIG_BCM43XX_PIO=y
CONFIG_BCM43XX_DMA_AND_PIO_MODE=y
# CONFIG_BCM43XX_DMA_MODE is not set
# CONFIG_BCM43XX_PIO_MODE is not set
And "preemptible" made me check for PREEMPT options:
# CONFIG_PREEMPT_NONE is not set
CONFIG_PREEMPT_VOLUNTARY=y
# CONFIG_PREEMPT is not set
--
Paul Collins
Melbourne, Australia
Dag vijandelijk luchtschip de huismeester is dood
next reply other threads:[~2006-06-26 2:30 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-26 2:28 Paul Collins [this message]
2006-06-26 12:43 ` bcm43xx: "transmit timed out" and apparent hang with "preemptible periodic work" patches Michael Buesch
2006-06-26 15:27 ` Michael Buesch
2006-06-29 8:24 ` Paul Collins
2006-06-29 15:07 ` Michael Buesch
2006-06-29 15:22 ` Larry Finger
2006-06-29 15:31 ` Michael Buesch
[not found] ` <200606291731.50598.mb-fseUSCV1ubazQB+pC5nmwQ@public.gmane.org>
2006-06-29 16:16 ` Larry Finger
2006-06-29 16:47 ` Martin Langer
2006-06-29 16:47 ` Michael Buesch
2006-06-29 15:31 ` Paul Collins
2006-06-29 15:49 ` Michael Buesch
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=87ac80ps5o.fsf@briny.internal.ondioline.org \
--to=paul@briny.ondioline.org \
--cc=bcm43xx-dev@lists.berlios.de \
--cc=mb@bu3sch.de \
--cc=netdev@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;
as well as URLs for NNTP newsgroup(s).