Bug#808038: Same problem with RC8

[Hugo Peixoto]

I fixed the problem by adding the nvme module to initramfs.
Using a working kernel, edit /etc/initramfs-tools/modules, and run
update-initramfs.

Source: https://lists.debian.org/debian-kernel/2015/12/msg00023.html

Hugo Peixoto

Bug#808038: Re: Bug#808038: Same problem with RC8

[Hugo Peixoto]

Alexandre,

I also have that happening to me, but it doesn't seem to happen every time.
I'm not sure what the problem is, but it may be related to the video
drivers.

When i disabled modeset on the kernel, it seemed to stop happening,
but that makes X unusable, as far as I can tell.

I saw some attempts at solving the problem, but haven't tried them yet.
I can't seem to find the reference to those attempts, but you can try to
search
for it on the web. For example:
https://wiki.archlinux.org/index.php/Intel_graphics#Blank_screen_during_boot.2C_when_.22Loading_modules.22



Hugo Peixoto
--

http://hugopeixoto.net

On Wed, Jan 6, 2016 at 10:47 AM, Alexandre Russo 
wrote:

> Thank you Hugo,
>
> i confirm that when i enabled «nvme» module in initramfs-tools/modules I
> have no error messages and Luks ask me my password.
>
> But once i entered i have a black screen and I can't do anything.
>
> My laptop don't boot and i must press power button to turn off and reboot
> on kernel 4-3...
>
> I don't know if it's a kernel problem or other problem but i don't know
> where i can found related logs.
>
> Thank you.
>

Bug#810085: Please enable CONFIG_GPIO_SYSFS on x86/am64

[Sjoerd Simons]

Source: linux
Severity: wishlist

Hey,

In current debian kernels CONFIG_GPIO_SYSFS is only set for ARM kernels. This
options allows userspace to directly tinker with GPIO (if they're not bound
by a driver). Which is quite useful on development boards with GPIO extension
headers to tinker with electronics without having to write a full kernel
driver.

With the appearance of embedded/development based on Intel chips like e.g.
the Minnowboard, this is also useful on x86/amd64. (Actually if you use
some of the Minnowboard howto's/tutorials it's the suggested way for playing
with GPIO there).

So as the subject says, please enable CONFIG_GPIO_SYSFS on at least the x86
architectures as well. Though it might be useful to generally enable it (e.g.
at least mips has some devboards as well, probably others too).

-- System Information:
Debian Release: stretch/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'stable'), (101, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386, armhf, armel

Kernel: Linux 4.3.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Bug#808038: Re: Bug#808038: Same problem with RC8

[Alexandre Russo]

Thank you Hugo,

i confirm that when i enabled «nvme» module in initramfs-tools/modules 
I have no error messages and Luks ask me my password.

But once i entered i have a black screen and I can't do anything.

My laptop don't boot and i must press power button to turn off and
reboot on kernel 4-3...

I don't know if it's a kernel problem or other problem but i don't know
where i can found related logs. 

Thank you. 

Bug#808973: system freeze after kernel security update

[Martin Preen]

On Sat, 26 Dec 2015 19:13:31 +0100 Martin Preen 
 wrote:

I do have the same problem.

Wheezy updates with kernel upodate 3.2.73-2+deb7u1 freezes
my radeon systems.


Kernel update 3.2.73-2+deb7u2 solves the problem for me.

Thanks.
Martin



smime.p7s
Description: S/MIME Cryptographic Signature

Bug#809476: Linux 4.4-rc6 fails to boot on QNAP TS-109

[Roger Shimizu]

[Resend previous email to keep ARM experts in CC]

On Thu, Dec 31, 2015 at 9:09 AM, Martin Michlmayr  wrote:
> I tried to boot Debian's 4.4-rc6 kernel on my QNAP TS-109 and it failed
> to boot with:
> [   19.380002] Unpacking initramfs...
> [   19.380044] Initramfs unpacking failed: junk in compressed archive

I see this error message on my Linkstation boxes for long time, but
most of time they just boot fine.
After seeing your report, now I understand the root cause why failing
sometimes. :-)

> -U-Boot-Kernel-Address: 0x8000
> +U-Boot-Kernel-Address: 0x00c08000

I tried this on local db (/etc/flash-kernel/db) of my Linkstation, but
it failed to boot.
Except above change, did you also changed the address in uboot
command? (like a few lines below)

>> cp.b 0xff20 0x80 0x3f
>> setenv bootargs console=ttyS0,115200n8 root=/dev/ram rw 
>> initrd=0x80,0x3f
>> bootm 0xff00

> u-boot loads it like this:
>
> ## Booting image at 0040 ...
>Load Address: 8000
>Entry Point:  8000

I also don't understand where the address "0040" comes from. It's
neither in flash-kernel's db nor in uboot setting.
>From my understanding, the kernel image stores in flash, which address
is 0xff00, and it will be copied to "8000" by uboot on boot
time, then kernel will uncompress the image and then boot. Am I missed
something?

What I intend to do is following your QNAP's way to fix things on Linkstation.
Any clue would be appreciated. Thank you!

Cheers,
Roger

Bug#809815: [feature request] linux-image-4.3.0-1-sparc64-smp: tpm random module for linux LDOMs

[Anatoly Pugachev]

On Wed, Jan 6, 2016 at 5:24 AM, Ben Hutchings  wrote:
> Control: tag -1 moreinfo
>
> On Mon, 2016-01-04 at 13:48 +0300, Anatoly Pugachev wrote:
>> Package: src:linux
>> Version: 4.3.3-2
>> Severity: wishlist
>>
>> Dear Maintainer,
>>
>> Can you please enable CONFIG_TCG_TPM (TPM security chip) and
>> CONFIG_HW_RANDOM_TPM linux kernel config options (as modules), to
>> enable hardware RNG device for use in LDOM (containers) of debian
>> sparc64.
>>
>> Right now, there's no hardware RNG provider is available :
> [...]
>
> Both of those are generic TPM code and won't help you without a driver
> for the specific TPM that's present in LDOMs.
>
> I can't find any hint in the kernel source of which driver is needed
> for an LDOM, even in the UEK patched source, so perhaps it is out-of-
> tree?

Ben, well,

I'm going to build a generic (vanilla) kernel with this CONFIGs and
test how it would work. Going to report back soon. Thanks.

Bug#808973: system freeze after kernel security update

[tmueller890]

kernel 3.2.73-2+deb7u2 solves the issue for me too. Thanks for the fast 
response.

Bug#809430: marked as done (Subject: linux-image-4.3.0-1-amd64: USB wireless adapter causes xhci errors when plugged in)

[Debian Bug Tracking System]

Your message dated Wed, 06 Jan 2016 16:43:01 +
with message-id <1452098581.2768.119.ca...@decadent.org.uk>
and subject line Re: Bug#809430: Subject: linux-image-4.3.0-1-amd64: USB 
wireless adapter causes xhci errors when plugged in
has caused the Debian Bug report #809430,
regarding Subject: linux-image-4.3.0-1-amd64: USB wireless adapter causes xhci 
errors when plugged in
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.)


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


Package: src:linux
Version: 4.3.3-2
Severity: normal

Dear Maintainer,

(Sorry if I'm doing this wrong. It's my first bug report, and my third
attempt at filing it. Also, I couldn't get reportbug to work with any
mail server I tried, so this is a copy of its output.)

   * What led up to the situation?

   I dist-upgraded my Testing system yesterday morning, and this
   included the 4.3 kernel. When I rebooted, my USB wireless adapter
   (RNX-N180UBE) was no longer recognized.

   * What exactly did you do (or not do) that was effective (or
 ineffective)?

   First, I unplugged the adapter and plugged it back in. This did
   nothing: the light on the adapter started blinking, but it still
   wasn't recognized. Changing ports made no difference.

   Next, I tried a different adapter, a TP-Link TL-WN722N, and this had 
the same result. Checking the logs, I found a similar string of error 
messages with this adapter as with the other.


   I also tried inserting a USB flash drive. This was recognized and
   automounted, and I could browse it in Dolphin. I then unmounted it
   without any problems.  I didn't attempt any file transfers with it,
   however.

   After that, I rebooted to the older kernel (4.2.6). The original
   adapter works fine under this version.

   * What was the outcome of this action?

   Booting with the 4.3.3 kernel caused both wireless adapters to stop
   working, producing a number of xhci errors at boot or when plugged
   in. Both adapters worked with 4.2.6.

   * What outcome did you expect instead?

   I expected the adapters to continue working after the upgrade.

I'm currently running 4.2.6, as I need to use this computer for daily
tasks, and I have no Internet access with 4.3. (I'm too far away for a
wired connection.) I can reboot to 4.3 to gather more information, but
that will have to be when I'm not using it for anything else.

Below are what I think are the relevant parts of the logs from one
attempt at plugging in the first adapter a few minutes after boot. The
messages during boot or with the other adapter are similar. Only the
timestamps and addresses are different.

Thank you,
Michael

/var/log/messages:

12/29/15 05:26:20 AM	momikey	kernel	[ 1166.524325] usb 3-1: new 
high-speed USB device number 4 using xhci_hcd
12/29/15 05:26:20 AM	momikey	kernel	[ 1166.656042] usb 3-1: New USB 
device found, idVendor=0bda, idProduct=8172
12/29/15 05:26:20 AM	momikey	kernel	[ 1166.656050] usb 3-1: New USB 
device strings: Mfr=1, Product=2, SerialNumber=3
12/29/15 05:26:20 AM	momikey	kernel	[ 1166.656054] usb 3-1: Product: 
RNX-180UBE
12/29/15 05:26:20 AM	momikey	kernel	[ 1166.656058] usb 3-1: 
Manufacturer: Manufacturer Realtek
12/29/15 05:26:20 AM	momikey	kernel	[ 1166.656061] usb 3-1: 
SerialNumber: 00e04c01
12/29/15 05:26:20 AM	momikey	kernel	[ 1166.657440] r8712u: register 
rtl8712_netdev_ops to netdev_ops
12/29/15 05:26:20 AM	momikey	kernel	[ 1166.657450] usb 3-1: r8712u: 
USB_SPEED_HIGH with 4 endpoints
12/29/15 05:26:20 AM	momikey	kernel	[ 1166.658253] usb 3-1: r8712u: Boot 
from EFUSE: Autoload OK
12/29/15 05:26:21 AM	momikey	kernel	[ 1167.696504] usb 3-1: r8712u: 
CustomerID = 0x
12/29/15 05:26:21 AM	momikey	kernel	[ 1167.696511] usb 3-1: r8712u: MAC 
Address from efuse = 68:1c:a2:04:7e:4b
12/29/15 05:26:21 AM	momikey	kernel	[ 1167.696515] usb 3-1: r8712u: 
Loading firmware from "rtlwifi/rtl8712u.bin"
12/29/15 05:26:21 AM	momikey	kernel	[ 1167.696809] usb 3-1: firmware: 
direct-loading firmware rtlwifi/rtl8712u.bin
12/29/15 05:26:21 AM	momikey	mtp-probe	checking bus 3, device 4: 
"/sys/devices/pci:00/:00:10.1/usb3/3-1"
12/29/15 05:26:21 AM	momikey	mtp-probe	bus: 3, device: 4 was not an MTP 
device
12/29/15 05:26:22 AM	momikey	kernel	[ 1168.725366] IPv6: 
ADDRCONF(NETDEV_UP): wlan0: link is not ready
12/29/15 05:26:23 AM	momikey	kernel	[ 1169.444041] r8712u 3-1:1.0 wlan0: 
1 RCR=0x153f00e
12/29/15 05:26:23 AM	momikey	kernel	[ 1169.445282] r8712u 3-1:1.0 wlan0: 
2 RCR=0x553f00e
12/29/15 05:26:23 AM	

Bug#810121: linux: KVM guests randomly get I/O errors on VirtIO based devices

[Jordi Mallach]

Source: linux
Version: 3.16.7-ckt11-1+deb8u5
Severity: important

Hi kernel maintainers,

We've been seeing a strange bug in KVM guests hosted by a Debian jessie box 
(running 3.16.7-ckt11-1+deb8u5),

Basically, we are getting random VirtIO errors inside our guests, resulting in 
stuff like this

[4735406.568235] blk_update_request: I/O error, dev vda, sector 142339584
[4735406.572008] EXT4-fs warning (device dm-0): ext4_end_bio:317: I/O error -5 
writing to inode 1184437 (offset 0 size 208896 starting block 17729472)
[4735406.572008] Buffer I/O error on device dm-0, logical block 17729472
[ ... ]
[4735406.572008] Buffer I/O error on device dm-0, logical block 17729481
[4735406.643486] blk_update_request: I/O error, dev vda, sector 142356480
[ ... ]
[4735406.748456] blk_update_request: I/O error, dev vda, sector 38587480
[4735411.020309] Buffer I/O error on dev dm-0, logical block 12640808, lost 
sync page write
[4735411.055184] Aborting journal on device dm-0-8.
[4735411.056148] Buffer I/O error on dev dm-0, logical block 12615680, lost 
sync page write
[4735411.057626] JBD2: Error -5 detected when updating journal superblock for 
dm-0-8.
[4735411.057936] Buffer I/O error on dev dm-0, logical block 0, lost sync page 
write
[4735411.057946] EXT4-fs error (device dm-0): ext4_journal_check_start:56: 
Detected aborted journal
[4735411.057948] EXT4-fs (dm-0): Remounting filesystem read-only
[4735411.057949] EXT4-fs (dm-0): previous I/O error to superblock detected

