Processed: Re: Bug#774977: upgrade-reports: dist-upgrade (jessi 3.14-2-amd64 -> 3.16.0-4-amd64): xserver unable to identify monitor -> fallback to vesa/not configurable

2015-01-18 Thread Debian Bug Tracking System 
Processing control commands:

> reassign -1 src:linux 3.16.7-ckt2-1
Bug #774977 [upgrade-reports] upgrade-reports: dist-upgrade (jessi 3.14-2-amd64 
-> 3.16.0-4-amd64): xserver unable to identify monitor -> fallback to vesa/not 
configurable
Bug reassigned from package 'upgrade-reports' to 'src:linux'.
Ignoring request to alter found versions of bug #774977 to the same values 
previously set
Ignoring request to alter fixed versions of bug #774977 to the same values 
previously set
Bug #774977 [src:linux] upgrade-reports: dist-upgrade (jessi 3.14-2-amd64 -> 
3.16.0-4-amd64): xserver unable to identify monitor -> fallback to vesa/not 
configurable
Marked as found in versions linux/3.16.7-ckt2-1.

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


--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
https://lists.debian.org/handler.s.b774977.142165206332724.transcr...@bugs.debian.org

Re: Bug#774977: upgrade-reports: dist-upgrade (jessi 3.14-2-amd64 -> 3.16.0-4-amd64): xserver unable to identify monitor -> fallback to vesa/not configurable

2015-01-18 Thread Julien Cristau 
Control: reassign -1 src:linux 3.16.7-ckt2-1

On Fri, Jan  9, 2015 at 17:14:48 +0100, Thorben Kaufmann wrote:

> Gfx:
> Asus NVIDIA GeForce GTX750TI
> + nouveau driver
> Board:
> Asus Sabertooth 990FX R2.0 + AMD FX8350
> 
> Problem:
> When dist-upgrading 3.14-2-amd64 to 3.16.0-4-amd64 grafik mode is locked to 
> either 640x480 or 800x600 on DVI with ugly pixelation.
> By trying to configure a higher resolution, only HDMI-Port works with 
> 1024x768 (also pixelated). Chars are almost unreadable.
> One problem seems to be missing ability to read out monitor data. 
> Reboot with old kernel works around that issue (Resolution 1920x1400).
> 
Please provide kernel and X logs for old and new kernel.

Thanks,
Julien


signature.asc
Description: Digital signature

Bug#775712: dvb: support for new tuner device request -- hauppauge wintv hvr 2255

2015-01-18 Thread Brian Paterni 
Package: src:linux
Version: 3.16.7-ckt4-1
Severity: normal

Dear Maintainer,

I recently purchased a PCIe DVB tuner advertised as a

Hauppauge WinTV-HVR-2250

However, what was in the box was actually a more recent revision of the
hardware known as a:

Hauppauge WinTV-HVR-2255

Looking at my kernel log though, it appears this new device is
unsupported at the time of this writing. I would much appreciate it if
support could be added for this newer hardware. Please let me know if
there's anything I can do to help with the process


-- Package-specific info:
** Version:
Linux version 3.16.0-4-amd64 (debian-kernel@lists.debian.org) (gcc version 
4.8.4 (Debian 4.8.4-1) ) #1 SMP Debian 3.16.7-ckt4-1 (2015-01-16)

** Command line:
BOOT_IMAGE=/vmlinuz-3.16.0-4-amd64 root=/dev/mapper/hafx-root ro

** Not tainted

** Kernel log:
[3.924837] EXT4-fs (dm-0): re-mounted. Opts: errors=remount-ro
[3.927200] sp5100_tco: SP5100/SB800 TCO WatchDog Timer Driver v0.05
[3.927381] snd_hda_intel :01:00.1: enabling device ( -> 0002)
[3.927416] snd_hda_intel :01:00.1: Handle VGA-switcheroo audio client
[3.927445] snd_hda_intel :01:00.1: irq 100 for MSI/MSI-X
[3.927489] snd_hda_intel :06:00.1: enabling device ( -> 0002)
[3.927521] snd_hda_intel :06:00.1: Handle VGA-switcheroo audio client
[3.932961] snd_hda_intel :06:00.1: irq 101 for MSI/MSI-X
[3.933085] sp5100_tco: PCI Revision ID: 0x42
[3.933111] sp5100_tco: Using 0xfed80b00 for watchdog MMIO address
[3.933121] sp5100_tco: Last reboot was not triggered by watchdog.
[3.933201] sp5100_tco: initialized (0xc900018bab00). heartbeat=60 sec 
(nowayout=0)
[3.942836] saa7164 driver loaded
[3.942886] saa7164 :05:00.0: enabling device ( -> 0002)
[3.942947] saa7164[0]: Your board isn't known (yet) to the driver.
saa7164[0]: Try to pick one of the existing card configs via
saa7164[0]: card= insmod option.  Updating to the latest
saa7164[0]: version might help as well.
[3.942947] saa7164[0]: Here are valid choices for the card= insmod 
option:
[3.942948] saa7164[0]:card=0 -> Unknown
[3.942948] saa7164[0]:card=1 -> Generic Rev2
[3.942949] saa7164[0]:card=2 -> Generic Rev3
[3.942949] saa7164[0]:card=3 -> Hauppauge WinTV-HVR2250
[3.942950] saa7164[0]:card=4 -> Hauppauge WinTV-HVR2200
[3.942950] saa7164[0]:card=5 -> Hauppauge WinTV-HVR2200
[3.942951] saa7164[0]:card=6 -> Hauppauge WinTV-HVR2200
[3.942951] saa7164[0]:card=7 -> Hauppauge WinTV-HVR2250
[3.942952] saa7164[0]:card=8 -> Hauppauge WinTV-HVR2250
[3.942952] saa7164[0]:card=9 -> Hauppauge WinTV-HVR2200
[3.942953] saa7164[0]:card=10 -> Hauppauge WinTV-HVR2200
[3.942986] CORE saa7164[0]: subsystem: 0070:f111, board: Unknown 
[card=0,autodetected]
[3.942989] saa7164[0]/0: found at :05:00.0, rev: 129, irq: 47, latency: 
0, mmio: 0xfe00
[3.943011] saa7164_initdev() Unsupported board detected, registering 
without firmware
[3.962011] input: HD-Audio Generic HDMI/DP,pcm=3 as 
/devices/pci:00/:00:0b.0/:06:00.1/sound/card2/input10
[3.962255] input: HD-Audio Generic HDMI/DP,pcm=7 as 
/devices/pci:00/:00:0b.0/:06:00.1/sound/card2/input11
[3.962366] input: HD-Audio Generic HDMI/DP,pcm=8 as 
/devices/pci:00/:00:0b.0/:06:00.1/sound/card2/input12
[3.962515] input: HD-Audio Generic HDMI/DP,pcm=9 as 
/devices/pci:00/:00:0b.0/:06:00.1/sound/card2/input13
[3.962599] input: HD-Audio Generic HDMI/DP,pcm=10 as 
/devices/pci:00/:00:0b.0/:06:00.1/sound/card2/input14
[3.962673] input: HD-Audio Generic HDMI/DP,pcm=11 as 
/devices/pci:00/:00:0b.0/:06:00.1/sound/card2/input15
[3.962786] input: HD-Audio Generic HDMI/DP,pcm=3 as 
/devices/pci:00/:00:02.0/:01:00.1/sound/card1/input16
[3.962884] input: HD-Audio Generic HDMI/DP,pcm=7 as 
/devices/pci:00/:00:02.0/:01:00.1/sound/card1/input17
[3.965282] input: HD-Audio Generic HDMI/DP,pcm=8 as 
/devices/pci:00/:00:02.0/:01:00.1/sound/card1/input18
[3.965483] input: HD-Audio Generic HDMI/DP,pcm=9 as 
/devices/pci:00/:00:02.0/:01:00.1/sound/card1/input19
[3.965727] input: HD-Audio Generic HDMI/DP,pcm=10 as 
/devices/pci:00/:00:02.0/:01:00.1/sound/card1/input20
[3.965893] input: HD-Audio Generic HDMI/DP,pcm=11 as 
/devices/pci:00/:00:02.0/:01:00.1/sound/card1/input21
[3.969527] AVX version of gcm_enc/dec engaged.
[3.979538] alg: No test for __gcm-aes-aesni (__driver-gcm-aes-aesni)
[3.981777] pstore: Registered efi as persistent store backend
[3.984908] sound hdaudioC0D0: autoconfig: line_outs=4 
(0x14/0x15/0x16/0x17/0x0) type:line
[3.984910] sound hdaudioC0D0:speaker_outs=0 (0x0/0x0/0x0/0x0/0x0)
[3.984911] sound hdaudioC0D0:hp_outs=1 (0x1b/0x0/0x0/0x0/0x0)
[3.984911] sound hdaudioC0D0:mon

linux_3.18.3-1~exp1_multi.changes ACCEPTED into experimental

2015-01-18 Thread Debian FTP Masters 


Accepted:

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 18 Jan 2015 20:48:06 +
Source: linux
Binary: linux-source-3.18 linux-doc-3.18 linux-manual-3.18 
linux-support-3.18.0-trunk linux-libc-dev linux-headers-3.18.0-trunk-all 
linux-headers-3.18.0-trunk-all-alpha linux-headers-3.18.0-trunk-common 
linux-image-3.18.0-trunk-alpha-generic linux-headers-3.18.0-trunk-alpha-generic 
linux-image-3.18.0-trunk-alpha-smp linux-headers-3.18.0-trunk-alpha-smp 
linux-image-3.18.0-trunk-alpha-legacy linux-headers-3.18.0-trunk-alpha-legacy 
linux-headers-3.18.0-trunk-all-amd64 kernel-image-3.18.0-trunk-amd64-di 
nic-modules-3.18.0-trunk-amd64-di nic-wireless-modules-3.18.0-trunk-amd64-di 
nic-shared-modules-3.18.0-trunk-amd64-di serial-modules-3.18.0-trunk-amd64-di 
usb-serial-modules-3.18.0-trunk-amd64-di ppp-modules-3.18.0-trunk-amd64-di 
pata-modules-3.18.0-trunk-amd64-di cdrom-core-modules-3.18.0-trunk-amd64-di 
firewire-core-modules-3.18.0-trunk-amd64-di 
scsi-core-modules-3.18.0-trunk-amd64-di scsi-modules-3.18.0-trunk-amd64-di 
scsi-common-modules-3.18.0-trunk-amd64-di
 scsi-extra-modules-3.18.0-trunk-amd64-di loop-modules-3.18.0-trunk-amd64-di 
