2.6.32-rc1-git2: Reported regressions 2.6.30 -> 2.6.31

Jens Axboe · External Since: Oct 04, 2006 Posts: 673

On Fri, Oct 02 2009, Jaswinder Singh Rajput wrote:
> Hello Jens,
>
> On Thu, 2009-10-01 at 21:55 +0200, 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=14133
> > Subject : WARNING: at arch/x86/kernel/smp.c:117 native_smp_send_reschedule
> > Submitter : Jens Axboe <jens.axboe RemoveThis @oracle.com>
> > Date : 2009-08-31 20:43 (32 days old)
> > References : http://marc.info/?l=linux-kernel&m=125175143918050&w=4
> >
> >
>
> Are you still getting this warning in latest -tip. If yes, can you do
> git bisect and specify the commit.

Nope, it seems to have disappeared.

--
Jens Axboe

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo RemoveThis @vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

Cyrill Gorcunov · External Since: Feb 18, 2007 Posts: 128

On 10/1/09, Rafael J. Wysocki <rjw.DeleteThis@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).
>

Michael has been asked to bisect it (if possible). I cant reproduce it
in kvm unfortunately.

>
> Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=14270
> Subject : Cannot boot on a PIII Celeron
> Submitter : Michael Tokarev <mjt.DeleteThis@tls.msk.ru>
> Date : 2009-09-28 15:26 (4 days old)
> References : http://marc.info/?l=linux-kernel&m=125415160524110&w=4
>
>
>
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo.DeleteThis@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

Frans Pop · External Since: May 04, 2006 Posts: 460

On Thursday 01 October 2009, Rafael J. Wysocki wrote:
> 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.TakeThisOut@planet.nl>
> Date : 2009-09-06 7:40 (26 days old)
> References : http://marc.info/?l=linux-kernel&m=125222287419691&w=4
> Handled-By : Pekka Enberg <penberg.TakeThisOut@cs.helsinki.fi>

I'm not sure about this.

The error messages from failed allocations should now be a lot less as a
result of this commit:
commit f82a924cc88a5541df1d4b9d38a0968cd077a051
Author: Reinette Chatre <reinette.chatre.TakeThisOut@intel.com>
Date: Thu Sep 17 10:43:56 2009 -0700
iwlwifi: reduce noise when skb allocation fails

That commit is in mainline, and I'm not sure if it is important enough for
a stable update (AFAICT it's not listed for 2.6.31.2).

That commit is mostly cosmetic, but possibly the real regression is not in
iwlagn but in the way memory is freed/defragmented. That aspect was also
reported by Bartlomiej (#14016) and was extensively discussed (without a
clear conclusion) here: http://lkml.org/lkml/2009/8/26/140.

My own feeling is that Bartlomiej is correct and that something has changed
since .29 and that on average we do have less higher order areas available
after the system has been in use for some time, but I can't substantiate
that. I do know that before .30 I had never seen the SKB allocation
errors.

Main problem is that it's hard to deliberately and reproducibly get the
system in a state where the errors occur.

I certainly do feel that the kernel should try to make sure higher order
allocations remain possible during system use. They are not only needed
shortly after boot: drivers can be loaded/unloaded at any time. OTOH Mel
probably does have a point that really high order GFP_ATOMIC allocations
by drivers make no sense [1].

Anyway, I have no problems with this BR being closed.

Cheers,
FJP

[1] <20090921133704.GO12726.TakeThisOut@csn.ul.ie>
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo.TakeThisOut@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

Michael Tokarev · External Since: Nov 12, 2004 Posts: 140

Cyrill Gorcunov wrote:
> On 10/1/09, Rafael J. Wysocki <rjw RemoveThis @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).
>
> Michael has been asked to bisect it (if possible). I cant reproduce it
> in kvm unfortunately.

Yes, and that's what I'll be trying to do shortly.
I had other issues to sort out and wasn't able to
get to it in few last days.

Also I've a few other suspects. For example, in this .31
config I changed from bzip to lzma compression - and that's
where (or near) kernel is rebooting.

/mjt

>> Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=14270
>> Subject : Cannot boot on a PIII Celeron
>> Submitter : Michael Tokarev <mjt RemoveThis @tls.msk.ru>
>> Date : 2009-09-28 15:26 (4 days old)
>> References : http://marc.info/?l=linux-kernel&m=125415160524110&w=4
>>
>>
>>

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo RemoveThis @vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

