From: Ignacy Gawedzki <lkml@qult.net>
To: "Rafael J. Wysocki" <rjw@sisk.pl>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: kernel BUG at mm/rmap.c:631!
Date: Sun, 17 Feb 2008 23:16:03 +0100 [thread overview]
Message-ID: <20080217221603.GA32482@zenon.in.qult.net> (raw)
In-Reply-To: <200802172116.37205.rjw@sisk.pl>
On Sun, Feb 17, 2008 at 09:16:36PM +0100, thus spake Rafael J. Wysocki:
> On Sunday, 17 of February 2008, Ignacy Gawedzki wrote:
> > Hi,
>
> Hi,
>
> > I was printing on the parallel port and suddenly the "parallel" CUPS backend
> > went 50% CPU (obviously endless-looping), while the other 50% were eaten by
> > ghostscript (strace didn't show anything, so this might be an "internal"
> > loop). When I eventually killed the latter, I got this:
>
> Which kernel is this?
As is shown in the dmesg, it is 2.6.24.1.
> Is it a regression?
Can't really say for sure. At least it already happened with 2.6.23.9.
> If so, what's the last known
> working kernel?
This is really difficult to determine, since the event is pretty hard to
reproduce. I'll try to investigate more, then. :/ This one happened pretty
much right after a reboot due to a completely frozen machine (no Oops or Eeek
whatsoever) apparently due to intensive writing to the parallel port (the
kernel complained that "FIFO write timed out" twice before locking up).
Of course I do suspect a hardware problem, but since last time I had similarly
strange things it ended up being due to misconfiguration, I still hope
someone will tell me this is also the case here.
--
:wq!
prev parent reply other threads:[~2008-02-17 22:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-17 19:44 Ignacy Gawedzki
2008-02-17 20:16 ` Rafael J. Wysocki
2008-02-17 22:16 ` Ignacy Gawedzki [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=20080217221603.GA32482@zenon.in.qult.net \
--to=lkml@qult.net \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rjw@sisk.pl \
/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
all inboxes | Powered by JetHome®