From owner-freebsd-current Sat Sep 14 21:10: 1 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9B27F37B400 for ; Sat, 14 Sep 2002 21:09:58 -0700 (PDT) Received: from tomts13-srv.bellnexxia.net (tomts13.bellnexxia.net [209.226.175.34]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8947343E6E for ; Sat, 14 Sep 2002 21:09:57 -0700 (PDT) (envelope-from matt@gsicomp.on.ca) Received: from xena.gsicomp.on.ca ([65.95.177.86]) by tomts13-srv.bellnexxia.net (InterMail vM.5.01.04.19 201-253-122-122-119-20020516) with ESMTP id <20020915040954.ELBG16602.tomts13-srv.bellnexxia.net@xena.gsicomp.on.ca> for ; Sun, 15 Sep 2002 00:09:54 -0400 Received: from hermes (hermes.gsicomp.on.ca [192.168.0.18]) by xena.gsicomp.on.ca (8.11.3/8.11.3) with SMTP id g8F2u5X95836 for ; Sat, 14 Sep 2002 22:56:06 -0400 (EDT) (envelope-from matt@gsicomp.on.ca) Message-ID: <021801c25c6d$c027f530$1200a8c0@gsicomp.on.ca> From: "Matthew Emmerton" To: Subject: Fw: Problem booting 5.0-DP1 on Thinkpad T23 Date: Sun, 15 Sep 2002 00:09:55 -0400 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4807.1700 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4910.0300 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG ----- Original Message ----- From: "Matthew Emmerton" To: Sent: Saturday, September 14, 2002 11:52 PM Subject: Problem booting 5.0-DP1 on Thinkpad T23 > > I'm trying to get some version of 5.0 installed on my IBM ThinkPad T23 so > that I can start testing ports on 5.x and work on some of phk's TODOs for > 5.0. > > I was initially running 4.6-REL on this machine without problems, and then > tried to upgrade to -CURRENT. This approach led to disaster, with > any -CURRENT kernel hanging immediately upon boot. I suspected some kind of > wierd 4.x/5.x interaction, so I wiped the system clean and installed > 5.0-DP1. > > The first time I booted I got a fatal trap; what I could retrieve from the > console buffer is reproduced below. > > ----------- start console output leading up to trap ------------------ > > acpi0: power button is handled as a fixed feature programming model. > ACPI timer looks GOOD min = 2, max = 3, width = 2 > [ repeated 9 times ] > Timecounter "ACPI-fast" frequency 3579545 Hz > ACPI-0413: *** Error: NsSearchAndEnter: Bad character in ACPI Name > [ repeated ~30 times ] > can't fetch resources for \_SB_.LNKB - AE_AML_OPERAND_TYPE > ACPI-0413: *** Error: NsSearchAndEnter: Bad character in ACPI Name > [ repeated ~10 times ] > can't fetch resources for \_SB.LNKC - AE_AML_UNINITIALIZED_LOCAL > ACPI-0413: *** Error: NsSearchAndEnter: Bad character in ACPI Name > [ repeated ~10 times ] > > Fatal trap 18: integer divide fault while in kernel mode > instruction pointer = 0x8:0xc0512287 > stack pointer = 0x10:0xc05609ac > frame pointer = 0x10:0xc05609ec > code segment = base 0x0, limit 0xffff, type 0x1b > = DPL 0, pres 1, def32 1, gran 1 > processor eflags = interrupt enabled, resume, IOPL = 0 > current process = 0 (swapper) > kernel: type 18 trap, code =0 > Stopped at AcpiExInsertIntoField+0x33: divl %ebx,%eax > > [ 'show registers' has %ebx 0, %eax 0xffffffff ] > > ----------- end console output leading up to trap ------------------ > > So, knowing that ACPI was somehow at fault, I decided to reboot and see what > was really being set in the loader. > > ACPI-related settings at bootup: > > acpi_load=YES > hint.acpi.0.oem=IBM XXXXX$ (where X are some !isalnum() ascii chars, like > \a, 0xf6, etc) > hint.acpi.0.revision=2 > hint.acpi.0.rsdt=0x1ff6fdc5 > hint.acpi.0.xsdt=0x000000001ff6fdf9 > hint.acpi.0.xsdt_length=36 > > I set acpi_load=NO and hint.acpi.0.oem=IBM (without the trailing garbage) > and booted. This time I got tonnes of the ACPI-0413 messages (like above), > but I actually saw device probes throughout the mess. Immediately after > probing vga0, the system rebooted itself. > > I know there's been a lot of ACPI work done since -DP1, but the only way I'm > able to get a newer kernel on this machine is via the convoluted method of > booting with the install disks, going to fixit mode, bringing up a network > connection and dragging over a kernel (and modules) from somewhere, and I > don't have any other machines that I want to "contaminate" with 5.0 kernel > sources. > > Does anyone have any tips to help me get over these ACPI problems? I was having trouble searching the archives earlier, but of course, I had no problems after I sent this email. I found that the right thing to do was set hint.acpi.0.disable="1" at boot-time and things are well now. I am going to try re-enabling ACPI once I cvsup, so who is the best person to contact about ACPI problems & fixes? Or should I send my observations (and patches) to -current? Sorry for the noise. -- Matt Emmerton To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message