From owner-freebsd-hackers@FreeBSD.ORG Fri Jan 7 22:26:09 2011 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D7B79106566B for ; Fri, 7 Jan 2011 22:26:09 +0000 (UTC) (envelope-from yanegomi@gmail.com) Received: from mail-wy0-f182.google.com (mail-wy0-f182.google.com [74.125.82.182]) by mx1.freebsd.org (Postfix) with ESMTP id 677608FC12 for ; Fri, 7 Jan 2011 22:26:09 +0000 (UTC) Received: by wyf19 with SMTP id 19so18044005wyf.13 for ; Fri, 07 Jan 2011 14:26:08 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:sender:received :in-reply-to:references:date:x-google-sender-auth:message-id:subject :from:to:cc:content-type:content-transfer-encoding; bh=uRpdI3ND37JgvGXqrB1G1+2HGZ85S0biAMdSW5dM6s8=; b=aLQrHAWfZHG0TuC8NvX56K0FPVE/eNt+iBrT7CA1h1h/e899k2dBZueoX/KoHFwYxr WrilI29FTIGLX0zMZcz3c3BW/AHicjc+VJBqvYm6vgmDo0tT4njBFix7B20xjYEYtsSg SPUxxcnMGRdyetMpjFXon0nAfcTZvzJJ13BNA= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type :content-transfer-encoding; b=oRZNU3J8TBIwahpla8/cwKMoO3WaWZPwgXUw8HX2CD1kVYst0rVIMG0AYjxls1kkHm k/uvWzWYC2ElGwQuotpZAf7NX+SiNpbOxcQtsDdlJKX9sh99vZ5WKw5CfenNCbjBZ7Z7 kOua5+q8ZMBuOOG3P1jExHEG5pIH4J0d4PTFw= MIME-Version: 1.0 Received: by 10.227.134.142 with SMTP id j14mr16459817wbt.53.1294439168471; Fri, 07 Jan 2011 14:26:08 -0800 (PST) Sender: yanegomi@gmail.com Received: by 10.216.254.226 with HTTP; Fri, 7 Jan 2011 14:26:08 -0800 (PST) In-Reply-To: References: Date: Fri, 7 Jan 2011 14:26:08 -0800 X-Google-Sender-Auth: O7OZmMFJFejs7sZifNkT9Xzkq8g Message-ID: From: Garrett Cooper To: Mark Saad Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: freebsd-hackers@freebsd.org Subject: Re: With out ddb and kdb set 7.3-RELEASE amd64 does not boot. 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: Fri, 07 Jan 2011 22:26:10 -0000 On Fri, Jan 7, 2011 at 2:22 PM, Mark Saad wrote: > On Fri, Jan 7, 2011 at 4:56 PM, Garrett Cooper wrot= e: >> On Fri, Jan 7, 2011 at 1:20 PM, Mark Saad wrote= : >>> Hello hackers@, >>> =A0I have a good question that I cant find an answer for. I believe >>> found a kernel bug in 7.3-RELEASE that prevents me from booting 64-bit >>> kernels on HP's DL360 G4p . The kernel dies with "Fatal trap 12: page >>> fault while in kernel mode " . The hardware works fine in 7.2-RELEASE >>> amd64, 7.1-RELEASE amd64, and 6.4-RELEASE amd64 . >>> >>> In 7.3-RELEASE amd64 I can not boot from cd or pxe correctly using the >>> stock 7.3-RELEASE amd64 kernel however i386 works fine. To see if this >>> issue was some how fixed in 7.3-RELEASE-p4 amd64 I rebuilt a GENERIC >>> kernel using patches sources and tried to boot and I got the same >>> crash. >>> >>> =A0Next I rebuilt the kernel with KDB and DDB to see if I could get a >>> core-dump of the system. I also set loader.conf to >>> >>> kernel=3D"kernel.DEBUG" >>> kern.dumpdev=3D"/dev/da0s1b" >>> >>> Next I pxebooted =A0the box and the system does not crash on boot up, i= t >>> will easily load a nfs root and work fine. So I copied my debug >>> kernel, and loader.conf to the local disk and rebooted and it boots >>> fine from the local disk . >>> >>> Rebooting the server and running off the local disks and debug kernel, >>> I cant find any issues. >>> >>> Reboot the box into a GENERIC 7.3-RELEASE-p4 kernel and it crashes >>> >>> With this error >>> >>> Fatal trap 12: page fault while in kernel mode >>> cpuid =3D 0; apic id =3D 00 >>> fault virtual address =A0 =3D 0x0 >>> fault code =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =3D supervisor write data, p= age not present >>> instruction pointer =A0 =A0 =3D 0x8:0xffffffff800070fa >>> stack pointer =A0 =A0 =A0 =A0 =A0 =A0=3D 0x10:0xffffffff8153cbe0 >>> frame pointer =A0 =A0 =A0 =A0 =A0 =A0=3D 0x10:0xffffffff8153cc50 >>> code segment =A0 =A0 =A0 =A0 =A0=3D base 0x0, limit 0xfffff, type 0x1b >>> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0=3D DPL 0, p= res 1, long 1, def32 0, gran 1 >>> processor eflags =A0 =A0 =A0=3D interrupt enabled, resume, IOPL =3D 0 >>> current process =A0 =A0 =A0 =3D 0 (swapper) >>> [thread pid 0 tid 100000 ] >>> Stopped at =A0 =A0 =A0bzero+0xa: =A0 =A0 repe stosq =A0 =A0 =A0 %es:(%r= di) >>> >>> >>> What do I do , has anyone else seen anything like this ? >> >> =A0 =A0What are the messages before that on the kernel console and what >> are your drivers loaded on a stable system? >> Thanks, >> -Garrett >> > Garrett > =A0The last 4 lines of the verbose boot up of the generic kernel are > all from sio1 Is sio1 pointing to a generic UART, or is it something more special like the HP lights-out SOL interface? Simple test might be to disable the sio/uart driver in the kernel and see if things worked. Thanks, -Garrett