Messages in this thread | | | Date | Fri, 10 Feb 2006 19:03:30 -0600 | From | "hackmiester (Hunter Fuller)" <> | Subject | Re: CD-blanking leads to machine freeze with current -git [was: Re: CD writing in future Linux try #2 [ was: Re: CD writing in future Linux (stirring up a hornets' nest) ]] |
| |
Hrm. ssh into the box and then try to blank the CD on the local machine. Is the ssh session still responsive? I suspect it will be, especially if the GNOME clock's still running. -- --hackmiester Walk a mile in my shoes and you will be a mile away in a new pair of shoes.
Marc Koschewski wrote: > * Phillip Susi <psusi@cfl.rr.com> [2006-02-10 14:19:16 -0500]: > > >>Marc Koschewski wrote: >> >>>I just tried blanking a CD-RW with the latest -git tree. The machine just >>>became >>>unresponsive and then froze. When it became unresponsive the clock in >>>GNOME still >>>displayed the current time but I could not focus any windows anymore. Then >>>I had >>>to hard reboot the machine. The logs say nothing. I repeat: nothing. >>> >>>Does anyone have similar problems? >> >>Instead of rebooting, just wait for the blanking to finish. My guess is >>that your burner and hard drive are both on the same ide channel, and so >>you can not access the disk while the burner is blanking. If this is >>the case, put each drive on their own ide channel. > > > I've been waiting 30 minutes for the machine to come back but no chance. SSH > didn't work either. I thought I could login remote... but uh uh. > > The problem is, it's a laptop. So there not much chance to move the cdrom device > over to another controller or whatever. ;) > > But let's face it: is it really crappy to render a laptop unusable just because > blanking a CD-RW. The circumstances were: run xcdroast via gksu (thus running as > root), blank CD-RW. Due to cd-burning being totally unusable as a user (problems > here and there if it was just doing anything at all). So I've no other chance > than to run this as root. Couldn't cdrecord 'watch' ide load or - even better - > forcecast it? It knows blanking leads to inresponsiveness sometimes (even more due > to the fact that both devices share the same bus). Why not kind of 'renice' > the process that blanks? > > Marc > - > 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/ > > - 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/
| |