btrfs-modules-3.18.0-trunk-amd64-di ext4-modules-3.18.0-trunk-amd64-di 
isofs-modules-3.18.0-trunk-amd64-di jfs-modules-3.18.0-trunk-amd64-di 
ntfs-modules-3.18.0-trunk-amd64-di xfs-modules-3.18.0-trunk-amd64-di 
fat-modules-3.18.0-trunk-amd64-di md-modules-3.18.0-trunk-amd64-di 
multipath-modules-3.18.0-trunk-amd64-di usb-modules-3.18.0-trunk-amd64-di 
usb-storage-modules-3.18.0-trunk-amd64-di 
pcmcia-storage-modules-3.18.0-trunk-amd64-di fb-modules-3.18.0-trunk-amd64-di 
input-modules-3.18.0-trunk-amd64-di event-modules-3.18.0-trunk-amd64-di 
mouse-modules-3.18.0-trunk-amd64-di nic-pcmcia-modules-3.18.0-trunk-amd64-di 
pcmcia-modules-3.18.0-trunk-amd64-di nic-usb-modules-3.18.0-trunk-amd64-di 
sata-modules-3.18.0-trunk-amd64-di core-modules-3.18.0-trunk-amd64-di 
acpi-modules-3.18.0-trunk-amd64-di i2c-modules-3.18.0-trunk-amd64-di 
crc-modules-3.18.0-trunk-amd64-di crypto-modules-3.18.0-trunk-amd64-di
 crypto-dm-modules-3.18.0-trunk-amd64-di efi-modules-3.18.0-trunk-amd64-di 
ata-modules-3.18.0-trunk-amd64-di mmc-core-modules-3.18.0-trunk-amd64-di 
mmc-modules-3.18.0-trunk-amd64-di nbd-modules-3.18.0-trunk-amd64-di 
squashfs-modules-3.18.0-trunk-amd64-di speakup-modules-3.18.0-trunk-amd64-di 
virtio-modules-3.18.0-trunk-amd64-di uinput-modules-3.18.0-trunk-amd64-di 
sound-modules-3.18.0-trunk-amd64-di hyperv-modules-3.18.0-trunk-amd64-di 
udf-modules-3.18.0-trunk-amd64-di fuse-modules-3.18.0-trunk-amd64-di 
linux-image-3.18.0-trunk-amd64 linux-headers-3.18.0-trunk-amd64 
linux-image-3.18.0-trunk-amd64-dbg xen-linux-system-3.18.0-trunk-amd64 
linux-headers-3.18.0-trunk-all-arm64 kernel-image-3.18.0-trunk-arm64-di 
nic-modules-3.18.0-trunk-arm64-di nic-wireless-modules-3.18.0-trunk-arm64-di 
nic-shared-modules-3.18.0-trunk-arm64-di ppp-modules-3.18.0-trunk-arm64-di 
cdrom-core-modules-3.18.0-trunk-arm64-di scsi-core-modules-3.18.0-trunk-arm64-di
 scsi-modules-3.18.0-trunk-arm64-di loop-modules-3.18.0-trunk-arm64-di 
btrfs-modules-3.18.0-trunk-arm64-di ext4-modules-3.18.0-trunk-arm64-di 
isofs-modules-3.18.0-trunk-arm64-di jfs-modules-3.18.0-trunk-arm64-di 
xfs-modules-3.18.0-trunk-arm64-di fat-modules-3.18.0-trunk-arm64-di 
md-modules-3.18.0-trunk-arm64-di multipath-modules-3.18.0-trunk-arm64-di 
usb-modules-3.18.0-trunk-arm64-di usb-storage-modules-3.18.0-trunk-arm64-di 
input-modules-3.18.0-trunk-arm64-di event-modules-3.18.0-trunk-arm64-di 
nic-usb-modules-3.18.0-trunk-arm64-di sata-modules-3.18.0-trunk-arm64-di 
core-modules-3.18.0-trunk-arm64-di crc-modules-3.18.0-trunk-arm64-di 
crypto-modules-3.18.0-trunk-arm64-di crypto-dm-modules-3.18.0-trunk-arm64-di 
efi-modules-3.18.0-trunk-arm64-di ata-modules-3.18.0-trunk-arm64-di 
mmc-modules-3.18.0-trunk-arm64-di nbd-modules-3.18.0-trunk-arm64-di 
squashfs-modules-3.18.0-trunk-arm64-di virtio-modules-3.18.0-trunk-arm64-di 
uinput-modules-3.18.0-trunk-arm64-di
 zlib-modules-3.18.0-trunk-arm64-di udf-modules-3.18.0-trunk-arm64-di 
fuse-modules-3.18.0-trunk-arm64-di linux-image-3.18.0-trunk-arm64 
linux-headers-3.18.0-trunk-arm64 linux-image-3.18.0-trunk-arm64-dbg 
linux-headers-3.18.0-trunk-all-armel kernel-image-3.18.0-trunk-kirkwood-di 
nic-modules-3.18.0-trunk-kirkwood-di 
nic-shared-modules-3.18.0-trunk-kirkwood-di 
usb-serial-modules-3.18.0-trunk-kirkwood-di 
ppp-modules-3.18.0-trunk-kirkwood-di 
cdrom-core-modules-3.18.0-trunk-kirkwood-di 
scsi-core-modules-3.18.0-trunk-kirkwood-di 
loop-modules-3.18.0-trunk-kirkwood-di btrfs-modules-3.18.0-trunk-kirkwood-di 
ext4-modules-3.18.0-trunk-kirkwood-di isofs-modules-3.18.0-trunk-kirkwood-di 
jfs-modules-3.18.0-trunk-kirkwood-di fat-modules-3.18.0-trunk-kirkwood-di 
minix-modules-3.18.0-trunk-kirkwood-di md-modules-3.18.0-trunk-kirkwood-di 
multipath-modules-3.18.0-trunk-kirkwood-di usb-modules-3.18.0-trunk-kirkwood-di 
usb-storage-modules-3.18

Processing of linux_3.18.3-1~exp1_multi.changes

2015-01-18 Thread Debian FTP Masters 
linux_3.18.3-1~exp1_multi.changes uploaded successfully to localhost
along with the files:
  linux_3.18.3-1~exp1.dsc
  linux_3.18.3.orig.tar.xz
  linux_3.18.3-1~exp1.debian.tar.xz
  linux-support-3.18.0-trunk_3.18.3-1~exp1_all.deb
  linux-doc-3.18_3.18.3-1~exp1_all.deb
  linux-manual-3.18_3.18.3-1~exp1_all.deb
  linux-source-3.18_3.18.3-1~exp1_all.deb

Greetings,

Your Debian queue daemon (running on host franck.debian.org)


-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/e1yd1je-yi...@franck.debian.org

Bug#775611: marked as done ([sh]: FTBFS due to unknown compiler option '-m32')

2015-01-18 Thread Debian Bug Tracking System 
Your message dated Mon, 19 Jan 2015 01:49:50 +
with message-id 
and subject line Bug#775611: fixed in linux 3.18.3-1~exp1
has caused the Debian Bug report #775611,
regarding [sh]: FTBFS due to unknown compiler option '-m32'
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.)


-- 
775611: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=775611
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: linux
Version: 3.16.7-ckt4-1
Severity: normal
Tags: patch

Hi!

The kernel package currently fails to build from source on sh4 since
the build scripts try to pass the '-m32' compiler option on gcc which
is not available with gcc on sh4 (also according to the manpage).

Selecting HAVE_C_RECORDMCOUNT in arch/sh/Kconfig (see attached patch
by Ben Hutchings) fixes the issues. However, I also suggest removing
the line "$cc .= " -m32";" for sh compiler options in scripts/
recordmcount.pl.

Thanks!
Adrian
diff --git a/arch/sh/Kconfig b/arch/sh/Kconfig
index 0f09f52..b2c9904 100644
--- a/arch/sh/Kconfig
+++ b/arch/sh/Kconfig
@@ -44,6 +44,7 @@ config SUPERH
   select OLD_SIGSUSPEND
   select OLD_SIGACTION
   select HAVE_ARCH_AUDITSYSCALL
+  select HAVE_C_RECORDMCOUNT
   help
 The SuperH is a RISC processor targeted for use in embedded systems
   and consumer electronics; it was also used in the Sega Dreamcast
--- End Message ---
--- Begin Message ---
Source: linux
Source-Version: 3.18.3-1~exp1

We believe that the bug you reported is fixed in the latest version of
linux, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 775...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Ben Hutchings  (supplier of updated linux package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 18 Jan 2015 20:48:06 +
Source: linux
Binary: linux-source-3.18 linux-doc-3.18 linux-manual-3.18 
linux-support-3.18.0-trunk linux-libc-dev linux-headers-3.18.0-trunk-all 
linux-headers-3.18.0-trunk-all-alpha linux-headers-3.18.0-trunk-common 
linux-image-3.18.0-trunk-alpha-generic linux-headers-3.18.0-trunk-alpha-generic 
linux-image-3.18.0-trunk-alpha-smp linux-headers-3.18.0-trunk-alpha-smp 
linux-image-3.18.0-trunk-alpha-legacy linux-headers-3.18.0-trunk-alpha-legacy 
linux-headers-3.18.0-trunk-all-amd64 kernel-image-3.18.0-trunk-amd64-di 
nic-modules-3.18.0-trunk-amd64-di nic-wireless-modules-3.18.0-trunk-amd64-di 
nic-shared-modules-3.18.0-trunk-amd64-di serial-modules-3.18.0-trunk-amd64-di 
usb-serial-modules-3.18.0-trunk-amd64-di ppp-modules-3.18.0-trunk-amd64-di 
pata-modules-3.18.0-trunk-amd64-di cdrom-core-modules-3.18.0-trunk-amd64-di 
firewire-core-modules-3.18.0-trunk-amd64-di 
scsi-core-modules-3.18.0-trunk-amd64-di scsi-modules-3.18.0-trunk-amd64-di 
scsi-common-modules-3.18.0-trunk-amd64-di
 scsi-extra-modules-3.18.0-trunk-amd64-di loop-modules-3.18.0-trunk-amd64-di 
btrfs-modules-3.18.0-trunk-amd64-di ext4-modules-3.18.0-trunk-amd64-di 
isofs-modules-3.18.0-trunk-amd64-di jfs-modules-3.18.0-trunk-amd64-di 
ntfs-modules-3.18.0-trunk-amd64-di xfs-modules-3.18.0-trunk-amd64-di 
fat-modules-3.18.0-trunk-amd64-di md-modules-3.18.0-trunk-amd64-di 
multipath-modules-3.18.0-trunk-amd64-di usb-modules-3.18.0-trunk-amd64-di 
usb-storage-modules-3.18.0-trunk-amd64-di 
pcmcia-storage-modules-3.18.0-trunk-amd64-di fb-modules-3.18.0-trunk-amd64-di 
input-modules-3.18.0-trunk-amd64-di event-modules-3.18.0-trunk-amd64-di 
mouse-modules-3.18.0-trunk-amd64-di nic-pcmcia-modules-3.18.0-trunk-amd64-di 
pcmcia-modules-3.18.0-trunk-amd64-di nic-usb-modules-3.18.0-trunk-amd64-di 
sata-modules-3.18.0-trunk-amd64-di core-modules-3.18.0-trunk-amd64-di 
acpi-modules-3.18.0-trunk-amd64-di i2c-modules-3.18.0-trunk-amd64-di 
crc-modules-3.18.0-trunk-amd64-di crypto-modules-3.18.0-trunk-amd64-di
 crypto-dm-modules-3.18.0-trunk-amd64-di efi-modules-3.18.0-trunk-amd64-di 
ata-modules-3.18.0-trunk-amd64-di mmc-core-modules-3.18.0-trunk-amd64-di 
mmc-modules-3.18.0-trunk-amd64-di nbd-modules-3.18.0-trunk-amd64-di 
squashfs-modules-3.18.0-trunk-amd64-di speakup-modules-3.18.0-trunk-amd64-di 
virtio-modules-3.18.0-trunk-amd64-di uinput-modules-3.18.0-trunk-am

Bug#770102: marked as done (PATCH: fix packaging the hppa kernel package)

2015-01-18 Thread Debian Bug Tracking System 
Your message dated Mon, 19 Jan 2015 01:49:50 +
with message-id 
and subject line Bug#770102: fixed in linux 3.18.3-1~exp1
has caused the Debian Bug report #770102,
regarding PATCH: fix packaging the hppa kernel package
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.)


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

