Bug#746411: linux-image-3.2.0-4-amd64: regression: suspend/resume not working after update

2014-05-12 Thread Jens Thiele
Ben Hutchings b...@decadent.org.uk writes:

 Thanks a lot.  This should be reverted in the next security update.
 (Yes, even though it is not a security issue.)

looking forward for the update, thanks!

greetings,
jens

PS:
i could imagine the revert will break stuff for other machines and
likely a fixed version of e07518e9ce84547ef7a81478dbd3fed1539726da will
be needed?

if i can be of help by testing a possible new version, feel free to
contact me


pgpTYpS8qUPeB.pgp
Description: PGP signature


Fwd: Debian 7.5 fails with kernel.org backports

2014-05-12 Thread Steffen Dettmer
Hi,

after upgrading to Debian 7.5 (linux-headers-3.2.0-4-common),
backports 3.10.2 [1] does not compile anymore [2]. Without it, I have
issues with Antheros WLAN cards.

Does Debian 7.5 include another backported versions? Can it be removed
and replaced by official backports 3.10.2 from [1]?

I also tried backports-3.13-rc8-1 [3] without success.

It could be that it is related to some e1000e backport (the sources
also don't compile anymore, I did not yet tested whether the driver
included in 7.5 works without backported driver) as in #705959 [4]?

How do I get wireless backports working again with 7.5?

Is it normal to have such breaking changes in a minor release? I was
really surpised, what can I do?

Any help appreciated!

Best regards,
Steffen

[1] 
https://www.kernel.org/pub/linux/kernel/projects/backports/stable/v3.10/backports-3.10-2.tar.bz2

[2] In file included from
/tmp/nd-ath9k/backports-3.10-2/compat/compat-3.7.c:13:0:
/tmp/nd-ath9k/backports-3.10-2/backport-include/linux/pci.h:112:19:
error: redefinition of ‘pcie_capability_set_word’
/usr/src/linux-headers-3.2.0-4-common/include/linux/pci.h:806:19:
note: previous definition of ‘pcie_capability_set_word’ was here

[3] 
https://www.kernel.org/pub/linux/kernel/projects/backports/stable/v3.13-rc8/backports-3.13-rc8-1.tar.xz

[4] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=705959


--
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/caobounnm++tkqrrfshf0kzeegixq3p4nscje25ogmhtcmmq...@mail.gmail.com



Re: Fwd: Debian 7.5 fails with kernel.org backports

2014-05-12 Thread Ben Hutchings
On Mon, 2014-05-12 at 11:45 +0200, Steffen Dettmer wrote:
 Hi,
 
 after upgrading to Debian 7.5 (linux-headers-3.2.0-4-common),
 backports 3.10.2 [1] does not compile anymore [2]. Without it, I have
 issues with Antheros WLAN cards.
 
 Does Debian 7.5 include another backported versions? Can it be removed
 and replaced by official backports 3.10.2 from [1]?
 
 I also tried backports-3.13-rc8-1 [3] without success.

I don't understand why you're picking random old versions.  There is
also a backports-3.14, though I don't know that it will work any better.

 It could be that it is related to some e1000e backport (the sources
 also don't compile anymore, I did not yet tested whether the driver
 included in 7.5 works without backported driver) as in #705959 [4]?
 
 How do I get wireless backports working again with 7.5?
 
 Is it normal to have such breaking changes in a minor release? I was
 really surpised, what can I do?
[...]

Yes, it is normal for OOT modules to fail to build after we backport
stuff.  This also happens in all other distributions that backport
drivers.

But you shouldn't *need* to rebuild them, as we do maintain binary
compatibility as far as possible.

Ben.

-- 
Ben Hutchings
Knowledge is power.  France is bacon.


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


Bug#747871: mkinitramfs: breaks with LUKS root on MMC (mkinitramfs: for root /dev/dm-0 missing mmcblk /sys/block/ entry) and MODULES=dep

2014-05-12 Thread Sascha Silbe
Package: initramfs-tools
Version: 0.109.1
Severity: normal
File: /usr/sbin/mkinitramfs

Dear Maintainer,

on a system with the rootfs living inside LUKS on an SD card,
mkinitramfs (and thus update-initramfs) fails with:

