Bug#695328: marked as done ([testing/wheezy] UEFI installed system fails to boot)

[Debian Bug Tracking System]

Your message dated Fri, 1 Mar 2013 23:47:26 -0800
with message-id <20130302074726.gy13...@kenyonralph.com>
and subject line giving up for now
has caused the Debian Bug report #695328,
regarding [testing/wheezy] UEFI installed system fails to boot
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
695328: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=695328
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: installation-reports

Boot method: USB memory stick

Image version: 
http://cdimage.debian.org/cdimage/daily-builds/daily/arch-latest/amd64/iso-cd/debian-testing-amd64-netinst.iso
dated 2012-12-07T04:21

Date: 2012-12-07T22:00-08:00

Machine: Intel DH77EB motherboard, latest firmware, version 0097 (dated 
2012-10-31)
Processor: Intel Core i7-3770
Memory: 32 GB
Partitions: the installer's "use the whole disk" default (efi boot
partition, ext4 root, swap)

Output of lspci -knn (or lspci -nn): (output taken using grml 2012.05)
00:00.0 Host bridge [0600]: Intel Corporation 3rd Gen Core processor DRAM 
Controller [8086:0150] (rev 09)
Subsystem: Intel Corporation Device [8086:2032]
Kernel driver in use: agpgart-intel
00:02.0 VGA compatible controller [0300]: Intel Corporation 3rd Gen Core 
processor Graphics Controller [8086:0162] (rev 09)
Subsystem: Intel Corporation Device [8086:2032]
Kernel driver in use: i915
00:14.0 USB controller [0c03]: Intel Corporation 7 Series Chipset Family USB 
xHCI Host Controller [8086:1e31] (rev 04)
Subsystem: Intel Corporation Device [8086:2032]
Kernel driver in use: xhci_hcd
00:16.0 Communication controller [0780]: Intel Corporation 7 Series Chipset 
Family MEI Controller #1 [8086:1e3a] (rev 04)
Subsystem: Intel Corporation Device [8086:2032]
00:19.0 Ethernet controller [0200]: Intel Corporation 82579V Gigabit Network 
Connection [8086:1503] (rev 04)
Subsystem: Intel Corporation Device [8086:2032]
Kernel driver in use: e1000e
00:1a.0 USB controller [0c03]: Intel Corporation 7 Series Chipset Family USB 
Enhanced Host Controller #2 [8086:1e2d] (rev 04)
Subsystem: Intel Corporation Device [8086:2032]
Kernel driver in use: ehci_hcd
00:1b.0 Audio device [0403]: Intel Corporation 7 Series Chipset Family High 
Definition Audio Controller [8086:1e20] (rev 04)
Subsystem: Intel Corporation Device [8086:2032]
Kernel driver in use: snd_hda_intel
00:1d.0 USB controller [0c03]: Intel Corporation 7 Series Chipset Family USB 
Enhanced Host Controller #1 [8086:1e26] (rev 04)
Subsystem: Intel Corporation Device [8086:2032]
Kernel driver in use: ehci_hcd
00:1f.0 ISA bridge [0601]: Intel Corporation H77 Express Chipset LPC Controller 
[8086:1e4a] (rev 04)
Subsystem: Intel Corporation Device [8086:2032]
00:1f.2 SATA controller [0106]: Intel Corporation 7 Series Chipset Family 
6-port SATA AHCI Controller [8086:1e02] (rev 04)
Subsystem: Intel Corporation Device [8086:2032]
Kernel driver in use: ahci
00:1f.3 SMBus [0c05]: Intel Corporation 7 Series Chipset Family SMBus 
Controller [8086:1e22] (rev 04)
Subsystem: Intel Corporation Device [8086:2032]