(From an Ubuntu 15.04 guest, EXT4 on LVM2)

Or,

Jan 06 03:39:11 titanium kernel: end_request: I/O error, dev vda, sector 
1592467904
Jan 06 03:39:11 titanium kernel: EXT4-fs warning (device vda3): 
ext4_end_bio:317: I/O error -5 writing to inode 31169653 (offset 0 size 0 
starting block 199058492)
Jan 06 03:39:11 titanium kernel: Buffer I/O error on device vda3, logical block 
198899256
[...]
Jan 06 03:39:12 titanium kernel: Aborting journal on device vda3-8.
Jan 06 03:39:12 titanium kernel: Buffer I/O error on device vda3, logical block 
99647488

(From a Debian jessie guest, EXT4 directly on a VirtIO-based block device)

When this happens, it affects multiple guests on the hosts at the same time.
Normally they are severe enough that they end up with a r/o file system, but
we've seen a few hosts survive with a non-fatal I/O error. The host's dmesg has
nothing interesting to see.

We've seen this happen with quite heterogeneous guests:

- Debian 6, 7 and 8 (Debian kernels 2.6.32, 3.2 and 3.16)
- Ubuntu 14.09 and 15.04 (Ubuntu kernels)
- 32 bit and 64 bit installs.

In short, we haven't seen a clear characteristic in any guest, other than the
affected hosts being the ones with some sustained I/O load (build machines,
cgit servers, PostgreSQL RDBMs...). Most of the times, hosts that just sit
there doing nothing with their disks are not affected.

The host is a stock Debian jessie install that manages libvirt-based QEMU
guests. All the guests have their block devices using virtio drivers, some of
them on spinning media based on LSI RAID (was a 3ware card before, got replaced
as we were very suspicious about it, but are getting the same results), and
some of them based on PCIe SSD storage. We have some other 3 hosts, similar
setup except they run Debian wheezy (and honestly we're not too keen on
upgrading them yet, just in case), none of them has ever shown this kind of
problem

We've been seeing this since last summer, and haven't found a pattern that
tells us where these I/O error bugs are coming from. Google isn't revealing
other people with a similar problem, and we're finding that quite surprising as
our setup is quite basic.

Thanks,
Jordi

Bug#809430: Subject: linux-image-4.3.0-1-amd64: USB wireless adapter causes xhci errors when plugged in

[Michael Potter]

I saw that 4.3.3-5 landed in Testing, so I upgraded. After the reboot, 
there were no more xhci error messages. The adapter shows up just fine 
in plasma-nm, and I ran a few speed tests to generate traffic. 
Everything's looking good, and it seems like this update fixed the problem.


Thanks again,
Michael Potter

Bug#808374: marked as done (linux-image-3.16.0-4-686-pae: FreeRADIUS EAP-TLS stopped working when kernel was updated)

[Debian Bug Tracking System]

Your message dated Wed, 06 Jan 2016 22:24:56 +
with message-id 
and subject line Bug#808293: fixed in linux 3.2.73-2+deb7u2
has caused the Debian Bug report #808293,
regarding linux-image-3.16.0-4-686-pae: FreeRADIUS EAP-TLS stopped working when 
kernel was updated
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.)


-- 
808293: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=808293
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:linux
Version: 3.16.7-ckt20-1+deb8u1
Severity: important

Dear Maintainer,

After updating the kernel with the latest security release FreeRADIUS
seem to be unable to process the UDP packets it is receiving.  As you
can see in this strace there's some error occuring with the recvfrom()
that is triggered by the incoming packet.  Downgrading the kernel to
linux-image-3.16.0-4-686-pae:i386 3.16.7-ckt11-1+deb8u6 makes it work
again.

This is a i686 domU on a X86_64 XEN host if that matters.


When using current kernel:

execve("/usr/sbin/freeradius", ["freeradius", "-s"], [/* 21 vars */]) = 0
brk(0)  = 0x9e47000
access("/etc/ld.so.nohwcap", F_OK)  = -1 ENOENT (No such file or
directory)
mmap2(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1,
0) = 0xb77c5000
mmap2(NULL, 12288, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1,
0) = 0xb77c2000
[...]
select(10, [4 6 7 8 9], NULL, NULL, NULL) = 1 (in [6])
recvfrom(6, 0xbf9909c8, 4, 2, 0xbf990948, 0xbf990944) = -1 EAGAIN
(Resource temporarily unavailable)
select(10, [4 6 7 8 9], NULL, NULL, NULL) = 1 (in [6])
recvfrom(6, 0xbf9909c8, 4, 2, 0xbf990948, 0xbf990944) = -1 EAGAIN
(Resource temporarily unavailable)
select(10, [4 6 7 8 9], NULL, NULL, NULL) = 1 (in [6])
recvfrom(6, 0xbf9909c8, 4, 2, 0xbf990948, 0xbf990944) = -1 EAGAIN
(Resource temporarily unavailable)
select(10, [4 6 7 8 9], NULL, NULL, NULL) = ? ERESTARTNOHAND (To be
restarted if no handler)
--- SIGINT {si_signo=SIGINT, si_code=SI_KERNEL,
si_value={int=1851877730, ptr=0x6e616962}} ---
exit_group(2)   = ?
+++ exited with 2 +++

When using the linux-image-3.16.0-4-686-pae:i386 3.16.7-ckt11-1+deb8u6
kernel - which is working:

