Ok, message didn't send entire post history, this should be it.
Hopefully it's readable enough.
Hello, I purchased a new Clevo M860TU on the account that it ran linux
very well and was hoping it would fair the same on FreeBSD. Not so
much, little help? I posted this in mobile originally but though
stable would be a better choice. Don't know if it is more appropriate
here or ACPI.
I'm giving you as much information as I know how to get. as I cannot
get sysinstall to load I am having to type all these dmesg. The boot
process is hanging. This is all with 7.x, I can give 6.x if needed.
Hardware:
Intel P9500
4gb DDR3-1066
Nvidia 9800M GT
Atheros AR5006e
FreeBSD 7.1-BETA2
These snippets of dmesg happen around the end where it hangs.
1. Default
...
cpu0: <ACPI CPU> on acpi0
ACPI Error (dsopcode-0350): No pointer back to NS node in buffer obj
0xc6a02d40 [20070320]
ACPI Exception (dswexec-0556): AE_AML_INTERNAL, While resolving
operands for [OpcodeName unavailable] [20070320]
ACPI Error (psparse-0626): Method parse/execution failed
[\_PR_.CPU0._OSC] (Node 0xc68556e0), AE_AML_INTERNAL
est0: <Enhanced SpeedStep Frequency Control> on cpu0
p4tcc0: <CPU Frequency Thermal Control> on cpu0
cpu1: <ACPI CPU> on acpi0
ACPI Error (dsopcode-0350): No pointer back to NS node in buffer obj
0xc6a0e300 [20070320]
ACPI Exception (dswexec-0556): AE_AML_INTERNAL, While resolving
operands for [OpcodeName unavailable] [20070320]
ACPI Error (psparse-0626): Method parse/execution failed
[\_PR_.CPU1._OSC] (Node 0xc685560), AE_AML_INTERNAL
est1: <Enhanced SpeedStep Frequency Control> on cpu1
p4tcc1: <CPU Frequency Thermal Control> on cpu1
...
cpu0: Cx states changed
cpu1: Cx states changed
unknown: timeout waiting for read DRQ
unknown: timeout waiting for read DRQ
acd0: DVDR <Optiarc DVD RW AD-7560S/SX01> at ata3-master UDMA33
GEOM_LABEL: Label for provider acd0 is iso9660/FreeBSD_Install
run_interrupt_driven_hooks: still waiting after 60 seconds for xpt_config
run_interrupt_driven_hooks: still waiting after 120 seconds for xpt_config
run_interrupt_driven_hooks: still waiting after 180 seconds for xpt_config
run_interrupt_driven_hooks: still waiting after 240 seconds for xpt_config
run_interrupt_driven_hooks: still waiting after 300 seconds for xpt_config
Then just stalls
2. No ACPI
...
unknown: timeout waiting for read DRQ
unknown: timeout waiting for read DRQ
acd0: DVDR <Optiarc DVD RW AD-7560S/SX01> at ata3-master UDMA33
GEOM_LABEL: Label for provider acd0 is iso9660/FreeBSD_Install
run_interrupt_driven_hooks: still waiting after 60 seconds for xpt_config
run_interrupt_driven_hooks: still waiting after 120 seconds for xpt_config
run_interrupt_driven_hooks: still waiting after 180 seconds for xpt_config
run_interrupt_driven_hooks: still waiting after 240 seconds for xpt_config
run_interrupt_driven_hooks: still waiting after 300 seconds for xpt_config
Then just stalls
3. Safe Mode
I can only tell you a little because console is spammed. It is the
same as no ACPI, but with an interrupt storm.
...
unknown: timeout waiting for read DRQ
unknown: timeout waiting for read DRQ
acd0: DVDR <Optiarc DVD RW AD-7560S/SX01> at ata3-master UDMA33
GEOM_LABEL: Label for provider acd0 is iso9660/FreeBSD_Install
run_interrupt_driven_hooks: still waiting after 60 seconds for xpt_config
run_interrupt_driven_hooks: still waiting after 120 seconds for xpt_config
run_interrupt_driven_hooks: still waiting after 180 seconds for xpt_config
run_interrupt_driven_hooks: still waiting after 240 seconds for xpt_config
run_interrupt_driven_hooks: still waiting after 300 seconds for xpt_config
When it gets to the unknowns, this is spammed.
interrupt storm detected on "irq10:"; throttling interrupt source
Other than the interrupt storm spam, it is halted like the others.
4. Single User Mode
Same as 1, Default
5. Verbose
All I can tell you is what is spammed at the end.
acpi: bad write to port 0x080 (32), val hex
Where hex is ever increasing and loops when it hits 0xff01. I can also
see run_interrupt_driven_hooks message in all the spam.
Using some googling if you add the sysctl before boot
debug.acpi.block_bad_io=1
it might be of some help. This just leads to a never ending loop of
acpi errors - the scroll very fast and difficult to record might I
add!
...
acpi: bad write to port 0x080 (32), val hex
ACPI Exception (evregion-0529): AE_BAD_PARAMETER, Returned by handler
for [SystemIO] [20070320]
ACPI Error (psparse-0626): Method parse/execution failed [\P8XH] (Node
0xc6850a60), AE_BAD_PARAMETER
ACPI Error (psparse-0626): Method parse/execution failed [\_GPE._L01]
[20070320]
ACPI Exception (evgpe-0687): AE_BAD_PARAMETER, while evauating GPE
method [_L01] [20070320]
--repeat--
...
FreeBSD 7.0-REL
7.0 is a little different than 7.1. Messages are somewhat the same but
they happen near the beginning of dmesg instead of around the end. The
run_interrupt_driven_hooks issue is nonexistant as well, but it still
hangs. I'm guessing that's a debug tool more than an error.
1. Default
...
cpu0: <ACPI CPU> on acpi0
ACPI Error (dsopcode-0350): No pointer back to NS node in buffer obj
0xc6862580 [20070320]
ACPI Exception (dswexec-0556): AE_AML_INTERNAL, While resolving
operands for [OpcodeName unavailable] [20070320]
ACPI Error (psparse-0626): Method parse/execution failed
[\_PR_.CPU0._OSC] (Node 0xc682d580), AE_AML_INTERNAL
est0: <Enhanced SpeedStep Frequency Control> on cpu0
p4tcc0: <CPU Frequency Thermal Control> on cpu0
cpu1: <ACPI CPU> on acpi0
ACPI Error (dsopcode-0350): No pointer back to NS node in buffer obj
0xc6861100 [20070320]
ACPI Exception (dswexec-0556): AE_AML_INTERNAL, While resolving
operands for [OpcodeName unavailable] [20070320]
ACPI Error (psparse-0626): Method parse/execution failed
[\_PR_.CPU1._OSC] (Node 0xc682d4a0), AE_AML_INTERNAL
est1: <Enhanced SpeedStep Frequency Control> on cpu1
p4tcc1: <CPU Frequency Thermal Control> on cpu1
...
cpu0: Cx states changed
cpu1: Cx states changed
unknown: timeout waiting for read DRQ
unknown: timeout waiting for read DRQ
acd0: DVDR <Optiarc DVD RW AD-7560S/SX01> at ata3-master UDMA33
GEOM_LABEL: Label for provider acd0 is iso9660/FreeBSD_Install
Hangs.
2. No ACPI
..
unknown: timeout waiting for read DRQ
unknown: timeout waiting for read DRQ
..
Hangs.
3. Safe Mode
Same interrupt storm as 7.1-BETA2.
...
interrupt storm detected on "irq10:"; throttling interrupt source
--repeat--
4. Single User Mode
Same as 1. Default.
5. Verbose
Hang like normal, cannot see the ACPI errors since they fly off the
scroll lock buffer.
...
cpu0: Cx states changed
cpu1: Cx states changed
...
unknown: timeout waiting for read DRQ
unknown: timeout waiting for read DRQ
...
Thanks again.
On Wed, 29 Oct 2008, Ryan wrote:
Hello, I purchased a new Clevo M860TU on the account that it ran
linux very well and was hoping it would fair the same on FreeBSD. Not
so much, little help? I posted this in mobile originally but though
stable would be a better choice. Don't know if it is more appropriate
here or ACPI.
I'm giving you as much information as I know how to get. as I
cannot get sysinstall to load I am having to type all these dmesg. The
boot process is hanging. This is all with 7.x, I can give 6.x if
needed.
xpt_config is the CAM configuration wait, so basically the system is
waiting for a storage device to report back on whether it could be
used as a root file system.
I recently saw a similar report of problems involving a firewire
controller on an nvidia motherboard following an upgrade to 7.x, and I
wonder if you might try the following: see if 6.4 will install, and if
so, install it. Then cvsup 7.x, and do a buildworld but not an
installworld. This will let you build and experiment with 7.x kernels
from a known-working environment.
Make sure to keep a working 6.x kernel around -- I suggest something
like "cp -r /boot/kernel /boot/kernel.good" before starting so you can
always fall back to a good kernel. Now try building a 7.x kernel
without USB or firewire support, and booting that?
Also, it's worth checking there are no BIOS upgrades available for the
motherboard...
Robert N M Watson
Computer Laboratory
University of Cambridge
Thanks for your interest Robert, unfortunately it was a no-go. I went
ahead and tested 6.4RC1 and 6.3. Now all I am getting are ACPI errors
which I would think I could get the installer going by disabling ACPI.
And yes, I'm running on the latest - and only - bios revision for the
laptop.
The following were done under default boot option. No ACPI did not
generate any error messages and hung, single user mode acted the same
as default, and safe mode created an interrupt storm like 7.x did.
6.4-RC1
...
acpi_timer0: <24-bit timer at 3.579545 MHz> port 0x408-0x40b on acpi0
acpi_ec0: <Embedded Controller: GPE 0x18> port 0x62, 0x66 on acpi0
cpu0: <ACPI CPU> on acpi0
ACPI-0328: *** Error: No pointer back to NS node in buffer obj 0xc85c87c0
ACPI-1304: *** Error: Method execution failed [\_PR_.CPU0._OSC]
(Node 0xc84e2580), AE_AML_INTERNAL
acpi_throttle0: <ACPI CPU Throttling> on cpu0
...
then this gets spammed 6 times at the end
ACPI-0438: *** Error: Looking up [\_PR_.CPU0._PPC] in name space, AE_NOT_FOUND
SearchNode 0xc84cdcc0 StartNode 0xc84cdcc0 ReturnNode 0
ACPI-1304: *** Error: Method execution failed [\_SB_.AC__.ADJP] (Node
0xc84cdcc0), AE_NOT_FOUND
ACPI-1304: *** Error: Method execution failed [\_SB.AC__._PSR] (Node
0xc84cdd00), AE_NOT_FOUND
6.3-REL
6.3 gives the same errors but with different node addresses.
...
acpi_timer0: <24-bit timer at 3.579545 MHz> port 0x408-0x40b on acpi0
acpi_ec0: <Embedded Controller: GPE 0x18> port 0x62, 0x66 on acpi0
cpu0: <ACPI CPU> on acpi0
ACPI-0328: *** Error: No pointer back to NS node in buffer obj 0xc85c94c0
ACPI-1304: *** Error: Method execution failed [\_PR_.CPU0._OSC]
(Node 0xc84e3780), AE_AML_INTERNAL
acpi_throttle0: <ACPI CPU Throttling> on cpu0
...
spammed again 6 times at the end
ACPI-0438: *** Error: Looking up [\_PR_.CPU0._PPC] in name space, AE_NOT_FOUND
SearchNode 0xc84cdd20 StartNode 0xc84cdd20 ReturnNode 0
ACPI-1304: *** Error: Method execution failed [\_SB_.AC__.ADJP] (Node
0xc84cdd20), AE_NOT_FOUND
ACPI-1304: *** Error: Method execution failed [\_SB.AC__._PSR] (Node
0xc84e3780), AE_NOT_FOUND
Help at all?
Ryan skrev:
- Show quoted text -
Hello, I purchased a new Clevo M860TU on the account that it ran linux
very well and was hoping it would fair the same on FreeBSD. Not so
much, little help? I posted this in mobile originally but though
stable would be a better choice. Don't know if it is more appropriate
here or ACPI.
I'm giving you as much information as I know how to get. as I cannot
get sysinstall to load I am having to type all these dmesg. The boot
process is hanging. This is all with 7.x, I can give 6.x if needed.
Hardware:
Intel P9500
4gb DDR3-1066
Nvidia 9800M GT
Atheros AR5006e
FreeBSD 7.1-BETA2
These snippets of dmesg happen around the end where it hangs.
1. Default
...
cpu0: <ACPI CPU> on acpi0
ACPI Error (dsopcode-0350): No pointer back to NS node in buffer obj
0xc6a02d40 [20070320]
ACPI Exception (dswexec-0556): AE_AML_INTERNAL, While resolving
operands for [OpcodeName unavailable] [20070320]
ACPI Error (psparse-0626): Method parse/execution failed
[\_PR_.CPU0._OSC] (Node 0xc68556e0), AE_AML_INTERNAL
est0: <Enhanced SpeedStep Frequency Control> on cpu0
p4tcc0: <CPU Frequency Thermal Control> on cpu0
cpu1: <ACPI CPU> on acpi0
ACPI Error (dsopcode-0350): No pointer back to NS node in buffer obj
0xc6a0e300 [20070320]
ACPI Exception (dswexec-0556): AE_AML_INTERNAL, While resolving
operands for [OpcodeName unavailable] [20070320]
ACPI Error (psparse-0626): Method parse/execution failed
[\_PR_.CPU1._OSC] (Node 0xc685560), AE_AML_INTERNAL
est1: <Enhanced SpeedStep Frequency Control> on cpu1
p4tcc1: <CPU Frequency Thermal Control> on cpu1
...
cpu0: Cx states changed
cpu1: Cx states changed
unknown: timeout waiting for read DRQ
unknown: timeout waiting for read DRQ
acd0: DVDR <Optiarc DVD RW AD-7560S/SX01> at ata3-master UDMA33
GEOM_LABEL: Label for provider acd0 is iso9660/FreeBSD_Install
run_interrupt_driven_hooks: still waiting after 60 seconds for xpt_config
run_interrupt_driven_hooks: still waiting after 120 seconds for xpt_config
run_interrupt_driven_hooks: still waiting after 180 seconds for xpt_config
run_interrupt_driven_hooks: still waiting after 240 seconds for xpt_config
run_interrupt_driven_hooks: still waiting after 300 seconds for xpt_config
Disabling firewire completely in BIOS might at least get the machine
booting. You should try that if you haven't already. I've seen this
problem on at least two different systems...
--
Joel
Sadly with the quality of BIOS recently, that is not an option. Not
much to offer. Attached is a picture of what I have to change. Other
and XP are the same, Vista unlocks AHCI.
Another way of accomplishing disabling firewire is to remake the
install CD with a different kernel and not quite sure how to do that.
Ryan skrev:
Sadly with the quality of BIOS recently, that is not an option. Not
much to offer. Attached is a picture of what I have to change. Other
and XP are the same, Vista unlocks AHCI.
Another way of accomplishing disabling firewire is to remake the
install CD with a different kernel and not quite sure how to do that.
Take a look at the release(7) manpage for information about building
your own customized release CD.
--
Joel
Finally had time to understand some how release works and made some
new cds. Some new updates to the situation since as I am still having
issues. I was not able to figure out how to make release with a custom
kernel, would always fail that step so I had to stick with GENERIC. To
simulate taking out firewire support I just deleted the corresponding
kernel modules in /boot/kernel and remade the iso. Stable as of
12-07-2008 is giving the same feedback as 7.1-B2 but actually gives a
panic screen.
panic: run_interrupt_driven_config_hooks: waited too long
cpuid = 0
KDB: enter: panic
[thread pid 0 tid 100000 ]
Stopped at kdb_enter+0x3a: movl $0,kdb_why
db>
There has been a bios update recently and have applied it, but there
has been no change in any of the tests by a quick glance.
If it makes a difference the cds I create with cdrecord generate the
added errors acd0: FAILURE - READ BIG timed out. I don't think that
has anything to do with it, just saying it for full disclosure.
Disregard if irrelevant. That error applies to only the stable builds
I made.