From: Ozgur Yuksel <ozgur.yuksel@oracle.com>
To: Bjorn Helgaas <bjorn.helgaas@hp.com>
Cc: Dominik Brodowski <linux@dominikbrodowski.net>,
Andrew Morton <akpm@linux-foundation.org>,
Yinghai Lu <yinghai@kernel.org>, Dmitry Torokhov <dtor@mail.ru>,
bugzilla-daemon@bugzilla.kernel.org,
bugme-daemon@bugzilla.kernel.org, linux-kernel@vger.kernel.org,
"Rafael J. Wysocki" <rjw@sisk.pl>
Subject: Re: [Bugme-new] [Bug 15621] New: BUG: unable to handle kernel paging request - comm: pccardd
Date: Thu, 1 Apr 2010 12:18:08 +0300 [thread overview]
Message-ID: <20100401091808.GA3236@oracle.com> (raw)
In-Reply-To: <201003301711.00351.bjorn.helgaas@hp.com>
Tue, Mar 30, 2010 at 05:10:59PM -0600 was the time for Bjorn Helgaas to speak thus:
> Anyway, I'd like to see the entire dmesg log when booted *without*
> pci=nocrs, because that's the case that fails. Since the system doesn't
> boot, you'll have to use a serial console or netconsole to collect the
> whole thing. The serial console log in comment 7 is corrupted; it looks
> like all the lines got truncated to 80 columns or something. And please
> boot with "ignore_loglevel" so we see all the debug messages on the console.
Interestingly when ignore_loglevel is used, the problem does not reproduce. Now
I'll proceed with actions in comment #11.
next prev parent reply other threads:[~2010-04-01 9:20 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-15621-10286@https.bugzilla.kernel.org/>
2010-03-24 11:12 ` [Bugme-new] [Bug 15621] New: BUG: unable to handle kernel paging request - comm: pccardd Andrew Morton
2010-03-25 16:51 ` Bjorn Helgaas
2010-03-25 17:01 ` Dominik Brodowski
2010-03-29 9:12 ` Ozgur Yuksel
2010-03-30 23:10 ` Bjorn Helgaas
2010-04-01 9:18 ` Ozgur Yuksel [this message]
2010-04-01 17:34 ` Bjorn Helgaas
2010-04-02 16:59 ` Ozgur Yuksel
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=20100401091808.GA3236@oracle.com \
--to=ozgur.yuksel@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=bjorn.helgaas@hp.com \
--cc=bugme-daemon@bugzilla.kernel.org \
--cc=bugzilla-daemon@bugzilla.kernel.org \
--cc=dtor@mail.ru \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@dominikbrodowski.net \
--cc=rjw@sisk.pl \
--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.