RE: repeatable crash with 5.4-RELEASE and PAE

From: Danny Cooper (danny.cooper_at_uk.tiscali.com)
Date: 06/02/05

  • Next message: Claus Guttesen: "Re: repeatable crash with 5.4-RELEASE and PAE" 
    To: "'Brendan White'" <bmwt@caida.org>, <freebsd-stable@freebsd.org>
Date: Thu, 2 Jun 2005 22:09:47 +0100

    Hi Brendan,

    I have 2

    Dual Xeon 3.6 Dell Poweredge 2850
    4 gigs of ram
    8 gigs of swap
    amr raid

    They can crash at any moment not just underload, I persisted for 10 days to
    get a stable system with and without PAE but to no avail with 4GB of RAM.

    I did try and turn off ACPI, HTT which made the machine more stable but only
    for 6-24 hours.

    I have formatted the one machine with FreeBSD 5.4R (amd64) and have keep the
    CPU 100% with a load average of 4.00 for 2 hours and no crash.

    I haven't started to mess around with memory settings yet to increase the
    performance of the machine, as want to run it underload for a day then start
    to tune the box.

    I also turned USB in the kernel and rc.conf

    usbd_enable="NO"

    Here is my amd64 kernel

    /usr/src/sys/amd64/conf/MK-TESTBOX-1-SMP
    # SMP -- Generic kernel configuration file for FreeBSD/amd64 SMP
    # Use this for multi-processor machines
    #
    # $FreeBSD: src/sys/amd64/conf/SMP,v 1.1.2.1 2004/10/23 19:58:27 kensmith
    Exp $
    include MK-TESTBOX-1
    options SMP

    /usr/src/sys/amd64/conf/MK-TESTBOX-1
    # $FreeBSD: src/sys/amd64/conf/GENERIC,v 1.421.2.11.2.1 2005/04/09 17:28:37
    kensmith Exp $

    machine amd64
    cpu HAMMER
    ident MK-TESTBOX-1

    # To statically compile in device wiring instead of /boot/device.hints
    #hints "GENERIC.hints" # Default places to look for
    devices.

    options SCHED_4BSD # 4BSD scheduler
    options INET # InterNETworking
    #options INET6 # IPv6 communications protocols
    options FFS # Berkeley Fast Filesystem
    options SOFTUPDATES # Enable FFS soft updates support
    options UFS_ACL # Support for access control lists
    options UFS_DIRHASH # Improve performance on big
    directories
    options MD_ROOT # MD is a potential root device
    #options NFSCLIENT # Network Filesystem Client
    #options NFSSERVER # Network Filesystem Server
    #options NFS_ROOT # NFS usable as /, requires
    NFSCLIENT
    #options NTFS # NT File System
    #options MSDOSFS # MSDOS Filesystem
    options CD9660 # ISO 9660 Filesystem
    options PROCFS # Process filesystem (requires
    PSEUDOFS)
    options PSEUDOFS # Pseudo-filesystem framework
    options GEOM_GPT # GUID Partition Tables.
    options COMPAT_43 # Needed by COMPAT_LINUX32
    options COMPAT_IA32 # Compatible with i386 binaries
    options COMPAT_FREEBSD4 # Compatible with FreeBSD4
    options COMPAT_LINUX32 # Compatible with i386 linux
    binaries
    options SCSI_DELAY=15000 # Delay (in ms) before probing SCSI
    options KTRACE # ktrace(1) support
    options SYSVSHM # SYSV-style shared memory
    options SYSVMSG # SYSV-style message queues
    options SYSVSEM # SYSV-style semaphores
    options _KPOSIX_PRIORITY_SCHEDULING # POSIX P1003_1B real-time
    extensions
    options KBD_INSTALL_CDEV # install a CDEV entry in /dev
    options AHC_REG_PRETTY_PRINT # Print register bitfields in debug
                                            # output. Adds ~128k to driver.
    options AHD_REG_PRETTY_PRINT # Print register bitfields in debug
                                            # output. Adds ~215k to driver.
    options ADAPTIVE_GIANT # Giant mutex is adaptive.

    # Workarounds for some known-to-be-broken chipsets (nVidia nForce3-Pro150)
    device atpic # 8259A compatability

    # Enabling NO_MIXED_MODE gives a performance improvement on some
    motherboards
    # but does not work with some boards (mostly nVidia chipset based).
    #options NO_MIXED_MODE # Don't penalize working chipsets

    # Linux 32-bit ABI support
    options LINPROCFS # Cannot be a module yet.

    # Bus support. Do not remove isa, even if you have no isa slots
    device acpi
    device isa
    device pci

    # Floppy drives
    device fdc

    # ATA and ATAPI devices
    device ata
    device atadisk # ATA disk drives
    device ataraid # ATA RAID drives
    device atapicd # ATAPI CDROM drives
    device atapifd # ATAPI floppy drives
    device atapist # ATAPI tape drives
    options ATA_STATIC_ID # Static device numbering

    # SCSI Controllers
    #device ahc # AHA2940 and onboard AIC7xxx devices
    #device ahd # AHA39320/29320 and onboard AIC79xx devices
    #device amd # AMD 53C974 (Tekram DC-390(T))
    #device isp # Qlogic family
    ##device ispfw # Firmware for QLogic HBAs- normally a
    module
    #device mpt # LSI-Logic MPT-Fusion
    ##device ncr # NCR/Symbios Logic
    #device sym # NCR/Symbios Logic (newer chipsets + those
    of `ncr')
    #device trm # Tekram DC395U/UW/F DC315U adapters

    #device adv # Advansys SCSI adapters
    #device adw # Advansys wide SCSI adapters
    #device aic # Adaptec 15[012]x SCSI adapters,
    AIC-6[23]60.
    #device bt # Buslogic/Mylex MultiMaster SCSI adapters

    # SCSI peripherals
    device scbus # SCSI bus (required for SCSI)
    device ch # SCSI media changers
    device da # Direct Access (disks)
    device sa # Sequential Access (tape etc)
    device cd # CD
    device pass # Passthrough device (direct SCSI access)
    device ses # SCSI Environmental Services (and SAF-TE)

    # RAID controllers interfaced to the SCSI subsystem
    device amr # AMI MegaRAID
    #device arcmsr # Areca SATA II RAID
    #device ciss # Compaq Smart RAID 5*
    #device dpt # DPT Smartcache III, IV - See NOTES for
    options
    #device iir # Intel Integrated RAID
    #device ips # IBM (Adaptec) ServeRAID
    #device mly # Mylex AcceleRAID/eXtremeRAID
    #device twa # 3ware 9000 series PATA/SATA RAID

    # RAID controllers
    #device aac # Adaptec FSA RAID
    #device aacp # SCSI passthrough for aac (requires CAM)
    #device ida # Compaq Smart RAID
    #device mlx # Mylex DAC960 family
    ##XXX pointer/int warnings
    ##device pst # Promise Supertrak SX6000
    #device twe # 3ware ATA RAID

    # atkbdc0 controls both the keyboard and the PS/2 mouse
    device atkbdc # AT keyboard controller
    device atkbd # AT keyboard
    device psm # PS/2 mouse

    device vga # VGA video card driver

    device splash # Splash screen and screen saver support

    # syscons is the default console driver, resembling an SCO console
    device sc

    # PCCARD (PCMCIA) support
    # PCMCIA and cardbus bridge support
    #device cbb # cardbus (yenta) bridge
    #device pccard # PC Card (16-bit) bus
    #device cardbus # CardBus (32-bit) bus

    # Serial (COM) ports
    device sio # 8250, 16[45]50 based serial ports

    # Parallel port
    #device ppc
    #device ppbus # Parallel port bus (required)
    #device lpt # Printer
    #device plip # TCP/IP over parallel
    #device ppi # Parallel port interface device
    #device vpo # Requires scbus and da

    # If you've got a "dumb" serial or parallel PCI card that is
    # supported by the puc(4) glue driver, uncomment the following
    # line to enable it (connects to the sio and/or ppc drivers):
    #device puc

    # PCI Ethernet NICs.
    #device de # DEC/Intel DC21x4x (``Tulip'')
    device em # Intel PRO/1000 adapter Gigabit Ethernet
    Card
    #device ixgb # Intel PRO/10GbE Ethernet Card
    #device txp # 3Com 3cR990 (``Typhoon'')
    #device vx # 3Com 3c590, 3c595 (``Vortex'')

    # PCI Ethernet NICs that use the common MII bus controller code.
    # NOTE: Be sure to keep the 'device miibus' line in order to use these NICs!
    #device miibus # MII bus support
    #device bfe # Broadcom BCM440x 10/100 Ethernet
    #device bge # Broadcom BCM570xx Gigabit Ethernet
    #device dc # DEC/Intel 21143 and various workalikes
    #device fxp # Intel EtherExpress PRO/100B (82557, 82558)
    #device lge # Level 1 LXT1001 gigabit Ethernet
    #device nge # NatSemi DP83820 gigabit Ethernet
    #device pcn # AMD Am79C97x PCI 10/100 (precedence over
    'lnc')
    #device re # RealTek 8139C+/8169/8169S/8110S
    #device rl # RealTek 8129/8139
    #device sf # Adaptec AIC-6915 (``Starfire'')
    #device sis # Silicon Integrated Systems SiS 900/SiS
    7016
    #device sk # SysKonnect SK-984x & SK-982x gigabit
    Ethernet
    #device ste # Sundance ST201 (D-Link DFE-550TX)
    #device ti # Alteon Networks Tigon I/II gigabit
    Ethernet
    #device tl # Texas Instruments ThunderLAN
    #device tx # SMC EtherPower II (83c170 ``EPIC'')
    #device vge # VIA VT612x gigabit Ethernet
    #device vr # VIA Rhine, Rhine II
    #device wb # Winbond W89C840F
    #device xl # 3Com 3c90x (``Boomerang'', ``Cyclone'')

    # ISA Ethernet NICs. pccard NICs included.
    #device cs # Crystal Semiconductor CS89x0 NIC
    # 'device ed' requires 'device miibus'
    # XXX kvtop brokenness, pointer/int warnings
    #device ed # NE[12]000, SMC Ultra, 3c503, DS8390 cards
    #device ex # Intel EtherExpress Pro/10 and Pro/10+
    #device ep # Etherlink III based cards
    #device fe # Fujitsu MB8696x based cards
    # XXX kvtop brokenness, pointer/int warnings
    #device lnc # NE2100, NE32-VL Lance Ethernet cards
    #device sn # SMC's 9000 series of Ethernet chips
    #device xe # Xircom pccard Ethernet

    # Wireless NIC cards
    #device wlan # 802.11 support
    #device an # Aironet 4500/4800 802.11 wireless NICs.
    #device awi # BayStack 660 and others
    #device wi # WaveLAN/Intersil/Symbol 802.11 wireless
    NICs.

    # Pseudo devices.
    device loop # Network loopback
    device mem # Memory and kernel memory devices
    device io # I/O device
    device random # Entropy device
    device ether # Ethernet support
    #device sl # Kernel SLIP
    #device ppp # Kernel PPP
    #device tun # Packet tunnel.
    device pty # Pseudo-ttys (telnet etc)
    device md # Memory "disks"
    #device gif # IPv6 and IPv4 tunneling
    #device faith # IPv6-to-IPv4 relaying (translation)

    # The `bpf' device enables the Berkeley Packet Filter.
    # Be aware of the administrative consequences of enabling this!
    # Note that 'bpf' is required for DHCP.
    device bpf # Berkeley packet filter

    # USB support
    #device uhci # UHCI PCI->USB interface
    #device ohci # OHCI PCI->USB interface
    ##device ehci # EHCI PCI->USB interface (USB 2.0)
    #device usb # USB Bus (required)
    ##device udbp # USB Double Bulk Pipe devices
    #device ugen # Generic
    #device uhid # "Human Interface Devices"
    #device ukbd # Keyboard
    #device ulpt # Printer
    #device umass # Disks/Mass storage - Requires scbus and da
    #device ums # Mouse
    #device urio # Diamond Rio 500 MP3 player
    #device uscanner # Scanners
    ## USB Ethernet, requires mii
    #device aue # ADMtek USB Ethernet
    #device axe # ASIX Electronics USB Ethernet
    #device cdce # Generic USB over Ethernet
    #device cue # CATC USB Ethernet
    #device kue # Kawasaki LSI USB Ethernet
    #device rue # RealTek RTL8150 USB Ethernet
    #
    ## FireWire support
    #device firewire # FireWire bus code
    #device sbp # SCSI over FireWire (Requires scbus and da)
    #device fwe # Ethernet over FireWire (non-standard!)

    options IPFIREWALL #firewall
    options IPFIREWALL_DEFAULT_TO_ACCEPT #allow everything by default
    options IPFILTER #ipfilter support
    options IPFILTER_LOG #ipfilter logging

    Regards,

    Danny Cooper

    -----Original Message-----
    From: owner-freebsd-stable@freebsd.org
    [mailto:owner-freebsd-stable@freebsd.org] On Behalf Of Brendan White
    Sent: 02 June 2005 21:00
    To: freebsd-stable@freebsd.org
    Subject: repeatable crash with 5.4-RELEASE and PAE

    We're having crash under load problems using freebsd 5.4-release
    (i386) and PAE kernel.

    Machine:
    Dual Xeon 3.6 Dell Poweredge 2850
    8 gigs of ram
    16 gigs of swap
    amr raid

    The machine will reliably crash under load within an hour or so.
    "under load" involves large network transfers being processed by cpu
    and memory intensive processes.

    i cant get a crash dump (when it starts dumping, it will stop part
    way thru displaying memory increments.)

    I have gotten it to spit out a trace from KDB, which i've copied out
    below.
    (i had to do it from a screenshot/by hand- i checked it twice, but if
    things dont make sence, there may be a typo)

    kernel config included below the trace.
    We've tried turning off hyperthreading. The problem persists.
    We've tried turning off PAE (which brings us from 8 gigs to 3). The
    problem goes away.
    This is obviously not the optimal solution. 

    ---
