Date: Thu, 18 Feb 1999 23:26:40 +0100 (CET) From: frank@barda.agala.harz.de To: FreeBSD-gnats-submit@freebsd.org Subject: kern/10154: syncing disks ... giving up Message-ID: <199902182226.XAA05306@vogon.agala.harz.de>
next in thread | raw e-mail | index | archive | help
>Number: 10154
>Category: kern
>Synopsis: System is unable to sync the disks when it shuts down
>Confidential: no
>Severity: serious
>Priority: high
>Responsible: freebsd-bugs
>State: open
>Quarter:
>Keywords:
>Date-Required:
>Class: sw-bug
>Submitter-Id: current-users
>Arrival-Date: Thu Feb 18 14:40:00 PST 1999
>Closed-Date:
>Last-Modified:
>Originator: Frank J. Beckmann
>Release: FreeBSD 3.1-RELEASE i386
>Organization:
agala naga doron
>Environment:
Intel DK440LX, 2 * Pentium II 333, 64 MB ram
dmesg:
Copyright (c) 1992-1999 FreeBSD Inc.
Copyright (c) 1982, 1986, 1989, 1991, 1993
The Regents of the University of California. All rights reserved.
FreeBSD 3.1-RELEASE #0: Tue Feb 16 16:09:06 CET 1999
root@vogon.agala.harz.de:/usr/src/sys/compile/VOGON
Timecounter "i8254" frequency 1193182 Hz
CPU: Pentium II/Xeon/Celeron (686-class CPU)
Origin = "GenuineIntel" Id = 0x652 Stepping=2
Features=0x183fbff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,MMX,<b24>>
real memory = 67108864 (65536K bytes)
config> pnp 1 0 os enable port0 0x534 port2 0x220 irq0 10 drq0 1 drq1 3
avail memory = 61181952 (59748K bytes)
Programming 24 pins in IOAPIC #0
FreeBSD/SMP: Multiprocessor motherboard
cpu0 (BSP): apic id: 1, version: 0x00040011, at 0xfee00000
cpu1 (AP): apic id: 0, version: 0x00040011, at 0xfee00000
io0 (APIC): apic id: 2, version: 0x00170011, at 0xfec00000
Preloaded elf kernel "kernel" at 0xf03d7000.
Preloaded userconfig_script "/boot/sound.config" at 0xf03d709c.
vinum: loaded
Probing for devices on PCI bus 0:
chip0: <Host to PCI bridge (vendor=8086 device=7180)> rev 0x03 on pci0.0.0
chip1: <PCI to PCI bridge (vendor=8086 device=7181)> rev 0x03 on pci0.1.0
chip2: <Intel 82371AB PCI to ISA bridge> rev 0x01 on pci0.2.0
ide_pci0: <Intel PIIX4 Bus-master IDE controller> rev 0x01 on pci0.2.1
uhci0: <Intel 82371AB/EB USB Host Controller> rev 0x01 int d irq 19 on pci0.2.2
usb0: USB version 1.0, interrupting at 9
chip3: <Intel 82371AB Power management controller> rev 0x01 on pci0.2.3
fxp0: <Intel EtherExpress Pro 10/100B Ethernet> rev 0x02 int a irq 19 on pci0.3.0
fxp0: Ethernet address 00:a0:c9:61:7f:06
ahc0: <Adaptec aic7895 Ultra SCSI adapter> rev 0x03 int a irq 17 on pci0.9.0
ahc0: aic7895 Wide Channel A, SCSI Id=7, 16/255 SCBs
ahc1: <Adaptec aic7895 Ultra SCSI adapter> rev 0x03 int b irq 17 on pci0.9.1
ahc1: aic7895 Wide Channel B, SCSI Id=7, 16/255 SCBs
vga0: <Matrox MGA 2164W graphics accelerator> rev 0x00 int a irq 18 on pci0.14.0
bktr0: <BrookTree 878> rev 0x02 int a irq 19 on pci0.15.0
bti2c0: <bt848 Hard/Soft I2C controller>
iicbb0: <I2C generic bit-banging driver> on bti2c0
iicbus0: <Philips I2C bus> on iicbb0 master-only
iicsmb0: <I2C to SMB bridge> on iicbus0
smbus0: <System Management Bus> on iicsmb0
smb0: <SMBus general purpose I/O> on smbus0
iic0: <I2C general purpose I/O> on iicbus0
smbus1: <System Management Bus> on bti2c0
smb1: <SMBus general purpose I/O> on smbus1
Hauppauge WinCast/TV, Philips FR1216 PAL tuner, msp3400c stereo.
Detected a MSP3410D-B4
Probing for devices on PCI bus 1:
Probing for PnP devices:
CSN 1 Vendor ID: CSC0b35 [0x350b630e] Serial 0xffffffff Comp ID: @@@0000 [0x00000000]
mss_attach <CS4236B>1 at 0x530 irq 10 dma 1:3 flags 0x13
pcm1 (CS423x/Yamaha/AD1816 <CS4236B> sn 0xffffffff) at 0x530-0x537 irq 10 drq 1 flags 0x13 on isa
Probing for devices on the ISA bus:
sc0 on isa
sc0: VGA color <16 virtual consoles, flags=0x0>
atkbdc0 at 0x60-0x6f on motherboard
atkbd0 irq 1 on isa
psm0 irq 12 on isa
psm0: model Generic PS/2 mouse, device ID 0
sio0 at 0x3f8-0x3ff irq 4 flags 0x10 on isa
sio0: type 16550A
sio1 at 0x2f8-0x2ff irq 3 on isa
sio1: type 16550A
sio4 at 0x100-0x107 flags 0x10b05 on isa
sio4: type TL16750 (multiport)
sio5 at 0x108-0x10f flags 0x10b05 on isa
sio5: type TL16750 (multiport)
sio6 at 0x110-0x117 flags 0x310b05 on isa
sio6: type TL16750 (multiport)
sio7 at 0x118-0x11f flags 0x310b05 on isa
sio7: type TL16750 (multiport)
sio8 at 0x140-0x147 flags 0x310b05 on isa
sio8: type TL16750 (multiport)
sio9 at 0x128-0x12f flags 0x10b05 on isa
sio9: type TL16750 (multiport)
sio10 at 0x130-0x137 flags 0x10b05 on isa
sio10: type TL16750 (multiport)
sio11 at 0x138-0x13f irq 11 flags 0x10b05 on isa
sio11: type TL16750 (multiport master)
pcm0 not probed due to drq conflict with pcm1 at 1
pca0 on motherboard
pca0: PC speaker audio driver
wdc0 not found at 0x1f0
wdc1 not found at 0x170
fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa
fdc0: FIFO enabled, 8 bytes threshold
fd0: 1.44MB 3.5in
ppc0 at 0x378 irq 7 on isa
ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode
ppc0: FIFO with 16/16/8 bytes threshold
nlpt0: <generic printer> on ppbus 0
nlpt0: Interrupt-driven port
ppi0: <generic parallel i/o> on ppbus 0
lppps0: <Pulse per second Timing Interface> on ppbus 0
plip0: <PLIP network interface> on ppbus 0
vga0 at 0x3b0-0x3df maddr 0xa0000 msize 131072 on isa
npx0 on motherboard
npx0: INT 16 interface
apm0 on isa
apm: found APM BIOS version 1.2
usb0: <Intel 82371AB/EB USB Host Controller>
uhub0 at usb0
uhub0: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1
uhub0: 2 ports with 2 removable, self powered
APIC_IO: Testing 8254 interrupt delivery
APIC_IO: routing 8254 via pin 2
IP packet filtering initialized, divert enabled, rule-based forwarding enabled, unlimited logging
ccd0-3: Concatenated disk drivers
DUMMYNET initialized (980901) -- size dn_pkt 48
Waiting 4 seconds for SCSI devices to settle
SMP: AP CPU #1 Launched!
sa0 at ahc1 bus 0 target 0 lun 0
sa0: <WANGTEK 5150ES SCSI ES41 C510> Removable Sequential Access SCSI-CCS device
sa0: 3.300MB/s transfers
da1 at ahc1 bus 0 target 1 lun 0
da1: <SyQuest SQ3270S 3-14> Removable Direct Access SCSI-2 device
da1: 5.0MB/s transfers (5.0MHz, offset 15)
da1: 256MB (524288 512 byte sectors: 64H 32S/T 256C)
da4 at ahc0 bus 0 target 1 lun 0
da4: <IBM DPES-31080 S31Q> Fixed Direct Access SCSI-2 device
da4: 10.0MB/s transfers (10.0MHz, offset 15), Tagged Queueing Enabled
da4: 1034MB (2118144 512 byte sectors: 255H 63S/T 131C)
da5 at ahc1 bus 0 target 5 lun 0
da5: <IBM DPES-31080 S31Q> Fixed Direct Access SCSI-2 device
da5: 10.0MB/s transfers (10.0MHz, offset 15), Tagged Queueing Enabled
da5: 1034MB (2118144 512 byte sectors: 255H 63S/T 131C)
da0 at ahc0 bus 0 target 0 lun 0
da0: <IBM DDRS-34560W S92A> Fixed Direct Access SCSI-2 device
da0: 40.0MB/s transfers (20.0MHz, offset 8, 16bit), Tagged Queueing Enabled
da0: 4357MB (8925000 512 byte sectors: 255H 63S/T 555C)
WARNING: / was not properly dismounted
cd0 at ahc1 bus 0 target 3 lun 0
cd0: <PLEXTOR CD-ROM PX-32TS 1.02> Removable CD-ROM SCSI-2 device
cd0: 20.0MB/s transfers (20.0MHz, offset 15)
cd0: cd present [151809 x 2048 byte records]
ffs_mountfs: superblock updated for soft updates
ffs_mountfs: superblock updated for soft updates
ffs_mountfs: superblock updated for soft updates
ffs_mountfs: superblock updated for soft updates
(da0:ahc0:0:0:0): tagged openings now 64
/sys/i386/conf/VOGON:
#
# VOGON -- Intel DK440LX
#
#
# This directive is mandatory; it defines the architecture to be
# configured for; in this case, the 386 family based IBM-PC and
# compatibles.
#
machine "i386"
#
# This is the ``identification'' of the kernel. Usually this should
# be the same as the name of your kernel.
#
ident VOGON
#
# The `maxusers' parameter controls the static sizing of a number of
# internal system tables by a complicated formula defined in param.c.
#
maxusers 64
#
# Certain applications can grow to be larger than the 128M limit
# that FreeBSD initially imposes. Below are some options to
# allow that limit to grow to 256MB, and can be increased further
# with changing the parameters. MAXDSIZ is the maximum that the
# limit can be set to, and the DFLDSIZ is the default value for
# the limit. You might want to set the default lower than the
# max, and explicitly set the maximum with a shell command for processes
# that regularly exceed the limit like INND.
#
options "MAXDSIZ=(512*1024*1024)"
options "DFLDSIZ=(512*1024*1024)"
# When this is set, be extra conservative in various parts of the kernel
# and choose functionality over speed (on the widest variety of systems).
options FAILSAFE
# Options for the VM subsystem
options PQ_LARGECACHE # color for 512k/16k cache
# This allows you to actually store this configuration file into
# the kernel binary itself, where it may be later read by saying:
# strings -aout -n 3 /kernel | grep ^___ | sed -e 's/^___//' > MYKERNEL
#
options INCLUDE_CONFIG_FILE # Include this file in kernel
#
# This directive defines a number of things:
# - The compiled kernel is to be called `kernel'
# - The root filesystem might be on partition wd0a
# - Crash dumps will be written to wd0b, if possible. Specifying the
# dump device here is not recommended. Use dumpon(8).
#
config kernel root on da0s1
#####################################################################
# SMP OPTIONS:
#
# SMP enables building of a Symmetric MultiProcessor Kernel.
# APIC_IO enables the use of the IO APIC for Symmetric I/O.
# NCPU sets the number of CPUs, defaults to 2.
# NBUS sets the number of busses, defaults to 4.
# NAPIC sets the number of IO APICs on the motherboard, defaults to 1.
# NINTR sets the total number of INTs provided by the motherboard.
#
# Notes:
#
# An SMP kernel will ONLY run on an Intel MP spec. qualified motherboard.
#
# Be sure to disable 'cpu "I386_CPU"' && 'cpu "I486_CPU"' for SMP kernels.
#
# Check the 'Rogue SMP hardware' section to see if additional options
# are required by your hardware.
#
# Mandatory:
options SMP # Symmetric MultiProcessor Kernel
options APIC_IO # Symmetric (APIC) I/O
#####################################################################
# CPU OPTIONS
#
# You must specify at least one CPU (the one you intend to run on);
# deleting the specification for CPUs you don't need to use may make
# parts of the system run faster. This is especially true removing
# I386_CPU.
#
cpu "I686_CPU" # aka Pentium Pro(tm)
#####################################################################
# COMPATIBILITY OPTIONS
#
# Implement system calls compatible with 4.3BSD and older versions of
# FreeBSD. You probably do NOT want to remove this as much current code
# still relies on the 4.3 emulation.
#
options "COMPAT_43"
#
# Allow user-mode programs to manipulate their local descriptor tables.
# This option is required for the WINE Windows(tm) emulator, and is
# not used by anything else (that we know of).
#
options USER_LDT #allow user-level control of i386 ldt
#
# These three options provide support for System V Interface
# Definition-style interprocess communication, in the form of shared
# memory, semaphores, and message queues, respectively.
#
options SYSVSHM
options SYSVSEM
options SYSVMSG
#
# This option includes a MD5 routine in the kernel, this is used for
# various authentication and privacy uses.
#
options "MD5"
#
# Allow processes to switch to vm86 mode, as well as enabling direct
# user-mode access to the I/O port space. This option is necessary for
# the doscmd emulator to run.
#
options "VM86"
#####################################################################
# DEBUGGING OPTIONS
#
# KTRACE enables the system-call tracing facility ktrace(2).
#
options KTRACE #kernel tracing
#
# PERFMON causes the driver for Pentium/Pentium Pro performance counters
# to be compiled. See perfmon(4) for more information.
#
options PERFMON
# XXX - this doesn't belong here.
# Allow ordinary users to take the console - this is useful for X.
options UCONSOLE
# XXX - this doesn't belong here either
options USERCONFIG #boot -c editor
options VISUAL_USERCONFIG #visual boot -c editor
#####################################################################
# NETWORKING OPTIONS
#
# Protocol families:
# Only the INET (Internet) family is officially supported in FreeBSD.
# Source code for the NS (Xerox Network Service) is provided for amusement
# value.
#
options INET #Internet communications protocols
#
# Network interfaces:
# The `loop' pseudo-device is MANDATORY when networking is enabled.
# The `ether' pseudo-device provides generic code to handle
# Ethernets; it is MANDATORY when a Ethernet device driver is
# configured.
# The 'fddi' pseudo-device provides generic code to support FDDI.
# The `sppp' pseudo-device serves a similar role for certain types
# of synchronous PPP links (like `cx', `ar').
# The `sl' pseudo-device implements the Serial Line IP (SLIP) service.
# The `ppp' pseudo-device implements the Point-to-Point Protocol.
# The `bpfilter' pseudo-device enables the Berkeley Packet Filter. Be
# aware of the legal and administrative consequences of enabling this
# option. The number of devices determines the maximum number of
# simultaneous BPF clients programs runnable.
# The `disc' pseudo-device implements a minimal network interface,
# which throws away all packets sent and never receives any. It is
# included for testing purposes.
# The `tun' pseudo-device implements the User Process PPP (iijppp)
#
# The PPP_BSDCOMP option enables support for compress(1) style entire
# packet compression, the PPP_DEFLATE is for zlib/gzip style compression.
# PPP_FILTER enables code for filtering the ppp data stream and selecting
# events for resetting the demand dial activity timer - requires bpfilter.
# See pppd(8) for more details.
#
pseudo-device ether #Generic Ethernet
pseudo-device sppp #Generic Synchronous PPP
pseudo-device loop #Network loopback device
pseudo-device bpfilter 4 #Berkeley packet filter
pseudo-device disc #Discard device
pseudo-device tun 6 #Tunnel driver (user process ppp(8))
pseudo-device sl 6 #Serial Line IP
pseudo-device ppp 6 #Point-to-point protocol
options PPP_BSDCOMP #PPP BSD-compress support
options PPP_DEFLATE #PPP zlib/deflate/gzip support
options PPP_FILTER #enable bpf filtering (needs bpfilter)
#
# Internet family options:
#
# MROUTING enables the kernel multicast packet forwarder, which works
# with mrouted(8).
#
# IPFIREWALL enables support for IP firewall construction, in
# conjunction with the `ipfw' program. IPFIREWALL_VERBOSE sends
# logged packets to the system logger. IPFIREWALL_VERBOSE_LIMIT
# limits the number of times a matching entry can be logged.
#
# WARNING: IPFIREWALL defaults to a policy of "deny ip from any to any"
# and if you do not add other rules during startup to allow access,
# YOU WILL LOCK YOURSELF OUT. It is suggested that you set firewall=open
# in /etc/rc.conf when first enabling this feature, then refining the
# firewall rules in /etc/rc.firewall after you've tested that the new kernel
# feature works properly.
#
# IPFIREWALL_DEFAULT_TO_ACCEPT causes the default rule (at boot) to
# allow everything. Use with care, if a cracker can crash your
# firewall machine, they can get to your protected machines. However,
# if you are using it as an as-needed filter for specific problems as
# they arise, then this may be for you. Changing the default to 'allow'
# means that you won't get stuck if the kernel and /sbin/ipfw binary get
# out of sync.
#
# IPDIVERT enables the divert IP sockets, used by ``ipfw divert''
#
# IPFILTER enables Darren Reed's ipfilter package.
# IPFILTER_LOG enables ipfilter's logging.
# IPFILTER_LKM enables LKM support for an ipfilter module (untested).
#
options MROUTING # Multicast routing
options IPFIREWALL #firewall
options IPFIREWALL_VERBOSE #print information about
# dropped packets
options IPFIREWALL_FORWARD #enable xparent proxy support
#options "IPFIREWALL_VERBOSE_LIMIT=100" #limit verbosity
#options IPFIREWALL_DEFAULT_TO_ACCEPT #allow everything by default
options IPDIVERT #divert sockets
#options IPFILTER #kernel ipfilter support
#options IPFILTER_LOG #ipfilter logging
#options IPFILTER_LKM #kernel support for ip_fil.o LKM
# ICMP_BANDLIM enables icmp error response bandwidth limiting. You
# typically want this option as it will help protect the machine from
# D.O.S. packet attacks.
#
options "ICMP_BANDLIM"
# DUMMYNET enables the "dummynet" bandwidth limiter. You need
# IPFIREWALL as well. See the dummynet(4) manpage for more info.
# BRIDGE enables bridging between ethernet cards -- see bridge(4).
# You can use IPFIREWALL and dummynet together with bridging.
options DUMMYNET
#options BRIDGE
#####################################################################
# FILESYSTEM OPTIONS
#
# Only the root, /usr, and /tmp filesystems need be statically
# compiled; everything else will be automatically loaded at mount
# time. (Exception: the UFS family---FFS, and MFS --- cannot
# currently be demand-loaded.) Some people still prefer to statically
# compile other filesystems as well.
#
# NB: The NULL, PORTAL, UMAP and UNION filesystems are known to be
# buggy, and WILL panic your system if you attempt to do anything with
# them. They are included here as an incentive for some enterprising
# soul to sit down and fix them.
#
# One of these is mandatory:
options FFS #Fast filesystem
options MFS #Memory File System
options NFS #Network File System
# The rest are optional:
options FFS_ROOT #FFS usable as root device
# Soft updates is technique for improving file system speed and
# making abrupt shutdown less risky. It is not enabled by default due
# to copyright restraints on the code that implement it.
#
# Read .../../ufs/ffs/README.softupdates to learn what you need to
# do to enable this. ../../../contrib/sys/softupdates/README gives
# more details on how they actually work.
#
options SOFTUPDATES
# Allows MFS filesystems to be exported via nfs
options EXPORTMFS
# Allow this many swap-devices.
options NSWAPDEV=20
# In particular multi-session CD-Rs might require a huge amount of
# time in order to "settle". If we are about mounting them as the
# root f/s, we gotta wait a little.
#
# The number is supposed to be in seconds.
options "CD9660_ROOTDELAY=20"
#####################################################################
# POSIX P1003.1B
# Real time extensions added int the 1993 Posix
# P1003_1B: Infrastructure
# _KPOSIX_PRIORITY_SCHEDULING: Build in _POSIX_PRIORITY_SCHEDULING
# _KPOSIX_VERSION: Version kernel is built for
#options "P1003_1B"
#options "_KPOSIX_PRIORITY_SCHEDULING"
#options "_KPOSIX_VERSION=199309L"
#####################################################################
# SCSI DEVICES
# SCSI DEVICE CONFIGURATION
controller ahc0
controller ahc1
controller scbus0 at ahc0 #base SCSI code
controller scbus1 at ahc1
device ch0 #SCSI media changers
device da0 #SCSI direct access devices (aka disks)
device da4 at scbus0 target1
device da5 at scbus1 target5
device sa0 at scbus1 target0 #SCSI tapes
device sa1 at scbus0 target4
device cd0 #SCSI CD-ROMs
#device od0 #SCSI optical disk
device pass0 #CAM passthrough driver
# The previous devices (ch, da, st, cd) are recognized by config.
# config doesn't (and shouldn't) know about these newer ones,
# so we have to specify that they are on a SCSI bus with the "at scbus?"
# clause.
device pt0 at scbus? # SCSI processor type
device sctarg0 at scbus? # SCSI target
# CAM OPTIONS:
# CAM_MAX_HIGHPOWER: Maximum number of concurrent high power (start unit) cmds
# SCSI_DELAY: The number of MILLISECONDS to freeze the SIM (scsi adapter)
# queue after a bus reset, and the number of milliseconds to
# freeze the device queue after a bus device reset.
options "CAM_MAX_HIGHPOWER=4"
options SCSI_DELAY=4000 # Be pessimistic about Joe SCSI device
# Options for the CAM sequential access driver:
# SA_SPACE_TIMEOUT: Timeout for space operations, in minutes
# SA_REWIND_TIMEOUT: Timeout for rewind operations, in minutes
# SA_ERASE_TIMEOUT: Timeout for erase operations, in minutes
options "SA_SPACE_TIMEOUT=(60)"
options "SA_REWIND_TIMEOUT=(2*60)"
options "SA_ERASE_TIMEOUT=(4*60)"
#####################################################################
# MISCELLANEOUS DEVICES AND OPTIONS
# The `pty' device usually turns out to be ``effectively mandatory'',
# as it is required for `telnetd', `rlogind', `screen', `emacs', and
# `xterm', among others.
pseudo-device pty 128 #Pseudo ttys - can go as high as 256
pseudo-device speaker #Play IBM BASIC-style noises out your speaker
pseudo-device gzip #Exec gzipped a.out's
pseudo-device vn #Vnode driver (turns a file into a device)
pseudo-device snp 3 #Snoop device - to look at pty/vty/etc..
pseudo-device ccd 4 #Concatenated disk driver
pseudo-device vinum #Vinum concat/mirror/raid driver
options VINUMDEBUG #enable Vinum debugging hooks
#####################################################################
# HARDWARE DEVICE CONFIGURATION
# ISA and EISA devices:
# EISA support is available for some device, so they can be auto-probed.
# Micro Channel is not supported at all.
#
# Mandatory ISA devices: isa, npx
#
controller isa0
#
# Options for `isa':
#
# AUTO_EOI_1 enables the `automatic EOI' feature for the master 8259A
# interrupt controller. This saves about 0.7-1.25 usec for each interrupt.
# This option breaks suspend/resume on some portables.
#
# AUTO_EOI_2 enables the `automatic EOI' feature for the slave 8259A
# interrupt controller. This saves about 0.7-1.25 usec for each interrupt.
# Automatic EOI is documented not to work for for the slave with the
# original i8259A, but it works for some clones and some integrated
# versions.
options "AUTO_EOI_1"
#options "AUTO_EOI_2"
# Enable PnP support in the kernel. This allows you to automaticly
# attach to PnP cards for drivers that support it and allows you to
# configure cards from USERCONFIG. See pnp(4) for more info.
controller pnp0
# The keyboard controller; it controlls the keyboard and the PS/2 mouse.
controller atkbdc0 at isa? port IO_KBD tty
# The AT keyboard
device atkbd0 at isa? tty irq 1
# `flags' for atkbd:
# 0x01 Force detection of keyboard, else we always assume a keyboard
# 0x02 Don't reset keyboard, useful for some newer ThinkPads
# 0x04 Old-style (XT) keyboard support, useful for older ThinkPads
# PS/2 mouse
device psm0 at isa? tty irq 12
# The video card driver.
device vga0 at isa? port ? conflicts
# Splash screen at start up! Screen savers require this too.
pseudo-device splash
# The syscons console driver (sco color console compatible).
device sc0 at isa? tty
options MAXCONS=16 # number of virtual consoles
options SC_HISTORY_SIZE=200 # number of history buffer lines
#
# `flags' for sc0:
# 0x01 Use a 'visual' bell
# 0x02 Use a 'blink' cursor
# 0x04 Use a 'underline' cursor
# 0x06 Use a 'blinking underline' (destructive) cursor
# 0x40 Make the bell quiet if it is rung in the backgroud vty.
#
# The Numeric Processing eXtension driver. This should be configured if
# your machine has a math co-processor, unless the coprocessor is very
# buggy. If it is not configured then you *must* configure math emulation
# (see above). If both npx0 and emulation are configured, then only npx0
# is used (provided it works).
device npx0 at isa? port IO_NPX iosiz 0x0 flags 0x0 irq 13
#
# `flags' for npx0:
# 0x01 don't use the npx registers to optimize bcopy
# 0x02 don't use the npx registers to optimize bzero
# 0x04 don't use the npx registers to optimize copyin or copyout.
# The npx registers are normally used to optimize copying and zeroing when
# all of the following conditions are satisfied:
# "I586_CPU" is an option
# the cpu is an i586 (perhaps not a Pentium)
# the probe for npx0 succeeds
# INT 16 exception handling works.
# Then copying and zeroing using the npx registers is normally 30-100% faster.
# The flags can be used to control cases where it doesn't work or is slower.
# Setting them at boot time using userconfig works right (the optimizations
# are not used until later in the bootstrap when npx0 is attached).
#
#
# `iosiz' for npx0:
# This can be used instead of the MAXMEM option to set the memory size. If
# it is nonzero, then it overrides both the MAXMEM option and the memory
# size reported by the BIOS. Setting it at boot time using userconfig takes
# effect on the next reboot after the change has been recorded in the kernel
# binary (the size is used early in the boot before userconfig has a chance
# to change it).
#
#
# Optional ISA and EISA devices:
#
#
# ST-506, ESDI, and IDE hard disks: `wdc' and `wd'
#
# The flags fields are used to enable the multi-sector I/O and
# the 32BIT I/O modes. The flags may be used in either the controller
# definition or in the individual disk definitions. The controller
# definition is supported for the boot configuration stuff.
#
# Each drive has a 16 bit flags value defined:
# The low 8 bits are the maximum value for the multi-sector I/O,
# where 0xff defaults to the maximum that the drive can handle.
# The high bit of the 16 bit flags (0x8000) allows probing for
# 32 bit transfers. Bit 14 (0x4000) enables a hack to wake
# up powered-down laptop drives. Bit 13 (0x2000) allows
# probing for PCI IDE DMA controllers, such as Intel's PIIX
# south bridges. Bit 12 (0x1000) sets LBA mode instead of the
# default CHS mode for accessing the drive. See the wd.4 man page.
#
# The flags field for the drives can be specified in the controller
# specification with the low 16 bits for drive 0, and the high 16 bits
# for drive 1.
# e.g.:
#controller wdc0 at isa? port "IO_WD1" bio irq 14 flags 0x00ff8004
#
# specifies that drive 0 will be allowed to probe for 32 bit transfers and
# a maximum multi-sector transfer of 4 sectors, and drive 1 will not be
# allowed to probe for 32 bit transfers, but will allow multi-sector
# transfers up to the maximum that the drive supports.
#
controller wdc0 at isa? port "IO_WD1" bio irq 14 flags 0xa0ffa0ff
disk wd0 at wdc0 drive 0
disk wd1 at wdc0 drive 1
controller wdc1 at isa? port "IO_WD2" bio irq 15 flags 0xa0ffa0ff
disk wd2 at wdc1 drive 0
disk wd3 at wdc1 drive 1
#
# ATAPI enables the support for ATAPI-compatible IDE devices
#
options ATAPI #Enable ATAPI support for IDE bus
options ATAPI_STATIC #Don't do it as an LKM
#
# This option allow you to override the default probe time for IDE
# devices, to get a faster probe. Setting this below 10000 violate
# the IDE specs, but may still work for you (it will work for most
# people).
#
options IDE_DELAY=8000 # Be optimistic about Joe IDE device
#
# Standard floppy disk controllers and floppy tapes: `fdc', `fd', and `ft'
#
controller fdc0 at isa? port "IO_FD1" bio irq 6 drq 2
disk fd0 at fdc0 drive 0
disk fd1 at fdc0 drive 1
#
# Other standard PC hardware: `lpt', `mse', `sio', etc.
#
# lpt: printer port
# lpt specials:
# The port may be specified as ?. This will cause the
# driver to scan the BIOS port list.
# The irq clause may be omitted. This will force the port
# into polling mode.
# sio: serial ports (see sio(4))
device sio0 at isa? port "IO_COM1" tty flags 0x10 irq 4
device sio1 at isa? port "IO_COM2" tty irq 3
options COM_MULTIPORT
device sio4 at isa? port 0x100 tty flags 0x00010b05
device sio5 at isa? port 0x108 tty flags 0x00010b05
device sio6 at isa? port 0x110 tty flags 0x00310b05
device sio7 at isa? port 0x118 tty flags 0x00310b05
device sio8 at isa? port 0x140 tty flags 0x00310b05
device sio9 at isa? port 0x128 tty flags 0x00010b05
device sio10 at isa? port 0x130 tty flags 0x00010b05
device sio11 at isa? port 0x138 tty flags 0x00010b05 irq 11
#
# `flags' for serial drivers that support consoles (only for sio now):
# 0x10 enable console support for this unit. The other console flags
# are ignored unless this is set. Enabling console support does
# not make the unit the preferred console - boot with -h or set
# the 0x20 flag for that. Currently, at most one unit can have
# console support; the first one (in config file order) with
# this flag set is preferred. Setting this flag for sio0 gives
# the old behaviour.
# 0x20 force this unit to be the console (unless there is another
# higher priority console). This replaces the COMCONSOLE option.
# 0x40 reserve this unit for low level console operations. Do not
# access the device in any normal way.
#
# PnP `flags' (set via userconfig using pnp x flags y)
# 0x1 disable probing of this device. Used to prevent your modem
# from being attached as a PnP modem.
#
options CONSPEED=115200 #default speed for serial console
# Other flags for sio that aren't documented in the man page.
# 0x20000 enable hardware RTS/CTS and larger FIFOs. Only works for
# ST16650A-compatible UARTs.
# Luigi's snd code (use INSTEAD of snd0 and all VOXWARE drivers!).
# You may also wish to enable the pnp controller with this, for pnp
# sound cards.
#
device pcm0 at isa? port ? tty irq 10 drq 1
# Not controlled by `snd'
device pca0 at isa? port "IO_TIMER1" tty
#
# Miscellaneous hardware:
#
# apm: Laptop Advanced Power Management (experimental)
# bktr: Brooktree bt848/848a/849/878/879 family video capture and TV Tuner board
device apm0 at isa?
#
# PCI devices & PCI options:
#
# The main PCI bus device is `pci'. It provides auto-detection and
# configuration support for all devices on the PCI bus, using either
# configuration mode defined in the PCI specification.
#
# The `ahc' device provides support for the Adaptec 29/3940(U)(W)
# and motherboard based AIC7870/AIC7880 adapters.
#
# The `fxp' device provides support for the Intel EtherExpress Pro/100B
# PCI Fast Ethernet adapters.
#
# The 'bktr' device is a PCI video capture device using the Brooktree
# bt848/bt848a/bt849/bt878/bt879 chipset. When used with a TV Tuner it forms a
# TV card, eg Miro PC/TV,Hauppauge WinCast/TV WinTV, VideoLogic Captivator,
# Intel Smart Video III, AverMedia, IMS Turbo.
# The following options can be used to override the auto detection
# options OVERRIDE_CARD=xxx
# options OVERRIDE_TUNER=xxx
# options OVERRIDE_MSP=1
# options OVERRIDE_DBX=1
# The current values are found in /usr/src/sys/pci/brooktree848.c
#
# option BROOKTREE_SYSTEM_DEFAULT=BROOKTREE_PAL
# This is required for Dual Crystal (28&35Mhz) boards where PAL is used
# to prevent hangs during initialisation. eg VideoLogic Captivator PCI.
#
# PAL or SECAM users who have a 28Mhz crystal (and no 35Mhz crystal)
# must enable PLL mode with this option. eg some new Hauppauge cards.
# option BKTR_USE_PLL
#
# Using sysctl(8) run-time overrides on a per-card basis can be made
#
controller pci0
device fxp0
# Brooktree driver has been ported to the new I2C framework. Thus,
# you'll need at least iicbus, iicbb and smbus. iic/smb are only needed if you
# want to control other I2C slaves connected to the external connector of
# some cards.
#
device bktr0
options BROOKTREE_SYSTEM_DEFAULT=BROOKTREE_PAL
options BKTR_USE_PLL
#
# SMB bus
#
# System Management Bus support provided by the 'smbus' device.
#
# Supported devices:
# smb standard io
#
# Supported interfaces:
# iicsmb I2C to SMB bridge with any iicbus interface
# bktr brooktree848 I2C hardware interface
#
controller smbus0
device smb0 at smbus?
#
# I2C Bus
#
# Philips i2c bus support is provided by the `iicbus' device.
#
# Supported devices:
# ic i2c network interface
# iic i2c standard io
# iicsmb i2c to smb bridge. Allow i2c i/o with smb commands.
#
# Supported interfaces:
# pcf Philips PCF8584 ISA-bus controller
# bktr brooktree848 I2C software interface
#
# Other:
# iicbb generic I2C bit-banging code (needed by lpbb, bktr)
#
controller iicbus0
controller iicbb0
device ic0 at iicbus?
device iic0 at iicbus?
device iicsmb0 at iicbus?
#controller pcf0 at isa? port 0x320 net irq 5
# Parallel-Port Bus
#
# Parallel port bus support is provided by the `ppbus' device.
# Multiple devices may be attached to the parallel port, devices
# are automatically probed and attached when found.
#
# Supported devices:
# vpo Iomega Zip Drive
# Requires SCSI disk support ('scbus' and 'da'), best
# performance is achieved with ports in EPP 1.9 mode.
# nlpt Parallel Printer, use _instead_ of lpt0
# plip Parallel network interface
# ppi General-purpose I/O ("Geek Port")
# pps Pulse per second Timing Interface
# lpbb Philips official parallel port I2C bit-banging interface
#
# Supported interfaces:
# ppc ISA-bus parallel port interfaces.
#
device ppc0 at isa? port? net irq 7
controller ppbus0
controller vpo0 at ppbus?
device nlpt0 at ppbus?
device plip0 at ppbus?
device ppi0 at ppbus?
device pps0 at ppbus?
device lpbb0 at ppbus?
# USB support
# UHCI controller
controller uhci0
# OHCI controller
controller ohci0
# General USB code (mandatory for USB)
controller usb0
#
# for the moment we have to specify the priorities of the device
# drivers explicitly by the ordering in the list below. This will
# be changed in the future.
#
# USB mouse
device ums0
# USB keyboard
device ukbd0
# USB printer
device ulpt0
# USB hub (kind of mandatory, no other driver is available for the root hub)
device uhub0
# USB communications driver
device ucom0
# USB modem driver
device umodem0
# Human Interface Device (anything with buttons and dials)
device hid0
# Generic USB device driver
device ugen0
#
options USBVERBOSE
# More undocumented options for linting.
options SHOW_BUSYBUFS # List buffers that prevent root unmount
/etc/fstab:
# Device Mountpoint FStype Options Dump Pass#
/dev/da0s1b none swap sw 0 0
/dev/da0s1a / ufs rw 1 1
/dev/da0s1e /usr ufs rw 1 2
/dev/da0s1f /home ufs rw 1 2
/dev/da0s1g /var ufs rw 1 2
/dev/da0s1b /tmp mfs rw 0 0
/dev/ccd0c /ccd0 ufs rw 1 2
proc /proc procfs rw 0 0
/dev/cd0c /cdrom cd9660 ro,noauto 0 0
It also happens with the GENERIC kernel, wit and without
SMP, with and without softupdates.
>Description:
When shutting down the system tries to sync its disk. It says:
"syncing disks" then 3 high numbers and then it repeats the 5
till ist says "giving up" at the end of the line. The 5 unsynced
blocks are:
1: dev:0000ff00, flags:01000034, blkno:48, blkno:48
2: dev:0000ff00, flags:01010034, blkno:2032, blkno:0
3: dev:0000ff00, flags:01020034, blkno:64, blkno:64
4: dev:0000ff00, flags:01010034, blkno:16, blkno:16
5: dev:0000ff00, flags:01010034, blkno:2016, blkno:2016
They are allways this 5 block (few times only 4 or 3 of them).
The disk look ok, a lowlevel formating didn't change anything.
The problem appeared first in 3.0-current in january but went
away end of january. Now I did an update to 3.1-RELEASE and it's
back.
>How-To-Repeat:
It happens on every shutdown.
>Fix:
I don't know.
>Release-Note:
>Audit-Trail:
>Unformatted:
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-bugs" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199902182226.XAA05306>