Ubuntu
linux-source-2.6.20 package

soft lockup during install wizard for missing java in firefox

Bug #132173 reported by Liam O'Reilly
4
Affects Status Importance Assigned to Milestone
linux-source-2.6.20 (Ubuntu)
Fix Released
Undecided
Unassigned

Bug Description

Binary package hint: linux-source-2.6.20

Description:
when using firefox to check java installation at java.sun.com and using firefox wizard to try and install missing java plugin, the system had a soft lockup.

Step to reproduce:
1) Stat firefox
2) Visit http://java.com/en/download/installed.jsp?detect=jre&try=1 which will check if java is installed correctly
3) Page comes back with install instructions, but firefox requests confirmation of installing "missing plugins"

Expected result:
Page to come back and say: Java not installed with instructions how to install.

Actual Results:
Page displaying spinning green circle, spinning green circle never finished and believed to have caused soft lockup. Screen froze, caps lock failed to toggle. Machine was responsive to ping. Then it came back alive.

How reproducible is this problem:
I have been unable to reproduce this problem since.

Additional Information:
This appeared in dmesg:
[ 201.200814] BUG: soft lockup detected on CPU#1!
[ 201.200823]
[ 201.200824] Call Trace:
[ 201.200828] <IRQ> [<ffffffff802bc34a>] softlockup_tick+0xfa/0x120
[ 201.200863] [<ffffffff80211c9f>] __do_softirq+0x5f/0xd0
[ 201.200875] [<ffffffff80299277>] update_process_times+0x57/0x90
[ 201.200887] [<ffffffff8027a664>] smp_local_timer_interrupt+0x34/0x60
[ 201.200895] [<ffffffff8027ade9>] smp_apic_timer_interrupt+0x59/0x80
[ 201.200906] [<ffffffff80261ce6>] apic_timer_interrupt+0x66/0x70
[ 201.200911] <EOI> [<ffffffff80234d16>] do_setitimer+0x76/0x4c0
[ 201.200942] [<ffffffff80234d6f>] do_setitimer+0xcf/0x4c0
[ 201.200957] [<ffffffff802938e2>] sys_setitimer+0xb2/0xd0
[ 201.200980] [<ffffffff8026111e>] system_call+0x7e/0x83
[ 201.201003]
[ 201.201007] BUG: soft lockup detected on CPU#0!
[ 201.201011]
[ 201.201013] Call Trace:
[ 201.201016] <IRQ> [<ffffffff802bc34a>] softlockup_tick+0xfa/0x120
[ 201.201038] [<ffffffff80299277>] update_process_times+0x57/0x90
[ 201.201049] [<ffffffff8027a664>] smp_local_timer_interrupt+0x34/0x60
[ 201.201057] [<ffffffff8027ade9>] smp_apic_timer_interrupt+0x59/0x80
[ 201.201067] [<ffffffff80261ce6>] apic_timer_interrupt+0x66/0x70
[ 201.201076] [<ffffffff80319f90>] dummy_task_kill+0x0/0x10
[ 201.201094] [<ffffffff80267b48>] _spin_unlock_irqrestore+0x8/0x10
[ 201.201106] [<ffffffff803bb6bd>] serio_interrupt+0x7d/0xa0
[ 201.201119] [<ffffffff803bc506>] i8042_interrupt+0x226/0x250
[ 201.201135] [<ffffffff80210769>] handle_IRQ_event+0x29/0x60
[ 201.201147] [<ffffffff802be0e9>] handle_edge_irq+0xf9/0x150
[ 201.201153] [<ffffffff8028ba1c>] task_rq_lock+0x4c/0x90
[ 201.201164] [<ffffffff80270189>] do_IRQ+0x89/0x100
[ 201.201174] [<ffffffff80261631>] ret_from_intr+0x0/0xa
[ 201.201182] [<ffffffff80319f90>] dummy_task_kill+0x0/0x10
[ 201.201200] [<ffffffff80267b48>] _spin_unlock_irqrestore+0x8/0x10
[ 201.201212] [<ffffffff8025dbde>] group_send_sig_info+0x6e/0x90
[ 201.201227] [<ffffffff8029b825>] send_group_sig_info+0x35/0x50
[ 201.201237] [<ffffffff80293c4b>] it_real_fn+0x2b/0x70
[ 201.201242] [<ffffffff80298eb9>] do_timer+0x99/0x360
[ 201.201247] [<ffffffff80293c20>] it_real_fn+0x0/0x70
[ 201.201255] [<ffffffff80251673>] hrtimer_run_queues+0x103/0x160
[ 201.201267] [<ffffffff80298ac3>] run_timer_softirq+0x23/0x1c0
[ 201.201272] [<ffffffff802714ab>] main_timer_handler+0x1fb/0x420
[ 201.201286] [<ffffffff80211c9f>] __do_softirq+0x5f/0xd0
[ 201.201299] [<ffffffff8026223c>] call_softirq+0x1c/0x28
[ 201.201308] [<ffffffff8027009c>] do_softirq+0x2c/0x90
[ 201.201316] [<ffffffff8027adee>] smp_apic_timer_interrupt+0x5e/0x80
[ 201.201326] [<ffffffff80261ce6>] apic_timer_interrupt+0x66/0x70
[ 201.201331] <EOI> [<ffffffff88030945>] :processor:acpi_processor_idle+0x286/0x485
[ 201.201374] [<ffffffff8803093b>] :processor:acpi_processor_idle+0x27c/0x485
[ 201.201380] [<ffffffff80265391>] __sched_text_start+0x1/0x82b
[ 201.201392] [<ffffffff880306bf>] :processor:acpi_processor_idle+0x0/0x485
[ 201.201403] [<ffffffff8024b15b>] cpu_idle+0x9b/0xd0
[ 201.201414] [<ffffffff805707ca>] start_kernel+0x24a/0x260
[ 201.201424] [<ffffffff80570163>] _sinittext+0x163/0x170
[ 201.201434]

