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:07:54 +0200 [thread overview]
Message-ID: <200606291707.55172.mb@bu3sch.de> (raw)
In-Reply-To: <871wt8xtc9.fsf@briny.internal.ondioline.org>
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).
--
Greetings Michael.
next prev parent reply other threads:[~2006-06-29 15:08 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 [this message]
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=200606291707.55172.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 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.