2.6.31-rc5-git5: Reported regressions from 2.6.30

2.6.31-rc5-git5: Reported regressions from 2.6.30

[Rafael J. Wysocki]

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

If you know of any other unresolved regressions from 2.6.30, 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-08-10       89       27          24
  2009-08-02       76       36          28
  2009-07-27       70       51          43
  2009-07-07       35       25          21
  2009-06-29       22       22          15


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

Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13950
Subject		: Oops when USB Serial disconnected while in use
Submitter	: Bruno Prémont <bonbons@linux-vserver.org>
Date		: 2009-08-08 17:47 (2 days old)
References	: http://marc.info/?l=linux-kernel&m=124975432900466&w=4


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13947
Subject		: Libertas: Association request to the driver failed
Submitter	: Daniel Mack <daniel@caiaq.de>
Date		: 2009-08-07 19:11 (3 days old)
First-Bad-Commit: http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=57921c312e8cef72ba35a4cfe870b376da0b1b87
References	: http://marc.info/?l=linux-kernel&m=124967234311481&w=4
Handled-By	: Roel Kluin <roel.kluin@gmail.com>


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13943
Subject		: WARNING: at net/mac80211/mlme.c:2292 with ath5k
Submitter	: Fabio Comolli <fabio.comolli@gmail.com>
Date		: 2009-08-06 20:15 (4 days old)
References	: http://marc.info/?l=linux-kernel&m=124958978600600&w=4


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13942
Subject		: Troubles with AoE and uninitialized object
Submitter	: Bruno Prémont <bonbons@linux-vserver.org>
Date		: 2009-08-04 10:12 (6 days old)
References	: http://marc.info/?l=linux-kernel&m=124938117104811&w=4


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13941
Subject		: x86 Geode issue
Submitter	: Martin-Éric Racine <q-funk@iki.fi>
Date		: 2009-08-03 12:58 (7 days old)
References	: http://marc.info/?l=linux-kernel&m=124930434732481&w=4


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13940
Subject		: iwlagn and sky2 stopped working, ACPI-related
Submitter	: Ricardo Jorge da Fonseca Marques Ferreira <storm@sys49152.net>
Date		: 2009-08-07 22:33 (3 days old)
References	: http://marc.info/?l=linux-kernel&m=124968457731107&w=4


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13935
Subject		: 2.6.31-rcX breaks Apple MightyMouse (Bluetooth version)
Submitter	: Adrian Ulrich <kernel@blinkenlights.ch>
Date		: 2009-08-08 22:08 (2 days old)
First-Bad-Commit: http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=fa047e4f6fa63a6e9d0ae4d7749538830d14a343


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13914
Subject		: e1000e reports invalid NVM Checksum on 82566DM-2 (bisected)
Submitter	:  <jsbronder@gentoo.org>
Date		: 2009-08-04 18:06 (6 days old)


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13906
Subject		: Huawei E169 GPRS connection causes Ooops
Submitter	: Clemens Eisserer <linuxhippy@gmail.com>
Date		: 2009-08-04 09:02 (6 days old)


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13899
Subject		: Oops from tar, 2.6.31-rc5, 32 bit on quad core phenom.
Submitter	: Gene Heskett <gene.heskett@verizon.net>
Date		: 2009-08-01 13:04 (9 days old)
References	: http://marc.info/?l=linux-kernel&m=124913190304149&w=4


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13895
Subject		: 2.6.31-rc4 - slab entry tak_delay_info leaking ???
Submitter	: Paul Rolland <rol@as2917.net>
Date		: 2009-07-29 08:20 (12 days old)
References	: http://marc.info/?l=linux-kernel&m=124884847925375&w=4


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13869
Subject		: Radeon framebuffer (w/o KMS) corruption at boot.
Submitter	: Duncan <1i5t5.duncan@cox.net>
Date		: 2009-07-29 16:44 (12 days old)


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13848
Subject		: iwlwifi (4965) regression since 2.6.30
Submitter	: Lukas Hejtmanek <xhejtman@ics.muni.cz>
Date		: 2009-07-26 7:57 (15 days old)
References	: http://marc.info/?l=linux-kernel&m=124859658502866&w=4


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13846
Subject		: LEDs switched off permanently by power saving with rt61pci driver
Submitter	: Chris Clayton <chris2553@googlemail.com>
Date		: 2009-07-13 8:27 (28 days old)
References	: http://marc.info/?l=linux-kernel&m=124747418828398&w=4


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13837
Subject		: Input : regression - touchpad not detected
Submitter	: Dave Young <hidave.darkstar@gmail.com>
Date		: 2009-07-17 07:13 (24 days old)
References	: http://marc.info/?l=linux-kernel&m=124780763701571&w=4


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13836
Subject		: suspend script fails, related to stdout?
Submitter	: Tomas M. <tmezzadra@gmail.com>
Date		: 2009-07-17 21:24 (24 days old)
References	: http://marc.info/?l=linux-kernel&m=124785853811667&w=4


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13833
Subject		: Kernel Oops when trying to suspend with ubifs mounted on block2mtd mtd device
Submitter	: Tobias Diedrich <ranma@tdiedrich.de>
Date		: 2009-07-15 14:20 (26 days old)
First-Bad-Commit: http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=15bce40cb3133bcc07d548013df97e4653d363c1
References	: http://marc.info/?l=linux-kernel&m=124766049207807&w=4
		  http://marc.info/?l=linux-kernel&m=124704927819769&w=4


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13819
Subject		: system freeze when switching to console
Submitter	: Reinette Chatre <reinette.chatre@intel.com>
Date		: 2009-07-23 17:57 (18 days old)


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13809
Subject		: oprofile: possible circular locking dependency detected
Submitter	: Jerome Marchand <jmarchan@redhat.com>
Date		: 2009-07-22 13:35 (19 days old)


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13740
Subject		: X server crashes with 2.6.31-rc2 when options are changed
Submitter	: Michael S. Tsirkin <m.s.tsirkin@gmail.com>
Date		: 2009-07-07 15:19 (34 days old)


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13733
Subject		: 2.6.31-rc2: irq 16: nobody cared
Submitter	: Niel Lambrechts <niel.lambrechts@gmail.com>
Date		: 2009-07-06 18:32 (35 days old)
References	: http://marc.info/?l=linux-kernel&m=124690524027166&w=4


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13716
Subject		: The AIC-7892P controller does not work any more
Submitter	: Andrej Podzimek <andrej@podzimek.org>
Date		: 2009-07-05 19:23 (36 days old)


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13713
Subject		: [drm/i915] Possible regression due to commit "Change GEM throttling to be 20ms (...)"
Submitter	:  <kazikcz@gmail.com>
Date		: 2009-07-05 10:49 (36 days old)
First-Bad-Commit: http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=b962442e46a9340bdbc6711982c59ff0cc2b5afb


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13645
Subject		: NULL pointer dereference at (null) (level2_spare_pgt)
Submitter	: poornima nayak <mpnayak@linux.vnet.ibm.com>
Date		: 2009-06-17 17:56 (54 days old)
References	: http://lkml.org/lkml/2009/6/17/194


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

Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13948
Subject		: ath5k broken after suspend-to-ram
Submitter	: Johannes Stezenbach <js@sig21.net>
Date		: 2009-08-07 21:51 (3 days old)
References	: http://marc.info/?l=linux-kernel&m=124968192727854&w=4
Handled-By	: Nick Kossifidis <mickflemm@gmail.com>
Patch		: http://patchwork.kernel.org/patch/38550/


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13946
Subject		: x86 MCE malfunction on Thinkpad T42p
Submitter	: Johannes Stezenbach <js@sig21.net>
Date		: 2009-08-07 17:09 (3 days old)
References	: http://marc.info/?l=linux-kernel&m=124966500232399&w=4
Handled-By	: Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>
Patch		: http://patchwork.kernel.org/patch/37908/


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13944
Subject		: MD raid regression
Submitter	: Mike Snitzer <snitzer@redhat.com>
Date		: 2009-08-05 15:06 (5 days old)
First-Bad-Commit: http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=449aad3e25358812c43afc60918c5ad3819488e7
References	: http://marc.info/?l=linux-kernel&m=124948481218857&w=4
Handled-By	: NeilBrown <neilb@suse.de>
Patch		: http://patchwork.kernel.org/patch/39521/


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

As you can see, there is a Bugzilla entry for each of the listed regressions.
There also is a Bugzilla entry used for tracking the regressions from 2.6.30,
unresolved as well as resolved, at:

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

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-acpi" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Bug #13645] NULL pointer dereference at (null) (level2_spare_pgt)