kdb_enter(c05a1e33) at kdb_enter+0x2b
panic(c05a0a51,fffffffe,c05a0a3b,cb65ed80,fffffffe) at panic+0x127
lockmgr(cbadb7e4,6,cbadb738,0,f1b93a0c) at lockmgr+0x421
vop_stdunlock(f1b93a3c,f1b93a18,c038320f,f1b93a3c,f1b93a59) at  
vop_stdunlock+0x1f
vop_defaultop(f1b93a3c,f1b93a58,c038379c,f1b93a3c,1000) at  
vop_defaultop+0x13
spec_vnoperate(f1b93a3c,1000,7f010000,cba4e100,f1b93aa4) at  
spec_vnoperate+0x13
spec_write(f1b93a84,f1b93ad0,c04fce99,f1b93a84,cb65ed80) at spec_write 
+0x64
spec_vnoperate(f1b93a84) at spec_vnoperate+0x13
vnode_pager_generic_putpages(cbadb738,f1b93be0,1000,0,f1b93b60) at  
vnode_pager_generic_putpages+0x221
vop_stdputpages 
(f1b93b18,f1b93b18,f1b93b04,c038320f,f1b93b18,f1b93b44) at  
vop_stdputpages+0x1a
vop_defaultop(f1b93b18,f1b93b44,c04fcc36,f1b93b18,1000) at  
vop_defaultop+0x13
spec_vnoperate(f1b93b18) at spec_vnoperate+0x13
vnode_pager_putpages(cbb53ad4,f1b93be0,1,0,f1b93b60) at  
vnode_pager_putpages+0xba
vm_pageout_flush(f1b93be0,1,0,cbd7a600,f1b93bb8) at vm_pageout_flush 
+0xcb
vm_pageout_clean(c4254e4c) at vm_pageout_clean+0x2a1
vm_pageout_scan(0) at vm_pageout_scan+0x706
vm_pageout(0,f1b93d38) at vm_pageout+0x312
fork_exit(c04f5e1c,0,f1b93d38) at fork_exit+0x75
fork_trampoline() at fork_trampoline+0x8
--- trap 0x1, eip=0, esp = 0xf1b93d6c, ebp = 0 ---
kernel config:
include GENERIC
ident           PAE-GENERIC
options         KDB_TRACE
options         KDB
options         DDB
makeoptions     DEBUG=-g
options         SMP
options         COMPAT_LINUX
device          acpi
makeoptions     NO_MODULES=yes
nodevice        ahb
nodevice        amd
nodevice        sym
nodevice        trm
nodevice        adv
nodevice        adw
nodevice        aha
nodevice        aic
nodevice        bt
nodevice        ncv
nodevice        nsp
nodevice        stg
nodevice        asr
nodevice        dpt
nodevice        iir
nodevice        mly
nodevice        ida
nodevice        mlx
nodevice        pst
nodevice        agp
nodevice        de
nodevice        txp
nodevice        vx
nodevice        dc
nodevice        pcn
nodevice        rl
nodevice        sf
nodevice        sis
nodevice        ste
nodevice        tl
nodevice        tx
nodevice        vr
nodevice        wb
nodevice        cs
nodevice        ed
nodevice        ex
nodevice        ep
nodevice        fe
nodevice        ie
nodevice        lnc
nodevice        sn
nodevice        xe
nodevice        wlan
nodevice        an
nodevice        awi
nodevice        wi
nodevice        uhci
nodevice        ohci
nodevice        ehci
nodevice        usb
nodevice        ugen
nodevice        uhid
nodevice        ukbd
nodevice        ulpt
nodevice        umass
nodevice        ums
nodevice        urio
nodevice        uscanner
nodevice        aue
nodevice        axe
nodevice        cdce
nodevice        cue
nodevice        kue
nodevice        rue
_______________________________________________
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org"

    attached mail follows:

    To: "'David Barnett'" <davidb@santacruz.k12.ca.us>, "'Gary Schrock'" <lists@eyelab.psy.msu.edu>
