From owner-freebsd-hackers@FreeBSD.ORG Sun Feb 25 16:15:23 2007 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 8F69416A402; Sun, 25 Feb 2007 16:15:23 +0000 (UTC) (envelope-from joe@netmusician.org) Received: from netmusician.org (netmusician.org [216.9.132.179]) by mx1.freebsd.org (Postfix) with ESMTP id 4A26713C481; Sun, 25 Feb 2007 16:15:23 +0000 (UTC) (envelope-from joe@netmusician.org) Received: from localhost (localhost [127.0.0.1]) by netmusician.org (Postfix) with ESMTP id 887467E8DC; Sun, 25 Feb 2007 11:15:25 -0500 (EST) X-Virus-Scanned: by amavisd-new at netmusician.org Received: from netmusician.org ([127.0.0.1]) by localhost (netmusician.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id YBdrneUAtLMT; Sun, 25 Feb 2007 11:15:24 -0500 (EST) Received: from [192.168.0.2] (74-130-30-11.dhcp.insightbb.com [74.130.30.11]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by netmusician.org (Postfix) with ESMTP id 84F8D7E8C3; Sun, 25 Feb 2007 11:15:24 -0500 (EST) In-Reply-To: <200702251146.08150.Danovitsch@vitsch.net> References: <6B2A41DC-79FA-42A1-B1BC-BB9F0A74B765@netmusician.org> <200702251146.08150.Danovitsch@vitsch.net> Mime-Version: 1.0 (Apple Message framework v752.2) Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: <228AFDCF-D9C1-43F1-ACBE-719595B10FEE@netmusician.org> Content-Transfer-Encoding: 7bit From: Joe Auty Date: Sun, 25 Feb 2007 11:14:55 -0500 To: Daan Vreeken [PA4DAN] X-Pgp-Agent: GPGMail 1.1.2 (Tiger) X-Gpgmail-State: signed X-Mailer: Apple Mail (2.752.2) Cc: Kip Macy , freebsd-questions@freebsd.org, freebsd-hackers@freebsd.org Subject: Re: kernel panic at boot on any 6.x OS X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 25 Feb 2007 16:15:23 -0000 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Feb 25, 2007, at 5:46 AM, Daan Vreeken [PA4DAN] wrote: > On Sunday 25 February 2007 08:59, Kip Macy wrote: >> It looks as if you've hit a device driver that is trying to print out >> a null string. The message you've given doesn't provide any more >> information than that. If you install a snapshot kernel it will >> probably have ddb compiled in which will allow you to at least get a >> backtrace. I'm sorry you're having trouble. > > Grepping the source tree on 6.2-RELEASE shows this message can only > have com > from one place : sys/kern/kern_conf.c in the function prep_cdevsw() : > > if (devsw->d_version != D_VERSION_01) { > printf( > "WARNING: Device driver \"%s\" has wrong > version %s\n", > devsw->d_name == NULL ? "???" : devsw->d_name, > "and is disabled. Recompile KLD module."); > > Looks like the kernel and the modules are out of sync. > Any idea how this could have happened after disabling everything in my /etc/loader.conf, and simply running a: make buildworld make buildkernel KERNCONF=myconfig make installkernel KERNCONF=myconfig Shouldn't this have installed a fresh kernel plus only essential modules? Here is a diff of my kernel config (which I've called, rather uncreatively, 6.x) against GENERIC: nothing unusual, just IPFIREWALL and Linux compat stuff, right? # diff 6.x GENERIC 19c19 < # $FreeBSD: src/sys/i386/conf/GENERIC,v 1.429.2.7.2.2 2006/05/01 00:15:12 scottl Exp $ - --- > # $FreeBSD: src/sys/i386/conf/GENERIC,v 1.429.2.13 2006/10/09 18:41:36 simon Exp $ 30,42c30 < options IPFIREWALL < options IPFIREWALL_VERBOSE < options IPFIREWALL_VERBOSE_LIMIT=10 < options IPFIREWALL_DEFAULT_TO_ACCEPT < options IPDIVERT < #options VFS_AIO < #options HZ=1200 < #options SMP # Symmetric MultiProcessor Kernel < #device pf < #device pflog < #device pfsync < options COMPAT_LINUX < options BRIDGE - --- > makeoptions DEBUG=-g # Build kernel with gdb(1) debug symbols 44,49d31 < # Enable the linux-like proc filesystem support (requires COMPAT_LINUX and PSEUDOFS) < options LINPROCFS < < #makeoptions DEBUG=-g # Build kernel with gdb(1) debug symbols < < #options SCHED_ULE # ULE scheduler 77,80d58 < 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. 103a82,83 > options AHC_REG_PRETTY_PRINT # Print register bitfields in debug > # output. Adds ~128k to driver. 104a85,86 > options AHD_REG_PRETTY_PRINT # Print register bitfields in debug > # output. Adds ~215k to driver. 226a209 > device stge # Sundance/Tamarack TC9021 gigabit Ethernet 248a232,234 > device wlan_wep # 802.11 WEP support > device wlan_ccmp # 802.11 CCMP support > device wlan_tkip # 802.11 TKIP support 249a236,238 > device ath # Atheros pci/cardbus NIC's > device ath_hal # Atheros HAL (Hardware Access Layer) > device ath_rate_sample # SampleRate tx rate control for ath > >> On 2/24/07, Joe Auty wrote: >>> Hello, >>> >>> (sorry, don't know whether kernel problems should go to questions or >>> hackers, or both).. >>> >>> This has been a long-standing problem of mine, but I always ignored >>> it hoping it would go away on its own with a future 6.x release, but >>> it remains... >>> >>> No matter whether I boot into safe mode or regular mode, with all >>> kernel extensions disabled in /boot/loader.conf, I get the following >>> panic late at boot of a fresh RELENG_6_2 kernel (with only a few >>> services left to bring up). The 6.x kernels I've tried all build and >>> installed cleanly without any errors... >>> >>>> WARNING: Device driver " >>>> >>>> Fatal trap 12: page fault while in kernel mode >>>> fault virtual address = 0x400000 >>>> fault code = supervisor read, page not present >>>> instruction pointer = 0x20:0xc06d4614 >>>> stack pointer = 0x28:0xf015491c >>>> frame pointer = 0x28:0xf015491c >>>> code segment = base 0x0, limit 0xffffff, type 0x1b >>>> = DPL 0, pres 1, def32 1, gran 1 >>>> processor eflags = interupt enabled, resume, IOPL = 0 >>>> current process = 898 (kldload) >>>> trap number = 12 >>>> panic: page fault >>>> uptime: 36s >>>> cannot dump. No dump device defined >>>> automatic reboot in 15 seconds >>> >>> This problem does not occur within any 5.x OS for me. I would >>> certainly like to resolve this issue now, but this sort of debugging >>> is over my head beyond running fsck (which I've tried). Any ideas >>> here? >>> >>> Thanks in advance for your help! >>> >>> >>> >>> >>> >>> ----------- >>> Joe Auty >>> NetMusician: web publishing software for musicians >>> http://www.netmusician.org >>> joe@netmusician.org >> >> _______________________________________________ >> freebsd-hackers@freebsd.org mailing list >> http://lists.freebsd.org/mailman/listinfo/freebsd-hackers >> To unsubscribe, send any mail to "freebsd-hackers- >> unsubscribe@freebsd.org" > > -- > Daan > _______________________________________________ > freebsd-hackers@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-hackers > To unsubscribe, send any mail to "freebsd-hackers- > unsubscribe@freebsd.org" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (Darwin) iD8DBQFF4bX/CgdfeCwsL5ERAiKCAJwKUt52wgB1mtqFSYUr8eFV39lpwgCglL4R t+fcWGuCYkjn6lylcrrZeEM= =bca6 -----END PGP SIGNATURE-----