Laptop not booting, utrace?

[kurtdriver]

This is far as it gets.

cryptomgr_test used greatest stack depth: 5968 bytes left
I had just updated to F14 and then after a update installed fedora-release-rawhide. I don't understand that error message at all.
Even after commenting out the new kernel, it doesn't boot, it just stops here. Is there a way to avoid re-installing? I've done it so many times on this infernal machine. Thanks, Kurt
There is a bug (https://bugzilla.redhat.com/show_bug.cgi?id=625077) and a suggestion that it's something to do with utrace.

[andrewthomas]

try kernel-2.6.36-0.0.rc0.git1.fc15

http://koji.fedoraproject.org/koji/buildinfo?buildID=188293

[kurtdriver]

Thanks, how do I install it? The computer doesn't boot with any of the three kernels.

[karo1170]

Thanks, how do I install it? The computer doesn't boot with any of the three kernels.

May be the following works on your machine?

1. Boot with a live-cd
2. Download the rpm for the kernel from koji
3. Mount /
4. chroot and install the kernel rpm.
5. modify grub (menue.lst) and reboot

Cordialement
karo

[dd_wizard]

The change log for
[gene@Mobile-PC ~]$ uname -sr
Linux 2.6.36-0.6.rc1.git3.fc15.x86_64
says that the utrace problem is fixed, and indeed, it boots for me. However, I got three kernel oops and can't report them because of dbus problems. :( So there appear to be other issues.

dd_wizard

[andrewthomas]

Linux 2.6.36-0.6.rc1.git3.fc15.x86_64 also does boot for me but I am still getting this:
(but have been getting as far back as 2.6.34-0.38.rc5.git0.fc14.x86_64)kernel: CPU0: AMD Phenom(tm) 9500 Quad-Core Processor stepping 02
kernel: NMI watchdog enabled, takes one hw-pmu counter.
kernel: lockdep: fixing up alternatives.
kernel:
kernel: ================================================== =
kernel: [ INFO: suspicious rcu_dereference_check() usage. ]
kernel: ---------------------------------------------------
kernel: kernel/sched.c:618 invoked rcu_dereference_check() without protection!
kernel:
kernel: other info that might help us debug this:
kernel:
kernel:
kernel: rcu_scheduler_active = 1, debug_locks = 0
kernel: 3 locks held by kworker/0:0/4:
kernel: #0: (events){+.+.+.}, at: [<ffffffff81067e11>] process_one_work+0x160/0x2ec
kernel: #1: ((&c_idle.work)){+.+.+.}, at: [<ffffffff81067e11>] process_one_work+0x160/0x2ec
kernel: #2: (&rq->lock){-.....}, at: [<ffffffff81490279>] init_idle+0x30/0x131
kernel:
kernel: stack backtrace:
kernel: Pid: 4, comm: kworker/0:0 Not tainted 2.6.36-0.6.rc1.git3.fc15.x86_64 #1
kernel: Call Trace:
kernel: [<ffffffff8107d944>] lockdep_rcu_dereference+0xaa/0xb3
kernel: [<ffffffff810401ce>] task_group+0x80/0x8f
kernel: [<ffffffff810401f4>] set_task_rq+0x17/0x73
kernel: [<ffffffff81490333>] init_idle+0xea/0x131
kernel: [<ffffffff81490703>] fork_idle+0x92/0xa3
kernel: [<ffffffff8101050d>] ? sched_clock+0x9/0xd
kernel: [<ffffffff8148e17c>] do_fork_idle+0x1c/0x2d
kernel: [<ffffffff81067e6d>] process_one_work+0x1bc/0x2ec
kernel: [<ffffffff81067e11>] ? process_one_work+0x160/0x2ec
kernel: [<ffffffff8148e160>] ? do_fork_idle+0x0/0x2d
kernel: [<ffffffff81068d6c>] ? manage_workers.clone.9+0xe0/0x173
kernel: [<ffffffff81068f03>] worker_thread+0x104/0x19b
kernel: [<ffffffff81068dff>] ? worker_thread+0x0/0x19b
kernel: [<ffffffff8106c84c>] kthread+0x9d/0xa5
kernel: [<ffffffff8100aae4>] kernel_thread_helper+0x4/0x10
kernel: [<ffffffff81498150>] ? restore_args+0x0/0x30
kernel: [<ffffffff8106c7af>] ? kthread+0x0/0xa5
kernel: [<ffffffff8100aae0>] ? kernel_thread_helper+0x0/0x10
kernel: Booting Node 0, Processors #1
kernel: NMI watchdog enabled, takes one hw-pmu counter.
kernel: lockdep: fixing up alternatives.
kernel: #2
kernel: NMI watchdog enabled, takes one hw-pmu counter.
kernel: lockdep: fixing up alternatives.
kernel: #3
kernel: NMI watchdog enabled, takes one hw-pmu counter
also during the plymouth splash I got a bunch of corruption (about 1/4 of the screen black) but it seems to work ok

[dd_wizard]

I've seen that [ INFO: suspicious rcu_dereference_check() usage. ] error off and on since the 2.6.32 or .33 kernel. I'm getting it now with the latest 2.6.35 kernel as well. Bug 610967 (https://bugzilla.redhat.com/show_bug.cgi?id=610967) is open against the 2.6.35 kernel.

dd_wizard

[andrewthomas]

I've seen that [ INFO: suspicious rcu_dereference_check() usage. ] error off and on since the 2.6.32 or .33 kernel. I'm getting it now with the latest 2.6.35 kernel as well. Bug 610967 (https://bugzilla.redhat.com/show_bug.cgi?id=610967) is open against the 2.6.35 kernel.

dd_wizard

Thanks for the bug #. Do you get any screen corruption during the plymouth splash with kernel-2.6.36-0.6.rc1.git3.fc15.x86_64?

[dd_wizard]

I didn't notice, I always boot without the plymouth splash screen. After getting repeated kernel oops for my wifi, I switched back to the 2.6.35 kernel.

dd_wizard

[kurtdriver]

May be the following works on your machine?

1. Boot with a live-cd
2. Download the rpm for the kernel from koji
3. Mount /
4. chroot and install the kernel rpm.
5. modify grub (menue.lst) and reboot

Cordialement
karo
Merci, Karo.
I chrooted to /mount/3002345...etc and installed the 2.6.36.05 kernel. After a couple of hours wrestling with grub.conf, grub started loading the new kernel and voila, the same error message. I'll wrestle with it again after work tomorrow night.

dd_wizard, where'd you get the 2.6.36-0.6.rc1.git3.fc15.x86_64 from? I searched koji and "no search results".

[andrewthomas]

dd_wizard, where'd you get the 2.6.36-0.6.rc1.git3.fc15.x86_64 from? .

kernel-2.6.36-0.6.rc1.git3.fc15
http://koji.fedoraproject.org/koji/buildinfo?buildID=191339