Mel Gorman · External Since: May 19, 2006 Posts: 253

On Fri, Oct 02, 2009 at 11:11:52AM +0200, Frans Pop wrote:
> On Thursday 01 October 2009, Rafael J. Wysocki wrote:
> > 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 DeleteThis @planet.nl>
> > Date : 2009-09-06 7:40 (26 days old)
> > References : http://marc.info/?l=linux-kernel&m=125222287419691&w=4
> > Handled-By : Pekka Enberg <penberg DeleteThis @cs.helsinki.fi>
>
> I'm not sure about this.
>
> The error messages from failed allocations should now be a lot less as a
> result of this commit:
> commit f82a924cc88a5541df1d4b9d38a0968cd077a051
> Author: Reinette Chatre <reinette.chatre DeleteThis @intel.com>
> Date: Thu Sep 17 10:43:56 2009 -0700
> iwlwifi: reduce noise when skb allocation fails
>
> That commit is in mainline, and I'm not sure if it is important enough for
> a stable update (AFAICT it's not listed for 2.6.31.2).
>
> That commit is mostly cosmetic, but possibly the real regression is not in
> iwlagn but in the way memory is freed/defragmented. That aspect was also
> reported by Bartlomiej (#14016) and was extensively discussed (without a
> clear conclusion) here: http://lkml.org/lkml/2009/8/26/140.
>
> My own feeling is that Bartlomiej is correct and that something has changed
> since .29 and that on average we do have less higher order areas available
> after the system has been in use for some time, but I can't substantiate
> that. I do know that before .30 I had never seen the SKB allocation
> errors.
>
> Main problem is that it's hard to deliberately and reproducibly get the
> system in a state where the errors occur.
>

Apparently, Karol Lewandowski (cc added) has a reliable
reproduction case for when the firmware loading problem occurs
(http://lkml.org/lkml/2009/9/30/242). While it's not the same problem exactly,
it's probable they're related. I'm hoping the problem commit can be identified
by his bisection whenever he gets around to it.

> I certainly do feel that the kernel should try to make sure higher order
> allocations remain possible during system use. They are not only needed
> shortly after boot: drivers can be loaded/unloaded at any time. OTOH Mel
> probably does have a point that really high order GFP_ATOMIC allocations
> by drivers make no sense [1].
>

While they don't make sense, I accept that the problem is apparently
occuring more now than it did so something has changed that is not
obvious to normal testing. Hopefully Karol will be able to help us out.

> Anyway, I have no problems with this BR being closed.
>
> Cheers,
> FJP
>
> [1] <20090921133704.GO12726 DeleteThis @csn.ul.ie>
>

--
Mel Gorman
Part-time Phd Student Linux Technology Center
University of Limerick IBM Dublin Software Lab
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo DeleteThis @vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

Frans Pop · External Since: May 04, 2006 Posts: 460

On Friday 02 October 2009, Mel Gorman wrote:
> On Fri, Oct 02, 2009 at 11:11:52AM +0200, Frans Pop wrote:
> > My own feeling is that Bartlomiej is correct and that something has
> > changed since .29 and that on average we do have less higher order
> > areas available after the system has been in use for some time, but I
> > can't substantiate that. I do know that before .30 I had never seen
> > the SKB allocation errors.
> >
> > Main problem is that it's hard to deliberately and reproducibly get
> > the system in a state where the errors occur.
>
> Apparently, Karol Lewandowski (cc added) has a reliable
> reproduction case for when the firmware loading problem occurs
> (http://lkml.org/lkml/2009/9/30/242). While it's not the same problem
> exactly, it's probable they're related. I'm hoping the problem commit
> can be identified by his bisection whenever he gets around to it.

That does indeed look like a third independent report for basically the
same issue.

> [...], I accept that the problem is apparently occuring more now than it
> did so something has changed that is not obvious to normal testing.

Cool, that's progress Wink

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo DeleteThis @vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

Michael Tokarev · External Since: Nov 12, 2004 Posts: 140

Michael Tokarev wrote:
> Cyrill Gorcunov wrote:
>> On 10/1/09, Rafael J. Wysocki <rjw DeleteThis @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).
>>
>> Michael has been asked to bisect it (if possible). I cant reproduce it
>> in kvm unfortunately.
>
> Yes, and that's what I'll be trying to do shortly.
> I had other issues to sort out and wasn't able to
> get to it in few last days.
>
> Also I've a few other suspects. For example, in this .31
> config I changed from bzip to lzma compression - and that's
> where (or near) kernel is rebooting.

And that was the problem. After switching from LZMA
to BZIP2 kernel boots again.

Dunno if it can be treated as a regression, but it's
definitely a bug.

/mjt

>>> Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=14270
>>> Subject : Cannot boot on a PIII Celeron
>>> Submitter : Michael Tokarev <mjt DeleteThis @tls.msk.ru>
>>> Date : 2009-09-28 15:26 (4 days old)
>>> References : http://marc.info/?l=linux-kernel&m=125415160524110&w=4
>>>
>>>
>>>
>

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo DeleteThis @vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

Michael Tokarev · External Since: Nov 12, 2004 Posts: 140

Cyrill Gorcunov wrote:
> On 10/2/09, Michael Tokarev <mjt RemoveThis @tls.msk.ru> wrote:
>> Michael Tokarev wrote:
>>> Cyrill Gorcunov wrote:
>>>> On 10/1/09, Rafael J. Wysocki <rjw RemoveThis @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).
>>>> Michael has been asked to bisect it (if possible). I cant reproduce it
>>>> in kvm unfortunately.
>>> Yes, and that's what I'll be trying to do shortly.
>>> I had other issues to sort out and wasn't able to
>>> get to it in few last days.
>>>
>>> Also I've a few other suspects. For example, in this .31
>>> config I changed from bzip to lzma compression - and that's
>>> where (or near) kernel is rebooting.
>> And that was the problem. After switching from LZMA
>> to BZIP2 kernel boots again.
>>
>> Dunno if it can be treated as a regression, but it's
>> definitely a bug.
>
> thanks for tracking it down Michael!
> Rafael, who is responsible for LZMA now?
> Cc him please.

Please hold on for a while.

I switched to BZIP2, it booted fine. I switched back to LZMA -
and that one now boots too. Original bzImage, which were built
by the same compiler from the same source using the same
options reboots.

So um... I'm now trying to reproduce it Wink

/mjt
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo RemoveThis @vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

Cyrill Gorcunov · External Since: Feb 18, 2007 Posts: 128

On 10/2/09, Michael Tokarev <mjt.RemoveThis@tls.msk.ru> wrote:
> Michael Tokarev wrote:
>> Cyrill Gorcunov wrote:
>>> On 10/1/09, Rafael J. Wysocki <rjw.RemoveThis@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).
>>>
>>> Michael has been asked to bisect it (if possible). I cant reproduce it
>>> in kvm unfortunately.
>>
>> Yes, and that's what I'll be trying to do shortly.
>> I had other issues to sort out and wasn't able to
>> get to it in few last days.
>>
>> Also I've a few other suspects. For example, in this .31
>> config I changed from bzip to lzma compression - and that's
>> where (or near) kernel is rebooting.
>
> And that was the problem. After switching from LZMA
> to BZIP2 kernel boots again.
>
> Dunno if it can be treated as a regression, but it's
> definitely a bug.
>
> /mjt

