Bug 60812 - Asus Zenbook ux31e: crash or hard poweroff after switching from bat to ac
Summary: Asus Zenbook ux31e: crash or hard poweroff after switching from bat to ac
Status: CLOSED UNREPRODUCIBLE
Alias: None
Product: ACPI
Classification: Unclassified
Component: Power-Battery (show other bugs)
Hardware: All Linux
: P1 normal
Assignee: Lan Tianyu
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-08-29 13:38 UTC by Oleksij Rempel
Modified: 2014-06-14 15:38 UTC (History)
3 users (show)

See Also:
Kernel Version: 3.11
Subsystem:
Regression: No
Bisected commit-id:


Attachments
acpidump (368.64 KB, text/plain)
2013-08-30 06:01 UTC, Oleksij Rempel
Details
lspci (1.34 KB, text/plain)
2013-08-30 06:02 UTC, Oleksij Rempel
Details
lspci verbose (7.02 KB, text/plain)
2013-08-30 06:02 UTC, Oleksij Rempel
Details
dmesg (79.19 KB, text/plain)
2013-08-30 06:04 UTC, Oleksij Rempel
Details
ac.patch (873 bytes, patch)
2013-09-04 06:27 UTC, Lan Tianyu
Details | Diff

Description Oleksij Rempel 2013-08-29 13:38:35 UTC
If i switch my Asus Zenbook ux31e from AC to battery or back, it will freeze or go off.
The freeze looks not like kernel panic. At least i was not able to trigger kexec/kdump on it.
Poweroff is sort of hardware poweroff. At least, i had no power off string in logs.
As workaround i use two methods:
1. suspend to ram, then plug or unplug AC. So it wont crush
2. or kill/stop all services polling acpi. For example acpid and upower.

I was able to use EHCI Debug port with DIY adapter made of two FX2 boards. See:
http://www.coreboot.org/DIY_EHCI_debug_dongle
But suddenly i haven't seen any last words of dying laptop :)

There is no know working kernel. So far i know this problem was always present, but not 100% reproducible. For each test i need at least a day, to be sure if there are some changes.

It seems to work on windows, and it affect some other users of this hardware:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/989191
Comment 1 Aaron Lu 2013-08-30 01:57:16 UTC
Please attach acpidump:
# acpidump > acpidump.txt
And lspci, dmesg, thanks.
Comment 2 Oleksij Rempel 2013-08-30 06:01:49 UTC
Created attachment 107364 [details]
acpidump
Comment 3 Oleksij Rempel 2013-08-30 06:02:07 UTC
Created attachment 107365 [details]
lspci
Comment 4 Oleksij Rempel 2013-08-30 06:02:24 UTC
Created attachment 107366 [details]
lspci verbose
Comment 5 Oleksij Rempel 2013-08-30 06:04:26 UTC
Created attachment 107367 [details]
dmesg
Comment 6 Lan Tianyu 2013-09-04 06:27:53 UTC
Created attachment 107411 [details]
ac.patch

Please try this patch.
Comment 7 Oleksij Rempel 2013-09-04 07:17:18 UTC
Hi Lan,

right now i hope to reproduce it again. I removed battery and after i attached it again, i can't reproduce it. It looks like suspend/resume issue: https://bugzilla.kernel.org/show_bug.cgi?id=42728
If suspend/resume filed, this laptop came back with misconfigured memory controller. To fix it i needed to reattach battery (do complete reset).

Here seems to have similar roots. ACPI code is probably ok, but after some other issue EC was not responding correctly.

