Re: Top 10 kernel oopses for the week ending January 12th, 2008

2008-01-15 Thread Jiri Kosina
On Sun, 13 Jan 2008, Adrian Bunk wrote: > > Rank 1: implement (hid code) > > WARN_ON at drivers/hid/hid-core.c:784 > > Reported 23 times (39 total reports) > > This appears to be the kernel doing a WARN_ON based on unexpected > > ioctl() arguments > > More info:

Re: Top 10 kernel oopses for the week ending January 12th, 2008

2008-01-15 Thread Jiri Kosina
On Sun, 13 Jan 2008, Adrian Bunk wrote: Rank 1: implement (hid code) WARN_ON at drivers/hid/hid-core.c:784 Reported 23 times (39 total reports) This appears to be the kernel doing a WARN_ON based on unexpected ioctl() arguments More info:

Re: Top 10 kernel oopses for the week ending January 12th, 2008

2008-01-12 Thread Arjan van de Ven
Adrian Bunk wrote: On Sat, Jan 12, 2008 at 03:13:29PM -0800, Arjan van de Ven wrote: Adrian Bunk wrote: All the other reports only contain the plain trace. Is there any way to get more information whether the former is a pattern or not, and to get this information somehow displayed on the

Re: Top 10 kernel oopses for the week ending January 12th, 2008

2008-01-12 Thread Adrian Bunk
On Sat, Jan 12, 2008 at 03:13:29PM -0800, Arjan van de Ven wrote: > Adrian Bunk wrote: >> >> All the other reports only contain the plain trace. Is there any way to >> get more information whether the former is a pattern or not, and to >> get this information somehow displayed on the webpage? > >

Re: Top 10 kernel oopses for the week ending January 12th, 2008

2008-01-12 Thread Arjan van de Ven
Adrian Bunk wrote: All the other reports only contain the plain trace. Is there any way to get more information whether the former is a pattern or not, and to get this information somehow displayed on the webpage? IF the kernel prints that its tainted or whatever it'll be shown, as well as

Re: Top 10 kernel oopses for the week ending January 12th, 2008

2008-01-12 Thread Adrian Bunk
On Sat, Jan 12, 2008 at 10:48:05AM -0800, Arjan van de Ven wrote: > The http://www.kerneloops.org website collects kernel oops and > warning reports from various mailing lists and bugzillas as well as > with a client users can install to auto-submit oopses. > Below is a top 10 list of the oopses

Top 10 kernel oopses for the week ending January 12th, 2008

2008-01-12 Thread Arjan van de Ven
The http://www.kerneloops.org website collects kernel oops and warning reports from various mailing lists and bugzillas as well as with a client users can install to auto-submit oopses. Below is a top 10 list of the oopses collected in the last 7 days. (Reports prior to 2.6.23 have been omitted

Top 10 kernel oopses for the week ending January 12th, 2008

2008-01-12 Thread Arjan van de Ven
The http://www.kerneloops.org website collects kernel oops and warning reports from various mailing lists and bugzillas as well as with a client users can install to auto-submit oopses. Below is a top 10 list of the oopses collected in the last 7 days. (Reports prior to 2.6.23 have been omitted

Re: Top 10 kernel oopses for the week ending January 12th, 2008

2008-01-12 Thread Arjan van de Ven
Adrian Bunk wrote: All the other reports only contain the plain trace. Is there any way to get more information whether the former is a pattern or not, and to get this information somehow displayed on the webpage? IF the kernel prints that its tainted or whatever it'll be shown, as well as

Re: Top 10 kernel oopses for the week ending January 12th, 2008

2008-01-12 Thread Adrian Bunk
On Sat, Jan 12, 2008 at 03:13:29PM -0800, Arjan van de Ven wrote: Adrian Bunk wrote: All the other reports only contain the plain trace. Is there any way to get more information whether the former is a pattern or not, and to get this information somehow displayed on the webpage? IF the