[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.30.  Please verify if it still should be listed and let me know
(either way).


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13645
Subject		: NULL pointer dereference at (null) (level2_spare_pgt)
Submitter	: poornima nayak <mpnayak-23VcF4HTsmIX0ybBhKVfKdBPR1lH4CV8@public.gmane.org>
Date		: 2009-06-17 17:56 (54 days old)
References	: http://lkml.org/lkml/2009/6/17/194

[Bug #13713] [drm/i915] Possible regression due to commit "Change GEM throttling to be 20ms (...)"

[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.30.  Please verify if it still should be listed and let me know
(either way).


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13713
Subject		: [drm/i915] Possible regression due to commit "Change GEM throttling to be 20ms (...)"
Submitter	:  <kazikcz@gmail.com>
Date		: 2009-07-05 10:49 (36 days old)
First-Bad-Commit: http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=b962442e46a9340bdbc6711982c59ff0cc2b5afb

[Bug #13819] system freeze when switching to console

[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.30.  Please verify if it still should be listed and let me know
(either way).


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13819
Subject		: system freeze when switching to console
Submitter	: Reinette Chatre <reinette.chatre-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
Date		: 2009-07-23 17:57 (18 days old)

[Bug #13809] oprofile: possible circular locking dependency detected

[Rafael J. Wysocki]

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

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


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13809
Subject		: oprofile: possible circular locking dependency detected
Submitter	: Jerome Marchand <jmarchan@redhat.com>
Date		: 2009-07-22 13:35 (19 days old)

[Bug #13716] The AIC-7892P controller does not work any more

[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.30.  Please verify if it still should be listed and let me know
(either way).


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13716
Subject		: The AIC-7892P controller does not work any more
Submitter	: Andrej Podzimek <andrej-+Hii8LNHG6Ng9hUCZPvPmw@public.gmane.org>
Date		: 2009-07-05 19:23 (36 days old)

[Bug #13740] X server crashes with 2.6.31-rc2 when options are changed

[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.30.  Please verify if it still should be listed and let me know
(either way).


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13740
Subject		: X server crashes with 2.6.31-rc2 when options are changed
Submitter	: Michael S. Tsirkin <m.s.tsirkin-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Date		: 2009-07-07 15:19 (34 days old)

[Bug #13733] 2.6.31-rc2: irq 16: nobody cared

[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.30.  Please verify if it still should be listed and let me know
(either way).


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13733
Subject		: 2.6.31-rc2: irq 16: nobody cared
Submitter	: Niel Lambrechts <niel.lambrechts-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Date		: 2009-07-06 18:32 (35 days old)
References	: http://marc.info/?l=linux-kernel&m=124690524027166&w=4

[Bug #13833] Kernel Oops when trying to suspend with ubifs mounted on block2mtd mtd device

[Rafael J. Wysocki]

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

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


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13833
Subject		: Kernel Oops when trying to suspend with ubifs mounted on block2mtd mtd device
Submitter	: Tobias Diedrich <ranma@tdiedrich.de>
Date		: 2009-07-15 14:20 (26 days old)
First-Bad-Commit: http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=15bce40cb3133bcc07d548013df97e4653d363c1
References	: http://marc.info/?l=linux-kernel&m=124766049207807&w=4
		  http://marc.info/?l=linux-kernel&m=124704927819769&w=4

[Bug #13837] Input : regression - touchpad not detected

[Rafael J. Wysocki]

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

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


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13837
Subject		: Input : regression - touchpad not detected
Submitter	: Dave Young <hidave.darkstar@gmail.com>
Date		: 2009-07-17 07:13 (24 days old)
References	: http://marc.info/?l=linux-kernel&m=124780763701571&w=4

Re: [Bug #13837] Input : regression - touchpad not detected

[Dave Young]

On Mon, Aug 10, 2009 at 5:10 AM, Rafael J. Wysocki<rjw-KKrjLPT3xs0@public.gmane.org> wrote:
> This message has been generated automatically as a part of a report
> of recent regressions.
>
> The following bug entry is on the current list of known regressions
> from 2.6.30.  Please verify if it still should be listed and let me know
> (either way).

Rafael, I can not produce the bug recent days. I upgraded dell bios to
A12, don't know if it is related.

>
>
> Bug-Entry       : http://bugzilla.kernel.org/show_bug.cgi?id=13837
> Subject         : Input : regression - touchpad not detected
> Submitter       : Dave Young <hidave.darkstar-Re5JQEeQqe8@public.gmane.orgm>
> Date            : 2009-07-17 07:13 (24 days old)
> References      : http://marc.info/?l=linux-kernel&m=124780763701571&w=4
>
>
>



-- 
Regards
dave

Re: [Bug #13837] Input : regression - touchpad not detected

[Rafael J. Wysocki]

On Monday 10 August 2009, Dave Young wrote:
> On Mon, Aug 10, 2009 at 5:10 AM, Rafael J. Wysocki<rjw-KKrjLPT3xs0@public.gmane.org> wrote:
> > This message has been generated automatically as a part of a report
> > of recent regressions.
> >
> > The following bug entry is on the current list of known regressions
> > from 2.6.30.  Please verify if it still should be listed and let me know
> > (either way).
> 
> Rafael, I can not produce the bug recent days. I upgraded dell bios to
> A12, don't know if it is related.

OK, I closed the bug as not reproducible.

Thanks,
Rafael

[Bug #13836] suspend script fails, related to stdout?

[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.30.  Please verify if it still should be listed and let me know
(either way).


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13836
Subject		: suspend script fails, related to stdout?
Submitter	: Tomas M. <tmezzadra@gmail.com>
Date		: 2009-07-17 21:24 (24 days old)
References	: http://marc.info/?l=linux-kernel&m=124785853811667&w=4

[Bug #13848] iwlwifi (4965) regression since 2.6.30

[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.30.  Please verify if it still should be listed and let me know
(either way).


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13848
Subject		: iwlwifi (4965) regression since 2.6.30
Submitter	: Lukas Hejtmanek <xhejtman-8qz54MUs51PtwjQa/ONI9g@public.gmane.org>
Date		: 2009-07-26 7:57 (15 days old)
References	: http://marc.info/?l=linux-kernel&m=124859658502866&w=4

[Bug #13869] Radeon framebuffer (w/o KMS) corruption at boot.

[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.30.  Please verify if it still should be listed and let me know
(either way).


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13869
Subject		: Radeon framebuffer (w/o KMS) corruption at boot.
Submitter	: Duncan <1i5t5.duncan@cox.net>
Date		: 2009-07-29 16:44 (12 days old)

Re: [Bug #13869] Radeon framebuffer (w/o KMS) corruption at boot.

[Duncan]

On Sunday 09 August 2009 13:44:24 Rafael J. Wysocki wrote:
> This message has been generated automatically as a part of a report
> of recent regressions.
>
> The following bug entry is on the current list of known regressions
> from 2.6.30.  Please verify if it still should be listed and let me know
> (either way).
>
> Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13869
> Subject		: Radeon framebuffer (w/o KMS) corruption at boot.
> Submitter	: Duncan <1i5t5.duncan@cox.net>
> Date		: 2009-07-29 16:44 (12 days old)

Yes, as of today's pull, it's still there.

-- 
Duncan - List replies preferred.   No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master."  Richard Stallman

Re: [Bug #13869] Radeon framebuffer (w/o KMS) corruption at boot.

[Rafael J. Wysocki]

On Monday 10 August 2009, Duncan wrote:
> On Sunday 09 August 2009 13:44:24 Rafael J. Wysocki wrote:
> > This message has been generated automatically as a part of a report
> > of recent regressions.
> >
> > The following bug entry is on the current list of known regressions
> > from 2.6.30.  Please verify if it still should be listed and let me know
> > (either way).
> >
> > Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13869
> > Subject		: Radeon framebuffer (w/o KMS) corruption at boot.
> > Submitter	: Duncan <1i5t5.duncan-j9pdmedNgrk@public.gmane.org>
> > Date		: 2009-07-29 16:44 (12 days old)
> 
> Yes, as of today's pull, it's still there.

Thanks for the update.

Rafael

[Bug #13846] LEDs switched off permanently by power saving with rt61pci driver

[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.30.  Please verify if it still should be listed and let me know
(either way).


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13846
Subject		: LEDs switched off permanently by power saving with rt61pci driver
Submitter	: Chris Clayton <chris2553@googlemail.com>
Date		: 2009-07-13 8:27 (28 days old)
References	: http://marc.info/?l=linux-kernel&m=124747418828398&w=4

Re: [Bug #13846] LEDs switched off permanently by power saving with rt61pci driver

[Chris Clayton]

Hi Rafael,

On Sunday 09 August 2009, Rafael J. Wysocki wrote:
> This message has been generated automatically as a part of a report
> of recent regressions.
>
> The following bug entry is on the current list of known regressions
> from 2.6.30.  Please verify if it still should be listed and let me know
> (either way).
>

Ivo sent a test patch for this and I tested it., but without success. I reported my findings but 
didn't get a reply. See http://marc.info/?l=linux-wireless&m=124940189007154&w=4.

I suspect the failure is due to the same PS hardware probelms that were at the route of my original 
report.. Unless one of the wireless folks say otherwise, I think we should close this on the basis 
of busted hardware. I'm happy to simply eject the card and re-insert it now that I have some udev 
scripts to tear down the wireless configuration on the ejection and set it uop again when the card 
is re-inserted.

Thanks

Chris


>
> Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13846
> Subject		: LEDs switched off permanently by power saving with rt61pci
> driver Submitter	: Chris Clayton <chris2553-gM/Ye1E23mwN+BqQ9rBEUg@public.gmane.org>
> Date		: 2009-07-13 8:27 (28 days old)
> References	: http://marc.info/?l=linux-kernel&m=124747418828398&w=4


-- 
No, Sir; there is nothing which has yet been contrived by man, by which so much happiness is 
produced as by a good tavern or inn - Doctor Samuel Johnson

Re: [Bug #13846] LEDs switched off permanently by power saving with rt61pci driver

[Rafael J. Wysocki]

On Monday 10 August 2009, Chris Clayton wrote:
> Hi Rafael,
> 
> On Sunday 09 August 2009, Rafael J. Wysocki wrote:
> > This message has been generated automatically as a part of a report
> > of recent regressions.
> >
> > The following bug entry is on the current list of known regressions
> > from 2.6.30.  Please verify if it still should be listed and let me know
> > (either way).
> >
> 
> Ivo sent a test patch for this and I tested it., but without success. I reported my findings but 
> didn't get a reply. See http://marc.info/?l=linux-wireless&m=124940189007154&w=4.
> 
> I suspect the failure is due to the same PS hardware probelms that were at the route of my original 
> report.. Unless one of the wireless folks say otherwise, I think we should close this on the basis 
> of busted hardware. I'm happy to simply eject the card and re-insert it now that I have some udev 
> scripts to tear down the wireless configuration on the ejection and set it uop again when the card 
> is re-inserted.

Thanks, closed.

Rafael

[Bug #13895] 2.6.31-rc4 - slab entry tak_delay_info leaking ???

[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.30.  Please verify if it still should be listed and let me know
(either way).


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13895
Subject		: 2.6.31-rc4 - slab entry tak_delay_info leaking ???
Submitter	: Paul Rolland <rol-hQZ2c1jdYO6sTnJN9+BGXg@public.gmane.org>
Date		: 2009-07-29 08:20 (12 days old)
References	: http://marc.info/?l=linux-kernel&m=124884847925375&w=4

[Bug #13914] e1000e reports invalid NVM Checksum on 82566DM-2 (bisected)

[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.30.  Please verify if it still should be listed and let me know
(either way).


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13914
Subject		: e1000e reports invalid NVM Checksum on 82566DM-2 (bisected)
Submitter	:  <jsbronder@gentoo.org>
Date		: 2009-08-04 18:06 (6 days old)

[Bug #13906] Huawei E169 GPRS connection causes Ooops

[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.30.  Please verify if it still should be listed and let me know
(either way).


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13906
Subject		: Huawei E169 GPRS connection causes Ooops
Submitter	: Clemens Eisserer <linuxhippy-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Date		: 2009-08-04 09:02 (6 days old)

[Bug #13899] Oops from tar, 2.6.31-rc5, 32 bit on quad core phenom.

[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.30.  Please verify if it still should be listed and let me know
(either way).


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13899
Subject		: Oops from tar, 2.6.31-rc5, 32 bit on quad core phenom.
Submitter	: Gene Heskett <gene.heskett@verizon.net>
Date		: 2009-08-01 13:04 (9 days old)
References	: http://marc.info/?l=linux-kernel&m=124913190304149&w=4

Re: [Bug #13899] Oops from tar, 2.6.31-rc5, 32 bit on quad core phenom.

[Gene Heskett]

On Sunday 09 August 2009, Rafael J. Wysocki wrote:
>This message has been generated automatically as a part of a report
>of recent regressions.
>
>The following bug entry is on the current list of known regressions
>from 2.6.30.  Please verify if it still should be listed and let me know
>(either way).
>
>
>Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13899
>Subject		: Oops from tar, 2.6.31-rc5, 32 bit on quad core phenom.
>Submitter	: Gene Heskett <gene.heskett-H+0wwilmMs3R7s880joybQ@public.gmane.org>
>Date		: 2009-08-01 13:04 (9 days old)
>References	: http://marc.info/?l=linux-kernel&m=124913190304149&w=4

Yes, it is still doing it to rc5 but only on the first invocation after the 
bootup.  Strangely, it apparently has no other effect, either on the machine, 
or how amanda itself works.

-- 
Cheers, Gene
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
The NRA is offering FREE Associate memberships to anyone who wants them.
<https://www.nrahq.org/nrabonus/accept-membership.asp>

If I set here and stare at nothing long enough, people might think
I'm an engineer working on something.
		-- S.R. McElroy

Re: [Bug #13899] Oops from tar, 2.6.31-rc5, 32 bit on quad core phenom.

[Rafael J. Wysocki]

On Monday 10 August 2009, Gene Heskett wrote:
> On Sunday 09 August 2009, Rafael J. Wysocki wrote:
> >This message has been generated automatically as a part of a report
> >of recent regressions.
> >
> >The following bug entry is on the current list of known regressions
> >from 2.6.30.  Please verify if it still should be listed and let me know
> >(either way).
> >
> >
> >Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13899
> >Subject		: Oops from tar, 2.6.31-rc5, 32 bit on quad core phenom.
> >Submitter	: Gene Heskett <gene.heskett-H+0wwilmMs3R7s880joybQ@public.gmane.org>
> >Date		: 2009-08-01 13:04 (9 days old)
> >References	: http://marc.info/?l=linux-kernel&m=124913190304149&w=4
> 
> Yes, it is still doing it to rc5 but only on the first invocation after the 
> bootup.  Strangely, it apparently has no other effect, either on the machine, 
> or how amanda itself works.

Thanks for the update.

Rafael

[Bug #13941] x86 Geode issue

[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.30.  Please verify if it still should be listed and let me know
(either way).


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13941
Subject		: x86 Geode issue
Submitter	: Martin-Éric Racine <q-funk-X3B1VOXEql0@public.gmane.org>
Date		: 2009-08-03 12:58 (7 days old)
References	: http://marc.info/?l=linux-kernel&m=124930434732481&w=4

Re: [Bug #13941] x86 Geode issue

[Martin-Éric Racine]

Yes, this bug is still valid.

Ubuntu kernel team member Leann Ogasawara and I are slowly bisecting
our way through the changes that took place since 2.6.30 to find the
commit that introduced this regression. Please stay tuned.

On Mon, Aug 10, 2009 at 12:10 AM, Rafael J. Wysocki<rjw-KKrjLPT3xs0@public.gmane.org> wrote:
> This message has been generated automatically as a part of a report
> of recent regressions.
>
> The following bug entry is on the current list of known regressions
> from 2.6.30.  Please verify if it still should be listed and let me know
> (either way).
>
>
> Bug-Entry       : http://bugzilla.kernel.org/show_bug.cgi?id=13941
> Subject         : x86 Geode issue
> Submitter       : Martin-Éric Racine <q-funk@iki.fi>
> Date            : 2009-08-03 12:58 (7 days old)
> References      : http://marc.info/?l=linux-kernel&m=124930434732481&w=4
>
>
>

Re: [Bug #13941] x86 Geode issue

[Ingo Molnar]

* Martin-Éric Racine <q-funk-X3B1VOXEql0@public.gmane.org> wrote:

> Yes, this bug is still valid.
> 
> Ubuntu kernel team member Leann Ogasawara and I are slowly 
> bisecting our way through the changes that took place since 2.6.30 
> to find the commit that introduced this regression. Please stay 
> tuned.

hm, the only outright Geode related commit was:

 d6c585a: x86: geode: Mark mfgpt irq IRQF_TIMER to prevent resume failure

the jpg at:

  http://launchpadlibrarian.net/28892781/00002.jpg

is very out of focus - but what i could decypher suggests a 
pagefault crash in the VFS code, in generic_delete_inode().

Which could be a VFS bug, or a filesystem bug, or some unrelated 
memory corruption hitting the inode data structure.

	Ingo

Re: [Bug #13941] x86 Geode issue

[Martin-Éric Racine]

On Thu, Aug 13, 2009 at 12:07 PM, Ingo Molnar<mingo-X9Un+BFzKDI@public.gmane.org> wrote:
>
> * Martin-Éric Racine <q-funk-X3B1VOXEql0@public.gmane.org> wrote:
>
>> Yes, this bug is still valid.
>>
>> Ubuntu kernel team member Leann Ogasawara and I are slowly
>> bisecting our way through the changes that took place since 2.6.30
>> to find the commit that introduced this regression. Please stay
>> tuned.
>
> hm, the only outright Geode related commit was:
>
>  d6c585a: x86: geode: Mark mfgpt irq IRQF_TIMER to prevent resume failure
>
> the jpg at:
>
>  http://launchpadlibrarian.net/28892781/00002.jpg
>
> is very out of focus - but what i could decypher suggests a
> pagefault crash in the VFS code, in generic_delete_inode().

There's a few more JPEG images below that have a slightly sharper image.

> Which could be a VFS bug, or a filesystem bug, or some unrelated
> memory corruption hitting the inode data structure.

It could indeed be many things.

I've been trying to boot this into a larger framebuffer to be able to
fit more data into my snapshots, but it appears that vga=795 doesn't
work anymore. Have we reverted to Hex values again or is this just an
issue of some kernel module missing from initrd?

Martin-Éric

Re: [Bug #13941] x86 Geode issue

[Martin-Éric Racine]

2009/8/13 Martin-Éric Racine <q-funk-X3B1VOXEql0@public.gmane.org>:
> On Thu, Aug 13, 2009 at 12:07 PM, Ingo Molnar<mingo-X9Un+BFzKDI@public.gmane.org> wrote:
>> * Martin-Éric Racine <q-funk-X3B1VOXEql0@public.gmane.org> wrote:
>>> Yes, this bug is still valid.
>>>
>>> Ubuntu kernel team member Leann Ogasawara and I are slowly
>>> bisecting our way through the changes that took place since 2.6.30
>>> to find the commit that introduced this regression. Please stay
>>> tuned.
>>
>> hm, the only outright Geode related commit was:
>>
>>  d6c585a: x86: geode: Mark mfgpt irq IRQF_TIMER to prevent resume failure
>>
>> the jpg at:
>>
>>  http://launchpadlibrarian.net/28892781/00002.jpg
>>
>> is very out of focus - but what i could decypher suggests a
>> pagefault crash in the VFS code, in generic_delete_inode().

This one might be a bit better:

http://launchpadlibrarian.net/30267494/2.6.31-5.24.jpg

>> Which could be a VFS bug, or a filesystem bug, or some unrelated
>> memory corruption hitting the inode data structure.
>
> It could indeed be many things.
>
> I've been trying to boot this into a larger framebuffer to be able to
> fit more data into my snapshots, but it appears that vga=795 doesn't
> work anymore. Have we reverted to Hex values again or is this just an
> issue of some kernel module missing from initrd?

Never mind. Seems that vesafb was blacklisted. Works now. See the
image above. :)

Martin-Éric

Re: [Bug #13941] x86 Geode issue

[Rafael J. Wysocki]

On Thursday 13 August 2009, Martin-Éric Racine wrote:
> 2009/8/13 Martin-Éric Racine <q-funk-X3B1VOXEql0@public.gmane.org>:
> > On Thu, Aug 13, 2009 at 12:07 PM, Ingo Molnar<mingo-X9Un+BFzKDI@public.gmane.org> wrote:
> >> * Martin-Éric Racine <q-funk-X3B1VOXEql0@public.gmane.org> wrote:
> >>> Yes, this bug is still valid.
> >>>
> >>> Ubuntu kernel team member Leann Ogasawara and I are slowly
> >>> bisecting our way through the changes that took place since 2.6.30
> >>> to find the commit that introduced this regression. Please stay
> >>> tuned.
> >>
> >> hm, the only outright Geode related commit was:
> >>
> >>  d6c585a: x86: geode: Mark mfgpt irq IRQF_TIMER to prevent resume failure
> >>
> >> the jpg at:
> >>
> >>  http://launchpadlibrarian.net/28892781/00002.jpg
> >>
> >> is very out of focus - but what i could decypher suggests a
> >> pagefault crash in the VFS code, in generic_delete_inode().
> 
> This one might be a bit better:
> 
> http://launchpadlibrarian.net/30267494/2.6.31-5.24.jpg
> 
> >> Which could be a VFS bug, or a filesystem bug, or some unrelated
> >> memory corruption hitting the inode data structure.
> >
> > It could indeed be many things.
> >
> > I've been trying to boot this into a larger framebuffer to be able to
> > fit more data into my snapshots, but it appears that vga=795 doesn't
> > work anymore. Have we reverted to Hex values again or is this just an
> > issue of some kernel module missing from initrd?
> 
> Never mind. Seems that vesafb was blacklisted. Works now. See the
> image above. :)

OK, so I guess the bug should be closed?

Rafael

Re: [Bug #13941] x86 Geode issue

[Martin-Éric Racine]

On Thu, Aug 13, 2009 at 5:54 PM, Rafael J. Wysocki<rjw-KKrjLPT3xs0@public.gmane.org> wrote:
> On Thursday 13 August 2009, Martin-Éric Racine wrote:
>> 2009/8/13 Martin-Éric Racine <q-funk-X3B1VOXEql0@public.gmane.org>:
>> > On Thu, Aug 13, 2009 at 12:07 PM, Ingo Molnar<mingo-X9Un+BFzKDI@public.gmane.org> wrote:
>> >> * Martin-Éric Racine <q-funk-X3B1VOXEql0@public.gmane.org> wrote:
>> >>> Yes, this bug is still valid.
>> >>>
>> >>> Ubuntu kernel team member Leann Ogasawara and I are slowly
>> >>> bisecting our way through the changes that took place since 2.6.30
>> >>> to find the commit that introduced this regression. Please stay
>> >>> tuned.
>> >>
>> >> hm, the only outright Geode related commit was:
>> >>
>> >>  d6c585a: x86: geode: Mark mfgpt irq IRQF_TIMER to prevent resume failure
>> >>
>> >> the jpg at:
>> >>
>> >>  http://launchpadlibrarian.net/28892781/00002.jpg
>> >>
>> >> is very out of focus - but what i could decypher suggests a
>> >> pagefault crash in the VFS code, in generic_delete_inode().
>>
>> This one might be a bit better:
>>
>> http://launchpadlibrarian.net/30267494/2.6.31-5.24.jpg
>>
>> >> Which could be a VFS bug, or a filesystem bug, or some unrelated
>> >> memory corruption hitting the inode data structure.
>> >
>> > It could indeed be many things.
>> >
>> > I've been trying to boot this into a larger framebuffer to be able to
>> > fit more data into my snapshots, but it appears that vga=795 doesn't
>> > work anymore. Have we reverted to Hex values again or is this just an
>> > issue of some kernel module missing from initrd?
>>
>> Never mind. Seems that vesafb was blacklisted. Works now. See the
>> image above. :)
>
> OK, so I guess the bug should be closed?

No, it cannot.  Please read the above more carefully.

Martin-Éric

Re: [Bug #13941] x86 Geode issue

[Rafael J. Wysocki]

On Thursday 13 August 2009, Martin-Éric Racine wrote:
> On Thu, Aug 13, 2009 at 5:54 PM, Rafael J. Wysocki<rjw-KKrjLPT3xs0@public.gmane.org> wrote:
> > On Thursday 13 August 2009, Martin-Éric Racine wrote:
> >> 2009/8/13 Martin-Éric Racine <q-funk-X3B1VOXEql0@public.gmane.org>:
> >> > On Thu, Aug 13, 2009 at 12:07 PM, Ingo Molnar<mingo-X9Un+BFzKDI@public.gmane.org> wrote:
> >> >> * Martin-Éric Racine <q-funk-X3B1VOXEql0@public.gmane.org> wrote:
> >> >>> Yes, this bug is still valid.
> >> >>>
> >> >>> Ubuntu kernel team member Leann Ogasawara and I are slowly
> >> >>> bisecting our way through the changes that took place since 2.6.30
> >> >>> to find the commit that introduced this regression. Please stay
> >> >>> tuned.
> >> >>
> >> >> hm, the only outright Geode related commit was:
> >> >>
> >> >>  d6c585a: x86: geode: Mark mfgpt irq IRQF_TIMER to prevent resume failure
> >> >>
> >> >> the jpg at:
> >> >>
> >> >>  http://launchpadlibrarian.net/28892781/00002.jpg
> >> >>
> >> >> is very out of focus - but what i could decypher suggests a
> >> >> pagefault crash in the VFS code, in generic_delete_inode().
> >>
> >> This one might be a bit better:
> >>
> >> http://launchpadlibrarian.net/30267494/2.6.31-5.24.jpg

Hmm.  This looks like a sysfs oops to my untrained eye.

Thanks,
Rafael

Re: [Bug #13941] x86 Geode issue

[Martin-Éric Racine]

On Thu, Aug 13, 2009 at 9:34 PM, Rafael J. Wysocki<rjw-KKrjLPT3xs0@public.gmane.org> wrote:
> On Thursday 13 August 2009, Martin-Éric Racine wrote:
>> On Thu, Aug 13, 2009 at 5:54 PM, Rafael J. Wysocki<rjw-KKrjLPT3xs0@public.gmane.org> wrote:
>> > On Thursday 13 August 2009, Martin-Éric Racine wrote:
>> >> 2009/8/13 Martin-Éric Racine <q-funk-X3B1VOXEql0@public.gmane.org>:
>> >> > On Thu, Aug 13, 2009 at 12:07 PM, Ingo Molnar<mingo-X9Un+BFzKDI@public.gmane.org> wrote:
>> >> >> * Martin-Éric Racine <q-funk-X3B1VOXEql0@public.gmane.org> wrote:
>> >> >>> Yes, this bug is still valid.
>> >> >>>
>> >> >>> Ubuntu kernel team member Leann Ogasawara and I are slowly
>> >> >>> bisecting our way through the changes that took place since 2.6.30
>> >> >>> to find the commit that introduced this regression. Please stay
>> >> >>> tuned.
>> >> >>
>> >> >> hm, the only outright Geode related commit was:
>> >> >>
>> >> >>  d6c585a: x86: geode: Mark mfgpt irq IRQF_TIMER to prevent resume failure
>> >> >>
>> >> >> the jpg at:
>> >> >>
>> >> >>  http://launchpadlibrarian.net/28892781/00002.jpg
>> >> >>
>> >> >> is very out of focus - but what i could decypher suggests a
>> >> >> pagefault crash in the VFS code, in generic_delete_inode().
>> >>
>> >> This one might be a bit better:
>> >>
>> >> http://launchpadlibrarian.net/30267494/2.6.31-5.24.jpg
>
> Hmm.  This looks like a sysfs oops to my untrained eye.

The bisect I did with Leann Ogasawara has narrowed the kernel panic
down to the following:

commit f19d4a8fa6f9b6ccf54df0971c97ffcaa390b7b0
Author: Al Viro <viro-RmSDqhL/yNMiFSDQTTA3OLVCufUGDwFn@public.gmane.org>
Date: Mon Jun 8 19:50:45 2009 -0400

    add caching of ACLs in struct inode

    No helpers, no conversions yet.

    Signed-off-by: Al Viro <viro-RmSDqhL/yNMiFSDQTTA3OLVCufUGDwFn@public.gmane.org>

Best Regards,
Martin-Éric

Re: [Bug #13941] x86 Geode issue

[Ingo Molnar]

* Martin-Éric Racine <q-funk-X3B1VOXEql0@public.gmane.org> wrote:

> On Thu, Aug 13, 2009 at 9:34 PM, Rafael J. Wysocki<rjw-KKrjLPT3xs0@public.gmane.org> wrote:
> > On Thursday 13 August 2009, Martin-Éric Racine wrote:
> >> On Thu, Aug 13, 2009 at 5:54 PM, Rafael J. Wysocki<rjw-KKrjLPT3xs0@public.gmane.org> wrote:
> >> > On Thursday 13 August 2009, Martin-Éric Racine wrote:
> >> >> 2009/8/13 Martin-Éric Racine <q-funk-X3B1VOXEql0@public.gmane.org>:
> >> >> > On Thu, Aug 13, 2009 at 12:07 PM, Ingo Molnar<mingo-X9Un+BFzKDI@public.gmane.org> wrote:
> >> >> >> * Martin-Éric Racine <q-funk-X3B1VOXEql0@public.gmane.org> wrote:
> >> >> >>> Yes, this bug is still valid.
> >> >> >>>
> >> >> >>> Ubuntu kernel team member Leann Ogasawara and I are slowly
> >> >> >>> bisecting our way through the changes that took place since 2.6.30
> >> >> >>> to find the commit that introduced this regression. Please stay
> >> >> >>> tuned.
> >> >> >>
> >> >> >> hm, the only outright Geode related commit was:
> >> >> >>
> >> >> >>  d6c585a: x86: geode: Mark mfgpt irq IRQF_TIMER to prevent resume failure
> >> >> >>
> >> >> >> the jpg at:
> >> >> >>
> >> >> >>  http://launchpadlibrarian.net/28892781/00002.jpg
> >> >> >>
> >> >> >> is very out of focus - but what i could decypher suggests a
> >> >> >> pagefault crash in the VFS code, in generic_delete_inode().
> >> >>
> >> >> This one might be a bit better:
> >> >>
> >> >> http://launchpadlibrarian.net/30267494/2.6.31-5.24.jpg
> >
> > Hmm.  This looks like a sysfs oops to my untrained eye.
> 
> The bisect I did with Leann Ogasawara has narrowed the kernel panic
> down to the following:
> 
> commit f19d4a8fa6f9b6ccf54df0971c97ffcaa390b7b0
> Author: Al Viro <viro-RmSDqhL/yNMiFSDQTTA3OLVCufUGDwFn@public.gmane.org>
> Date: Mon Jun 8 19:50:45 2009 -0400
> 
>     add caching of ACLs in struct inode
> 
>     No helpers, no conversions yet.
> 
>     Signed-off-by: Al Viro <viro-RmSDqhL/yNMiFSDQTTA3OLVCufUGDwFn@public.gmane.org>

Weird. If the functions do what their name suggests, i.e. if 
inode_init_always() is an always called constructor and if 
destroy_inode() is an unconditional destructor then this patch 
should have no functional effect on the VFS side.

It increases the size of struct inode, so if you have some old 
module (built to an older version of fs.h) still around it might 
corrupt your inode data structure.

Or the size change might trigger some dormant bug. It might move a 
critical inode right into the path of a pre-existing (but not 
visibly crash-triggering) data corruption.

The possibilities on the 'weird bug' front are endless - the 
crash/oops itself should be turned into text, posted here and 
analyzed.

	Ingo

Re: [Bug #13941] x86 Geode issue

[Ingo Molnar]

* Ingo Molnar <mingo-X9Un+BFzKDI@public.gmane.org> wrote:

> 
> * Martin-Éric Racine <q-funk-X3B1VOXEql0@public.gmane.org> wrote:
> 
> > On Thu, Aug 13, 2009 at 9:34 PM, Rafael J. Wysocki<rjw-KKrjLPT3xs0@public.gmane.org> wrote:
> > > On Thursday 13 August 2009, Martin-Éric Racine wrote:
> > >> On Thu, Aug 13, 2009 at 5:54 PM, Rafael J. Wysocki<rjw-KKrjLPT3xs0@public.gmane.org> wrote:
> > >> > On Thursday 13 August 2009, Martin-Éric Racine wrote:
> > >> >> 2009/8/13 Martin-Éric Racine <q-funk-X3B1VOXEql0@public.gmane.org>:
> > >> >> > On Thu, Aug 13, 2009 at 12:07 PM, Ingo Molnar<mingo-X9Un+BFzKDI@public.gmane.org> wrote:
> > >> >> >> * Martin-Éric Racine <q-funk-X3B1VOXEql0@public.gmane.org> wrote:
> > >> >> >>> Yes, this bug is still valid.
> > >> >> >>>
> > >> >> >>> Ubuntu kernel team member Leann Ogasawara and I are slowly
> > >> >> >>> bisecting our way through the changes that took place since 2.6.30
> > >> >> >>> to find the commit that introduced this regression. Please stay
> > >> >> >>> tuned.
> > >> >> >>
> > >> >> >> hm, the only outright Geode related commit was:
> > >> >> >>
> > >> >> >>  d6c585a: x86: geode: Mark mfgpt irq IRQF_TIMER to prevent resume failure
> > >> >> >>
> > >> >> >> the jpg at:
> > >> >> >>
> > >> >> >>  http://launchpadlibrarian.net/28892781/00002.jpg
> > >> >> >>
> > >> >> >> is very out of focus - but what i could decypher suggests a
> > >> >> >> pagefault crash in the VFS code, in generic_delete_inode().
> > >> >>
> > >> >> This one might be a bit better:
> > >> >>
> > >> >> http://launchpadlibrarian.net/30267494/2.6.31-5.24.jpg
> > >
> > > Hmm.  This looks like a sysfs oops to my untrained eye.
> > 
> > The bisect I did with Leann Ogasawara has narrowed the kernel panic
> > down to the following:
> > 
> > commit f19d4a8fa6f9b6ccf54df0971c97ffcaa390b7b0
> > Author: Al Viro <viro-RmSDqhL/yNMiFSDQTTA3OLVCufUGDwFn@public.gmane.org>
> > Date: Mon Jun 8 19:50:45 2009 -0400
> > 
> >     add caching of ACLs in struct inode
> > 
> >     No helpers, no conversions yet.
> > 
> >     Signed-off-by: Al Viro <viro-RmSDqhL/yNMiFSDQTTA3OLVCufUGDwFn@public.gmane.org>
> 
> Weird. If the functions do what their name suggests, i.e. if 
> inode_init_always() is an always called constructor and if 
> destroy_inode() is an unconditional destructor then this patch 
> should have no functional effect on the VFS side.
> 
> It increases the size of struct inode, so if you have some old 
> module (built to an older version of fs.h) still around it might 
> corrupt your inode data structure.
> 
> Or the size change might trigger some dormant bug. It might move a 
> critical inode right into the path of a pre-existing (but not 
> visibly crash-triggering) data corruption.
> 
> The possibilities on the 'weird bug' front are endless - the 
> crash/oops itself should be turned into text, posted here and 
> analyzed.

Btw., before you invest any time into the 'weird crash' theory, i'd 
suggest to double check the bisection result:

  f19d4a8fa6f9b6ccf54df0971c97ffcaa390b7b0    crashes
  f19d4a8fa6f9b6ccf54df0971c97ffcaa390b7b0~1  boots fine

You can save yourself from a lot of head scratching that way - the 
bisection result looks weird. (albeit plausible - a VFS crash points 
to a VFS commit.)

_Maybe_ the bisection is just off a little bit (there was a 
bisection mistake in the last few steps), and the real buggy commit 
is one of the nearby ones:

1cbd20d: switch xfs to generic acl caching helpers
073aaa1: helpers for acl caching + switch to those
06b16e9: switch shmem to inode->i_acl
281eede: switch reiserfs to inode->i_acl
7a77b15: switch reiserfs to usual conventions for caching ACLs
e68888b: reiserfs: minimal fix for ACL caching
d441b1c: switch nilfs2 to inode->i_acl
5affd88: switch btrfs to inode->i_acl
290c263: switch jffs2 to inode->i_acl
05fc079: switch jfs to inode->i_acl
d4bfe2f: switch ext4 to inode->i_acl
6582a0e: switch ext3 to inode->i_acl
5e78b43: switch ext2 to inode->i_acl
f19d4a8: add caching of ACLs in struct inode
3e63cbb: fs: Add new pre-allocation ioctls to vfs for compatibility with legacy xfs ioctls
01c0319: cleanup __writeback_single_inode
f21f622: ... and the same for vfsmount id/mount group id
c63e09e: Make allocation of anon devices cheaper
7e325d3: update Documentation/filesystems/Locking
f6cc746: devpts: remove module-related code
3b22edc: VFS: Switch init_mount_tree() to use the new create_mnt_ns() helper
654f562: vfs: fix nd->root leak in do_filp_open()
b5450d9: reiserfs: remove stray unlock_super in reiserfs_resize
c912e7a: ALSA: hda - Fix support for Samsung P50 with AD1986A codec

	Ingo

Re: [Bug #13941] x86 Geode issue

[Martin-Éric Racine]

2009/8/17 Ingo Molnar <mingo-X9Un+BFzKDI@public.gmane.org>:
>
> * Ingo Molnar <mingo-X9Un+BFzKDI@public.gmane.org> wrote:
>
>>
>> * Martin-Éric Racine <q-funk-X3B1VOXEql0@public.gmane.org> wrote:
>>
>> > On Thu, Aug 13, 2009 at 9:34 PM, Rafael J. Wysocki<rjw-KKrjLPT3xs0@public.gmane.org> wrote:
>> > > On Thursday 13 August 2009, Martin-Éric Racine wrote:
>> > >> On Thu, Aug 13, 2009 at 5:54 PM, Rafael J. Wysocki<rjw-KKrjLPT3xs0@public.gmane.org> wrote:
>> > >> > On Thursday 13 August 2009, Martin-Éric Racine wrote:
>> > >> >> 2009/8/13 Martin-Éric Racine <q-funk-X3B1VOXEql0@public.gmane.org>:
>> > >> >> > On Thu, Aug 13, 2009 at 12:07 PM, Ingo Molnar<mingo@elte.hu> wrote:
>> > >> >> >> * Martin-Éric Racine <q-funk-X3B1VOXEql0@public.gmane.org> wrote:
>> > >> >> >>> Yes, this bug is still valid.
>> > >> >> >>>
>> > >> >> >>> Ubuntu kernel team member Leann Ogasawara and I are slowly
>> > >> >> >>> bisecting our way through the changes that took place since 2.6.30
>> > >> >> >>> to find the commit that introduced this regression. Please stay
>> > >> >> >>> tuned.
>> > >> >> >>
>> > >> >> >> hm, the only outright Geode related commit was:
>> > >> >> >>
>> > >> >> >>  d6c585a: x86: geode: Mark mfgpt irq IRQF_TIMER to prevent resume failure
>> > >> >> >>
>> > >> >> >> the jpg at:
>> > >> >> >>
>> > >> >> >>  http://launchpadlibrarian.net/28892781/00002.jpg
>> > >> >> >>
>> > >> >> >> is very out of focus - but what i could decypher suggests a
>> > >> >> >> pagefault crash in the VFS code, in generic_delete_inode().
>> > >> >>
>> > >> >> This one might be a bit better:
>> > >> >>
>> > >> >> http://launchpadlibrarian.net/30267494/2.6.31-5.24.jpg
>> > >
>> > > Hmm.  This looks like a sysfs oops to my untrained eye.
>> >
>> > The bisect I did with Leann Ogasawara has narrowed the kernel panic
>> > down to the following:
>> >
>> > commit f19d4a8fa6f9b6ccf54df0971c97ffcaa390b7b0
>> > Author: Al Viro <viro-RmSDqhL/yNMiFSDQTTA3OLVCufUGDwFn@public.gmane.org>
>> > Date: Mon Jun 8 19:50:45 2009 -0400
>> >
>> >     add caching of ACLs in struct inode
>> >
>> >     No helpers, no conversions yet.
>> >
>> >     Signed-off-by: Al Viro <viro-RmSDqhL/yNMiFSDQTTA3OLVCufUGDwFn@public.gmane.org>
>>
>> Weird. If the functions do what their name suggests, i.e. if
>> inode_init_always() is an always called constructor and if
>> destroy_inode() is an unconditional destructor then this patch
>> should have no functional effect on the VFS side.
>>
>> It increases the size of struct inode, so if you have some old
>> module (built to an older version of fs.h) still around it might
>> corrupt your inode data structure.
>>
>> Or the size change might trigger some dormant bug. It might move a
>> critical inode right into the path of a pre-existing (but not
>> visibly crash-triggering) data corruption.
>>
>> The possibilities on the 'weird bug' front are endless - the
>> crash/oops itself should be turned into text, posted here and
>> analyzed.
>
> Btw., before you invest any time into the 'weird crash' theory, i'd
> suggest to double check the bisection result:
>
>  f19d4a8fa6f9b6ccf54df0971c97ffcaa390b7b0    crashes
>  f19d4a8fa6f9b6ccf54df0971c97ffcaa390b7b0~1  boots fine
>
> You can save yourself from a lot of head scratching that way - the
> bisection result looks weird. (albeit plausible - a VFS crash points
> to a VFS commit.)
>
> _Maybe_ the bisection is just off a little bit (there was a
> bisection mistake in the last few steps), and the real buggy commit
> is one of the nearby ones:

We double checked again last week with fresh builds and validated that
the above result is correct.

What puzzles us is the start of the crash:


BUG: unable to handle kernel paging request at ffffb4ff
IP: [<c01f716b>] __destroy_inode+0x4b/0x80
*pde = 00810067 *pte = 00000000
Oops: 0000 [#1] SMP
last sysfs file: /sys/power/resume


Any ideas?
Martin-Éric

Re: [Bug #13941] x86 Geode issue

[Martin-Éric Racine]

2009/8/16 Ingo Molnar <mingo-X9Un+BFzKDI@public.gmane.org>:
>
> * Martin-Éric Racine <q-funk-X3B1VOXEql0@public.gmane.org> wrote:
>
>> On Thu, Aug 13, 2009 at 9:34 PM, Rafael J. Wysocki<rjw-KKrjLPT3xs0@public.gmane.org> wrote:
>> > On Thursday 13 August 2009, Martin-Éric Racine wrote:
>> >> On Thu, Aug 13, 2009 at 5:54 PM, Rafael J. Wysocki<rjw-KKrjLPT3xs0@public.gmane.org> wrote:
>> >> > On Thursday 13 August 2009, Martin-Éric Racine wrote:
>> >> >> 2009/8/13 Martin-Éric Racine <q-funk-X3B1VOXEql0@public.gmane.org>:
>> >> >> > On Thu, Aug 13, 2009 at 12:07 PM, Ingo Molnar<mingo-X9Un+BFzKDI@public.gmane.org> wrote:
>> >> >> >> * Martin-Éric Racine <q-funk-X3B1VOXEql0@public.gmane.org> wrote:
>> >> >> >>> Yes, this bug is still valid.
>> >> >> >>>
>> >> >> >>> Ubuntu kernel team member Leann Ogasawara and I are slowly
>> >> >> >>> bisecting our way through the changes that took place since 2.6.30
>> >> >> >>> to find the commit that introduced this regression. Please stay
>> >> >> >>> tuned.
>> >> >> >>
>> >> >> >> hm, the only outright Geode related commit was:
>> >> >> >>
>> >> >> >>  d6c585a: x86: geode: Mark mfgpt irq IRQF_TIMER to prevent resume failure
>> >> >> >>
>> >> >> >> the jpg at:
>> >> >> >>
>> >> >> >>  http://launchpadlibrarian.net/28892781/00002.jpg
>> >> >> >>
>> >> >> >> is very out of focus - but what i could decypher suggests a
>> >> >> >> pagefault crash in the VFS code, in generic_delete_inode().
>> >> >>
>> >> >> This one might be a bit better:
>> >> >>
>> >> >> http://launchpadlibrarian.net/30267494/2.6.31-5.24.jpg
>> >
>> > Hmm.  This looks like a sysfs oops to my untrained eye.
>>
>> The bisect I did with Leann Ogasawara has narrowed the kernel panic
>> down to the following:
>>
>> commit f19d4a8fa6f9b6ccf54df0971c97ffcaa390b7b0
>> Author: Al Viro <viro-RmSDqhL/yNMiFSDQTTA3OLVCufUGDwFn@public.gmane.org>
>> Date: Mon Jun 8 19:50:45 2009 -0400
>>
>>     add caching of ACLs in struct inode
>>
>>     No helpers, no conversions yet.
>>
>>     Signed-off-by: Al Viro <viro-RmSDqhL/yNMiFSDQTTA3OLVCufUGDwFn@public.gmane.org>
>
> Weird. If the functions do what their name suggests, i.e. if
> inode_init_always() is an always called constructor and if
> destroy_inode() is an unconditional destructor then this patch
> should have no functional effect on the VFS side.
>
> It increases the size of struct inode, so if you have some old
> module (built to an older version of fs.h) still around it might
> corrupt your inode data structure.
>
> Or the size change might trigger some dormant bug. It might move a
> critical inode right into the path of a pre-existing (but not
> visibly crash-triggering) data corruption.
>
> The possibilities on the 'weird bug' front are endless - the
> crash/oops itself should be turned into text, posted here and
> analyzed.

If you mean something else than the large-size snapshot of the whole
panic output that was linked earlier in this thread, I'd appreciate
instructions on how to turn that crash into text.

Martin-Éric

Re: [Bug #13941] x86 Geode issue

[Ingo Molnar]

* Martin-Éric Racine <q-funk-X3B1VOXEql0@public.gmane.org> wrote:

> 2009/8/16 Ingo Molnar <mingo-X9Un+BFzKDI@public.gmane.org>:
> >
> > * Martin-Éric Racine <q-funk-X3B1VOXEql0@public.gmane.org> wrote:
> >
> >> On Thu, Aug 13, 2009 at 9:34 PM, Rafael J. Wysocki<rjw-KKrjLPT3xs0@public.gmane.org> wrote:
> >> > On Thursday 13 August 2009, Martin-Éric Racine wrote:
> >> >> On Thu, Aug 13, 2009 at 5:54 PM, Rafael J. Wysocki<rjw-KKrjLPT3xs0@public.gmane.org> wrote:
> >> >> > On Thursday 13 August 2009, Martin-Éric Racine wrote:
> >> >> >> 2009/8/13 Martin-Éric Racine <q-funk-X3B1VOXEql0@public.gmane.org>:
> >> >> >> > On Thu, Aug 13, 2009 at 12:07 PM, Ingo Molnar<mingo@elte.hu> wrote:
> >> >> >> >> * Martin-Éric Racine <q-funk-X3B1VOXEql0@public.gmane.org> wrote:
> >> >> >> >>> Yes, this bug is still valid.
> >> >> >> >>>
> >> >> >> >>> Ubuntu kernel team member Leann Ogasawara and I are slowly
> >> >> >> >>> bisecting our way through the changes that took place since 2.6.30
> >> >> >> >>> to find the commit that introduced this regression. Please stay
> >> >> >> >>> tuned.
> >> >> >> >>
> >> >> >> >> hm, the only outright Geode related commit was:
> >> >> >> >>
> >> >> >> >>  d6c585a: x86: geode: Mark mfgpt irq IRQF_TIMER to prevent resume failure
> >> >> >> >>
> >> >> >> >> the jpg at:
> >> >> >> >>
> >> >> >> >>  http://launchpadlibrarian.net/28892781/00002.jpg
> >> >> >> >>
> >> >> >> >> is very out of focus - but what i could decypher suggests a
> >> >> >> >> pagefault crash in the VFS code, in generic_delete_inode().
> >> >> >>
> >> >> >> This one might be a bit better:
> >> >> >>
> >> >> >> http://launchpadlibrarian.net/30267494/2.6.31-5.24.jpg
> >> >
> >> > Hmm.  This looks like a sysfs oops to my untrained eye.
> >>
> >> The bisect I did with Leann Ogasawara has narrowed the kernel panic
> >> down to the following:
> >>
> >> commit f19d4a8fa6f9b6ccf54df0971c97ffcaa390b7b0
> >> Author: Al Viro <viro-RmSDqhL/yNMiFSDQTTA3OLVCufUGDwFn@public.gmane.org>
> >> Date: Mon Jun 8 19:50:45 2009 -0400
> >>
> >>     add caching of ACLs in struct inode
> >>
> >>     No helpers, no conversions yet.
> >>
> >>     Signed-off-by: Al Viro <viro-RmSDqhL/yNMiFSDQTTA3OLVCufUGDwFn@public.gmane.org>
> >
> > Weird. If the functions do what their name suggests, i.e. if
> > inode_init_always() is an always called constructor and if
> > destroy_inode() is an unconditional destructor then this patch
> > should have no functional effect on the VFS side.
> >
> > It increases the size of struct inode, so if you have some old
> > module (built to an older version of fs.h) still around it might
> > corrupt your inode data structure.
> >
> > Or the size change might trigger some dormant bug. It might move a
> > critical inode right into the path of a pre-existing (but not
> > visibly crash-triggering) data corruption.
> >
> > The possibilities on the 'weird bug' front are endless - the 
> > crash/oops itself should be turned into text, posted here and 
> > analyzed.
> 
> If you mean something else than the large-size snapshot of the 
> whole panic output that was linked earlier in this thread, I'd 
> appreciate instructions on how to turn that crash into text.

it's still a JPG - posting the transcribed oops in email text would 
certainly help more folks looking over it.

(painful i know ...)

	Ingo

Re: [Bug #13941] x86 Geode issue

[Martin-Éric Racine]

2009/8/17 Ingo Molnar <mingo-X9Un+BFzKDI@public.gmane.org>:
>
> * Martin-Éric Racine <q-funk-X3B1VOXEql0@public.gmane.org> wrote:
>
>> 2009/8/16 Ingo Molnar <mingo-X9Un+BFzKDI@public.gmane.org>:
>> >
>> > * Martin-Éric Racine <q-funk-X3B1VOXEql0@public.gmane.org> wrote:
>> >
>> >> On Thu, Aug 13, 2009 at 9:34 PM, Rafael J. Wysocki<rjw-KKrjLPT3xs0@public.gmane.org> wrote:
>> >> > On Thursday 13 August 2009, Martin-Éric Racine wrote:
>> >> >> On Thu, Aug 13, 2009 at 5:54 PM, Rafael J. Wysocki<rjw-KKrjLPT3xs0@public.gmane.org> wrote:
>> >> >> > On Thursday 13 August 2009, Martin-Éric Racine wrote:
>> >> >> >> 2009/8/13 Martin-Éric Racine <q-funk-X3B1VOXEql0@public.gmane.org>:
>> >> >> >> > On Thu, Aug 13, 2009 at 12:07 PM, Ingo Molnar<mingo@elte.hu> wrote:
>> >> >> >> >> * Martin-Éric Racine <q-funk-X3B1VOXEql0@public.gmane.org> wrote:
>> >> >> >> >>> Yes, this bug is still valid.
>> >> >> >> >>>
>> >> >> >> >>> Ubuntu kernel team member Leann Ogasawara and I are slowly
>> >> >> >> >>> bisecting our way through the changes that took place since 2.6.30
>> >> >> >> >>> to find the commit that introduced this regression. Please stay
>> >> >> >> >>> tuned.
>> >> >> >> >>
>> >> >> >> >> hm, the only outright Geode related commit was:
>> >> >> >> >>
>> >> >> >> >>  d6c585a: x86: geode: Mark mfgpt irq IRQF_TIMER to prevent resume failure
>> >> >> >> >>
>> >> >> >> >> the jpg at:
>> >> >> >> >>
>> >> >> >> >>  http://launchpadlibrarian.net/28892781/00002.jpg
>> >> >> >> >>
>> >> >> >> >> is very out of focus - but what i could decypher suggests a
>> >> >> >> >> pagefault crash in the VFS code, in generic_delete_inode().
>> >> >> >>
>> >> >> >> This one might be a bit better:
>> >> >> >>
>> >> >> >> http://launchpadlibrarian.net/30267494/2.6.31-5.24.jpg
>> >> >
>> >> > Hmm.  This looks like a sysfs oops to my untrained eye.
>> >>
>> >> The bisect I did with Leann Ogasawara has narrowed the kernel panic
>> >> down to the following:
>> >>
>> >> commit f19d4a8fa6f9b6ccf54df0971c97ffcaa390b7b0
>> >> Author: Al Viro <viro-RmSDqhL/yNMiFSDQTTA3OLVCufUGDwFn@public.gmane.org>
>> >> Date: Mon Jun 8 19:50:45 2009 -0400
>> >>
>> >>     add caching of ACLs in struct inode
>> >>
>> >>     No helpers, no conversions yet.
>> >>
>> >>     Signed-off-by: Al Viro <viro-RmSDqhL/yNMiFSDQTTA3OLVCufUGDwFn@public.gmane.org>
>> >
>> > Weird. If the functions do what their name suggests, i.e. if
>> > inode_init_always() is an always called constructor and if
>> > destroy_inode() is an unconditional destructor then this patch
>> > should have no functional effect on the VFS side.
>> >
>> > It increases the size of struct inode, so if you have some old
>> > module (built to an older version of fs.h) still around it might
>> > corrupt your inode data structure.
>> >
>> > Or the size change might trigger some dormant bug. It might move a
>> > critical inode right into the path of a pre-existing (but not
>> > visibly crash-triggering) data corruption.
>> >
>> > The possibilities on the 'weird bug' front are endless - the
>> > crash/oops itself should be turned into text, posted here and
>> > analyzed.
>>
>> If you mean something else than the large-size snapshot of the
>> whole panic output that was linked earlier in this thread, I'd
>> appreciate instructions on how to turn that crash into text.
>
> it's still a JPG - posting the transcribed oops in email text would
> certainly help more folks looking over it.
>
> (painful i know ...)

I welcome suggestions for proper OCR software that can extract the
text displayed therein. Manually transcribing it is too error-prone to
even try.

Martin-Éric

Re: [Bug #13941] x86 Geode issue

[Willy Tarreau]

On Tue, Aug 18, 2009 at 12:02:34AM +0300, Martin-Éric Racine wrote:
(...)
> > it's still a JPG - posting the transcribed oops in email text would
> > certainly help more folks looking over it.
> >
> > (painful i know ...)
> 
> I welcome suggestions for proper OCR software that can extract the
> text displayed therein. Manually transcribing it is too error-prone to
> even try.

Well, there are less risks of errors retyping by hand than passing via
an OCR. At least *you* know that everything you see are hex numbers, the
OCR does not. Eventhough it's quite annoying to do that by hand, it
generally takes less than 5 minutes to retype an oops, which is not that
much. Of course, the serial cable to another machine to get a panic dump
is the easiest solution ;-)

Willy

Re: [Bug #13941] x86 Geode issue

[Martin-Éric Racine]

2009/8/18 Willy Tarreau <w@1wt.eu>:
> On Tue, Aug 18, 2009 at 12:02:34AM +0300, Martin-Éric Racine wrote:
> (...)
>> > it's still a JPG - posting the transcribed oops in email text would
>> > certainly help more folks looking over it.
>> >
>> > (painful i know ...)
>>
>> I welcome suggestions for proper OCR software that can extract the
>> text displayed therein. Manually transcribing it is too error-prone to
>> even try.
>
> Well, there are less risks of errors retyping by hand than passing via
> an OCR. At least *you* know that everything you see are hex numbers, the
> OCR does not. Eventhough it's quite annoying to do that by hand, it
> generally takes less than 5 minutes to retype an oops, which is not that
> much. Of course, the serial cable to another machine to get a panic dump
> is the easiest solution ;-)

That would be assuming that a serial console is available.  This is
not the case here. No legacy port whatsoever.

Martin-Éric

[Bug #13935] 2.6.31-rcX breaks Apple MightyMouse (Bluetooth version)

[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.30.  Please verify if it still should be listed and let me know
(either way).


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13935
Subject		: 2.6.31-rcX breaks Apple MightyMouse (Bluetooth version)
Submitter	: Adrian Ulrich <kernel-4ZM2p5qjiQGewZBzVTKGGg@public.gmane.org>
Date		: 2009-08-08 22:08 (2 days old)
First-Bad-Commit: http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=fa047e4f6fa63a6e9d0ae4d7749538830d14a343

Re: [Bug #13935] 2.6.31-rcX breaks Apple MightyMouse (Bluetooth version)

[Jan Scholz]

Hi,

I can confirm the reported bug, but for me reverting fa047e4f6fa63a6 is
not sufficient. I have to remove the device id of the mighty mouse from
the hid_blacklist list in drivers/hid/hid-core.c as well, see the patch below.

Concerning the need for the quirks: I think there might be some
dependence on the version of X that is used. If I recall correctly, with
xorg-server-1.3 the quirk "APPLE_INVERT_HWHEEL" was necessary, but this
changed when I switched to xorg-server-1.5.3, where now horizontal
scrolling moves in directions you'd expect from vertical scrolling.
...but I wouldn't bet on my memory regarding things with xorg-server-1.3
since it's been quite some time ago and I never really liked the
horizontal scrolling anyway.

Cheers,
Jan

"Rafael J. Wysocki" <rjw-KKrjLPT3xs0@public.gmane.org> writes:

> 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.30.  Please verify if it still should be listed and let me know
> (either way).
>
>
> Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13935
> Subject		: 2.6.31-rcX breaks Apple MightyMouse (Bluetooth version)
> Submitter	: Adrian Ulrich <kernel-4ZM2p5qjiQGewZBzVTKGGg@public.gmane.org>
> Date		: 2009-08-08 22:08 (2 days old)
> First-Bad-Commit: http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=fa047e4f6fa63a6e9d0ae4d7749538830d14a343
>

From b7393ed6dfe00c9e126a2dd34659156548df15cc Mon Sep 17 00:00:00 2001
From: Jan Scholz <Scholz-wOpdxP1gw6Cc+IqHO83+wjjhTm2NLCe8@public.gmane.org>
Date: Tue, 11 Aug 2009 14:33:27 +0200
Subject: [PATCH] HID: commit fa047e4f is incomplete

Commit fa047e4f6fa63a6e9d0ae4d7749538830d14a343 "HID: fix inverted
wheel for bluetooth version of apple mighty mouse" is incomplete. If
we remove Apple MightyMouse (bluetooth version) from the list of
apple_devices in drivers/hid/hid-apple.c we have to remove it from
hid_blacklist in drivers/hid/hid-core.c as well.

Signed-off-by: Jan Scholz <Scholz-wOpdxP1gw6Cc+IqHO83+wjjhTm2NLCe8@public.gmane.org>
---
 drivers/hid/hid-core.c |    1 -
 1 files changed, 0 insertions(+), 1 deletions(-)

diff --git a/drivers/hid/hid-core.c b/drivers/hid/hid-core.c
index 5eb10c2..047844d 100644
--- a/drivers/hid/hid-core.c
+++ b/drivers/hid/hid-core.c
@@ -1319,7 +1319,6 @@ static const struct hid_device_id hid_blacklist[] = {
 	{ HID_USB_DEVICE(USB_VENDOR_ID_ZEROPLUS, 0x0005) },
 	{ HID_USB_DEVICE(USB_VENDOR_ID_ZEROPLUS, 0x0030) },
 
-	{ HID_BLUETOOTH_DEVICE(USB_VENDOR_ID_APPLE, 0x030c) },
 	{ HID_BLUETOOTH_DEVICE(USB_VENDOR_ID_MICROSOFT, USB_DEVICE_ID_MS_PRESENTER_8K_BT) },
 	{ }
 };
-- 
1.6.3.3

Re: [Bug #13935] 2.6.31-rcX breaks Apple MightyMouse (Bluetooth version)

[Rafael J. Wysocki]

On Tuesday 11 August 2009, Jan Scholz wrote:
> Hi,
> 
> I can confirm the reported bug, but for me reverting fa047e4f6fa63a6 is
> not sufficient. I have to remove the device id of the mighty mouse from
> the hid_blacklist list in drivers/hid/hid-core.c as well, see the patch below.
> 
> Concerning the need for the quirks: I think there might be some
> dependence on the version of X that is used. If I recall correctly, with
> xorg-server-1.3 the quirk "APPLE_INVERT_HWHEEL" was necessary, but this
> changed when I switched to xorg-server-1.5.3, where now horizontal
> scrolling moves in directions you'd expect from vertical scrolling.
> ...but I wouldn't bet on my memory regarding things with xorg-server-1.3
> since it's been quite some time ago and I never really liked the
> horizontal scrolling anyway.

Thanks for the information.

Best,
Rafael


> "Rafael J. Wysocki" <rjw-KKrjLPT3xs0@public.gmane.org> writes:
> 
> > 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.30.  Please verify if it still should be listed and let me know
> > (either way).
> >
> >
> > Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13935
> > Subject		: 2.6.31-rcX breaks Apple MightyMouse (Bluetooth version)
> > Submitter	: Adrian Ulrich <kernel-4ZM2p5qjiQGewZBzVTKGGg@public.gmane.org>
> > Date		: 2009-08-08 22:08 (2 days old)
> > First-Bad-Commit: http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=fa047e4f6fa63a6e9d0ae4d7749538830d14a343
> >
> 
> From b7393ed6dfe00c9e126a2dd34659156548df15cc Mon Sep 17 00:00:00 2001
> From: Jan Scholz <Scholz-wOpdxP1gw6Cc+IqHO83+wjjhTm2NLCe8@public.gmane.org>
> Date: Tue, 11 Aug 2009 14:33:27 +0200
> Subject: [PATCH] HID: commit fa047e4f is incomplete
> 
> Commit fa047e4f6fa63a6e9d0ae4d7749538830d14a343 "HID: fix inverted
> wheel for bluetooth version of apple mighty mouse" is incomplete. If
> we remove Apple MightyMouse (bluetooth version) from the list of
> apple_devices in drivers/hid/hid-apple.c we have to remove it from
> hid_blacklist in drivers/hid/hid-core.c as well.
> 
> Signed-off-by: Jan Scholz <Scholz-wOpdxP1gw6Cc+IqHO83+wjjhTm2NLCe8@public.gmane.org>
> ---
>  drivers/hid/hid-core.c |    1 -
>  1 files changed, 0 insertions(+), 1 deletions(-)
> 
> diff --git a/drivers/hid/hid-core.c b/drivers/hid/hid-core.c
> index 5eb10c2..047844d 100644
> --- a/drivers/hid/hid-core.c
> +++ b/drivers/hid/hid-core.c
> @@ -1319,7 +1319,6 @@ static const struct hid_device_id hid_blacklist[] = {
>  	{ HID_USB_DEVICE(USB_VENDOR_ID_ZEROPLUS, 0x0005) },
>  	{ HID_USB_DEVICE(USB_VENDOR_ID_ZEROPLUS, 0x0030) },
>  
> -	{ HID_BLUETOOTH_DEVICE(USB_VENDOR_ID_APPLE, 0x030c) },
>  	{ HID_BLUETOOTH_DEVICE(USB_VENDOR_ID_MICROSOFT, USB_DEVICE_ID_MS_PRESENTER_8K_BT) },
>  	{ }
>  };

Re: [Bug #13935] 2.6.31-rcX breaks Apple MightyMouse (Bluetooth version)

[Jan Scholz]

Hi,

now that the patch "HID: completely remove apple mightymouse from
blacklist" is merged upstream as
"42960a13001aa6df52ca9952ce996f94a744ea65" I think it should be merged
in the v2.6.31-stable series as well.

Best regards,
   Jan

Jan Scholz <scholz-wOpdxP1gw6Cc+IqHO83+wjjhTm2NLCe8@public.gmane.org> writes:

> I can confirm the reported bug, but for me reverting fa047e4f6fa63a6 is
> not sufficient. I have to remove the device id of the mighty mouse from
> the hid_blacklist list in drivers/hid/hid-core.c as well, see the patch below.
>
> "Rafael J. Wysocki" <rjw-KKrjLPT3xs0@public.gmane.org> writes:
>
>> 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.30.  Please verify if it still should be listed and let me know
>> (either way).
>>
>>
>> Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13935
>> Subject		: 2.6.31-rcX breaks Apple MightyMouse (Bluetooth version)
>> Submitter	: Adrian Ulrich <kernel-4ZM2p5qjiQGewZBzVTKGGg@public.gmane.org>
>> Date		: 2009-08-08 22:08 (2 days old)
>> First-Bad-Commit: http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=fa047e4f6fa63a6e9d0ae4d7749538830d14a343
>>
>
> From b7393ed6dfe00c9e126a2dd34659156548df15cc Mon Sep 17 00:00:00 2001
> From: Jan Scholz <Scholz-wOpdxP1gw6Cc+IqHO83+wjjhTm2NLCe8@public.gmane.org>
> Date: Tue, 11 Aug 2009 14:33:27 +0200
> Subject: [PATCH] HID: commit fa047e4f is incomplete
>
> Commit fa047e4f6fa63a6e9d0ae4d7749538830d14a343 "HID: fix inverted
> wheel for bluetooth version of apple mighty mouse" is incomplete. If
> we remove Apple MightyMouse (bluetooth version) from the list of
> apple_devices in drivers/hid/hid-apple.c we have to remove it from
> hid_blacklist in drivers/hid/hid-core.c as well.
>
> Signed-off-by: Jan Scholz <Scholz-wOpdxP1gw6Cc+IqHO83+wjjhTm2NLCe8@public.gmane.org>
> ---
>  drivers/hid/hid-core.c |    1 -
>  1 files changed, 0 insertions(+), 1 deletions(-)
>
> diff --git a/drivers/hid/hid-core.c b/drivers/hid/hid-core.c
> index 5eb10c2..047844d 100644
> --- a/drivers/hid/hid-core.c
> +++ b/drivers/hid/hid-core.c
> @@ -1319,7 +1319,6 @@ static const struct hid_device_id hid_blacklist[] = {
>  	{ HID_USB_DEVICE(USB_VENDOR_ID_ZEROPLUS, 0x0005) },
>  	{ HID_USB_DEVICE(USB_VENDOR_ID_ZEROPLUS, 0x0030) },
>  
> -	{ HID_BLUETOOTH_DEVICE(USB_VENDOR_ID_APPLE, 0x030c) },
>  	{ HID_BLUETOOTH_DEVICE(USB_VENDOR_ID_MICROSOFT, USB_DEVICE_ID_MS_PRESENTER_8K_BT) },
>  	{ }
>  };

Re: [Bug #13935] 2.6.31-rcX breaks Apple MightyMouse (Bluetooth version)

[Jiri Kosina]

On Wed, 30 Sep 2009, Jan Scholz wrote:

> now that the patch "HID: completely remove apple mightymouse from
> blacklist" is merged upstream as
> "42960a13001aa6df52ca9952ce996f94a744ea65" I think it should be merged
> in the v2.6.31-stable series as well.

Agreed. As it didn't have "Cc: stable@kernel.org" in the changelog, it 
will not be picked up automagically. 

Will do.

-- 
Jiri Kosina
SUSE Labs, Novell Inc.

[Bug #13940] iwlagn and sky2 stopped working, ACPI-related

[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.30.  Please verify if it still should be listed and let me know
(either way).


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13940
Subject		: iwlagn and sky2 stopped working, ACPI-related
Submitter	: Ricardo Jorge da Fonseca Marques Ferreira <storm@sys49152.net>
Date		: 2009-08-07 22:33 (3 days old)
References	: http://marc.info/?l=linux-kernel&m=124968457731107&w=4

[Bug #13946] x86 MCE malfunction on Thinkpad T42p

[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.30.  Please verify if it still should be listed and let me know
(either way).


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13946
Subject		: x86 MCE malfunction on Thinkpad T42p
Submitter	: Johannes Stezenbach <js@sig21.net>
Date		: 2009-08-07 17:09 (3 days old)
References	: http://marc.info/?l=linux-kernel&m=124966500232399&w=4
Handled-By	: Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>
Patch		: http://patchwork.kernel.org/patch/37908/

[Bug #13942] Troubles with AoE and uninitialized object

[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.30.  Please verify if it still should be listed and let me know
(either way).


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13942
Subject		: Troubles with AoE and uninitialized object
Submitter	: Bruno Prémont <bonbons@linux-vserver.org>
Date		: 2009-08-04 10:12 (6 days old)
References	: http://marc.info/?l=linux-kernel&m=124938117104811&w=4

[Bug #13944] MD raid regression

[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.30.  Please verify if it still should be listed and let me know
(either way).


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13944
Subject		: MD raid regression
Submitter	: Mike Snitzer <snitzer@redhat.com>
Date		: 2009-08-05 15:06 (5 days old)
First-Bad-Commit: http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=449aad3e25358812c43afc60918c5ad3819488e7
References	: http://marc.info/?l=linux-kernel&m=124948481218857&w=4
Handled-By	: NeilBrown <neilb@suse.de>
Patch		: http://patchwork.kernel.org/patch/39521/

Re: [Bug #13944] MD raid regression

[Neil Brown]

On Sunday August 9, rjw@sisk.pl wrote:
> This message has been generated automatically as a part of a report
> of recent regressions.
> 
> The following bug entry is on the current list of known regressions
> from 2.6.30.  Please verify if it still should be listed and let me know
> (either way).

Yes, it still should be listed.  The first patch didn't quite fix it.
A second one probably does.

Thanks.
NeilBrown

> 
> 
> Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13944
> Subject		: MD raid regression
> Submitter	: Mike Snitzer <snitzer@redhat.com>
> Date		: 2009-08-05 15:06 (5 days old)
> First-Bad-Commit: http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=449aad3e25358812c43afc60918c5ad3819488e7
> References	: http://marc.info/?l=linux-kernel&m=124948481218857&w=4
> Handled-By	: NeilBrown <neilb@suse.de>
> Patch		: http://patchwork.kernel.org/patch/39521/
> 
> 
> --
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/

Re: [Bug #13944] MD raid regression

[Rafael J. Wysocki]

On Monday 10 August 2009, Neil Brown wrote:
> On Sunday August 9, rjw-KKrjLPT3xs0@public.gmane.org wrote:
> > This message has been generated automatically as a part of a report
> > of recent regressions.
> > 
> > The following bug entry is on the current list of known regressions
> > from 2.6.30.  Please verify if it still should be listed and let me know
> > (either way).
> 
> Yes, it still should be listed.  The first patch didn't quite fix it.
> A second one probably does.

Thanks for the update.

Is the patch listed below the right one?

> > Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13944
> > Subject		: MD raid regression
> > Submitter	: Mike Snitzer <snitzer-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
> > Date		: 2009-08-05 15:06 (5 days old)
> > Handled-By	: NeilBrown <neilb-l3A5Bk7waGM@public.gmane.org>
> > Patch		: http://patchwork.kernel.org/patch/39521/

Rafael

Re: [Bug #13944] MD raid regression

[Mike Snitzer]

On Mon, Aug 10 2009 at 10:11am -0400,
Rafael J. Wysocki <rjw-KKrjLPT3xs0@public.gmane.org> wrote:

> On Monday 10 August 2009, Neil Brown wrote:
> > On Sunday August 9, rjw-KKrjLPT3xs0@public.gmane.org wrote:
> > > This message has been generated automatically as a part of a report
> > > of recent regressions.
> > > 
> > > The following bug entry is on the current list of known regressions
> > > from 2.6.30.  Please verify if it still should be listed and let me know
> > > (either way).
> > 
> > Yes, it still should be listed.  The first patch didn't quite fix it.
> > A second one probably does.
> 
> Thanks for the update.
> 
> Is the patch listed below the right one?
> 
> > > Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13944
> > > Subject		: MD raid regression
> > > Submitter	: Mike Snitzer <snitzer-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
> > > Date		: 2009-08-05 15:06 (5 days old)
> > > Handled-By	: NeilBrown <neilb-l3A5Bk7waGM@public.gmane.org>
> > > Patch		: http://patchwork.kernel.org/patch/39521/

The updated patch is here:
http://patchwork.kernel.org/patch/40328/

I haven't yet tested it but will do so shortly.

Mike

Re: [Bug #13944] MD raid regression

[Rafael J. Wysocki]

On Monday 10 August 2009, Mike Snitzer wrote:
> On Mon, Aug 10 2009 at 10:11am -0400,
> Rafael J. Wysocki <rjw-KKrjLPT3xs0@public.gmane.org> wrote:
> 
> > On Monday 10 August 2009, Neil Brown wrote:
> > > On Sunday August 9, rjw-KKrjLPT3xs0@public.gmane.org wrote:
> > > > This message has been generated automatically as a part of a report
> > > > of recent regressions.
> > > > 
> > > > The following bug entry is on the current list of known regressions
> > > > from 2.6.30.  Please verify if it still should be listed and let me know
> > > > (either way).
> > > 
> > > Yes, it still should be listed.  The first patch didn't quite fix it.
> > > A second one probably does.
> > 
> > Thanks for the update.
> > 
> > Is the patch listed below the right one?
> > 
> > > > Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13944
> > > > Subject		: MD raid regression
> > > > Submitter	: Mike Snitzer <snitzer-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
> > > > Date		: 2009-08-05 15:06 (5 days old)
> > > > Handled-By	: NeilBrown <neilb-l3A5Bk7waGM@public.gmane.org>
> > > > Patch		: http://patchwork.kernel.org/patch/39521/
> 
> The updated patch is here:
> http://patchwork.kernel.org/patch/40328/

Thanks, bug entry updated.

Rafael

[Bug #13943] WARNING: at net/mac80211/mlme.c:2292 with ath5k

[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.30.  Please verify if it still should be listed and let me know
(either way).


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13943
Subject		: WARNING: at net/mac80211/mlme.c:2292 with ath5k
Submitter	: Fabio Comolli <fabio.comolli-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Date		: 2009-08-06 20:15 (4 days old)
References	: http://marc.info/?l=linux-kernel&m=124958978600600&w=4

Re: [Bug #13943] WARNING: at net/mac80211/mlme.c:2292 with ath5k

[Fabio Comolli]

It happened only once so it's hard to tell. I'm going to test -rc6
when it comes out and report back.

Regards,
Fabio



On Sun, Aug 9, 2009 at 11:10 PM, Rafael J. Wysocki<rjw-KKrjLPT3xs0@public.gmane.org> wrote:
> This message has been generated automatically as a part of a report
> of recent regressions.
>
> The following bug entry is on the current list of known regressions
> from 2.6.30.  Please verify if it still should be listed and let me know
> (either way).
>
>
> Bug-Entry       : http://bugzilla.kernel.org/show_bug.cgi?id=13943
> Subject         : WARNING: at net/mac80211/mlme.c:2292 with ath5k
> Submitter       : Fabio Comolli <fabio.comolli@gmail.com>
> Date            : 2009-08-06 20:15 (4 days old)
> References      : http://marc.info/?l=linux-kernel&m=124958978600600&w=4
>
>
>

Re: [Bug #13943] WARNING: at net/mac80211/mlme.c:2292 with ath5k

[Rafael J. Wysocki]

On Monday 10 August 2009, Fabio Comolli wrote:
> It happened only once so it's hard to tell. I'm going to test -rc6
> when it comes out and report back.

OK, thanks for the update.

Rafael

[Bug #13948] ath5k broken after suspend-to-ram

[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.30.  Please verify if it still should be listed and let me know
(either way).


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13948
Subject		: ath5k broken after suspend-to-ram
Submitter	: Johannes Stezenbach <js@sig21.net>
Date		: 2009-08-07 21:51 (3 days old)
References	: http://marc.info/?l=linux-kernel&m=124968192727854&w=4
Handled-By	: Nick Kossifidis <mickflemm@gmail.com>
Patch		: http://patchwork.kernel.org/patch/38550/

[Bug #13950] Oops when USB Serial disconnected while in use

[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.30.  Please verify if it still should be listed and let me know
(either way).


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13950
Subject		: Oops when USB Serial disconnected while in use
Submitter	: Bruno Prémont <bonbons-ud5FBsm0p/xEiooADzr8i9i2O/JbrIOy@public.gmane.org>
Date		: 2009-08-08 17:47 (2 days old)
References	: http://marc.info/?l=linux-kernel&m=124975432900466&w=4

[Bug #13947] Libertas: Association request to the driver failed

[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.30.  Please verify if it still should be listed and let me know
(either way).


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13947
Subject		: Libertas: Association request to the driver failed
Submitter	: Daniel Mack <daniel-rDUAYElUppE@public.gmane.org>
Date		: 2009-08-07 19:11 (3 days old)
First-Bad-Commit: http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=57921c312e8cef72ba35a4cfe870b376da0b1b87
References	: http://marc.info/?l=linux-kernel&m=124967234311481&w=4
Handled-By	: Roel Kluin <roel.kluin-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>

Re: 2.6.31-rc5-git5: Reported regressions from 2.6.30

[James Bottomley]

On Sun, 2009-08-09 at 22:36 +0200, Rafael J. Wysocki wrote:
> Bug-Entry       : http://bugzilla.kernel.org/show_bug.cgi?id=13716
> Subject         : The AIC-7892P controller does not work any more
> Submitter       : Andrej Podzimek <andrej@podzimek.org>
> Date            : 2009-07-05 19:23 (36 days old)

This one sounds like an IRQ routing error, so probably ACPI, but we've
been totally unsuccessful at getting any further information out of the
submitter.  Use your own time judgement on this, but if he hasn't been
responding to you either for 36 days, I'd suggest closing this as
unresponsive.

James

Re: 2.6.31-rc5-git5: Reported regressions from 2.6.30

[Rafael J. Wysocki]

On Monday 10 August 2009, James Bottomley wrote:
> On Sun, 2009-08-09 at 22:36 +0200, Rafael J. Wysocki wrote:
> > Bug-Entry       : http://bugzilla.kernel.org/show_bug.cgi?id=13716
> > Subject         : The AIC-7892P controller does not work any more
> > Submitter       : Andrej Podzimek <andrej-+Hii8LNHG6Ng9hUCZPvPmw@public.gmane.org>
> > Date            : 2009-07-05 19:23 (36 days old)
> 
> This one sounds like an IRQ routing error, so probably ACPI, but we've
> been totally unsuccessful at getting any further information out of the
> submitter.  Use your own time judgement on this, but if he hasn't been
> responding to you either for 36 days, I'd suggest closing this as
> unresponsive.

Thanks, I've closed it.

Best,
Rafael