=== Begin ===
root@mimosa:/boot# update-initramfs -k 3.0.19-mimosa-8-01603-g1b85fba -c
update-initramfs: Generating /boot/initrd.img-3.0.19-mimosa-8-01603-g1b85fba
mkinitramfs: for root /dev/dm-0 missing mmcblk /sys/block/ entry
mkinitramfs: workaround is MODULES=most
mkinitramfs: Error please report the bug
update-initramfs: failed for /boot/initrd.img-3.0.19-mimosa-8-01603-g1b85fba 
with 1.
=== End ===


Older versions displayed a warning (which I ignored since everything
needed for boot is built-in to the custom kernel anyway), but didn't
abort initramfs generation.

It looks like hook-functions is a bit overzealous in stripping down
the partition name to a device name, resulting in mmcblk rather than
mmcblk0. There's existing special casing in dep_add_modules for
device mapper (LVM/LUKS) on top of cciss or ida and for root on cciss,
ida, mmc and a few more in place already, but not for device mapper on
top of mmc. Maybe a recursive function would be a better fit for
determining the modules needed for the rootfs?

For reference, this is a trace of mkinitramfs:

=== Begin trace ===
+ CONFDIR=/etc/initramfs-tools
+ verbose=n
+ test -e /bin/busybox
+ BUSYBOXDIR=/bin
+ test -e /usr/lib/initramfs-tools/bin/busybox
+ export BUSYBOXDIR
++ getopt -o c:d:ko:r:v -n mkinitramfs -- -o 
/boot/initrd.img-3.0.19-mimosa-8-01603-g1b85fba.new 
3.0.19-mimosa-8-01603-g1b85fba
+ OPTIONS=' -o '\''/boot/initrd.img-3.0.19-mimosa-8-01603-g1b85fba.new'\'' -- 
'\''3.0.19-mimosa-8-01603-g1b85fba'\'''
+ '[' 0 '!=' 0 ']'
+ eval set -- ' -o '\''/boot/initrd.img-3.0.19-mimosa-8-01603-g1b85fba.new'\'' 
-- '\''3.0.19-mimosa-8-01603-g1b85fba'\'''
++ set -- -o /boot/initrd.img-3.0.19-mimosa-8-01603-g1b85fba.new -- 
3.0.19-mimosa-8-01603-g1b85fba
+ true
+ case $1 in
+ outfile=/boot/initrd.img-3.0.19-mimosa-8-01603-g1b85fba.new
+ shift 2
+ true
+ case $1 in
+ shift
+ break
+ . /usr/share/initramfs-tools/scripts/functions
+ . /usr/share/initramfs-tools/hook-functions
+ . /etc/initramfs-tools/initramfs.conf
++ MODULES=dep
++ BUSYBOX=y
++ KEYMAP=n
++ COMPRESS=gzip
++ DEVICE=
++ NFSROOT=auto
+ EXTRA_CONF=
+ for i in '/usr/share/initramfs-tools/conf.d/*' '${CONFDIR}/conf.d/*'
+ '[' -e '/usr/share/initramfs-tools/conf.d/*' ']'
+ for i in '/usr/share/initramfs-tools/conf.d/*' '${CONFDIR}/conf.d/*'
+ '[' -e '/etc/initramfs-tools/conf.d/*' ']'
+ for i in '/usr/share/initramfs-tools/conf-hooks.d/*'
+ '[' -d /usr/share/initramfs-tools/conf-hooks.d/cryptsetup ']'
+ '[' -e /usr/share/initramfs-tools/conf-hooks.d/cryptsetup ']'
+ . /usr/share/initramfs-tools/conf-hooks.d/cryptsetup
++ KEYMAP=y
++ BUSYBOX=y
++ FRAMEBUFFER=y
+ '[' -n '' ']'
+ '[' -z /boot/initrd.img-3.0.19-mimosa-8-01603-g1b85fba.new ']'
+ touch /boot/initrd.img-3.0.19-mimosa-8-01603-g1b85fba.new
++ readlink -f /boot/initrd.img-3.0.19-mimosa-8-01603-g1b85fba.new
+ outfile=/boot/initrd.img-3.0.19-mimosa-8-01603-g1b85fba.new
+ '[' 1 -ne 1 ']'
+ version=3.0.19-mimosa-8-01603-g1b85fba
+ case ${version} in
+ case ${version} in
+ '[' -z '' ']'
+ compress=gzip
+ command -v gzip
+ dpkg --compare-versions 3.0.19-mimosa-8-01603-g1b85fba lt 2.6.38
+ '[' gzip = lzop ']'
+ '[' gzip = xz ']'
+ '[' -d /boot/initrd.img-3.0.19-mimosa-8-01603-g1b85fba.new ']'
+ MODULESDIR=/lib/modules/3.0.19-mimosa-8-01603-g1b85fba
+ '[' '!' -e /lib/modules/3.0.19-mimosa-8-01603-g1b85fba ']'
+ '[' '!' -e /lib/modules/3.0.19-mimosa-8-01603-g1b85fba/modules.dep ']'
+ '[' -n '' ']'
++ mktemp -d /var/tmp/mkinitramfs_XX
+ DESTDIR=/var/tmp/mkinitramfs_K8XasF
+ chmod 755 /var/tmp/mkinitramfs_K8XasF
+ NOEXEC=
++ tail -1
++ awk '{print $6}'
++ df -P /var/tmp/mkinitramfs_K8XasF
+ fs=/
+ '[' -n / ']'
+ grep -q 'on / .*noexec'
+ mount
++ mktemp /var/tmp/mkinitramfs-OL_XX
+ __TMPCPIOGZ=/var/tmp/mkinitramfs-OL_OuJNFs
++ dpkg --print-architecture
+ DPKG_ARCH=armel
+ export MODULESDIR
+ export version
+ export CONFDIR
+ export DESTDIR
+ export DPKG_ARCH
+ export verbose
+ export KEYMAP
+ export MODULES
+ export BUSYBOX
+ export __TMPCPIOGZ
+ for d in bin conf/conf.d etc lib/modules run sbin scripts '${MODULESDIR}'
+ mkdir -p /var/tmp/mkinitramfs_K8XasF/bin
+ for d in bin conf/conf.d etc lib/modules run sbin scripts '${MODULESDIR}'
+ mkdir -p /var/tmp/mkinitramfs_K8XasF/conf/conf.d
+ for d in bin conf/conf.d etc lib/modules run sbin scripts '${MODULESDIR}'
+ mkdir -p /var/tmp/mkinitramfs_K8XasF/etc
+ for d in bin conf/conf.d etc lib/modules run sbin scripts '${MODULESDIR}'
+ mkdir -p /var/tmp/mkinitramfs_K8XasF/lib/modules
+ for d in bin conf/conf.d etc lib/modules run sbin scripts '${MODULESDIR}'
+ mkdir -p /var/tmp/mkinitramfs_K8XasF/run
+ for d in bin conf/conf.d etc lib/modules run sbin scripts '${MODULESDIR}'
+ mkdir -p /var/tmp/mkinitramfs_K8XasF/sbin
+ for d in bin conf/conf.d etc lib/modules run sbin 

