From: Tejun Heo <htejun@gmail.com>
To: Tjenarvi Tjenarvi <tjenarvi@yahoo.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Jeff Garzik <jgarzik@pobox.com>,
Linus Torvalds <torvalds@linux-foundation.org>
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: Sun, 20 May 2007 13:54:08 +0200 [thread overview]
Message-ID: <465036E0.9050805@gmail.com> (raw)
In-Reply-To: <647742.64243.qm@web58814.mail.re1.yahoo.com>
Tjenarvi Tjenarvi wrote:
> These dmesg if not as Tejun said, Which he said should only libata
> drivers used to get more information. Frankly, I don't know which one I
> have to take off in kernel configuration to comply this. I guess the
> libata is in:
>
> Device Drivers --->
> SCSI device support --->
>
> But, don't know which one to take off, so that only libata driver
> compiled. Please tell me.
Please turn off Device Drivers -> ATA/ATAPi/MFM/RLL support. I'm not
sure which ide driver is grabbing the first port. Can you post the
original .config?
> The machine seems nothing wrong whether I used "pci=assign-busses" or
> not. But, I found another message that I don't understand in the dmesg
> whether I use "pci=assign-busses" or not, the message still occur, I
> don't know this is related or not. The message is "PCI: If a device
> doesn't work, try "pci=routeirq". If it helps, post a report". Should
> I try this kernel option?
I don't think you need to pay attention to the message.
--
tejun
next parent reply other threads:[~2007-05-20 11:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <647742.64243.qm@web58814.mail.re1.yahoo.com>
2007-05-20 11:54 ` Tejun Heo [this message]
[not found] <3767.73594.qm@web58805.mail.re1.yahoo.com>
2007-05-20 17:27 ` no DRQ after issuing MULTWRITE_EXT AND PCI: Bus #0b (-#0e) is hidden behind transparent bridge #0a (-#0a) (try 'pci=assign-busses') Tejun Heo
[not found] <466481.34138.qm@web58810.mail.re1.yahoo.com>
2007-05-15 15:33 ` Linus Torvalds
2007-05-16 17:09 ` 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=465036E0.9050805@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.