I'll continue to monitor this laptop and see if i can reproduce it again.
Comment 8 Lan Tianyu 2013-09-04 07:27:13 UTC
(In reply to Oleksij Rempel from comment #7)
> Hi Lan,
> 
> right now i hope to reproduce it again. I removed battery and after i
> attached it again, i can't reproduce it. It looks like suspend/resume issue:
> https://bugzilla.kernel.org/show_bug.cgi?id=42728
> If suspend/resume filed, this laptop came back with misconfigured memory
> controller. To fix it i needed to reattach battery (do complete reset).
> 

"Do complete reset" is "reset Bios", right?

> Here seems to have similar roots. ACPI code is probably ok, but after some
> other issue EC was not responding correctly.

How do you find EC was not responding? Is there some err logs?

> 
> I'll continue to monitor this laptop and see if i can reproduce it again.

Ok. Thanks.
Comment 9 Oleksij Rempel 2013-09-04 08:00:28 UTC
(In reply to Lan Tianyu from comment #8)
> (In reply to Oleksij Rempel from comment #7)
> > Hi Lan,
> > 
> > right now i hope to reproduce it again. I removed battery and after i
> > attached it again, i can't reproduce it. It looks like suspend/resume
> issue:
> > https://bugzilla.kernel.org/show_bug.cgi?id=42728
> > If suspend/resume filed, this laptop came back with misconfigured memory
> > controller. To fix it i needed to reattach battery (do complete reset).
> > 
> 
> "Do complete reset" is "reset Bios", right?

no. complete power off: AC and battery are removed. If battery is not removed it will stay in broken state. There is no need to remove CMOS battery, so i assume BIOS is not reseted.

> > Here seems to have similar roots. ACPI code is probably ok, but after some
> > other issue EC was not responding correctly.
> 
> How do you find EC was not responding? Is there some err logs?

Just assumption. Probably incorrect.
Comment 10 Lan Tianyu 2013-09-16 09:28:05 UTC
(In reply to Oleksij Rempel from comment #9)
> (In reply to Lan Tianyu from comment #8)
> > (In reply to Oleksij Rempel from comment #7)
> > > Hi Lan,
> > > 
> > > right now i hope to reproduce it again. I removed battery and after i
> > > attached it again, i can't reproduce it. It looks like suspend/resume
> issue:
> > > https://bugzilla.kernel.org/show_bug.cgi?id=42728
> > > If suspend/resume filed, this laptop came back with misconfigured memory
> > > controller. To fix it i needed to reattach battery (do complete reset).
> > > 
> > 
> > "Do complete reset" is "reset Bios", right?
> 
> no. complete power off: AC and battery are removed. If battery is not
> removed it will stay in broken state. There is no need to remove CMOS
> battery, so i assume BIOS is not reseted.

Ok. Maybe, removing the battery makes some hardwares reset and the issue is fixed by it. So now you can't replace the issue, right?  

> 
> > > Here seems to have similar roots. ACPI code is probably ok, but after
> some
> > > other issue EC was not responding correctly.
> > 
> > How do you find EC was not responding? Is there some err logs?
> 
> Just assumption. Probably incorrect.
Comment 11 Lan Tianyu 2013-09-16 09:28:38 UTC
(In reply to Lan Tianyu from comment #10)
> (In reply to Oleksij Rempel from comment #9)
> > (In reply to Lan Tianyu from comment #8)
> > > (In reply to Oleksij Rempel from comment #7)
> > > > Hi Lan,
> > > > 
> > > > right now i hope to reproduce it again. I removed battery and after i
> > > > attached it again, i can't reproduce it. It looks like suspend/resume
> issue:
> > > > https://bugzilla.kernel.org/show_bug.cgi?id=42728
> > > > If suspend/resume filed, this laptop came back with misconfigured
> memory
> > > > controller. To fix it i needed to reattach battery (do complete reset).
> > > > 
> > > 
> > > "Do complete reset" is "reset Bios", right?
> > 
> > no. complete power off: AC and battery are removed. If battery is not
> > removed it will stay in broken state. There is no need to remove CMOS
> > battery, so i assume BIOS is not reseted.
> 
> Ok. Maybe, removing the battery makes some hardwares reset and the issue is
> fixed by it. So now you can't replace the issue, right?  

/replace/reproduce/

> 
> > 
> > > > Here seems to have similar roots. ACPI code is probably ok, but after
> some
> > > > other issue EC was not responding correctly.
> > > 
> > > How do you find EC was not responding? Is there some err logs?
> > 
> > Just assumption. Probably incorrect.
Comment 12 Oleksij Rempel 2013-09-16 10:27:12 UTC
(In reply to Lan Tianyu from comment #10)
> > 
> > no. complete power off: AC and battery are removed. If battery is not
> > removed it will stay in broken state. There is no need to remove CMOS
> > battery, so i assume BIOS is not reseted.
> 
> Ok. Maybe, removing the battery makes some hardwares reset and the issue is
> fixed by it. So now you can't replace the issue, right?  

right.
Comment 13 Lan Tianyu 2013-09-16 12:39:01 UTC
Ok. Thanks for reply. Close this bug as unreproducible.
Comment 14 Alexis Jeandet 2014-06-14 15:38:13 UTC
Hi,

I might be late now, but I always got this issue and I was sure that it was some hardware issue. I saw this post yesterday and tried to remove the battery(on my Zenbook UX31E) and now it works perfectly with kernel 3.14 on fedora 20.

Note that I've first installed fedora 19 when I received it(something like 2 years ago) then update the bios to the latest version and today I did this.

Thanks it saved my laptop and my money!
Best regards,
Alexis.

Note You need to log in before you can comment on or make changes to this bug.