From: Max Valdez <maxvalde@fis.unam.mx>
To: kernel <linux-kernel@vger.kernel.org>
Subject: Re: 2.5.70: Lilo needs patching?
Date: 12 Jun 2003 18:35:15 +0000 [thread overview]
Message-ID: <1055442915.2690.9.camel@garaged.homeip.net> (raw)
In-Reply-To: <20030612154333.608bca2c.akpm@digeo.com>
[-- Attachment #1: Type: text/plain, Size: 1840 bytes --]
I wish I knew that before ruining my boot sector
But at the end I got to give gentoo a try, so, now i need to go back and
compile 2.5 and try it with that trick
BTW, only woosies have a boot disk, if anybody is willing to make the
comment :-P
Thanks anyway for that advice
On Thu, 2003-06-12 at 22:43, Andrew Morton wrote:
> Unai Garro Arrazola <Unai.Garro@ee.ed.ac.uk> wrote:
> >
> > Since version 2.5.69 (now with 2.5.70-mm6), I'm having trouble using lilo.
> > Every time I try to change the lilo boot, the boot menu is either not
> > changed, or it's corrupted. It looks like if Lilo doesn't manage to
> > completely write the boot sector.
> >
> > I've been looking around, but I haven't found any information about this. Has
> > anything changed in the latest versions? Are there any patches that I need to
> > apply to lilo to make it work now?
> >
>
> It's a bug. Seems that the ramdisk driver has somehow managed to
> compromise the livelock avoidance logic in the sync() system call.
>
> For now you can
>
> a) stop using the ramdisk driver (don't mount it) or
>
> b) manually run `blockdev --flushbufs /dev/hdXX' against the boot
> partition before rebooting.
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
--
uname -a: Linux garaged.fis.unam.mx 2.4.21-pre4-ac4 #5 SMP Thu Feb 13 10:26:24 CST 2003 i686 unknown unknown GNU/Linux
-----BEGIN GEEK CODE BLOCK-----
Version: 3.1
GS/ d-s:a-28C++ILHA+++P+L++>+++E---W++N*o--K-w++++O-M--V--PS+PEY--PGP++t5XRtv++b++DI--D-G++e++h-r+y**
------END GEEK CODE BLOCK------
gpg-key: http://garaged.homeip.net/gpg-key.txt
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2003-06-12 23:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-12 22:29 Unai Garro Arrazola
2003-06-12 22:43 ` Andrew Morton
2003-06-12 18:35 ` Max Valdez [this message]
2003-06-13 0:23 ` Samuel Flory
2003-06-13 0:44 ` Kurt Wall
2003-06-12 22:50 ` Unai Garro Arrazola
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=1055442915.2690.9.camel@garaged.homeip.net \
--to=maxvalde@fis.unam.mx \
--cc=linux-kernel@vger.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 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®