Source: linux
Version: 3.16.7-2
Severity: important
Tags: patch

Dear debian kernel maintainers,

please apply the attached patch to the debian kernel sources for the next 
upload.
It fixes this error when building and packaging the debian hppa kernel:
...
kernel-wedge install-files 3.16.0-4
...
kernel-wedge find-dups 3.16.0-4-parisc
some modules are in more than one package
debian/pata-modules-3.16.0-4-parisc-di 
lib/modules/3.16.0-4-parisc/kernel/drivers/ata/libata.ko
debian/ata-modules-3.16.0-4-parisc-di 
lib/modules/3.16.0-4-parisc/kernel/drivers/ata/libata.ko
command exited with status 1

Thanks,
Helge
diff -up ./linux-3.16.7/debian/installer/hppa/modules/hppa/ata-modules.org ./linux-3.16.7/debian/installer/hppa/modules/hppa/ata-modules
--- ./linux-3.16.7/debian/installer/hppa/modules/hppa/ata-modules.org	2014-11-05 22:27:31.0 +0100
+++ ./linux-3.16.7/debian/installer/hppa/modules/hppa/ata-modules	2014-11-13 14:58:24.0 +0100
@@ -1 +1,2 @@
 #include 
+libata -
diff -up ./linux-3.16.7/debian/installer/hppa/package-list.org ./linux-3.16.7/debian/installer/hppa/package-list
--- ./linux-3.16.7/debian/installer/hppa/package-list.org	2014-09-08 06:58:01.0 +0200
+++ ./linux-3.16.7/debian/installer/hppa/package-list	2014-11-13 22:38:11.0 +0100
@@ -12,7 +12,7 @@ Package: ide-modules
 Depends: kernel-image, ide-core-modules, nls-core-modules
 
 Package: pata-modules
-Depends: kernel-image, scsi-core-modules
+Depends: kernel-image, ata-modules, scsi-core-modules
 
 Package: fb-modules
 Depends: kernel-image
--- End Message ---
--- Begin Message ---
Source: linux
Source-Version: 3.18.3-1~exp1

