Just had a Windows experience in Mandrake 8.2

Post #79,056

2/3/03 8:18:49 PM

Was copying over stuff from a CD-R. Started getting momentary hangs in the whole system. No response for about a second. Then read errors.

I tried to kill -9 the job. It wouldn't die. Tried all the kill signals I could think of. No dice. Tried to umount the CD as root. "Device busy." Hit the button on the drive, no open.

Tried to reboot. The shutdown hung on the CD drive "bad seek" or some such. Had to hit the reset switch.

It's a vanilla ATAPI CDROM drive slaved behind a CD burner. Granted the disk must be bad. But surely a proper OS should handle the situation better than this?

"Going to a march organized by Communists doesn't make you a Communist, any more than going to a march organized by Nazis makes you a Nazi." - Glenn Reynolds
The trouble with the French is they have no word for "roulons."
CHICKENHAWK! Scourge of clucking hens everywhere!
Victory is the answer. There are no alternatives.
[link|http://www.angelfire.com/ca3/marlowe/index.html|http://www.angelfire...arlowe/index.html]

Post #79,061

by deSitter

2/3/03 8:55:56 PM

Can't fight wrong hardware

I have utter confidence in device drivers. Whoever writes them does a wonderful job. It takes a certain kind of mind to do that. The funny thing - all this code that works by sticking to the rules - usually it's fugly. An exception is the real Linus code.

So if your system is bitching like that, it must be a hardware issue.

-drl

Post #79,062

by boxley

2/3/03 8:56:15 PM

You had a hardware plunk

I am not sure if umount -F(force) is part of mandrake. The reboot command is trying to gracefully shut the system via umount which failed. When you did the kill -9 did you try the original spawning pid?
thanx,
bill

will work for cash and other incentives [link|http://home.tampabay.rr.com/boxley/resume/Resume.html|skill set]

questions, help? [link|mailto:pappas@catholic.org|email pappas at catholic.org]

Post #79,080

by folkert

2/3/03 10:02:08 PM

Nope...

That is part of the problems currently with the mixed "ide-scsi"/atapi stuff in the kernel.

Kinda why they are swapping in the device mapper...

Also, if it's a "generic CDROM" isn't as compliant with ATAPI as it should be ... well that just complicates the problem more.

I've had that problem with everything except... Kernels with the some of the I/O patches out there ones design to account for spin-locks and time-outs and such...

Which version of the Kernel you running? 2.4.18+ has much better handling... but will still bung-up like that in specific configs and situations.

Yes, I do keep to much in my head... a plethora of useless/useful information... just wish I could speak and write it all down sometimes... ;)

[link|mailto:curley95@attbi.com|greg] - Grand-Master Artist in IT

[link|http://www.iwethey.org/ed_curry/|REMEMBER ED CURRY!] [link|http://pascal.rockford.com:8888/SSK@kQMsmc74S0Tw3KHQiRQmDem0gAIPAgM/edcurry/1//|ED'S GHOST SPEAKS!]

[link|http://www.eweek.com/article2/0,3959,857673,00.asp|Even Microsoft will develop apps for Linux by 2004]

Heimatland Geheime Staatspolizei reminds:
These [link|http://www.whitehouse.gov/pcipb/cyberstrategy-draft.html|Civilian General Orders], please memorize them.
"Questions" will be asked at safety checkpoints.

Post #79,169

by rickmoen

2/4/03 10:17:16 AM

Re: Just had a Windows experience in Mandrake 8.2

marlowe wrote:

Was copying over stuff from a CD-R. Started getting momentary hangs in the whole system. No response for about a second. Then read errors.

I tried to kill -9 the job. It wouldn't die. Tried all the kill signals I could think of. No dice. Tried to umount the CD as root. "Device busy." Hit the button on the drive, no open.

Tried to reboot. The shutdown hung on the CD drive "bad seek" or some such. Had to hit the reset switch.

It's a vanilla ATAPI CDROM drive slaved behind a CD burner. Granted the disk must be bad. But surely a proper OS should handle the situation better than this?

Not really. Addressing ATAPI devices requires running some fairly dogdy stuff in kernelspace. If the driver or the CD drive hardware itself has a problem while doing an uniterruptable operation in kernel mode, you're potentially screwed: Effectively, the kernel can seize up.

I still insist on using SCSI (except on my laptops). The syndrome's much rarer, there.

Rick Moen
rick@linuxmafia.com

If you lived here, you'd be $HOME already.

Welcome to IWETHEY!