Skip to contentSkip to conversation

2.6.23-rc6: known regressions

PATCH In review Michal Piotrowski 9 participants 12 messages Sep 12, 2007 – Sep 13, 2007

Subsystems (3)
lore
Share & tools
lore
#0 lore raw

PATCH 1/4 2.6.23-rc6: known regressions

Hi all,

Here is a list of some known regressions in 2.6.23-rc6.

Feel free to add new regressions/remove fixed etc.
http://kernelnewbies.org/known_regressions

List of Aces

Name Regressions fixed since 21-Jun-2007

Adrian Bunk                            10
Linus Torvalds                         6
Alan Stern                             5
Andi Kleen                             5
Hugh Dickins                           5
Trond Myklebust                        5
Andrew Morton                          4
Al Viro                                3
Alexey Starikovskiy                    3
Cornelia Huck                          3
David S. Miller                        3
Jens Axboe                             3
Stephen Hemminger                      3
Tejun Heo                              3

Unclassified

Subject : x86_64 vdso patch is broken somehow?
References : http://lkml.org/lkml/2007/8/29/136
Last known good : ?
Submitter : Chuck Ebbert <[email protected]>

                  commit 2aae950b21e4bc789d1fc6668faf67e8748300b7

Handled-By : ?
Status : unknown

Subject : cpu hotplug support broken in 2.6.23-rc3/highres timers break cpu hotplug in 2.6.23-rc5
References : http://lkml.org/lkml/2007/8/27/58

                  http://lkml.org/lkml/2007/9/3/65
Last known good : ?
Submitter       : Pavel Machek <[email protected]>
Caused-By       : ?
Handled-By      : ?
Status          : problem is being debugged

Subject : 2.6.23-rc3-git1 crash/stuck on VIA CN700 system
References : http://lkml.org/lkml/2007/8/20/174
Last known good : ?
Submitter : Stefan Becker <[email protected]>

                  commit 19d36ccdc34f5ed444f8a6af0cbfdb6790eb1177

Dave Jones <[email protected]>
Workaround : http://lkml.org/lkml/2007/9/5/221
Status : problem is being debugged

Subject : console is messed up after resume from s2ram or switching to console from X
References : http://lkml.org/lkml/2007/8/4/6
Last known good : ?
Submitter : Jeff Chua <[email protected]>

Antonino A. Daplas <[email protected]>
Workaround : "s2ram --force --acpi_sleep 1 --vbe_mode"
Status : problem is being debugged

Subject : konqueror suddenly vanishing, "konqueror: Fatal IO error: client killed"
References : http://lkml.org/lkml/2007/7/22/86
Last known good : ?
Submitter : Markus <[email protected]>

Caused-By       : ?
Handled-By      : Ingo Molnar <[email protected]>
Status          : problem is being debugged

Subject : uml on x86_64 compile error
References : http://lkml.org/lkml/2007/9/3/86
Last known good : ?
Submitter : Adrian Bunk <[email protected]>

                  commit d1254b12c93e1e586137a2ffef71fd33cf273f35

Handled-By : ?
Status : unknown

Regards,
Michal

--
LOG
http://www.stardust.webpages.pl/log/

#1 lore raw
Quoted 10 lines · Michal Piotrowski

Hi all,
...
Subject : uml on x86_64 compile error
References : http://lkml.org/lkml/2007/9/3/86
Last known good : ?
Submitter : Adrian Bunk <[email protected]>

                  commit d1254b12c93e1e586137a2ffef71fd33cf273f35

Handled-By : ?
Status : unknown

This one was fixed by commit 980abe215b861891c39aba0936817c46f372143b

Quoted 2 lines

Regards,
Michal

cu
Adrian

Signature · 4 lines
       "Is there not promise of rain?" Ling Tan asked suddenly out
        of the darkness. There had been need of rain for many days.
       "Only a promise," Lao Er said.
                                       Pearl S. Buck - Dragon Seed
#2 lore raw
In reply to Michal Piotrowski
Quoted 9 lines · Michal Piotrowski

Subject : x86_64 vdso patch is broken somehow?
References : http://lkml.org/lkml/2007/8/29/136
Last known good : ?
Submitter : Chuck Ebbert <[email protected]>

                  commit 2aae950b21e4bc789d1fc6668faf67e8748300b7

Handled-By : ?
Status : unknown

This should be fixed now. Just pushed out with commit 95b08679963c78ce0d675224a6efdb5169f2bf75 ("x86_64: Add missing mask operation to vdso").

Quoted 10 lines

Subject : 2.6.23-rc3-git1 crash/stuck on VIA CN700 system
References : http://lkml.org/lkml/2007/8/20/174
Last known good : ?
Submitter : Stefan Becker <[email protected]>

                  commit 19d36ccdc34f5ed444f8a6af0cbfdb6790eb1177

Dave Jones <[email protected]>
Workaround : http://lkml.org/lkml/2007/9/5/221
Status : problem is being debugged

This *seems* to be a VIA bug. Regardless, it should be fixed by commit a534b679180025aa324ebd63c05516e478551cfd ("x86_64: Remove CLFLUSH in text_poke()").