select(10, [4 6 7 8 9], NULL, NULL, NULL) = 1 (in [6])
recvfrom(6, "\1\f\0\244", 4, MSG_PEEK, {sa_family=AF_INET,
sin_port=htons(39163), sin_addr=inet_addr("192.168.20.25")}, [16]) = 4
getsockname(6, {sa_family=AF_INET, sin_port=htons(1812),
sin_addr=inet_addr("0.0.0.0")}, [16]) = 0
recvfrom(6, "\1\f\0\244", 4, MSG_PEEK, {sa_family=AF_INET,
sin_port=htons(39163), sin_addr=inet_addr("192.168.20.25")}, [16]) = 4
getsockname(6, {sa_family=AF_INET, sin_port=htons(1812),
sin_addr=inet_addr("0.0.0.0")}, [16]) = 0
recvmsg(6, {msg_name(16)={sa_family=AF_INET, sin_port=htons(39163),
sin_addr=inet_addr("192.168.20.25")},
msg_iov(1)=[{"\1\f\0\244_\7\317Y\232\343U\306\6
\\\312\31\2775\315\1\10nobody\4\6\300\250"..., 164}], msg_controllen=24,
{cmsg_len=24, cmsg_level=SOL_IP, cmsg_type=, ...}, msg_flags=0}, 0) = 164

I don't have any clue as to what change has caused the problem though..

/Andreas Sundstrom


-- Package-specific info:
** Version:
Linux version 3.16.0-4-686-pae (debian-kernel@lists.debian.org) (gcc
version 4.8.4 (Debian 4.8.4-1) ) #1 SMP Debian 3.16.7-ckt20-1+deb8u1
(2015-12-14)

** Command line:
root=UUID=4692e988-b453-4884-bbf0-43c29565b821 ro  quiet

** Not tainted

** Kernel log:
[1.558784] xenbus_probe_frontend: Device with no driver:
device/vbd/51760
[1.558785] xenbus_probe_frontend: Device with no driver:
device/vbd/51776
[1.558786] xenbus_probe_frontend: Device with no driver:
device/vbd/51792
[1.558787] xenbus_probe_frontend: Device with no driver:
device/vbd/51808
[1.558788] xenbus_probe_frontend: Device with no driver:
device/vbd/51824
[1.558789] xenbus_probe_frontend: Device with no driver:
device/vbd/51840
[1.558790] xenbus_probe_frontend: Device with no driver:
device/vbd/51856
[1.558791] xenbus_probe_frontend: Device with no driver: device/vif/0
[1.558871] rtc_hctosys: unable to open rtc device (rtc0)
[1.558896] PM: Hibernation image not present or could not be loaded.
[1.559264] Freeing unused kernel memory: 656K (c1671000 - c1715000)
[1.560167] Write protecting the kernel text: 4612k
[1.560455] Write protecting the kernel read-only data: 1456k
[1.560457] NX-protecting the kernel data: 3580k
[1.579136] systemd-udevd[63]: starting version 215
[1.579513] random: systemd-udevd urandom read with 16 bits of
entropy available
[1.591625] 

Bug#808431: marked as done (linux-source-3.16: FreeRADIUS stopped working when kernel was updated to 3.16.7-ckt20)

[Debian Bug Tracking System]

Your message dated Wed, 06 Jan 2016 22:24:56 +
with message-id 
and subject line Bug#808293: fixed in linux 3.2.73-2+deb7u2
has caused the Debian Bug report #808293,
regarding linux-source-3.16: FreeRADIUS stopped working when kernel was updated 
to 3.16.7-ckt20
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.)


-- 
808293: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=808293
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: linux-source-3.16
Version: 3.16.7-ckt-20
Severity: important

Dear Maintainer,

*** Reporter, please consider answering these questions, where appropriate ***

   * What led up to the situation?
Upgrading the Kernel from 3.16.7-ckt11 to 3.16.7-ckt20 (compiled from
source each) broke FreeRADIUS. The freeradius daemon stopped responding to udp
auth queries from locally installed hostapd wifi daemon. Wifi clients using
EAP-TLS auth cannot authenticate an more.


   * What exactly did you do (or not do) that was effective (or
 ineffective)?
Downgrade to Kernel 3.16.7-ckt11 fixed the issue.

   * What was the outcome of this action?
   * What outcome did you expect instead?

*** End of the template - remove these template lines ***



-- System Information:
Debian Release: 8.2
  APT prefers stable
  APT policy: (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.16.0-4-amd64 (SMP w/2 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
--- End Message ---
--- Begin Message ---
Source: linux
Source-Version: 3.2.73-2+deb7u2

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 808...@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: Sat, 02 Jan 2016 03:31:22 +
Source: linux
Binary: linux-source-3.2 linux-doc-3.2 linux-manual-3.2 linux-support-3.2.0-4 
linux-libc-dev linux-headers-3.2.0-4-all linux-headers-3.2.0-4-all-alpha 
linux-headers-3.2.0-4-common linux-image-3.2.0-4-alpha-generic 
linux-headers-3.2.0-4-alpha-generic linux-image-3.2.0-4-alpha-smp 
linux-headers-3.2.0-4-alpha-smp linux-image-3.2.0-4-alpha-legacy 
linux-headers-3.2.0-4-alpha-legacy linux-headers-3.2.0-4-all-amd64 
kernel-image-3.2.0-4-amd64-di nic-modules-3.2.0-4-amd64-di 
nic-extra-modules-3.2.0-4-amd64-di nic-wireless-modules-3.2.0-4-amd64-di 
nic-shared-modules-3.2.0-4-amd64-di serial-modules-3.2.0-4-amd64-di 
usb-serial-modules-3.2.0-4-amd64-di ppp-modules-3.2.0-4-amd64-di 
pata-modules-3.2.0-4-amd64-di cdrom-core-modules-3.2.0-4-amd64-di 
firewire-core-modules-3.2.0-4-amd64-di scsi-core-modules-3.2.0-4-amd64-di 
scsi-modules-3.2.0-4-amd64-di scsi-common-modules-3.2.0-4-amd64-di 
scsi-extra-modules-3.2.0-4-amd64-di plip-modules-3.2.0-4-amd64-di 
floppy-modules-3.2.0-4-amd64-di
 loop-modules-3.2.0-4-amd64-di btrfs-modules-3.2.0-4-amd64-di 
ext2-modules-3.2.0-4-amd64-di ext3-modules-3.2.0-4-amd64-di 
ext4-modules-3.2.0-4-amd64-di isofs-modules-3.2.0-4-amd64-di 
jfs-modules-3.2.0-4-amd64-di ntfs-modules-3.2.0-4-amd64-di 
reiserfs-modules-3.2.0-4-amd64-di xfs-modules-3.2.0-4-amd64-di 
fat-modules-3.2.0-4-amd64-di ufs-modules-3.2.0-4-amd64-di 
qnx4-modules-3.2.0-4-amd64-di md-modules-3.2.0-4-amd64-di 
multipath-modules-3.2.0-4-amd64-di usb-modules-3.2.0-4-amd64-di 
usb-storage-modules-3.2.0-4-amd64-di pcmcia-storage-modules-3.2.0-4-amd64-di 
fb-modules-3.2.0-4-amd64-di input-modules-3.2.0-4-amd64-di 
event-modules-3.2.0-4-amd64-di mouse-modules-3.2.0-4-amd64-di 
irda-modules-3.2.0-4-amd64-di parport-modules-3.2.0-4-amd64-di 
nic-pcmcia-modules-3.2.0-4-amd64-di pcmcia-modules-3.2.0-4-amd64-di 
nic-usb-modules-3.2.0-4-amd64-di sata-modules-3.2.0-4-amd64-di 
core-modules-3.2.0-4-amd64-di acpi-modules-3.2.0-4-amd64-di 
i2c-modules-3.2.0-4-amd64-di
 crc-modules-3.2.0-4-amd64-di crypto-modules-3.2.0-4-amd64-di 

Bug#808293: marked as done (Regression in short UDP reads caused by "net: Fix skb csum races when peeking")

[Debian Bug Tracking System]

Your message dated Wed, 06 Jan 2016 22:24:56 +
with message-id 
and subject line Bug#808293: fixed in linux 3.2.73-2+deb7u2
has caused the Debian Bug report #808293,
regarding Regression in short UDP reads caused by "net: Fix skb csum races when 
peeking"
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.)


-- 
808293: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=808293
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: freeradius
Version: 2.1.12+dfsg-1.2
Severity: grave
Tags: upstream
Justification: renders package unusable

Dear Maintainer,

I just upgraded libc and kernel image:
# tail /var/log/apt/history.log

Start-Date: 2015-12-18  09:22:57
Commandline: apt-get upgrade -y
Upgrade: linux-libc-dev:i386 (3.2.68-1+deb7u6, 3.2.73-2+deb7u1), 
linux-image-3.2.0-4-686-pae:i386 (3.2.68-1+deb7u6, 3.2.73-2+deb7u1)
End-Date: 2015-12-18  09:23:15

Start-Date: 2015-12-18  10:30:59
Commandline: apt-get install strace
Install: strace:i386 (4.5.20-2.3)
End-Date: 2015-12-18  10:31:04

After reboot, I noticed that freeradius stopped processing requests.
This is freeradius -X output:
# freeradius -X
FreeRADIUS Version 2.1.12, for host i486-pc-linux-gnu, built on Dec 16 2012 at 
22:03:33
Copyright (C) 1999-2009 The FreeRADIUS server project and contributors.
There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A
PARTICULAR PURPOSE.
You may redistribute copies of FreeRADIUS under the terms of the
GNU General Public License v2.
Starting - reading configuration files ...
including configuration file /etc/freeradius/radiusd.conf
including configuration file /etc/freeradius/proxy.conf
including configuration file /etc/freeradius/clients.conf
including files in directory /etc/freeradius/modules/
including configuration file /etc/freeradius/modules/preprocess
including configuration file /etc/freeradius/modules/redis
including configuration file /etc/freeradius/modules/ippool
including configuration file /etc/freeradius/modules/expiration
including configuration file /etc/freeradius/modules/detail.log
including configuration file /etc/freeradius/modules/expr
including configuration file /etc/freeradius/modules/digest
including configuration file /etc/freeradius/modules/files
including configuration file /etc/freeradius/modules/attr_filter
including configuration file /etc/freeradius/modules/linelog
including configuration file /etc/freeradius/modules/echo
including configuration file /etc/freeradius/modules/detail.example.com
including configuration file /etc/freeradius/modules/chap
including configuration file /etc/freeradius/modules/soh
including configuration file /etc/freeradius/modules/passwd
including configuration file /etc/freeradius/modules/rediswho
including configuration file /etc/freeradius/modules/dynamic_clients
including configuration file /etc/freeradius/modules/checkval
including configuration file /etc/freeradius/modules/mschap
including configuration file /etc/freeradius/modules/acct_unique
including configuration file /etc/freeradius/modules/perl
including configuration file /etc/freeradius/modules/detail
including configuration file /etc/freeradius/modules/attr_rewrite
including configuration file /etc/freeradius/modules/sql_log
including configuration file /etc/freeradius/modules/replicate
including configuration file /etc/freeradius/modules/smbpasswd
including configuration file /etc/freeradius/modules/mac2ip
including configuration file /etc/freeradius/modules/etc_group
including configuration file /etc/freeradius/modules/pam
including configuration file /etc/freeradius/modules/mac2vlan
including configuration file /etc/freeradius/modules/unix
including configuration file /etc/freeradius/modules/policy
including configuration file /etc/freeradius/modules/always
including configuration file /etc/freeradius/modules/exec
including configuration file /etc/freeradius/modules/pap
including configuration file /etc/freeradius/modules/opendirectory
including configuration file /etc/freeradius/modules/counter
including configuration file /etc/freeradius/modules/ldap
including configuration file /etc/freeradius/modules/ntlm_auth
including configuration file /etc/freeradius/modules/realm
including configuration file /etc/freeradius/modules/smsotp
including configuration file /etc/freeradius/modules/cui
including configuration file /etc/freeradius/modules/radutmp
including configuration file /etc/freeradius/modules/krb5
including configuration file /etc/freeradius/modules/wimax
including configuration file /etc/freeradius/modules/inner-eap

Processing of linux_3.2.73-2+deb7u2~bpo60+1_multi.changes

[Debian FTP Masters]

linux_3.2.73-2+deb7u2~bpo60+1_multi.changes uploaded successfully to localhost
along with the files:
  linux_3.2.73-2+deb7u2~bpo60+1.dsc
  linux_3.2.73-2+deb7u2~bpo60+1.debian.tar.xz
  linux-doc-3.2_3.2.73-2+deb7u2~bpo60+1_all.deb
  linux-support-3.2.0-0.bpo.4_3.2.73-2+deb7u2~bpo60+1_all.deb
  linux-manual-3.2_3.2.73-2+deb7u2~bpo60+1_all.deb
  linux-source-3.2_3.2.73-2+deb7u2~bpo60+1_all.deb

Greetings,

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

linux_3.2.73-2+deb7u2~bpo60+1_multi.changes ACCEPTED into squeeze-backports->backports-policy

[Debian FTP Masters]

Accepted:

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 03 Jan 2016 02:04:37 +
Source: linux
Binary: linux-source-3.2 linux-doc-3.2 linux-manual-3.2 
linux-support-3.2.0-0.bpo.4 linux-libc-dev linux-headers-3.2.0-0.bpo.4-all 
linux-headers-3.2.0-0.bpo.4-all-alpha linux-headers-3.2.0-0.bpo.4-common 
linux-image-3.2.0-0.bpo.4-alpha-generic 
linux-headers-3.2.0-0.bpo.4-alpha-generic linux-image-3.2.0-0.bpo.4-alpha-smp 
linux-headers-3.2.0-0.bpo.4-alpha-smp linux-image-3.2.0-0.bpo.4-alpha-legacy 
linux-headers-3.2.0-0.bpo.4-alpha-legacy linux-headers-3.2.0-0.bpo.4-all-amd64 
linux-image-3.2.0-0.bpo.4-amd64 linux-headers-3.2.0-0.bpo.4-amd64 
linux-image-3.2.0-0.bpo.4-amd64-dbg xen-linux-system-3.2.0-0.bpo.4-amd64 
linux-headers-3.2.0-0.bpo.4-common-rt linux-image-3.2.0-0.bpo.4-rt-amd64 
linux-headers-3.2.0-0.bpo.4-rt-amd64 linux-image-3.2.0-0.bpo.4-rt-amd64-dbg 
linux-headers-3.2.0-0.bpo.4-all-armel linux-image-3.2.0-0.bpo.4-iop32x 
linux-headers-3.2.0-0.bpo.4-iop32x linux-image-3.2.0-0.bpo.4-ixp4xx 
linux-headers-3.2.0-0.bpo.4-ixp4xx linux-image-3.2.0-0.bpo.4-kirkwood
 linux-headers-3.2.0-0.bpo.4-kirkwood linux-image-3.2.0-0.bpo.4-mv78xx0 
linux-headers-3.2.0-0.bpo.4-mv78xx0 linux-image-3.2.0-0.bpo.4-orion5x 
linux-headers-3.2.0-0.bpo.4-orion5x linux-image-3.2.0-0.bpo.4-versatile 
linux-headers-3.2.0-0.bpo.4-versatile linux-headers-3.2.0-0.bpo.4-all-armhf 
linux-image-3.2.0-0.bpo.4-mx5 linux-headers-3.2.0-0.bpo.4-mx5 
linux-image-3.2.0-0.bpo.4-omap linux-headers-3.2.0-0.bpo.4-omap 
linux-image-3.2.0-0.bpo.4-vexpress linux-headers-3.2.0-0.bpo.4-vexpress 
linux-headers-3.2.0-0.bpo.4-all-hppa linux-image-3.2.0-0.bpo.4-parisc 
linux-headers-3.2.0-0.bpo.4-parisc linux-image-3.2.0-0.bpo.4-parisc-smp 
linux-headers-3.2.0-0.bpo.4-parisc-smp linux-image-3.2.0-0.bpo.4-parisc64 
linux-headers-3.2.0-0.bpo.4-parisc64 linux-image-3.2.0-0.bpo.4-parisc64-smp 
linux-headers-3.2.0-0.bpo.4-parisc64-smp linux-headers-3.2.0-0.bpo.4-all-i386 
linux-image-3.2.0-0.bpo.4-486 linux-headers-3.2.0-0.bpo.4-486 
linux-image-3.2.0-0.bpo.4-686-pae
 linux-headers-3.2.0-0.bpo.4-686-pae linux-image-3.2.0-0.bpo.4-686-pae-dbg 
xen-linux-system-3.2.0-0.bpo.4-686-pae linux-image-3.2.0-0.bpo.4-rt-686-pae 
linux-headers-3.2.0-0.bpo.4-rt-686-pae linux-image-3.2.0-0.bpo.4-rt-686-pae-dbg 
linux-headers-3.2.0-0.bpo.4-all-ia64 linux-image-3.2.0-0.bpo.4-itanium 
linux-headers-3.2.0-0.bpo.4-itanium linux-image-3.2.0-0.bpo.4-mckinley 
linux-headers-3.2.0-0.bpo.4-mckinley linux-headers-3.2.0-0.bpo.4-all-m68k 
linux-image-3.2.0-0.bpo.4-amiga linux-headers-3.2.0-0.bpo.4-amiga 
linux-image-3.2.0-0.bpo.4-atari linux-headers-3.2.0-0.bpo.4-atari 
linux-image-3.2.0-0.bpo.4-bvme6000 linux-headers-3.2.0-0.bpo.4-bvme6000 
linux-image-3.2.0-0.bpo.4-mac linux-headers-3.2.0-0.bpo.4-mac 
linux-image-3.2.0-0.bpo.4-mvme147 linux-headers-3.2.0-0.bpo.4-mvme147 
linux-image-3.2.0-0.bpo.4-mvme16x linux-headers-3.2.0-0.bpo.4-mvme16x 
linux-headers-3.2.0-0.bpo.4-all-mips linux-image-3.2.0-0.bpo.4-r4k-ip22 
linux-headers-3.2.0-0.bpo.4-r4k-ip22
 linux-image-3.2.0-0.bpo.4-r5k-ip32 linux-headers-3.2.0-0.bpo.4-r5k-ip32 
linux-image-3.2.0-0.bpo.4-sb1-bcm91250a 
linux-headers-3.2.0-0.bpo.4-sb1-bcm91250a 
linux-image-3.2.0-0.bpo.4-sb1a-bcm91480b 
linux-headers-3.2.0-0.bpo.4-sb1a-bcm91480b linux-image-3.2.0-0.bpo.4-4kc-malta 
linux-headers-3.2.0-0.bpo.4-4kc-malta linux-image-3.2.0-0.bpo.4-5kc-malta 
linux-headers-3.2.0-0.bpo.4-5kc-malta linux-image-3.2.0-0.bpo.4-octeon 
linux-headers-3.2.0-0.bpo.4-octeon linux-headers-3.2.0-0.bpo.4-all-mipsel 
linux-image-3.2.0-0.bpo.4-r5k-cobalt linux-headers-3.2.0-0.bpo.4-r5k-cobalt 
linux-image-3.2.0-0.bpo.4-loongson-2f linux-headers-3.2.0-0.bpo.4-loongson-2f 
linux-headers-3.2.0-0.bpo.4-all-powerpc linux-image-3.2.0-0.bpo.4-powerpc 
linux-headers-3.2.0-0.bpo.4-powerpc linux-image-3.2.0-0.bpo.4-powerpc-smp 
linux-headers-3.2.0-0.bpo.4-powerpc-smp linux-image-3.2.0-0.bpo.4-powerpc64 
linux-headers-3.2.0-0.bpo.4-powerpc64 linux-headers-3.2.0-0.bpo.4-all-ppc64
 linux-headers-3.2.0-0.bpo.4-all-s390 linux-image-3.2.0-0.bpo.4-s390x 
linux-headers-3.2.0-0.bpo.4-s390x linux-image-3.2.0-0.bpo.4-s390x-dbg 
linux-image-3.2.0-0.bpo.4-s390x-tape linux-headers-3.2.0-0.bpo.4-all-s390x 
linux-headers-3.2.0-0.bpo.4-all-sh4 linux-image-3.2.0-0.bpo.4-sh7751r 
linux-headers-3.2.0-0.bpo.4-sh7751r linux-image-3.2.0-0.bpo.4-sh7785lcr 
linux-headers-3.2.0-0.bpo.4-sh7785lcr linux-headers-3.2.0-0.bpo.4-all-sparc 
linux-image-3.2.0-0.bpo.4-sparc64 linux-headers-3.2.0-0.bpo.4-sparc64 
linux-image-3.2.0-0.bpo.4-sparc64-smp linux-headers-3.2.0-0.bpo.4-sparc64-smp
 linux-headers-3.2.0-0.bpo.4-all-sparc64
Architecture: all source
Version: 3.2.73-2+deb7u2~bpo60+1
Distribution: squeeze-backports
Urgency: medium
Maintainer: Debian Kernel Team 
Changed-By: Ben Hutchings 
Closes: 785189 786551 789180 805880 808293 808602 808953 808973
Description: 
 linux-doc-3.2 - Linux kernel specific documentation 

Bug#808602: marked as done (USB 3 regression - external HDD disconnects immediately after connecting)

[Debian Bug Tracking System]

Your message dated Wed, 06 Jan 2016 22:17:43 +
with message-id 
and subject line Bug#808602: fixed in linux 3.16.7-ckt20-1+deb8u2
has caused the Debian Bug report #808602,
regarding USB 3 regression - external HDD disconnects immediately after 
connecting
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.)


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

Package: linux-image-3.16.0-4-amd64
Version: 3.16.7-ckt20-1+deb8u1
Severity: normal

Dear Maintainer,

the recent kernel update (to version 3.16.7-ckt20-1+deb8u1) introduced a 
regression on my systems - my HDDs in the external USB 3.0 box are 
disconnected immediately after I connect them to any USB port on my 
laptop. In other words connecting to USB 3.0 or 2.0 port does not make a 
difference - it is not possible to use the external HDD in both cases.


After downgrading the kernel (to version 3.16.7-ckt11-1+deb8u3) the HDDs 
in the external USB 3.0 box work normally. On both kernel versions my 
USB 2.0 devices (flash disks, mouse etc.) seems to work ok.


For now as a workaround I use the previous kernel version 
3.16.7-ckt11-1+deb8u3, because I need to use the external HDDs often, 
however it would be nice to resume the security updates for the kernel 
as soon as this issue is fixed.


If needed I will be able (in a day or two) to test whether the problem 
occurs also with another USB 3.0 flash disk and on a different laptop.


Thanks
Your Happy Debian User



-- 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-ckt20-1+deb8u1 
(2015-12-14)


** Kernel log (lines related to this USB problem):
[  254.846529] usb 4-1: new SuperSpeed USB device number 2 using xhci_hcd
[  254.864086] usb 4-1: New USB device found, idVendor=152d, idProduct=0539
[  254.864093] usb 4-1: New USB device strings: Mfr=1, Product=2, 
SerialNumber=5

[  254.864096] usb 4-1: Product: USB to ATA/ATAPI Bridge
[  254.864099] usb 4-1: Manufacturer: JMicron
[  254.864101] usb 4-1: SerialNumber: 2461937287FF
[  254.864596] usb 4-1: Set SEL for device-initiated U1 failed.
[  259.867742] usb 4-1: Set SEL for device-initiated U2 failed.
[  259.867867] usb-storage 4-1:1.0: USB Mass Storage device detected
[  259.868398] scsi7 : usb-storage 4-1:1.0
[  264.872900] usb 4-1: Set SEL for device-initiated U1 failed.
[  269.878233] usb 4-1: Set SEL for device-initiated U2 failed.
[  292.514162] usb 4-1: reset SuperSpeed USB device number 2 using xhci_hcd
[  292.540524] usb 4-1: device descriptor read/8, error -71
[  292.641985] usb 4-1: reset SuperSpeed USB device number 2 using xhci_hcd
[  292.668663] usb 4-1: device descriptor read/8, error -71
[  292.826931] usb 4-1: USB disconnect, device number 2
[  292.827371] xhci_hcd :00:14.0: xHCI xhci_drop_endpoint called 
with disabled ep 880036e60040
[  292.827378] xhci_hcd :00:14.0: xHCI xhci_drop_endpoint called 
with disabled ep 880036e60088


** Loaded modules:
nls_utf8
nls_cp437
vfat
fat
ctr
ccm
pci_stub
vboxpci(O)
vboxnetadp(O)
vboxnetflt(O)
vboxdrv(O)
ip6t_REJECT
xt_hl
ip6t_rt
nf_conntrack_ipv6
nf_defrag_ipv6
ipt_REJECT
xt_LOG
xt_limit
xt_tcpudp
xt_addrtype
nf_conntrack_ipv4
nf_defrag_ipv4
xt_conntrack
ip6table_filter
ip6_tables
nf_conntrack_netbios_ns
nf_conntrack_broadcast
nf_nat_ftp
nf_nat
nf_conntrack_ftp
nf_conntrack
iptable_filter
ip_tables
x_tables
uvcvideo
videobuf2_vmalloc
videobuf2_memops
videobuf2_core
v4l2_common
videodev
snd_hda_codec_hdmi
snd_hda_codec_realtek
snd_hda_codec_generic
media
arc4
ath9k
ath9k_common
ath9k_hw
joydev
ath
mac80211
snd_hda_intel
snd_hda_controller
snd_hda_codec
iTCO_wdt
snd_hwdep
iTCO_vendor_support
acer_wmi
cfg80211
x86_pkg_temp_thermal
snd_pcm_oss
intel_powerclamp
evdev
intel_rapl
sparse_keymap
psmouse
serio_raw
rfkill
snd_mixer_oss
snd_pcm
i915
drm_kms_helper
drm
snd_timer
i2c_i801
i2c_algo_bit
i2c_core
video
processor
shpchp
snd
soundcore
lpc_ich
mfd_core
mei_me
mei
thermal_sys
battery
ac
kvm_intel
kvm
button
wmi
coretemp
fuse
autofs4
ext4
crc16
mbcache
jbd2
sha256_ssse3
sha256_generic
algif_skcipher
af_alg
dm_crypt
dm_mod
hid_generic
usbhid
hid
sg
sd_mod
sr_mod
crc_t10dif
cdrom
crct10dif_generic
usb_storage
crct10dif_pclmul
crct10dif_common
crc32_pclmul
crc32c_intel
ghash_clmulni_intel
ahci
aesni_intel
libahci
aes_x86_64
lrw
gf128mul
glue_helper
ablk_helper
ehci_pci
cryptd
libata
xhci_hcd
ehci_hcd
tg3
sdhci_pci
scsi_mod
sdhci
ptp
pps_core
mmc_core
libphy
usbcore

Processing of linux_3.16.7-ckt20-1+deb8u2~bpo70+1_multi.changes

[Debian FTP Masters]

linux_3.16.7-ckt20-1+deb8u2~bpo70+1_multi.changes uploaded successfully to 
localhost
along with the files:
  linux_3.16.7-ckt20-1+deb8u2~bpo70+1.dsc
  linux_3.16.7-ckt20-1+deb8u2~bpo70+1.debian.tar.xz
  linux-support-3.16.0-0.bpo.4_3.16.7-ckt20-1+deb8u2~bpo70+1_all.deb
  linux-doc-3.16_3.16.7-ckt20-1+deb8u2~bpo70+1_all.deb
  linux-manual-3.16_3.16.7-ckt20-1+deb8u2~bpo70+1_all.deb
  linux-source-3.16_3.16.7-ckt20-1+deb8u2~bpo70+1_all.deb

Greetings,

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

Bug#808602: marked as done (USB 3 regression - external HDD disconnects immediately after connecting)

[Debian Bug Tracking System]

Your message dated Wed, 06 Jan 2016 22:24:56 +
with message-id 
and subject line Bug#808602: fixed in linux 3.2.73-2+deb7u2
has caused the Debian Bug report #808602,
regarding USB 3 regression - external HDD disconnects immediately after 
connecting
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.)


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

