On Sun, Feb 01, 2009 at 07:56:48PM -0500, Pete Carah
wrote:> I fixed the problem on my 4801's by having noticed a correlation with
> psm and hangs on my laptop, and
> thought there may be a LOR or such involving the keyboard driver and/or
> kbdmux. Since a 4801 has no need
> of those drivers, but *does* contain the hardware they control, just
> with no external peripherals connected, I tried
> configuring the Soekris kernel with all vestiges of atkbdc, psm, kbdmux,
> sc, and such removed. This did appear to fix the hangs.
Hmmm... not for me. This is my kernel config for the hanging net4801s.
It is being in use for a couple of years now and I didn't change it
before the trouble began early December:
---------------------- cut here --------------------------------------------
# SOEKRIS kernel config file, based upon FreeBSD 6.0-STABLE 2006-01-03.
#cpu I486_CPU
cpu I586_CPU
ident SOEKRIS
options CPU_SOEKRIS #Enable Soekris hardware stuff.
options CPU_GEODE #GEODE GL1100 Chips (Soekris)
#device pf #DON'T Enable PF (use as a module!)
makeoptions DEBUG=-g # Build kernel with gdb(1) debug symbols
options SCHED_4BSD # 4BSD scheduler
options PREEMPTION # Enable kernel thread preemption
options INET # InterNETworking
options INET6 # IPv6 communications protocols
options SCTP # Stream Control Transmission Protocol
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 UFS_GJOURNAL # Enable gjournal-based UFS journaling
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 PROCFS # Process filesystem (requires PSEUDOFS)
options PSEUDOFS # Pseudo-filesystem framework
options GEOM_PART_GPT # GUID Partition Tables.
options GEOM_LABEL # Provides labelization
options COMPAT_43TTY # BSD 4.3 TTY compat [KEEP THIS!]
options COMPAT_FREEBSD6 # Compatible with FreeBSD6
options SCSI_DELAY=1000 # 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 ADAPTIVE_GIANT # Giant mutex is adaptive.
options STOP_NMI # Stop CPUS using NMI instead of IPI
options AUDIT # Security event auditing
# options SMP # Symmetric MultiProcessor Kernel
# device apic # I/O APIC
# CPU frequency control
device cpufreq
# Bus support.
device eisa
device pci
# ATA and ATAPI devices
device ata
device atadisk # ATA disk drives
options ATA_STATIC_ID # Static device numbering
device agp # support several AGP chipsets
# Add suspend/resume support for the i8254.
device pmtimer
# Serial (COM) ports
device sio # 8250, 16[45]50 based serial ports
device uart # Generic UART driver
device miibus # MII bus support
device sis # Silicon Integrated Systems SiS 900/SiS 7016
# Pseudo devices.
device loop # Network loopback
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"
# 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 usb # USB Bus (required)
#device udbp # USB Double Bulk Pipe devices
device ugen # Generic
-------------------------- cut here ---------------------------------------
As you see, no atkbdc, psm, kbdmux, sc, etc.... but still sporadic
hangs... :(
> The hangs only seem to happen on AMD hardware; I have several
> ich{3,5}+p3 or p4 machines that don't hang.
>
> Before I figured that out I noticed some PHK notes about enabling the
> hardware watchdog and did that too, but did the upgrade mentioned above
> before any watchdog hits. I haven't seen any spontaneous reboots
(which
> a watchdog hit would look like) since the reconfig either.
>
> -- Pete
Regards,
-cpghost.
--
Cordula's Web. http://www.cordula.ws/