You are not logged in.
Pages: 1
OK. In this thread we all help me to get rid of errors system writes to console, logs, etc.
Model: Samsung NP350U2B
Let's see:
[ 0.000000] Notice: NX (Execute Disable) protection cannot be enabled: non-PAE kernel!
[ 0.000000] ACPI Warning: 32/64 FACS address mismatch in FADT - two FACS tables! (20120913/tbfadt-394)
[ 0.000000] ACPI BIOS Bug: Warning: 32/64X FACS address mismatch in FADT - 0xDAFE5E40/0x00000000DAFE5D40, using 32 (20120913/tbfadt-521)
[ 0.247811] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
[ 0.684279] \_SB_.PCI0:_OSC invalid UUID
[ 0.692500] \_SB_.PCI0:_OSC invalid UUID
[ 0.692504] pci0000:00: ACPI _OSC support notification failed, disabling PCIe ASPM
[ 0.692506] pci0000:00: Unable to request _OSC control (_OSC support mask: 0x08)
[ 0.705397] ACPI Error: Invalid/unsupported resource descriptor: Type 0x00 (20120913/utresrc-650)
[ 0.705402] pnp 00:01: can't evaluate _CRS: 12311
[ 7.407628] mei 0000:00:16.0: wd: failed to find the client
[ 7.428964] ACPI Warning: 0x00000428-0x0000042f SystemIO conflicts with Region \PMIO 1 (20120913/utaddress-251)
[ 7.428973] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
[ 7.428978] ACPI Warning: 0x00000540-0x0000054f SystemIO conflicts with Region \GPIO 1 (20120913/utaddress-251)
[ 7.428983] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
[ 7.428986] ACPI Warning: 0x00000530-0x0000053f SystemIO conflicts with Region \GPIO 1 (20120913/utaddress-251)
[ 7.428990] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
[ 7.428993] ACPI Warning: 0x00000500-0x0000052f SystemIO conflicts with Region \GPIO 1 (20120913/utaddress-251)
[ 7.428997] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
[ 7.429000] lpc_ich: Resource conflict(s) found affecting gpio_ich
[ 7.598065] ACPI: Invalid active2 threshold
[ 8.157544] ACPI Warning: 0x0000e040-0x0000e05f SystemIO conflicts with Region \_SB_.PCI0.SBUS.SMBI 1 (20120913/utaddress-251)
[ 8.157558] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
So, any help and advice how to fix all the things if possible?
Last edited by eruditorum (2013-02-10 09:59:08)
Offline
It may be off-topic, but I'm also interested why beautiful and clear "eth0" and "wlan0" were renamed to ugly "enp*" and "wlp*"?
Offline
OK. In this thread we all help me to get rid of errors system writes to console, logs, etc.
Then please name the thread appropriately.
Re: your error messages, Samsung users are intimately familiar with that companies habit of producing firmware that writes to odd address locations...
Offline
I don't boot with UEFI. Laptop isn't "bricked" at all. And kernel doesn't panic during runtime. I just want to want to fix messages which are annoying.
Last edited by eruditorum (2013-02-10 05:30:14)
Offline
I don't boot with UEFI. Laptop isn't "bricked" at all. And kernel doesn't panic during runtime. I just want to want to fix messages which are annoying.
I wasn't suggesting any of the above: I was pointing out that this is symptomatic of Samsung's cavalier approach to firmware and that the errors are probably beyond your control...
Offline
Well, can I do anything except getting laptop with a nicer firmware?
Offline
I don't know; have you searched for similar issues, bug reports and the like?
Is there any impact on your machine's performance, or are the messages purely cosmetic?
Does enabling more verbose logging provide any more details about the error messages?
Is the dmesg error related to the other errors you are describing (but not pasting)?
And, if you have read this far, you might want to read this:
How To Ask Questions The Smart Way
Offline
EDIT:
journald was always trying to write something (coredumps, etc.) into "/var" before it was mounted, so I unmounted var and deleted everything in this directory.
systemd errors are cured now.
OKAY. ACPI is totally broken on this system. Then still, what is this:
[ 7.407628] mei 0000:00:16.0: wd: failed to find the client
?
jason, no crashes. These errors simply don't look pretty. Also, I have no "lpc_ich: Resource conflict(s) found affecting iTCO_wdt" which is seen in your link. Just gpio conflict.
Thanks :]
Last edited by eruditorum (2013-02-10 10:10:44)
Offline
Oh, noes!
I also see that sometimes laptop just reboots instead of resuming from hibernation.
Anyone knows what is that? :[
Last edited by eruditorum (2013-02-13 11:32:58)
Offline
And, if you have read this far, you might want to read this:
How To Ask Questions The Smart Way
*sigh*
Perhaps a different approach is needed.
If read this far
read: How To Ask Questions The Smart Way
else
read anyway: How To Ask Questions The Smart Way
fi
EDIT: This link is not to give you the runaround or to ignore your issues. It is a genuine attempt to help you learn to present the problems you are facing in a way that will be most conducive to finding solutions. Your present style of posting is not likely to lead to solutions. If you are offended by my lighthearted pokes, know that offense was not the goal ... but poking was. It would be easy to ignore posts that were not productive - but ignoring them would be equally unproductive (for everyone).
Last edited by Trilby (2013-02-13 13:16:27)
"UNIX is simple and coherent..." - Dennis Ritchie, "GNU's Not UNIX" - Richard Stallman
Offline
Pages: 1