Re: -STABLE NVidia drivers

On Saturday 17 November 2001 12:41 am, you wrote: Hi, Hey, Well, since nobody seems to be interested (I can't for the life of mine understand why), thanks and a couple of (perhaps silly) questions. i) any plans on porting to -CURRENT? On GLX stuff? And does it work with DEVFS? I have

Re: Tracking down BTX halted

On Fri, 16 Nov 2001, Matthew Emmerton wrote: There is a bug in Adaptec BIOSen that they will not tolerate DD disks. Which controllers have this bug? I've got a whole bunch of 7880 and 79xx controllers with disks running in DD mode and never have had this problem. Happens to me on L440GX+

Re: Tracking down BTX halted

There is a bug in Adaptec BIOSen that they will not tolerate DD disks. Which controllers have this bug? I've got a whole bunch of 7880 and 79xx controllers with disks running in DD mode and never have had this problem. Happens to me on L440GX+ boards. Also happens on IBM Netfinity

Re: -STABLE NVidia drivers

Vladimir Kushnir wrote: Well, since nobody seems to be interested (I can't for the life of mine understand why), thanks and a couple of (perhaps silly) questions. I'm interested, I've just been busy thats all. I haven't had a chance to play with the drivers yet. Thanks David! To

Re: Tracking down BTX halted

Doug White wrote: On Fri, 16 Nov 2001, Sandeep Joshi wrote: I changed the disklabels on a few SCSI disks and now I keep getting these BTX halted messages every time I reboot. Lemme guess, you're running them in 'dangerously dedicated' mode. There is a bug in Adaptec BIOSen that

Re: Tracking down BTX halted

Doug White wrote: On Fri, 16 Nov 2001, Matthew Emmerton wrote: There is a bug in Adaptec BIOSen that they will not tolerate DD disks. Which controllers have this bug? I've got a whole bunch of 7880 and 79xx controllers with disks running in DD mode and never have had this problem.

Does DDB's watch feature actually work?

I've been using DDB the last few days attempting to track down a supposed bug in our TCP/IP stack. (See PR/31746). From what I've been able to tell so far (using the ugly insert-printf-here mechanism of debugging), a structure is getting zeroed which is causing the problem reported in the PR.

vkm problem or vmstat problem

Hi guys: I got a weird problem in version 4.1 stable. my vmstat all the sudden stopped working. it compains no _kmemstatistics, _bucket, _zlist, symbols from the kvm_nlist() in vmstat. I tried many ways, such as doing nm /kernel, I can see the b _bucket symbol. How come vmstat still compains?