Author Topic: Blog: Linux Bricks Some UEFI Samsung Laptops  (Read 343 times)

Offline menotu

  • PCLinuxOS Tester
  • Super Villain
  • *******
  • Posts: 15316
  • ┌∩┐(◕_◕)┌∩┐
Blog: Linux Bricks Some UEFI Samsung Laptops
« on: January 31, 2013, 06:21:42 AM »
Posted by Michael Larabel on January 30, 2013

Generating a fair amount of attention today is word that when booting modern versions of Ubuntu -- and other Linux distributions -- on Samsung laptops that utilize UEFI, Linux can actually brick the system. There's now an urgent Linux kernel patch underway. The Samsung UEFI Linux bricking issue has been known going back to last summer per LaunchPad Bug 1040557:

I cannot provide detailed log massages because laptop is bricked right now.

f you have courage to try it select UEFI boot from bios and than try to boot laptop using liveusb (made form Precise Pangolin 12.04.1 amd64).

Laptop hangs up in black screen. If you force power-off, after it, laptop wont start. I mean it not event start bios, just black screen no sounds nothing.

I filing this report, because i already bricked second laptop. At first i thought it was unrelated issue and laptop was fixed by warranty service (replaced motherboard), but after second time i quite sure.


Others have confirmed this issue too and it's affected both Ubuntu 12.04 and Ubuntu 12.10. The aforementioned bug report has been very active going back to last summer and it's accumulated more than 129 comments and confirmation of the issue affecting at least three dozen users and likely many more.

Hitting the kernel mailing list just now is an urgent patch for disabling samsung-laptop on EFI hardware. "It has been reported that running this driver on some Samsung laptops with EFI can cause those machines to become bricked."

The samsung-laptop Linux kernel driver has been reported to cause Machine Check Exceptions, so the workaround for now is disabling it from being used on EFI-enabled Samsung laptops. That's it for now.

http://www.phoronix.com/scan.php?page=news_item&px=MTI4ODQ
PCLinuxOS 32bit KDE 4.10.1; kernel-3.4.11-pclos1.bfs & 64bit 3.2.18bfs; NVidia GeForce 8400GS 1GB 310.19 driver

Sony Vaio SVE1513A4ESI Laptop, Intel Core i5, 2.6GHz, 6GB RAM, 750GB, 15.6" Intel HD Graphics 4000

Offline pags

  • Hero Member
  • *****
  • Posts: 2519
  • Keep it clean.
Re: Blog: Linux Bricks Some UEFI Samsung Laptops
« Reply #1 on: January 31, 2013, 08:39:38 AM »
 :o

Hopefully the fix will flow down soon...wouldn't want to be seen as "copying" the practices of some (unnamed) proprietory companies...

Online Just17

  • PCLinuxOS Tester
  • Super Villain
  • *******
  • Posts: 10690
  • MLUs Forever!
Re: Blog: Linux Bricks Some UEFI Samsung Laptops
« Reply #2 on: January 31, 2013, 09:00:55 AM »
Quote
The Samsung UEFI Linux bricking issue has been known going back to last summer per LaunchPad Bug 1040557:

What the !@#$

Why did it take until now to disable it?  Meanwhile lots of people have had their laptops bricked!

MLUs rule the roost!

Linux XPS 3.4.38-pclos1.bfs  64 bit
Intel Core2 Quad CPU Q9450 @ 2.66GHz
4 GB RAM
MCP51 High Def Audio
GeForce GTX 550 Ti
PHILIPS  ‎DVD+-RW DVD8701
‎Logitech ‎BT Mini-Receiver
Afatech DTT

Online Just17

  • PCLinuxOS Tester
  • Super Villain
  • *******
  • Posts: 10690
  • MLUs Forever!
Re: Blog: Linux Bricks Some UEFI Samsung Laptops
« Reply #3 on: February 10, 2013, 03:58:17 AM »
It appears it is not only Linux that bricks this laptop .......  Windows does too!

http://hardware.slashdot.org/story/13/02/09/2146207/samsung-laptop-bug-is-not-linux-specific


Quote
Matthew Garrett, a Linux kernel developer who was investigating the recent Linux-on-Samsung-in-UEFI-mode problem, has bricked a Samsung laptop using a test userspace program in Windows. The most fascinating part of the story is on what is actually causing the firmware boot failure: 'Unfortunately, it turns out that some Samsung laptops will fail to boot if too much of the [UEFI] variable storage space is used. We don't know what "too much" is yet, but writing a bunch of variables from Windows is enough to trigger it. I put some sample code here — it writes out 36 variables each containing a kilobyte of random data. I ran this as an administrator under Windows and then rebooted the system. It never came back.'"


Details here


http://mjg59.dreamwidth.org/22855.html
MLUs rule the roost!

Linux XPS 3.4.38-pclos1.bfs  64 bit
Intel Core2 Quad CPU Q9450 @ 2.66GHz
4 GB RAM
MCP51 High Def Audio
GeForce GTX 550 Ti
PHILIPS  ‎DVD+-RW DVD8701
‎Logitech ‎BT Mini-Receiver
Afatech DTT