RE: Today's -CURRENT -- SMP OK; UP panics
Welp, wish me luck as well. I haven't had a -current system that booted in about a
week. I noticed that there've been changes to the acpi stuff in my cvsup this morning,
so I'm hoping maybe the fix is in there.
-Original Message-
From: David Wolfskill [mailto:[EMAIL PROTECTED]]
Sent: Wed 7/31/2002 4:11 PM
To: [EMAIL PROTECTED]
Cc:
Subject: Re: Today's -CURRENT -- SMP OK; UP panics
>Date: Wed, 31 Jul 2002 11:58:04 -0700 (PDT)
>From: David Wolfskill <[EMAIL PROTECTED]>
>[Re: panic during probes at boot time for today's -CURRENT]
Well, absent any better ideas, I rebooted the laptop, but into
single-user mode. It came up just fine, so I did the "fsck -p"; no
problem.
So I rebooted again (multi-user mode); it's up & running as I type --
I'm logged in, running X, and:
g1-9(5.0-C)[1] uname -a
FreeBSD g1-9.catwhisker.org 5.0-CURRENT FreeBSD 5.0-CURRENT #7: Wed Jul 31
10:45:23 PDT 2002 [EMAIL PROTECTED]:/common/S3/obj/usr/src/sys/LAPTOP_30W
i386
g1-9(5.0-C)[2]
Weird.
Cheers,
david (links to my resume at http://www.catwhisker.org/~david)
--
David H. Wolfskill [EMAIL PROTECTED]
To paraphrase David Hilbert, there can be no conflicts between Microsoft
and the discipline of systems administration, since they have nothing in
common.
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
N
'²æìr¸zǧvf¢Ú&j:+v¨· è® "¶§²æìr¸yúÞy» rêëz{bØ^nr¡ûazg¬±¨
Unable to boot -current for last week
All,
Starting about a week ago, -current started refusing to boot on my TOS 5005-S504.
Depending on the config I use, it hard locks at boot in one of two places: either when
loading the fxp driver, or when probing the pci bus. And I do mean hard. I can't break
to debug, nothing. A power cycle is the only option. Since this is a legacy free
laptop, I'm not able to attach a console, so I'm pretty much hunting in the dark. I am
however, still able to boot the GENERIC from DP1. I was also wondering if anyone had
bothered to create an absolute minimal kernel config, and if so, would you send it to
me to try? Then I can start adding back to see where it breaks.
At any rate, the last cvs code that booted on this box was from around July 24th.
Thanks,
Rob
èR{.nÇ+·¬zwfj)m¢f£¢·hkyàRàÂ+aº{.nÇ+·ç±×.®·§¶)í
æèw* ¶¦zË
ACPI Errors
Reposted because I screwed up the first time and sent it to the wrong list System: TOS 5005-S504 Error with any kernel build: Using $PIR table, 0 entries at 0xc00f0190 ACPI-0171: *** Error: AcpiLoadTables: RSDP Failed validation: AE_BAD_SIGNATURE ACPI-0213: *** Error: AcpiLoadTables: Could not load tables: AE_BAD_SIGNATURE ACPI: Table load failed: AE_BAD_SIGNATURE Shortly after that, I get a hard lock at at either the load of the fxp driver, or when probing the pci bus. Same thing happens if I do an unset acpi_load or if I try boot -s, or both. Ideas? ¡Iì¹» ®&Þ±éݨ¥¶Ý¢jçH:+éì¹» ®&Þ~·nÇ\ººÞا¶¡Ü¨~Ø^ë,j
RE: ACPI errors
-Original Message-
From: Mitsuru IWASAKI [mailto:[EMAIL PROTECTED]]
Sent: Sun 8/4/2002 8:59 AM
To: Robert D Hughes
Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED]
Subject: Re: ACPI errors
[move to -current because STABLE don't have acpica support yet]
I reposted it over there, so let's move the conversation there.
Hi,
> System: TOS 5005-S504
> Error with any kernel build:
> Using $PIR table, 0 entries at 0xc00f0190
> ACPI-0171: *** Error: AcpiLoadTables: RSDP Failed validation:
AE_BAD_SIGNATURE
> ACPI-0213: *** Error: AcpiLoadTables: Could not load tables:
AE_BAD_SIGNATURE
> ACPI: Table load failed: AE_BAD_SIGNATURE
It seems that this problem happens after sys/i386/i386/pmap.c rev
1.352 changes. Could you replace pmap.c with 1.351 ?
How would I pull a specific version from cvs?
Peter, do you have any ideas with this ?
> Same thing happens if I do an unset acpi_load or if I try boot -s, or both.
I think your kernel config file includes 'device acpica'.
Nope. It's auto-loading as a module, as per NOTES.
Thanks,
Rob
èR{.nÇ+·¬zwfj)m¢f£¢·hkyàRàÂ+aº{.nÇ+·ç±×.®·§¶)í
æèw* ¶¦zË
