[lkml]   [2003]   [Jun]   [12]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: 2.5.70: Lilo needs patching?
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 <> 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
> More majordomo info at
> Please read the FAQ at
uname -a: Linux 2.4.21-pre4-ac4 #5 SMP Thu Feb 13 10:26:24 CST 2003 i686 unknown unknown GNU/Linux
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**
[unhandled content-type:application/pgp-signature]
 \ /
  Last update: 2005-03-22 13:36    [W:0.036 / U:0.848 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site