Package: linux-image-3.16.0-4-amd64
Version: 3.16.7-ckt20-1+deb8u1
Severity: normal

Dear Maintainer,

the recent kernel update (to version 3.16.7-ckt20-1+deb8u1) introduced a 
regression on my systems - my HDDs in the external USB 3.0 box are 
disconnected immediately after I connect them to any USB port on my 
laptop. In other words connecting to USB 3.0 or 2.0 port does not make a 
difference - it is not possible to use the external HDD in both cases.


After downgrading the kernel (to version 3.16.7-ckt11-1+deb8u3) the HDDs 
in the external USB 3.0 box work normally. On both kernel versions my 
USB 2.0 devices (flash disks, mouse etc.) seems to work ok.


For now as a workaround I use the previous kernel version 
3.16.7-ckt11-1+deb8u3, because I need to use the external HDDs often, 
however it would be nice to resume the security updates for the kernel 
as soon as this issue is fixed.


If needed I will be able (in a day or two) to test whether the problem 
occurs also with another USB 3.0 flash disk and on a different laptop.


Thanks
Your Happy Debian User



-- 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-ckt20-1+deb8u1 
(2015-12-14)


** Kernel log (lines related to this USB problem):
[  254.846529] usb 4-1: new SuperSpeed USB device number 2 using xhci_hcd
[  254.864086] usb 4-1: New USB device found, idVendor=152d, idProduct=0539
[  254.864093] usb 4-1: New USB device strings: Mfr=1, Product=2, 
SerialNumber=5

[  254.864096] usb 4-1: Product: USB to ATA/ATAPI Bridge
[  254.864099] usb 4-1: Manufacturer: JMicron
[  254.864101] usb 4-1: SerialNumber: 2461937287FF
[  254.864596] usb 4-1: Set SEL for device-initiated U1 failed.
[  259.867742] usb 4-1: Set SEL for device-initiated U2 failed.
[  259.867867] usb-storage 4-1:1.0: USB Mass Storage device detected
[  259.868398] scsi7 : usb-storage 4-1:1.0
[  264.872900] usb 4-1: Set SEL for device-initiated U1 failed.
[  269.878233] usb 4-1: Set SEL for device-initiated U2 failed.
[  292.514162] usb 4-1: reset SuperSpeed USB device number 2 using xhci_hcd
[  292.540524] usb 4-1: device descriptor read/8, error -71
[  292.641985] usb 4-1: reset SuperSpeed USB device number 2 using xhci_hcd
[  292.668663] usb 4-1: device descriptor read/8, error -71
[  292.826931] usb 4-1: USB disconnect, device number 2
[  292.827371] xhci_hcd :00:14.0: xHCI xhci_drop_endpoint called 
with disabled ep 880036e60040
[  292.827378] xhci_hcd :00:14.0: xHCI xhci_drop_endpoint called 
with disabled ep 880036e60088


** Loaded modules:
nls_utf8
nls_cp437
vfat
fat
ctr
ccm
pci_stub
vboxpci(O)
vboxnetadp(O)
vboxnetflt(O)
vboxdrv(O)
ip6t_REJECT
xt_hl
ip6t_rt
nf_conntrack_ipv6
nf_defrag_ipv6
ipt_REJECT
xt_LOG
xt_limit
xt_tcpudp
xt_addrtype
nf_conntrack_ipv4
nf_defrag_ipv4
xt_conntrack
ip6table_filter
ip6_tables
nf_conntrack_netbios_ns
nf_conntrack_broadcast
nf_nat_ftp
nf_nat
nf_conntrack_ftp
nf_conntrack
iptable_filter
ip_tables
x_tables
uvcvideo
videobuf2_vmalloc
videobuf2_memops
videobuf2_core
v4l2_common
videodev
snd_hda_codec_hdmi
snd_hda_codec_realtek
snd_hda_codec_generic
media
arc4
ath9k
ath9k_common
ath9k_hw
joydev
ath
mac80211
snd_hda_intel
snd_hda_controller
snd_hda_codec
iTCO_wdt
snd_hwdep
iTCO_vendor_support
acer_wmi
cfg80211
x86_pkg_temp_thermal
snd_pcm_oss
intel_powerclamp
evdev
intel_rapl
sparse_keymap
psmouse
serio_raw
rfkill
snd_mixer_oss
snd_pcm
i915
drm_kms_helper
drm
snd_timer
i2c_i801
i2c_algo_bit
i2c_core
video
processor
shpchp
snd
soundcore
lpc_ich
mfd_core
mei_me
mei
thermal_sys
battery
ac
kvm_intel
kvm
button
wmi
coretemp
fuse
autofs4
ext4
crc16
mbcache
jbd2
sha256_ssse3
sha256_generic
algif_skcipher
af_alg
dm_crypt
dm_mod
hid_generic
usbhid
hid
sg
sd_mod
sr_mod
crc_t10dif
cdrom
crct10dif_generic
usb_storage
crct10dif_pclmul
crct10dif_common
crc32_pclmul
crc32c_intel
ghash_clmulni_intel
ahci
aesni_intel
libahci
aes_x86_64
lrw
gf128mul
glue_helper
ablk_helper
ehci_pci
cryptd
libata
xhci_hcd
ehci_hcd
tg3
sdhci_pci
scsi_mod
sdhci
ptp
pps_core
mmc_core
libphy
usbcore

Bug#808953: marked as done (linux: xhci regression in backported patch)

[Debian Bug Tracking System]

Your message dated Wed, 06 Jan 2016 22:24:56 +
with message-id 
and subject line Bug#808953: fixed in linux 3.2.73-2+deb7u2
has caused the Debian Bug report #808953,
regarding linux: xhci regression in backported patch
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.)


-- 
808953: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=808953
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: linux
Version: 3.16.7-ckt20-1
Severity: important

Hi,

While testing the code from here: http://www.bitbabbler.org I ran into a
problem on recently updated Jessie systems where devices plugged into an
XHCI port would always time out between transfers when the transfer size
was larger than 16kB.  And since it wasn't doing that a few weeks ago, I
went digging :)

All the following was tested on amd64.

I can confirm that 3.16.7-ckt17-1 does not have this problem and it's a
newly introduced regression that's first seen with the ckt20 patch set.
I can also confirm that 4.2.0-0.bpo.1 from jessie-backports does not
have this problem.