We believe that the bug you reported is fixed in the latest version of
linux, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 770...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Ben Hutchings  (supplier of updated linux package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 18 Jan 2015 20:48:06 +
Source: linux
Binary: linux-source-3.18 linux-doc-3.18 linux-manual-3.18 
linux-support-3.18.0-trunk linux-libc-dev linux-headers-3.18.0-trunk-all 
linux-headers-3.18.0-trunk-all-alpha linux-headers-3.18.0-trunk-common 
linux-image-3.18.0-trunk-alpha-generic linux-headers-3.18.0-trunk-alpha-generic 
linux-image-3.18.0-trunk-alpha-smp linux-headers-3.18.0-trunk-alpha-smp 
linux-image-3.18.0-trunk-alpha-legacy linux-headers-3.18.0-trunk-alpha-legacy 
linux-headers-3.18.0-trunk-all-amd64 kernel-image-3.18.0-trunk-amd64-di 
nic-modules-3.18.0-trunk-amd64-di nic-wireless-modules-3.18.0-trunk-amd64-di 
nic-shared-modules-3.18.0-trunk-amd64-di serial-modules-3.18.0-trunk-amd64-di 
usb-serial-modules-3.18.0-trunk-amd64-di ppp-modules-3.18.0-trunk-amd64-di 
pata-modules-3.18.0-trunk-amd64-di cdrom-core-modules-3.18.0-trunk-amd64-di 
firewire-core-modules-3.18.0-trunk-amd64-di 
scsi-core-modules-3.18.0-trunk-amd64-di scsi-modules-3.18.0-trunk-amd64-di 
scsi-common-modules-3.18.0-trunk-amd64-di
 scsi-extra-modules-3.18.0-trunk-amd64-di loop-modules-3.18.0-trunk-amd64-di 
btrfs-modules-3.18.0-trunk-amd64-di ext4-modules-3.18.0-trunk-amd64-di 
isofs-modules-3.18.0-trunk-amd64-di jfs-modules-3.18.0-trunk-amd64-di 
ntfs-modules-3.18.0-trunk-amd64-di xfs-modules-3.18.0-trunk-amd64-di 
fat-modules-3.18.0-trunk-amd64-di md-modules-3.18.0-trunk-amd64-di 
multipath-modules-3.18.0-trunk-amd64-di usb-modules-3.18.0-trunk-amd64-di 
usb-storage-modules-3.18.0-trunk-amd64-di 
pcmcia-storage-modules-3.18.0-trunk-amd64-di fb-modules-3.18.0-trunk-amd64-di 
input-modules-3.18.0-trunk-amd64-di event-modules-3.18.0-trunk-amd64-di 
mouse-modules-3.18.0-trunk-amd64-di nic-pcmcia-modules-3.18.0-trunk-amd64-di 
pcmcia-modules-3.18.0

Processed: Re: Bug#773643: initramfs-tools: mkfs.* not added to initrd image (Warning: couldn't identify filesystem type for fsck hook, ignoring.)

2015-01-18 Thread Debian Bug Tracking System 
Processing control commands:

> forcemerge 766448 -1
Bug #766448 [initramfs-tools] root fstype "auto" in /etc/fstab guaranteed 
unbootable
Bug #773643 [initramfs-tools] initramfs-tools: mkfs.* not added to initrd image 
(Warning: couldn't identify filesystem type for fsck hook, ignoring.)
Severity set to 'grave' from 'important'
Added tag(s) patch.
Bug #766448 [initramfs-tools] root fstype "auto" in /etc/fstab guaranteed 
unbootable
Added tag(s) moreinfo.
Merged 766448 773643
> tag -1 - moreinfo
Bug #773643 [initramfs-tools] initramfs-tools: mkfs.* not added to initrd image 
(Warning: couldn't identify filesystem type for fsck hook, ignoring.)
Bug #766448 [initramfs-tools] root fstype "auto" in /etc/fstab guaranteed 
unbootable
Removed tag(s) moreinfo.
Removed tag(s) moreinfo.

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


--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
https://lists.debian.org/handler.s.b773643.142162877920852.transcr...@bugs.debian.org

Bug#773643: initramfs-tools: mkfs.* not added to initrd image (Warning: couldn't identify filesystem type for fsck hook, ignoring.)

2015-01-18 Thread Ben Hutchings 
Control: forcemerge 766448 -1
Control: tag -1 - moreinfo

On Sun, 2015-01-18 at 23:47 +0100, Paul Menzel wrote:
> Am Sonntag, den 18.01.2015, 15:12 + schrieb Ben Hutchings:
[...]
> > I think I know why this is, but please can you send the fstab line for
> > the root filesystem?
> 
> Sure.
> 
> UUID=2b45d72e-7bd8-490f-bd9e-7e5990859148   /  auto
> discard,noatime,commit=600,defaults,errors=remount-ro 0   1
> 
> In `/etc/fstab` tabs instead of spaces are used.

OK, this is the same as in #766448 and I have a fix for it.

> PS: In the future, should I remove the tag `moreinfo` when I answer your
> question or better leave it and let you do it, if you see fit?

You can do that if you like.

Ben.

-- 
Ben Hutchings
Larkinson's Law: All laws are basically false.


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

Bug#773643: initramfs-tools: mkfs.* not added to initrd image (Warning: couldn't identify filesystem type for fsck hook, ignoring.)

2015-01-18 Thread Paul Menzel 
Am Sonntag, den 18.01.2015, 15:12 + schrieb Ben Hutchings:
> Control: tag -1 moreinfo
> 
> On Sun, 21 Dec 2014 12:46:18 +0100 Paul Menzel  
> wrote:
> > Package: initramfs-tools
> > Version: 0.118
> > Severity: important

> > since some time, the filesystem type of the LUKS encrypted root
> > partition (/) is not detected.
> > 
> > $ sudo update-initramfs -u
> > update-initramfs: Generating /boot/initrd.img-3.16.0-4-amd64
> > W: Possible missing firmware /lib/firmware/rtl_nic/rtl8168g-3.fw 
> > for module r8169
> > W: Possible missing firmware /lib/firmware/rtl_nic/rtl8168g-2.fw 
> > for module r8169
> > W: Possible missing firmware /lib/firmware/rtl_nic/rtl8106e-2.fw 
> > for module r8169
> > W: Possible missing firmware /lib/firmware/rtl_nic/rtl8106e-1.fw 
> > for module r8169
> > W: Possible missing firmware /lib/firmware/rtl_nic/rtl8411-2.fw for 
> > module r8169
> > W: Possible missing firmware /lib/firmware/rtl_nic/rtl8411-1.fw for 
> > module r8169
> > W: Possible missing firmware /lib/firmware/rtl_nic/rtl8402-1.fw for 
> > module r8169
> > W: Possible missing firmware /lib/firmware/rtl_nic/rtl8168f-2.fw 
> > for module r8169
> > W: Possible missing firmware /lib/firmware/rtl_nic/rtl8168f-1.fw 
> > for module r8169
> > W: Possible missing firmware /lib/firmware/rtl_nic/rtl8105e-1.fw 
> > for module r8169
> > W: Possible missing firmware /lib/firmware/rtl_nic/rtl8168e-3.fw 
> > for module r8169
> > W: Possible missing firmware /lib/firmware/rtl_nic/rtl8168e-2.fw 
> > for module r8169
> > W: Possible missing firmware /lib/firmware/rtl_nic/rtl8168e-1.fw 
> > for module r8169
> > W: Possible missing firmware /lib/firmware/rtl_nic/rtl8168d-2.fw 
> > for module r8169
> > W: Possible missing firmware /lib/firmware/rtl_nic/rtl8168d-1.fw 
> > for module r8169
> > Warning: couldn't identify filesystem type for fsck hook, ignoring.
> > setupcon is missing. Please install the 'console-setup' package.
> [...]
> 
> I think I know why this is, but please can you send the fstab line for
> the root filesystem?

Sure.

UUID=2b45d72e-7bd8-490f-bd9e-7e5990859148   /  auto
discard,noatime,commit=600,defaults,errors=remount-ro 0   1

In `/etc/fstab` tabs instead of spaces are used.


Thanks,

Paul


PS: In the future, should I remove the tag `moreinfo` when I answer your
question or better leave it and let you do it, if you see fit?


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

Bug#775319: Re[10]: Bug#775319: pulseaudio: unable to use headphones or other line out ports for audio. only speakers

2015-01-18 Thread lachlan-00 
Thanks for your help.
That suggests the kernel or the card itself. If alsa cannot play, then
pulseaudio is not the culprit. I am reassigning to the kernel, lets
see if the kernel maintainers can think of something else. I suggest
attaching the alsa-info.sh output[1], as it is usually helpful.

[1] https://wiki.ubuntu.com/Audio/AlsaInfo 
(https://wiki.ubuntu.com/Audio/AlsaInfo)

Script output:
http://www.alsa-project.org/db/?f=95682589ed95550bedd44d1bd9aca7e95ae03930 
(http://www.alsa-project.org/db/?f=95682589ed95550bedd44d1bd9aca7e95ae03930)

Processed: Re: Re[8]: Bug#775319: pulseaudio: unable to use headphones or other line out ports for audio. only speakers

2015-01-18 Thread Debian Bug Tracking System 
Processing control commands:

> reassign -1 linux-image-3.16.0-4-amd64
Bug #775319 [pulseaudio] pulseaudio: unable to use headphones or other line out 
ports for audio. only speakers
Bug reassigned from package 'pulseaudio' to 'linux-image-3.16.0-4-amd64'.
No longer marked as found in versions pulseaudio/5.0-13.
Ignoring request to alter fixed versions of bug #775319 to the same values 
previously set

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


--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
https://lists.debian.org/handler.s.b775319.14216205846867.transcr...@bugs.debian.org

Re: Incomplete log for linux 3.16.7-ckt4-1 on mips

2015-01-18 Thread Ben Hutchings 
On Sun, 2015-01-18 at 20:59 +0100, Andreas Barth wrote:
> * Ben Hutchings (b...@decadent.org.uk) [150118 14:23]:
> > The attempted build of linux version 3.16.7-ckt4-1 on mips-aql-01
> > failed, but the log shown at
> > 
> >  is incomplete so I have no idea why.  Is there any more information you 
> > can retrieve that could explain the failure?
> 
> Unfortunatly the log on the filesystem is incomplete as well. I'll
> schedule a rebuild.

Thanks.

Ben.

-- 
Ben Hutchings
The generation of random numbers is too important to be left to chance.
- Robert Coveyou


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

Re: Incomplete log for linux 3.16.7-ckt4-1 on mips

2015-01-18 Thread Andreas Barth 
* Ben Hutchings (b...@decadent.org.uk) [150118 14:23]:
> The attempted build of linux version 3.16.7-ckt4-1 on mips-aql-01
> failed, but the log shown at
> 
>  is incomplete so I have no idea why.  Is there any more information you can 
> retrieve that could explain the failure?

Unfortunatly the log on the filesystem is incomplete as well. I'll
schedule a rebuild.


Andi


-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/20150118195920.go5...@mails.so.argh.org

Bug#766920: produces unbootable initramfs with lilo hexadecimal syntax (root=803)

2015-01-18 Thread Ben Hutchings 
On Sun, 2015-01-18 at 18:09 +0100, Richard Lucassen wrote:
> On Sat, 17 Jan 2015 16:06:15 +
> Ben Hutchings  wrote:
> 
> > Control: tag -1 moreinfo
> > 
> > I'm unable to reproduce the numeric root in /etc/mtab.  I tried using
> > lilo with a non-UUID root, using the Debian packaged kernel and then
> > with a custom kernel with no initramfs.  In both cases I see / mounted
> > from /dev/root and that device node does exist.  I also tested using
> > both systemd and sysvinit.  In all cases /etc/mtab is a symlink
> > to /proc/mounts (as both init systems create it).
> 
> I think it is a misunderstanding. I created a symlink in the root
> directory (mind, in the meantime I changed to sda5 instead of sda3):
> 
> # ln -s /dev/sda3 /805
> # ls -al /805
> lrwxrwxrwx 1 root root 9 Jan 17 21:41 /803 -> /dev/sda5

I understood that, but not where we got the name 803 (or 805) from.

[...]
> When I choose "Linux-nosd" using "root=UUID", the system boots and a
> mount shows this:
> 
> /dev/sda5 on / type ext4 (rw,noatime,nodiratime,discard,data=ordered)
> 
> mtab:
> 
> rootfs / rootfs rw 0 0
> /dev/disk/by-uuid/d94d08f7-4b3d-47be-acaf-d425e71efece / ext4
> rw,noatime,nodiratime,discard,data=ordered 0 0
> 
> When a new initrd.img is generated by apt, everything is ok.
> 
> When I choose "test-805" using "root=/dev/sda5", the system boots, but
> "mount" shows:
> 
> 805 on / type ext4 (rw,noatime,nodiratime,discard,data=ordered)
> 
> mtab:
> 
> rootfs / rootfs rw 0 0
> /dev/root / ext4 rw,noatime,nodiratime,discard,data=ordered 0 0
[...]

Oh I see, it's not in /etc/mtab but only in the mount output.  It seems
like that's a bug in mount.  Maybe we should only read /proc/mounts and
not run mount at all.

Ben.

-- 
Ben Hutchings
The generation of random numbers is too important to be left to chance.
- Robert Coveyou


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

[PATCH initramfs-tools] dep_add_modules: Add modules needed for /usr device

2015-01-18 Thread Ben Hutchings 
In case the root and /usr filesystems are of different types, or are
on different types of device, we must add the modules needed for both.

Signed-off-by: Ben Hutchings 
---
I don't think we have an open bug report for this, but it's obvious we
need to deal with it.  It looks like a big patch but mostly it's
renaming to generalise from root.

Tested using a VM with MODULES=dep, root on virtio disk and /usr on an
emulated PIIX PATA disk.

Ben.

 hook-functions | 152 +++--
 1 file changed, 83 insertions(+), 69 deletions(-)

diff --git a/hook-functions b/hook-functions
index e71f0f8..4edbfde 100644
--- a/hook-functions
+++ b/hook-functions
@@ -256,53 +256,61 @@ add_loaded_modules()
fi
 }
 
-# find and only copy root relevant modules
-dep_add_modules()
+# find and only copy modules relevant to a mountpoint
+dep_add_modules_mount()
 {
-   local block minor root FSTYPE root_dev_path
+   local dir block minor dev_node FSTYPE dev_sys_path
local modules=
 
+   dir="$1"
+
# require mounted sysfs
if [ ! -d /sys/devices/ ]; then
echo "mkinitramfs: MODULES dep requires mounted sysfs on /sys" 
>&2
exit 1
fi
 
-   # findout root block device + fstype
+   # find out block device + fstype
eval "$( mount | while read -r dev foo mp foo fs opts rest ; do \
-   [ "$mp" = "/" ] && [ "$fs" != "rootfs" ] \
-   && printf "root='%s'\nFSTYPE='%s'" "$dev" "$fs" \
+   [ "$mp" = "$dir" ] && [ "$fs" != "rootfs" ] \
+   && printf "dev_node='%s'\nFSTYPE='%s'" "$dev" "$fs" \
&& break; done)"
 
# On failure fallback to /proc/mounts if readable
-   if [ -z "$root" ] && [ -r /proc/mounts ]; then
+   if [ -z "$dev_node" ] && [ -r /proc/mounts ]; then
eval "$(while read dev mp fs opts rest ; do \
-   [ "$mp" = "/" ] && [ "$fs" != "rootfs" ] \
-   && printf "root=$dev\nFSTYPE=$fs"\
+   [ "$mp" = "$dir" ] && [ "$fs" != "rootfs" ] \
+   && printf "dev_node=$dev\nFSTYPE=$fs"\
&& break; done < /proc/mounts)"
fi
 
-   # handle ubifs and return since ubifs root is a char device but
-   # most of the commands below only work with block devices.
+   # Only the root mountpoint has to exist; do nothing if any other
+   # directory is not a mountpoint.
+   if [ "$dir" != / ] && [ -z "$dev_node" ]; then
+   return
+   fi
+
+   # handle ubifs and return since ubifs is mounted on char devices
+   # but most of the commands below only work with block devices.
if [ "${FSTYPE}" = "ubifs" ]; then
manual_add_modules "${FSTYPE}"
return
fi
 
-   if [ "${root}" = "/dev/root" ] ; then
-   if [ -b "${root}" ]; then
+   if [ "$dir" = / ] && [ "${dev_node}" = "/dev/root" ] ; then
+   if [ -b "${dev_node}" ]; then
# Match it to the canonical device name by UUID
-   root="/dev/disk/by-uuid/"$(blkid -o value -s UUID 
${root}) 2>/dev/null
+   dev_node="/dev/disk/by-uuid/"$(blkid -o value -s UUID 
${dev_node}) 2>/dev/null
else
# Does not exist in our namespace, so look at the
# kernel command line
-   root=
+   dev_node=
for arg in $(cat /proc/cmdline); do
case "$arg" in
root=*)
-   root="${arg#root=}"
-   if [ "${root#/dev/}" = "$root" ]; then
-   root="/dev/$root"
+   dev_node="${arg#root=}"
+   if [ "${dev_node#/dev/}" = "$dev_node" 
]; then
+   dev_node="/dev/$dev_node"
fi
;;
--)
@@ -315,9 +323,10 @@ dep_add_modules()
fi
fi
 
-   # recheck root device
-   if [ -z "$root" ] || ! root="$(readlink -f ${root})" || ! [ -b "$root" 
]; then
-   echo "mkinitramfs: failed to determine root device" >&2
+   # recheck device
+   if [ -z "$dev_node" ] || ! dev_node="$(readlink -f ${dev_node})" \
+   || ! [ -b "$dev_node" ]; then
+   echo "mkinitramfs: failed to determine device for $dir" >&2
echo "mkinitramfs: workaround is MODULES=most, check:" >&2
echo "grep -r MODULES /etc/initramfs-tools/" >&2
echo "" >&2
@@ -327,26 +336,26 @@ dep_add_modules()
fi
 
# do not trust mount, check su

Bug#766920: produces unbootable initramfs with lilo hexadecimal syntax (root=803)

2015-01-18 Thread Richard Lucassen 
On Sat, 17 Jan 2015 16:06:15 +
Ben Hutchings  wrote:

[erratum]

# ln -s /dev/sda5 /805
# ls -al /805
lrwxrwxrwx 1 root root 9 Jan 17 21:41 /805 -> /dev/sda5

-- 
___
It is better to remain silent and be thought a fool, than to speak
aloud and remove all doubt.

+--+
| Richard Lucassen, Utrecht|
+--+


-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/20150118182016.219845f7602e45ac72bcf...@xaq.nl

Bug#766920: produces unbootable initramfs with lilo hexadecimal syntax (root=803)

2015-01-18 Thread Richard Lucassen 
On Sat, 17 Jan 2015 16:06:15 +
Ben Hutchings  wrote:

> Control: tag -1 moreinfo
> 
> I'm unable to reproduce the numeric root in /etc/mtab.  I tried using
> lilo with a non-UUID root, using the Debian packaged kernel and then
> with a custom kernel with no initramfs.  In both cases I see / mounted
> from /dev/root and that device node does exist.  I also tested using
> both systemd and sysvinit.  In all cases /etc/mtab is a symlink
> to /proc/mounts (as both init systems create it).

I think it is a misunderstanding. I created a symlink in the root
directory (mind, in the meantime I changed to sda5 instead of sda3):

# ln -s /dev/sda3 /805
# ls -al /805
lrwxrwxrwx 1 root root 9 Jan 17 21:41 /803 -> /dev/sda5

> - Did you boot from an initramfs before running update-initramfs?

Yes, it's a Debian testing distro, using the debian kernels

> - Which init system are you using, and which version of it?

I use sysv-init

> - Is /etc/mtab a regular file or symlink?

It is a symlink to /proc/mounts as expected. But: I use lilo, not grub.
And this is what I can reproduce, the issue is in lilo.conf:

boot=/dev/sda
map=/boot/map
delay=20
compact
prompt
timeout=20
default=Linux-nosd

image=/vmlinuz
label=Linux-nosd
root="UUID=d94d08f7-4b3d-47be-acaf-d425e71efece"
read-only
initrd=/initrd.img

image=/vmlinuz
label=test-805
root=/dev/sda5
read-only
initrd=/initrd.img

When I choose "Linux-nosd" using "root=UUID", the system boots and a
mount shows this:

/dev/sda5 on / type ext4 (rw,noatime,nodiratime,discard,data=ordered)

mtab:

rootfs / rootfs rw 0 0
/dev/disk/by-uuid/d94d08f7-4b3d-47be-acaf-d425e71efece / ext4
rw,noatime,nodiratime,discard,data=ordered 0 0

When a new initrd.img is generated by apt, everything is ok.

When I choose "test-805" using "root=/dev/sda5", the system boots, but
"mount" shows:

805 on / type ext4 (rw,noatime,nodiratime,discard,data=ordered)

mtab:

rootfs / rootfs rw 0 0
/dev/root / ext4 rw,noatime,nodiratime,discard,data=ordered 0 0

The problem finally occurs when I boot "test-805" and apt produces a new
initrd.img. With the generated initrd.img the system refuses to boot. A
workaround is:

# ln -s /dev/sda5 /805

Please note that I'd rather do not test an update-initramfs as I have
to take the HDD out of the laptop and "lilo" it manually on other
sytem ;-)

HTH, if I can so some further tests, I's be at your service :)

R.

-- 
___
It is better to remain silent and be thought a fool, than to speak
aloud and remove all doubt.

+--+
| Richard Lucassen, Utrecht|
+--+


-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/20150118180908.3b7d78bc388d31e718144...@xaq.nl

Processed: reopening 752381, reassign 752381 to src:grub2

2015-01-18 Thread Debian Bug Tracking System 
Processing commands for cont...@bugs.debian.org:

> reopen 752381
Bug #752381 {Done: Ben Hutchings } [initramfs-tools] 
initramfs-tools: does not activate logical volume before trying to mount root 
filesystem on LVM
Bug reopened
Ignoring request to alter fixed versions of bug #752381 to the same values 
previously set
> reassign 752381 src:grub2 2.02~beta2-19
Bug #752381 [initramfs-tools] initramfs-tools: does not activate logical volume 
before trying to mount root filesystem on LVM
Bug reassigned from package 'initramfs-tools' to 'src:grub2'.
No longer marked as found in versions initramfs-tools/0.113, 
initramfs-tools/0.98.8, initramfs-tools/0.112, initramfs-tools/0.99, 
initramfs-tools/0.106, initramfs-tools/0.109.1, initramfs-tools/0.98.7, and 
initramfs-tools/0.115~bpo70+1.
Ignoring request to alter fixed versions of bug #752381 to the same values 
previously set
Bug #752381 [src:grub2] initramfs-tools: does not activate logical volume 
before trying to mount root filesystem on LVM
Marked as found in versions grub2/2.02~beta2-19.
> thanks
Stopping processing here.

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


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

Bug#774896: Exynos4 CONFIG_HZ

2015-01-18 Thread Sten Spans 


With the  improvements in upstream support for exynos4 devices
I've been looking into adding support odroid devices to Debian's
armmp kernel. The kernel config changes needed are quite minimal
as can be seen here:

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=774896

Mostly enabling support and various modules.

However as Ian Campbell notes, enabling ARCH_EXYNOS4 triggers
the following from arch/arm/Kconfig:
config HZ_FIXED
int
default 200 if ARCH_EBSA110 || ARCH_S3C24XX || \
ARCH_S5PV210 || ARCH_EXYNOS4
default AT91_TIMER_HZ if ARCH_AT91
default SHMOBILE_TIMER_HZ if ARCH_SHMOBILE_LEGACY
default 0

This forces CONFIG_HZ=200 for the entire armmp kernel, which is
undesirable. The reason for this setting isn't very clear to either
me or Ian. I personally have verified that HZ=250 (the default for debian
armmp kernels) boots fine.

Is there a particular reason for this setting?
Would a patch removing this requirement for ARCH_EXYNOS4 be accepted?

--
Sten Spans

"There is a crack in everything, that's how the light gets in."
Leonard Cohen - Anthem


--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
https://lists.debian.org/alpine.deb.0.9.1501181744400.30...@zem.blinkenlights.nl

Bug#752381: initramfs-tools: does not activate logical volume - two obversations

2015-01-18 Thread Martin Steigerwald 
Am Sonntag, 18. Januar 2015, 15:25:52 schrieb Ben Hutchings:
> Control: notfound -1 0.115~bpo70+1
> 
> On Mon, 23 Jun 2014 10:34:02 +0200 Martin Steigerwald  
wrote:
> > Hi!
> > 
> > I bzr diff on /boot/grub/grub.cfg revealed – but already from last week
> > as I upgraded to the newer backport initramfs-tools, where booting still
> > worked> 
> > okay:
> >  menuentry 'Debian GNU/Linux, mit Linux 3.2.0-4-686-pae' --class debian --
> > 
> > class gnu-linux --class gnu --class os {
> > 
> > load_video
> > insmod gzio
> > 
> > @@ -67,7 +90,7 @@
> > 
> > set root='(hd0,msdos1)'
> > search --no-floppy --fs-uuid --set=root [UUID]
> > echo'Linux 3.2.0-4-686-pae wird geladen …'
> > 
> > -   linux   /vmlinuz-3.2.0-4-686-pae
> > root=/dev/mapper/mondschein-debian ro +   linux  
> > /vmlinuz-3.2.0-4-686-pae root=UUID=[UUID ro
> > 
> > echo'Initiale Ramdisk wird geladen …'
> > initrd  /initrd.img-3.2.0-4-686-pae
> >  
> >  }
> 
> [...]
> 
> The 'UUID=...' syntax is not supported for root on an LV.  You *must*
> use the /dev/mapper device name so that the lvm2 script can work out
> which VG to activate.  (It is not safe in general to activate all
> visible VGs.)

Its not me using a UUID, its update-grub. In /boot/grub/grub.cfg I have:

linux   /vmlinuz-3.16-0.bpo.3-686-pae root=UUID=[some UUID]

yet in /etc/fstab I have:

/dev/mondschein/debian  /  ext4defaults 0 1

In /etc/default/grub I do not set the root= parameter manually. In fact I 
have:

GRUB_CMDLINE_LINUX_DEFAULT=""
GRUB_CMDLINE_LINUX=""


So I do not see where I tell grub to use a UUID. For reference here is the 
complete grub configuration:

# If you change this file, run 'update-grub' afterwards to update
# /boot/grub/grub.cfg.
# For full documentation of the options in this file, see:
#   info -f grub -n 'Simple configuration'

GRUB_DEFAULT=0
GRUB_TIMEOUT=5
GRUB_DISTRIBUTOR=`lsb_release -i -s 2> /dev/null || echo Debian`
GRUB_CMDLINE_LINUX_DEFAULT=""
GRUB_CMDLINE_LINUX=""

# Uncomment to enable BadRAM filtering, modify to suit your needs
# This works with Linux (no patch required) and with any kernel that obtains
# the memory map information from GRUB (GNU Mach, kernel of FreeBSD ...)
#GRUB_BADRAM="0x01234567,0xfefefefe,0x89abcdef,0xefefefef"

# Uncomment to disable graphical terminal (grub-pc only)
#GRUB_TERMINAL=console

# The resolution used on graphical terminal
# note that you can use only modes which your graphic card supports via VBE
# you can see them in real GRUB with the command `vbeinfo'
#GRUB_GFXMODE=640x480

# Uncomment if you don't want GRUB to pass "root=UUID=xxx" parameter to Linux
#GRUB_DISABLE_LINUX_UUID=true

# Uncomment to disable generation of recovery mode menu entries
#GRUB_DISABLE_RECOVERY="true"

# Uncomment to get a beep at grub start
#GRUB_INIT_TUNE="480 440 1"



On Sid tough update-grub creates this:

root=/dev/mapper/sata-debian

which does seem to fit what you say initramfs-tools requires (except that by 
default it adds both devices to BTRFS RAID 1, see below about bug 747653).


Please re-open and if you really think its not initramfs-tools bug, reassign 
to grub-pc for having it use /dev/VG/LV syntax instead. Or advise on another 
solution. I can also keep the work-around of course, but its important to make 
sure that in Jessie this setup will work without any additional work-around. 
And if UUIDs are not supported for LVM, I think this deserves a promiment 
mention somewhere as well. Cause not booting due to not activing a logical 
volume is not so nice to the user.


This may be solved there with a patch similar to what upstream provided:

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=747653#25

I did not yet come around to build grub-pc myself into /usr/local and test 
this patch.

Ciao,
-- 
Martin 'Helios' Steigerwald - http://www.Lichtvoll.de
GPG: 03B0 0D6C 0040 0710 4AFA  B82F 991B EAAC A599 84C7

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

Bug#742962: fails to mount root when root is on lvm.

2015-01-18 Thread Ben Hutchings 
On Sat, 29 Mar 2014 14:35:08 +0100 Kenneth Johansson  wrote:
> Package: initramfs-tool
> Version: 0.115
> 
> 
> So I updated to latest kernel package in SID 3.13-1 and system did not 
> reboot.
> problem is that the ramdisk can't find root.
> 
> looking into this I can see that the raid device is found but the lvm on 
> top of the raid is never started.
> if*//*I run "lvm vgchange -ay" then the disks shows up in /dev/mapper/

What is the 'root' kernel parameter set to?

[...]
> Also got a bit confused as I saw systemd running from the ramdisk and I 
> have not yet installed systemd.
[...]

udev is running in the initramfs, as it has always done.  udev is now
part of the systemd project, but systemd is not used as an init system.

Ben.

-- 
Ben Hutchings
The generation of random numbers is too important to be left to chance.
- Robert Coveyou


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

Bug#752381: marked as done (initramfs-tools: does not activate logical volume before trying to mount root filesystem on LVM)

2015-01-18 Thread Debian Bug Tracking System 
Your message dated Sun, 18 Jan 2015 15:25:52 +
with message-id <1421594752.31046.154.ca...@decadent.org.uk>
and subject line Re: initramfs-tools: does not activate logical volume - two 
obversations
has caused the Debian Bug report #752381,
regarding initramfs-tools: does not activate logical volume before trying to 
mount root filesystem on LVM
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.)


-- 
752381: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=752381
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: initramfs-tools
Version: 0.115~bpo70+1
Severity: important

What did I do:

Today I installed backports version of open-vm-dkms and upgraded to most
recent 3.14 backport kernel from a previous version of it I installed due
to using BTRFS with skinny meta data on one partition.


Current results:

After this the machine failed to boot. It didn´t find the root filesystem
by its UUID. I typed "vgchange -ay" in initramfs and then Ctrl-D and then
it booted. This used to work without manual interaction before.

To make it boot consistently I added as a work-around:

mondschein:~> cat /etc/initramfs-tools/scripts/local-top/lvm-manual 
#!/bin/sh

PREREQ="lvm"
prereqs()
{
echo $PREREQ
}

case $1 in
prereqs)
prereqs
exit 0;
esac

. /scripts/functions

log_begin_msg "Activitating logical volumes (as it does not seem to be done 
automatically at the moment)."

