I have the following messages:
Will now halt
hub:4-0:1.0: hub_port_status_failed (err 110)
repeated twice.
I did not attend the shutdown last evening and it was blocked there this
morning. Retested and found same error.
Will open a regression bug (never have got this since 2.6.33).
-- eric
[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)
>
> repeated twice.
>
> I did not attend the shutdown last evening and it was blocked there this
> morning. Retested and found same error.
>
> Will open a regression bug (never have got this since 2.6.33).
>
> -- eric
---
~Randy
*** Remember to use Documentation/SubmitChecklist when testing your code ***
desserts: http://www.xenotime.net/linux/recipes/
On Thu, 23 Dec 2010 23:06:32 +0100 Eric Valette wrote:
> On 23/12/2010 23:02, Randy Dunlap wrote:
> > [add linux-usb list]
>
> Note that after making
> make O=buildir mrproper; make mproper and rebuilding
>
> I still have the hang after the "Will now halt", but no more the usb
> message.
OK, thanks for the info.
Can you update https://bugzilla.kernel.org/show_bug.cgi?id=25522
to include kernel log messages when you try to shutdown, please?
---
~Randy
*** Remember to use Documentation/SubmitChecklist when testing your code ***
desserts: http://www.xenotime.net/linux/recipes/
On 23/12/2010 23:02, Randy Dunlap wrote:
> [add linux-usb list]
Note that after making
make O=buildir mrproper; make mproper and rebuilding
I still have the hang after the "Will now halt", but no more the usb
message.
--eric
On 23/12/2010 23:10, Randy Dunlap wrote:
> OK, thanks for the info.
>
> Can you update https://bugzilla.kernel.org/show_bug.cgi?id=25522
>
> to include kernel log messages when you try to shutdown, please?
I'm afraid I cannot. It's my professional computer and I'm now on
vacation up to January. I will try to see if I have the same problem on
my home computers.
Besides, at this point (System will now halt) I'm not sure I can do
anything via keyboard or even gdb remote.
--eric
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)
> >
> > repeated twice.
> >
> > I did not attend the shutdown last evening and it was blocked there this
> > morning. Retested and found same error.
> >
> > Will open a regression bug (never have got this since 2.6.33).
That error message probably has no connection with whatever caused the
system to hang up.
Alan Stern
Hi,
On Thu, 23 Dec 2010 17:57:52 -0500 (EST), Alan Stern
<[email protected]> 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
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
On Fri, Dec 24, 2010 at 8:47 AM, Eric Valette <[email protected]> wrote:
> 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).
Just as a data point, my Dell E6400 still shuts down fine in both 2.6.37-rc7
and -rc7-git2. This one has integrated Intel video (i915) and I use the
out-of-tree broadcom-sta driver for the wireless interface. If needed, I can
post my .config in the bugzilla entry (but won't, unless asked - in order to
avoid possible bug noise).
--alessandro
?"There's always a siren singing you to shipwreck"
?? (Radiohead, "There There")
On Saturday 25 December 2010 00:42:58 Alessandro Suardi wrote:
> > 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).
> >
> Just as a data point, my Dell E6400 still shuts down fine in both
> 2.6.37-rc7 and -rc7-git2. This one has integrated Intel video (i915) and I
> use the out-of-tree broadcom-sta driver for the wireless interface. If
> needed, I can post my .config in the bugzilla entry (but won't, unless
> asked - in order to avoid possible bug noise).
That illustrates if needed the DELL reference multiple hardware problem. I put
2.6.37-rc7 (git1/git2) on my personnal laptop and I do not experience the
shutdown problem either.
I hope the problem is rare enough as I cannot supply more information before
getting back to work.
-- eric