Date: Wed, 25 Jul 2001 22:45:11 -0700 From: "Ted Mittelstaedt" <tedm@toybox.placo.com> To: "Jim Arnold" <jim@ohio.com>, <freebsd-questions@FreeBSD.ORG> Subject: RE: spontaneous reboots: how common in general? Message-ID: <002c01c11596$22fa6f00$1401a8c0@tedm.placo.com> In-Reply-To: <a05100310b784b6ce51b0@[206.128.102.10]>
next in thread | previous in thread | raw e-mail | index | archive | help
I'll bet your running an IDE cdrom right? Stuff like this doesen't happen with SCSI because the SCSI command set is very tightly defined. IDE/ATAPI on the other hand, particularly with CDROMs, is spec of the month. Most likely what the problem is that the CDROM drive that you were attempting to read the CD from used a non-standard error return code that the ATAPI driver doesen't have in it's list. This has been discussed before on this list. There's ways that you can identify this and submit it to the ATAPI developer who can add it in to the driver so that instead of panicing, the system just comes back with an error message. But most people just find some Windows system with a different model of CDROM drive in it that's willing to make "a donation" and swap CD drives. Then the Windows user gets the problem drive, but since Windows crashes so much anyway, when it happens to them the users don't realize that the system is not supposed to be crashing. Your NFS panic on the other hand, well that's just NFS. There's a reason that it's nicknamed the Network Flaying System. Ted Mittelstaedt tedm@toybox.placo.com Author of: The FreeBSD Corporate Networker's Guide Book website: http://www.freebsd-corp-net-guide.com >-----Original Message----- >From: owner-freebsd-questions@FreeBSD.ORG >[mailto:owner-freebsd-questions@FreeBSD.ORG]On Behalf Of Jim Arnold >Sent: Wednesday, July 25, 2001 10:54 AM >To: freebsd-questions@FreeBSD.ORG >Subject: Re: spontaneous reboots: how common in general? > > >maybe i have chosen my wording poorly. by spontaneous reboots i >don't mean that >the computer is just happily crunching away and then for no reason it >just reboots. > >I'm talking about doing *something* that literally freaks FreeBSD out and >it reboots instead of handling the situation or letting you kill the >offending >process. > >as an example today i went to copy mp3 files off a cd i burned at home >on my my FBSD box and transfer them to my FBSD work box. For some >reason I was getting a "bad address" error on one file. > >I tried to copy that file to another directory when a weird buzzing >sound started >coming out of my speakers. X locked up and i could not ssh into into the box. >about 20 seconds after it started the computer just rebooted itself. > >hope that helps clarify. > >jim > >>I have only had this problem with bad memory. >> >>Ray >> >>On Wed, 25 Jul 2001, Jim Arnold wrote: >> >>> I have been working with FreeBSD now (4.3 Stable and Release) for >>>the past few >>> months on several different boxes. Before that I was running >Slackware Linux >>> for about a year and and half. >>> >>> On three of four different occasions I have had my FreeBSD boxes >>>spontaneously >>> reboot. Once it was due to an NFS situation (from what I could guess) >>> and two or three other times >>> it was due to me trying to mount a cdrom that shouldn't be mounted or >>> a cdrom that had a bad file on it >>> that didn't want to be copied to the hard drive. >>> >>> How common, in general, are spontaneous reboots in the FreeBSD world? >>> I never once >>> had my Linux box just give up like FreeBSD seems willing to do. From >>> what I have read >>> softupdates adds a layer of protection again system corruption in >>> these situations. >>> >>> I guess my expectations coming to FreeBSD from Slackware were pretty >>> high so I am somewhat >>> surprised this has happened as often as it has. Other than that, my >>> experience with FreeBSD has >>> been great. It's head and shoulders above Linux in everything else. >>> >>> Can anyone give some insights or perspective on this? Is this FreeBSD >>> glass jaw? How serious >>> or potentially damaging are these kinds of spontaneous reboots and >>> why does FreeBSD seem more >>> prone to these than Linux. Even if I did something stupid I didn't >>> expect FreeBSD to just take its >>> toys, reboot and go home. >>> >>> Just wondering what other's experiences are. >>> >>> Thanks, >>> Jim >>> >>> To Unsubscribe: send mail to majordomo@FreeBSD.org >>> with "unsubscribe freebsd-questions" in the body of the message >>> >> >> >>To Unsubscribe: send mail to majordomo@FreeBSD.org >>with "unsubscribe freebsd-questions" in the body of the message > > >-- > >___________________________________________________________ >Jim Arnold <jim@ohio.com> Voice: 330.253.9524 x 9-12 >Ohio.com Site Administrator Fax: 330.253.8214 >http://www.ohio.com Cell: 330.730.0797 >AOL IM: instantjim > >12 E. Exchange Street - 2nd Fl -- Akron, OH 44308 > > >To Unsubscribe: send mail to majordomo@FreeBSD.org >with "unsubscribe freebsd-questions" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?002c01c11596$22fa6f00$1401a8c0>