Re: loop problems continue in 2.4.3
If you're intent on making it oops why not write a script to mount/unmount it repeatedly? Regards, Aaron -Original Message- From: Arthur Pedyczak <[EMAIL PROTECTED]> To: Jens Axboe <[EMAIL PROTECTED]> CC: Linux kernel list <[EMAIL PROTECTED]>; Jeff Garzik <[EMAIL PROTECTED]> Sent: Sat Apr 14 08:46:49 2001 Subject: Re: loop problems continue in 2.4.3 On Sat, 14 Apr 2001, Jens Axboe wrote: [ SNIP..] > > = > > Apr 13 20:50:03 cs865114-a kernel: Unable to handle kernel paging request at virtual address 7e92bfd7 > > Please disable syslog decoding (it sucks) and feed it through ksymoops > instead. > > In other words, reproduce and dmesg | ksymoops instead. > > I tried to reproduce the error this morning and couldn't. Same kernel (2.4.3), same setup, same iso file. It mounted/unmounted 10 times with no problem. DOn't know what to think. Arthur - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] 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 [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
RE: Mount locks on bad ISO image?
I'm running 2.4.2 so it's probably just the broken loop device. Thanks, Aaron -Original Message- From: Guest section DW [mailto:[EMAIL PROTECTED]] Sent: March 29, 2001 15:13 To: Aaron Lunansky; [EMAIL PROTECTED] Subject: Re: Mount locks on bad ISO image? On Thu, Mar 29, 2001 at 02:16:03PM -0500, Aaron Lunansky wrote: > I tried mounting a file as an ISO image (turns out it was corrupted) - after > running mount file.iso /cdrom -o loop > mount hung and did not respond.. I could not ^Z it into the background, or > kill, or kill -9 it... > > I'm certain that I have ISO and loopback support compiled into my kernel. > > Anyone know what might be going on? Answer 1: in 2.4.2 the loop device does not work (but things are better in the -ac patches). Answer 2: the kernel tends to believe filesystem data, and a corrupted filesystem can seriously confuse the kernel. If you make sure that the problem does not lie in loop (you can mount other images without problems), then I wouldnt mind seeing your image (or rather, the first MB or two of it) to see whether the isofs code must be improved. (In that case, put some smallish fragment up for ftp and mail the URL to [EMAIL PROTECTED] Don't mail cd images.) Andries - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Mount locks on bad ISO image?
I tried mounting a file as an ISO image (turns out it was corrupted) - after running mount file.iso /cdrom -o loop mount hung and did not respond.. I could not ^Z it into the background, or kill, or kill -9 it... I'm certain that I have ISO and loopback support compiled into my kernel. Anyone know what might be going on? Regards, Aaron - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [OT] how to catch HW fault
Sounds like the only thing you haven't swapped out of your machine is the ram/cpu. It could very well be your ram (I don't suspect the cpu). If you can, try a different stick of ram. -Original Message- From: kees <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] <[EMAIL PROTECTED]> Sent: Sat Mar 17 11:29:35 2001 Subject: [OT] how to catch HW fault Hi, I'm getting mad because of random freezes of my system. Linux-2.2.19pre7 on MSI 694D dual PIII(677MHz) 128 MB, no OC. I tried to isolate the problem with replacing cards (S3 video, 3com 59X, ES1373 and AIC7xxx) didn't solve anything. Even in initlevel 1 with only a videocard the freeze happens. It is a total lockup, no SYSRQ , no ping from network, nothing in the logs. A freeze may happen 4 times in a hour or once in 2 weeks. I have the same mobo and PIII's at home without the slightest problems. Who knows of a suitable diagnostics to track this down? regards Kees - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] 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 [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
