Re: ALTQ patch for if_vlan.c

On Thu, Jan 06, 2005 at 05:00:32PM +1030, Wilkinson, Alex wrote: > 0n Wed, Jan 05, 2005 at 12:51:56PM -0800, Brooks Davis wrote: > > >FYI, spl*() funtions are all no-ops now. We just have them around to > >remind us that we need to lock certain functions and to document what > >w

Re: ALTQ patch for if_vlan.c

0n Wed, Jan 05, 2005 at 12:51:56PM -0800, Brooks Davis wrote: >FYI, spl*() funtions are all no-ops now. We just have them around to >remind us that we need to lock certain functions and to document what >was protected before. What is meant by "no-ops" ? - aW __

Re: unstable 5.3 boxes

At 06:29 PM 05/01/2005, Mitch Parks wrote: It seems both my test and production boxes are not stable with 5.3-Release. I'm hoping for some insight in how to make at least the production box not crash. The crashes have been at different times of the day and I've found no suspicious log activity.

Re: uplcom usb to serial adapter broken

On Thu, Jan 06, 2005 at 10:33:18AM +1030, Daniel O'Connor wrote: > > What does the device probe as? Let's see 'pciconf -l'. > > I think you mean usbdevs :) Bah, humbug. Yes, that's what I mean. :) > Also the output of dmesg after insertion would be useful. Yah, what he said! > I have one of

Re: SATA/UDMA100 support on ATI RS300 chipset?

On Wed, 05 Jan 2005 15:33:48 -0700, secmgr <[EMAIL PROTECTED]> wrote: > That would be ASUS who would have embedded the 3COM chip. probably > special order, which is why it didn't report back something recognized. > The ATI chipset is pretty new vs the more tried and known > nVIDIA/SiS/VIA/AMD [So

Re: uplcom usb to serial adapter broken

On Thu, 6 Jan 2005 08:48, Brian Reichert wrote: > On Wed, Jan 05, 2005 at 11:29:18AM -0700, Ryan Falkenberg wrote: > > I have a PL-2303 usb to serial adapter that I am trying to make work > > on my laptop that I've recently migrated to freebsd 5.3 from linux. > > What does the device probe as? Let

Re: mysql crashes on 5.3-stable, SMP, linuxthreads

Billy Newsom wrote: I have just built a FreeBSD 5.3 box with SMP enabled on a dual processor machine. I kept having a lot of crashes at some point in the install, and I believe I now have the cuprit: mysql-server-4.1.7 is doing it. Lately, when mysql-server is running under no load, it caused

unstable 5.3 boxes

It seems both my test and production boxes are not stable with 5.3-Release. I'm hoping for some insight in how to make at least the production box not crash. Production Box: Dell 2600, Dual 2.8 Xeon, 2Gb ram, onboard (amr) RAID. This box was stable running 5.1, 5.2, and 5.2.1, but has crashed/r

Re: netstat fails with memory allocation error and error in kvm_read

On Wednesday 05 January 2005 18:26, J. Martin Petersen wrote: > > I just got another "netstat: kvm_read: Bad address". > > vm.kvm_free was 675278848 two seconds earlier and a couple of > > seconds later (and also currently). > > We just had another hard hang, and this time I managed to break to the

Re: uplcom usb to serial adapter broken

On Wed, Jan 05, 2005 at 11:29:18AM -0700, Ryan Falkenberg wrote: > I have a PL-2303 usb to serial adapter that I am trying to make work > on my laptop that I've recently migrated to freebsd 5.3 from linux. What does the device probe as? Let's see 'pciconf -l'. -- Brian Reichert

RE: IBM ServeRAID 7k & 5.3

Hi, I'm looking at the same issue with a Serveraid 6i in an xSeries x226. In hindsight, I should have specified an iir controller, possibly with some machine other than an IBM! There seems to be an ioctl where a user mode program can issue a command to the controller to find out what is going on

Re: USB scanner not attached when connected after system startup]

On Mon, Jan 03, 2005 at 09:32:20PM +0100, Roland Smith wrote: > That's not good. AFAICT, the code that reports a new scanner to dmesg is > also present in 4.x, so if you don't see a message, it looks like the > scanner is not found for one reason or another. > > Do you see anything in dmesg if i

Instant reboots with CPUTYPE=pentium-m

