Bug#782058: Pegasos II: installer boots up to 'returning from prom_init'

[John Paul Adrian Glaubitz]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

On 12/09/2015 03:39 AM, Milan Kupcevic wrote:
> The module in question gets loaded and is used in D-I only. Pay 
> attention to the case you are pointing at: the graphics does not
> work on boot/reboot into an installed system. At this point this
> module plays no role because it is blacklisted in the main system.
> This user is having some other issues unrelated to this module.

Did you actually check that it is blacklisted after installation?

radeon KMS worked fine on every PPC Mac hardware that I tested. However,
I always ran into exactly this issue when radeonfb was loaded, even when
it was unloaded later. Apparently, radeonfb sets the GPU in a state from
which the radeon KMS module cannot recover it.

My Mac Mini G4 is currently packed up because I am moving soon. But I
will re-test this at some point because I am pretty sure this is again
radeonfb messing with the GPU as the symptoms are the same.

Adrian

- -- 
 .''`.  John Paul Adrian Glaubitz
: :' :  Debian Developer - glaub...@debian.org
`. `'   Freie Universitaet Berlin - glaub...@physik.fu-berlin.de
  `-GPG: 62FF 8A75 84E0 2956 9546  0006 7426 3B37 F5B5 F913
-BEGIN PGP SIGNATURE-
Version: GnuPG v2

iQIcBAEBCAAGBQJWZ/h2AAoJEHQmOzf1tfkTG5QP/3fIYZCRl+V3MbpWoXjivBU/
Njgwtsjh67Z/vouM9eT50U2Jc3Db/6a8rtWb3cwuYfES+36fxxK3HiExr5/aRwzo
19gBbkCweYGDErZLoc0OnY7UZT1Fk0FcNfU4FdC4edMtrb63dYsQAhxFbI8NVfba
tJTH1pJi5MqLx03rzcPKl97/4OKFTP4b1+54nojZaXYnQG7pmFsK1Amx4nM4xqAJ
5uxbJ/q/ViEGqgLE8xso9471mKyTYm3+FI8kcxq83XNEqf9WDilRBcQgPvIkwfvW
lB5ALaKpd3fjb2yOM2557W857hMuzD7+i0jW23P5ieKcb0hxc3HVOJKLCTNDrYDR
inknkx/ZoOGhzHQC1sr4e8AHsT6Tp1dQLK0fyuGKasa2FKHeqN4eueYZImO2QFpG
Ir/xoYYVXZPWyAS0xGH3sddn9WsP7tvOphChgPyi5VBMoaaJqq2CBupdUTLarc9/
cZeU4jPYZo7seRtCKcdTPibm0V+keInzUC5PNoVb2lDD20kWSlDpaeCHcVp+yp8s
Y1ZwFUtaPYjGljz6ei23+0v+VIei2fhGyzpLkQ8xJjQt2/XsGaWT0eD9CAsNPocC
C/nWxruTt8+RUg9Wg/fO9K8X1cNCh/HfU9wNtMid74ski9prxZNG+xxFgOOfzxo1
2UEz9Xkajsesb8+nZTaA
=21XG
-END PGP SIGNATURE-

Bug#795839: initramfs-tools: When adding i8042 also add psmouse as some keyboards are behind the mouse

[Ben Hutchings]

Control: tag -1 pending

On Mon, 17 Aug 2015 11:36:29 +0100 Andy Whitcroft  wrote:
> Package: initramfs-tools
> Version: 0.120
> Severity: normal
> 
> hook-functions/auto_add_modules: include psmouse as some keyboards are
> connected to the "pass-thru" port on the PS2 mouse port (because that is
> such a good idea).

Applied, thanks.

Ben.

-- 
Ben Hutchings
I'm always amazed by the number of people who take up solipsism because
they heard someone else explain it. - E*Borg on alt.fan.pratchett

signature.asc
Description: This is a digitally signed message part

Bug#795833: initramfs-tools: add mountroot failure support to allow meaningful messages and recovery attempts

[Ben Hutchings]

On Mon, 17 Aug 2015 10:52:14 +0100 Andy Whitcroft  wrote:
> Package: initramfs-tools
> Version: 0.120
> Severity: normal
> 
> Allow hooks to supply specific root mount failure handlers.  These can
> both report more specific failure reasons, and in some cases may even be
> able to attempt recovery.  This is useful for more complex scenarios
> such as LVM and mdadm setups.
> 
> We use this in Ubuntu to allow augmented lvm2 and mdadm hooks to recover
> failed raids and the like.
> 
> NOTE: that the splash handling here may well be Ubuntu specific.

Thanks for your patch.

Can you explain why this was implemented by extending existing scripts
rather than by adding a new phase (possibly with stamp files to control
what they do)?

[...]
> --- a/scripts/functions
> +++ b/scripts/functions
[...]
> +# Run failure hooks.
> +# When a failure hook exits "1", it has not done anything to correct the
> +# system.  Exiting "0" means that something has been attempted to resolve
> +# the lack of a root filesystem.
> +# Hooks are run in lexigraphical order, and are responsible for removing
> +# themselves if they should not re-run in a later cycle.  When one exits
> +# "0", the stack is stopped, so the caller can return to the main rootfs
> +# wait loop.

'Hook' is reserved for build-time scripts, so use 'script' here.

> +try_failure_hooks()
> +{
> + local hook
> +
> + # Disable usplash so text from hooks can be seen
> + if [ -x /sbin/usplash_write ]; then
> + /sbin/usplash_write "QUIT"
> + fi
> + chvt 1
> + if [ -x /bin/plymouth ] && plymouth --ping; then
> + /bin/plymouth hide-splash > /dev/null 2>&1
> + fi
[...]

This bit can be handled by 'panic' scripts once #602331 is fixed
(currently pending).

Ben.

-- 
Ben Hutchings
I'm always amazed by the number of people who take up solipsism because
they heard someone else explain it. - E*Borg on alt.fan.pratchett

signature.asc
Description: This is a digitally signed message part

Processed: Re: initramfs-tools: When adding i8042 also add psmouse as some keyboards are behind the mouse

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #795839 [initramfs-tools] initramfs-tools: When adding i8042 also add 
psmouse as some keyboards are behind the mouse
Added tag(s) pending.

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

Processed: tagging 795833

[Debian Bug Tracking System]

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

> tags 795833 + moreinfo
Bug #795833 [initramfs-tools] initramfs-tools: add mountroot failure support to 
allow meaningful messages and recovery attempts
Added tag(s) moreinfo.
> thanks
Stopping processing here.

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

Bug#795832: [PATCH initramfs-tools] initramfs-tools: Support multiple break points using a comma delimiter

[Ben Hutchings]

Thanks for your patch, but I would prefer to avoid adding more sub-
shells.  Also, this change needs to be documented.  What do you t
hink of this patch?

Ben.
---
Closes: #795832
Signed-off-by: Ben Hutchings 
---
 initramfs-tools.8 | 3 ++-
 scripts/functions | 6 --
 2 files changed, 6 insertions(+), 3 deletions(-)

diff --git a/initramfs-tools.8 b/initramfs-tools.8
index ea8c098..a276be3 100644
--- a/initramfs-tools.8
+++ b/initramfs-tools.8
@@ -110,7 +110,8 @@ Use for example "debug=vc".
 spawns a shell in the initramfs image at the chosen phase
 (top, modules, premount, mount, mountroot, bottom, init)
 before actually executing the corresponding scripts
-(see the "Boot scripts" section) or action.
+(see the "Boot scripts" section) or action.  Multiple
+phases may be specified, delimited by commas.
 The default, if no phase is specified, is "premount".
 Beware that if both "panic" and "break" are present,
 initramfs will not spawn any shells but reboot instead.
diff --git a/scripts/functions b/scripts/functions
index 33fddcf..91d3407 100644
--- a/scripts/functions
+++ b/scripts/functions
@@ -61,9 +61,11 @@ panic()
 
 maybe_break()
 {
-   if [ "${break:-}" = "$1" ]; then
+   case ",$break," in
+   *,$1,*)
    panic "Spawning shell within the initramfs"
-   fi
+   ;;
+   esac
 }
 
 render()
-- 
Ben Hutchings
I'm always amazed by the number of people who take up solipsism because
they heard someone else explain it. - E*Borg on alt.fan.pratchett

signature.asc
Description: This is a digitally signed message part

Processed: limit source to initramfs-tools, tagging 783291, tagging 797361, tagging 784234, tagging 766920

[Debian Bug Tracking System]

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

> limit source initramfs-tools
Limiting to bugs with field 'source' containing at least one of 
'initramfs-tools'
Limit currently set to 'source':'initramfs-tools'

> tags 783291 + pending
Bug #783291 [initramfs-tools] /bin/touch is missing if built with BUSYBOX=n or 
busybox package not installed
Bug #785435 [initramfs-tools] init: touch not found
Bug #786385 [initramfs-tools] /init: touch not found
Added tag(s) pending.
Added tag(s) pending.
Added tag(s) pending.
> tags 797361 + pending
Bug #797361 [initramfs-tools] initramfs-tools: hooks/fsck includes too many 
tools
Added tag(s) pending.
> tags 784234 + pending
Bug #784234 [initramfs-tools] initramfs-tools: searches for fsck.btrfs in the 
wrong directory
Bug #784368 [initramfs-tools] initramfs-tools: update-initramfs tries to use 
/sbin/fsck.btrfs instead of /bin/fsck.btrfs
Bug #803322 [initramfs-tools] initramfs-tools: gives wrong warnings about 
fsck.btrfs
Added tag(s) pending.
Added tag(s) pending.
Added tag(s) pending.
> tags 766920 + pending
Bug #766920 [initramfs-tools] produces unbootable initramfs with lilo 
hexadecimal syntax (root=803)
Added tag(s) pending.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
766920: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=766920
783291: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=783291
784234: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=784234
784368: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=784368
785435: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=785435
786385: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=786385
797361: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=797361
803322: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=803322
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

