From: Michael Buesch <mb@bu3sch.de>
To: Paul Collins <paul@briny.ondioline.org>
Cc: 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:49:53 +0200 [thread overview]
Message-ID: <200606291749.53858.mb@bu3sch.de> (raw)
In-Reply-To: <87mzbwvv07.fsf@briny.internal.ondioline.org>
On Thursday 29 June 2006 17:31, Paul Collins wrote:
> Michael Buesch <mb@bu3sch.de> writes:
>
> > 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 did it by running the commands I listed in my previous message.
> Here they are again, minus the pesky log messages.
>
> ip set link eth1 up
> ip set link eth1 down
> iwconfig eth1 essid wlan-ap enc off
> ip set link eth1 down
> ip set link eth1 up
> iwconfig eth1 essid wlan-ap enc off
> dhclient eth1
Uh, oh. You are doing an up-down-up cycle here...
I might get a clue now. This reminds me of some thought at yesterday
evening. I think that the up-down-up(down-up....) cycle is
broken and works only by accident mostly.
This bug might be hitting you here.
I will do a careful patch and send it out, later.
--
Greetings Michael.
prev parent reply other threads:[~2006-06-29 15:50 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
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 [this message]
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=200606291749.53858.mb@bu3sch.de \
--to=mb@bu3sch.de \
--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).