Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 99538
Summary: | Anaconda hangs when trying to sbp2 kernel module | ||||||
---|---|---|---|---|---|---|---|
Product: | [Retired] Red Hat Linux Beta | Reporter: | Bernd Bartmann <bernd.bartmann> | ||||
Component: | kernel | Assignee: | Dave Jones <davej> | ||||
Status: | CLOSED WONTFIX | QA Contact: | Brian Brock <bbrock> | ||||
Severity: | medium | Docs Contact: | |||||
Priority: | medium | ||||||
Version: | beta1 | CC: | benhsu, pfrields | ||||
Target Milestone: | --- | ||||||
Target Release: | --- | ||||||
Hardware: | All | ||||||
OS: | Linux | ||||||
Whiteboard: | |||||||
Fixed In Version: | Doc Type: | Bug Fix | |||||
Doc Text: | Story Points: | --- | |||||
Clone Of: | Environment: | ||||||
Last Closed: | 2004-11-20 01:54:03 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: | 100644 | ||||||
Attachments: |
|
Description
Bernd Bartmann
2003-07-21 19:27:54 UTC
Created attachment 93032 [details]
output of lspci -vv
I am also seeing this bug. My hardware is a Lucent FW323 1394 controller (lspci output follows) and an ADS 1394 enclosure. It hangs with the 2.4.21 kernel in Severn both when installing and after installing. I went back to my old kernel (vanilla 2.4.20 w/ interactivity patches) and it works fine there. With 2.6.0-test2 and later my device is not detected. 01:07.0 FireWire (IEEE 1394): Lucent Microelectronics FW323 (rev 04) (prog-if 10 [OHCI]) Subsystem: Indigita Corporation FireWire Host Bus Adapter Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- Status: Cap+ 66Mhz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- Latency: 32 (3000ns min, 6000ns max), cache line size 08 Interrupt: pin A routed to IRQ 9 Region 0: Memory at ec011000 (32-bit, non-prefetchable) [size=4K] Capabilities: <available only to root> I hope this information was useful I applied the following patch on Stefan Richter (of the Linux ieee1394 list)'s recommendation, and although the hang went away, my drive was not detected after bootup http://www.linux1394.org/patches/scsi_add_rem.diff Ben, what happens if you rescan the bus after booting with http://www.garloff.de/kurt/linux/rescan-scsi-bus.sh Dave, I compiled 2 kernels: the first has the scsi hotplug patch and the second has the scsi hotplug patch and the latest ieee1394. With both of them I was able to get my drive recognized with the following steps: - modprobe ohci1394 (may also need to do modprobe sbp2). I have not tinkered with modules.conf but this step should be automatable. - rescan-scsi-bus.sh This situation looks stable. I tested it by playing ogg files off the disk for 1/2 an hour and copying several gigs of data within the disk. FYI the second kernel has not been tested beyond "oh, it works" After that I did all the remaining testing with first kernel on the assumption that the patch should be as small as possible. FYI, in previous attempts to get this to work I installed the latest hotplug scripts from the linux hotplug site. I do not know if those made any difference how did things work out with the final release / subsequent errata's ? |