vgchange -ay

log_end_msg


which I had handy as I use a similar workaround for enabling BTRFS RAID 1
boot on my laptop, which does not work as default.

This worked after actually chmod'ing +x it :)


Expected results:

Machine boots without manual adaptions to InitRD.


Additional information:

The machine still boots from an Ext4 filesystem. The BTRFS filesystem is
mounted later on by fstab.

There is a lvm and a BTRFS script in InitRD already, but the lvm script did
not seem to work properly:

mondschein:~> lsinitramfs /boot/initrd.img-3.14-0.bpo.1-686-pae | grep script
scripts
scripts/functions
scripts/nfs
scripts/init-bottom
scripts/init-bottom/udev
scripts/init-bottom/ORDER
scripts/local-premount
scripts/local-premount/btrfs
scripts/local-premount/resume
scripts/local-premount/ORDER
scripts/local
scripts/local-top
scripts/local-top/lvm-manual
scripts/local-top/lvm2
scripts/local-top/ORDER
scripts/init-top
scripts/init-top/blacklist
scripts/init-top/keymap
scripts/init-top/udev
scripts/init-top/ORDER
scripts/init-top/all_generic_ide


I thought it was an update to initramfs-tools causing this, but these have
been upgraded last week already:

Start-Date: 2014-06-12  11:46:49
Commandline: apt-get install -t wheezy-backports 
linux-image-3.14-0.bpo.1-686-pae linux-headers-3.14-0.bpo.1-686-pae btrfs-tools
Install: linux-headers-3.14-0.bpo.1-686-pae:i386 (3.14.5-1~bpo70+1), 
linux-image-3.14-0.bpo.1-686-pae:i386 (3.14.5-1~bpo70+1), 
linux-compiler-gcc-4.6-x
86:i386 (3.14.5-1~bpo70+1, automatic), btrfs-tools:i386 (3.14.1-1~bpo70+1), 
liblzo2-2:i386 (2.06-1, automatic), linux-kbuild-3.14:i386 (3.14-1~bpo70+1,
 automatic), linux-headers-3.14-0.bpo.1-common:i386 (3.14.5-1~bpo70+1, 
automatic)
Upgrade: initramfs-tools:i386 (0.109.1, 0.115~bpo70+1)
End-Date: 2014-06-12  11:48:06


