Bug 5710 - First boot locked - kernel call trace in syslog - RC PreRelease DVD 64
Summary: First boot locked - kernel call trace in syslog - RC PreRelease DVD 64
Status: RESOLVED FIXED
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: x86_64 Linux
Priority: Normal critical
Target Milestone: ---
Assignee: Thomas Backlund
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-05-01 17:50 CEST by claire robinson
Modified: 2012-07-06 18:36 CEST (History)
0 users

See Also:
Source RPM: kernel
CVE:
Status comment:


Attachments
/var/log/kernel/errors.log (507 bytes, text/plain)
2012-05-01 17:55 CEST, claire robinson
Details
the complete syslog (216.01 KB, text/plain)
2012-05-01 17:56 CEST, claire robinson
Details

Description claire robinson 2012-05-01 17:50:51 CEST
This was with a default gnome installation into virtualbox.

Hard locked starting gnome classic desktop at first log in. Logged in at gdm classic, ended with a spinning cursor which stopped spinning. Had to reset.

Found kernel Call Trace in syslog after managing to boot, sorry for the paste..

May  1 16:16:36 localhost kernel: [   70.989492] ppdev0: no associated port!
May  1 16:17:05 localhost gnome-session[1617]: WARNING: Application 'metacity.desktop' failed to register before timeout
May  1 16:17:35 localhost kernel: [  129.519078] INFO: rcu_sched detected stalls on CPUs/tasks: { 1} (detected by 0, t=60002 jiffies)
May  1 16:17:35 localhost kernel: [  129.519097] Pid: 0, comm: swapper/0 Tainted: G           O 3.3.4-desktop-1.mga2 #1
May  1 16:17:35 localhost kernel: [  129.519100] Call Trace:
May  1 16:17:35 localhost kernel: [  129.519107]  <IRQ>  [<ffffffff810d3613>] __rcu_pending+0x3a3/0x3f0
May  1 16:17:35 localhost kernel: [  129.519183]  [<ffffffff810d3ac0>] rcu_check_callbacks+0xb0/0x1b0
May  1 16:17:35 localhost kernel: [  129.519203]  [<ffffffff8105f128>] update_process_times+0x48/0x90
May  1 16:17:35 localhost kernel: [  129.519222]  [<ffffffff810a2eb4>] tick_sched_timer+0x64/0xc0
May  1 16:17:35 localhost kernel: [  129.519237]  [<ffffffff81074e20>] __run_hrtimer+0x70/0x1e0
May  1 16:17:35 localhost kernel: [  129.519240]  [<ffffffff810a2e50>] ? tick_nohz_handler+0xf0/0xf0
May  1 16:17:35 localhost kernel: [  129.519246]  [<ffffffff8107578b>] hrtimer_interrupt+0xeb/0x210
May  1 16:17:35 localhost kernel: [  129.519266]  [<ffffffff81032709>] smp_apic_timer_interrupt+0x69/0xa0
May  1 16:17:35 localhost kernel: [  129.519303]  [<ffffffff81461b1e>] apic_timer_interrupt+0x6e/0x80
May  1 16:17:35 localhost kernel: [  129.519305]  <EOI>  [<ffffffff81083de5>] ? sched_clock_local+0x25/0x90
May  1 16:17:35 localhost kernel: [  129.519323]  [<ffffffff8103ad16>] ? native_safe_halt+0x6/0x10
May  1 16:17:35 localhost kernel: [  129.519337]  [<ffffffff8101c773>] default_idle+0x53/0x1d0
May  1 16:17:35 localhost kernel: [  129.519346]  [<ffffffff81013239>] cpu_idle+0xd9/0x120
May  1 16:17:35 localhost kernel: [  129.519360]  [<ffffffff81434d7e>] rest_init+0x72/0x74
May  1 16:17:35 localhost kernel: [  129.519407]  [<ffffffff81ab7bfd>] start_kernel+0x3bf/0x3ca
May  1 16:17:35 localhost kernel: [  129.519437]  [<ffffffff81ab7346>] x86_64_start_reservations+0x131/0x135
May  1 16:17:35 localhost kernel: [  129.519440]  [<ffffffff81ab7140>] ? early_idt_handlers+0x140/0x140
May  1 16:17:35 localhost kernel: [  129.519443]  [<ffffffff81ab744c>] x86_64_start_kernel+0x102/0x111
Comment 1 claire robinson 2012-05-01 17:55:51 CEST
Created attachment 2147 [details]
/var/log/kernel/errors.log
Comment 2 claire robinson 2012-05-01 17:56:53 CEST
Created attachment 2148 [details]
the complete syslog
Comment 3 Marja Van Waes 2012-05-26 13:02:43 CEST
Hi,

This bug was filed against cauldron, but we do not have cauldron at the moment.

Please report whether this bug is still valid for Mageia 2.

Thanks :)

Cheers,
marja

Keywords: (none) => NEEDINFO

Comment 4 claire robinson 2012-07-06 18:36:33 CEST
This no longer seems valid.

Closing

Keywords: NEEDINFO => (none)
Status: NEW => RESOLVED
Resolution: (none) => FIXED


Note You need to log in before you can comment on or make changes to this bug.