Quoted 9 lines

Subject : console is messed up after resume from s2ram or switching to console from X
References : http://lkml.org/lkml/2007/8/4/6
Last known good : ?
Submitter : Jeff Chua <[email protected]>

Antonino A. Daplas <[email protected]>
Workaround : "s2ram --force --acpi_sleep 1 --vbe_mode"
Status : problem is being debugged

This needs to be re-tested (was it the BIOS register overwriting, perhaps?).

Quoted 7 lines

Subject : konqueror suddenly vanishing, "konqueror: Fatal IO error: client killed"
References : http://lkml.org/lkml/2007/7/22/86
Last known good : ?
Submitter : Markus <[email protected]>

Caused-By       : ?
Handled-By      : Ingo Molnar <[email protected]>
Status          : problem is being debugged

This should probably be dropped. I don't think we have any new reports on it, and nobody else ever saw it.

Quoted 8 lines

Subject : uml on x86_64 compile error
References : http://lkml.org/lkml/2007/9/3/86
Last known good : ?
Submitter : Adrian Bunk <[email protected]>

                  commit d1254b12c93e1e586137a2ffef71fd33cf273f35

Handled-By : ?
Status : unknown

This should be fixed by commit 980abe215b861891c39aba0936817c46f372143b ("UML: Fix ELF_CORE_COPY_REGS build botch").

Linus

#3 lore raw
In reply to Michal Piotrowski
Quoted 8 lines · Michal Piotrowski

Subject : x86_64 vdso patch is broken somehow?
References : http://lkml.org/lkml/2007/8/29/136
Last known good : ?
Submitter : Chuck Ebbert <[email protected]>

                  commit 2aae950b21e4bc789d1fc6668faf67e8748300b7

Handled-By : ?
Status : unknown

Patch available:
http://lkml.org/lkml/2007/9/11/161

Quoted 8 lines

Subject : cpu hotplug support broken in 2.6.23-rc3/highres timers break cpu hotplug in 2.6.23-rc5
References : http://lkml.org/lkml/2007/8/27/58

                  http://lkml.org/lkml/2007/9/3/65
Last known good : ?
Submitter       : Pavel Machek <[email protected]>
Caused-By       : ?
Handled-By      : ?
Status          : problem is being debugged

This might be the same problem as the jinxed VAIO suspend/resume thingy, which is a regression as well.

Please assign the Handled-By to me.

Thanks,

tglx

#4 lore raw

Thomas Gleixner pisze:

Quoted 10 lines · Michal Piotrowski
Quoted 8 lines

Subject : x86_64 vdso patch is broken somehow?
References : http://lkml.org/lkml/2007/8/29/136
Last known good : ?
Submitter : Chuck Ebbert <[email protected]>

                  commit 2aae950b21e4bc789d1fc6668faf67e8748300b7

Handled-By : ?
Status : unknown

Quoted 2 lines

Patch available:
http://lkml.org/lkml/2007/9/11/161

It is already fixed ;)

Quoted 10 lines
Quoted 9 lines

Subject : cpu hotplug support broken in 2.6.23-rc3/highres timers break cpu hotplug in 2.6.23-rc5
References : http://lkml.org/lkml/2007/8/27/58

                  http://lkml.org/lkml/2007/9/3/65
Last known good : ?
Submitter       : Pavel Machek <[email protected]>
Caused-By       : ?
Handled-By      : ?
Status          : problem is being debugged
Quoted 4 lines

This might be the same problem as the jinxed VAIO suspend/resume thingy, which is a regression as well.

Please assign the Handled-By to me.

Ok.

Quoted 5 lines

Thanks,

tglx

Regards,
Michal

Signature · 2 lines
LOG
http://www.stardust.webpages.pl/log/
#5 lore raw
In reply to Michal Piotrowski
Quoted 3 lines · Michal Piotrowski

Hi all,

Here is a list of some known regressions in 2.6.23-rc6.

...

Missing from the list:

USB "autosuspend" feature (new in 2.6.23) breaks *lots* of devices. Many have since been blacklisted in one-at-a-time discovery patches, but that's really just the tip of the iceberg.

This "feature" breaks a TON of user-visible things, mostly USB storage devices (USB drives/pens, digicams, etc..).

The functionality is broken for just too much stuff,
and needs to either be reverted or defaulted to "off" rather than "on".

Cheers

#6 lore raw
Quoted 11 lines · Mark Lord
Quoted 2 lines · Michal Piotrowski

Hi all,
Here is a list of some known regressions in 2.6.23-rc6.

...

Missing from the list:

USB "autosuspend" feature (new in 2.6.23) breaks *lots* of devices. Many have since been blacklisted in one-at-a-time discovery patches, but that's really just the tip of the iceberg.

Quoted 5 lines

This "feature" breaks a TON of user-visible things, mostly USB storage devices (USB drives/pens, digicams, etc..).

The functionality is broken for just too much stuff,
and needs to either be reverted or defaulted to "off" rather than "on".

