Y560p BIOS Bug

Hello.
I am using Linux with my y560p. We have an issue with gpe18. It is causing high CPU usage and freezes on display while system is idle.
There is a bug report on Linux Kernel: https://bugzilla.kernel.org/show_bug.cgi?id=61051
Lan Tianyu from Intel has a message there regarding this seems a hardware or Bios issue. Who can I consult is this issue about BIOS or Linux Kernel and ask for a BIOS update if possible.
Best regards.

Hi Tommy,
Tried the acpi off switch. Didn't work. In fact I redid the install with the linux acpi=off. However no luck. I switched acpi to no in BIOS too, however, no luck with that either.
The reboot issue persists with ACPI: unable to locate RSDP showing up.
Will try the to look for the USB setting in BIOS as per your suggestion and get back to you.
Ta very much,

Similar Messages

Thinkpad S540 possible BIOS bug concerning WOL

I have had a Thinkpad S540 for a few months, and have it installed as dual boot Windows 8.1 and arch linux. After completely shutting the machine down from linux I found that the battery would be down to around 70% charge after three days unused, and decided to investigate this problem since it was not reasonable for a new battery to lose charge at anything like this rate.
By chance I came across a piece of information concerning the issue of disabling WOL (Wake on LAN) on the network interface, since I had seen one report that by default WOL is enabled and this requires power to be going to the network interface even when shut down in order to be able to respond to magic packets to start the machine up when it is shut down.
First I checked the BIOS WOL setting and found it was set to "AC only" by default. So I changed it to disabled. This machine has the latest available BIOS version 1.54.
However on investigating this after rebooting in linux I found that
# cat /sys/class/net/enp3s0/device/power/wakeup
enabled
# ethtool enp3s0 | grep Wake-on
Supports Wake-on: pumbg
Wake-on: g
So WOL was still enabled despite it being set to disabled in the BIOS!
I learned that I can make sure that in arch linux the WOL setting can be changed to set to disabled after bootup by using a udev rule:
# cat 70-disable_wol.rules
ACTION=="add", SUBSYSTEM=="net", KERNEL=="enp3s0", RUN+="/usr/bin/ethtool -s enp3s0 wol d"
Then rebooting the machine I checked the WOL setting and it really is disabled now:
# ethtool enp3s0 | grep Wake-on
Supports Wake-on: pumbg
Wake-on: d
# cat /sys/class/net/enp3s0/device/power/wakeup
disabled
So I then ensured that the battery was 100% charged and shut down the machine and left it two and a half days - rebooting this morning the battery was still at 100% charge and no longer discharges unnecessarily when the machine is switched off, so this is a clear indication of a bug in the BIOS for the WOL setting - it is still enabled despite the BIOS saying it is disabled!
How do I report this to Lenovo so that they can fix the BIOS and release a new one that is working?
I am aware of other users with different Thinkpads who seem to have the same problem, so this may be more widespread an issue than just on the S540.
It is also not just an issue with the battery running down when fully shut down but will likely also be a problem for a machine in suspend mode since the network interface may be consuming a watt or so of power when in suspend, which will again run the battery down at an unacceptable rate.
I cannot imagine any use case where it would be necessary to have WOL enabled on a laptop that is mostly going to be used mobile - so having the default setting to AC only enabled, and having a BIOS bug enabling it when it is explicitely disabled is a serious problem.

Anyone running windows in the same laptop can check the same issue of battery drain due to WOl being enabled by default - in the Device Manager under the network card, opening the settings menu for the ethernet wired card the default for Wake-on-LAN on my computer was set to enabled. This can be changed to disabled, and you may need to also disable the setting for Wake on Magic Packet. Also in the Power Management tab it is possible to uncheck the settings for "Allow this device to wake the computer" and "Only allow a magic packet to wake the computer"
In my laptop these were all set to enabled by default.

U110 BIOS bug?

