From: Felipe Balbi <me@felipebalbi.com>
To: Alan Stern <stern@rowland.harvard.edu>
Cc: Randy Dunlap <rdunlap@xenotime.net>, <Eric.Valette@Free.fr>,
lud <linux-usb@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: 2.6.37-rc7: no more shutdown on DELL E6400
Date: Thu, 23 Dec 2010 17:56:58 -0600 [thread overview]
Message-ID: <36f50535272fab60e974dc75e172bf29@secure211.sgcpanel.com> (raw)
In-Reply-To: <Pine.LNX.4.44L0.1012231755180.11535-100000@netrider.rowland.org>
Hi,
On Thu, 23 Dec 2010 17:57:52 -0500 (EST), Alan Stern
<stern@rowland.harvard.edu> wrote:
> On Thu, 23 Dec 2010, Randy Dunlap wrote:
>
>> [add linux-usb list]
>>
>>
>> On Thu, 23 Dec 2010 10:55:38 +0100 Eric Valette wrote:
>>
>> > I have the following messages:
>> >
>> > Will now halt
>> > hub:4-0:1.0: hub_port_status_failed (err 110)
I've got an E6400 myself and the only time I could get
it to hang was when trying to use brcm80211 driver from
staging. The problem appears when I rmmod/modprobe the
driver after it looses connection to my wifi router.
Since the driver is still in staging and buggy as hell
I didn't bother notifying anyone. But it's true that
shutdown truly hangs.
Are you using brcm80211 driver too ?
--
balbi
next prev parent reply other threads:[~2010-12-24 0:47 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-23 9:55 Eric Valette
2010-12-23 22:02 ` Randy Dunlap
2010-12-23 22:06 ` Eric Valette
2010-12-23 22:10 ` Randy Dunlap
2010-12-23 22:19 ` Eric Valette
2010-12-23 22:57 ` Alan Stern
2010-12-23 23:56 ` Felipe Balbi [this message]
2010-12-24 7:47 ` Eric Valette
2010-12-24 23:42 ` Alessandro Suardi
2010-12-25 15:58 ` Eric Valette
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=36f50535272fab60e974dc75e172bf29@secure211.sgcpanel.com \
--to=me@felipebalbi.com \
--cc=Eric.Valette@Free.fr \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=rdunlap@xenotime.net \
--cc=stern@rowland.harvard.edu \
/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
all inboxes | Powered by JetHome®