On Thursday January 10, [EMAIL PROTECTED] wrote:
> On Thu, Jan 10, 2008 at 03:13:48PM +1100, Neil Brown wrote:
> > > What guarantees that it doesn't happen before we get to callback? AFAICS,
> > > nothing whatsoever...
> >
> > Yes, that's bad isn't it :-)
> >
> > I think I should be using sysfs_
On Thu, Jan 10, 2008 at 03:13:48PM +1100, Neil Brown wrote:
> > What guarantees that it doesn't happen before we get to callback? AFAICS,
> > nothing whatsoever...
>
> Yes, that's bad isn't it :-)
>
> I think I should be using sysfs_schedule_callback here. That makes the
> required 'get' and '
On Tuesday January 8, [EMAIL PROTECTED] wrote:
>
> FWIW, I'm going to go through Arjan's collection and post blow-by-blow
> analysis of some of those suckers. Tonight, probably...
>
> Let's take e.g. http://www.kerneloops.org/raw.php?rawid=2618
Thanks for that analysis.
...
>
> Humm... So we
Johannes Berg wrote:
Rank 1: __ieee80211_rx
Warning at net/mac80211/rx.c:1672
Reported 6 times (11 total reports)
Same issue that was ranked 2nd last week
Johannes has diagnosed this as a driver bug in the iwlwifi drivers
More info: http://www.kerneloops.or
> Rank 1: __ieee80211_rx
> Warning at net/mac80211/rx.c:1672
> Reported 6 times (11 total reports)
> Same issue that was ranked 2nd last week
> Johannes has diagnosed this as a driver bug in the iwlwifi drivers
> More info: http://www.kerneloops.org/search.php?search=
On Tuesday, 8 of January 2008, Linus Torvalds wrote:
>
> On Tue, 8 Jan 2008, Arjan van de Ven wrote:
> >
> > ok done; I had to fizzle a bit because some things aren't *exactly* a
> > BUG() statement but I track them anyway (things like the "sleeping in
> > invalid context" check), so I had to s
On Tue, 8 Jan 2008, Arjan van de Ven wrote:
>
> ok done; I had to fizzle a bit because some things aren't *exactly* a
> BUG() statement but I track them anyway (things like the "sleeping in
> invalid context" check), so I had to somewhat arbitrarily assign
> categories for those. I might fine
Linus Torvalds wrote:
On Tue, 8 Jan 2008, Arjan van de Ven wrote:
the database has the information so it's just a matter of slightly different
php code ;)
Before I do that... do you want the BUG's separate, part of the warnings or
part of the oopses?
(I rather make this change once ;)
I'd lik
On Tue, 8 Jan 2008, Arjan van de Ven wrote:
>
> the database has the information so it's just a matter of slightly different
> php code ;)
> Before I do that... do you want the BUG's separate, part of the warnings or
> part of the oopses?
> (I rather make this change once ;)
I'd like them all s
Linus Torvalds wrote:
Cool.
One thing I wonder about - could you separate out the bug-ons and warnings
from the oopses? They really are different issues, and an oops with
register information etc is very different from a BUG() with line numbers,
which in turn is very different from a WARN_ON(
On Tue, 8 Jan 2008, Arjan van de Ven wrote:
>
> I've made life easier for those using the www.kerneloops.org website;
> at least for x86 oopses the website now does this for you and shows
> the decoded Code: line in the raw oops data:
>
> http://www.kerneloops.org/raw.php?rawid=2716
Cool.
One
Randy Dunlap wrote:
(You can do it other and smarter ways too, I'm not claiming that's a
particularly good way to do it, and the old "ksymoops" program used to do
a pretty good job of this, but I'm used to that particular idiotic way
myself, since it's how I've basically always done it)
One
Linus Torvalds <[EMAIL PROTECTED]> writes:
>
> I usually just compile a small program like
Just use scripts/decodecode and cat the Code line into that.
> particularly good way to do it, and the old "ksymoops" program used to do
> a pretty good job of this, but I'm used to that particular idiotic
On Mon, 7 Jan 2008 19:26:12 -0800 (PST) Linus Torvalds wrote:
> On Mon, 7 Jan 2008, Kevin Winchester wrote:
>
> > J. Bruce Fields wrote:
> > >
> > > Is there any good basic documentation on this to point people at?
> >
> > I would second this question. I see people "decode" oops on lkml often
On 08-01-2008 06:59, Al Viro wrote:
> On Mon, Jan 07, 2008 at 07:26:12PM -0800, Linus Torvalds wrote:
>
>> I usually just compile a small program like
>>
>> const char array[]="\xnn\xnn\xnn...";
>>
>> int main(int argc, char **argv)
>> {
>> printf("%p\n", array);
>>
On Mon, Jan 07, 2008 at 07:26:12PM -0800, Linus Torvalds wrote:
> I usually just compile a small program like
>
> const char array[]="\xnn\xnn\xnn...";
>
> int main(int argc, char **argv)
> {
> printf("%p\n", array);
> *(int *)0=0;
> }
Heh. I
On Mon, 7 Jan 2008, Kevin Winchester wrote:
> J. Bruce Fields wrote:
> >
> > Is there any good basic documentation on this to point people at?
>
> I would second this question. I see people "decode" oops on lkml often
> enough, but I've never been entirely sure how its done. Is it somewhere
J. Bruce Fields wrote:
> On Sat, Jan 05, 2008 at 09:39:35PM +, Al Viro wrote:
>> On Sat, Jan 05, 2008 at 01:06:17PM -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 wit
On Sat, Jan 05, 2008 at 09:39:35PM +, Al Viro wrote:
> On Sat, Jan 05, 2008 at 01:06:17PM -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
On Sat, Jan 05, 2008 at 07:31:29PM -0800, Arjan van de Ven wrote:
> Andi Kleen wrote:
> >Arjan van de Ven <[EMAIL PROTECTED]> writes:
> >>Rank 4: remove_proc_entry
> >>Was also ranked 4th last week
> >>Only in tainted oopses
> >>Reported 3 times (12 total reports)
> >>More info:
>
Andi Kleen wrote:
Arjan van de Ven <[EMAIL PROTECTED]> writes:
Rank 4: remove_proc_entry
Was also ranked 4th last week
Only in tainted oopses
Reported 3 times (12 total reports)
More info: http://www.kerneloops.org/search.php?search=remove_proc_entry
Likely a br
Arjan van de Ven <[EMAIL PROTECTED]> writes:
>
> Rank 4: remove_proc_entry
> Was also ranked 4th last week
> Only in tainted oopses
> Reported 3 times (12 total reports)
> More info: http://www.kerneloops.org/search.php?search=remove_proc_entry
Likely a broken module_exit()
On Sat, Jan 05, 2008 at 01:06:17PM -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 co
On Sat, Jan 05, 2008 at 01:06:17PM -0800, Arjan van de Ven wrote:
> Rank 3: d_splice_alias
> NULL pointer deref
> Reported 3 times
> Happens in the isofs code
> Only seen in 2.6.24-rc5-mm1
> More info: http://www.kerneloops.org/search.php?search=d_splice_alias
in -rc6
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 in
25 matches
Mail list logo
