From: Chr <chunkeey@web.de>
To: Larry Finger <Larry.Finger@lwfinger.net>
Cc: "David S. Miller" <davem@davemloft.net>,
wireless <linux-wireless@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: p54usb broken by commit b19fa1f
Date: Sat, 2 Aug 2008 14:57:46 +0200 [thread overview]
Message-ID: <200808021457.46438.chunkeey@web.de> (raw)
In-Reply-To: <4893CF3D.1070504@lwfinger.net>
On Saturday 02 August 2008 05:06:37 Larry Finger wrote:
> In testing 2.6.27-rc1, I found that p54usb caused my machine to freeze. A
> few times, I was able to use the KDE system status applet to see that the
> system was using essentially 100% of the CPU's. One other time, the system
> responded a little - enough for me to see tha wpa_supplicant was consuming
> 100% of the my AMD Turion 64 X2 running an x86_64 kernel. From bisection,
> the problem is due to
>
> commit b19fa1fa91845234961c64dbd564671aa7c0fd27
> Author: David S. Miller <davem@davemloft.net>
> Date: Tue Jul 8 23:14:24 2008 -0700
>
> net: Delete NETDEVICES_MULTIQUEUE kconfig option.
>
> Multiple TX queue support is a core networking feature.
>
> Signed-off-by: David S. Miller <davem@davemloft.net>
>
> Obviously, something in the driver cannot handle multiqueues, but I
> have not found anything, and I have not been able to get any logged events
> that show what is going wrong.
>
Hmm that's a bit odd as my p54usb-adapter seems to work usual with
2.6.27-rc1?!... That said: it doesn't work nearly as stable as the
minipci card that I have too. Is there anyone else who can confirm
that this problem is specific to the p54 driver & 2.6.27-rc1?
Regards,
Chr.
next prev parent reply other threads:[~2008-08-02 12:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-02 3:06 p54usb broken by commit b19fa1f Larry Finger
2008-08-02 12:57 ` Chr [this message]
2008-08-03 20:07 ` Larry Finger
2008-08-03 20:13 ` [RFC/RFT] p54usb: Regression due to " Larry Finger
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=200808021457.46438.chunkeey@web.de \
--to=chunkeey@web.de \
--cc=Larry.Finger@lwfinger.net \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@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 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.