Bug#746232: linux-image-3.2.0-4-rt-686-pae: rcu_preempt detected stalls at boot

2014-05-12 Thread Alexandra N. Kossovsky
On May 11 01:11, Ben Hutchings wrote:
 On Sat, 2014-05-10 at 09:54 +0400, Alexandra N. Kossovsky wrote:
  On May 09 18:46, Ben Hutchings wrote:
   Is this a regression from version 3.2.54-2?
  
  No. All 3.2.x-rt Debain kernels I've tried do not boot.  I've gone back
  for at least one year.
 
 As this is not a regression, I have no idea where to look for the bug.
 Please try reporting this on the linux-rt-us...@vger.kernel.org list,
 and cc this bug address.

I do not think linux-rt people are interested in finding a bug which was
already fixed more than a year ago.  linux-image-3.6-trunk-rt-686-pae
version
3.6.9-1~experimental.1 and all newer rt kernels including the latest
3.12-0.bpo.1-rt-686-pae (3.12.9-1~bpo70+1) boot properly.

Feel free to close this bug as wantfix.

-- 
Alexandra N. Kossovsky
OKTET Labs (http://www.oktetlabs.ru/)


-- 
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/20140512133928.gi12...@oktetlabs.ru



Bug#735491: Shutdown Ok in linux-3.11.10

2014-05-12 Thread Arvind R
The shutdown failure does not occur with linux-3.11.10, the last of the
3.11 series kernels.


-


Bug#742619: linux: Please reenable CONFIG_SCSI_PROC_FS

2014-05-12 Thread Christian Seiler

Hello,

I'm sorry if this seems pushy, but since it is trivial to implement 
this
change, I'd like to ask if you've considered reenabling 
CONFIG_SCSI_PROC_FS?


Thank you!

Regards,
Christian


--
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/189678693b172f6b2e7e369f770d5...@iwakd.de



Bug#746232: linux-image-3.2.0-4-rt-686-pae: rcu_preempt detected stalls at boot

2014-05-12 Thread Ben Hutchings
On Mon, 2014-05-12 at 17:39 +0400, Alexandra N. Kossovsky wrote:
 On May 11 01:11, Ben Hutchings wrote:
  On Sat, 2014-05-10 at 09:54 +0400, Alexandra N. Kossovsky wrote:
   On May 09 18:46, Ben Hutchings wrote:
Is this a regression from version 3.2.54-2?
   
   No. All 3.2.x-rt Debain kernels I've tried do not boot.  I've gone back
   for at least one year.
  
  As this is not a regression, I have no idea where to look for the bug.
  Please try reporting this on the linux-rt-us...@vger.kernel.org list,
  and cc this bug address.
 
 I do not think linux-rt people are interested in finding a bug which was
 already fixed more than a year ago.  linux-image-3.6-trunk-rt-686-pae
 version
 3.6.9-1~experimental.1 and all newer rt kernels including the latest
 3.12-0.bpo.1-rt-686-pae (3.12.9-1~bpo70+1) boot properly.
 
 Feel free to close this bug as wantfix.

The 3.2-rt stable branch is still maintained by Steven Rostedt.  He or
others might recognise this failure.

Ben.

-- 
Ben Hutchings
Knowledge is power.  France is bacon.


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


Uploading linux (3.14.4-1)

2014-05-12 Thread Ben Hutchings
I intend to upload linux to unstable on Tuesday, once 3.14.4 is out.
This may require an ABI bump; that's not clear yet.

Ben.

-- 
Ben Hutchings
Knowledge is power.  France is bacon.


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


Processing of linux_3.2.57-3+deb7u1_amd64.changes

2014-05-12 Thread Debian FTP Masters
linux_3.2.57-3+deb7u1_amd64.changes uploaded successfully to localhost
along with the files:
  linux_3.2.57-3+deb7u1.dsc
  linux_3.2.57.orig.tar.xz
  linux_3.2.57-3+deb7u1.debian.tar.xz
  linux-support-3.2.0-4_3.2.57-3+deb7u1_all.deb
  linux-doc-3.2_3.2.57-3+deb7u1_all.deb
  linux-manual-3.2_3.2.57-3+deb7u1_all.deb
  linux-source-3.2_3.2.57-3+deb7u1_all.deb
  linux-headers-3.2.0-4-amd64_3.2.57-3+deb7u1_amd64.deb
  linux-image-3.2.0-4-amd64-dbg_3.2.57-3+deb7u1_amd64.deb
  linux-image-3.2.0-4-amd64_3.2.57-3+deb7u1_amd64.deb
  xen-linux-system-3.2.0-4-amd64_3.2.57-3+deb7u1_amd64.deb
  linux-headers-3.2.0-4-common_3.2.57-3+deb7u1_amd64.deb
  linux-headers-3.2.0-4-all_3.2.57-3+deb7u1_amd64.deb
  linux-headers-3.2.0-4-all-amd64_3.2.57-3+deb7u1_amd64.deb
  linux-libc-dev_3.2.57-3+deb7u1_amd64.deb
  linux-headers-3.2.0-4-rt-amd64_3.2.57-3+deb7u1_amd64.deb
  linux-image-3.2.0-4-rt-amd64-dbg_3.2.57-3+deb7u1_amd64.deb
  linux-image-3.2.0-4-rt-amd64_3.2.57-3+deb7u1_amd64.deb
  linux-headers-3.2.0-4-common-rt_3.2.57-3+deb7u1_amd64.deb
  kernel-image-3.2.0-4-amd64-di_3.2.57-3+deb7u1_amd64.udeb
  nic-modules-3.2.0-4-amd64-di_3.2.57-3+deb7u1_amd64.udeb
  nic-extra-modules-3.2.0-4-amd64-di_3.2.57-3+deb7u1_amd64.udeb
  nic-wireless-modules-3.2.0-4-amd64-di_3.2.57-3+deb7u1_amd64.udeb
  nic-shared-modules-3.2.0-4-amd64-di_3.2.57-3+deb7u1_amd64.udeb
  serial-modules-3.2.0-4-amd64-di_3.2.57-3+deb7u1_amd64.udeb
  usb-serial-modules-3.2.0-4-amd64-di_3.2.57-3+deb7u1_amd64.udeb
  ppp-modules-3.2.0-4-amd64-di_3.2.57-3+deb7u1_amd64.udeb
  pata-modules-3.2.0-4-amd64-di_3.2.57-3+deb7u1_amd64.udeb
  cdrom-core-modules-3.2.0-4-amd64-di_3.2.57-3+deb7u1_amd64.udeb
  firewire-core-modules-3.2.0-4-amd64-di_3.2.57-3+deb7u1_amd64.udeb
  scsi-core-modules-3.2.0-4-amd64-di_3.2.57-3+deb7u1_amd64.udeb
  scsi-modules-3.2.0-4-amd64-di_3.2.57-3+deb7u1_amd64.udeb
  scsi-common-modules-3.2.0-4-amd64-di_3.2.57-3+deb7u1_amd64.udeb
  scsi-extra-modules-3.2.0-4-amd64-di_3.2.57-3+deb7u1_amd64.udeb
  plip-modules-3.2.0-4-amd64-di_3.2.57-3+deb7u1_amd64.udeb
  floppy-modules-3.2.0-4-amd64-di_3.2.57-3+deb7u1_amd64.udeb
  loop-modules-3.2.0-4-amd64-di_3.2.57-3+deb7u1_amd64.udeb
  btrfs-modules-3.2.0-4-amd64-di_3.2.57-3+deb7u1_amd64.udeb
  ext2-modules-3.2.0-4-amd64-di_3.2.57-3+deb7u1_amd64.udeb
  ext3-modules-3.2.0-4-amd64-di_3.2.57-3+deb7u1_amd64.udeb
  ext4-modules-3.2.0-4-amd64-di_3.2.57-3+deb7u1_amd64.udeb
  isofs-modules-3.2.0-4-amd64-di_3.2.57-3+deb7u1_amd64.udeb
  jfs-modules-3.2.0-4-amd64-di_3.2.57-3+deb7u1_amd64.udeb
  ntfs-modules-3.2.0-4-amd64-di_3.2.57-3+deb7u1_amd64.udeb
  reiserfs-modules-3.2.0-4-amd64-di_3.2.57-3+deb7u1_amd64.udeb
  xfs-modules-3.2.0-4-amd64-di_3.2.57-3+deb7u1_amd64.udeb
  fat-modules-3.2.0-4-amd64-di_3.2.57-3+deb7u1_amd64.udeb
  ufs-modules-3.2.0-4-amd64-di_3.2.57-3+deb7u1_amd64.udeb
  qnx4-modules-3.2.0-4-amd64-di_3.2.57-3+deb7u1_amd64.udeb
  md-modules-3.2.0-4-amd64-di_3.2.57-3+deb7u1_amd64.udeb
  multipath-modules-3.2.0-4-amd64-di_3.2.57-3+deb7u1_amd64.udeb
  usb-modules-3.2.0-4-amd64-di_3.2.57-3+deb7u1_amd64.udeb
  usb-storage-modules-3.2.0-4-amd64-di_3.2.57-3+deb7u1_amd64.udeb
  pcmcia-storage-modules-3.2.0-4-amd64-di_3.2.57-3+deb7u1_amd64.udeb
  fb-modules-3.2.0-4-amd64-di_3.2.57-3+deb7u1_amd64.udeb
  input-modules-3.2.0-4-amd64-di_3.2.57-3+deb7u1_amd64.udeb
  event-modules-3.2.0-4-amd64-di_3.2.57-3+deb7u1_amd64.udeb
  mouse-modules-3.2.0-4-amd64-di_3.2.57-3+deb7u1_amd64.udeb
  irda-modules-3.2.0-4-amd64-di_3.2.57-3+deb7u1_amd64.udeb
  parport-modules-3.2.0-4-amd64-di_3.2.57-3+deb7u1_amd64.udeb
  nic-pcmcia-modules-3.2.0-4-amd64-di_3.2.57-3+deb7u1_amd64.udeb
  pcmcia-modules-3.2.0-4-amd64-di_3.2.57-3+deb7u1_amd64.udeb
  nic-usb-modules-3.2.0-4-amd64-di_3.2.57-3+deb7u1_amd64.udeb
  sata-modules-3.2.0-4-amd64-di_3.2.57-3+deb7u1_amd64.udeb
  core-modules-3.2.0-4-amd64-di_3.2.57-3+deb7u1_amd64.udeb
  acpi-modules-3.2.0-4-amd64-di_3.2.57-3+deb7u1_amd64.udeb
  i2c-modules-3.2.0-4-amd64-di_3.2.57-3+deb7u1_amd64.udeb
  crc-modules-3.2.0-4-amd64-di_3.2.57-3+deb7u1_amd64.udeb
  crypto-modules-3.2.0-4-amd64-di_3.2.57-3+deb7u1_amd64.udeb
  crypto-dm-modules-3.2.0-4-amd64-di_3.2.57-3+deb7u1_amd64.udeb
  efi-modules-3.2.0-4-amd64-di_3.2.57-3+deb7u1_amd64.udeb
  ata-modules-3.2.0-4-amd64-di_3.2.57-3+deb7u1_amd64.udeb
  mmc-core-modules-3.2.0-4-amd64-di_3.2.57-3+deb7u1_amd64.udeb
  mmc-modules-3.2.0-4-amd64-di_3.2.57-3+deb7u1_amd64.udeb
  nbd-modules-3.2.0-4-amd64-di_3.2.57-3+deb7u1_amd64.udeb
  squashfs-modules-3.2.0-4-amd64-di_3.2.57-3+deb7u1_amd64.udeb
  speakup-modules-3.2.0-4-amd64-di_3.2.57-3+deb7u1_amd64.udeb
  virtio-modules-3.2.0-4-amd64-di_3.2.57-3+deb7u1_amd64.udeb
  uinput-modules-3.2.0-4-amd64-di_3.2.57-3+deb7u1_amd64.udeb
  sound-modules-3.2.0-4-amd64-di_3.2.57-3+deb7u1_amd64.udeb
  zlib-modules-3.2.0-4-amd64-di_3.2.57-3+deb7u1_amd64.udeb
  hyperv-modules-3.2.0-4-amd64-di_3.2.57-3+deb7u1_amd64.udeb
  udf-modules-3.2.0-4-amd64-di_3.2.57-3+deb7u1_amd64.udeb
  fuse-modules-3.2.0-4-amd64-di_3.2.57-3+deb7u1_amd64.udeb

Greetings,

Processed: [bts-link] source package linux

2014-05-12 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

 #
 # bts-link upstream status pull for source package linux
 # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
 #
 user bts-link-upstr...@lists.alioth.debian.org
Setting user to bts-link-upstr...@lists.alioth.debian.org (was 
bts-link-de...@lists.alioth.debian.org).
 # remote status report for #742512 (http://bugs.debian.org/742512)
 # Bug title: linux: kernel 3.13 breaks fan cooling on HP 6830S laptop
 #  * http://bugzilla.kernel.org/show_bug.cgi?id=71711
 #  * remote status changed: ASSIGNED - RESOLVED
 #  * remote resolution changed: (?) - PATCH-ALREADY-AVAILABLE
 #  * closed upstream
 tags 742512 + fixed-upstream
Bug #742512 [linux] linux: kernel 3.13 breaks fan cooling on HP 6830S laptop
Added tag(s) fixed-upstream.
 usertags 742512 - status-ASSIGNED
Usertags were: status-ASSIGNED.
Usertags are now: .
 usertags 742512 + status-RESOLVED resolution-PATCH-ALREADY-AVAILABLE
There were no usertags set.
Usertags are now: status-RESOLVED resolution-PATCH-ALREADY-AVAILABLE.
 thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
742512: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=742512
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.139991626027041.transcr...@bugs.debian.org



Processed: fixed 747166 in 3.2.57-3+deb7u1

2014-05-12 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

 fixed 747166 3.2.57-3+deb7u1
Bug #747166 [linux] CVE-2014-0196: pty layer race condition memory corruption
There is no source info for the package 'linux' at version '3.2.57-3+deb7u1' 
with architecture ''
Unable to make a source version for version '3.2.57-3+deb7u1'
Marked as fixed in versions 3.2.57-3+deb7u1.
 thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
747166: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=747166
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.139993081722146.transcr...@bugs.debian.org



Processed: fixed 747326 in 3.2.57-3+deb7u1

2014-05-12 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

 fixed 747326 3.2.57-3+deb7u1
Bug #747326 [linux] CVE-2014-3122: try_to_unmap_cluster() should lock_page() 
before mlocking
There is no source info for the package 'linux' at version '3.2.57-3+deb7u1' 
with architecture ''
Unable to make a source version for version '3.2.57-3+deb7u1'
Marked as fixed in versions 3.2.57-3+deb7u1.
 thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
747326: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=747326
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.139993082422259.transcr...@bugs.debian.org



Re: Bug#741485: xserver-xorg-video-ati: System hang at boot with kernel 3.12+ with ati 4650 and xserver-xorg-video-ati

2014-05-12 Thread Julien Cristau
Control: reassign -1 src:linux 3.14~rc5-1~exp1
Control: severity -1 important

On Mon, Mar 17, 2014 at 13:04:34 +0900, Michel Dänzer wrote:

 On Fre, 2014-03-14 at 11:50 +0200, Alex wrote:
  
  So i have 2 dmesg one is when i boot normally with 3.14rc5 which i get the
  issueof booting up but black screen a cursor and it constantly tries to fix 
  it
  self but comes back to black screen.(dmesg)
  The 2nd dmesg is with radeon.dpm=0 on kernel 3.14rc5 which it successfully
  opens with correct graphics (at least as i see it) but only with kernel 
  3.14rc5
  and not with kernels 3.13 and 3.12(dmesgnodpm)
 
 Please file an upstream bug report at
 https://bugs.freedesktop.org/enter_bug.cgi?product=DRI , component
 DRM/Radeon, and report back the resulting bug number here.
 
 
 P.S. This bug report should be reassigned to the kernel packages.
 
Doing so now.

Cheers,
Julien


signature.asc
Description: Digital signature


Processed: Re: Bug#741485: xserver-xorg-video-ati: System hang at boot with kernel 3.12+ with ati 4650 and xserver-xorg-video-ati

2014-05-12 Thread Debian Bug Tracking System
Processing control commands:

 reassign -1 src:linux 3.14~rc5-1~exp1
Bug #741485 [src:xserver-xorg-video-ati] xserver-xorg-video-ati: System hang at 
boot with kernel 3.12+ with ati 4650 and xserver-xorg-video-ati
Bug reassigned from package 'src:xserver-xorg-video-ati' to 'src:linux'.
No longer marked as found in versions xserver-xorg-video-ati/current and 
xserver-xorg-video-ati/1:7.3.0-1.
Ignoring request to alter fixed versions of bug #741485 to the same values 
previously set
Bug #741485 [src:linux] xserver-xorg-video-ati: System hang at boot with kernel 
3.12+ with ati 4650 and xserver-xorg-video-ati
Marked as found in versions linux/3.14~rc5-1~exp1.
 severity -1 important
Bug #741485 [src:linux] xserver-xorg-video-ati: System hang at boot with kernel 
3.12+ with ati 4650 and xserver-xorg-video-ati
Severity set to 'important' from 'critical'

-- 
741485: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=741485
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.b741485.13999388574025.transcr...@bugs.debian.org



Bug#747922: kernel hang during boot on s390x in a virtual machine under z/VM when logged on to a terminal

2014-05-12 Thread Stephen Powell
Package: linux
Version: 3.10.1-1
Severity: normal

I have discovered a bug in the Linux kernel.
This bug only occurs for the s390x port, only
when running in a virtual machine under z/VM, only with conmode=3215,
and only when the virtual machine is logged on to a 3270 terminal (not
disconnected).  I am using TERM=dumb as a kernel boot parameter, and
the console definition in /etc/inittab looks like this:

   T0:23:respawn:/sbin/getty -L --noclear ttyS0 9600 dumb

The problem is that the kernel hangs during boot.  The last message
displayed on the console during boot before the hang varies.  One
common freeze point for the 3.13 kernel is

   PID hash table entries: 2048 (order: 2, 16384 bytes)

Pressing the Enter key a couple of times gets it going again.  Pressing
it once puts the virtual machine into a VM READ state.  Pressing it
the second time causes console output to resume.  However, due to
buffering, I don't think the above message is indicative of where the
kernel actually is in its processing.  Many of the messages have time
stamps on them.  By comparing the time stamps, I can tell where the
long pause actually was.  In a recent boot, for example, I saw the
following sequence of messages:

-

               Begin: Loading essential drivers ... done.
               Begin: Running /scripts/init-premount ... done.
               Begin: Mounting root file system ...
               Begin: Running /scripts/local-top ... done.
               Begin: Running /scripts/local-premount ...
[    1.973615] PM: Starting manual resume from disk
               done.
[    1.999199] EXT4-fs (dasdc1): mounting ext3 file system using the ext4 
subsystem
[    2.042526] EXT4-fs (dasdc1): mounted filesystem with ordered data mode. 
Opts: (null)
               Begin: Running /scripts/local-bottom ... done.
               done.
               Begin: Running /scripts/init-bottom ... done.

               INIT: version 2.88 booting


               Using makefile-style concurrent boot in runlevel S.

               Starting the hotplug events dispatcher: udevd.

               Synthesizing the initial hotplug events...
[  164.525332] systemd-udevd[277]: starting version 204
               done.

               Waiting for /dev to be fully populated...

-

(I have reformatted the above messages so that messages without a timestamp
prefix and messages with a timestamp prefix line up starting with the main
message text.)  As you can see, there is a huge time gap between 2.042526
and 164.525332.  That is where it was hung, waiting for me to press the
Enter key.  It is somewhere between mounting the permanent root file system
read only and starting the second instance of the udev daemon.  (The first
instance of the udev daemon starts shortly after mounting the initial RAM
file system.)

By bisecting the kernel using official Debian kernel image packages only,
it appears that the problem exists between 3.9.8-1 and 3.10.1-1.  That is,

   linux-image-3.9-1-s390x_3.9.8-1_s390x.deb     works, and
   linux-image-3.10-1-s390x_3.10.1-1_s390x.deb   fails.

And every version I have tried since 3.10.1-1 fails also.
It should be noted that a kernel which fails does not always fail.
Sometimes it does not hang.  But it hangs the majority of the time.
If the virtual machine is disconnected, that is, not logged on to a
real terminal, it seems to always boot fine, whether the virtual
machine has a SECUSER or not.  When logged on to a terminal, the chances
of failure are increased if the kernel is explicitly selected from the
boot menu, such as with

   #CP VINPUT VMSG 1

as opposed to letting a timeout occur and letting the default kernel
boot via a timeout.  I don't know why that matters, but that has been
my experience.


I will be more than happy to assist in debugging this.

-- 
  .''`. Stephen Powell
 : :'  :
 `. `'`
   `-


--
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/299380321.1225525.1399939304318.javamail.r...@md01.wow.synacor.com



Bug#747929: fail to boot btrfs rootfs

2014-05-12 Thread Jesse Sung

Package: src:linux
Version: 3.14.2-1
Severity: important

Dear Maintainer,

After having upgraded to 3.14.2-1, system fails to boot with a btrfs 
root. It complains about unable to load btrfs.ko due to unknown symbols.


Comparing the depends of btrfs.ko in 3.13 and 3.14:
% sudo modinfo /lib/modules/3.13-1-amd64/kernel/fs/btrfs/btrfs.ko
filename:   /lib/modules/3.13-1-amd64/kernel/fs/btrfs/btrfs.ko
license:GPL
alias:  devname:btrfs-control
alias:  char-major-10-234
alias:  fs-btrfs
depends:libcrc32c,raid6_pq,xor
intree: Y
vermagic:   3.13-1-amd64 SMP mod_unload modversions

% sudo modinfo /lib/modules/3.14-1-amd64/kernel/fs/btrfs/btrfs.ko
filename:   /lib/modules/3.14-1-amd64/kernel/fs/btrfs/btrfs.ko
license:GPL
alias:  devname:btrfs-control
alias:  char-major-10-234
alias:  fs-btrfs
depends:raid6_pq,xor
intree: Y
vermagic:   3.14-1-amd64 SMP mod_unload modversions

By adding libcrc32c to /etc/initramfs-tools/modules, system boots again.

Regards,
Jesse


--
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/537192e8.3070...@cola.voip.idv.tw



Bug#747257: linux-image-3.2.0-4-amd64: Wheezy kernel update in 7.5 won't resume from suspend correctly

2014-05-12 Thread Jaimos Skriletz
In the recent linux security DSA it appears the issue has been found,

This update also fixes a regression in the isci
driver and suspend problems with certain AMD CPUs (introduced in the
updated kernel from the Wheezy 7.5 point release).
​

I have installed the newest kernel and my few tests pm-suspend and resume
is working as it was before the point release.

jaimos


Processed: Re: Bug#747927: qemu-utils: qemu-nbd blocks

2014-05-12 Thread Debian Bug Tracking System
Processing control commands:

 reassign -1 linux-image-3.13-1-amd64 3.13.10-1
Bug #747927 [qemu-utils] qemu-utils: qemu-nbd blocks
Bug reassigned from package 'qemu-utils' to 'linux-image-3.13-1-amd64'.
No longer marked as found in versions qemu/2.0.0+dfsg-4.
Ignoring request to alter fixed versions of bug #747927 to the same values 
previously set
Bug #747927 [linux-image-3.13-1-amd64] qemu-utils: qemu-nbd blocks
Marked as found in versions linux/3.13.10-1.

-- 
747927: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=747927
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.b747927.13999572155954.transcr...@bugs.debian.org