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: Fri, 2 Apr 2010 19:59:35 +0300 [thread overview]
Message-ID: <20100402165935.GA3238@oracle.com> (raw)
In-Reply-To: <201004011134.15175.bjorn.helgaas@hp.com>
Thu, Apr 01, 2010 at 11:34:13AM -0600 was the time for Bjorn Helgaas to speak thus:
> Using ignore_loglevel shouldn't affect the problem, so I'm confused.
> Can you reproduce the original problem and attach the entire serial
> console log?
It seems that the problem does not reproduce at all now. Unfortunately I do not
have the images I have built on 2010-03-29 08:46 and building from a fresh
ae6be51ed01d6c4aaf249a207b4434bc7785853b does not reproduce the problem. It is
most likely the specific .config I used at the time (which I do not have
anymore). Also I have been doing other builds on the same system, so maybe it
was just a stale module or smth.
FWIW the problem does not reproduce with 2.6.34-rc3 at all too (on the very same
hardware).
prev parent reply other threads:[~2010-04-02 17:04 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
2010-04-01 17:34 ` Bjorn Helgaas
2010-04-02 16:59 ` Ozgur Yuksel [this message]
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=20100402165935.GA3238@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.