Bug 200924
| Summary: | futex + apic_timer BUG: spinlock lockup on CPU#0 | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | John Reiser <jreiser> | ||||||||
| Component: | kernel | Assignee: | Dave Jones <davej> | ||||||||
| Status: | CLOSED RAWHIDE | QA Contact: | Brian Brock <bbrock> | ||||||||
| Severity: | medium | Docs Contact: | |||||||||
| Priority: | medium | ||||||||||
| Version: | 6 | CC: | konradr, pfrields, wtogami | ||||||||
| Target Milestone: | --- | ||||||||||
| Target Release: | --- | ||||||||||
| Hardware: | i686 | ||||||||||
| OS: | Linux | ||||||||||
| Whiteboard: | |||||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||||
| Doc Text: | Story Points: | --- | |||||||||
| Clone Of: | Environment: | ||||||||||
| Last Closed: | 2006-10-12 06:22:08 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: | 202141 | ||||||||||
| Attachments: |
|
||||||||||
|
Description
John Reiser
2006-08-01 16:43:39 UTC
Created attachment 133415 [details]
screen photograph showing lockup traceback
darn, I'd love to see the bit that had scrolled off the top of the screen. Is this reproducable ? Any chance you could hook up a serial console ? Created attachment 133479 [details]
serial console capture
After trimming down the glibc tests to just the nptl subdirectory, it took
about 10 minutes to tickle the kernel BUG. Here is the serial console, as
captured by minicom.
The PI Futex code did get some important fixes after 2431. Can you repeat this on the latest rawhide kernel? (Btw, I also just sent a fix upstream for the incorrect tainting of your oopses. That shouldn't happen). Booting kernel-2.6.17-1.2510.fc6 and running the glibc/nptl tests, I get no BUG. There was one "Maximum lock depth 1024 reached task: ld-linux.so.2 (4210)" which happened the first time, but not in the next 4 passes, not even with a reboot between pass 3 and pass 4. So the probability seems less. I will attach the serial console log. [Thank you for looking into the incorrect tainting, too. I wondered what was going on there; I use only modules from Fedora Core fc6t1 builds, and no others.] Created attachment 133584 [details]
captured serial console log
Note "Maximum lock depth 1024 reached ..." on line 260.
Is this still happening with the current builds ? I have not seen this problem since I last reported it on Aug.3. "Yum update" has been run approximately weekly. ok, thanks. |