From: Tejun Heo <htejun@gmail.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Tjenarvi Tjenarvi <tjenarvi@yahoo.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Jeff Garzik <jgarzik@pobox.com>
Subject: Re: no DRQ after issuing MULTWRITE_EXT AND PCI: Bus #0b (-#0e) is hidden behind transparent bridge #0a (-#0a) (try 'pci=assign-busses')
Date: Wed, 16 May 2007 19:09:23 +0200 [thread overview]
Message-ID: <464B3AC3.4090204@gmail.com> (raw)
In-Reply-To: <alpine.LFD.0.98.0705150819140.16401@woody.linux-foundation.org>
Linus Torvalds wrote:
>> Someone got this link to patch this bug,
>> http://www.spinics.net/lists/linux-ide/msg04810.html. Then I post
>> another thread in
>> http://www.linuxquestions.org/questions/showthread.php?t=551630
>
> Have you tried it, and does that patch actually fix things for you?
>
> That patch has not been merged, possibly because it got forgotten, but
> possibly because it had other problems. So if you can test it and send the
> results back to Tejun and Jeff (both Cc'd), please do.
Those patch actually is merged. It just looks different because the
table got merged back into ich6m table after finding out ich6m has the
same issue. Also, the patch deals only with detection.
Can you boot 2.6.21.1 with only libata drivers compiled in and report
the dmesg? libata usually dumps more info than ide drivers so it's
easier to find out what's going on.
--
tejun
next prev parent reply other threads:[~2007-05-16 17:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <466481.34138.qm@web58810.mail.re1.yahoo.com>
2007-05-15 15:33 ` no DRQ after issuing MULTWRITE_EXT AND PCI: Bus #0b (-#0e) is hidden behind transparent bridge #0a (-#0a) (try 'pci=assign-busses') Linus Torvalds
2007-05-16 17:09 ` Tejun Heo [this message]
[not found] <647742.64243.qm@web58814.mail.re1.yahoo.com>
2007-05-20 11:54 ` Tejun Heo
[not found] <3767.73594.qm@web58805.mail.re1.yahoo.com>
2007-05-20 17:27 ` Tejun Heo
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=464B3AC3.4090204@gmail.com \
--to=htejun@gmail.com \
--cc=jgarzik@pobox.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tjenarvi@yahoo.com \
--cc=torvalds@linux-foundation.org \
/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;
as well as URLs for NNTP newsgroup(s).