And there rebooting the machine worked out of the box.

So maybe something in open-vm-tools or open-vm-dkms from wheezy-backports
interacts with InitRD script stuff in a way that breaks boot. But OTOH
I see no open-vm related scripts in above lsinitramfs output.

Thanks,
Martin

-- Package-specific info:
-- initramfs sizes
-rw-r--r-- 1 root root 13M Jun 23 09:58 /boot/initrd.img-3.14-0.bpo.1-686-pae
-rw-r--r-- 1 root root 11M Jun 23 09:58 /boot/initrd.img-3.2.0-4-686-pae
-- /proc/cmdline
BOOT_IMAGE=/vmlinuz-3.14-0.bpo.1-686-pae 
root=UUID=a8e69cdf-f016-4f07-8d2d-d975881d2095 ro

-- resume
RESUME=/dev/sda2
-- /proc/filesystems
btrfs
ext3
ext2
ext4

-- lsmod
Module  Size  Used by
coretemp   12734  0 
crc32_pclmul   12809  0 
crc32c_intel   12624  0 
vmw_balloon12502  0 
irda   90367  0 
parport_pc 25991  0 
crc_ccitt  12331  1 irda
parport35207  1 parport_pc
aesni_intel17934  0 
vmwgfx142296  0 
ttm59829  1 vmwgfx
aes_i586   16647  1 aesni_intel
xts12583  1 aesni_intel
lrw12686  1 aesni_intel
gf128mul   12834  2 lrw,xts
ablk_helper12508  1 aesni_intel
cryptd

Processed: unmerging 752381

2015-01-18 Thread Debian Bug Tracking System 
Processing commands for cont...@bugs.debian.org:

> unmerge 752381
Bug #752381 [initramfs-tools] initramfs-tools: does not activate logical volume 
before trying to mount root filesystem on LVM
Bug #616689 [initramfs-tools] Root-on-LVM setup fails often due to timing issues
Bug #633024 [initramfs-tools] initramfs-tools: Race condition when root 
filesystem is on a LV and mdadm array
Bug #678696 [initramfs-tools] Event based block device handling (fixes USB and 
nested devices problem)
Bug #707286 [initramfs-tools] linux-image-3.8-1-amd64: makes system unbootable
Bug #712984 [initramfs-tools] linux-image-3.9-1-amd64: Unable to find LVM 
volume system/root
Bug #712999 [initramfs-tools] linux-image-3.9-1-amd64: Unable to find LVM volume
Bug #718533 [initramfs-tools] linux-image-3.10-1-amd64 fails to boot with RAID5
Bug #720716 [initramfs-tools] initramfs-tools: workaround in 707286 solves 
serious problem
Bug #742962 [initramfs-tools] fails to mount root when root is on lvm.
Disconnected #752381 from all other report(s).
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
616689: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=616689
633024: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=633024
678696: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=678696
707286: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=707286
712984: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=712984
712999: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=712999
718533: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=718533
720716: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=720716
742962: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=742962
752381: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=752381
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems


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

Bug#773643: initramfs-tools: mkfs.* not added to initrd image (Warning: couldn't identify filesystem type for fsck hook, ignoring.)

2015-01-18 Thread Ben Hutchings 
Control: tag -1 moreinfo

On Sun, 21 Dec 2014 12:46:18 +0100 Paul Menzel  wrote:
> Package: initramfs-tools
> Version: 0.118
> Severity: important
> 
> Dear Debian folks,
> 
> 
> since some time, the filesystem type of the LUKS encrypted root
> partition (/) is not detected.
> 
> $ sudo update-initramfs -u
> update-initramfs: Generating /boot/initrd.img-3.16.0-4-amd64
> W: Possible missing firmware /lib/firmware/rtl_nic/rtl8168g-3.fw for 
> module r8169
> W: Possible missing firmware /lib/firmware/rtl_nic/rtl8168g-2.fw for 
> module r8169
> W: Possible missing firmware /lib/firmware/rtl_nic/rtl8106e-2.fw for 
> module r8169
> W: Possible missing firmware /lib/firmware/rtl_nic/rtl8106e-1.fw for 
> module r8169
> W: Possible missing firmware /lib/firmware/rtl_nic/rtl8411-2.fw for 
> module r8169
> W: Possible missing firmware /lib/firmware/rtl_nic/rtl8411-1.fw for 
> module r8169
> W: Possible missing firmware /lib/firmware/rtl_nic/rtl8402-1.fw for 
> module r8169
> W: Possible missing firmware /lib/firmware/rtl_nic/rtl8168f-2.fw for 
> module r8169
> W: Possible missing firmware /lib/firmware/rtl_nic/rtl8168f-1.fw for 
> module r8169
> W: Possible missing firmware /lib/firmware/rtl_nic/rtl8105e-1.fw for 
> module r8169
> W: Possible missing firmware /lib/firmware/rtl_nic/rtl8168e-3.fw for 
> module r8169
> W: Possible missing firmware /lib/firmware/rtl_nic/rtl8168e-2.fw for 
> module r8169
> W: Possible missing firmware /lib/firmware/rtl_nic/rtl8168e-1.fw for 
> module r8169
> W: Possible missing firmware /lib/firmware/rtl_nic/rtl8168d-2.fw for 
> module r8169
> W: Possible missing firmware /lib/firmware/rtl_nic/rtl8168d-1.fw for 
> module r8169
> Warning: couldn't identify filesystem type for fsck hook, ignoring.
> setupcon is missing. Please install the 'console-setup' package.
[...]

I think I know why this is, but please can you send the fstab line for
the root filesystem?

Ben.

-- 
Ben Hutchings
The generation of random numbers is too important to be left to chance.
- Robert Coveyou


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

