2.6.29-git13: Reported regressions from 2.6.28

2.6.29-git13: Reported regressions from 2.6.28

[Rafael J. Wysocki]

[Notes:
* Some new regressions from 2.6.28 have been reported since the release of
  2.6.29, so here's an update of the regression list.
* I could have missed some fixes due to the large amounts of stuff merged
  recently.  Please have a look at the list and let me know if I can drop
  anything from it.
* I'm not going to track regressions from 2.6.27 any more.
* Next time I'll list regressions from 2.6.29 (after 2.6.30-rc1) and new
  regressions from 2.6.28 (if any) will be appended to the list below as
  "regressions introduced between 2.6.28 and 2.6.29".]

This message contains a list of some regressions from 2.6.28, 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 from 2.6.28, 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-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=13019
Subject		: /proc/<pid>/maps offset output broken in 2.6.29
Submitter	: "Chris Friesen" <cfriesen-ZIRUuHA3oDzQT0dZR+AlfA@public.gmane.org>
Date		: 2009-04-01 23:18 (6 days old)
References	: http://marc.info/?l=linuxppc-embedded&m=123862902916059&w=4
Handled-By	: Hugh Dickins <hugh-DTz5qymZ9yRBDgjK7y7TUQ@public.gmane.org>


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13018
Subject		: 2.6.29 on MacBook 2,1 fails to reboot
Submitter	: Trenton Adams <trenton.d.adams-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Date		: 2009-03-30 2:04 (8 days old)
References	: http://marc.info/?l=linux-kernel&m=123837870307249&w=4
Handled-By	: "Morten P.D. Stevens" <mstevens-APqb+XXLJz/QQQFqJy/XgFaTQe2KTcn/@public.gmane.org>


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13017
Subject		: ATA bus errors on resume
Submitter	: Niel Lambrechts <niel.lambrechts-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Date		: 2009-03-25 5:19 (13 days old)
References	: http://marc.info/?l=linux-kernel&m=123795841615989&w=4
Handled-By	: Tejun Heo <htejun-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13015
Subject		: pppoe over ethernet
Submitter	: Detlef Tschirschky <detlef.tschirschky-Mmb7MZpHnFY@public.gmane.org>
Date		: 2009-03-25 21:28 (13 days old)
References	: http://marc.info/?l=linux-kernel&m=123801663105671&w=4


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13001
Subject		: PCI-DMA: Out of IOMMU space
Submitter	:  <optimusgd-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Date		: 2009-04-03 09:30 (4 days old)


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12980
Subject		: lockup in X.org
Submitter	: Marcus Better <marcus-sJr3legBufCzQB+pC5nmwQ@public.gmane.org>
Date		: 2009-03-31 08:58 (7 days old)


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12975
Subject		: ata2:   lots of error messages, but OS still running well
Submitter	: Peter Teoh <htmldeveloper-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Date		: 2009-03-30 08:03 (8 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 <dobrev666-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Date		: 2009-03-29 18:02 (9 days old)


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12961
Subject		: Kernel panics in early boot: IO-APIC + timer doesn't work
Submitter	: Daniel Vetter <daniel-/w4YWyX8dFk@public.gmane.org>
Date		: 2009-03-28 19:00 (10 days old)
First-Bad-Commit: http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=8d6f0c8214928f7c5083dd54ecb69c5d615b516e


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/wNWPw@public.gmane.org>
Date		: 2009-03-26 16:14 (12 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 <cat-LJ1TwQYPT6cQrrorzV6ljw@public.gmane.org>
Date		: 2009-03-16 10:25 (22 days old)
References	: http://marc.info/?l=linux-kernel&m=123720083515950&w=4


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12908
Subject		: acpi_ex_extract_from_field -- div by zero
Submitter	: Jiri Slaby <jirislaby-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Date		: 2009-03-15 10:47 (23 days old)
References	: http://marc.info/?l=linux-kernel&m=123711408225013&w=4
Handled-By	: Lin Ming <ming.m.lin-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12899
Subject		: Crash in i915.ko: i915_driver_irq_handler
Submitter	: Helge Bahmann <helge.bahmann-opNxpl+3fjRBDgjK7y7TUQ@public.gmane.org>
Date		: 2009-03-20 07:13 (18 days old)


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12872
Subject		: pwc mmap always fails with EAGAIN
Submitter	: Markus <M4rkusXXL-S0/GAf8tV78@public.gmane.org>
Date		: 2009-03-14 16:42 (24 days old)
References	: http://marc.info/?l=linux-kernel&m=123704902201378&w=4


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12871
Subject		: usb bluetooth crashes system
Submitter	: Pavel Machek <pavel-+ZI9xUNit7I@public.gmane.org>
Date		: 2009-03-10 11:23 (28 days old)
References	: http://marc.info/?l=linux-kernel&m=123668450400940&w=4


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12867
Subject		: 2.6.29-rc7 broke r8169 MAC on Thecus n2100 ARM board
Submitter	: Mikael Pettersson <mikpe-1zs4UD6AkMk@public.gmane.org>
Date		: 2009-03-09 20:29 (29 days old)
References	: http://marc.info/?l=linux-kernel&m=123663065403760&w=4
Handled-By	: Francois Romieu <romieu-W8zweXLXuWQS+FvcfC7Uqw@public.gmane.org>


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 <jkarlson-kf+aQKke1yb1KXRcyAk9cg@public.gmane.org>
Date		: 2009-03-12 12:06 (26 days old)


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12836
Subject		: 2.6.29-rc breaks STD using Intel 945
Submitter	: Rolf Eike Beer <eike-kernel-F+mm6HnICJmzQB+pC5nmwQ@public.gmane.org>
Date		: 2009-03-04 19:20 (34 days old)
References	: http://marc.info/?l=linux-kernel&m=123619451406192&w=4


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12809
Subject		: iozone regression with 2.6.29-rc6
Submitter	: Lin Ming <ming.m.lin-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
Date		: 2009-02-27 9:13 (39 days old)
First-Bad-Commit: http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=1cf6e7d83bf334cc5916137862c920a97aabc018
References	: http://marc.info/?l=linux-kernel&m=123572630504360&w=4
		  http://lkml.org/lkml/2009/3/14/265
Handled-By	: Wu Fengguang <fengguang.wu-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12792
Subject		: 2.6.29-rc6-git4 boot failure
Submitter	: "Sachin P. Sant" <sachinp-xthvdsQ13ZrQT0dZR+AlfA@public.gmane.org>
Date		: 2009-02-27 23:19 (39 days old)
References	: http://ozlabs.org/pipermail/linuxppc-dev/2009-February/068771.html


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12778
Subject		: suspend regression from 29rc5 to 29rc6
Submitter	: yury <urykhy-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Date		: 2009-02-25 09:25 (41 days old)


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12771
Subject		: Oops in i915_gem_flush
Submitter	: Kalev Lember <kalev-KfhB8dnw0QSuvFJfX82//w@public.gmane.org>
Date		: 2009-02-24 08:35 (42 days old)


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-/E1597aS9LQAvxtiuMwx3w@public.gmane.org>
Date		: 2009-02-21 15:38 (45 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


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12763
Subject		: Different cpu MHz values for processor0 and processor1
Submitter	: "Matthew A. Bockol" <mbockol-dmoCqaWXHRX2fBVCVOL8/A@public.gmane.org>
Date		: 2009-02-21 5:42 (45 days old)
References	: http://marc.info/?l=linux-kernel&m=123519687807246&w=4


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 <nico-linux-20090213-xuaVFQXs+5hIG4jRRZ66WA@public.gmane.org>
Date		: 2009-02-13 9:33 (53 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
Handled-By	: Len Brown <lenb-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>


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 <smpuj-5URONGGNgjI@public.gmane.org>
Date		: 2009-02-09 13:01 (57 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=12670
Subject		: BUG: unable to handle kernel paging request at pin_to_kill+0x21
Submitter	: Alessandro Bono <alessandro.bono-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Date		: 2009-02-08 11:04 (58 days old)
References	: http://marc.info/?l=linux-kernel&m=123409113223833&w=4


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12668
Subject		: USB flash disk surprise disconnect
Submitter	: Vegard Nossum <vegard.nossum-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Date		: 2009-02-08 10:21 (58 days old)
References	: http://marc.info/?l=linux-kernel&m=123408851821292&w=4


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12574
Subject		: possible circular locking dependency detected
Submitter	: Michael S. Tsirkin <m.s.tsirkin-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Date		: 2009-01-29 11:35 (68 days old)
References	: http://lkml.org/lkml/2009/2/9/205


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12499
Subject		: Problem with using bluetooth adaper connected to usb port
Submitter	: "Maciej Rutecki" <maciej.rutecki-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Date		: 2009-01-13 18:34 (84 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" <rathamahata-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Date		: 2009-01-12 7:38 (85 days old)
References	: http://marc.info/?l=linux-kernel&m=123174591509586&w=4
Handled-By	: Bob Copeland <me-aXfl/3sk2vNUbtYUoyoikg@public.gmane.org>


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

Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13027
Subject		: Resume after hibernation regression in forcedeth
Submitter	: "Tvrtko A. Ursulin" <tvrtko-9sj9WOxYP5jR7s880joybQ@public.gmane.org>
Date		: 2009-03-27 20:09 (11 days old)
References	: http://marc.info/?l=linux-kernel&m=123818507814476&w=4
Handled-By	: Ed Swierk <eswierk-BGArkANP9klv6pq1l3V1OdBPR1lH4CV8@public.gmane.org>
Patch		: http://marc.info/?l=linux-kernel&m=123878076717061&w=4


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13026
Subject		: cs5536 is broken
Submitter	: Arnd Hannemann <hannemann-JasiFyN5vQG662+jY7v6MhvVK+yQ3ZXh@public.gmane.org>
Date		: 2009-04-06 18:11 (1 days old)
References	: http://marc.info/?l=linux-kernel&m=123904159829771&w=4
Handled-By	: Sergei Shtylyov <sshtylyov-hkdhdckH98+B+jHODAdFcQ@public.gmane.org>
Patch		: http://marc.info/?l=linux-kernel&m=123904273731477&w=4


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13016
Subject		: consistent oops from request_key in 2.6.29
Submitter	: Jeff Layton <jlayton-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
Date		: 2009-03-31 12:45 (7 days old)
References	: http://marc.info/?l=linux-kernel&m=123850360107293&w=4
Handled-By	: David Howells <dhowells-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
Patch		: http://marc.info/?l=linux-kernel&m=123852150806814&w=4


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12870
Subject		: 2.6.29-rc "TKIP: replay detected" regression
Submitter	: Hugh Dickins <hugh-DTz5qymZ9yRBDgjK7y7TUQ@public.gmane.org>
Date		: 2009-03-11 12:07 (27 days old)
References	: http://marc.info/?l=linux-kernel&m=123677337219148&w=4
Handled-By	: "John W. Linville" <linville-2XuSBdqkA4R54TAoqtyWWQ@public.gmane.org>
Patch		: http://marc.info/?l=linux-wireless&m=123678463704691&w=2


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12671
Subject		: uvc_status_cleanup(): undefined reference to `input_unregister_device'
Submitter	: Ingo Molnar <mingo-X9Un+BFzKDI@public.gmane.org>
Date		: 2009-02-08 14:58 (58 days old)
References	: http://marc.info/?l=linux-kernel&m=123410529909318&w=4
Handled-By	: Randy Dunlap <randy.dunlap-QHcLZuEGTsvQT0dZR+AlfA@public.gmane.org>
Patch		: http://lkml.org/lkml/2009/2/15/172


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12667
Subject		: Badness at kernel/time/timekeeping.c:98 in pmud (timekeeping_suspended)
Submitter	: Paul Collins <paul-dsjeNyW6Qm/D+ROgJ3VA+kB+6BGkLq7r@public.gmane.org>
Date		: 2009-01-21 7:15 (76 days old)
First-Bad-Commit: http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=1c5745aa380efb6417b5681104b007c8612fb496
References	: http://marc.info/?l=linux-kernel&m=123252215315106&w=4
Handled-By	: Benjamin Herrenschmidt <benh-XVmvHMARGAS8U2dJNN8I7kB+6BGkLq7r@public.gmane.org>
Patch		: http://lkml.org/lkml/2009/2/16/78


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 from 2.6.28,
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

2.6.29-git13: Reported regressions from 2.6.28

[Rafael J. Wysocki]

[Notes:
* Some new regressions from 2.6.28 have been reported since the release of
  2.6.29, so here's an update of the regression list.
* I could have missed some fixes due to the large amounts of stuff merged
  recently.  Please have a look at the list and let me know if I can drop
  anything from it.
* I'm not going to track regressions from 2.6.27 any more.
* Next time I'll list regressions from 2.6.29 (after 2.6.30-rc1) and new
  regressions from 2.6.28 (if any) will be appended to the list below as
  "regressions introduced between 2.6.28 and 2.6.29".]

This message contains a list of some regressions from 2.6.28, 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 from 2.6.28, 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-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=13019
Subject		: /proc/<pid>/maps offset output broken in 2.6.29
Submitter	: "Chris Friesen" <cfriesen@nortel.com>
Date		: 2009-04-01 23:18 (6 days old)
References	: http://marc.info/?l=linuxppc-embedded&m=123862902916059&w=4
Handled-By	: Hugh Dickins <hugh@veritas.com>


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13018
Subject		: 2.6.29 on MacBook 2,1 fails to reboot
Submitter	: Trenton Adams <trenton.d.adams@gmail.com>
Date		: 2009-03-30 2:04 (8 days old)
References	: http://marc.info/?l=linux-kernel&m=123837870307249&w=4
Handled-By	: "Morten P.D. Stevens" <mstevens@win-professional.com>


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13017
Subject		: ATA bus errors on resume
Submitter	: Niel Lambrechts <niel.lambrechts@gmail.com>
Date		: 2009-03-25 5:19 (13 days old)
References	: http://marc.info/?l=linux-kernel&m=123795841615989&w=4
Handled-By	: Tejun Heo <htejun@gmail.com>


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13015
Subject		: pppoe over ethernet
Submitter	: Detlef Tschirschky <detlef.tschirschky@gmx.de>
Date		: 2009-03-25 21:28 (13 days old)
References	: http://marc.info/?l=linux-kernel&m=123801663105671&w=4


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13001
Subject		: PCI-DMA: Out of IOMMU space
Submitter	:  <optimusgd@gmail.com>
Date		: 2009-04-03 09:30 (4 days old)


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12980
Subject		: lockup in X.org
Submitter	: Marcus Better <marcus@better.se>
Date		: 2009-03-31 08:58 (7 days old)


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12975
Subject		: ata2:   lots of error messages, but OS still running well
Submitter	: Peter Teoh <htmldeveloper@gmail.com>
Date		: 2009-03-30 08:03 (8 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 <dobrev666@gmail.com>
Date		: 2009-03-29 18:02 (9 days old)


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12961
Subject		: Kernel panics in early boot: IO-APIC + timer doesn't work
Submitter	: Daniel Vetter <daniel@ffwll.ch>
Date		: 2009-03-28 19:00 (10 days old)
First-Bad-Commit: http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=8d6f0c8214928f7c5083dd54ecb69c5d615b516e


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@xs4all.nl>
Date		: 2009-03-26 16:14 (12 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 <cat@zip.com.au>
Date		: 2009-03-16 10:25 (22 days old)
References	: http://marc.info/?l=linux-kernel&m=123720083515950&w=4


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12908
Subject		: acpi_ex_extract_from_field -- div by zero
Submitter	: Jiri Slaby <jirislaby@gmail.com>
Date		: 2009-03-15 10:47 (23 days old)
References	: http://marc.info/?l=linux-kernel&m=123711408225013&w=4
Handled-By	: Lin Ming <ming.m.lin@intel.com>


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12899
Subject		: Crash in i915.ko: i915_driver_irq_handler
Submitter	: Helge Bahmann <helge.bahmann@secunet.com>
Date		: 2009-03-20 07:13 (18 days old)


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12872
Subject		: pwc mmap always fails with EAGAIN
Submitter	: Markus <M4rkusXXL@web.de>
Date		: 2009-03-14 16:42 (24 days old)
References	: http://marc.info/?l=linux-kernel&m=123704902201378&w=4


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12871
Subject		: usb bluetooth crashes system
Submitter	: Pavel Machek <pavel@ucw.cz>
Date		: 2009-03-10 11:23 (28 days old)
References	: http://marc.info/?l=linux-kernel&m=123668450400940&w=4


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12867
Subject		: 2.6.29-rc7 broke r8169 MAC on Thecus n2100 ARM board
Submitter	: Mikael Pettersson <mikpe@it.uu.se>
Date		: 2009-03-09 20:29 (29 days old)
References	: http://marc.info/?l=linux-kernel&m=123663065403760&w=4
Handled-By	: Francois Romieu <romieu@fr.zoreil.com>


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 <jkarlson@cc.hut.fi>
Date		: 2009-03-12 12:06 (26 days old)


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12836
Subject		: 2.6.29-rc breaks STD using Intel 945
Submitter	: Rolf Eike Beer <eike-kernel@sf-tec.de>
Date		: 2009-03-04 19:20 (34 days old)
References	: http://marc.info/?l=linux-kernel&m=123619451406192&w=4


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12809
Subject		: iozone regression with 2.6.29-rc6
Submitter	: Lin Ming <ming.m.lin@intel.com>
Date		: 2009-02-27 9:13 (39 days old)
First-Bad-Commit: http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=1cf6e7d83bf334cc5916137862c920a97aabc018
References	: http://marc.info/?l=linux-kernel&m=123572630504360&w=4
		  http://lkml.org/lkml/2009/3/14/265
Handled-By	: Wu Fengguang <fengguang.wu@intel.com>


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12792
Subject		: 2.6.29-rc6-git4 boot failure
Submitter	: "Sachin P. Sant" <sachinp@in.ibm.com>
Date		: 2009-02-27 23:19 (39 days old)
References	: http://ozlabs.org/pipermail/linuxppc-dev/2009-February/068771.html


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12778
Subject		: suspend regression from 29rc5 to 29rc6
Submitter	: yury <urykhy@gmail.com>
Date		: 2009-02-25 09:25 (41 days old)


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12771
Subject		: Oops in i915_gem_flush
Submitter	: Kalev Lember <kalev@colleduc.ee>
Date		: 2009-02-24 08:35 (42 days old)


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@yahoo.com>
Date		: 2009-02-21 15:38 (45 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


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12763
Subject		: Different cpu MHz values for processor0 and processor1
Submitter	: "Matthew A. Bockol" <mbockol@carleton.edu>
Date		: 2009-02-21 5:42 (45 days old)
References	: http://marc.info/?l=linux-kernel&m=123519687807246&w=4


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 <nico-linux-20090213@schottelius.org>
Date		: 2009-02-13 9:33 (53 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
Handled-By	: Len Brown <lenb@kernel.org>


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 <smpuj@bk.ru>
Date		: 2009-02-09 13:01 (57 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=12670
Subject		: BUG: unable to handle kernel paging request at pin_to_kill+0x21
Submitter	: Alessandro Bono <alessandro.bono@gmail.com>
Date		: 2009-02-08 11:04 (58 days old)
References	: http://marc.info/?l=linux-kernel&m=123409113223833&w=4


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12668
Subject		: USB flash disk surprise disconnect
Submitter	: Vegard Nossum <vegard.nossum@gmail.com>
Date		: 2009-02-08 10:21 (58 days old)
References	: http://marc.info/?l=linux-kernel&m=123408851821292&w=4


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12574
Subject		: possible circular locking dependency detected
Submitter	: Michael S. Tsirkin <m.s.tsirkin@gmail.com>
Date		: 2009-01-29 11:35 (68 days old)
References	: http://lkml.org/lkml/2009/2/9/205


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12499
Subject		: Problem with using bluetooth adaper connected to usb port
Submitter	: "Maciej Rutecki" <maciej.rutecki@gmail.com>
Date		: 2009-01-13 18:34 (84 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" <rathamahata@gmail.com>
Date		: 2009-01-12 7:38 (85 days old)
References	: http://marc.info/?l=linux-kernel&m=123174591509586&w=4
Handled-By	: Bob Copeland <me@bobcopeland.com>


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

Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13027
Subject		: Resume after hibernation regression in forcedeth
Submitter	: "Tvrtko A. Ursulin" <tvrtko@ursulin.net>
Date		: 2009-03-27 20:09 (11 days old)
References	: http://marc.info/?l=linux-kernel&m=123818507814476&w=4
Handled-By	: Ed Swierk <eswierk@aristanetworks.com>
Patch		: http://marc.info/?l=linux-kernel&m=123878076717061&w=4


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13026
Subject		: cs5536 is broken
Submitter	: Arnd Hannemann <hannemann@nets.rwth-aachen.de>
Date		: 2009-04-06 18:11 (1 days old)
References	: http://marc.info/?l=linux-kernel&m=123904159829771&w=4
Handled-By	: Sergei Shtylyov <sshtylyov@ru.mvista.com>
Patch		: http://marc.info/?l=linux-kernel&m=123904273731477&w=4


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13016
Subject		: consistent oops from request_key in 2.6.29
Submitter	: Jeff Layton <jlayton@redhat.com>
Date		: 2009-03-31 12:45 (7 days old)
References	: http://marc.info/?l=linux-kernel&m=123850360107293&w=4
Handled-By	: David Howells <dhowells@redhat.com>
Patch		: http://marc.info/?l=linux-kernel&m=123852150806814&w=4


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12870
Subject		: 2.6.29-rc "TKIP: replay detected" regression
Submitter	: Hugh Dickins <hugh@veritas.com>
Date		: 2009-03-11 12:07 (27 days old)
References	: http://marc.info/?l=linux-kernel&m=123677337219148&w=4
Handled-By	: "John W. Linville" <linville@tuxdriver.com>
Patch		: http://marc.info/?l=linux-wireless&m=123678463704691&w=2


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12671
Subject		: uvc_status_cleanup(): undefined reference to `input_unregister_device'
Submitter	: Ingo Molnar <mingo@elte.hu>
Date		: 2009-02-08 14:58 (58 days old)
References	: http://marc.info/?l=linux-kernel&m=123410529909318&w=4
Handled-By	: Randy Dunlap <randy.dunlap@oracle.com>
Patch		: http://lkml.org/lkml/2009/2/15/172


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12667
Subject		: Badness at kernel/time/timekeeping.c:98 in pmud (timekeeping_suspended)
Submitter	: Paul Collins <paul@burly.ondioline.org>
Date		: 2009-01-21 7:15 (76 days old)
First-Bad-Commit: http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=1c5745aa380efb6417b5681104b007c8612fb496
References	: http://marc.info/?l=linux-kernel&m=123252215315106&w=4
Handled-By	: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Patch		: http://lkml.org/lkml/2009/2/16/78


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 from 2.6.28,
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

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

[Rafael J. Wysocki]

This message has been generated automatically as a part of a report
of recent regressions.

The following bug entry is on the current list of known regressions
from 2.6.28.  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" <maciej.rutecki@gmail.com>
Date		: 2009-01-13 18:34 (84 days old)
References	: http://marc.info/?l=linux-kernel&m=123187185426236&w=4

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

[Rafael J. Wysocki]

This message has been generated automatically as a part of a report
of recent regressions.

The following bug entry is on the current list of known regressions
from 2.6.28.  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" <maciej.rutecki-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Date		: 2009-01-13 18:34 (84 days old)
References	: http://marc.info/?l=linux-kernel&m=123187185426236&w=4

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

[Rafael J. Wysocki]

This message has been generated automatically as a part of a report
of recent regressions.

The following bug entry is on the current list of known regressions
from 2.6.28.  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 <smpuj-5URONGGNgjI@public.gmane.org>
Date		: 2009-02-09 13:01 (57 days old)
First-Bad-Commit: http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=1cfe62c8010ac56e1bd3827e30386a87cc2f3594

[Bug #12574] possible circular locking dependency detected

[Rafael J. Wysocki]

This message has been generated automatically as a part of a report
of recent regressions.

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


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12574
Subject		: possible circular locking dependency detected
Submitter	: Michael S. Tsirkin <m.s.tsirkin@gmail.com>
Date		: 2009-01-29 11:35 (68 days old)
References	: http://lkml.org/lkml/2009/2/9/205

[Bug #12668] USB flash disk surprise disconnect

[Rafael J. Wysocki]

This message has been generated automatically as a part of a report
of recent regressions.

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


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12668
Subject		: USB flash disk surprise disconnect
Submitter	: Vegard Nossum <vegard.nossum@gmail.com>
Date		: 2009-02-08 10:21 (58 days old)
References	: http://marc.info/?l=linux-kernel&m=123408851821292&w=4

[Bug #12671] uvc_status_cleanup(): undefined reference to `input_unregister_device'

[Rafael J. Wysocki]

This message has been generated automatically as a part of a report
of recent regressions.

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


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12671
Subject		: uvc_status_cleanup(): undefined reference to `input_unregister_device'
Submitter	: Ingo Molnar <mingo@elte.hu>
Date		: 2009-02-08 14:58 (58 days old)
References	: http://marc.info/?l=linux-kernel&m=123410529909318&w=4
Handled-By	: Randy Dunlap <randy.dunlap@oracle.com>
Patch		: http://lkml.org/lkml/2009/2/15/172

[Bug #12670] BUG: unable to handle kernel paging request at pin_to_kill+0x21

[Rafael J. Wysocki]

This message has been generated automatically as a part of a report
of recent regressions.

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


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12670
Subject		: BUG: unable to handle kernel paging request at pin_to_kill+0x21
Submitter	: Alessandro Bono <alessandro.bono@gmail.com>
Date		: 2009-02-08 11:04 (58 days old)
References	: http://marc.info/?l=linux-kernel&m=123409113223833&w=4

[Bug #12667] Badness at kernel/time/timekeeping.c:98 in pmud (timekeeping_suspended)

[Rafael J. Wysocki]

This message has been generated automatically as a part of a report
of recent regressions.

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


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12667
Subject		: Badness at kernel/time/timekeeping.c:98 in pmud (timekeeping_suspended)
Submitter	: Paul Collins <paul@burly.ondioline.org>
Date		: 2009-01-21 7:15 (76 days old)
First-Bad-Commit: http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=1c5745aa380efb6417b5681104b007c8612fb496
References	: http://marc.info/?l=linux-kernel&m=123252215315106&w=4
Handled-By	: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Patch		: http://lkml.org/lkml/2009/2/16/78

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

[Rafael J. Wysocki]

This message has been generated automatically as a part of a report
of recent regressions.

The following bug entry is on the current list of known regressions
from 2.6.28.  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 <smpuj@bk.ru>
Date		: 2009-02-09 13:01 (57 days old)
First-Bad-Commit: http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=1cfe62c8010ac56e1bd3827e30386a87cc2f3594

[Bug #12670] BUG: unable to handle kernel paging request at pin_to_kill+0x21

[Rafael J. Wysocki]

This message has been generated automatically as a part of a report
of recent regressions.

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


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12670
Subject		: BUG: unable to handle kernel paging request at pin_to_kill+0x21
Submitter	: Alessandro Bono <alessandro.bono-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Date		: 2009-02-08 11:04 (58 days old)
References	: http://marc.info/?l=linux-kernel&m=123409113223833&w=4

[Bug #12574] possible circular locking dependency detected

[Rafael J. Wysocki]

This message has been generated automatically as a part of a report
of recent regressions.

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


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12574
Subject		: possible circular locking dependency detected
Submitter	: Michael S. Tsirkin <m.s.tsirkin-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Date		: 2009-01-29 11:35 (68 days old)
References	: http://lkml.org/lkml/2009/2/9/205

[Bug #12668] USB flash disk surprise disconnect

[Rafael J. Wysocki]

This message has been generated automatically as a part of a report
of recent regressions.

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


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12668
Subject		: USB flash disk surprise disconnect
Submitter	: Vegard Nossum <vegard.nossum-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Date		: 2009-02-08 10:21 (58 days old)
References	: http://marc.info/?l=linux-kernel&m=123408851821292&w=4

[Bug #12671] uvc_status_cleanup(): undefined reference to `input_unregister_device'

[Rafael J. Wysocki]

This message has been generated automatically as a part of a report
of recent regressions.

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


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12671
Subject		: uvc_status_cleanup(): undefined reference to `input_unregister_device'
Submitter	: Ingo Molnar <mingo-X9Un+BFzKDI@public.gmane.org>
Date		: 2009-02-08 14:58 (58 days old)
References	: http://marc.info/?l=linux-kernel&m=123410529909318&w=4
Handled-By	: Randy Dunlap <randy.dunlap-QHcLZuEGTsvQT0dZR+AlfA@public.gmane.org>
Patch		: http://lkml.org/lkml/2009/2/15/172

[Bug #12667] Badness at kernel/time/timekeeping.c:98 in pmud (timekeeping_suspended)

[Rafael J. Wysocki]

This message has been generated automatically as a part of a report
of recent regressions.

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


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12667
Subject		: Badness at kernel/time/timekeeping.c:98 in pmud (timekeeping_suspended)
Submitter	: Paul Collins <paul-dsjeNyW6Qm/D+ROgJ3VA+kB+6BGkLq7r@public.gmane.org>
Date		: 2009-01-21 7:15 (76 days old)
First-Bad-Commit: http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=1c5745aa380efb6417b5681104b007c8612fb496
References	: http://marc.info/?l=linux-kernel&m=123252215315106&w=4
Handled-By	: Benjamin Herrenschmidt <benh-XVmvHMARGAS8U2dJNN8I7kB+6BGkLq7r@public.gmane.org>
Patch		: http://lkml.org/lkml/2009/2/16/78

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

[Rafael J. Wysocki]

This message has been generated automatically as a part of a report
of recent regressions.

The following bug entry is on the current list of known regressions
from 2.6.28.  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@yahoo.com>
Date		: 2009-02-21 15:38 (45 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

[Bug #12771] Oops in i915_gem_flush

[Rafael J. Wysocki]

This message has been generated automatically as a part of a report
of recent regressions.

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


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12771
Subject		: Oops in i915_gem_flush
Submitter	: Kalev Lember <kalev@colleduc.ee>
Date		: 2009-02-24 08:35 (42 days old)

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

[Rafael J. Wysocki]

This message has been generated automatically as a part of a report
of recent regressions.

The following bug entry is on the current list of known regressions
from 2.6.28.  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 <nico-linux-20090213@schottelius.org>
Date		: 2009-02-13 9:33 (53 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
Handled-By	: Len Brown <lenb@kernel.org>

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

[Rafael J. Wysocki]

This message has been generated automatically as a part of a report
of recent regressions.

The following bug entry is on the current list of known regressions
from 2.6.28.  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-/E1597aS9LQAvxtiuMwx3w@public.gmane.org>
Date		: 2009-02-21 15:38 (45 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

[Bug #12771] Oops in i915_gem_flush

[Rafael J. Wysocki]

This message has been generated automatically as a part of a report
of recent regressions.

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


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12771
Subject		: Oops in i915_gem_flush
Submitter	: Kalev Lember <kalev-KfhB8dnw0QSuvFJfX82//w@public.gmane.org>
Date		: 2009-02-24 08:35 (42 days old)

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

[Rafael J. Wysocki]

This message has been generated automatically as a part of a report
of recent regressions.

The following bug entry is on the current list of known regressions
from 2.6.28.  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 <nico-linux-20090213-xuaVFQXs+5hIG4jRRZ66WA@public.gmane.org>
Date		: 2009-02-13 9:33 (53 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
Handled-By	: Len Brown <lenb-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>

[Bug #12778] suspend regression from 29rc5 to 29rc6

[Rafael J. Wysocki]

This message has been generated automatically as a part of a report
of recent regressions.

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


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12778
Subject		: suspend regression from 29rc5 to 29rc6
Submitter	: yury <urykhy@gmail.com>
Date		: 2009-02-25 09:25 (41 days old)

[Bug #12778] suspend regression from 29rc5 to 29rc6

[Rafael J. Wysocki]

This message has been generated automatically as a part of a report
of recent regressions.

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


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12778
Subject		: suspend regression from 29rc5 to 29rc6
Submitter	: yury <urykhy-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Date		: 2009-02-25 09:25 (41 days old)

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

[Rafael J. Wysocki]

This message has been generated automatically as a part of a report
of recent regressions.

The following bug entry is on the current list of known regressions
from 2.6.28.  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 <jkarlson@cc.hut.fi>
Date		: 2009-03-12 12:06 (26 days old)

[Bug #12836] 2.6.29-rc breaks STD using Intel 945

[Rafael J. Wysocki]

This message has been generated automatically as a part of a report
of recent regressions.

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


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12836
Subject		: 2.6.29-rc breaks STD using Intel 945
Submitter	: Rolf Eike Beer <eike-kernel@sf-tec.de>
Date		: 2009-03-04 19:20 (34 days old)
References	: http://marc.info/?l=linux-kernel&m=123619451406192&w=4

[Bug #12867] 2.6.29-rc7 broke r8169 MAC on Thecus n2100 ARM board

[Rafael J. Wysocki]

This message has been generated automatically as a part of a report
of recent regressions.

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


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12867
Subject		: 2.6.29-rc7 broke r8169 MAC on Thecus n2100 ARM board
Submitter	: Mikael Pettersson <mikpe@it.uu.se>
Date		: 2009-03-09 20:29 (29 days old)
References	: http://marc.info/?l=linux-kernel&m=123663065403760&w=4
Handled-By	: Francois Romieu <romieu@fr.zoreil.com>

[Bug #12809] iozone regression with 2.6.29-rc6

[Rafael J. Wysocki]

This message has been generated automatically as a part of a report
of recent regressions.

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


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12809
Subject		: iozone regression with 2.6.29-rc6
Submitter	: Lin Ming <ming.m.lin@intel.com>
Date		: 2009-02-27 9:13 (39 days old)
First-Bad-Commit: http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=1cf6e7d83bf334cc5916137862c920a97aabc018
References	: http://marc.info/?l=linux-kernel&m=123572630504360&w=4
		  http://lkml.org/lkml/2009/3/14/265
Handled-By	: Wu Fengguang <fengguang.wu@intel.com>

[Bug #12809] iozone regression with 2.6.29-rc6

[Rafael J. Wysocki]

This message has been generated automatically as a part of a report
of recent regressions.

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


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12809
Subject		: iozone regression with 2.6.29-rc6
Submitter	: Lin Ming <ming.m.lin-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
Date		: 2009-02-27 9:13 (39 days old)
First-Bad-Commit: http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=1cf6e7d83bf334cc5916137862c920a97aabc018
References	: http://marc.info/?l=linux-kernel&m=123572630504360&w=4
		  http://lkml.org/lkml/2009/3/14/265
Handled-By	: Wu Fengguang <fengguang.wu-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>

[Bug #12836] 2.6.29-rc breaks STD using Intel 945

[Rafael J. Wysocki]

This message has been generated automatically as a part of a report
of recent regressions.

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


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12836
Subject		: 2.6.29-rc breaks STD using Intel 945
Submitter	: Rolf Eike Beer <eike-kernel-F+mm6HnICJmzQB+pC5nmwQ@public.gmane.org>
Date		: 2009-03-04 19:20 (34 days old)
References	: http://marc.info/?l=linux-kernel&m=123619451406192&w=4

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

[Rafael J. Wysocki]

This message has been generated automatically as a part of a report
of recent regressions.

The following bug entry is on the current list of known regressions
from 2.6.28.  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 <jkarlson-kf+aQKke1yb1KXRcyAk9cg@public.gmane.org>
Date		: 2009-03-12 12:06 (26 days old)

[Bug #12867] 2.6.29-rc7 broke r8169 MAC on Thecus n2100 ARM board

[Rafael J. Wysocki]

This message has been generated automatically as a part of a report
of recent regressions.

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


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12867
Subject		: 2.6.29-rc7 broke r8169 MAC on Thecus n2100 ARM board
Submitter	: Mikael Pettersson <mikpe-1zs4UD6AkMk@public.gmane.org>
Date		: 2009-03-09 20:29 (29 days old)
References	: http://marc.info/?l=linux-kernel&m=123663065403760&w=4
Handled-By	: Francois Romieu <romieu-W8zweXLXuWQS+FvcfC7Uqw@public.gmane.org>

[Bug #12871] usb bluetooth crashes system

[Rafael J. Wysocki]

This message has been generated automatically as a part of a report
of recent regressions.

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


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12871
Subject		: usb bluetooth crashes system
Submitter	: Pavel Machek <pavel@ucw.cz>
Date		: 2009-03-10 11:23 (28 days old)
References	: http://marc.info/?l=linux-kernel&m=123668450400940&w=4

[Bug #12871] usb bluetooth crashes system

[Rafael J. Wysocki]

This message has been generated automatically as a part of a report
of recent regressions.

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


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12871
Subject		: usb bluetooth crashes system
Submitter	: Pavel Machek <pavel-+ZI9xUNit7I@public.gmane.org>
Date		: 2009-03-10 11:23 (28 days old)
References	: http://marc.info/?l=linux-kernel&m=123668450400940&w=4

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

[Rafael J. Wysocki]

This message has been generated automatically as a part of a report
of recent regressions.

The following bug entry is on the current list of known regressions
from 2.6.28.  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 <helge.bahmann@secunet.com>
Date		: 2009-03-20 07:13 (18 days old)

[Bug #12908] acpi_ex_extract_from_field -- div by zero

[Rafael J. Wysocki]

This message has been generated automatically as a part of a report
of recent regressions.

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


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12908
Subject		: acpi_ex_extract_from_field -- div by zero
Submitter	: Jiri Slaby <jirislaby@gmail.com>
Date		: 2009-03-15 10:47 (23 days old)
References	: http://marc.info/?l=linux-kernel&m=123711408225013&w=4
Handled-By	: Lin Ming <ming.m.lin@intel.com>

[Bug #12872] pwc mmap always fails with EAGAIN

[Rafael J. Wysocki]

This message has been generated automatically as a part of a report
of recent regressions.

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


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12872
Subject		: pwc mmap always fails with EAGAIN
Submitter	: Markus <M4rkusXXL@web.de>
Date		: 2009-03-14 16:42 (24 days old)
References	: http://marc.info/?l=linux-kernel&m=123704902201378&w=4

[Bug #12908] acpi_ex_extract_from_field -- div by zero

[Rafael J. Wysocki]

This message has been generated automatically as a part of a report
of recent regressions.

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


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12908
Subject		: acpi_ex_extract_from_field -- div by zero
Submitter	: Jiri Slaby <jirislaby-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Date		: 2009-03-15 10:47 (23 days old)
References	: http://marc.info/?l=linux-kernel&m=123711408225013&w=4
Handled-By	: Lin Ming <ming.m.lin-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>

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

[Rafael J. Wysocki]

This message has been generated automatically as a part of a report
of recent regressions.

The following bug entry is on the current list of known regressions
from 2.6.28.  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 <helge.bahmann-opNxpl+3fjRBDgjK7y7TUQ@public.gmane.org>
Date		: 2009-03-20 07:13 (18 days old)

[Bug #12872] pwc mmap always fails with EAGAIN

[Rafael J. Wysocki]

This message has been generated automatically as a part of a report
of recent regressions.

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


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12872
Subject		: pwc mmap always fails with EAGAIN
Submitter	: Markus <M4rkusXXL-S0/GAf8tV78@public.gmane.org>
Date		: 2009-03-14 16:42 (24 days old)
References	: http://marc.info/?l=linux-kernel&m=123704902201378&w=4

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

[Rafael J. Wysocki]

This message has been generated automatically as a part of a report
of recent regressions.

The following bug entry is on the current list of known regressions
from 2.6.28.  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 <dobrev666@gmail.com>
Date		: 2009-03-29 18:02 (9 days old)

[Bug #12961] Kernel panics in early boot: IO-APIC + timer doesn't work

[Rafael J. Wysocki]

This message has been generated automatically as a part of a report
of recent regressions.

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


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12961
Subject		: Kernel panics in early boot: IO-APIC + timer doesn't work
Submitter	: Daniel Vetter <daniel@ffwll.ch>
Date		: 2009-03-28 19:00 (10 days old)
First-Bad-Commit: http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=8d6f0c8214928f7c5083dd54ecb69c5d615b516e

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

[Rafael J. Wysocki]

This message has been generated automatically as a part of a report
of recent regressions.

The following bug entry is on the current list of known regressions
from 2.6.28.  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 <cat@zip.com.au>
Date		: 2009-03-16 10:25 (22 days old)
References	: http://marc.info/?l=linux-kernel&m=123720083515950&w=4

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

[Rafael J. Wysocki]

This message has been generated automatically as a part of a report
of recent regressions.

The following bug entry is on the current list of known regressions
from 2.6.28.  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@xs4all.nl>
Date		: 2009-03-26 16:14 (12 days old)

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

[Rafael J. Wysocki]

This message has been generated automatically as a part of a report
of recent regressions.

The following bug entry is on the current list of known regressions
from 2.6.28.  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/wNWPw@public.gmane.org>
Date		: 2009-03-26 16:14 (12 days old)

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

[Rafael J. Wysocki]

This message has been generated automatically as a part of a report
of recent regressions.

The following bug entry is on the current list of known regressions
from 2.6.28.  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 <cat-LJ1TwQYPT6cQrrorzV6ljw@public.gmane.org>
Date		: 2009-03-16 10:25 (22 days old)
References	: http://marc.info/?l=linux-kernel&m=123720083515950&w=4

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

[Rafael J. Wysocki]

This message has been generated automatically as a part of a report
of recent regressions.

The following bug entry is on the current list of known regressions
from 2.6.28.  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 <dobrev666-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Date		: 2009-03-29 18:02 (9 days old)

[Bug #12961] Kernel panics in early boot: IO-APIC + timer doesn't work

[Rafael J. Wysocki]

This message has been generated automatically as a part of a report
of recent regressions.

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


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12961
Subject		: Kernel panics in early boot: IO-APIC + timer doesn't work
Submitter	: Daniel Vetter <daniel-/w4YWyX8dFk@public.gmane.org>
Date		: 2009-03-28 19:00 (10 days old)
First-Bad-Commit: http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=8d6f0c8214928f7c5083dd54ecb69c5d615b516e

[Bug #12975] ata2: lots of error messages, but OS still running well

[Rafael J. Wysocki]

This message has been generated automatically as a part of a report
of recent regressions.

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


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12975
Subject		: ata2:   lots of error messages, but OS still running well
Submitter	: Peter Teoh <htmldeveloper@gmail.com>
Date		: 2009-03-30 08:03 (8 days old)

[Bug #12980] lockup in X.org

[Rafael J. Wysocki]

This message has been generated automatically as a part of a report
of recent regressions.

The following bug entry is on the current list of known regressions
from 2.6.28.  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 <marcus@better.se>
Date		: 2009-03-31 08:58 (7 days old)

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

[Rafael J. Wysocki]

This message has been generated automatically as a part of a report
of recent regressions.

The following bug entry is on the current list of known regressions
from 2.6.28.  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	:  <optimusgd@gmail.com>
Date		: 2009-04-03 09:30 (4 days old)

[Bug #12980] lockup in X.org

[Rafael J. Wysocki]

This message has been generated automatically as a part of a report
of recent regressions.

The following bug entry is on the current list of known regressions
from 2.6.28.  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 <marcus-sJr3legBufCzQB+pC5nmwQ@public.gmane.org>
Date		: 2009-03-31 08:58 (7 days old)

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

[Rafael J. Wysocki]

This message has been generated automatically as a part of a report
of recent regressions.

The following bug entry is on the current list of known regressions
from 2.6.28.  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	:  <optimusgd-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Date		: 2009-04-03 09:30 (4 days old)

[Bug #12975] ata2: lots of error messages, but OS still running well

[Rafael J. Wysocki]

This message has been generated automatically as a part of a report
of recent regressions.

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


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12975
Subject		: ata2:   lots of error messages, but OS still running well
Submitter	: Peter Teoh <htmldeveloper-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Date		: 2009-03-30 08:03 (8 days old)

[Bug #13016] consistent oops from request_key in 2.6.29

[Rafael J. Wysocki]

This message has been generated automatically as a part of a report
of recent regressions.

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


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13016
Subject		: consistent oops from request_key in 2.6.29
Submitter	: Jeff Layton <jlayton@redhat.com>
Date		: 2009-03-31 12:45 (7 days old)
References	: http://marc.info/?l=linux-kernel&m=123850360107293&w=4
Handled-By	: David Howells <dhowells@redhat.com>
Patch		: http://marc.info/?l=linux-kernel&m=123852150806814&w=4

[Bug #13017] ATA bus errors on resume

[Rafael J. Wysocki]

This message has been generated automatically as a part of a report
of recent regressions.

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


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13017
Subject		: ATA bus errors on resume
Submitter	: Niel Lambrechts <niel.lambrechts@gmail.com>
Date		: 2009-03-25 5:19 (13 days old)
References	: http://marc.info/?l=linux-kernel&m=123795841615989&w=4
Handled-By	: Tejun Heo <htejun@gmail.com>

[Bug #13015] pppoe over ethernet

[Rafael J. Wysocki]

This message has been generated automatically as a part of a report
of recent regressions.

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


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13015
Subject		: pppoe over ethernet
Submitter	: Detlef Tschirschky <detlef.tschirschky@gmx.de>
Date		: 2009-03-25 21:28 (13 days old)
References	: http://marc.info/?l=linux-kernel&m=123801663105671&w=4

[Bug #13015] pppoe over ethernet

[Rafael J. Wysocki]

This message has been generated automatically as a part of a report
of recent regressions.

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


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13015
Subject		: pppoe over ethernet
Submitter	: Detlef Tschirschky <detlef.tschirschky-Mmb7MZpHnFY@public.gmane.org>
Date		: 2009-03-25 21:28 (13 days old)
References	: http://marc.info/?l=linux-kernel&m=123801663105671&w=4

[Bug #13017] ATA bus errors on resume

[Rafael J. Wysocki]

This message has been generated automatically as a part of a report
of recent regressions.

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


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13017
Subject		: ATA bus errors on resume
Submitter	: Niel Lambrechts <niel.lambrechts-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Date		: 2009-03-25 5:19 (13 days old)
References	: http://marc.info/?l=linux-kernel&m=123795841615989&w=4
Handled-By	: Tejun Heo <htejun-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>

[Bug #13016] consistent oops from request_key in 2.6.29

[Rafael J. Wysocki]

This message has been generated automatically as a part of a report
of recent regressions.

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


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13016
Subject		: consistent oops from request_key in 2.6.29
Submitter	: Jeff Layton <jlayton-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
Date		: 2009-03-31 12:45 (7 days old)
References	: http://marc.info/?l=linux-kernel&m=123850360107293&w=4
Handled-By	: David Howells <dhowells-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
Patch		: http://marc.info/?l=linux-kernel&m=123852150806814&w=4

[Bug #13026] cs5536 is broken

[Rafael J. Wysocki]

This message has been generated automatically as a part of a report
of recent regressions.

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


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13026
Subject		: cs5536 is broken
Submitter	: Arnd Hannemann <hannemann@nets.rwth-aachen.de>
Date		: 2009-04-06 18:11 (1 days old)
References	: http://marc.info/?l=linux-kernel&m=123904159829771&w=4
Handled-By	: Sergei Shtylyov <sshtylyov@ru.mvista.com>
Patch		: http://marc.info/?l=linux-kernel&m=123904273731477&w=4

[Bug #13019] /proc/<pid>/maps offset output broken in 2.6.29

[Rafael J. Wysocki]

This message has been generated automatically as a part of a report
of recent regressions.

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


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13019
Subject		: /proc/<pid>/maps offset output broken in 2.6.29
Submitter	: "Chris Friesen" <cfriesen@nortel.com>
Date		: 2009-04-01 23:18 (6 days old)
References	: http://marc.info/?l=linuxppc-embedded&m=123862902916059&w=4
Handled-By	: Hugh Dickins <hugh@veritas.com>

[Bug #13026] cs5536 is broken

[Rafael J. Wysocki]

This message has been generated automatically as a part of a report
of recent regressions.

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


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13026
Subject		: cs5536 is broken
Submitter	: Arnd Hannemann <hannemann-JasiFyN5vQG662+jY7v6MhvVK+yQ3ZXh@public.gmane.org>
Date		: 2009-04-06 18:11 (1 days old)
References	: http://marc.info/?l=linux-kernel&m=123904159829771&w=4
Handled-By	: Sergei Shtylyov <sshtylyov-hkdhdckH98+B+jHODAdFcQ@public.gmane.org>
Patch		: http://marc.info/?l=linux-kernel&m=123904273731477&w=4

[Bug #13019] /proc/<pid>/maps offset output broken in 2.6.29

[Rafael J. Wysocki]

This message has been generated automatically as a part of a report
of recent regressions.

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


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13019
Subject		: /proc/<pid>/maps offset output broken in 2.6.29
Submitter	: "Chris Friesen" <cfriesen-ZIRUuHA3oDzQT0dZR+AlfA@public.gmane.org>
Date		: 2009-04-01 23:18 (6 days old)
References	: http://marc.info/?l=linuxppc-embedded&m=123862902916059&w=4
Handled-By	: Hugh Dickins <hugh-DTz5qymZ9yRBDgjK7y7TUQ@public.gmane.org>

Re: 2.6.29-git13: Reported regressions from 2.6.28

[Linus Torvalds]

On Mon, 6 Apr 2009, Rafael J. Wysocki wrote:
> 
> Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13019
> Subject		: /proc/<pid>/maps offset output broken in 2.6.29
> Submitter	: "Chris Friesen" <cfriesen@nortel.com>
> Date		: 2009-04-01 23:18 (6 days old)
> References	: http://marc.info/?l=linuxppc-embedded&m=123862902916059&w=4
> Handled-By	: Hugh Dickins <hugh@veritas.com>

I don't think that's a regression, nor really a bug. It looks cosmetic, 
and likely to be fixed, but not really worth worrying about.

> Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13018
> Subject		: 2.6.29 on MacBook 2,1 fails to reboot
> Submitter	: Trenton Adams <trenton.d.adams@gmail.com>
> Date		: 2009-03-30 2:04 (8 days old)
> References	: http://marc.info/?l=linux-kernel&m=123837870307249&w=4
> Handled-By	: "Morten P.D. Stevens" <mstevens@win-professional.com>

This went through bisection, but looking at the email log, I tend to 
suspect that maybe Trenton marked some versions good even though they 
weren't (because they got versions numbers from v2.6.27), and didn't 
realize that that messes up bisection in a big way.

The bug _sounds_ like some deadlock due to lock problems - the shutdown 
path often triggers locks that no other path really cares about. And we 
had some lock problems in the sound subsystem that got fixed post-2.6.28, 
for example. 

And it looks like the problem is somewhere in sound shutdown:

12181 delete_module("snd_hda_codec", O_RDONLY|O_EXCL) = -1 EAGAIN (Resource temporarily unavailable) <0.000011>

So commits like 91054598f794fb5d8a0b1e747ff8e2e8fc2115b3 ("ALSA: pcm_oss, 
fix locking typo") might explain it.

		Linus

Re: 2.6.29-git13: Reported regressions from 2.6.28

[Linus Torvalds]

On Mon, 6 Apr 2009, Rafael J. Wysocki wrote:
> 
> Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13019
> Subject		: /proc/<pid>/maps offset output broken in 2.6.29
> Submitter	: "Chris Friesen" <cfriesen@nortel.com>
> Date		: 2009-04-01 23:18 (6 days old)
> References	: http://marc.info/?l=linuxppc-embedded&m=123862902916059&w=4
> Handled-By	: Hugh Dickins <hugh@veritas.com>

I don't think that's a regression, nor really a bug. It looks cosmetic, 
and likely to be fixed, but not really worth worrying about.

> Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13018
> Subject		: 2.6.29 on MacBook 2,1 fails to reboot
> Submitter	: Trenton Adams <trenton.d.adams@gmail.com>
> Date		: 2009-03-30 2:04 (8 days old)
> References	: http://marc.info/?l=linux-kernel&m=123837870307249&w=4
> Handled-By	: "Morten P.D. Stevens" <mstevens@win-professional.com>

This went through bisection, but looking at the email log, I tend to 
suspect that maybe Trenton marked some versions good even though they 
weren't (because they got versions numbers from v2.6.27), and didn't 
realize that that messes up bisection in a big way.

The bug _sounds_ like some deadlock due to lock problems - the shutdown 
path often triggers locks that no other path really cares about. And we 
had some lock problems in the sound subsystem that got fixed post-2.6.28, 
for example. 

And it looks like the problem is somewhere in sound shutdown:

12181 delete_module("snd_hda_codec", O_RDONLY|O_EXCL) = -1 EAGAIN (Resource temporarily unavailable) <0.000011>

So commits like 91054598f794fb5d8a0b1e747ff8e2e8fc2115b3 ("ALSA: pcm_oss, 
fix locking typo") might explain it.

		Linus

Re: [Bug #12809] iozone regression with 2.6.29-rc6

[Linus Torvalds]

On Mon, 6 Apr 2009, Rafael J. Wysocki wrote:
>
> This message has been generated automatically as a part of a report
> of recent regressions.
> 
> The following bug entry is on the current list of known regressions
> from 2.6.28.  Please verify if it still should be listed and let me know
> (either way).
> 
> Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12809

Hmm. I applied the commit that should fix it, but I applied it _after_ 
2.6.29. I was too scared to apply it late in the -rc and quite frankly 
I'm not sure we should necessarily back-port it.

So I'm hoping that we can close it as "fixed", even though 2.6.29 will 
have that particular regression - for those particular machines. It is, 
after all, just a "where do we draw the line" kind of issue.

But I won't close it myself, and I leave it to others to argue whether it 
really maybe should be back-ported after all.

			Linus

Re: [Bug #12809] iozone regression with 2.6.29-rc6

[Linus Torvalds]

On Mon, 6 Apr 2009, Rafael J. Wysocki wrote:
>
> This message has been generated automatically as a part of a report
> of recent regressions.
> 
> The following bug entry is on the current list of known regressions
> from 2.6.28.  Please verify if it still should be listed and let me know
> (either way).
> 
> Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12809

Hmm. I applied the commit that should fix it, but I applied it _after_ 
2.6.29. I was too scared to apply it late in the -rc and quite frankly 
I'm not sure we should necessarily back-port it.

So I'm hoping that we can close it as "fixed", even though 2.6.29 will 
have that particular regression - for those particular machines. It is, 
after all, just a "where do we draw the line" kind of issue.

But I won't close it myself, and I leave it to others to argue whether it 
really maybe should be back-ported after all.

			Linus

Re: [Bug #12809] iozone regression with 2.6.29-rc6

[Wu Fengguang]

On Tue, Apr 07, 2009 at 03:05:38AM +0800, Rafael J. Wysocki wrote:
> This message has been generated automatically as a part of a report
> of recent regressions.
> 
> The following bug entry is on the current list of known regressions
> from 2.6.28.  Please verify if it still should be listed and let me know
> (either way).
> 
> 
> Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12809
> Subject		: iozone regression with 2.6.29-rc6
> Submitter	: Lin Ming <ming.m.lin@intel.com>
> Date		: 2009-02-27 9:13 (39 days old)
> First-Bad-Commit: http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=1cf6e7d83bf334cc5916137862c920a97aabc018
> References	: http://marc.info/?l=linux-kernel&m=123572630504360&w=4
> 		  http://lkml.org/lkml/2009/3/14/265
> Handled-By	: Wu Fengguang <fengguang.wu@intel.com>
> 

This bug could be closed.

The performance regression is triggered by commit 1cf6e7d83bf3(mm:
task dirty accounting fix). Which has been reverted in 2.6.29.

For 2.6.30, commit 1cf6e7d83bf33(mm: task dirty accounting fix) and
1b5e62b42b55(writeback: double the dirty thresholds) were just merged
together. The latter one restores the iozone performance. (However
might deteriorate some writeback slowness bugs..)

Thanks,
Fengguang

Re: [Bug #12809] iozone regression with 2.6.29-rc6

[Wu Fengguang]

On Tue, Apr 07, 2009 at 03:05:38AM +0800, Rafael J. Wysocki wrote:
> This message has been generated automatically as a part of a report
> of recent regressions.
> 
> The following bug entry is on the current list of known regressions
> from 2.6.28.  Please verify if it still should be listed and let me know
> (either way).
> 
> 
> Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12809
> Subject		: iozone regression with 2.6.29-rc6
> Submitter	: Lin Ming <ming.m.lin-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
> Date		: 2009-02-27 9:13 (39 days old)
> First-Bad-Commit: http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=1cf6e7d83bf334cc5916137862c920a97aabc018
> References	: http://marc.info/?l=linux-kernel&m=123572630504360&w=4
> 		  http://lkml.org/lkml/2009/3/14/265
> Handled-By	: Wu Fengguang <fengguang.wu-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
> 

This bug could be closed.

The performance regression is triggered by commit 1cf6e7d83bf3(mm:
task dirty accounting fix). Which has been reverted in 2.6.29.

For 2.6.30, commit 1cf6e7d83bf33(mm: task dirty accounting fix) and
1b5e62b42b55(writeback: double the dirty thresholds) were just merged
together. The latter one restores the iozone performance. (However
might deteriorate some writeback slowness bugs..)

Thanks,
Fengguang

Re: [Bug #12809] iozone regression with 2.6.29-rc6

[Wu Fengguang]

On Tue, Apr 07, 2009 at 06:15:09AM +0800, Wu Fengguang wrote:
> On Tue, Apr 07, 2009 at 03:05:38AM +0800, Rafael J. Wysocki wrote:
> > This message has been generated automatically as a part of a report
> > of recent regressions.
> > 
> > The following bug entry is on the current list of known regressions
> > from 2.6.28.  Please verify if it still should be listed and let me know
> > (either way).
> > 
> > 
> > Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12809
> > Subject		: iozone regression with 2.6.29-rc6
> > Submitter	: Lin Ming <ming.m.lin@intel.com>
> > Date		: 2009-02-27 9:13 (39 days old)
> > First-Bad-Commit: http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=1cf6e7d83bf334cc5916137862c920a97aabc018
> > References	: http://marc.info/?l=linux-kernel&m=123572630504360&w=4
> > 		  http://lkml.org/lkml/2009/3/14/265
> > Handled-By	: Wu Fengguang <fengguang.wu@intel.com>
> > 
> 
> This bug could be closed.
> 
> The performance regression is triggered by commit 1cf6e7d83bf3(mm:
> task dirty accounting fix). Which has been reverted in 2.6.29.

Sorry for the mistake, commit 1cf6e7d83bf3 was _not_ reverted.
So 2.6.29 is expected to have this regression.. 

Thanks,
Fengguang

> For 2.6.30, commit 1cf6e7d83bf33(mm: task dirty accounting fix) and
> 1b5e62b42b55(writeback: double the dirty thresholds) were just merged
> together. The latter one restores the iozone performance. (However
> might deteriorate some writeback slowness bugs..)
> 
> Thanks,
> Fengguang
> 

Re: [Bug #12809] iozone regression with 2.6.29-rc6

[Wu Fengguang]

On Tue, Apr 07, 2009 at 06:15:09AM +0800, Wu Fengguang wrote:
> On Tue, Apr 07, 2009 at 03:05:38AM +0800, Rafael J. Wysocki wrote:
> > This message has been generated automatically as a part of a report
> > of recent regressions.
> > 
> > The following bug entry is on the current list of known regressions
> > from 2.6.28.  Please verify if it still should be listed and let me know
> > (either way).
> > 
> > 
> > Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12809
> > Subject		: iozone regression with 2.6.29-rc6
> > Submitter	: Lin Ming <ming.m.lin-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
> > Date		: 2009-02-27 9:13 (39 days old)
> > First-Bad-Commit: http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=1cf6e7d83bf334cc5916137862c920a97aabc018
> > References	: http://marc.info/?l=linux-kernel&m=123572630504360&w=4
> > 		  http://lkml.org/lkml/2009/3/14/265
> > Handled-By	: Wu Fengguang <fengguang.wu-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
> > 
> 
> This bug could be closed.
> 
> The performance regression is triggered by commit 1cf6e7d83bf3(mm:
> task dirty accounting fix). Which has been reverted in 2.6.29.

Sorry for the mistake, commit 1cf6e7d83bf3 was _not_ reverted.
So 2.6.29 is expected to have this regression.. 

Thanks,
Fengguang

> For 2.6.30, commit 1cf6e7d83bf33(mm: task dirty accounting fix) and
> 1b5e62b42b55(writeback: double the dirty thresholds) were just merged
> together. The latter one restores the iozone performance. (However
> might deteriorate some writeback slowness bugs..)
> 
> Thanks,
> Fengguang
> 

Re: [Bug #12809] iozone regression with 2.6.29-rc6

[Rafael J. Wysocki]

On Tuesday 07 April 2009, Wu Fengguang wrote:
> On Tue, Apr 07, 2009 at 06:15:09AM +0800, Wu Fengguang wrote:
> > On Tue, Apr 07, 2009 at 03:05:38AM +0800, Rafael J. Wysocki wrote:
> > > This message has been generated automatically as a part of a report
> > > of recent regressions.
> > > 
> > > The following bug entry is on the current list of known regressions
> > > from 2.6.28.  Please verify if it still should be listed and let me know
> > > (either way).
> > > 
> > > 
> > > Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12809
> > > Subject		: iozone regression with 2.6.29-rc6
> > > Submitter	: Lin Ming <ming.m.lin@intel.com>
> > > Date		: 2009-02-27 9:13 (39 days old)
> > > First-Bad-Commit: http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=1cf6e7d83bf334cc5916137862c920a97aabc018
> > > References	: http://marc.info/?l=linux-kernel&m=123572630504360&w=4
> > > 		  http://lkml.org/lkml/2009/3/14/265
> > > Handled-By	: Wu Fengguang <fengguang.wu@intel.com>
> > > 
> > 
> > This bug could be closed.
> > 
> > The performance regression is triggered by commit 1cf6e7d83bf3(mm:
> > task dirty accounting fix). Which has been reverted in 2.6.29.
> 
> Sorry for the mistake, commit 1cf6e7d83bf3 was _not_ reverted.
> So 2.6.29 is expected to have this regression.. 

Added -stable to the CC list.  I'm not sure if that was included into .29.1.

> > For 2.6.30, commit 1cf6e7d83bf33(mm: task dirty accounting fix) and
> > 1b5e62b42b55(writeback: double the dirty thresholds) were just merged
> > together. The latter one restores the iozone performance. (However
> > might deteriorate some writeback slowness bugs..)

Thanks, I've closed the bug.

Rafael

Re: [Bug #12809] iozone regression with 2.6.29-rc6

[Rafael J. Wysocki]

On Tuesday 07 April 2009, Wu Fengguang wrote:
> On Tue, Apr 07, 2009 at 06:15:09AM +0800, Wu Fengguang wrote:
> > On Tue, Apr 07, 2009 at 03:05:38AM +0800, Rafael J. Wysocki wrote:
> > > This message has been generated automatically as a part of a report
> > > of recent regressions.
> > > 
> > > The following bug entry is on the current list of known regressions
> > > from 2.6.28.  Please verify if it still should be listed and let me know
> > > (either way).
> > > 
> > > 
> > > Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12809
> > > Subject		: iozone regression with 2.6.29-rc6
> > > Submitter	: Lin Ming <ming.m.lin-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
> > > Date		: 2009-02-27 9:13 (39 days old)
> > > First-Bad-Commit: http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=1cf6e7d83bf334cc5916137862c920a97aabc018
> > > References	: http://marc.info/?l=linux-kernel&m=123572630504360&w=4
> > > 		  http://lkml.org/lkml/2009/3/14/265
> > > Handled-By	: Wu Fengguang <fengguang.wu-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
> > > 
> > 
> > This bug could be closed.
> > 
> > The performance regression is triggered by commit 1cf6e7d83bf3(mm:
> > task dirty accounting fix). Which has been reverted in 2.6.29.
> 
> Sorry for the mistake, commit 1cf6e7d83bf3 was _not_ reverted.
> So 2.6.29 is expected to have this regression.. 

Added -stable to the CC list.  I'm not sure if that was included into .29.1.

> > For 2.6.30, commit 1cf6e7d83bf33(mm: task dirty accounting fix) and
> > 1b5e62b42b55(writeback: double the dirty thresholds) were just merged
> > together. The latter one restores the iozone performance. (However
> > might deteriorate some writeback slowness bugs..)

Thanks, I've closed the bug.

Rafael

Re: 2.6.29-git13: Reported regressions from 2.6.28

[Rafael J. Wysocki]

On Monday 06 April 2009, Linus Torvalds wrote:
> 
> On Mon, 6 Apr 2009, Rafael J. Wysocki wrote:
> > 
> > Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13019
> > Subject		: /proc/<pid>/maps offset output broken in 2.6.29
> > Submitter	: "Chris Friesen" <cfriesen@nortel.com>
> > Date		: 2009-04-01 23:18 (6 days old)
> > References	: http://marc.info/?l=linuxppc-embedded&m=123862902916059&w=4
> > Handled-By	: Hugh Dickins <hugh@veritas.com>
> 
> I don't think that's a regression, nor really a bug. It looks cosmetic, 
> and likely to be fixed, but not really worth worrying about.

OK, I've dropped it from the list.

Thanks,
Rafael

Re: 2.6.29-git13: Reported regressions from 2.6.28

[Rafael J. Wysocki]

On Monday 06 April 2009, Linus Torvalds wrote:
> 
> On Mon, 6 Apr 2009, Rafael J. Wysocki wrote:
> > 
> > Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13019
> > Subject		: /proc/<pid>/maps offset output broken in 2.6.29
> > Submitter	: "Chris Friesen" <cfriesen@nortel.com>
> > Date		: 2009-04-01 23:18 (6 days old)
> > References	: http://marc.info/?l=linuxppc-embedded&m=123862902916059&w=4
> > Handled-By	: Hugh Dickins <hugh@veritas.com>
> 
> I don't think that's a regression, nor really a bug. It looks cosmetic, 
> and likely to be fixed, but not really worth worrying about.

OK, I've dropped it from the list.

Thanks,
Rafael

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

[CaT]

On Mon, Apr 06, 2009 at 09:05:41PM +0200, Rafael J. Wysocki wrote:
> Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12909
> Subject		: boot/kernel init duration regression from 2.6.28
> Submitter	: CaT <cat@zip.com.au>
> Date		: 2009-03-16 10:25 (22 days old)
> References	: http://marc.info/?l=linux-kernel&m=123720083515950&w=4

I got it tracked down to .29-rc1. I guess I'll need to learn to use git
now (and user the desktop - compiling on the EEE takes /ages/). Also have
.29.1 ready to test when I get home tonight.

-- 
  "A search of his car uncovered pornography, a homemade sex aid, women's 
  stockings and a Jack Russell terrier."
    - http://www.news.com.au/story/0%2C27574%2C24675808-421%2C00.html

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

[CaT]

On Mon, Apr 06, 2009 at 09:05:41PM +0200, Rafael J. Wysocki wrote:
> Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12909
> Subject		: boot/kernel init duration regression from 2.6.28
> Submitter	: CaT <cat-LJ1TwQYPT6cQrrorzV6ljw@public.gmane.org>
> Date		: 2009-03-16 10:25 (22 days old)
> References	: http://marc.info/?l=linux-kernel&m=123720083515950&w=4

I got it tracked down to .29-rc1. I guess I'll need to learn to use git
now (and user the desktop - compiling on the EEE takes /ages/). Also have
.29.1 ready to test when I get home tonight.

-- 
  "A search of his car uncovered pornography, a homemade sex aid, women's 
  stockings and a Jack Russell terrier."
    - http://www.news.com.au/story/0%2C27574%2C24675808-421%2C00.html

Re: [Bug #12870] 2.6.29-rc "TKIP: replay detected" regression

[Hugh Dickins]

On Mon, 6 Apr 2009, Rafael J. Wysocki wrote:
> 
> Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12870
> Subject		: 2.6.29-rc "TKIP: replay detected" regression
> Submitter	: Hugh Dickins <hugh@veritas.com>
> Date		: 2009-03-11 12:07 (27 days old)
> References	: http://marc.info/?l=linux-kernel&m=123677337219148&w=4
> Handled-By	: "John W. Linville" <linville@tuxdriver.com>
> Patch		: http://marc.info/?l=linux-wireless&m=123678463704691&w=2

John's fix went into 2.6.29 final: please remove this regression now.

Hugh

Re: [Bug #12870] 2.6.29-rc "TKIP: replay detected" regression

[Hugh Dickins]

On Mon, 6 Apr 2009, Rafael J. Wysocki wrote:
> 
> Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12870
> Subject		: 2.6.29-rc "TKIP: replay detected" regression
> Submitter	: Hugh Dickins <hugh-DTz5qymZ9yRBDgjK7y7TUQ@public.gmane.org>
> Date		: 2009-03-11 12:07 (27 days old)
> References	: http://marc.info/?l=linux-kernel&m=123677337219148&w=4
> Handled-By	: "John W. Linville" <linville-2XuSBdqkA4R54TAoqtyWWQ@public.gmane.org>
> Patch		: http://marc.info/?l=linux-wireless&m=123678463704691&w=2

John's fix went into 2.6.29 final: please remove this regression now.

Hugh

Re: [Bug #13019] /proc/<pid>/maps offset output broken in 2.6.29

[Hugh Dickins]

On Mon, 6 Apr 2009, Rafael J. Wysocki wrote:
> 
> Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13019
> Subject		: /proc/<pid>/maps offset output broken in 2.6.29
> Submitter	: "Chris Friesen" <cfriesen@nortel.com>
> Date		: 2009-04-01 23:18 (6 days old)
> References	: http://marc.info/?l=linuxppc-embedded&m=123862902916059&w=4
> Handled-By	: Hugh Dickins <hugh@veritas.com>

No, this shouldn't be listed as a regression from 2.6.28: if it's to be
counted as a regression at all, it's 2.6.23's regression from 2.6.22.
(We're about to deal with it in 2.6.30, but hardly worth backporting.)

Hugh

Re: [Bug #13019] /proc/<pid>/maps offset output broken in 2.6.29

[Hugh Dickins]

On Mon, 6 Apr 2009, Rafael J. Wysocki wrote:
> 
> Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13019
> Subject		: /proc/<pid>/maps offset output broken in 2.6.29
> Submitter	: "Chris Friesen" <cfriesen-ZIRUuHA3oDzQT0dZR+AlfA@public.gmane.org>
> Date		: 2009-04-01 23:18 (6 days old)
> References	: http://marc.info/?l=linuxppc-embedded&m=123862902916059&w=4
> Handled-By	: Hugh Dickins <hugh-DTz5qymZ9yRBDgjK7y7TUQ@public.gmane.org>

No, this shouldn't be listed as a regression from 2.6.28: if it's to be
counted as a regression at all, it's 2.6.23's regression from 2.6.22.
(We're about to deal with it in 2.6.30, but hardly worth backporting.)

Hugh

Re: [stable] [Bug #12809] iozone regression with 2.6.29-rc6

[Chris Wright]

* Rafael J. Wysocki (rjw@sisk.pl) wrote:
> On Tuesday 07 April 2009, Wu Fengguang wrote:
> > On Tue, Apr 07, 2009 at 06:15:09AM +0800, Wu Fengguang wrote:
> > > On Tue, Apr 07, 2009 at 03:05:38AM +0800, Rafael J. Wysocki wrote:
> > > > Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12809
> > > > Subject		: iozone regression with 2.6.29-rc6
> > > > Submitter	: Lin Ming <ming.m.lin@intel.com>
> > > > Date		: 2009-02-27 9:13 (39 days old)
> > > > First-Bad-Commit: http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=1cf6e7d83bf334cc5916137862c920a97aabc018
> > > > References	: http://marc.info/?l=linux-kernel&m=123572630504360&w=4
> > > > 		  http://lkml.org/lkml/2009/3/14/265
> > > > Handled-By	: Wu Fengguang <fengguang.wu@intel.com>
> > > 
> > > This bug could be closed.
> > > 
> > > The performance regression is triggered by commit 1cf6e7d83bf3(mm:
> > > task dirty accounting fix). Which has been reverted in 2.6.29.
> > 
> > Sorry for the mistake, commit 1cf6e7d83bf3 was _not_ reverted.
> > So 2.6.29 is expected to have this regression.. 
> 
> Added -stable to the CC list.  I'm not sure if that was included into .29.1.

1cf6e7d83bf3 is part of 2.6.29.1 (came in 2.6.29-rc6)

> > > For 2.6.30, commit 1cf6e7d83bf33(mm: task dirty accounting fix) and
> > > 1b5e62b42b55(writeback: double the dirty thresholds) were just merged
> > > together. The latter one restores the iozone performance. (However
> > > might deteriorate some writeback slowness bugs..)

1b5e62b42b55 is not in -stable.

thanks,
-chris

Re: [stable] [Bug #12809] iozone regression with 2.6.29-rc6

[Chris Wright]

* Rafael J. Wysocki (rjw-KKrjLPT3xs0@public.gmane.org) wrote:
> On Tuesday 07 April 2009, Wu Fengguang wrote:
> > On Tue, Apr 07, 2009 at 06:15:09AM +0800, Wu Fengguang wrote:
> > > On Tue, Apr 07, 2009 at 03:05:38AM +0800, Rafael J. Wysocki wrote:
> > > > Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12809
> > > > Subject		: iozone regression with 2.6.29-rc6
> > > > Submitter	: Lin Ming <ming.m.lin-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
> > > > Date		: 2009-02-27 9:13 (39 days old)
> > > > First-Bad-Commit: http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=1cf6e7d83bf334cc5916137862c920a97aabc018
> > > > References	: http://marc.info/?l=linux-kernel&m=123572630504360&w=4
> > > > 		  http://lkml.org/lkml/2009/3/14/265
> > > > Handled-By	: Wu Fengguang <fengguang.wu-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
> > > 
> > > This bug could be closed.
> > > 
> > > The performance regression is triggered by commit 1cf6e7d83bf3(mm:
> > > task dirty accounting fix). Which has been reverted in 2.6.29.
> > 
> > Sorry for the mistake, commit 1cf6e7d83bf3 was _not_ reverted.
> > So 2.6.29 is expected to have this regression.. 
> 
> Added -stable to the CC list.  I'm not sure if that was included into .29.1.

1cf6e7d83bf3 is part of 2.6.29.1 (came in 2.6.29-rc6)

> > > For 2.6.30, commit 1cf6e7d83bf33(mm: task dirty accounting fix) and
> > > 1b5e62b42b55(writeback: double the dirty thresholds) were just merged
> > > together. The latter one restores the iozone performance. (However
> > > might deteriorate some writeback slowness bugs..)

1b5e62b42b55 is not in -stable.

thanks,
-chris

Re: [Bug #13018] 2.6.29 on MacBook 2,1 fails to reboot

[Trenton D. Adams]

Hi Rafael,

Yes, it is still a problem.  I have identified it as far down to being
an alsa problem.  Please follow the other thread related to this.  I
posted some more recent data, with strace info and such.  I also used
git bisect to narrow it down.  I wasn't, however, able to understand
what was happening exactly in the code.

If you need more info, or want me to try something, please just let me know.

Thanks.

On Mon, Apr 6, 2009 at 1:05 PM, Rafael J. Wysocki <rjw@sisk.pl> wrote:
> This message has been generated automatically as a part of a report
> of recent regressions.
>
> The following bug entry is on the current list of known regressions
> from 2.6.28.  Please verify if it still should be listed and let me know
> (either way).
>
>
> Bug-Entry       : http://bugzilla.kernel.org/show_bug.cgi?id=13018
> Subject         : 2.6.29 on MacBook 2,1 fails to reboot
> Submitter       : Trenton Adams <trenton.d.adams@gmail.com>
> Date            : 2009-03-30 2:04 (8 days old)
> References      : http://marc.info/?l=linux-kernel&m=123837870307249&w=4
> Handled-By      : "Morten P.D. Stevens" <mstevens@win-professional.com>
>
>
>

Re: [Bug #13018] 2.6.29 on MacBook 2,1 fails to reboot

[Trenton D. Adams]

Hi Rafael,

Yes, it is still a problem.  I have identified it as far down to being
an alsa problem.  Please follow the other thread related to this.  I
posted some more recent data, with strace info and such.  I also used
git bisect to narrow it down.  I wasn't, however, able to understand
what was happening exactly in the code.

If you need more info, or want me to try something, please just let me know.

Thanks.

On Mon, Apr 6, 2009 at 1:05 PM, Rafael J. Wysocki <rjw-KKrjLPT3xs0@public.gmane.org> wrote:
> This message has been generated automatically as a part of a report
> of recent regressions.
>
> The following bug entry is on the current list of known regressions
> from 2.6.28.  Please verify if it still should be listed and let me know
> (either way).
>
>
> Bug-Entry       : http://bugzilla.kernel.org/show_bug.cgi?id=13018
> Subject         : 2.6.29 on MacBook 2,1 fails to reboot
> Submitter       : Trenton Adams <trenton.d.adams-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
> Date            : 2009-03-30 2:04 (8 days old)
> References      : http://marc.info/?l=linux-kernel&m=123837870307249&w=4
> Handled-By      : "Morten P.D. Stevens" <mstevens@win-professional.com>
>
>
>

Re: [Bug #13018] 2.6.29 on MacBook 2,1 fails to reboot

[Trenton D. Adams]

On Mon, Apr 6, 2009 at 8:13 PM, Trenton D. Adams
<trenton.d.adams@gmail.com> wrote:
> Hi Rafael,
>
> Yes, it is still a problem.  I have identified it as far down to being
> an alsa problem.  Please follow the other thread related to this.  I

Oops, sorry, I should make clear that it is not an alsa problem
specifically, but an alsa hda-intel driver issue, which is related to
alsa.

Re: [Bug #13018] 2.6.29 on MacBook 2,1 fails to reboot

[Trenton D. Adams]

On Mon, Apr 6, 2009 at 8:13 PM, Trenton D. Adams
<trenton.d.adams-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:
> Hi Rafael,
>
> Yes, it is still a problem.  I have identified it as far down to being
> an alsa problem.  Please follow the other thread related to this.  I

Oops, sorry, I should make clear that it is not an alsa problem
specifically, but an alsa hda-intel driver issue, which is related to
alsa.

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

[Bob Copeland]

On Mon, Apr 06, 2009 at 08:55:05PM +0200, Rafael J. Wysocki wrote:
> 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" <rathamahata@gmail.com>
> Date		: 2009-01-12 7:38 (85 days old)
> References	: http://marc.info/?l=linux-kernel&m=123174591509586&w=4
> Handled-By	: Bob Copeland <me@bobcopeland.com>

I must admit I still don't have an idea of the root cause on this
one.  It still looks like some kind of memory corruption to me, 
but no smoking gun so far.  The one patch in 2.6.30 that might have 
fixed it in the driver didn't help.

Anyway here's a patch to buy some time.  Johannes, would this be
an acceptable band-aid for now?

Sergey, can you test this patch?  It doesn't fix anything but hopefully
makes your system survive the bug.  I gave it a quick test by forcing
one of the rate indexes to a bad value.

From: Bob Copeland <me@bobcopeland.com>
Date: Mon, 6 Apr 2009 22:04:09 -0400
Subject: [PATCH] mac80211: be more resilient in the face of bad rate indexes

If for whatever reason the rate tables contain invalid rates,
ieee80211_get_tx_rate will warn and return NULL, causing some
drivers to crash.  Those that don't will subsequently hit a
BUG_ON() in rate.c.  Instead, return a valid rate structure from
ieee80211_get_tx_rate() and only WARN() in rate_control_get_rate().

Signed-off-by: Bob Copeland <me@bobcopeland.com>
---
 include/net/mac80211.h |   12 +++++++++---
 net/mac80211/rate.c    |    2 +-
 2 files changed, 10 insertions(+), 4 deletions(-)

diff --git a/include/net/mac80211.h b/include/net/mac80211.h
index 3b83a80..4a74f40 100644
--- a/include/net/mac80211.h
+++ b/include/net/mac80211.h
@@ -1014,13 +1014,19 @@ static inline void SET_IEEE80211_PERM_ADDR(struct ieee80211_hw *hw, u8 *addr)
 	memcpy(hw->wiphy->perm_addr, addr, ETH_ALEN);
 }
 
+static inline s8
+rate_lowest_index(struct ieee80211_supported_band *sband,
+		  struct ieee80211_sta *sta);
+
 static inline struct ieee80211_rate *
 ieee80211_get_tx_rate(const struct ieee80211_hw *hw,
 		      const struct ieee80211_tx_info *c)
 {
-	if (WARN_ON(c->control.rates[0].idx < 0))
-		return NULL;
-	return &hw->wiphy->bands[c->band]->bitrates[c->control.rates[0].idx];
+	s8 idx = c->control.rates[0].idx;
+	if (WARN_ON(idx < 0))
+		idx = rate_lowest_index(hw->wiphy->bands[c->band],
+					c->control.sta);
+	return &hw->wiphy->bands[c->band]->bitrates[idx];
 }
 
 static inline struct ieee80211_rate *
diff --git a/net/mac80211/rate.c b/net/mac80211/rate.c
index 4641f00..d8a5d46 100644
--- a/net/mac80211/rate.c
+++ b/net/mac80211/rate.c
@@ -238,7 +238,7 @@ void rate_control_get_rate(struct ieee80211_sub_if_data *sdata,
 				      sdata->max_ratectrl_rateidx);
 	}
 
-	BUG_ON(info->control.rates[0].idx < 0);
+	WARN_ON(info->control.rates[0].idx < 0);
 }
 
 struct rate_control_ref *rate_control_get(struct rate_control_ref *ref)
-- 
1.6.0.6




-- 
Bob Copeland %% www.bobcopeland.com

Re: [Bug #13015] pppoe over ethernet

[Cyrill Gorcunov]

On 4/6/09, Rafael J. Wysocki <rjw@sisk.pl> wrote:
> This message has been generated automatically as a part of a report
> of recent regressions.
>
> The following bug entry is on the current list of known regressions
> from 2.6.28.  Please verify if it still should be listed and let me know
> (either way).
>
>
> Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13015
> Subject		: pppoe over ethernet
> Submitter	: Detlef Tschirschky <detlef.tschirschky@gmx.de>
> Date		: 2009-03-25 21:28 (13 days old)
> References	: http://marc.info/?l=linux-kernel&m=123801663105671&w=4
>
>
>
I expect the issue is inspered by network problem found in plain
2.6.29. Detlef could you confirm the problem is still active in
2.6.29.1 or in current -git mainline?

Re: [Bug #13015] pppoe over ethernet

[Cyrill Gorcunov]

On 4/6/09, Rafael J. Wysocki <rjw-KKrjLPT3xs0@public.gmane.org> wrote:
> This message has been generated automatically as a part of a report
> of recent regressions.
>
> The following bug entry is on the current list of known regressions
> from 2.6.28.  Please verify if it still should be listed and let me know
> (either way).
>
>
> Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13015
> Subject		: pppoe over ethernet
> Submitter	: Detlef Tschirschky <detlef.tschirschky-Mmb7MZpHnFY@public.gmane.org>
> Date		: 2009-03-25 21:28 (13 days old)
> References	: http://marc.info/?l=linux-kernel&m=123801663105671&w=4
>
>
>
I expect the issue is inspered by network problem found in plain
2.6.29. Detlef could you confirm the problem is still active in
2.6.29.1 or in current -git mainline?

Re: 2.6.29-git13: Reported regressions from 2.6.28

[Trenton D. Adams]

On Mon, Apr 6, 2009 at 3:53 PM, Linus Torvalds
<torvalds@linux-foundation.org> wrote:
>
>
> On Mon, 6 Apr 2009, Rafael J. Wysocki wrote:
>>
>> Bug-Entry     : http://bugzilla.kernel.org/show_bug.cgi?id=13018
>> Subject               : 2.6.29 on MacBook 2,1 fails to reboot
>> Submitter     : Trenton Adams <trenton.d.adams@gmail.com>
>> Date          : 2009-03-30 2:04 (8 days old)
>> References    : http://marc.info/?l=linux-kernel&m=123837870307249&w=4
>> Handled-By    : "Morten P.D. Stevens" <mstevens@win-professional.com>
>
> This went through bisection, but looking at the email log, I tend to
> suspect that maybe Trenton marked some versions good even though they
> weren't (because they got versions numbers from v2.6.27), and didn't
> realize that that messes up bisection in a big way.

Is it appropriate for me to respond to these things?

I was wondering about that.  Someone had mentioned that I should trust
the bisect, even when it takes me into "other versions", and it was
taking me through 2.6.27, which I thought was just really weird.
Would you like me to try the bisect again with a little more
diligence, or do you think it can be found with the info given?  It
may take a week or so, due to being a bit busy.

Thanks
--
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Re: 2.6.29-git13: Reported regressions from 2.6.28

[Trenton D. Adams]

On Mon, Apr 6, 2009 at 3:53 PM, Linus Torvalds
<torvalds@linux-foundation.org> wrote:
>
>
> On Mon, 6 Apr 2009, Rafael J. Wysocki wrote:
>>
>> Bug-Entry     : http://bugzilla.kernel.org/show_bug.cgi?id=13018
>> Subject               : 2.6.29 on MacBook 2,1 fails to reboot
>> Submitter     : Trenton Adams <trenton.d.adams@gmail.com>
>> Date          : 2009-03-30 2:04 (8 days old)
>> References    : http://marc.info/?l=linux-kernel&m=123837870307249&w=4
>> Handled-By    : "Morten P.D. Stevens" <mstevens@win-professional.com>
>
> This went through bisection, but looking at the email log, I tend to
> suspect that maybe Trenton marked some versions good even though they
> weren't (because they got versions numbers from v2.6.27), and didn't
> realize that that messes up bisection in a big way.

Is it appropriate for me to respond to these things?

I was wondering about that.  Someone had mentioned that I should trust
the bisect, even when it takes me into "other versions", and it was
taking me through 2.6.27, which I thought was just really weird.
Would you like me to try the bisect again with a little more
diligence, or do you think it can be found with the info given?  It
may take a week or so, due to being a bit busy.

Thanks

Re: 2.6.29-git13: Reported regressions from 2.6.28

[Trenton D. Adams]

On Mon, Apr 6, 2009 at 3:53 PM, Linus Torvalds
<torvalds@linux-foundation.org> wrote:
>
>
> On Mon, 6 Apr 2009, Rafael J. Wysocki wrote:
>>
>> Bug-Entry     : http://bugzilla.kernel.org/show_bug.cgi?id=13018
>> Subject               : 2.6.29 on MacBook 2,1 fails to reboot
>> Submitter     : Trenton Adams <trenton.d.adams@gmail.com>
>> Date          : 2009-03-30 2:04 (8 days old)
>> References    : http://marc.info/?l=linux-kernel&m=123837870307249&w=4
>> Handled-By    : "Morten P.D. Stevens" <mstevens@win-professional.com>
>
> This went through bisection, but looking at the email log, I tend to
> suspect that maybe Trenton marked some versions good even though they
> weren't (because they got versions numbers from v2.6.27), and didn't
> realize that that messes up bisection in a big way.

Is it appropriate for me to respond to these things?

I was wondering about that.  Someone had mentioned that I should trust
the bisect, even when it takes me into "other versions", and it was
taking me through 2.6.27, which I thought was just really weird.
Would you like me to try the bisect again with a little more
diligence, or do you think it can be found with the info given?  It
may take a week or so, due to being a bit busy.

Thanks

Re: 2.6.29-git13: Reported regressions from 2.6.28

[Linus Torvalds]

On Mon, 6 Apr 2009, Trenton D. Adams wrote:
> >
> > This went through bisection, but looking at the email log, I tend to
> > suspect that maybe Trenton marked some versions good even though they
> > weren't (because they got versions numbers from v2.6.27), and didn't
> > realize that that messes up bisection in a big way.
> 
> Is it appropriate for me to respond to these things?

Yes. I added you to the cc exactly because it was hard for me to judge 
from the email discussion that is linked to in the regression list whether 
you actually _did_ mark some versions good because of confusion about the 
version numbering.

That would certainly explain why bisection didn't seem to work.

But it's not the _only_ reason bisection doesn't work. Sometimes you can 
be as careful as possible, but if it's a bug that is even _slightly_ flaky 
(timing-dependencies etc), and the bisection marked something good that 
shouldn't have been (or vice versa, but that's unusual), then the 
bisection end result won't be right.

So you may well have done everything right, and I'm not trying to blame 
you. I just was hoping that maybe that confusion would explain why the 
bisection didn't seem to pinpoint anything sane..

> I was wondering about that.  Someone had mentioned that I should trust
> the bisect, even when it takes me into "other versions", and it was
> taking me through 2.6.27, which I thought was just really weird.
> Would you like me to try the bisect again with a little more
> diligence, or do you think it can be found with the info given?  It
> may take a week or so, due to being a bit busy.

It would be good, especially if this bug doesn't end up being solved some 
other way... And slow results are better than no results at all ;)

			Linus

Re: 2.6.29-git13: Reported regressions from 2.6.28

[Linus Torvalds]

On Mon, 6 Apr 2009, Trenton D. Adams wrote:
> >
> > This went through bisection, but looking at the email log, I tend to
> > suspect that maybe Trenton marked some versions good even though they
> > weren't (because they got versions numbers from v2.6.27), and didn't
> > realize that that messes up bisection in a big way.
> 
> Is it appropriate for me to respond to these things?

Yes. I added you to the cc exactly because it was hard for me to judge 
from the email discussion that is linked to in the regression list whether 
you actually _did_ mark some versions good because of confusion about the 
version numbering.

That would certainly explain why bisection didn't seem to work.

But it's not the _only_ reason bisection doesn't work. Sometimes you can 
be as careful as possible, but if it's a bug that is even _slightly_ flaky 
(timing-dependencies etc), and the bisection marked something good that 
shouldn't have been (or vice versa, but that's unusual), then the 
bisection end result won't be right.

So you may well have done everything right, and I'm not trying to blame 
you. I just was hoping that maybe that confusion would explain why the 
bisection didn't seem to pinpoint anything sane..

> I was wondering about that.  Someone had mentioned that I should trust
> the bisect, even when it takes me into "other versions", and it was
> taking me through 2.6.27, which I thought was just really weird.
> Would you like me to try the bisect again with a little more
> diligence, or do you think it can be found with the info given?  It
> may take a week or so, due to being a bit busy.

It would be good, especially if this bug doesn't end up being solved some 
other way... And slow results are better than no results at all ;)

			Linus

Re: [Bug #12908] acpi_ex_extract_from_field -- div by zero

[Len Brown]

On Mon, 6 Apr 2009, Rafael J. Wysocki wrote:

> This message has been generated automatically as a part of a report
> of recent regressions.
> 
> The following bug entry is on the current list of known regressions
> from 2.6.28.  Please verify if it still should be listed and let me know
> (either way).
> 
> 
> Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12908
> Subject		: acpi_ex_extract_from_field -- div by zero
> Submitter	: Jiri Slaby <jirislaby@gmail.com>
> Date		: 2009-03-15 10:47 (23 days old)
> References	: http://marc.info/?l=linux-kernel&m=123711408225013&w=4
> Handled-By	: Lin Ming <ming.m.lin@intel.com>

This is unreproducible and now marked closed.
The theory is that somebody (else:-) scribbled on random kernel memory...

thanks,
Len Brown, Intel Open Source Technology Center

Re: [Bug #12908] acpi_ex_extract_from_field -- div by zero

[Len Brown]

On Mon, 6 Apr 2009, Rafael J. Wysocki wrote:

> This message has been generated automatically as a part of a report
> of recent regressions.
> 
> The following bug entry is on the current list of known regressions
> from 2.6.28.  Please verify if it still should be listed and let me know
> (either way).
> 
> 
> Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12908
> Subject		: acpi_ex_extract_from_field -- div by zero
> Submitter	: Jiri Slaby <jirislaby-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
> Date		: 2009-03-15 10:47 (23 days old)
> References	: http://marc.info/?l=linux-kernel&m=123711408225013&w=4
> Handled-By	: Lin Ming <ming.m.lin-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>

This is unreproducible and now marked closed.
The theory is that somebody (else:-) scribbled on random kernel memory...

thanks,
Len Brown, Intel Open Source Technology Center

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

[Len Brown]

On Mon, 6 Apr 2009, Rafael J. Wysocki wrote:

> This message has been generated automatically as a part of a report
> of recent regressions.
> 
> The following bug entry is on the current list of known regressions
> from 2.6.28.  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 <nico-linux-20090213@schottelius.org>
> Date		: 2009-02-13 9:33 (53 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

> Handled-By	: Len Brown <lenb@kernel.org>

Handled-By	: Eric Anholt <eric@anholt.net>

thanks,
Len Brown, Intel Open Source Technology Center

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

[Len Brown]

On Mon, 6 Apr 2009, Rafael J. Wysocki wrote:

> This message has been generated automatically as a part of a report
> of recent regressions.
> 
> The following bug entry is on the current list of known regressions
> from 2.6.28.  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 <nico-linux-20090213-xuaVFQXs+5hIG4jRRZ66WA@public.gmane.org>
> Date		: 2009-02-13 9:33 (53 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

> Handled-By	: Len Brown <lenb-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>

Handled-By	: Eric Anholt <eric-WhKQ6XTQaPysTnJN9+BGXg@public.gmane.org>

thanks,
Len Brown, Intel Open Source Technology Center

Re: 2.6.29-git13: Reported regressions from 2.6.28

[Trenton D. Adams]

On Mon, Apr 6, 2009 at 10:07 PM, Linus Torvalds
<torvalds@linux-foundation.org> wrote:
>
>
> On Mon, 6 Apr 2009, Trenton D. Adams wrote:
>> >
>> > This went through bisection, but looking at the email log, I tend to
>> > suspect that maybe Trenton marked some versions good even though they
>> > weren't (because they got versions numbers from v2.6.27), and didn't
>> > realize that that messes up bisection in a big way.
>>
>> Is it appropriate for me to respond to these things?
>
> Yes. I added you to the cc exactly because it was hard for me to judge
> from the email discussion that is linked to in the regression list whether
> you actually _did_ mark some versions good because of confusion about the
> version numbering.

Oh, didn't know you CC'd me.  I have just been searching for my name
to try and keep up to date on threads I participated in, because the
list volume is just too much.

> So you may well have done everything right, and I'm not trying to blame
> you. I just was hoping that maybe that confusion would explain why the
> bisection didn't seem to pinpoint anything sane..

This gave me a bit of a chuckle. ROFL.  I didn't think you were
_blaming_ me.  And even if you were, I'd just say "I'M HUMAN MAN". ;)

It is very well possible that I simply booted the wrong kernel, seeing
I had like 20 to choose from at the time, after doing all those
bisects.  This time, I will make the new kernels the default so that
it is impossible to happen again, assuming that is what happened.  I
will also stop and start alsa 2 or 3 times, in case it is a deadlock
timing issue as you mentioned.

I'm glad to know that I shouldn't be switching kernel versions though.
 I thought that was really crazy.

>
>
> It would be good, especially if this bug doesn't end up being solved some
> other way... And slow results are better than no results at all ;)
>
>                        Linus
>

Okay, I will try again.  Hopefully in a few days I'll have something
for the bug.

Re: 2.6.29-git13: Reported regressions from 2.6.28

[Trenton D. Adams]

On Mon, Apr 6, 2009 at 10:07 PM, Linus Torvalds
<torvalds@linux-foundation.org> wrote:
>
>
> On Mon, 6 Apr 2009, Trenton D. Adams wrote:
>> >
>> > This went through bisection, but looking at the email log, I tend to
>> > suspect that maybe Trenton marked some versions good even though they
>> > weren't (because they got versions numbers from v2.6.27), and didn't
>> > realize that that messes up bisection in a big way.
>>
>> Is it appropriate for me to respond to these things?
>
> Yes. I added you to the cc exactly because it was hard for me to judge
> from the email discussion that is linked to in the regression list whether
> you actually _did_ mark some versions good because of confusion about the
> version numbering.

Oh, didn't know you CC'd me.  I have just been searching for my name
to try and keep up to date on threads I participated in, because the
list volume is just too much.

> So you may well have done everything right, and I'm not trying to blame
> you. I just was hoping that maybe that confusion would explain why the
> bisection didn't seem to pinpoint anything sane..

This gave me a bit of a chuckle. ROFL.  I didn't think you were
_blaming_ me.  And even if you were, I'd just say "I'M HUMAN MAN". ;)

It is very well possible that I simply booted the wrong kernel, seeing
I had like 20 to choose from at the time, after doing all those
bisects.  This time, I will make the new kernels the default so that
it is impossible to happen again, assuming that is what happened.  I
will also stop and start alsa 2 or 3 times, in case it is a deadlock
timing issue as you mentioned.

I'm glad to know that I shouldn't be switching kernel versions though.
 I thought that was really crazy.

>
>
> It would be good, especially if this bug doesn't end up being solved some
> other way... And slow results are better than no results at all ;)
>
>                        Linus
>

Okay, I will try again.  Hopefully in a few days I'll have something
for the bug.

Re: 2.6.29-git13: Reported regressions from 2.6.28

[Jarek Poplawski]

On 07-04-2009 06:23, Trenton D. Adams wrote:
...
> This gave me a bit of a chuckle. ROFL.  I didn't think you were
> _blaming_ me.  And even if you were, I'd just say "I'M HUMAN MAN". ;)

So, do you think you should be treated better than others? @-)

Jarek P.

Re: 2.6.29-git13: Reported regressions from 2.6.28

[Jarek Poplawski]

On 07-04-2009 06:23, Trenton D. Adams wrote:
...
> This gave me a bit of a chuckle. ROFL.  I didn't think you were
> _blaming_ me.  And even if you were, I'd just say "I'M HUMAN MAN". ;)

So, do you think you should be treated better than others? @-)

Jarek P.

Re: 2.6.29-git13: Reported regressions from 2.6.28

[Trenton D. Adams]

On Tue, Apr 7, 2009 at 12:24 AM, Jarek Poplawski <jarkao2@gmail.com> wrote:
> On 07-04-2009 06:23, Trenton D. Adams wrote:
> ...
>> This gave me a bit of a chuckle. ROFL.  I didn't think you were
>> _blaming_ me.  And even if you were, I'd just say "I'M HUMAN MAN". ;)
>
> So, do you think you should be treated better than others? @-)
>
> Jarek P.
>

This gave me a bit of a confused look. Better, how so?  And what would
provoke such a comment?  Linus was simply being excessively polite,
which is a good side to error on I suppose, but I don't need excessive
politeness.  I didn't in any way think he had blamed me for anything.
And why would I?  He hadn't said anything that indicated he was.

Yeah, having trouble getting into your head on that comment.  _confused look_

Re: 2.6.29-git13: Reported regressions from 2.6.28

[Trenton D. Adams]

On Tue, Apr 7, 2009 at 12:24 AM, Jarek Poplawski <jarkao2@gmail.com> wrote:
> On 07-04-2009 06:23, Trenton D. Adams wrote:
> ...
>> This gave me a bit of a chuckle. ROFL.  I didn't think you were
>> _blaming_ me.  And even if you were, I'd just say "I'M HUMAN MAN". ;)
>
> So, do you think you should be treated better than others? @-)
>
> Jarek P.
>

This gave me a bit of a confused look. Better, how so?  And what would
provoke such a comment?  Linus was simply being excessively polite,
which is a good side to error on I suppose, but I don't need excessive
politeness.  I didn't in any way think he had blamed me for anything.
And why would I?  He hadn't said anything that indicated he was.

Yeah, having trouble getting into your head on that comment.  _confused look_

Re: 2.6.29-git13: Reported regressions from 2.6.28

[Jarek Poplawski]

On Tue, Apr 07, 2009 at 12:31:52AM -0600, Trenton D. Adams wrote:
> On Tue, Apr 7, 2009 at 12:24 AM, Jarek Poplawski <jarkao2@gmail.com> wrote:
> > On 07-04-2009 06:23, Trenton D. Adams wrote:
> > ...
> >> This gave me a bit of a chuckle. ROFL.  I didn't think you were
> >> _blaming_ me.  And even if you were, I'd just say "I'M HUMAN MAN". ;)
> >
> > So, do you think you should be treated better than others? @-)
> >
> > Jarek P.
> >
> 
> This gave me a bit of a confused look. Better, how so?  And what would

Hmm... I mean better than NON-HUMANS of course! Everybody is equal here.

Jarek P.

Re: 2.6.29-git13: Reported regressions from 2.6.28

[Jarek Poplawski]

On Tue, Apr 07, 2009 at 12:31:52AM -0600, Trenton D. Adams wrote:
> On Tue, Apr 7, 2009 at 12:24 AM, Jarek Poplawski <jarkao2@gmail.com> wrote:
> > On 07-04-2009 06:23, Trenton D. Adams wrote:
> > ...
> >> This gave me a bit of a chuckle. ROFL.  I didn't think you were
> >> _blaming_ me.  And even if you were, I'd just say "I'M HUMAN MAN". ;)
> >
> > So, do you think you should be treated better than others? @-)
> >
> > Jarek P.
> >
> 
> This gave me a bit of a confused look. Better, how so?  And what would

Hmm... I mean better than NON-HUMANS of course! Everybody is equal here.

Jarek P.

Re: 2.6.29-git13: Reported regressions from 2.6.28

[Trenton D. Adams]

On Tue, Apr 7, 2009 at 12:41 AM, Jarek Poplawski <jarkao2-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:
> On Tue, Apr 07, 2009 at 12:31:52AM -0600, Trenton D. Adams wrote:
>> On Tue, Apr 7, 2009 at 12:24 AM, Jarek Poplawski <jarkao2-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:
>> > On 07-04-2009 06:23, Trenton D. Adams wrote:
>> > ...
>> >> This gave me a bit of a chuckle. ROFL.  I didn't think you were
>> >> _blaming_ me.  And even if you were, I'd just say "I'M HUMAN MAN". ;)
>> >
>> > So, do you think you should be treated better than others? @-)
>> >
>> > Jarek P.
>> >
>>
>> This gave me a bit of a confused look. Better, how so?  And what would
>
> Hmm... I mean better than NON-HUMANS of course! Everybody is equal here.
>
> Jarek P.
>

Oh, I did not see your smiley before, because I have never seen that
particular smiley, so my brain filtered it out.  What kind of emotion
does it imply?

Boy, you'd thunk I would have seen it by now. :P

Re: 2.6.29-git13: Reported regressions from 2.6.28

[Trenton D. Adams]

On Tue, Apr 7, 2009 at 12:41 AM, Jarek Poplawski <jarkao2@gmail.com> wrote:
> On Tue, Apr 07, 2009 at 12:31:52AM -0600, Trenton D. Adams wrote:
>> On Tue, Apr 7, 2009 at 12:24 AM, Jarek Poplawski <jarkao2@gmail.com> wrote:
>> > On 07-04-2009 06:23, Trenton D. Adams wrote:
>> > ...
>> >> This gave me a bit of a chuckle. ROFL.  I didn't think you were
>> >> _blaming_ me.  And even if you were, I'd just say "I'M HUMAN MAN". ;)
>> >
>> > So, do you think you should be treated better than others? @-)
>> >
>> > Jarek P.
>> >
>>
>> This gave me a bit of a confused look. Better, how so?  And what would
>
> Hmm... I mean better than NON-HUMANS of course! Everybody is equal here.
>
> Jarek P.
>

Oh, I did not see your smiley before, because I have never seen that
particular smiley, so my brain filtered it out.  What kind of emotion
does it imply?

Boy, you'd thunk I would have seen it by now. :P

Re: 2.6.29-git13: Reported regressions from 2.6.28

[Trenton D. Adams]

On Tue, Apr 7, 2009 at 12:41 AM, Jarek Poplawski <jarkao2@gmail.com> wrote:
> On Tue, Apr 07, 2009 at 12:31:52AM -0600, Trenton D. Adams wrote:
>> On Tue, Apr 7, 2009 at 12:24 AM, Jarek Poplawski <jarkao2@gmail.com> wrote:
>> > On 07-04-2009 06:23, Trenton D. Adams wrote:
>> > ...
>> >> This gave me a bit of a chuckle. ROFL.  I didn't think you were
>> >> _blaming_ me.  And even if you were, I'd just say "I'M HUMAN MAN". ;)
>> >
>> > So, do you think you should be treated better than others? @-)
>> >
>> > Jarek P.
>> >
>>
>> This gave me a bit of a confused look. Better, how so?  And what would
>
> Hmm... I mean better than NON-HUMANS of course! Everybody is equal here.
>
> Jarek P.
>

Oh, I did not see your smiley before, because I have never seen that
particular smiley, so my brain filtered it out.  What kind of emotion
does it imply?

Boy, you'd thunk I would have seen it by now. :P

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

[Marcel Holtmann]

Hi Rafael,

> This message has been generated automatically as a part of a report
> of recent regressions.
> 
> The following bug entry is on the current list of known regressions
> from 2.6.28.  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" <maciej.rutecki@gmail.com>
> Date		: 2009-01-13 18:34 (84 days old)
> References	: http://marc.info/?l=linux-kernel&m=123187185426236&w=4

I prefer to have this checked against 2.6.30-rc1 once Linus released
that one. I think that I know the root cause for this one and it is
actually a hardware/firmware bug. Some Bluetooth dongles expect to have
the interrupt and bulk URBs available at the same time. Otherwise they
do pee in their pants.

Regards

Marcel

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

[Marcel Holtmann]

Hi Rafael,

> This message has been generated automatically as a part of a report
> of recent regressions.
> 
> The following bug entry is on the current list of known regressions
> from 2.6.28.  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" <maciej.rutecki-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
> Date		: 2009-01-13 18:34 (84 days old)
> References	: http://marc.info/?l=linux-kernel&m=123187185426236&w=4

I prefer to have this checked against 2.6.30-rc1 once Linus released
that one. I think that I know the root cause for this one and it is
actually a hardware/firmware bug. Some Bluetooth dongles expect to have
the interrupt and bulk URBs available at the same time. Otherwise they
do pee in their pants.

Regards

Marcel

Re: [Bug #12871] usb bluetooth crashes system

[Marcel Holtmann]

Hi Rafael,

> This message has been generated automatically as a part of a report
> of recent regressions.
> 
> The following bug entry is on the current list of known regressions
> from 2.6.28.  Please verify if it still should be listed and let me know
> (either way).
> 
> 
> Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12871
> Subject		: usb bluetooth crashes system
> Submitter	: Pavel Machek <pavel@ucw.cz>
> Date		: 2009-03-10 11:23 (28 days old)
> References	: http://marc.info/?l=linux-kernel&m=123668450400940&w=4

please have this re-tested against 2.6.30-rc1 then we can work on
figuring out which patch might have fixed it. I think it is fixed now,
but I could be also wrong here.

Regards

Marcel

Re: [Bug #12871] usb bluetooth crashes system

[Marcel Holtmann]

Hi Rafael,

> This message has been generated automatically as a part of a report
> of recent regressions.
> 
> The following bug entry is on the current list of known regressions
> from 2.6.28.  Please verify if it still should be listed and let me know
> (either way).
> 
> 
> Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12871
> Subject		: usb bluetooth crashes system
> Submitter	: Pavel Machek <pavel-+ZI9xUNit7I@public.gmane.org>
> Date		: 2009-03-10 11:23 (28 days old)
> References	: http://marc.info/?l=linux-kernel&m=123668450400940&w=4

please have this re-tested against 2.6.30-rc1 then we can work on
figuring out which patch might have fixed it. I think it is fixed now,
but I could be also wrong here.

Regards

Marcel

Re: [Bug #12871] usb bluetooth crashes system

[Pavel Machek]

Hi!

> > > This message has been generated automatically as a part of a report
> > > of recent regressions.
> > > 
> > > The following bug entry is on the current list of known regressions
> > > from 2.6.28.  Please verify if it still should be listed and let me know
> > > (either way).
> > > 
> > > 
> > > Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12871
> > > Subject		: usb bluetooth crashes system
> > > Submitter	: Pavel Machek <pavel@ucw.cz>
> > > Date		: 2009-03-10 11:23 (28 days old)
> > > References	: http://marc.info/?l=linux-kernel&m=123668450400940&w=4
> > 
> > please have this re-tested against 2.6.30-rc1 then we can work on
> > figuring out which patch might have fixed it. I think it is fixed now,
> > but I could be also wrong here.
> 
> 2.6.30-rc1 does not seem to be out (according to kernel.org); I can
> test the latest git if that helps?

Seems to be ok in 2.6.30-rc1 after quick test...

-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html

Re: [Bug #12871] usb bluetooth crashes system

[Pavel Machek]

Hi!

> > > This message has been generated automatically as a part of a report
> > > of recent regressions.
> > > 
> > > The following bug entry is on the current list of known regressions
> > > from 2.6.28.  Please verify if it still should be listed and let me know
> > > (either way).
> > > 
> > > 
> > > Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12871
> > > Subject		: usb bluetooth crashes system
> > > Submitter	: Pavel Machek <pavel-+ZI9xUNit7I@public.gmane.org>
> > > Date		: 2009-03-10 11:23 (28 days old)
> > > References	: http://marc.info/?l=linux-kernel&m=123668450400940&w=4
> > 
> > please have this re-tested against 2.6.30-rc1 then we can work on
> > figuring out which patch might have fixed it. I think it is fixed now,
> > but I could be also wrong here.
> 
> 2.6.30-rc1 does not seem to be out (according to kernel.org); I can
> test the latest git if that helps?

Seems to be ok in 2.6.30-rc1 after quick test...

-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html

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

[Maciej Rutecki]

2009/4/7 Marcel Holtmann <marcel@holtmann.org>:
> Hi Rafael,
>
>> This message has been generated automatically as a part of a report
>> of recent regressions.
>>
>> The following bug entry is on the current list of known regressions
>> from 2.6.28.  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" <maciej.rutecki@gmail.com>
>> Date          : 2009-01-13 18:34 (84 days old)

I forgot this bug :)

>> References    : http://marc.info/?l=linux-kernel&m=123187185426236&w=4
>
> I prefer to have this checked against 2.6.30-rc1 once Linus released
> that one. I think that I know the root cause for this one and it is
> actually a hardware/firmware bug. Some Bluetooth dongles expect to have
> the interrupt and bulk URBs available at the same time. Otherwise they
> do pee in their pants.

I will check -rc1 when will be available.

>
> Regards
>
> Marcel
>
>
>


Regards
-- 
Maciej Rutecki
http://www.maciek.unixy.pl

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

[Maciej Rutecki]

2009/4/7 Marcel Holtmann <marcel-kz+m5ild9QBg9hUCZPvPmw@public.gmane.org>:
> Hi Rafael,
>
>> This message has been generated automatically as a part of a report
>> of recent regressions.
>>
>> The following bug entry is on the current list of known regressions
>> from 2.6.28.  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" <maciej.rutecki-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
>> Date          : 2009-01-13 18:34 (84 days old)

I forgot this bug :)

>> References    : http://marc.info/?l=linux-kernel&m=123187185426236&w=4
>
> I prefer to have this checked against 2.6.30-rc1 once Linus released
> that one. I think that I know the root cause for this one and it is
> actually a hardware/firmware bug. Some Bluetooth dongles expect to have
> the interrupt and bulk URBs available at the same time. Otherwise they
> do pee in their pants.

I will check -rc1 when will be available.

>
> Regards
>
> Marcel
>
>
>


Regards
-- 
Maciej Rutecki
http://www.maciek.unixy.pl

Re: [Bug #12670] BUG: unable to handle kernel paging request at pin_to_kill+0x21

[Alessandro Bono]

On Mon, 2009-04-06 at 21:05 +0200, Rafael J. Wysocki wrote:
> This message has been generated automatically as a part of a report
> of recent regressions.
> 
> The following bug entry is on the current list of known regressions
> from 2.6.28.  Please verify if it still should be listed and let me know
> (either way).
> 
> 
> Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12670
> Subject		: BUG: unable to handle kernel paging request at pin_to_kill+0x21
> Submitter	: Alessandro Bono <alessandro.bono@gmail.com>
> Date		: 2009-02-08 11:04 (58 days old)
> References	: http://marc.info/?l=linux-kernel&m=123409113223833&w=4
> 
> 
HI

please close this bug
I'm not able to reproduce and at time of this problem my notebook has
broken memory modules

thanks

-- 
Cordiali Saluti
Alessandro Bono

Re: [Bug #12670] BUG: unable to handle kernel paging request at pin_to_kill+0x21

[Alessandro Bono]

On Mon, 2009-04-06 at 21:05 +0200, Rafael J. Wysocki wrote:
> This message has been generated automatically as a part of a report
> of recent regressions.
> 
> The following bug entry is on the current list of known regressions
> from 2.6.28.  Please verify if it still should be listed and let me know
> (either way).
> 
> 
> Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12670
> Subject		: BUG: unable to handle kernel paging request at pin_to_kill+0x21
> Submitter	: Alessandro Bono <alessandro.bono-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
> Date		: 2009-02-08 11:04 (58 days old)
> References	: http://marc.info/?l=linux-kernel&m=123409113223833&w=4
> 
> 
HI

please close this bug
I'm not able to reproduce and at time of this problem my notebook has
broken memory modules

thanks

-- 
Cordiali Saluti
Alessandro Bono

Re: [Bug #13015] pppoe over ethernet

[Detlef Tschirschky]

On Tue, 7 Apr 2009, Cyrill Gorcunov wrote:

> On 4/6/09, Rafael J. Wysocki wrote:

>> Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13015
>> Subject	: pppoe over ethernet

> I expect the issue is inspered by network problem found in plain
> 2.6.29. Detlef could you confirm the problem is still active in
> 2.6.29.1 or in current -git mainline?

Moin Cyrill,

2.6.29.1 is running fine for me. Can't find any network problems in 
2.6.29.1 now.

Thanks and regards

Detlef

Re: [Bug #13015] pppoe over ethernet

[Detlef Tschirschky]

On Tue, 7 Apr 2009, Cyrill Gorcunov wrote:

> On 4/6/09, Rafael J. Wysocki wrote:

>> Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13015
>> Subject	: pppoe over ethernet

> I expect the issue is inspered by network problem found in plain
> 2.6.29. Detlef could you confirm the problem is still active in
> 2.6.29.1 or in current -git mainline?

Moin Cyrill,

2.6.29.1 is running fine for me. Can't find any network problems in 
2.6.29.1 now.

Thanks and regards

Detlef

Re: [Bug #13015] pppoe over ethernet

[Cyrill Gorcunov]

On 4/7/09, Detlef Tschirschky <detlef.tschirschky@gmx.de> wrote:
> On Tue, 7 Apr 2009, Cyrill Gorcunov wrote:
>
>> On 4/6/09, Rafael J. Wysocki wrote:
>
>>> Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13015
>>> Subject	: pppoe over ethernet
>
>> I expect the issue is inspered by network problem found in plain
>> 2.6.29. Detlef could you confirm the problem is still active in
>> 2.6.29.1 or in current -git mainline?
>
> Moin Cyrill,
>
> 2.6.29.1 is running fine for me. Can't find any network problems in
> 2.6.29.1 now.
>
> Thanks and regards
>
> Detlef
>
>
Thanks a lot, Detlef!
Rafael, i guess we could close the bug.

Re: [Bug #13015] pppoe over ethernet

[Cyrill Gorcunov]

On 4/7/09, Detlef Tschirschky <detlef.tschirschky-Mmb7MZpHnFY@public.gmane.org> wrote:
> On Tue, 7 Apr 2009, Cyrill Gorcunov wrote:
>
>> On 4/6/09, Rafael J. Wysocki wrote:
>
>>> Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13015
>>> Subject	: pppoe over ethernet
>
>> I expect the issue is inspered by network problem found in plain
>> 2.6.29. Detlef could you confirm the problem is still active in
>> 2.6.29.1 or in current -git mainline?
>
> Moin Cyrill,
>
> 2.6.29.1 is running fine for me. Can't find any network problems in
> 2.6.29.1 now.
>
> Thanks and regards
>
> Detlef
>
>
Thanks a lot, Detlef!
Rafael, i guess we could close the bug.

Re: 2.6.29-git13: Reported regressions from 2.6.28

[Ilpo Järvinen]

On Mon, 6 Apr 2009, Rafael J. Wysocki wrote:

> Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12867
> Subject		: 2.6.29-rc7 broke r8169 MAC on Thecus n2100 ARM board
> Submitter	: Mikael Pettersson <mikpe@it.uu.se>
> Date		: 2009-03-09 20:29 (29 days old)
> References	: http://marc.info/?l=linux-kernel&m=123663065403760&w=4
> Handled-By	: Francois Romieu <romieu@fr.zoreil.com>

I think this was fixed in the mainline by revert
ea8dbdd17099a9a5864ebd4c87e01e657b19c7ab.


-- 
 i.

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

[Johannes Berg]

[-- Attachment #1: Type: text/plain, Size: 396 bytes --]


> Anyway here's a patch to buy some time.  Johannes, would this be
> an acceptable band-aid for now?

This is going to make it print two warnings for one occurrence of the
problem though. I'd much prefer to put something into minstrel.c to
catch when _it_ returns bogus values and in that case return 0, that way
at least the bandaid is restricted to the code it patches up.

johannes

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

Re: [Bug #12908] acpi_ex_extract_from_field -- div by zero

[Jiri Slaby]

On 04/07/2009 06:09 AM, Len Brown wrote:
> On Mon, 6 Apr 2009, Rafael J. Wysocki wrote:
> 
>> This message has been generated automatically as a part of a report
>> of recent regressions.
>>
>> The following bug entry is on the current list of known regressions
>> from 2.6.28.  Please verify if it still should be listed and let me know
>> (either way).
>>
>>
>> Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12908
>> Subject		: acpi_ex_extract_from_field -- div by zero
>> Submitter	: Jiri Slaby <jirislaby@gmail.com>
>> Date		: 2009-03-15 10:47 (23 days old)
>> References	: http://marc.info/?l=linux-kernel&m=123711408225013&w=4
>> Handled-By	: Lin Ming <ming.m.lin@intel.com>
> 
> This is unreproducible and now marked closed.

s/un/hardly /. As I wrote earlier this usually happens after few days
being off which makes it peculiar.

> The theory is that somebody (else:-) scribbled on random kernel memory...

Might be, this will probably be hard to catch :/.

Or even a HW malfunction...

Re: [Bug #12908] acpi_ex_extract_from_field -- div by zero

[Jiri Slaby]

On 04/07/2009 06:09 AM, Len Brown wrote:
> On Mon, 6 Apr 2009, Rafael J. Wysocki wrote:
> 
>> This message has been generated automatically as a part of a report
>> of recent regressions.
>>
>> The following bug entry is on the current list of known regressions
>> from 2.6.28.  Please verify if it still should be listed and let me know
>> (either way).
>>
>>
>> Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12908
>> Subject		: acpi_ex_extract_from_field -- div by zero
>> Submitter	: Jiri Slaby <jirislaby-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
>> Date		: 2009-03-15 10:47 (23 days old)
>> References	: http://marc.info/?l=linux-kernel&m=123711408225013&w=4
>> Handled-By	: Lin Ming <ming.m.lin-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
> 
> This is unreproducible and now marked closed.

s/un/hardly /. As I wrote earlier this usually happens after few days
being off which makes it peculiar.

> The theory is that somebody (else:-) scribbled on random kernel memory...

Might be, this will probably be hard to catch :/.

Or even a HW malfunction...

Re: 2.6.29-git13: Reported regressions from 2.6.28

[Stefan Richter]

Linus Torvalds wrote:
> On Mon, 6 Apr 2009, Rafael J. Wysocki wrote:
>> Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13018
>> Subject		: 2.6.29 on MacBook 2,1 fails to reboot
>> Submitter	: Trenton Adams <trenton.d.adams-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
>> Date		: 2009-03-30 2:04 (8 days old)
>> References	: http://marc.info/?l=linux-kernel&m=123837870307249&w=4
>> Handled-By	: "Morten P.D. Stevens" <mstevens-APqb+XXLJz/QQQFqJy/XgFaTQe2KTcn/@public.gmane.org>
> 
> This went through bisection, but looking at the email log, I tend to 
> suspect that maybe Trenton marked some versions good even though they 
> weren't (because they got versions numbers from v2.6.27), and didn't 
> realize that that messes up bisection in a big way.
> 
> The bug _sounds_ like some deadlock due to lock problems - the shutdown 
> path often triggers locks that no other path really cares about. And we 
> had some lock problems in the sound subsystem that got fixed post-2.6.28, 
> for example. 
> 
> And it looks like the problem is somewhere in sound shutdown:
> 
> 12181 delete_module("snd_hda_codec", O_RDONLY|O_EXCL) = -1 EAGAIN (Resource temporarily unavailable) <0.000011>
> 
> So commits like 91054598f794fb5d8a0b1e747ff8e2e8fc2115b3 ("ALSA: pcm_oss, 
> fix locking typo") might explain it.

Trenton,
could it be the same as this one?
http://bugzilla.kernel.org/show_bug.cgi?id=12321
"System hangs when unloading alsa modules"
http://bugs.gentoo.org/show_bug.cgi?id=253535
"System hangs when unloading alsa modules on Kernel >2.6.28"
-- 
Stefan Richter
-=====-==--= -=-- --===
http://arcgraph.de/sr/

Re: 2.6.29-git13: Reported regressions from 2.6.28

[Stefan Richter]

Linus Torvalds wrote:
> On Mon, 6 Apr 2009, Rafael J. Wysocki wrote:
>> Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13018
>> Subject		: 2.6.29 on MacBook 2,1 fails to reboot
>> Submitter	: Trenton Adams <trenton.d.adams@gmail.com>
>> Date		: 2009-03-30 2:04 (8 days old)
>> References	: http://marc.info/?l=linux-kernel&m=123837870307249&w=4
>> Handled-By	: "Morten P.D. Stevens" <mstevens@win-professional.com>
> 
> This went through bisection, but looking at the email log, I tend to 
> suspect that maybe Trenton marked some versions good even though they 
> weren't (because they got versions numbers from v2.6.27), and didn't 
> realize that that messes up bisection in a big way.
> 
> The bug _sounds_ like some deadlock due to lock problems - the shutdown 
> path often triggers locks that no other path really cares about. And we 
> had some lock problems in the sound subsystem that got fixed post-2.6.28, 
> for example. 
> 
> And it looks like the problem is somewhere in sound shutdown:
> 
> 12181 delete_module("snd_hda_codec", O_RDONLY|O_EXCL) = -1 EAGAIN (Resource temporarily unavailable) <0.000011>
> 
> So commits like 91054598f794fb5d8a0b1e747ff8e2e8fc2115b3 ("ALSA: pcm_oss, 
> fix locking typo") might explain it.

Trenton,
could it be the same as this one?
http://bugzilla.kernel.org/show_bug.cgi?id=12321
"System hangs when unloading alsa modules"
http://bugs.gentoo.org/show_bug.cgi?id=253535
"System hangs when unloading alsa modules on Kernel >2.6.28"
-- 
Stefan Richter
-=====-==--= -=-- --===
http://arcgraph.de/sr/

Re: 2.6.29-git13: Reported regressions from 2.6.28

[Stefan Richter]

Linus Torvalds wrote:
> On Mon, 6 Apr 2009, Rafael J. Wysocki wrote:
>> Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13018
>> Subject		: 2.6.29 on MacBook 2,1 fails to reboot
>> Submitter	: Trenton Adams <trenton.d.adams@gmail.com>
>> Date		: 2009-03-30 2:04 (8 days old)
>> References	: http://marc.info/?l=linux-kernel&m=123837870307249&w=4
>> Handled-By	: "Morten P.D. Stevens" <mstevens@win-professional.com>
> 
> This went through bisection, but looking at the email log, I tend to 
> suspect that maybe Trenton marked some versions good even though they 
> weren't (because they got versions numbers from v2.6.27), and didn't 
> realize that that messes up bisection in a big way.
> 
> The bug _sounds_ like some deadlock due to lock problems - the shutdown 
> path often triggers locks that no other path really cares about. And we 
> had some lock problems in the sound subsystem that got fixed post-2.6.28, 
> for example. 
> 
> And it looks like the problem is somewhere in sound shutdown:
> 
> 12181 delete_module("snd_hda_codec", O_RDONLY|O_EXCL) = -1 EAGAIN (Resource temporarily unavailable) <0.000011>
> 
> So commits like 91054598f794fb5d8a0b1e747ff8e2e8fc2115b3 ("ALSA: pcm_oss, 
> fix locking typo") might explain it.

Trenton,
could it be the same as this one?
http://bugzilla.kernel.org/show_bug.cgi?id=12321
"System hangs when unloading alsa modules"
http://bugs.gentoo.org/show_bug.cgi?id=253535
"System hangs when unloading alsa modules on Kernel >2.6.28"
-- 
Stefan Richter
-=====-==--= -=-- --===
http://arcgraph.de/sr/

Re: 2.6.29-git13: Reported regressions from 2.6.28

[Trenton D. Adams]

On Tue, Apr 7, 2009 at 10:16 AM, Stefan Richter
<stefanr-MtYdepGKPcBMYopoZt5u/LNAH6kLmebB@public.gmane.org> wrote:
> Linus Torvalds wrote:
>> On Mon, 6 Apr 2009, Rafael J. Wysocki wrote:
>>> Bug-Entry    : http://bugzilla.kernel.org/show_bug.cgi?id=13018
>>> Subject              : 2.6.29 on MacBook 2,1 fails to reboot
>>> Submitter    : Trenton Adams <trenton.d.adams-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
>>> Date         : 2009-03-30 2:04 (8 days old)
>>> References   : http://marc.info/?l=linux-kernel&m=123837870307249&w=4
>>> Handled-By   : "Morten P.D. Stevens" <mstevens@win-professional.com>
>>
>
> Trenton,
> could it be the same as this one?
> http://bugzilla.kernel.org/show_bug.cgi?id=12321
> "System hangs when unloading alsa modules"
> http://bugs.gentoo.org/show_bug.cgi?id=253535
> "System hangs when unloading alsa modules on Kernel >2.6.28"
> --
> Stefan Richter
> -=====-==--= -=-- --===
> http://arcgraph.de/sr/
>

The first one looks similar, if not identical.  The second one
doesn't, because my problem happens on 2.6.29 only, not 2.6.28.
Either way, the unload problem with the module didn't happen in
2.6.28.

Re: 2.6.29-git13: Reported regressions from 2.6.28

[Trenton D. Adams]

On Tue, Apr 7, 2009 at 10:16 AM, Stefan Richter
<stefanr@s5r6.in-berlin.de> wrote:
> Linus Torvalds wrote:
>> On Mon, 6 Apr 2009, Rafael J. Wysocki wrote:
>>> Bug-Entry    : http://bugzilla.kernel.org/show_bug.cgi?id=13018
>>> Subject              : 2.6.29 on MacBook 2,1 fails to reboot
>>> Submitter    : Trenton Adams <trenton.d.adams@gmail.com>
>>> Date         : 2009-03-30 2:04 (8 days old)
>>> References   : http://marc.info/?l=linux-kernel&m=123837870307249&w=4
>>> Handled-By   : "Morten P.D. Stevens" <mstevens@win-professional.com>
>>
>
> Trenton,
> could it be the same as this one?
> http://bugzilla.kernel.org/show_bug.cgi?id=12321
> "System hangs when unloading alsa modules"
> http://bugs.gentoo.org/show_bug.cgi?id=253535
> "System hangs when unloading alsa modules on Kernel >2.6.28"
> --
> Stefan Richter
> -=====-==--= -=-- --===
> http://arcgraph.de/sr/
>

The first one looks similar, if not identical.  The second one
doesn't, because my problem happens on 2.6.29 only, not 2.6.28.
Either way, the unload problem with the module didn't happen in
2.6.28.

Re: 2.6.29-git13: Reported regressions from 2.6.28

[Trenton D. Adams]

On Tue, Apr 7, 2009 at 10:16 AM, Stefan Richter
<stefanr@s5r6.in-berlin.de> wrote:
> Linus Torvalds wrote:
>> On Mon, 6 Apr 2009, Rafael J. Wysocki wrote:
>>> Bug-Entry    : http://bugzilla.kernel.org/show_bug.cgi?id=13018
>>> Subject              : 2.6.29 on MacBook 2,1 fails to reboot
>>> Submitter    : Trenton Adams <trenton.d.adams@gmail.com>
>>> Date         : 2009-03-30 2:04 (8 days old)
>>> References   : http://marc.info/?l=linux-kernel&m=123837870307249&w=4
>>> Handled-By   : "Morten P.D. Stevens" <mstevens@win-professional.com>
>>
>
> Trenton,
> could it be the same as this one?
> http://bugzilla.kernel.org/show_bug.cgi?id=12321
> "System hangs when unloading alsa modules"
> http://bugs.gentoo.org/show_bug.cgi?id=253535
> "System hangs when unloading alsa modules on Kernel >2.6.28"
> --
> Stefan Richter
> -=====-==--= -=-- --===
> http://arcgraph.de/sr/
>

The first one looks similar, if not identical.  The second one
doesn't, because my problem happens on 2.6.29 only, not 2.6.28.
Either way, the unload problem with the module didn't happen in
2.6.28.

2.6.29 on MacBook 2, 1 fails to reboot (was Re: 2.6.29-git13: Reported regressions from 2.6.28)

[Stefan Richter]

Trenton D. Adams wrote:
> On Tue, Apr 7, 2009 at 10:16 AM, Stefan Richter
> <stefanr@s5r6.in-berlin.de> wrote:
>> Linus Torvalds wrote:
>>> On Mon, 6 Apr 2009, Rafael J. Wysocki wrote:
>>>> Bug-Entry    : http://bugzilla.kernel.org/show_bug.cgi?id=13018
>>>> Subject              : 2.6.29 on MacBook 2,1 fails to reboot
...
>>> The bug _sounds_ like some deadlock due to lock problems - the shutdown 
>>> path often triggers locks that no other path really cares about. And we 
>>> had some lock problems in the sound subsystem that got fixed post-2.6.28, 
>>> for example. 
>>> 
>>> And it looks like the problem is somewhere in sound shutdown:
>>> 
>>> 12181 delete_module("snd_hda_codec", O_RDONLY|O_EXCL) = -1 EAGAIN (Resource temporarily unavailable) <0.000011>
>>> 
>>> So commits like 91054598f794fb5d8a0b1e747ff8e2e8fc2115b3 ("ALSA: pcm_oss, 
>>> fix locking typo") might explain it.
...
>> could it be the same as this one?
>> http://bugzilla.kernel.org/show_bug.cgi?id=12321
>> "System hangs when unloading alsa modules"
>> http://bugs.gentoo.org/show_bug.cgi?id=253535
>> "System hangs when unloading alsa modules on Kernel >2.6.28"
...
> The first one looks similar, if not identical.  The second one
> doesn't, because my problem happens on 2.6.29 only, not 2.6.28.

The Gentoo bug entry too is about a regression _after_ 2.6.28. :-)
I.e. 2.6.28.y. are unaffected.  It's actually just the downstream
duplicate of the kernel.org bug entry.

> Either way, the unload problem with the module didn't happen in
> 2.6.28.

Interdependencies between ALSA modules have changed.  The Gentoo init
scripts attempted to unload them in an order which deadlocked modprobe
due to dependencies.  The fix for Gentoo is to just not unload the
modules on system shutdown.  My Gentoo/amd64 Mac mini was affected by
this too; fixed by userland update.

(Added Cc to tiwai@suse.de)
-- 
Stefan Richter
-=====-=-=== -=-= -==-=
http://arcgraph.de/sr/

2.6.29 on MacBook 2,1 fails to reboot (was Re: 2.6.29-git13: Reported regressions from 2.6.28)

[Stefan Richter]

Trenton D. Adams wrote:
> On Tue, Apr 7, 2009 at 10:16 AM, Stefan Richter
> <stefanr@s5r6.in-berlin.de> wrote:
>> Linus Torvalds wrote:
>>> On Mon, 6 Apr 2009, Rafael J. Wysocki wrote:
>>>> Bug-Entry    : http://bugzilla.kernel.org/show_bug.cgi?id=13018
>>>> Subject              : 2.6.29 on MacBook 2,1 fails to reboot
...
>>> The bug _sounds_ like some deadlock due to lock problems - the shutdown 
>>> path often triggers locks that no other path really cares about. And we 
>>> had some lock problems in the sound subsystem that got fixed post-2.6.28, 
>>> for example. 
>>> 
>>> And it looks like the problem is somewhere in sound shutdown:
>>> 
>>> 12181 delete_module("snd_hda_codec", O_RDONLY|O_EXCL) = -1 EAGAIN (Resource temporarily unavailable) <0.000011>
>>> 
>>> So commits like 91054598f794fb5d8a0b1e747ff8e2e8fc2115b3 ("ALSA: pcm_oss, 
>>> fix locking typo") might explain it.
...
>> could it be the same as this one?
>> http://bugzilla.kernel.org/show_bug.cgi?id=12321
>> "System hangs when unloading alsa modules"
>> http://bugs.gentoo.org/show_bug.cgi?id=253535
>> "System hangs when unloading alsa modules on Kernel >2.6.28"
...
> The first one looks similar, if not identical.  The second one
> doesn't, because my problem happens on 2.6.29 only, not 2.6.28.

The Gentoo bug entry too is about a regression _after_ 2.6.28. :-)
I.e. 2.6.28.y. are unaffected.  It's actually just the downstream
duplicate of the kernel.org bug entry.

> Either way, the unload problem with the module didn't happen in
> 2.6.28.

Interdependencies between ALSA modules have changed.  The Gentoo init
scripts attempted to unload them in an order which deadlocked modprobe
due to dependencies.  The fix for Gentoo is to just not unload the
modules on system shutdown.  My Gentoo/amd64 Mac mini was affected by
this too; fixed by userland update.

(Added Cc to tiwai@suse.de)
-- 
Stefan Richter
-=====-=-=== -=-= -==-=
http://arcgraph.de/sr/

Re: 2.6.29 on MacBook 2,1 fails to reboot (was Re: 2.6.29-git13: Reported regressions from 2.6.28)

[Justin Mattock]

On Tue, Apr 7, 2009 at 10:10 AM, Stefan Richter
<stefanr-MtYdepGKPcBMYopoZt5u/LNAH6kLmebB@public.gmane.org> wrote:
> Trenton D. Adams wrote:
>> On Tue, Apr 7, 2009 at 10:16 AM, Stefan Richter
>> <stefanr-MtYdepGKPcBMYopoZt5u/LNAH6kLmebB@public.gmane.org> wrote:
>>> Linus Torvalds wrote:
>>>> On Mon, 6 Apr 2009, Rafael J. Wysocki wrote:
>>>>> Bug-Entry    : http://bugzilla.kernel.org/show_bug.cgi?id=13018
>>>>> Subject              : 2.6.29 on MacBook 2,1 fails to reboot
> ...
>>>> The bug _sounds_ like some deadlock due to lock problems - the shutdown
>>>> path often triggers locks that no other path really cares about. And we
>>>> had some lock problems in the sound subsystem that got fixed post-2.6.28,
>>>> for example.
>>>>
>>>> And it looks like the problem is somewhere in sound shutdown:
>>>>
>>>> 12181 delete_module("snd_hda_codec", O_RDONLY|O_EXCL) = -1 EAGAIN (Resource temporarily unavailable) <0.000011>
>>>>
>>>> So commits like 91054598f794fb5d8a0b1e747ff8e2e8fc2115b3 ("ALSA: pcm_oss,
>>>> fix locking typo") might explain it.
> ...
>>> could it be the same as this one?
>>> http://bugzilla.kernel.org/show_bug.cgi?id=12321
>>> "System hangs when unloading alsa modules"
>>> http://bugs.gentoo.org/show_bug.cgi?id=253535
>>> "System hangs when unloading alsa modules on Kernel >2.6.28"
> ...
>> The first one looks similar, if not identical.  The second one
>> doesn't, because my problem happens on 2.6.29 only, not 2.6.28.
>
> The Gentoo bug entry too is about a regression _after_ 2.6.28. :-)
> I.e. 2.6.28.y. are unaffected.  It's actually just the downstream
> duplicate of the kernel.org bug entry.
>
>> Either way, the unload problem with the module didn't happen in
>> 2.6.28.
>
> Interdependencies between ALSA modules have changed.  The Gentoo init
> scripts attempted to unload them in an order which deadlocked modprobe
> due to dependencies.  The fix for Gentoo is to just not unload the
> modules on system shutdown.  My Gentoo/amd64 Mac mini was affected by
> this too; fixed by userland update.
>
> (Added Cc to tiwai-l3A5Bk7waGM@public.gmane.org)
> --
> Stefan Richter
> -=====-=-=== -=-= -==-=
> http://arcgraph.de/sr/
> --
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/
>

With the imac(kernel 2.6.29)
/sbin/shutdown -h now   (works)
but
/sbin/reboot
hangs

-- 
Justin P. Mattock

Re: 2.6.29 on MacBook 2,1 fails to reboot (was Re: 2.6.29-git13: Reported regressions from 2.6.28)

[Justin Mattock]

On Tue, Apr 7, 2009 at 10:10 AM, Stefan Richter
<stefanr@s5r6.in-berlin.de> wrote:
> Trenton D. Adams wrote:
>> On Tue, Apr 7, 2009 at 10:16 AM, Stefan Richter
>> <stefanr@s5r6.in-berlin.de> wrote:
>>> Linus Torvalds wrote:
>>>> On Mon, 6 Apr 2009, Rafael J. Wysocki wrote:
>>>>> Bug-Entry    : http://bugzilla.kernel.org/show_bug.cgi?id=13018
>>>>> Subject              : 2.6.29 on MacBook 2,1 fails to reboot
> ...
>>>> The bug _sounds_ like some deadlock due to lock problems - the shutdown
>>>> path often triggers locks that no other path really cares about. And we
>>>> had some lock problems in the sound subsystem that got fixed post-2.6.28,
>>>> for example.
>>>>
>>>> And it looks like the problem is somewhere in sound shutdown:
>>>>
>>>> 12181 delete_module("snd_hda_codec", O_RDONLY|O_EXCL) = -1 EAGAIN (Resource temporarily unavailable) <0.000011>
>>>>
>>>> So commits like 91054598f794fb5d8a0b1e747ff8e2e8fc2115b3 ("ALSA: pcm_oss,
>>>> fix locking typo") might explain it.
> ...
>>> could it be the same as this one?
>>> http://bugzilla.kernel.org/show_bug.cgi?id=12321
>>> "System hangs when unloading alsa modules"
>>> http://bugs.gentoo.org/show_bug.cgi?id=253535
>>> "System hangs when unloading alsa modules on Kernel >2.6.28"
> ...
>> The first one looks similar, if not identical.  The second one
>> doesn't, because my problem happens on 2.6.29 only, not 2.6.28.
>
> The Gentoo bug entry too is about a regression _after_ 2.6.28. :-)
> I.e. 2.6.28.y. are unaffected.  It's actually just the downstream
> duplicate of the kernel.org bug entry.
>
>> Either way, the unload problem with the module didn't happen in
>> 2.6.28.
>
> Interdependencies between ALSA modules have changed.  The Gentoo init
> scripts attempted to unload them in an order which deadlocked modprobe
> due to dependencies.  The fix for Gentoo is to just not unload the
> modules on system shutdown.  My Gentoo/amd64 Mac mini was affected by
> this too; fixed by userland update.
>
> (Added Cc to tiwai@suse.de)
> --
> Stefan Richter
> -=====-=-=== -=-= -==-=
> http://arcgraph.de/sr/
> --
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/
>

With the imac(kernel 2.6.29)
/sbin/shutdown -h now   (works)
but
/sbin/reboot
hangs

-- 
Justin P. Mattock

Re: 2.6.29 on MacBook 2, 1 fails to reboot (was Re: 2.6.29-git13: Reported regressions from 2.6.28)

[Justin Mattock]

On Tue, Apr 7, 2009 at 10:10 AM, Stefan Richter
<stefanr@s5r6.in-berlin.de> wrote:
> Trenton D. Adams wrote:
>> On Tue, Apr 7, 2009 at 10:16 AM, Stefan Richter
>> <stefanr@s5r6.in-berlin.de> wrote:
>>> Linus Torvalds wrote:
>>>> On Mon, 6 Apr 2009, Rafael J. Wysocki wrote:
>>>>> Bug-Entry    : http://bugzilla.kernel.org/show_bug.cgi?id=13018
>>>>> Subject              : 2.6.29 on MacBook 2,1 fails to reboot
> ...
>>>> The bug _sounds_ like some deadlock due to lock problems - the shutdown
>>>> path often triggers locks that no other path really cares about. And we
>>>> had some lock problems in the sound subsystem that got fixed post-2.6.28,
>>>> for example.
>>>>
>>>> And it looks like the problem is somewhere in sound shutdown:
>>>>
>>>> 12181 delete_module("snd_hda_codec", O_RDONLY|O_EXCL) = -1 EAGAIN (Resource temporarily unavailable) <0.000011>
>>>>
>>>> So commits like 91054598f794fb5d8a0b1e747ff8e2e8fc2115b3 ("ALSA: pcm_oss,
>>>> fix locking typo") might explain it.
> ...
>>> could it be the same as this one?
>>> http://bugzilla.kernel.org/show_bug.cgi?id=12321
>>> "System hangs when unloading alsa modules"
>>> http://bugs.gentoo.org/show_bug.cgi?id=253535
>>> "System hangs when unloading alsa modules on Kernel >2.6.28"
> ...
>> The first one looks similar, if not identical.  The second one
>> doesn't, because my problem happens on 2.6.29 only, not 2.6.28.
>
> The Gentoo bug entry too is about a regression _after_ 2.6.28. :-)
> I.e. 2.6.28.y. are unaffected.  It's actually just the downstream
> duplicate of the kernel.org bug entry.
>
>> Either way, the unload problem with the module didn't happen in
>> 2.6.28.
>
> Interdependencies between ALSA modules have changed.  The Gentoo init
> scripts attempted to unload them in an order which deadlocked modprobe
> due to dependencies.  The fix for Gentoo is to just not unload the
> modules on system shutdown.  My Gentoo/amd64 Mac mini was affected by
> this too; fixed by userland update.
>
> (Added Cc to tiwai@suse.de)
> --
> Stefan Richter
> -=====-=-=== -=-= -==-=
> http://arcgraph.de/sr/
> --
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/
>

With the imac(kernel 2.6.29)
/sbin/shutdown -h now   (works)
but
/sbin/reboot
hangs

-- 
Justin P. Mattock

Re: 2.6.29 on MacBook 2,1 fails to reboot (was Re: 2.6.29-git13: Reported regressions from 2.6.28)

[Justin Mattock]

On Tue, Apr 7, 2009 at 10:10 AM, Stefan Richter
<stefanr-MtYdepGKPcBMYopoZt5u/LNAH6kLmebB@public.gmane.org> wrote:
> Trenton D. Adams wrote:
>> On Tue, Apr 7, 2009 at 10:16 AM, Stefan Richter
>> <stefanr-MtYdepGKPcBMYopoZt5u/LNAH6kLmebB@public.gmane.org> wrote:
>>> Linus Torvalds wrote:
>>>> On Mon, 6 Apr 2009, Rafael J. Wysocki wrote:
>>>>> Bug-Entry    : http://bugzilla.kernel.org/show_bug.cgi?id=13018
>>>>> Subject              : 2.6.29 on MacBook 2,1 fails to reboot
> ...
>>>> The bug _sounds_ like some deadlock due to lock problems - the shutdown
>>>> path often triggers locks that no other path really cares about. And we
>>>> had some lock problems in the sound subsystem that got fixed post-2.6.28,
>>>> for example.
>>>>
>>>> And it looks like the problem is somewhere in sound shutdown:
>>>>
>>>> 12181 delete_module("snd_hda_codec", O_RDONLY|O_EXCL) = -1 EAGAIN (Resource temporarily unavailable) <0.000011>
>>>>
>>>> So commits like 91054598f794fb5d8a0b1e747ff8e2e8fc2115b3 ("ALSA: pcm_oss,
>>>> fix locking typo") might explain it.
> ...
>>> could it be the same as this one?
>>> http://bugzilla.kernel.org/show_bug.cgi?id=12321
>>> "System hangs when unloading alsa modules"
>>> http://bugs.gentoo.org/show_bug.cgi?id=253535
>>> "System hangs when unloading alsa modules on Kernel >2.6.28"
> ...
>> The first one looks similar, if not identical.  The second one
>> doesn't, because my problem happens on 2.6.29 only, not 2.6.28.
>
> The Gentoo bug entry too is about a regression _after_ 2.6.28. :-)
> I.e. 2.6.28.y. are unaffected.  It's actually just the downstream
> duplicate of the kernel.org bug entry.
>
>> Either way, the unload problem with the module didn't happen in
>> 2.6.28.
>
> Interdependencies between ALSA modules have changed.  The Gentoo init
> scripts attempted to unload them in an order which deadlocked modprobe
> due to dependencies.  The fix for Gentoo is to just not unload the
> modules on system shutdown.  My Gentoo/amd64 Mac mini was affected by
> this too; fixed by userland update.
>
> (Added Cc to tiwai-l3A5Bk7waGM@public.gmane.org)
> --
> Stefan Richter
> -=====-=-=== -=-= -==-=
> http://arcgraph.de/sr/
> --
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/
>

With the imac(kernel 2.6.29)
/sbin/shutdown -h now   (works)
but
/sbin/reboot
hangs

-- 
Justin P. Mattock

Re: 2.6.29 on MacBook 2,1 fails to reboot (was Re: 2.6.29-git13: Reported regressions from 2.6.28)

[Trenton D. Adams]

On Tue, Apr 7, 2009 at 11:10 AM, Stefan Richter
<stefanr@s5r6.in-berlin.de> wrote:
> Trenton D. Adams wrote:
> Interdependencies between ALSA modules have changed.  The Gentoo init
> scripts attempted to unload them in an order which deadlocked modprobe
> due to dependencies.  The fix for Gentoo is to just not unload the
> modules on system shutdown.  My Gentoo/amd64 Mac mini was affected by
> this too; fixed by userland update.
>

While that is interesting, I am not seeing that problem on my Gentoo
box (the macbook), which is completely up-to-date.  2.6.28 works, and
2.6.29 doesn't.  Same init scripts, different kernels.

And sure, I could put a comment on the rmmod, in the init script, but
IMO that would be a hack around a _bug_.  Which is fine for me.  But,
is it worth leaving the issue in the kernel?

Re: 2.6.29 on MacBook 2,1 fails to reboot (was Re: 2.6.29-git13: Reported regressions from 2.6.28)

[Trenton D. Adams]

On Tue, Apr 7, 2009 at 11:10 AM, Stefan Richter
<stefanr@s5r6.in-berlin.de> wrote:
> Trenton D. Adams wrote:
> Interdependencies between ALSA modules have changed.  The Gentoo init
> scripts attempted to unload them in an order which deadlocked modprobe
> due to dependencies.  The fix for Gentoo is to just not unload the
> modules on system shutdown.  My Gentoo/amd64 Mac mini was affected by
> this too; fixed by userland update.
>

While that is interesting, I am not seeing that problem on my Gentoo
box (the macbook), which is completely up-to-date.  2.6.28 works, and
2.6.29 doesn't.  Same init scripts, different kernels.

And sure, I could put a comment on the rmmod, in the init script, but
IMO that would be a hack around a _bug_.  Which is fine for me.  But,
is it worth leaving the issue in the kernel?

Re: 2.6.29 on MacBook 2, 1 fails to reboot (was Re: 2.6.29-git13: Reported regressions from 2.6.28)

[Trenton D. Adams]

On Tue, Apr 7, 2009 at 11:10 AM, Stefan Richter
<stefanr@s5r6.in-berlin.de> wrote:
> Trenton D. Adams wrote:
> Interdependencies between ALSA modules have changed.  The Gentoo init
> scripts attempted to unload them in an order which deadlocked modprobe
> due to dependencies.  The fix for Gentoo is to just not unload the
> modules on system shutdown.  My Gentoo/amd64 Mac mini was affected by
> this too; fixed by userland update.
>

While that is interesting, I am not seeing that problem on my Gentoo
box (the macbook), which is completely up-to-date.  2.6.28 works, and
2.6.29 doesn't.  Same init scripts, different kernels.

And sure, I could put a comment on the rmmod, in the init script, but
IMO that would be a hack around a _bug_.  Which is fine for me.  But,
is it worth leaving the issue in the kernel?

Re: 2.6.29 on MacBook 2,1 fails to reboot (was Re: 2.6.29-git13: Reported regressions from 2.6.28)

[Stefan Richter]

Trenton D. Adams wrote:
> On Tue, Apr 7, 2009 at 11:10 AM, Stefan Richter
> <stefanr-MtYdepGKPcBMYopoZt5u/LNAH6kLmebB@public.gmane.org> wrote:
>>>> http://bugs.gentoo.org/show_bug.cgi?id=253535
>> Interdependencies between ALSA modules have changed.  The Gentoo init
>> scripts attempted to unload them in an order which deadlocked modprobe
>> due to dependencies.  The fix for Gentoo is to just not unload the
>> modules on system shutdown.  My Gentoo/amd64 Mac mini was affected by
>> this too; fixed by userland update.
>>
> 
> While that is interesting, I am not seeing that problem on my Gentoo
> box (the macbook), which is completely up-to-date.  2.6.28 works, and
> 2.6.29 doesn't.  Same init scripts, different kernels.

Note that the respective update changed /etc/conf.d/alsasound (a local
configuration file) to include
UNLOAD_ON_STOP="no"
KILLPROC_ON_STOP="no"
This change by update is not activated by a mere emerge; one needs to
incorporate that change with dispatch-conf or an equivalent method.
(Or simply edit the file to have these variables set to "no".)

> And sure, I could put a comment on the rmmod, in the init script, but
> IMO that would be a hack around a _bug_.  Which is fine for me.  But,
> is it worth leaving the issue in the kernel?

Is it a kernel issue if a script attempts to unload a busy module, then
fails to proceed?  I wouldn't think so.

But more importantly, is this init scripts related bug really what's
happening at your system?  Or do you actually experience an entirely
different bug?
-- 
Stefan Richter
-=====-=-=== -=-= -==-=
http://arcgraph.de/sr/

Re: 2.6.29 on MacBook 2,1 fails to reboot (was Re: 2.6.29-git13: Reported regressions from 2.6.28)

[Stefan Richter]

Trenton D. Adams wrote:
> On Tue, Apr 7, 2009 at 11:10 AM, Stefan Richter
> <stefanr@s5r6.in-berlin.de> wrote:
>>>> http://bugs.gentoo.org/show_bug.cgi?id=253535
>> Interdependencies between ALSA modules have changed.  The Gentoo init
>> scripts attempted to unload them in an order which deadlocked modprobe
>> due to dependencies.  The fix for Gentoo is to just not unload the
>> modules on system shutdown.  My Gentoo/amd64 Mac mini was affected by
>> this too; fixed by userland update.
>>
> 
> While that is interesting, I am not seeing that problem on my Gentoo
> box (the macbook), which is completely up-to-date.  2.6.28 works, and
> 2.6.29 doesn't.  Same init scripts, different kernels.

Note that the respective update changed /etc/conf.d/alsasound (a local
configuration file) to include
UNLOAD_ON_STOP="no"
KILLPROC_ON_STOP="no"
This change by update is not activated by a mere emerge; one needs to
incorporate that change with dispatch-conf or an equivalent method.
(Or simply edit the file to have these variables set to "no".)

> And sure, I could put a comment on the rmmod, in the init script, but
> IMO that would be a hack around a _bug_.  Which is fine for me.  But,
> is it worth leaving the issue in the kernel?

Is it a kernel issue if a script attempts to unload a busy module, then
fails to proceed?  I wouldn't think so.

But more importantly, is this init scripts related bug really what's
happening at your system?  Or do you actually experience an entirely
different bug?
-- 
Stefan Richter
-=====-=-=== -=-= -==-=
http://arcgraph.de/sr/

Re: 2.6.29 on MacBook 2, 1 fails to reboot (was Re: 2.6.29-git13: Reported regressions from 2.6.28)

[Stefan Richter]

Trenton D. Adams wrote:
> On Tue, Apr 7, 2009 at 11:10 AM, Stefan Richter
> <stefanr@s5r6.in-berlin.de> wrote:
>>>> http://bugs.gentoo.org/show_bug.cgi?id=253535
>> Interdependencies between ALSA modules have changed.  The Gentoo init
>> scripts attempted to unload them in an order which deadlocked modprobe
>> due to dependencies.  The fix for Gentoo is to just not unload the
>> modules on system shutdown.  My Gentoo/amd64 Mac mini was affected by
>> this too; fixed by userland update.
>>
> 
> While that is interesting, I am not seeing that problem on my Gentoo
> box (the macbook), which is completely up-to-date.  2.6.28 works, and
> 2.6.29 doesn't.  Same init scripts, different kernels.

Note that the respective update changed /etc/conf.d/alsasound (a local
configuration file) to include
UNLOAD_ON_STOP="no"
KILLPROC_ON_STOP="no"
This change by update is not activated by a mere emerge; one needs to
incorporate that change with dispatch-conf or an equivalent method.
(Or simply edit the file to have these variables set to "no".)

> And sure, I could put a comment on the rmmod, in the init script, but
> IMO that would be a hack around a _bug_.  Which is fine for me.  But,
> is it worth leaving the issue in the kernel?

Is it a kernel issue if a script attempts to unload a busy module, then
fails to proceed?  I wouldn't think so.

But more importantly, is this init scripts related bug really what's
happening at your system?  Or do you actually experience an entirely
different bug?
-- 
Stefan Richter
-=====-=-=== -=-= -==-=
http://arcgraph.de/sr/

Re: 2.6.29 on MacBook 2,1 fails to reboot (was Re: 2.6.29-git13: Reported regressions from 2.6.28)

[Trenton D. Adams]

On Tue, Apr 7, 2009 at 1:23 PM, Stefan Richter
<stefanr-MtYdepGKPcBMYopoZt5u/LNAH6kLmebB@public.gmane.org> wrote:
> Trenton D. Adams wrote:
>> On Tue, Apr 7, 2009 at 11:10 AM, Stefan Richter
>> <stefanr-MtYdepGKPcBMYopoZt5u/LNAH6kLmebB@public.gmane.org> wrote:
>>>>> http://bugs.gentoo.org/show_bug.cgi?id=253535
>>> Interdependencies between ALSA modules have changed.  The Gentoo init
>>> scripts attempted to unload them in an order which deadlocked modprobe
>>> due to dependencies.  The fix for Gentoo is to just not unload the
>>> modules on system shutdown.  My Gentoo/amd64 Mac mini was affected by
>>> this too; fixed by userland update.
>>>
>>
>> While that is interesting, I am not seeing that problem on my Gentoo
>> box (the macbook), which is completely up-to-date.  2.6.28 works, and
>> 2.6.29 doesn't.  Same init scripts, different kernels.
>
> Note that the respective update changed /etc/conf.d/alsasound (a local
> configuration file) to include
> UNLOAD_ON_STOP="no"
> KILLPROC_ON_STOP="no"
> This change by update is not activated by a mere emerge; one needs to
> incorporate that change with dispatch-conf or an equivalent method.
> (Or simply edit the file to have these variables set to "no".)

I run dispatch-conf every time I update.  It did not set it to no by
default.  I do see the option though.

>
>> And sure, I could put a comment on the rmmod, in the init script, but
>> IMO that would be a hack around a _bug_.  Which is fine for me.  But,
>> is it worth leaving the issue in the kernel?
>
> Is it a kernel issue if a script attempts to unload a busy module, then
> fails to proceed?  I wouldn't think so.

I don't know really.  It worked before, now it doesn't.  But, now I'm
recalling something you said earlier.  They are being done in the
wrong order.  The gentoo bug mentions the correct order.  I hadn't
realized that.

>
> But more importantly, is this init scripts related bug really what's
> happening at your system?  Or do you actually experience an entirely
> different bug?

It could be.  I will try it out when I get home from work, and get
back to you.  That would be cool if it was a simple init script
problem.  Cause then I don't have to do anymore git bisects. ;)

> --
> Stefan Richter
> -=====-=-=== -=-= -==-=
> http://arcgraph.de/sr/
>

Re: 2.6.29 on MacBook 2,1 fails to reboot (was Re: 2.6.29-git13: Reported regressions from 2.6.28)

[Trenton D. Adams]

On Tue, Apr 7, 2009 at 1:23 PM, Stefan Richter
<stefanr@s5r6.in-berlin.de> wrote:
> Trenton D. Adams wrote:
>> On Tue, Apr 7, 2009 at 11:10 AM, Stefan Richter
>> <stefanr@s5r6.in-berlin.de> wrote:
>>>>> http://bugs.gentoo.org/show_bug.cgi?id=253535
>>> Interdependencies between ALSA modules have changed.  The Gentoo init
>>> scripts attempted to unload them in an order which deadlocked modprobe
>>> due to dependencies.  The fix for Gentoo is to just not unload the
>>> modules on system shutdown.  My Gentoo/amd64 Mac mini was affected by
>>> this too; fixed by userland update.
>>>
>>
>> While that is interesting, I am not seeing that problem on my Gentoo
>> box (the macbook), which is completely up-to-date.  2.6.28 works, and
>> 2.6.29 doesn't.  Same init scripts, different kernels.
>
> Note that the respective update changed /etc/conf.d/alsasound (a local
> configuration file) to include
> UNLOAD_ON_STOP="no"
> KILLPROC_ON_STOP="no"
> This change by update is not activated by a mere emerge; one needs to
> incorporate that change with dispatch-conf or an equivalent method.
> (Or simply edit the file to have these variables set to "no".)

I run dispatch-conf every time I update.  It did not set it to no by
default.  I do see the option though.

>
>> And sure, I could put a comment on the rmmod, in the init script, but
>> IMO that would be a hack around a _bug_.  Which is fine for me.  But,
>> is it worth leaving the issue in the kernel?
>
> Is it a kernel issue if a script attempts to unload a busy module, then
> fails to proceed?  I wouldn't think so.

I don't know really.  It worked before, now it doesn't.  But, now I'm
recalling something you said earlier.  They are being done in the
wrong order.  The gentoo bug mentions the correct order.  I hadn't
realized that.

>
> But more importantly, is this init scripts related bug really what's
> happening at your system?  Or do you actually experience an entirely
> different bug?

It could be.  I will try it out when I get home from work, and get
back to you.  That would be cool if it was a simple init script
problem.  Cause then I don't have to do anymore git bisects. ;)

> --
> Stefan Richter
> -=====-=-=== -=-= -==-=
> http://arcgraph.de/sr/
>

Re: 2.6.29 on MacBook 2, 1 fails to reboot (was Re: 2.6.29-git13: Reported regressions from 2.6.28)

[Trenton D. Adams]

On Tue, Apr 7, 2009 at 1:23 PM, Stefan Richter
<stefanr@s5r6.in-berlin.de> wrote:
> Trenton D. Adams wrote:
>> On Tue, Apr 7, 2009 at 11:10 AM, Stefan Richter
>> <stefanr@s5r6.in-berlin.de> wrote:
>>>>> http://bugs.gentoo.org/show_bug.cgi?id=253535
>>> Interdependencies between ALSA modules have changed.  The Gentoo init
>>> scripts attempted to unload them in an order which deadlocked modprobe
>>> due to dependencies.  The fix for Gentoo is to just not unload the
>>> modules on system shutdown.  My Gentoo/amd64 Mac mini was affected by
>>> this too; fixed by userland update.
>>>
>>
>> While that is interesting, I am not seeing that problem on my Gentoo
>> box (the macbook), which is completely up-to-date.  2.6.28 works, and
>> 2.6.29 doesn't.  Same init scripts, different kernels.
>
> Note that the respective update changed /etc/conf.d/alsasound (a local
> configuration file) to include
> UNLOAD_ON_STOP="no"
> KILLPROC_ON_STOP="no"
> This change by update is not activated by a mere emerge; one needs to
> incorporate that change with dispatch-conf or an equivalent method.
> (Or simply edit the file to have these variables set to "no".)

I run dispatch-conf every time I update.  It did not set it to no by
default.  I do see the option though.

>
>> And sure, I could put a comment on the rmmod, in the init script, but
>> IMO that would be a hack around a _bug_.  Which is fine for me.  But,
>> is it worth leaving the issue in the kernel?
>
> Is it a kernel issue if a script attempts to unload a busy module, then
> fails to proceed?  I wouldn't think so.

I don't know really.  It worked before, now it doesn't.  But, now I'm
recalling something you said earlier.  They are being done in the
wrong order.  The gentoo bug mentions the correct order.  I hadn't
realized that.

>
> But more importantly, is this init scripts related bug really what's
> happening at your system?  Or do you actually experience an entirely
> different bug?

It could be.  I will try it out when I get home from work, and get
back to you.  That would be cool if it was a simple init script
problem.  Cause then I don't have to do anymore git bisects. ;)

> --
> Stefan Richter
> -=====-=-=== -=-= -==-=
> http://arcgraph.de/sr/
>

Re: 2.6.29 on MacBook 2,1 fails to reboot (was Re: 2.6.29-git13: Reported regressions from 2.6.28)

[Trenton D. Adams]

On Tue, Apr 7, 2009 at 1:23 PM, Stefan Richter
<stefanr-MtYdepGKPcBMYopoZt5u/LNAH6kLmebB@public.gmane.org> wrote:
> Trenton D. Adams wrote:
>> On Tue, Apr 7, 2009 at 11:10 AM, Stefan Richter
>> <stefanr-MtYdepGKPcBMYopoZt5u/LNAH6kLmebB@public.gmane.org> wrote:
>>>>> http://bugs.gentoo.org/show_bug.cgi?id=253535
>>> Interdependencies between ALSA modules have changed.  The Gentoo init
>>> scripts attempted to unload them in an order which deadlocked modprobe
>>> due to dependencies.  The fix for Gentoo is to just not unload the
>>> modules on system shutdown.  My Gentoo/amd64 Mac mini was affected by
>>> this too; fixed by userland update.
>>>
>>
>> While that is interesting, I am not seeing that problem on my Gentoo
>> box (the macbook), which is completely up-to-date.  2.6.28 works, and
>> 2.6.29 doesn't.  Same init scripts, different kernels.
>
> Note that the respective update changed /etc/conf.d/alsasound (a local
> configuration file) to include
> UNLOAD_ON_STOP="no"
> KILLPROC_ON_STOP="no"
> This change by update is not activated by a mere emerge; one needs to
> incorporate that change with dispatch-conf or an equivalent method.
> (Or simply edit the file to have these variables set to "no".)

I run dispatch-conf every time I update.  It did not set it to no by
default.  I do see the option though.

>
>> And sure, I could put a comment on the rmmod, in the init script, but
>> IMO that would be a hack around a _bug_.  Which is fine for me.  But,
>> is it worth leaving the issue in the kernel?
>
> Is it a kernel issue if a script attempts to unload a busy module, then
> fails to proceed?  I wouldn't think so.

I don't know really.  It worked before, now it doesn't.  But, now I'm
recalling something you said earlier.  They are being done in the
wrong order.  The gentoo bug mentions the correct order.  I hadn't
realized that.

>
> But more importantly, is this init scripts related bug really what's
> happening at your system?  Or do you actually experience an entirely
> different bug?

It could be.  I will try it out when I get home from work, and get
back to you.  That would be cool if it was a simple init script
problem.  Cause then I don't have to do anymore git bisects. ;)

> --
> Stefan Richter
> -=====-=-=== -=-= -==-=
> http://arcgraph.de/sr/
>

Re: [Bug #12871] usb bluetooth crashes system

[Pavel Machek]

On Tue 2009-04-07 09:16:39, Marcel Holtmann wrote:
> Hi Rafael,
> 
> > This message has been generated automatically as a part of a report
> > of recent regressions.
> > 
> > The following bug entry is on the current list of known regressions
> > from 2.6.28.  Please verify if it still should be listed and let me know
> > (either way).
> > 
> > 
> > Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12871
> > Subject		: usb bluetooth crashes system
> > Submitter	: Pavel Machek <pavel@ucw.cz>
> > Date		: 2009-03-10 11:23 (28 days old)
> > References	: http://marc.info/?l=linux-kernel&m=123668450400940&w=4
> 
> please have this re-tested against 2.6.30-rc1 then we can work on
> figuring out which patch might have fixed it. I think it is fixed now,
> but I could be also wrong here.

2.6.30-rc1 does not seem to be out (according to kernel.org); I can
test the latest git if that helps?
									Pavel
-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html

Re: [Bug #12871] usb bluetooth crashes system

[Pavel Machek]

On Tue 2009-04-07 09:16:39, Marcel Holtmann wrote:
> Hi Rafael,
> 
> > This message has been generated automatically as a part of a report
> > of recent regressions.
> > 
> > The following bug entry is on the current list of known regressions
> > from 2.6.28.  Please verify if it still should be listed and let me know
> > (either way).
> > 
> > 
> > Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12871
> > Subject		: usb bluetooth crashes system
> > Submitter	: Pavel Machek <pavel-+ZI9xUNit7I@public.gmane.org>
> > Date		: 2009-03-10 11:23 (28 days old)
> > References	: http://marc.info/?l=linux-kernel&m=123668450400940&w=4
> 
> please have this re-tested against 2.6.30-rc1 then we can work on
> figuring out which patch might have fixed it. I think it is fixed now,
> but I could be also wrong here.

2.6.30-rc1 does not seem to be out (according to kernel.org); I can
test the latest git if that helps?
									Pavel
-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html

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

[Rafael J. Wysocki]

On Tuesday 07 April 2009, Marcel Holtmann wrote:
> Hi Rafael,

Hi,

> > This message has been generated automatically as a part of a report
> > of recent regressions.
> > 
> > The following bug entry is on the current list of known regressions
> > from 2.6.28.  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" <maciej.rutecki@gmail.com>
> > Date		: 2009-01-13 18:34 (84 days old)
> > References	: http://marc.info/?l=linux-kernel&m=123187185426236&w=4
> 
> I prefer to have this checked against 2.6.30-rc1 once Linus released
> that one. I think that I know the root cause for this one and it is
> actually a hardware/firmware bug. Some Bluetooth dongles expect to have
> the interrupt and bulk URBs available at the same time. Otherwise they
> do pee in their pants.

Works for me. :-)

Thanks,
Rafael

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

[Rafael J. Wysocki]

On Tuesday 07 April 2009, Marcel Holtmann wrote:
> Hi Rafael,

Hi,

> > This message has been generated automatically as a part of a report
> > of recent regressions.
> > 
> > The following bug entry is on the current list of known regressions
> > from 2.6.28.  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" <maciej.rutecki-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
> > Date		: 2009-01-13 18:34 (84 days old)
> > References	: http://marc.info/?l=linux-kernel&m=123187185426236&w=4
> 
> I prefer to have this checked against 2.6.30-rc1 once Linus released
> that one. I think that I know the root cause for this one and it is
> actually a hardware/firmware bug. Some Bluetooth dongles expect to have
> the interrupt and bulk URBs available at the same time. Otherwise they
> do pee in their pants.

Works for me. :-)

Thanks,
Rafael

Re: [Bug #12670] BUG: unable to handle kernel paging request at pin_to_kill+0x21

[Rafael J. Wysocki]

On Tuesday 07 April 2009, Alessandro Bono wrote:
> On Mon, 2009-04-06 at 21:05 +0200, Rafael J. Wysocki wrote:
> > This message has been generated automatically as a part of a report
> > of recent regressions.
> > 
> > The following bug entry is on the current list of known regressions
> > from 2.6.28.  Please verify if it still should be listed and let me know
> > (either way).
> > 
> > 
> > Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12670
> > Subject		: BUG: unable to handle kernel paging request at pin_to_kill+0x21
> > Submitter	: Alessandro Bono <alessandro.bono@gmail.com>
> > Date		: 2009-02-08 11:04 (58 days old)
> > References	: http://marc.info/?l=linux-kernel&m=123409113223833&w=4
> > 
> > 
> HI
> 
> please close this bug
> I'm not able to reproduce and at time of this problem my notebook has
> broken memory modules

Thanks, closed.

Rafael

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

[Rafael J. Wysocki]

On Tuesday 07 April 2009, Len Brown wrote:
> 
> On Mon, 6 Apr 2009, Rafael J. Wysocki wrote:
> 
> > This message has been generated automatically as a part of a report
> > of recent regressions.
> > 
> > The following bug entry is on the current list of known regressions
> > from 2.6.28.  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 <nico-linux-20090213@schottelius.org>
> > Date		: 2009-02-13 9:33 (53 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
> 
> > Handled-By	: Len Brown <lenb@kernel.org>
> 
> Handled-By	: Eric Anholt <eric@anholt.net>

Updated.

Thanks,
Rafael

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

[Rafael J. Wysocki]

On Tuesday 07 April 2009, Len Brown wrote:
> 
> On Mon, 6 Apr 2009, Rafael J. Wysocki wrote:
> 
> > This message has been generated automatically as a part of a report
> > of recent regressions.
> > 
> > The following bug entry is on the current list of known regressions
> > from 2.6.28.  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 <nico-linux-20090213-xuaVFQXs+5hIG4jRRZ66WA@public.gmane.org>
> > Date		: 2009-02-13 9:33 (53 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
> 
> > Handled-By	: Len Brown <lenb-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
> 
> Handled-By	: Eric Anholt <eric-WhKQ6XTQaPysTnJN9+BGXg@public.gmane.org>

Updated.

Thanks,
Rafael

Re: [Bug #13019] /proc/<pid>/maps offset output broken in 2.6.29

[Rafael J. Wysocki]

On Tuesday 07 April 2009, Hugh Dickins wrote:
> On Mon, 6 Apr 2009, Rafael J. Wysocki wrote:
> > 
> > Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13019
> > Subject		: /proc/<pid>/maps offset output broken in 2.6.29
> > Submitter	: "Chris Friesen" <cfriesen@nortel.com>
> > Date		: 2009-04-01 23:18 (6 days old)
> > References	: http://marc.info/?l=linuxppc-embedded&m=123862902916059&w=4
> > Handled-By	: Hugh Dickins <hugh@veritas.com>
> 
> No, this shouldn't be listed as a regression from 2.6.28: if it's to be
> counted as a regression at all, it's 2.6.23's regression from 2.6.22.
> (We're about to deal with it in 2.6.30, but hardly worth backporting.)

Thanks, dropped from the list already.

Best,
Rafael

Re: [Bug #13019] /proc/<pid>/maps offset output broken in 2.6.29

[Rafael J. Wysocki]

On Tuesday 07 April 2009, Hugh Dickins wrote:
> On Mon, 6 Apr 2009, Rafael J. Wysocki wrote:
> > 
> > Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13019
> > Subject		: /proc/<pid>/maps offset output broken in 2.6.29
> > Submitter	: "Chris Friesen" <cfriesen-ZIRUuHA3oDzQT0dZR+AlfA@public.gmane.org>
> > Date		: 2009-04-01 23:18 (6 days old)
> > References	: http://marc.info/?l=linuxppc-embedded&m=123862902916059&w=4
> > Handled-By	: Hugh Dickins <hugh-DTz5qymZ9yRBDgjK7y7TUQ@public.gmane.org>
> 
> No, this shouldn't be listed as a regression from 2.6.28: if it's to be
> counted as a regression at all, it's 2.6.23's regression from 2.6.22.
> (We're about to deal with it in 2.6.30, but hardly worth backporting.)

Thanks, dropped from the list already.

Best,
Rafael

Re: [Bug #13015] pppoe over ethernet

[Rafael J. Wysocki]

On Tuesday 07 April 2009, Cyrill Gorcunov wrote:
> On 4/7/09, Detlef Tschirschky <detlef.tschirschky@gmx.de> wrote:
> > On Tue, 7 Apr 2009, Cyrill Gorcunov wrote:
> >
> >> On 4/6/09, Rafael J. Wysocki wrote:
> >
> >>> Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13015
> >>> Subject	: pppoe over ethernet
> >
> >> I expect the issue is inspered by network problem found in plain
> >> 2.6.29. Detlef could you confirm the problem is still active in
> >> 2.6.29.1 or in current -git mainline?
> >
> > Moin Cyrill,
> >
> > 2.6.29.1 is running fine for me. Can't find any network problems in
> > 2.6.29.1 now.
> >
> > Thanks and regards
> >
> > Detlef
> >
> >
> Thanks a lot, Detlef!
> Rafael, i guess we could close the bug.

OK, closed.

Thanks,
Rafael

Re: [Bug #13015] pppoe over ethernet

[Rafael J. Wysocki]

On Tuesday 07 April 2009, Cyrill Gorcunov wrote:
> On 4/7/09, Detlef Tschirschky <detlef.tschirschky-Mmb7MZpHnFY@public.gmane.org> wrote:
> > On Tue, 7 Apr 2009, Cyrill Gorcunov wrote:
> >
> >> On 4/6/09, Rafael J. Wysocki wrote:
> >
> >>> Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13015
> >>> Subject	: pppoe over ethernet
> >
> >> I expect the issue is inspered by network problem found in plain
> >> 2.6.29. Detlef could you confirm the problem is still active in
> >> 2.6.29.1 or in current -git mainline?
> >
> > Moin Cyrill,
> >
> > 2.6.29.1 is running fine for me. Can't find any network problems in
> > 2.6.29.1 now.
> >
> > Thanks and regards
> >
> > Detlef
> >
> >
> Thanks a lot, Detlef!
> Rafael, i guess we could close the bug.

OK, closed.

Thanks,
Rafael

Re: [Bug #12870] 2.6.29-rc "TKIP: replay detected" regression

[Rafael J. Wysocki]

On Tuesday 07 April 2009, Hugh Dickins wrote:
> On Mon, 6 Apr 2009, Rafael J. Wysocki wrote:
> > 
> > Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12870
> > Subject		: 2.6.29-rc "TKIP: replay detected" regression
> > Submitter	: Hugh Dickins <hugh@veritas.com>
> > Date		: 2009-03-11 12:07 (27 days old)
> > References	: http://marc.info/?l=linux-kernel&m=123677337219148&w=4
> > Handled-By	: "John W. Linville" <linville@tuxdriver.com>
> > Patch		: http://marc.info/?l=linux-wireless&m=123678463704691&w=2
> 
> John's fix went into 2.6.29 final: please remove this regression now.

Done.

Thanks,
Rafael

Re: [Bug #12870] 2.6.29-rc "TKIP: replay detected" regression

[Rafael J. Wysocki]

On Tuesday 07 April 2009, Hugh Dickins wrote:
> On Mon, 6 Apr 2009, Rafael J. Wysocki wrote:
> > 
> > Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12870
> > Subject		: 2.6.29-rc "TKIP: replay detected" regression
> > Submitter	: Hugh Dickins <hugh-DTz5qymZ9yRBDgjK7y7TUQ@public.gmane.org>
> > Date		: 2009-03-11 12:07 (27 days old)
> > References	: http://marc.info/?l=linux-kernel&m=123677337219148&w=4
> > Handled-By	: "John W. Linville" <linville-2XuSBdqkA4R54TAoqtyWWQ@public.gmane.org>
> > Patch		: http://marc.info/?l=linux-wireless&m=123678463704691&w=2
> 
> John's fix went into 2.6.29 final: please remove this regression now.

Done.

Thanks,
Rafael

Re: [Bug #13018] 2.6.29 on MacBook 2,1 fails to reboot

[Rafael J. Wysocki]

On Tuesday 07 April 2009, Trenton D. Adams wrote:
> On Mon, Apr 6, 2009 at 8:13 PM, Trenton D. Adams
> <trenton.d.adams@gmail.com> wrote:
> > Hi Rafael,
> >
> > Yes, it is still a problem.  I have identified it as far down to being
> > an alsa problem.  Please follow the other thread related to this.  I
> 
> Oops, sorry, I should make clear that it is not an alsa problem
> specifically, but an alsa hda-intel driver issue, which is related to
> alsa.

OK, thanks for the update.

Rafael

Re: [Bug #13018] 2.6.29 on MacBook 2,1 fails to reboot

[Rafael J. Wysocki]

On Tuesday 07 April 2009, Trenton D. Adams wrote:
> On Mon, Apr 6, 2009 at 8:13 PM, Trenton D. Adams
> <trenton.d.adams-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:
> > Hi Rafael,
> >
> > Yes, it is still a problem.  I have identified it as far down to being
> > an alsa problem.  Please follow the other thread related to this.  I
> 
> Oops, sorry, I should make clear that it is not an alsa problem
> specifically, but an alsa hda-intel driver issue, which is related to
> alsa.

OK, thanks for the update.

Rafael

Re: [Bug #13018] 2.6.29 on MacBook 2,1 fails to reboot

[Trenton D. Adams]

Also, someone named Stefan has been discussing it with me as well.
See the other macbook thread.

On Tue, Apr 7, 2009 at 3:30 PM, Rafael J. Wysocki <rjw@sisk.pl> wrote:
> On Tuesday 07 April 2009, Trenton D. Adams wrote:
>> On Mon, Apr 6, 2009 at 8:13 PM, Trenton D. Adams
>> <trenton.d.adams@gmail.com> wrote:
>> > Hi Rafael,
>> >
>> > Yes, it is still a problem.  I have identified it as far down to being
>> > an alsa problem.  Please follow the other thread related to this.  I
>>
>> Oops, sorry, I should make clear that it is not an alsa problem
>> specifically, but an alsa hda-intel driver issue, which is related to
>> alsa.
>
> OK, thanks for the update.
>
> Rafael
> --
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/
>

Re: [Bug #13018] 2.6.29 on MacBook 2,1 fails to reboot

[Trenton D. Adams]

Also, someone named Stefan has been discussing it with me as well.
See the other macbook thread.

On Tue, Apr 7, 2009 at 3:30 PM, Rafael J. Wysocki <rjw-KKrjLPT3xs0@public.gmane.org> wrote:
> On Tuesday 07 April 2009, Trenton D. Adams wrote:
>> On Mon, Apr 6, 2009 at 8:13 PM, Trenton D. Adams
>> <trenton.d.adams-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:
>> > Hi Rafael,
>> >
>> > Yes, it is still a problem.  I have identified it as far down to being
>> > an alsa problem.  Please follow the other thread related to this.  I
>>
>> Oops, sorry, I should make clear that it is not an alsa problem
>> specifically, but an alsa hda-intel driver issue, which is related to
>> alsa.
>
> OK, thanks for the update.
>
> Rafael
> --
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/
>

Re: 2.6.29-git13: Reported regressions from 2.6.28

[Rafael J. Wysocki]

On Tuesday 07 April 2009, Ilpo Järvinen wrote:
> On Mon, 6 Apr 2009, Rafael J. Wysocki wrote:
> 
> > Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12867
> > Subject		: 2.6.29-rc7 broke r8169 MAC on Thecus n2100 ARM board
> > Submitter	: Mikael Pettersson <mikpe@it.uu.se>
> > Date		: 2009-03-09 20:29 (29 days old)
> > References	: http://marc.info/?l=linux-kernel&m=123663065403760&w=4
> > Handled-By	: Francois Romieu <romieu@fr.zoreil.com>
> 
> I think this was fixed in the mainline by revert
> ea8dbdd17099a9a5864ebd4c87e01e657b19c7ab.

Thanks, closed.

Rafael

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

[Bob Copeland]

On Tue, Apr 07, 2009 at 12:03:45PM +0200, Johannes Berg wrote:
> 
> > Anyway here's a patch to buy some time.  Johannes, would this be
> > an acceptable band-aid for now?
> 
> This is going to make it print two warnings for one occurrence of the
> problem though. I'd much prefer to put something into minstrel.c to
> catch when _it_ returns bogus values and in that case return 0, that way
> at least the bandaid is restricted to the code it patches up.

Ok, then maybe something like this?

I think this covers most of the bases: if the driver is returning crap or
the ->cb gets corrupted, it'll get caught in tx_status.  If minstrel
stuffs a -1 in the first slot for any other reason we'll get a warning
before get_tx_rate and a hopefully valid index gets substituted.

diff --git a/net/mac80211/rc80211_minstrel.c b/net/mac80211/rc80211_minstrel.c
index 3824990..1cf7152 100644
--- a/net/mac80211/rc80211_minstrel.c
+++ b/net/mac80211/rc80211_minstrel.c
@@ -181,6 +181,11 @@ minstrel_tx_status(void *priv, struct ieee80211_supported_band *sband,
 		if (ar[i].idx < 0)
 			break;
 
+		if (WARN(ar[i].idx >= mi->n_rates,
+		    "minstrel: invalid rate report %d (n=%d)\n",
+		    ar[i].idx, mi->n_rates))
+			break;
+
 		ndx = rix_to_ndx(mi, ar[i].idx);
 		mi->r[ndx].attempts += ar[i].count;
 
@@ -328,7 +333,7 @@ minstrel_get_rate(void *priv, struct ieee80211_sta *sta,
 			ar[0].count = mp->max_retry;
 		ar[1].idx = mi->lowest_rix;
 		ar[1].count = mp->max_retry;
-		return;
+		goto done;
 	}
 
 	/* MRR setup */
@@ -346,6 +351,10 @@ minstrel_get_rate(void *priv, struct ieee80211_sta *sta,
 		ar[i].idx = mi->r[mrr_ndx[i - 1]].rix;
 		ar[i].count = mi->r[mrr_ndx[i - 1]].adjusted_retry_count;
 	}
+
+done:
+	if (WARN_ON(ar[0].idx < 0))
+		ar[0].idx = rate_lowest_index(sband, sta);
 }
 
 

-- 
Bob Copeland %% www.bobcopeland.com

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

[Bob Copeland]

On Tue, Apr 07, 2009 at 12:03:45PM +0200, Johannes Berg wrote:
> 
> > Anyway here's a patch to buy some time.  Johannes, would this be
> > an acceptable band-aid for now?
> 
> This is going to make it print two warnings for one occurrence of the
> problem though. I'd much prefer to put something into minstrel.c to
> catch when _it_ returns bogus values and in that case return 0, that way
> at least the bandaid is restricted to the code it patches up.

Ok, then maybe something like this?

I think this covers most of the bases: if the driver is returning crap or
the ->cb gets corrupted, it'll get caught in tx_status.  If minstrel
stuffs a -1 in the first slot for any other reason we'll get a warning
before get_tx_rate and a hopefully valid index gets substituted.

diff --git a/net/mac80211/rc80211_minstrel.c b/net/mac80211/rc80211_minstrel.c
index 3824990..1cf7152 100644
--- a/net/mac80211/rc80211_minstrel.c
+++ b/net/mac80211/rc80211_minstrel.c
@@ -181,6 +181,11 @@ minstrel_tx_status(void *priv, struct ieee80211_supported_band *sband,
 		if (ar[i].idx < 0)
 			break;
 
+		if (WARN(ar[i].idx >= mi->n_rates,
+		    "minstrel: invalid rate report %d (n=%d)\n",
+		    ar[i].idx, mi->n_rates))
+			break;
+
 		ndx = rix_to_ndx(mi, ar[i].idx);
 		mi->r[ndx].attempts += ar[i].count;
 
@@ -328,7 +333,7 @@ minstrel_get_rate(void *priv, struct ieee80211_sta *sta,
 			ar[0].count = mp->max_retry;
 		ar[1].idx = mi->lowest_rix;
 		ar[1].count = mp->max_retry;
-		return;
+		goto done;
 	}
 
 	/* MRR setup */
@@ -346,6 +351,10 @@ minstrel_get_rate(void *priv, struct ieee80211_sta *sta,
 		ar[i].idx = mi->r[mrr_ndx[i - 1]].rix;
 		ar[i].count = mi->r[mrr_ndx[i - 1]].adjusted_retry_count;
 	}
+
+done:
+	if (WARN_ON(ar[0].idx < 0))
+		ar[0].idx = rate_lowest_index(sband, sta);
 }
 
 

-- 
Bob Copeland %% www.bobcopeland.com

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

[Johannes Berg]

[-- Attachment #1: Type: text/plain, Size: 1498 bytes --]

On Tue, 2009-04-07 at 20:46 -0400, Bob Copeland wrote:
> On Tue, Apr 07, 2009 at 12:03:45PM +0200, Johannes Berg wrote:
> > 
> > > Anyway here's a patch to buy some time.  Johannes, would this be
> > > an acceptable band-aid for now?
> > 
> > This is going to make it print two warnings for one occurrence of the
> > problem though. I'd much prefer to put something into minstrel.c to
> > catch when _it_ returns bogus values and in that case return 0, that way
> > at least the bandaid is restricted to the code it patches up.
> 
> Ok, then maybe something like this?
> 
> I think this covers most of the bases: if the driver is returning crap or
> the ->cb gets corrupted, it'll get caught in tx_status.  If minstrel
> stuffs a -1 in the first slot for any other reason we'll get a warning
> before get_tx_rate and a hopefully valid index gets substituted.

Yeah, that looks nicer, thanks.

> diff --git a/net/mac80211/rc80211_minstrel.c b/net/mac80211/rc80211_minstrel.c
> index 3824990..1cf7152 100644
> --- a/net/mac80211/rc80211_minstrel.c
> +++ b/net/mac80211/rc80211_minstrel.c
> @@ -181,6 +181,11 @@ minstrel_tx_status(void *priv, struct ieee80211_supported_band *sband,
>  		if (ar[i].idx < 0)
>  			break;
>  
> +		if (WARN(ar[i].idx >= mi->n_rates,
> +		    "minstrel: invalid rate report %d (n=%d)\n",
> +		    ar[i].idx, mi->n_rates))
> +			break;

It might be easier to print this in hex -- that way things like 0x6b are
more apparent?

johannes

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

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

[Johannes Berg]

[-- Attachment #1: Type: text/plain, Size: 1498 bytes --]

On Tue, 2009-04-07 at 20:46 -0400, Bob Copeland wrote:
> On Tue, Apr 07, 2009 at 12:03:45PM +0200, Johannes Berg wrote:
> > 
> > > Anyway here's a patch to buy some time.  Johannes, would this be
> > > an acceptable band-aid for now?
> > 
> > This is going to make it print two warnings for one occurrence of the
> > problem though. I'd much prefer to put something into minstrel.c to
> > catch when _it_ returns bogus values and in that case return 0, that way
> > at least the bandaid is restricted to the code it patches up.
> 
> Ok, then maybe something like this?
> 
> I think this covers most of the bases: if the driver is returning crap or
> the ->cb gets corrupted, it'll get caught in tx_status.  If minstrel
> stuffs a -1 in the first slot for any other reason we'll get a warning
> before get_tx_rate and a hopefully valid index gets substituted.

Yeah, that looks nicer, thanks.

> diff --git a/net/mac80211/rc80211_minstrel.c b/net/mac80211/rc80211_minstrel.c
> index 3824990..1cf7152 100644
> --- a/net/mac80211/rc80211_minstrel.c
> +++ b/net/mac80211/rc80211_minstrel.c
> @@ -181,6 +181,11 @@ minstrel_tx_status(void *priv, struct ieee80211_supported_band *sband,
>  		if (ar[i].idx < 0)
>  			break;
>  
> +		if (WARN(ar[i].idx >= mi->n_rates,
> +		    "minstrel: invalid rate report %d (n=%d)\n",
> +		    ar[i].idx, mi->n_rates))
> +			break;

It might be easier to print this in hex -- that way things like 0x6b are
more apparent?

johannes

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

Re: 2.6.29 on MacBook 2,1 fails to reboot (was Re: 2.6.29-git13: Reported regressions from 2.6.28)

[Trenton D. Adams]

On Tue, Apr 7, 2009 at 2:52 PM, Trenton D. Adams
<trenton.d.adams@gmail.com> wrote:
> On Tue, Apr 7, 2009 at 1:23 PM, Stefan Richter
> <stefanr@s5r6.in-berlin.de> wrote:
>>
>> But more importantly, is this init scripts related bug really what's
>> happening at your system?  Or do you actually experience an entirely
>> different bug?
>
> It could be.  I will try it out when I get home from work, and get
> back to you.  That would be cool if it was a simple init script
> problem.  Cause then I don't have to do anymore git bisects. ;)

Yes, the order is what causes this, you can close the bug.

Sorry for wasting everyone's time.  I thought it was a kernel bug
because I had not needed to update my gentoo system to make it happen.

Thanks.
--
To unsubscribe from this list: send the line "unsubscribe linux-acpi" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Re: 2.6.29 on MacBook 2,1 fails to reboot (was Re: 2.6.29-git13: Reported regressions from 2.6.28)

[Trenton D. Adams]

On Tue, Apr 7, 2009 at 2:52 PM, Trenton D. Adams
<trenton.d.adams@gmail.com> wrote:
> On Tue, Apr 7, 2009 at 1:23 PM, Stefan Richter
> <stefanr@s5r6.in-berlin.de> wrote:
>>
>> But more importantly, is this init scripts related bug really what's
>> happening at your system?  Or do you actually experience an entirely
>> different bug?
>
> It could be.  I will try it out when I get home from work, and get
> back to you.  That would be cool if it was a simple init script
> problem.  Cause then I don't have to do anymore git bisects. ;)

Yes, the order is what causes this, you can close the bug.

Sorry for wasting everyone's time.  I thought it was a kernel bug
because I had not needed to update my gentoo system to make it happen.

Thanks.

Re: 2.6.29 on MacBook 2, 1 fails to reboot (was Re: 2.6.29-git13: Reported regressions from 2.6.28)

[Trenton D. Adams]

On Tue, Apr 7, 2009 at 2:52 PM, Trenton D. Adams
<trenton.d.adams@gmail.com> wrote:
> On Tue, Apr 7, 2009 at 1:23 PM, Stefan Richter
> <stefanr@s5r6.in-berlin.de> wrote:
>>
>> But more importantly, is this init scripts related bug really what's
>> happening at your system?  Or do you actually experience an entirely
>> different bug?
>
> It could be.  I will try it out when I get home from work, and get
> back to you.  That would be cool if it was a simple init script
> problem.  Cause then I don't have to do anymore git bisects. ;)

Yes, the order is what causes this, you can close the bug.

Sorry for wasting everyone's time.  I thought it was a kernel bug
because I had not needed to update my gentoo system to make it happen.

Thanks.

Re: 2.6.29 on MacBook 2,1 fails to reboot (was Re: 2.6.29-git13: Reported regressions from 2.6.28)

[Trenton D. Adams]

On Tue, Apr 7, 2009 at 2:52 PM, Trenton D. Adams
<trenton.d.adams@gmail.com> wrote:
> On Tue, Apr 7, 2009 at 1:23 PM, Stefan Richter
> <stefanr@s5r6.in-berlin.de> wrote:
>>
>> But more importantly, is this init scripts related bug really what's
>> happening at your system?  Or do you actually experience an entirely
>> different bug?
>
> It could be.  I will try it out when I get home from work, and get
> back to you.  That would be cool if it was a simple init script
> problem.  Cause then I don't have to do anymore git bisects. ;)

Yes, the order is what causes this, you can close the bug.

Sorry for wasting everyone's time.  I thought it was a kernel bug
because I had not needed to update my gentoo system to make it happen.

Thanks.
--
To unsubscribe from this list: send the line "unsubscribe linux-acpi" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Re: 2.6.29 on MacBook 2,1 fails to reboot (was Re: 2.6.29-git13: Reported regressions from 2.6.28)

[Rafael J. Wysocki]

On Wednesday 08 April 2009, Trenton D. Adams wrote:
> On Tue, Apr 7, 2009 at 2:52 PM, Trenton D. Adams
> <trenton.d.adams@gmail.com> wrote:
> > On Tue, Apr 7, 2009 at 1:23 PM, Stefan Richter
> > <stefanr@s5r6.in-berlin.de> wrote:
> >>
> >> But more importantly, is this init scripts related bug really what's
> >> happening at your system?  Or do you actually experience an entirely
> >> different bug?
> >
> > It could be.  I will try it out when I get home from work, and get
> > back to you.  That would be cool if it was a simple init script
> > problem.  Cause then I don't have to do anymore git bisects. ;)
> 
> Yes, the order is what causes this, you can close the bug.

Closed.

Thanks,
Rafael

Re: 2.6.29 on MacBook 2, 1 fails to reboot (was Re: 2.6.29-git13: Reported regressions from 2.6.28)

[Rafael J. Wysocki]

On Wednesday 08 April 2009, Trenton D. Adams wrote:
> On Tue, Apr 7, 2009 at 2:52 PM, Trenton D. Adams
> <trenton.d.adams@gmail.com> wrote:
> > On Tue, Apr 7, 2009 at 1:23 PM, Stefan Richter
> > <stefanr@s5r6.in-berlin.de> wrote:
> >>
> >> But more importantly, is this init scripts related bug really what's
> >> happening at your system?  Or do you actually experience an entirely
> >> different bug?
> >
> > It could be.  I will try it out when I get home from work, and get
> > back to you.  That would be cool if it was a simple init script
> > problem.  Cause then I don't have to do anymore git bisects. ;)
> 
> Yes, the order is what causes this, you can close the bug.

Closed.

Thanks,
Rafael

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

[Maciej Rutecki]

2009/4/7 Maciej Rutecki <maciej.rutecki@gmail.com>:
> 2009/4/7 Marcel Holtmann <marcel@holtmann.org>:

[...]

>> I prefer to have this checked against 2.6.30-rc1 once Linus released
>> that one. I think that I know the root cause for this one and it is
>> actually a hardware/firmware bug. Some Bluetooth dongles expect to have
>> the interrupt and bulk URBs available at the same time. Otherwise they
>> do pee in their pants.
>
> I will check -rc1 when will be available.
>

2.6.30-rc1 works. Thanks

Regards
-- 
Maciej Rutecki
http://www.maciek.unixy.pl

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

[Maciej Rutecki]

2009/4/7 Maciej Rutecki <maciej.rutecki-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>:
> 2009/4/7 Marcel Holtmann <marcel-kz+m5ild9QBg9hUCZPvPmw@public.gmane.org>:

[...]

>> I prefer to have this checked against 2.6.30-rc1 once Linus released
>> that one. I think that I know the root cause for this one and it is
>> actually a hardware/firmware bug. Some Bluetooth dongles expect to have
>> the interrupt and bulk URBs available at the same time. Otherwise they
>> do pee in their pants.
>
> I will check -rc1 when will be available.
>

2.6.30-rc1 works. Thanks

Regards
-- 
Maciej Rutecki
http://www.maciek.unixy.pl

Re: 2.6.29-git13: Reported regressions from 2.6.28

[Chris Friesen]

Rafael J. Wysocki wrote:
> On Monday 06 April 2009, Linus Torvalds wrote:
>> On Mon, 6 Apr 2009, Rafael J. Wysocki wrote:
>>> Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13019
>>> Subject		: /proc/<pid>/maps offset output broken in 2.6.29
>>> Submitter	: "Chris Friesen" <cfriesen-ZIRUuHA3oDzQT0dZR+AlfA@public.gmane.org>
>>> Date		: 2009-04-01 23:18 (6 days old)
>>> References	: http://marc.info/?l=linuxppc-embedded&m=123862902916059&w=4
>>> Handled-By	: Hugh Dickins <hugh-DTz5qymZ9yRBDgjK7y7TUQ@public.gmane.org>
>> I don't think that's a regression, nor really a bug. It looks cosmetic, 
>> and likely to be fixed, but not really worth worrying about.
> 
> OK, I've dropped it from the list.

I'm okay with that.  The problem causes some backwards compatibility 
problems with existing apps that get confused by the large "offset" 
number.  The fix is going to cause problems too, but in a different way.

We'll work around it.

Chris

Re: 2.6.29-git13: Reported regressions from 2.6.28

[Chris Friesen]

Rafael J. Wysocki wrote:
> On Monday 06 April 2009, Linus Torvalds wrote:
>> On Mon, 6 Apr 2009, Rafael J. Wysocki wrote:
>>> Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13019
>>> Subject		: /proc/<pid>/maps offset output broken in 2.6.29
>>> Submitter	: "Chris Friesen" <cfriesen@nortel.com>
>>> Date		: 2009-04-01 23:18 (6 days old)
>>> References	: http://marc.info/?l=linuxppc-embedded&m=123862902916059&w=4
>>> Handled-By	: Hugh Dickins <hugh@veritas.com>
>> I don't think that's a regression, nor really a bug. It looks cosmetic, 
>> and likely to be fixed, but not really worth worrying about.
> 
> OK, I've dropped it from the list.

I'm okay with that.  The problem causes some backwards compatibility 
problems with existing apps that get confused by the large "offset" 
number.  The fix is going to cause problems too, but in a different way.

We'll work around it.

Chris

Re: 2.6.29-git13: Reported regressions from 2.6.28

[Chris Friesen]

Rafael J. Wysocki wrote:
> On Monday 06 April 2009, Linus Torvalds wrote:
>> On Mon, 6 Apr 2009, Rafael J. Wysocki wrote:
>>> Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13019
>>> Subject		: /proc/<pid>/maps offset output broken in 2.6.29
>>> Submitter	: "Chris Friesen" <cfriesen@nortel.com>
>>> Date		: 2009-04-01 23:18 (6 days old)
>>> References	: http://marc.info/?l=linuxppc-embedded&m=123862902916059&w=4
>>> Handled-By	: Hugh Dickins <hugh@veritas.com>
>> I don't think that's a regression, nor really a bug. It looks cosmetic, 
>> and likely to be fixed, but not really worth worrying about.
> 
> OK, I've dropped it from the list.

I'm okay with that.  The problem causes some backwards compatibility 
problems with existing apps that get confused by the large "offset" 
number.  The fix is going to cause problems too, but in a different way.

We'll work around it.

Chris

Re: 2.6.29-git13: Reported regressions from 2.6.28

[Linus Torvalds]

On Thu, 16 Apr 2009, Chris Friesen wrote:
> 
> I'm okay with that.  The problem causes some backwards compatibility problems
> with existing apps that get confused by the large "offset" number.  The fix is
> going to cause problems too, but in a different way.
> 
> We'll work around it.

If you have actual apps that care, that's a different issue.

We do try to bend over backwards on ABI issues if it really is noticeable 
for applications. Now, in this case, if you can just fix your app to not 
care (because it really was badly written in the first place to even 
notice), then that is the _much_ superior solution.

But if you actually have binary-only commercial apps that break, we'll do 
a compatibility thing rather than the 0 that already got merged.

Although I don't really even see what we can sanely do except for the 0 
case. We could put the virtual address in there instead of zero (I forget 
what old kernels used to do - whatever magic value the anonymous mappings 
got, it wasn't really designed as an important value in its own right, it 
was designed to trigger the "we can merge these vma's" logic.

			Linus

Re: 2.6.29-git13: Reported regressions from 2.6.28

[Linus Torvalds]

On Thu, 16 Apr 2009, Chris Friesen wrote:
> 
> I'm okay with that.  The problem causes some backwards compatibility problems
> with existing apps that get confused by the large "offset" number.  The fix is
> going to cause problems too, but in a different way.
> 
> We'll work around it.

If you have actual apps that care, that's a different issue.

We do try to bend over backwards on ABI issues if it really is noticeable 
for applications. Now, in this case, if you can just fix your app to not 
care (because it really was badly written in the first place to even 
notice), then that is the _much_ superior solution.

But if you actually have binary-only commercial apps that break, we'll do 
a compatibility thing rather than the 0 that already got merged.

Although I don't really even see what we can sanely do except for the 0 
case. We could put the virtual address in there instead of zero (I forget 
what old kernels used to do - whatever magic value the anonymous mappings 
got, it wasn't really designed as an important value in its own right, it 
was designed to trigger the "we can merge these vma's" logic.

			Linus

Re: 2.6.29-git13: Reported regressions from 2.6.28

[Rolf Eike Beer]

[-- Attachment #1: Type: text/plain, Size: 353 bytes --]

Rafael J. Wysocki wrote:

> Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12836
> Subject		: 2.6.29-rc breaks STD using Intel 945
> Submitter	: Rolf Eike Beer <eike-kernel@sf-tec.de>
> Date		: 2009-03-04 19:20 (34 days old)
> References	: http://marc.info/?l=linux-kernel&m=123619451406192&w=4

Looks like this is fixed since 2.6.30-rc1.

Eike

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 197 bytes --]

Re: 2.6.29-git13: Reported regressions from 2.6.28

[Rolf Eike Beer]

[-- Attachment #1.1: Type: text/plain, Size: 353 bytes --]

Rafael J. Wysocki wrote:

> Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12836
> Subject		: 2.6.29-rc breaks STD using Intel 945
> Submitter	: Rolf Eike Beer <eike-kernel@sf-tec.de>
> Date		: 2009-03-04 19:20 (34 days old)
> References	: http://marc.info/?l=linux-kernel&m=123619451406192&w=4

Looks like this is fixed since 2.6.30-rc1.

Eike

[-- Attachment #1.2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 197 bytes --]

[-- Attachment #2: Type: text/plain, Size: 0 bytes --]

Re: 2.6.29-git13: Reported regressions from 2.6.28

[Rolf Eike Beer]

[-- Attachment #1: Type: text/plain, Size: 383 bytes --]

Rafael J. Wysocki wrote:

> Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12836
> Subject		: 2.6.29-rc breaks STD using Intel 945
> Submitter	: Rolf Eike Beer <eike-kernel-F+mm6HnICJmzQB+pC5nmwQ@public.gmane.org>
> Date		: 2009-03-04 19:20 (34 days old)
> References	: http://marc.info/?l=linux-kernel&m=123619451406192&w=4

Looks like this is fixed since 2.6.30-rc1.

Eike

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 197 bytes --]

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

[Nico Schottelius]

[-- Attachment #1: Type: text/plain, Size: 945 bytes --]

Nico Schottelius [Fri, Apr 17, 2009 at 04:35:32PM +0200]:
> Brightness is *AGAIN* broken in 2.6.30-rc2-00195-g9f76208.

2.6.30-rc2-next-20090420:

My display *is* at full brightness, but I cannot adjust it,
because I'm missing some files:

[12:35] ikn:~# ls /sys/class/video_output 
[12:35] ikn:~# ls /sys/class/backlight   
[12:35] ikn:~# ls /proc/acpi           
ac_adapter  debug_layer  embedded_controller  fan   power_resource  thermal_zone
battery     debug_level  event          ibm   processor     wakeup
button      dsdt   fadt         info  sleep

So I cannot adjust brightness. I saw that
/proc/acpi/video/VID/LCD0/brightness was not existing on 2.6.30-rc2-00195-g9f76208
either.

Bug or am I missing some new file location?

Nico

-- 
Think about Free and Open Source Software (FOSS).
http://nico.schottelius.org/documentations/foss/the-term-foss/

PGP: BFE4 C736 ABE5 406F 8F42  F7CF B8BE F92A 9885 188C

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 197 bytes --]

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

[Nico Schottelius]

[-- Attachment #1: Type: text/plain, Size: 945 bytes --]

Nico Schottelius [Fri, Apr 17, 2009 at 04:35:32PM +0200]:
> Brightness is *AGAIN* broken in 2.6.30-rc2-00195-g9f76208.

2.6.30-rc2-next-20090420:

My display *is* at full brightness, but I cannot adjust it,
because I'm missing some files:

[12:35] ikn:~# ls /sys/class/video_output 
[12:35] ikn:~# ls /sys/class/backlight   
[12:35] ikn:~# ls /proc/acpi           
ac_adapter  debug_layer  embedded_controller  fan   power_resource  thermal_zone
battery     debug_level  event          ibm   processor     wakeup
button      dsdt   fadt         info  sleep

So I cannot adjust brightness. I saw that
/proc/acpi/video/VID/LCD0/brightness was not existing on 2.6.30-rc2-00195-g9f76208
either.

Bug or am I missing some new file location?

Nico

-- 
Think about Free and Open Source Software (FOSS).
http://nico.schottelius.org/documentations/foss/the-term-foss/

PGP: BFE4 C736 ABE5 406F 8F42  F7CF B8BE F92A 9885 188C

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 197 bytes --]

Re: 2.6.29-git13: Reported regressions from 2.6.28

[Chris Friesen]

Linus Torvalds wrote:
> 
> On Thu, 16 Apr 2009, Chris Friesen wrote:
>> I'm okay with that.  The problem causes some backwards compatibility problems
>> with existing apps that get confused by the large "offset" number.  The fix is
>> going to cause problems too, but in a different way.
>>
>> We'll work around it.
> 
> If you have actual apps that care, that's a different issue.
> 
> We do try to bend over backwards on ABI issues if it really is noticeable 
> for applications. Now, in this case, if you can just fix your app to not 
> care (because it really was badly written in the first place to even 
> notice), then that is the _much_ superior solution.

Yep, we can fix the app to ignore that field for anonymous mappings.

> Although I don't really even see what we can sanely do except for the 0 
> case. We could put the virtual address in there instead of zero (I forget 
> what old kernels used to do - whatever magic value the anonymous mappings 
> got, it wasn't really designed as an important value in its own right, it 
> was designed to trigger the "we can merge these vma's" logic.

For anonymous mappings, the older kernels put the starting address of 
the VMA (from the point of view of the app) as the offset.  Until the 
recent change, new kernels still did this for most VMAs, but the stack 
offset was a 64-bit value with no obvious relation to the VMA start address.

Chris

Re: 2.6.29-git13: Reported regressions from 2.6.28

[Chris Friesen]

Linus Torvalds wrote:
> 
> On Thu, 16 Apr 2009, Chris Friesen wrote:
>> I'm okay with that.  The problem causes some backwards compatibility problems
>> with existing apps that get confused by the large "offset" number.  The fix is
>> going to cause problems too, but in a different way.
>>
>> We'll work around it.
> 
> If you have actual apps that care, that's a different issue.
> 
> We do try to bend over backwards on ABI issues if it really is noticeable 
> for applications. Now, in this case, if you can just fix your app to not 
> care (because it really was badly written in the first place to even 
> notice), then that is the _much_ superior solution.

Yep, we can fix the app to ignore that field for anonymous mappings.

> Although I don't really even see what we can sanely do except for the 0 
> case. We could put the virtual address in there instead of zero (I forget 
> what old kernels used to do - whatever magic value the anonymous mappings 
> got, it wasn't really designed as an important value in its own right, it 
> was designed to trigger the "we can merge these vma's" logic.

For anonymous mappings, the older kernels put the starting address of 
the VMA (from the point of view of the app) as the offset.  Until the 
recent change, new kernels still did this for most VMAs, but the stack 
offset was a 64-bit value with no obvious relation to the VMA start address.

Chris

Re: 2.6.29-git13: Reported regressions from 2.6.28

[Chris Friesen]

Linus Torvalds wrote:
> 
> On Thu, 16 Apr 2009, Chris Friesen wrote:
>> I'm okay with that.  The problem causes some backwards compatibility problems
>> with existing apps that get confused by the large "offset" number.  The fix is
>> going to cause problems too, but in a different way.
>>
>> We'll work around it.
> 
> If you have actual apps that care, that's a different issue.
> 
> We do try to bend over backwards on ABI issues if it really is noticeable 
> for applications. Now, in this case, if you can just fix your app to not 
> care (because it really was badly written in the first place to even 
> notice), then that is the _much_ superior solution.

Yep, we can fix the app to ignore that field for anonymous mappings.

> Although I don't really even see what we can sanely do except for the 0 
> case. We could put the virtual address in there instead of zero (I forget 
> what old kernels used to do - whatever magic value the anonymous mappings 
> got, it wasn't really designed as an important value in its own right, it 
> was designed to trigger the "we can merge these vma's" logic.

For anonymous mappings, the older kernels put the starting address of 
the VMA (from the point of view of the app) as the offset.  Until the 
recent change, new kernels still did this for most VMAs, but the stack 
offset was a 64-bit value with no obvious relation to the VMA start address.

Chris

Re: 2.6.29-git13: Reported regressions from 2.6.28

[Hugh Dickins]

On Mon, 20 Apr 2009, Chris Friesen wrote:
> Linus Torvalds wrote:
> > On Thu, 16 Apr 2009, Chris Friesen wrote:
> > > I'm okay with that.  The problem causes some backwards compatibility
> > > problems
> > > with existing apps that get confused by the large "offset" number.  The
> > > fix is
> > > going to cause problems too, but in a different way.
> > >
> > > We'll work around it.
> > 
> > If you have actual apps that care, that's a different issue.

Yes, that's what I told Chris too.
But asked for more info, suspecting his app was already broken.

> > 
> > We do try to bend over backwards on ABI issues if it really is noticeable
> > for applications. Now, in this case, if you can just fix your app to not
> > care (because it really was badly written in the first place to even
> > notice), then that is the _much_ superior solution.
> 
> Yep, we can fix the app to ignore that field for anonymous mappings.
> 
> > Although I don't really even see what we can sanely do except for the 0
> > case. We could put the virtual address in there instead of zero (I forget
> > what old kernels used to do - whatever magic value the anonymous mappings
> > got, it wasn't really designed as an important value in its own right, it
> > was designed to trigger the "we can merge these vma's" logic.
> 
> For anonymous mappings, the older kernels put the starting address of the VMA
> (from the point of view of the app) as the offset.  Until the recent change,
> new kernels still did this for most VMAs, but the stack offset was a 64-bit
> value with no obvious relation to the VMA start address.

No, what they put there was something that in most cases matched the
starting address of the VMA; but try moving that VMA with mremap (and
an old /proc/<pid>/maps!) and you'll see that the "offset" remained
unchanged even when the starting address of the VMA was changed.

(The offset remaining constant so that rmap can locate the VMA's pages
and unmap them, despite their being mapped at different virtual
addresses in parent and child after a move in one of them.)

... so I think your app was indeed already broken, wasn't it?

It's also unclear why you'd want to use the offset field for the
starting address of the VMA, when /proc/<pid>/maps already shows
the starting address of the VMA.  I think you've more to tell us!

Hugh

Re: 2.6.29-git13: Reported regressions from 2.6.28

[Hugh Dickins]

On Mon, 20 Apr 2009, Chris Friesen wrote:
> Linus Torvalds wrote:
> > On Thu, 16 Apr 2009, Chris Friesen wrote:
> > > I'm okay with that.  The problem causes some backwards compatibility
> > > problems
> > > with existing apps that get confused by the large "offset" number.  The
> > > fix is
> > > going to cause problems too, but in a different way.
> > >
> > > We'll work around it.
> > 
> > If you have actual apps that care, that's a different issue.

Yes, that's what I told Chris too.
But asked for more info, suspecting his app was already broken.

> > 
> > We do try to bend over backwards on ABI issues if it really is noticeable
> > for applications. Now, in this case, if you can just fix your app to not
> > care (because it really was badly written in the first place to even
> > notice), then that is the _much_ superior solution.
> 
> Yep, we can fix the app to ignore that field for anonymous mappings.
> 
> > Although I don't really even see what we can sanely do except for the 0
> > case. We could put the virtual address in there instead of zero (I forget
> > what old kernels used to do - whatever magic value the anonymous mappings
> > got, it wasn't really designed as an important value in its own right, it
> > was designed to trigger the "we can merge these vma's" logic.
> 
> For anonymous mappings, the older kernels put the starting address of the VMA
> (from the point of view of the app) as the offset.  Until the recent change,
> new kernels still did this for most VMAs, but the stack offset was a 64-bit
> value with no obvious relation to the VMA start address.

No, what they put there was something that in most cases matched the
starting address of the VMA; but try moving that VMA with mremap (and
an old /proc/<pid>/maps!) and you'll see that the "offset" remained
unchanged even when the starting address of the VMA was changed.

(The offset remaining constant so that rmap can locate the VMA's pages
and unmap them, despite their being mapped at different virtual
addresses in parent and child after a move in one of them.)

... so I think your app was indeed already broken, wasn't it?

It's also unclear why you'd want to use the offset field for the
starting address of the VMA, when /proc/<pid>/maps already shows
the starting address of the VMA.  I think you've more to tell us!

Hugh

Re: 2.6.29-git13: Reported regressions from 2.6.28

[Hugh Dickins]

On Mon, 20 Apr 2009, Chris Friesen wrote:
> Linus Torvalds wrote:
> > On Thu, 16 Apr 2009, Chris Friesen wrote:
> > > I'm okay with that.  The problem causes some backwards compatibility
> > > problems
> > > with existing apps that get confused by the large "offset" number.  The
> > > fix is
> > > going to cause problems too, but in a different way.
> > >
> > > We'll work around it.
> > 
> > If you have actual apps that care, that's a different issue.

Yes, that's what I told Chris too.
But asked for more info, suspecting his app was already broken.

> > 
> > We do try to bend over backwards on ABI issues if it really is noticeable
> > for applications. Now, in this case, if you can just fix your app to not
> > care (because it really was badly written in the first place to even
> > notice), then that is the _much_ superior solution.
> 
> Yep, we can fix the app to ignore that field for anonymous mappings.
> 
> > Although I don't really even see what we can sanely do except for the 0
> > case. We could put the virtual address in there instead of zero (I forget
> > what old kernels used to do - whatever magic value the anonymous mappings
> > got, it wasn't really designed as an important value in its own right, it
> > was designed to trigger the "we can merge these vma's" logic.
> 
> For anonymous mappings, the older kernels put the starting address of the VMA
> (from the point of view of the app) as the offset.  Until the recent change,
> new kernels still did this for most VMAs, but the stack offset was a 64-bit
> value with no obvious relation to the VMA start address.

No, what they put there was something that in most cases matched the
starting address of the VMA; but try moving that VMA with mremap (and
an old /proc/<pid>/maps!) and you'll see that the "offset" remained
unchanged even when the starting address of the VMA was changed.

(The offset remaining constant so that rmap can locate the VMA's pages
and unmap them, despite their being mapped at different virtual
addresses in parent and child after a move in one of them.)

... so I think your app was indeed already broken, wasn't it?

It's also unclear why you'd want to use the offset field for the
starting address of the VMA, when /proc/<pid>/maps already shows
the starting address of the VMA.  I think you've more to tell us!

Hugh

Re: 2.6.29-git13: Reported regressions from 2.6.28

[Chris Friesen]

Hugh Dickins wrote:
> On Mon, 20 Apr 2009, Chris Friesen wrote:

>> For anonymous mappings, the older kernels put the starting address of the VMA
>> (from the point of view of the app) as the offset.  Until the recent change,
>> new kernels still did this for most VMAs, but the stack offset was a 64-bit
>> value with no obvious relation to the VMA start address.
> 
> No, what they put there was something that in most cases matched the
> starting address of the VMA; but try moving that VMA with mremap (and
> an old /proc/<pid>/maps!) and you'll see that the "offset" remained
> unchanged even when the starting address of the VMA was changed.
> 
> (The offset remaining constant so that rmap can locate the VMA's pages
> and unmap them, despite their being mapped at different virtual
> addresses in parent and child after a move in one of them.)
> 
> ... so I think your app was indeed already broken, wasn't it?
> 
> It's also unclear why you'd want to use the offset field for the
> starting address of the VMA, when /proc/<pid>/maps already shows
> the starting address of the VMA.  I think you've more to tell us!

Yeah, given the above the app was broken.  We just didn't run into any 
cases where the assumption caused any problems.

Also, it's not so much that we were relying on the offset value for 
anything, so much as we were parsing the file and had made some 
assumptions about valid offsets for anonymous memory.

Anyways, we'll fix it going forward to simply ignore the offset for 
anonymous memory.

Chris

Re: 2.6.29-git13: Reported regressions from 2.6.28

[Chris Friesen]

Hugh Dickins wrote:
> On Mon, 20 Apr 2009, Chris Friesen wrote:

>> For anonymous mappings, the older kernels put the starting address of the VMA
>> (from the point of view of the app) as the offset.  Until the recent change,
>> new kernels still did this for most VMAs, but the stack offset was a 64-bit
>> value with no obvious relation to the VMA start address.
> 
> No, what they put there was something that in most cases matched the
> starting address of the VMA; but try moving that VMA with mremap (and
> an old /proc/<pid>/maps!) and you'll see that the "offset" remained
> unchanged even when the starting address of the VMA was changed.
> 
> (The offset remaining constant so that rmap can locate the VMA's pages
> and unmap them, despite their being mapped at different virtual
> addresses in parent and child after a move in one of them.)
> 
> ... so I think your app was indeed already broken, wasn't it?
> 
> It's also unclear why you'd want to use the offset field for the
> starting address of the VMA, when /proc/<pid>/maps already shows
> the starting address of the VMA.  I think you've more to tell us!

Yeah, given the above the app was broken.  We just didn't run into any 
cases where the assumption caused any problems.

Also, it's not so much that we were relying on the offset value for 
anything, so much as we were parsing the file and had made some 
assumptions about valid offsets for anonymous memory.

Anyways, we'll fix it going forward to simply ignore the offset for 
anonymous memory.

Chris

Re: 2.6.29-git13: Reported regressions from 2.6.28

[Chris Friesen]

Hugh Dickins wrote:
> On Mon, 20 Apr 2009, Chris Friesen wrote:

>> For anonymous mappings, the older kernels put the starting address of the VMA
>> (from the point of view of the app) as the offset.  Until the recent change,
>> new kernels still did this for most VMAs, but the stack offset was a 64-bit
>> value with no obvious relation to the VMA start address.
> 
> No, what they put there was something that in most cases matched the
> starting address of the VMA; but try moving that VMA with mremap (and
> an old /proc/<pid>/maps!) and you'll see that the "offset" remained
> unchanged even when the starting address of the VMA was changed.
> 
> (The offset remaining constant so that rmap can locate the VMA's pages
> and unmap them, despite their being mapped at different virtual
> addresses in parent and child after a move in one of them.)
> 
> ... so I think your app was indeed already broken, wasn't it?
> 
> It's also unclear why you'd want to use the offset field for the
> starting address of the VMA, when /proc/<pid>/maps already shows
> the starting address of the VMA.  I think you've more to tell us!

Yeah, given the above the app was broken.  We just didn't run into any 
cases where the assumption caused any problems.

Also, it's not so much that we were relying on the offset value for 
anything, so much as we were parsing the file and had made some 
assumptions about valid offsets for anonymous memory.

Anyways, we'll fix it going forward to simply ignore the offset for 
anonymous memory.

Chris

boot/kernel init duration regression in 2.6.39 (was: Re: [Bug #12909] boot/kernel init duration regression from 2.6.28)

[CaT]

On Tue, Apr 07, 2009 at 08:47:49AM +1000, CaT wrote:
> On Mon, Apr 06, 2009 at 09:05:41PM +0200, Rafael J. Wysocki wrote:
> > Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12909
> > Subject		: boot/kernel init duration regression from 2.6.28
> > Submitter	: CaT <cat@zip.com.au>
> > Date		: 2009-03-16 10:25 (22 days old)
> > References	: http://marc.info/?l=linux-kernel&m=123720083515950&w=4
> 
> I got it tracked down to .29-rc1. I guess I'll need to learn to use git
> now (and user the desktop - compiling on the EEE takes /ages/). Also have
> .29.1 ready to test when I get home tonight.

This bug appears to be back in .39 and .39.2. Same pause in the same section.

eeepc 901 is involved.

[    2.536287] eeepc_laptop: Eee PC Hotkey Driver
[    2.538806] eeepc_laptop: Hotkey init flags 0x41
[    3.353526] hub 2-0:1.0: hub_suspend
[    3.353557] usb usb2: bus auto-suspend
[    3.353569] usb usb2: suspend_rh
[    3.596813] usb usb5: suspend_rh (auto-stop)
[    4.020640] input: ImPS/2 Logitech Wheel Mouse as /devices/platform/i8042/serio1/input/input7
[    4.353541] hub 3-0:1.0: hub_suspend
[    4.353581] usb usb3: bus auto-suspend
[    4.353597] usb usb3: suspend_rh
[    4.353638] hub 4-0:1.0: hub_suspend
[    4.353655] usb usb4: bus auto-suspend
[    4.353665] usb usb4: suspend_rh
[    4.353720] usb 1-8: usb auto-suspend
[    4.506857] hub 5-0:1.0: hub_suspend
[    4.506894] usb usb5: bus auto-suspend
[    4.506911] usb usb5: suspend_rh
[    4.506957] hub 6-0:1.0: hub_suspend
[    4.506977] usb usb6: bus auto-suspend
[    6.170185] ata2: link is slow to respond, please be patient (ready=0)
[    6.366858] hub 1-0:1.0: hub_suspend
[    6.366895] usb usb1: bus auto-suspend
[    6.366911] ehci_hcd 0000:00:1d.7: suspend root hub
[    7.670579] ata2.00: CFA: ASUS-PHISON SSD, TST2.04U, max UDMA/66
[    7.673098] ata2.00: 7880544 sectors, multi 0: LBA 
[    7.680458] ata2.00: configured for UDMA/66
[    7.683267] scsi 1:0:0:0: Direct-Access     ATA      ASUS-PHISON SSD  TST2 PQ: 0 ANSI: 5
[    7.686546] sd 1:0:0:0: [sdb] 7880544 512-byte logical blocks: (4.03 GB/3.75 GiB)
[    7.686909] sd 1:0:0:0: Attached scsi generic sg1 type 0
[    7.692132] sd 1:0:0:0: [sdb] Write Protect is off
[    7.694745] sd 1:0:0:0: [sdb] Mode Sense: 00 3a 00 00
[    7.694812] sd 1:0:0:0: [sdb] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA
[    7.700201]  sdb: sdb1 sdb2 < sdb5 > sdb3 sdb4
[    7.704471] sd 1:0:0:0: [sdb] Attached SCSI disk
[   27.999338] eeepc_laptop: TYPE (2000000) not reported by BIOS, enabling anyway
[   28.006959] eeepc_laptop: PANELPOWER (4000000) not reported by BIOS, enabling anyway
[   28.009855] eeepc_laptop: Get control methods supported: 0x6101713
[   28.015878] input: Asus EeePC extra buttons as /devices/platform/eeepc/input/input8
[   29.421681] eeepc_laptop: BIOS says wireless lan is unblocked, but the pci device is absent
[   29.424576] eeepc_laptop: skipped wireless hotplug as probably inappropriate for this model

-- 
  "A search of his car uncovered pornography, a homemade sex aid, women's 
  stockings and a Jack Russell terrier."
    - http://www.dailytelegraph.com.au/news/wacky/indeed/story-e6frev20-1111118083480

[Bug #12809] iozone regression with 2.6.29-rc6

[Rafael J. Wysocki]

This message has been generated automatically as a part of a report
of recent regressions.

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


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12809
Subject		: iozone regression with 2.6.29-rc6
Submitter	: Lin Ming <ming.m.lin@intel.com>
Date		: 2009-02-27 9:13 (23 days old)
First-Bad-Commit: http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=1cf6e7d83bf334cc5916137862c920a97aabc018
References	: http://marc.info/?l=linux-kernel&m=123572630504360&w=4
		  http://lkml.org/lkml/2009/3/14/265
Handled-By	: Wu Fengguang <fengguang.wu@intel.com>

[Bug #12809] iozone regression with 2.6.29-rc6

[Rafael J. Wysocki]

This message has been generated automatically as a part of a report
of recent regressions.

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


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12809
Subject		: iozone regression with 2.6.29-rc6
Submitter	: Lin Ming <ming.m.lin-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
Date		: 2009-02-27 9:13 (23 days old)
First-Bad-Commit: http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=1cf6e7d83bf334cc5916137862c920a97aabc018
References	: http://marc.info/?l=linux-kernel&m=123572630504360&w=4
		  http://lkml.org/lkml/2009/3/14/265
Handled-By	: Wu Fengguang <fengguang.wu-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>

Re: [Bug #12809] iozone regression with 2.6.29-rc6

[Wu Fengguang]

On Mon, Mar 16, 2009 at 01:03:42PM +0800, Lin, Ming wrote:
> On Sun, 2009-03-15 at 08:27 +0800, Linus Torvalds wrote:
> > 
> > On Sat, 14 Mar 2009, Rafael J. Wysocki wrote:
> > > 
> > > The following bug entry is on the current list of known regressions
> > > from 2.6.28.  Please verify if it still should be listed and let me know
> > > (either way).
> > > 
> > > 
> > > Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12809
> > > Subject		: iozone regression with 2.6.29-rc6
> > > Submitter	: Lin Ming <ming.m.lin@intel.com>
> > > Date		: 2009-02-27 9:13 (16 days old)
> > > First-Bad-Commit: http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=1cf6e7d83bf334cc5916137862c920a97aabc018
> > > References	: http://marc.info/?l=linux-kernel&m=123572630504360&w=4
> > > Handled-By	: Wu Fengguang <fengguang.wu@intel.com>
> > 
> > I suspect that I should just raise the default dirty limits. Wu reported 
> > that it fixed the regression, and while he picked some rather high 
> > percentages, I think we could certainly raise the rather aggressive 
> > default ones. 
> > 
> > After all, those default percentages were picked (a) with the old dirty 
> > logic and (b) largely at random and (c) designed to be aggressive. In 
> > particular, that (a) means that having fixed some of the dirty accounting, 
> > maybe the real bug is now that it was always too aggressive, just hidden 
> > by an accounting issue.
> > 
> > If we raised the default ratio from 5/10 to 10/20, what happens to the 
> > iozone regression?
> 
> echo 10 > /proc/sys/vm/dirty_background_ratio
> echo 20 > /proc/sys/vm/dirty_ratio
> 
> It fixed the regression of iozone (filesize 1200M) on 4P dual-core HT
> machine(8G mem).

A quick&coarse calculation: 8G * 15% = 1200M.
This means an iozone process dirtying 1200M data won't be write-blocked.

So the thresholds of 10/20 are just about enough for fixing this regression.

Thanks,
Fengguang

Re: [Bug #12809] iozone regression with 2.6.29-rc6

[Wu Fengguang]

On Mon, Mar 16, 2009 at 01:03:42PM +0800, Lin, Ming wrote:
> On Sun, 2009-03-15 at 08:27 +0800, Linus Torvalds wrote:
> > 
> > On Sat, 14 Mar 2009, Rafael J. Wysocki wrote:
> > > 
> > > The following bug entry is on the current list of known regressions
> > > from 2.6.28.  Please verify if it still should be listed and let me know
> > > (either way).
> > > 
> > > 
> > > Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12809
> > > Subject		: iozone regression with 2.6.29-rc6
> > > Submitter	: Lin Ming <ming.m.lin-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
> > > Date		: 2009-02-27 9:13 (16 days old)
> > > First-Bad-Commit: http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=1cf6e7d83bf334cc5916137862c920a97aabc018
> > > References	: http://marc.info/?l=linux-kernel&m=123572630504360&w=4
> > > Handled-By	: Wu Fengguang <fengguang.wu-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
> > 
> > I suspect that I should just raise the default dirty limits. Wu reported 
> > that it fixed the regression, and while he picked some rather high 
> > percentages, I think we could certainly raise the rather aggressive 
> > default ones. 
> > 
> > After all, those default percentages were picked (a) with the old dirty 
> > logic and (b) largely at random and (c) designed to be aggressive. In 
> > particular, that (a) means that having fixed some of the dirty accounting, 
> > maybe the real bug is now that it was always too aggressive, just hidden 
> > by an accounting issue.
> > 
> > If we raised the default ratio from 5/10 to 10/20, what happens to the 
> > iozone regression?
> 
> echo 10 > /proc/sys/vm/dirty_background_ratio
> echo 20 > /proc/sys/vm/dirty_ratio
> 
> It fixed the regression of iozone (filesize 1200M) on 4P dual-core HT
> machine(8G mem).

A quick&coarse calculation: 8G * 15% = 1200M.
This means an iozone process dirtying 1200M data won't be write-blocked.

So the thresholds of 10/20 are just about enough for fixing this regression.

Thanks,
Fengguang

Re: [Bug #12809] iozone regression with 2.6.29-rc6

[Lin Ming]

On Sun, 2009-03-15 at 08:27 +0800, Linus Torvalds wrote:
> 
> On Sat, 14 Mar 2009, Rafael J. Wysocki wrote:
> > 
> > The following bug entry is on the current list of known regressions
> > from 2.6.28.  Please verify if it still should be listed and let me know
> > (either way).
> > 
> > 
> > Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12809
> > Subject		: iozone regression with 2.6.29-rc6
> > Submitter	: Lin Ming <ming.m.lin@intel.com>
> > Date		: 2009-02-27 9:13 (16 days old)
> > First-Bad-Commit: http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=1cf6e7d83bf334cc5916137862c920a97aabc018
> > References	: http://marc.info/?l=linux-kernel&m=123572630504360&w=4
> > Handled-By	: Wu Fengguang <fengguang.wu@intel.com>
> 
> I suspect that I should just raise the default dirty limits. Wu reported 
> that it fixed the regression, and while he picked some rather high 
> percentages, I think we could certainly raise the rather aggressive 
> default ones. 
> 
> After all, those default percentages were picked (a) with the old dirty 
> logic and (b) largely at random and (c) designed to be aggressive. In 
> particular, that (a) means that having fixed some of the dirty accounting, 
> maybe the real bug is now that it was always too aggressive, just hidden 
> by an accounting issue.
> 
> If we raised the default ratio from 5/10 to 10/20, what happens to the 
> iozone regression?

echo 10 > /proc/sys/vm/dirty_background_ratio
echo 20 > /proc/sys/vm/dirty_ratio

It fixed the regression of iozone (filesize 1200M) on 4P dual-core HT
machine(8G mem).

Lin Ming

Re: [Bug #12809] iozone regression with 2.6.29-rc6

[Lin Ming]

On Sun, 2009-03-15 at 08:27 +0800, Linus Torvalds wrote:
> 
> On Sat, 14 Mar 2009, Rafael J. Wysocki wrote:
> > 
> > The following bug entry is on the current list of known regressions
> > from 2.6.28.  Please verify if it still should be listed and let me know
> > (either way).
> > 
> > 
> > Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12809
> > Subject		: iozone regression with 2.6.29-rc6
> > Submitter	: Lin Ming <ming.m.lin-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
> > Date		: 2009-02-27 9:13 (16 days old)
> > First-Bad-Commit: http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=1cf6e7d83bf334cc5916137862c920a97aabc018
> > References	: http://marc.info/?l=linux-kernel&m=123572630504360&w=4
> > Handled-By	: Wu Fengguang <fengguang.wu-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
> 
> I suspect that I should just raise the default dirty limits. Wu reported 
> that it fixed the regression, and while he picked some rather high 
> percentages, I think we could certainly raise the rather aggressive 
> default ones. 
> 
> After all, those default percentages were picked (a) with the old dirty 
> logic and (b) largely at random and (c) designed to be aggressive. In 
> particular, that (a) means that having fixed some of the dirty accounting, 
> maybe the real bug is now that it was always too aggressive, just hidden 
> by an accounting issue.
> 
> If we raised the default ratio from 5/10 to 10/20, what happens to the 
> iozone regression?

echo 10 > /proc/sys/vm/dirty_background_ratio
echo 20 > /proc/sys/vm/dirty_ratio

It fixed the regression of iozone (filesize 1200M) on 4P dual-core HT
machine(8G mem).

Lin Ming

Re: [Bug #12809] iozone regression with 2.6.29-rc6

[Wu Fengguang]

On Sun, Mar 15, 2009 at 08:27:08AM +0800, Linus Torvalds wrote:
> 
> 
> On Sat, 14 Mar 2009, Rafael J. Wysocki wrote:
> > 
> > The following bug entry is on the current list of known regressions
> > from 2.6.28.  Please verify if it still should be listed and let me know
> > (either way).
> > 
> > 
> > Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12809
> > Subject		: iozone regression with 2.6.29-rc6
> > Submitter	: Lin Ming <ming.m.lin@intel.com>
> > Date		: 2009-02-27 9:13 (16 days old)
> > First-Bad-Commit: http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=1cf6e7d83bf334cc5916137862c920a97aabc018
> > References	: http://marc.info/?l=linux-kernel&m=123572630504360&w=4
> > Handled-By	: Wu Fengguang <fengguang.wu@intel.com>
> 
> I suspect that I should just raise the default dirty limits. Wu reported 
> that it fixed the regression, and while he picked some rather high 
> percentages, I think we could certainly raise the rather aggressive 
> default ones. 
> 
> After all, those default percentages were picked (a) with the old dirty 
> logic and (b) largely at random and (c) designed to be aggressive. In 
> particular, that (a) means that having fixed some of the dirty accounting, 
> maybe the real bug is now that it was always too aggressive, just hidden 
> by an accounting issue.

I second that.

1) The _real_ dirty threshold used to be large.
2) It is a _real_ regression. It impacts real user experiences.

So when introducing Nick's correct-dirty-accounting patch, we'd better
increase the dirty thresholds correspondingly.

> If we raised the default ratio from 5/10 to 10/20, what happens to the 
> iozone regression?

Maybe tomorrow. Ling Ming?

In general we should not cater the thresholds for one specific workload.
But this is a case of _regression_, and it would be better to raise the
bars above it.

Thanks,
Fengguang

Re: [Bug #12809] iozone regression with 2.6.29-rc6

[Wu Fengguang]

On Sun, Mar 15, 2009 at 08:27:08AM +0800, Linus Torvalds wrote:
> 
> 
> On Sat, 14 Mar 2009, Rafael J. Wysocki wrote:
> > 
> > The following bug entry is on the current list of known regressions
> > from 2.6.28.  Please verify if it still should be listed and let me know
> > (either way).
> > 
> > 
> > Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12809
> > Subject		: iozone regression with 2.6.29-rc6
> > Submitter	: Lin Ming <ming.m.lin-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
> > Date		: 2009-02-27 9:13 (16 days old)
> > First-Bad-Commit: http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=1cf6e7d83bf334cc5916137862c920a97aabc018
> > References	: http://marc.info/?l=linux-kernel&m=123572630504360&w=4
> > Handled-By	: Wu Fengguang <fengguang.wu-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
> 
> I suspect that I should just raise the default dirty limits. Wu reported 
> that it fixed the regression, and while he picked some rather high 
> percentages, I think we could certainly raise the rather aggressive 
> default ones. 
> 
> After all, those default percentages were picked (a) with the old dirty 
> logic and (b) largely at random and (c) designed to be aggressive. In 
> particular, that (a) means that having fixed some of the dirty accounting, 
> maybe the real bug is now that it was always too aggressive, just hidden 
> by an accounting issue.

I second that.

1) The _real_ dirty threshold used to be large.
2) It is a _real_ regression. It impacts real user experiences.

So when introducing Nick's correct-dirty-accounting patch, we'd better
increase the dirty thresholds correspondingly.

> If we raised the default ratio from 5/10 to 10/20, what happens to the 
> iozone regression?

Maybe tomorrow. Ling Ming?

In general we should not cater the thresholds for one specific workload.
But this is a case of _regression_, and it would be better to raise the
bars above it.

Thanks,
Fengguang

Re: [Bug #12809] iozone regression with 2.6.29-rc6

[Linus Torvalds]

On Sat, 14 Mar 2009, Rafael J. Wysocki wrote:
> 
> The following bug entry is on the current list of known regressions
> from 2.6.28.  Please verify if it still should be listed and let me know
> (either way).
> 
> 
> Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12809
> Subject		: iozone regression with 2.6.29-rc6
> Submitter	: Lin Ming <ming.m.lin@intel.com>
> Date		: 2009-02-27 9:13 (16 days old)
> First-Bad-Commit: http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=1cf6e7d83bf334cc5916137862c920a97aabc018
> References	: http://marc.info/?l=linux-kernel&m=123572630504360&w=4
> Handled-By	: Wu Fengguang <fengguang.wu@intel.com>

I suspect that I should just raise the default dirty limits. Wu reported 
that it fixed the regression, and while he picked some rather high 
percentages, I think we could certainly raise the rather aggressive 
default ones. 

After all, those default percentages were picked (a) with the old dirty 
logic and (b) largely at random and (c) designed to be aggressive. In 
particular, that (a) means that having fixed some of the dirty accounting, 
maybe the real bug is now that it was always too aggressive, just hidden 
by an accounting issue.

If we raised the default ratio from 5/10 to 10/20, what happens to the 
iozone regression?

		Linus

[Bug #12809] iozone regression with 2.6.29-rc6

[Rafael J. Wysocki]

This message has been generated automatically as a part of a report
of recent regressions.

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


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12809
Subject		: iozone regression with 2.6.29-rc6
Submitter	: Lin Ming <ming.m.lin@intel.com>
Date		: 2009-02-27 9:13 (16 days old)
First-Bad-Commit: http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=1cf6e7d83bf334cc5916137862c920a97aabc018
References	: http://marc.info/?l=linux-kernel&m=123572630504360&w=4
Handled-By	: Wu Fengguang <fengguang.wu@intel.com>

[Bug #12809] iozone regression with 2.6.29-rc6

[Rafael J. Wysocki]

This message has been generated automatically as a part of a report
of recent regressions.

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


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12809
Subject		: iozone regression with 2.6.29-rc6
Submitter	: Lin Ming <ming.m.lin-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
Date		: 2009-02-27 9:13 (16 days old)
First-Bad-Commit: http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=1cf6e7d83bf334cc5916137862c920a97aabc018
References	: http://marc.info/?l=linux-kernel&m=123572630504360&w=4
Handled-By	: Wu Fengguang <fengguang.wu-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>

Re: [Bug #12809] iozone regression with 2.6.29-rc6

[Rafael J. Wysocki]

On Thursday 05 March 2009, Wu Fengguang wrote:
> On Tue, Mar 03, 2009 at 09:25:59PM +0200, Rafael J. Wysocki wrote:
> > This message has been generated automatically as a part of a report
> > of recent regressions.
> > 
> > The following bug entry is on the current list of known regressions
> > from 2.6.28.  Please verify if it still should be listed and let me know
> > (either way).
> > 
> > 
> > Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12809
> > Subject		: iozone regression with 2.6.29-rc6
> > Submitter	: Lin Ming <ming.m.lin@intel.com>
> > Date		: 2009-02-27 9:13 (5 days old)
> > First-Bad-Commit: http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=1cf6e7d83bf334cc5916137862c920a97aabc018
> > References	: http://marc.info/?l=linux-kernel&m=123572630504360&w=4
> > Handled-By	: Wu Fengguang <fengguang.wu@intel.com>
> 
> Following Peter's idea of relaxing writeback throttling, Lin Ming
> and I tried the idea of totally disabling writeback throttling by
> doing benchmarks with the following parameters:
> 
>         echo 60 > /proc/sys/vm/dirty_ratio
>         echo 50 > /proc/sys/vm/dirty_background_ratio
> 
> The result is encouraging: the iozone performance is restored to the
> level of 2.6.29-rc5!
> 
> We'll continue to evaluate the dirty/throttling numbers with Nick's patch.

Thanks for the update.

Rafael

Re: [Bug #12809] iozone regression with 2.6.29-rc6

[Rafael J. Wysocki]

On Thursday 05 March 2009, Wu Fengguang wrote:
> On Tue, Mar 03, 2009 at 09:25:59PM +0200, Rafael J. Wysocki wrote:
> > This message has been generated automatically as a part of a report
> > of recent regressions.
> > 
> > The following bug entry is on the current list of known regressions
> > from 2.6.28.  Please verify if it still should be listed and let me know
> > (either way).
> > 
> > 
> > Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12809
> > Subject		: iozone regression with 2.6.29-rc6
> > Submitter	: Lin Ming <ming.m.lin-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
> > Date		: 2009-02-27 9:13 (5 days old)
> > First-Bad-Commit: http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=1cf6e7d83bf334cc5916137862c920a97aabc018
> > References	: http://marc.info/?l=linux-kernel&m=123572630504360&w=4
> > Handled-By	: Wu Fengguang <fengguang.wu-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
> 
> Following Peter's idea of relaxing writeback throttling, Lin Ming
> and I tried the idea of totally disabling writeback throttling by
> doing benchmarks with the following parameters:
> 
>         echo 60 > /proc/sys/vm/dirty_ratio
>         echo 50 > /proc/sys/vm/dirty_background_ratio
> 
> The result is encouraging: the iozone performance is restored to the
> level of 2.6.29-rc5!
> 
> We'll continue to evaluate the dirty/throttling numbers with Nick's patch.

Thanks for the update.

Rafael

Re: [Bug #12809] iozone regression with 2.6.29-rc6

[Peter Zijlstra]

(list restored)

On Thu, 2009-03-05 at 10:13 +0800, Zhang, Yanmin wrote:

> My idea:
> 1) When the main thread traps into kernel and find need to write back pages; it just starts
> write back, but it needn't change timestamp (???or something like that) on writeback; and start
> pdflush;
> 2) Later on pdflush could pick up the file to write back for other pages on the same file;
> 3) The target is to let pdflush to writeback pages and main testing thread continues on its own
> work, so we can benefit from SMP.

No!

This is not about parallelism, this is about making sure there is a
limited number of dirty pages, that means the tasks generating dirty
pages will _have_ to wait. You simply cannot delegate that.

Furthermore, the task throttling explicitly wants to throttle the task
that generates all those dirty pages more than other tasks. So pushing
the throttle out to pdflush will destroy the whole scheme.

The reason we want to make the heavy dirtier throttle sooner is that
other tasks, who only occasionally dirty a page, don't get caught in the
massive throttle latency.

Re: [Bug #12809] iozone regression with 2.6.29-rc6

[Wu Fengguang]

On Tue, Mar 03, 2009 at 09:25:59PM +0200, Rafael J. Wysocki wrote:
> This message has been generated automatically as a part of a report
> of recent regressions.
> 
> The following bug entry is on the current list of known regressions
> from 2.6.28.  Please verify if it still should be listed and let me know
> (either way).
> 
> 
> Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12809
> Subject		: iozone regression with 2.6.29-rc6
> Submitter	: Lin Ming <ming.m.lin@intel.com>
> Date		: 2009-02-27 9:13 (5 days old)
> First-Bad-Commit: http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=1cf6e7d83bf334cc5916137862c920a97aabc018
> References	: http://marc.info/?l=linux-kernel&m=123572630504360&w=4
> Handled-By	: Wu Fengguang <fengguang.wu@intel.com>

Following Peter's idea of relaxing writeback throttling, Lin Ming
and I tried the idea of totally disabling writeback throttling by
doing benchmarks with the following parameters:

        echo 60 > /proc/sys/vm/dirty_ratio
        echo 50 > /proc/sys/vm/dirty_background_ratio

The result is encouraging: the iozone performance is restored to the
level of 2.6.29-rc5!

We'll continue to evaluate the dirty/throttling numbers with Nick's patch.

Thanks,
Fengguang

Re: [Bug #12809] iozone regression with 2.6.29-rc6

[Wu Fengguang]

On Tue, Mar 03, 2009 at 09:25:59PM +0200, Rafael J. Wysocki wrote:
> This message has been generated automatically as a part of a report
> of recent regressions.
> 
> The following bug entry is on the current list of known regressions
> from 2.6.28.  Please verify if it still should be listed and let me know
> (either way).
> 
> 
> Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12809
> Subject		: iozone regression with 2.6.29-rc6
> Submitter	: Lin Ming <ming.m.lin-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
> Date		: 2009-02-27 9:13 (5 days old)
> First-Bad-Commit: http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=1cf6e7d83bf334cc5916137862c920a97aabc018
> References	: http://marc.info/?l=linux-kernel&m=123572630504360&w=4
> Handled-By	: Wu Fengguang <fengguang.wu-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>

Following Peter's idea of relaxing writeback throttling, Lin Ming
and I tried the idea of totally disabling writeback throttling by
doing benchmarks with the following parameters:

        echo 60 > /proc/sys/vm/dirty_ratio
        echo 50 > /proc/sys/vm/dirty_background_ratio

The result is encouraging: the iozone performance is restored to the
level of 2.6.29-rc5!

We'll continue to evaluate the dirty/throttling numbers with Nick's patch.

Thanks,
Fengguang

[Bug #12809] iozone regression with 2.6.29-rc6

[Rafael J. Wysocki]

This message has been generated automatically as a part of a report
of recent regressions.

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


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12809
Subject		: iozone regression with 2.6.29-rc6
Submitter	: Lin Ming <ming.m.lin@intel.com>
Date		: 2009-02-27 9:13 (5 days old)
First-Bad-Commit: http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=1cf6e7d83bf334cc5916137862c920a97aabc018
References	: http://marc.info/?l=linux-kernel&m=123572630504360&w=4
Handled-By	: Wu Fengguang <fengguang.wu@intel.com>

[Bug #12809] iozone regression with 2.6.29-rc6

[Rafael J. Wysocki]

This message has been generated automatically as a part of a report
of recent regressions.

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


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12809
Subject		: iozone regression with 2.6.29-rc6
Submitter	: Lin Ming <ming.m.lin-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
Date		: 2009-02-27 9:13 (5 days old)
First-Bad-Commit: http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=1cf6e7d83bf334cc5916137862c920a97aabc018
References	: http://marc.info/?l=linux-kernel&m=123572630504360&w=4
Handled-By	: Wu Fengguang <fengguang.wu-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>