Bug 51706
Summary: | kernel locks up toshiba notebook | ||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|
Product: | [Retired] Red Hat Linux | Reporter: | hjl | ||||||||
Component: | kernel | Assignee: | Arjan van de Ven <arjanv> | ||||||||
Status: | CLOSED RAWHIDE | QA Contact: | Brock Organ <borgan> | ||||||||
Severity: | medium | Docs Contact: | |||||||||
Priority: | medium | ||||||||||
Version: | 7.3 | ||||||||||
Target Milestone: | --- | ||||||||||
Target Release: | --- | ||||||||||
Hardware: | i386 | ||||||||||
OS: | Linux | ||||||||||
Whiteboard: | |||||||||||
Fixed In Version: | Doc Type: | Bug Fix | |||||||||
Doc Text: | Story Points: | --- | |||||||||
Clone Of: | Environment: | ||||||||||
Last Closed: | 2001-08-15 14:57:34 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: | 53209 | ||||||||||
Attachments: |
|
Description
hjl
2001-08-14 04:45:23 UTC
Please note that there is another cardbus bridge on the port replicator. That may confuse yenta_socket. Strange question: could you try the enterprise kernel on this ? This defect is considered SHOULD-FIX for Fairfax. The enterprise kernel also locks up the machine. One more thing. There is no IRQ assigned for the CardBus bridge on the port replicator. It may confuse the kernel. I think one fix may be to ignore the socket without an IRQ during init. Here is a patch. With it applied, I got Linux Kernel Card Services 3.1.22 options: [pci] [cardbus] [pm] PCI: Found IRQ 11 for device 00:0b.0 PCI: Found IRQ 11 for device 00:0b.1 PCI: Sharing IRQ 11 with 00:00.1 CardBus bridge (1179:0617, 1179:0001) without PCI interrupt is ignored! Yenta IRQ list 0000, PCI irq11 Socket status: 30000007 Yenta IRQ list 0000, PCI irq11 Socket status: 30000020 Does kernel know how to assign an IRQ to a pci device? Created attachment 27855 [details]
A patch
Created attachment 27877 [details]
slightly modified patch
The kernel should be able to assign irq's. If it doesn't, that's a bug, but the check should only be done after enabling the device, attached patch does that first. Created attachment 27973 [details]
An updated patch
Here is the new kernel message. I don't think Linux knows how to assign an IRQ to a PCI device, at least on x86. It has to be assigned by BIOS. Linux Kernel Card Services 3.1.22 options: [pci] [cardbus] [pm] PCI: Found IRQ 11 for device 00:0b.0 PCI: Found IRQ 11 for device 00:0b.0 PCI: Found IRQ 11 for device 00:0b.1 PCI: Sharing IRQ 11 with 00:00.1 PCI: Found IRQ 11 for device 00:0b.1 PCI: Sharing IRQ 11 with 00:00.1 PCI: No IRQ known for interrupt pin A of device 01:05.0. Please try using pci=biosirq. PCI CardBus bridge (1179:0617, 1179:0001) without IRQ is ignored! Passing pci=biosirq to kernel, I got Linux Kernel Card Services 3.1.22 options: [pci] [cardbus] [pm] PCI: Found IRQ 11 for device 00:0b.0 PCI: Found IRQ 11 for device 00:0b.0 PCI: Found IRQ 11 for device 00:0b.1 PCI: Sharing IRQ 11 with 00:00.1 PCI: Found IRQ 11 for device 00:0b.1 PCI: Sharing IRQ 11 with 00:00.1 PCI: No IRQ known for interrupt pin A of device 01:05.0. PCI CardBus bridge (1179:0617, 1179:0001) without IRQ is ignored! FYI, I updated my patch to print out PCI: CardBus bridge (1179:0617, 1179:0001) without IRQ is ignored! to be consistent with other PCI messages. patch added to the kernel; thanks! |