[PATCH initramfs-tools] Set emacs local variables to implement our shell coding style

[Ben Hutchings]

Signed-off-by: Ben Hutchings 
---
 .dir-locals.el | 8 
 1 file changed, 8 insertions(+)
 create mode 100644 .dir-locals.el

diff --git a/.dir-locals.el b/.dir-locals.el
new file mode 100644
index 000..e91b46a
--- /dev/null
+++ b/.dir-locals.el
@@ -0,0 +1,8 @@
+;;; Directory Local Variables
+;;; For more information see (info "(emacs) Directory Variables")
+
+((sh-mode
+  (sh-basic-offset . 8)
+  (sh-indentation . 8)
+  (sh-indent-for-case-label . 0)
+  (sh-indent-for-case-alt . +)))
-- 
Ben Hutchings
I'm always amazed by the number of people who take up solipsism because
they heard someone else explain it. - E*Borg on alt.fan.pratchett


signature.asc
Description: This is a digitally signed message part

Bug#807497: marked as done (linux-image-4.2.0-1-amd64: Enable CONFIG_MOUSE_PS2_VMMOUSE)

[Debian Bug Tracking System]

Your message dated Wed, 09 Dec 2015 17:40:42 +
with message-id <1449682842.2824.155.ca...@decadent.org.uk>
and subject line Re: Bug#807497: linux-image-4.2.0-1-amd64: Enable 
CONFIG_MOUSE_PS2_VMMOUSE
has caused the Debian Bug report #807497,
regarding linux-image-4.2.0-1-amd64: Enable CONFIG_MOUSE_PS2_VMMOUSE
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.)


-- 
807497: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=807497
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:linux
Version: 4.2.6-1
Severity: normal

Rootless Xorg is enabled with Debian "stretch".  VMWare's user mode
vmmouse driver cannot function in this mode.  As a result,
Debian-stretch VMWare guests will lose all mouse functionality, i.e.
no cursor, no mouse clicks.

VMWare has moved the mouse driver to the kernel, and this
(CONFIG_MOUSE_PS2_VMMOUSE) should be enabled by default.  Once this is
enabled, mouse will work again in Debian-stretch guests.

I have verified this behavior by rebuilding kernel v4.2 with the
the option turned on.

Enabling this option should have no impact on none-VMWare guests as
the driver will detect this condition and not initialize.



-- Package-specific info:
** Kernel log: boot messages should be attached

** Model information
sys_vendor: VMware, Inc.
product_name: VMware Virtual Platform
product_version: None
chassis_vendor: No Enclosure
chassis_version: N/A
bios_vendor: Phoenix Technologies LTD
bios_version: 6.00
board_vendor: Intel Corporation
board_name: 440BX Desktop Reference Platform
board_version: None

** PCI devices:
00:00.0 Host bridge [0600]: Intel Corporation 440BX/ZX/DX - 82443BX/ZX/DX Host 
bridge [8086:7190] (rev 01)
Subsystem: VMware Virtual Machine Chipset [15ad:1976]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- 
SERR- TAbort- 
SERR- TAbort- 
Reset- FastB2B-
PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-

00:07.0 ISA bridge [0601]: Intel Corporation 82371AB/EB/MB PIIX4 ISA 
[8086:7110] (rev 08)
Subsystem: VMware Virtual Machine Chipset [15ad:1976]
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap- 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- 
SERR- TAbort- 
SERR- TAbort- 
SERR- TAbort- 
SERR- 
Kernel driver in use: vmw_vmci

00:0f.0 VGA compatible controller [0300]: VMware SVGA II Adapter [15ad:0405] 
(prog-if 00 [VGA controller])
Subsystem: VMware SVGA II Adapter [15ad:0405]
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- 
SERR- 
Kernel driver in use: vmwgfx

00:10.0 SCSI storage controller [0100]: LSI Logic / Symbios Logic 53c1030 PCI-X 
Fusion-MPT Dual Ultra320 SCSI [1000:0030] (rev 01)
Subsystem: VMware LSI Logic Parallel SCSI Controller [15ad:1976]
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- 
SERR- 
Kernel driver in use: mptspi

00:11.0 PCI bridge [0604]: VMware PCI bridge [15ad:0790] (rev 02) (prog-if 01 
[Subtractive decode])
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- 
SERR- TAbort- 
Reset- FastB2B-
PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
Capabilities: 

00:15.0 PCI bridge [0604]: VMware PCI Express Root Port [15ad:07a0] (rev 01) 
(prog-if 00 [Normal decode])
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- Reset- FastB2B-
PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
Capabilities: 
Kernel driver in use: pcieport

00:15.1 PCI bridge [0604]: VMware PCI Express Root Port [15ad:07a0] (rev 01) 
(prog-if 00 [Normal decode])
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- Reset- FastB2B-
PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
Capabilities: 

Bug#807497: linux-image-4.2.0-1-amd64: Enable CONFIG_MOUSE_PS2_VMMOUSE

[Sinclair Yeh]

Package: src:linux
Version: 4.2.6-1
Severity: normal

Rootless Xorg is enabled with Debian "stretch".  VMWare's user mode
vmmouse driver cannot function in this mode.  As a result,
Debian-stretch VMWare guests will lose all mouse functionality, i.e.
no cursor, no mouse clicks.

VMWare has moved the mouse driver to the kernel, and this
(CONFIG_MOUSE_PS2_VMMOUSE) should be enabled by default.  Once this is
enabled, mouse will work again in Debian-stretch guests.

I have verified this behavior by rebuilding kernel v4.2 with the
the option turned on.

Enabling this option should have no impact on none-VMWare guests as
the driver will detect this condition and not initialize.



-- Package-specific info:
** Kernel log: boot messages should be attached

** Model information
sys_vendor: VMware, Inc.
product_name: VMware Virtual Platform
product_version: None
chassis_vendor: No Enclosure
chassis_version: N/A
bios_vendor: Phoenix Technologies LTD
bios_version: 6.00
board_vendor: Intel Corporation
board_name: 440BX Desktop Reference Platform
board_version: None

** PCI devices:
00:00.0 Host bridge [0600]: Intel Corporation 440BX/ZX/DX - 82443BX/ZX/DX Host 
bridge [8086:7190] (rev 01)
Subsystem: VMware Virtual Machine Chipset [15ad:1976]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- 
SERR- TAbort- 
SERR- TAbort- 
Reset- FastB2B-
PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-

00:07.0 ISA bridge [0601]: Intel Corporation 82371AB/EB/MB PIIX4 ISA 
[8086:7110] (rev 08)
Subsystem: VMware Virtual Machine Chipset [15ad:1976]
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap- 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- 
SERR- TAbort- 
SERR- TAbort- 
SERR- TAbort- 
SERR- 
Kernel driver in use: vmw_vmci

00:0f.0 VGA compatible controller [0300]: VMware SVGA II Adapter [15ad:0405] 
(prog-if 00 [VGA controller])
Subsystem: VMware SVGA II Adapter [15ad:0405]
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- 
SERR- 
Kernel driver in use: vmwgfx

00:10.0 SCSI storage controller [0100]: LSI Logic / Symbios Logic 53c1030 PCI-X 
Fusion-MPT Dual Ultra320 SCSI [1000:0030] (rev 01)
Subsystem: VMware LSI Logic Parallel SCSI Controller [15ad:1976]
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- 
SERR- 
Kernel driver in use: mptspi

00:11.0 PCI bridge [0604]: VMware PCI bridge [15ad:0790] (rev 02) (prog-if 01 
[Subtractive decode])
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- 
SERR- TAbort- 
Reset- FastB2B-
PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
Capabilities: 

00:15.0 PCI bridge [0604]: VMware PCI Express Root Port [15ad:07a0] (rev 01) 
(prog-if 00 [Normal decode])
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- Reset- FastB2B-
PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
Capabilities: 
Kernel driver in use: pcieport

00:15.1 PCI bridge [0604]: VMware PCI Express Root Port [15ad:07a0] (rev 01) 
(prog-if 00 [Normal decode])
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- Reset- FastB2B-
PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
Capabilities: 
Kernel driver in use: pcieport

00:15.2 PCI bridge [0604]: VMware PCI Express Root Port [15ad:07a0] (rev 01) 
(prog-if 00 [Normal decode])
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- Reset- FastB2B-
PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
Capabilities: 
Kernel driver in use: pcieport

00:15.3 PCI bridge [0604]: VMware PCI Express Root Port [15ad:07a0] (rev 01) 
(prog-if 00 [Normal decode])
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- Reset- FastB2B-
PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
Capabilities: 
Kernel 

Processed: tagging 801154

[Debian Bug Tracking System]

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

> tags 801154 + moreinfo
Bug #801154 [initramfs-tools] [debian] initramfs-tools: add PARTUUID to 
resolve_device
Added tag(s) moreinfo.
> thanks
Stopping processing here.

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

Processed: tagging 337176

[Debian Bug Tracking System]

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

> tags 337176 + wontfix
Bug #337176 [initramfs-tools] troubles due to 32-bit chroot on amd64
Added tag(s) wontfix.
> thanks
Stopping processing here.

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

Bug#801154: [PATCH initramfs-tools 2/2] scripts/functions: Handle PARTLABEL= and PARTUUID= block device IDs using blkid

[Ben Hutchings]

Please can you test this along with the previous patch?

Ben.
---
Closes: #801154
Signed-off-by: Ben Hutchings 
---
 scripts/functions | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/scripts/functions b/scripts/functions
