Skip to contentSkip to conversation

2.6.30-rc6: Reported regressions 2.6.28 -> 2.6.29

PATCH New Rafael J. Wysocki 11 participants 55 messages May 16, 2009 – May 20, 2009 1 message not in the archive

Subsystems (5)
Networking Network drivers SCSI ACPI +1 more subsystems
lore
Share & tools
lore
#0 lore raw

This message contains a list of some regressions introduced between 2.6.28 and 2.6.29, for which there are no fixes in the mainline I know of. If any of them have been fixed already, please let me know.

If you know of any other unresolved regressions introduced between 2.6.28 and 2.6.29, please let me know either and I'll add them to the list. Also, please let me know if any of the entries below are invalid.

Each entry from the list will be sent additionally in an automatic reply to this message with CCs to the people involved in reporting and handling the issue.

Listed regressions statistics:

Date Total Pending Unresolved
----------------------------------------

  2009-05-17      162       27          25
  2009-04-26      160       29          27
  2009-04-06      142       37          31
  2009-03-21      128       29          26
  2009-03-14      124       36          32
  2009-03-03      108       33          28
  2009-02-24       95       32          24
  2009-02-14       85       33          27
  2009-02-08       82       45          36
  2009-02-04       66       51          39
  2009-01-20       38       35          27
  2009-01-11       13       13          10

Unresolved regressions
----------------------

Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=13271
Subject : ath9k stop working since 2.6.29
Submitter : lyman <[email protected]>
Date : 2009-05-10 01:58 (7 days old)

Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=13269
Subject : WARNING: at kernel/hrtimer.c:625 hres_timers_resume+0x3c/0x48() when resuming
Submitter : cedric <[email protected]>
Date : 2009-05-08 08:48 (9 days old)

Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=13232
Subject : ext3/4 with synchronous writes gets wedged by Postfix
Submitter : David Watson <[email protected]>
Date : 2009-05-03 19:46 (14 days old)

Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=13225
Subject : [2.6.29 regression] Software suspend no longer works
Submitter : Artem S. Tashkinov <t.artem-VInPYn6yXxRWk0Htik3J/[email protected]>
Date : 2009-05-02 21:41 (15 days old)

Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=13183
Subject : forcedeth: no link during initialization
Submitter : Harald Dunkel <[email protected]>
Date : 2009-04-23 13:02 (24 days old)
References : http://marc.info/?l=linux-kernel&m=124049180309233&w=4

Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=13178
Subject : Booting very slow
Submitter : Martin Knoblauch <[email protected]>
Date : 2009-04-24 12:45 (23 days old)
References : http://marc.info/?l=linux-kernel&m=124057716231773&w=4

Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=13175
Subject : sata_nv incompatible with async scsi scan
Submitter : Benny Halevy <[email protected]>
Date : 2009-04-21 7:03 (26 days old)
References : http://marc.info/?l=linux-kernel&m=124029746431777&w=4

Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=13172
Subject : Spontaneous reboots since 2.6.29-rc*
Submitter : Maciej Rutecki <[email protected]>
Date : 2009-04-17 17:03 (30 days old)
References : http://marc.info/?l=linux-kernel&m=123998788921733&w=4

Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=13144
Subject : resume from suspend fails using video card i915
Submitter : C Sights <[email protected]>
Date : 2009-04-21 17:03 (26 days old)

Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=13100
Subject : can't anymore even do a s2ram-s2disk-s2ram cycle on acer aspire 5720G
Submitter : Maxim Levitsky <[email protected]>
Date : 2009-04-06 23:52 (41 days old)
First-Bad-Commit: http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=a0d4922da2e4ccb0973095d8d29f36f6b1b5f703
References : http://marc.info/?l=linux-kernel&m=123906202829074&w=4

Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=13074
Subject : gspca_stv06xx doesn't work with Logitech QuickCam Express (046d:0840)
Submitter : Paulo Matias <matias-fd97jBR+K/[email protected]>
Date : 2009-04-12 14:10 (35 days old)

Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=13072
Subject : forcedeth seems to switch off eth on shutdown
Submitter : Daniel Bierstedt <[email protected]>
Date : 2009-04-12 07:00 (35 days old)

Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=13025
Subject : After upgrading to kernel 2.6.29, pulseaudio stopped with some strange error
Submitter : Yaroslav Isakov <[email protected]>
Date : 2009-04-06 19:47 (41 days old)

Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=13024
Subject : nozomi: pppd fails on kernel 2.6.29
Submitter : Mark Karpeles <mark-pwcEARUeV57PDbFq/[email protected]>
Date : 2009-04-06 19:12 (41 days old)

Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=13001
Subject : PCI-DMA: Out of IOMMU space
Submitter : <[email protected]>
Date : 2009-04-03 09:30 (44 days old)
References : http://lkml.org/lkml/2009/4/28/133

Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=12980
Subject : lockup in X.org
Submitter : Marcus Better <[email protected]>
Date : 2009-03-31 08:58 (47 days old)

Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=12971
Subject : "tg3 transmit timed out" when transmitting at high bitrate
Submitter : Nikolay <[email protected]>
Date : 2009-03-29 18:02 (49 days old)

Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=12947
Subject : r128: system hangs when X is started with DRI enabled
Submitter : Jos van der Ende <seraph-qWit8jRvyhVmR6Xm/[email protected]>
Date : 2009-03-26 16:14 (52 days old)

Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=12909
Subject : boot/kernel init duration regression from 2.6.28
Submitter : CaT <[email protected]>
Date : 2009-03-16 10:25 (62 days old)
References : http://marc.info/?l=linux-kernel&m=123720083515950&w=4

Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=12899
Subject : Crash in i915.ko: i915_driver_irq_handler
Submitter : Helge Bahmann <[email protected]>
Date : 2009-03-20 07:13 (58 days old)

Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=12861
Subject : Xorg fails to start "Failed to allocate space for kernel memory manager"
Submitter : Emil Karlson <[email protected]>
Date : 2009-03-12 12:06 (66 days old)
First-Bad-Commit: http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=ab657db12d7020629f26f30d287558a8d0e32b41

Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=12705
Subject : X200: Brightness broken since 2.6.29-rc4-58-g4c098bc
Submitter : Nico Schottelius <[email protected]>
Date : 2009-02-13 9:33 (93 days old)
First-Bad-Commit: http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=e806b4957412bf472d826bd8cc571da041248799
References : http://marc.info/?l=linux-kernel&m=123451768406825&w=4

		  http://marc.info/?l=linux-kernel&m=123479975503827&w=2

Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=12681
Subject : s2ram: fails to wake up on Acer Extensa 4220 (SMP disabled)
Submitter : Orivej Desh <[email protected]>
Date : 2009-02-09 13:01 (97 days old)
First-Bad-Commit: http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=1cfe62c8010ac56e1bd3827e30386a87cc2f3594

Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=12499
Subject : Problem with using bluetooth adaper connected to usb port
Submitter : Maciej Rutecki <[email protected]>
Date : 2009-01-13 18:34 (124 days old)
References : http://marc.info/?l=linux-kernel&m=123187185426236&w=4

Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=12490
Subject : ath5k related kernel panic in 2.6.29-rc1
Submitter : Sergey S. Kostyliov <[email protected]>
Date : 2009-01-12 7:38 (125 days old)
References : http://marc.info/?l=linux-kernel&m=123174591509586&w=4

		  http://lkml.org/lkml/2009/4/6/527

Regressions with patches
------------------------

Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=13186
Subject : cpufreq timer teardown problem
Submitter : Mathieu Desnoyers <mathieu.desnoyers-scC8bbJcJLCw5LPnMra/[email protected]>
Date : 2009-04-23 14:00 (24 days old)
References : http://marc.info/?l=linux-kernel&m=124049523515036&w=4

Patch : http://patchwork.kernel.org/patch/19754/

		  http://patchwork.kernel.org/patch/19753/

Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=12765
Subject : i915 VT switch with AIGLX causes X lock up
Submitter : Sitsofe Wheeler <sitsofe-/[email protected]>
Date : 2009-02-21 15:38 (85 days old)
First-Bad-Commit: http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=14d200c5e5bd19219d930bbb9a5a22758c8f5bec
References : http://marc.info/?l=linux-kernel&m=123523074304955&w=4

		  http://lkml.org/lkml/2009/4/27/317

