I just installed openSuse 12.3 and Windows 7 as dual boot on my new ASUS BU 400V notebook. Unfortunately I am experiencing strange problems. When the external power is connected, everything runs smooth. However, as soon as I disconnect the external power supply, the system hangs and when booting without external power, dmesg shows lots of errors of the form:
112.655438] ata1.00: status: { DRDY }
112.655442] ata1.00: failed command: WRITE FPDMA QUEUED
112.655452] ata1.00: cmd 61/08:58:90:21:8b/00:00:0f:00:00/40 tag 11 ncq 4096 out
112.655452] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
112.655457] ata1.00: status: { DRDY }
112.655461] ata1.00: failed command: WRITE FPDMA QUEUED
112.655470] ata1.00: cmd 61/08:60:10:21:8a/00:00:0f:00:00/40 tag 12 ncq 4096 out
112.655470] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
112.655476] ata1.00: status: { DRDY }
112.655480] ata1.00: failed command: WRITE FPDMA QUEUED
112.655489] ata1.00: cmd 61/08:68:00:40:90/00:00:0f:00:00/40 tag 13 ncq 4096 out
112.655489] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
112.655494] ata1.00: status: { DRDY }
112.655503] ata1: hard resetting link
112.959741] ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
112.972057] ata1.00: ACPI cmd f5/00:00:00:00:00:a0 (SECURITY FREEZE LOCK) filtered out
112.972140] ata1.00: ACPI cmd ef/10:06:00:00:00:a0 (SET FEATURES) succeeded
112.972149] ata1.00: ACPI cmd ef/10:03:00:00:00:a0 (SET FEATURES) filtered out
112.991966] ata1.00: ACPI cmd f5/00:00:00:00:00:a0 (SECURITY FREEZE LOCK) filtered out
112.992042] ata1.00: ACPI cmd ef/10:06:00:00:00:a0 (SET FEATURES) succeeded
112.992051] ata1.00: ACPI cmd ef/10:03:00:00:00:a0 (SET FEATURES) filtered out
113.001865] ata1.00: configured for UDMA/133
113.002247] ata1.00: device reported invalid CHS sector 0
At first, I was worried, the SSD was defect, but if I re-connect to external power, the system responds normally again. I did some research on the internet, but the only solutions I found were
Change IDE cables (seems to make little sense, since systems works when power is connected)
Add libata.force=noncq to GRUB command line. This did not improve the situation.
The system runs with a 256 GB SSD.
I have absolutely no idea, what could possibly cause this behaviour, so I tried to limit the information provided to those settings, which I am pretty sure are related to the problem. If you need any additional system information, please do not hesitate to ask, and I gladly provide whatever necessary.
On Tue, 30 Apr 2013 20:06:02 +0000, claashk wrote:
> Any help would be greatly appreciated
Only thought that comes immediately to mind for me is if the battery
isn’t putting out enough power to drive the system. Low voltage
certainly could cause weird problems.
Only thought that comes immediately to mind for me is if the battery
isn’t putting out enough power to drive the system. Low voltage
certainly could cause weird problems.
Hi Jim!
Thanks for the comment. However, as Windows is running smooth in battery mode, the notebook is new, and the battery is fully charged, I doubt this is the problem. Is it possible, though, that the problem could be related to ACPI? I would expect different power settings for battery mode compared to the charging mode. But since this is my first notebook running linux I know zip about how this works. Is there a way to check or set the settings for power management?
On Wed, 01 May 2013 08:16:01 +0000, claashk wrote:
> Thanks for the comment. However, as Windows is running smooth in
> battery mode, the notebook is new, and the battery is fully charged, I
> doubt this is the problem. Is it possible, though, that the problem
> could be related to ACPI? I would expect different power settings for
> battery mode compared to the charging mode. But since this is my first
> notebook running linux I know zip about how this works. Is there a way
> to check or set the settings for power management?
That’s good to know - you hadn’t mentioned if a similar problem existed
under the Windows installation or not, so it seemed the only change was
plugged in/not plugged in.
YaST has a power management section, you might look at that and see what
it’s set to. Try setting it to “performance” and see if that makes any
difference (“performance” mode disables all/most powersaving elements and
should not reduce voltages anywhere as I understand it).
> That’s good to know - you hadn’t mentioned if a similar problem existed
> under the Windows installation or not, so it seemed the only change was
> plugged in/not plugged in.
Sorry.
> YaST has a power management section, you might look at that and see what
> it’s set to. Try setting it to “performance” and see if that makes any
> difference (“performance” mode disables all/most powersaving elements and
> should not reduce voltages anywhere as I understand it).
Thanks for the hint. I did not even have the yast-power management module installed. However, after installing it and setting the mode to “minimum latency” (there is no performace mode in my version), the symptoms remained. However, there is a check box “power management enabled” when clicking on the battery symbol in the task bar. Unchecking this box seemingly helps, although I have no idea where these changes are made. If this completely disables power management, its probably a high price to pay. None-the-less, thanks for the tip.
Is this a well known problem or should I open a bug report somewhere?
On Fri, 03 May 2013 18:16:01 +0000, claashk wrote:
> Thanks for the hint. I did not even have the yast-power management
> module installed. However, after installing it and setting the mode to
> “minimum latency” (there is no performace mode in my version), the
> symptoms remained. However, there is a check box “power management
> enabled” when clicking on the battery symbol in the task bar. Unchecking
> this box seemingly helps, although I have no idea where these changes
> are made. If this completely disables power management, its probably a
> high price to pay. None-the-less, thanks for the tip.
>
> Is this a well known problem or should I open a bug report somewhere?
It was a bit of an educated guess on my part - you should probably report
it on bugzilla (have a quick search first just to see if it’s there). http://bugzilla.novell.com is where openSUSE bugs are reported - there’s
a good set of guidelines at http://en.opensuse.org/Bug_Reporting_FAQ
Unfortunately things got worse after improving. Since I did not manage to disable powermanagement permanently (after reboot it automatically turned on), I added the line acpi=off to the bootloader. The result was a crash which forced a re-installation because grub2 could somehow not restore the bootloader. So completely disabling acpi via the bootloader is not an option. I checked dmesg again and found some ACPI related warnings, even if power is connected
6.041553] ACPI: AC Adapter [AC0] (on-line)
6.345905] ACPI Warning: 0x000000000000f040-0x000000000000f05f SystemIO conflicts with Region \SMB0 1 (20120913/utaddress-251)
6.345914] ACPI Warning: 0x000000000000f040-0x000000000000f05f SystemIO conflicts with Region \_SB_.PCI0.SBUS.SMBI 2 (20120913/utaddress-251)
6.345920] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
6.581258] ACPI: Deprecated procfs I/F for battery is loaded, please retry with CONFIG_ACPI_PROCFS_POWER cleared
6.581268] ACPI: Battery Slot [BAT0] (battery present)
6.583126] ACPI Warning: 0x0000000000000428-0x000000000000042f SystemIO conflicts with Region \GPIS 1 (20120913/utaddress-251)
6.583134] ACPI Warning: 0x0000000000000428-0x000000000000042f SystemIO conflicts with Region \PMIO 2 (20120913/utaddress-251)
6.583141] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
6.583146] ACPI Warning: 0x0000000000000530-0x000000000000053f SystemIO conflicts with Region \GPIO 1 (20120913/utaddress-251)
6.583151] ACPI Warning: 0x0000000000000530-0x000000000000053f SystemIO conflicts with Region \GP01 2 (20120913/utaddress-251)
6.583157] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
6.583159] ACPI Warning: 0x0000000000000500-0x000000000000052f SystemIO conflicts with Region \GPIO 1 (20120913/utaddress-251)
6.583164] ACPI Warning: 0x0000000000000500-0x000000000000052f SystemIO conflicts with Region \GP01 2 (20120913/utaddress-251)
6.583169] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
6.635015] ACPI Error: Needed [Buffer/String/Package], found [Integer] ffff880222e37228 (20120913/exresop-590)
6.635020] ACPI Exception: AE_AML_OPERAND_TYPE, While resolving operands for [Index] (20120913/dswexec-460)
6.635025] ACPI Error: Method parse/execution failed \_SB_.PCI0.GFX0._DSM] (Node ffff88022303bb78), AE_AML_OPERAND_TYPE (20120913/psparse-536)
7.168952] asus_wmi: Backlight controlled by ACPI video driver
On Sat, 04 May 2013 12:56:02 +0000, claashk wrote:
> Could this be a related problem?
I suppose it’s possible it could be related. I’d definitely get a bug
entered, as this is going to need to be looked at by someone with deeper
kernel knowledge, I think.
This notebook seems to be an Optimus system, something that surely can explain your problems at least partially, maybe all of them. Can you confirm this, give us the output of