Bug 251339
Summary: | Kernel 2.6.22.1-41.fc7 hangs on boot with a LSI53C1030 SCSI card | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | 260795 <d.sbragion> |
Component: | kernel | Assignee: | Kernel Maintainer List <kernel-maint> |
Status: | CLOSED NOTABUG | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | medium | Docs Contact: | |
Priority: | low | ||
Version: | 7 | ||
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: | 2007-08-22 19:35:19 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
260795
2007-08-08 14:12:46 UTC
Does the kernel option "pci=nomsi" make a difference? I am running kernel-2.6.22.1-41.fc7.i686.rpm on a DELL Precision 350 with: Symbios Logic 53c1030 PCI-X Fusion-MPT Dual Ultra320 SCSI (rev 07) fine. dmesg sais: Fusion MPT base driver 3.04.04 Copyright (c) 1999-2007 LSI Logic Corporation Fusion MPT SPI Host driver 3.04.04 Modprobe.conf has: alias scsi_hostadapter mptbase alias scsi_hostadapter1 mptspi Kernel line in grub.conf has no extra options. FYI PS: I had similar hangs with this system in the past when I connected an external SCSI device. Do you have any? Sorry for being so late, I've been out of office. I tried with "pci=nomsi", but it seems to make no difference. I can't attach external devices, there's no connector. Probably it is the same chipset but a different adapter model. BTW dmesg, with the fc6 kernel, reports this: Fusion MPT base driver 3.04.03 Copyright (c) 1999-2007 LSI Logic Corporation Fusion MPT SPI Host driver 3.04.03 ACPI: PCI Interrupt 0000:03:03.0[A] -> GSI 24 (level, low) -> IRQ 18 mptbase: Initiating ioc0 bringup ioc0: 53C1030: Capabilities={Initiator,Target} scsi0 : ioc0: LSI53C1030, FwRev=01032700h, Ports=1, MaxQ=255, IRQ=18 When it started with the fc7 kernel it reported this: Aug 8 14:47:00 server kernel: Fusion MPT base driver 3.04.04 Aug 8 14:47:01 server kernel: Copyright (c) 1999-2007 LSI Logic Corporation Aug 8 14:47:01 server kernel: Fusion MPT SPI Host driver 3.04.04 Aug 8 14:47:01 server kernel: ACPI: PCI Interrupt 0000:03:03.0[A] -> GSI 24 (le vel, low) -> IRQ 17 Aug 8 14:47:01 server kernel: mptbase: Initiating ioc0 bringup Aug 8 14:47:01 server kernel: ioc0: 53C1030: Capabilities={Initiator,Target} Aug 8 14:47:01 server kernel: scsi0 : ioc0: LSI53C1030, FwRev=01032700h, Ports= 1, MaxQ=255, IRQ=17 The difference in the IRQ it's because in the meantime I disabled the USB chip, just to see if it made a difference, so the SCSI adapter got assigned a different IRQ. Then I left it disabled, we have no USB devices attached, but it makes no difference at all. Apart from the IRQ and the different driver version they look to be the same. Furthermore, modprobe.conf has only one line referring to SCSI: alias scsi_hostadapter mptspi Does it make any difference? After a lot of fiddling with kernels going from 2.6.18 to the latest 2.6.22.2-57.fc7 test kernel I found the source of the problem. First of all I got many different kind of apparently unrelated problems apart form the boot one described above, ranging from parallel ports not working to hangs on serial port detection, to pnp device activation problems. After adding an "acpi=off" boot option everything started working perfectly, with any of the kernels tested. Now I'm using the official 2.6.22.1-41.fc7. I've found on Internet that there are many broken ACPI bioses around. Probably my HP ML 110 has one of them. After all it's a server and not even one the most recent. If there's an interest in finding workarounds for the problem I can supply any desired information about the hardware configuration and the ACPI bios used by my server. Thanks anyway for your support and your help. Other than trying to see if a BIOS update fixes the problems, there probably isn't much more to try. |