Ok, after conferring with Oliver this morning, I think the best solution here is to both revert the usb-storage suspend patch as it has some basic problems that can cause data loss, _and_ add the change to the kernel that by default disables autosuspend on all USB devices except hubs.

If anyone has any objections to this, please let me know.

thanks,

greg k-h

-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
User-mode-linux-devel mailing list [email protected]
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel

#7 lore raw
Quoted 15 lines · Greg KH
Quoted 14 lines · Mark Lord
Quoted 2 lines · Michal Piotrowski

Hi all,
Here is a list of some known regressions in 2.6.23-rc6.

...

Missing from the list:

USB "autosuspend" feature (new in 2.6.23) breaks *lots* of devices. Many have since been blacklisted in one-at-a-time discovery patches, but that's really just the tip of the iceberg.

This "feature" breaks a TON of user-visible things, mostly USB storage devices (USB drives/pens, digicams, etc..).

Quoted 8 lines
Quoted 2 lines

The functionality is broken for just too much stuff,
and needs to either be reverted or defaulted to "off" rather than "on".

Ok, after conferring with Oliver this morning, I think the best solution here is to both revert the usb-storage suspend patch as it has some basic problems that can cause data loss, _and_ add the change to the kernel that by default disables autosuspend on all USB devices except hubs.

Sounds like a sane approach.

Hopefully the kinks can be worked out in time for a reattempt in 2.6.24. I understand how important this stuff is for battery powered devices, but it just doesn't appear to be ready yet.

Cheers

#8 lore raw
In reply to Greg KH
Quoted 5 lines · Greg KH

Ok, after conferring with Oliver this morning, I think the best solution here is to both revert the usb-storage suspend patch as it has some basic problems that can cause data loss, _and_ add the change to the kernel that by default disables autosuspend on all USB devices except hubs.

Are you referring to the disk spin-down issue? As far as I know, that's the only troublesome aspect of usb-storage autosuspend (apart from the fact that so many devices don't seem to support it very well, if at all).

Solving the spin-down problem will require coordination with the SCSI developers. Basically, the SCSI core has to notify the HBA driver whenever the bus has been idle sufficiently long and all its devices are ready to be suspended. In particular, all disk heads should be parked and drives spun down, if they need to be.

Alan Stern

#9 lore raw
Quoted 13 lines · Alan Stern
Quoted 5 lines · Greg KH

Ok, after conferring with Oliver this morning, I think the best solution here is to both revert the usb-storage suspend patch as it has some basic problems that can cause data loss, _and_ add the change to the kernel that by default disables autosuspend on all USB devices except hubs.

Are you referring to the disk spin-down issue? As far as I know, that's the only troublesome aspect of usb-storage autosuspend (apart from the fact that so many devices don't seem to support it very well, if at all).

Quoted 5 lines

Solving the spin-down problem will require coordination with the SCSI developers. Basically, the SCSI core has to notify the HBA driver whenever the bus has been idle sufficiently long and all its devices are ready to be suspended. In particular, all disk heads should be parked and drives spun down, if they need to be.

I am not sure. I will defer to Oliver for the knowledge of the details, it was early in the morning and I can't remember them all exactly :)

(although it might be a few days for him to respond, he's here at a conference without a laptop, so his lag time might be a bit longer than normal...)

thanks,

greg k-h

-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
[email protected]
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-devel

#10 lore raw
Quoted 20 lines · Greg KH
Quoted 13 lines · Alan Stern
Quoted 5 lines · Greg KH

Ok, after conferring with Oliver this morning, I think the best solution here is to both revert the usb-storage suspend patch as it has some basic problems that can cause data loss, _and_ add the change to the kernel that by default disables autosuspend on all USB devices except hubs.

Are you referring to the disk spin-down issue? As far as I know, that's the only troublesome aspect of usb-storage autosuspend (apart from the fact that so many devices don't seem to support it very well, if at all).

Quoted 5 lines

Solving the spin-down problem will require coordination with the SCSI developers. Basically, the SCSI core has to notify the HBA driver whenever the bus has been idle sufficiently long and all its devices are ready to be suspended. In particular, all disk heads should be parked and drives spun down, if they need to be.

Quoted 6 lines

I am not sure. I will defer to Oliver for the knowledge of the details, it was early in the morning and I can't remember them all exactly :)

(although it might be a few days for him to respond, he's here at a conference without a laptop, so his lag time might be a bit longer than normal...)

I'll wait, certainly ... enjoy the Czech backwoods.

One thing I would say though is that if there's special action we have to take after autosuspend, it should probably be built into the framework Kristen is developing for ACHI link power management (your USB autosuspend is effectively a simple type of link power management as well).

James

-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
[email protected]
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-devel

#11 lore raw
In reply to Michal Piotrowski
Quoted 11 lines · Michal Piotrowski

Subject : console is messed up after resume from s2ram or switching to console from X
References : http://lkml.org/lkml/2007/8/4/6
Last known good : ?
Submitter : Jeff Chua <[email protected]>

Antonino A. Daplas <[email protected]>
Workaround : "s2ram --force --acpi_sleep 1 --vbe_mode"
Status : problem is being debugged

Finally diagnosed. A patch should be coming shortly.

-hpa