thanks for tracking it down Michael!
Rafael, who is responsible for LZMA now?
Cc him please.
>
>>>> Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=14270
>>>> Subject : Cannot boot on a PIII Celeron
>>>> Submitter : Michael Tokarev <mjt.RemoveThis@tls.msk.ru>
>>>> Date : 2009-09-28 15:26 (4 days old)
>>>> References : http://marc.info/?l=linux-kernel&m=125415160524110&w=4
>>>>
>>>>
>>>>
>>
>
>
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo.RemoveThis@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

Jan Scholz · External Since: Oct 02, 2009 Posts: 1

Hi,

for me this bug is fixed by:

commit 42960a13001aa6df52ca9952ce996f94a744ea65
HID: completely remove apple mightymouse from blacklist

Cheers,
Jan

"Rafael J. Wysocki" <rjw.TakeThisOut@sisk.pl> writes:

> 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=13935
> Subject : 2.6.31-rcX breaks Apple MightyMouse (Bluetooth version)
> Submitter : Adrian Ulrich <kernel.TakeThisOut@blinkenlights.ch>
> Date : 2009-08-08 22:08 (55 days old)
> First-Bad-Commit: http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=com...;h=fa04
>
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo.TakeThisOut@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo.TakeThisOut@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

Tetsuo Handa · External Since: Feb 14, 2007 Posts: 19

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.
This memory leak might exist in all releases since 23 Sep 2005.
http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=com...diff;h=
>
> 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).
As of now, the patch is not yet merged into Linus's tree.
It still should be listed.
>
> Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=14258
> Subject : Memory leak in SCSI initialization
> Submitter : Tetsuo Handa <penguin-kernel.DeleteThis@i-love.sakura.ne.jp>
> Date : 2009-09-22 4:18 (10 days old)
> References : http://marc.info/?l=linux-kernel&m=125359311312243&w=4
> Handled-By : Michael Ellerman <michael.DeleteThis@ellerman.id.au>
> Patch : http://patchwork.kernel.org/patch/49258/
>
Regards.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo.DeleteThis@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

