On Tuesday 16 October 2001 11:07, Andrea Arcangeli wrote:
> Only in 2.4.13pre2aa1: 00_lvm-1.0.1-rc4-1.bz2
> Only in 2.4.13pre3aa1: 00_lvm-1.0.1-rc4-2.bz2
>
> Rediffed merging the unsigned long change in the blkdev size ioctl.
>
> Only in 2.4.13pre2aa1: 00_vm-3.1
> Only in 2.4.13pre3aa1: 00_vm-3.2
>
> Further vm minor updates. In particular make sure not to overstimate
> the amount of buffers available during balance_dirty(), by using the
> exact per-classzone active/inactive info.
>
> Only in 2.4.13pre2aa1: 50_uml-patch-2.4.12-1-1.bz2
> Only in 2.4.13pre3aa1: 50_uml-patch-2.4.12-3-1.bz2
>
> Latest update from Jeff.
>
> Only in 2.4.13pre2aa1: 60_tux-2.4.10-ac10-F5.bz2
> Only in 2.4.13pre3aa1: 60_tux-2.4.10-ac12-H1.bz2
>
> Latest update from Ingo.
>
> Andrea
I was expecting a more serious bug-fix. I recently upgraded my kernel from
2.4.11pre1 to 2.4.13-pre2aa1. Now anacron "kill"s the machine every morning
by starting updatedb. Basicly everything swaps out. If I don't touch the
mouse for 3 seconds, it will take 15 seconds to respond next time I touch it.
Switching between desktops in KDE, takes from 3 to 10 minutes, and updatedb
never seems to complete, I have had to kill it manually every time so far. I
had similar problems every morning with 2.4.9 although not as bad, but I
havent seen them before in 2.4.10 and later.
The problem is easily replicable, I just need to run updatedb. Would you like
some statistics and which?
regards
`Allan
-
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/
This archive was generated by hypermail 2b29 : Tue Oct 23 2001 - 21:00:14 EST