[Bug #13941] x86 Geode issue

[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/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

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

Re: [Bug #13941] x86 Geode issue

[Martin-Éric Racine]

Yes, it's still valid.

Screenshots of the crash have been provided. Is anything else missing
for the LKML to be able to debug and fix this?

On Wed, Aug 19, 2009 at 11:26 PM, Rafael J. Wysocki<rjw@sisk.pl> wrote:
> This message has been generated automatically as a part of a report
> of recent regressions.
>
> The following bug entry is on the current list of known regressions
> from 2.6.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 (17 days old)
> References      : http://marc.info/?l=linux-kernel&m=124930434732481&w=4
>
>
>

Re: [Bug #13941] x86 Geode issue

[Rafael J. Wysocki]

On Thursday 20 August 2009, Martin-Éric Racine wrote:
> Yes, it's still valid.

Thanks for the update.

> Screenshots of the crash have been provided. Is anything else missing
> for the LKML to be able to debug and fix this?

An idea of what can be wrong?

> On Wed, Aug 19, 2009 at 11:26 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=13941
> > Subject         : x86 Geode issue
> > Submitter       : Martin-Éric Racine <q-funk-X3B1VOXEql0@public.gmane.org>
> > Date            : 2009-08-03 12:58 (17 days old)
> > References      : http://marc.info/?l=linux-kernel&m=124930434732481&w=4

Rafael

Re: [Bug #13941] x86 Geode issue

[Cyrill Gorcunov]

[Rafael J. Wysocki - Thu, Aug 20, 2009 at 05:04:06PM +0200]
| On Thursday 20 August 2009, Martin-Éric Racine wrote:
| > Yes, it's still valid.
| 
| Thanks for the update.
| 
| > Screenshots of the crash have been provided. Is anything else missing
| > for the LKML to be able to debug and fix this?
| 
| An idea of what can be wrong?
| 
| > On Wed, Aug 19, 2009 at 11:26 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=13941
| > > Subject         : x86 Geode issue
| > > Submitter       : Martin-Éric Racine <q-funk-X3B1VOXEql0@public.gmane.org>
| > > Date            : 2009-08-03 12:58 (17 days old)
| > > References      : http://marc.info/?l=linux-kernel&m=124930434732481&w=4
| 
| Rafael
| 

Hi,

may I post a thought?

It seems strange to me that alloc_inode may set 

#ifdef CONFIG_FS_POSIX_ACL
	inode->i_acl = inode->i_default_acl = ACL_NOT_CACHED;
#endif

[where ACL_NOT_CACHED is #define ACL_NOT_CACHED ((void *)(-1))]

meanwhile say jffs2_init_acl_post use ACL_NOT_CACHED
as a valid value and trying to parse it.

But perhaps, I miss something.

	-- Cyrill

Re: [Bug #13941] x86 Geode issue

[Cyrill Gorcunov]

[Cyrill Gorcunov - Thu, Aug 20, 2009 at 10:36:35PM +0400]
...
| | > > 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 (17 days old)
| | > > References      : http://marc.info/?l=linux-kernel&m=124930434732481&w=4
| | 
| | Rafael
| | 
| 
| Hi,
| 
| may I post a thought?
| 
| It seems strange to me that alloc_inode may set 
| 
| #ifdef CONFIG_FS_POSIX_ACL
| 	inode->i_acl = inode->i_default_acl = ACL_NOT_CACHED;
| #endif
| 
| [where ACL_NOT_CACHED is #define ACL_NOT_CACHED ((void *)(-1))]
| 
| meanwhile say jffs2_init_acl_post use ACL_NOT_CACHED
| as a valid value and trying to parse it.
| 
| But perhaps, I miss something.
| 
| 	-- Cyrill

Sorry, this is unrelated and wrong. Drop this message.

	-- Cyrill

[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@iki.fi>
Date		: 2009-08-03 12:58 (23 days old)
References	: http://marc.info/?l=linux-kernel&m=124930434732481&w=4

Re: [Bug #13941] x86 Geode issue

[Martin-Éric Racine]

Yes, it still is valid.

Screen dumps of the kernel panic were provided.  Can we get anyone to
investigate them now and find a fix? Thanks!

On Tue, Aug 25, 2009 at 11:34 PM, Rafael J. Wysocki<rjw@sisk.pl> wrote:
> This message has been generated automatically as a part of a report
> of recent regressions.
>
> The following bug entry is on the current list of known regressions
> from 2.6.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 (23 days old)
> References      : http://marc.info/?l=linux-kernel&m=124930434732481&w=4
>
>
>

Re: [Bug #13941] x86 Geode issue

[Rafael J. Wysocki]

On Wednesday 26 August 2009, Martin-Éric Racine wrote:
> Yes, it still is valid.

Thanks for the update.

Rafael

 
> On Tue, Aug 25, 2009 at 11:34 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=13941
> > Subject         : x86 Geode issue
> > Submitter       : Martin-Éric Racine <q-funk-X3B1VOXEql0@public.gmane.org>
> > Date            : 2009-08-03 12:58 (23 days old)
> > References      : http://marc.info/?l=linux-kernel&m=124930434732481&w=4

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

Re: [Bug #13941] x86 Geode issue

[Martin-Éric Racine]

Yes, it should still be listed, for as long as it hasn't been resolved.

On Sun, Sep 6, 2009 at 8:24 PM, Rafael J. Wysocki<rjw@sisk.pl> wrote:
> This message has been generated automatically as a part of a report
> of recent regressions.
>
> The following bug entry is on the current list of known regressions
> from 2.6.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 (35 days old)
> References      : http://marc.info/?l=linux-kernel&m=124930434732481&w=4
>
>
>

Re: [Bug #13941] x86 Geode issue

[Rafael J. Wysocki]

On Sunday 06 September 2009, Martin-Éric Racine wrote:
> Yes, it should still be listed, for as long as it hasn't been resolved.

Thanks for the update.

Rafael

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

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

[Bug #13941] x86 Geode issue

[Rafael J. Wysocki]

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

The following bug entry is on the current list of known regressions
introduced between 2.6.30 and 2.6.31.  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 (60 days old)
References	: http://marc.info/?l=linux-kernel&m=124930434732481&w=4

[Bug #13941] x86 Geode issue

[Rafael J. Wysocki]

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

The following bug entry is on the current list of known regressions
introduced between 2.6.30 and 2.6.31.  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 (70 days old)
References	: http://marc.info/?l=linux-kernel&m=124930434732481&w=4

2.6.32-rc5-git3: Reported regressions 2.6.30 -> 2.6.31

[Rafael J. Wysocki]

This message contains a list of some regressions introduced between 2.6.30 and
2.6.31, 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.30
and 2.6.31, 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-10-26      170       37          32
  2009-10-12      161       45          35
  2009-10-02      151       49          42
  2009-09-06      123       34          27
  2009-08-26      108       33          26
  2009-08-20      102       32          29
  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=14476
Subject		: Unable to handle kernel paging request in nfs_write_mapping
Submitter	: Stephan von Krawczynski <skraw@ithnet.com>
Date		: 2009-10-14 9:53 (13 days old)
References	: http://marc.info/?l=linux-kernel&m=125551421405656&w=4
Handled-By	: Trond Myklebust <Trond.Myklebust@netapp.com>


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=14474
Subject		: restorecond going crazy on 2.6.31.4 - inotify regression?
Submitter	: Robert Hancock <hancockrwd@gmail.com>
Date		: 2009-10-16 0:03 (11 days old)
References	: http://marc.info/?l=linux-kernel&m=125565159520489&w=4


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=14446
Subject		: battery status info broken/useless in 2.6.32-rc3 - MSI PR200 (possibly others, too)
Submitter	: Eddy Petrișor <eddy.petrisor+linbug@gmail.com>
Date		: 2009-10-20 08:25 (7 days old)


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=14417
Subject		: [Regression] Wireless driver iwlagn+iwlcore doesn't work after resume (needs reloading)
Submitter	: Eddy Petrișor <eddy.petrisor+linbug@gmail.com>
Date		: 2009-10-16 11:07 (11 days old)


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=14402
Subject		: Atheros ath9k module is not working with 2.6.31.1 on an Acer Extensa 7630EZ
Submitter	: Bernhard <berndl81@gmx.at>
Date		: 2009-10-14 11:17 (13 days old)


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=14400
Subject		: disable/enable wlan broken with ath5k
Submitter	: Daniel Bumke <danielbumke@gmail.com>
Date		: 2009-10-13 12:35 (14 days old)


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=14391
Subject		: use after free of struct powernow_k8_data
Submitter	: Michal Schmidt <mschmidt@redhat.com>
Date		: 2009-09-24 14:51 (33 days old)
References	: http://marc.info/?l=linux-kernel&m=125380383515615&w=4


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=14388
Subject		: keyboard under X with 2.6.31
Submitter	: Frédéric L. W. Meunier <fredlwm@gmail.com>
Date		: 2009-10-07 20:19 (20 days old)
First-Bad-Commit: http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=e043e42bdb66885b3ac10d27a01ccb9972e2b0a3
References	: http://marc.info/?l=linux-kernel&m=125494753228217&w=4


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=14385
Subject		: DMAR regression in 2.6.31 leads to ext4 corruption?
Submitter	: Andy Isaacson <adi@hexapodia.org>
Date		: 2009-10-08 23:56 (19 days old)
References	: http://marc.info/?l=linux-kernel&m=125504643703877&w=4


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=14294
Subject		: kernel BUG at drivers/ide/ide-disk.c:187
Submitter	: Santiago Garcia Mantinan <manty@manty.net>
Date		: 2009-09-30 11:05 (27 days old)
References	: http://marc.info/?l=linux-kernel&m=125430926311466&w=4
Handled-By	: David Miller <davem@davemloft.net>


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=14267
Subject		: Disassociating atheros wlan
Submitter	: Kristoffer Ericson <kristoffer.ericson@gmail.com>
Date		: 2009-09-24 10:16 (33 days old)
References	: http://marc.info/?l=linux-kernel&m=125378723723384&w=4


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=14265
Subject		: ifconfig: page allocation failure. order:5, mode:0x8020 w/ e100
Submitter	: Karol Lewandowski <karol.k.lewandowski@gmail.com>
Date		: 2009-09-15 12:05 (42 days old)
References	: http://marc.info/?l=linux-kernel&m=125301636509517&w=4


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=14257
Subject		: Not able to boot on 32 bit System
Submitter	: Rishikesh <risrajak@linux.vnet.ibm.com>
Date		: 2009-09-21 15:25 (36 days old)
References	: http://marc.info/?l=linux-kernel&m=125354604314412&w=4


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=14256
Subject		: kernel BUG at fs/ext3/super.c:435
Submitter	: Mikael Pettersson <mikpe@it.uu.se>
Date		: 2009-09-21 7:29 (36 days old)
References	: http://marc.info/?l=linux-kernel&m=125351816109264&w=4


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=14252
Subject		: WARNING: at include/linux/skbuff.h:1382 w/ e1000
Submitter	: Stephan von Krawczynski <skraw@ithnet.com>
Date		: 2009-09-20 11:26 (37 days old)
References	: http://marc.info/?l=linux-kernel&m=125344599006033&w=4


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=14249
Subject		: BUG: oops in gss_validate on 2.6.31
Submitter	: Bastian Blank <bastian@waldi.eu.org>
Date		: 2009-09-16 10:29 (41 days old)
References	: http://marc.info/?l=linux-kernel&m=125309700417283&w=4
Handled-By	: Trond Myklebust <trond.myklebust@fys.uio.no>


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=14248
Subject		: 2.6.31 wireless: WARNING: at net/wireless/ibss.c:34
Submitter	: Jurriaan <thunder8@xs4all.nl>
Date		: 2009-09-13 7:32 (44 days old)
References	: http://marc.info/?l=linux-kernel&m=125282721113553&w=4


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=14204
Subject		: MCE prevent booting on my computer(pentium iii @500Mhz)
Submitter	: GNUtoo <GNUtoo@no-log.org>
Date		: 2009-09-21 20:36 (36 days old)


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=14181
Subject		: b43 causes panic at ifconfig down / shutdown
Submitter	: Jeremy Huddleston <jeremyhu@freedesktop.org>
Date		: 2009-09-15 18:34 (42 days old)


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=14157
Subject		: end_request: I/O error, dev cciss/cXdX, sector 0
Submitter	:  <jiri.harcarik@gmail.com>
Date		: 2009-09-11 07:42 (46 days old)


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=14141
Subject		: order 2 page allocation failures in iwlagn
Submitter	: Frans Pop <elendil@planet.nl>
Date		: 2009-09-06 7:40 (51 days old)
First-Bad-Commit: http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=2ff05b2b4eac2e63d345fc731ea151a060247f53
References	: http://marc.info/?l=linux-kernel&m=125222287419691&w=4
		  http://lkml.org/lkml/2009/10/2/86
		  http://lkml.org/lkml/2009/10/5/24
		  http://lkml.indiana.edu/hypermail/linux/kernel/0910.1/01395.html
Handled-By	: Pekka Enberg <penberg@cs.helsinki.fi>


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=14114
Subject		: Tuning a saa7134 based card is broken in kernel 2.6.31-rc7
Submitter	: Tsvety Petrov <Tsvetoslav.Petrov@itron.com>
Date		: 2009-09-03 21:06 (54 days old)


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=14090
Subject		: WARNING: at fs/notify/inotify/inotify_user.c:394
Submitter	: Joerg Platte <bugzilla@jako.ping.de>
Date		: 2009-08-30 15:21 (58 days old)


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=14058
Subject		: Oops in fsnotify
Submitter	: Grant Wilson <grant.wilson@zen.co.uk>
Date		: 2009-08-20 15:48 (68 days old)
References	: http://marc.info/?l=linux-kernel&m=125078450923133&w=4


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13987
Subject		: Received NMI interrupt at resume
Submitter	: Christian Casteyde <casteyde.christian@free.fr>
Date		: 2009-08-15 07:55 (73 days old)
First-Bad-Commit: http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=f41f3f373dd72344c65d801d6381fe83ef3a2c54


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


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 (84 days old)


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


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


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 (132 days old)
References	: http://lkml.org/lkml/2009/6/17/194


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

Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=14340
Subject		: speedstep-ich driver not working in 2.6.31
Submitter	:  <dave.mueller@gmx.ch>
Date		: 2009-10-07 08:16 (20 days old)
Handled-By	: Eric Pielbug <e.a.b.piel@tudelft.nl>
		  Rusty Russell <rusty@rustcorp.com.au>
Patch		: http://patchwork.kernel.org/patch/54672/


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=14258
Subject		: Memory leak in SCSI initialization
Submitter	: Tetsuo Handa <penguin-kernel@i-love.sakura.ne.jp>
Date		: 2009-09-22 4:18 (35 days old)
References	: http://marc.info/?l=linux-kernel&m=125359311312243&w=4
Handled-By	: Michael Ellerman <michael@ellerman.id.au>
		  James Bottomley <James.Bottomley@suse.de>
Patch		: http://patchwork.kernel.org/patch/51412/


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=14253
Subject		: Oops in driversbasefirmware_class
Submitter	: Lars Ericsson <Lars_Ericsson@telia.com>
Date		: 2009-09-16 20:44 (41 days old)
References	: http://lkml.org/lkml/2009/9/16/461
Handled-By	: Frederik Deweerdt <frederik.deweerdt@xprog.eu>
Patch		: http://patchwork.kernel.org/patch/49914/


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=14137
Subject		: usb console regressions
Submitter	: Jason Wessel <jason.wessel@windriver.com>
Date		: 2009-09-05 21:08 (52 days old)
References	: http://marc.info/?l=linux-kernel&m=125218501310512&w=4
Handled-By	: Jason Wessel <jason.wessel@windriver.com>
Patch		: http://patchwork.kernel.org/patch/45953/
		  http://patchwork.kernel.org/patch/45952/


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=14017
Subject		: _end symbol missing from Symbol.map
Submitter	: Hannes Reinecke <hare@suse.de>
Date		: 2009-08-13 6:45 (75 days old)
First-Bad-Commit: http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=091e52c3551d3031343df24b573b770b4c6c72b6
References	: http://marc.info/?l=linux-kernel&m=125014649102253&w=4
Handled-By	: Hannes Reinecke <hare@suse.de>
Patch		: http://marc.info/?l=linux-kernel&m=125014649102253&w=4


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.30 and 2.6.31, 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 regressions introduced between 2.6.30 and 2.6.31.

The following bug entry is on the current list of known regressions
introduced between 2.6.30 and 2.6.31.  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@linux.vnet.ibm.com>
Date		: 2009-06-17 17:56 (132 days old)
References	: http://lkml.org/lkml/2009/6/17/194

[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 regressions introduced between 2.6.30 and 2.6.31.

The following bug entry is on the current list of known regressions
introduced between 2.6.30 and 2.6.31.  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@gmail.com>
Date		: 2009-07-06 18:32 (113 days old)
References	: http://marc.info/?l=linux-kernel&m=124690524027166&w=4

[Bug #14017] _end symbol missing from Symbol.map

[Rafael J. Wysocki]

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

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


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=14017
Subject		: _end symbol missing from Symbol.map
Submitter	: Hannes Reinecke <hare-l3A5Bk7waGM@public.gmane.org>
Date		: 2009-08-13 6:45 (75 days old)
First-Bad-Commit: http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=091e52c3551d3031343df24b573b770b4c6c72b6
References	: http://marc.info/?l=linux-kernel&m=125014649102253&w=4
Handled-By	: Hannes Reinecke <hare-l3A5Bk7waGM@public.gmane.org>
Patch		: http://marc.info/?l=linux-kernel&m=125014649102253&w=4

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

[Rafael J. Wysocki]

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

The following bug entry is on the current list of known regressions
introduced between 2.6.30 and 2.6.31.  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-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
Date		: 2009-07-22 13:35 (97 days old)

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

[Rafael J. Wysocki]

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

The following bug entry is on the current list of known regressions
introduced between 2.6.30 and 2.6.31.  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 (102 days old)
References	: http://marc.info/?l=linux-kernel&m=124785853811667&w=4

[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 regressions introduced between 2.6.30 and 2.6.31.

The following bug entry is on the current list of known regressions
introduced between 2.6.30 and 2.6.31.  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 (82 days old)
References	: http://marc.info/?l=linux-kernel&m=124958978600600&w=4

[Bug #13987] Received NMI interrupt at resume

[Rafael J. Wysocki]

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

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


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13987
Subject		: Received NMI interrupt at resume
Submitter	: Christian Casteyde <casteyde.christian@free.fr>
Date		: 2009-08-15 07:55 (73 days old)
First-Bad-Commit: http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=f41f3f373dd72344c65d801d6381fe83ef3a2c54

[Bug #13941] x86 Geode issue

[Rafael J. Wysocki]

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

The following bug entry is on the current list of known regressions
introduced between 2.6.30 and 2.6.31.  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 (85 days old)
References	: http://marc.info/?l=linux-kernel&m=124930434732481&w=4

[Bug #13906] Huawei E169 GPRS connection causes Ooops

[Rafael J. Wysocki]

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

The following bug entry is on the current list of known regressions
introduced between 2.6.30 and 2.6.31.  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@gmail.com>
Date		: 2009-08-04 09:02 (84 days old)

[Bug #14058] Oops in fsnotify

[Rafael J. Wysocki]

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

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


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=14058
Subject		: Oops in fsnotify
Submitter	: Grant Wilson <grant.wilson-1HOZaDBbGgxaa/9Udqfwiw@public.gmane.org>
Date		: 2009-08-20 15:48 (68 days old)
References	: http://marc.info/?l=linux-kernel&m=125078450923133&w=4

[Bug #14114] Tuning a saa7134 based card is broken in kernel 2.6.31-rc7

[Rafael J. Wysocki]

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

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


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=14114
Subject		: Tuning a saa7134 based card is broken in kernel 2.6.31-rc7
Submitter	: Tsvety Petrov <Tsvetoslav.Petrov-qXmYkbEmOXkAvxtiuMwx3w@public.gmane.org>
Date		: 2009-09-03 21:06 (54 days old)

[Bug #14090] WARNING: at fs/notify/inotify/inotify_user.c:394

[Rafael J. Wysocki]

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

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


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=14090
Subject		: WARNING: at fs/notify/inotify/inotify_user.c:394
Submitter	: Joerg Platte <bugzilla@jako.ping.de>
Date		: 2009-08-30 15:21 (58 days old)

[Bug #14137] usb console regressions

[Rafael J. Wysocki]

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

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


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=14137
Subject		: usb console regressions
Submitter	: Jason Wessel <jason.wessel@windriver.com>
Date		: 2009-09-05 21:08 (52 days old)
References	: http://marc.info/?l=linux-kernel&m=125218501310512&w=4
Handled-By	: Jason Wessel <jason.wessel@windriver.com>
Patch		: http://patchwork.kernel.org/patch/45953/
		  http://patchwork.kernel.org/patch/45952/

[Bug #14141] order 2 page allocation failures in iwlagn

[Rafael J. Wysocki]

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

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


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=14141
Subject		: order 2 page allocation failures in iwlagn
Submitter	: Frans Pop <elendil@planet.nl>
Date		: 2009-09-06 7:40 (51 days old)
First-Bad-Commit: http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=2ff05b2b4eac2e63d345fc731ea151a060247f53
References	: http://marc.info/?l=linux-kernel&m=125222287419691&w=4
		  http://lkml.org/lkml/2009/10/2/86
		  http://lkml.org/lkml/2009/10/5/24
		  http://lkml.indiana.edu/hypermail/linux/kernel/0910.1/01395.html
Handled-By	: Pekka Enberg <penberg@cs.helsinki.fi>

[Bug #14157] end_request: I/O error, dev cciss/cXdX, sector 0

[Rafael J. Wysocki]

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

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


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=14157
Subject		: end_request: I/O error, dev cciss/cXdX, sector 0
Submitter	:  <jiri.harcarik@gmail.com>
Date		: 2009-09-11 07:42 (46 days old)

[Bug #14181] b43 causes panic at ifconfig down / shutdown

[Rafael J. Wysocki]

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

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


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=14181
Subject		: b43 causes panic at ifconfig down / shutdown
Submitter	: Jeremy Huddleston <jeremyhu@freedesktop.org>
Date		: 2009-09-15 18:34 (42 days old)

[Bug #14248] 2.6.31 wireless: WARNING: at net/wireless/ibss.c:34

[Rafael J. Wysocki]

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

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


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=14248
Subject		: 2.6.31 wireless: WARNING: at net/wireless/ibss.c:34
Submitter	: Jurriaan <thunder8-qWit8jRvyhVmR6Xm/wNWPw@public.gmane.org>
Date		: 2009-09-13 7:32 (44 days old)
References	: http://marc.info/?l=linux-kernel&m=125282721113553&w=4

[Bug #14204] MCE prevent booting on my computer(pentium iii @500Mhz)

[Rafael J. Wysocki]

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

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


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=14204
Subject		: MCE prevent booting on my computer(pentium iii @500Mhz)
Submitter	: GNUtoo <GNUtoo-n+LsquliYkMdnm+yROfE0A@public.gmane.org>
Date		: 2009-09-21 20:36 (36 days old)

[Bug #14249] BUG: oops in gss_validate on 2.6.31

[Rafael J. Wysocki]

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

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


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=14249
Subject		: BUG: oops in gss_validate on 2.6.31
Submitter	: Bastian Blank <bastian-yyjItF7Rl6lg9hUCZPvPmw@public.gmane.org>
Date		: 2009-09-16 10:29 (41 days old)
References	: http://marc.info/?l=linux-kernel&m=125309700417283&w=4
Handled-By	: Trond Myklebust <trond.myklebust-41N18TsMXrtuMpJDpNschA@public.gmane.org>

[Bug #14252] WARNING: at include/linux/skbuff.h:1382 w/ e1000

[Rafael J. Wysocki]

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

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


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=14252
Subject		: WARNING: at include/linux/skbuff.h:1382 w/ e1000
Submitter	: Stephan von Krawczynski <skraw-DcQCyzbjH0jQT0dZR+AlfA@public.gmane.org>
Date		: 2009-09-20 11:26 (37 days old)
References	: http://marc.info/?l=linux-kernel&m=125344599006033&w=4

[Bug #14253] Oops in driversbasefirmware_class

[Rafael J. Wysocki]

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

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


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=14253
Subject		: Oops in driversbasefirmware_class
Submitter	: Lars Ericsson <Lars_Ericsson-zq6IREYz3ykAvxtiuMwx3w@public.gmane.org>
Date		: 2009-09-16 20:44 (41 days old)
References	: http://lkml.org/lkml/2009/9/16/461
Handled-By	: Frederik Deweerdt <frederik.deweerdt-kjvbsxwSFqI@public.gmane.org>
Patch		: http://patchwork.kernel.org/patch/49914/

[Bug #14256] kernel BUG at fs/ext3/super.c:435

[Rafael J. Wysocki]

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

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


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=14256
Subject		: kernel BUG at fs/ext3/super.c:435
Submitter	: Mikael Pettersson <mikpe-1zs4UD6AkMk@public.gmane.org>
Date		: 2009-09-21 7:29 (36 days old)
References	: http://marc.info/?l=linux-kernel&m=125351816109264&w=4

[Bug #14257] Not able to boot on 32 bit System

[Rafael J. Wysocki]

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

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


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=14257
Subject		: Not able to boot on 32 bit System
Submitter	: Rishikesh <risrajak@linux.vnet.ibm.com>
Date		: 2009-09-21 15:25 (36 days old)
References	: http://marc.info/?l=linux-kernel&m=125354604314412&w=4

[Bug #14258] Memory leak in SCSI initialization

[Rafael J. Wysocki]

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

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


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=14258
Subject		: Memory leak in SCSI initialization
Submitter	: Tetsuo Handa <penguin-kernel-1yMVhJb1mP/7nzcFbJAaVXf5DAMn2ifp@public.gmane.org>
Date		: 2009-09-22 4:18 (35 days old)
References	: http://marc.info/?l=linux-kernel&m=125359311312243&w=4
Handled-By	: Michael Ellerman <michael-Gsx/Oe8HsFggBc27wqDAHg@public.gmane.org>
		  James Bottomley <James.Bottomley-l3A5Bk7waGM@public.gmane.org>
Patch		: http://patchwork.kernel.org/patch/51412/

[Bug #14265] ifconfig: page allocation failure. order:5, mode:0x8020 w/ e100

[Rafael J. Wysocki]

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

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


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=14265
Subject		: ifconfig: page allocation failure. order:5, mode:0x8020 w/ e100
Submitter	: Karol Lewandowski <karol.k.lewandowski@gmail.com>
Date		: 2009-09-15 12:05 (42 days old)
References	: http://marc.info/?l=linux-kernel&m=125301636509517&w=4

[Bug #14267] Disassociating atheros wlan

[Rafael J. Wysocki]

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

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


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=14267
Subject		: Disassociating atheros wlan
Submitter	: Kristoffer Ericson <kristoffer.ericson@gmail.com>
Date		: 2009-09-24 10:16 (33 days old)
References	: http://marc.info/?l=linux-kernel&m=125378723723384&w=4

[Bug #14340] speedstep-ich driver not working in 2.6.31

[Rafael J. Wysocki]

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

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


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=14340
Subject		: speedstep-ich driver not working in 2.6.31
Submitter	:  <dave.mueller-OI3hZJvNYWs@public.gmane.org>
Date		: 2009-10-07 08:16 (20 days old)
Handled-By	: Eric Pielbug <e.a.b.piel-hGVxb2UgFK3z+pZb47iToQ@public.gmane.org>
		  Rusty Russell <rusty-8n+1lVoiYb80n/F98K4Iww@public.gmane.org>
Patch		: http://patchwork.kernel.org/patch/54672/

[Bug #14294] kernel BUG at drivers/ide/ide-disk.c:187

[Rafael J. Wysocki]

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

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


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=14294
Subject		: kernel BUG at drivers/ide/ide-disk.c:187
Submitter	: Santiago Garcia Mantinan <manty-gaW6/AuhO2xeoWH0uzbU5w@public.gmane.org>
Date		: 2009-09-30 11:05 (27 days old)
References	: http://marc.info/?l=linux-kernel&m=125430926311466&w=4
Handled-By	: David Miller <davem-fT/PcQaiUtIeIZ0/mPfg9Q@public.gmane.org>

[Bug #14391] use after free of struct powernow_k8_data

[Rafael J. Wysocki]

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

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


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=14391
Subject		: use after free of struct powernow_k8_data
Submitter	: Michal Schmidt <mschmidt-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
Date		: 2009-09-24 14:51 (33 days old)
References	: http://marc.info/?l=linux-kernel&m=125380383515615&w=4

[Bug #14388] keyboard under X with 2.6.31

[Rafael J. Wysocki]

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

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


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=14388
Subject		: keyboard under X with 2.6.31
Submitter	: Frédéric L. W. Meunier <fredlwm@gmail.com>
Date		: 2009-10-07 20:19 (20 days old)
First-Bad-Commit: http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=e043e42bdb66885b3ac10d27a01ccb9972e2b0a3
References	: http://marc.info/?l=linux-kernel&m=125494753228217&w=4

[Bug #14385] DMAR regression in 2.6.31 leads to ext4 corruption?

[Rafael J. Wysocki]

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

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


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=14385
Subject		: DMAR regression in 2.6.31 leads to ext4 corruption?
Submitter	: Andy Isaacson <adi@hexapodia.org>
Date		: 2009-10-08 23:56 (19 days old)
References	: http://marc.info/?l=linux-kernel&m=125504643703877&w=4

[Bug #14400] disable/enable wlan broken with ath5k

[Rafael J. Wysocki]

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

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


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=14400
Subject		: disable/enable wlan broken with ath5k
Submitter	: Daniel Bumke <danielbumke@gmail.com>
Date		: 2009-10-13 12:35 (14 days old)

[Bug #14417] [Regression] Wireless driver iwlagn+iwlcore doesn't work after resume (needs reloading)

[Rafael J. Wysocki]

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

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


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=14417
Subject		: [Regression] Wireless driver iwlagn+iwlcore doesn't work after resume (needs reloading)
Submitter	: Eddy Petri»ôor <eddy.petrisor+linbug-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Date		: 2009-10-16 11:07 (11 days old)

[Bug #14402] Atheros ath9k module is not working with 2.6.31.1 on an Acer Extensa 7630EZ

[Rafael J. Wysocki]

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

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


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=14402
Subject		: Atheros ath9k module is not working with 2.6.31.1 on an Acer Extensa 7630EZ
Submitter	: Bernhard <berndl81-RbZlAiThDcE@public.gmane.org>
Date		: 2009-10-14 11:17 (13 days old)

[Bug #14446] battery status info broken/useless in 2.6.32-rc3 - MSI PR200 (possibly others, too)

[Rafael J. Wysocki]

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

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


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=14446
Subject		: battery status info broken/useless in 2.6.32-rc3 - MSI PR200 (possibly others, too)
Submitter	: Eddy Petri»ôor <eddy.petrisor+linbug@gmail.com>
Date		: 2009-10-20 08:25 (7 days old)

[Bug #14476] Unable to handle kernel paging request in nfs_write_mapping

[Rafael J. Wysocki]

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

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


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=14476
Subject		: Unable to handle kernel paging request in nfs_write_mapping
Submitter	: Stephan von Krawczynski <skraw-DcQCyzbjH0jQT0dZR+AlfA@public.gmane.org>
Date		: 2009-10-14 9:53 (13 days old)
References	: http://marc.info/?l=linux-kernel&m=125551421405656&w=4
Handled-By	: Trond Myklebust <Trond.Myklebust-HgOvQuBEEgTQT0dZR+AlfA@public.gmane.org>

[Bug #14474] restorecond going crazy on 2.6.31.4 - inotify regression?

[Rafael J. Wysocki]

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

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


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=14474
Subject		: restorecond going crazy on 2.6.31.4 - inotify regression?
Submitter	: Robert Hancock <hancockrwd-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Date		: 2009-10-16 0:03 (11 days old)
References	: http://marc.info/?l=linux-kernel&m=125565159520489&w=4

Re: [Bug #14058] Oops in fsnotify

[Eric Paris]

On Mon, 2009-10-26 at 20:31 +0100, Rafael J. Wysocki wrote:
> This message has been generated automatically as a part of a report
> of regressions introduced between 2.6.30 and 2.6.31.
> 
> The following bug entry is on the current list of known regressions
> introduced between 2.6.30 and 2.6.31.  Please verify if it still should
> be listed and let me know (either way).

Should have been fixed by:
9f0d793b52eb2266359661369ef6303838904855

At least I have my fingers crossed hoping so.  I can't make it happen
with that patch.

-Eric
> 
> 
> Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=14058
> Subject		: Oops in fsnotify
> Submitter	: Grant Wilson <grant.wilson-1HOZaDBbGgxaa/9Udqfwiw@public.gmane.org>
> Date		: 2009-08-20 15:48 (68 days old)
> References	: http://marc.info/?l=linux-kernel&m=125078450923133&w=4
> 
> 

Re: [Bug #14267] Disassociating atheros wlan

[Kristoffer Ericson]

On Mon, 26 Oct 2009 20:31:55 +0100 (CET)
"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.30 and 2.6.31.
> 
> The following bug entry is on the current list of known regressions
> introduced between 2.6.30 and 2.6.31.  Please verify if it still should
> be listed and let me know (either way).
> 
> 
> Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=14267
> Subject		: Disassociating atheros wlan
> Submitter	: Kristoffer Ericson <kristoffer.ericson@gmail.com>
> Date		: 2009-09-24 10:16 (33 days old)
> References	: http://marc.info/?l=linux-kernel&m=125378723723384&w=4
> 
> 

Still valid and should remain.


-- 
Kristoffer Ericson <kristoffer.ericson@gmail.com>

Re: [Bug #14058] Oops in fsnotify

[Rafael J. Wysocki]

On Monday 26 October 2009, Eric Paris wrote:
> On Mon, 2009-10-26 at 20:31 +0100, Rafael J. Wysocki wrote:
> > This message has been generated automatically as a part of a report
> > of regressions introduced between 2.6.30 and 2.6.31.
> > 
> > The following bug entry is on the current list of known regressions
> > introduced between 2.6.30 and 2.6.31.  Please verify if it still should
> > be listed and let me know (either way).
> 
> Should have been fixed by:
> 9f0d793b52eb2266359661369ef6303838904855
> 
> At least I have my fingers crossed hoping so.  I can't make it happen
> with that patch.

OK, closing.

Thanks,
Rafael

Re: [Bug #14267] Disassociating atheros wlan

[Rafael J. Wysocki]

On Monday 26 October 2009, Kristoffer Ericson wrote:
> On Mon, 26 Oct 2009 20:31:55 +0100 (CET)
> "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.30 and 2.6.31.
> > 
> > The following bug entry is on the current list of known regressions
> > introduced between 2.6.30 and 2.6.31.  Please verify if it still should
> > be listed and let me know (either way).
> > 
> > 
> > Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=14267
> > Subject		: Disassociating atheros wlan
> > Submitter	: Kristoffer Ericson <kristoffer.ericson@gmail.com>
> > Date		: 2009-09-24 10:16 (33 days old)
> > References	: http://marc.info/?l=linux-kernel&m=125378723723384&w=4
> > 
> > 
> 
> Still valid and should remain.

Thanks for the update.

Rafael

Re: [Bug #13941] x86 Geode issue

[Martin-Éric Racine]

I do not recall anyone on LKML actually ever doing any work towards
fixing this issue so, yes, it is still open.

On Mon, Oct 26, 2009 at 9:31 PM, 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.30 and 2.6.31.
>
> The following bug entry is on the current list of known regressions
> introduced between 2.6.30 and 2.6.31.  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 (85 days old)
> References      : http://marc.info/?l=linux-kernel&m=124930434732481&w=4
>
>
>

Re: [Bug #13941] x86 Geode issue

[Rafael J. Wysocki]

On Monday 26 October 2009, Martin-Éric Racine wrote:
> I do not recall anyone on LKML actually ever doing any work towards
> fixing this issue so, yes, it is still open.

Thanks for the update.

Rafael


> On Mon, Oct 26, 2009 at 9:31 PM, 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.30 and 2.6.31.
> >
> > The following bug entry is on the current list of known regressions
> > introduced between 2.6.30 and 2.6.31.  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 (85 days old)
> > References      : http://marc.info/?l=linux-kernel&m=124930434732481&w=4

Re: [Bug #14388] keyboard under X with 2.6.31

[Boyan]

Rafael J. Wysocki wrote:
> This message has been generated automatically as a part of a report
> of regressions introduced between 2.6.30 and 2.6.31.
> 
> The following bug entry is on the current list of known regressions
> introduced between 2.6.30 and 2.6.31.  Please verify if it still should
> be listed and let me know (either way).
> 
> 
> Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=14388
> Subject		: keyboard under X with 2.6.31
> Submitter	: Frédéric L. W. Meunier <fredlwm-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
> Date		: 2009-10-07 20:19 (20 days old)
> First-Bad-Commit: http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=e043e42bdb66885b3ac10d27a01ccb9972e2b0a3
> References	: http://marc.info/?l=linux-kernel&m=125494753228217&w=4
> 

I think it is fixed in 2.6.31.5. I can't reproduce the problem with it.

Re: [Bug #14388] keyboard under X with 2.6.31

[Linus Torvalds]

On Tue, 27 Oct 2009, Boyan wrote:
> 
> I think it is fixed in 2.6.31.5. I can't reproduce the problem with it.

It was fixed by mainline commit c8e33141911bf8fe87dc6c92793b9a59b2be0130 
("tty: Make flush_to_ldisc() locking more robust"), which got back-ported 
to 2.6.31.5 as commit 86d23a057.

			Linus

Re: [Bug #14388] keyboard under X with 2.6.31

[Ed Tomlinson]

On Monday 26 October 2009 18:45:27 Linus Torvalds wrote:
> 
> On Tue, 27 Oct 2009, Boyan wrote:
> > 
> > I think it is fixed in 2.6.31.5. I can't reproduce the problem with it.
> 
> It was fixed by mainline commit c8e33141911bf8fe87dc6c92793b9a59b2be0130 
> ("tty: Make flush_to_ldisc() locking more robust"), which got back-ported 
> to 2.6.31.5 as commit 86d23a057.

I can confirm that the keyboard is no longer missbehaving here  with 31.5

Ed

Re: [Bug #14474] restorecond going crazy on 2.6.31.4 - inotify regression?

[Robert Hancock]

On Mon, Oct 26, 2009 at 1:32 PM, 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.30 and 2.6.31.
>
> The following bug entry is on the current list of known regressions
> introduced between 2.6.30 and 2.6.31.  Please verify if it still should
> be listed and let me know (either way).
>
>
> Bug-Entry       : http://bugzilla.kernel.org/show_bug.cgi?id=14474
> Subject         : restorecond going crazy on 2.6.31.4 - inotify regression?
> Submitter       : Robert Hancock <hancockrwd-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
> Date            : 2009-10-16 0:03 (11 days old)
> References      : http://marc.info/?l=linux-kernel&m=125565159520489&w=4

This is definitely reproducible on 2.6.31.4 on CentOS 5.4, I'll likely
try 2.6.31.5 shortly, but it doesn't seem like any of the 2.6.31.5
patches touch inotify..

Re: [Bug #14388] keyboard under X with 2.6.31

[Justin P. Mattock]

Ed Tomlinson wrote:
> On Monday 26 October 2009 18:45:27 Linus Torvalds wrote:
>    
>> On Tue, 27 Oct 2009, Boyan wrote:
>>      
>>> I think it is fixed in 2.6.31.5. I can't reproduce the problem with it.
>>>        
>> It was fixed by mainline commit c8e33141911bf8fe87dc6c92793b9a59b2be0130
>> ("tty: Make flush_to_ldisc() locking more robust"), which got back-ported
>> to 2.6.31.5 as commit 86d23a057.
>>      
>
> I can confirm that the keyboard is no longer missbehaving here  with 31.5
>
> Ed
>
>    
I guess there you have it... everybody
confirms this is fixed.
safe to say yes close, but not until the patch
has been pushed to the main tree..

cheers

Justin P. Mattock

Re: [Bug #14388] keyboard under X with 2.6.31

[Rafael J. Wysocki]

On Monday 26 October 2009, Linus Torvalds wrote:
> 
> On Tue, 27 Oct 2009, Boyan wrote:
> > 
> > I think it is fixed in 2.6.31.5. I can't reproduce the problem with it.
> 
> It was fixed by mainline commit c8e33141911bf8fe87dc6c92793b9a59b2be0130 
> ("tty: Make flush_to_ldisc() locking more robust"), which got back-ported 
> to 2.6.31.5 as commit 86d23a057.

Thanks, closing.

Rafael

Re: [Bug #14474] restorecond going crazy on 2.6.31.4 - inotify regression?

[Rafael J. Wysocki]

On Tuesday 27 October 2009, Robert Hancock wrote:
> On Mon, Oct 26, 2009 at 1:32 PM, 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.30 and 2.6.31.
> >
> > The following bug entry is on the current list of known regressions
> > introduced between 2.6.30 and 2.6.31.  Please verify if it still should
> > be listed and let me know (either way).
> >
> >
> > Bug-Entry       : http://bugzilla.kernel.org/show_bug.cgi?id=14474
> > Subject         : restorecond going crazy on 2.6.31.4 - inotify regression?
> > Submitter       : Robert Hancock <hancockrwd-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
> > Date            : 2009-10-16 0:03 (11 days old)
> > References      : http://marc.info/?l=linux-kernel&m=125565159520489&w=4
> 
> This is definitely reproducible on 2.6.31.4 on CentOS 5.4, I'll likely
> try 2.6.31.5 shortly, but it doesn't seem like any of the 2.6.31.5
> patches touch inotify..

Thanks for the update.

Rafael

Re: [Bug #14474] restorecond going crazy on 2.6.31.4 - inotify regression?

[Eric Paris]

On Tue, Oct 27, 2009 at 4:24 AM, Rafael J. Wysocki <rjw@sisk.pl> wrote:
> On Tuesday 27 October 2009, Robert Hancock wrote:
>> On Mon, Oct 26, 2009 at 1:32 PM, 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.30 and 2.6.31.
>> >
>> > The following bug entry is on the current list of known regressions
>> > introduced between 2.6.30 and 2.6.31.  Please verify if it still should
>> > be listed and let me know (either way).
>> >
>> >
>> > Bug-Entry       : http://bugzilla.kernel.org/show_bug.cgi?id=14474
>> > Subject         : restorecond going crazy on 2.6.31.4 - inotify regression?
>> > Submitter       : Robert Hancock <hancockrwd@gmail.com>
>> > Date            : 2009-10-16 0:03 (11 days old)
>> > References      : http://marc.info/?l=linux-kernel&m=125565159520489&w=4
>>
>> This is definitely reproducible on 2.6.31.4 on CentOS 5.4, I'll likely
>> try 2.6.31.5 shortly, but it doesn't seem like any of the 2.6.31.5
>> patches touch inotify..

It's a restorecond bug.  restorecon acted as if watch descriptors
could never be reused.  They weren't on old kernels and it's possible
they are reused now.  Restorecon was fixed.

http://marc.info/?l=selinux&m=125380417916233&w=2

a change in the kernel caused a buggy userspace program to break.  I
know how to put the kernel back the way it was, but I don't know if we
call this a regression, you guys tell me.

-Eric

Re: [Bug #14090] WARNING: at fs/notify/inotify/inotify_user.c:394

[Eric Paris]

On Mon, Oct 26, 2009 at 3:31 PM, 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.30 and 2.6.31.
>
> The following bug entry is on the current list of known regressions
> introduced between 2.6.30 and 2.6.31.  Please verify if it still should
> be listed and let me know (either way).
>
>
> Bug-Entry       : http://bugzilla.kernel.org/show_bug.cgi?id=14090
> Subject         : WARNING: at fs/notify/inotify/inotify_user.c:394
> Submitter       : Joerg Platte <bugzilla-ilKWAAXSMVN6lmGzAMPh1A@public.gmane.org>
> Date            : 2009-08-30 15:21 (58 days old)

should be fixed by: 9f0d793b52eb2266359661369ef6303838904855 in linus' tree

Re: [Bug #14090] WARNING: at fs/notify/inotify/inotify_user.c:394

[Rafael J. Wysocki]

On Tuesday 27 October 2009, Eric Paris wrote:
> On Mon, Oct 26, 2009 at 3:31 PM, 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.30 and 2.6.31.
> >
> > The following bug entry is on the current list of known regressions
> > introduced between 2.6.30 and 2.6.31.  Please verify if it still should
> > be listed and let me know (either way).
> >
> >
> > Bug-Entry       : http://bugzilla.kernel.org/show_bug.cgi?id=14090
> > Subject         : WARNING: at fs/notify/inotify/inotify_user.c:394
> > Submitter       : Joerg Platte <bugzilla-ilKWAAXSMVN6lmGzAMPh1A@public.gmane.org>
> > Date            : 2009-08-30 15:21 (58 days old)
> 
> should be fixed by: 9f0d793b52eb2266359661369ef6303838904855 in linus' tree

Thanks, closing.

Rafael

Re: [Bug #14474] restorecond going crazy on 2.6.31.4 - inotify regression?

[Rafael J. Wysocki]

On Tuesday 27 October 2009, Eric Paris wrote:
> On Tue, Oct 27, 2009 at 4:24 AM, Rafael J. Wysocki <rjw-KKrjLPT3xs0@public.gmane.org> wrote:
> > On Tuesday 27 October 2009, Robert Hancock wrote:
> >> On Mon, Oct 26, 2009 at 1:32 PM, 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.30 and 2.6.31.
> >> >
> >> > The following bug entry is on the current list of known regressions
> >> > introduced between 2.6.30 and 2.6.31.  Please verify if it still should
> >> > be listed and let me know (either way).
> >> >
> >> >
> >> > Bug-Entry       : http://bugzilla.kernel.org/show_bug.cgi?id=14474
> >> > Subject         : restorecond going crazy on 2.6.31.4 - inotify regression?
> >> > Submitter       : Robert Hancock <hancockrwd-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
> >> > Date            : 2009-10-16 0:03 (11 days old)
> >> > References      : http://marc.info/?l=linux-kernel&m=125565159520489&w=4
> >>
> >> This is definitely reproducible on 2.6.31.4 on CentOS 5.4, I'll likely
> >> try 2.6.31.5 shortly, but it doesn't seem like any of the 2.6.31.5
> >> patches touch inotify..
> 
> It's a restorecond bug.  restorecon acted as if watch descriptors
> could never be reused.  They weren't on old kernels and it's possible
> they are reused now.  Restorecon was fixed.
> 
> http://marc.info/?l=selinux&m=125380417916233&w=2
> 
> a change in the kernel caused a buggy userspace program to break.  I
> know how to put the kernel back the way it was, but I don't know if we
> call this a regression, you guys tell me.

Yes, we do, AFAICS.  The policy is not to break user space, even if it happens
to work by accident.

Thanks,
Rafael

Re: [Bug #14474] restorecond going crazy on 2.6.31.4 - inotify regression?

[jim owens]

Rafael J. Wysocki wrote:
> On Tuesday 27 October 2009, Eric Paris wrote:
>> It's a restorecond bug.  restorecon acted as if watch descriptors
>> could never be reused.  They weren't on old kernels and it's possible
>> they are reused now.  Restorecon was fixed.
>>
>> http://marc.info/?l=selinux&m=125380417916233&w=2
>>
>> a change in the kernel caused a buggy userspace program to break.  I
>> know how to put the kernel back the way it was, but I don't know if we
>> call this a regression, you guys tell me.
> 
> Yes, we do, AFAICS.  The policy is not to break user space, even if it happens
> to work by accident.

But if we make a rule of "never break even bad user programs" then
we also should never plug security holes because that breaks a
user program expecting that attack vector :)

Silly example, but the point is we need to decide if the
user program would have done something wrong eventually
anyway (as in if the system was up long enough, they would
have hit a duplicate id and failed with the old kernel) so
the kernel change just makes it easy to hit the user code bug.

jim

Re: [Bug #14474] restorecond going crazy on 2.6.31.4 - inotify regression?

[Rafael J. Wysocki]

On Wednesday 28 October 2009, jim owens wrote:
> Rafael J. Wysocki wrote:
> > On Tuesday 27 October 2009, Eric Paris wrote:
> >> It's a restorecond bug.  restorecon acted as if watch descriptors
> >> could never be reused.  They weren't on old kernels and it's possible
> >> they are reused now.  Restorecon was fixed.
> >>
> >> http://marc.info/?l=selinux&m=125380417916233&w=2
> >>
> >> a change in the kernel caused a buggy userspace program to break.  I
> >> know how to put the kernel back the way it was, but I don't know if we
> >> call this a regression, you guys tell me.
> > 
> > Yes, we do, AFAICS.  The policy is not to break user space, even if it happens
> > to work by accident.
> 
> But if we make a rule of "never break even bad user programs" then
> we also should never plug security holes because that breaks a
> user program expecting that attack vector :)

Well, that's why this rule is not carved in stone.

Clearly, there are some cases in which we can't afford keeping the buggy user
space happy, not only security-related.

Thanks,
Rafael

Re: [Bug #14265] ifconfig: page allocation failure. order:5, mode:0x8020 w/ e100

[Karol Lewandowski]

On Mon, Oct 26, 2009 at 08:31:54PM +0100, Rafael J. Wysocki wrote:
> Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=14265
> Subject		: ifconfig: page allocation failure. order:5, mode:0x8020 w/ e100
> Submitter	: Karol Lewandowski <karol.k.lewandowski-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
> Date		: 2009-09-15 12:05 (42 days old)
> References	: http://marc.info/?l=linux-kernel&m=125301636509517&w=4

Bug is still present in 2.6.32-rc5.

(I'm currently testing Mel's patches.)

Thanks.

[Bug #13941] x86 Geode issue

[Rafael J. Wysocki]

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

The following bug entry is on the current list of known regressions
introduced between 2.6.30 and 2.6.31.  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 (106 days old)
References	: http://marc.info/?l=linux-kernel&m=124930434732481&w=4

[Bug #13941] x86 Geode issue

[Rafael J. Wysocki]

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

The following bug entry is on the current list of known regressions
introduced between 2.6.30 and 2.6.31.  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 (111 days old)
References	: http://marc.info/?l=linux-kernel&m=124930434732481&w=4

Re: [Bug #13941] x86 Geode issue

[Martin-Éric Racine]

No, it is not resolved.

Attachments have been recently added to the bug and it would be highly
desirable for whoever introduced those regressions in 2.6.31 to
examine them and participate in resolving the issue. Alternately,
reverting those ACL caching changes to 2.6.30 status would be equally
acceptable as a solution.