The cause appears to be a botched backport of
e210c422b6fdd2dc123bedc588f399aefd8bf9de (from Linus' repo) because I can
also confirm that a locally built kernel from the 3.16.7-ckt20-1 source
with only that patch reverted also does not have this problem.

If it's really important that we have that patch for some reason, then
it looks like (at least) 40a3b775f49c2784c96b19170fd2478e5e5511a1 would
also need to be backported too, and maybe some other changes that effect
this as well.  I haven't analysed that part of it in more detail, but
it's clear this patch needs something more than just being massaged to
fit the context to actually work.

This is a fairly serious regression that makes USB3 ports (even with
USB2 devices in them) pretty close to useless you're heavily into having
10 second latency between every transfer that occurs - so we should
probably revert this unless someone who knows that code well can review
a better backport of it to ensure there won't be unintended ill effects.

  Cheers,
  Ron
--- End Message ---
--- Begin Message ---
Source: linux
Source-Version: 3.2.73-2+deb7u2

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 808...@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: Sat, 02 Jan 2016 03:31:22 +
Source: linux
Binary: linux-source-3.2 linux-doc-3.2 linux-manual-3.2 linux-support-3.2.0-4 
linux-libc-dev linux-headers-3.2.0-4-all linux-headers-3.2.0-4-all-alpha 
linux-headers-3.2.0-4-common linux-image-3.2.0-4-alpha-generic 
linux-headers-3.2.0-4-alpha-generic linux-image-3.2.0-4-alpha-smp 
linux-headers-3.2.0-4-alpha-smp linux-image-3.2.0-4-alpha-legacy 
linux-headers-3.2.0-4-alpha-legacy linux-headers-3.2.0-4-all-amd64 
kernel-image-3.2.0-4-amd64-di nic-modules-3.2.0-4-amd64-di 
nic-extra-modules-3.2.0-4-amd64-di nic-wireless-modules-3.2.0-4-amd64-di 
nic-shared-modules-3.2.0-4-amd64-di serial-modules-3.2.0-4-amd64-di 
usb-serial-modules-3.2.0-4-amd64-di ppp-modules-3.2.0-4-amd64-di 
pata-modules-3.2.0-4-amd64-di cdrom-core-modules-3.2.0-4-amd64-di 
firewire-core-modules-3.2.0-4-amd64-di scsi-core-modules-3.2.0-4-amd64-di 
scsi-modules-3.2.0-4-amd64-di scsi-common-modules-3.2.0-4-amd64-di 
scsi-extra-modules-3.2.0-4-amd64-di plip-modules-3.2.0-4-amd64-di 
floppy-modules-3.2.0-4-amd64-di
 loop-modules-3.2.0-4-amd64-di btrfs-modules-3.2.0-4-amd64-di 
ext2-modules-3.2.0-4-amd64-di ext3-modules-3.2.0-4-amd64-di 
ext4-modules-3.2.0-4-amd64-di isofs-modules-3.2.0-4-amd64-di 
jfs-modules-3.2.0-4-amd64-di ntfs-modules-3.2.0-4-amd64-di 
reiserfs-modules-3.2.0-4-amd64-di xfs-modules-3.2.0-4-amd64-di 
fat-modules-3.2.0-4-amd64-di ufs-modules-3.2.0-4-amd64-di 
qnx4-modules-3.2.0-4-amd64-di md-modules-3.2.0-4-amd64-di 
multipath-modules-3.2.0-4-amd64-di usb-modules-3.2.0-4-amd64-di 
usb-storage-modules-3.2.0-4-amd64-di 

linux_3.2.73-2+deb7u2_multi.changes ACCEPTED into oldstable-proposed-updates->oldstable-new, oldstable-proposed-updates

[Debian FTP Masters]

Accepted:

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sat, 02 Jan 2016 03:31:22 +
Source: linux
Binary: linux-source-3.2 linux-doc-3.2 linux-manual-3.2 linux-support-3.2.0-4 
linux-libc-dev linux-headers-3.2.0-4-all linux-headers-3.2.0-4-all-alpha 
linux-headers-3.2.0-4-common linux-image-3.2.0-4-alpha-generic 
linux-headers-3.2.0-4-alpha-generic linux-image-3.2.0-4-alpha-smp 
linux-headers-3.2.0-4-alpha-smp linux-image-3.2.0-4-alpha-legacy 
linux-headers-3.2.0-4-alpha-legacy linux-headers-3.2.0-4-all-amd64 
kernel-image-3.2.0-4-amd64-di nic-modules-3.2.0-4-amd64-di 
nic-extra-modules-3.2.0-4-amd64-di nic-wireless-modules-3.2.0-4-amd64-di 
nic-shared-modules-3.2.0-4-amd64-di serial-modules-3.2.0-4-amd64-di 
usb-serial-modules-3.2.0-4-amd64-di ppp-modules-3.2.0-4-amd64-di 
pata-modules-3.2.0-4-amd64-di cdrom-core-modules-3.2.0-4-amd64-di 
firewire-core-modules-3.2.0-4-amd64-di scsi-core-modules-3.2.0-4-amd64-di 
scsi-modules-3.2.0-4-amd64-di scsi-common-modules-3.2.0-4-amd64-di 
scsi-extra-modules-3.2.0-4-amd64-di plip-modules-3.2.0-4-amd64-di 
floppy-modules-3.2.0-4-amd64-di
 loop-modules-3.2.0-4-amd64-di btrfs-modules-3.2.0-4-amd64-di 
ext2-modules-3.2.0-4-amd64-di ext3-modules-3.2.0-4-amd64-di 
ext4-modules-3.2.0-4-amd64-di isofs-modules-3.2.0-4-amd64-di 
jfs-modules-3.2.0-4-amd64-di ntfs-modules-3.2.0-4-amd64-di 
reiserfs-modules-3.2.0-4-amd64-di xfs-modules-3.2.0-4-amd64-di 
fat-modules-3.2.0-4-amd64-di ufs-modules-3.2.0-4-amd64-di 
qnx4-modules-3.2.0-4-amd64-di md-modules-3.2.0-4-amd64-di 
multipath-modules-3.2.0-4-amd64-di usb-modules-3.2.0-4-amd64-di 
usb-storage-modules-3.2.0-4-amd64-di pcmcia-storage-modules-3.2.0-4-amd64-di 
fb-modules-3.2.0-4-amd64-di input-modules-3.2.0-4-amd64-di 
event-modules-3.2.0-4-amd64-di mouse-modules-3.2.0-4-amd64-di 
irda-modules-3.2.0-4-amd64-di parport-modules-3.2.0-4-amd64-di 
nic-pcmcia-modules-3.2.0-4-amd64-di pcmcia-modules-3.2.0-4-amd64-di 
nic-usb-modules-3.2.0-4-amd64-di sata-modules-3.2.0-4-amd64-di 
core-modules-3.2.0-4-amd64-di acpi-modules-3.2.0-4-amd64-di 
i2c-modules-3.2.0-4-amd64-di
 crc-modules-3.2.0-4-amd64-di crypto-modules-3.2.0-4-amd64-di 
crypto-dm-modules-3.2.0-4-amd64-di efi-modules-3.2.0-4-amd64-di 
ata-modules-3.2.0-4-amd64-di mmc-core-modules-3.2.0-4-amd64-di 
mmc-modules-3.2.0-4-amd64-di nbd-modules-3.2.0-4-amd64-di 
squashfs-modules-3.2.0-4-amd64-di speakup-modules-3.2.0-4-amd64-di 
virtio-modules-3.2.0-4-amd64-di uinput-modules-3.2.0-4-amd64-di 
sound-modules-3.2.0-4-amd64-di zlib-modules-3.2.0-4-amd64-di 
hyperv-modules-3.2.0-4-amd64-di udf-modules-3.2.0-4-amd64-di 
fuse-modules-3.2.0-4-amd64-di linux-image-3.2.0-4-amd64 
linux-headers-3.2.0-4-amd64 linux-image-3.2.0-4-amd64-dbg 
xen-linux-system-3.2.0-4-amd64 linux-headers-3.2.0-4-common-rt 
linux-image-3.2.0-4-rt-amd64 linux-headers-3.2.0-4-rt-amd64 
linux-image-3.2.0-4-rt-amd64-dbg linux-headers-3.2.0-4-all-armel 
kernel-image-3.2.0-4-iop32x-di nic-modules-3.2.0-4-iop32x-di 
nic-shared-modules-3.2.0-4-iop32x-di usb-serial-modules-3.2.0-4-iop32x-di 
ppp-modules-3.2.0-4-iop32x-di
 pata-modules-3.2.0-4-iop32x-di cdrom-core-modules-3.2.0-4-iop32x-di 
scsi-core-modules-3.2.0-4-iop32x-di loop-modules-3.2.0-4-iop32x-di 
ipv6-modules-3.2.0-4-iop32x-di btrfs-modules-3.2.0-4-iop32x-di 
ext2-modules-3.2.0-4-iop32x-di ext3-modules-3.2.0-4-iop32x-di 
ext4-modules-3.2.0-4-iop32x-di isofs-modules-3.2.0-4-iop32x-di 
jffs2-modules-3.2.0-4-iop32x-di jfs-modules-3.2.0-4-iop32x-di 
reiserfs-modules-3.2.0-4-iop32x-di fat-modules-3.2.0-4-iop32x-di 
md-modules-3.2.0-4-iop32x-di multipath-modules-3.2.0-4-iop32x-di 
usb-modules-3.2.0-4-iop32x-di usb-storage-modules-3.2.0-4-iop32x-di 
event-modules-3.2.0-4-iop32x-di nic-usb-modules-3.2.0-4-iop32x-di 
sata-modules-3.2.0-4-iop32x-di core-modules-3.2.0-4-iop32x-di 
crc-modules-3.2.0-4-iop32x-di crypto-modules-3.2.0-4-iop32x-di 
crypto-dm-modules-3.2.0-4-iop32x-di ata-modules-3.2.0-4-iop32x-di 
nbd-modules-3.2.0-4-iop32x-di squashfs-modules-3.2.0-4-iop32x-di 
zlib-modules-3.2.0-4-iop32x-di udf-modules-3.2.0-4-iop32x-di
 fuse-modules-3.2.0-4-iop32x-di kernel-image-3.2.0-4-kirkwood-di 
nic-modules-3.2.0-4-kirkwood-di nic-shared-modules-3.2.0-4-kirkwood-di 
usb-serial-modules-3.2.0-4-kirkwood-di ppp-modules-3.2.0-4-kirkwood-di 
cdrom-core-modules-3.2.0-4-kirkwood-di scsi-core-modules-3.2.0-4-kirkwood-di 
loop-modules-3.2.0-4-kirkwood-di ipv6-modules-3.2.0-4-kirkwood-di 
btrfs-modules-3.2.0-4-kirkwood-di ext2-modules-3.2.0-4-kirkwood-di 
ext3-modules-3.2.0-4-kirkwood-di ext4-modules-3.2.0-4-kirkwood-di 
isofs-modules-3.2.0-4-kirkwood-di jfs-modules-3.2.0-4-kirkwood-di 
reiserfs-modules-3.2.0-4-kirkwood-di fat-modules-3.2.0-4-kirkwood-di 
minix-modules-3.2.0-4-kirkwood-di md-modules-3.2.0-4-kirkwood-di 
multipath-modules-3.2.0-4-kirkwood-di usb-modules-3.2.0-4-kirkwood-di 
usb-storage-modules-3.2.0-4-kirkwood-di fb-modules-3.2.0-4-kirkwood-di 
input-modules-3.2.0-4-kirkwood-di event-modules-3.2.0-4-kirkwood-di 

linux_3.16.7-ckt20-1+deb8u2~bpo70+1_multi.changes ACCEPTED into wheezy-backports->backports-policy

[Debian FTP Masters]

Accepted:

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 03 Jan 2016 02:19:19 +
Source: linux
Binary: linux-source-3.16 linux-doc-3.16 linux-manual-3.16 
linux-support-3.16.0-0.bpo.4 linux-libc-dev linux-headers-3.16.0-0.bpo.4-all 
linux-headers-3.16.0-0.bpo.4-all-amd64 kernel-image-3.16.0-0.bpo.4-amd64-di 
nic-modules-3.16.0-0.bpo.4-amd64-di 
nic-wireless-modules-3.16.0-0.bpo.4-amd64-di 
nic-shared-modules-3.16.0-0.bpo.4-amd64-di 
serial-modules-3.16.0-0.bpo.4-amd64-di 
usb-serial-modules-3.16.0-0.bpo.4-amd64-di ppp-modules-3.16.0-0.bpo.4-amd64-di 
pata-modules-3.16.0-0.bpo.4-amd64-di cdrom-core-modules-3.16.0-0.bpo.4-amd64-di 
firewire-core-modules-3.16.0-0.bpo.4-amd64-di 
scsi-core-modules-3.16.0-0.bpo.4-amd64-di scsi-modules-3.16.0-0.bpo.4-amd64-di 
scsi-common-modules-3.16.0-0.bpo.4-amd64-di 
scsi-extra-modules-3.16.0-0.bpo.4-amd64-di loop-modules-3.16.0-0.bpo.4-amd64-di 
btrfs-modules-3.16.0-0.bpo.4-amd64-di ext4-modules-3.16.0-0.bpo.4-amd64-di 
isofs-modules-3.16.0-0.bpo.4-amd64-di jfs-modules-3.16.0-0.bpo.4-amd64-di 
ntfs-modules-3.16.0-0.bpo.4-amd64-di
 xfs-modules-3.16.0-0.bpo.4-amd64-di fat-modules-3.16.0-0.bpo.4-amd64-di 
md-modules-3.16.0-0.bpo.4-amd64-di multipath-modules-3.16.0-0.bpo.4-amd64-di 
usb-modules-3.16.0-0.bpo.4-amd64-di usb-storage-modules-3.16.0-0.bpo.4-amd64-di 
pcmcia-storage-modules-3.16.0-0.bpo.4-amd64-di 
fb-modules-3.16.0-0.bpo.4-amd64-di input-modules-3.16.0-0.bpo.4-amd64-di 
event-modules-3.16.0-0.bpo.4-amd64-di mouse-modules-3.16.0-0.bpo.4-amd64-di 
nic-pcmcia-modules-3.16.0-0.bpo.4-amd64-di 
pcmcia-modules-3.16.0-0.bpo.4-amd64-di nic-usb-modules-3.16.0-0.bpo.4-amd64-di 
sata-modules-3.16.0-0.bpo.4-amd64-di core-modules-3.16.0-0.bpo.4-amd64-di 
acpi-modules-3.16.0-0.bpo.4-amd64-di i2c-modules-3.16.0-0.bpo.4-amd64-di 
crc-modules-3.16.0-0.bpo.4-amd64-di crypto-modules-3.16.0-0.bpo.4-amd64-di 
crypto-dm-modules-3.16.0-0.bpo.4-amd64-di efi-modules-3.16.0-0.bpo.4-amd64-di 
ata-modules-3.16.0-0.bpo.4-amd64-di mmc-core-modules-3.16.0-0.bpo.4-amd64-di 
mmc-modules-3.16.0-0.bpo.4-amd64-di
 nbd-modules-3.16.0-0.bpo.4-amd64-di squashfs-modules-3.16.0-0.bpo.4-amd64-di 
speakup-modules-3.16.0-0.bpo.4-amd64-di virtio-modules-3.16.0-0.bpo.4-amd64-di 
uinput-modules-3.16.0-0.bpo.4-amd64-di sound-modules-3.16.0-0.bpo.4-amd64-di 
hyperv-modules-3.16.0-0.bpo.4-amd64-di udf-modules-3.16.0-0.bpo.4-amd64-di 
fuse-modules-3.16.0-0.bpo.4-amd64-di linux-headers-3.16.0-0.bpo.4-common 
linux-image-3.16.0-0.bpo.4-amd64 linux-headers-3.16.0-0.bpo.4-amd64 
linux-image-3.16.0-0.bpo.4-amd64-dbg xen-linux-system-3.16.0-0.bpo.4-amd64 
linux-headers-3.16.0-0.bpo.4-all-armel kernel-image-3.16.0-0.bpo.4-kirkwood-di 
nic-modules-3.16.0-0.bpo.4-kirkwood-di 
nic-shared-modules-3.16.0-0.bpo.4-kirkwood-di 
usb-serial-modules-3.16.0-0.bpo.4-kirkwood-di 
ppp-modules-3.16.0-0.bpo.4-kirkwood-di 
cdrom-core-modules-3.16.0-0.bpo.4-kirkwood-di 
scsi-core-modules-3.16.0-0.bpo.4-kirkwood-di 
loop-modules-3.16.0-0.bpo.4-kirkwood-di btrfs-modules-3.16.0-0.bpo.4-kirkwood-di
 ext4-modules-3.16.0-0.bpo.4-kirkwood-di 
isofs-modules-3.16.0-0.bpo.4-kirkwood-di jfs-modules-3.16.0-0.bpo.4-kirkwood-di 
fat-modules-3.16.0-0.bpo.4-kirkwood-di minix-modules-3.16.0-0.bpo.4-kirkwood-di 
md-modules-3.16.0-0.bpo.4-kirkwood-di 
multipath-modules-3.16.0-0.bpo.4-kirkwood-di 
usb-modules-3.16.0-0.bpo.4-kirkwood-di 
usb-storage-modules-3.16.0-0.bpo.4-kirkwood-di 
fb-modules-3.16.0-0.bpo.4-kirkwood-di input-modules-3.16.0-0.bpo.4-kirkwood-di 
event-modules-3.16.0-0.bpo.4-kirkwood-di 
mouse-modules-3.16.0-0.bpo.4-kirkwood-di 
nic-usb-modules-3.16.0-0.bpo.4-kirkwood-di 
sata-modules-3.16.0-0.bpo.4-kirkwood-di core-modules-3.16.0-0.bpo.4-kirkwood-di 
crc-modules-3.16.0-0.bpo.4-kirkwood-di 
crypto-modules-3.16.0-0.bpo.4-kirkwood-di 
crypto-dm-modules-3.16.0-0.bpo.4-kirkwood-di 
mmc-modules-3.16.0-0.bpo.4-kirkwood-di nbd-modules-3.16.0-0.bpo.4-kirkwood-di 
squashfs-modules-3.16.0-0.bpo.4-kirkwood-di 
uinput-modules-3.16.0-0.bpo.4-kirkwood-di
 leds-modules-3.16.0-0.bpo.4-kirkwood-di udf-modules-3.16.0-0.bpo.4-kirkwood-di 
fuse-modules-3.16.0-0.bpo.4-kirkwood-di kernel-image-3.16.0-0.bpo.4-orion5x-di 
nic-modules-3.16.0-0.bpo.4-orion5x-di 
nic-shared-modules-3.16.0-0.bpo.4-orion5x-di 
usb-serial-modules-3.16.0-0.bpo.4-orion5x-di 
ppp-modules-3.16.0-0.bpo.4-orion5x-di 
cdrom-core-modules-3.16.0-0.bpo.4-orion5x-di 
scsi-core-modules-3.16.0-0.bpo.4-orion5x-di 
loop-modules-3.16.0-0.bpo.4-orion5x-di ipv6-modules-3.16.0-0.bpo.4-orion5x-di 
btrfs-modules-3.16.0-0.bpo.4-orion5x-di ext4-modules-3.16.0-0.bpo.4-orion5x-di 
isofs-modules-3.16.0-0.bpo.4-orion5x-di jffs2-modules-3.16.0-0.bpo.4-orion5x-di 
jfs-modules-3.16.0-0.bpo.4-orion5x-di fat-modules-3.16.0-0.bpo.4-orion5x-di 
minix-modules-3.16.0-0.bpo.4-orion5x-di md-modules-3.16.0-0.bpo.4-orion5x-di 
multipath-modules-3.16.0-0.bpo.4-orion5x-di 
usb-modules-3.16.0-0.bpo.4-orion5x-di 
usb-storage-modules-3.16.0-0.bpo.4-orion5x-di 
event-modules-3.16.0-0.bpo.4-orion5x-di
 

Bug#808953: marked as done (linux: xhci regression in backported patch)

[Debian Bug Tracking System]

Your message dated Wed, 06 Jan 2016 22:17:43 +
with message-id 
and subject line Bug#808953: fixed in linux 3.16.7-ckt20-1+deb8u2
has caused the Debian Bug report #808953,
regarding linux: xhci regression in backported patch
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.)


-- 
808953: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=808953
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: linux
Version: 3.16.7-ckt20-1
Severity: important

Hi,

While testing the code from here: http://www.bitbabbler.org I ran into a
problem on recently updated Jessie systems where devices plugged into an
XHCI port would always time out between transfers when the transfer size
was larger than 16kB.  And since it wasn't doing that a few weeks ago, I
went digging :)

All the following was tested on amd64.

I can confirm that 3.16.7-ckt17-1 does not have this problem and it's a
newly introduced regression that's first seen with the ckt20 patch set.
I can also confirm that 4.2.0-0.bpo.1 from jessie-backports does not
have this problem.

The cause appears to be a botched backport of
e210c422b6fdd2dc123bedc588f399aefd8bf9de (from Linus' repo) because I can
also confirm that a locally built kernel from the 3.16.7-ckt20-1 source
with only that patch reverted also does not have this problem.

If it's really important that we have that patch for some reason, then
it looks like (at least) 40a3b775f49c2784c96b19170fd2478e5e5511a1 would
also need to be backported too, and maybe some other changes that effect
this as well.  I haven't analysed that part of it in more detail, but
it's clear this patch needs something more than just being massaged to
fit the context to actually work.

This is a fairly serious regression that makes USB3 ports (even with
USB2 devices in them) pretty close to useless you're heavily into having
10 second latency between every transfer that occurs - so we should
probably revert this unless someone who knows that code well can review
a better backport of it to ensure there won't be unintended ill effects.

  Cheers,
  Ron
--- End Message ---
--- Begin Message ---
Source: linux
Source-Version: 3.16.7-ckt20-1+deb8u2

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 808...@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: Sat, 02 Jan 2016 03:31:39 +
Source: linux
Binary: linux-source-3.16 linux-doc-3.16 linux-manual-3.16 
linux-support-3.16.0-4 linux-libc-dev linux-headers-3.16.0-4-all 
linux-headers-3.16.0-4-all-alpha kernel-image-3.16.0-4-alpha-generic-di 
nic-modules-3.16.0-4-alpha-generic-di 
nic-wireless-modules-3.16.0-4-alpha-generic-di 
nic-shared-modules-3.16.0-4-alpha-generic-di 
serial-modules-3.16.0-4-alpha-generic-di 
usb-serial-modules-3.16.0-4-alpha-generic-di 
ppp-modules-3.16.0-4-alpha-generic-di pata-modules-3.16.0-4-alpha-generic-di 
cdrom-core-modules-3.16.0-4-alpha-generic-di 
scsi-core-modules-3.16.0-4-alpha-generic-di 
scsi-modules-3.16.0-4-alpha-generic-di 
scsi-common-modules-3.16.0-4-alpha-generic-di 
scsi-extra-modules-3.16.0-4-alpha-generic-di 
loop-modules-3.16.0-4-alpha-generic-di btrfs-modules-3.16.0-4-alpha-generic-di 
ext4-modules-3.16.0-4-alpha-generic-di isofs-modules-3.16.0-4-alpha-generic-di 
jfs-modules-3.16.0-4-alpha-generic-di xfs-modules-3.16.0-4-alpha-generic-di 
fat-modules-3.16.0-4-alpha-generic-di
 md-modules-3.16.0-4-alpha-generic-di 
multipath-modules-3.16.0-4-alpha-generic-di 
usb-modules-3.16.0-4-alpha-generic-di 
usb-storage-modules-3.16.0-4-alpha-generic-di 
fb-modules-3.16.0-4-alpha-generic-di input-modules-3.16.0-4-alpha-generic-di 
event-modules-3.16.0-4-alpha-generic-di mouse-modules-3.16.0-4-alpha-generic-di 
nic-pcmcia-modules-3.16.0-4-alpha-generic-di 
pcmcia-modules-3.16.0-4-alpha-generic-di 
nic-usb-modules-3.16.0-4-alpha-generic-di 
sata-modules-3.16.0-4-alpha-generic-di core-modules-3.16.0-4-alpha-generic-di 

Bug#808431: marked as done (linux-source-3.16: FreeRADIUS stopped working when kernel was updated to 3.16.7-ckt20)

[Debian Bug Tracking System]

Your message dated Wed, 06 Jan 2016 22:17:43 +
with message-id 
and subject line Bug#808293: fixed in linux 3.16.7-ckt20-1+deb8u2
has caused the Debian Bug report #808293,
regarding linux-source-3.16: FreeRADIUS stopped working when kernel was updated 
to 3.16.7-ckt20
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.)


-- 
808293: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=808293
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: linux-source-3.16
Version: 3.16.7-ckt-20
Severity: important

Dear Maintainer,

*** Reporter, please consider answering these questions, where appropriate ***

   * What led up to the situation?
Upgrading the Kernel from 3.16.7-ckt11 to 3.16.7-ckt20 (compiled from
source each) broke FreeRADIUS. The freeradius daemon stopped responding to udp
auth queries from locally installed hostapd wifi daemon. Wifi clients using
EAP-TLS auth cannot authenticate an more.


   * What exactly did you do (or not do) that was effective (or
 ineffective)?
Downgrade to Kernel 3.16.7-ckt11 fixed the issue.

   * What was the outcome of this action?
   * What outcome did you expect instead?

*** End of the template - remove these template lines ***