index 8f2fac7..53419e2 100644
--- a/scripts/functions
+++ b/scripts/functions
@@ -298,7 +298,7 @@ resolve_device() {
DEV="$1"
 
case "$DEV" in
-   LABEL=* | UUID=*)
+   LABEL=* | UUID=* | PARTLABEL=* | PARTUUID=*)
if command -v blkid >/dev/null 2>&1; then
DEV="$(blkid -l -t "$DEV" -o device)"
else


signature.asc
Description: Digital signature

Bug#801154: [PATCH initramfs-tools 1/2] scripts/functions: Use blkid to resolve LABEL= and UUID= block device IDs

[Ben Hutchings]

This is a preparatory patch for fixing #801154.

Ben.
---
This means we will deal correctly with various other characters than
'/' that also need to be escaped.

Signed-off-by: Ben Hutchings 
---
 scripts/functions | 32 +---
 1 file changed, 5 insertions(+), 27 deletions(-)

diff --git a/scripts/functions b/scripts/functions
index aa53010..8f2fac7 100644
--- a/scripts/functions
+++ b/scripts/functions
@@ -297,35 +297,13 @@ read_fstab_entry() {
 resolve_device() {
DEV="$1"
 
-   case $DEV in
-   LABEL=*)
-   DEV="${DEV#LABEL=}"
-
-   # support any / in LABEL= path (escape to \x2f)
-   case "${DEV}" in
-   */*)
-   if command -v sed >/dev/null 2>&1; then
-   DEV="$(echo ${DEV} | sed 's,/,\\x2f,g')"
+   case "$DEV" in
+   LABEL=* | UUID=*)
+   if command -v blkid >/dev/null 2>&1; then
+   DEV="$(blkid -l -t "$DEV" -o device)"
else
-   if [ "${DEV}" != "${DEV#/}" ]; then
-   DEV="\x2f${DEV#/}"
-   fi
-   if [ "${DEV}" != "${DEV%/}" ]; then
-   DEV="${DEV%/}\x2f"
-   fi
-   IFS='/'
-   newroot=
-   for s in $DEV; do
-   newroot="${newroot:+${newroot}\\x2f}${s}"
-   done
-   unset IFS
-   DEV="${newroot}"
+   log_warning_msg "blkid not present, so cannot resolve 
$DEV"
fi
-   esac
-   DEV="/dev/disk/by-label/${DEV}"
-   ;;
-   UUID=*)
-   DEV="/dev/disk/by-uuid/${DEV#UUID=}"
;;
esac
# Only canonicalise if a valid file, in case $DEV isn't a filename



signature.asc
Description: Digital signature

Bug#597581: update-initramfs should not set PATH

[Ben Hutchings]

Control: tag -1 wontfix

I'm not at all convinced that update-initramfs should be sensitive to
the path of the process invoking it.  update-initramfs is not only used
interactively, but also automatically by package installation.

It seems to me that it would make more sense for hooks that need
commands in /usr/local/{s,}bin to modify their $PATH accordingly.

Ben.

-- 
Ben Hutchings
I'm always amazed by the number of people who take up solipsism because
they heard someone else explain it. - E*Borg on alt.fan.pratchett


signature.asc
Description: This is a digitally signed message part

Bug#597581: update-initramfs should not set PATH

[Ben Hutchings]

On Wed, 2015-12-09 at 22:05 +, Ian Jackson wrote:
> Ben Hutchings writes ("Re: update-initramfs should not set PATH"):
> > On Wed, 2015-12-09 at 21:56 +, Ian Jackson wrote:
> > > Ben Hutchings writes ("Re: update-initramfs should not set PATH"):
> > > > I'm not at all convinced that update-initramfs should be sensitive to
> > > > the path of the process invoking it.  update-initramfs is not only used
> > > > interactively, but also automatically by package installation.
> > > 
> > > Package installation should also occur with an appropriate PATH.  If
> > > PATH contains exciting things then that is presumably deliberate.
> > > 
> > > See policy 6.1 (last para):
> > > 
> > >   [...] Maintainer scripts should also not reset the PATH,
> > >   though they might choose to modify it by prepending or appending
> > >   package-specific directories. These considerations really apply to all
> > >   shell scripts.
> > > 
> > > I think it would be better to follow this recommendation here, unless
> > > you have a compelling reason to deviate from our usual practice.
> > 
> > As update-initramfs is not a maintainer script, I fail to see the relevance.
> 
> Firstly, the argument you made above, that update-initramfs is called
> "automatically by package installation", seems to be based on the idea
> that this is a good reason for setting the PATH.

My point was that it's called both from interactive shells *and* from
package upgrades, and there's no reason to think $PATH will be
consistent between those.

> Secondly, note "These considerations really apply to all shell
> scripts".

Yet most init scripts reset the PATH because this turns out to be a bad
idea in reality.

$ grep -rl 'PATH=[^$]*$' /etc/init.d | wc -l
63
$ grep -rL 'PATH=[^$]*$' /etc/init.d | wc -l
44

Ben.

-- 
Ben Hutchings
I'm always amazed by the number of people who take up solipsism because
they heard someone else explain it. - E*Borg on alt.fan.pratchett

signature.asc
Description: This is a digitally signed message part

Processed: Re: mkinitramfs fails with latest udev (>= 220-7) on some systems

[Debian Bug Tracking System]

Processing control commands:

> tag -1 patch moreinfo
Bug #790722 [initramfs-tools] mkinitramfs fails with latest udev (>= 220-7) on 
some systems
Added tag(s) moreinfo and patch.

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

Bug#790722: mkinitramfs fails with latest udev (>= 220-7) on some systems

[Ben Hutchings]

Control: tag -1 patch moreinfo

On Wed, 1 Jul 2015 03:39:07 -0400 (EDT) Stephen Powell  
wrote:
[...]
> The second problem causes a problem for initramfs-tools.  The parse_numeric
> function in /usr/share/initramfs-tools/scripts/functions has code in it which
> looks like this:
> 
>if command -v udevd >/dev/null 2>&1; then
>ROOT=/dev/block/${major}:${minor}
>else
>mknod -m 600 /dev/root b ${major} ${minor}
>ROOT=/dev/root
>fi
> 
> Obviously, initramfs-tools is testing for the existence of udev by checking
> to see if there is a command available called udevd.  If not, then it assumes
> that there is no udev.  Older releases of udev contained this command.  udev
> 220-7 (and above) does not.

It does but now it's called systemd-udevd and isn't on the path.

This should be fixed on my branch benh/parse-numeric-fixes at
https://anonscm.debian.org/cgit/kernel/initramfs-tools.git

[...]
> By the way, I am still hoping to get my parse_numeric patch, available at
> http://users.wowway.com/~zlinuxman/kernel/parse_numeric.patch, included in
> initramfs-tools.

It's not there any more...

> The current code cannot handle a kernel composite device number
> greater than 0xf.  With the patch, it should be able to handle any valid
> kernel composite device number.

...but I sent you my patch for this.  It's also on that git branch.

Please can you test initramfs-tools built from that branch?  Note that
this has the binary package split into initramfs-tools and initramfs-
tools-core, and you'll need to install both.

Ben.

-- 
Ben Hutchings
I'm always amazed by the number of people who take up solipsism because
they heard someone else explain it. - E*Borg on alt.fan.pratchett

signature.asc
Description: This is a digitally signed message part

Bug#770912: marked as done (initramfs-tools: Add xhci-pci to base modules (linux 3.18))

[Debian Bug Tracking System]

Your message dated Wed, 09 Dec 2015 22:41:04 +
with message-id <1449700864.2824.197.ca...@decadent.org.uk>
and subject line Re: initramfs-tools: Add xhci-pci to base modules (linux 3.18)
has caused the Debian Bug report #770912,
regarding initramfs-tools: Add xhci-pci to base modules (linux 3.18)
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.)


-- 
770912: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=770912
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: initramfs-tools
Version: 0.116
Severity: normal
Tags: patch

While trying out an upstream kernel build to debug another issue, I
discovered that I couldn't enter any text at my disk encryption
password prompt.  After bisecting, I discovered that this was due to a
patch that split xhci-pci out into a separate module.  Sure enough,
adding that to my initrd modules list allowed me to boot and decrypt
on later kernels.

This should be added to the standard base modules list to avoid anyone
else running into this problem.

-- Package-specific info:
-- initramfs sizes
-rw-r--r-- 1 root root 16M Nov 12 06:55 /boot/initrd.img-3.16.0-4-amd64
-rw-r--r-- 1 root root 16M Nov 25 00:43 /boot/initrd.img-3.17.0-rc6-bisect
-- /proc/cmdline
BOOT_IMAGE=/vmlinuz-3.17.0-rc6-bisect root=/dev/mapper/scratch--vg-root ro 
video=1920x1080@60 quiet

-- resume
RESUME=/dev/mapper/scratch--vg-swap_1
-- /proc/filesystems
ext3
ext2
ext4
fuseblk

-- lsmod
Module  Size  Used by
binfmt_misc12853  1 
bnep   17349  2 
nfsd  267715  2 
auth_rpcgss55111  1 nfsd
oid_registry   12419  1 auth_rpcgss
nfs_acl12511  1 nfsd
nfs   196017  0 
lockd  83177  2 nfs,nfsd
fscache45208  1 nfs
sunrpc241210  6 nfs,nfsd,auth_rpcgss,lockd,nfs_acl
arc4   12536  2 
iwlmvm151401  0 
mac80211  495284  1 iwlmvm
snd_hda_codec_realtek67468  1 
snd_hda_codec_generic63084  1 snd_hda_codec_realtek
iwlwifi96207  1 iwlmvm
snd_hda_codec_hdmi 49213  1 
iTCO_wdt   12831  0 
cfg80211  412519  3 iwlwifi,mac80211,iwlmvm
iTCO_vendor_support12649  1 iTCO_wdt
x86_pkg_temp_thermal12951  0 
intel_powerclamp   17122  0 
intel_rapl 17356  0 
coretemp   12820  0 
kvm_intel 139066  0 
kvm   396575  1 kvm_intel
fuse   83314  1 
evdev  17445  18 
ecb12737  1 
btusb  29911  0 
pcspkr 12595  0 
bluetooth 382589  21 bnep,btusb
i2c_i801   16965  0 
rfkill 18867  4 cfg80211,bluetooth
shpchp 31114  0 
mei_me 17900  0 
lpc_ich20768  0 
mfd_core   12601  1 lpc_ich
mei75079  1 mei_me
snd_hda_intel  26387  5 
snd_hda_controller 26938  1 snd_hda_intel
i915  881375  6 
tpm_tis17182  0 
nuvoton_cir17153  0 
snd_hda_codec 104440  5 
snd_hda_codec_realtek,snd_hda_codec_hdmi,snd_hda_codec_generic,snd_hda_intel,snd_hda_controller
tpm31467  1 tpm_tis
battery13356  0 
rc_core22437  1 nuvoton_cir
snd_hwdep  13148  1 snd_hda_codec
drm_kms_helper 76652  1 i915
snd_pcm88603  4 
snd_hda_codec_hdmi,snd_hda_codec,snd_hda_intel,snd_hda_controller
drm   255010  5 i915,drm_kms_helper
snd_timer  26614  1 snd_pcm
video  18078  1 i915
snd69340  18 
snd_hda_codec_realtek,snd_hwdep,snd_timer,snd_hda_codec_hdmi,snd_pcm,snd_hda_codec_generic,snd_hda_codec,snd_hda_intel
i2c_algo_bit   12744  1 i915
soundcore  13031  2 snd,snd_hda_codec
i2c_designware_platform12645  0 
i2c_designware_core12813  1 i2c_designware_platform
processor  28184  0 
button 12988  1 i915
parport_pc 26300  1 
ppdev  16782  0 
lp 17074  0 
parport35749  3 lp,ppdev,parport_pc
autofs435529  2 
ext4  477391  2 
crc16  12343  2 ext4,bluetooth
mbcache17171  1 ext4
jbd2   82321  1 ext4
algif_skcipher 17051  0 
af_alg 12988  1 algif_skcipher
hid_logitech_dj17192  0 
hid_generic12393  

Bug#781658: initramfs-tools: Upgrade Wheezy -> Jessie: not asked for cryptsetup password on boot - solved reinstalling kernel

[Ben Hutchings]

Control: found -1 0.116
Control: notfound -1 0.119
Control: tag -1 moreinfo

Thanks for your detailed bug report.

On Wed, 01 Apr 2015 12:27:15 +0200 Laura Arjona Reina  
wrote:
[...]
> So I've tried to gather the relevant log information and I'm attaching apt
> history.log, term.log and dpk.log covering:
> * The inmediate action before upgrading (which was reinstalling cryptsetup but
> from wheezy-backports instead from wheezy).
> * The upgrade itself.
> * The reinstalling of the kernel, that solved the issue.
[...]

According to these logs, this was seen on upgrade to 0.116, not 0.119.

There were a very large number of fixes to initramfs-tools between
version 0.116 and 0.120 (which jessie was released with), so this may
well have been fixed along the way.

I note also that issue.term.log includes this error message:

> cryptsetup: WARNING: invalid line in /etc/crypttab for pdc -

though that may be entirely unrelated.

I'm going to leave this open for now, but I don't have a clue what went
wrong so without a method to reproduce it there's not much I can do.

Ben.

-- 
Ben Hutchings
I'm always amazed by the number of people who take up solipsism because
they heard someone else explain it. - E*Borg on alt.fan.pratchett

signature.asc
Description: This is a digitally signed message part

Bug#597581: update-initramfs should not set PATH

[Ian Jackson]

Ben Hutchings writes ("Re: update-initramfs should not set PATH"):
> Control: tag -1 wontfix
> 
> I'm not at all convinced that update-initramfs should be sensitive to
> the path of the process invoking it.  update-initramfs is not only used
> interactively, but also automatically by package installation.

Package installation should also occur with an appropriate PATH.  If
PATH contains exciting things then that is presumably deliberate.

See policy 6.1 (last para):

  Programs called from maintainer scripts should not normally have a
  path prepended to them. Before installation is started, the package
  management system checks to see if the programs ldconfig,
  start-stop-daemon, and update-rc.d can be found via the PATH
  environment variable. Those programs, and any other program that one
  would expect to be in the PATH, should thus be invoked without an
  absolute pathname. Maintainer scripts should also not reset the PATH,
  though they might choose to modify it by prepending or appending
  package-specific directories. These considerations really apply to all
  shell scripts.

I think it would be better to follow this recommendation here, unless
you have a compelling reason to deviate from our usual practice.

Thanks,
Ian.

Processed: Re: initramfs-tools: Upgrade Wheezy -> Jessie: not asked for cryptsetup password on boot - solved reinstalling kernel

[Debian Bug Tracking System]

Processing control commands:

> found -1 0.116
Bug #781658 [initramfs-tools] initramfs-tools: Upgrade Wheezy -> Jessie: not 
asked for cryptsetup password on boot - solved reinstalling kernel
Marked as found in versions initramfs-tools/0.116.
> notfound -1 0.119
Bug #781658 [initramfs-tools] initramfs-tools: Upgrade Wheezy -> Jessie: not 
asked for cryptsetup password on boot - solved reinstalling kernel
No longer marked as found in versions initramfs-tools/0.119.
> tag -1 moreinfo
Bug #781658 [initramfs-tools] initramfs-tools: Upgrade Wheezy -> Jessie: not 
asked for cryptsetup password on boot - solved reinstalling kernel
Added tag(s) moreinfo.

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

Bug#597581: update-initramfs should not set PATH

[Ben Hutchings]

On Wed, 2015-12-09 at 21:56 +, Ian Jackson wrote:
> Ben Hutchings writes ("Re: update-initramfs should not set PATH"):
> > Control: tag -1 wontfix
> > 
> > I'm not at all convinced that update-initramfs should be sensitive to
> > the path of the process invoking it.  update-initramfs is not only used
> > interactively, but also automatically by package installation.
> 
> Package installation should also occur with an appropriate PATH.  If
> PATH contains exciting things then that is presumably deliberate.
> 
> See policy 6.1 (last para):
> 
>   Programs called from maintainer scripts should not normally have a
>   path prepended to them. Before installation is started, the package
>   management system checks to see if the programs ldconfig,
>   start-stop-daemon, and update-rc.d can be found via the PATH
>   environment variable. Those programs, and any other program that one
>   would expect to be in the PATH, should thus be invoked without an
>   absolute pathname. Maintainer scripts should also not reset the PATH,
>   though they might choose to modify it by prepending or appending
>   package-specific directories. These considerations really apply to all
>   shell scripts.
> 
> I think it would be better to follow this recommendation here, unless
> you have a compelling reason to deviate from our usual practice.

As update-initramfs is not a maintainer script, I fail to see the relevance.

Ben.

-- 
Ben Hutchings
I'm always amazed by the number of people who take up solipsism because
they heard someone else explain it. - E*Borg on alt.fan.pratchett

signature.asc
Description: This is a digitally signed message part

Processed: reassign 678636 to cryptsetup, closing 678636

[Debian Bug Tracking System]

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

> reassign 678636 cryptsetup 2:1.1.3-4squeeze2
Bug #678636 [initramfs-tools] initramfs-tools: dm-crypt partitions not further 
working. No asking password to encrypt. System will not boot
Bug reassigned from package 'initramfs-tools' to 'cryptsetup'.
No longer marked as found in versions initramfs-tools/0.106.
Ignoring request to alter fixed versions of bug #678636 to the same values 
previously set
Bug #678636 [cryptsetup] initramfs-tools: dm-crypt partitions not further 
working. No asking password to encrypt. System will not boot
Marked as found in versions cryptsetup/2:1.1.3-4squeeze2.
> close 678636 2:1.4.3-2
Bug #678636 [cryptsetup] initramfs-tools: dm-crypt partitions not further 
working. No asking password to encrypt. System will not boot
Marked as fixed in versions cryptsetup/2:1.4.3-2.
Bug #678636 [cryptsetup] initramfs-tools: dm-crypt partitions not further 
working. No asking password to encrypt. System will not boot
Marked Bug as done
> thanks
Stopping processing here.

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

Processed: Re: Bug#689851: initramfs-tools: Wrong keymap at boot while, prompting for the passphrase

[Debian Bug Tracking System]

Processing control commands:

> tag -1 wheezy wontfix
Bug #689851 [initramfs-tools] initramfs-tools: Wrong keymap at boot while 
prompting for the passphrase
Added tag(s) wheezy and wontfix.
> affects -1 console-tools
Bug #689851 [initramfs-tools] initramfs-tools: Wrong keymap at boot while 
prompting for the passphrase
Added indication that 689851 affects console-tools
> notfound -1 0.107
Bug #689851 [initramfs-tools] initramfs-tools: Wrong keymap at boot while 
prompting for the passphrase
No longer marked as found in versions initramfs-tools/0.107.
> found -1 0.108
Bug #689851 [initramfs-tools] initramfs-tools: Wrong keymap at boot while 
prompting for the passphrase
Marked as found in versions initramfs-tools/0.108.

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

Bug#689851: initramfs-tools: Wrong keymap at boot while, prompting for the passphrase

[Ben Hutchings]

Control: tag -1 wheezy wontfix
Control: affects -1 console-tools
Control: notfound -1 0.107
Control: found -1 0.108

On Thu, 28 Nov 2013 11:37:54 +0100 Ondřej Vodáček
 wrote:
> Hello,
> 
> I have upgraded initramfs-tools to version 0.115 and it looks like
its fixed. Same keyboard layout like in version 0.107.

I don't see any changes between 0.109 and 0.115 that might have fixed
this.

It appears that initramfs-tools doesn't work properly with console-
tools (but does work with kbd).  console-tools was removed after
wheezy, so this is now moot.

Ben.
 
-- 
Ben Hutchings
I'm always amazed by the number of people who take up solipsism because
they heard someone else explain it. - E*Borg on alt.fan.pratchett

signature.asc
Description: This is a digitally signed message part

Processed: tagging 785564

[Debian Bug Tracking System]

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

> tags 785564 + pending
Bug #785564 [initramfs-tools] initramfs-tools: Boot fails do to missing 
switch_root
Added tag(s) pending.
> thanks
Stopping processing here.

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

Processed: severity of 737333 is wishlist

[Debian Bug Tracking System]

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

> severity 737333 wishlist
Bug #737333 [initramfs-tools] initramfs-tools: Please support virtfs root
Severity set to 'wishlist' from 'normal'
> thanks
Stopping processing here.

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

Processed: forcibly merging 639876 701656

[Debian Bug Tracking System]

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

> forcemerge 639876 701656
Bug #639876 [initramfs-tools] MODULES=dep does not include input drivers
Bug #772578 [initramfs-tools] [initramfs-tools] Missing keyboard modules 
i2c_designware_* in initramfs
Bug #701656 [initramfs-tools] Include current input drivers when MODULES=dep, 
to support rescue shell
Marked as found in versions initramfs-tools/0.116.
Bug #639876 [initramfs-tools] MODULES=dep does not include input drivers
Marked as found in versions initramfs-tools/0.109.
Marked as found in versions initramfs-tools/0.109.
Bug #772578 [initramfs-tools] [initramfs-tools] Missing keyboard modules 
i2c_designware_* in initramfs
Merged 639876 701656 772578
> thanks
Stopping processing here.

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

Processed: reassign 751955 to console-setup, affects 751955

[Debian Bug Tracking System]

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

> reassign 751955 console-setup 1.134
Bug #751955 [initramfs-tools] initramfs-tools: Warning: error while trying to 
store keymap file - ignoring request to install /etc/boottime.kmap.gz
Bug reassigned from package 'initramfs-tools' to 'console-setup'.
No longer marked as found in versions initramfs-tools/0.120 and 
initramfs-tools/0.115.
Ignoring request to alter fixed versions of bug #751955 to the same values 
previously set
Bug #751955 [console-setup] initramfs-tools: Warning: error while trying to 
store keymap file - ignoring request to install /etc/boottime.kmap.gz
Marked as found in versions console-setup/1.134.
> affects 751955 initramfs-tools
Bug #751955 [console-setup] initramfs-tools: Warning: error while trying to 
store keymap file - ignoring request to install /etc/boottime.kmap.gz
Added indication that 751955 affects initramfs-tools
> thanks
Stopping processing here.

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

Processed: tagging 799443

[Debian Bug Tracking System]

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

> tags 799443 + patch
Bug #799443 [initramfs-tools] initramfs-tools: avoid executing firmware and 
maintain symlinks
Added tag(s) patch.
> thanks
Stopping processing here.

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

Processed: tagging 771158, found 772416 in 0.120, tagging 770912, found 768913 in 0.120, found 721088 in 0.113

[Debian Bug Tracking System]

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

> # Fixing bugs marked as wrong suite
> tags 771158 - experimental
Bug #771158 [initramfs-tools] /etc/kernel/postinst.d/initramfs-tools: please 
support CONFIG_MODULE_COMPRESS=y
Bug #781002 [initramfs-tools] initramfs-tools: does not support 
CONFIG_MODULE_COMPRESS
Bug #781205 [initramfs-tools] initramfs-tools: does not support 
CONFIG_MODULE_COMPRESS
Removed tag(s) experimental.
Removed tag(s) experimental.
Removed tag(s) experimental.
> found 772416 0.120
Bug #772416 [initramfs-tools] initrd: support booting from chroot
Marked as found in versions initramfs-tools/0.120.
> tags 770912 - experimental
Bug #770912 [initramfs-tools] initramfs-tools: Add xhci-pci to base modules 
(linux 3.18)
Bug #773445 [initramfs-tools] linux-image-3.18.0-trunk-686-pae fails to boot 
from encrypted usb drive
Removed tag(s) experimental.
Removed tag(s) experimental.
> found 768913 0.120
Bug #768913 [initramfs-tools] /etc/kernel/postinst.d/initramfs-tools: fragile 
PATH dependency
Marked as found in versions initramfs-tools/0.120.
> found 721088 0.113
Bug #721088 [initramfs-tools] initramfs-tools: nfsroot with pxelinux fails on 
systems with multiple NICs
Marked as found in versions initramfs-tools/0.113.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
721088: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=721088
768913: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=768913
770912: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=770912
771158: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=771158
772416: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=772416
773445: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=773445
781002: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=781002
781205: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=781205
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#512679: initramfs-tools: 'more' pager is broken in initramfs shell

[Ben Hutchings]

It looks like we need to use 'setsid -c' to fix this.  Unfortunately
busybox does not support the -c option and klibc-utils does not have
setsid at all.

Ben.

-- 
Ben Hutchings
I'm always amazed by the number of people who take up solipsism because
they heard someone else explain it. - E*Borg on alt.fan.pratchett


signature.asc
Description: This is a digitally signed message part

Bug#512679: [PATCH initramfs-tools] HACK: scripts/functions: Connect panic shell to single console device

[Ben Hutchings]

This works for me, but it's a gross hack so I'm not going to apply
this version.

Ben.
---
If only one console device is enabled, we can open a shell on that
rather than /dev/console and it will have full control over the tty.
For example, this allows pagers to work.

Unfortunately this depends on 'setsid -c' which is not provided by
busybox or klibc-utils.

Closes: #512679
Signed-off-by: Ben Hutchings 
---
 mkinitramfs   |  4 
 scripts/functions | 21 -
 2 files changed, 24 insertions(+), 1 deletion(-)

diff --git a/mkinitramfs b/mkinitramfs
index b64c7fb..b818751 100755
--- a/mkinitramfs
+++ b/mkinitramfs
@@ -315,6 +315,10 @@ if [ ! -e "${DESTDIR}/bin/sh" ]; then
    copy_exec /bin/sh "${DESTDIR}/bin/"
 fi
 
+# HACK replace busybox setsid with util-linux version
+rm -f "${DESTDIR}/bin/setsid"
+copy_exec /usr/bin/setsid /bin/
+
 # Remove any looping or broken symbolic links, since they break cpio.
 [ "${verbose}" = y ] && xargs_verbose="-t"
 (cd "${DESTDIR}" && find . -type l -printf '%p %Y\n' | sed -n 's/ [LN]$//p' \
diff --git a/scripts/functions b/scripts/functions
index aa53010..7bf346e 100644
--- a/scripts/functions
+++ b/scripts/functions
@@ -33,6 +33,8 @@ log_end_msg()
 
 panic()
 {
+   local console tty_dev rest setsid
+
    if command -v chvt >/dev/null 2>&1; then
    chvt 1
    fi
@@ -56,7 +58,24 @@ panic()
 
    run_scripts /scripts/panic
 
-   REASON="$@" PS1='(initramfs) ' /bin/sh -i /dev/console 
2>&1
+   # Do not use built-in setsid
+   if [ -x /bin/setsid ]; then
+   setsid='/bin/setsid -c'
+   while read console rest; do
+   if [ -z "$tty_dev" ]; then
+   # Single console, so use it directly to enable
+   # full tty control
+   tty_dev="/dev/$console"
+   else
+   # Multiple consoles, so write to them all
+   tty_dev=/dev/console
+   fi
+   done < /proc/consoles
+   else
+   setsid=
+   tty_dev=/dev/console
+   fi
+   REASON="$@" PS1='(initramfs) ' $setsid /bin/sh -i <"$tty_dev" 
>"$tty_dev" 2>&1
 }
 
 maybe_break()
-- 
Ben Hutchings
I'm always amazed by the number of people who take up solipsism because
they heard someone else explain it. - E*Borg on alt.fan.pratchett

signature.asc
Description: This is a digitally signed message part

Processed: tagging 603944

[Debian Bug Tracking System]

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

> tags 603944 + moreinfo
Bug #603944 [initramfs-tools] retry mounting of root
Added tag(s) moreinfo.
> thanks
Stopping processing here.

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

Bug#603944: Updated patch

[Ben Hutchings]

Serge, I'm sorry this patch hasn't had any attention for so long.

On Thu, 9 Dec 2010 15:20:28 -0600 "Serge E. Hallyn" 
 wrote:
> Here is a patch (against the ubuntu package, just as example)
> which instead of doing a dumb retry loop, waits for udev.
> 
> === modified file 'debian/changelog'
> --- debian/changelog  2010-04-26 15:17:47 +
> +++ debian/changelog  2010-12-08 21:44:32 +
> @@ -1,3 +1,15 @@
> +initramfs-tools (0.92bubuntu79) natty; urgency=low
> +
> +  * When using multipath, it is possible that mountroot() will race
> +with udev's renaming of /dev/disk/by-uuid/{rootfs-uuid} from
> +/dev/sd?? to /dev/mapper/something.  After multipath has grabbed
> +the /dev/sd?? and until udev completes the rename, mounting
> +/dev/disk/by-uuid/{rootfs-uuid} will fail with -EBUSY.  In that
> +case, call 'udevsettle' to wait until udev has finished all its
> +related actions. (Closes LP: #686832)
> +
> + -- Serge Hallyn   Fri, 19 Nov 2010 12:19:43 -0600

(Bear in mind that I have no experience of using multipath.)

If one path shows up quickly and the other rather later, can't we still
end up mounting the single-path device rather than the multipath
device?  How do we tell when multipath discovery is complete?

Does it even make sense to specify a multipath device by UUID rather
than by its device-mapper name?  This certainly isn't supported for
LVM.

Ben.

>  initramfs-tools (0.92bubuntu78) lucid; urgency=low
>  
>* hooks/compcache: Escape $-expansions inside < 
> === modified file 'scripts/local'
> --- scripts/local 2009-12-21 23:06:53 +
> +++ scripts/local 2010-11-20 01:03:26 +
> @@ -69,10 +69,19 @@
>   # FIXME This has no error checking
>   [ -n "${FSTYPE}" ] && modprobe ${FSTYPE}
>  
> - # FIXME This has no error checking
>   # Mount root
> - mount ${roflag} ${FSTYPE:+-t ${FSTYPE} }${ROOTFLAGS} ${ROOT} ${rootmnt}
> - mountroot_status="$?"
> + tries=0
> + ret=1
> + while [ $tries -lt 2 -a $ret -ne 0 ]; do
> + mount ${roflag} ${FSTYPE:+-t ${FSTYPE} }${ROOTFLAGS} ${ROOT} 
> ${rootmnt}
> + ret=$?
> + if [ $ret -ne 0 ]; then
> + echo "failed attempt $tries to mount $ROOT as root"
> + udevadm settle
> + tries=$((tries+1))
> + fi
> + done
> + mountroot_status=$ret
>   if [ "$LOOP" ]; then
>   if [ "$mountroot_status" != 0 ]; then
>   if [ ${FSTYPE} = ntfs ] || [ ${FSTYPE} = vfat ]; then
> 
> 
> 
> 
-- 
Ben Hutchings
I'm always amazed by the number of people who take up solipsism because
they heard someone else explain it. - E*Borg on alt.fan.pratchett

signature.asc
Description: This is a digitally signed message part

Processed: tagging 776623

[Debian Bug Tracking System]

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

> tags 776623 + moreinfo unreproducible
Bug #776623 [initramfs-tools] dpkg-reconfigure leaves initramfs-tools in broken 
't' state (dpkg)
Added tag(s) unreproducible and moreinfo.
> thanks
Stopping processing here.

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

Processed: Re: update-initramfs should not set PATH

[Debian Bug Tracking System]

Processing control commands:

> tag -1 wontfix
Bug #597581 [initramfs-tools] update-initramfs should not set PATH
Added tag(s) wontfix.

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

Processed: tagging 753814

[Debian Bug Tracking System]

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

> tags 753814 + wontfix
Bug #753814 [initramfs-tools] update-initramfs produce warnings about missing 
modules dir, when kernel is built with no modules
Added tag(s) wontfix.
> thanks
Stopping processing here.

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

Processed: tagging 762634

[Debian Bug Tracking System]

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

> tags 762634 + moreinfo
Bug #762634 [initramfs-tools] [armhf] mounting rootfs on USB disk fails / some 
USB host controller drivers missing in initramfs
Added tag(s) moreinfo.
> thanks
Stopping processing here.

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

Processed: tagging 807000

[Debian Bug Tracking System]

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

> tags 807000 + patch pending
Bug #807000 [initramfs-tools] initramfs-tools: module nvme not included in 
block modules on kernel > 4.2
Added tag(s) pending and patch.
> thanks
Stopping processing here.

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

Bug#597581: update-initramfs should not set PATH

[Ian Jackson]

Ben Hutchings writes ("Re: update-initramfs should not set PATH"):
> On Wed, 2015-12-09 at 21:56 +, Ian Jackson wrote:
> > Ben Hutchings writes ("Re: update-initramfs should not set PATH"):
> > > I'm not at all convinced that update-initramfs should be sensitive to
> > > the path of the process invoking it.  update-initramfs is not only used
> > > interactively, but also automatically by package installation.
> > 
> > Package installation should also occur with an appropriate PATH.  If
> > PATH contains exciting things then that is presumably deliberate.
> > 
> > See policy 6.1 (last para):
> > 
> >   [...] Maintainer scripts should also not reset the PATH,
> >   though they might choose to modify it by prepending or appending
> >   package-specific directories. These considerations really apply to all
> >   shell scripts.
> > 
> > I think it would be better to follow this recommendation here, unless
> > you have a compelling reason to deviate from our usual practice.
> 
> As update-initramfs is not a maintainer script, I fail to see the relevance.

Firstly, the argument you made above, that update-initramfs is called
"automatically by package installation", seems to be based on the idea
that this is a good reason for setting the PATH.

Secondly, note "These considerations really apply to all shell
scripts".

Ian.

Bug#797881: QNAP TS-219P II: qcontrol no longer works after upgrading to linux-image-4.1.0-0.bpo.1-kirkwood

[Martin Michlmayr]

* Ian Campbell  [2015-10-04 14:04]:
> I suspect this is due to the device path for the input node changing
> from /dev/input/by-path/platform-gpio_keys-event to /dev/input/by
> -path/platform-gpio-keys-event. With the version of qcontrol in Jessie
> it won't even start if it can't find the device, even though it can do
> many of its core things without it (the node is for button input only).
> 
> This is fixed by qcontrol 0.5.4-4 in testing (both looking for old and
> new names, as well as not treating failure to find either as a
> catastrophe), but for Jessie you can just edit the path in
> /etc/qcontrol.conf.
> 
> If that works for you then it might be worth uploading an updated
> qcontrol to backports.

Ian, were you going to upload qcontrol to backports or did you want
someone else to do it?

-- 
Martin Michlmayr
http://www.cyrius.com/

Bug#797880: QNAP TS-219P II with linux-image-4.1.0-0.bpo.1-kirkwood "loses" one hard disk from the RAID while flashing initramfs, causing read-only remount and dpkg to fail

[Martin Michlmayr]

* Robert Schlabbach  [2015-09-03 12:19]:
> Package: linux-image-4.1.0-0.bpo.1-kirkwood
> Version: 4.1.3-1~bpo8+1
> 
> Bad things happen when flash-kernel (3.45) flashes the initramfs with this 
> Linux kernel on my QNAP TS-219P II:

Ian Campbell added a workaround to flash-kernel 3.52 for this kernel
issue.

Can you try if 3.52 works for you?  If so, I guess it makes sense to
upload 3.52 to backports.

-- 
Martin Michlmayr
http://www.cyrius.com/

Processed: tagging 696632

[Debian Bug Tracking System]

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

> tags 696632 + pending
Bug #696632 [initramfs-tools] initramfs-tools: Patches to clean up /run 
handling for jessie
Added tag(s) pending.
> thanks
Stopping processing here.

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

Processed: Re: "modprobe: module css:t0 not found in modules.dep" issued during boot

[Debian Bug Tracking System]

Processing control commands:

> retitle -1 Module aliases should be resolved at build time
Bug #792910 [initramfs-tools] "modprobe: module css:t0 not found in 
modules.dep" issued during boot
Changed Bug title to 'Module aliases should be resolved at build time' from 
'"modprobe: module css:t0 not found in modules.dep" issued during boot'

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

Bug#597581: update-initramfs should not set PATH

[Ian Jackson]

Ben Hutchings writes ("Re: Bug#597581: update-initramfs should not set PATH"):
> > Firstly, the argument you made above, that update-initramfs is called
> > "automatically by package installation", seems to be based on the idea
> > that this is a good reason for setting the PATH.
> 
> My point was that it's called both from interactive shells *and* from
> package upgrades, and there's no reason to think $PATH will be
> consistent between those.

Package upgrades are often run from interactive shells and there is
nothing in the the package upgrade machinery which modifies PATH.

The logic of your argument would seem to apply to almost any program.
Should texmf reset PATH, say ?  I think clearly not.

> > Secondly, note "These considerations really apply to all shell
> > scripts".
> 
> Yet most init scripts reset the PATH because this turns out to be a bad
> idea in reality.
> 
> $ grep -rl 'PATH=[^$]*$' /etc/init.d | wc -l
> 63
> $ grep -rL 'PATH=[^$]*$' /etc/init.d | wc -l
> 44

Daemons are arguably a special case, particularly because many of them
spawn other processes of a very general nature that oughtn't to
inherit an exciting environment.

Ian.

Bug#792910: "modprobe: module css:t0 not found in modules.dep" issued during boot

[Ben Hutchings]

Control: retitle -1 Module aliases should be resolved at build time

On Sun, 19 Jul 2015 22:01:06 -0400 (EDT) Stephen Powell  
wrote:
> Package: initramfs-tools
> Version: 0.120
> Severity: minor
> 
> During boot of a jessie system on the s390x platform, I noticed the
> following error message on the console:
> 
> Begin: Loading essential drivers ...
> modprobe: module css:t0 not found in modules.dep
> 
> The error didn't seem to affect the ability of the system to boot,
> but I decided to investigate.  I traced the problem to the
> sys_walk_modalias function in /usr/share/initramfs-tools/hook-functions.
> The relevant code goes something like this:
> 
>if [ -n "${modalias}" ]; then
>force_load "${modalias}"
>fi
> 
> The problem here is that the code does not distinguish between a regular
> module alias and what I call a udev alias.  (I'm not sure what the proper
> terminology is.  If you know please tell me.)

They're both module aliases.  The ones with colons in are generated at
kernel build time from the device ID tables in each module and at run-
time from the discovered device information.  Although udev handles the
uevents, it's always kmod that matches aliases against the installed
modules.

The specific problem here is that the driver that matches the module
alias 'css:t0' is ccw_device, which is built-in.

[...]
> Most of the udev aliases have asterisks in them.  All of them seem to have
> a colon in them.  I suggest the following code to replace the above:
> 
>case "${modalias}" in
>""|*:*)
>:
>;;
>*)
>force_load "${modalias}"
>;;
>esac
> 
> The attached patch file fixes the problem on my system.

I think this is the wrong approach.  I don't think its make sense to
include *any* module aliases in /conf/modules; only the actual modules
should be listed there.

Ben.

-- 
Ben Hutchings
I'm always amazed by the number of people who take up solipsism because
they heard someone else explain it. - E*Borg on alt.fan.pratchett

signature.asc
Description: This is a digitally signed message part

Bug#807527: initramfs-tools: Please provide an API or best practices for custom initramfs hook configuration

[Guilhem Moulin]

Package: initramfs-tools
Severity: normal
X-Debug-CC: pkg-cryptsetup-de...@lists.alioth.debian.org

Dear Maintainer,

AFAIK there is no documentation for where users should set variables to
configure an initramfs hook.  There are a couple of workaround, all
hacky and/or relying on undocumented properties of initramfs-tools(8):

  1/ Setting said variable in initramfs.conf(5).  (Since hook scripts
 are executed is sub-shells the variable need to be exported.)  This
 is somewhat ugly since initramfs.conf(5) is the configuration file
 *for mkinitramfs*, not for the hook files.

  2/ Using /usr/share/initramfs-tools/conf-hooks.d/$hook.  This is an
 undocumented (short of an entry in the changelog) hack.  Also
 unless that file is marked as a conffile (which violates the
 policy) user modifications are wiped upon upgrade.

  3/ Make /usr/share/initramfs-tools/conf-hooks.d/$hook a symlink to
 /etc/initramfs-tools/conf-hooks.d/$hook.  But again, this uses an
 undocumented property of mkinitramfs(8), and it might hijack your
 /etc/initramfs-tools namespace.

There are packages that ship user configurable initramfs hooks
(cryptsetup and dropbear-initramfs come to mind).  These package need
documented instructions for where to drop user configuration
(/etc/initramfs-tools/conf-hooks.d/$package comes to mind).

Alternatively, in a private discussion with Jonas Meurer of the Debian
Cryptsetup Team (X-Debug-CC), I've been suggested that mkinitramfs(8)
could instead source files in /etc/initramfs-tools/conf-hooks.d/ after
sourcing /usr/share/initramfs-tools/conf-hooks.d/.  This way package
maintainers would ship variables with their default in /usr while users
would write their custom configuration in /etc.

-8<->8-
--- a/mkinitramfs
+++ b/mkinitramfs
@@ -87,6 +87,7 @@
echo "Warning: ${i} is a directory instead of file, ignoring."
elif [ -e "${i}" ]; then
. "${i}"
+   . [ ! -f "/etc/${i#/usr/share/}" ] || . "/etc/${i#/usr/share/}"
fi
 done
 
-8<->8-

Either way, IMHO initramfs-tools(8) should include some instructions for
custom initramfs hook configuration.

Cheers,
-- 
Guilhem.

PS. In fact I've implemented 3/ in dropbear-initramfs a couple of weeks
ago.  Oops…


signature.asc
Description: PGP signature

Processed: block 783393 with 807527, block 786578 with 807527

[Debian Bug Tracking System]

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

> block 783393 with 807527
Bug #783393 [cryptsetup] initramfs-tools: Missing crypto-components in 
initramfs when explicitly requested
783393 was not blocked by any bugs.
783393 was not blocking any bugs.
Added blocking bug(s) of 783393: 807527
> block 786578 with 807527
Bug #786578 [cryptsetup] cryptsetup: crypt asks passphrase instead of using 
keyfile
786578 was not blocked by any bugs.
786578 was not blocking any bugs.
Added blocking bug(s) of 786578: 807527
> thanks
Stopping processing here.

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

Bug#710119: marked as done (initramfs-tools: Installation with dmraid randomly fails to boot)

[Debian Bug Tracking System]

Your message dated Thu, 10 Dec 2015 03:33:26 +
with message-id <1449718406.2824.218.ca...@decadent.org.uk>
and subject line Re: initramfs-tools: Installation with dmraid randomly fails 
to boot
has caused the Debian Bug report #710119,
regarding initramfs-tools: Installation with dmraid randomly 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.)


-- 
710119: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=710119
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: initramfs-tools
Version: 0.109.1
Severity: grave

Dear Maintainer,

I found this bug described very well in bug #699437, but as the author of the 
bug, I strongly believe that the bug is related to initramfs-tools.
My RAID controller is a Silicon Image SiI 3112A SATARaid, configured in RAID1.
I strongly encourage you to read the previously mentionned bug report.

Basically, my box randomly fails to boot (meaning that sometimes it succeds) on 
my RAID partition, with the exact same screen as in the bug #688437.

I tried to add a rootdelay=5 option, which didn't change anything.

I'm not completely sure about that, but it seems that the bug only occurs with 
kernel 3.2 and not with kernel 2.6.

A patch to handle dmraid better would be most appreciated.

Best regards,
Quentin Lefebvre


-- /proc/cmdline
BOOT_IMAGE=/vmlinuz-3.2.0-4-686-pae root=UUID=... ro dmraid=true quiet

-- /etc/kernel-img.conf
# Kernel image management overrides
# See kernel-img.conf(5) for details
do_symlinks = yes
do_bootloader = no
do_initrd = yes
link_in_boot = no

-- /etc/initramfs-tools/initramfs.conf
MODULES=most
BUSYBOX=y
KEYMAP=n
COMPRESS=gzip
DEVICE=
NFSROOT=auto

-- /etc/initramfs-tools/update-initramfs.conf
update_initramfs=yes
backup_initramfs=no

-- System Information:
Debian Release: 7.0
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: i386

Versions of packages initramfs-tools depends on:
ii  cpio   2.11+dfsg-0.1
ii  klibc-utils2.0.1-3.1
ii  kmod   9-3
ii  module-init-tools  9-3
ii  udev   175-7.2

Versions of packages initramfs-tools recommends:
ii  busybox  1:1.20.0-7

Versions of packages initramfs-tools suggests:
ii  bash-completion  1:2.0-1

-- no debconf information
--- End Message ---
--- Begin Message ---
Closing this, as it seems to be caused by a configuration error that
dmraid should warn about.

Ben.

-- 
Ben Hutchings
If more than one person is responsible for a bug, no one is at fault.


signature.asc
Description: This is a digitally signed message part
--- End Message ---

Bug#495946: marked as done (initramfs-tools: potential race condition between nfsmounts in fstab and network interfaces)

[Debian Bug Tracking System]

Your message dated Thu, 10 Dec 2015 03:38:35 +
with message-id <1449718715.2824.221.ca...@decadent.org.uk>
and subject line Re: initramfs-tools: potential race condition between 
nfsmounts in fstab and network interfaces
has caused the Debian Bug report #495946,
regarding initramfs-tools: potential race condition between nfsmounts in fstab 
and network interfaces
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.)


-- 
495946: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=495946
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: initramfs-tools
Version: 0.85i
Severity: important


On a server with three e1000-based cards, I have configured eth0 and 
then bond0 which uses eth1 and eth2.

I have an NFS share that requires mounting on boot and uses the network 
attached to the bonded interface.

If eth0 is listed first in the /etc/network/interfaces file, the system 
tries to mount the share before bond0 is brought up and times out as a 
result (although the timeout appears to be 7 minutes, not 180 seconds).

If I place the "auto bond0" statement as the first statement in the 
file, the system works without issue.

This issue can be replicated using SAMBA in place of NFS and is present 
after a base install with only a few more packages (such as ifenslave) 
installed.

I realise that this may not be an initramfs issue, however I am unable 
to track it down any further.  Please feel free to move to a more 
appropriate package if you think it may be required.

Matt


-- Package-specific info:
-- /proc/cmdline
root=/dev/md0 ro

-- /proc/filesystems
cramfs
ext3

-- lsmod
Module  Size  Used by
button  6672  0 
ac  5188  0 
battery 9636  0 
ipv6  226272  30 
nls_iso8859_1   4256  1 
cifs  190684  1 
dm_snapshot15552  0 
dm_mirror  19152  0 
dm_mod 50232  2 dm_snapshot,dm_mirror
loop   15048  0 
i2c_i8017468  0 
i2c_core   19680  1 i2c_i801
parport_pc 32132  0 
parport33256  1 parport_pc
psmouse35016  0 
serio_raw   6660  0 
evdev   9088  0 
floppy 53156  0 
pcspkr  3072  0 
rtc12372  0 
ext3  119240  4 
jbd52456  1 ext3
mbcache 8356  1 ext3
raid1  21056  5 
md_mod 70388  6 raid1
ide_generic 1408  0 [permanent]
sd_mod 19040  12 
ata_piix   13896  10 
libata 89396  1 ata_piix
scsi_mod  124168  2 sd_mod,libata
generic 4868  0 [permanent]
ide_core  110504  2 ide_generic,generic
ehci_hcd   28136  0 
uhci_hcd   21164  0 
e1000 108832  0 
usbcore   112644  3 ehci_hcd,uhci_hcd
thermal13608  0 
processor  28840  1 thermal
fan 4804  0 
bonding71528  0 

-- kernel-img.conf
# Kernel image management overrides
# See kernel-img.conf(5) for details
do_symlinks = yes
relative_links = yes
do_bootloader = no
do_bootfloppy = no
do_initrd = yes
link_in_boot = no
postinst_hook = update-grub
postrm_hook   = update-grub


-- System Information:
Debian Release: 4.0
  APT prefers stable
  APT policy: (500, 'stable')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.18-6-686
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)

Versions of packages initramfs-tools depends on:
ii  busybox   1:1.1.3-4  Tiny utilities for small and embed
ii  cpio  2.6-18.1+etch1 GNU cpio -- a program to manage ar
ii  klibc-utils   1.4.34-2   small statically-linked utilities 
ii  module-init-tools 3.3-pre4-2 tools for managing Linux kernel mo
ii  udev  0.105-4/dev/ and hotplug management daemo

initramfs-tools recommends no packages.

-- no debconf information


--- End Message ---
--- Begin Message ---
I'm sorry this bug report was left for so long.

initramfs-tools has no responsibility for mounting anything but the
root and /usr filesystems.  Since you are not using an NFS-root, I
don't believe it has anything to do with the problem you had.

If you still have problems with NFS mounts, please report them against
nfs-common.

Ben.

-- 
Ben Hutchings
If more than one person is 

Processed: Re: linux-image-3.12-1-amd64: kernel does not boot

[Debian Bug Tracking System]

Processing control commands:

> retitle -1 RAID boot failure with Linux 3.10
Bug #730049 [initramfs-tools] linux-image-3.12-1-amd64: kernel does not boot
Changed Bug title to 'RAID boot failure with Linux 3.10' from 
'linux-image-3.12-1-amd64: kernel does not boot'
> tag -1 moreinfo
Bug #730049 [initramfs-tools] RAID boot failure with Linux 3.10
Added tag(s) moreinfo.

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

Bug#730049: linux-image-3.12-1-amd64: kernel does not boot

[Ben Hutchings]

Control: retitle -1 RAID boot failure with Linux 3.10
Control: tag -1 moreinfo

I'm treating this bug (#730049) as covering the boot failure described
in message #14  and bug #717698 as
covering the original boot failure described in messages #5, #24, etc.
Please keep these issues separate.

Do you still see a failure to set up the RAID ("mdadm: No devices
listed in conf file were found") on some machines?  Can you send the
/etc/mdadm.conf file from one of those?

Ben.

-- 
Ben Hutchings
If more than one person is responsible for a bug, no one is at fault.



signature.asc
Description: This is a digitally signed message part

Processed: tagging 783620

[Debian Bug Tracking System]

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

> tags 783620 + pending
Bug #783620 [initramfs-tools] initramfs-tools: initramfs broken on first boot 
into Jessie, "Unable to mount root fs on unknown-block(0, 0)"
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#717698: Problem sort of went away with 3.11

[Ben Hutchings]

Control: tag -1 moreinfo

On Tue, 19 Nov 2013 15:13:43 +0100 Toni Mueller 
wrote:
> 
> Hello,
> 
> I installed
> 
> linux-image-3.11-2-amd64  3.11.7-1
> 
> and this kernel seems to boot at the second or third attempt at the
> latest, while the 3.10 kernel usually refused to boot even after five or
> more attempts.
> 
> By attempt, I mean successive attempts directly after power-up, not
> across power cycles.
> 
> I have attached a dmesg for the 3.11 kernel I am currently running.

What's the status of this issue in the jessie kernel version?

Ben.

-- 
Ben Hutchings
If more than one person is responsible for a bug, no one is at fault.


signature.asc
Description: This is a digitally signed message part

Processed: tagging 730049

[Debian Bug Tracking System]

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

> tags 730049 - jessie sid stretch
Bug #730049 [initramfs-tools] linux-image-3.12-1-amd64: kernel does not boot
Removed tag(s) stretch, sid, and jessie.
> thanks
Stopping processing here.

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

Processed: Re: Problem sort of went away with 3.11

[Debian Bug Tracking System]

Processing control commands:

> tag -1 moreinfo
Bug #717698 [src:linux] linux-image-3.10-1-amd64: kernel does not boot
Added tag(s) moreinfo.

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

Processed: limit source to initramfs-tools, tagging 795831

[Debian Bug Tracking System]

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

> limit source initramfs-tools
Limiting to bugs with field 'source' containing at least one of 
'initramfs-tools'
Limit currently set to 'source':'initramfs-tools'

> tags 795831 + pending
Bug #795831 [initramfs-tools] initramfs-tools: ensure error output from 
switch_root/run-init are on the console
Added tag(s) pending.
> thanks
Stopping processing here.

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

Processed: forcibly merging 797361 804446

[Debian Bug Tracking System]

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

> forcemerge 797361 804446
Bug #797361 [initramfs-tools] initramfs-tools: hooks/fsck includes too many 
tools
Bug #804446 [initramfs-tools] initramfs-tools: Do not include fsck tools for 
non-fscable filesystems
Added tag(s) pending.
Merged 797361 804446
> thanks
Stopping processing here.

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

Processed: reassign 790385 to src:zfs-linux

[Debian Bug Tracking System]

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

> reassign 790385 src:zfs-linux
Bug #790385 [initramfs-tools] initramfs-tools: breaks building initramfs for 
zfs over (mirrored) LUKS - "can't find root device"
Bug reassigned from package 'initramfs-tools' to 'src:zfs-linux'.
Warning: Unknown package 'src:zfs-linux'
Warning: Unknown package 'src:zfs-linux'
No longer marked as found in versions initramfs-tools/0.120.
Warning: Unknown package 'src:zfs-linux'
Warning: Unknown package 'src:zfs-linux'
Ignoring request to alter fixed versions of bug #790385 to the same values 
previously set
Warning: Unknown package 'src:zfs-linux'
> thanks
Stopping processing here.

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

Processed: tagging 781002

[Debian Bug Tracking System]

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

> tags 781002 - moreinfo
Bug #781002 [initramfs-tools] initramfs-tools: does not support 
CONFIG_MODULE_COMPRESS
Bug #771158 [initramfs-tools] /etc/kernel/postinst.d/initramfs-tools: please 
support CONFIG_MODULE_COMPRESS=y
Bug #781205 [initramfs-tools] initramfs-tools: does not support 
CONFIG_MODULE_COMPRESS
Removed tag(s) moreinfo.
Removed tag(s) moreinfo.
Removed tag(s) moreinfo.
> thanks
Stopping processing here.

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

Processed: tagging 792910

[Debian Bug Tracking System]

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

> tags 792910 - patch
Bug #792910 [initramfs-tools] Module aliases should be resolved at build time
Removed tag(s) patch.
> thanks
Stopping processing here.

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

Bug#807527: initramfs-tools: Please provide an API or best practices for custom initramfs hook configuration

[Guilhem Moulin]

s/X-Debug-CC/X-Debbugs-CC/

-- 
Guilhem.


signature.asc
Description: PGP signature

Bug#777243: marked as done (Boot fails due to missing ext4 module)

[Debian Bug Tracking System]

Your message dated Thu, 10 Dec 2015 03:47:37 +
with message-id <1449719257.2824.224.ca...@decadent.org.uk>
and subject line Re: Boot fails due to missing ext4 module
has caused the Debian Bug report #777243,
regarding Boot fails due to missing ext4 module
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.)


-- 
777243: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=777243
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: kernel-package
Version: 13.014+nmu1
Severity: grave
Tags: newcomer
Justification: renders package unusable

I've upgraded my LG notebook (X-note: LS50a) from wheezy to jessie and:
1. the upgrade have installed kernel "version-i585" in addition to my earlier
(automatically installed during an upgrade to wheezy) "version-i486".
2. when booting "i486", it fails to modprobe "ext4-fs" during the boot. It
breaks boot sequence, but manual (from shell prompt) modprobe ext4 does not
load the module into the kernel.
3. when booting "i586", it fails to load kernel module responsible for notebook
keyboard (touchpad is loaded OK). USB keyboard works fine.
4. DRM:i9xx fails to configure with "*ERROR* pipe A underrun"



-- System Information:
Debian Release: 8.0
  APT prefers testing
  APT policy: (990, 'testing')
Architecture: i386 (i686)

Kernel: Linux 3.16.0-4-586
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Init: systemd (via /run/systemd/system)

Versions of packages kernel-package depends on:
ii  bc   1.06.95-9
ii  binutils 2.24.90.20141023-1
ii  build-essential  11.7
ii  bzip21.0.6-7+b2
ii  dpkg-dev 1.17.23
ii  file 1:5.20-2
ii  gettext  0.19.3-2
ii  kmod 18-3
ii  lzma 9.22-2
ii  po-debconf   1.0.16+nmu3
ii  xmlto0.0.25-2
ii  xz-utils [lzma]  5.1.1alpha+20120614-2+b3

Versions of packages kernel-package recommends:
ii  cpio   2.11+dfsg-4
ii  docbook-utils  0.6.14-3
ii  kernel-common  13.014+nmu1
pn  uboot-mkimage  

Versions of packages kernel-package suggests:
ii  libncurses5-dev [libncurses-dev]  5.9+20140913-1+b1
pn  linux-source  

-- no debconf information
--- End Message ---
--- Begin Message ---
Sorry, I'm out of ideas here.  We already established that the bug
appears some time after the real init system is running, so it's not a
bug in initramfs-tools, but it's not clear what *is* at fault.

If the problem has not somehow been solved already, you should use one
of the support mailing lists or web site to get help:
.

Ben.

-- 
Ben Hutchings
If more than one person is responsible for a bug, no one is at fault.


signature.asc
Description: This is a digitally signed message part
--- End Message ---

Bug#797881: QNAP TS-219P II: qcontrol no longer works after upgrading to linux-image-4.1.0-0.bpo.1-kirkwood

[Ian Campbell]

On Wed, 2015-12-09 at 16:04 -0800, Martin Michlmayr wrote:
> * Ian Campbell  [2015-10-04 14:04]:
> > I suspect this is due to the device path for the input node
> changing
> > from /dev/input/by-path/platform-gpio_keys-event to /dev/input/by
> > -path/platform-gpio-keys-event. With the version of qcontrol in
> Jessie
> > it won't even start if it can't find the device, even though it can
> do
> > many of its core things without it (the node is for button input
> only).
> > 
> > This is fixed by qcontrol 0.5.4-4 in testing (both looking for old
> and
> > new names, as well as not treating failure to find either as a
> > catastrophe), but for Jessie you can just edit the path in
> > /etc/qcontrol.conf.
> > 
> > If that works for you then it might be worth uploading an updated
> > qcontrol to backports.
> 
> Ian, were you going to upload qcontrol to backports or did you want
> someone else to do it?

I wasn't, but now I am. I've left a build going and will (hopefully)
upload after breakfast.

Ian.