[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20130821194357.GA22587@electric-eye.fr.zoreil.com>
Date: Wed, 21 Aug 2013 21:43:57 +0200
From: Francois Romieu <romieu@...zoreil.com>
To: Anton Arapov <anton@...hat.com>
Cc: "Theodore Ts'o" <tytso@....edu>,
Greg KH <gregkh@...uxfoundation.org>,
ksummit-2013-discuss@...ts.linuxfoundation.org,
linux-kernel@...r.kernel.org
Subject: Re: [ATTEND] oops.kernel.org prospect
Anton Arapov <anton@...hat.com> :
[...]
> Oh well,... I didn't have a time for this right now, nor project is
> not exactly in the state I'm willing to show (mostly webui)
I have sorted the r8169 oopses by kernel revision to start with the most
recent kernels. I don't get why the r8169 driver appears in the
"Caused by:" field when
- the bug is about "scheduling while atomic: Xorg/3042/0×00000001"
- the kernel is PDWO with fglrx
- r8169 appears in the module list, nowhere else (not even the oops)
I tried :
http://oops.kernel.org/browse-reports/?c=1&d=1&oopsclass=default&oopstype=default&distro=default&module=&driver=r8169&function=&file=&bugline=&kernel=&tainted=true&search=submit
(0 answer if Stack, Registers or Disassembled code is added)
("tainted=true" while "Untainted only" was asked for, huh ?)
The answers contains:
http://oops.kernel.org/browse-reports/oops-detail/?id=29778
and
http://oops.kernel.org/browse-reports/oops-detail/?id=29856
I can't even find the "r8169" word in those.
Is it the currently expected behavior ?
--
Ueimor
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists