From: Larry Finger <Larry.Finger-tQ5ms3gMjBLk1uMJSBkQmQ@public.gmane.org>
To: Michael Buesch <mb-fseUSCV1ubazQB+pC5nmwQ@public.gmane.org>
Cc: bcm43xx-dev-0fE9KPoRgkgATYTw5x5z8w@public.gmane.org,
netdev-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linville-2XuSBdqkA4R54TAoqtyWWQ@public.gmane.org
Subject: Re: bcm43xx: "transmit timed out" and apparent hang with "preemptible periodic work" patches
Date: Thu, 29 Jun 2006 11:16:05 -0500 [thread overview]
Message-ID: <44A3FCC5.1070305@lwfinger.net> (raw)
In-Reply-To: <200606291731.50598.mb-fseUSCV1ubazQB+pC5nmwQ@public.gmane.org>
Michael Buesch wrote:
> On Thursday 29 June 2006 17:22, Larry Finger wrote:
>> 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?
No, the tree is modified. It appears that something has messed up the bcm->ieee data. I am currently
in the process of re basing my copy of Linville's tree and will try with an unmodified version.
Larry
next prev parent reply other threads:[~2006-06-29 16:16 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
[not found] ` <200606291731.50598.mb-fseUSCV1ubazQB+pC5nmwQ@public.gmane.org>
2006-06-29 16:16 ` Larry Finger [this message]
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=44A3FCC5.1070305@lwfinger.net \
--to=larry.finger-tq5ms3gmjblk1umjsbkqmq@public.gmane.org \
--cc=bcm43xx-dev-0fE9KPoRgkgATYTw5x5z8w@public.gmane.org \
--cc=linville-2XuSBdqkA4R54TAoqtyWWQ@public.gmane.org \
--cc=mb-fseUSCV1ubazQB+pC5nmwQ@public.gmane.org \
--cc=netdev-u79uwXL29TY76Z2rM5mHXA@public.gmane.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.