-- System Information:
Debian Release: 8.2
  APT prefers stable
  APT policy: (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.16.0-4-amd64 (SMP w/2 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
--- End Message ---
--- Begin Message ---
Source: linux
Source-Version: 3.16.7-ckt20-1+deb8u2

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 808...@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: Sat, 02 Jan 2016 03:31:39 +
Source: linux
Binary: linux-source-3.16 linux-doc-3.16 linux-manual-3.16 
linux-support-3.16.0-4 linux-libc-dev linux-headers-3.16.0-4-all 
linux-headers-3.16.0-4-all-alpha kernel-image-3.16.0-4-alpha-generic-di 
nic-modules-3.16.0-4-alpha-generic-di 
nic-wireless-modules-3.16.0-4-alpha-generic-di 
nic-shared-modules-3.16.0-4-alpha-generic-di 
serial-modules-3.16.0-4-alpha-generic-di 
usb-serial-modules-3.16.0-4-alpha-generic-di 
ppp-modules-3.16.0-4-alpha-generic-di pata-modules-3.16.0-4-alpha-generic-di 
cdrom-core-modules-3.16.0-4-alpha-generic-di 
scsi-core-modules-3.16.0-4-alpha-generic-di 
scsi-modules-3.16.0-4-alpha-generic-di 
scsi-common-modules-3.16.0-4-alpha-generic-di 
scsi-extra-modules-3.16.0-4-alpha-generic-di 
loop-modules-3.16.0-4-alpha-generic-di btrfs-modules-3.16.0-4-alpha-generic-di 
ext4-modules-3.16.0-4-alpha-generic-di isofs-modules-3.16.0-4-alpha-generic-di 
jfs-modules-3.16.0-4-alpha-generic-di xfs-modules-3.16.0-4-alpha-generic-di 
fat-modules-3.16.0-4-alpha-generic-di
 md-modules-3.16.0-4-alpha-generic-di 
multipath-modules-3.16.0-4-alpha-generic-di 
usb-modules-3.16.0-4-alpha-generic-di 
usb-storage-modules-3.16.0-4-alpha-generic-di 
fb-modules-3.16.0-4-alpha-generic-di input-modules-3.16.0-4-alpha-generic-di 
event-modules-3.16.0-4-alpha-generic-di mouse-modules-3.16.0-4-alpha-generic-di 
nic-pcmcia-modules-3.16.0-4-alpha-generic-di 
pcmcia-modules-3.16.0-4-alpha-generic-di 
nic-usb-modules-3.16.0-4-alpha-generic-di 
sata-modules-3.16.0-4-alpha-generic-di core-modules-3.16.0-4-alpha-generic-di 
crc-modules-3.16.0-4-alpha-generic-di crypto-modules-3.16.0-4-alpha-generic-di 
crypto-dm-modules-3.16.0-4-alpha-generic-di 
ata-modules-3.16.0-4-alpha-generic-di nbd-modules-3.16.0-4-alpha-generic-di 
squashfs-modules-3.16.0-4-alpha-generic-di 
virtio-modules-3.16.0-4-alpha-generic-di zlib-modules-3.16.0-4-alpha-generic-di 
fuse-modules-3.16.0-4-alpha-generic-di srm-modules-3.16.0-4-alpha-generic-di 
linux-headers-3.16.0-4-common
 linux-image-3.16.0-4-alpha-generic linux-headers-3.16.0-4-alpha-generic 

Processed: Re: [pkg-cryptsetup-devel] Bug#783297: breaks initramfs if BUSYBOX=n

[Debian Bug Tracking System]

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

> clone 783297 -1 -2
Bug #783297 [cryptsetup] breaks initramfs if BUSYBOX=n
Bug 783297 cloned as bugs 810153-810154
> reassign -1 busybox
Bug #810153 [cryptsetup] breaks initramfs if BUSYBOX=n
Bug reassigned from package 'cryptsetup' to 'busybox'.
No longer marked as found in versions cryptsetup/2:1.6.6-5.
Ignoring request to alter fixed versions of bug #810153 to the same values 
previously set
> retitle -1 don't source initramfs.conf in busybox initramfs hook
Bug #810153 [busybox] breaks initramfs if BUSYBOX=n
Changed Bug title to 'don't source initramfs.conf in busybox initramfs hook' 
from 'breaks initramfs if BUSYBOX=n'
> reassign -2 initramfs-tools
Bug #810154 [cryptsetup] breaks initramfs if BUSYBOX=n
Bug reassigned from package 'cryptsetup' to 'initramfs-tools'.
No longer marked as found in versions cryptsetup/2:1.6.6-5.
Ignoring request to alter fixed versions of bug #810154 to the same values 
previously set
> retitle -2 remove busybox hook, leave responsibility to busybox package
Bug #810154 [initramfs-tools] breaks initramfs if BUSYBOX=n
Changed Bug title to 'remove busybox hook, leave responsibility to busybox 
package' from 'breaks initramfs if BUSYBOX=n'
> severity -2 important
Bug #810154 [initramfs-tools] remove busybox hook, leave responsibility to 
busybox package
Severity set to 'important' from 'grave'
> retitle 783297 split initramfs integration into a separate package
Bug #783297 [cryptsetup] breaks initramfs if BUSYBOX=n
Changed Bug title to 'split initramfs integration into a separate package' from 
'breaks initramfs if BUSYBOX=n'
> severity 783297 wishlist
Bug #783297 [cryptsetup] split initramfs integration into a separate package
Severity set to 'wishlist' from 'grave'
> thanks
Stopping processing here.

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

Re: [pkg-cryptsetup-devel] Bug#783297: breaks initramfs if BUSYBOX=n

[Jonas Meurer]

clone 783297 -1 -2
reassign -1 busybox
retitle -1 don't source initramfs.conf in busybox initramfs hook
reassign -2 initramfs-tools
retitle -2 remove busybox hook, leave responsibility to busybox package
severity -2 important
retitle 783297 split initramfs integration into a separate package
severity 783297 wishlist
thanks

This mail clones the original bugreport two times and reassigns the
clones to the busybox and initramfs-tools packages with appropriate
titles. See below for details.

Am 27.12.2015 um 07:35 schrieb Ben Hutchings:
> On Fri, 2015-12-25 at 14:46 +0100, Jonas Meurer wrote:
> [...]
>>
>>> /usr/share/initramfs-tools/hooks/busybox will see the BUSYBOX=y setting
>>> and copy the busybox binary.
>>>
>>> /usr/share/initramfs-tools/hooks/zz-busybox sources
>>> /etc/initramfs-tools/initramfs.conf, therefor BUSYBOX=n will be set
>>> again, and the symlinks are not created.
>>
>> Honestly, this looks like a bug in busybox to me. What's the reason for
>> the two busybox initramfs hook scripts at all?
>>
>> *) /usr/share/initramfs-tools/hooks/busybox copies bin/busybox to the
>>initramfs and links /bin/sh to it without sourcing initramfs.conf.
> 
> This is part of initramfs-tools.

So this busybox initramfs hook should be dropped from initramfs-tools
and responsibility for installing busybox into initramfs be handed over
to the busybox package.

>> *) /usr/share/initramfs-tools/hooks/zz-busybox-initramfs sources
>>initramfs.conf, removes busybox binary from initramfs if existent,
>>and copies bin/busybox to initramfs and links all aliases provided
>>by busybox to it.
> 
> This is actually called zz-busybox, and is part of busybox.  Somehow I
> failed to notice this exists. :-/
> 
>> I don't understand the following:
>>
>> What's the purpose of /usr/share/initramfs-tools/hooks/busybox at all,
>> if changes are reverted by
>> /usr/share/initramfs-tools/hooks/zz-busybox-initramfs later on anyway
>> and redone in a slightly different fashion?
> 
> Yes, this is stupid.  We should arrange to properly hand over
> responsibility for installing busybox, and adjust package dependencies
> accordingly.

Ack.

> 
>> Why does /usr/share/initramfs-tools/hooks/zz-busybox-initramfs source
>> initramfs.conf? The BUSYBOY variable is exported by mkinitramfs anyway.
>>
>> The simplest fix to this bug would be to stop sourcing initramfs.conf in
>> hooks/zz-busybox-initramfs.
> 
> It should certainly stop doing that.

This is about the bug in busybox: stop sourcing initramfs.conf from the
zz-busybox initramfs hook.

> [...]
>>> b/ /usr/share/initramfs-tools/conf-hooks.d/cryptsetup drops the
>>> BUSYBOX=y line. And if this is not an option, because cryptsetup
>>> requires busybox, then this should be reflected in the package
>>> dependencies accordingly by making the Recommends a Depends.
>>
>> Do you think that the cryptsetup packages should depend on
>> initramfs-tools and busybox despite the fact that they're usable without?
> 
> No, they should only recommend them.   The busybox hook script is
> changed in initramfs-tools 0.121~rc2 to hard fail if busybox is wanted
> but not installed.  If it's dropped in favour of the zz-busybox hook
> script, then I can move that check into mkinitramfs.

So indeed the check needs to be moved to mkinitramfs as soon as
responsibility for installing busybox is handed over to the busybox
package itself.

Am 27.12.2015 um 14:21 schrieb Michael Biebl:
> Am 25.12.2015 um 14:46 schrieb Jonas Meurer:
>> Yes, cryptsetup initramfs scripts do depend on busybox. At least this
>> was the case some years ago.
>>
>> As cryptsetup can be used without initramfs (e.g. only home
>> partition or removable storage encrypted), the cryptsetup package
>> doesn't depend on "initramfs-tools, busybox" but merely recommends
>> them.
>
> If you want to cleanly support those two different use cases, it looks
> like the cleanest solution would be, to ship the initramfs integration
> in a separate binary package, say cryptsetup-initramfs-tools.
>
> This subpackage would have a strict dependency on initramfs-tools and
> busybox. The main cryptsetup package could have a recommends on that
> subpackage.

This part is about the cryptsetup package itself: it is suggested to
split the initramfs stuff out into a seperate binary package (I prefer
the name 'cryptsetup-initramfs'). This is a wishlist bug.

Cheers,
 jonas




signature.asc
Description: OpenPGP digital signature

Bug#809815: [feature request] linux-image-4.3.0-1-sparc64-smp: tpm random module for linux LDOMs

[Ben Hutchings]

On Wed, 2016-01-06 at 23:13 +0300, Anatoly Pugachev wrote:
[...]
> Sorry for wrong feature request, please close this bug as non-valid. Thanks.

I don't mind keeping it open if you're still hoping to get more
information.

Ben.

-- 
Ben Hutchings
Life would be so much easier if we could look at the source code.


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

linux_3.16.7-ckt20-1+deb8u2_multi.changes ACCEPTED into proposed-updates->stable-new, proposed-updates

[Debian FTP Masters]

Accepted:

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sat, 02 Jan 2016 03:31:39 +
Source: linux
Binary: linux-source-3.16 linux-doc-3.16 linux-manual-3.16 
linux-support-3.16.0-4 linux-libc-dev linux-headers-3.16.0-4-all 
linux-headers-3.16.0-4-all-alpha kernel-image-3.16.0-4-alpha-generic-di 
nic-modules-3.16.0-4-alpha-generic-di 
nic-wireless-modules-3.16.0-4-alpha-generic-di 
nic-shared-modules-3.16.0-4-alpha-generic-di 
serial-modules-3.16.0-4-alpha-generic-di 
usb-serial-modules-3.16.0-4-alpha-generic-di 
ppp-modules-3.16.0-4-alpha-generic-di pata-modules-3.16.0-4-alpha-generic-di 
cdrom-core-modules-3.16.0-4-alpha-generic-di 
scsi-core-modules-3.16.0-4-alpha-generic-di 
scsi-modules-3.16.0-4-alpha-generic-di 
scsi-common-modules-3.16.0-4-alpha-generic-di 
scsi-extra-modules-3.16.0-4-alpha-generic-di 
loop-modules-3.16.0-4-alpha-generic-di btrfs-modules-3.16.0-4-alpha-generic-di 
ext4-modules-3.16.0-4-alpha-generic-di isofs-modules-3.16.0-4-alpha-generic-di 
jfs-modules-3.16.0-4-alpha-generic-di xfs-modules-3.16.0-4-alpha-generic-di 
fat-modules-3.16.0-4-alpha-generic-di
 md-modules-3.16.0-4-alpha-generic-di 
multipath-modules-3.16.0-4-alpha-generic-di 
usb-modules-3.16.0-4-alpha-generic-di 
usb-storage-modules-3.16.0-4-alpha-generic-di 
fb-modules-3.16.0-4-alpha-generic-di input-modules-3.16.0-4-alpha-generic-di 
event-modules-3.16.0-4-alpha-generic-di mouse-modules-3.16.0-4-alpha-generic-di 
nic-pcmcia-modules-3.16.0-4-alpha-generic-di 
pcmcia-modules-3.16.0-4-alpha-generic-di 
nic-usb-modules-3.16.0-4-alpha-generic-di 
sata-modules-3.16.0-4-alpha-generic-di core-modules-3.16.0-4-alpha-generic-di 
crc-modules-3.16.0-4-alpha-generic-di crypto-modules-3.16.0-4-alpha-generic-di 
crypto-dm-modules-3.16.0-4-alpha-generic-di 
ata-modules-3.16.0-4-alpha-generic-di nbd-modules-3.16.0-4-alpha-generic-di 
squashfs-modules-3.16.0-4-alpha-generic-di 
virtio-modules-3.16.0-4-alpha-generic-di zlib-modules-3.16.0-4-alpha-generic-di 
fuse-modules-3.16.0-4-alpha-generic-di srm-modules-3.16.0-4-alpha-generic-di 
linux-headers-3.16.0-4-common
 linux-image-3.16.0-4-alpha-generic linux-headers-3.16.0-4-alpha-generic 
