RE: The bikeshed T-shirt
Cool! BTW, the real links are: http://phk.freebsd.dk/misc/bsdcon03.fig http://phk.freebsd.dk/misc/bsdcon03.pdf ...but I would have used a blue bicycle and a white roof. ;-) John > -Original Message- > From: Poul-Henning Kamp [mailto:[EMAIL PROTECTED] > Sent: Thursday, September 11, 2003 6:05 PM > To: [EMAIL PROTECTED] > Subject: The bikeshed T-shirt > > > > The bikeshed T-shirt which has been referred about was only produced > in 5 copies and I hadn't really expected that so many people would > ask me about it. > > I don't want to get into the clothing business, so if you want one, > you'll probably have to make it yourself. I can ask the company > which produced them if they will be willing to ship abroad, but I > doubt they are set up for that sort of thing. > > The xfig source is here: > http://phk.frebsd.dk/misc/bsdcon03.fig > http://phk.frebsd.dk/misc/bsdcon03.pdf > > Enjoy... > > -- > Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 > [EMAIL PROTECTED] | TCP/IP since RFC 956 > FreeBSD committer | BSD since 4.3-tahoe > Never attribute to malice what can adequately be explained by > incompetence. > ___ > [EMAIL PROTECTED] mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to > "[EMAIL PROTECTED]" > ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
RE: pci configuration
If you're using a server with the Compaq PCI-X Hot Plug controller, you can read the maximum bus speed and current device speed from the hot plug controller. For details, take a look at the drivers/pci/hotplug/cpqphp.h and drivers/pci/hotplug/cpqphp_core.c files in the latest Linux 2.6 kernel. Here are a couple links: http://lxr.linux.no/source/drivers/pci/hotplug/cpqphp_core.c?v=2.6.0-tes t2 http://lxr.linux.no/source/drivers/pci/hotplug/cpqphp.h?v=2.6.0-test2 Regards, John John Cagle [EMAIL PROTECTED] Principal Member Technical Staff Industry Standard Servers Hewlett-Packard Company > -Original Message- > From: Scott Long [mailto:[EMAIL PROTECTED] > Sent: Tuesday, August 12, 2003 8:55 PM > To: Doug White > Cc: [EMAIL PROTECTED]; Petri Helenius > Subject: Re: pci configuration > > > Doug White wrote: > > On Tue, 12 Aug 2003, Petri Helenius wrote: > > > > > >>Is there way to view PCI / PCI-X configuration with > bus-width and clock > >>values when FreeBSD has already booted? > > > > > > If you know where in PCI config space to look you could use > pciconf to > > query it. Can't say I've heard of PCI speed negotiation > issues, though. > > > > I'm not aware of any registers in the standard PCI config space that > will tell you the speed of the bus. Some PCI devices will make that > information available, but not in a standard way. The BIOS of some > higher-end systems might also tell you this information. > > Scott > > ___ > [EMAIL PROTECTED] mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to > "[EMAIL PROTECTED]" > ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
RE: Dual P4 2.4Ghz Xeon With Hyperthreading enabled...
I think the valid settings are only 0 or 1, with the default being 1 which will disable all logical CPUs. If you want to enable the extra logical CPUS, then set it to 0 (zero). They will come online immediately. John Cagle [EMAIL PROTECTED] Principal Member Technical Staff Industry Standard Servers Hewlett-Packard Company > -Original Message- > From: Scott M. Likens [mailto:[EMAIL PROTECTED] > Sent: Tuesday, August 12, 2003 8:19 PM > To: Brooks Davis > Cc: [EMAIL PROTECTED] > Subject: Re: Dual P4 2.4Ghz Xeon With Hyperthreading enabled... > > > On Tue, 2003-08-12 at 15:41, Brooks Davis wrote: > > On Tue, Aug 12, 2003 at 03:38:29PM -0700, Scott M. Likens wrote: > > > Well friend of mine just landed a Dual P4 2.4Ghz Xeon with > > > Hyperthreading Enabled, and yet I know there's a > hyperthreading option > > > in 4.8-RELEASE but I don't see one at ALL in 5.1? > > > > > > am I suddenly blind or do I need to cvsup to CURRENT to > take proper > > > advantage? > > > > There is no option in current. Instead, you use the sysctl > > machdep.hlt_logical_cpus to indicate if you want to use the logical > > cpus. > > > > -- Brooks > > For clarification, setting this to 2 would mean 2 processor's to > process? > > Thanks. > > -- > "I think we ought to be out there doing what we do best - making large > holes in other people's countries." - George Carlin > > ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
RE: Best Known Methods for dual booting WinXP + -current
You are right, thanks for the correction! > -Original Message- > From: Wilko Bulte [mailto:[EMAIL PROTECTED] > Sent: Friday, August 08, 2003 4:41 AM > To: David O'Brien; Cagle, John (ISS-Houston); John Reynolds; > [EMAIL PROTECTED] > Subject: Re: Best Known Methods for dual booting WinXP + -current > > > On Thu, Aug 07, 2003 at 06:49:55PM -0700, David O'Brien wrote: > > On Thu, Aug 07, 2003 at 03:40:27PM -0500, Cagle, John > (ISS-Houston) wrote: > > > Had to use FFS filesystem since Grub doesn't support UFS. > > ^^^ > > UFS1 > ^^^ > UFS2 > -- > | / o / /_ _ [EMAIL PROTECTED] > |/|/ / / /( (_) Bulte > ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
RE: Best Known Methods for dual booting WinXP + -current
I use Grub to multi-boot XPpro, Linux & FreeBSD. Had to use FFS filesystem since Grub doesn't support UFS. > -Original Message- > From: John Reynolds [mailto:[EMAIL PROTECTED] > Sent: Thursday, August 07, 2003 3:10 PM > To: [EMAIL PROTECTED] > Subject: Best Known Methods for dual booting WinXP + -current > > > hello all, > > Having had a positive experience thus far with 5.1-RELEASE > and -current beyond > that on one of the new boxes I recently built, it is now time > to build up the > dual-boot system (BSD for me, WinXP for the wife ;). I've > read different > reports (some from laptop users) about using the WinXP loader > to boot FreeBSD > and I've also read reports that people used the standard > boot-easy to boot both > (while even others using GRUB). > > Are there currently any issues with dual-booting 5.1-RELEASE > and/or -current > along with Windows XP (probably SP1)? This would be on the > same physical > disk. What do you other -current users who are faced with > dual booting XP do > for the most part? > > Thanks, > > -Jr > > -- > John & Jennifer Reynolds johnjen at reynoldsnet.org www.reynoldsnet.org Sr. Physical Design Engineer - WCCG/CCE PDE jreynold at sedona.ch.intel.com Running FreeBSD since 2.1.5-RELEASE. FreeBSD: The Power to Serve! "Unix is user friendly, it's just particular about the friends it chooses." ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]" ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
RE: Compaq Evo N610c
Which version of the N610C BIOS are you using? (F.14 is the latest on the hp.com
website.) I know that the _OSI("Windows 2001") bug will be fixed in the F.15 release,
but I don't think the _GL_ portion of your patch will be included. Did you have to
remove the Acquire & Release of _GL_ in order to get xbat to work? (This is not a
problem we see with Linux ACPI in 2.4.21, so I think that FreeBSD's ACPI stack needs
updating.)
Thanks,
John
John Cagle [EMAIL PROTECTED]
Principal Member Technical Staff
Industry Standard Servers
Hewlett-Packard Company
> -Original Message-
> From: Robert Blacquière [mailto:[EMAIL PROTECTED]
> Sent: Wednesday, July 30, 2003 7:47 AM
> To: Tony Maher
> Cc: [EMAIL PROTECTED]
> Subject: Re: Compaq Evo N610c
>
>
>
> Great this works ;-)
>
> even with the drive bay battery removed and inserted ;-)
>
> Only thing stil acts weird is the pcmcia (wireless) stuff...
> It seems the first memory ports can't be used zo 0x100-0x13f but the
> second card gets a other pool 0x180 i think and works ...
> maybe i can overrule or block the first block ?
>
> Robert
>
>
> On Wed, Jul 30, 2003 at 09:19:31PM +1000, Tony Maher wrote:
> >
> > Update on Compaq Evo N610c
> >
> > Thanks to an email from Simon in the UK I now have battery support
> > in my N610c.
> >
> > /boot/loader.conf is now
> >
> > hw.pci.allow_unsupported_io_range=1
> > acpi_dsdt_load="YES"
> > acpi_dsdt_name="/boot/acpi_dsdt.aml
> >
> > A patch for acpi_dsdt is attached.
> >
> > Now xbatt (and apm) works perfectly.
> >
> > Now all I need is another unexpected email that details how
> to solve the
> > suspending problem (actually the resumption) and the
> switching between X
> > and vga screen sync problem and I'd be completely set ;-)
> >
> > Thanks again to Simon!
> >
> > cheers
> > --
> > tonym
>
>
> --
> Microsoft: Where do you want to go today?
> Linux: Where do you want to go tomorrow?
> FreeBSD: Are you guys coming or what?
> OpenBSD: He guys you left some holes out there!
>
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
RE: Best way to get max KVA setting?
I'm that guy who was running PAE on an 8GB machine... BTW, it turns out the problem was _not_ the autotuning, it was simply an overflow of a 32-bit variable in the kernel. It's been fixed in -current, checked in 2 weeks ago. -Original Message- From: Terry Lambert [mailto:[EMAIL PROTECTED] Sent: Wednesday, June 25, 2003 3:26 AM To: Mike Silbersack Cc: [EMAIL PROTECTED] Subject: Re: Best way to get max KVA setting? Mike Silbersack wrote: > I could probably grep for this, but what's the best way to get a hold > of the # of pages (or MB of ram) that max KVA is set to? I'm adding > another autosize option, and I want to base it on min (KVA, ram) so > that it doesn't balloon on boxes where ram >> KVA. I posted a patch about a month ago that did exactly this. It was for a guy who was was running with PAE enabled on an 8G machine, and the autotuning was shooting him in the foot when it tried to grab enough memory to create kmem_map entries for the 8G of RAM in his 2G KVA space, and its head exploded. Let me know if you can't find it in the -current archives, and I can dig it out for you, if you're willing to wait a day or two. -- Terry ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
RE: sio problem in -current (COM1)
Thanks! It was an ACPI-related problem. I disabled ACPI (hint.acpi.0.disabled="1" in /boot/device.hints) and rebooted and now both com ports show up properly as they did with FreeBSD 4.8. (These are just standard com ports, btw.) I didn't realize ACPI was involved in legacy com port detection. That's weird. Thanks, John > -Original Message- > From: Bruce Evans [mailto:[EMAIL PROTECTED] > Sent: Wednesday, April 02, 2003 9:17 PM > To: Cagle, John (ISS-Houston) > Cc: [EMAIL PROTECTED] > Subject: Re: sio problem in -current (COM1) > > > On Wed, 2 Apr 2003, Cagle, John (ISS-Houston) wrote: > > > I'm having a problem with -current on a ProLiant BL10e > blade server. > > On the blade server, we use a serial console on sio0/COM1. > This works > > perfectly with 4.8, but for some reason, the sio driver doesn't see > > COM1 at all, and assigns COM2 resources to sio0. Any pointers to > > where I should look would be greatly appreciated. > > > > I've attached dmesg output for 4.8 and -current on this blade. > > 4.8: > > ... > > config> di sio2 > > Maybe this helps. sio2's irq is often the same as sio0's, > and this can sometimes cause problems. Workarounds for some > of these problems have been broken and turned off since FreeBSD-2. > > > ... > > sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 > > sio0: type 16550A, console > > sio1 at port 0x2f8-0x2ff irq 3 on isa0 > > sio1: type 16550A > > -current: > > ... > > sio0 port 0x2f8-0x2ff irq 3 on acpi0 > > sio0: type 16550A, console > > acpi sometimes does this for reasons that no one understands > AFAIK. Booting with -v should show the usual sio0 being > probed and something about why the probe failed, provided > sio0 is in hints. The probe order may be relevant. > > Bruce ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
sio problem in -current (COM1)
I'm having a problem with -current on a ProLiant BL10e blade server. On the blade server, we use a serial console on sio0/COM1. This works perfectly with 4.8, but for some reason, the sio driver doesn't see COM1 at all, and assigns COM2 resources to sio0. Any pointers to where I should look would be greatly appreciated. I've attached dmesg output for 4.8 and -current on this blade. Thanks, John John Cagle [EMAIL PROTECTED] Principal Member Technical Staff Industry Standard Servers Hewlett-Packard Company Copyright (c) 1992-2003 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 4.8-RC #3: Tue Apr 1 20:26:11 CST 2003 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/BL10E Timecounter "i8254" frequency 1193182 Hz CPU: Mobile Intel(R) Pentium(R) III CPU - M 900MHz (889.85-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x6b4 Stepping = 4 Features=0x383f9ff real memory = 536854528 (524272K bytes) config> di sio2 config> di ppc0 config> di bt0 config> di ata1 config> di aic0 config> di aha0 config> di adv0 config> q avail memory = 517517312 (505388K bytes) Preloaded elf kernel "kernel" at 0xc04c. Preloaded userconfig_script "/boot/kernel.conf" at 0xc04c009c. Pentium Pro MTRR support enabled md0: Malloc disk npx0: on motherboard npx0: INT 16 interface pcib0: on motherboard pci0: on pcib0 pci0: (vendor=0x0e11, dev=0xa0f0) at 1.0 irq 5 pci0: at 2.0 irq 7 fxp0: port 0x2800-0x283f mem 0xc4e0-0xc4ef,0xc4ffe000-0xc4ffefff irq 10 at device 3.0 on pci0 fxp0: Ethernet address 00:08:02:a3:ff:aa inphy0: on miibus0 inphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto fxp1: port 0x2840-0x287f mem 0xc4c0-0xc4cf,0xc4dff000-0xc4df irq 11 at device 4.0 on pci0 fxp1: Ethernet address 00:08:02:a3:ff:ab inphy1: on miibus1 inphy1: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto isab0: at device 15.0 on pci0 isa0: on isab0 atapci0: port 0x2000-0x200f,0x374-0x377,0x170-0x177,0x3f4-0x3f7,0x1f0-0x1f7 at device 15.1 on pci0 ata0: at 0x1f0 irq 14 on atapci0 ata1: at 0x170 irq 15 on atapci0 ohci0: mem 0xc4bff000-0xc4bf irq 7 at device 15.2 on pci0 usb0: OHCI version 1.0, legacy support usb0: SMM does not respond, resetting usb0: on ohci0 usb0: USB revision 1.0 uhub0: (0x1166) OHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 4 ports with 4 removable, self powered pcib2: on motherboard pci2: on pcib2 pcib1: on motherboard pci1: on pcib1 eisa0: on motherboard mainboard0: on eisa0 slot 0 orm0: at iomem 0xc-0xc7fff,0xc8000-0xc97ff,0xe-0xe7fff on isa0 fdc0: at port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on isa0 fdc0: FIFO enabled, 8 bytes threshold fd0: <1440-KB 3.5" drive> on fdc0 drive 0 atkbdc0: at port 0x60,0x64 on isa0 vga0: at port 0x3c0-0x3df iomem 0xa-0xb on isa0 sc0: at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=0x100> sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 16550A, console sio1 at port 0x2f8-0x2ff irq 3 on isa0 sio1: type 16550A ad0: 38154MB [77520/16/63] at ata0-master UDMA100 Mounting root from ufs:/dev/ad0s1a Copyright (c) 1992-2003 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 5.0-CURRENT #2: Tue Apr 1 20:04:55 GMT 2003 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/BL10E Preloaded elf kernel "/boot/kernel/kernel" at 0xc04e3000. Preloaded elf module "/boot/kernel/acpi.ko" at 0xc04e30a8. Timecounter "i8254" frequency 1193182 Hz Timecounter "TSC" frequency 889848904 Hz CPU: Mobile Intel(R) Pentium(R) III CPU - M 900MHz (889.85-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x6b4 Stepping = 4 Features=0x383f9ff real memory = 536854528 (511 MB) avail memory = 516214784 (492 MB) Allocating major#253 to "net" Allocating major#252 to "g_ctl" Allocating major#251 to "pci" Pentium Pro MTRR support enabled npx0: on motherboard npx0: INT 16 interface acpi0: on motherboard ACPI-0625: *** Info: GPE Block0 defined as GPE0 to GPE31 acpi0: power button is handled as a fixed feature programming model. Timecounter "ACPI-safe" frequency 3579545 Hz pcibios: BIOS version 2.10 acpi_timer0: <32-bit timer at 3.579545MHz> port 0xf808-0xf80b on acpi0 acpi_cpu0: on acpi0 acpi_tz0: on acpi0 pcib0: on acpi0 pci0: on pcib0 pci0: at device 1.0 (no driver attached) pci0: at device 2.0 (no driver attached) fxp0: port 0x2800-0x283f mem 0xc4e0-0xc4ef,0xc4ffe000-0xc4ffefff irq 10 at device 3.0 on pci0 fxp0: Ethernet address 00:08:02:a3:ff:82 miibus0: on fxp0 inphy0: on miibus0 inphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto fxp1: port 0x2840-0x287f mem 0xc4c0-0xc4cf,0xc4dff000-0xc4df irq 11 at device 4.0 on pci0 fxp1: Ethernet address 00:08:02:a3:ff:83 miibus1: on fxp1 inphy1: on m
RE: IP over IEEE1394?
Wouldn't you need a firewire switch to do a cluster of more than 2 nodes? Or are you thinking of using multiple firewire interfaces per node? > -Original Message- > From: David Leimbach [mailto:[EMAIL PROTECTED] > Sent: Wednesday, March 05, 2003 8:32 AM > To: Christopher Fowler > Cc: [EMAIL PROTECTED] > Subject: Re: IP over IEEE1394? > > > True... I guess I didn't state my case clearly enough that I > think IP > over firewire > is in itself a good thing for clusters. > > ppp connections with it are fine too but not very useful for > my line of > work > which is parallel computing middleware :) > > Dave To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
RE: HEADS UP: cvsup cvs-supfile users!
Are all the official mirrors in the USA (cvsup1..17.freebsd.org) supposed to have the "cvsroot-all" package? I just tried cvsup16 and it doesn't have it. > -Original Message- > From: Peter Wemm [mailto:[EMAIL PROTECTED] > Sent: Tuesday, March 04, 2003 1:45 PM > To: Stijn Hoop > Cc: [EMAIL PROTECTED] > Subject: Re: HEADS UP: cvsup cvs-supfile users! > > > Stijn Hoop wrote: > > > On Tue, Mar 04, 2003 at 11:10:45AM -0800, Peter Wemm wrote: > > > Anybody who uses the cvs-supfile example to get the repository > > > should add "cvsroot-all" to their supfile. This is in > addition to > > > src-all, ports-al= > > l, > > > doc-all etc. > > >=20 > > > This is *ONLY* for the folks getting the CVS ,v files via > cvsup. If > > >you use tag=3D. or tag=3DRELENG_4, then you are not affected by > > >this. =20 I have updated cvs-supfile in -current but not RELENG_4 > > >yet. > > > > Just to be doubly sure, this goes for cvsup mirrors as > well, I assume? > > So I have to edit /usr/local/etc/cvsup/supfile to include > it? If so, > > then you might want to update > ports/net/cvsup-mirror/files/supfile a= > > lso. > > No, people who use cvs-all are already getting this stuff. > If you use the cvsup-mirror port yourself, you do not need to > change anything either. Mirrors who use cvs-all (official and > unofficial) do not need to change anything. > > Cheers, > -Peter > -- > Peter Wemm - [EMAIL PROTECTED]; [EMAIL PROTECTED]; > [EMAIL PROTECTED] "All of this is for nothing if we don't > go to the stars" - JMS/B5 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
RE: Drive Resetting
What kind of IDE cable are you using (40 or 80-conductor)? You might try a new cable. Do you know which UDMA mode the ata driver is running in? Have you tried turning off DMA and/or write-caching? (I think you can use sysctl to do this.) > -Original Message- > From: Beech Rintoul [mailto:[EMAIL PROTECTED]] > Sent: Tuesday, February 18, 2003 3:53 PM > To: [EMAIL PROTECTED] > Subject: Drive Resetting > > > I just installed a new maxtor drive on a 200Mhz Compaq > Deskpro running 5.0 setup went normally (no errors) fsck > showed no errors. However, I am now getting the following > under heavy disk activity: > > Feb 18 12:32:46 stargate kernel: ad2: WRITE command timeout > tag=0 serv=0 - reset ting Feb 18 12:32:46 stargate kernel: > ata1: resetting devices .. Feb 18 12:32:46 stargate kernel: done > > Anyone have any suggestions on how to fix this? Its happens > frequently, especially during compiles. > > Beech > --- > Beech Rintoul - Network Administrator - [EMAIL PROTECTED] > /"\ ASCII Ribbon Campaign | NorthWind Communications > \ / - NO HTML/RTF in e-mail | > X - NO Word docs in e-mail | Anchorage, AK 99518-1841 > No More Spam! http://www.knockmail.com/default.asp?AID=B0R00073 > / \ - > > > > > > > > > > > > > > > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
RE: Smart Array 5312 (Compaq)
Thanks, Paul! I talked to our storage experts and as long as the driver already has 5i support, then all that's needed is to add the new id (which your patch does). Thanks, John John Cagle [EMAIL PROTECTED] Principal Member Technical Staff Industry Standard Servers Hewlett-Packard Company > -Original Message- > From: Paul Saab [mailto:[EMAIL PROTECTED]] > Sent: Thursday, January 30, 2003 7:46 PM > To: John > Cc: [EMAIL PROTECTED] > Subject: Re: Smart Array 5312 (Compaq) > > > Try this patch > > http://people.freebsd.org/~ps/ciss.diff > > John ([EMAIL PROTECTED]) wrote: > > Is anyone working on a driver for said raid controller? > > Here is a pciconf -lv (from 5.0-R) and a link for some info on the > > card. > > > > > > ne3@pci6:2:0: class=0x010400 card=0x40830e11 > chip=0xb1780e11 rev=0x01 hdr=0x00 > > class= mass storage > > subclass = RAID > > > > > http://h18004.www1.hp.com/products/servers/pro> liantstorage/arraycontro > > llers/smartarray5312/questionsanswers.html > > > > To Unsubscribe: send mail to [EMAIL PROTECTED] > > with "unsubscribe freebsd-current" in the body of the message > > -- > Paul Saab > Technical Yahoo > [EMAIL PROTECTED] - [EMAIL PROTECTED] - [EMAIL PROTECTED] > Do You .. uhh .. Yahoo!? > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
RE: Performance problems with 5.0-RELEASE
> From: Atte Peltomaki [mailto:[EMAIL PROTECTED]] > > > > If it's long enough to pause the console noticibly, the > next thing > > > to try is breaking to the debugger -- which might require an NMI > > > card -- to see what code it's stuck in during the pause. > > > > It's noticeable - if you type under heavy load in console, you > > experience similar to ssh lag - you can't see what you type, but it > > appears a second later to the screen. > > Just as an update: I've been listening to quite a lot of > techno/trance music lately, and it scares me - every now and > then xmms loses the beat when playing, even if there was > absolutely no other load. The pause is so quick you can't > really notice it elsewhere, but it's definetely there. > > Continuing investigations. Has anyone tried disabling ACPI to see if it's the culprit? John Cagle [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
RE: bad ACPL asl's on motherboards
You might ask that question on the ACPI development list. I think there are several people who have contributed patched ASL's for machines that are broken. Here's a link: Acpi-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/acpi-devel > -Original Message- > From: Joel M. Baldwin [mailto:[EMAIL PROTECTED]] > Sent: Thursday, January 16, 2003 8:08 AM > To: [EMAIL PROTECTED] > Subject: bad ACPL asl's on motherboards > > > > I gather that there are quite a few Motherboards with bad > ACPI asl's on them. I know that my Abit BP6 sure has > problems. As a result I can't run ACPI. > > What are those of us with these motherboards supposed to to? > > I realize that we can use acpidump to get the asl, correct > it, and then recompile it using iasl from the acpicatools > port, to generate the aml that can be used during boot. > > acpi_dsdt_load="YES"# DSDT Overriding > acpi_dsdt_name="/boot/abitBP6.aml" > # Override DSDT in BIOS by this file > > But this doesn't help me much since I don't know what > corrections to make to the original asl file. Nor does it > help the other people out there using BP6's. > > Is someone going to create a asl erratica web page? > How about something to help us correct our asl files like a FAQ? > > > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
RE: SMP hang at boot on Compaq Proliant ML370
Thanks for the info. I've found a ML370 G3 and will look into this today or tommorrow. I'll be in touch. Thanks, John > -Original Message- > From: Peter Wemm [mailto:[EMAIL PROTECTED]] > Sent: Wednesday, January 15, 2003 11:32 AM > To: John Baldwin > Cc: Cagle, John (ISS-Houston); [EMAIL PROTECTED] > Subject: Re: SMP hang at boot on Compaq Proliant ML370 > > > John Baldwin wrote: > > > > On 15-Jan-2003 Cagle, John (ISS-Houston) wrote: > > > That's a vicious rumor -- no operating system could work without > > > clock interrupts in SMP mode... Could it? > > > > I think it had something to do more with the RTC interrupt > not being > > routed to the I/O APIC and FreeBSD currently can only > handle the ISA > > timer interrupt being only rounted to the 8259A PICs. > Thus, FreeBSD > > hangs because it doesn't get any interrupts from the RTC > via the I/O > > APIC. I couldn't remmeber the exact details earlier hence the > > vagueness of my message. > > The same problem happens with a newer DL380 that we have > here. G3 I think, but I can never keep track of all the new toys. :-) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
RE: SMP hang at boot on Compaq Proliant ML370
That's a vicious rumor -- no operating system could work without clock interrupts in SMP mode... Could it? Which generation of the ML370 is having this problem? I had a similar problem on another box that was corrected with a newer BIOS version. Thanks, John > -Original Message- > From: John Baldwin [mailto:[EMAIL PROTECTED]] > Sent: Wednesday, January 15, 2003 10:55 AM > To: Nicolas Kowalski > Cc: [EMAIL PROTECTED] > Subject: Re: SMP hang at boot on Compaq Proliant ML370 > > > > On 15-Jan-2003 Nicolas Kowalski wrote: > > [EMAIL PROTECTED] writes: > > > >> I had a Compaq visit my lab recently. Unless the aic driver were > >> removed from the kernel (disabling it might have worked > too) it would > >> screw up the floppy driver. > >> > >> This sounds like black magic, but the explanation is that the aic > >> driver has a very intrusive probe routine which sticks > random bytes > >> into whatever I/O locations it feels like and this > appearantly is not > >> liked by certain machines. > >> > >> Compaqs with all their bells and whistles could be particular > >> sensitive to this, so try to disable the aic driver and see if it > >> helps. > > > > I tried this. Now there is only the ahc driver (the only > one needed) > > compiled in the kernel but this does not help, the server > still hangs. > > I also removed the ata driver, without success. :-( > > Is the ML370 a new box? I've heard rumors recently that one > of the recent Compaq boxes effectively doesn't generate clock > interrupts in SMP mode and there isn't a workaround for that > at the moment. > > -- > > John Baldwin <[EMAIL PROTECTED]> <>< > http://www.FreeBSD.org/~jhb/ "Power Users Use > the Power to > Serve!" - http://www.FreeBSD.org/ > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
RE: 5.0 RC3 usb errors
Sorry, I should have said this earlier: nothing is connected to them. This is a really weird problem -- the error messages stopped within 60 seconds of setting the correct date on the server (it was set for November, 2002) and I cannot get them to come back, even by setting the date back to November. So, "nevermind" -- I'll let you know if the error messages turn up again... Thanks, John > -Original Message- > From: Alexander Kabaev [mailto:[EMAIL PROTECTED]] > Sent: Tuesday, January 14, 2003 8:43 PM > To: Cagle, John (ISS-Houston) > Cc: [EMAIL PROTECTED] > Subject: Re: 5.0 RC3 usb errors > > > What USB devices are connected to these ports? > On Tue, 14 Jan 2003 20:34:49 -0600 > "Cagle, John (ISS-Houston)" <[EMAIL PROTECTED]> wrote: > > > I've installed 5.0 RC3 on an HP ProLiant DL380 G3 (which has USB > > ports), and I'm constantly getting these error messages on the > > console: > > > > uhub0: port error, giving up port 2 > > uhub0: port error, restarting port 2 > > > > What USB devices are connected to these ports? > > -- > Alexander Kabaev > To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
5.0 RC3 usb errors
I've installed 5.0 RC3 on an HP ProLiant DL380 G3 (which has USB ports), and I'm constantly getting these error messages on the console: uhub0: port error, giving up port 2 uhub0: port error, restarting port 2 Anyone else seeing these errors? I didn't get these with 4.7, but I did see them with 5.0 RC2. Any pointers to help debug this appreciated. I am a FreeBSD newbie... :-) Thanks, John John Cagle [EMAIL PROTECTED] Principal Member Technical Staff Industry Standard Servers Hewlett-Packard Company To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