Processed: Re: initramfs-tools: mkfs.* not added to initrd image (Warning: couldn't identify filesystem type for fsck hook, ignoring.)

2015-01-18 Thread Debian Bug Tracking System 
Processing control commands:

> tag -1 moreinfo
Bug #773643 [initramfs-tools] initramfs-tools: mkfs.* not added to initrd image 
(Warning: couldn't identify filesystem type for fsck hook, ignoring.)
Added tag(s) moreinfo.

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


--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
https://lists.debian.org/handler.s.b773643.142159393127124.transcr...@bugs.debian.org

Processed: Re: initramfs-tools: mkfs.* not added to initrd image (Warning: couldn't identify filesystem type for fsck hook, ignoring.)

2015-01-18 Thread Debian Bug Tracking System 
Processing control commands:

> tag -1 moreinfo
Bug #773643 [initramfs-tools] initramfs-tools: mkfs.* not added to initrd image 
(Warning: couldn't identify filesystem type for fsck hook, ignoring.)
Ignoring request to alter tags of bug #773643 to the same tags previously set

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


--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
https://lists.debian.org/handler.s.u773643.142159393127115.transcr...@bugs.debian.org

Bug#775676: linux-image-3.16.0-4-686-pae: brcmsac (card bcm4313) cannot use channels > 11

2015-01-18 Thread Ben Hutchings 
Control: tag -1 wontfix

On Sun, 2015-01-18 at 14:48 +0100, Jakob Wiedner wrote:
> Package: src:linux
> Version: 3.16.7-ckt2-1
> Severity: important
> 
> Dear Maintainer,
> 
> I run Debian 8 on a Lenovo Ideapad n581 with a Broadcom bcm4313 wireless card.
> I can connect to the internet but channels over 11 are not detected although
> they can be used here in Norway (I have set regdom to NO via crda and also
> tried "iw reg set NO" but no success).
> 
> iwlist chan says:
> 
> wlan0 11 channels in total; available frequencies :
>   Channel 01 : 2.412 GHz
>   Channel 02 : 2.417 GHz
>   Channel 03 : 2.422 GHz
>   Channel 04 : 2.427 GHz
>   Channel 05 : 2.432 GHz
>   Channel 06 : 2.437 GHz
>   Channel 07 : 2.442 GHz
>   Channel 08 : 2.447 GHz
>   Channel 09 : 2.452 GHz
>   Channel 10 : 2.457 GHz
>   Channel 11 : 2.462 GHz
>   Current Frequency:2.417 GHz (Channel 2)
> 
> lono frequency information.
> 
> eth0  no frequency information.
[...]

Based on the kernel log, it appears that the card was manufactured for
use in the USA (or another country that uses the same regulations).  If
you set the country to Norway using crda, the effective rules will be
the intersection of the two countries' rules.

Ben.

-- 
Ben Hutchings
The generation of random numbers is too important to be left to chance.
- Robert Coveyou


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

Processed: Re: Bug#775676: linux-image-3.16.0-4-686-pae: brcmsac (card bcm4313) cannot use channels > 11

2015-01-18 Thread Debian Bug Tracking System 
Processing control commands:

> tag -1 wontfix
Bug #775676 [src:linux] linux-image-3.16.0-4-686-pae: brcmsac (card bcm4313) 
cannot use channels > 11
Added tag(s) wontfix.

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


--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
https://lists.debian.org/handler.s.b775676.142159367525456.transcr...@bugs.debian.org

Bug#775676: linux-image-3.16.0-4-686-pae: brcmsac (card bcm4313) cannot use channels > 11

2015-01-18 Thread Jakob Wiedner 
Package: src:linux
Version: 3.16.7-ckt2-1
Severity: important

Dear Maintainer,

I run Debian 8 on a Lenovo Ideapad n581 with a Broadcom bcm4313 wireless card.
I can connect to the internet but channels over 11 are not detected although
they can be used here in Norway (I have set regdom to NO via crda and also
tried "iw reg set NO" but no success).

iwlist chan says:

wlan0 11 channels in total; available frequencies :
  Channel 01 : 2.412 GHz
  Channel 02 : 2.417 GHz
  Channel 03 : 2.422 GHz
  Channel 04 : 2.427 GHz
  Channel 05 : 2.432 GHz
  Channel 06 : 2.437 GHz
  Channel 07 : 2.442 GHz
  Channel 08 : 2.447 GHz
  Channel 09 : 2.452 GHz
  Channel 10 : 2.457 GHz
  Channel 11 : 2.462 GHz
  Current Frequency:2.417 GHz (Channel 2)

lono frequency information.

eth0  no frequency information.



-- Package-specific info:
** Version:
Linux version 3.16.0-4-686-pae (debian-kernel@lists.debian.org) (gcc version 
4.8.3 (Debian 4.8.3-16) ) #1 SMP Debian 3.16.7-ckt2-1 (2014-12-08)

** Command line:
BOOT_IMAGE=/boot/vmlinuz-3.16.0-4-686-pae 
root=UUID=18507928-78b3-46da-abb9-3a3848ef3080 ro initrd=/install/initrd.gz 
quiet

** Not tainted

** Kernel log:
[   12.141281] iTCO_wdt: initialized. heartbeat=30 sec (nowayout=0)
[   12.961659] cfg80211: Calling CRDA to update world regulatory domain
[   13.070968] [drm] Enabling RC6 states: RC6 on, RC6p off, RC6pp off
[   13.320933] snd_hda_intel :00:1b.0: irq 44 for MSI/MSI-X
[   13.559896] Support for cores revisions 0x17 and 0x18 disabled by module 
param allhwsupport=0. Try b43.allhwsupport=1
[   13.559992] b43: probe of bcma0:0 failed with error -524
[   13.560022] Broadcom 43xx driver loaded [ Features: PMNLS ]
[   13.916473] sound hdaudioC0D0: CX20590: BIOS auto-probing.
[   13.916936] sound hdaudioC0D0: autoconfig: line_outs=1 
(0x1f/0x0/0x0/0x0/0x0) type:speaker
[   13.916942] sound hdaudioC0D0:speaker_outs=0 (0x0/0x0/0x0/0x0/0x0)
[   13.916946] sound hdaudioC0D0:hp_outs=1 (0x19/0x0/0x0/0x0/0x0)
[   13.916950] sound hdaudioC0D0:mono: mono_out=0x0
[   13.916953] sound hdaudioC0D0:inputs:
[   13.916958] sound hdaudioC0D0:  Internal Mic=0x1b
[   13.916962] sound hdaudioC0D0:  Mic=0x1a
[   13.917874] sound hdaudioC0D0: Enable sync_write for stable communication
[   14.253841] input: HDA Digital PCBeep as 
/devices/pci:00/:00:1b.0/sound/card0/hdaudioC0D0/input11
[   14.258490] input: HDA Intel PCH Mic as 
/devices/pci:00/:00:1b.0/sound/card0/input12
[   14.258696] input: HDA Intel PCH Headphone as 
/devices/pci:00/:00:1b.0/sound/card0/input13
[   14.258896] input: HDA Intel PCH HDMI/DP,pcm=3 as 
/devices/pci:00/:00:1b.0/sound/card0/input14
[   14.350752] brcmsmac bcma0:0: mfg 4bf core 812 rev 24 class 0 irq 17
[   14.638970] Bluetooth: Core ver 2.19
[   14.639009] NET: Registered protocol family 31
[   14.639012] Bluetooth: HCI device and connection manager initialized
[   14.639024] Bluetooth: HCI socket layer initialized
[   14.639030] Bluetooth: L2CAP socket layer initialized
[   14.639053] Bluetooth: SCO socket layer initialized
[   14.892678] ieee80211 phy0: Selected rate control algorithm 'minstrel_ht'
[   14.893100] cfg80211: Calling CRDA to update world regulatory domain
[   14.976438] Adding 1951740k swap on /dev/sda6.  Priority:-1 extents:1 
across:1951740k FS
[   15.002100] media: Linux media interface: v0.10
[   15.015087] Linux video capture interface: v2.00
[   15.028436] usbcore: registered new interface driver btusb
[   15.074441] cfg80211: Calling CRDA to update world regulatory domain
[   15.372347] uvcvideo: Found UVC 1.00 device Lenovo EasyCamera (04f2:b2e2)
[   15.374887] input: Lenovo EasyCamera as 
/devices/pci:00/:00:1d.0/usb4/4-1/4-1.6/4-1.6:1.0/input/input15
[   15.375105] usbcore: registered new interface driver uvcvideo
[   15.375109] USB Video Class driver (1.1.1)
[   15.531345] cfg80211: World regulatory domain updated:
[   15.531355] cfg80211:  DFS Master region: unset
[   15.531359] cfg80211:   (start_freq - end_freq @ bandwidth), 
(max_antenna_gain, max_eirp), (dfs_cac_time)
[   15.531365] cfg80211:   (2402000 KHz - 2472000 KHz @ 4 KHz), (N/A, 2000 
mBm), (N/A)
[   15.531369] cfg80211:   (2457000 KHz - 2482000 KHz @ 4 KHz), (N/A, 2000 
mBm), (N/A)
[   15.531373] cfg80211:   (2474000 KHz - 2494000 KHz @ 2 KHz), (N/A, 2000 
mBm), (N/A)
[   15.531378] cfg80211:   (517 KHz - 525 KHz @ 8 KHz, 16 KHz 
AUTO), (N/A, 2000 mBm), (N/A)
[   15.531383] cfg80211:   (525 KHz - 533 KHz @ 8 KHz, 16 KHz 
AUTO), (N/A, 2000 mBm), (0 s)
[   15.531388] cfg80211:   (549 KHz - 573 KHz @ 16 KHz), (N/A, 2000 
mBm), (0 s)
[   15.531392] cfg80211:   (5735000 KHz - 5835000 KHz @ 8 KHz), (N/A, 2000 
mBm), (N/A)
[   15.531396] cfg80211:   (5724 KHz - 6372 KHz @ 216 KHz), (N/A, 0 
mBm), (N/A)
[   15.531422] cfg80211: Cal

Processed: Re: Bug#775615: Upstream bug

2015-01-18 Thread Debian Bug Tracking System 
Processing control commands:

> forwarded -1 https://bugs.freedesktop.org/show_bug.cgi?id=54226
Bug #775615 [src:linux] i915: GPU HANG: ecode -1:0x, reason: Kicking 
stuck semaphore on render ring, action: continue
Set Bug forwarded-to-address to 
'https://bugs.freedesktop.org/show_bug.cgi?id=54226'.

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


--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
https://lists.debian.org/handler.s.b775615.142158694815956.transcr...@bugs.debian.org

Bug#775615: Upstream bug

2015-01-18 Thread Ben Hutchings 
Control: forwarded -1 https://bugs.freedesktop.org/show_bug.cgi?id=54226

On Sun, 2015-01-18 at 14:46 +0200, Vasil Kolev wrote:
> On Sun, 18 Jan 2015 12:03:10 +
> Ben Hutchings  wrote:
> 
> > On Sun, 2015-01-18 at 03:06 +0200, Vasil Kolev wrote:
> > > This looks like the upstream bug:
> > > https://bugs.freedesktop.org/show_bug.cgi?id=54226
> > 
> > As the error message said, you should open a *new* upstream bug report
> > and let the maintainers work out whether it is the same as that one.
> > 
> > Ben.
> > 
> 
> I already have one that was labeled as a duplicate of this upstream one.

OK, thanks.

Ben.

-- 
Ben Hutchings
The generation of random numbers is too important to be left to chance.
- Robert Coveyou


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

Bug#775611: [sh]: FTBFS due to unknown compiler option '-m32'

2015-01-18 Thread John Paul Adrian Glaubitz 
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

On 01/18/2015 12:52 PM, Ben Hutchings wrote:
> The next question is whether recordmcount.c works properly for SH.
> 
> Adrian, can you check whether ftrace seems to work on the kernel
> built with HAVE_C_RECORDMCOUNT selected?  (See
> Documentation/trace/ftrace.txt and particularly the 'function'
> example.)

I guess that involves also installing the kernel and running it? The
reason why I ask is that I currently don't have physical access to
any of the SH4 machines yet as I am still waiting for Nobuhiro Iwamatsu
to send me one of the spare boards he has.

Thus, if the kernel locks up the kernel for whatever reason, I am a
bit lost until Nobuhiro can reset the machine. Having my own local
SH4 machine would simplify things dramatically.

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 v1

iQIcBAEBCAAGBQJUu646AAoJEHQmOzf1tfkT7V4P/R13gZfztFdJhC2t7k5naDAh
IcS5dwdeilCqRHEGm0Su5eGV7d6taZASplcKahDgw14VlQ/7tpSlMNQU2AYj8IKo
bQ8xJfjmwznPOE3U/4p/dH2whfQWXowLoTKIO/Ayd06N/swP2kfMvwQMbVlxfbm6
fy5BmDry7NQQO39cCfIA1GPo4Eme1VHLaG/mRRDvuXWaujX/CFA9aFdiiZ2ZRQjp
achH6zIb/9TdflWVNdMbadusUaZZgkin7p3Ky4jC0kk9pWtcWRR4zZdBGoKFrr3N
HsdPVJScNWZeaaH7G//3L9WNgITQHC+gjoxuBrVN4NuVU5TIoHitsdhQGdJ96wJZ
TENKenPiCQxwwLwljSjJ6lV+V1B7YT1nOpOBwK5jePzqIUL3ymejigwPXNQqlwev
LK4I2tGMWDyh1VwZz0lwmRLh+Nu1NdPFzlu6981OAWOO8rSpcxzGTp5ipNPPY3VY
j2MC0nibwx74DJYHzgDGCUdGN5lvDe0qNtwkqyKgnKCjsVdNHKZVEynFOfdmPSLz
2YfY8PZFRgmb5/Fb59990mvfEkY+No4o67yZP6k9jBcfAY7E/jTFjpzKQQjYdkhB
q3hKl2M5fcvSKMCMrDWSOPEbC4By0arYvsDVVUecTvgecP/TGeBiJpPLVY9gLSAx
JlAltcZjGayAdPYLgwFV
=M5g3
-END PGP SIGNATURE-


-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/54bbae3b.8020...@physik.fu-berlin.de

Bug#775615: Upstream bug

2015-01-18 Thread Vasil Kolev 
On Sun, 18 Jan 2015 12:03:10 +
Ben Hutchings  wrote:

> On Sun, 2015-01-18 at 03:06 +0200, Vasil Kolev wrote:
> > This looks like the upstream bug:
> > https://bugs.freedesktop.org/show_bug.cgi?id=54226
> 
> As the error message said, you should open a *new* upstream bug report
> and let the maintainers work out whether it is the same as that one.
> 
> Ben.
> 

I already have one that was labeled as a duplicate of this upstream one.


pgppBiR5nFMlq.pgp
Description: OpenPGP digital signature

Incomplete log for linux 3.16.7-ckt4-1 on mips

2015-01-18 Thread Ben Hutchings 
The attempted build of linux version 3.16.7-ckt4-1 on mips-aql-01
failed, but the log shown at

 is incomplete so I have no idea why.  Is there any more information you can 
retrieve that could explain the failure?

Ben.

-- 
Ben Hutchings
The generation of random numbers is too important to be left to chance.
- Robert Coveyou


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

Bug#775615: Upstream bug

2015-01-18 Thread Ben Hutchings 
On Sun, 2015-01-18 at 03:06 +0200, Vasil Kolev wrote:
> This looks like the upstream bug:
> https://bugs.freedesktop.org/show_bug.cgi?id=54226

As the error message said, you should open a *new* upstream bug report
and let the maintainers work out whether it is the same as that one.

Ben.

-- 
Ben Hutchings
The generation of random numbers is too important to be left to chance.
- Robert Coveyou


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

Processed: tagging 775611

2015-01-18 Thread Debian Bug Tracking System 
Processing commands for cont...@bugs.debian.org:

> tags 775611 + upstream
Bug #775611 [linux] [sh]: FTBFS due to unknown compiler option '-m32'
Added tag(s) upstream.
> thanks
Stopping processing here.

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


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

Bug#775611: [sh]: FTBFS due to unknown compiler option '-m32'

2015-01-18 Thread Ben Hutchings 
On Sun, 2015-01-18 at 12:15 +0100, Geert Uytterhoeven wrote:
> On Sun, Jan 18, 2015 at 10:58 AM, Ben Hutchings  wrote:
> > On Sun, 2015-01-18 at 00:35 +0100, John Paul Adrian Glaubitz wrote:
> >> Package: linux
> >> Version: 3.16.7-ckt4-1
> >> Severity: normal
> >> Tags: patch
> >>
> >> Hi!
> >>
> >> The kernel package currently fails to build from source on sh4 since
> >> the build scripts try to pass the '-m32' compiler option on gcc which
> >> is not available with gcc on sh4 (also according to the manpage).
> >>
> >> Selecting HAVE_C_RECORDMCOUNT in arch/sh/Kconfig (see attached patch
> >> by Ben Hutchings) fixes the issues. However, I also suggest removing
> >> the line "$cc .= " -m32";" for sh compiler options in scripts/
> >> recordmcount.pl.
> >
> > Steven and SH experts, what do you think of this?
> 
> It seems most compilers don't support -m32, unless they're biarch.
> On an Ubuntu 14.04 LTS box with lots of cross-compilers from korg/crosstool:
[...]

Right.  It's also not mentioned at all in the documentation of SH
options for gcc 4.9.  There appear to be multiple 32-bit modes and
instruction encodings to choose from, so it wouldn't be very useful.

The next question is whether recordmcount.c works properly for SH.

Adrian, can you check whether ftrace seems to work on the kernel built
with HAVE_C_RECORDMCOUNT selected?  (See Documentation/trace/ftrace.txt
and particularly the 'function' example.)

Ben.

-- 
Ben Hutchings
The generation of random numbers is too important to be left to chance.
- Robert Coveyou


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

Processed: tagging 766920, severity of 766920 is important

2015-01-18 Thread Debian Bug Tracking System 
Processing commands for cont...@bugs.debian.org:

> tags 766920 + unreproducible
Bug #766920 [initramfs-tools] produces unbootable initramfs with lilo 
hexadecimal syntax (root=803)
Added tag(s) unreproducible.
> severity 766920 important
Bug #766920 [initramfs-tools] produces unbootable initramfs with lilo 
hexadecimal syntax (root=803)
Severity set to 'important' from 'serious'
> thanks
Stopping processing here.

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


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

Bug#775611: [sh]: FTBFS due to unknown compiler option '-m32'

2015-01-18 Thread Geert Uytterhoeven 
On Sun, Jan 18, 2015 at 10:58 AM, Ben Hutchings  wrote:
> On Sun, 2015-01-18 at 00:35 +0100, John Paul Adrian Glaubitz wrote:
>> Package: linux
>> Version: 3.16.7-ckt4-1
>> Severity: normal
>> Tags: patch
>>
>> Hi!
>>
>> The kernel package currently fails to build from source on sh4 since
>> the build scripts try to pass the '-m32' compiler option on gcc which
>> is not available with gcc on sh4 (also according to the manpage).
>>
>> Selecting HAVE_C_RECORDMCOUNT in arch/sh/Kconfig (see attached patch
>> by Ben Hutchings) fixes the issues. However, I also suggest removing
>> the line "$cc .= " -m32";" for sh compiler options in scripts/
>> recordmcount.pl.
>
> Steven and SH experts, what do you think of this?

It seems most compilers don't support -m32, unless they're biarch.
On an Ubuntu 14.04 LTS box with lots of cross-compilers from korg/crosstool:

/usr/bin/c89-gcc OK
/usr/bin/c99-gcc OK
/usr/bin/x86_64-linux-gnu-gcc OK
/opt/cross/gcc-4.2.4-nolibc/avr32-linux/bin/avr32-linux-gcc cc1:
error: unrecognized command line option "-m32"
/opt/cross/gcc-4.8.0-nolibc/microblaze-linux/bin/microblaze-linux-gcc
microblaze-linux-gcc: error: unrecognized command line option '-m32'
/opt/cross/gcc-4.8.0-nolibc/powerpc64-linux/bin/powerpc64-linux-gcc OK
/opt/cross/gcc-4.5.1-nolibc/or32-linux/bin/or32-linux-gcc cc1: error:
unrecognized command line option "-m32"
/opt/cross/gcc-4.6.3-nolibc/crisv32-linux/bin/crisv32-linux-gcc cc1:
error: unrecognized command line option '-m32'
/opt/cross/gcc-4.6.3-nolibc/frv-linux/bin/frv-linux-gcc cc1: error:
unrecognized command line option '-m32'
/opt/cross/gcc-4.6.3-nolibc/bfin-uclinux/bin/bfin-uclinux-gcc cc1:
error: unrecognized command line option '-m32'
/opt/cross/gcc-4.6.3-nolibc/sparc64-linux/bin/sparc64-linux-gcc OK
/opt/cross/gcc-4.6.3-nolibc/m68k-linux/bin/m68k-linux-gcc cc1: error:
unrecognized command line option '-m32'
/opt/cross/gcc-4.6.3-nolibc/alpha-linux/bin/alpha-linux-gcc cc1:
error: unrecognized command line option '-m32'
/opt/cross/gcc-4.6.3-nolibc/sh4-linux/bin/sh4-linux-gcc cc1: error:
unrecognized command line option '-m32'
/opt/cross/gcc-4.6.3-nolibc/m32r-linux/bin/m32r-linux-gcc cc1: error:
unrecognized command line option '-m32'
/opt/cross/gcc-4.6.3-nolibc/ia64-linux/bin/ia64-linux-gcc cc1: error:
unrecognized command line option '-m32'
/opt/cross/gcc-4.6.3-nolibc/xtensa-linux/bin/xtensa-linux-gcc cc1:
error: unrecognized command line option '-m32'
/opt/cross/gcc-4.6.3-nolibc/arm-unknown-linux-gnueabi/bin/arm-unknown-linux-gnueabi-gcc
cc1: error: unrecognized command line option '-m32'
/opt/cross/gcc-4.6.3-nolibc/am33_2.0-linux/bin/am33_2.0-linux-gcc cc1:
error: unrecognized command line option '-m32'
/opt/cross/gcc-4.6.3-nolibc/mips64-linux/bin/mips64-linux-gcc cc1:
error: unrecognized command line option '-m32'
/opt/cross/gcc-4.6.3-nolibc/s390x-linux/bin/s390x-linux-gcc cc1:
error: unrecognized command line option '-m32'
/opt/cross/gcc-4.6.3-nolibc/hppa64-linux/bin/hppa64-linux-gcc cc1:
error: unrecognized command line option '-m32'
/opt/cross/gcc-linaro-aarch64-none-elf-4.8-2013.08_linux/bin/aarch64-none-elf-gcc
aarch64-none-elf-gcc: error: unrecognized command line option ‘-m32’

Gr{oetje,eeting}s,

Geert

--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- ge...@linux-m68k.org

In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds


--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
https://lists.debian.org/CAMuHMdXe=hRZ_i=9-jpgmykfhnn4gtokheam+laa5qn0ywf...@mail.gmail.com

Bug#770790: random/intermittent black screen fixed upstream in 3.16.7-ckt2

2015-01-18 Thread Tuxo Holic 
Update:


Turns out rebuilding 3.16.7-ckt2 (which is the current kernel source in 
testing) and using this PATCH [1] does fix it for me.
I assume this will be pushed soon to a new linux-image-3.16.0-xx ?



[1] https://bugzilla.kernel.org/show_bug.cgi?id=83461#c27

Bug#775611: [sh]: FTBFS due to unknown compiler option '-m32'

2015-01-18 Thread Ben Hutchings 
On Sun, 2015-01-18 at 00:35 +0100, John Paul Adrian Glaubitz wrote:
> Package: linux
> Version: 3.16.7-ckt4-1
> Severity: normal
> Tags: patch
> 
> Hi!
> 
> The kernel package currently fails to build from source on sh4 since
> the build scripts try to pass the '-m32' compiler option on gcc which
> is not available with gcc on sh4 (also according to the manpage).
> 
> Selecting HAVE_C_RECORDMCOUNT in arch/sh/Kconfig (see attached patch
> by Ben Hutchings) fixes the issues. However, I also suggest removing
> the line "$cc .= " -m32";" for sh compiler options in scripts/
> recordmcount.pl.

Steven and SH experts, what do you think of this?

Ben.

-- 
Ben Hutchings
The generation of random numbers is too important to be left to chance.
- Robert Coveyou


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