Date: Thu, 2 Jun 2005 18:03:57 +0100

    I have disabled usb via rc.conf

    usbd_enable="NO"

    But in the new custom kernel I have commented out all of the usb devices and
    firewire.

    However the machine managed to stay up for 22 hours without any problems.

    But I decided to put it underload, through multiple make de/install's of
    mysql, apache, php, net-snmp to get the load of the machine high but after 1
    hour of load, the machine crashed once again.

    Now I have formatted one of the 2850's and put FreeBSD 5.4R (amd64)

    I still have disabled usb and nonessential parts of the kernel and placed
    the machine under heavy load, so far so good.

    DC

    -----Original Message-----
    From: owner-freebsd-stable@freebsd.org
    [mailto:owner-freebsd-stable@freebsd.org] On Behalf Of David Barnett
    Sent: 02 June 2005 17:52
    To: Gary Schrock
    Cc: freebsd-stable@freebsd.org
    Subject: Re: DELL PowerEdge 2850 and FreeBSD 5.4

    Gary,

    I'm fighting the same battle on two new 2850's and two 1850's; "Interrupt
    storm detected on "irq18:uhci2"; throttling interrupt source".

    These machines have 2GB of ram and I using the i386 5.4Rel. version.
    This happens
    right after the reboot at the end of an install from CD. I've chosen to
    install "all",
    and bring up the ethernet interface. When I get the message, the
    machine is unresponsive
    to keyboard input or pings; basically frozen. I also tried 5.3 Rel.
    with the same results.

     From searching the lists I concluded disabling USB might be worth
    trying, so I did that
    in the BIOS. I'm still getting the same message and freeze.

    How are you disabling USB? It seems that has worked for you.

    One tidbit, they have the DRAC 4/I remote access controller cards in
    them, but I have no
    reason to believe they're involved at this point. Oh, and firmware is
    current throughout.

    Thanks for any hints.

    Dave Barnett

    Gary Schrock wrote:

    > At 05:05 AM 6/1/2005, you wrote:
    >
    >> I have checked on the DELL site for any updates to the BIOS/Firmware
    >> and the
    >> 2 PE2850's are running the latest versions.
    >>
    >> BIOS A02
    >> Dell Backplane Firmware, v.1.00, A00
    >> Dell BMC Firmware, v.1.23, A03
    >> LSI Logic Perc 4e/Di, v.516A, A01
    >>
    >> Both machines have the same symptoms or the reboots at random times.
    >>
    >> I have now disabled the USB via rc.conf to see if the reboots still
    >> occur.
    >> On one machine I shall drop the PAE kernel and see if that increases the
    >> stability
    >
    >
    > We've been running a 2850 with dual processors for a while now,
    > although we're only running 2G of ram. I'm also running the i386
    > verson of freebsd instead of amd64 (since I couldn't decide whether
    > I'd really gain anything by running that version, especially with my
    > low ram amount). We did initially have a problem with our add-on
    > perc4 controller, but that was obviously a problem with that
    > controller, but after that was resolved, the only issue I've had with
    > it is the usb interrupt storms. Since we don't use usb on that
    > system, I've just completely disabled it. After that, it's run
    > flawlessly for about 6 months now.
    >
    >> Regards
    >>
    >> Danny
    >>
    >> -----Original Message-----
    >> From: owner-freebsd-stable@freebsd.org
    >> [mailto:owner-freebsd-stable@freebsd.org] On Behalf Of Vinny Abello
    >> Sent: 01 June 2005 05:10
    >> To: Danny Cooper
    >> Cc: freebsd-stable@freebsd.org
    >> Subject: RE: DELL PowerEdge 2850 and FreeBSD 5.4
    >>
    >> What BIOS revision are you running in your 2850? Make sure all your
    >> firmware is up to date. I had problems with an slightly older Dell
    >> 2650 trying to install FreeBSD until I flashed the latest RAID
    >> controller firmware. If this doesn't help, try running some
    >> diagnostics on the hardware. Dell has some pretty extensive
    >> utilities. I think you can boot a Dell diagnostic CD you download
    >> from their web site. It's possible you have bad RAM.
    >>
    >> At 11:50 AM 5/31/2005, Danny Cooper wrote:
    >> >With the kernel I removed all non-required devices
    >> >
    >> >Firewire, usb all the NIC's except em and removed all RAID and SCSI
    >> >controllers to make sure nothing would interfere.
    >> >
    >> >I tried to boot with the AMD64 CD but with no success, the machine just
    >> >hangs when it tries to load the CD, still trying to work out a
    >> solution to
    >> >the problem, but it just seems these DELL 2850 machines are for
    >> Windows or
    >> >RedHat!!!
    >> >
    >> >DC
    >> >
    >> >-----Original Message-----
    >> >From: owner-freebsd-stable@freebsd.org
    >> >[mailto:owner-freebsd-stable@freebsd.org] On Behalf Of Claus Guttesen
    >> >Sent: 31 May 2005 16:15
    >> >To: Danny Cooper
    >> >Cc: freebsd-stable@freebsd.org
    >> >Subject: Re: DELL PowerEdge 2850 and FreeBSD 5.4
    >> >
    >> > > I have installed FreeBSD 5.4 RELEASE and upgraded to -STABLE on a
    >> DELL
    >> > > PE2850.
    >> > >
    >> > > FreeBSD 5.4-STABLE #1: Wed May 25 23:43:12 BST 2005
    >> > > CPU: Intel(R) Xeon(TM) CPU 3.20GHz (3192.22-MHz 686-class CPU)
    >> > > real memory = 5100273664 (4864 MB)
    >> > > avail memory = 4189892608 (3995 MB)
    >> > > MPTable: <DELL PE 016D >
    >> > > FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs
    >> > > cpu0 (BSP): APIC ID: 0
    >> > > cpu1 (AP): APIC ID: 6
    >> > > amr0: <LSILogic PERC 4e/Di> Firmware 516A, BIOS H418, 256MB RAM
    >> > >
    >> > > I have disabled ACPI HTT and enabled PAE to make the whole system
    >> memory
    >> > > available.
    >> > >
    >> > > However the problem I have is the system can crash at any moment,
    >> and is
    >> >not
    >> > > load related. As the crash info below is when the machine was in
    >> an 100%
    >> > > idle state.
    >> >
    >> >I have the same hardware as well, running on the i386-port. I have
    >> >disabled usb with usbd_enable="NO" in /etc/rc.conf. I have no idea
    >> >whether this helps but havent't had an issue with the 2850. Except
    >> >with a qlogic-hba and the isp-driver (I suspect) *on* amd64, but *not*
    >> >on i386.
    >> >
    >> >Claus
    >> >_______________________________________________
    >> >freebsd-stable@freebsd.org mailing list
    >> >http://lists.freebsd.org/mailman/listinfo/freebsd-stable
    >> >To unsubscribe, send any mail to
    >> "freebsd-stable-unsubscribe@freebsd.org"
    >> >
    >> >
    >> >_______________________________________________
    >> >freebsd-stable@freebsd.org mailing list
    >> >http://lists.freebsd.org/mailman/listinfo/freebsd-stable
    >> >To unsubscribe, send any mail to
    >> "freebsd-stable-unsubscribe@freebsd.org"
    >>
    >>
    >> Vinny Abello
    >> Network Engineer
    >> Server Management
    >> vinny@tellurian.com
    >> (973)300-9211 x 125
    >> (973)940-6125 (Direct)
    >> PGP Key Fingerprint: 3BC5 9A48 FC78 03D3 82E0 E935 5325 FBCB 0100 977A
    >>
    >> Tellurian Networks - The Ultimate Internet Connection
    >> http://www.tellurian.com (888)TELLURIAN
    >>
    >> "Courage is resistance to fear, mastery of fear - not absence of
    >> fear" -- Mark Twain
    >>
    >>
    >> _______________________________________________
    >> freebsd-stable@freebsd.org mailing list
    >> http://lists.freebsd.org/mailman/listinfo/freebsd-stable
    >> To unsubscribe, send any mail to
    >> "freebsd-stable-unsubscribe@freebsd.org"
    >>
    >>
    >> _______________________________________________
    >> freebsd-stable@freebsd.org mailing list
    >> http://lists.freebsd.org/mailman/listinfo/freebsd-stable
    >> To unsubscribe, send any mail to
    >> "freebsd-stable-unsubscribe@freebsd.org"
    >
    >
    > _______________________________________________
    > freebsd-stable@freebsd.org mailing list
    > http://lists.freebsd.org/mailman/listinfo/freebsd-stable
    > To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org"

    _______________________________________________
    freebsd-stable@freebsd.org mailing list
    http://lists.freebsd.org/mailman/listinfo/freebsd-stable
    To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org"

  • Next message: Claus Guttesen: "Re: repeatable crash with 5.4-RELEASE and PAE"

    Relevant Pages

    • Re: Problems With All USB Devices Connected to Dimension 8300
      ... I have 5 USB Root Hub entries with Power Management tabs. ... There is a thread on DELL TALK about someone who is having the exact same problems with his Maxtor One Touch USB II External drive, ... It may be a common problem with 8200 and 8300 machines and Dell doesn't want to admit it, which is why their tech support wants you to spend 3-4 hours on the phone with them running tests, before they will replace the motherboard (and USB controller) knowing it may not fix a problem that is possibly inherent to these models. ...
      (alt.sys.pc-clone.dell)
    • RE: DELL PowerEdge 2850 and FreeBSD 5.4
      ... >I have checked on the DELL site for any updates to the BIOS/Firmware and the ... >I have now disabled the USB via rc.conf to see if the reboots still occur. ... obviously a problem with that controller, but after that was resolved, the ... I had problems with an slightly older Dell ...
      (freebsd-stable)
    • Re: USB2.0 compatibility
      ... I had to buy an USB 2.0 controller card to get up to snuff. ... listed in Device Manager as Intel 8280 1BA/BAM USB Universal Host ... Dell is an older model, maybe 5 years old (that's all I know at this ...
      (alt.sys.pc-clone.dell)
    • Re: Vs2005 to PDA to Rs232 interface
      ... Serial support in 2.0 is basically the same as OpenNETCF 1.4, ... you don't have to port the board support package and other ... I realize comparing the Dell x51v to our pcb is apples to oranges but it ... Rs232 and Usb connections) is not due ...
      (microsoft.public.dotnet.framework.compactframework)
    • Re: 70% CPU Usage Due to Hardware Interrupt Conflicts
      ... I would suggest looking for updated usb drivers from Dell. ... > CPU 70% utilized (as measured by Windows Task Manager) ...
      (microsoft.public.windowsxp.general)