Here are some `funnies' that I have found with USB hard disks. Strictly off topic for `Re: [Cooker] kernel panic debugging' but it may help.

1) Some USB disk drives will also cause a kernel panic if plugged in during a boot. These tend to be the `in caddy' type rather than the key fob type. Solution in this case is only to plug them in after the boot has finished. Harddrake doesn't help with this one at all.

2)
Take a PC with two USB ports and refer to them as A and B.
Plug a USB disk drive (of any type) into A.
Mount it, (do some accesses if you wish) and unmount it.
Leave the PC for a while (no exact timings available)
Plug ANOTHER USB disk into A and attempt to mount it.
Error appears typically stating that /dev/sdaX is not a mountable
volume
Plug same drive into B and attempt to mount it.
Success
Plug the original drive into A and attempt to mount it.
Success

Result:
Both USB ports are now hard wired to only accept specific hard discs!
A reboot is required to use other disck drives.
If by any chance another disk drive does actually mount the system
will always lock solid usually during a copy or move to the USB disc.


3) There is a kernel patch for the SanDisk USB disk caddies but this does not appear to have been incoporated into the Mandrake kernel.

Thanks,
Owen

Pascal Cavy wrote:
Le Vendredi 24 Janvier 2003 12:25, Chmouel Boudjnah a �crit :


humm let's try by each case, what if you remove the /etc/modules.conf
and reboot does it do alway start ?

what do you have in your /etc/modules.conf ?
/etc/modules and /etc/modules.conf as I use them now (with the random
boot lock) are attached.

testing without these module will proceed shortly.
I'll also test with the latest kernel.
try to just disable ov511 and reboot...

Well well I've done numerous reboots and tests, and dear people here are the results of the french jury :

- latest kernel has the same behaviour (stuck somewhere in rc3.d/xxxx) as previous

- removing ov511 (from modules.conf and physically) does not cure the problem
- more interesting, maybe this manipulation can make you reproduce the behaviour:
1. get at least 2 usb devices connected and recognized at boot (I have intellimouse explorer usb, epson 1200u scanner and ov511 webcam)
2. boot and let harddrake configure all this
3. reboot several times maybe it will stuck 4. if not, just shutdown, remove the usb mouse (or ONE usb device)
5. reboot, let hardddrake complains and timeout and boot continuing
6. reboot this time the boot stops (in harddrake ?)
I absolutly cannot have a complete boot this time until I replugged the mouse and harddrake configures it.

- belgium 3 poyyynnnntsssssssss




Reply via email to