401973 – sys-fs/udev-17x breaks communication with Marvell 88SE6121 SATA II Controller

Bug 401973 - sys-fs/udev-17x breaks communication with Marvell 88SE6121 SATA II Controller

Summary: sys-fs/udev-17x breaks communication with Marvell 88SE6121 SATA II Controller

Status:	RESOLVED FIXED

Alias:	None

Product:	Gentoo Linux
Classification:	Unclassified
Component:	[OLD] Core system (show other bugs)
Hardware:	All Linux

Importance:	Normal normal
Assignee:	udev maintainers

URL:
Whiteboard:
Keywords:

Depends on:
Blocks:

Reported:	2012-02-02 19:04 UTC by Gernot Kohlhaas
Modified:	2013-01-20 13:41 UTC (History)
CC List:	0 users

See Also:
Package list:
Runtime testing required:	---

Attachments
Output of emerge --info (einfo_20120202.txt,5.40 KB, text/plain) 2012-02-02 19:04 UTC, Gernot Kohlhaas	Details
The relevant parts of kern.log (kern_20120128.log,384.31 KB, text/plain) 2012-02-02 19:05 UTC, Gernot Kohlhaas	Details
Output of lspci -v (lspci.txt,10.64 KB, text/plain) 2012-02-02 19:05 UTC, Gernot Kohlhaas	Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description Gernot Kohlhaas 2012-02-02 19:04:48 UTC

Created attachment 300801 [details]
Output of emerge --info

After updating udev to version udev-171-r5, I was unable to access my hdd that's connected to a "03:00.0 IDE interface: Marvell Technology Group Ltd. 88SE6121 SATA II Controller (rev b2)" Controller. This controller is built into the Mainboard (P35 MSI Neo2-FR).
When booting the system, udev tries to populate /dev but hangs there for a Minute or two. After that the system boots, but isn't able to access the drive that's connected to the Marvel Controller.
Many ATA-Errors appear in the kernel Log and the communication with the drive itself seems distorted. No program can access the drive anymore. hdparm, smartctl - it isn't even recognized as a drive anymore.
Upgrading to udev-175-r1 won't help, either.
But after downgrading to udev-164-r2, everything works like a charm, again.
No ATA-Errors in the kernel-log etc.
Other operating systems are working just fine with the drive/controller and the HDD is relatively new.

Comment 1 Gernot Kohlhaas 2012-02-02 19:05:34 UTC

Created attachment 300803 [details]
The relevant parts of kern.log

Comment 2 Gernot Kohlhaas 2012-02-02 19:05:53 UTC

Created attachment 300805 [details]
Output of lspci -v

Comment 3 Chí-Thanh Christopher Nguyễn gentoo-dev

2012-02-03 21:47:16 UTC

What happens if you use ahci for the Marvell chipset? (be aware that PATA devices will no longer work as ahci doesn't support them)

To use ahci instead of pata_marvell, pass ahci.marvell_enable=1 kernel parameter and/or disable pata_marvell in your kernel config.

Comment 4 Gernot Kohlhaas 2012-02-04 15:01:40 UTC

Hi!
If I use AHCI for the Marvell-Controller, it works.
The only problem left now is the one you mentioned:
I have a IDE DVD-Burner connected to the controller. I could live with this "fix/workaround" for a while, but it would be nice if I still could read and write CDs/DVDs under Gentoo.
ATM a SATA-Drive would be out of the question because I don't have a SATA port free anymore.

Comment 5 Samuli Suominen (RETIRED) gentoo-dev

2013-01-20 10:34:21 UTC

Try with current stable =sys-fs/udev-197-r3. Reopen if this is any of a problem anymore, if not, set to FIXED

Comment 6 Gernot Kohlhaas 2013-01-20 13:41:42 UTC

In the meantime, my configuration changed. Now I have an pci-express SATA-Controller on which a BD-ROM is attached via sata. On my Marvell-controller, there's only a harddisk attached now. So everything's fine now either way.