Skip to contentSkip to conversation

2.6.37-rc7: no more shutdown on DELL E6400

DISCUSSION Eric Valette 5 participants 10 messages Dec 23, 2010 – Dec 25, 2010

lore
Share & tools
lore
#0 lore raw

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

#1 lore raw

[add linux-usb list]

Quoted 5 lines · 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)

Quoted 8 lines

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/

#3 lore raw
In reply to Eric Valette
Quoted 8 lines · On Thu, 23 Dec 2010 23:06:32 +0100 Eric Valette wrote:
Quoted 1 line · Randy Dunlap

[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/

#2 lore raw
In reply to Randy Dunlap
Quoted 1 line · Randy Dunlap

[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

#4 lore raw
In reply to Randy Dunlap
Quoted 5 lines · Randy Dunlap

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

#5 lore raw
In reply to Randy Dunlap
Quoted 16 lines · Randy Dunlap

[add linux-usb list]

Quoted 11 lines · 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

#6 lore raw

Hi,

Quoted 11 lines · Alan Stern
Quoted 9 lines · Randy Dunlap

[add linux-usb list]

Quoted 4 lines · 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 ?

Signature · 1 line
balbi
#7 lore raw
Quoted 7 lines · Felipe Balbi

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.

Quoted 6 lines

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

#8 lore raw
Quoted 20 lines · Eric Valette
Quoted 8 lines · Felipe Balbi

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.

Quoted 6 lines

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).

Quoted 7 lines

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")

#9 lore raw
Quoted 9 lines · On Saturday 25 December 2010 00:42:58 Alessandro Suardi wrote:
Quoted 4 lines

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