Re: [BISECTED] pata_jmicron: no drives found on post 2.6.25 kernels

From: Plamen Petrov
Date: Wed May 21 2008 - 11:49:43 EST

Shaohua Li ÐÐÐÐÑÐ:

On Tue, 2008-05-20 at 19:09 +0300, Plamen Petrov wrote:
Shaohua Li ÐÐÐÐÑÐ:

> On Tue, 2008-05-20 at 01:37 +0300, Plamen Petrov wrote:
>> Hello, folks! >> >> After 2.6.26 merge window opened, the optical drives in my
>> computer, hanging off a JMicron controler were not detected
>> by linux any more. >> >> Luca Tettamanti reported similar troubles:
>> >> >> Its been 20 days, so I decided to bisect.
>> git bisect revealed that commit
>> 7d715a6c1ae5785d00fb9a876b5abdfc43abc44b
>> is the one causing pata_jmicron to fail to detect drives,
>> connected to the JMicron controler on my motherboard.
>> At least in my case, anyway...
>> Changing kernel config to CONFIG_PCIEASPM=n makes the drives
>> attached to the JMicron SATA/PATA controller usable again. > When you enable this option, did you change any ASPM policy? By default,
> we are using the BIOS setting, so it shouldn't change any thing. >

No, I did not change any ASPM policy, mainly because I do not how.

> Also can you please send me the 'lspci -vvvxxxx' output with/without the
> ASPM enabled? >
Can you please try below patch?
The Slot 03:00.* of JMicron controller has two functions, but one is
PCIE endpoint the other isn't PCIE device, very strange. PCIE spec
defines all functions should have the same config for ASPM, so disable
ASPM for the whole slot in this case.

With the provided patch applied on top of latest git tree, the optical
drive connected to the JMicron controller WORKS with CONFIG_PCIEASPM=y.

Just in case - this is on a Gigabyte GA-P35-DS3R v2.1 motherboard,


Plamen Petrov, network & system administrator
Filial - Silistra
RU "Angel Kantchev"
this message is UTF8 encoded

This message was sent by the mail server
at using the web interface:
E-mail postmaster@xxxxxxxxxxxxx with anything,
regarding the server itself
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at
Please read the FAQ at