From: Clemens Ladisch <clemens@ladisch.de>
To: Rob Allen <ra-kernel@hotmail.co.uk>
Cc: Yinghai Lu <yinghai@kernel.org>,
Stefan Richter <stefanr@s5r6.in-berlin.de>,
Ram Pai <linuxram@us.ibm.com>,
linux1394-devel@lists.sourceforge.net, linux-pci@vger.kernel.org
Subject: Re: [Bug 43244] New: firewire_ohci prevents boot
Date: Wed, 16 May 2012 15:53:29 +0200 [thread overview]
Message-ID: <4FB3B159.2090401@ladisch.de> (raw)
In-Reply-To: <BLU0-SMTP12B809D527F768CCC42B18B7180@phx.gbl>
Rob Allen wrote:
> On 14/05/12 07:39, Yinghai Lu wrote:
>> can you post full log with pci debug enabled with lastest upsteam kernel?
>
> I'm happy to do that, although I need with some guidance on what I need to
> enable to get the required output.
For Ubuntu, see <https://wiki.ubuntu.com/KernelTeam/GitKernelBuild>.
To enable PCI debugging, enable the configuration options
CONFIG_DEBUG_KERNEL and CONFIG_PCI_DEBUG.
Regards,
Clemens
next prev parent reply other threads:[~2012-05-16 13:53 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-43244-4803@https.bugzilla.kernel.org/>
[not found] ` <20120513221357.7574ae79@stein>
2012-05-14 6:32 ` [Bug 43244] New: firewire_ohci prevents boot Clemens Ladisch
2012-05-14 6:39 ` Yinghai Lu
2012-05-16 13:12 ` Rob Allen
2012-05-16 13:53 ` Clemens Ladisch [this message]
2012-05-21 19:33 ` Rob Allen
2012-05-21 20:08 ` Stefan Richter
2012-05-21 20:20 ` Clemens Ladisch
2012-05-24 18:26 ` Stefan Richter
2012-05-24 18:43 ` Rob Allen
2012-06-04 23:59 ` Yinghai Lu
[not found] ` <4FBE8146.1030803@hotmail.co.uk>
2012-06-04 11:00 ` Rob Allen
2012-06-05 2:54 ` Ram Pai
2012-06-19 21:11 ` Rob Allen
[not found] ` <BAY153-W382DF41517C8EA770817E4B7EB0@phx.gbl>
2012-07-01 20:56 ` Yinghai Lu
2012-07-05 19:53 ` Rob Allen
[not found] ` <4FF5F09C.5020507@hotmail.co.uk>
2012-07-21 11:31 ` Rob Allen
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=4FB3B159.2090401@ladisch.de \
--to=clemens@ladisch.de \
--cc=linux-pci@vger.kernel.org \
--cc=linux1394-devel@lists.sourceforge.net \
--cc=linuxram@us.ibm.com \
--cc=ra-kernel@hotmail.co.uk \
--cc=stefanr@s5r6.in-berlin.de \
--cc=yinghai@kernel.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.