[opensuse-kernel] APEI: Invalid bit width + offset in GAR
Hi: I a remote machine, after "upgrading" it from Centos 5 to openSUSE 12.1 with kernel 3.4.1 from kernel:Stable, my logs are beign flooded with [Firmware Bug]: APEI: Invalid bit width + offset in GAR [0xbf7c4ba0/32/0/1/0] (Needless to say, I already updated the system's BIOS) thousands of times.. I couldnt care less about this APEI thing but I cannot find the right kernel parameter/ BIOS option to get it to stop flooding the system log. Any hints ? -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kernel+owner@opensuse.org
Hi Cristian, Le jeudi 07 juin 2012 à 00:43 -0400, Cristian Rodríguez a écrit :
I a remote machine, after "upgrading" it from Centos 5 to openSUSE 12.1 with kernel 3.4.1 from kernel:Stable, my logs are beign flooded with
[Firmware Bug]: APEI: Invalid bit width + offset in GAR [0xbf7c4ba0/32/0/1/0]
(Needless to say, I already updated the system's BIOS)
thousands of times.. I couldnt care less about this APEI thing but I cannot find the right kernel parameter/ BIOS option to get it to stop flooding the system log.
Any hints ?
I see the same here, it was already reported upstream: https://bugzilla.kernel.org/show_bug.cgi?id=43282 Investigation is in progress. A few patches have been submitted, but I consider them as workarounds rather than actual fixes. While this is really a BIOS bug, given that earlier kernels worked around silently, the current behavior is definitely a regression. -- Jean Delvare Suse L3 -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kernel+owner@opensuse.org
Le jeudi 07 juin 2012 à 00:43 -0400, Cristian Rodríguez a écrit :
I a remote machine, after "upgrading" it from Centos 5 to openSUSE 12.1 with kernel 3.4.1 from kernel:Stable, my logs are beign flooded with
[Firmware Bug]: APEI: Invalid bit width + offset in GAR [0xbf7c4ba0/32/0/1/0]
(Needless to say, I already updated the system's BIOS)
thousands of times.. I couldnt care less about this APEI thing but I cannot find the right kernel parameter/ BIOS option to get it to stop flooding the system log.
Any hints ?
Oh, and to answer your question: you can boot with ghes.disable=1 to avoid the log flood for now. At the cost of missing functionality, obviously, but I admit I did not yet figure out what the whole stuff was good for anyway. -- Jean Delvare Suse L3 -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kernel+owner@opensuse.org
El 07/06/12 10:57, Jean Delvare escribió:
Oh, and to answer your question: you can boot with ghes.disable=1 to avoid the log flood for now.
Thanks, that has stopped the flood with no ill efects. ;) -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kernel+owner@opensuse.org
Le jeudi 07 juin 2012 à 19:40 -0400, Cristian Rodríguez a écrit :
El 07/06/12 10:57, Jean Delvare escribió:
Oh, and to answer your question: you can boot with ghes.disable=1 to avoid the log flood for now.
Thanks, that has stopped the flood with no ill efects.
;)
Great. For the record, can you please tell us what motherboard is affected? I want to put a workaround in the upstream kernel, so the more information I have to argue, the better. -- Jean Delvare Suse L3 -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kernel+owner@opensuse.org
El 08/06/12 04:42, Jean Delvare escribió:
Le jeudi 07 juin 2012 à 19:40 -0400, Cristian Rodríguez a écrit :
El 07/06/12 10:57, Jean Delvare escribió:
Oh, and to answer your question: you can boot with ghes.disable=1 to avoid the log flood for now.
Thanks, that has stopped the flood with no ill efects.
;)
Great. For the record, can you please tell us what motherboard is affected? I want to put a workaround in the upstream kernel, so the more information I have to argue, the better.
Motherboard is Supermicro X8SIE-F with Xeon Proccessor. -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kernel+owner@opensuse.org
Cristian Rodríguez
El 08/06/12 04:42, Jean Delvare escribió:
Le jeudi 07 juin 2012 à 19:40 -0400, Cristian Rodríguez a écrit :
El 07/06/12 10:57, Jean Delvare escribió:
Oh, and to answer your question: you can boot with ghes.disable=1 to avoid the log flood for now.
Thanks, that has stopped the flood with no ill efects.
;)
Great. For the record, can you please tell us what motherboard is affected? I want to put a workaround in the upstream kernel, so the more information I have to argue, the better.
Motherboard is Supermicro X8SIE-F with Xeon Proccessor.
Same problem with Fedora 16, kernel 3.4.4-4.fc16.x86_64, thanks for the workaround, MB is ASUS dual socket with Infiniband: Manufacturer: ASUSTek Computer INC. Product Name: RS704D-E6-PS8 Davide -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kernel+owner@opensuse.org
participants (3)
-
Cristian Rodríguez -
Davide Cesari -
Jean Delvare