On 9/17/2013 8:40 PM, Robert Hancock wrote: > On Tue, Sep 17, 2013 at 6:35 PM, Bruce Link <br...@1045.ca> wrote: >>> Hello, >>> >>> On Fri, Sep 06, 2013 at 07:53:49PM -0600, Robert Hancock wrote: >>>>> Is there any more information I can supply that would be helpful? >>>> I'm not quite sure what the next step would be. It's quite possible >>>> that the NVIDIA driver in Windows is doing some magic to work around >>>> the problem that we don't know about, but it's hard to say what that >>>> might be. The fact that the default drivers used in the WinPE boot >>>> don't seem to work would tend to point toward some kind of hardware >>>> incompatibility issue. >>>> >>>> Tejun, think you poked with some of this stuff before - any ideas? >>> It has been years since I looked at MCP quirks, of which there are too >>> many. It's likely another quirk on the controller side that nvidia >>> worked around somehow without telling anyone. Given the history and >>> that nvidia is out of chipset market, I think it's highly unlikely to >>> learn what the issue and workaround are without reverse engineering >>> it. So, um, no idea. >>> >>> Thanks. >>> >>> -- >>> tejun >>> -- >> >> Robert, >> >> I've inquired about this problem with Allen Martin at Nvidia, he had the >> following reply: >> >> /--------SNIP---------------/ >> Hi Bruce, I did work on the Windows SATA driver for those chipsets, so I’m >> familiar with it. I’m not aware of any of any timing workarounds for any >> devices in the driver, but it’s certainly true that there are devices that >> have timing sensitivity, especially around the IDENTIFY command and it may >> inadvertently work with one driver and not another. >> >> From the bug reports it looks like it’s always timing out on a >> TEST_UNIT_READY command? I assume this is probably the first command sent >> down after IDENTIFY to check for presense of a CD in the drive? If so it’s >> likely the drive is locked up and any command at that point will fail. If >> you want to test out the theory about it being a timing issue, I would stick >> some udelay()s in the identify code path, both before and after starting the >> transfer to see if it makes any difference. Also do you know if the driver >> does a PHY reset when it resets the link? If not, you can try doing that by >> writing a 0 to SControl and then restoring it with the original value. >> >> Hope this helps, >> >> -Allen >> /--------SNIP---------------/ >> >> Does this provide any actionable information? I've tried searching for the >> proper location to impliment these delays in the sata_nv.c and libata-eh.c >> files but admittedly, am in over my head. > Don't think there's any earth-shaking revelations but it might be a > few things to try. First, though, apparently there is a firmware > update for this drive of at least one revision up (WL0G) available > from Lite-ON that you could try updating to. (You'll likely need to > use Windows for that.) Given that it seems broken in at least two > different environments on this controller, it's possible they fixed > something related in the drive. Robert,
I can report that the new firmware for the drive does not solve the problem. watchtv@teevee:~$ dmesg |grep ata5 [ 1.090360] ata5: SATA max UDMA/133 cmd 0x9e0 ctl 0xbe0 bmdma 0xc400 irq 20 [ 1.556044] ata5: SATA link up 1.5 Gbps (SStatus 113 SControl 300) [ 1.564199] ata5.00: ATAPI: ATAPI iHOS104, WL0G, max UDMA/100 [ 1.580140] ata5.00: configured for UDMA/100 [ 6.580035] ata5.00: qc timeout (cmd 0xa0) [ 6.580043] ata5.00: TEST_UNIT_READY failed (err_mask=0x4) [ 7.048042] ata5: SATA link up 1.5 Gbps (SStatus 113 SControl 300) [ 7.072124] ata5.00: configured for UDMA/100 [ 12.072029] ata5.00: qc timeout (cmd 0xa0) [ 12.072037] ata5.00: TEST_UNIT_READY failed (err_mask=0x4) [ 12.072041] ata5: limiting SATA link speed to 1.5 Gbps [ 12.072043] ata5.00: limiting speed to UDMA/100:PIO3 [ 12.540058] ata5: SATA link up 1.5 Gbps (SStatus 113 SControl 300) [ 12.564141] ata5.00: configured for UDMA/100 [ 17.564038] ata5.00: qc timeout (cmd 0xa0) [ 17.564045] ata5.00: TEST_UNIT_READY failed (err_mask=0x4) [ 17.564048] ata5.00: disabled [ 17.564063] ata5: hard resetting link [ 17.564065] ata5: nv: skipping hardreset on occupied port [ 18.032068] ata5: SATA link up 1.5 Gbps (SStatus 113 SControl 300) [ 18.032082] ata5: EH complete watchtv@teevee:~$ My apologies for not noticing the firmware update earlier. I do recall checking at one time, though it may have been prior to Sept. 2011. Bruce -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1063474 Title: System fails to connect to iHOS-104 DVD drive with nvidia MCP61 chipset. Status in “linux” package in Ubuntu: Confirmed Bug description: The computer fails to connect to the LG iHOS-104 DVD drive. The drive is working, as it will boot the Windows installer. I have seen similar bugs posted on the internet for the past 5 years. Here's a thread that shows the problem fixed for the MCP55 chipset. http://www.gossamer- threads.com/lists/linux/kernel/1234502?do=post_view_threaded#1234502 WORKAROUND: Use the DVD drive with a USB-SATA adapter. Upstream discussion: http://marc.info/?l=linux- ide&m=137736028900971&w=2 ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: linux-image-3.5.0-17-generic 3.5.0-17.27 ProcVersionSignature: Ubuntu 3.5.0-17.27-generic 3.5.5 Uname: Linux 3.5.0-17-generic x86_64 ApportVersion: 2.6.1-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC1: watchtv 7366 F.... pulseaudio /dev/snd/controlC0: watchtv 4814 F.... alsamixer watchtv 7366 F.... pulseaudio CRDA: Error: [Errno 2] No such file or directory: 'iw' Date: Sun Oct 7 19:34:10 2012 HibernationDevice: RESUME=UUID=914386c4-84a9-4eb4-8382-cb6f877f7ef6 IwConfig: eth0 no wireless extensions. lo no wireless extensions. Lsusb: Bus 002 Device 006: ID 046d:c047 Logitech, Inc. Laser Mouse Bus 002 Device 005: ID 0e8f:0021 GreenAsia Inc. Multimedia Keyboard Controller Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: Gigabyte Technology Co., Ltd. M68M-S2P ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-17-generic root=UUID=81823799-2b15-4236-887b-e3497f3f6a46 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.5.0-17-generic N/A linux-backports-modules-3.5.0-17-generic N/A linux-firmware 1.94 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) WifiSyslog: dmi.bios.date: 07/15/2010 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: FCb dmi.board.name: M68M-S2P dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrFCb:bd07/15/2010:svnGigabyteTechnologyCo.,Ltd.:pnM68M-S2P:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnM68M-S2P:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: M68M-S2P dmi.sys.vendor: Gigabyte Technology Co., Ltd. --- ApportVersion: 2.12-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC1: watchtv 1305 F.... pulseaudio CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. CurrentDmesg: [ 55.165828] pool[1480]: segfault at 40 ip 00007f3d05544f87 sp 00007f3d03653c50 error 4 in tumbler-gst-thumbnailer.so[7f3d05542000+4000] [ 707.285402] python[6778]: segfault at 0 ip 00007eff23bde2f7 sp 00007fffeba941f8 error 4 in libgtk-3.so.0.800.2[7eff23ade000+4c5000] DistroRelease: Ubuntu 13.10 HibernationDevice: RESUME=UUID=914386c4-84a9-4eb4-8382-cb6f877f7ef6 IwConfig: eth0 no wireless extensions. lo no wireless extensions. Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 003: ID 0e8f:0021 GreenAsia Inc. Multimedia Keyboard Controller Bus 002 Device 002: ID 045e:0719 Microsoft Corp. Xbox 360 Wireless Adapter Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: Gigabyte Technology Co., Ltd. M68M-S2P MarkForUpload: True Package: linux (not installed) ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.10.0-6-generic root=UUID=e276cadb-f115-40c5-abe4-2471badc3113 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.10.0-6.17-generic 3.10.3 RelatedPackageVersions: linux-restricted-modules-3.10.0-6-generic N/A linux-backports-modules-3.10.0-6-generic N/A linux-firmware 1.113 RfKill: Tags: saucy Uname: Linux 3.10.0-6-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo dmi.bios.date: 08/25/2010 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: FC dmi.board.name: M68M-S2P dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrFC:bd08/25/2010:svnGigabyteTechnologyCo.,Ltd.:pnM68M-S2P:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnM68M-S2P:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: M68M-S2P dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1063474/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
