search for: emmerton

...d; all other filesystems are scheduled for background fsck 6) Encounter panic "ffs_valloc: dup alloc" 7) In debugger, reset (or panic to get vmcore) Attached is the full dmesg and stacktrace output from kgdb for the *second* panic, since I figure this is the more critical issue. -- Matt Emmerton -------------- next part -------------- Script started on Sat Mar 18 12:58:13 2006 root@gabby# kgdb /boot/kernel/kernel.debug vmcore.0 [GDB will not be able to debug user-mode threads: /usr/lib/libthread_db.so: Undefined symbol "ps_pglobal_lookup"] GNU gdb 6.1.1 [FreeBSD] Copyright 2004 F...

Hi there, I'm having an odd problem where this NIC (cheap-o, yes I know) doesn't seem to work on FreeBSD correctly. I have the same cards (even revision models) in two win boxen and they work fine. 10baseT works but not 100baseT. With a normal NIC config, without explicitly setting the media to 10baseT, it will autosense as 100BaseT @ full-duplex, showing active. However I can't

I know this is a freeBSD mailing list, but I didn't know where else to ask this question. I've recently switch to FreeBSD 4.8 (great OS btw), and I've been so pleasantly surprised that i'm now planning to switch over my dad's firm over to freeBSD. There computers/software are rapidly getting old and obselete, and microsoft's price/security is...well expensive/crap.