Bug 4514
Summary: | cdrecord with /dev/hda hangs machine | ||
---|---|---|---|
Product: | IO/Storage | Reporter: | Jeff Wiegley (jeffw) |
Component: | IDE | Assignee: | Bartlomiej Zolnierkiewicz (bzolnier) |
Status: | REJECTED INSUFFICIENT_DATA | ||
Severity: | high | CC: | protasnb, t8m |
Priority: | P2 | ||
Hardware: | i386 | ||
OS: | Linux | ||
Kernel Version: | 2.6.14-rc3 | Subsystem: | |
Regression: | --- | Bisected commit-id: | |
Attachments: | The errors that the alim15x3 controller generates... |
Description
Jeff Wiegley
2005-04-18 13:04:05 UTC
Ooops, forgot to include the lspci output... duh! 0000:00:00.0 Host bridge: ATI Technologies Inc: Unknown device 5950 (rev 01) 0000:00:01.0 PCI bridge: ATI Technologies Inc: Unknown device 5a3f 0000:00:06.0 PCI bridge: ATI Technologies Inc: Unknown device 5a38 0000:00:18.0 Host bridge: Advanced Micro Devices [AMD] K8 NorthBridge 0000:00:18.1 Host bridge: Advanced Micro Devices [AMD] K8 NorthBridge 0000:00:18.2 Host bridge: Advanced Micro Devices [AMD] K8 NorthBridge 0000:00:18.3 Host bridge: Advanced Micro Devices [AMD] K8 NorthBridge 0000:00:19.0 PCI bridge: ALi Corporation M5249 HTT to PCI Bridge 0000:00:1c.0 USB Controller: ALi Corporation USB 1.1 Controller (rev 03) 0000:00:1c.1 USB Controller: ALi Corporation USB 1.1 Controller (rev 03) 0000:00:1c.2 USB Controller: ALi Corporation USB 1.1 Controller (rev 03) 0000:00:1c.3 USB Controller: ALi Corporation USB 2.0 Controller (rev 01) 0000:00:1d.0 0403: ALi Corporation: Unknown device 5461 0000:00:1e.0 ISA bridge: ALi Corporation: Unknown device 1573 (rev 31) 0000:00:1e.1 Bridge: ALi Corporation M7101 Power Management Controller [PMU] 0000:00:1f.0 IDE interface: ALi Corporation M5229 IDE (rev c7) 0000:00:1f.1 RAID bus controller: ALi Corporation: Unknown device 5287 (rev 02) 0000:01:05.0 VGA compatible controller: ATI Technologies Inc: Unknown device 5954 0000:02:00.0 Ethernet controller: Broadcom Corporation NetXtreme BCM5751 Gigabit Ethernet PCI Express (rev 01) 0000:03:15.0 FireWire (IEEE 1394): VIA Technologies, Inc. IEEE 1394 Host Controller (rev 80) <BEGIN SARCASM> Very, Very nice to see how well the bug tracker is maintained. <END SARCASM> Seriously, either a) Maintain and assign bugs, or b) don't put up a bug tracker like this at all. This bug was entered three weeks ago and it hasn't been touched since. Why did I spend the time to submit the bug at all? > Seriously, either > a) Maintain and assign bugs, or > b) don't put up a bug tracker like this at all. > > This bug was entered three weeks ago and it hasn't been > touched since. Why did I spend the time to submit the > bug at all? Your report is still useful if somebody hits the same issue and/or wants to work on it. I assume this is still happening in 2.6.12-rc5? If so, it might be useful to enable CONFIG_X86_LOCAL_APIC=y CONFIG_X86_IO_APIC=y and to boot with the `nmi_watchdog=1' boot option, see if that generates any diagnostics. I've tried everything with this damn bug. Basically here is what I believe: The alim15x3 driver is broken. I am now running 2.6.14-rc3. The moment I try to do: cdrecord blank=all dev=ATAPI:/dev/hda The following is generated in the log files when cdrecord starts accessing the disc: and cdrecord locks up. Even sending a KILL signal to the cdrecord process fails to wake it up. Nothing else can access /dev/hda anymore either. eject /dev/hda seems to work if I issue it before trying to access data on a disc so I'm not crazy. I have the right driver and it is seeing the drive. But data access through alim15x3 is broken. *Please* prove me wrong. I've tried lots and lots of fixes over the past *SIX* months and nothing makes a difference. I have tried a pioneer drive instead of my default sony drive so I know it's not a drive hardware issue because the pioneer does the same thing. Shuttle ST20G5 box with ATI radeon Xpress 200 chipset (I will never buy another ATI product.) Please help! Created attachment 6247 [details]
The errors that the alim15x3 controller generates...
Got the latest BIOS working. Still no go. still "hda lost interrupt" occurs and it doesn't seem possible to kill the process that triggered the offense. And I seem to be talking to myself. Hello?? *thump* *thump* Is this thing on? changed kernel version. This is similar to http://bugzilla.kernel.org/show_bug.cgi?id=5786 which is being worked on currently. As 2.6.8 worked for you, could you try to identify the regression to a particular snapshot kernel version or changeset? Jeff, any update from you? Is this still a problem with newer kernels? Thanks. I'm closing this one, please re-open if the problem can still be reproduced with the recent kernels. |