Patch : http://patchwork.kernel.org/patch/20197/

For details, please visit the bug entries and follow the links given in references.

As you can see, there is a Bugzilla entry for each of the listed regressions. There also is a Bugzilla entry used for tracking the regressions introduced between 2.6.28 and 2.6.29, unresolved as well as resolved, at:

http://bugzilla.kernel.org/show_bug.cgi?id=12398

Please let me know if there are any Bugzilla entries that should be added to the list in there.

Thanks,
Rafael

--
To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html

#1 lore raw

[Bug #12490] ath5k related kernel panic in 2.6.29-rc1

This message has been generated automatically as a part of a report of regressions introduced between 2.6.28 and 2.6.29.

The following bug entry is on the current list of known regressions introduced between 2.6.28 and 2.6.29. Please verify if it still should be listed and let me know (either way).

Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=12490
Subject : ath5k related kernel panic in 2.6.29-rc1
Submitter : Sergey S. Kostyliov <[email protected]>
Date : 2009-01-12 7:38 (125 days old)
References : http://marc.info/?l=linux-kernel&m=123174591509586&w=4

		  http://lkml.org/lkml/2009/4/6/527
#2 lore raw

[Bug #12499] Problem with using bluetooth adaper connected to usb port

In reply to Rafael J. Wysocki

This message has been generated automatically as a part of a report of regressions introduced between 2.6.28 and 2.6.29.

The following bug entry is on the current list of known regressions introduced between 2.6.28 and 2.6.29. Please verify if it still should be listed and let me know (either way).

Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=12499
Subject : Problem with using bluetooth adaper connected to usb port
Submitter : Maciej Rutecki <[email protected]>
Date : 2009-01-13 18:34 (124 days old)
References : http://marc.info/?l=linux-kernel&m=123187185426236&w=4

#3 lore raw

Re: [Bug #12499] Problem with using bluetooth adaper connected to usb port

2009/5/16 Rafael J. Wysocki <[email protected]>:

Quoted 8 lines

This message has been generated automatically as a part of a report of regressions introduced between 2.6.28 and 2.6.29.

The following bug entry is on the current list of known regressions introduced between 2.6.28 and 2.6.29.  Please verify if it still should be listed and let me know (either way).

Quoted 7 lines

Bug-Entry       : http://bugzilla.kernel.org/show_bug.cgi?id=12499
Subject         : Problem with using bluetooth adaper connected to usb port Submitter       : Maciej Rutecki <[email protected]>
Date            : 2009-01-13 18:34 (124 days old)
References      : http://marc.info/?l=linux-kernel&m=123187185426236&w=4
Handled-By      : Marcel Holtmann <[email protected]>

2.6.30-rc6 works fine. Please, remove it.

Thanks

Signature · 2 lines
Maciej Rutecki
http://www.maciek.unixy.pl
#4 lore raw

Re: [Bug #12499] Problem with using bluetooth adaper connected to usb port

Quoted 17 lines · Maciej Rutecki

2009/5/16 Rafael J. Wysocki <[email protected]>:

Quoted 8 lines

This message has been generated automatically as a part of a report of regressions introduced between 2.6.28 and 2.6.29.

The following bug entry is on the current list of known regressions introduced between 2.6.28 and 2.6.29. Please verify if it still should be listed and let me know (either way).

Quoted 7 lines

Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=12499
Subject : Problem with using bluetooth adaper connected to usb port
Submitter : Maciej Rutecki <[email protected]>
Date : 2009-01-13 18:34 (124 days old)
References : http://marc.info/?l=linux-kernel&m=123187185426236&w=4

Quoted 1 line

2.6.30-rc6 works fine. Please, remove it.

Removed.

Thanks,
Rafael

#5 lore raw

[Bug #12705] X200: Brightness broken since 2.6.29-rc4-58-g4c098bc

In reply to Rafael J. Wysocki

This message has been generated automatically as a part of a report of regressions introduced between 2.6.28 and 2.6.29.

The following bug entry is on the current list of known regressions introduced between 2.6.28 and 2.6.29. Please verify if it still should be listed and let me know (either way).

Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=12705
Subject : X200: Brightness broken since 2.6.29-rc4-58-g4c098bc
Submitter : Nico Schottelius <[email protected]>
Date : 2009-02-13 9:33 (93 days old)
First-Bad-Commit: http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=e806b4957412bf472d826bd8cc571da041248799
References : http://marc.info/?l=linux-kernel&m=123451768406825&w=4

		  http://marc.info/?l=linux-kernel&m=123479975503827&w=2
#6 lore raw

[Bug #12765] i915 VT switch with AIGLX causes X lock up

In reply to Rafael J. Wysocki

This message has been generated automatically as a part of a report of regressions introduced between 2.6.28 and 2.6.29.

The following bug entry is on the current list of known regressions introduced between 2.6.28 and 2.6.29. Please verify if it still should be listed and let me know (either way).

Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=12765
Subject : i915 VT switch with AIGLX causes X lock up
Submitter : Sitsofe Wheeler <sitsofe-/[email protected]>
Date : 2009-02-21 15:38 (85 days old)
First-Bad-Commit: http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=14d200c5e5bd19219d930bbb9a5a22758c8f5bec
References : http://marc.info/?l=linux-kernel&m=123523074304955&w=4

		  http://lkml.org/lkml/2009/4/27/317

Patch : http://patchwork.kernel.org/patch/20197/

#7 lore raw

Re: [Bug #12765] i915 VT switch with AIGLX causes X lock up

Quoted 11 lines · Rafael J. Wysocki

The following bug entry is on the current list of known regressions introduced between 2.6.28 and 2.6.29. Please verify if it still should be listed and let me know (either way).

Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=12765
Subject : i915 VT switch with AIGLX causes X lock up
Submitter : Sitsofe Wheeler <sitsofe-/[email protected]>
Date : 2009-02-21 15:38 (85 days old)
First-Bad-Commit: http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=14d200c5e5bd19219d930bbb9a5a22758c8f5bec
References : http://marc.info/?l=linux-kernel&m=123523074304955&w=4

Quoted 3 lines
		  http://lkml.org/lkml/2009/4/27/317

Patch : http://patchwork.kernel.org/patch/20197/

Yes, this problem is still here in 2.6.30-rc6-00026-g0f6f49a .

Signature · 1 line
Sitsofe | http://sucs.org/~sits/
#8 lore raw

Re: [Bug #12765] i915 VT switch with AIGLX causes X lock up

Quoted 16 lines · Sitsofe Wheeler
Quoted 11 lines · Rafael J. Wysocki

The following bug entry is on the current list of known regressions introduced between 2.6.28 and 2.6.29. Please verify if it still should be listed and let me know (either way).

Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=12765
Subject : i915 VT switch with AIGLX causes X lock up
Submitter : Sitsofe Wheeler <sitsofe-/[email protected]>
Date : 2009-02-21 15:38 (85 days old)
First-Bad-Commit: http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=14d200c5e5bd19219d930bbb9a5a22758c8f5bec
References : http://marc.info/?l=linux-kernel&m=123523074304955&w=4

Quoted 3 lines
		  http://lkml.org/lkml/2009/4/27/317

Patch : http://patchwork.kernel.org/patch/20197/

Quoted 1 line

Yes, this problem is still here in 2.6.30-rc6-00026-g0f6f49a .

Thanks for the update.

Rafael

#9 lore raw

[Bug #12681] s2ram: fails to wake up on Acer Extensa 4220 (SMP disabled)

In reply to Rafael J. Wysocki

This message has been generated automatically as a part of a report of regressions introduced between 2.6.28 and 2.6.29.

The following bug entry is on the current list of known regressions introduced between 2.6.28 and 2.6.29. Please verify if it still should be listed and let me know (either way).

Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=12681
Subject : s2ram: fails to wake up on Acer Extensa 4220 (SMP disabled)
Submitter : Orivej Desh <[email protected]>
Date : 2009-02-09 13:01 (97 days old)
First-Bad-Commit: http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=1cfe62c8010ac56e1bd3827e30386a87cc2f3594

#10 lore raw

[Bug #12861] Xorg fails to start "Failed to allocate space for kernel memory manager"

In reply to Rafael J. Wysocki

This message has been generated automatically as a part of a report of regressions introduced between 2.6.28 and 2.6.29.

The following bug entry is on the current list of known regressions introduced between 2.6.28 and 2.6.29. Please verify if it still should be listed and let me know (either way).

Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=12861
Subject : Xorg fails to start "Failed to allocate space for kernel memory manager"
Submitter : Emil Karlson <[email protected]>
Date : 2009-03-12 12:06 (66 days old)
First-Bad-Commit: http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=ab657db12d7020629f26f30d287558a8d0e32b41

#11 lore raw

[Bug #12971] "tg3 transmit timed out" when transmitting at high bitrate

In reply to Rafael J. Wysocki

This message has been generated automatically as a part of a report of regressions introduced between 2.6.28 and 2.6.29.

The following bug entry is on the current list of known regressions introduced between 2.6.28 and 2.6.29. Please verify if it still should be listed and let me know (either way).

Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=12971
Subject : "tg3 transmit timed out" when transmitting at high bitrate
Submitter : Nikolay <[email protected]>
Date : 2009-03-29 18:02 (49 days old)

#12 lore raw

[Bug #12899] Crash in i915.ko: i915_driver_irq_handler

In reply to Rafael J. Wysocki

This message has been generated automatically as a part of a report of regressions introduced between 2.6.28 and 2.6.29.

The following bug entry is on the current list of known regressions introduced between 2.6.28 and 2.6.29. Please verify if it still should be listed and let me know (either way).

Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=12899
Subject : Crash in i915.ko: i915_driver_irq_handler
Submitter : Helge Bahmann <[email protected]>
Date : 2009-03-20 07:13 (58 days old)

#13 lore raw

[Bug #12947] r128: system hangs when X is started with DRI enabled

In reply to Rafael J. Wysocki

This message has been generated automatically as a part of a report of regressions introduced between 2.6.28 and 2.6.29.

The following bug entry is on the current list of known regressions introduced between 2.6.28 and 2.6.29. Please verify if it still should be listed and let me know (either way).

Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=12947
Subject : r128: system hangs when X is started with DRI enabled
Submitter : Jos van der Ende <seraph-qWit8jRvyhVmR6Xm/[email protected]>
Date : 2009-03-26 16:14 (52 days old)

#14 lore raw

Re: [Bug #12947] r128: system hangs when X is started with DRI enabled

Quoted 6 lines · On Sat, 16 May 2009 22:05:58 +0200 (CEST) "Rafael J. Wysocki"…

This message has been generated automatically as a part of a report of regressions introduced between 2.6.28 and 2.6.29.

The following bug entry is on the current list of known regressions introduced between 2.6.28 and 2.6.29. Please verify if it still should be listed and let me know (either way).

The bug is still present in 2.6.29.3, but we've found the likely cause and a potential fix. As soon as I have access to the system again, I will test this patch. Unfortunately I won't be anywhere near the system this week. I'll get back to it on Monday 25th.

Signature · 1 line
Jos van der Ende <seraph-qWit8jRvyhVmR6Xm/[email protected]>
#15 lore raw

[Bug #12909] boot/kernel init duration regression from 2.6.28

In reply to Rafael J. Wysocki

This message has been generated automatically as a part of a report of regressions introduced between 2.6.28 and 2.6.29.

The following bug entry is on the current list of known regressions introduced between 2.6.28 and 2.6.29. Please verify if it still should be listed and let me know (either way).

Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=12909
Subject : boot/kernel init duration regression from 2.6.28
Submitter : CaT <[email protected]>
Date : 2009-03-16 10:25 (62 days old)
References : http://marc.info/?l=linux-kernel&m=123720083515950&w=4

#16 lore raw

[Bug #12980] lockup in X.org

In reply to Rafael J. Wysocki

This message has been generated automatically as a part of a report of regressions introduced between 2.6.28 and 2.6.29.

The following bug entry is on the current list of known regressions introduced between 2.6.28 and 2.6.29. Please verify if it still should be listed and let me know (either way).

Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=12980
Subject : lockup in X.org
Submitter : Marcus Better <[email protected]>
Date : 2009-03-31 08:58 (47 days old)

#17 lore raw

Re: [Bug #12980] lockup in X.org

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Quoted 4 lines · Rafael J. Wysocki

Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=12980
Subject : lockup in X.org
Submitter : Marcus Better <[email protected]>
Date : 2009-03-31 08:58 (47 days old)

Bug went away for unknown reason, hasn't occurred in more than a month.

Cheers,

Marcus

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEARECAAYFAkoQL78ACgkQXjXn6TzcAQlQNQCcDH+GrasHNGT7UrrsvfNOH/iy hlkAoMo9JJ+33MJLPrTF49HgfgcIdp/r
=ovke
-----END PGP SIGNATURE-----

#19 lore raw

[Bug #13001] PCI-DMA: Out of IOMMU space

In reply to Rafael J. Wysocki

This message has been generated automatically as a part of a report of regressions introduced between 2.6.28 and 2.6.29.

The following bug entry is on the current list of known regressions introduced between 2.6.28 and 2.6.29. Please verify if it still should be listed and let me know (either way).

Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=13001
Subject : PCI-DMA: Out of IOMMU space
Submitter : <[email protected]>
Date : 2009-04-03 09:30 (44 days old)
References : http://lkml.org/lkml/2009/4/28/133

#20 lore raw

[Bug #13024] nozomi: pppd fails on kernel 2.6.29

In reply to Rafael J. Wysocki

This message has been generated automatically as a part of a report of regressions introduced between 2.6.28 and 2.6.29.

The following bug entry is on the current list of known regressions introduced between 2.6.28 and 2.6.29. Please verify if it still should be listed and let me know (either way).

Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=13024
Subject : nozomi: pppd fails on kernel 2.6.29
Submitter : Mark Karpeles <mark-pwcEARUeV57PDbFq/[email protected]>
Date : 2009-04-06 19:12 (41 days old)

#21 lore raw

[Bug #13072] forcedeth seems to switch off eth on shutdown

In reply to Rafael J. Wysocki

This message has been generated automatically as a part of a report of regressions introduced between 2.6.28 and 2.6.29.

The following bug entry is on the current list of known regressions introduced between 2.6.28 and 2.6.29. Please verify if it still should be listed and let me know (either way).

Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=13072
Subject : forcedeth seems to switch off eth on shutdown
Submitter : Daniel Bierstedt <[email protected]>
Date : 2009-04-12 07:00 (35 days old)

A message that is not in the archive (sent off-list or not yet received): [email protected]

#23 lore raw

Re: [Bug #13072] forcedeth seems to switch off eth on shutdown

Quoted 10 lines · Daniel Bierstedt

Hello,

as I wrote on 26'th of April:

yes, this bug entry should be listed. This bug prevents people from using live-cd's or testing the 2.6.29 (if they know about this bug...).

Meanwhile I did some tests with knoppix 6 (2.6.28.4) and the systemrescue-cd (2.6.27.somewhat). Both could deal with eth0, but the physical device remained dead...

Thanks for the update.

Rafael

#24 lore raw

[Bug #13025] After upgrading to kernel 2.6.29, pulseaudio stopped with some strange error

In reply to Rafael J. Wysocki

This message has been generated automatically as a part of a report of regressions introduced between 2.6.28 and 2.6.29.

The following bug entry is on the current list of known regressions introduced between 2.6.28 and 2.6.29. Please verify if it still should be listed and let me know (either way).

Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=13025
Subject : After upgrading to kernel 2.6.29, pulseaudio stopped with some strange error
Submitter : Yaroslav Isakov <[email protected]>
Date : 2009-04-06 19:47 (41 days old)

#25 lore raw

[Bug #13074] gspca_stv06xx doesn't work with Logitech QuickCam Express (046d:0840)

In reply to Rafael J. Wysocki

This message has been generated automatically as a part of a report of regressions introduced between 2.6.28 and 2.6.29.

The following bug entry is on the current list of known regressions introduced between 2.6.28 and 2.6.29. Please verify if it still should be listed and let me know (either way).

Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=13074
Subject : gspca_stv06xx doesn't work with Logitech QuickCam Express (046d:0840)
Submitter : Paulo Matias <matias-fd97jBR+K/[email protected]>
Date : 2009-04-12 14:10 (35 days old)

#26 lore raw

[Bug #13100] can't anymore even do a s2ram-s2disk-s2ram cycle on acer aspire 5720G

In reply to Rafael J. Wysocki

This message has been generated automatically as a part of a report of regressions introduced between 2.6.28 and 2.6.29.

The following bug entry is on the current list of known regressions introduced between 2.6.28 and 2.6.29. Please verify if it still should be listed and let me know (either way).

Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=13100
Subject : can't anymore even do a s2ram-s2disk-s2ram cycle on acer aspire 5720G
Submitter : Maxim Levitsky <[email protected]>
Date : 2009-04-06 23:52 (41 days old)
First-Bad-Commit: http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=a0d4922da2e4ccb0973095d8d29f36f6b1b5f703
References : http://marc.info/?l=linux-kernel&m=123906202829074&w=4

#27 lore raw

[Bug #13172] Spontaneous reboots since 2.6.29-rc*

In reply to Rafael J. Wysocki

This message has been generated automatically as a part of a report of regressions introduced between 2.6.28 and 2.6.29.

The following bug entry is on the current list of known regressions introduced between 2.6.28 and 2.6.29. Please verify if it still should be listed and let me know (either way).

Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=13172
Subject : Spontaneous reboots since 2.6.29-rc*
Submitter : Maciej Rutecki <[email protected]>
Date : 2009-04-17 17:03 (30 days old)
References : http://marc.info/?l=linux-kernel&m=123998788921733&w=4

#28 lore raw

Re: [Bug #13172] Spontaneous reboots since 2.6.29-rc*

2009/5/16 Rafael J. Wysocki <[email protected]>:

Quoted 8 lines

This message has been generated automatically as a part of a report of regressions introduced between 2.6.28 and 2.6.29.

The following bug entry is on the current list of known regressions introduced between 2.6.28 and 2.6.29.  Please verify if it still should be listed and let me know (either way).

Quoted 7 lines

Bug-Entry       : http://bugzilla.kernel.org/show_bug.cgi?id=13172
Subject         : Spontaneous reboots since 2.6.29-rc* Submitter       : Maciej Rutecki <[email protected]> Date            : 2009-04-17 17:03 (30 days old)
References      : http://marc.info/?l=linux-kernel&m=123998788921733&w=4

I try:
CONFIG_MTRR_SANITIZER=y
CONFIG_MTRR_SANITIZER_ENABLE_DEFAULT=1
CONFIG_MTRR_SANITIZER_SPARE_REG_NR_DEFAULT=1

from:
http://marc.info/?l=linux-kernel&m=124022460715035&w=4

Spontaneous reboots occur less often than in previous .config. From last report it occur once or twice. I think, it's hardware/bios/mtrr issue.

Because of this I think we should remove this regression from list, until I find out, why it happen, or more people report this. What do You think?

Regards

Signature · 2 lines
Maciej Rutecki
http://www.maciek.unixy.pl
#29 lore raw

Re: [Bug #13172] Spontaneous reboots since 2.6.29-rc*

Quoted 25 lines · Maciej Rutecki

2009/5/16 Rafael J. Wysocki <[email protected]>:

Quoted 8 lines

This message has been generated automatically as a part of a report of regressions introduced between 2.6.28 and 2.6.29.

The following bug entry is on the current list of known regressions introduced between 2.6.28 and 2.6.29. Please verify if it still should be listed and let me know (either way).

Quoted 7 lines

Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=13172
Subject : Spontaneous reboots since 2.6.29-rc*
Submitter : Maciej Rutecki <[email protected]>
Date : 2009-04-17 17:03 (30 days old)
References : http://marc.info/?l=linux-kernel&m=123998788921733&w=4

I try:
CONFIG_MTRR_SANITIZER=y
CONFIG_MTRR_SANITIZER_ENABLE_DEFAULT=1
CONFIG_MTRR_SANITIZER_SPARE_REG_NR_DEFAULT=1

from:
http://marc.info/?l=linux-kernel&m=124022460715035&w=4

Quoted 7 lines

Spontaneous reboots occur less often than in previous .config. From last report it occur once or twice. I think, it's hardware/bios/mtrr issue.

Because of this I think we should remove this regression from list, until I find out, why it happen, or more people report this. What do You think?

I've closed the bug. Pleaes reopen it once you've found the root cause.

Thanks,
Rafael

#30 lore raw

[Bug #13175] sata_nv incompatible with async scsi scan

In reply to Rafael J. Wysocki

This message has been generated automatically as a part of a report of regressions introduced between 2.6.28 and 2.6.29.

The following bug entry is on the current list of known regressions introduced between 2.6.28 and 2.6.29. Please verify if it still should be listed and let me know (either way).

Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=13175
Subject : sata_nv incompatible with async scsi scan
Submitter : Benny Halevy <[email protected]>
Date : 2009-04-21 7:03 (26 days old)
References : http://marc.info/?l=linux-kernel&m=124029746431777&w=4

#31 lore raw

[Bug #13178] Booting very slow

In reply to Rafael J. Wysocki

This message has been generated automatically as a part of a report of regressions introduced between 2.6.28 and 2.6.29.

The following bug entry is on the current list of known regressions introduced between 2.6.28 and 2.6.29. Please verify if it still should be listed and let me know (either way).

Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=13178
Subject : Booting very slow
Submitter : Martin Knoblauch <[email protected]>
Date : 2009-04-24 12:45 (23 days old)
References : http://marc.info/?l=linux-kernel&m=124057716231773&w=4

#32 lore raw

Re: [Bug #13178] Booting very slow

----- Original Message ----

Quoted 14 lines

From: Rafael J. Wysocki <[email protected]>
To: Linux Kernel Mailing List <[email protected]>
Cc: Kernel Testers List <[email protected]>; Martin Knoblauch <[email protected]>
Sent: Saturday, May 16, 2009 10:06:02 PM
Subject: [Bug #13178] Booting very slow

This message has been generated automatically as a part of a report of regressions introduced between 2.6.28 and 2.6.29.

The following bug entry is on the current list of known regressions introduced between 2.6.28 and 2.6.29. Please verify if it still should be listed and let me know (either way).

Quoted 5 lines

Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=13178
Subject : Booting very slow
Submitter : Martin Knoblauch
Date : 2009-04-24 12:45 (23 days old)
References : http://marc.info/?l=linux-kernel&m=124057716231773&w=4

The issue is still open. It turns out that starting with 2.6.29-rc1 /proc/mounts already has a "sysfs" line when entering the startup scripts from initrd. This breaks the RHEL4 firmware hotplug script.

Simple fix to user space is available. I do not know how important this issue is.

Anyway, I am in the process of bisecting the problem. It is just a bit tedious in the my customers and employers environment :-(

Cheers
Martin

#33 lore raw

Re: [Bug #13178] Booting very slow

Quoted 23 lines · Martin Knoblauch

----- Original Message ----

Quoted 14 lines

From: Rafael J. Wysocki <[email protected]>
To: Linux Kernel Mailing List <[email protected]>
Cc: Kernel Testers List <[email protected]>; Martin Knoblauch <[email protected]>
Sent: Saturday, May 16, 2009 10:06:02 PM
Subject: [Bug #13178] Booting very slow

This message has been generated automatically as a part of a report of regressions introduced between 2.6.28 and 2.6.29.

The following bug entry is on the current list of known regressions introduced between 2.6.28 and 2.6.29. Please verify if it still should be listed and let me know (either way).

Quoted 5 lines

Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=13178
Subject : Booting very slow
Submitter : Martin Knoblauch
Date : 2009-04-24 12:45 (23 days old)
References : http://marc.info/?l=linux-kernel&m=124057716231773&w=4

Quoted 5 lines

The issue is still open. It turns out that starting with 2.6.29-rc1 /proc/mounts already has a "sysfs" line when entering the startup scripts from initrd. This breaks the RHEL4 firmware hotplug script.

Simple fix to user space is available. I do not know how important this issue is.

Anyway, I am in the process of bisecting the problem. It is just a bit tedious in the my customers and employers environment :-(

Thanks a lot for doing this.

Best,
Rafael

#34 lore raw

Re: [Bug #13178] Booting very slow

In reply to Martin Knoblauch
Quoted 7 lines · Martin Knoblauch
Quoted 5 lines

Bug-Entry    : http://bugzilla.kernel.org/show_bug.cgi?id=13178
Subject        : Booting very slow
Submitter    : Martin Knoblauch
Date        : 2009-04-24 12:45 (23 days old)
References    : http://marc.info/?l=linux-kernel&m=124057716231773&w=4

 The issue is still open. It turns out that starting with 2.6.29-rc1 /proc/mounts already has a "sysfs" line when entering the startup scripts from initrd. This breaks the RHEL4 firmware hotplug script.

Is that possibly a missing/failing "umount /sys" _in_ initramfs, which leaves the sysfs entry in /proc/mounts behind, which then shows up as a duplicate when running in the real rootfs?

Thanks,
Kay

#35 lore raw

Re: [Bug #13178] Booting very slow

----- Original Message ----

Quoted 14 lines

From: Kay Sievers <[email protected]>
To: Martin Knoblauch <[email protected]>
Cc: Rafael J. Wysocki <[email protected]>; Linux Kernel Mailing List <[email protected]>; Kernel Testers List <[email protected]>
Sent: Tuesday, May 19, 2009 2:26:04 AM
Subject: Re: [Bug #13178] Booting very slow

Quoted 6 lines · Martin Knoblauch
Quoted 5 lines

Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=13178
Subject : Booting very slow
Submitter : Martin Knoblauch
Date : 2009-04-24 12:45 (23 days old)
References : http://marc.info/?l=linux-kernel&m=124057716231773&w=4

Quoted 8 lines
Quoted 1 line

The issue is still open. It turns out that starting with 2.6.29-rc1

/proc/mounts already has a "sysfs" line when entering the startup scripts from initrd. This breaks the RHEL4 firmware hotplug script.

Is that possibly a missing/failing "umount /sys" _in_ initramfs, which leaves the sysfs entry in /proc/mounts behind, which then shows up as a duplicate when running in the real rootfs?

could be. Remains the question, why it never showed up before 2.6.29. I compared my initrd images for 2.6.28 and 2.6.29-rc1, and they only differ in the module-binaries.

Cheers
Martin

#36 lore raw

Re: [Bug #13178] Booting very slow

Quoted 9 lines · Martin Knoblauch
Quoted 7 lines
Quoted 1 line

 The issue is still open. It turns out that starting with 2.6.29-rc1

/proc/mounts already has a "sysfs" line when entering the startup scripts from initrd. This breaks the RHEL4 firmware hotplug script.

Is that possibly a missing/failing "umount /sys" _in_ initramfs, which leaves the sysfs entry in /proc/mounts behind, which then shows up as a duplicate when running in the real rootfs?

 could be. Remains the question, why it never showed up before 2.6.29. I compared my initrd images for 2.6.28 and 2.6.29-rc1, and they only differ in the module-binaries.

I wouldn't be surprised if we are just "too fast" again now with the async stuff, for another piece of rather fragile userspace bootup logic, making some wrong assumptions. Are you compiling-in the modules for the root disk and the root filesystem?

Cheers,
Kay

#37 lore raw

Re: [Bug #13178] Booting very slow

------------------------------------------------------
Martin Knoblauch

email: k n o b i AT knobisoft DOT de
www:   http://www.knobisoft.de

----- Original Message ----

Quoted 20 lines

From: Kay Sievers <[email protected]>
To: Martin Knoblauch <[email protected]>
Cc: Rafael J. Wysocki <[email protected]>; Linux Kernel Mailing List <[email protected]>; Kernel Testers List <[email protected]>
Sent: Tuesday, May 19, 2009 10:58:24 AM
Subject: Re: [Bug #13178] Booting very slow

Quoted 2 lines · Martin Knoblauch
Quoted 2 lines
Quoted 1 line

The issue is still open. It turns out that starting with 2.6.29-rc1

/proc/mounts already has a "sysfs" line when entering the startup scripts

from

Quoted 7 lines
Quoted 5 lines

initrd. This breaks the RHEL4 firmware hotplug script.

Is that possibly a missing/failing "umount /sys" _in_ initramfs, which leaves the sysfs entry in /proc/mounts behind, which then shows up as a duplicate when running in the real rootfs?

could be. Remains the question, why it never showed up before 2.6.29. I

compared my initrd images for 2.6.28 and 2.6.29-rc1, and they only differ in the module-binaries.

Quoted 7 lines

I wouldn't be surprised if we are just "too fast" again now with the async stuff, for another piece of rather fragile userspace bootup logic, making some wrong assumptions. Are you compiling-in the modules for the root disk and the root filesystem?

Cheers,
Kay

timing may actually be the answer. I finally manged to bisect the thing and the first bad commit is this one:

|commit 1120f8b8169fb2cb51219d326892d963e762edb6
|Author: Stephen Hemminger <[email protected]>
|Date:   Thu Dec 18 09:17:16 2008 -0800
|
|    PCI: handle long delays in VPD access
|
|    Accessing the VPD area can take a long time.  The existing
|    VPD access code fails consistently on my hardware. There are comments
|
|    Change the access routines to:
|      * use a mutex rather than spinning with IRQ's disabled and lock held
|      * have a much longer timeout
|      * call cond_resched while spinning
|
|    Signed-off-by: Stephen Hemminger <[email protected]>
|    Reviewed-by: Matthew Wilcox <willy-VuQAYsv1563Yd54FQh9/[email protected]>
|    Signed-off-by: Jesse Barnes <[email protected]>

And no, the "cciss", "ext3" and "jbd" are modules in my intrd image.

I will continue the discussion under the original topic.

Cheers

#38 lore raw

[Bug #13144] resume from suspend fails using video card i915

In reply to Rafael J. Wysocki

This message has been generated automatically as a part of a report of regressions introduced between 2.6.28 and 2.6.29.

The following bug entry is on the current list of known regressions introduced between 2.6.28 and 2.6.29. Please verify if it still should be listed and let me know (either way).

Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=13144
Subject : resume from suspend fails using video card i915
Submitter : C Sights <[email protected]>
Date : 2009-04-21 17:03 (26 days old)

#39 lore raw

[Bug #13183] forcedeth: no link during initialization

In reply to Rafael J. Wysocki

This message has been generated automatically as a part of a report of regressions introduced between 2.6.28 and 2.6.29.

The following bug entry is on the current list of known regressions introduced between 2.6.28 and 2.6.29. Please verify if it still should be listed and let me know (either way).

Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=13183
Subject : forcedeth: no link during initialization
Submitter : Harald Dunkel <[email protected]>
Date : 2009-04-23 13:02 (24 days old)
References : http://marc.info/?l=linux-kernel&m=124049180309233&w=4

#40 lore raw

[Bug #13186] cpufreq timer teardown problem

In reply to Rafael J. Wysocki

This message has been generated automatically as a part of a report of regressions introduced between 2.6.28 and 2.6.29.

The following bug entry is on the current list of known regressions introduced between 2.6.28 and 2.6.29. Please verify if it still should be listed and let me know (either way).

Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=13186
Subject : cpufreq timer teardown problem
Submitter : Mathieu Desnoyers <mathieu.desnoyers-scC8bbJcJLCw5LPnMra/[email protected]>
Date : 2009-04-23 14:00 (24 days old)
References : http://marc.info/?l=linux-kernel&m=124049523515036&w=4

Patch : http://patchwork.kernel.org/patch/19754/

		  http://patchwork.kernel.org/patch/19753/
#41 lore raw

PATCH 1/1 cpufreq: remove rwsem lock from CPUFREQ_GOV_STOP call

Quoted 8 lines · * Rafael J. Wysocki ([email protected]) wrote:

This message has been generated automatically as a part of a report of regressions introduced between 2.6.28 and 2.6.29.

The following bug entry is on the current list of known regressions introduced between 2.6.28 and 2.6.29. Please verify if it still should be listed and let me know (either way).

Quoted 8 lines

Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=13186
Subject : cpufreq timer teardown problem
Submitter : Mathieu Desnoyers <mathieu.desnoyers-scC8bbJcJLCw5LPnMra/[email protected]>
Date : 2009-04-23 14:00 (24 days old)
References : http://marc.info/?l=linux-kernel&m=124049523515036&w=4

Patch : http://patchwork.kernel.org/patch/19754/

		  http://patchwork.kernel.org/patch/19753/

The patches linked above depend on the following patch to remove circular locking dependency :

cpufreq: remove rwsem lock from CPUFREQ_GOV_STOP call

(the following issue was faced when using cancel_delayed_work_sync() in the timer teardown (which fixes a race).

Quoted 9 lines · * KOSAKI Motohiro ([email protected])…

Hi

my box output following warnings.
it seems regression by commit 7ccc7608b836e58fbacf65ee4f8eefa288e86fac.

A: work -> do_dbs_timer() -> cpu_policy_rwsem
B: store() -> cpu_policy_rwsem -> cpufreq_governor_dbs() -> work

Hrm, I think it must be due to my attempt to fix the timer teardown race in ondemand governor mixed with new locking behavior in 2.6.30-rc.

The rwlock seems to be taken around the whole call to cpufreq_governor_dbs(), when it should be only taken around accesses to the locked data, and especially *not* around the call to dbs_timer_exit().

Reverting my fix attempt would put the teardown race back in place (replacing the cancel_delayed_work_sync by cancel_delayed_work). Instead, a proper fix would imply modifying this critical section :

cpufreq.c: __cpufreq_remove_dev()
...

        if (cpufreq_driver->target)
                __cpufreq_governor(data, CPUFREQ_GOV_STOP);

        unlock_policy_rwsem_write(cpu);

To make sure the __cpufreq_governor() callback is not called with rwsem held. This would allow execution of cancel_delayed_work_sync() without being nested within the rwsem.

Applies on top of the 2.6.30-rc5 tree.

Required to remove circular dep in teardown of both conservative and ondemande governors so they can use cancel_delayed_work_sync(). CPUFREQ_GOV_STOP does not modify the policy, therefore this locking seemed unneeded.

CC KOSAKI Motohiro <[email protected]>
Cc Greg KH <[email protected]>
CC Ingo Molnar <[email protected]>
CC "Rafael J. Wysocki" <[email protected]>
CC Ben Slusky <sluskyb-k/[email protected]>
CC Dave Jones <[email protected]>
CC Chris Wright <[email protected]>
CC Andrew Morton <akpm-de/[email protected]>
---
 drivers/cpufreq/cpufreq.c |    4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)
drivers/cpufreq/cpufreq.c +2 -2
Index: linux-2.6-lttng/drivers/cpufreq/cpufreq.c
===================================================================
@@ -1070,11 +1070,11 @@ static int __cpufreq_remove_dev(struct s
 	spin_unlock_irqrestore(&cpufreq_driver_lock, flags);
 #endif
 
+	unlock_policy_rwsem_write(cpu);
+
 	if (cpufreq_driver->target)
 		__cpufreq_governor(data, CPUFREQ_GOV_STOP);
 
-	unlock_policy_rwsem_write(cpu);
-
 	kobject_put(&data->kobj);
 
 	/* we need to make sure that the underlying kobj is actually
Signature · 2 lines
Mathieu Desnoyers
OpenPGP key fingerprint: 8CD5 52C3 8E3C 4140 715F  BA06 3F25 A8FE 3BAE 9A68
#42 lore raw

PATCH 1/1 cpufreq fix timer teardown in conservative governor

In reply to Rafael J. Wysocki
Quoted 8 lines · * Rafael J. Wysocki ([email protected]) wrote:

This message has been generated automatically as a part of a report of regressions introduced between 2.6.28 and 2.6.29.

The following bug entry is on the current list of known regressions introduced between 2.6.28 and 2.6.29. Please verify if it still should be listed and let me know (either way).

Quoted 9 lines

Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=13186
Subject : cpufreq timer teardown problem
Submitter : Mathieu Desnoyers <mathieu.desnoyers-scC8bbJcJLCw5LPnMra/[email protected]>
Date : 2009-04-23 14:00 (24 days old)
References : http://marc.info/?l=linux-kernel&m=124049523515036&w=4

Patch : http://patchwork.kernel.org/patch/19754/

		  http://patchwork.kernel.org/patch/19753/

(re-send with updated changelog)

cpufreq fix timer teardown in conservative governor

The problem is that dbs_timer_exit() uses cancel_delayed_work() when it should use cancel_delayed_work_sync(). cancel_delayed_work() does not wait for the workqueue handler to exit.

The ondemand governor does not seem to be affected because the
"if (!dbs_info->enable)" check at the beginning of the workqueue handler returns immediately without rescheduling the work. The conservative governor in 2.6.30-rc has the same check as the ondemand governor, which makes things usually run smoothly. However, if the governor is quickly stopped and then started, this could lead to the following race :

dbs_enable could be reenabled and multiple do_dbs_timer handlers would run. This is why a synchronized teardown is required.

Depends on patch
cpufreq: remove rwsem lock from CPUFREQ_GOV_STOP call

The following patch applies to 2.6.30-rc2. Stable kernels have a similar issue which should also be fixed, but the code changed between 2.6.29 and 2.6.30, so this patch only applies to 2.6.30-rc.

---
 drivers/cpufreq/cpufreq_conservative.c |    5 ++++-
 1 file changed, 4 insertions(+), 1 deletion(-)
drivers/cpufreq/cpufreq_conservative.c +4 -1
Index: linux-2.6-lttng/drivers/cpufreq/cpufreq_conservative.c
===================================================================
@@ -91,6 +91,9 @@ static unsigned int dbs_enable;	/* numbe
  * (like __cpufreq_driver_target()) is being called with dbs_mutex taken, then
  * cpu_hotplug lock should be taken before that. Note that cpu_hotplug lock
  * is recursive for the same process. -Venki
+ * DEADLOCK ALERT! (2) : do_dbs_timer() must not take the dbs_mutex, because it
+ * would deadlock with cancel_delayed_work_sync(), which is needed for proper
+ * raceless workqueue teardown.
  */
 static DEFINE_MUTEX(dbs_mutex);
 
@@ -542,7 +545,7 @@ static inline void dbs_timer_init(struct
 static inline void dbs_timer_exit(struct cpu_dbs_info_s *dbs_info)
 {
 	dbs_info->enable = 0;
-	cancel_delayed_work(&dbs_info->work);
+	cancel_delayed_work_sync(&dbs_info->work);
 }
 
 static int cpufreq_governor_dbs(struct cpufreq_policy *policy,
Signature · 2 lines
Mathieu Desnoyers
OpenPGP key fingerprint: 8CD5 52C3 8E3C 4140 715F  BA06 3F25 A8FE 3BAE 9A68
#43 lore raw

PATCH 1/1 cpufreq fix timer teardown in ondemand governor

In reply to Rafael J. Wysocki
Quoted 8 lines · * Rafael J. Wysocki ([email protected]) wrote:

This message has been generated automatically as a part of a report of regressions introduced between 2.6.28 and 2.6.29.

The following bug entry is on the current list of known regressions introduced between 2.6.28 and 2.6.29. Please verify if it still should be listed and let me know (either way).

Quoted 9 lines

Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=13186
Subject : cpufreq timer teardown problem
Submitter : Mathieu Desnoyers <mathieu.desnoyers-scC8bbJcJLCw5LPnMra/[email protected]>
Date : 2009-04-23 14:00 (24 days old)
References : http://marc.info/?l=linux-kernel&m=124049523515036&w=4

Patch : http://patchwork.kernel.org/patch/19754/

		  http://patchwork.kernel.org/patch/19753/

(updated changelog)

cpufreq fix timer teardown in ondemand governor

The problem is that dbs_timer_exit() uses cancel_delayed_work() when it should use cancel_delayed_work_sync(). cancel_delayed_work() does not wait for the workqueue handler to exit.

The ondemand governor does not seem to be affected because the
"if (!dbs_info->enable)" check at the beginning of the workqueue handler returns immediately without rescheduling the work. The conservative governor in 2.6.30-rc has the same check as the ondemand governor, which makes things usually run smoothly. However, if the governor is quickly stopped and then started, this could lead to the following race :

dbs_enable could be reenabled and multiple do_dbs_timer handlers would run. This is why a synchronized teardown is required.

The following patch applies to, at least, 2.6.28.x, 2.6.29.1, 2.6.30-rc2.

Depends on patch
cpufreq: remove rwsem lock from CPUFREQ_GOV_STOP call

---
 drivers/cpufreq/cpufreq_ondemand.c |    5 ++++-
 1 file changed, 4 insertions(+), 1 deletion(-)
drivers/cpufreq/cpufreq_ondemand.c +4 -1
Index: linux-2.6-lttng/drivers/cpufreq/cpufreq_ondemand.c
===================================================================
@@ -98,6 +98,9 @@ static unsigned int dbs_enable;	/* numbe
  * (like __cpufreq_driver_target()) is being called with dbs_mutex taken, then
  * cpu_hotplug lock should be taken before that. Note that cpu_hotplug lock
  * is recursive for the same process. -Venki
+ * DEADLOCK ALERT! (2) : do_dbs_timer() must not take the dbs_mutex, because it
+ * would deadlock with cancel_delayed_work_sync(), which is needed for proper
+ * raceless workqueue teardown.
  */
 static DEFINE_MUTEX(dbs_mutex);
 
@@ -562,7 +565,7 @@ static inline void dbs_timer_init(struct
 static inline void dbs_timer_exit(struct cpu_dbs_info_s *dbs_info)
 {
 	dbs_info->enable = 0;
-	cancel_delayed_work(&dbs_info->work);
+	cancel_delayed_work_sync(&dbs_info->work);
 }
 
 static int cpufreq_governor_dbs(struct cpufreq_policy *policy,
Signature · 2 lines
Mathieu Desnoyers
OpenPGP key fingerprint: 8CD5 52C3 8E3C 4140 715F  BA06 3F25 A8FE 3BAE 9A68
#44 lore raw

[Bug #13225] [2.6.29 regression] Software suspend no longer works

In reply to Rafael J. Wysocki

This message has been generated automatically as a part of a report of regressions introduced between 2.6.28 and 2.6.29.

The following bug entry is on the current list of known regressions introduced between 2.6.28 and 2.6.29. Please verify if it still should be listed and let me know (either way).

Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=13225
Subject : [2.6.29 regression] Software suspend no longer works
Submitter : Artem S. Tashkinov <t.artem-VInPYn6yXxRWk0Htik3J/[email protected]>
Date : 2009-05-02 21:41 (15 days old)

#45 lore raw

[Bug #13269] WARNING: at kernel/hrtimer.c:625 hres_timers_resume+0x3c/0x48() when resuming

In reply to Rafael J. Wysocki

This message has been generated automatically as a part of a report of regressions introduced between 2.6.28 and 2.6.29.

The following bug entry is on the current list of known regressions introduced between 2.6.28 and 2.6.29. Please verify if it still should be listed and let me know (either way).

Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=13269
Subject : WARNING: at kernel/hrtimer.c:625 hres_timers_resume+0x3c/0x48() when resuming
Submitter : cedric <[email protected]>
Date : 2009-05-08 08:48 (9 days old)

#46 lore raw

[Bug #13232] ext3/4 with synchronous writes gets wedged by Postfix

In reply to Rafael J. Wysocki

This message has been generated automatically as a part of a report of regressions introduced between 2.6.28 and 2.6.29.

The following bug entry is on the current list of known regressions introduced between 2.6.28 and 2.6.29. Please verify if it still should be listed and let me know (either way).

Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=13232
Subject : ext3/4 with synchronous writes gets wedged by Postfix
Submitter : David Watson <[email protected]>
Date : 2009-05-03 19:46 (14 days old)

#47 lore raw

Re: [Bug #13232] ext3/4 with synchronous writes gets wedged by Postfix

Quoted 8 lines · Rafael J. Wysocki

This message has been generated automatically as a part of a report of regressions introduced between 2.6.28 and 2.6.29.

The following bug entry is on the current list of known regressions introduced between 2.6.28 and 2.6.29. Please verify if it still should be listed and let me know (either way).

Quoted 4 lines

Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=13232
Subject : ext3/4 with synchronous writes gets wedged by Postfix
Submitter : David Watson <[email protected]>
Date : 2009-05-03 19:46 (14 days old)

This turned out to be caused by change in the VFS, as documented in the bug report. Al Viro has a patch, which I've reviewed.

David, would you be able to try testing Al's proposed patch, since you have an easy reproduction case? Thanks,

- Ted

#48 lore raw

Re: [Bug #13232] ext3/4 with synchronous writes gets wedged by Postfix

Quoted 11 lines · Theodore Tso
Quoted 4 lines · Rafael J. Wysocki

Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=13232
Subject : ext3/4 with synchronous writes gets wedged by Postfix
Submitter : David Watson <[email protected]>
Date : 2009-05-03 19:46 (14 days old)

This turned out to be caused by change in the VFS, as documented in the bug report. Al Viro has a patch, which I've reviewed.

David, would you be able to try testing Al's proposed patch, since you have an easy reproduction case? Thanks,

Yes, it fixes the problem for me on 2.6.30-rc6-git3 and 2.6.29.4-rc1.

#49 lore raw

Re: [Bug #13232] ext3/4 with synchronous writes gets wedged by Postfix

Quoted 7 lines · David Watson
Quoted 6 lines · Theodore Tso
Quoted 4 lines · Rafael J. Wysocki

Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=13232
Subject : ext3/4 with synchronous writes gets wedged by Postfix
Submitter : David Watson <[email protected]>
Date : 2009-05-03 19:46 (14 days old)

Quoted 7 lines
Quoted 5 lines

This turned out to be caused by change in the VFS, as documented in the bug report. Al Viro has a patch, which I've reviewed.

David, would you be able to try testing Al's proposed patch, since you have an easy reproduction case? Thanks,

Yes, it fixes the problem for me on 2.6.30-rc6-git3 and 2.6.29.4-rc1.

Thanks, David.

Al, Jan Kara and I have reviewed your patch, and we can add a
Tested-by: from David Watson (assuming David, you don't mind your name or e-mail address showing up in the Kernel commit logs --- if you want us to suppress one or both, please let us know). Given this is a 2.6.28 regression, and this can certainly affect real-life users, I think we should push your patch to Linus for 2.6.30. Do you agree?

Regards,

- Ted

#50 lore raw

Re: [Bug #13232] ext3/4 with synchronous writes gets wedged by Postfix

Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line

"Theodore" == Theodore Tso <[email protected]> writes:

Quoted 7 lines · David Watson
Quoted 7 lines · Theodore Tso
Quoted 6 lines · Rafael J. Wysocki
Quoted 4 lines

Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=13232
Subject : ext3/4 with synchronous writes gets wedged by Postfix
Submitter : David Watson <[email protected]>
Date : 2009-05-03 19:46 (14 days old)

Quoted 7 lines
Quoted 7 lines
Quoted 5 lines

This turned out to be caused by change in the VFS, as documented in the bug report. Al Viro has a patch, which I've reviewed.

David, would you be able to try testing Al's proposed patch, since you have an easy reproduction case? Thanks,

Yes, it fixes the problem for me on 2.6.30-rc6-git3 and 2.6.29.4-rc1.

Theodore> Al, Jan Kara and I have reviewed your patch, and we can add Theodore> a Tested-by: from David Watson (assuming David, you don't Theodore> mind your name or e-mail address showing up in the Kernel Theodore> commit logs --- if you want us to suppress one or both, Theodore> please let us know). Given this is a 2.6.28 regression, and Theodore> this can certainly affect real-life users, I think we should Theodore> push your patch to Linus for 2.6.30. Do you agree?

I wonder if this is the reason my main file server has been locking up solid under 2.6.29 or newer kernels lately, but 2.6.28 is rock solid. Since it's my main file server at home, and with my home dir NFS mounted from it onto another system, it's been hard to catch. I spent some time fiddling around getting netconsole setup, but then I ran out of time.

My system is a Debian, pretty upto date, PIII, 550Mhz Dual CPU, 3Gb RAM, lots of SCSI, SATA and IDE busses, with various types of devices on all the busses, from DLT tape drive and library, to a mix of disks. I'm also running ext4 on a mirrored pair disks I use for spooling backups to tape from. Ext3 on the rest of my mirrored filesystems as well.

If someone could send me the patch, I'll apply it and see how well 2.6.29.[34] works, and whether or not 2.6.30-rcN works as well. Reproducing the problem was pretty easy for me.

Thanks,
John

#51 lore raw

Re: [Bug #13232] ext3/4 with synchronous writes gets wedged by Postfix

Quoted 6 lines · John Stoffel

I wonder if this is the reason my main file server has been locking up solid under 2.6.29 or newer kernels lately, but 2.6.28 is rock solid. Since it's my main file server at home, and with my home dir NFS mounted from it onto another system, it's been hard to catch. I spent some time fiddling around getting netconsole setup, but then I ran out of time.

Unless you have your partition mounted with the "sync" mount option (which has negative performance implifications; it makes sense for a mail queue directory, but not necessarily for a general purpose file server) or you have a directory chattr'ed with the sync flag, probably not...

If you want to try it, though, the patch is available here:

http://bugzilla.kernel.org/attachment.cgi?id=21436

Quoted 3 lines

If someone could send me the patch, I'll apply it and see how well 2.6.29.[34] works, and whether or not 2.6.30-rcN works as well. Reproducing the problem was pretty easy for me.

Anything on the console? Any oops messages, or soft lockup warnings?

What filesystem(s) are you using?

- Ted

#52 lore raw

Re: [Bug #13232] ext3/4 with synchronous writes gets wedged by Postfix

Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line

"Theodore" == Theodore Tso <[email protected]> writes:

Oops. It looks like 2.6.29.3 is actually quite solid. My fault, I must have gotten confused. I know that 2.6.30-rc* was unstable on there and locked up easily.

Quoted 6 lines · John Stoffel
Quoted 6 lines

I wonder if this is the reason my main file server has been locking up solid under 2.6.29 or newer kernels lately, but 2.6.28 is rock solid. Since it's my main file server at home, and with my home dir NFS mounted from it onto another system, it's been hard to catch. I spent some time fiddling around getting netconsole setup, but then I ran out of time.

Theodore> Unless you have your partition mounted with the "sync" mount Theodore> option (which has negative performance implifications; it Theodore> makes sense for a mail queue directory, but not necessarily Theodore> for a general purpose file server) or you have a directory Theodore> chattr'ed with the sync flag, probably not...

Theodore> If you want to try it, though, the patch is available here:

Theodore> http://bugzilla.kernel.org/attachment.cgi?id=21436

Ok, then it's probably not something I need to test, since I'm only mounting stuff noatime.

Quoted 3 lines
Quoted 3 lines

If someone could send me the patch, I'll apply it and see how well 2.6.29.[34] works, and whether or not 2.6.30-rcN works as well. Reproducing the problem was pretty easy for me.

Theodore> Anything on the console? Any oops messages, or soft lockup warnings?

Nothing. I've not had the time lately to reboot the system to try 2.6.29 or newer with all the lockup debugging stuff yet. Maybe tonight I'll get a chance.

Theodore> What filesystem(s) are you using?

ext3 for everything, except one staging area running ext4 which is only used for bacula to stage data before writing to tape. It's solid under 2.6.29.3 (dammit, I must have mis-remembered) and it's been up now for six days running backups and serving NFS files.

Here's my filesystems:

Quoted 1 line

mount

/dev/sda2 on / type ext3 (rw,errors=remount-ro)
tmpfs on /lib/init/rw type tmpfs (rw,nosuid,mode=0755) proc on /proc type proc (rw,noexec,nosuid,nodev) sysfs on /sys type sysfs (rw,noexec,nosuid,nodev) procbususb on /proc/bus/usb type usbfs (rw)
/udev on /dev type tmpfs (rw,mode=0755)
tmpfs on /dev/shm type tmpfs (rw,nosuid,nodev)
devpts on /dev/pts type devpts (rw,noexec,nosuid,gid=5,mode=620) fusectl on /sys/fs/fuse/connections type fusectl (rw) /dev/sda5 on /var type ext3 (rw,noatime)
/dev/sda1 on /boot type ext3 (rw,noatime)
/dev/sda6 on /usr type ext3 (rw,noatime)
/dev/dm-1 on /home type ext3 (rw,noatime)
/dev/dm-2 on /local type ext3 (rw,noatime)
overflow on /tmp type tmpfs (rw,size=1048576,mode=1777,size=50%) rpc_pipefs on /var/lib/nfs/rpc_pipefs type rpc_pipefs (rw) nfsd on /proc/fs/nfsd type nfsd (rw)
binfmt_misc on /proc/sys/fs/binfmt_misc type binfmt_misc (rw,noexec,nosuid,nodev) /dev/mapper/onetwenty-staging on /staging type ext4 (rw,noatime)

When the system locks up, there's nothing in the logs, nothing on the screen, even when I leave it turned to VT1 (Ctl-Alt-F1) and then wait for a lockup, the screen is completely blank.

I'll see about finding some more time to beat on this and get better results back to people.

John

#53 lore raw

[Bug #13271] ath9k stop working since 2.6.29

In reply to Rafael J. Wysocki

This message has been generated automatically as a part of a report of regressions introduced between 2.6.28 and 2.6.29.

The following bug entry is on the current list of known regressions introduced between 2.6.28 and 2.6.29. Please verify if it still should be listed and let me know (either way).

Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=13271
Subject : ath9k stop working since 2.6.29
Submitter : lyman <[email protected]>
Date : 2009-05-10 01:58 (7 days old)

#54 lore raw
In reply to Rafael J. Wysocki

2009/5/16 Rafael J. Wysocki <[email protected]>:

Quoted 6 lines

Bug-Entry       : http://bugzilla.kernel.org/show_bug.cgi?id=12499
Subject         : Problem with using bluetooth adaper connected to usb port Submitter       : Maciej Rutecki <[email protected]> Date            : 2009-01-13 18:34 (124 days old)
References      : http://marc.info/?l=linux-kernel&m=123187185426236&w=4
Handled-By      : Marcel Holtmann <[email protected]>

2.6.30-rc6 works fine. Please remove it.

Regards

Signature · 6 lines
Maciej Rutecki
http://www.maciek.unixy.pl
--
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
#55 lore raw
In reply to Rafael J. Wysocki

2009/5/16 Rafael J. Wysocki <[email protected]>:

Quoted 6 lines

Bug-Entry       : http://bugzilla.kernel.org/show_bug.cgi?id=12499
Subject         : Problem with using bluetooth adaper connected to usb port Submitter       : Maciej Rutecki <[email protected]> Date            : 2009-01-13 18:34 (124 days old)
References      : http://marc.info/?l=linux-kernel&m=123187185426236&w=4
Handled-By      : Marcel Holtmann <[email protected]>

2.6.30-rc6 works fine. Please remove it.

Regards

Signature · 6 lines
Maciej Rutecki
http://www.maciek.unixy.pl
_______________________________________________
linux-pm mailing list
[email protected]
https://lists.linux-foundation.org/mailman/listinfo/linux-pm