Date: Sat, 17 Oct 1998 23:19:53 -0500 From: Tom Jackson <toj@gorilla.net> To: Peter Wemm <peter@netplex.com.au> Cc: Karl Pielorz <kpielorz@tdx.co.uk>, Chuck Robey <chuckr@mat.net>, freebsd-current@FreeBSD.ORG Subject: Re: panic Message-ID: <19981017231953.A1263@TOJ.org> In-Reply-To: <199810180239.KAA16030@spinner.netplex.com.au>; from Peter Wemm on Sun, Oct 18, 1998 at 10:39:13AM %2B0800 References: <19981017202305.A12163@TOJ.org> <199810180239.KAA16030@spinner.netplex.com.au>
next in thread | previous in thread | raw e-mail | index | archive | help
--J2SCkAp4GZ/dPZZf Content-Type: text/plain; charset=us-ascii On Sun, Oct 18, 1998 at 10:39:13AM +0800, Peter Wemm wrote: > Tom Jackson wrote: > > nm tells me module_register (dugh) not module_init. > > > > For me, no amount of dumps on anything will produce a crash dump. On my > > laptop it just says bad dump device and on my server (which is not crashing > > now) I get a count down but no crash modules are produced. > > > > btw, these are 100% elf and I don't think the panic is a smp problem. > > > > Maybe Peter will know what the problem is. > > I can guess, but I need more information. Can you mail me your kernel > config file[s] that are breaking? > > My gut reaction is that the sysinit table is getting corrupted, or that > something is calling module_register too soon. module_init() initializes > a couple of tailq's, and all sorts of things go wrong if something tries > to add to these lists before then. > > As a long shot, can you add #define DIAGNOSTIC to the start of > kern/kern_malloc.c and see if the fault address changes to something > along the lines of 0xdeadc0de. ip is still 0xf01205ac, that is, no change > > How far does it get into the boot sequence before crashing? What are the > last few messages? It is possible that some filesystem initialization that > you are using that I didn't test with is causing this. various probes ... pcic: controller irq 3 Initializing pc-card drivers: ed sio Fatal Trap 12 ... when I hit any key at the db>, Card inserted, slot 1, appears at the prompt. In a normal boot sequence, changing root device to wd0s1a, normally appears between the Initializing... and the Card inserted... To reiterate, this problem only shows up on my old Thinkpad. No problem on the smp server. Let me know if there's anything else I can do. > > > On Sun, Oct 18, 1998 at 12:15:22AM +0100, Karl Pielorz wrote: > > > > > > Tom Jackson wrote: > > > > > > > [snip] > > > > > > > > I'm getting this crash, not on elf(kernel+exec)/smp/scsi but on a old > > > > Thinkpad with a pccard ed0, a elf(kernel+exec)/up/ide. Thought since the > > > > reference to modules that pcvt instead of sc0 might work - no such luck. > > > > I get the panic right after the pcic is probed and before the pccard is > > > > initialized. > > > > > > > > I'm not getting any crash dumps on any of my elf systems. > > > > > > Hi, > > > > > > I've been talking to Chuck about this - if the panic is similar / the same > as > > > his, you won't get a crashdump - as it's happening too soon into the boot > > > process... > > > > > > The only thing I could think of was to have a line similar to: > > > > > > config kernel root on XXX dumps on YYYY > > > > > > In the kernel config - Though LINT warns against this, it might be the only > > > way of telling the system where to dump to - as it's panics so soon during > > > boot... > > > > > > I'm hoping someone who knows more what there talking about will step in wit > h > > > "That's a good/bad idea" - and why... > > > > > > I seem to remember using the kernel config to specify the dump device, but > > > that was from ages ago (2.2.2? :-) > > > > > > Regards, > > > > > > Karl > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > > with "unsubscribe freebsd-current" in the body of the message > > > > > > > -- > > Tom > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-current" in the body of the message > > > > Cheers, > -Peter > -- > Peter Wemm <peter@netplex.com.au> Netplex Consulting > "No coffee, No workee!" :-) > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > -- Tom --J2SCkAp4GZ/dPZZf Content-Type: text/plain; charset=us-ascii Content-Description: kernel config Content-Disposition: attachment; filename=SLIM # # PCCARD -- GENERIC laptop support # # For more information read the handbook part System Administration -> # Configuring the FreeBSD Kernel -> The Configuration File. # The handbook is available in /usr/share/doc/handbook or online as # latest version from the FreeBSD World Wide Web server # <URL:http://www.FreeBSD.ORG/>; # # An exhaustive list of options and more detailed explanations of the # device lines is present in the ./LINT configuration file. If you are # in doubt as to the purpose or necessity of a line, check first in LINT. # # $Id: PCCARD,v 1.2 1997/11/11 00:47:01 nate Exp $ machine "i386" cpu "I386_CPU" cpu "I486_CPU" #cpu "I586_CPU" #cpu "I686_CPU" ident SLIM maxusers 10 options GPL_MATH_EMULATE #Support for x87 GPL emulation #options MATH_EMULATE # x87 emulation options INET #InterNETworking options FFS #Berkeley Fast Filesystem options NFS #Network Filesystem options MSDOSFS #MSDOS Filesystem #options "CD9660" #ISO 9660 Filesystem options PROCFS #Process filesystem #options DEVFS #options SLICE options "COMPAT_43" #Compatible with BSD 4.3 [KEEP THIS!] #options SCSI_DELAY=15 #Be pessimistic about Joe SCSI device options UCONSOLE #Allow users to grab the console options FAILSAFE #Be conservative options USERCONFIG #boot -c editor options VISUAL_USERCONFIG #visual boot -c editor options "NO_F00F_HACK" # strings -aout /kernel | grep ^___ | sed -e 's/^___//' > MYKERNEL options INCLUDE_CONFIG_FILE # include this file in kernel #options "VM86" #options VESA options DDB config kernel root on wd0 controller isa0 #controller pci0 controller fdc0 at isa? port "IO_FD1" bio irq 6 drq 2 vector fdintr disk fd0 at fdc0 drive 0 #options "CMD640" # work around CMD640 chip deficiency controller wdc0 at isa? port "IO_WD1" bio irq 14 vector wdintr disk wd0 at wdc0 drive 0 #controller wdc1 at isa? port "IO_WD2" bio irq 15 vector wdintr #options ATAPI #Enable ATAPI support for IDE bus #options ATAPI_STATIC #Don't do it as an LKM #device wcd0 #IDE CD-ROM #controller aic0 at isa? port 0x340 bio irq 11 vector aicintr #controller scbus0 #device sd0 #device od0 #See LINT for possible `od' options. #device st0 #device cd0 #Only need one of these, the code dynamically grows # syscons is the default console driver, resembling an SCO console #device sc0 at isa? port "IO_KBD" tty irq 1 flags 0x10 vector scintr # Enable this and PCVT_FREEBSD for pcvt vt220 compatible console driver device vt0 at isa? port "IO_KBD" conflicts tty irq 1 vector pcrint options XSERVER # support for X server #options FAT_CURSOR # start with block cursor # If you have a ThinkPAD, uncomment this along with the rest of the PCVT lines options PCVT_SCANSET=2 # IBM keyboards are non-std device npx0 at isa? port "IO_NPX" irq 13 vector npxintr # # Laptop support (see LINT for more options) # device apm0 at isa? flags 0x31 # Advanced Power Management # PCCARD (PCMCIA) support controller card0 device pcic0 at card? device pcic1 at card? device sio0 at isa? port "IO_COM1" flags 0x10 tty irq 4 vector siointr #device sio1 at isa? port "IO_COM2" tty irq 3 vector siointr #device sio2 at isa? disable port "IO_COM3" tty irq 5 vector siointr #device sio3 at isa? disable port "IO_COM4" tty irq 9 vector siointr device lpt0 at isa? port? tty irq 7 vector lptintr device psm0 at isa? port "IO_KBD" conflicts tty irq 12 vector psmintr options PSM_HOOKAPM #hook the APM resume event options PSM_RESETAFTERSUSPEND #reset the device at the resume event device ed0 at isa? port 0x280 net irq 10 iomem 0xd8000 vector edintr #device ep0 at isa? port 0x300 net irq 10 vector epintr #device fe0 at isa? port 0x300 net irq ? vector feintr pseudo-device loop pseudo-device ether #pseudo-device sl 1 # iijppp uses tun instead of ppp device #pseudo-device ppp 1 pseudo-device tun 1 pseudo-device pty 16 pseudo-device gzip # Exec gzipped a.out's # KTRACE enables the system-call tracing facility ktrace(2). # This adds 4 KB bloat to your kernel, and slightly increases # the costs of each syscall. options KTRACE #kernel tracing # This provides support for System V shared memory. # options SYSVSHM #options SYSVSEM #options SYSVMSG --J2SCkAp4GZ/dPZZf-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?19981017231953.A1263>