1:51 a.m.
Just for knowledge, it boots fine.
Already looked at:
http://www.tux.org/lkml/#s1-18
WARNING: CPU: 0 PID: 1730 at lib/idr.c:527
idr_remove.part.6+0x243/0x250()
idr_remove called for id=94 which is not allocated.
Cannot report due to tainted kernel,
can this happen without proprietary stuff (nvidia etc..?
CPU: 0 PID: 1730 Comm: systemd Tainted: G W
3.13.0-0.rc7.git0.2.fc21.x86_64 #1 Hardware name: Gigabyte Technology
Co., Ltd. To be filled by O.E.M./H61MA-D2V, BIOS F6 04/17/2013
___
Regards,
Frank
www.frankly3d.com
2:14 a.m.
On Mon, 2014-01-13 at 07:51 +0000, Frank Murphy wrote:
Cannot report due to tainted kernel,
can this happen without proprietary stuff (nvidia etc..?
Sure, see Documentation/oops-tracing.txt in the kernel sources.
CPU: 0 PID: 1730 Comm: systemd Tainted: G W
'G' if all modules loaded have a GPL or compatible license [...]
'W' if a warning has previously been issued by the kernel. [...]
And I don't think the 'W' flag alone is reason to never report this. But
I would try first to see what happened before the WARNING you quoted
(partially, it seems) was triggered and set that flag.
Paul Bolle
8:56 a.m.
On 01/13/2014 02:51 AM, Frank Murphy wrote:
Just for knowledge, it boots fine.
Already looked at:
http://www.tux.org/lkml/#s1-18
WARNING: CPU: 0 PID: 1730 at lib/idr.c:527
idr_remove.part.6+0x243/0x250()
idr_remove called for id=94 which is not allocated.
Cannot report due to tainted kernel,
can this happen without proprietary stuff (nvidia etc..?
CPU: 0 PID: 1730 Comm: systemd Tainted: G W
3.13.0-0.rc7.git0.2.fc21.x86_64 #1 Hardware name: Gigabyte Technology
Co., Ltd. To be filled by O.E.M./H61MA-D2V, BIOS F6 04/17/2013
The warning above is what kicked the "W" taint:
static void idr_remove_warning(int id)
{
WARN(1, "idr_remove called for id=%d which is not allocated.\n", id);
}
Yes, this can happen without proprietary stuff. The issue is that it looks like
something that is using the idr allocation scheme is busted. Any chance you
have a better log than the snippet you posted above (ie, dmesg?)
You should open up a BZ.
P.
___
Regards,
Frank
www.frankly3d.com
_______________________________________________
kernel mailing list
kernel(a)lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/kernel
9:07 a.m.
On Mon, 13 Jan 2014 09:56:28 -0500
Prarit Bhargava <prarit(a)redhat.com> wrote:
The warning above is what kicked the "W" taint:
static void idr_remove_warning(int id)
{
WARN(1, "idr_remove called for id=%d which is not
allocated.\n", id); }
Yes, this can happen without proprietary stuff. The issue is that it
looks like something that is using the idr allocation scheme is
busted. Any chance you have a better log than the snippet you posted
above (ie, dmesg?)
You should open up a BZ.
I have the whole abrt folder with backtrace & friends
But should I wait until it happens a number of times.
___
Regards,
Frank
www.frankly3d.com
9:26 a.m.
On Mon, 13 Jan 2014 09:56:28 -0500
Prarit Bhargava <prarit(a)redhat.com> wrote:
You should open up a BZ.
Think this is it: ## close enough
https://bugzilla.redhat.com/show_bug.cgi?id=1045755
___
Regards,
Frank
www.frankly3d.com
3758
days inactive
3763
days old
kernel@lists.fedoraproject.org
5 comments
4 participants
participants (4)
-
David Timothy Strauss -
Frank Murphy -
Paul Bolle -
Prarit Bhargava