From: Eric Dumazet <eric.dumazet@gmail.com>
To: Lee <lee-in-berlin@web.de>
Cc: netdev@vger.kernel.org
Subject: Re: WARNING: at net/sched/sch_generic.c:261 dev_watchdog+0x249/0x260()
Date: Fri, 26 Mar 2010 15:34:10 +0100 [thread overview]
Message-ID: <1269614050.2839.77.camel@edumazet-laptop> (raw)
In-Reply-To: <4BACC1FD.3000609@web.de>
Le vendredi 26 mars 2010 à 15:17 +0100, Lee a écrit :
> Hi again,
>
> As this mail went unanswered, did I forget anything? Was it too verbose?
> Should I file a bug report on bugzilla.kernel.org instead?
>
> Regards,
> Lee
>
Well, many problems with rtl8169, unfortunatly.
You could try Francois patch :
http://www.spinics.net/lists/netdev/msg124131.html
> On 22/03/10 21:52, Lee wrote:
> > Hi everyone,
> >
> > I get a kernel oops on 2.6.32.10 when I use an rt73usb WLAN stick with
> > hostapd 0.6.10. It's bridged with one of my ethernet (r8169) interfaces.
> > When I have the stick plugged in without hostapd, the kernel oops
> > doesn't happen. It's not easily triggered, it usually happens within a
> > few hours of use with hostapd. I have about a dozen of those from while
> > tracking this bug down, if needed.
> >
> > Everything seems to work fine (before and after the oops), but at least
> > on one occasion I had a large delay on my ssh line when the oops happened.
> >
> > I have no idea what is causing this, but will happily test any patches
> > that are handed in my direction :)
> >
> > Kernel oops, .config and hostapd.conf are attached. Please tell me if
> > anything else is needed to hunt down this bug.
> >
> > Regards,
> > Lee
>
prev parent reply other threads:[~2010-03-26 14:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-22 20:52 WARNING: at net/sched/sch_generic.c:261 dev_watchdog+0x249/0x260() Lee
2010-03-26 14:17 ` Lee
2010-03-26 14:34 ` Eric Dumazet [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=1269614050.2839.77.camel@edumazet-laptop \
--to=eric.dumazet@gmail.com \
--cc=lee-in-berlin@web.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