Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 242410
Summary: | FC7 random system freeze, libata? | ||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Rene Rattur <renerattur> | ||||||||
Component: | kernel | Assignee: | Jeff Garzik <jgarzik> | ||||||||
Status: | CLOSED CURRENTRELEASE | QA Contact: | Brian Brock <bbrock> | ||||||||
Severity: | high | Docs Contact: | |||||||||
Priority: | low | ||||||||||
Version: | 7 | CC: | cebbert, davej, peterm, renerattur, wljonespe | ||||||||
Target Milestone: | --- | ||||||||||
Target Release: | --- | ||||||||||
Hardware: | i686 | ||||||||||
OS: | Linux | ||||||||||
Whiteboard: | |||||||||||
Fixed In Version: | 2.6.21 | Doc Type: | Bug Fix | ||||||||
Doc Text: | Story Points: | --- | |||||||||
Clone Of: | Environment: | ||||||||||
Last Closed: | 2007-09-13 20:16:37 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: | |||||||||||
Bug Depends On: | |||||||||||
Bug Blocks: | 172490 | ||||||||||
Attachments: |
|
Description
Rene Rattur
2007-06-04 06:19:19 UTC
OK I get to different stack trace, the first one occurs during boot-up and the second one when in virtual terminal. 1) Call Trace: [<c04064da>] die+0x199/0x240 [<c04067d7>] do_divide_error+0x0/0xa8 [<c0406876>] do_divide_error+0x9f/0xa8 [<c060171d>] _spin_unlock_irqrestore+0x8/0x9 [<c041fab5>] __wake_up_common+0x32/0x55 [<c0420991>] complete+0x39/0x48 [<d88f80cd>] __ata_qc_complete+0x8c/0x92 [libata] [<d88f816c>] ata_qc_complete+0x99/0xa9 [libata] [<d88f86e6>] ata_hsm_qc_complete+0xb6/0xc1 [libata] [<c060190c>] error_code+0x7c/0x84 [<c060171d>] _spin_unlock_irqrestore+0x8/0x9 [<d88fc1c0>] ata_interrupt+0x1c5/0x1d7 [libata] [<c04521aa>] handle_IRQ_event+0x1a/0x3f [<c04535ea>] handle_level_irq+0x81/0xc7 [<c0453569>] handle_level_irq+0x0/0xc7 [<c04072bb>] do_IRQ+0xac/0xd1 [<c04058ff>] common_interrupt+0x23/0x28 Code: e2 ff 90 fe 06 79 09 f3 90 80 3b 00 7e f9 eb f2 5b c3 31 d2 86 10 31 c0 84 d2 0f 9f c0 c3 b2 01 86 10 c3 89 d1 b2 01 86 10 51 9d <c3> b2 01 86 10 fb c3 90 83 28 01 79 05 e8 e9 fc ff ff c3 9c 5a EIP: [<c060171d>] _spin_unlock_irqrestore+0x8/0x9 SS:ESP 0068:c077ce7c Kernel panic - not syncing: Fatal exception in interrupt -------------------------------------------------------------------------------- Here's the second one, I ommited memory addresses (too much typing): __delay panic do_exit die do_divide_error do_divide_error default_idle enqueue_hrtimer hrtimer_start ktime_get handle_level_irq do_IRQ error_code default_idle default_idle cpu_idle start_kernel unknown_bootoption EIP: [<c04e6611>] delay_tsc+0xd/0x13 SS:ESP 0068:c0716e58 Kernel panic - not syncing: Attempted to kill the idle task! Created attachment 156173 [details]
/var/log/dmesg
Created attachment 156174 [details]
/var/log/messages
Created attachment 156175 [details]
Smolt profile
Computer freezes with 2.6.21-3228.fc7, does not freeze with 2.6.20-2925.11.fc7xen (used only with fc7), with Windows xp, or with OpenSUSE10.2, all on the same computer, HP m7259c with AMD64x2 processor and 2GB memory. Freeze time is random, but fast reboot means fast freeze. This bug fixed for me with updates of 7/17/07 and 7/19/07. Installing updates was difficult, so I cannot tell which one did it. Hello folks, I'm reviewing this bug as part of the kernel bug triage project, an attempt to isolate current bugs in the fedora kernel. http://fedoraproject.org/wiki/KernelBugTriage I am CC'ing myself to this bug. There hasn't been much activity on this bug for a while and it appears resolved. I am therefore closing. If I have erred, please forgive me and re-open with any additional information you are able to give. I will then try and assist you if I can. Cheers Chris |