Re: Grip Causing System Lockup
On Tue, Mar 18, 2003 at 06:20:20PM -0600, Joseph A Nagy Jr wrote: > nate wrote: > >Joseph A Nagy Jr said: > > >probably not so much a grip problem as an I/O problem. Any way to > >check the kernel logs on the machine? I'm thinkin they are getting > >flooded with I/O errors, in which case there's not a whole lot you > >can do, besides try not to use discs that generate such errors. Sometimes > >a process that is recieving these errors can be killed, othertimes it > >cannot. Really depends. > > > >but the symtoms you describe are in my experience similar to generic > >I/O errors which can be triggered by most any program accessing > >the hardware. > > > >nate > > That is what I was fearing. :( Did you try to renice it? renice +20 pidof grip Grip is just a wrapper around a bunch of other tools. You might try using cdparanoia (ripping tool) directly. There are some command-line options which may prove handy. I once had serious slowdowns with grip and certain CD's It was awhile ago, but I think, (although I'm not sure) that it was at least in part to scsi emulation on my cdrom drive. If you're using the ide-scsi kernel module, try disabling it while you rip those essential discs. That's usually enabled/disabled via an "append=" line in your lilo.conf more food for thought... -troy -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Grip Causing System Lockup
nate wrote: Joseph A Nagy Jr said: probably not so much a grip problem as an I/O problem. Any way to check the kernel logs on the machine? I'm thinkin they are getting flooded with I/O errors, in which case there's not a whole lot you can do, besides try not to use discs that generate such errors. Sometimes a process that is recieving these errors can be killed, othertimes it cannot. Really depends. but the symtoms you describe are in my experience similar to generic I/O errors which can be triggered by most any program accessing the hardware. nate That is what I was fearing. :( -- http://mc-luug.homelinux.org MC-LUUG Home Page http://www.hsv-hotspots.com/ Your hotspot for Wireless in HSV, AL -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Grip Causing System Lockup
Nicos Gollan wrote: On Tuesday 18 March 2003 23:23, Joseph A Nagy Jr wrote: Hi All, I've recently been having problems where if grip encounters a particular nasty track, it will totally slow down the computer but continue ripping (albeit at 0.1x). Clicking repeatedly on abort rip (or abort rip + encode (the encoding process dies just fine)) seems to have no effect and I usually have to resort to rebooting the whole system. Is this a known issue with Grip? Could it be that you're trying to rip a defective (copy-protected) disc? The slowdown indicates that something is probably screwing up the drive. Well, one disc is in absolute pristine condition. No scratches, mars, or known copy-protection (it was pressed in 1994), the other plays very well, pressed in 1997. The other cd has known problems on one of the tracks, but that's it (although it locks up the instant I start ripping). It could also be an old or badly pressed disc. I got some old discs that will play fine oin some players and fail at a certain position in others. Poo. I was hoping it was a problem with GRIP. These happen to be CD's I consider 'vital' to my collection (either for depth of music for a track or two or just sheer mind-blowing awesomeness of the entire compilation) -- http://mc-luug.homelinux.org MC-LUUG Home Page http://www.hsv-hotspots.com/ Your hotspot for Wireless in HSV, AL -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Grip Causing System Lockup
Joseph A Nagy Jr said: > Hi All, > > I've recently been having problems where if grip encounters a particular > nasty track, it will totally slow down the computer but continue ripping > (albeit at 0.1x). Clicking repeatedly on abort rip (or abort rip + encode > (the encoding process dies just fine)) seems to have no effect and I > usually have to resort to rebooting the whole system. Is this a known > issue with Grip? > > BTW, running grip 3.0.0 from KDE 2.2.2 under Debian Woody 3.0r0 probably not so much a grip problem as an I/O problem. Any way to check the kernel logs on the machine? I'm thinkin they are getting flooded with I/O errors, in which case there's not a whole lot you can do, besides try not to use discs that generate such errors. Sometimes a process that is recieving these errors can be killed, othertimes it cannot. Really depends. but the symtoms you describe are in my experience similar to generic I/O errors which can be triggered by most any program accessing the hardware. nate -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Grip Causing System Lockup
On Tuesday 18 March 2003 23:23, Joseph A Nagy Jr wrote: > Hi All, > > I've recently been having problems where if grip encounters a particular > nasty track, it will totally slow down the computer but continue ripping > (albeit at 0.1x). Clicking repeatedly on abort rip (or abort rip + > encode (the encoding process dies just fine)) seems to have no effect > and I usually have to resort to rebooting the whole system. Is this a > known issue with Grip? Could it be that you're trying to rip a defective (copy-protected) disc? The slowdown indicates that something is probably screwing up the drive. It could also be an old or badly pressed disc. I got some old discs that will play fine oin some players and fail at a certain position in others. -- Got Backup? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
