| Summary: | kernel oops in kswapd0 during disk I/O | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Joel Uckelman <uckelman> | ||||||
| Component: | kernel | Assignee: | Kernel Maintainer List <kernel-maint> | ||||||
| Status: | CLOSED DUPLICATE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||
| Severity: | urgent | Docs Contact: | |||||||
| Priority: | unspecified | ||||||||
| Version: | 15 | CC: | aquini, gansalmon, itamar, jonathan, kernel-maint, madhu.chinakonda | ||||||
| Target Milestone: | --- | ||||||||
| Target Release: | --- | ||||||||
| Hardware: | x86_64 | ||||||||
| OS: | Linux | ||||||||
| Whiteboard: | |||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||
| Doc Text: | Story Points: | --- | |||||||
| Clone Of: | Environment: | ||||||||
| Last Closed: | 2011-07-20 18:31:30 UTC | Type: | --- | ||||||
| Regression: | --- | Mount Type: | --- | ||||||
| Documentation: | --- | CRM: | |||||||
| Verified Versions: | Category: | --- | |||||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||||
| Attachments: |
|
||||||||
Created attachment 513879 [details]
errors, screenshot #2
*** This bug has been marked as a duplicate of bug 712198 *** |
Created attachment 513878 [details] errors, screenshot #1 Description of problem: On a fresh Fedora 15 install, when I try to copy data from an external USB drive to an internal SATA drive, I get a kernel oops within about 30 seconds of starting. This happens consistently, regardless of what I'm using to copy data (e.g., cp, rsync). Subsequently, if I do anything which causes disk access, the VT in which I do it locks up, rendering the machine essentially inoperable (I can't even shut it down properly). To test whether this problem was due to flaky hardware, I did a fresh install of Fedora 14, which I had run for some time on this machine. I cannot reproduce the problem with the 2.6.35.13-92.fc14 kernel. I am able to successfully copy many gigabytes of data from the external drive to the internal one without incident. Unfortunately, the error output never gets written to disk---my guess is because rsyslogd isn't able to write it out---so I can't provide a text copy of the oops. What I can do is *photograph* it on the screen. I'm still able to scroll up in the VT and it's not so large as to fill the scroll buffer, so I can still capture all of it. I've attached pictures of the first two screenfulls of error output. I would be eager to photograph the rest of the error output if that would help get this bug resolved, so just ask. I'd love to get this resolved quickly, as the problem machine is my backup server; the fact that it's inoperable is now preventing me from backing up my other machines as normal. Version-Release number of selected component (if applicable): 2.6.38.6-26.rc1.f15 How reproducible: Always Steps to Reproduce: 1. Copy a large amount of data to the internal drive. Actual results: kernel oops, disk access becomes impossible Expected results: data should copy properly