2.5.70: Lilo needs patching?

2.5.70: Lilo needs patching?

[Unai Garro Arrazola]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

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? 

Thanks in advance

[Please, if you don't mind,  CC me off this list. I can't subscribe to it due 
to the high volume of mails it has every day. Thanks.]

	Unai
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)

iD8DBQE+6P7YhxDfDIoZlaURAv8zAJ9Kbd5rDgACuwP7vXcysKshdOcqtgCeNBfZ
WQ7tTe2kJzEgubPRCKxg69U=
=51n8
-----END PGP SIGNATURE-----

Re: 2.5.70: Lilo needs patching?

[Andrew Morton]

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.

Re: 2.5.70: Lilo needs patching?

[Max Valdez]

[-- 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 --]

Re: 2.5.70: Lilo needs patching?

[Samuel Flory]

Max Valdez wrote:

>
>BTW, only woosies have a boot disk, if anybody is willing to make the
>comment :-P
>  
>
  Real men pxeboot to an nfsroot instead;-)

-- 
There is no such thing as obsolete hardware.
Merely hardware that other people don't want.
(The Second Rule of Hardware Acquisition)
Sam Flory  <sflory@rackable.com>

Re: 2.5.70: Lilo needs patching?

[Kurt Wall]

Quoth Max Valdez:
> 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

Put me down as a major league "woosie", then, whatever that is.

Kurt
-- 
Why did the Lord give us so much quickness of movement unless it was to
avoid responsibility with?

Re: 2.5.70: Lilo needs patching?

[Unai Garro Arrazola]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Thursday 12 June 2003 23:43, Andrew Morton wrote:
>
> 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.

Thanks! I'll give it a try.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)

iD8DBQE+6QOnhxDfDIoZlaURAsfFAJkBrSfM1ykjuLUBqmuFqV8jZrMNegCfeayL
WX4A9Y1h8zzJQARYvWJ51KY=
=w8wL
-----END PGP SIGNATURE-----