ACPI causes page fault/panic upon reboot
Dan Hulme
d at diefree.com
Thu Jan 1 12:28:48 PST 2004
Pete, I'm sending this again with a little more info.
> Can you provide a verbose dmesg, `boot -Dhv'? How many instances of
> Windows did you change? If there's more than one, you might want to
> try changing one at a time.
>
When I get the chance, I will. There were only two instances of
windows, and both were in the same block. The second one was a test for
windows ME, and was nested inside the else of the previous test. In
other words, if the first test succeeded, the second test never would
occur. I suppose I could make it try to match the "Windows ME" block
instead, but somehow I doubt that will work, either.
I can't exactly capture the dmesg, because it doesn't boot far enough
for it to get recorded. I will type in the last bit for you:
Timecoutner "ACPI-fast" frequency 3579545 Hz quality 1000
acpi-timer0: <24-bit timer at 3.5795454Mhz> port 0x1008-0x100b on acpi0
acpi_cpu0: <CPU> on acpi0
Device configuration finished
procfs registered
Timecounter "TSC" frequency 664649328 Hz quality 800
Timecounters tick every 10.000 msec
lo0: bpf attached
Mounting root from ufs:/dev/ad0s1a
setrootbyname failed
ffs_mountroot: can't find rootvp
Root mount failed: 6
Then it asks for me to manually specify the root. Of course, that is
the right root slice, so there's nothing I can do.
-Dan
>> acpi.asl 123: If (S3EN)
>> Error 1037 - ^ syntax error
>>
>> Here are the surrounding lines. To be honest, I really don't see what
>> could be causing a syntax error.
>>
>> 118 Name (_S0, Package (0x02)
>> 119 {
>> 120 0x00,
>> 121 0x00
>> 122 })
>
> ^
> It looks like you've got an extra closing paren at the end of line 122.
>
That's what I thought initially, until I looked at the rest of the file,
and saw that *all* the Name clauses end like that, including two others
that I quoted already:
>> 123 If (S3EN)
>> 124 {
>> 125 Name (_S3, Package (0x02)
>> 126 {
>> 127 0x05,
>> 128 0x05
>> 129 })
>> 130 }
>> 131 Else
>> 132 {
>> 133 Name (_S1, Package (0x02)
>> 134 {
>> 135 0x01,
>> 136 0x01
>> 137 })
>> 138 }
>>
-Dan
More information about the freebsd-current
mailing list