Cyrill Gorcunov · External Since: Feb 18, 2007 Posts: 128

[Michael Tokarev - Fri, Oct 02, 2009 at 02:59:09PM +0400]
....
>
> Please hold on for a while.
>
> I switched to BZIP2, it booted fine. I switched back to LZMA -
> and that one now boots too. Original bzImage, which were built
> by the same compiler from the same source using the same
> options reboots.
>
> So um... I'm now trying to reproduce it Wink

>
> /mjt
>

ok, perhaps it was indirect error or cosmic rays

-- Cyrill
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo.RemoveThis@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

Jiri Kosina · External Since: Nov 29, 2006 Posts: 142

On Thu, 1 Oct 2009, 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=13935
> Subject : 2.6.31-rcX breaks Apple MightyMouse (Bluetooth version)
> Submitter : Adrian Ulrich <kernel DeleteThis @blinkenlights.ch>
> Date : 2009-08-08 22:08 (55 days old)
> First-Bad-Commit: http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=com...;h=fa04

Fixed now in Linus' tree (42960a13) and submitted for stable. Please
close.

--
Jiri Kosina
SUSE Labs, Novell Inc.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo DeleteThis @vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

Rafael J. Wysocki · External Since: May 20, 2006 Posts: 1721

On Friday 02 October 2009, Fabio Comolli wrote:
> Hi.
> I suppose this is still valid. I had to work around it by rfkill-ing
> the device during the suspend process and reenabling at resume time.

Thanks for the update.

> I can try to reproduce it with 2.6.31.1 if you want it.

In fact I'm more interested in whether or not it's still present in the Linus'
tree.

Thanks,
Rafael
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo.RemoveThis@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

Rafael J. Wysocki · External Since: May 20, 2006 Posts: 1721

On Friday 02 October 2009, Jiri Kosina wrote:
> On Thu, 1 Oct 2009, 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=13935
> > Subject : 2.6.31-rcX breaks Apple MightyMouse (Bluetooth version)
> > Submitter : Adrian Ulrich <kernel.TakeThisOut@blinkenlights.ch>
> > Date : 2009-08-08 22:08 (55 days old)
> > First-Bad-Commit: http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=com...;h=fa04
>
> Fixed now in Linus' tree (42960a13) and submitted for stable. Please
> close.

Done.

Thanks,
Rafael
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo.TakeThisOut@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

Rafael J. Wysocki · External Since: May 20, 2006 Posts: 1721

On Friday 02 October 2009, Jens Axboe wrote:
> On Fri, Oct 02 2009, Jaswinder Singh Rajput wrote:
> > Hello Jens,
> >
> > On Thu, 2009-10-01 at 21:55 +0200, 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=14133
> > > Subject : WARNING: at arch/x86/kernel/smp.c:117 native_smp_send_reschedule
> > > Submitter : Jens Axboe <jens.axboe DeleteThis @oracle.com>
> > > Date : 2009-08-31 20:43 (32 days old)
> > > References : http://marc.info/?l=linux-kernel&m=125175143918050&w=4
> > >
> > >
> >
> > Are you still getting this warning in latest -tip. If yes, can you do
> > git bisect and specify the commit.
>
> Nope, it seems to have disappeared.

OK, closed.

Thanks,
Rafael
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo DeleteThis @vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

Rafael J. Wysocki · External Since: May 20, 2006 Posts: 1721

On Friday 02 October 2009, Tetsuo Handa wrote:
> 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.
> This memory leak might exist in all releases since 23 Sep 2005.
> http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=com...diff;h=
> >
> > 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).
> As of now, the patch is not yet merged into Linus's tree.
> It still should be listed.
> >
> > Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=14258
> > Subject : Memory leak in SCSI initialization
> > Submitter : Tetsuo Handa <penguin-kernel.DeleteThis@i-love.sakura.ne.jp>
> > Date : 2009-09-22 4:18 (10 days old)
> > References : http://marc.info/?l=linux-kernel&m=125359311312243&w=4
> > Handled-By : Michael Ellerman <michael.DeleteThis@ellerman.id.au>
> > Patch : http://patchwork.kernel.org/patch/49258/

