> FYI,
>
> pre-patch-2.0.31-7 had no problems doing badblocks, while
> pre-patch-2.0.31-6 produced "Couldn't get a free page" and was
> unreachable over the network (no response to pings) for 10-20 sec.
>
> Interactive performance was sluggish throughout badblocks run with
> either kernel.
FWIW, people should probably be aware that almost no system in the world
will *not* be sluggish suring a badblocks run simply because the drive bus
is being nailed so hard that interactive work has to wait its turn in line
to get drive requests out the queue (which will be a rather large queue
when doing a badblocks -w).
*****************************************************************************
* Doug Ledford * Unix, Novell, Dos, Windows 3.x, *
* dledford@dialnet.net 873-DIAL * WfW, Windows 95 & NT Technician *
* PPP access $14.95/month *****************************************
* Springfield, MO and surrounding * Usenet news, e-mail and shell account.*
* communities. Sign-up online at * Web page creation and hosting, other *
* 873-9000 V.34 * services available, call for info. *
*****************************************************************************