From: Shaohua Li <shaohua.li@intel.com>
To: Luca Tettamanti <kronos.it@gmail.com>
Cc: Plamen Petrov <pvp-lsts@fs.ru.acad.bg>,
linux-kernel@vger.kernel.org,
Jesse Barnes <jbarnes@virtuousgeek.org>
Subject: Re: [BISECTED] pata_jmicron: no drives found on post 2.6.25 kernels
Date: Thu, 22 May 2008 09:15:24 +0800 [thread overview]
Message-ID: <1211418924.15223.1.camel@sli10-desk.sh.intel.com> (raw)
In-Reply-To: <68676e00805211245u1a1973e5g847bd7e8a6c9e5a7@mail.gmail.com>
On Wed, 2008-05-21 at 21:45 +0200, Luca Tettamanti wrote:
> On Wed, May 21, 2008 at 10:58 AM, Shaohua Li <shaohua.li@intel.com> wrote:
> > 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:
> >> >> http://marc.info/?l=linux-kernel&m=120958791323911&w=2
> >> >>
> >> >> 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?
>
> I confirm that the patch fixes the issue when CONFIG_ASPM is enabled.
>
> > The Slot 03:00.* of JMicron controller has two functions, but one is
> > PCIE endpoint the other isn't PCIE device, very strange.
>
> Right, that's what I'm seeing here (motherboard is an ASUS P5B-E). I'm
> attaching the output of lspci.
Jesse, can you take this patch. It should be safe for 2.6.26.
Thanks,
Shaohua
next prev parent reply other threads:[~2008-05-22 1:11 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <courier.4832011A.000041C2@fs.ru.acad.bg>
2008-05-20 1:48 ` Shaohua Li
2008-05-20 16:09 ` Plamen Petrov
2008-05-21 8:58 ` Shaohua Li
2008-05-21 15:49 ` Plamen Petrov
2008-05-21 19:45 ` Luca Tettamanti
2008-05-22 1:15 ` Shaohua Li [this message]
2008-05-22 1:30 ` Jesse Barnes
2008-05-20 14:13 ` Alan Cox
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1211418924.15223.1.camel@sli10-desk.sh.intel.com \
--to=shaohua.li@intel.com \
--cc=jbarnes@virtuousgeek.org \
--cc=kronos.it@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pvp-lsts@fs.ru.acad.bg \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®