Modify UEFI anti-bricking code

Bug #1199401 reported by Luis Henriques
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Fix Released
Medium
Unassigned
Precise
Fix Released
Medium
Unassigned
Quantal
Fix Released
Medium
Luis Henriques
Raring
Fix Released
Medium
Unassigned

Bug Description

Ubuntu kernels have already been SRU'ed (bug #1040557) to mitigate the problem of UEFI machines being bricked by nvram being filled up. However, this problem is still present and a recent upstream fix has been accepted in mainline:

f8b8404337de4e2466e2e1139ea68b1f8295974f Modify UEFI anti-bricking code

This fix should be backported to Ubuntu kernels, starting with Precise.

ProblemType: Bug
DistroRelease: Ubuntu 12.10
Package: linux-image-3.5.0-37-generic 3.5.0-37.58
ProcVersionSignature: Ubuntu 3.5.0-37.58-generic 3.5.7.16
Uname: Linux 3.5.0-37-generic x86_64
ApportVersion: 2.6.1-0ubuntu12
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC1: miguel 2073 F.... pulseaudio
 /dev/snd/controlC0: miguel 2073 F.... pulseaudio
CRDA: Error: [Errno 2] No such file or directory: 'iw'
Date: Tue Jul 9 16:00:44 2013
HibernationDevice: RESUME=UUID=a6251583-fdd9-4246-8677-7a470ac9e219
InstallationDate: Installed on 2013-03-20 (110 days ago)
InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Alpha amd64 (20120808)
MachineType: TOSHIBA Satellite A210
MarkForUpload: True
PccardctlIdent:
 Socket 0:
   no product info available
PccardctlStatus:
 Socket 0:
   no card
ProcFB: 0 radeondrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-37-generic root=UUID=fcec33e6-2066-4bf1-879c-0389d0b4947d ro
RelatedPackageVersions:
 linux-restricted-modules-3.5.0-37-generic N/A
 linux-backports-modules-3.5.0-37-generic N/A
 linux-firmware 1.95.1
RfKill:
 0: phy0: Wireless LAN
  Soft blocked: no
  Hard blocked: no
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 06/10/2008
dmi.bios.vendor: TOSHIBA
dmi.bios.version: V2.00
dmi.board.name: IALAA
dmi.board.vendor: TOSHIBA
dmi.board.version: 1.00
dmi.chassis.asset.tag: *
dmi.chassis.type: 10
dmi.chassis.vendor: TOSHIBA
dmi.chassis.version: N/A
dmi.modalias: dmi:bvnTOSHIBA:bvrV2.00:bd06/10/2008:svnTOSHIBA:pnSatelliteA210:pvrPSAELE-04R01GPT:rvnTOSHIBA:rnIALAA:rvr1.00:cvnTOSHIBA:ct10:cvrN/A:
dmi.product.name: Satellite A210
dmi.product.version: PSAELE-04R01GPT
dmi.sys.vendor: TOSHIBA

Revision history for this message
Luis Henriques (henrix) wrote :
Revision history for this message
Brad Figg (brad-figg) wrote : Status changed to Confirmed

This change was made by a bot.

Changed in linux (Ubuntu):
status: New → Confirmed
Changed in linux (Ubuntu Precise):
status: New → Confirmed
Changed in linux (Ubuntu Quantal):
status: New → Confirmed
Changed in linux (Ubuntu Raring):
status: New → Confirmed
Luis Henriques (henrix)
Changed in linux (Ubuntu Quantal):
assignee: nobody → Luis Henriques (henrix)
Changed in linux (Ubuntu):
importance: Undecided → Medium
Changed in linux (Ubuntu Precise):
importance: Undecided → Medium
Changed in linux (Ubuntu Raring):
importance: Undecided → Medium
Changed in linux (Ubuntu Quantal):
importance: Undecided → Medium
Revision history for this message
Luis Henriques (henrix) wrote :

Kernels currently in -updates (3.2.0-52.78, 3.5.0-39.60 and 3.8.0-29.42) already contain this fix. Changing to 'fix released'.

Changed in linux (Ubuntu Quantal):
status: Confirmed → Fix Released
Changed in linux (Ubuntu Precise):
status: Confirmed → Fix Released
Changed in linux (Ubuntu Raring):
status: Confirmed → Fix Released
penalvch (penalvch)
Changed in linux (Ubuntu):
status: Confirmed → Triaged
Revision history for this message
penalvch (penalvch) wrote :

Luis Henriques, closing out the linux (Ubuntu) general task as this would appear completed already in Saucy+ as per:
http://kernel.ubuntu.com/git?p=ubuntu/ubuntu-saucy.git;a=commit;h=cb03dc094ad4bfb8223d02b28e2374c51e4c31fb

Changed in linux (Ubuntu):
status: Triaged → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.