From: Eric Valette <eric.valette@free.fr>
To: Felipe Balbi <me@felipebalbi.com>
Cc: Alan Stern <stern@rowland.harvard.edu>,
Randy Dunlap <rdunlap@xenotime.net>,
lud <linux-usb@vger.kernel.org>,
linux-kernel@vger.kernel.org
Subject: Re: 2.6.37-rc7: no more shutdown on DELL E6400
Date: Fri, 24 Dec 2010 08:47:34 +0100 [thread overview]
Message-ID: <4D145016.60906@free.fr> (raw)
In-Reply-To: <36f50535272fab60e974dc75e172bf29@secure211.sgcpanel.com>
On 24/12/2010 00:56, Felipe Balbi wrote:
> Hi,
> 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 ?
>
No. Mine has an Intel WiFi chipset. With DELL the same reference can be
used for multiple different hardware instantiation (I have a nvidia vido
chipset some seems now to have an intel one).
PS: For me the hang appeared with 2.6.37-rc7. I run linux on it for more
than a year changing stable kernel as soon as they appear and usually
trying future kernel around rc6 stage.
2.6.36.2 works perfectly. I did not change my config except maybe if the
make oldconfig was proposing something obvious (e.g new generic MII
support).
--eric
next prev parent reply other threads:[~2010-12-24 7:47 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-23 9:55 2.6.37-rc7: no more shutdown on DELL E6400 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
2010-12-24 7:47 ` Eric Valette [this message]
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=4D145016.60906@free.fr \
--to=eric.valette@free.fr \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=me@felipebalbi.com \
--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