Jaye Mathisen wrote:
>
> UDP v2 mounts, Netapp Filer.
>
> Getting a fair # of:
> got bad cookie vp 0xd24bf1c0 bp 0xc9090500
> got bad cookie vp 0xd24bfda0 bp 0xc906ceb0
>
> on the console, and it seems to lock the machine up for several minutes
> when it does. Then it comes back to life, and c
Alexander Langer wrote:
> Thus spake Wilko Bulte ([EMAIL PROTECTED]):
>
> > I just upgraded one of my boxes to 4.0-stable. Now I seem to have
> > a 'unknown card' on the PCI, seems related to the bktr. I remember
>
> That is the Radio-chip of your TV-card:
>
> > bktr0: mem 0xe700-0xe7000ff
In the last episode (May 21), Christian Weisgerber said:
> Arun Sharma <[EMAIL PROTECTED]> wrote:
>
> > http://sharmas.dhs.org/~adsharma/projects/freebsd/truss-diff.gz
>
> Those gratuitous whitespace and formatting changes are a pain...
>
> Related question:
> Currently, truss does very little
On Sun, May 21, 2000 at 06:35:55PM +0200, Alexander Langer wrote:
> Thus spake Wilko Bulte ([EMAIL PROTECTED]):
>
> > I just upgraded one of my boxes to 4.0-stable. Now I seem to have
> > a 'unknown card' on the PCI, seems related to the bktr. I remember
>
> That is the Radio-chip of your TV-car
It's just another part of the card that doesn't need to have a driver for
it to function, take a look at my dmesg:
bktr0: mem 0xe9002000-0xe9002fff irq 5 at device 17.0 on pci0
bktr0: Hauppauge Model 61291 D110
Hauppauge WinCast/TV, Philips NTSC tuner.
pci0: (vendor=0x109e, dev=0x0878) at 17.1
Thus spake Wilko Bulte ([EMAIL PROTECTED]):
> I just upgraded one of my boxes to 4.0-stable. Now I seem to have
> a 'unknown card' on the PCI, seems related to the bktr. I remember
That is the Radio-chip of your TV-card:
> bktr0: mem 0xe700-0xe7000fff irq 7 at device 10.0 on
I just upgraded one of my boxes to 4.0-stable. Now I seem to have
a 'unknown card' on the PCI, seems related to the bktr. I remember
there was a posting once with a WWW pointer to a PCI-ID database. Alas
I cannot find that pointer :-(
Any clue what I'm looking at? Fxtv works like a charm BTW
bkt
Arun Sharma <[EMAIL PROTECTED]> wrote:
> http://sharmas.dhs.org/~adsharma/projects/freebsd/truss-diff.gz
Those gratuitous whitespace and formatting changes are a pain...
Related question:
Currently, truss does very little parsing of syscall arguments.
That table in syscalls.c looks anemic. Is t
On 19-May-00 Warner Losh wrote:
> Actually, forget what I said. Mike smith's way is much cleaner.
> Assuming that the batteries have enough juice in them to do the
> reboot.
Doesn't matter if they do or not though..
If it powers down while you are starting up, so what? :)
---
Daniel O'Connor
Steven Kehlet wrote:
>
> With 3.4-STABLE code, cvsup'd on Tues May 9th, enabling -DNAMEBLOCK in
> /sys/i386/boot/biosboot/Makefile breaks the build:
^^^
We no longer use that. I'm surprised it is present at all in 3.4's
source code. Alas... maybe it is an old version that s
Thus spake Sergey Babkin ([EMAIL PROTECTED]):
> the old version somehow wedges the system. And upgrading drivers
> on a running production system is not something I personally would
> do. This is a dangerous operation and if it would cause any problems
Heh. Of course.
But also the bktr-driver,
Before I go to sleep, I've shortened the diff by about 50%. The new diff
is at:
http://sharmas.dhs.org/~adsharma/projects/freebsd/truss-diff.gz
http://sharmas.dhs.org/~adsharma/projects/freebsd/truss.tar.gz
To be applied as:
cd truss
gzcat -dc truss-diff.gz | patch -p1
The real 100 lines of ch
12 matches
Mail list logo
