no reboot / shutdown on asus m6ne laptop [breezy]

Bug #22413 reported by furukama
8
Affects Status Importance Assigned to Milestone
linux-source-2.6.15 (Ubuntu)
Invalid
Medium
Ben Collins

Bug Description

after upgrading to breezy, rebooting and shutting down doesn't work anymore.

rebooting just stops the system after the message "localhost shutdown[5721]:
shutting down for system reboot" in /var/log/messages. I have to manually press
the power button twice to reboot the system.

The same goes for shutting down.

The difference is: rebooting stops with a blank screen and shutting down with
the console screen.

Revision history for this message
furukama (eigenarbeit) wrote :

kernel is: 2.6.12-8-686

Revision history for this message
furukama (eigenarbeit) wrote :
Download full text (3.9 KiB)

ACPI related dmesg lines:

294672.373000] ACPI: PCI Root Bridge [PCI0] (0000:00)
[4294672.373000] ACPI: Assume root bridge [\_SB_.PCI0] segment is 0
[4294672.375000] ACPI-0287: *** Error: Region EmbeddedControl(3) has no handler
[4294672.375000] ACPI-0508: *** Error: Method execution failed
[\_SB_.PCI0.SBRG.EC0_.BATS] (Node dffe9480), AE_NOT_EXIST
[4294672.375000] ACPI-0508: *** Error: Method execution failed
[\_SB_.BAT0._STA] (Node dffe6280), AE_NOT_EXIST
[4294672.375000] ACPI-0171: *** Error: Method execution failed
[\_SB_.BAT0._STA] (Node dffe6280), AE_NOT_EXIST
[4294672.379000] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0._PRT]
[4294672.382000] ACPI: Embedded Controller [EC0] (gpe 28)
[4294672.383000] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.P0P2._PRT]
[4294672.383000] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.P0P1._PRT]
[4294672.386000] ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 5 6 7 10 *11 12)
[4294672.387000] ACPI: PCI Interrupt Link [LNKB] (IRQs 3 *4 5 6 7 11 12)
[4294672.387000] ACPI: PCI Interrupt Link [LNKC] (IRQs *10 12)
[4294672.388000] ACPI: PCI Interrupt Link [LNKD] (IRQs *5 6 10)
[4294672.388000] ACPI: PCI Interrupt Link [LNKE] (IRQs 6 11) *0, disabled.
[4294672.389000] ACPI: PCI Interrupt Link [LNKF] (IRQs 3 7) *0, disabled.
[4294672.389000] ACPI: PCI Interrupt Link [LNKG] (IRQs 4 7) *0, disabled.
[4294672.390000] ACPI: PCI Interrupt Link [LNKH] (IRQs 4 6 *10 12)
[4294672.390000] pnp: PnP ACPI init
[4294672.396000] pnp: PnP ACPI: found 15 devices
[4294672.396000] PnPBIOS: Disabled by ACPI PNP
[4294672.396000] PCI: Using ACPI for IRQ routing
[4294672.779000] ACPI: PCI Interrupt Link [LNKB] enabled at IRQ 4
[4294672.779000] ACPI: PCI Interrupt 0000:00:1f.6[B] -> Link [LNKB] -> GSI 4
(level, low) -> IRQ 4
[4294672.779000] ACPI: PCI interrupt for device 0000:00:1f.6 disabled
[4294672.792000] ACPI wakeup devices:
[4294672.792000] ACPI: (supports S0 S3 S4 S5)
[4294672.844000] ACPI: bus type ide registered
[4294672.850000] ACPI: PCI Interrupt Link [LNKC] enabled at IRQ 10
[4294672.850000] ACPI: PCI Interrupt 0000:00:1f.1[A] -> Link [LNKC] -> GSI 10
(level, low) -> IRQ 10
[4294677.113000] ACPI: PCI Interrupt Link [LNKA] enabled at IRQ 11
[4294677.113000] ACPI: PCI Interrupt 0000:00:1d.0[A] -> Link [LNKA] -> GSI 11
(level, low) -> IRQ 11
[4294677.178000] ACPI: PCI Interrupt Link [LNKD] enabled at IRQ 5
[4294677.178000] ACPI: PCI Interrupt 0000:00:1d.1[B] -> Link [LNKD] -> GSI 5
(level, low) -> IRQ 5
[4294677.243000] ACPI: PCI Interrupt 0000:00:1d.2[C] -> Link [LNKC] -> GSI 10
(level, low) -> IRQ 10
[4294677.329000] ACPI: PCI Interrupt Link [LNKH] enabled at IRQ 10
[4294677.329000] ACPI: PCI Interrupt 0000:00:1d.7[D] -> Link [LNKH] -> GSI 10
(level, low) -> IRQ 10
[4294677.407000] ACPI: PCI Interrupt 0000:02:00.0[A] -> Link [LNKB] -> GSI 4
(level, low) -> IRQ 4
[4294679.680000] ACPI: CPU0 (power states: C1[C1])
[4294679.688000] ACPI: Thermal Zone [THRM] (65 C)
[4294697.296000] ACPI: PCI Interrupt 0000:00:1f.5[B] -> Link [LNKB] -> GSI 4
(level, low) -> IRQ 4
[4294698.685000] ACPI: PCI Interrupt 0000:02:01.0[A] -> Link [LNKB] -> GSI 4
(level, low) -> IRQ 4
[4294698.816000] ACPI: PCI Interrupt 0000:02:01.1[B] ->...

Read more...

Revision history for this message
Tan Quach (guoguojin) wrote :

This is also the case on a SONY FS115B laptop.

Revision history for this message
Matthew Garrett (mjg59) wrote :

Please try the latest kernel to see if that improves things.

Revision history for this message
Nicolò Chieffo (yelo3) wrote :

I think you have to ad a boot option to resolve this issue:
nolapic
because lapic is compiled in the kernel but it's not supported by asus laptops! try!

Revision history for this message
comeon (comeon2424) wrote :

This happens on my Asus M6BNE. Occasionaly it will not just hang with the
rebooting messages but the screen will go blank and then it hangs.

Revision history for this message
yannux (yannux) wrote :

(In reply to comment #5)
> I think you have to ad a boot option to resolve this issue:
> nolapic
> because lapic is compiled in the kernel but it's not supported by asus
laptops! try!

I confirm to try with nolapic, it's work fine on my asus M6BNE :)
Thanks :)

Revision history for this message
Ben Collins (ben-collins) wrote :

If possible, please upgrade to Dapper's 2.6.15-8 kernel. If you do not want to
upgrade to Dapper, then you can also wait for the Dapper Flight 2 CD's, which
are due out within the next few days.

Let me know if this bug still exists with this kernel.

Revision history for this message
Carthik Sharma (carthik) wrote :

Thank you for reporting this bug and following up on it.

I am marking this bug Closed since there has been no response from you for over three months. We
would like to fix all existing issues, but need need feedback to help with debugging.

Should you still have a problem with the latest up to date Dapper kernel and packages, please reopen this bug. In this case, please answer the questions that have already been asked of you before and provide the log files and information required for debugging.

Changed in linux-source-2.6.15:
status: Needs Info → Rejected
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.