Bug 202822
Summary: | sata_via timeouts under heavy I/O load _IF_ irqbalance running | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | JuanJo Ciarlante <jjo> |
Component: | kernel | Assignee: | Kernel Maintainer List <kernel-maint> |
Status: | CLOSED INSUFFICIENT_DATA | QA Contact: | Brian Brock <bbrock> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 5 | CC: | klaus.franken, oli, slawomir.czarko, 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: | 2008-02-05 13:34:51 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: |
Description
JuanJo Ciarlante
2006-08-16 16:32:43 UTC
I'd forgotten: Given that my primary disk is PATA /dev/hda, I could "revive" SATA access (even before doing irqbalance workaround) by: echo "scsi remove-single-device 0 0 0 0" > /proc/scsi/scsi dmsetup remove_all umount -f /mnt/sata/ ... rmmod sata_via modprobe sata_via vgchange -ay mount ... useit... A new kernel update has been released (Version: 2.6.18-1.2200.fc5) based upon a new upstream kernel release. Please retest against this new kernel, as a large number of patches go into each upstream release, possibly including changes that may address this problem. This bug has been placed in NEEDINFO state. Due to the large volume of inactive bugs in bugzilla, if this bug is still in this state in two weeks time, it will be closed. Should this bug still be relevant after this period, the reporter can reopen the bug at any time. Any other users on the Cc: list of this bug can request that the bug be reopened by adding a comment to the bug. In the last few updates, some users upgrading from FC4->FC5 have reported that installing a kernel update has left their systems unbootable. If you have been affected by this problem please check you only have one version of device-mapper & lvm2 installed. See bug 207474 for further details. If this bug is a problem preventing you from installing the release this version is filed against, please see bug 169613. If this bug has been fixed, but you are now experiencing a different problem, please file a separate bug for the new problem. Thank you. This bug has been mass-closed along with all other bugs that have been in NEEDINFO state for several months. Due to the large volume of inactive bugs in bugzilla, this is the only method we have of cleaning out stale bug reports where the reporter has disappeared. If you can reproduce this bug after installing all the current updates, please reopen this bug. If you are not the reporter, you can add a comment requesting it be reopened, and someone will get to it asap. Thank you. (In reply to comment #2) > A new kernel update has been released (Version: 2.6.18-1.2200.fc5) > based upon a new upstream kernel release. > > Please retest against this new kernel, as a large number of patches > go into each upstream release, possibly including changes that > may address this problem. > It is the same problem with kernel 2.6.18-1.2849.fc6 I tested several versions of kernels (i386 / x86_64, smp / nosmp) for fc5 and 6. Always the same trouble. After deactivating irqbalance everything is OK. Closing since there was an error in previous mass-close and they remained in NEEDINFO. I have the same kind of problem after installing Fedora 12 on a laptop with VIA chipset (A5440[4261] from one.de). I installed Fedora 12 and then I'd get these time-outs after a few minutes when running initial "yum update" after the installation. Just disabling irqbalance significantly reduced the frequency of the time-outs. I got the same timeouts again though when running "yum install" to add additional software. On the same system with disabled irqbalance I later also added irqpoll to kernel command line. This seems to have removed the time-outs completely(?). So far I was able to run "yum update" and "yum install". I also tested the laptop running 10 copies of bonnie++ and haven't seen these time-outs any more. Let me know what data should I provide to help fixing this bug. |