Hi list, I am still having the problems with instant reboots that I reported [1] a couple of weeks ago. I have a bit more info now and hope that someone can lead me in the right direction. The problem is that setting CPUTYPE=pentium-m in make.conf leads to a corrupt boot loader and a corrupt ke

Re: ALTQ patch for if_vlan.c

On Wed, Jan 05, 2005 at 12:32:55PM -0800, Jon Simola wrote: > I just whipped up this against > 5.3-STABLE #1: Wed Dec 22 17:11:02 PST 2004 > > Would someone who knows a bit more about this than myself give it a > quick lookover and see if it appears sane? I'm mostly wondering about > the splimp()

ALTQ patch for if_vlan.c

I just whipped up this against 5.3-STABLE #1: Wed Dec 22 17:11:02 PST 2004 Would someone who knows a bit more about this than myself give it a quick lookover and see if it appears sane? I'm mostly wondering about the splimp() and splx() and whether it's required or excessive due to the mtx_lock/un

Missing Man-Pages in RELENG_4

Hi, i miss the manpages for ipf.conf ipnat.conf under RELENG_4 last updated 2005-01-05 via cvsup. thanks regards Michael ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail

uplcom usb to serial adapter broken

I have a PL-2303 usb to serial adapter that I am trying to make work on my laptop that I've recently migrated to freebsd 5.3 from linux. After loading ucom and uplcom I can connect to and send commands to serial devices with minicom but I cannot see the results of any commands. If I connect to a

RE: netstat fails with memory allocation error and error in kvm_read

> I just got another "netstat: kvm_read: Bad address". > vm.kvm_free was 675278848 two seconds earlier and a couple of > seconds later (and also currently). We just had another hard hang, and this time I managed to break to the debugger on the serial console. I got this stack trace

Re: fsck: broken file system with background check remains broken after bootup

Craig Boston <[EMAIL PROTECTED]> wrote: > On Tuesday 04 January 2005 9:57 pm, Wilkinson, Alex wrote: > > How can I confirm that ACPI has been setup to do this ? > > Hmm, well, the easiest thing to check is to run > > sysctl hw.acpi.power_button_state > > and see if that sysctl exists and

Sound Card Troubles

Im having a bit of difficulty in getting sound to work, due to the fact i have On-Board Sound as well as a Sound Card (PCI) .. im wanting to use both but being a lil new im unsure of hwo to procedd, could someone please point me in the right direction ? -- Yours Sincerely Shinjii http://www.shi

RELENG_3: SMP/ACPI on ASUS CUR-DLS possible?

Dear Sirs. I use FreeBSD 5.3-STABLE, most recently updated and built-world today. I realised strange behaviour with the used ASUS CUR-DLS mainboard and FreeBSD 5.3-{RELEASE|STABLE}. SMP is impossible on this mainboard with FreeBSD 5.3. With or without ACPI enabled, the machine crashes after a w

Re: libmap.conf and ports

On Wednesday, 5. January 2005 10:33, [EMAIL PROTECTED] wrote: > Hi all, > > I have major problems to compile gpgme-1.0.1 on *some* machines (see > below). > > Before all the compile/link-errors one major question: > > What about /etc/libmap.conf and the mapping of libc_r to libpthread? > It was onc

Re: fsck: broken file system with background check remains broken after bootup

On Wednesday, 5. January 2005 04:29, Wilkinson, Alex wrote: > 0n Tue, Jan 04, 2005 at 02:01:22PM +0100, Oliver Fromme wrote: > >By the way, you can map a key combination (Ctrl-Alt-Del or > >something else) to the »halt« or »power-down« functions, > >using kbdcontrol, so it's very ea

libmap.conf and ports

Hi all, I have major problems to compile gpgme-1.0.1 on *some* machines (see below). Before all the compile/link-errors one major question: What about /etc/libmap.conf and the mapping of libc_r to libpthread? It was once recommended and I never heard anything about it. Is it still recomm

SATA/UDMA100 support on ATI RS300 chipset?

I have an ASUS Pundit-R chassis with an integrated ATI RS300 based motherboard. The IDE controller is detected but only as a generic controller: atapci0: port 0xff00-0xff0f,0x376,0x170-0x177,0x3f6,0x1f0-0x1f7 at device 20.1 on pci0 ata0: channel #0 on atapci0 ata1: channel #1 on atapci0