linux-image-3.16.0-4-alpha-smp linux-headers-3.16.0-4-alpha-smp 
linux-headers-3.16.0-4-all-amd64 kernel-image-3.16.0-4-amd64-di 
nic-modules-3.16.0-4-amd64-di nic-wireless-modules-3.16.0-4-amd64-di 
nic-shared-modules-3.16.0-4-amd64-di serial-modules-3.16.0-4-amd64-di 
usb-serial-modules-3.16.0-4-amd64-di ppp-modules-3.16.0-4-amd64-di 
pata-modules-3.16.0-4-amd64-di cdrom-core-modules-3.16.0-4-amd64-di 
firewire-core-modules-3.16.0-4-amd64-di scsi-core-modules-3.16.0-4-amd64-di 
scsi-modules-3.16.0-4-amd64-di scsi-common-modules-3.16.0-4-amd64-di 
scsi-extra-modules-3.16.0-4-amd64-di loop-modules-3.16.0-4-amd64-di 
btrfs-modules-3.16.0-4-amd64-di ext4-modules-3.16.0-4-amd64-di 
isofs-modules-3.16.0-4-amd64-di jfs-modules-3.16.0-4-amd64-di 
ntfs-modules-3.16.0-4-amd64-di xfs-modules-3.16.0-4-amd64-di 
fat-modules-3.16.0-4-amd64-di md-modules-3.16.0-4-amd64-di 
multipath-modules-3.16.0-4-amd64-di
 usb-modules-3.16.0-4-amd64-di usb-storage-modules-3.16.0-4-amd64-di 
pcmcia-storage-modules-3.16.0-4-amd64-di fb-modules-3.16.0-4-amd64-di 
input-modules-3.16.0-4-amd64-di event-modules-3.16.0-4-amd64-di 
mouse-modules-3.16.0-4-amd64-di nic-pcmcia-modules-3.16.0-4-amd64-di 
pcmcia-modules-3.16.0-4-amd64-di nic-usb-modules-3.16.0-4-amd64-di 
sata-modules-3.16.0-4-amd64-di core-modules-3.16.0-4-amd64-di 
acpi-modules-3.16.0-4-amd64-di i2c-modules-3.16.0-4-amd64-di 
crc-modules-3.16.0-4-amd64-di crypto-modules-3.16.0-4-amd64-di 
crypto-dm-modules-3.16.0-4-amd64-di efi-modules-3.16.0-4-amd64-di 
ata-modules-3.16.0-4-amd64-di mmc-core-modules-3.16.0-4-amd64-di 
mmc-modules-3.16.0-4-amd64-di nbd-modules-3.16.0-4-amd64-di 
squashfs-modules-3.16.0-4-amd64-di speakup-modules-3.16.0-4-amd64-di 
virtio-modules-3.16.0-4-amd64-di uinput-modules-3.16.0-4-amd64-di 
sound-modules-3.16.0-4-amd64-di hyperv-modules-3.16.0-4-amd64-di 
udf-modules-3.16.0-4-amd64-di fuse-modules-3.16.0-4-amd64-di
 linux-image-3.16.0-4-amd64 linux-headers-3.16.0-4-amd64 
linux-image-3.16.0-4-amd64-dbg xen-linux-system-3.16.0-4-amd64 
linux-headers-3.16.0-4-all-arm64 kernel-image-3.16.0-4-arm64-di 
nic-modules-3.16.0-4-arm64-di nic-wireless-modules-3.16.0-4-arm64-di 
nic-shared-modules-3.16.0-4-arm64-di ppp-modules-3.16.0-4-arm64-di 
cdrom-core-modules-3.16.0-4-arm64-di scsi-core-modules-3.16.0-4-arm64-di 
scsi-modules-3.16.0-4-arm64-di loop-modules-3.16.0-4-arm64-di 
btrfs-modules-3.16.0-4-arm64-di ext4-modules-3.16.0-4-arm64-di 
isofs-modules-3.16.0-4-arm64-di jfs-modules-3.16.0-4-arm64-di 
xfs-modules-3.16.0-4-arm64-di fat-modules-3.16.0-4-arm64-di 
md-modules-3.16.0-4-arm64-di multipath-modules-3.16.0-4-arm64-di 
usb-modules-3.16.0-4-arm64-di usb-storage-modules-3.16.0-4-arm64-di 
input-modules-3.16.0-4-arm64-di event-modules-3.16.0-4-arm64-di 
nic-usb-modules-3.16.0-4-arm64-di sata-modules-3.16.0-4-arm64-di 

Bug#810129: linux-source-4.3 and linux-grsec-source-4.3: error when trying to install together

[Ralf Treinen]

Package: linux-grsec-source-4.3,linux-source-4.3
Version: linux-grsec-source-4.3/4.3.3-5+grsec201512282134+1
Version: linux-source-4.3/4.3.3-5
Severity: serious
User: trei...@debian.org
Usertags: edos-file-overwrite

Date: 2016-01-06
Architecture: amd64
Distribution: sid

Hi,

automatic installation tests of packages that share a file and at the
same time do not conflict by their package dependency relationships has
detected the following problem:


Selecting previously unselected package xz-utils.
(Reading database ... 10940 files and directories currently installed.)
Preparing to unpack .../xz-utils_5.1.1alpha+20120614-2.1_amd64.deb ...
Unpacking xz-utils (5.1.1alpha+20120614-2.1) ...
Selecting previously unselected package binutils.
Preparing to unpack .../binutils_2.25.90.20160101-1_amd64.deb ...
Unpacking binutils (2.25.90.20160101-1) ...
Selecting previously unselected package linux-grsec-source-4.3.
Preparing to unpack 
.../linux-grsec-source-4.3_4.3.3-5+grsec201512282134+1_all.deb ...
Unpacking linux-grsec-source-4.3 (4.3.3-5+grsec201512282134+1) ...
Selecting previously unselected package linux-source-4.3.
Preparing to unpack .../linux-source-4.3_4.3.3-5_all.deb ...
Unpacking linux-source-4.3 (4.3.3-5) ...
dpkg: error processing archive 
/var/cache/apt/archives/linux-source-4.3_4.3.3-5_all.deb (--unpack):
 trying to overwrite '/usr/src/linux-source-4.3.tar.xz', which is also in 
package linux-grsec-source-4.3 4.3.3-5+grsec201512282134+1
dpkg-deb: error: subprocess paste was killed by signal (Broken pipe)
Processing triggers for man-db (2.7.5-1) ...
Errors were encountered while processing:
 /var/cache/apt/archives/linux-source-4.3_4.3.3-5_all.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)


This is a serious bug as it makes installation fail, and violates
sections 7.6.1 and 10.1 of the policy. An optimal solution would
consist in only one of the packages installing that file, and renaming
or removing the file in the other package. Depending on the
circumstances you might also consider Replace relations or file
diversions. If the conflicting situation cannot be resolved then, as a
last resort, the two packages have to declare a mutual
Conflict. Please take into account that Replaces, Conflicts and
diversions should only be used when packages provide different
implementations for the same functionality.

Here is a list of files that are known to be shared by both packages
(according to the Contents file for sid/amd64, which may be
slightly out of sync):

  /usr/src/linux-source-4.3.tar.xz

This bug has been filed against both packages. If you, the maintainers of
the two packages in question, have agreed on which of the packages will
resolve the problem please reassign the bug to that package. You may then
also register in the BTS that the other package is affected by the bug.

-Ralf.

PS: for more information about the detection of file overwrite errors
of this kind see http://qa.debian.org/dose/file-overwrites.html.

Bug#810120: linux-image-3.16.0-4-amd64: i915 drm, dualscreen, FIFO underrun, kernel call trace

[Hans Meiser]

Some more details:

* the distorted X11 screen on output LVDS1 seems only to happen with
simple window-managers like fvwm2 and jwm, but not with a
desktop-environment xfce.

This is bad because I have not found a replacement for fvwm2, which is
as configurable like fvwm2. I use fvwm2 constantly.

* Also this Problem occures, when using VGA1 instead of DP1. :(

Regards.


2016-01-06 16:40 GMT+01:00, x201-user :
> Package: src:linux
> Version: 3.16.7-ckt20-1+deb8u2
> Severity: important
>
> Dear Maintainer,
>
> ** What led up to the situation?
> Installing a plain debian jessie on a Laptop Lenovo X201,
> connecting a external screen and
> boot the system.
>
>
> ** How to reproduce on running system:
> 1.) enable second screen
> xrandr --output LVDS1 --auto --primary --output DP1 --auto --above LVDS1
> 2.) Switch screens via dpms to off
> xset dpms force off
> 3.) move mouse to awake screens and look into dmesg to see kernel call
> trace
>  ...

Processed: Re: Bug#810129: linux-source-4.3 and linux-grsec-source-4.3: error when trying to install together

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 linux-grsec-source-4.3
Bug #810129 [linux-grsec-source-4.3,linux-source-4.3] linux-source-4.3 and 
linux-grsec-source-4.3: error when trying to install together
Bug reassigned from package 'linux-grsec-source-4.3,linux-source-4.3' to 
'linux-grsec-source-4.3'.
Ignoring request to alter found versions of bug #810129 to the same values 
previously set
Ignoring request to alter fixed versions of bug #810129 to the same values 
previously set

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

Bug#809815: [feature request] linux-image-4.3.0-1-sparc64-smp: tpm random module for linux LDOMs

[Anatoly Pugachev]

On Wed, Jan 6, 2016 at 5:21 PM, Anatoly Pugachev  wrote:
> On Wed, Jan 6, 2016 at 5:24 AM, Ben Hutchings  wrote:
>> Control: tag -1 moreinfo
>>
>> On Mon, 2016-01-04 at 13:48 +0300, Anatoly Pugachev wrote:
>>> Package: src:linux
>>> Version: 4.3.3-2
>>> Severity: wishlist
>>>
>>> Dear Maintainer,
>>>
>>> Can you please enable CONFIG_TCG_TPM (TPM security chip) and
>>> CONFIG_HW_RANDOM_TPM linux kernel config options (as modules), to
>>> enable hardware RNG device for use in LDOM (containers) of debian
>>> sparc64.
>>>
>>> Right now, there's no hardware RNG provider is available :
>> [...]
>>
>> Both of those are generic TPM code and won't help you without a driver
>> for the specific TPM that's present in LDOMs.
>>
>> I can't find any hint in the kernel source of which driver is needed
>> for an LDOM, even in the UEK patched source, so perhaps it is out-of-
>> tree?
>
> Ben, well,
>
> I'm going to build a generic (vanilla) kernel with this CONFIGs and
> test how it would work. Going to report back soon. Thanks.

Ben,

you was right, this modules does not help.

root@deb4g:/home/mator# lsmod | grep rng
tpm_rng 1020  0
n2_rng  6878  0
rng_core8172  2 n2_rng,tpm_rng
root@deb4g:/home/mator# cat /sys/class/misc/hw_random/rng_available
tpm-rng

rngd still gives error:

root@deb4g:/home/mator# rngd -f -r /dev/hwrng
error reading from entropy source:: No such device

I don't know, but I probably should report to upstream kernel
bugzilla, about n2_rng, that it does not work.
Openbsd says [1] it does support it (starting from T1 and T2 processors),
Solaris says [2] it does support it (from T2 till M6 processors,
including this machine T5 cpu)

running show-devs from openboot console for this LDOM, i can see
random-number-generator device is being present:

{0} ok show-devs
/cpu@3
/cpu@2
/cpu@1
/cpu@0
/virtual-devices@100
/reboot-memory@0
/iscsi-hba
/virtual-memory
/memory@m0,3000
/aliases
/options
/openprom
/chosen
/packages
/virtual-devices@100/channel-devices@200
/virtual-devices@100/console@1
/virtual-devices@100/random-number-generator@e
/virtual-devices@100/flashprom@0
/virtual-devices@100/channel-devices@200/virtual-domain-service@0
/virtual-devices@100/channel-devices@200/pciv-communication@0
/virtual-devices@100/channel-devices@200/disk@1
/virtual-devices@100/channel-devices@200/disk@0
/virtual-devices@100/channel-devices@200/network@0
/iscsi-hba/disk
/openprom/client-services
/packages/vnet-helper-pkg
/packages/vdisk-helper-pkg
/packages/obp-tftp
/packages/kbd-translator
/packages/SUNW,asr
/packages/dropins
/packages/terminal-emulator
/packages/disk-label
/packages/deblocker
/packages/SUNW,builtin-drivers
{0} ok

but n2_rng does not see it. I'm going to test a more recent kernel,
instead of 4.1.15. The choice of old 4.1.15 kernel to test, was
because oracle sparc linux is using 4.1.8, and i wanted to test it
first. Compiling 4.4rc8 right now...

Searching on the web, found [3], where cpu is T4 and 4.3.0 kernel, but
n2rng gives more messages on boot.

Sorry for wrong feature request, please close this bug as non-valid. Thanks.

1. http://undeadly.org/cgi?action=article=20090201164147
2. http://prsync.com/oracle/solaris-random-number-generation-570469/
3. https://lkml.org/lkml/2015/10/30/678

Bug#810129: linux-source-4.3 and linux-grsec-source-4.3: error when trying to install together

[Yves-Alexis Perez]

control: reassign -1 linux-grsec-source-4.3
On mer., 2016-01-06 at 19:54 +0100, Ralf Treinen wrote:
> Here is a list of files that are known to be shared by both packages
> (according to the Contents file for sid/amd64, which may be
> slightly out of sync):
> 
>   /usr/src/linux-source-4.3.tar.xz
> 
> This bug has been filed against both packages. If you, the maintainers of
> the two packages in question, have agreed on which of the packages will
> resolve the problem please reassign the bug to that package. You may then
> also register in the BTS that the other package is affected by the bug.

Indeed, it's a problem in linux-grsec, I'll fix it for the next upload.

Regards,
-- 
Yves-Alexis



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