Created attachment 92261 [details] /proc/acpi folder Notebook periodicaly hangs. dmesg | grep "War\|war\|Err\|Bug": [ 0.000000] Booting paravirtualized kernel on bare hardware [ 0.219889] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored [ 1.019584] ACPI Error: Invalid/unsupported resource descriptor: Type 0x00 (20120320/utresrc-650) [ 13.464231] mei: module is from the staging directory, the quality is unknown, you have been warned. [ 14.067681] psmouse serio1: elantech: assuming hardware version 3 (with firmware version 0x350f00) [ 14.465572] iwlwifi 0000:02:00.0: loaded firmware version 18.168.6.1 [ 14.725732] ACPI Error: Needed [Buffer/String/Package], found [Integer] f75aef30 (20120320/exresop-590) [ 14.725741] ACPI Error: Method parse/execution failed [\_SB_.PCI0.GFX0._DSM] (Node f7435750), AE_AML_OPERAND_TYPE (20120320/psparse-536) [ 15.764291] [Firmware Bug]: ACPI(PEGP) defines _DOD but not _DOS
Created attachment 92271 [details] lspci -vvnn one more attach
Created attachment 92281 [details] dmidecode and one more attach
Notebook model SAMSUNG NP300V5A-S16RU
Created attachment 92291 [details] files from /var/log (dmesg, kern, syslog)
I will have access to notebook until tommorow. So if any more info needed, please write to me as soon as posiblr.
Hi Anderey, By periodically hang, do you mean it crashed after being used some time or it stuck for a while then becoming usable again? And is it possible for you to test an upstream kernel, not the disto provided kernel if you still have access to the notebook, thanks.
On 02/18/2013 10:59 AM, bugzilla-daemon@bugzilla.kernel.org wrote: > https://bugzilla.kernel.org/show_bug.cgi?id=53231 > > > Aaron Lu <aaron.lu@intel.com> changed: > > What |Removed |Added > ---------------------------------------------------------------------------- > CC| |aaron.lu@intel.com > AssignedTo|acpi_other@kernel-bugs.osdl |aaron.lu@intel.com > |.org | > > > > > --- Comment #6 from Aaron Lu <aaron.lu@intel.com> 2013-02-18 08:59:00 --- > Hi Anderey, > > By periodically hang, do you mean it crashed after being used some time or it > stuck for a while then becoming usable again? > > And is it possible for you to test an upstream kernel, not the disto provided > kernel if you still have access to the notebook, thanks. > It just freeze. No any reaction on numlock or capslock. But notebook rebooted by sysrq+alt+b. I can't test in cause of notebook already in another company. -- Andrey Kravchina system administrator
Hi Anderey, When you have access to the notebook again, can you please test several upstream kernels and try to identify which kernel starts to have this problem and which don't? And finding out the offending commit with git-bisect would definitely help a lot. Also, you can try booting into console mode and adding nomodeset kernel parameters to see if system still hangs, thanks.