Clevo M860TU Install Issues

Tue Oct 21 21:44:35 UTC 2008

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'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 AR242x

I can give linux equivilant commands when I am done installing that.

Any input? Much appreciated.

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 interupt 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.