Base System Installation Checklist:
[O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it

Initial boot:   [O]
Detect network card:[O]
Configure network:  [O]
Detect CD:  [ ]
Load installer modules: [O]
Detect hard drives: [O]
Partition hard drives:  [O]
Install base system:[O]
Clock/timezone setup:   [O]
User/password setup:[O]
Install tasks:  [O]
Install boot loader:[O]
Overall install:[E]

Comments/Problems:

Installer booted into EFI bootloader, and I used the graphical
installer. Installation goes fine, but the resulting system does not
boot. The computer acts as if there is no bootable disk ("please
insert boot disk").

Ubuntu 12.10 installs and boots using UEFI fine. I suspect a problem
with the EFI NVRAM boot entry that the Debian Installer creates, as
reported by efibootmgr. It looked quite different from what Ubuntu
created (unfortunately I didn't save the output), but I think the
Ubuntu entry had a /boot/efi path in it.

The motherboard is set to the default of "try EFI booting first, and
fall back to legacy BIOS".

Booting into rescue mode and running modprobe efivars ; efibootmgr
--verbose gives this output:

BootCurrent: 0003
Timeout: 1 seconds
BootOrder: ,0003,0001,0002
Boot* debianVendor(99e275e7-75a0-4b37-a2e6-c5385e6c00cb,)
Boot0001* SATA : PORT 6G 0 : INTEL SSDSC2CW120A3

Processed: retitle 696658 to task-print-server: rename to "Support for local printer / print server".

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> retitle 696658 task-print-server: rename to "Support for local printer / 
> print server".
Bug #696658 [tasksel] Everything worked fine, well done!
Changed Bug title to 'task-print-server: rename to "Support for local printer / 
print server".' from 'Everything worked fine, well done!'
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
696658: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=696658
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems


--
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/handler.s.c.136220898721479.transcr...@bugs.debian.org

Debian installer build: failed or old builds

[Daily build aggregator]

Debian installer build overview
---

Failed or old builds:

* OLD BUILD:s390x Feb 27 00:01 buildd@zemlinsky build_generic 
http://d-i.debian.org/daily-images/s390x/daily/build_generic.log

* OLD BUILD:s390x Feb 27 00:01 buildd@zemlinsky build_tape 
http://d-i.debian.org/daily-images/s390x/daily/build_tape.log


Totals: 99 builds (0 failed, 2 old)


-- 
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/e1ubanz-0001ho...@ravel.debian.org

Bug#702021: debian wheezy not booting

[Piotrek]

Package: installation-reports

Boot method: 
Image version: 

Date: <01.03.2013>

Machine: 
Processor:i5 3210
Memory:4gb


Base System Installation Checklist:
[O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it

Initial boot:   [e ]
Detect network card:[ ]
Configure network:  [ ]
Detect CD:  [ ]
Load installer modules: [ ]
Detect hard drives: [ ]
Partition hard drives:  [ ]
Install base system:[ ]
Clock/timezone setup:   [ ]
User/password setup:[ ]
Install tasks:  [ ]
Install boot loader:[ ]
Overall install:[ ]

Comments/Problems:

Spam cleaning effort: February 2013

[Christian PERRIER]

We're now in March, so it's time for our team of magic reviewers to
work on February 2013 archives.
 
More details on http://wiki.debian.org/DebianInstaller/SpamClean



signature.asc
Description: Digital signature

Processed: user release.debian....@packages.debian.org, tagging 694928, usertagging 694928, tagging 694986 ...

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> user release.debian@packages.debian.org
Setting user to release.debian@packages.debian.org (was 
jcris...@debian.org).
> tags 694928 + wheezy-ignore
Bug #694928 [flash-kernel] flash-kernel: postinst modifies /etc/default/rcS
Added tag(s) wheezy-ignore.
> usertags 694928 wheezy-can-defer
There were no usertags set.
Usertags are now: wheezy-can-defer.
> tags 694986 + wheezy-ignore
Bug #694986 [initscripts] flash-kernel: postinst modifies /etc/default/rcS
Added tag(s) wheezy-ignore.
> usertags 694986 wheezy-can-defer
There were no usertags set.
Usertags are now: wheezy-can-defer.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
694928: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=694928
694986: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=694986
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems


--
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/handler.s.c.136214473325599.transcr...@bugs.debian.org

Processed: severity of 700976 is important

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> severity 700976 important
Bug #700976 [installation-reports] debian-installer: Failed to boot installed 
UEFI system
Severity set to 'important' from 'critical'
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
700976: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=700976
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems


--
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/handler.s.c.136214455024192.transcr...@bugs.debian.org

Processed: severity of 700656 is important

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> severity 700656 important
Bug #700656 [installation-reports] installation-reports: Corrupt screens after 
grub menu with UEFI
Severity set to 'important' from 'critical'
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
700656: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=700656
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems


--
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/handler.s.c.136214453624095.transcr...@bugs.debian.org

Processed: severity of 683705 is normal

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> severity 683705 normal
Bug #683705 [installation-reports] installation-report: Installer failing to 
boot from known-good media on known-good hardware
Severity set to 'normal' from 'grave'
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
683705: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=683705
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems


--
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/handler.s.c.136214440323049.transcr...@bugs.debian.org

Processed: Re: Bug#690046: installation-reports: System unstable, page faults on A4-3300 APU

[Debian Bug Tracking System]

Processing control commands:

> tag -1 moreinfo
Bug #690046 [installation-reports] installation-reports: System unstable, page 
faults on A4-3300 APU
Added tag(s) moreinfo.
> severity -1 important
Bug #690046 [installation-reports] installation-reports: System unstable, page 
faults on A4-3300 APU
Severity set to 'important' from 'critical'

-- 
690046: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=690046
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems


--
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/handler.s.b690046.136214451824007.transcr...@bugs.debian.org

Bug#690046: installation-reports: System unstable, page faults on A4-3300 APU

[Julien Cristau]

Control: tag -1 moreinfo
Control: severity -1 important

On Tue, Oct  9, 2012 at 14:24:07 +0100, Fred wrote:

> Package: installation-reports
> Severity: critical
> Justification: breaks the whole system
> 
> System becomes unstable. Have tried both 32 bit and 64 bit installs with all 
> standard kernels offered with both 6.0.5 and 6.0.6 net-inst CD images.
> 
> Stripped out all extraneous hardware but problem persists with just the 
> motherboard, APU and RAM.
> 
> Here is a log extract of one of the faults:
> 
> Oct  9 14:05:35 media kernel: [  148.633457] Pid: 5239, comm: factor Not 
> tainted 2.6.32-5-686 #1
> Oct  9 14:05:35 media kernel: [  148.633459] Call Trace:
> Oct  9 14:05:35 media kernel: [  148.633467]  [] ? 
> bad_page+0xd7/0xeb
> Oct  9 14:05:35 media kernel: [  148.633471]  [] ? 
> get_page_from_freelist+0x2e7/0x3c7
> Oct  9 14:05:35 media kernel: [  148.633474]  [] ? 
> __alloc_pages_nodemask+0xf3/0x4d9
> Oct  9 14:05:35 media kernel: [  148.633478]  [] ? 
> anon_vma_prepare+0x32/0x8c
> Oct  9 14:05:35 media kernel: [  148.633481]  [] ? 
> handle_mm_fault+0x2ba/0x959
> Oct  9 14:05:35 media kernel: [  148.633484]  [] ? 
> do_brk+0x246/0x28e
> Oct  9 14:05:35 media kernel: [  148.633488]  [] ? 
> do_page_fault+0x2f1/0x307
> Oct  9 14:05:35 media kernel: [  148.633491]  [] ? 
> do_page_fault+0x0/0x307
> Oct  9 14:05:35 media kernel: [  148.633493]  [] ? 
> error_code+0x73/0x78
> Oct  9 14:05:35 media kernel: [  148.633495] Disabling lock debugging due to 
> kernel taint
> 
Hi, and sorry for the late answer.

Did you check the RAM in that machine?  This seems more likely to be
hardware failure than anything else as far as I can tell...

Cheers,
Julien


signature.asc
Description: Digital signature

Processed: severity of 612293 is normal

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> severity 612293 normal
Bug #612293 [installation-reports] installation-reports: hangs up trying floppy
Severity set to 'normal' from 'serious'
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
612293: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=612293
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems


--
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/handler.s.c.136214435322748.transcr...@bugs.debian.org

Bug#695328: [testing/wheezy] UEFI installed system fails to boot

[Kenyon Ralph]

On 2012-12-29T20:55:05-0800, Kenyon Ralph  wrote:
> On 2012-12-29T19:25:59-0800, Kenyon Ralph  wrote:
> > I have a feeling that using grub2 2.00 (like Ubuntu uses) would work.
> > I'll try to build an installer including that if I can figure it out.
> 
> Instead of building a new installer, I just installed grub2 2.00-8
> from experimental in rescue mode. System still did not boot, so I
> don't know what to try now. It would be nice if we could figure out
> why Ubuntu 12.10 installs and boots in EFI mode, and bring those
> changes into the Debian packages.

Just trying to install wheezy in UEFI mode again on the Intel DH77EB
motherboard, now with firmware version 99 and the latest daily build
of debian-testing-amd64-netinst.iso. Still the same result: the
resulting Debian installation is unbootable.

Here is output when I install and boot Ubuntu 12.10:

$ sudo efibootmgr --verbose
BootCurrent: 0002
Timeout: 1 seconds
BootOrder: 0002,0003,
Boot* debianVendor(99e275e7-75a0-4b37-a2e6-c5385e6c00cb,)
Boot0002* ubuntu
HD(1,800,2f000,017b4fcf-b5a3-4549-a8d6-a94cb7eb699a)File(\EFI\ubuntu\grubx64.efi)
Boot0003* UEFI : SATA : PORT 6G 0 : INTEL SSDSC2CW120A3 : PART 0 : OS 
Bootloader
ACPI(a0341d0,0)PCI(1f,2)03120a00HD(1,800,2f000,017b4fcf-b5a3-4549-a8d6-a94cb7eb699a)AMBO

In Debian rescue mode after installing Debian, replacing the previous
Ubuntu installation:

# efibootmgr --verbose
BootCurrent: 0003
Timeout: 1 seconds
BootOrder: 0003,0002,
Boot* debianVendor(99e275e7-75a0-4b37-a2e6-c5385e6c00cb,)
Boot0002* ubuntuVendor(99e275e7-75a0-4b37-a2e6-c5385e6c00cb,)
Boot0003* UEFI : USB :  0.00 : PART 0 : OS Bootloader   
ACPI(a0341d0,0)PCI(1d,0)USB(1,0)USB(1,0)HD(1,10a74,380,27f931c5)AMBO

Running 'grub-install /dev/sda' in Debian rescue mode causes the
debian line to change to this:

Boot* debian
HD(1,800,f3800,f8636d01-62af-4d23-9ab6-5b22c5ffd5e6)File(\EFI\debian\grubx64.efi)

But like I said in a previous email, upon reboot this disappears, and
reentering rescue mode shows the
"Vendor(99e275e7-75a0-4b37-a2e6-c5385e6c00cb,)" line for debian
instead.

Notice how there is no UEFI SATA hard drive in the efibootmgr output
on Debian. That's probably the problem, since the debian line needs to
refer to that device, but I have no idea why Ubuntu has this properly
and Debian lacks it.

-- 
Kenyon Ralph


signature.asc
Description: Digital signature

Processed: tagging 701960

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> tags 701960 - pending
Bug #701960 [busybox] busybox awk incorrectly uses FS variable
Removed tag(s) pending.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
701960: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=701960
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems


--
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/handler.s.c.136213270925396.transcr...@bugs.debian.org

Processed: tagging 701960

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> tags 701960 - pending patch
Bug #701960 [busybox] busybox awk incorrectly uses FS variable
Removed tag(s) patch.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
701960: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=701960
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems


--
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/handler.s.c.136213271525435.transcr...@bugs.debian.org

Bug#698347: debootstrap: New variant based on PRoot

[Rémi Duraffort]

Hello Cyril,

I have created a debian package for PRoot.

The sources are : http://ivoire.dinauz.org/debian/proot/
The ITP is #701894


Rgds

--
Rémi Duraffort | ivoire
http://ivoire.dinauz.org/blog/


--
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/06d8db423643ffe0e7a368bfe3503...@dinauz.org

Bug#701968: several busybox applets may fail or produce garbage

[Michael Tokarev]

Package: busybox
Version: 1:1.20.0-7
Severity: important
Tags: patch upstream fixed-upstream pending

Several bugs (typos) has been found in busybox in macros that
performs conversion from host words to unaligned buffers, one
in generic code and two more in compression library (xz).

First bug (generic move_to_unaligned16() implementation) copies
2 more bytes than necessary, thus can overflow the destination,
which may cause either memory corruption or a segmentation fault.

Second bug in xz is wrong usage of move_to_unaligned16 (which
copied 4 instead of 2 bytes by accident) to handle 32bit
quantities - is exposed when the first bug is fixed.

Other usages of move_to_unaligned16() in whole busybox sources
appears to be okay.

The severity is important because the overflow usually goes
silent but may produce garbage output, which leads to data
corruption in archivals.  Reportedly this happens on sparc.

/mjt


-- 
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/20130301090411.10418.18662.reportbug@gandalf.local

Bug#701965: busybox mdev creates deep subdirs in /dev with 0777 permissions

[Michael Tokarev]

Package: busybox
Version: 1:1.20.0-7
Severity: important
Tags: security patch upstream fixed-upstream pending

When device node or symlink in /dev should be created inside
2-or-deeper subdirectory (/dev/dir1/dir2.../node), the
intermediate directories are incorrectly created with mode
0777, which is an obvious security issue.

mdev is an alternative for udev, but since udev is used
almost universally, and many packages depend on it, mdev
isn't used often.  Also, subdirs of more than one level
are not common, especially with mdev which, unlike udev,
has limited "language" to construct filenames/symlinks,
so often, when mdev is used, a task of creating device
nodes with complex names is implemented using an external
script instead.  However it is important to fix this to
avoid surprizes.

The issue has been fixed upstream in commit
4609f477c7e043a4f6147dfe6e86b775da2ef784.


-- 
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/20130301084436.9719.88191.reportbug@gandalf.local