Bug 607411
Summary: | kernel bug: installing rhel3.9 occasionally throws "kernel panic" error | ||||||||
---|---|---|---|---|---|---|---|---|---|
Product: | Red Hat Enterprise Linux 3 | Reporter: | Jianjiao Sun <jsun> | ||||||
Component: | kernel | Assignee: | Red Hat Kernel Manager <kernel-mgr> | ||||||
Status: | CLOSED WONTFIX | QA Contact: | Red Hat Kernel QE team <kernel-qe> | ||||||
Severity: | high | Docs Contact: | |||||||
Priority: | high | ||||||||
Version: | 3.9 | CC: | gyue, kcao, llim, mkenneth, rwu, shuang, tburke, virt-maint, xen-maint | ||||||
Target Milestone: | --- | ||||||||
Target Release: | --- | ||||||||
Hardware: | All | ||||||||
OS: | Linux | ||||||||
Whiteboard: | |||||||||
Fixed In Version: | Doc Type: | Bug Fix | |||||||
Doc Text: | Story Points: | --- | |||||||
Clone Of: | Environment: | ||||||||
Last Closed: | 2012-06-20 15:55:06 UTC | Type: | --- | ||||||
Regression: | --- | Mount Type: | --- | ||||||
Documentation: | --- | CRM: | |||||||
Verified Versions: | Category: | --- | |||||||
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||
Cloudforms Team: | --- | Target Upstream Version: | |||||||
Embargoed: | |||||||||
Attachments: |
|
Description
Jianjiao Sun
2010-06-24 03:40:01 UTC
This request was evaluated by Red Hat Product Management for inclusion in a Red Hat Enterprise Linux major release. Product Management has requested further review of this request by Red Hat Engineering, for potential inclusion in a Red Hat Enterprise Linux Major release. This request is not yet committed for inclusion. Probably not virt-manager related, reassigning to KVM for further triage. Which nic model are you using? Can you try with different nic? Gleb, I hit this error with rtl8139 nic. VM is rhel3.9-64bit with ide disk. Attached the screenshot. Created attachment 432012 [details]
kernel panic
(In reply to comment #7) > Created an attachment (id=432012) [details] > kernel panic code disassembles to: 0f 0b ud2a which is BUG(). The BUG is in add_timer() called from ide_timer_expiry(): BUG_ON(timer_pending(timer) || !timer->function); Code tries to add timer when one is still pending. Look like guest bug to me. any progress on this bug? make it block kvm bug tier2, and remove it later, if it is indeed a guest bug... it always happen on AMD host Call Trace: [<ffffffff8021979b>]{ide_set_handler+27} [<ffffffffa007a328>]{:ide-cd:cdrom_read_intr+856} [<ffffffff80131ef9>]{do_timer+41} [<ffffffff80116952>]{timer_interrupt+930} [<ffffffff8011f99c>]{wake_up_cpu+28} [<ffffffffa0079fd0>]{:ide-cd:cdrom_read_intr+0} [<ffffffff80126bd5>]{printk+485} [<ffffffff80110857>]{common_interrupt+95} [<ffffffff80221b60>]{ide_timer_expiry+0} [<ffffffff80221f5d>]{ide_intr+349} [<ffffffff8011f99c>]{wake_up_cpu+28} [<ffffffffa0079fd0>]{:ide-cd:cdrom_read_intr+0} [<ffffffff80221c92>]{ide_timer_expiry+306} [<ffffffff801325ec>]{timer_bh+684} [<ffffffff80110857>]{common_interrupt+95} [<ffffffff8012cfbf>]{bh_action+79} [<ffffffff8012ce6b>]{tasklet_hi_action+139} [<ffffffff8012cb3d>]{do_softirq+253} [<ffffffff801137a3>]{do_IRQ+339} [<ffffffff8010de20>]{default_idle+0} [<ffffffff8010de20>]{default_idle+0} [<ffffffff80110857>]{common_interrupt+95} <EOI> [<ffffffff8010de3e>]{default_idle+30} [<ffffffff8010de20>]{default_idle+0} [<ffffffff8010dec9>]{cpu_idle+73} Process swapper (pid: 0, stackpage=ffffffff80623000) Stack: ffffffff805effc0 0000000000000018 ffffffff8021979b 0000000000000092 ffffffffa007a328 000641900000029f 00000058d1b71759 0000000000000086 0000000000000086 ffffffff80131ef9 Call Trace: [<ffffffff8021979b>]{ide_set_handler+27} [<ffffffffa007a328>]{:ide-cd:cdrom_read_intr+856} [<ffffffff80131ef9>]{do_timer+41} [<ffffffff80116952>]{timer_interrupt+930} [<ffffffff8011f99c>]{wake_up_cpu+28} [<ffffffffa0079fd0>]{:ide-cd:cdrom_read_intr+0} [<ffffffff80126bd5>]{printk+485} [<ffffffff80110857>]{common_interrupt+95} [<ffffffff80221b60>]{ide_timer_expiry+0} [<ffffffff80221f5d>]{ide_intr+349} [<ffffffff8011f99c>]{wake_up_cpu+28} [<ffffffffa0079fd0>]{:ide-cd:cdrom_read_intr+0} [<ffffffff80221c92>]{ide_timer_expiry+306} [<ffffffff801325ec>]{timer_bh+684} [<ffffffff80110857>]{common_interrupt+95} [<ffffffff8012cfbf>]{bh_action+79} [<ffffffff8012ce6b>]{tasklet_hi_action+139} [<ffffffff8012cb3d>]{do_softirq+253} [<ffffffff801137a3>]{do_IRQ+339} [<ffffffff8010de20>]{default_idle+0} [<ffffffff8010de20>]{default_idle+0} [<ffffffff80110857>]{common_interrupt+95} <EOI> [<ffffffff8010de3e>]{default_idle+30} [<ffffffff8010de20>]{default_idle+0} [<ffffffff8010dec9>]{cpu_idle+73} Code: 0f 0b ab ce 2d 80 ff ff ff ff 3c 01 48 85 d2 74 13 0f 0b ab (In reply to comment #11) > it always happen on AMD host It always happen on AMD when you are doing what? (In reply to comment #12) > (In reply to comment #11) > > it always happen on AMD host I didn't meet kernel panic issue when install rhel3.9 on Intel host. > It always happen on AMD when you are doing what? rhel3.9 installation Thank you for submitting this issue for consideration in Red Hat Enterprise Linux. The release for which you requested us to review is now End of Life. Please See https://access.redhat.com/support/policy/updates/errata/ If you would like Red Hat to re-consider your feature request for an active release, please re-open the request via appropriate support channels and provide additional supporting details about the importance of this issue. |