Date: Mon, 24 Feb 1997 13:15:02 -0600 (CST) From: Mark Tinguely <tinguely@plains.nodak.edu> To: kongwah@iss.nus.sg, multimedia@FreeBSD.org Subject: Re: unknown reboot reason on FreeBSD Message-ID: <199702241915.NAA29000@plains.nodak.edu>
next in thread | raw e-mail | index | archive | help
> I am running an licence plate recognition system > on a Pentium running FreeBSD and using the Matrox > Meteor card. > > I have reboot problems for no apparent reasons. > I am thinking of directing the reboot error > messages onto /var/log files, via syslogd. But I > would like to check out whether this reboot stuff > is already a well-known problem with you guys. I moved this to the -multimedia mailling list instead of the -questions mailling list, because more people on -multimedia can help you. Is the PCI chipset happen to be a Neptune? -- (you can tell by looking at the message when the system boots, it will say something like: chip0 <Intel 82434NX (Neptune) PCI cache memory controller> rev 17 on pci0:0 more information on the OS version, other devices such as SCSI. I can lock up a Neptune based PCI motherboard or cause a reboot of FreeBSD with the Meteor when I am BOTH capturing and displaying on the same machine. Move the same programs and cards to a Triton based PCI motherbaoard and the problem disappears. Also capturing on the Neptune based machine but displaying the information (X application) on another machine, there is no problems. Intel found that the Meteor and clones built on the same Phillips chipsets generate an illegel PCI code; this is why the meteor does not work with Pentium Pro machines. I reported the Neptune problem to Intel when they were looking into the Pentium Pro <> Meteor errors (they both have the same symptoms), but they did not pursue the Neptune. I suspect when both the video capture and heavy X use on the same PCI bus causes the Meteor error to be caught on the Neptune. --mark.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199702241915.NAA29000>