2.6.30-rc3-git1: Reported regressions 2.6.28 -> 2.6.29

2.6.30-rc3-git1: Reported regressions 2.6.28 -> 2.6.29

[Rafael J. Wysocki]

[NOTES:
 * The number of regressions related to DRI is alarming, especially that for
   some of the reporters have identified the "bad" commits.
 * I have closed some bugs where there was no activity.]

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

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

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


Listed regressions statistics:

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


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

Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13184
Subject		: Left audio channel broken after resume from suspend with Intel HDA
Submitter	: Tino Keitel <tino.keitel@tikei.de>
Date		: 2009-04-20 18:40 (7 days old)
References	: http://marc.info/?l=linux-kernel&m=124025290831292&w=4
Handled-By	: Takashi Iwai <tiwai@suse.de>


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


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


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


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


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


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13112
Subject		: Oops in drain_array
Submitter	: Bart <mmx@riz.pl>
Date		: 2009-04-14 10:21 (13 days old)
References	: http://marc.info/?l=linux-kernel&m=123970493224628&w=4


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13100
Subject		: can't anymore even do a s2ram-s2disk-s2ram cycle on acer aspire 5720G
Submitter	: Maxim Levitsky <maximlevitsky@gmail.com>
Date		: 2009-04-06 23:52 (21 days old)
First-Bad-Commit: http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=a0d4922da2e4ccb0973095d8d29f36f6b1b5f703
References	: http://marc.info/?l=linux-kernel&m=123906202829074&w=4
Handled-By	: Rafael J. Wysocki <rjw@sisk.pl>


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13074
Subject		: gspca_stv06xx doesn't work with Logitech QuickCam Express (046d:0840)
Submitter	: Paulo Matias <matias@archlinux-br.org>
Date		: 2009-04-12 14:10 (15 days old)


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13072
Subject		: forcedeth seems to switch off eth on shutdown
Submitter	: Daniel Bierstedt <daniel.bierstedt@gmx.de>
Date		: 2009-04-12 07:00 (15 days old)


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13040
Subject		: DRM radeon
Submitter	: Roger Luethi <rl@hellgate.ch>
Date		: 2009-04-07 20:07 (20 days old)


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13032
Subject		: 2.6.29 regression: network interfaces drop after suspend/resume
Submitter	: Jose Marino <braket@hotmail.com>
Date		: 2009-04-07 00:08 (20 days old)
First-Bad-Commit: http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=31878dd86b7df9a147f5e6cc6e07092b4308782b


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13025
Subject		: After upgrading to kernel 2.6.29, pulseaudio stopped with some strange error
Submitter	: Yaroslav Isakov <yaroslav.isakov@gmail.com>
Date		: 2009-04-06 19:47 (21 days old)


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13003
Subject		: [2.6.29 regression] ivtv driver causes strange oops'es, disrupts software suspend
Submitter	: Artem S. Tashkinov <t.artem@mailcity.com>
Date		: 2009-04-03 14:57 (24 days old)
Handled-By	: Hans Verkuil <hverkuil@xs4all.nl>


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 (24 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 (27 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 (29 days old)
Handled-By	: Matt Carlson <mcarlson@broadcom.com>


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 (32 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 (42 days old)
References	: http://marc.info/?l=linux-kernel&m=123720083515950&w=4


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


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


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=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 (54 days old)
References	: http://marc.info/?l=linux-kernel&m=123619451406192&w=4


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 (65 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=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 (73 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	: Eric Anholt <eric@anholt.net>


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 (77 days old)
First-Bad-Commit: http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=1cfe62c8010ac56e1bd3827e30386a87cc2f3594
Handled-By	: Alexey Starikovskiy <astarikovskiy@suse.de>


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 (104 days old)
References	: http://marc.info/?l=linux-kernel&m=123187185426236&w=4
Handled-By	: Marcel Holtmann <marcel@holtmann.org>


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 (105 days old)
References	: http://marc.info/?l=linux-kernel&m=123174591509586&w=4
		  http://lkml.org/lkml/2009/4/6/527
Handled-By	: Bob Copeland <me@bobcopeland.com>


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

Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13186
Subject		: cpufreq timer teardown problem
Submitter	: Mathieu Desnoyers <mathieu.desnoyers@polymtl.ca>
Date		: 2009-04-23 14:00 (4 days old)
References	: http://marc.info/?l=linux-kernel&m=124049523515036&w=4
Handled-By	: Mathieu Desnoyers <mathieu.desnoyers@polymtl.ca>
Patch		: http://patchwork.kernel.org/patch/19754/
		  http://patchwork.kernel.org/patch/19753/


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 (30 days old)
First-Bad-Commit: http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=8d6f0c8214928f7c5083dd54ecb69c5d615b516e
Handled-By	: Andreas Herrmann <andreas.herrmann3@amd.com>
Patch		: http://bugzilla.kernel.org/attachment.cgi?id=21070


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

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

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

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

Thanks,
Rafael

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

[Rafael J. Wysocki]

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

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


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12490
Subject		: ath5k related kernel panic in 2.6.29-rc1
Submitter	: Sergey S. Kostyliov <rathamahata@gmail.com>
Date		: 2009-01-12 7:38 (105 days old)
References	: http://marc.info/?l=linux-kernel&m=123174591509586&w=4
		  http://lkml.org/lkml/2009/4/6/527
Handled-By	: Bob Copeland <me@bobcopeland.com>

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

[Rafael J. Wysocki]

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

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


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=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 (105 days old)
References	: http://marc.info/?l=linux-kernel&m=123174591509586&w=4
		  http://lkml.org/lkml/2009/4/6/527
Handled-By	: Bob Copeland <me-aXfl/3sk2vNUbtYUoyoikg@public.gmane.org>

[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 regressions introduced between 2.6.28 and 2.6.29.

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


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12681
Subject		: s2ram: fails to wake up on Acer Extensa 4220 (SMP disabled)
Submitter	: Orivej Desh <smpuj@bk.ru>
Date		: 2009-02-09 13:01 (77 days old)
First-Bad-Commit: http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=1cfe62c8010ac56e1bd3827e30386a87cc2f3594
Handled-By	: Alexey Starikovskiy <astarikovskiy@suse.de>

[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 regressions introduced between 2.6.28 and 2.6.29.

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


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12705
Subject		: X200: Brightness broken since 2.6.29-rc4-58-g4c098bc
Submitter	: Nico Schottelius <nico-linux-20090213@schottelius.org>
Date		: 2009-02-13 9:33 (73 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	: Eric Anholt <eric@anholt.net>

[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 regressions introduced between 2.6.28 and 2.6.29.

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


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12499
Subject		: Problem with using bluetooth adaper connected to usb port
Submitter	: Maciej Rutecki <maciej.rutecki@gmail.com>
Date		: 2009-01-13 18:34 (104 days old)
References	: http://marc.info/?l=linux-kernel&m=123187185426236&w=4
Handled-By	: Marcel Holtmann <marcel@holtmann.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 regressions introduced between 2.6.28 and 2.6.29.

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


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12765
Subject		: i915 VT switch with AIGLX causes X lock up
Submitter	: Sitsofe Wheeler <sitsofe@yahoo.com>
Date		: 2009-02-21 15:38 (65 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 #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 regressions introduced between 2.6.28 and 2.6.29.

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


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

[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 regressions introduced between 2.6.28 and 2.6.29.

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


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12899
Subject		: Crash in i915.ko: i915_driver_irq_handler
Submitter	: Helge Bahmann <helge.bahmann@secunet.com>
Date		: 2009-03-20 07:13 (38 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 regressions introduced between 2.6.28 and 2.6.29.

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


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12947
Subject		: r128: system hangs when X is started with DRI enabled
Submitter	: Jos van der Ende <seraph@xs4all.nl>
Date		: 2009-03-26 16:14 (32 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 regressions introduced between 2.6.28 and 2.6.29.

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


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

[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 regressions introduced between 2.6.28 and 2.6.29.

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


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=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 (54 days old)
References	: http://marc.info/?l=linux-kernel&m=123619451406192&w=4

[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 regressions introduced between 2.6.28 and 2.6.29.

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


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12765
Subject		: i915 VT switch with AIGLX causes X lock up
Submitter	: Sitsofe Wheeler <sitsofe@yahoo.com>
Date		: 2009-02-21 15:38 (65 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



------------------------------------------------------------------------------
Crystal Reports &#45; New Free Runtime and 30 Day Trial
Check out the new simplified licensign option that enables unlimited
royalty&#45;free distribution of the report engine for externally facing 
server and web deployment.
http://p.sf.net/sfu/businessobjects
--

[Bug #12980] lockup in X.org

[Rafael J. Wysocki]

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

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


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

[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 regressions introduced between 2.6.28 and 2.6.29.

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


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12971
Subject		: "tg3 transmit timed out" when transmitting at high bitrate
Submitter	: Nikolay <dobrev666@gmail.com>
Date		: 2009-03-29 18:02 (29 days old)
Handled-By	: Matt Carlson <mcarlson@broadcom.com>

[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 regressions introduced between 2.6.28 and 2.6.29.

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


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=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 (30 days old)
First-Bad-Commit: http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=8d6f0c8214928f7c5083dd54ecb69c5d615b516e
Handled-By	: Andreas Herrmann <andreas.herrmann3@amd.com>
Patch		: http://bugzilla.kernel.org/attachment.cgi?id=21070

[Bug #13003] [2.6.29 regression] ivtv driver causes strange oops'es, disrupts software suspend

[Rafael J. Wysocki]

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

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


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13003
Subject		: [2.6.29 regression] ivtv driver causes strange oops'es, disrupts software suspend
Submitter	: Artem S. Tashkinov <t.artem@mailcity.com>
Date		: 2009-04-03 14:57 (24 days old)
Handled-By	: Hans Verkuil <hverkuil@xs4all.nl>

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

[Rafael J. Wysocki]

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

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


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

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

[Rafael J. Wysocki]

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

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


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13025
Subject		: After upgrading to kernel 2.6.29, pulseaudio stopped with some strange error
Submitter	: Yaroslav Isakov <yaroslav.isakov@gmail.com>
Date		: 2009-04-06 19:47 (21 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 regressions introduced between 2.6.28 and 2.6.29.

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


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

[Bug #13003] [2.6.29 regression] ivtv driver causes strange oops'es, disrupts software suspend

[Rafael J. Wysocki]

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

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


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13003
Subject		: [2.6.29 regression] ivtv driver causes strange oops'es, disrupts software suspend
Submitter	: Artem S. Tashkinov <t.artem-VInPYn6yXxRWk0Htik3J/w@public.gmane.org>
Date		: 2009-04-03 14:57 (24 days old)
Handled-By	: Hans Verkuil <hverkuil-qWit8jRvyhVmR6Xm/wNWPw@public.gmane.org>

[Bug #13040] DRM radeon

[Rafael J. Wysocki]

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

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


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13040
Subject		: DRM radeon
Submitter	: Roger Luethi <rl@hellgate.ch>
Date		: 2009-04-07 20:07 (20 days old)

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

[Rafael J. Wysocki]

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

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


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13072
Subject		: forcedeth seems to switch off eth on shutdown
Submitter	: Daniel Bierstedt <daniel.bierstedt@gmx.de>
Date		: 2009-04-12 07:00 (15 days old)

[Bug #13032] 2.6.29 regression: network interfaces drop after suspend/resume

[Rafael J. Wysocki]

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

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


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13032
Subject		: 2.6.29 regression: network interfaces drop after suspend/resume
Submitter	: Jose Marino <braket@hotmail.com>
Date		: 2009-04-07 00:08 (20 days old)
First-Bad-Commit: http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=31878dd86b7df9a147f5e6cc6e07092b4308782b

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

[Rafael J. Wysocki]

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

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


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13074
Subject		: gspca_stv06xx doesn't work with Logitech QuickCam Express (046d:0840)
Submitter	: Paulo Matias <matias@archlinux-br.org>
Date		: 2009-04-12 14:10 (15 days old)

[Bug #13040] DRM radeon

[Rafael J. Wysocki]

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

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


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13040
Subject		: DRM radeon
Submitter	: Roger Luethi <rl@hellgate.ch>
Date		: 2009-04-07 20:07 (20 days old)



------------------------------------------------------------------------------
Crystal Reports &#45; New Free Runtime and 30 Day Trial
Check out the new simplified licensign option that enables unlimited
royalty&#45;free distribution of the report engine for externally facing 
server and web deployment.
http://p.sf.net/sfu/businessobjects
--

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

[Rafael J. Wysocki]

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

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


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13100
Subject		: can't anymore even do a s2ram-s2disk-s2ram cycle on acer aspire 5720G
Submitter	: Maxim Levitsky <maximlevitsky@gmail.com>
Date		: 2009-04-06 23:52 (21 days old)
First-Bad-Commit: http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=a0d4922da2e4ccb0973095d8d29f36f6b1b5f703
References	: http://marc.info/?l=linux-kernel&m=123906202829074&w=4
Handled-By	: Rafael J. Wysocki <rjw@sisk.pl>

[Bug #13112] Oops in drain_array

[Rafael J. Wysocki]

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

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


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13112
Subject		: Oops in drain_array
Submitter	: Bart <mmx@riz.pl>
Date		: 2009-04-14 10:21 (13 days old)
References	: http://marc.info/?l=linux-kernel&m=123970493224628&w=4

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

[Rafael J. Wysocki]

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

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


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

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

[Rafael J. Wysocki]

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

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


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

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

[Rafael J. Wysocki]

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

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


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13100
Subject		: can't anymore even do a s2ram-s2disk-s2ram cycle on acer aspire 5720G
Submitter	: Maxim Levitsky <maximlevitsky-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Date		: 2009-04-06 23:52 (21 days old)
First-Bad-Commit: http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=a0d4922da2e4ccb0973095d8d29f36f6b1b5f703
References	: http://marc.info/?l=linux-kernel&m=123906202829074&w=4
Handled-By	: Rafael J. Wysocki <rjw-KKrjLPT3xs0@public.gmane.org>

[Bug #13178] Booting very slow

[Rafael J. Wysocki]

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

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


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

[Bug #13175] sata_nv incompatible with async scsi scan

[Rafael J. Wysocki]

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

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


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

[Bug #13184] Left audio channel broken after resume from suspend with Intel HDA

[Rafael J. Wysocki]

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

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


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13184
Subject		: Left audio channel broken after resume from suspend with Intel HDA
Submitter	: Tino Keitel <tino.keitel@tikei.de>
Date		: 2009-04-20 18:40 (7 days old)
References	: http://marc.info/?l=linux-kernel&m=124025290831292&w=4
Handled-By	: Takashi Iwai <tiwai@suse.de>

[Bug #13183] forcedeth: no link during initialization

[Rafael J. Wysocki]

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

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


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

[Bug #13183] forcedeth: no link during initialization

[Rafael J. Wysocki]

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

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


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

[Bug #13186] cpufreq timer teardown problem

[Rafael J. Wysocki]

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

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


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13186
Subject		: cpufreq timer teardown problem
Submitter	: Mathieu Desnoyers <mathieu.desnoyers@polymtl.ca>
Date		: 2009-04-23 14:00 (4 days old)
References	: http://marc.info/?l=linux-kernel&m=124049523515036&w=4
Handled-By	: Mathieu Desnoyers <mathieu.desnoyers@polymtl.ca>
Patch		: http://patchwork.kernel.org/patch/19754/
		  http://patchwork.kernel.org/patch/19753/

Re: 2.6.30-rc3-git1: Reported regressions 2.6.28 -> 2.6.29

[Matthew Wilcox]

On Sun, Apr 26, 2009 at 11:42:21AM +0200, Rafael J. Wysocki wrote:
> [NOTES:
>  * The number of regressions related to DRI is alarming, especially that for
>    some of the reporters have identified the "bad" commits.

Probably worth letting dri-devel know about this then ... cc added.

>  * I have closed some bugs where there was no activity.]
> 
> This message contains a list of some regressions introduced between 2.6.28 and
> 2.6.29, for which there are no fixes in the mainline I know of.  If any of them
> have been fixed already, please let me know.
> 
> If you know of any other unresolved regressions introduced between 2.6.28
> and 2.6.29, please let me know either and I'll add them to the list.
> Also, please let me know if any of the entries below are invalid.
> 
> Each entry from the list will be sent additionally in an automatic reply to
> this message with CCs to the people involved in reporting and handling the
> issue.
> 
> 
> Listed regressions statistics:
> 
>   Date          Total  Pending  Unresolved
>   ----------------------------------------
>   2009-04-26      160       29          27
>   2009-04-06      142       37          31
>   2009-03-21      128       29          26
>   2009-03-14      124       36          32
>   2009-03-03      108       33          28
>   2009-02-24       95       32          24
>   2009-02-14       85       33          27
>   2009-02-08       82       45          36
>   2009-02-04       66       51          39
>   2009-01-20       38       35          27
>   2009-01-11       13       13          10
> 
> 
> Unresolved regressions
> ----------------------
> 
> Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13184
> Subject		: Left audio channel broken after resume from suspend with Intel HDA
> Submitter	: Tino Keitel <tino.keitel@tikei.de>
> Date		: 2009-04-20 18:40 (7 days old)
> References	: http://marc.info/?l=linux-kernel&m=124025290831292&w=4
> Handled-By	: Takashi Iwai <tiwai@suse.de>
> 
> 
> Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13183
> Subject		: forcedeth: no link during initialization
> Submitter	: Harald Dunkel <harald.dunkel@t-online.de>
> Date		: 2009-04-23 13:02 (4 days old)
> References	: http://marc.info/?l=linux-kernel&m=124049180309233&w=4
> 
> 
> Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13178
> Subject		: Booting very slow
> Submitter	: Martin Knoblauch <spamtrap@knobisoft.de>
> Date		: 2009-04-24 12:45 (3 days old)
> References	: http://marc.info/?l=linux-kernel&m=124057716231773&w=4
> 
> 
> Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13175
> Subject		: sata_nv incompatible with async scsi scan
> Submitter	: Benny Halevy <bhalevy@panasas.com>
> Date		: 2009-04-21 7:03 (6 days old)
> References	: http://marc.info/?l=linux-kernel&m=124029746431777&w=4
> 
> 
> Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13172
> Subject		: Spontaneous reboots since 2.6.29-rc*
> Submitter	: Maciej Rutecki <maciej.rutecki@gmail.com>
> Date		: 2009-04-17 17:03 (10 days old)
> References	: http://marc.info/?l=linux-kernel&m=123998788921733&w=4
> 
> 
> Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13144
> Subject		: resume from suspend fails using video card i915
> Submitter	: C Sights <csights@fastmail.fm>
> Date		: 2009-04-21 17:03 (6 days old)
> 
> 
> Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13112
> Subject		: Oops in drain_array
> Submitter	: Bart <mmx@riz.pl>
> Date		: 2009-04-14 10:21 (13 days old)
> References	: http://marc.info/?l=linux-kernel&m=123970493224628&w=4
> 
> 
> Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13100
> Subject		: can't anymore even do a s2ram-s2disk-s2ram cycle on acer aspire 5720G
> Submitter	: Maxim Levitsky <maximlevitsky@gmail.com>
> Date		: 2009-04-06 23:52 (21 days old)
> First-Bad-Commit: http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=a0d4922da2e4ccb0973095d8d29f36f6b1b5f703
> References	: http://marc.info/?l=linux-kernel&m=123906202829074&w=4
> Handled-By	: Rafael J. Wysocki <rjw@sisk.pl>
> 
> 
> Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13074
> Subject		: gspca_stv06xx doesn't work with Logitech QuickCam Express (046d:0840)
> Submitter	: Paulo Matias <matias@archlinux-br.org>
> Date		: 2009-04-12 14:10 (15 days old)
> 
> 
> Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13072
> Subject		: forcedeth seems to switch off eth on shutdown
> Submitter	: Daniel Bierstedt <daniel.bierstedt@gmx.de>
> Date		: 2009-04-12 07:00 (15 days old)
> 
> 
> Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13040
> Subject		: DRM radeon
> Submitter	: Roger Luethi <rl@hellgate.ch>
> Date		: 2009-04-07 20:07 (20 days old)
> 
> 
> Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13032
> Subject		: 2.6.29 regression: network interfaces drop after suspend/resume
> Submitter	: Jose Marino <braket@hotmail.com>
> Date		: 2009-04-07 00:08 (20 days old)
> First-Bad-Commit: http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=31878dd86b7df9a147f5e6cc6e07092b4308782b
> 
> 
> Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13025
> Subject		: After upgrading to kernel 2.6.29, pulseaudio stopped with some strange error
> Submitter	: Yaroslav Isakov <yaroslav.isakov@gmail.com>
> Date		: 2009-04-06 19:47 (21 days old)
> 
> 
> Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13003
> Subject		: [2.6.29 regression] ivtv driver causes strange oops'es, disrupts software suspend
> Submitter	: Artem S. Tashkinov <t.artem@mailcity.com>
> Date		: 2009-04-03 14:57 (24 days old)
> Handled-By	: Hans Verkuil <hverkuil@xs4all.nl>
> 
> 
> 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 (24 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 (27 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 (29 days old)
> Handled-By	: Matt Carlson <mcarlson@broadcom.com>
> 
> 
> 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 (32 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 (42 days old)
> References	: http://marc.info/?l=linux-kernel&m=123720083515950&w=4
> 
> 
> Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12899
> Subject		: Crash in i915.ko: i915_driver_irq_handler
> Submitter	: Helge Bahmann <helge.bahmann@secunet.com>
> Date		: 2009-03-20 07:13 (38 days old)
> 
> 
> Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12861
> Subject		: Xorg fails to start "Failed to allocate space for kernel memory manager"
> Submitter	: Emil Karlson <jkarlson@cc.hut.fi>
> Date		: 2009-03-12 12:06 (46 days old)
> First-Bad-Commit: http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=ab657db12d7020629f26f30d287558a8d0e32b41
> 
> 
> Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=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 (54 days old)
> References	: http://marc.info/?l=linux-kernel&m=123619451406192&w=4
> 
> 
> 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 (65 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=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 (73 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	: Eric Anholt <eric@anholt.net>
> 
> 
> 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 (77 days old)
> First-Bad-Commit: http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=1cfe62c8010ac56e1bd3827e30386a87cc2f3594
> Handled-By	: Alexey Starikovskiy <astarikovskiy@suse.de>
> 
> 
> 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 (104 days old)
> References	: http://marc.info/?l=linux-kernel&m=123187185426236&w=4
> Handled-By	: Marcel Holtmann <marcel@holtmann.org>
> 
> 
> 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 (105 days old)
> References	: http://marc.info/?l=linux-kernel&m=123174591509586&w=4
> 		  http://lkml.org/lkml/2009/4/6/527
> Handled-By	: Bob Copeland <me@bobcopeland.com>
> 
> 
> Regressions with patches
> ------------------------
> 
> Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13186
> Subject		: cpufreq timer teardown problem
> Submitter	: Mathieu Desnoyers <mathieu.desnoyers@polymtl.ca>
> Date		: 2009-04-23 14:00 (4 days old)
> References	: http://marc.info/?l=linux-kernel&m=124049523515036&w=4
> Handled-By	: Mathieu Desnoyers <mathieu.desnoyers@polymtl.ca>
> Patch		: http://patchwork.kernel.org/patch/19754/
> 		  http://patchwork.kernel.org/patch/19753/
> 
> 
> 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 (30 days old)
> First-Bad-Commit: http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=8d6f0c8214928f7c5083dd54ecb69c5d615b516e
> Handled-By	: Andreas Herrmann <andreas.herrmann3@amd.com>
> Patch		: http://bugzilla.kernel.org/attachment.cgi?id=21070
> 
> 
> For details, please visit the bug entries and follow the links given in
> references.
> 
> As you can see, there is a Bugzilla entry for each of the listed regressions.
> There also is a Bugzilla entry used for tracking the regressions introduced
> between 2.6.28 and 2.6.29, unresolved as well as resolved, at:
> 
> http://bugzilla.kernel.org/show_bug.cgi?id=12398
> 
> Please let me know if there are any Bugzilla entries that should be added to
> the list in there.
> 
> Thanks,
> Rafael
> 
> --
> To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html

-- 
Matthew Wilcox				Intel Open Source Technology Centre
"Bill, look, we understand that you're interested in selling us this
operating system, but compare it to ours.  We can't possibly take such
a retrograde step."

Re: 2.6.30-rc3-git1: Reported regressions 2.6.28 -> 2.6.29

[Matthew Wilcox]

On Sun, Apr 26, 2009 at 11:42:21AM +0200, Rafael J. Wysocki wrote:
> [NOTES:
>  * The number of regressions related to DRI is alarming, especially that for
>    some of the reporters have identified the "bad" commits.

Probably worth letting dri-devel know about this then ... cc added.

>  * I have closed some bugs where there was no activity.]
> 
> This message contains a list of some regressions introduced between 2.6.28 and
> 2.6.29, for which there are no fixes in the mainline I know of.  If any of them
> have been fixed already, please let me know.
> 
> If you know of any other unresolved regressions introduced between 2.6.28
> and 2.6.29, please let me know either and I'll add them to the list.
> Also, please let me know if any of the entries below are invalid.
> 
> Each entry from the list will be sent additionally in an automatic reply to
> this message with CCs to the people involved in reporting and handling the
> issue.
> 
> 
> Listed regressions statistics:
> 
>   Date          Total  Pending  Unresolved
>   ----------------------------------------
>   2009-04-26      160       29          27
>   2009-04-06      142       37          31
>   2009-03-21      128       29          26
>   2009-03-14      124       36          32
>   2009-03-03      108       33          28
>   2009-02-24       95       32          24
>   2009-02-14       85       33          27
>   2009-02-08       82       45          36
>   2009-02-04       66       51          39
>   2009-01-20       38       35          27
>   2009-01-11       13       13          10
> 
> 
> Unresolved regressions
> ----------------------
> 
> Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13184
> Subject		: Left audio channel broken after resume from suspend with Intel HDA
> Submitter	: Tino Keitel <tino.keitel@tikei.de>
> Date		: 2009-04-20 18:40 (7 days old)
> References	: http://marc.info/?l=linux-kernel&m=124025290831292&w=4
> Handled-By	: Takashi Iwai <tiwai@suse.de>
> 
> 
> Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13183
> Subject		: forcedeth: no link during initialization
> Submitter	: Harald Dunkel <harald.dunkel@t-online.de>
> Date		: 2009-04-23 13:02 (4 days old)
> References	: http://marc.info/?l=linux-kernel&m=124049180309233&w=4
> 
> 
> Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13178
> Subject		: Booting very slow
> Submitter	: Martin Knoblauch <spamtrap@knobisoft.de>
> Date		: 2009-04-24 12:45 (3 days old)
> References	: http://marc.info/?l=linux-kernel&m=124057716231773&w=4
> 
> 
> Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13175
> Subject		: sata_nv incompatible with async scsi scan
> Submitter	: Benny Halevy <bhalevy@panasas.com>
> Date		: 2009-04-21 7:03 (6 days old)
> References	: http://marc.info/?l=linux-kernel&m=124029746431777&w=4
> 
> 
> Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13172
> Subject		: Spontaneous reboots since 2.6.29-rc*
> Submitter	: Maciej Rutecki <maciej.rutecki@gmail.com>
> Date		: 2009-04-17 17:03 (10 days old)
> References	: http://marc.info/?l=linux-kernel&m=123998788921733&w=4
> 
> 
> Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13144
> Subject		: resume from suspend fails using video card i915
> Submitter	: C Sights <csights@fastmail.fm>
> Date		: 2009-04-21 17:03 (6 days old)
> 
> 
> Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13112
> Subject		: Oops in drain_array
> Submitter	: Bart <mmx@riz.pl>
> Date		: 2009-04-14 10:21 (13 days old)
> References	: http://marc.info/?l=linux-kernel&m=123970493224628&w=4
> 
> 
> Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13100
> Subject		: can't anymore even do a s2ram-s2disk-s2ram cycle on acer aspire 5720G
> Submitter	: Maxim Levitsky <maximlevitsky@gmail.com>
> Date		: 2009-04-06 23:52 (21 days old)
> First-Bad-Commit: http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=a0d4922da2e4ccb0973095d8d29f36f6b1b5f703
> References	: http://marc.info/?l=linux-kernel&m=123906202829074&w=4
> Handled-By	: Rafael J. Wysocki <rjw@sisk.pl>
> 
> 
> Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13074
> Subject		: gspca_stv06xx doesn't work with Logitech QuickCam Express (046d:0840)
> Submitter	: Paulo Matias <matias@archlinux-br.org>
> Date		: 2009-04-12 14:10 (15 days old)
> 
> 
> Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13072
> Subject		: forcedeth seems to switch off eth on shutdown
> Submitter	: Daniel Bierstedt <daniel.bierstedt@gmx.de>
> Date		: 2009-04-12 07:00 (15 days old)
> 
> 
> Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13040
> Subject		: DRM radeon
> Submitter	: Roger Luethi <rl@hellgate.ch>
> Date		: 2009-04-07 20:07 (20 days old)
> 
> 
> Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13032
> Subject		: 2.6.29 regression: network interfaces drop after suspend/resume
> Submitter	: Jose Marino <braket@hotmail.com>
> Date		: 2009-04-07 00:08 (20 days old)
> First-Bad-Commit: http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=31878dd86b7df9a147f5e6cc6e07092b4308782b
> 
> 
> Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13025
> Subject		: After upgrading to kernel 2.6.29, pulseaudio stopped with some strange error
> Submitter	: Yaroslav Isakov <yaroslav.isakov@gmail.com>
> Date		: 2009-04-06 19:47 (21 days old)
> 
> 
> Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13003
> Subject		: [2.6.29 regression] ivtv driver causes strange oops'es, disrupts software suspend
> Submitter	: Artem S. Tashkinov <t.artem@mailcity.com>
> Date		: 2009-04-03 14:57 (24 days old)
> Handled-By	: Hans Verkuil <hverkuil@xs4all.nl>
> 
> 
> 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 (24 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 (27 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 (29 days old)
> Handled-By	: Matt Carlson <mcarlson@broadcom.com>
> 
> 
> 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 (32 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 (42 days old)
> References	: http://marc.info/?l=linux-kernel&m=123720083515950&w=4
> 
> 
> Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12899
> Subject		: Crash in i915.ko: i915_driver_irq_handler
> Submitter	: Helge Bahmann <helge.bahmann@secunet.com>
> Date		: 2009-03-20 07:13 (38 days old)
> 
> 
> Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12861
> Subject		: Xorg fails to start "Failed to allocate space for kernel memory manager"
> Submitter	: Emil Karlson <jkarlson@cc.hut.fi>
> Date		: 2009-03-12 12:06 (46 days old)
> First-Bad-Commit: http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=ab657db12d7020629f26f30d287558a8d0e32b41
> 
> 
> Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=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 (54 days old)
> References	: http://marc.info/?l=linux-kernel&m=123619451406192&w=4
> 
> 
> 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 (65 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=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 (73 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	: Eric Anholt <eric@anholt.net>
> 
> 
> 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 (77 days old)
> First-Bad-Commit: http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=1cfe62c8010ac56e1bd3827e30386a87cc2f3594
> Handled-By	: Alexey Starikovskiy <astarikovskiy@suse.de>
> 
> 
> 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 (104 days old)
> References	: http://marc.info/?l=linux-kernel&m=123187185426236&w=4
> Handled-By	: Marcel Holtmann <marcel@holtmann.org>
> 
> 
> 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 (105 days old)
> References	: http://marc.info/?l=linux-kernel&m=123174591509586&w=4
> 		  http://lkml.org/lkml/2009/4/6/527
> Handled-By	: Bob Copeland <me@bobcopeland.com>
> 
> 
> Regressions with patches
> ------------------------
> 
> Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13186
> Subject		: cpufreq timer teardown problem
> Submitter	: Mathieu Desnoyers <mathieu.desnoyers@polymtl.ca>
> Date		: 2009-04-23 14:00 (4 days old)
> References	: http://marc.info/?l=linux-kernel&m=124049523515036&w=4
> Handled-By	: Mathieu Desnoyers <mathieu.desnoyers@polymtl.ca>
> Patch		: http://patchwork.kernel.org/patch/19754/
> 		  http://patchwork.kernel.org/patch/19753/
> 
> 
> 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 (30 days old)
> First-Bad-Commit: http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=8d6f0c8214928f7c5083dd54ecb69c5d615b516e
> Handled-By	: Andreas Herrmann <andreas.herrmann3@amd.com>
> Patch		: http://bugzilla.kernel.org/attachment.cgi?id=21070
> 
> 
> For details, please visit the bug entries and follow the links given in
> references.
> 
> As you can see, there is a Bugzilla entry for each of the listed regressions.
> There also is a Bugzilla entry used for tracking the regressions introduced
> between 2.6.28 and 2.6.29, unresolved as well as resolved, at:
> 
> http://bugzilla.kernel.org/show_bug.cgi?id=12398
> 
> Please let me know if there are any Bugzilla entries that should be added to
> the list in there.
> 
> Thanks,
> Rafael
> 
> --
> To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html

-- 
Matthew Wilcox				Intel Open Source Technology Centre
"Bill, look, we understand that you're interested in selling us this
operating system, but compare it to ours.  We can't possibly take such
a retrograde step."

------------------------------------------------------------------------------
Crystal Reports &#45; New Free Runtime and 30 Day Trial
Check out the new simplified licensign option that enables unlimited
royalty&#45;free distribution of the report engine for externally facing 
server and web deployment.
http://p.sf.net/sfu/businessobjects
--

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

[Angel]

On Sun, 26 Apr 2009 11:46:26 +0200 (CEST)
"Rafael J. Wysocki" <rjw@sisk.pl> wrote:

> This message has been generated automatically as a part of a report
> of regressions introduced between 2.6.28 and 2.6.29.
> 
> The following bug entry is on the current list of known regressions
> introduced between 2.6.28 and 2.6.29.  Please verify if it still should
> be listed and let me know (either way).

I've tested with kernel 2.6.29.1. The problem still persists. While everything works fine with 2.6.28 or lower, starting X (both 1.3 and 1.5) with DRI enabled on a 2.6.29 kernel results in a garbled screen and unresponsive keyboard.


-- 
Angel <angel@pearlgates.net>

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

[Angel]

On Sun, 26 Apr 2009 11:46:26 +0200 (CEST)
"Rafael J. Wysocki" <rjw@sisk.pl> wrote:

> This message has been generated automatically as a part of a report
> of regressions introduced between 2.6.28 and 2.6.29.
> 
> The following bug entry is on the current list of known regressions
> introduced between 2.6.28 and 2.6.29.  Please verify if it still should
> be listed and let me know (either way).

I've tested with kernel 2.6.29.1. The problem still persists. While everything works fine with 2.6.28 or lower, starting X (both 1.3 and 1.5) with DRI enabled on a 2.6.29 kernel results in a garbled screen and unresponsive keyboard.


-- 
Angel <angel@pearlgates.net>

------------------------------------------------------------------------------
Crystal Reports &#45; New Free Runtime and 30 Day Trial
Check out the new simplified licensign option that enables unlimited
royalty&#45;free distribution of the report engine for externally facing 
server and web deployment.
http://p.sf.net/sfu/businessobjects
--

Re: [Bug #13186] cpufreq timer teardown problem

[Mathieu Desnoyers]

* Rafael J. Wysocki (rjw@sisk.pl) wrote:
> This message has been generated automatically as a part of a report
> of regressions introduced between 2.6.28 and 2.6.29.
> 
> The following bug entry is on the current list of known regressions
> introduced between 2.6.28 and 2.6.29.  Please verify if it still should
> be listed and let me know (either way).
> 

I've had no news that the patches I proposed has been considered for
-stable. They fix the teardown problem here. So I guess it's better to
wait for the patches to get into -stable before we close this bug ?

Mathieu

> 
> Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13186
> Subject		: cpufreq timer teardown problem
> Submitter	: Mathieu Desnoyers <mathieu.desnoyers@polymtl.ca>
> Date		: 2009-04-23 14:00 (4 days old)
> References	: http://marc.info/?l=linux-kernel&m=124049523515036&w=4
> Handled-By	: Mathieu Desnoyers <mathieu.desnoyers@polymtl.ca>
> Patch		: http://patchwork.kernel.org/patch/19754/
> 		  http://patchwork.kernel.org/patch/19753/
> 
> 
> 

-- 
Mathieu Desnoyers
OpenPGP key fingerprint: 8CD5 52C3 8E3C 4140 715F  BA06 3F25 A8FE 3BAE 9A68

Re: [Bug #13186] cpufreq timer teardown problem

[Mathieu Desnoyers]

* Rafael J. Wysocki (rjw-KKrjLPT3xs0@public.gmane.org) wrote:
> This message has been generated automatically as a part of a report
> of regressions introduced between 2.6.28 and 2.6.29.
> 
> The following bug entry is on the current list of known regressions
> introduced between 2.6.28 and 2.6.29.  Please verify if it still should
> be listed and let me know (either way).
> 

I've had no news that the patches I proposed has been considered for
-stable. They fix the teardown problem here. So I guess it's better to
wait for the patches to get into -stable before we close this bug ?

Mathieu

> 
> Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13186
> Subject		: cpufreq timer teardown problem
> Submitter	: Mathieu Desnoyers <mathieu.desnoyers-scC8bbJcJLCw5LPnMra/2Q@public.gmane.org>
> Date		: 2009-04-23 14:00 (4 days old)
> References	: http://marc.info/?l=linux-kernel&m=124049523515036&w=4
> Handled-By	: Mathieu Desnoyers <mathieu.desnoyers-scC8bbJcJLCw5LPnMra/2Q@public.gmane.org>
> Patch		: http://patchwork.kernel.org/patch/19754/
> 		  http://patchwork.kernel.org/patch/19753/
> 
> 
> 

-- 
Mathieu Desnoyers
OpenPGP key fingerprint: 8CD5 52C3 8E3C 4140 715F  BA06 3F25 A8FE 3BAE 9A68

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

[Rafael J. Wysocki]

On Sunday 26 April 2009, Angel wrote:
> On Sun, 26 Apr 2009 11:46:26 +0200 (CEST)
> "Rafael J. Wysocki" <rjw@sisk.pl> wrote:
> 
> > This message has been generated automatically as a part of a report
> > of regressions introduced between 2.6.28 and 2.6.29.
> > 
> > The following bug entry is on the current list of known regressions
> > introduced between 2.6.28 and 2.6.29.  Please verify if it still should
> > be listed and let me know (either way).
> 
> I've tested with kernel 2.6.29.1. The problem still persists. While everything works fine with 2.6.28 or lower, starting X (both 1.3 and 1.5) with DRI enabled on a 2.6.29 kernel results in a garbled screen and unresponsive keyboard.

Thanks for the update.

Can you also test 2.6.30-rc3, please?

Rafael

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

[Rafael J. Wysocki]

On Sunday 26 April 2009, Angel wrote:
> On Sun, 26 Apr 2009 11:46:26 +0200 (CEST)
> "Rafael J. Wysocki" <rjw@sisk.pl> wrote:
> 
> > This message has been generated automatically as a part of a report
> > of regressions introduced between 2.6.28 and 2.6.29.
> > 
> > The following bug entry is on the current list of known regressions
> > introduced between 2.6.28 and 2.6.29.  Please verify if it still should
> > be listed and let me know (either way).
> 
> I've tested with kernel 2.6.29.1. The problem still persists. While everything works fine with 2.6.28 or lower, starting X (both 1.3 and 1.5) with DRI enabled on a 2.6.29 kernel results in a garbled screen and unresponsive keyboard.

Thanks for the update.

Can you also test 2.6.30-rc3, please?

Rafael

------------------------------------------------------------------------------
Crystal Reports &#45; New Free Runtime and 30 Day Trial
Check out the new simplified licensign option that enables unlimited
royalty&#45;free distribution of the report engine for externally facing 
server and web deployment.
http://p.sf.net/sfu/businessobjects
--

Re: [Bug #13186] cpufreq timer teardown problem

[Rafael J. Wysocki]

On Sunday 26 April 2009, Mathieu Desnoyers wrote:
> * Rafael J. Wysocki (rjw@sisk.pl) wrote:
> > This message has been generated automatically as a part of a report
> > of regressions introduced between 2.6.28 and 2.6.29.
> > 
> > The following bug entry is on the current list of known regressions
> > introduced between 2.6.28 and 2.6.29.  Please verify if it still should
> > be listed and let me know (either way).
> > 
> 
> I've had no news that the patches I proposed has been considered for
> -stable. They fix the teardown problem here. So I guess it's better to
> wait for the patches to get into -stable before we close this bug ?

In fact the bug is closeable as soon as they are in the Linus' tree.  Are they
in it right now?

Thanks,
Rafael

Re: [Bug #13186] cpufreq timer teardown problem

[Mathieu Desnoyers]

* Rafael J. Wysocki (rjw@sisk.pl) wrote:
> On Sunday 26 April 2009, Mathieu Desnoyers wrote:
> > * Rafael J. Wysocki (rjw@sisk.pl) wrote:
> > > This message has been generated automatically as a part of a report
> > > of regressions introduced between 2.6.28 and 2.6.29.
> > > 
> > > The following bug entry is on the current list of known regressions
> > > introduced between 2.6.28 and 2.6.29.  Please verify if it still should
> > > be listed and let me know (either way).
> > > 
> > 
> > I've had no news that the patches I proposed has been considered for
> > -stable. They fix the teardown problem here. So I guess it's better to
> > wait for the patches to get into -stable before we close this bug ?
> 
> In fact the bug is closeable as soon as they are in the Linus' tree.  Are they
> in it right now?
> 

Nope, Andrew pulled the conservative governor fix for 2.6.30-rc in his
tree, but that's about it.

The fixes for ondemand 2.6.28, 2.6.29 and 2.6.30-rc have not been pulled
yet. The fix for conservative 2.6.28, 2.6.29 has not been pulled
neither.

Mathieu

> Thanks,
> Rafael

-- 
Mathieu Desnoyers
OpenPGP key fingerprint: 8CD5 52C3 8E3C 4140 715F  BA06 3F25 A8FE 3BAE 9A68

Re: [Bug #13186] cpufreq timer teardown problem

[Mathieu Desnoyers]

* Rafael J. Wysocki (rjw-KKrjLPT3xs0@public.gmane.org) wrote:
> On Sunday 26 April 2009, Mathieu Desnoyers wrote:
> > * Rafael J. Wysocki (rjw-KKrjLPT3xs0@public.gmane.org) wrote:
> > > This message has been generated automatically as a part of a report
> > > of regressions introduced between 2.6.28 and 2.6.29.
> > > 
> > > The following bug entry is on the current list of known regressions
> > > introduced between 2.6.28 and 2.6.29.  Please verify if it still should
> > > be listed and let me know (either way).
> > > 
> > 
> > I've had no news that the patches I proposed has been considered for
> > -stable. They fix the teardown problem here. So I guess it's better to
> > wait for the patches to get into -stable before we close this bug ?
> 
> In fact the bug is closeable as soon as they are in the Linus' tree.  Are they
> in it right now?
> 

Nope, Andrew pulled the conservative governor fix for 2.6.30-rc in his
tree, but that's about it.

The fixes for ondemand 2.6.28, 2.6.29 and 2.6.30-rc have not been pulled
yet. The fix for conservative 2.6.28, 2.6.29 has not been pulled
neither.

Mathieu

> Thanks,
> Rafael

-- 
Mathieu Desnoyers
OpenPGP key fingerprint: 8CD5 52C3 8E3C 4140 715F  BA06 3F25 A8FE 3BAE 9A68

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

[Nico Schottelius]

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

Rafael J. Wysocki [Sun, Apr 26, 2009 at 11:46:25AM +0200]:
> This message has been generated automatically as a part of a report
> of regressions introduced between 2.6.28 and 2.6.29.

Sure, still broken. For some version it works, for most newer not,
as reported.

Can we stop that nag-service and spent time in fixing it better?

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 #13112] Oops in drain_array

[David Rientjes]

On Sun, 26 Apr 2009, Rafael J. Wysocki wrote:

> This message has been generated automatically as a part of a report
> of regressions introduced between 2.6.28 and 2.6.29.
> 
> The following bug entry is on the current list of known regressions
> introduced between 2.6.28 and 2.6.29.  Please verify if it still should
> be listed and let me know (either way).
> 
> 
> Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13112
> Subject		: Oops in drain_array
> Submitter	: Bart <mmx@riz.pl>
> Date		: 2009-04-14 10:21 (13 days old)
> References	: http://marc.info/?l=linux-kernel&m=123970493224628&w=4
> 

Bart, is it possible to try with CONFIG_DEBUG_SLAB enabled?

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

[Daniel Bierstedt]

Hello,

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

Am Sonntag, den 26.04.2009, 11:46 +0200 schrieb Rafael J. Wysocki:
> This message has been generated automatically as a part of a report
> of regressions introduced between 2.6.28 and 2.6.29.
> 
> The following bug entry is on the current list of known regressions
> introduced between 2.6.28 and 2.6.29.  Please verify if it still should
> be listed and let me know (either way).
> 
> 
> Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13072
> Subject		: forcedeth seems to switch off eth on shutdown
> Submitter	: Daniel Bierstedt <daniel.bierstedt@gmx.de>
> Date		: 2009-04-12 07:00 (15 days old)
> 

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

[Rafael J. Wysocki]

On Sunday 26 April 2009, Nico Schottelius wrote:
> Rafael J. Wysocki [Sun, Apr 26, 2009 at 11:46:25AM +0200]:
> > This message has been generated automatically as a part of a report
> > of regressions introduced between 2.6.28 and 2.6.29.
> 
> Sure, still broken. For some version it works, for most newer not,
> as reported.
> 
> Can we stop that nag-service and spent time in fixing it better?

Well, I'm not familiar with the code that broke and this is a way of notifying
the right people of the problem.

Thanks,
Rafael

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

[Rafael J. Wysocki]

On Sunday 26 April 2009, Nico Schottelius wrote:
> Rafael J. Wysocki [Sun, Apr 26, 2009 at 11:46:25AM +0200]:
> > This message has been generated automatically as a part of a report
> > of regressions introduced between 2.6.28 and 2.6.29.
> 
> Sure, still broken. For some version it works, for most newer not,
> as reported.
> 
> Can we stop that nag-service and spent time in fixing it better?

Well, I'm not familiar with the code that broke and this is a way of notifying
the right people of the problem.

Thanks,
Rafael

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

[Rafael J. Wysocki]

On Sunday 26 April 2009, Daniel Bierstedt wrote:
> Hello,
> 
> yes, this bug entry should be listed. This bug prevents people from
> using live-cd's or testing the 2.6.29 (if they know about this bug...).

Thanks for the update.

Rafael

Re: [Bug #13003] [2.6.29 regression] ivtv driver causes strange oops'es, disrupts software suspend

[Hans Verkuil]

On Sunday 26 April 2009 11:46:28 Rafael J. Wysocki wrote:
> This message has been generated automatically as a part of a report
> of regressions introduced between 2.6.28 and 2.6.29.
>
> The following bug entry is on the current list of known regressions
> introduced between 2.6.28 and 2.6.29.  Please verify if it still should
> be listed and let me know (either way).
>
>
> Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13003
> Subject		: [2.6.29 regression] ivtv driver causes strange oops'es,
> disrupts software suspend Submitter	: Artem S. Tashkinov
> <t.artem@mailcity.com>
> Date		: 2009-04-03 14:57 (24 days old)
> Handled-By	: Hans Verkuil <hverkuil@xs4all.nl>

This isn't a 2.6.29 regression. It is a bug - somewhere - but it's also been 
reproduced under 2.6.28 so it doesn't qualify as a regression.

Regards,

	Hans

-- 
Hans Verkuil - video4linux developer - sponsored by TANDBERG

Re: [Bug #13003] [2.6.29 regression] ivtv driver causes strange oops'es, disrupts software suspend

[Hans Verkuil]

On Sunday 26 April 2009 11:46:28 Rafael J. Wysocki wrote:
> This message has been generated automatically as a part of a report
> of regressions introduced between 2.6.28 and 2.6.29.
>
> The following bug entry is on the current list of known regressions
> introduced between 2.6.28 and 2.6.29.  Please verify if it still should
> be listed and let me know (either way).
>
>
> Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13003
> Subject		: [2.6.29 regression] ivtv driver causes strange oops'es,
> disrupts software suspend Submitter	: Artem S. Tashkinov
> <t.artem-VInPYn6yXxRWk0Htik3J/w@public.gmane.org>
> Date		: 2009-04-03 14:57 (24 days old)
> Handled-By	: Hans Verkuil <hverkuil-qWit8jRvyhVmR6Xm/wNWPw@public.gmane.org>

This isn't a 2.6.29 regression. It is a bug - somewhere - but it's also been 
reproduced under 2.6.28 so it doesn't qualify as a regression.

Regards,

	Hans

-- 
Hans Verkuil - video4linux developer - sponsored by TANDBERG

Re: [Bug #13178] Booting very slow

[Martin Knoblauch]

----- Original Message ----

> From: Rafael J. Wysocki <rjw@sisk.pl>
> To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
> Cc: Kernel Testers List <kernel-testers@vger.kernel.org>; Martin Knoblauch <spamtrap@knobisoft.de>
> Sent: Sunday, April 26, 2009 11:46:31 AM
> Subject: [Bug #13178] Booting very slow
> 
> This message has been generated automatically as a part of a report
> of regressions introduced between 2.6.28 and 2.6.29.
> 
> The following bug entry is on the current list of known regressions
> introduced between 2.6.28 and 2.6.29.  Please verify if it still should
> be listed and let me know (either way).
> 
> 
> Bug-Entry    : http://bugzilla.kernel.org/show_bug.cgi?id=13178
> Subject        : Booting very slow
> Submitter    : Martin Knoblauch 
> Date        : 2009-04-24 12:45 (3 days old)
> References    : http://marc.info/?l=linux-kernel&m=124057716231773&w=4

 Not really sure whether this is a real regression. Between 2.6.28 and 2.6.29 the content of /proc/mounts for sysfs changed from

/sys /sys sysfs rw 0 0

to

none /sys sysfs rw 0 0


 This breaks RHEL-4.3 userland which parses /proc/mounts in the firmware hotplug agent to find the mount-point for sysfs. As a result firmware loading started to fail in 2.6.29. There is a simple fix in the /etc/hotplug/firmware.agent script (just assume /sys as it is done elsewhere).

 Your call.

Cheers
Martin

Re: [Bug #13112] Oops in drain_array

[Pekka Enberg]

On Sun, 26 Apr 2009, Rafael J. Wysocki wrote:
>> This message has been generated automatically as a part of a report
>> of regressions introduced between 2.6.28 and 2.6.29.
>>
>> The following bug entry is on the current list of known regressions
>> introduced between 2.6.28 and 2.6.29.  Please verify if it still should
>> be listed and let me know (either way).
>>
>>
>> Bug-Entry     : http://bugzilla.kernel.org/show_bug.cgi?id=13112
>> Subject               : Oops in drain_array
>> Submitter     : Bart <mmx@riz.pl>
>> Date          : 2009-04-14 10:21 (13 days old)
>> References    : http://marc.info/?l=linux-kernel&m=123970493224628&w=4

On Sun, Apr 26, 2009 at 11:19 PM, David Rientjes <rientjes@google.com> wrote:
> Bart, is it possible to try with CONFIG_DEBUG_SLAB enabled?

Please also enable CONFIG_DEBUG_LIST. Looking at the oops:

  18:   4a 8b 8c eb 68 01 00    mov    0x168(%rbx,%r13,8),%rcx # l3 =
cachep->nodelists[node];
  1f:   00
  20:   48 8b 16                mov    (%rsi),%rdx
  23:   48 8b 46 08             mov    0x8(%rsi),%rax
  27:   48 89 42 08             mov    %rax,0x8(%rdx)
  2b:*  48 89 10                mov    %rdx,(%rax)     <-- trapping instruction
  2e:   89 e8                   mov    %ebp,%eax
  30:   48 c7 06 00 01 10 00    movq   $0x100100,(%rsi)
  37:   48 c7 46 08 00 02 20    movq   $0x200200,0x8(%rsi)

it seems like list_del() in free_block() explodes because because
->prev ("rax") of slab->list is bogus ("0000000000000cd0").

                                Pekka

Re: [Bug #13112] Oops in drain_array

[Pekka Enberg]

On Sun, 26 Apr 2009, Rafael J. Wysocki wrote:
>> This message has been generated automatically as a part of a report
>> of regressions introduced between 2.6.28 and 2.6.29.
>>
>> The following bug entry is on the current list of known regressions
>> introduced between 2.6.28 and 2.6.29.  Please verify if it still should
>> be listed and let me know (either way).
>>
>>
>> Bug-Entry     : http://bugzilla.kernel.org/show_bug.cgi?id=13112
>> Subject               : Oops in drain_array
>> Submitter     : Bart <mmx-G/jkD+u3s4s@public.gmane.org>
>> Date          : 2009-04-14 10:21 (13 days old)
>> References    : http://marc.info/?l=linux-kernel&m=123970493224628&w=4

On Sun, Apr 26, 2009 at 11:19 PM, David Rientjes <rientjes-hpIqsD4AKlfQT0dZR+AlfA@public.gmane.org> wrote:
> Bart, is it possible to try with CONFIG_DEBUG_SLAB enabled?

Please also enable CONFIG_DEBUG_LIST. Looking at the oops:

  18:   4a 8b 8c eb 68 01 00    mov    0x168(%rbx,%r13,8),%rcx # l3 =
cachep->nodelists[node];
  1f:   00
  20:   48 8b 16                mov    (%rsi),%rdx
  23:   48 8b 46 08             mov    0x8(%rsi),%rax
  27:   48 89 42 08             mov    %rax,0x8(%rdx)
  2b:*  48 89 10                mov    %rdx,(%rax)     <-- trapping instruction
  2e:   89 e8                   mov    %ebp,%eax
  30:   48 c7 06 00 01 10 00    movq   $0x100100,(%rsi)
  37:   48 c7 46 08 00 02 20    movq   $0x200200,0x8(%rsi)

it seems like list_del() in free_block() explodes because because
->prev ("rax") of slab->list is bogus ("0000000000000cd0").

                                Pekka

Re: [Bug #13112] Oops in drain_array

[Christoph Lameter]

On Mon, 27 Apr 2009, Pekka Enberg wrote:

>   18:   4a 8b 8c eb 68 01 00    mov    0x168(%rbx,%r13,8),%rcx # l3 =
> cachep->nodelists[node];
>   1f:   00
>   20:   48 8b 16                mov    (%rsi),%rdx
>   23:   48 8b 46 08             mov    0x8(%rsi),%rax
>   27:   48 89 42 08             mov    %rax,0x8(%rdx)
>   2b:*  48 89 10                mov    %rdx,(%rax)     <-- trapping instruction
>   2e:   89 e8                   mov    %ebp,%eax
>   30:   48 c7 06 00 01 10 00    movq   $0x100100,(%rsi)
>   37:   48 c7 46 08 00 02 20    movq   $0x200200,0x8(%rsi)
>
> it seems like list_del() in free_block() explodes because because
> ->prev ("rax") of slab->list is bogus ("0000000000000cd0").

Where do I find the rest of the information regarding this report?
bugzilla does only contain a pointer to the initial report on lkml no
discussion.

Typically these oopses occur because the slab header at the beginning of a
slab is overwritten. Enable debugging. Switching to SLUB would give better
diagnostics.

Re: [Bug #13112] Oops in drain_array

[Christoph Lameter]

On Mon, 27 Apr 2009, Pekka Enberg wrote:

>   18:   4a 8b 8c eb 68 01 00    mov    0x168(%rbx,%r13,8),%rcx # l3 =
> cachep->nodelists[node];
>   1f:   00
>   20:   48 8b 16                mov    (%rsi),%rdx
>   23:   48 8b 46 08             mov    0x8(%rsi),%rax
>   27:   48 89 42 08             mov    %rax,0x8(%rdx)
>   2b:*  48 89 10                mov    %rdx,(%rax)     <-- trapping instruction
>   2e:   89 e8                   mov    %ebp,%eax
>   30:   48 c7 06 00 01 10 00    movq   $0x100100,(%rsi)
>   37:   48 c7 46 08 00 02 20    movq   $0x200200,0x8(%rsi)
>
> it seems like list_del() in free_block() explodes because because
> ->prev ("rax") of slab->list is bogus ("0000000000000cd0").

Where do I find the rest of the information regarding this report?
bugzilla does only contain a pointer to the initial report on lkml no
discussion.

Typically these oopses occur because the slab header at the beginning of a
slab is overwritten. Enable debugging. Switching to SLUB would give better
diagnostics.

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

[Jesse Barnes]

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

On Sun, 26 Apr 2009 11:46:26 +0200 (CEST)
"Rafael J. Wysocki" <rjw@sisk.pl> wrote:

> This message has been generated automatically as a part of a report
> of regressions introduced between 2.6.28 and 2.6.29.
> 
> The following bug entry is on the current list of known regressions
> introduced between 2.6.28 and 2.6.29.  Please verify if it still
> should be listed and let me know (either way).
> 
> 
> 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 (65 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

I think we had a workaround for this (attached), but it sounds like
Robert has tracked down the root cause (search for "Broken vblanks on
Intel" on dri-devel@lists.sourceforge.net).  Will try to get the fix
into the Intel driver soon.  Fortunately this doesn't seem to be biting
a lot of people (at least not that I've heard); I certainly have a hard
time reproducing it.

-- 
Jesse Barnes, Intel Open Source Technology Center

[-- Attachment #2: drm-vblank-wait-fix.patch --]
[-- Type: text/x-patch, Size: 1372 bytes --]

diff --git a/drivers/gpu/drm/drm_irq.c b/drivers/gpu/drm/drm_irq.c
index 69aa0ab..c41cba4 100644
--- a/drivers/gpu/drm/drm_irq.c
+++ b/drivers/gpu/drm/drm_irq.c
@@ -341,7 +341,7 @@ int drm_control(struct drm_device *dev, void *data,
  * vblank events since the system was booted, including lost events due to
  * modesetting activity.
  */
-u32 drm_vblank_count(struct drm_device *dev, int crtc)
+unsigned int drm_vblank_count(struct drm_device *dev, int crtc)
 {
 	return atomic_read(&dev->_vblank_count[crtc]);
 }
@@ -522,6 +522,11 @@ out:
 	return ret;
 }
 
+#define frame_after_eq(a,b)	       \
+	(typecheck(unsigned int, a) && \
+	 typecheck(unsigned int, b) && \
+	 ((int)(a) - (int)(b) >= 0))
+
 /**
  * Wait for VBLANK.
  *
@@ -589,10 +594,12 @@ int drm_wait_vblank(struct drm_device *dev, void *data,
 	DRM_DEBUG("waiting on vblank count %d, crtc %d\n",
 		  vblwait->request.sequence, crtc);
 	dev->last_vblank_wait[crtc] = vblwait->request.sequence;
+
+	/* Wait for the sequence number to pass or IRQs to get disabled */
 	DRM_WAIT_ON(ret, dev->vbl_queue[crtc], 3 * DRM_HZ,
-		    (((drm_vblank_count(dev, crtc) -
-		       vblwait->request.sequence) <= (1 << 23)) ||
-		     !dev->irq_enabled));
+		    frame_after_eq(drm_vblank_count(dev, crtc),
+				   vblwait->request.sequence) ||
+		    !dev->irq_enabled);
 
 	if (ret != -EINTR) {
 		struct timeval now;

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

[Jesse Barnes]

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

On Sun, 26 Apr 2009 11:46:26 +0200 (CEST)
"Rafael J. Wysocki" <rjw-KKrjLPT3xs0@public.gmane.org> wrote:

> This message has been generated automatically as a part of a report
> of regressions introduced between 2.6.28 and 2.6.29.
> 
> The following bug entry is on the current list of known regressions
> introduced between 2.6.28 and 2.6.29.  Please verify if it still
> should be listed and let me know (either way).
> 
> 
> 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 (65 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

I think we had a workaround for this (attached), but it sounds like
Robert has tracked down the root cause (search for "Broken vblanks on
Intel" on dri-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org).  Will try to get the fix
into the Intel driver soon.  Fortunately this doesn't seem to be biting
a lot of people (at least not that I've heard); I certainly have a hard
time reproducing it.

-- 
Jesse Barnes, Intel Open Source Technology Center

[-- Attachment #2: drm-vblank-wait-fix.patch --]
[-- Type: text/x-patch, Size: 1372 bytes --]

diff --git a/drivers/gpu/drm/drm_irq.c b/drivers/gpu/drm/drm_irq.c
index 69aa0ab..c41cba4 100644
--- a/drivers/gpu/drm/drm_irq.c
+++ b/drivers/gpu/drm/drm_irq.c
@@ -341,7 +341,7 @@ int drm_control(struct drm_device *dev, void *data,
  * vblank events since the system was booted, including lost events due to
  * modesetting activity.
  */
-u32 drm_vblank_count(struct drm_device *dev, int crtc)
+unsigned int drm_vblank_count(struct drm_device *dev, int crtc)
 {
 	return atomic_read(&dev->_vblank_count[crtc]);
 }
@@ -522,6 +522,11 @@ out:
 	return ret;
 }
 
+#define frame_after_eq(a,b)	       \
+	(typecheck(unsigned int, a) && \
+	 typecheck(unsigned int, b) && \
+	 ((int)(a) - (int)(b) >= 0))
+
 /**
  * Wait for VBLANK.
  *
@@ -589,10 +594,12 @@ int drm_wait_vblank(struct drm_device *dev, void *data,
 	DRM_DEBUG("waiting on vblank count %d, crtc %d\n",
 		  vblwait->request.sequence, crtc);
 	dev->last_vblank_wait[crtc] = vblwait->request.sequence;
+
+	/* Wait for the sequence number to pass or IRQs to get disabled */
 	DRM_WAIT_ON(ret, dev->vbl_queue[crtc], 3 * DRM_HZ,
-		    (((drm_vblank_count(dev, crtc) -
-		       vblwait->request.sequence) <= (1 << 23)) ||
-		     !dev->irq_enabled));
+		    frame_after_eq(drm_vblank_count(dev, crtc),
+				   vblwait->request.sequence) ||
+		    !dev->irq_enabled);
 
 	if (ret != -EINTR) {
 		struct timeval now;

Re: [Bug #13112] Oops in drain_array

[Bart]

On Mon, 27 Apr 2009, Christoph Lameter wrote:

> On Mon, 27 Apr 2009, Pekka Enberg wrote:
>
>>   18:   4a 8b 8c eb 68 01 00    mov    0x168(%rbx,%r13,8),%rcx # l3 =
>> cachep->nodelists[node];
>>   1f:   00
>>   20:   48 8b 16                mov    (%rsi),%rdx
>>   23:   48 8b 46 08             mov    0x8(%rsi),%rax
>>   27:   48 89 42 08             mov    %rax,0x8(%rdx)
>>   2b:*  48 89 10                mov    %rdx,(%rax)     <-- trapping instruction
>>   2e:   89 e8                   mov    %ebp,%eax
>>   30:   48 c7 06 00 01 10 00    movq   $0x100100,(%rsi)
>>   37:   48 c7 46 08 00 02 20    movq   $0x200200,0x8(%rsi)
>>
>> it seems like list_del() in free_block() explodes because because
>> ->prev ("rax") of slab->list is bogus ("0000000000000cd0").
>
> Where do I find the rest of the information regarding this report?
> bugzilla does only contain a pointer to the initial report on lkml no
> discussion.
>
> Typically these oopses occur because the slab header at the beginning of a
> slab is overwritten. Enable debugging. Switching to SLUB would give better
> diagnostics.

After turning the suggested debuging options I've got tons of these when 
trying to stress the tape device like before:

Apr 27 16:57:30 fs kernel: [   96.446708] slab error in verify_redzone_free(): cache `size-128': memory outside object was overwritten
Apr 27 16:57:30 fs kernel: [   96.446713] Pid: 0, comm: swapper Not tainted 2.6.29.1-64 #2
Apr 27 16:57:30 fs kernel: [   96.446715] Call Trace:
Apr 27 16:57:30 fs kernel: [   96.446717]  <IRQ>  [<ffffffff8029adc5>] __slab_error+0x1f/0x25
Apr 27 16:57:30 fs kernel: [   96.446728]  [<ffffffff8029b24b>] cache_free_debugcheck+0x108/0x1d6
Apr 27 16:57:30 fs kernel: [   96.446731]  [<ffffffff8029b473>] kfree+0x81/0xc2
Apr 27 16:57:30 fs kernel: [   96.446735]  [<ffffffff802bd311>] bio_free_map_data+0xc/0x1e
Apr 27 16:57:30 fs kernel: [   96.446738]  [<ffffffff802bdc6d>] bio_uncopy_user+0x38/0x48
Apr 27 16:57:30 fs kernel: [   96.446742]  [<ffffffff803670e6>] blk_rq_unmap_user+0x1e/0x45
Apr 27 16:57:30 fs kernel: [   96.446747]  [<ffffffff8046ed7f>] st_scsi_execute_end+0x4e/0x5e
Apr 27 16:57:30 fs kernel: [   96.446751]  [<ffffffff8036425f>] blk_end_io+0x55/0x76
Apr 27 16:57:30 fs kernel: [   96.446754]  [<ffffffff804a17ad>] mpt_interrupt+0x422/0x53f
Apr 27 16:57:30 fs kernel: [   96.446758]  [<ffffffff8044be0b>] scsi_io_completion+0x18f/0x415
Apr 27 16:57:30 fs kernel: [   96.446762]  [<ffffffff80368160>] blk_done_softirq+0x62/0x72
Apr 27 16:57:30 fs kernel: [   96.446766]  [<ffffffff802523d0>] __do_softirq+0x7f/0x138
Apr 27 16:57:30 fs kernel: [   96.446770]  [<ffffffff80238d70>] ack_apic_level+0x46/0xce
Apr 27 16:57:30 fs kernel: [   96.446774]  [<ffffffff80225b3c>] call_softirq+0x1c/0x28
Apr 27 16:57:30 fs kernel: [   96.446777]  [<ffffffff8022706c>] do_softirq+0x2c/0x6c
Apr 27 16:57:30 fs kernel: [   96.446780]  [<ffffffff802272b1>] do_IRQ+0xb6/0xd5
Apr 27 16:57:30 fs kernel: [   96.446784]  [<ffffffff80225413>] ret_from_intr+0x0/0xa
Apr 27 16:57:30 fs kernel: [   96.446785]  <EOI>  [<ffffffff80564e7a>] udp_poll+0x0/0x10e
Apr 27 16:57:30 fs kernel: [   96.446793]  [<ffffffff8022b26c>] mwait_idle+0x63/0x66
Apr 27 16:57:30 fs kernel: [   96.446795]  [<ffffffff802238d6>] cpu_idle+0x40/0x5e
Apr 27 16:57:30 fs kernel: [   96.446798] ffff88013c197b48: redzone 1:0xd84156c5635688c0, redzone 2:0xffffe20004209348.

Can I help by testing an rc version if this happens too ?

-- 
  Regards,
  Bart mmx@riz.pl

Re: [Bug #13112] Oops in drain_array

[Christoph Lameter]

On Mon, 27 Apr 2009, Bart wrote:

> Apr 27 16:57:30 fs kernel: [   96.446708] slab error in verify_redzone_free():
> cache `size-128': memory outside object was overwritten

Allright so a write after or before a 128 byte kmalloc object. Can
you switch to the SLUB allocator so that we can get memory dumps of
the corruption which will help to diagnose this further?

Re: [Bug #13112] Oops in drain_array

[Christoph Lameter]

On Mon, 27 Apr 2009, Bart wrote:

> Apr 27 16:57:30 fs kernel: [   96.446708] slab error in verify_redzone_free():
> cache `size-128': memory outside object was overwritten

Allright so a write after or before a 128 byte kmalloc object. Can
you switch to the SLUB allocator so that we can get memory dumps of
the corruption which will help to diagnose this further?

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

[Jos van der Ende]

On Sun, 26 Apr 2009 19:43:44 +0200
"Rafael J. Wysocki" <rjw@sisk.pl> wrote:

> On Sunday 26 April 2009, Angel wrote:
> > On Sun, 26 Apr 2009 11:46:26 +0200 (CEST)
> > 
> > I've tested with kernel 2.6.29.1. The problem still persists. While everything works fine with 2.6.28 or lower, starting X (both 1.3 and 1.5) with DRI enabled on a 2.6.29 kernel results in a garbled screen and unresponsive keyboard.
> 
> Thanks for the update.
> 
> Can you also test 2.6.30-rc3, please?

Sure. Still broken in exactly the same way. (Garbled screen, non-working keyboard. System can still be ssh-ed into.)


-- 
Jos van der Ende <seraph@xs4all.nl>

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

[Jos van der Ende]

On Sun, 26 Apr 2009 19:43:44 +0200
"Rafael J. Wysocki" <rjw-KKrjLPT3xs0@public.gmane.org> wrote:

> On Sunday 26 April 2009, Angel wrote:
> > On Sun, 26 Apr 2009 11:46:26 +0200 (CEST)
> > 
> > I've tested with kernel 2.6.29.1. The problem still persists. While everything works fine with 2.6.28 or lower, starting X (both 1.3 and 1.5) with DRI enabled on a 2.6.29 kernel results in a garbled screen and unresponsive keyboard.
> 
> Thanks for the update.
> 
> Can you also test 2.6.30-rc3, please?

Sure. Still broken in exactly the same way. (Garbled screen, non-working keyboard. System can still be ssh-ed into.)


-- 
Jos van der Ende <seraph-qWit8jRvyhVmR6Xm/wNWPw@public.gmane.org>

Re: [Bug #13112] Oops in drain_array

[David Rientjes]

On Mon, 27 Apr 2009, Bart wrote:

> After turning the suggested debuging options I've got tons of these when
> trying to stress the tape device like before:
> 
> Apr 27 16:57:30 fs kernel: [   96.446708] slab error in verify_redzone_free():
> cache `size-128': memory outside object was overwritten
> Apr 27 16:57:30 fs kernel: [   96.446713] Pid: 0, comm: swapper Not tainted
> 2.6.29.1-64 #2
> Apr 27 16:57:30 fs kernel: [   96.446715] Call Trace:
> Apr 27 16:57:30 fs kernel: [   96.446717]  <IRQ>  [<ffffffff8029adc5>]
> __slab_error+0x1f/0x25
> Apr 27 16:57:30 fs kernel: [   96.446728]  [<ffffffff8029b24b>]
> cache_free_debugcheck+0x108/0x1d6
> Apr 27 16:57:30 fs kernel: [   96.446731]  [<ffffffff8029b473>]
> kfree+0x81/0xc2
> Apr 27 16:57:30 fs kernel: [   96.446735]  [<ffffffff802bd311>]
> bio_free_map_data+0xc/0x1e

This appears to be kfree(bmd->iovecs) in bio_free_map_data().  It looks 
like the memcpy size in bio_set_map_data() overrides the kmalloc size; in 
other words, for a redzone error, bio->bi_vcnt > nr_pages in 
bio_copy_user_iov().

Re: [Bug #13112] Oops in drain_array

[David Rientjes]

On Mon, 27 Apr 2009, Bart wrote:

> After turning the suggested debuging options I've got tons of these when
> trying to stress the tape device like before:
> 
> Apr 27 16:57:30 fs kernel: [   96.446708] slab error in verify_redzone_free():
> cache `size-128': memory outside object was overwritten
> Apr 27 16:57:30 fs kernel: [   96.446713] Pid: 0, comm: swapper Not tainted
> 2.6.29.1-64 #2
> Apr 27 16:57:30 fs kernel: [   96.446715] Call Trace:
> Apr 27 16:57:30 fs kernel: [   96.446717]  <IRQ>  [<ffffffff8029adc5>]
> __slab_error+0x1f/0x25
> Apr 27 16:57:30 fs kernel: [   96.446728]  [<ffffffff8029b24b>]
> cache_free_debugcheck+0x108/0x1d6
> Apr 27 16:57:30 fs kernel: [   96.446731]  [<ffffffff8029b473>]
> kfree+0x81/0xc2
> Apr 27 16:57:30 fs kernel: [   96.446735]  [<ffffffff802bd311>]
> bio_free_map_data+0xc/0x1e

This appears to be kfree(bmd->iovecs) in bio_free_map_data().  It looks 
like the memcpy size in bio_set_map_data() overrides the kmalloc size; in 
other words, for a redzone error, bio->bi_vcnt > nr_pages in 
bio_copy_user_iov().

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

[Sitsofe Wheeler]

On Mon, Apr 27, 2009 at 09:46:51AM -0700, Jesse Barnes wrote:
> On Sun, 26 Apr 2009 11:46:26 +0200 (CEST)
> "Rafael J. Wysocki" <rjw@sisk.pl> wrote:
> 
> > This message has been generated automatically as a part of a report
> > of regressions introduced between 2.6.28 and 2.6.29.
> > 
> > The following bug entry is on the current list of known regressions
> > introduced between 2.6.28 and 2.6.29.  Please verify if it still
> > should be listed and let me know (either way).

The problem is still here in 2.6.29-rc3.

> I think we had a workaround for this (attached), but it sounds like
> Robert has tracked down the root cause (search for "Broken vblanks on
> Intel" on dri-devel@lists.sourceforge.net).  Will try to get the fix

http://www.mail-archive.com/dri-devel@lists.sourceforge.net/msg39370.html
seems to be it.

> into the Intel driver soon.  Fortunately this doesn't seem to be biting
> a lot of people (at least not that I've heard); I certainly have a hard
> time reproducing it.

The patch that was attached to Jesse's mail seems to resolve the
problem...

-- 
Sitsofe | http://sucs.org/~sits/

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

[Sitsofe Wheeler]

On Mon, Apr 27, 2009 at 09:46:51AM -0700, Jesse Barnes wrote:
> On Sun, 26 Apr 2009 11:46:26 +0200 (CEST)
> "Rafael J. Wysocki" <rjw-KKrjLPT3xs0@public.gmane.org> wrote:
> 
> > This message has been generated automatically as a part of a report
> > of regressions introduced between 2.6.28 and 2.6.29.
> > 
> > The following bug entry is on the current list of known regressions
> > introduced between 2.6.28 and 2.6.29.  Please verify if it still
> > should be listed and let me know (either way).

The problem is still here in 2.6.29-rc3.

> I think we had a workaround for this (attached), but it sounds like
> Robert has tracked down the root cause (search for "Broken vblanks on
> Intel" on dri-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org).  Will try to get the fix

http://www.mail-archive.com/dri-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org/msg39370.html
seems to be it.

> into the Intel driver soon.  Fortunately this doesn't seem to be biting
> a lot of people (at least not that I've heard); I certainly have a hard
> time reproducing it.

The patch that was attached to Jesse's mail seems to resolve the
problem...

-- 
Sitsofe | http://sucs.org/~sits/

Re: [Bug #13112] Oops in drain_array

[Jens Axboe]

On Mon, Apr 27 2009, David Rientjes wrote:
> On Mon, 27 Apr 2009, Bart wrote:
> 
> > After turning the suggested debuging options I've got tons of these when
> > trying to stress the tape device like before:
> > 
> > Apr 27 16:57:30 fs kernel: [   96.446708] slab error in verify_redzone_free():
> > cache `size-128': memory outside object was overwritten
> > Apr 27 16:57:30 fs kernel: [   96.446713] Pid: 0, comm: swapper Not tainted
> > 2.6.29.1-64 #2
> > Apr 27 16:57:30 fs kernel: [   96.446715] Call Trace:
> > Apr 27 16:57:30 fs kernel: [   96.446717]  <IRQ>  [<ffffffff8029adc5>]
> > __slab_error+0x1f/0x25
> > Apr 27 16:57:30 fs kernel: [   96.446728]  [<ffffffff8029b24b>]
> > cache_free_debugcheck+0x108/0x1d6
> > Apr 27 16:57:30 fs kernel: [   96.446731]  [<ffffffff8029b473>]
> > kfree+0x81/0xc2
> > Apr 27 16:57:30 fs kernel: [   96.446735]  [<ffffffff802bd311>]
> > bio_free_map_data+0xc/0x1e
> 
> This appears to be kfree(bmd->iovecs) in bio_free_map_data().  It looks 
> like the memcpy size in bio_set_map_data() overrides the kmalloc size; in 
> other words, for a redzone error, bio->bi_vcnt > nr_pages in 
> bio_copy_user_iov().

What -git version was this reproduced with?

-- 
Jens Axboe

Re: [Bug #13112] Oops in drain_array

[Jens Axboe]

On Mon, Apr 27 2009, David Rientjes wrote:
> On Mon, 27 Apr 2009, Bart wrote:
> 
> > After turning the suggested debuging options I've got tons of these when
> > trying to stress the tape device like before:
> > 
> > Apr 27 16:57:30 fs kernel: [   96.446708] slab error in verify_redzone_free():
> > cache `size-128': memory outside object was overwritten
> > Apr 27 16:57:30 fs kernel: [   96.446713] Pid: 0, comm: swapper Not tainted
> > 2.6.29.1-64 #2
> > Apr 27 16:57:30 fs kernel: [   96.446715] Call Trace:
> > Apr 27 16:57:30 fs kernel: [   96.446717]  <IRQ>  [<ffffffff8029adc5>]
> > __slab_error+0x1f/0x25
> > Apr 27 16:57:30 fs kernel: [   96.446728]  [<ffffffff8029b24b>]
> > cache_free_debugcheck+0x108/0x1d6
> > Apr 27 16:57:30 fs kernel: [   96.446731]  [<ffffffff8029b473>]
> > kfree+0x81/0xc2
> > Apr 27 16:57:30 fs kernel: [   96.446735]  [<ffffffff802bd311>]
> > bio_free_map_data+0xc/0x1e
> 
> This appears to be kfree(bmd->iovecs) in bio_free_map_data().  It looks 
> like the memcpy size in bio_set_map_data() overrides the kmalloc size; in 
> other words, for a redzone error, bio->bi_vcnt > nr_pages in 
> bio_copy_user_iov().

What -git version was this reproduced with?

-- 
Jens Axboe

Re: [Bug #13112] Oops in drain_array

[FUJITA Tomonori]

On Mon, 27 Apr 2009 13:36:46 -0700 (PDT)
David Rientjes <rientjes@google.com> wrote:

> On Mon, 27 Apr 2009, Bart wrote:
> 
> > After turning the suggested debuging options I've got tons of these when
> > trying to stress the tape device like before:
> > 
> > Apr 27 16:57:30 fs kernel: [   96.446708] slab error in verify_redzone_free():
> > cache `size-128': memory outside object was overwritten
> > Apr 27 16:57:30 fs kernel: [   96.446713] Pid: 0, comm: swapper Not tainted
> > 2.6.29.1-64 #2
> > Apr 27 16:57:30 fs kernel: [   96.446715] Call Trace:
> > Apr 27 16:57:30 fs kernel: [   96.446717]  <IRQ>  [<ffffffff8029adc5>]
> > __slab_error+0x1f/0x25
> > Apr 27 16:57:30 fs kernel: [   96.446728]  [<ffffffff8029b24b>]
> > cache_free_debugcheck+0x108/0x1d6
> > Apr 27 16:57:30 fs kernel: [   96.446731]  [<ffffffff8029b473>]
> > kfree+0x81/0xc2
> > Apr 27 16:57:30 fs kernel: [   96.446735]  [<ffffffff802bd311>]
> > bio_free_map_data+0xc/0x1e
> 
> This appears to be kfree(bmd->iovecs) in bio_free_map_data().  It looks 
> like the memcpy size in bio_set_map_data() overrides the kmalloc size; in 
> other words, for a redzone error, bio->bi_vcnt > nr_pages in 
> bio_copy_user_iov().

Can you try this?

diff --git a/fs/bio.c b/fs/bio.c
index 7bbc98f..6a09356 100644
--- a/fs/bio.c
+++ b/fs/bio.c
@@ -817,6 +817,9 @@ struct bio *bio_copy_user_iov(struct request_queue *q,
 		len += iov[i].iov_len;
 	}
 
+	if (offset)
+		nr_pages += 1;
+
 	bmd = bio_alloc_map_data(nr_pages, iov_count, gfp_mask);
 	if (!bmd)
 		return ERR_PTR(-ENOMEM);

Re: [Bug #13112] Oops in drain_array

[FUJITA Tomonori]

On Mon, 27 Apr 2009 13:36:46 -0700 (PDT)
David Rientjes <rientjes-hpIqsD4AKlfQT0dZR+AlfA@public.gmane.org> wrote:

> On Mon, 27 Apr 2009, Bart wrote:
> 
> > After turning the suggested debuging options I've got tons of these when
> > trying to stress the tape device like before:
> > 
> > Apr 27 16:57:30 fs kernel: [   96.446708] slab error in verify_redzone_free():
> > cache `size-128': memory outside object was overwritten
> > Apr 27 16:57:30 fs kernel: [   96.446713] Pid: 0, comm: swapper Not tainted
> > 2.6.29.1-64 #2
> > Apr 27 16:57:30 fs kernel: [   96.446715] Call Trace:
> > Apr 27 16:57:30 fs kernel: [   96.446717]  <IRQ>  [<ffffffff8029adc5>]
> > __slab_error+0x1f/0x25
> > Apr 27 16:57:30 fs kernel: [   96.446728]  [<ffffffff8029b24b>]
> > cache_free_debugcheck+0x108/0x1d6
> > Apr 27 16:57:30 fs kernel: [   96.446731]  [<ffffffff8029b473>]
> > kfree+0x81/0xc2
> > Apr 27 16:57:30 fs kernel: [   96.446735]  [<ffffffff802bd311>]
> > bio_free_map_data+0xc/0x1e
> 
> This appears to be kfree(bmd->iovecs) in bio_free_map_data().  It looks 
> like the memcpy size in bio_set_map_data() overrides the kmalloc size; in 
> other words, for a redzone error, bio->bi_vcnt > nr_pages in 
> bio_copy_user_iov().

Can you try this?

diff --git a/fs/bio.c b/fs/bio.c
index 7bbc98f..6a09356 100644
--- a/fs/bio.c
+++ b/fs/bio.c
@@ -817,6 +817,9 @@ struct bio *bio_copy_user_iov(struct request_queue *q,
 		len += iov[i].iov_len;
 	}
 
+	if (offset)
+		nr_pages += 1;
+
 	bmd = bio_alloc_map_data(nr_pages, iov_count, gfp_mask);
 	if (!bmd)
 		return ERR_PTR(-ENOMEM);

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

[FUJITA Tomonori]

On Sun, 26 Apr 2009 11:46:28 +0200 (CEST)
"Rafael J. Wysocki" <rjw@sisk.pl> wrote:

> This message has been generated automatically as a part of a report
> of regressions introduced between 2.6.28 and 2.6.29.
> 
> The following bug entry is on the current list of known regressions
> introduced between 2.6.28 and 2.6.29.  Please verify if it still should
> be listed and let me know (either way).
> 
> 
> 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 (24 days old)

Probably, this is not a regression.

He doesn't hit this problem with 2.6.29 when he uses the kernel boot
option that he used with 2.6.28. I have no idea how not using
'allowdac' can solve the problem though.

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

[FUJITA Tomonori]

On Sun, 26 Apr 2009 11:46:28 +0200 (CEST)
"Rafael J. Wysocki" <rjw-KKrjLPT3xs0@public.gmane.org> wrote:

> This message has been generated automatically as a part of a report
> of regressions introduced between 2.6.28 and 2.6.29.
> 
> The following bug entry is on the current list of known regressions
> introduced between 2.6.28 and 2.6.29.  Please verify if it still should
> be listed and let me know (either way).
> 
> 
> 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 (24 days old)

Probably, this is not a regression.

He doesn't hit this problem with 2.6.29 when he uses the kernel boot
option that he used with 2.6.28. I have no idea how not using
'allowdac' can solve the problem though.

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

[Данила Жукоцкий]

No, it is regression. I can reproduce that without allowdac and any
other unnecessary boot options. In later discussion Grant Grundler ask
me apply patch that show 32 bit dma devices in my system. Results I
attached to bugreport. Looks like only one 32 bit dma device in my
system is ata controller, sata-nv. I can stable reproduce IOMMU out of
space when I write data to sata drive.

2009/4/28 FUJITA Tomonori <fujita.tomonori@lab.ntt.co.jp>:
> On Sun, 26 Apr 2009 11:46:28 +0200 (CEST)
> "Rafael J. Wysocki" <rjw@sisk.pl> wrote:
>
>> This message has been generated automatically as a part of a report
>> of regressions introduced between 2.6.28 and 2.6.29.
>>
>> The following bug entry is on the current list of known regressions
>> introduced between 2.6.28 and 2.6.29.  Please verify if it still should
>> be listed and let me know (either way).
>>
>>
>> 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 (24 days old)
>
> Probably, this is not a regression.
>
> He doesn't hit this problem with 2.6.29 when he uses the kernel boot
> option that he used with 2.6.28. I have no idea how not using
> 'allowdac' can solve the problem though.
>



-- 
С уважением Данила Жукоцкий, системный администратор ЗАО "Роснефтегазмаш"

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

[Данила Жукоцкий]

No, it is regression. I can reproduce that without allowdac and any
other unnecessary boot options. In later discussion Grant Grundler ask
me apply patch that show 32 bit dma devices in my system. Results I
attached to bugreport. Looks like only one 32 bit dma device in my
system is ata controller, sata-nv. I can stable reproduce IOMMU out of
space when I write data to sata drive.

2009/4/28 FUJITA Tomonori <fujita.tomonori-Zyj7fXuS5i5L9jVzuh4AOg@public.gmane.org>:
> On Sun, 26 Apr 2009 11:46:28 +0200 (CEST)
> "Rafael J. Wysocki" <rjw-KKrjLPT3xs0@public.gmane.org> wrote:
>
>> This message has been generated automatically as a part of a report
>> of regressions introduced between 2.6.28 and 2.6.29.
>>
>> The following bug entry is on the current list of known regressions
>> introduced between 2.6.28 and 2.6.29.  Please verify if it still should
>> be listed and let me know (either way).
>>
>>
>> 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 (24 days old)
>
> Probably, this is not a regression.
>
> He doesn't hit this problem with 2.6.29 when he uses the kernel boot
> option that he used with 2.6.28. I have no idea how not using
> 'allowdac' can solve the problem though.
>



-- 
С уважением Данила Жукоцкий, системный администратор ЗАО "Роснефтегазмаш"

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

[FUJITA Tomonori]

On Tue, 28 Apr 2009 14:18:57 +0500
**UNKNOWN CHARSET** <optimusgd@gmail.com> wrote:

> No, it is regression. I can reproduce that without allowdac and any
> other unnecessary boot options.

Hmm, in the bug repport, you said that you can't reproduce the problem:

http://bugzilla.kernel.org/show_bug.cgi?id=13001#c15

I can't find your comment like, "I can reproduce that without
allowdac".

> In later discussion Grant Grundler ask
> me apply patch that show 32 bit dma devices in my system. Results I
> attached to bugreport. Looks like only one 32 bit dma device in my
> system is ata controller, sata-nv.

Hmm, looks like http://bugzilla.kernel.org/attachment.cgi?id=20895
said that pata_amd and sata_nv use 32bit dma mask.


> I can stable reproduce IOMMU out of space when I write data to sata
> drive.

Ok, let's figure out what's wrong.

First, can you test v2.6.30-rc3 with the following patch?

http://www.kernel.org/pub/linux/kernel/people/tomo/misc/gart-debug.diff


Note that please enable CONFIG_DMA_API_DEBUG, CONFIG_IOMMU_DEBUG, and
CONFIG_IOMMU_LEAK and see if you can reproduce the problem (of course,
don't use any kernel option).

When the kernel is out of IOMMU space, it prints some useful
information.

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

[FUJITA Tomonori]

On Tue, 28 Apr 2009 14:18:57 +0500
**UNKNOWN CHARSET** <optimusgd-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:

> No, it is regression. I can reproduce that without allowdac and any
> other unnecessary boot options.

Hmm, in the bug repport, you said that you can't reproduce the problem:

http://bugzilla.kernel.org/show_bug.cgi?id=13001#c15

I can't find your comment like, "I can reproduce that without
allowdac".

> In later discussion Grant Grundler ask
> me apply patch that show 32 bit dma devices in my system. Results I
> attached to bugreport. Looks like only one 32 bit dma device in my
> system is ata controller, sata-nv.

Hmm, looks like http://bugzilla.kernel.org/attachment.cgi?id=20895
said that pata_amd and sata_nv use 32bit dma mask.


> I can stable reproduce IOMMU out of space when I write data to sata
> drive.

Ok, let's figure out what's wrong.

First, can you test v2.6.30-rc3 with the following patch?

http://www.kernel.org/pub/linux/kernel/people/tomo/misc/gart-debug.diff


Note that please enable CONFIG_DMA_API_DEBUG, CONFIG_IOMMU_DEBUG, and
CONFIG_IOMMU_LEAK and see if you can reproduce the problem (of course,
don't use any kernel option).

When the kernel is out of IOMMU space, it prints some useful
information.

Re: [Bug #13112] Oops in drain_array

[Bart]

> On Mon, 27 Apr 2009 13:36:46 -0700 (PDT)
> David Rientjes <rientjes@google.com> wrote:
>
>> On Mon, 27 Apr 2009, Bart wrote:
>>
>>> After turning the suggested debuging options I've got tons of these when
>>> trying to stress the tape device like before:
>>>
>>> Apr 27 16:57:30 fs kernel: [   96.446708] slab error in verify_redzone_free():
>>> cache `size-128': memory outside object was overwritten
>>> Apr 27 16:57:30 fs kernel: [   96.446713] Pid: 0, comm: swapper Not tainted
>>> 2.6.29.1-64 #2
>>> Apr 27 16:57:30 fs kernel: [   96.446715] Call Trace:
>>> Apr 27 16:57:30 fs kernel: [   96.446717]  <IRQ>  [<ffffffff8029adc5>]
>>> __slab_error+0x1f/0x25
>>> Apr 27 16:57:30 fs kernel: [   96.446728]  [<ffffffff8029b24b>]
>>> cache_free_debugcheck+0x108/0x1d6
>>> Apr 27 16:57:30 fs kernel: [   96.446731]  [<ffffffff8029b473>]
>>> kfree+0x81/0xc2
>>> Apr 27 16:57:30 fs kernel: [   96.446735]  [<ffffffff802bd311>]
>>> bio_free_map_data+0xc/0x1e
>>
>> This appears to be kfree(bmd->iovecs) in bio_free_map_data().  It looks
>> like the memcpy size in bio_set_map_data() overrides the kmalloc size; in
>> other words, for a redzone error, bio->bi_vcnt > nr_pages in
>> bio_copy_user_iov().
>
> Can you try this?
>
> diff --git a/fs/bio.c b/fs/bio.c
> index 7bbc98f..6a09356 100644
> --- a/fs/bio.c
> +++ b/fs/bio.c
> @@ -817,6 +817,9 @@ struct bio *bio_copy_user_iov(struct request_queue *q,
> 		len += iov[i].iov_len;
> 	}
>
> +	if (offset)
> +		nr_pages += 1;
> +
> 	bmd = bio_alloc_map_data(nr_pages, iov_count, gfp_mask);
> 	if (!bmd)
> 		return ERR_PTR(-ENOMEM);
>

There are no more errors in the dmesg after applying this patch to 
2.6.29.2.

Without this patch I can reproduce this kind of errors on 
2.6.29.1, 2.6.29.2.

I've not tested this patch with 2.6.29.1 and 2.6.30rc3-git3.
I will try to reproduce the error on 2.6.30rc3-git3 as soon as I compile 
it.

-- 
  Regards
  Bart mmx@riz.pl

Re: [Bug #13112] Oops in drain_array

[Bart]

> On Mon, 27 Apr 2009 13:36:46 -0700 (PDT)
> David Rientjes <rientjes-hpIqsD4AKlfQT0dZR+AlfA@public.gmane.org> wrote:
>
>> On Mon, 27 Apr 2009, Bart wrote:
>>
>>> After turning the suggested debuging options I've got tons of these when
>>> trying to stress the tape device like before:
>>>
>>> Apr 27 16:57:30 fs kernel: [   96.446708] slab error in verify_redzone_free():
>>> cache `size-128': memory outside object was overwritten
>>> Apr 27 16:57:30 fs kernel: [   96.446713] Pid: 0, comm: swapper Not tainted
>>> 2.6.29.1-64 #2
>>> Apr 27 16:57:30 fs kernel: [   96.446715] Call Trace:
>>> Apr 27 16:57:30 fs kernel: [   96.446717]  <IRQ>  [<ffffffff8029adc5>]
>>> __slab_error+0x1f/0x25
>>> Apr 27 16:57:30 fs kernel: [   96.446728]  [<ffffffff8029b24b>]
>>> cache_free_debugcheck+0x108/0x1d6
>>> Apr 27 16:57:30 fs kernel: [   96.446731]  [<ffffffff8029b473>]
>>> kfree+0x81/0xc2
>>> Apr 27 16:57:30 fs kernel: [   96.446735]  [<ffffffff802bd311>]
>>> bio_free_map_data+0xc/0x1e
>>
>> This appears to be kfree(bmd->iovecs) in bio_free_map_data().  It looks
>> like the memcpy size in bio_set_map_data() overrides the kmalloc size; in
>> other words, for a redzone error, bio->bi_vcnt > nr_pages in
>> bio_copy_user_iov().
>
> Can you try this?
>
> diff --git a/fs/bio.c b/fs/bio.c
> index 7bbc98f..6a09356 100644
> --- a/fs/bio.c
> +++ b/fs/bio.c
> @@ -817,6 +817,9 @@ struct bio *bio_copy_user_iov(struct request_queue *q,
> 		len += iov[i].iov_len;
> 	}
>
> +	if (offset)
> +		nr_pages += 1;
> +
> 	bmd = bio_alloc_map_data(nr_pages, iov_count, gfp_mask);
> 	if (!bmd)
> 		return ERR_PTR(-ENOMEM);
>

There are no more errors in the dmesg after applying this patch to 
2.6.29.2.

Without this patch I can reproduce this kind of errors on 
2.6.29.1, 2.6.29.2.

I've not tested this patch with 2.6.29.1 and 2.6.30rc3-git3.
I will try to reproduce the error on 2.6.30rc3-git3 as soon as I compile 
it.

-- 
  Regards
  Bart mmx-G/jkD+u3s4s@public.gmane.org

Re: [Bug #13112] Oops in drain_array

[Bart]

On Mon, 27 Apr 2009, Christoph Lameter wrote:

> On Mon, 27 Apr 2009, Bart wrote:
>
>> Apr 27 16:57:30 fs kernel: [   96.446708] slab error in verify_redzone_free():
>> cache `size-128': memory outside object was overwritten
>
> Allright so a write after or before a 128 byte kmalloc object. Can
> you switch to the SLUB allocator so that we can get memory dumps of
> the corruption which will help to diagnose this further?

After switching to SLUB I had a complete hard freeze when trying to 
reproduce the error. I've got a photo of the screen but I dont know if it 
is usefull so I did not copied it to txt:

http://bz.riz.pl/IMAG0032.jpg

-- 
  Regards
  Bart mmx@riz.pl

Re: [Bug #13112] Oops in drain_array

[Bart]

On Mon, 27 Apr 2009, Christoph Lameter wrote:

> On Mon, 27 Apr 2009, Bart wrote:
>
>> Apr 27 16:57:30 fs kernel: [   96.446708] slab error in verify_redzone_free():
>> cache `size-128': memory outside object was overwritten
>
> Allright so a write after or before a 128 byte kmalloc object. Can
> you switch to the SLUB allocator so that we can get memory dumps of
> the corruption which will help to diagnose this further?

After switching to SLUB I had a complete hard freeze when trying to 
reproduce the error. I've got a photo of the screen but I dont know if it 
is usefull so I did not copied it to txt:

http://bz.riz.pl/IMAG0032.jpg

-- 
  Regards
  Bart mmx-G/jkD+u3s4s@public.gmane.org

Re: [Bug #13112] Oops in drain_array

[FUJITA Tomonori]

On Tue, 28 Apr 2009 14:43:37 +0200 (CEST)
Bart <mmx@riz.pl> wrote:

> > On Mon, 27 Apr 2009 13:36:46 -0700 (PDT)
> > David Rientjes <rientjes@google.com> wrote:
> >
> >> On Mon, 27 Apr 2009, Bart wrote:
> >>
> >>> After turning the suggested debuging options I've got tons of these when
> >>> trying to stress the tape device like before:
> >>>
> >>> Apr 27 16:57:30 fs kernel: [   96.446708] slab error in verify_redzone_free():
> >>> cache `size-128': memory outside object was overwritten
> >>> Apr 27 16:57:30 fs kernel: [   96.446713] Pid: 0, comm: swapper Not tainted
> >>> 2.6.29.1-64 #2
> >>> Apr 27 16:57:30 fs kernel: [   96.446715] Call Trace:
> >>> Apr 27 16:57:30 fs kernel: [   96.446717]  <IRQ>  [<ffffffff8029adc5>]
> >>> __slab_error+0x1f/0x25
> >>> Apr 27 16:57:30 fs kernel: [   96.446728]  [<ffffffff8029b24b>]
> >>> cache_free_debugcheck+0x108/0x1d6
> >>> Apr 27 16:57:30 fs kernel: [   96.446731]  [<ffffffff8029b473>]
> >>> kfree+0x81/0xc2
> >>> Apr 27 16:57:30 fs kernel: [   96.446735]  [<ffffffff802bd311>]
> >>> bio_free_map_data+0xc/0x1e
> >>
> >> This appears to be kfree(bmd->iovecs) in bio_free_map_data().  It looks
> >> like the memcpy size in bio_set_map_data() overrides the kmalloc size; in
> >> other words, for a redzone error, bio->bi_vcnt > nr_pages in
> >> bio_copy_user_iov().
> >
> > Can you try this?
> >
> > diff --git a/fs/bio.c b/fs/bio.c
> > index 7bbc98f..6a09356 100644
> > --- a/fs/bio.c
> > +++ b/fs/bio.c
> > @@ -817,6 +817,9 @@ struct bio *bio_copy_user_iov(struct request_queue *q,
> > 		len += iov[i].iov_len;
> > 	}
> >
> > +	if (offset)
> > +		nr_pages += 1;
> > +
> > 	bmd = bio_alloc_map_data(nr_pages, iov_count, gfp_mask);
> > 	if (!bmd)
> > 		return ERR_PTR(-ENOMEM);
> >
> 
> There are no more errors in the dmesg after applying this patch to 
> 2.6.29.2.
> 
> Without this patch I can reproduce this kind of errors on 
> 2.6.29.1, 2.6.29.2.
> 
> I've not tested this patch with 2.6.29.1 and 2.6.30rc3-git3.
> I will try to reproduce the error on 2.6.30rc3-git3 as soon as I compile 
> it.

Thanks for testing! And very sorry about the bug.

I'm sure that you hit the same bug with 2.6.30-rc3-git.

Jens, can you please apply this against 2.6.30-rc (and we need this
for 2.6.29.x too)?

I know that bio_copy_user_iov() is hacky. I'll try to clean up the
mapping API later.

=
From: FUJITA Tomonori <fujita.tomonori@lab.ntt.co.jp>
Subject: [PATCH] bio: fix memcpy corruption in bio_copy_user_iov()

st driver uses blk_rq_map_user() in order to just build a request out
of page frames. In this case, map_data->offset is a non zero value and
iov[0].iov_base is NULL. We need to increase nr_pages for that.

Cc: stable@kernel.org
Signed-off-by: FUJITA Tomonori <fujita.tomonori@lab.ntt.co.jp>
---
 fs/bio.c |    3 +++
 1 files changed, 3 insertions(+), 0 deletions(-)

diff --git a/fs/bio.c b/fs/bio.c
index 7bbc98f..9871164 100644
--- a/fs/bio.c
+++ b/fs/bio.c
@@ -817,6 +817,9 @@ struct bio *bio_copy_user_iov(struct request_queue *q,
 		len += iov[i].iov_len;
 	}
 
+	if (offset)
+		nr_pages++;
+
 	bmd = bio_alloc_map_data(nr_pages, iov_count, gfp_mask);
 	if (!bmd)
 		return ERR_PTR(-ENOMEM);
-- 
1.6.0.6

Re: [Bug #13112] Oops in drain_array

[FUJITA Tomonori]

On Tue, 28 Apr 2009 14:43:37 +0200 (CEST)
Bart <mmx-G/jkD+u3s4s@public.gmane.org> wrote:

> > On Mon, 27 Apr 2009 13:36:46 -0700 (PDT)
> > David Rientjes <rientjes-hpIqsD4AKlfQT0dZR+AlfA@public.gmane.org> wrote:
> >
> >> On Mon, 27 Apr 2009, Bart wrote:
> >>
> >>> After turning the suggested debuging options I've got tons of these when
> >>> trying to stress the tape device like before:
> >>>
> >>> Apr 27 16:57:30 fs kernel: [   96.446708] slab error in verify_redzone_free():
> >>> cache `size-128': memory outside object was overwritten
> >>> Apr 27 16:57:30 fs kernel: [   96.446713] Pid: 0, comm: swapper Not tainted
> >>> 2.6.29.1-64 #2
> >>> Apr 27 16:57:30 fs kernel: [   96.446715] Call Trace:
> >>> Apr 27 16:57:30 fs kernel: [   96.446717]  <IRQ>  [<ffffffff8029adc5>]
> >>> __slab_error+0x1f/0x25
> >>> Apr 27 16:57:30 fs kernel: [   96.446728]  [<ffffffff8029b24b>]
> >>> cache_free_debugcheck+0x108/0x1d6
> >>> Apr 27 16:57:30 fs kernel: [   96.446731]  [<ffffffff8029b473>]
> >>> kfree+0x81/0xc2
> >>> Apr 27 16:57:30 fs kernel: [   96.446735]  [<ffffffff802bd311>]
> >>> bio_free_map_data+0xc/0x1e
> >>
> >> This appears to be kfree(bmd->iovecs) in bio_free_map_data().  It looks
> >> like the memcpy size in bio_set_map_data() overrides the kmalloc size; in
> >> other words, for a redzone error, bio->bi_vcnt > nr_pages in
> >> bio_copy_user_iov().
> >
> > Can you try this?
> >
> > diff --git a/fs/bio.c b/fs/bio.c
> > index 7bbc98f..6a09356 100644
> > --- a/fs/bio.c
> > +++ b/fs/bio.c
> > @@ -817,6 +817,9 @@ struct bio *bio_copy_user_iov(struct request_queue *q,
> > 		len += iov[i].iov_len;
> > 	}
> >
> > +	if (offset)
> > +		nr_pages += 1;
> > +
> > 	bmd = bio_alloc_map_data(nr_pages, iov_count, gfp_mask);
> > 	if (!bmd)
> > 		return ERR_PTR(-ENOMEM);
> >
> 
> There are no more errors in the dmesg after applying this patch to 
> 2.6.29.2.
> 
> Without this patch I can reproduce this kind of errors on 
> 2.6.29.1, 2.6.29.2.
> 
> I've not tested this patch with 2.6.29.1 and 2.6.30rc3-git3.
> I will try to reproduce the error on 2.6.30rc3-git3 as soon as I compile 
> it.

Thanks for testing! And very sorry about the bug.

I'm sure that you hit the same bug with 2.6.30-rc3-git.

Jens, can you please apply this against 2.6.30-rc (and we need this
for 2.6.29.x too)?

I know that bio_copy_user_iov() is hacky. I'll try to clean up the
mapping API later.

=
From: FUJITA Tomonori <fujita.tomonori-Zyj7fXuS5i5L9jVzuh4AOg@public.gmane.org>
Subject: [PATCH] bio: fix memcpy corruption in bio_copy_user_iov()

st driver uses blk_rq_map_user() in order to just build a request out
of page frames. In this case, map_data->offset is a non zero value and
iov[0].iov_base is NULL. We need to increase nr_pages for that.

Cc: stable-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org
Signed-off-by: FUJITA Tomonori <fujita.tomonori-Zyj7fXuS5i5L9jVzuh4AOg@public.gmane.org>
---
 fs/bio.c |    3 +++
 1 files changed, 3 insertions(+), 0 deletions(-)

diff --git a/fs/bio.c b/fs/bio.c
index 7bbc98f..9871164 100644
--- a/fs/bio.c
+++ b/fs/bio.c
@@ -817,6 +817,9 @@ struct bio *bio_copy_user_iov(struct request_queue *q,
 		len += iov[i].iov_len;
 	}
 
+	if (offset)
+		nr_pages++;
+
 	bmd = bio_alloc_map_data(nr_pages, iov_count, gfp_mask);
 	if (!bmd)
 		return ERR_PTR(-ENOMEM);
-- 
1.6.0.6

Re: [Bug #13112] Oops in drain_array

[Jens Axboe]

On Tue, Apr 28 2009, FUJITA Tomonori wrote:
> On Tue, 28 Apr 2009 14:43:37 +0200 (CEST)
> Bart <mmx@riz.pl> wrote:
> 
> > > On Mon, 27 Apr 2009 13:36:46 -0700 (PDT)
> > > David Rientjes <rientjes@google.com> wrote:
> > >
> > >> On Mon, 27 Apr 2009, Bart wrote:
> > >>
> > >>> After turning the suggested debuging options I've got tons of these when
> > >>> trying to stress the tape device like before:
> > >>>
> > >>> Apr 27 16:57:30 fs kernel: [   96.446708] slab error in verify_redzone_free():
> > >>> cache `size-128': memory outside object was overwritten
> > >>> Apr 27 16:57:30 fs kernel: [   96.446713] Pid: 0, comm: swapper Not tainted
> > >>> 2.6.29.1-64 #2
> > >>> Apr 27 16:57:30 fs kernel: [   96.446715] Call Trace:
> > >>> Apr 27 16:57:30 fs kernel: [   96.446717]  <IRQ>  [<ffffffff8029adc5>]
> > >>> __slab_error+0x1f/0x25
> > >>> Apr 27 16:57:30 fs kernel: [   96.446728]  [<ffffffff8029b24b>]
> > >>> cache_free_debugcheck+0x108/0x1d6
> > >>> Apr 27 16:57:30 fs kernel: [   96.446731]  [<ffffffff8029b473>]
> > >>> kfree+0x81/0xc2
> > >>> Apr 27 16:57:30 fs kernel: [   96.446735]  [<ffffffff802bd311>]
> > >>> bio_free_map_data+0xc/0x1e
> > >>
> > >> This appears to be kfree(bmd->iovecs) in bio_free_map_data().  It looks
> > >> like the memcpy size in bio_set_map_data() overrides the kmalloc size; in
> > >> other words, for a redzone error, bio->bi_vcnt > nr_pages in
> > >> bio_copy_user_iov().
> > >
> > > Can you try this?
> > >
> > > diff --git a/fs/bio.c b/fs/bio.c
> > > index 7bbc98f..6a09356 100644
> > > --- a/fs/bio.c
> > > +++ b/fs/bio.c
> > > @@ -817,6 +817,9 @@ struct bio *bio_copy_user_iov(struct request_queue *q,
> > > 		len += iov[i].iov_len;
> > > 	}
> > >
> > > +	if (offset)
> > > +		nr_pages += 1;
> > > +
> > > 	bmd = bio_alloc_map_data(nr_pages, iov_count, gfp_mask);
> > > 	if (!bmd)
> > > 		return ERR_PTR(-ENOMEM);
> > >
> > 
> > There are no more errors in the dmesg after applying this patch to 
> > 2.6.29.2.
> > 
> > Without this patch I can reproduce this kind of errors on 
> > 2.6.29.1, 2.6.29.2.
> > 
> > I've not tested this patch with 2.6.29.1 and 2.6.30rc3-git3.
> > I will try to reproduce the error on 2.6.30rc3-git3 as soon as I compile 
> > it.
> 
> Thanks for testing! And very sorry about the bug.
> 
> I'm sure that you hit the same bug with 2.6.30-rc3-git.
> 
> Jens, can you please apply this against 2.6.30-rc (and we need this
> for 2.6.29.x too)?
> 
> I know that bio_copy_user_iov() is hacky. I'll try to clean up the
> mapping API later.

I'll apply it for 2.6.30-rc and CC stable. bio_copy_user_iov() is indeed
not pretty, both the API and the implementation needs looking at...

-- 
Jens Axboe

Re: [Bug #13112] Oops in drain_array

[Jens Axboe]

On Tue, Apr 28 2009, FUJITA Tomonori wrote:
> On Tue, 28 Apr 2009 14:43:37 +0200 (CEST)
> Bart <mmx-G/jkD+u3s4s@public.gmane.org> wrote:
> 
> > > On Mon, 27 Apr 2009 13:36:46 -0700 (PDT)
> > > David Rientjes <rientjes-hpIqsD4AKlfQT0dZR+AlfA@public.gmane.org> wrote:
> > >
> > >> On Mon, 27 Apr 2009, Bart wrote:
> > >>
> > >>> After turning the suggested debuging options I've got tons of these when
> > >>> trying to stress the tape device like before:
> > >>>
> > >>> Apr 27 16:57:30 fs kernel: [   96.446708] slab error in verify_redzone_free():
> > >>> cache `size-128': memory outside object was overwritten
> > >>> Apr 27 16:57:30 fs kernel: [   96.446713] Pid: 0, comm: swapper Not tainted
> > >>> 2.6.29.1-64 #2
> > >>> Apr 27 16:57:30 fs kernel: [   96.446715] Call Trace:
> > >>> Apr 27 16:57:30 fs kernel: [   96.446717]  <IRQ>  [<ffffffff8029adc5>]
> > >>> __slab_error+0x1f/0x25
> > >>> Apr 27 16:57:30 fs kernel: [   96.446728]  [<ffffffff8029b24b>]
> > >>> cache_free_debugcheck+0x108/0x1d6
> > >>> Apr 27 16:57:30 fs kernel: [   96.446731]  [<ffffffff8029b473>]
> > >>> kfree+0x81/0xc2
> > >>> Apr 27 16:57:30 fs kernel: [   96.446735]  [<ffffffff802bd311>]
> > >>> bio_free_map_data+0xc/0x1e
> > >>
> > >> This appears to be kfree(bmd->iovecs) in bio_free_map_data().  It looks
> > >> like the memcpy size in bio_set_map_data() overrides the kmalloc size; in
> > >> other words, for a redzone error, bio->bi_vcnt > nr_pages in
> > >> bio_copy_user_iov().
> > >
> > > Can you try this?
> > >
> > > diff --git a/fs/bio.c b/fs/bio.c
> > > index 7bbc98f..6a09356 100644
> > > --- a/fs/bio.c
> > > +++ b/fs/bio.c
> > > @@ -817,6 +817,9 @@ struct bio *bio_copy_user_iov(struct request_queue *q,
> > > 		len += iov[i].iov_len;
> > > 	}
> > >
> > > +	if (offset)
> > > +		nr_pages += 1;
> > > +
> > > 	bmd = bio_alloc_map_data(nr_pages, iov_count, gfp_mask);
> > > 	if (!bmd)
> > > 		return ERR_PTR(-ENOMEM);
> > >
> > 
> > There are no more errors in the dmesg after applying this patch to 
> > 2.6.29.2.
> > 
> > Without this patch I can reproduce this kind of errors on 
> > 2.6.29.1, 2.6.29.2.
> > 
> > I've not tested this patch with 2.6.29.1 and 2.6.30rc3-git3.
> > I will try to reproduce the error on 2.6.30rc3-git3 as soon as I compile 
> > it.
> 
> Thanks for testing! And very sorry about the bug.
> 
> I'm sure that you hit the same bug with 2.6.30-rc3-git.
> 
> Jens, can you please apply this against 2.6.30-rc (and we need this
> for 2.6.29.x too)?
> 
> I know that bio_copy_user_iov() is hacky. I'll try to clean up the
> mapping API later.

I'll apply it for 2.6.30-rc and CC stable. bio_copy_user_iov() is indeed
not pretty, both the API and the implementation needs looking at...

-- 
Jens Axboe

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

[Rafael J. Wysocki]

On Monday 27 April 2009, Jos van der Ende wrote:
> On Sun, 26 Apr 2009 19:43:44 +0200
> "Rafael J. Wysocki" <rjw@sisk.pl> wrote:
> 
> > On Sunday 26 April 2009, Angel wrote:
> > > On Sun, 26 Apr 2009 11:46:26 +0200 (CEST)
> > > 
> > > I've tested with kernel 2.6.29.1. The problem still persists. While everything works fine with 2.6.28 or lower, starting X (both 1.3 and 1.5) with DRI enabled on a 2.6.29 kernel results in a garbled screen and unresponsive keyboard.
> > 
> > Thanks for the update.
> > 
> > Can you also test 2.6.30-rc3, please?
> 
> Sure. Still broken in exactly the same way. (Garbled screen, non-working keyboard. System can still be ssh-ed into.)

Thanks!

Best,
Rafael

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

[Rafael J. Wysocki]

On Monday 27 April 2009, Jos van der Ende wrote:
> On Sun, 26 Apr 2009 19:43:44 +0200
> "Rafael J. Wysocki" <rjw-KKrjLPT3xs0@public.gmane.org> wrote:
> 
> > On Sunday 26 April 2009, Angel wrote:
> > > On Sun, 26 Apr 2009 11:46:26 +0200 (CEST)
> > > 
> > > I've tested with kernel 2.6.29.1. The problem still persists. While everything works fine with 2.6.28 or lower, starting X (both 1.3 and 1.5) with DRI enabled on a 2.6.29 kernel results in a garbled screen and unresponsive keyboard.
> > 
> > Thanks for the update.
> > 
> > Can you also test 2.6.30-rc3, please?
> 
> Sure. Still broken in exactly the same way. (Garbled screen, non-working keyboard. System can still be ssh-ed into.)

Thanks!

Best,
Rafael

Re: [Bug #13003] [2.6.29 regression] ivtv driver causes strange oops'es, disrupts software suspend

[Rafael J. Wysocki]

On Monday 27 April 2009, Hans Verkuil wrote:
> On Sunday 26 April 2009 11:46:28 Rafael J. Wysocki wrote:
> > This message has been generated automatically as a part of a report
> > of regressions introduced between 2.6.28 and 2.6.29.
> >
> > The following bug entry is on the current list of known regressions
> > introduced between 2.6.28 and 2.6.29.  Please verify if it still should
> > be listed and let me know (either way).
> >
> >
> > Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13003
> > Subject		: [2.6.29 regression] ivtv driver causes strange oops'es,
> > disrupts software suspend Submitter	: Artem S. Tashkinov
> > <t.artem@mailcity.com>
> > Date		: 2009-04-03 14:57 (24 days old)
> > Handled-By	: Hans Verkuil <hverkuil@xs4all.nl>
> 
> This isn't a 2.6.29 regression. It is a bug - somewhere - but it's also been 
> reproduced under 2.6.28 so it doesn't qualify as a regression.

Thanks, dropped from the list.

Best,
Rafael

Re: [Bug #13003] [2.6.29 regression] ivtv driver causes strange oops'es, disrupts software suspend

[Rafael J. Wysocki]

On Monday 27 April 2009, Hans Verkuil wrote:
> On Sunday 26 April 2009 11:46:28 Rafael J. Wysocki wrote:
> > This message has been generated automatically as a part of a report
> > of regressions introduced between 2.6.28 and 2.6.29.
> >
> > The following bug entry is on the current list of known regressions
> > introduced between 2.6.28 and 2.6.29.  Please verify if it still should
> > be listed and let me know (either way).
> >
> >
> > Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13003
> > Subject		: [2.6.29 regression] ivtv driver causes strange oops'es,
> > disrupts software suspend Submitter	: Artem S. Tashkinov
> > <t.artem-VInPYn6yXxRWk0Htik3J/w@public.gmane.org>
> > Date		: 2009-04-03 14:57 (24 days old)
> > Handled-By	: Hans Verkuil <hverkuil-qWit8jRvyhVmR6Xm/wNWPw@public.gmane.org>
> 
> This isn't a 2.6.29 regression. It is a bug - somewhere - but it's also been 
> reproduced under 2.6.28 so it doesn't qualify as a regression.

Thanks, dropped from the list.

Best,
Rafael

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

[Nico Schottelius]

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

Update:

  Brightness works on 2.6.30-rc3-next-20090428-04067-g72f1b63 (linux-next)

-- 
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: 268 bytes --]

Update:

  Brightness works on 2.6.30-rc3-next-20090428-04067-g72f1b63 (linux-next)

-- 
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 #13001] PCI-DMA: Out of IOMMU space

[Данила Жукоцкий]

2009/4/28 FUJITA Tomonori <fujita.tomonori@lab.ntt.co.jp>:
> On Tue, 28 Apr 2009 14:18:57 +0500
> **UNKNOWN CHARSET** <optimusgd@gmail.com> wrote:
>
>> No, it is regression. I can reproduce that without allowdac and any
>> other unnecessary boot options.
>
> Hmm, in the bug repport, you said that you can't reproduce the problem:
>
> http://bugzilla.kernel.org/show_bug.cgi?id=13001#c15
>
> I can't find your comment like, "I can reproduce that without
> allowdac".

I was under a misapprehension. Later discussion was been in linux-pci
mailing list
http://markmail.org/message/pbng73ojpllln5fl

>
>> In later discussion Grant Grundler ask
>> me apply patch that show 32 bit dma devices in my system. Results I
>> attached to bugreport. Looks like only one 32 bit dma device in my
>> system is ata controller, sata-nv.
>
> Hmm, looks like http://bugzilla.kernel.org/attachment.cgi?id=20895
> said that pata_amd and sata_nv use 32bit dma mask.
>
>
>> I can stable reproduce IOMMU out of space when I write data to sata
>> drive.
>
> Ok, let's figure out what's wrong.
>
> First, can you test v2.6.30-rc3 with the following patch?
>
> http://www.kernel.org/pub/linux/kernel/people/tomo/misc/gart-debug.diff
>
>
> Note that please enable CONFIG_DMA_API_DEBUG, CONFIG_IOMMU_DEBUG, and
> CONFIG_IOMMU_LEAK and see if you can reproduce the problem (of course,
> don't use any kernel option).
>
> When the kernel is out of IOMMU space, it prints some useful
> information.
>

I can't reproduce bug in 2.6.30-rc3. I read and wrote ~ 100gb data
from and to sata drive. Dmesg has two warnings during boot,

------------[ cut here ]------------
WARNING: at lib/dma-debug.c:607 check_unmap+0x542/0x610()
Hardware name: HP xw9400 Workstation
3w-9xxx 0001:45:00.0: DMA-API: device driver tries to free DMA memory
it has not allocated [device address=0x0000000000000000] [size=36
bytes]
Modules linked in:
Pid: 0, comm: swapper Not tainted 2.6.30-rc3-git7 #1
Call Trace:
 <IRQ>  [<ffffffff8023ce2a>] ? warn_slowpath+0xea/0x160
 [<ffffffff802589ae>] ? sched_clock_cpu+0x6e/0x240
 [<ffffffff802370a2>] ? scheduler_tick+0xc2/0x220
 [<ffffffff80259f4b>] ? getnstimeofday+0x5b/0xe0
 [<ffffffff80256b30>] ? ktime_get_ts+0x30/0x60
 [<ffffffff80256b6c>] ? ktime_get+0xc/0x50
 [<ffffffff8021d828>] ? lapic_next_event+0x18/0x20
 [<ffffffff8025e1d6>] ? tick_dev_program_event+0x36/0xb0
 [<ffffffff8021e29c>] ? smp_apic_timer_interrupt+0x6c/0xa0
 [<ffffffff8020bf83>] ? apic_timer_interrupt+0x13/0x20
 [<ffffffff8023db13>] ? vprintk+0x2d3/0x420
 [<ffffffff803f0b12>] ? check_unmap+0x542/0x610
 [<ffffffff803f0d0e>] ? debug_dma_unmap_sg+0xde/0x180
 [<ffffffff8046c0fb>] ? scsi_dma_unmap+0x6b/0xa0
 [<ffffffff80472559>] ? twa_interrupt+0x3e9/0x6a0
 [<ffffffff80256f2d>] ? __hrtimer_start_range_ns+0x12d/0x2b0
 [<ffffffff8026b3b9>] ? handle_IRQ_event+0x59/0x130
 [<ffffffff8026d4e1>] ? handle_edge_irq+0xc1/0x160
 [<ffffffff8020e377>] ? handle_irq+0x17/0x20
 [<ffffffff8020dae5>] ? do_IRQ+0x65/0xf0
 [<ffffffff8020be13>] ? ret_from_intr+0x0/0xa
 <EOI>  [<ffffffff80213182>] ? default_idle+0x42/0x50
 [<ffffffff802131c4>] ? c1e_idle+0x34/0x100
 [<ffffffff802581d9>] ? __atomic_notifier_call_chain+0x19/0x50
 [<ffffffff8020a09a>] ? cpu_idle+0x5a/0xc0
---[ end trace eedd91b655a6fdac ]---

and

------------[ cut here ]------------
WARNING: at fs/namei.c:1251 lookup_one_len+0xe9/0x100()
Hardware name: HP xw9400 Workstation
Modules linked in: fuse nfs auth_rpcgss lockd sunrpc scsi_wait_scan
usbhid ohci_hcd usb_storage usb_libusual ehci_hcd usbcore
Pid: 2807, comm: mount Tainted: G        W  2.6.30-rc3-git7 #1
Call Trace:
 [<ffffffff8023ce2a>] ? warn_slowpath+0xea/0x160
 [<ffffffff80564ac6>] ? printk+0x4e/0x58
 [<ffffffff8032d8ba>] ? prepare_error_buf+0x51a/0x610
 [<ffffffff802a0afe>] ? new_slab+0x1ee/0x330
 [<ffffffff8032da91>] ? reiserfs_info+0x71/0xa0
 [<ffffffff802b3bb9>] ? lookup_one_len+0xe9/0x100
 [<ffffffff8033e8bd>] ? reiserfs_xattr_init+0x3d/0xb0
 [<ffffffff8032c2b3>] ? reiserfs_fill_super+0x663/0xb50
 [<ffffffff803dfad2>] ? kobject_get+0x12/0x20
 [<ffffffff80457864>] ? get_device+0x14/0x20
 [<ffffffff805676b2>] ? __down_write_nested+0xb2/0xc0
 [<ffffffff802a37e5>] ? kmem_cache_alloc+0x65/0xa0
 [<ffffffff802ac922>] ? sget+0x3c2/0x410
 [<ffffffff802acc94>] ? get_sb_bdev+0x174/0x1a0
 [<ffffffff8032bc50>] ? reiserfs_fill_super+0x0/0xb50
 [<ffffffff802ab726>] ? vfs_kern_mount+0x56/0xd0
 [<ffffffff802ab803>] ? do_kern_mount+0x53/0x120
 [<ffffffff802c450a>] ? do_mount+0x2ba/0x8c0
 [<ffffffff80568f88>] ? bad_gs+0xc34/0x1e0c
 [<ffffffff802c4bdd>] ? sys_mount+0xcd/0x100
 [<ffffffff8020b4eb>] ? system_call_fastpath+0x16/0x1b
---[ end trace eedd91b655a6fdae ]---

So I hope that bug is gone.

-- 
С уважением Данила Жукоцкий, системный администратор ЗАО "Роснефтегазмаш"

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

[Данила Жукоцкий]

2009/4/28 FUJITA Tomonori <fujita.tomonori-Zyj7fXuS5i5L9jVzuh4AOg@public.gmane.org>:
> On Tue, 28 Apr 2009 14:18:57 +0500
> **UNKNOWN CHARSET** <optimusgd-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:
>
>> No, it is regression. I can reproduce that without allowdac and any
>> other unnecessary boot options.
>
> Hmm, in the bug repport, you said that you can't reproduce the problem:
>
> http://bugzilla.kernel.org/show_bug.cgi?id=13001#c15
>
> I can't find your comment like, "I can reproduce that without
> allowdac".

I was under a misapprehension. Later discussion was been in linux-pci
mailing list
http://markmail.org/message/pbng73ojpllln5fl

>
>> In later discussion Grant Grundler ask
>> me apply patch that show 32 bit dma devices in my system. Results I
>> attached to bugreport. Looks like only one 32 bit dma device in my
>> system is ata controller, sata-nv.
>
> Hmm, looks like http://bugzilla.kernel.org/attachment.cgi?id=20895
> said that pata_amd and sata_nv use 32bit dma mask.
>
>
>> I can stable reproduce IOMMU out of space when I write data to sata
>> drive.
>
> Ok, let's figure out what's wrong.
>
> First, can you test v2.6.30-rc3 with the following patch?
>
> http://www.kernel.org/pub/linux/kernel/people/tomo/misc/gart-debug.diff
>
>
> Note that please enable CONFIG_DMA_API_DEBUG, CONFIG_IOMMU_DEBUG, and
> CONFIG_IOMMU_LEAK and see if you can reproduce the problem (of course,
> don't use any kernel option).
>
> When the kernel is out of IOMMU space, it prints some useful
> information.
>

I can't reproduce bug in 2.6.30-rc3. I read and wrote ~ 100gb data
from and to sata drive. Dmesg has two warnings during boot,

------------[ cut here ]------------
WARNING: at lib/dma-debug.c:607 check_unmap+0x542/0x610()
Hardware name: HP xw9400 Workstation
3w-9xxx 0001:45:00.0: DMA-API: device driver tries to free DMA memory
it has not allocated [device address=0x0000000000000000] [size=36
bytes]
Modules linked in:
Pid: 0, comm: swapper Not tainted 2.6.30-rc3-git7 #1
Call Trace:
 <IRQ>  [<ffffffff8023ce2a>] ? warn_slowpath+0xea/0x160
 [<ffffffff802589ae>] ? sched_clock_cpu+0x6e/0x240
 [<ffffffff802370a2>] ? scheduler_tick+0xc2/0x220
 [<ffffffff80259f4b>] ? getnstimeofday+0x5b/0xe0
 [<ffffffff80256b30>] ? ktime_get_ts+0x30/0x60
 [<ffffffff80256b6c>] ? ktime_get+0xc/0x50
 [<ffffffff8021d828>] ? lapic_next_event+0x18/0x20
 [<ffffffff8025e1d6>] ? tick_dev_program_event+0x36/0xb0
 [<ffffffff8021e29c>] ? smp_apic_timer_interrupt+0x6c/0xa0
 [<ffffffff8020bf83>] ? apic_timer_interrupt+0x13/0x20
 [<ffffffff8023db13>] ? vprintk+0x2d3/0x420
 [<ffffffff803f0b12>] ? check_unmap+0x542/0x610
 [<ffffffff803f0d0e>] ? debug_dma_unmap_sg+0xde/0x180
 [<ffffffff8046c0fb>] ? scsi_dma_unmap+0x6b/0xa0
 [<ffffffff80472559>] ? twa_interrupt+0x3e9/0x6a0
 [<ffffffff80256f2d>] ? __hrtimer_start_range_ns+0x12d/0x2b0
 [<ffffffff8026b3b9>] ? handle_IRQ_event+0x59/0x130
 [<ffffffff8026d4e1>] ? handle_edge_irq+0xc1/0x160
 [<ffffffff8020e377>] ? handle_irq+0x17/0x20
 [<ffffffff8020dae5>] ? do_IRQ+0x65/0xf0
 [<ffffffff8020be13>] ? ret_from_intr+0x0/0xa
 <EOI>  [<ffffffff80213182>] ? default_idle+0x42/0x50
 [<ffffffff802131c4>] ? c1e_idle+0x34/0x100
 [<ffffffff802581d9>] ? __atomic_notifier_call_chain+0x19/0x50
 [<ffffffff8020a09a>] ? cpu_idle+0x5a/0xc0
---[ end trace eedd91b655a6fdac ]---

and

------------[ cut here ]------------
WARNING: at fs/namei.c:1251 lookup_one_len+0xe9/0x100()
Hardware name: HP xw9400 Workstation
Modules linked in: fuse nfs auth_rpcgss lockd sunrpc scsi_wait_scan
usbhid ohci_hcd usb_storage usb_libusual ehci_hcd usbcore
Pid: 2807, comm: mount Tainted: G        W  2.6.30-rc3-git7 #1
Call Trace:
 [<ffffffff8023ce2a>] ? warn_slowpath+0xea/0x160
 [<ffffffff80564ac6>] ? printk+0x4e/0x58
 [<ffffffff8032d8ba>] ? prepare_error_buf+0x51a/0x610
 [<ffffffff802a0afe>] ? new_slab+0x1ee/0x330
 [<ffffffff8032da91>] ? reiserfs_info+0x71/0xa0
 [<ffffffff802b3bb9>] ? lookup_one_len+0xe9/0x100
 [<ffffffff8033e8bd>] ? reiserfs_xattr_init+0x3d/0xb0
 [<ffffffff8032c2b3>] ? reiserfs_fill_super+0x663/0xb50
 [<ffffffff803dfad2>] ? kobject_get+0x12/0x20
 [<ffffffff80457864>] ? get_device+0x14/0x20
 [<ffffffff805676b2>] ? __down_write_nested+0xb2/0xc0
 [<ffffffff802a37e5>] ? kmem_cache_alloc+0x65/0xa0
 [<ffffffff802ac922>] ? sget+0x3c2/0x410
 [<ffffffff802acc94>] ? get_sb_bdev+0x174/0x1a0
 [<ffffffff8032bc50>] ? reiserfs_fill_super+0x0/0xb50
 [<ffffffff802ab726>] ? vfs_kern_mount+0x56/0xd0
 [<ffffffff802ab803>] ? do_kern_mount+0x53/0x120
 [<ffffffff802c450a>] ? do_mount+0x2ba/0x8c0
 [<ffffffff80568f88>] ? bad_gs+0xc34/0x1e0c
 [<ffffffff802c4bdd>] ? sys_mount+0xcd/0x100
 [<ffffffff8020b4eb>] ? system_call_fastpath+0x16/0x1b
---[ end trace eedd91b655a6fdae ]---

So I hope that bug is gone.

-- 
С уважением Данила Жукоцкий, системный администратор ЗАО "Роснефтегазмаш"

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

[Grant Grundler]

2009/5/3 Данила Жукоцкий <optimusgd@gmail.com>:
...
> WARNING: at lib/dma-debug.c:607 check_unmap+0x542/0x610()
> Hardware name: HP xw9400 Workstation
> 3w-9xxx 0001:45:00.0: DMA-API: device driver tries to free DMA memory
> it has not allocated [device address=0x0000000000000000] [size=36
> bytes]

This is definitely a driver bug. Just follow the stack trace back to
the device driver.

thanks!
grant

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

[Grant Grundler]

2009/5/3 Данила Жукоцкий <optimusgd-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>:
...
> WARNING: at lib/dma-debug.c:607 check_unmap+0x542/0x610()
> Hardware name: HP xw9400 Workstation
> 3w-9xxx 0001:45:00.0: DMA-API: device driver tries to free DMA memory
> it has not allocated [device address=0x0000000000000000] [size=36
> bytes]

This is definitely a driver bug. Just follow the stack trace back to
the device driver.

thanks!
grant

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

[adam radford]

2009/5/4 Grant Grundler <grundler@google.com>:
> 2009/5/3 Данила Жукоцкий <optimusgd@gmail.com>:
> ...
>> WARNING: at lib/dma-debug.c:607 check_unmap+0x542/0x610()
>> Hardware name: HP xw9400 Workstation
>> 3w-9xxx 0001:45:00.0: DMA-API: device driver tries to free DMA memory
>> it has not allocated [device address=0x0000000000000000] [size=36
>> bytes]
>
> This is definitely a driver bug. Just follow the stack trace back to
> the device driver.
>

I think this is a regression from the scsi_dma_map()/unmap() changes a while
back.

Can you try this patch?

Thanks,

-Adam

diff -Naur linux-2.6.30-rc4/drivers/scsi/3w-9xxx.c
linux-2.6.30-rc4.new/drivers/scsi/3w-9xxx.c
--- linux-2.6.30-rc4/drivers/scsi/3w-9xxx.c	2009-05-04 21:19:49.000000000 -0700
+++ linux-2.6.30-rc4.new/drivers/scsi/3w-9xxx.c	2009-05-04
21:23:59.000000000 -0700
@@ -1978,7 +1978,8 @@
 {
 	struct scsi_cmnd *cmd = tw_dev->srb[request_id];

-	scsi_dma_unmap(cmd);
+	if (cmd->SCp.phase == TW_PHASE_SGLIST)
+		scsi_dma_unmap(cmd);
 } /* End twa_unmap_scsi_data() */

 /* scsi_host_template initializer */

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

[Данила Жукоцкий]

Full dmesg there: http://bugzilla.kernel.org/attachment.cgi?id=21222
Got this:
------------[ cut here ]------------
WARNING: at fs/namei.c:1251 lookup_one_len+0xe9/0x100()
Hardware name: HP xw9400 Workstation
Modules linked in: fuse nfs auth_rpcgss lockd sunrpc scsi_wait_scan
usbhid ohci_hcd usb_storage usb_libusual ehci_hcd usbcore
Pid: 2717, comm: mount Not tainted 2.6.30-rc4-git1 #1
Call Trace:
 [<ffffffff8023ceca>] ? warn_slowpath+0xea/0x160
 [<ffffffff80564d06>] ? printk+0x4e/0x58
 [<ffffffff8032daea>] ? prepare_error_buf+0x51a/0x610
 [<ffffffff802a0cfe>] ? new_slab+0x1ee/0x330
 [<ffffffff8032dcc1>] ? reiserfs_info+0x71/0xa0
 [<ffffffff802b3df9>] ? lookup_one_len+0xe9/0x100
 [<ffffffff8033eaed>] ? reiserfs_xattr_init+0x3d/0xb0
 [<ffffffff8032c4e3>] ? reiserfs_fill_super+0x663/0xb50
 [<ffffffff805678f2>] ? __down_write_nested+0xb2/0xc0
 [<ffffffff802a39e5>] ? kmem_cache_alloc+0x65/0xa0
 [<ffffffff802acb22>] ? sget+0x3c2/0x410
 [<ffffffff802ace94>] ? get_sb_bdev+0x174/0x1a0
 [<ffffffff8032be80>] ? reiserfs_fill_super+0x0/0xb50
 [<ffffffff802ab926>] ? vfs_kern_mount+0x56/0xd0
 [<ffffffff802aba03>] ? do_kern_mount+0x53/0x120
 [<ffffffff802c474a>] ? do_mount+0x2ba/0x8c0
 [<ffffffff805691c8>] ? bad_gs+0xc34/0x1e0c
 [<ffffffff802c4e1d>] ? sys_mount+0xcd/0x100
 [<ffffffff8020b4eb>] ? system_call_fastpath+0x16/0x1b
---[ end trace 93edef2de057a0ed ]---

and

------------[ cut here ]------------
WARNING: at lib/dma-debug.c:625 check_unmap+0x3b3/0x610()
Hardware name: HP xw9400 Workstation
forcedeth 0000:00:09.0: DMA-API: device driver frees DMA memory with
wrong function [device address=0x0000000023780c02] [size=42 bytes]
[mapped as single] [unmapped as page]
Modules linked in: nfsd exportfs iptable_filter iptable_mangle
ip_tables x_tables snd_seq snd_seq_device vboxnetflt vboxdrv
snd_hda_codec_realtek snd_hda_intel snd_hda_codec nvidia(P) snd_pcm
snd_timer snd firewire_ohci firewire_core soundcore snd_page_alloc
tpm_infineon tpm forcedeth floppy tpm_bios fuse nfs auth_rpcgss lockd
sunrpc scsi_wait_scan usbhid ohci_hcd usb_storage usb_libusual
ehci_hcd usbcore
Pid: 0, comm: swapper Tainted: P        W  2.6.30-rc4-git1 #1
Call Trace:
 <IRQ>  [<ffffffff8023ceca>] ? warn_slowpath+0xea/0x160
 [<ffffffff80231ad7>] ? task_rq_lock+0x47/0x90
 [<ffffffff8029b287>] ? dma_pool_alloc+0x1b7/0x2d0
 [<ffffffffa0059692>] ? ohci_urb_enqueue+0x1a2/0x980 [ohci_hcd]
 [<ffffffff80231a63>] ? __wake_up+0x43/0x70
 [<ffffffff802343f4>] ? find_busiest_group+0x244/0x920
 [<ffffffffa00073b7>] ? usb_hcd_submit_urb+0x117/0xa40 [usbcore]
 [<ffffffff803f0bb3>] ? check_unmap+0x3b3/0x610
 [<ffffffff803f0e58>] ? debug_dma_unmap_page+0x48/0x50
 [<ffffffffa014e639>] ? nv_tx_done_optimized+0xd9/0x2c0 [forcedeth]
 [<ffffffffa0151346>] ? nv_napi_poll+0x76/0x630 [forcedeth]
 [<ffffffff80256a1b>] ? hrtimer_get_next_event+0xdb/0xf0
 [<ffffffff804dcc47>] ? net_rx_action+0x87/0x130
 [<ffffffff802421fb>] ? __do_softirq+0x7b/0x110
 [<ffffffff8020c56c>] ? call_softirq+0x1c/0x30
 [<ffffffff8020e315>] ? do_softirq+0x35/0x80
 [<ffffffff80242055>] ? irq_exit+0x95/0xa0
 [<ffffffff8020db05>] ? do_IRQ+0x85/0xf0
 [<ffffffff8020be13>] ? ret_from_intr+0x0/0xa
 <EOI>  [<ffffffff80213182>] ? default_idle+0x42/0x50
 [<ffffffff802131c4>] ? c1e_idle+0x34/0x100
 [<ffffffff80258279>] ? __atomic_notifier_call_chain+0x19/0x50
 [<ffffffff8020a09a>] ? cpu_idle+0x5a/0xc0
---[ end trace 93edef2de057a0ee ]---



2009/5/5 adam radford <aradford@gmail.com>:
> 2009/5/4 Grant Grundler <grundler@google.com>:
>> 2009/5/3 Данила Жукоцкий <optimusgd@gmail.com>:
>> ...
>>> WARNING: at lib/dma-debug.c:607 check_unmap+0x542/0x610()
>>> Hardware name: HP xw9400 Workstation
>>> 3w-9xxx 0001:45:00.0: DMA-API: device driver tries to free DMA memory
>>> it has not allocated [device address=0x0000000000000000] [size=36
>>> bytes]
>>
>> This is definitely a driver bug. Just follow the stack trace back to
>> the device driver.
>>
>
> I think this is a regression from the scsi_dma_map()/unmap() changes a while
> back.
>
> Can you try this patch?
>
> Thanks,
>
> -Adam
>
> diff -Naur linux-2.6.30-rc4/drivers/scsi/3w-9xxx.c
> linux-2.6.30-rc4.new/drivers/scsi/3w-9xxx.c
> --- linux-2.6.30-rc4/drivers/scsi/3w-9xxx.c     2009-05-04 21:19:49.000000000 -0700
> +++ linux-2.6.30-rc4.new/drivers/scsi/3w-9xxx.c 2009-05-04
> 21:23:59.000000000 -0700
> @@ -1978,7 +1978,8 @@
>  {
>        struct scsi_cmnd *cmd = tw_dev->srb[request_id];
>
> -       scsi_dma_unmap(cmd);
> +       if (cmd->SCp.phase == TW_PHASE_SGLIST)
> +               scsi_dma_unmap(cmd);
>  } /* End twa_unmap_scsi_data() */
>
>  /* scsi_host_template initializer */
>



-- 
С уважением Данила Жукоцкий, системный администратор ЗАО "Роснефтегазмаш"

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

[Данила Жукоцкий]

Full dmesg there: http://bugzilla.kernel.org/attachment.cgi?id=21222
Got this:
------------[ cut here ]------------
WARNING: at fs/namei.c:1251 lookup_one_len+0xe9/0x100()
Hardware name: HP xw9400 Workstation
Modules linked in: fuse nfs auth_rpcgss lockd sunrpc scsi_wait_scan
usbhid ohci_hcd usb_storage usb_libusual ehci_hcd usbcore
Pid: 2717, comm: mount Not tainted 2.6.30-rc4-git1 #1
Call Trace:
 [<ffffffff8023ceca>] ? warn_slowpath+0xea/0x160
 [<ffffffff80564d06>] ? printk+0x4e/0x58
 [<ffffffff8032daea>] ? prepare_error_buf+0x51a/0x610
 [<ffffffff802a0cfe>] ? new_slab+0x1ee/0x330
 [<ffffffff8032dcc1>] ? reiserfs_info+0x71/0xa0
 [<ffffffff802b3df9>] ? lookup_one_len+0xe9/0x100
 [<ffffffff8033eaed>] ? reiserfs_xattr_init+0x3d/0xb0
 [<ffffffff8032c4e3>] ? reiserfs_fill_super+0x663/0xb50
 [<ffffffff805678f2>] ? __down_write_nested+0xb2/0xc0
 [<ffffffff802a39e5>] ? kmem_cache_alloc+0x65/0xa0
 [<ffffffff802acb22>] ? sget+0x3c2/0x410
 [<ffffffff802ace94>] ? get_sb_bdev+0x174/0x1a0
 [<ffffffff8032be80>] ? reiserfs_fill_super+0x0/0xb50
 [<ffffffff802ab926>] ? vfs_kern_mount+0x56/0xd0
 [<ffffffff802aba03>] ? do_kern_mount+0x53/0x120
 [<ffffffff802c474a>] ? do_mount+0x2ba/0x8c0
 [<ffffffff805691c8>] ? bad_gs+0xc34/0x1e0c
 [<ffffffff802c4e1d>] ? sys_mount+0xcd/0x100
 [<ffffffff8020b4eb>] ? system_call_fastpath+0x16/0x1b
---[ end trace 93edef2de057a0ed ]---

and

------------[ cut here ]------------
WARNING: at lib/dma-debug.c:625 check_unmap+0x3b3/0x610()
Hardware name: HP xw9400 Workstation
forcedeth 0000:00:09.0: DMA-API: device driver frees DMA memory with
wrong function [device address=0x0000000023780c02] [size=42 bytes]
[mapped as single] [unmapped as page]
Modules linked in: nfsd exportfs iptable_filter iptable_mangle
ip_tables x_tables snd_seq snd_seq_device vboxnetflt vboxdrv
snd_hda_codec_realtek snd_hda_intel snd_hda_codec nvidia(P) snd_pcm
snd_timer snd firewire_ohci firewire_core soundcore snd_page_alloc
tpm_infineon tpm forcedeth floppy tpm_bios fuse nfs auth_rpcgss lockd
sunrpc scsi_wait_scan usbhid ohci_hcd usb_storage usb_libusual
ehci_hcd usbcore
Pid: 0, comm: swapper Tainted: P        W  2.6.30-rc4-git1 #1
Call Trace:
 <IRQ>  [<ffffffff8023ceca>] ? warn_slowpath+0xea/0x160
 [<ffffffff80231ad7>] ? task_rq_lock+0x47/0x90
 [<ffffffff8029b287>] ? dma_pool_alloc+0x1b7/0x2d0
 [<ffffffffa0059692>] ? ohci_urb_enqueue+0x1a2/0x980 [ohci_hcd]
 [<ffffffff80231a63>] ? __wake_up+0x43/0x70
 [<ffffffff802343f4>] ? find_busiest_group+0x244/0x920
 [<ffffffffa00073b7>] ? usb_hcd_submit_urb+0x117/0xa40 [usbcore]
 [<ffffffff803f0bb3>] ? check_unmap+0x3b3/0x610
 [<ffffffff803f0e58>] ? debug_dma_unmap_page+0x48/0x50
 [<ffffffffa014e639>] ? nv_tx_done_optimized+0xd9/0x2c0 [forcedeth]
 [<ffffffffa0151346>] ? nv_napi_poll+0x76/0x630 [forcedeth]
 [<ffffffff80256a1b>] ? hrtimer_get_next_event+0xdb/0xf0
 [<ffffffff804dcc47>] ? net_rx_action+0x87/0x130
 [<ffffffff802421fb>] ? __do_softirq+0x7b/0x110
 [<ffffffff8020c56c>] ? call_softirq+0x1c/0x30
 [<ffffffff8020e315>] ? do_softirq+0x35/0x80
 [<ffffffff80242055>] ? irq_exit+0x95/0xa0
 [<ffffffff8020db05>] ? do_IRQ+0x85/0xf0
 [<ffffffff8020be13>] ? ret_from_intr+0x0/0xa
 <EOI>  [<ffffffff80213182>] ? default_idle+0x42/0x50
 [<ffffffff802131c4>] ? c1e_idle+0x34/0x100
 [<ffffffff80258279>] ? __atomic_notifier_call_chain+0x19/0x50
 [<ffffffff8020a09a>] ? cpu_idle+0x5a/0xc0
---[ end trace 93edef2de057a0ee ]---



2009/5/5 adam radford <aradford-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>:
> 2009/5/4 Grant Grundler <grundler-hpIqsD4AKlfQT0dZR+AlfA@public.gmane.org>:
>> 2009/5/3 Данила Жукоцкий <optimusgd-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>:
>> ...
>>> WARNING: at lib/dma-debug.c:607 check_unmap+0x542/0x610()
>>> Hardware name: HP xw9400 Workstation
>>> 3w-9xxx 0001:45:00.0: DMA-API: device driver tries to free DMA memory
>>> it has not allocated [device address=0x0000000000000000] [size=36
>>> bytes]
>>
>> This is definitely a driver bug. Just follow the stack trace back to
>> the device driver.
>>
>
> I think this is a regression from the scsi_dma_map()/unmap() changes a while
> back.
>
> Can you try this patch?
>
> Thanks,
>
> -Adam
>
> diff -Naur linux-2.6.30-rc4/drivers/scsi/3w-9xxx.c
> linux-2.6.30-rc4.new/drivers/scsi/3w-9xxx.c
> --- linux-2.6.30-rc4/drivers/scsi/3w-9xxx.c     2009-05-04 21:19:49.000000000 -0700
> +++ linux-2.6.30-rc4.new/drivers/scsi/3w-9xxx.c 2009-05-04
> 21:23:59.000000000 -0700
> @@ -1978,7 +1978,8 @@
>  {
>        struct scsi_cmnd *cmd = tw_dev->srb[request_id];
>
> -       scsi_dma_unmap(cmd);
> +       if (cmd->SCp.phase == TW_PHASE_SGLIST)
> +               scsi_dma_unmap(cmd);
>  } /* End twa_unmap_scsi_data() */
>
>  /* scsi_host_template initializer */
>



-- 
С уважением Данила Жукоцкий, системный администратор ЗАО "Роснефтегазмаш"

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

[FUJITA Tomonori]

On Tue, 5 May 2009 10:46:16 +0500
**UNKNOWN CHARSET** <optimusgd@gmail.com> wrote:

> Full dmesg there: http://bugzilla.kernel.org/attachment.cgi?id=21222
> Got this:
> ------------[ cut here ]------------
> WARNING: at fs/namei.c:1251 lookup_one_len+0xe9/0x100()
> Hardware name: HP xw9400 Workstation
> Modules linked in: fuse nfs auth_rpcgss lockd sunrpc scsi_wait_scan
> usbhid ohci_hcd usb_storage usb_libusual ehci_hcd usbcore
> Pid: 2717, comm: mount Not tainted 2.6.30-rc4-git1 #1
> Call Trace:
>  [<ffffffff8023ceca>] ? warn_slowpath+0xea/0x160
>  [<ffffffff80564d06>] ? printk+0x4e/0x58
>  [<ffffffff8032daea>] ? prepare_error_buf+0x51a/0x610
>  [<ffffffff802a0cfe>] ? new_slab+0x1ee/0x330
>  [<ffffffff8032dcc1>] ? reiserfs_info+0x71/0xa0
>  [<ffffffff802b3df9>] ? lookup_one_len+0xe9/0x100
>  [<ffffffff8033eaed>] ? reiserfs_xattr_init+0x3d/0xb0
>  [<ffffffff8032c4e3>] ? reiserfs_fill_super+0x663/0xb50
>  [<ffffffff805678f2>] ? __down_write_nested+0xb2/0xc0
>  [<ffffffff802a39e5>] ? kmem_cache_alloc+0x65/0xa0
>  [<ffffffff802acb22>] ? sget+0x3c2/0x410
>  [<ffffffff802ace94>] ? get_sb_bdev+0x174/0x1a0
>  [<ffffffff8032be80>] ? reiserfs_fill_super+0x0/0xb50
>  [<ffffffff802ab926>] ? vfs_kern_mount+0x56/0xd0
>  [<ffffffff802aba03>] ? do_kern_mount+0x53/0x120
>  [<ffffffff802c474a>] ? do_mount+0x2ba/0x8c0
>  [<ffffffff805691c8>] ? bad_gs+0xc34/0x1e0c
>  [<ffffffff802c4e1d>] ? sys_mount+0xcd/0x100
>  [<ffffffff8020b4eb>] ? system_call_fastpath+0x16/0x1b
> ---[ end trace 93edef2de057a0ed ]---

I think that this is a known issue.


> ------------[ cut here ]------------
> WARNING: at lib/dma-debug.c:625 check_unmap+0x3b3/0x610()
> Hardware name: HP xw9400 Workstation
> forcedeth 0000:00:09.0: DMA-API: device driver frees DMA memory with
> wrong function [device address=0x0000000023780c02] [size=42 bytes]
> [mapped as single] [unmapped as page]
> Modules linked in: nfsd exportfs iptable_filter iptable_mangle
> ip_tables x_tables snd_seq snd_seq_device vboxnetflt vboxdrv
> snd_hda_codec_realtek snd_hda_intel snd_hda_codec nvidia(P) snd_pcm
> snd_timer snd firewire_ohci firewire_core soundcore snd_page_alloc
> tpm_infineon tpm forcedeth floppy tpm_bios fuse nfs auth_rpcgss lockd
> sunrpc scsi_wait_scan usbhid ohci_hcd usb_storage usb_libusual
> ehci_hcd usbcore
> Pid: 0, comm: swapper Tainted: P        W  2.6.30-rc4-git1 #1
> Call Trace:
>  <IRQ>  [<ffffffff8023ceca>] ? warn_slowpath+0xea/0x160
>  [<ffffffff80231ad7>] ? task_rq_lock+0x47/0x90
>  [<ffffffff8029b287>] ? dma_pool_alloc+0x1b7/0x2d0
>  [<ffffffffa0059692>] ? ohci_urb_enqueue+0x1a2/0x980 [ohci_hcd]
>  [<ffffffff80231a63>] ? __wake_up+0x43/0x70
>  [<ffffffff802343f4>] ? find_busiest_group+0x244/0x920
>  [<ffffffffa00073b7>] ? usb_hcd_submit_urb+0x117/0xa40 [usbcore]
>  [<ffffffff803f0bb3>] ? check_unmap+0x3b3/0x610
>  [<ffffffff803f0e58>] ? debug_dma_unmap_page+0x48/0x50
>  [<ffffffffa014e639>] ? nv_tx_done_optimized+0xd9/0x2c0 [forcedeth]
>  [<ffffffffa0151346>] ? nv_napi_poll+0x76/0x630 [forcedeth]
>  [<ffffffff80256a1b>] ? hrtimer_get_next_event+0xdb/0xf0
>  [<ffffffff804dcc47>] ? net_rx_action+0x87/0x130
>  [<ffffffff802421fb>] ? __do_softirq+0x7b/0x110
>  [<ffffffff8020c56c>] ? call_softirq+0x1c/0x30
>  [<ffffffff8020e315>] ? do_softirq+0x35/0x80
>  [<ffffffff80242055>] ? irq_exit+0x95/0xa0
>  [<ffffffff8020db05>] ? do_IRQ+0x85/0xf0
>  [<ffffffff8020be13>] ? ret_from_intr+0x0/0xa
>  <EOI>  [<ffffffff80213182>] ? default_idle+0x42/0x50
>  [<ffffffff802131c4>] ? c1e_idle+0x34/0x100
>  [<ffffffff80258279>] ? __atomic_notifier_call_chain+0x19/0x50
>  [<ffffffff8020a09a>] ? cpu_idle+0x5a/0xc0
> ---[ end trace 93edef2de057a0ee ]---

Can you submit a bug report to netdev@vger.kernel.org? Well, I think
that the driver just uses pci_unmap_page for the areas mapped via
pci_map_single. That's not nice but causes no harm.

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

[FUJITA Tomonori]

On Tue, 5 May 2009 10:46:16 +0500
**UNKNOWN CHARSET** <optimusgd-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:

> Full dmesg there: http://bugzilla.kernel.org/attachment.cgi?id=21222
> Got this:
> ------------[ cut here ]------------
> WARNING: at fs/namei.c:1251 lookup_one_len+0xe9/0x100()
> Hardware name: HP xw9400 Workstation
> Modules linked in: fuse nfs auth_rpcgss lockd sunrpc scsi_wait_scan
> usbhid ohci_hcd usb_storage usb_libusual ehci_hcd usbcore
> Pid: 2717, comm: mount Not tainted 2.6.30-rc4-git1 #1
> Call Trace:
>  [<ffffffff8023ceca>] ? warn_slowpath+0xea/0x160
>  [<ffffffff80564d06>] ? printk+0x4e/0x58
>  [<ffffffff8032daea>] ? prepare_error_buf+0x51a/0x610
>  [<ffffffff802a0cfe>] ? new_slab+0x1ee/0x330
>  [<ffffffff8032dcc1>] ? reiserfs_info+0x71/0xa0
>  [<ffffffff802b3df9>] ? lookup_one_len+0xe9/0x100
>  [<ffffffff8033eaed>] ? reiserfs_xattr_init+0x3d/0xb0
>  [<ffffffff8032c4e3>] ? reiserfs_fill_super+0x663/0xb50
>  [<ffffffff805678f2>] ? __down_write_nested+0xb2/0xc0
>  [<ffffffff802a39e5>] ? kmem_cache_alloc+0x65/0xa0
>  [<ffffffff802acb22>] ? sget+0x3c2/0x410
>  [<ffffffff802ace94>] ? get_sb_bdev+0x174/0x1a0
>  [<ffffffff8032be80>] ? reiserfs_fill_super+0x0/0xb50
>  [<ffffffff802ab926>] ? vfs_kern_mount+0x56/0xd0
>  [<ffffffff802aba03>] ? do_kern_mount+0x53/0x120
>  [<ffffffff802c474a>] ? do_mount+0x2ba/0x8c0
>  [<ffffffff805691c8>] ? bad_gs+0xc34/0x1e0c
>  [<ffffffff802c4e1d>] ? sys_mount+0xcd/0x100
>  [<ffffffff8020b4eb>] ? system_call_fastpath+0x16/0x1b
> ---[ end trace 93edef2de057a0ed ]---

I think that this is a known issue.


> ------------[ cut here ]------------
> WARNING: at lib/dma-debug.c:625 check_unmap+0x3b3/0x610()
> Hardware name: HP xw9400 Workstation
> forcedeth 0000:00:09.0: DMA-API: device driver frees DMA memory with
> wrong function [device address=0x0000000023780c02] [size=42 bytes]
> [mapped as single] [unmapped as page]
> Modules linked in: nfsd exportfs iptable_filter iptable_mangle
> ip_tables x_tables snd_seq snd_seq_device vboxnetflt vboxdrv
> snd_hda_codec_realtek snd_hda_intel snd_hda_codec nvidia(P) snd_pcm
> snd_timer snd firewire_ohci firewire_core soundcore snd_page_alloc
> tpm_infineon tpm forcedeth floppy tpm_bios fuse nfs auth_rpcgss lockd
> sunrpc scsi_wait_scan usbhid ohci_hcd usb_storage usb_libusual
> ehci_hcd usbcore
> Pid: 0, comm: swapper Tainted: P        W  2.6.30-rc4-git1 #1
> Call Trace:
>  <IRQ>  [<ffffffff8023ceca>] ? warn_slowpath+0xea/0x160
>  [<ffffffff80231ad7>] ? task_rq_lock+0x47/0x90
>  [<ffffffff8029b287>] ? dma_pool_alloc+0x1b7/0x2d0
>  [<ffffffffa0059692>] ? ohci_urb_enqueue+0x1a2/0x980 [ohci_hcd]
>  [<ffffffff80231a63>] ? __wake_up+0x43/0x70
>  [<ffffffff802343f4>] ? find_busiest_group+0x244/0x920
>  [<ffffffffa00073b7>] ? usb_hcd_submit_urb+0x117/0xa40 [usbcore]
>  [<ffffffff803f0bb3>] ? check_unmap+0x3b3/0x610
>  [<ffffffff803f0e58>] ? debug_dma_unmap_page+0x48/0x50
>  [<ffffffffa014e639>] ? nv_tx_done_optimized+0xd9/0x2c0 [forcedeth]
>  [<ffffffffa0151346>] ? nv_napi_poll+0x76/0x630 [forcedeth]
>  [<ffffffff80256a1b>] ? hrtimer_get_next_event+0xdb/0xf0
>  [<ffffffff804dcc47>] ? net_rx_action+0x87/0x130
>  [<ffffffff802421fb>] ? __do_softirq+0x7b/0x110
>  [<ffffffff8020c56c>] ? call_softirq+0x1c/0x30
>  [<ffffffff8020e315>] ? do_softirq+0x35/0x80
>  [<ffffffff80242055>] ? irq_exit+0x95/0xa0
>  [<ffffffff8020db05>] ? do_IRQ+0x85/0xf0
>  [<ffffffff8020be13>] ? ret_from_intr+0x0/0xa
>  <EOI>  [<ffffffff80213182>] ? default_idle+0x42/0x50
>  [<ffffffff802131c4>] ? c1e_idle+0x34/0x100
>  [<ffffffff80258279>] ? __atomic_notifier_call_chain+0x19/0x50
>  [<ffffffff8020a09a>] ? cpu_idle+0x5a/0xc0
> ---[ end trace 93edef2de057a0ee ]---

Can you submit a bug report to netdev-u79uwXL29TY76Z2rM5mHXA@public.gmane.org? Well, I think
that the driver just uses pci_unmap_page for the areas mapped via
pci_map_single. That's not nice but causes no harm.

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

[FUJITA Tomonori]

On Mon, 4 May 2009 10:27:11 +0500
**UNKNOWN CHARSET** <optimusgd@gmail.com> wrote:

> 2009/4/28 FUJITA Tomonori <fujita.tomonori@lab.ntt.co.jp>:
> > On Tue, 28 Apr 2009 14:18:57 +0500
> > **UNKNOWN CHARSET** <optimusgd@gmail.com> wrote:
> >
> >> No, it is regression. I can reproduce that without allowdac and any
> >> other unnecessary boot options.
> >
> > Hmm, in the bug repport, you said that you can't reproduce the problem:
> >
> > http://bugzilla.kernel.org/show_bug.cgi?id=13001#c15
> >
> > I can't find your comment like, "I can reproduce that without
> > allowdac".
> 
> I was under a misapprehension. Later discussion was been in linux-pci
> mailing list
> http://markmail.org/message/pbng73ojpllln5fl

You didn't CC to me so it was impossible for me to track this bug.


> >> In later discussion Grant Grundler ask
> >> me apply patch that show 32 bit dma devices in my system. Results I
> >> attached to bugreport. Looks like only one 32 bit dma device in my
> >> system is ata controller, sata-nv.
> >
> > Hmm, looks like http://bugzilla.kernel.org/attachment.cgi?id=20895
> > said that pata_amd and sata_nv use 32bit dma mask.
> >
> >
> >> I can stable reproduce IOMMU out of space when I write data to sata
> >> drive.
> >
> > Ok, let's figure out what's wrong.
> >
> > First, can you test v2.6.30-rc3 with the following patch?
> >
> > http://www.kernel.org/pub/linux/kernel/people/tomo/misc/gart-debug.diff
> >
> >
> > Note that please enable CONFIG_DMA_API_DEBUG, CONFIG_IOMMU_DEBUG, and
> > CONFIG_IOMMU_LEAK and see if you can reproduce the problem (of course,
> > don't use any kernel option).
> >
> > When the kernel is out of IOMMU space, it prints some useful
> > information.
> >
> 
> I can't reproduce bug in 2.6.30-rc3. I read and wrote ~ 100gb data
> from and to sata drive. Dmesg has two warnings during boot,

Thanks, then let's debug 2.6.29.2.

http://www.kernel.org/pub/linux/kernel/people/tomo/misc/gart-debug-2.6.29.diff

As you did with 2.6.30-rc3, enable CONFIG_DMA_API_DEBUG,
CONFIG_IOMMU_DEBUG, and CONFIG_IOMMU_LEAK and don't use any kernel
boot option.

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

[FUJITA Tomonori]

On Mon, 4 May 2009 10:27:11 +0500
**UNKNOWN CHARSET** <optimusgd-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:

> 2009/4/28 FUJITA Tomonori <fujita.tomonori-Zyj7fXuS5i5L9jVzuh4AOg@public.gmane.org>:
> > On Tue, 28 Apr 2009 14:18:57 +0500
> > **UNKNOWN CHARSET** <optimusgd-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:
> >
> >> No, it is regression. I can reproduce that without allowdac and any
> >> other unnecessary boot options.
> >
> > Hmm, in the bug repport, you said that you can't reproduce the problem:
> >
> > http://bugzilla.kernel.org/show_bug.cgi?id=13001#c15
> >
> > I can't find your comment like, "I can reproduce that without
> > allowdac".
> 
> I was under a misapprehension. Later discussion was been in linux-pci
> mailing list
> http://markmail.org/message/pbng73ojpllln5fl

You didn't CC to me so it was impossible for me to track this bug.


> >> In later discussion Grant Grundler ask
> >> me apply patch that show 32 bit dma devices in my system. Results I
> >> attached to bugreport. Looks like only one 32 bit dma device in my
> >> system is ata controller, sata-nv.
> >
> > Hmm, looks like http://bugzilla.kernel.org/attachment.cgi?id=20895
> > said that pata_amd and sata_nv use 32bit dma mask.
> >
> >
> >> I can stable reproduce IOMMU out of space when I write data to sata
> >> drive.
> >
> > Ok, let's figure out what's wrong.
> >
> > First, can you test v2.6.30-rc3 with the following patch?
> >
> > http://www.kernel.org/pub/linux/kernel/people/tomo/misc/gart-debug.diff
> >
> >
> > Note that please enable CONFIG_DMA_API_DEBUG, CONFIG_IOMMU_DEBUG, and
> > CONFIG_IOMMU_LEAK and see if you can reproduce the problem (of course,
> > don't use any kernel option).
> >
> > When the kernel is out of IOMMU space, it prints some useful
> > information.
> >
> 
> I can't reproduce bug in 2.6.30-rc3. I read and wrote ~ 100gb data
> from and to sata drive. Dmesg has two warnings during boot,

Thanks, then let's debug 2.6.29.2.

http://www.kernel.org/pub/linux/kernel/people/tomo/misc/gart-debug-2.6.29.diff

As you did with 2.6.30-rc3, enable CONFIG_DMA_API_DEBUG,
CONFIG_IOMMU_DEBUG, and CONFIG_IOMMU_LEAK and don't use any kernel
boot option.

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

[Rafael J. Wysocki]

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

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


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

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

[Rafael J. Wysocki]

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

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


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

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

[Rafael J. Wysocki]

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

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


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

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

[Rafael J. Wysocki]

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

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


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

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

[Rafael J. Wysocki]

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

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


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

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

[Rafael J. Wysocki]

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

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


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

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

[Rafael J. Wysocki]

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

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


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

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

[Rafael J. Wysocki]

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

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


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

[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 #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)