From: Michael Buesch <mb@bu3sch.de>
To: Larry Finger <Larry.Finger@lwfinger.net>
Cc: Paul Collins <paul@briny.ondioline.org>,
bcm43xx-dev@lists.berlios.de, netdev@vger.kernel.org,
linville@tuxdriver.com
Subject: Re: bcm43xx: "transmit timed out" and apparent hang with "preemptible periodic work" patches
Date: Thu, 29 Jun 2006 17:31:50 +0200 [thread overview]
Message-ID: <200606291731.50598.mb@bu3sch.de> (raw)
In-Reply-To: <44A3F052.7030905@lwfinger.net>
On Thursday 29 June 2006 17:22, Larry Finger wrote:
> Michael Buesch wrote:
> > On Thursday 29 June 2006 10:24, Paul Collins wrote:
> >> Michael Buesch <mb@bu3sch.de> writes:
> >>
> >>> On Monday 26 June 2006 14:43, Michael Buesch wrote:
> >>>> Try to get more logs.
> >>>> I suggest to do a netconsole for logging.
> >>> Also note that current softmac trees have a patch missing.
> >>> It seems it got lost somewhere after my merge request.
> >>> I already contacted John in private for this, but no reply, yet.
> >>> The patch is attached. Maybe it fixes your issue.
> >> On a preempt kernel I can trigger the hang easily,
> >
> > How? I need to reproduce it to get a clue and fix it. :)
> > I have no idea where it might come from (I don't even know
> > what exactly happens).
> >
> > And please provide a _full_ dmesg log without comments inbetween
> > after triggering the hang (with a full Controller Restart cycle).
> >
>
> I am having what I think is a similar problem, although my system does not hang. I cannot send dmesg
> output as the buffer is quickly filled with the channel assertion messages you see below, but here
> is the relevant section of /var/log/messages.
>
> Jun 29 01:22:08 larrylap kernel: NETDEV WATCHDOG: wlan0: transmit timed out
> Jun 29 01:22:08 larrylap kernel: bcm43xx: Controller RESET (TX timeout) ...
> Jun 29 01:22:08 larrylap kernel: ACPI: PCI interrupt for device 0000:02:00.0 disabled
> Jun 29 01:22:08 larrylap kernel: PCI: Enabling device 0000:02:00.0 (0000 -> 0002)
> Jun 29 01:22:08 larrylap kernel: ACPI: PCI Interrupt 0000:02:00.0[A] -> Link [LNKA] -> GSI 11
> (level, low) -> IRQ 11
> Jun 29 01:22:08 larrylap kernel: bcm43xx: Chip ID 0x4306, rev 0x2
> Jun 29 01:22:08 larrylap kernel: bcm43xx: Number of cores: 6
> Jun 29 01:22:08 larrylap kernel: bcm43xx: Core 0: ID 0x800, rev 0x2, vendor 0x4243, enabled
> Jun 29 01:22:08 larrylap kernel: bcm43xx: Core 1: ID 0x812, rev 0x4, vendor 0x4243, enabled
> Jun 29 01:22:08 larrylap kernel: bcm43xx: Core 2: ID 0x80d, rev 0x1, vendor 0x4243, enabled
> Jun 29 01:22:08 larrylap kernel: bcm43xx: Core 3: ID 0x807, rev 0x1, vendor 0x4243, disabled
> Jun 29 01:22:08 larrylap kernel: bcm43xx: Core 4: ID 0x804, rev 0x7, vendor 0x4243, enabled
> Jun 29 01:22:08 larrylap kernel: bcm43xx: Core 5: ID 0x812, rev 0x4, vendor 0x4243, disabled
> Jun 29 01:22:08 larrylap kernel: bcm43xx: Ignoring additional 802.11 core.
> Jun 29 01:22:08 larrylap kernel: bcm43xx: PHY connected
> Jun 29 01:22:08 larrylap kernel: bcm43xx: Detected PHY: Version: 1, Type 2, Revision 1
> Jun 29 01:22:08 larrylap kernel: bcm43xx: Detected Radio: ID: 2205017f (Manuf: 17f Ver: 2050 Rev: 2)
> Jun 29 01:22:08 larrylap kernel: bcm43xx: Radio turned off
> Jun 29 01:22:08 larrylap kernel: bcm43xx: Radio turned off
> Jun 29 01:22:08 larrylap kernel: bcm43xx: Controller restarted
> Jun 29 01:23:08 larrylap kernel: bcm43xx: ASSERTION FAILED (channel >= 1 && channel <= 14) at:
> drivers/net/wireless/bcm43xx/bcm43xx_radio.c:79:channel2freq_bg()
WTF is that???
How is that possible to happen?
Are you sure you have an unmodified tree?
> Jun 29 01:24:08 larrylap kernel: bcm43xx: ASSERTION FAILED (channel >= 1 && channel <= 14) at:
> drivers/net/wireless/bcm43xx/bcm43xx_radio.c:79:channel2freq_bg()
> Jun 29 01:25:08 larrylap kernel: bcm43xx: ASSERTION FAILED (channel >= 1 && channel <= 14) at:
> drivers/net/wireless/bcm43xx/bcm43xx_radio.c:79:channel2freq_bg()
>
> These continue until the interface is brought down. My kernel is 2.6.17-g569df601-dirty from
> Linville's tree, is preemptible and all recent patches are installed.
>
> Larry
>
>
--
Greetings Michael.
next prev parent reply other threads:[~2006-06-29 15:33 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-26 2:28 bcm43xx: "transmit timed out" and apparent hang with "preemptible periodic work" patches Paul Collins
2006-06-26 12:43 ` 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 [this message]
[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=200606291731.50598.mb@bu3sch.de \
--to=mb@bu3sch.de \
--cc=Larry.Finger@lwfinger.net \
--cc=bcm43xx-dev@lists.berlios.de \
--cc=linville@tuxdriver.com \
--cc=netdev@vger.kernel.org \
--cc=paul@briny.ondioline.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).