Subject: Re: how to crash a diskless client (i386)
To: Manuel Bouyer <bouyer@antioche.lip6.fr>
From: None <ks@ub.uni-mainz.de>
List: current-users
Date: 05/10/1999 16:43:52
hi,
>
> Interesting ! Could you send me you config file ?
yup! no problem. here we go:
# $NetBSD: GENERIC,v 1.231 1999/03/29 21:51:25 perry Exp $
#
# GENERIC -- everything that's currently supported
#
include "arch/i386/conf/std.i386"
maxusers 32 # estimated number of users
# CPU support. At least one is REQUIRED.
options I486_CPU
options I586_CPU
# NO CPU-related options.
# Misc. i386-specific options
options XSERVER # X server support in console drivers
# Standard system options
#options UCONSOLE # users can use TIOCCONS (for xconsole)
options INSECURE # disable kernel security levels
options RTC_OFFSET=0 # hardware clock is this many mins. west of GMT
#options NTP # NTP phase/frequency locked loop
options KTRACE # system call tracing via ktrace(1)
options SYSVMSG # System V-like message queues
options SYSVSEM # System V-like semaphores
options SYSVSHM # System V-like memory sharing
#options SHMMAXPGS=1024 # 1024 pages is the default
#options LKM # loadable kernel modules
# Diagnostic/debugging support options
#options DIAGNOSTIC # cheap kernel consistency checks
#options DEBUG # expensive debugging checks/support
#options KMEMSTATS # kernel memory statistics (vmstat -m)
options DDB # in-kernel debugger
#options DDB_HISTORY_SIZE=100 # enable history editing in DDB
#options KGDB # remote debugger
#options "KGDB_DEVNAME=\"com\"",KGDBADDR=0x3f8,KGDBRATE=9600
#makeoptions DEBUG="-g" # compile full symbol table
# Compatibility options
options COMPAT_NOMID # compatibility with 386BSD, BSDI, NetBSD 0.8,
options COMPAT_09 # NetBSD 0.9,
options COMPAT_10 # NetBSD 1.0,
options COMPAT_11 # NetBSD 1.1,
options COMPAT_12 # NetBSD 1.2,
options COMPAT_13 # NetBSD 1.3,
options COMPAT_43 # and 4.3BSD
options COMPAT_386BSD_MBRPART # recognize old partition ID
#options COMPAT_SVR4 # binary compatibility with SVR4
#options COMPAT_IBCS2 # binary compatibility with SCO and ISC
#options COMPAT_LINUX # binary compatibility with Linux
#options COMPAT_FREEBSD # binary compatibility with FreeBSD
# Executable format options
#options EXEC_ELF32 # 32-bit ELF executables (SVR4, Linux)
# File systems
file-system FFS # UFS
#file-system EXT2FS # second extended file system (linux)
#file-system LFS # log-structured file system
file-system MFS # memory file system
file-system NFS # Network File System client
#file-system CD9660 # ISO 9660 + Rock Ridge file system
#file-system MSDOSFS # MS-DOS file system
#file-system FDESC # /dev/fd
#file-system KERNFS # /kern
#file-system NULLFS # loopback file system
#file-system PORTAL # portal filesystem (still experimental)
#file-system PROCFS # /proc
#file-system UMAPFS # NULLFS + uid and gid remapping
#file-system UNION # union file system
#file-system CODA # Coda File System; also needs vcoda (below)
# NO File system options
# Networking options
options INET # IP + ICMP + TCP + UDP
options NFS_BOOT_BOOTPARAM
# NO wscons options
# Kernel root file system and dump configuration.
config netbsd root on ? type ?
#config netbsd root on sd0a type ffs
#config netbsd root on ? type nfs
#
# Device configuration
#
mainbus0 at root
# Basic Bus Support
# NO PCI bus support
# NO EISA bus support
# ISA bus support
isa* at mainbus?
# NO PCMCIA bus support
# Coprocessor Support
# Math Coprocessor support
npx0 at isa? port 0xf0 irq 13 # x86 math coprocessor
# Console Devices
# ISA console. You can only configure one of these!
#pc0 at isa? port 0x60 irq 1 # pccons generic PC console driver
vt0 at isa? port 0x60 irq 1 # PCVT console driver
# NO wscons
# NO Serial Devices
# NO Parallel Printer Interfaces
# NO SCSI Controllers and Devices
# IDE and related devices
# NO PCI IDE controllers - see pciide(4) for supported hardware.
# NO ISA Plug-and-Play IDE controllers
# NO PCMCIA IDE controllers
# ISA ST506, ESDI, and IDE controllers
wdc0 at isa? port 0x1f0 irq 14
# IDE drives
# Flags are used only with controllers that support DMA operations
# and mode settings (e.g. some pciide controllers)
# The lowest order four bits (rightmost digit) of the flags define the PIO
# mode to use, the next set of four bits the DMA mode and the third set the
# UltraDMA mode. For each set of four bits, the 3 lower bits define the mode
# to use, and the last bit must be 1 for this setting to be used.
# For DMA and UDMA, 0xf (1111) means 'disable'.
# 0x0fac means 'use PIO mode 4, DMA mode 2, disable UltraDMA'.
# (0xc=1100, 0xa=1010, 0xf=1111)
# 0x0000 means "use whatever the drive claims to support".
wd* at wdc? channel ? drive ? flags 0x0000
# NO ATAPI bus support
# NO ATAPI devices
# NO Miscellaneous mass storage devices
# Network Interfaces
# NO PCI network interfaces
# NO EISA network interfaces
# NO ISA Plug-and-Play network interfaces
# NO PCMCIA network interfaces
# ISA network interfaces
ep0 at isa? port ? irq ? # 3C509 ethernet cards
# NO MII/PHY support
# NO USB Controller and Devices
# NO Audio Devices
# NO Mice
# NO Joysticks
# NO Miscellaneous Devices
# Pull in optional local configuration
include "arch/i386/conf/GENERIC.local"
# Pseudo-Devices
# NO disk/mass storage pseudo-devices
# network pseudo-devices
pseudo-device bpfilter 8 # Berkeley packet filter
pseudo-device loop # network loopback
# miscellaneous pseudo-devices
pseudo-device pty 16 # pseudo-terminals
# rnd works; RND_COM does not on port i386 yet.
pseudo-device rnd # /dev/random and in-kernel generator
> I'll try to get the line in the code corresponding to
> _wdc_ata_bio_intr+0x372
> Is this with 1.4_ALPHA, BETA, or 1.4 ?
this is what was suppable last friday or so as current, 1.4 now, I think.
a freshly compiled kernel from sources supped this morning does the same.
and the snapshot kernel from the install floppies from April 21. failed
this way, too.
if you need any further information or testing or... just ask!
-ks