Dear colleagues! Just got my new U110, seen Vista to work well and trying to install Debian Linux (Lenny) in it. When booting to the Linux system, I see in the very beginning this message:
PCI: BIOS Bug MCFG area at e0000000 is not E820-reserved.
PCI: Not using MMCONFIG
PCI: Cannot allocate reseource region 98 of bridge 000000:1c.2
Further, I have problem with starting X.org using xorg-xserver-video-intel . I am not sure if the problems are related, nor do I know if the first one is serious or not. Would appreciate any suggestions or solutions to either problem.
Laura, Helsinki

Hi Tommy,
Tried the acpi off switch. Didn't work. In fact I redid the install with the linux acpi=off. However no luck. I switched acpi to no in BIOS too, however, no luck with that either.
The reboot issue persists with ACPI: unable to locate RSDP showing up.
Will try the to look for the USB setting in BIOS as per your suggestion and get back to you.
Ta very much,

I'd heard about a bios bug!

Hi guys,
my system running not allways stable!I got some bluescreens of the art "STOP COMMAND"!
Exactly this three ones:
IRQL_NOT_LESS_OR_EQUAL
PAGE_FAULT_IN_NONPAGED_AREA and
BAD_CALL_POOLER
HERE are some information about it,but sorry,it's in german!
I think that the faults causes maybe in that two ways!
Once is a Memory error,because I become sometimes error Popups,that adresses can't written or read!
I use one TwinMos Modul of PC3200,512 Mb!
At the moment I test it in slot 3 and it seems to be more stable as in slot 1!The time settings seems to be not so important,I can use either 2.5-3-3-6,or 2-3-3-6!Normal is(I'm not sure 2.5-3-3-8)!
But more important I think is,that the motherboard monitor shows me a core voltage of under 1.5V~1.48v!!!That is also the reason I mean,that I can't overclock my system over 205 MHz frontsidebus stable!In 3D Mark 3 I get instantly by the first test Wings of Fury a totaly blue screen(not the error bluescreen!Much darker and without any message!)
So I'd heard about a bug in the AMI bios,that you can't store a new core voltage!Either increase,nor decrease!My settings are on 1.55 Volt!Isn#t that the right voltage for the prozessor and if,why it isn't there a possibility to increase the core voltage for overclocking!But that is a must for a good result!I'm a little bit confused about that!The other possibility is,that my PSU is not strong enough!What for a Voltage is important for the CPU Core?I mean the 3.3V,or?My customer had said that he test the PSU and it's stable!It shall be have 32A,normaly it is enough to hold the voltage correct,but I knew that in china the electric is another as in germany!!!
Another problem is that I have change my drive from the VIA controller to the promise,because I would first test the speed and if this controller is able to read the correct monitoring data(Firmware,temperature,UDMA mode...)!The VIA doesn't do that but the promise can!And I use now together my old seagate drive on it.
Because HDTunenow show me the correct UDMA mode,I'd seen that both drives are not running at their best settings!The samsung run at UDMA5,but can run on 7 and the seagate run on UDMA2,but can do it on 5!So I would change it,but I have no idea where I can do that!In the hardware manager it isn't a possibility,neither on IDE(there is only the VIA),nor at the SCSI devices!I cannot see any settings therefor at the promise controller!And if I change the settings in bios on RAID(for S-ATA) and go into the RAID Menue with Ctrl+f on bootup,I can see keys for changing values,but their shows no result!And I think if their would working I can't use it,because with the RAID setting the computer will not boot if you don't create an array!
Has anyone some ideas???
Thank you very much!

Thanx man!
How I write it in my system specifications,I'd try to change the slot and it seems to be better with the RAM in slot 3!
But,is it my not so good english or why you did not wrote anything about the bios bug I'd heard from!Is it true that it gives a bios version with this bug,that doesn't allow to store another core voltage?Because I think that is the problem!That my core voltage is only at 1.48V,wether I changed it to 1.55V,neither if I do that in bios,nor in bios on auto and do it with core center!
What is the "normal" processor voltage?1.5 V?And if,why it gives no possibility to increase it higher than 1.55V for overclocking?What for voltage amounts are important for the processor to run stable?Only +3.3V or also the +5V and +12V amounts?
But anyway, it seems to be that the +3400 version of the processor is coming at its end of power and isn't so good to be overclocked!Better I'd bought a +3200 one I think!
But my system is also good without overclocking if I take a look at my 3DMark and Aquamark results!!:worship:
And my system isn't so old,only 2 month,but the errors comes also in the fresh system at the first days!
Greetings from good old Germany!

BIOS BUG LEGACY FREE FADT DETECTED BUT FADT SIZE (129) is incorrect

Dear all
I am using linux ES4 (ORACLE LINUX) I am getting this issue while booting pl. any one has idea on this pls. give there suggestion for the same.
BIOS BUG LEGACY FREE FADT DETECTED BUT FADT SIZE (129) is incorrect
Tks/regs
Lilly

Maybe this links will help:
https://bugzilla.redhat.com/show_bug.cgi?id=227202
BIOS bug: Legacy free FADT detected

BIOS bug: Legacy free FADT detected

Hi,
It's a new install. I get the following info on booting the machine with OEL 4 update 5-Kernel 2.6.9-55.0.0.0.2.Elsmp
BIOS bug: Legacy free FADT detected, but FADT size (129) is incorrect!
The machine keep rebooting.
Please help.
Thanks and Regards,

Hi Tommy,
Tried the acpi off switch. Didn't work. In fact I redid the install with the linux acpi=off. However no luck. I switched acpi to no in BIOS too, however, no luck with that either.
The reboot issue persists with ACPI: unable to locate RSDP showing up.
Will try the to look for the USB setting in BIOS as per your suggestion and get back to you.
Ta very much,

T440s fn ctrl swap bios bug

Hi,
I think this was documented before, but I am now experiencing the fn ctrl swap bug when going to sleep.
I have swapped my fn and ctrl keys, and the setting never stays after resuming from deep sleep.
I have updated my bios to the latest version (2.19) but it has not fixed it.
Please advise. I do not want to turn off deep sleep.
Cheers
Solved!
Go to Solution.

Thank you for reporting this. Yes, I can confirm it is BIOS bug. We had this same issue on T430 generation and fixed it. But now it seems T440 generation also suffers from this same bug, needs fix. So I will report this to BIOS team. Sorry for this inconvenience.

Help---MSI KT4AV bios BUG ?!

Hi....(excuse my bad english... ) I try...
I have the MB MSI - KT4AV
two days ago , I have buy a AMD CPU 3200 Ghz , 32bit ofcourse, Inside the shop have sayed to me...no problems with this MB !!!
well I try , but I can't go UP 2800+ !!!
I try and Try with BIOS but no result.
I have read with the last BIOS is corretc the right recognised 3Ghz+ cpu...
I have update BUT always thesame.
So I have read arround, this MB can't support CPU uo 3Ghz !... so never 3,2 ...ok..but MY not go up 2,8 !!!!
BIOS setting....and here is the Myseriuos!!!
FSB...I can't select UP 170 or the PC non start , amnd I must reset the cmos/bios!
(200 I can't forget...I can work with 166.....)
MOLTIPLIC. I can set to x12.13 and My pc (166 - x12.13) give 2800
BUT....If i select x14 I became 880 Mhz !!! and if I set x 15 984 Mhz!!!!!!!
Why ?!?!? this is sure a bios bug....

impossible....sure NEVER He take back!!... later I used and Try.... sure I became in the...A..!
well IF this CPU is not supported WHY work and to 2800 ?!? work or not work....
and WHY x14 give the IDOT nummer 880 Mhz and x15 980 Ghz ? this is ONLY a BIOS problem.... to fixit!!!
so..I not belive MSI have not to do, with this bios...

Post Code 9A Error, 990FXA-GD80, Bios bug

After Bios B.40 i got same strange bug, sometimes when i load a oc profile my pc get stuck at 9A error and the only thing that i can do to recovery is use ctrl+home to recovery it, clear cmos is unless.
After a lot of tests to try understand what was happening i got the answer.
My CPU is a X3 710 (waiting for bulldozers) so i always use the unlock cpu core feature. I used this x3 with unlocked core for 2 years without any problem, so the locked core is good.
If i load a oc profile with unlock cpu core feature enabled from a already unlocked stage, everyting is ok, but if my bios seting "unlock cpu core" is disabled and i load a oc profile with it enabled my pc do 6 beeps, restart and get stuck at 9A post code.
I have sure that in Bios B.30 this wasnt happening.
MB: MSI 990FXA-GD80 (MS-7640)
BIOS: V11.5 (B.50)
CPU: Phenom X3 710
RAM: 2x2GB Corsair XMS3
VGA: ATI Radeon HD 4890 (RV790) 1GB
DISK1: 120 GB OCZ-VERTEX3 SATAIII SSD
DISK2: 3TB Hitachi HDS5C3030ALA630 SATAIII HDD
Optical Drive: SAMSUNG TSSTcorp CDDVDW SH-222AB SATA
Power Supply: GenieX 800 Watts
OS: WIndows 7 Ultimate Sp1

Guy, did u see me asking anything about overclock?
I was talking about a bios BUG that can damage the mainboard, and a lot of ppl cant recovery their bios like i did.
I posted to help ppl with same issue and alert others to avoid it.
I informed MSI about it using the right channel.
Ty for help me bump this topic.
Quote from: Fredrik on 26-September-11, 06:52:23
Hello!
Overclocking questions go somewhere else.
If you don't absolutely need to update BIOS to solve a problem, resist the temptation.
And if you do... Go back to the version that made you smile!
We ask people to state the max ampères the PSU can do. There is a list on the PSU box.

S10-3T BIOS bug?

We have purchased four Lenovo S10-3T (product code ********, greek version) and all four have the same problem:
Out of the box and on first boot, two BIOS issues appear:
ERROR 271Check Date and Time setting
WARNING 251 System CMOS checksum bad - Default configuration used
When you hit F2 to setup, a password is required - although no password has been set. A blank password doesn't work.
When you exit the setup (without entering the actual settings due to the password protection) , Windows first time setup continues with installation and creation of user account etc.
When I retry to enter BIOS Setup, the password prompt always appears.
Also have a look below at the screenshot.
Is it a BIOS bug which enables a supervisor password, or maybe a backup battery issue?
link to image
image(s) >50k converted to link(s) & serial number removed

as raggedrebel92 suggested, contact lenovo support line.

Lenovo Thinkpad T520 doesn't boot with GPT slices on FreeBSD 9-BETA3 - BIOS bug?

Hi!
I've bought a brand new Lenovo Thinkpad T520 laptop and decided to install FreeBSD 9 Beta 3 following this guide.
But when I rebooted the system, it simply doesn't boot (turns out to the BIOS boot menu).
It's even doesn't boot with default FreeBSD 9 UFS-on-GPT installation scheme through bsdInstaller
Changing BIOS (latest, 1.31) settings BIOS Startup->UEFI/Legacy Boot from "Both" to "Legacy only" has no effect. As FreeBSD AFAIK doesn't support UEFI boot, legacy boot should work picking up and starting pmbr (protected MBR record), but it doesn't.
However, FreeBSD 9 UFS-on-MBR installation (with mbr boot record and FreeBSD slice in MBR partition instead of GPT) works fine.
It seems to me that UEFI/Legacy Boot "Legacy" setting actually has no effect if 0xEE type Primary partition entry is present on disk.
First of all, has anyone installed Linux or FreeBSD with GPT partitioning scheme on latest Thinkpads?
And the second one, as I've saw similar problem on FreeBSD forum thread about T420s laptop I believe that this may be a bug in the BIOS. How can I fill the bugreport or send an e-mail to support or developers, as, obvious, phone support can consult only about Windows OS.

Volker1 wrote:
I've got a suspicion that the Thinkpad bios/efi is not simply executing the first stage bootloader, but looking around on the GPT disk and then crapping its pants when it doesn't find Windows.
Right now I have a MBR-formatted harddisk in the ultrabay with the bootloader in the MBR. Once I get the bootloader off the MBR disk, I can easily continue to boot from my GPT-formatted SSD.
Yes, it seems that it's a BIOS bug at least on T520, T420s and W520 laptops. Even in "Legacy" mode first stage bootloader doesn't execute if partition type is 0xEE (GPT).
Hope Lenovo developers will fix it. They fixed something on BIOS 1.31
[Problem fixes]
- Fixed an issue where the computer might not be booted from bootloader program.
but it doesn't work for now. Pity.

K8N Neo FSR, possible BIOS bug: setting Vcore with Cool'n Quiet enabled broken?

Athlon 64 3400+, socket 754
K8N Neo FSR, Pheonix-Award BIOS V1,5
WinXP SP2
Having Cool'n Quiet disabled in BIOS setup, CPU core voltage adjustment
using 'Adjust CPU VID' below the Athlon 64 default 1,5V core voltage
works like a charm. Fine!
But with Cool'n Quiet enabled in BIOS setup (and WinXP), under load the
CPU core voltage raises to 1,5V in any case, independently of what I did
define in BIOS setup with 'Adjust CPU VID' (e.g. 1,4V). Software tools setting
Vcore like Core Center are not running.
So I can choose to either run a silent system in idle mode with Cool'n Quiet
enabled or under heavy CPU load with Cool'n Quiet disabled but Vcore
reduced :-( Am I missing something or does it rather look like a BIOS
bug?
Greetings, Falo

Quote from: Tiresmoke on 21-March-05, 00:19:19
As undervolting is not considured standard operating proceedures then how can it be considured a bug.
nor is overclocking but MSI mobo manual reads 'This motherboard is designed to support overclocking.'
So this mobo is designed for supporting at least one non standard operating procedure
Seriously, if BIOS offers a feature I suppose it to work as expected.
regards, Falo

[BIOS Bug] Enabling Fn/Ctrl swap breaks [Ctrl]-[Alt]-[Up]

Hello all!
I'm very used to the standard keyboard layout, where the ctrl key is on the very left. Therefore I enabled the Swap Fn/Ctrl key option in the BIOS of my Lenovo Edge 11 AMD (2545A12, Bios 1.08).
Unfortunately this has the effect, that a very specific key combination is no longer working: Ctrl+Alt+Up
Ctrl-Alt-Down/Left/Right keep working as ususal. The problem does not happen with disabled key swap option.
This clearly seems to be a bug to me. Any hints on how to receive a fix?
Thanks & Regards
- Ben

I doubt this is a software/Linux problem. Same effect here under Fedora 15/Gnome: There this key combination is the essential as the desktop is only vertically oriented.
Can anybody try to assign this key combination in Windows, enable Fn/Ctrl swap and report if he shares the problem there?

Second battery does not report status correct - probably BIOS bug

Hi,
I have a T61 laptop and recently bought a second battery (for the CD drive slot).
The problem is, the status of the second battery is not properly reported. Sometimes it doesn't show the status (charging, discharging etc.), sometimes even not the capacity. This is a problem, as this can cause my laptop to shut down when one battery is running out of power, while the other is still full.
This happens both in windows and linux. You can see some more details here:
https://bugzilla.kernel.org/show_bug.cgi?id=17832
I'm pretty sure that this is a bug in the BIOS. Is there any way I can contact the people who are working on the BIOS? I tried to use the web support form to get in contact, but the support told me to contact the nearest service center - not very helpful.

On its home page http://www.ngolde.de/yacpi.html is a mention that there may possibly problems with battery status. You should probably try to contact the developer.

URGENT!!! Bios Bug found for P500 series BIOS v2.90. TAIS really needs to fix this!!

Affected unit: P500-ST6844 PSPGSU-0Q2012
I have had sleep issues with my laptop since I first purchased it back in 2010. I have made a previous post about it here: http://forums.toshiba.com/t5/Batteries-and-Power/Laptop-turns-off-instead-of-going-to-sleep/m-p/3101...
I recently found some some helpful troubleshooting documents for windows 7 power management on the Microsoft website. One of the utilities it suggested to use is the PWRTEST.exe included Windows driver SDK. Running PWRTEST /sleep /s:4 results in a successful Hibernate cycle, however running PWRTEST /sleep /s:3 results in:
NO.0 Transition--TargetState: S3
Error: Pwrtest tracing might be buffer overflow, and the data of this power is discarded.
    File: d:\5359\base\power\tools\pwrtest\exe\pstrace.cpp
    Line: 1653
    Error Code: 0xc0000001
importing pwrtest.etl created by the utility into the event viewer reveals bunch of these errors:
Unexpected GPE event was fired on GPE bits that should be disabled.
- <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
- <System>
<Provider Name="Microsoft-Windows-Kernel-Acpi" Guid="{c514638f-7723-485b-bcfc-96565d735d4a}" />
<EventID>2</EventID>
<Version>0</Version>
<Level>4</Level>
<Task>101</Task>
<Opcode>0</Opcode>
<Keywords>0x8000000000000001</Keywords>
<TimeCreated SystemTime="2012-12-23T03:10:45.894731800Z" />
<EventRecordID>4045</EventRecordID>
<Correlation />
<Execution ProcessID="0" ThreadID="0" ProcessorID="3" KernelTime="1572689" UserTime="0" />
<Channel />
<Computer>ChrisSolomon-PC</Computer>
<Security />
</System>
- <EventData>
<Data Name="GpeRegister">3</Data>
<Data Name="UnexpectedEventMap">142</Data>
</EventData>
</Event>
as well as this error :
Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
- <System>
<Provider Name="" Guid="{f2e0e060-bf32-4b88-b8e4-5cad15af6ae9}" />
<EventID>0</EventID>
<Version>0</Version>
<Level>1</Level>
<Task>0</Task>
<Opcode>2</Opcode>
<Keywords>0x0</Keywords>
<TimeCreated SystemTime="2012-12-23T03:10:45.852354300Z" />
<EventRecordID>4043</EventRecordID>
<Correlation />
<Execution ProcessID="5644" ThreadID="3088" ProcessorID="0" KernelTime="1925" UserTime="1240" />
<Channel />
<Computer>ChrisSolomon-PC</Computer>
<Security />
</System>
- <ProcessingErrorData>
<ErrorCode>15003</ErrorCode>
<DataItemName />
<EventPayload>4F626A656374203D205C5F53422E545641502E5350464300</EventPayload>
</ProcessingErrorData>
</Event>
doing reasearch on the first error reveals that this is caused by a bug in the BIOS.
the bug causes either one of two things two happen P500 does not enter Sleep (S3) properly, or when S3 is attempted the unit appears to enter S3 successfully, and the led sleep indicator blinks, but when trying to resume from S3, unit starts up from an off state and hangs after Toshiba bios screen is displayed. normal boot operation only occurs after forcing a power down and restarting unit.

Anyone running windows in the same laptop can check the same issue of battery drain due to WOl being enabled by default - in the Device Manager under the network cards, opening the settings menu for the ethernet wired card the default for Wake-on-LAN on my computer was set to enabled. This can be changed to disabled, and you may need to also disable the setting for Wake on Magic Packet. Also in the Power Management tab it is possible to uncheck the settings for "Allow this device to wake the computer" and "Only allow a magic packet to wake the computer"
In my laptop these were all set to enabled by default.

Y560p BIOS Bug

Similar Messages

Maybe you are looking for