When running a find | xargs grep on the cdrom the system will hang and then eventually reboot. How-To-Repeat: Mount the live filesystem disk from 2.1.0-RELEASE and then : cd /cdrom/usr/include find . -print | xargs grep -il wantthis
As Andrew Herdman wrote: > When running a find | xargs grep on the cdrom the system will hang and > then eventually reboot. Where is it mounted? From the SCSI, or the ATAPI CDROM? My /etc/daily used to reference all my mounted CDs for ages now, and i've never noticed a problem. Of course (:-), all of them are SCSI devices. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-)
On Sun, 26 May 1996, J Wunsch wrote: > As Andrew Herdman wrote: > > > When running a find | xargs grep on the cdrom the system will hang and > > then eventually reboot. > > Where is it mounted? From the SCSI, or the ATAPI CDROM? > > My /etc/daily used to reference all my mounted CDs for ages now, and > i've never noticed a problem. Of course (:-), all of them are SCSI > devices. > It happens with both SCSI and ATAPI devices. The system I use at home is SCSI and the one at work is ATAPI and they both give the same result, which is !crash! Andrew
As Andrew Herdman wrote: > > Where is it mounted? From the SCSI, or the ATAPI CDROM? > It happens with both SCSI and ATAPI devices. The system I use at home is > SCSI and the one at work is ATAPI and they both give the same result, > which is !crash! I'm afraid you will have to investigate more if you want this solved. Nobody else except you complained about it, and i'm pretty sure there are enough other people like me who regularly scan entire CDs. So it looks like it's only reproducible in your situation. (Perhaps you can get a kernel core dump? DDB output?) -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-)
On Mon, 27 May 1996, J Wunsch wrote: > As Andrew Herdman wrote: > > > > Where is it mounted? From the SCSI, or the ATAPI CDROM? > > > It happens with both SCSI and ATAPI devices. The system I use at home is > > SCSI and the one at work is ATAPI and they both give the same result, > > which is !crash! > > I'm afraid you will have to investigate more if you want this solved. > Nobody else except you complained about it, and i'm pretty sure there > are enough other people like me who regularly scan entire CDs. So it > looks like it's only reproducible in your situation. > > (Perhaps you can get a kernel core dump? DDB output?) Ok i just did it and got a core and here is what gdb shows me: gdb -k kernel.1 vmcore.1 GDB is free software and you are welcome to distribute copies of it under certain conditions; type "show copying" to see the conditions. There is absolutely no warranty for GDB; type "show warranty" for details. GDB 4.13 (i386-unknown-freebsd), Copyright 1994 Free Software Foundation, Inc...(no debugging symbols found)... IdlePTD 1df000 current pcb at 1cbb18 panic: vwakeup: neg numoutput #0 0xf017a547 in boot () (kgdb) bt #0 0xf017a547 in boot () #1 0xf0115236 in panic () #2 0xf012cbab in vwakeup () #3 0xf01297ee in biodone () #4 0xf0154153 in cd_strategy () #5 0xf0158dec in scsi_strategy () #6 0xf01539b8 in cdstrategy () #7 0xf0135d5a in spec_strategy () #8 0xf01050a0 in cd9660_strategy () #9 0xf012ac83 in cluster_read () #10 0xf01046d5 in cd9660_read () #11 0xf0131bd8 in vn_read () #12 0xf01168a7 in read () #13 0xf0180321 in syscall () #14 0xf0177e15 in Xsyscall () #15 0x6012 in ?? () #16 0x6cb0 in ?? () #17 0x1095 in ?? () I'll also put the dumps for anon ftp from ghoul.uunet.ca in /pub/ Andrew
State Changed From-To: open->feedback confirm status
State Changed From-To: feedback->closed The originator says that this is fixed in -current.