public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@zip.com.au>
To: Ville Herva <vherva@niksula.hut.fi>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.5.26 buffer layer error at page-writeback.c:420
Date: Sun, 21 Jul 2002 23:32:59 -0700	[thread overview]
Message-ID: <3D3BA71B.9E6DF92E@zip.com.au> (raw)
In-Reply-To: 20020721120837.GJ1548@niksula.cs.hut.fi

Ville Herva wrote:
> 
> I just booted 2.5.26 to textmode, logged in as root and left it there. After
> a while I got this.

urgh.  OK, thanks.  It's that dang ramdisk driver again.
I'll take a look.

> After that, floppy access etc fails.

That would probably be unrelated - the message is just a
warning/debug thing.

-

  parent reply	other threads:[~2002-07-22  6:21 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-07-21 12:08 2.5.26 buffer layer error at page-writeback.c:420 Ville Herva
2002-07-21 13:16 ` Ville Herva
2002-07-22  6:32 ` Andrew Morton [this message]
2002-07-22  7:53   ` 2.5.26 Floppy driver problem (was buffer layer error at page-writeback.c:420) Ville Herva

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=3D3BA71B.9E6DF92E@zip.com.au \
    --to=akpm@zip.com.au \
    --cc=linux-kernel@vger.kernel.org \
    --cc=vherva@niksula.hut.fi \
    /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