Thanks for the update.

Rafael
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo.DeleteThis@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

Bruno Prémont · External Since: Mar 21, 2009 Posts: 4

On Thu, 01 October 2009 "Rafael J. Wysocki" <rjw.DeleteThis@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=13942
> Subject : Troubles with AoE and uninitialized object
> Submitter : Bruno Prémont <bonbons.DeleteThis@linux-vserver.org>
> Date : 2009-08-04 10:12 (59 days old)
> References : http://marc.info/?l=linux-kernel&m=124938117104811&w=4

This should have been fixed with commits:

18d8217bc441630c3c5ec7416c5a65c69e8a0979
aoe: end barrier bios with EOPNOTSUPP

This addresses the trace on unmounting XFS

7135a71b19be1faf48b7148d77844d03bc0717d6
aoe: allocate unused request_queue for sysfs

This addresses the NULL kobject part

I think the second one made it into 2.6.31 but first one didn't,
please double-check! I've not seen them on stable though (which might
be worth especially for the first one)

Bruno
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo.DeleteThis@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

Bruno Prémont · External Since: Mar 21, 2009 Posts: 4

On Thu, 01 October 2009 "Rafael J. Wysocki" <rjw RemoveThis @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=13950
> Subject : Oops when USB Serial disconnected while in
> use Submitter : Bruno Prémont <bonbons RemoveThis @linux-vserver.org>
> Date : 2009-08-08 17:47 (55 days old)
> References : http://marc.info/?l=linux-kernel&m=124975432900466&w=4
> Handled-By : Alan Stern <stern RemoveThis @rowland.harvard.edu>

This has been adressed with following commits:
41bd34ddd7aa46dbc03b5bb33896e0fa8100fe7b
usb-serial: change referencing of port and serial structures

f5b0953a89fa3407fb293cc54ead7d8feec489e4
usb-serial: put subroutines in logical order

8bc2c1b2daf95029658868cb1427baea2da87139
usb-serial: change logic of serial lookups

cc56cd0157753c04a987888a2f793803df661a40
usb-serial: acquire references when a new tty is installed

7e29bb4b779f4f35385e6f21994758845bf14d23
usb-serial: fix termios initialization logic

74556123e034c8337b69a3ebac2f3a5fc0a97032
usb-serial: rename subroutines

ff8324df1187b7280e507c976777df76c73a1ef1
usb-serial: add missing tests and debug lines

320348c8d5c9b591282633ddb8959b42f7fc7a1c
usb-serial: straighten out serial_open

They went into 2.6.32-rc1 and are probably queued for 2.6.31.2 stable.

Bruno
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo RemoveThis @vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

Karol Lewandowski · External Since: Oct 02, 2009 Posts: 8

On Fri, Oct 02, 2009 at 10:32:26AM +0100, Mel Gorman wrote:
> On Fri, Oct 02, 2009 at 11:11:52AM +0200, Frans Pop wrote:
> > My own feeling is that Bartlomiej is correct and that something has changed
> > since .29 and that on average we do have less higher order areas available
> > after the system has been in use for some time, but I can't substantiate
> > that. I do know that before .30 I had never seen the SKB allocation
> > errors.
> >
> > Main problem is that it's hard to deliberately and reproducibly get the
> > system in a state where the errors occur.
> >
>
> Apparently, Karol Lewandowski (cc added) has a reliable
> reproduction case for when the firmware loading problem occurs
> (http://lkml.org/lkml/2009/9/30/242). While it's not the same problem exactly,
> it's probable they're related. I'm hoping the problem commit can be identified
> by his bisection whenever he gets around to it.

Unfortunately, I've had little success with bisecting this problem.
I've spend fair amount of time today trying to reproduce this problem,
but I'm unable to do so even on kernels that failed "easily" before.

Nothing has changed in hardware/software. I've changed methodology
somewhat from suspend-and-look-for-failure-on-resume to rmmod, fill
memory, modprobe-and-see-it-fail... but well, few days ago it failed
in either case.

Damn.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo RemoveThis @vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/