Version information:
Kernal version 2.6.20-16-generic (feisty)

Revision history for this message
Ralph Janke (txwikinger) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. Unfortunately we can't fix it, because your description does not yet have enough information.
Could you please check if this problem still occurs in the newest hardy kernel.
Please include the following additional information, if you have not already done so (pay attention to lspci's additional options), as required by the Ubuntu Kernel Team:
  1. Please include the output of the command "uname -a" in your next response. It should be one, long line of text which includes the exact kernel version you're running, as well as the CPU architecture.
  2. Please run the command "dmesg > dmesg.log" after a fresh boot and attach the resulting file "dmesg.log" to this bug report.
  3. Please run the command "sudo lspci -vvnn > lspci-vvnn.log" and attach the resulting file "lspci-vvnn.log" to this bug report.
  4. Please run the command "cat /proc/version_signature > version.log" and attach the resulting file "lspci-vvnn.log" to this bug report.
For your reference, the full description of procedures for kernel-related bug reports is available at http://wiki.ubuntu.com/KernelTeamBugPolicies. Thanks in advance!

Changed in linux-source-2.6.20:
assignee: nobody → txwikinger
status: New → Incomplete
Revision history for this message
Liam O'Reilly (aliam13-2) wrote :

Unfortunately I have already upgraded to Gutsy Gibbon, I could not reproduce the bug in Feisty. I have tried to reproduce it in Gutsy - but have been unable to.

uname -a output:
Linux liam-laptop 2.6.22-14-generic #1 SMP Tue Feb 12 02:46:46 UTC 2008 x86_64 GNU/Linux

I will post the files resulted, but I believe we will never get to the bottom of this bug.

Revision history for this message
Liam O'Reilly (aliam13-2) wrote :

dmesg log as requested

Revision history for this message
Liam O'Reilly (aliam13-2) wrote :

result of lspci--vvnn as requested

Revision history for this message
Liam O'Reilly (aliam13-2) wrote :

result of cat /proc/version_signature as requested.

Again I can not reproduce this bug.

Revision history for this message
Ralph Janke (txwikinger) wrote :

I am closing this report as fixed since it cannot be reproduce in kernel 2.6.22-14-generic on gutsy. Please feel free to re-open this report if there is information available that allows us to reproduce this problem.

Thanks

Changed in linux-source-2.6.20:
assignee: txwikinger → nobody
status: Incomplete → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.