Re: [Bug #14656] Oops at __rmqueue+0x98 with 2.6.32-rc6

2010-02-24 Thread Christian Kujau
Lucas, On Sun, 21 Feb 2010 at 22:42, Rafael J. Wysocki wrote: Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=14656 Subject : Oops at __rmqueue+0x98 with 2.6.32-rc6 References : http://marc.info/?l=linux-kernelm=125860255229092w=4 Your initial report said: kernel:

[Bug #14656] Oops at __rmqueue+0x98 with 2.6.32-rc6

2010-02-21 Thread Rafael J. Wysocki
This message has been generated automatically as a part of a report of regressions introduced between 2.6.31 and 2.6.32. The following bug entry is on the current list of known regressions introduced between 2.6.31 and 2.6.32. Please verify if it still should be listed and let the tracking team

[Bug #14656] Oops at __rmqueue+0x98 with 2.6.32-rc6

2010-02-07 Thread Rafael J. Wysocki
This message has been generated automatically as a part of a report of regressions introduced between 2.6.31 and 2.6.32. The following bug entry is on the current list of known regressions introduced between 2.6.31 and 2.6.32. Please verify if it still should be listed and let the tracking team

[Bug #14656] Oops at __rmqueue+0x98 with 2.6.32-rc6

2010-01-10 Thread Rafael J. Wysocki
This message has been generated automatically as a part of a report of regressions introduced between 2.6.31 and 2.6.32. The following bug entry is on the current list of known regressions introduced between 2.6.31 and 2.6.32. Please verify if it still should be listed and let me know (either

[Bug #14656] Oops at __rmqueue+0x98 with 2.6.32-rc6

2009-12-29 Thread Rafael J. Wysocki
This message has been generated automatically as a part of a report of regressions introduced between 2.6.31 and 2.6.32. The following bug entry is on the current list of known regressions introduced between 2.6.31 and 2.6.32. Please verify if it still should be listed and let me know (either

[Bug #14656] Oops at __rmqueue+0x98 with 2.6.32-rc6

2009-11-21 Thread 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.31. Please verify if it still should be listed and let me know (either way). Bug-Entry :