Bug#868556: linux-image-4.9.0-3-amd64: xHCI host not responding to stop endpoint command

[Lukas Fisch]

Package: src:linux
Version: 4.9.30-2+deb9u2
Severity: important

Dear Maintainer,

Having an external USB3 drive connected (/dev/sdd1) and copying data from it 
over an USB3 slot to an internal drive. Transfer rates are approx. 110MBytes/s.
Transfer fails after some minutes with "xHCI host not responding to stop 
endpoint command"
Excerpt from 'dmesg':
[  571.719939] xhci_hcd :03:00.0: xHCI host not responding to stop endpoint 
command.
[  571.719942] xhci_hcd :03:00.0: Assuming host is dying, halting host.
[  571.719973] xhci_hcd :03:00.0: HC died; cleaning up
[  571.720994] usb 3-4: USB disconnect, device number 2
[  571.736125] sd 5:0:0:0: [sdd] tag#0 FAILED Result: hostbyte=DID_NO_CONNECT 
driverbyte=DRIVER_OK
[  571.736130] sd 5:0:0:0: [sdd] tag#0 CDB: Read(10) 28 00 06 23 bb f0 00 02 00 
00
Only reboot recovers USB3 functionality. However, the issue is reproducible.

Transferring the data via USB2 slot instead works flawlessly.


-- Package-specific info:
** Version:
Linux version 4.9.0-3-amd64 (debian-kernel@lists.debian.org) (gcc version 6.3.0 
20170516 (Debian 6.3.0-18) ) #1 SMP Debian 4.9.30-2+deb9u2 (2017-06-26)

** Command line:
BOOT_IMAGE=/boot/vmlinuz-4.9.0-3-amd64 
root=UUID=5f4f17ee-e761-438f-9db6-17733a191579 ro quiet

** Tainted: PO (4097)
 * Proprietary module has been loaded.
 * Out-of-tree module has been loaded.

** Kernel log:
[8.231250] ata4: SATA link down (SStatus 0 SControl 300)
[8.231289] ata3: SATA link down (SStatus 0 SControl 300)
[8.231678] ata2.00: ATA-10: WDC WD40EFRX-68N32N0, 82.00A82, max UDMA/133
[8.231680] ata2.00: 7814037168 sectors, multi 16: LBA48 NCQ (depth 31/32), 
AA
[8.231849] ata1.00: ATA-10: WDC WD40EFRX-68N32N0, 82.00A82, max UDMA/133
[8.231851] ata1.00: 7814037168 sectors, multi 16: LBA48 NCQ (depth 31/32), 
AA
[8.232544] ata2.00: configured for UDMA/133
[8.232592] ata1.00: configured for UDMA/133
[8.232986] scsi 1:0:0:0: Direct-Access ATA  WDC WD40EFRX-68N 0A82 
PQ: 0 ANSI: 5
[8.274909] Console: switching to colour frame buffer device 128x48
[8.300909] ast :02:00.0: fb0: astdrmfb frame buffer device
[8.336224] [drm] Initialized ast 0.1.0 20120228 for :02:00.0 on minor 0
[8.336564] sd 1:0:0:0: Attached scsi generic sg1 type 0
[8.336999] scsi 2:0:0:0: Direct-Access ATA  WDC WD40EFRX-68N 0A82 
PQ: 0 ANSI: 5
[8.337270] sd 1:0:0:0: [sdb] 7814037168 512-byte logical blocks: (4.00 
TB/3.64 TiB)
[8.337273] sd 1:0:0:0: [sdb] 4096-byte physical blocks
[8.337363] sd 1:0:0:0: [sdb] Write Protect is off
[8.337366] sd 1:0:0:0: [sdb] Mode Sense: 00 3a 00 00
[8.337404] sd 1:0:0:0: [sdb] Write cache: enabled, read cache: enabled, 
doesn't support DPO or FUA
[8.360424] igb :00:14.0: added PHC on eth0
[8.360427] igb :00:14.0: Intel(R) Gigabit Ethernet Network Connection
[8.360500] igb :00:14.0: eth0: PBA No: 010A00-000
[8.360503] igb :00:14.0: Using MSI-X interrupts. 8 rx queue(s), 8 tx 
queue(s)
[8.386453] random: crng init done
[8.397646]  sdb: sdb1 sdb9
[8.398721] sd 1:0:0:0: [sdb] Attached SCSI removable disk
[8.400459] sd 2:0:0:0: [sdc] 7814037168 512-byte logical blocks: (4.00 
TB/3.64 TiB)
[8.400462] sd 2:0:0:0: [sdc] 4096-byte physical blocks
[8.400530] sd 2:0:0:0: Attached scsi generic sg2 type 0
[8.400588] sd 2:0:0:0: [sdc] Write Protect is off
[8.400591] sd 2:0:0:0: [sdc] Mode Sense: 00 3a 00 00
[8.400633] sd 2:0:0:0: [sdc] Write cache: enabled, read cache: enabled, 
doesn't support DPO or FUA
[8.445692]  sdc: sdc1 sdc9
[8.446616] sd 2:0:0:0: [sdc] Attached SCSI removable disk
[8.553136] usb 3-4: new SuperSpeed USB device number 2 using xhci_hcd
[8.578510] usb 3-4: New USB device found, idVendor=0bc2, idProduct=a013
[8.578513] usb 3-4: New USB device strings: Mfr=2, Product=3, SerialNumber=1
[8.578515] usb 3-4: Product: Backup+ BK
[8.578517] usb 3-4: Manufacturer: Seagate
[8.578519] usb 3-4: SerialNumber: NA51994Z
[8.580472] usb-storage 3-4:1.0: USB Mass Storage device detected
[8.580587] usb-storage 3-4:1.0: Quirks match for vid 0bc2 pid a013: 200
[8.580620] scsi host5: usb-storage 3-4:1.0
[8.593144] spl: loading out-of-tree module taints kernel.
[8.598606] SPL: Loaded module v0.6.5.9-1
[8.606700] znvpair: module license 'CDDL' taints kernel.
[8.606702] Disabling lock debugging due to kernel taint
[8.737196] igb :00:14.1: added PHC on eth1
[8.737200] igb :00:14.1: Intel(R) Gigabit Ethernet Network Connection
[8.737273] igb :00:14.1: eth1: PBA No: 010A00-000
[8.737275] igb :00:14.1: Using MSI-X interrupts. 8 rx queue(s), 8 tx 
queue(s)
[8.830651] ZFS: Loaded module v0.6.5.9-5, ZFS pool version 5000, ZFS 
filesystem version 5
[9.121108] igb :00:14.2: added PHC on eth2
[9.12] igb :00:14.2: Intel(R) Gigabit Ethernet Network Connection
[9.121184] igb :00:14.2: eth2: 

Processing of linux-latest_82~bpo9+1_multi.changes

[Debian FTP Masters]

linux-latest_82~bpo9+1_multi.changes uploaded successfully to localhost
along with the files:
  linux-latest_82~bpo9+1.dsc
  linux-latest_82~bpo9+1.tar.xz
  linux-latest_82~bpo9+1_source.buildinfo
  linux-doc_4.11+82~bpo9+1_all.deb
  linux-perf_4.11+82~bpo9+1_all.deb
  linux-source_4.11+82~bpo9+1_all.deb

Greetings,

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

Processed: Re: Not a kernel bug

[Debian Bug Tracking System]

Processing control commands:

> forwarded -1 https://bugzilla.kernel.org/show_bug.cgi?id=191201
Bug #867124 [src:linux] linux-image-4.9.0-3-amd64: crash if LRO / rx-mini is 
enabled with vmxnet3 on ESXi 6.5
Set Bug forwarded-to-address to 
'https://bugzilla.kernel.org/show_bug.cgi?id=191201'.
> severity -1 important
Bug #867124 [src:linux] linux-image-4.9.0-3-amd64: crash if LRO / rx-mini is 
enabled with vmxnet3 on ESXi 6.5
Severity set to 'important' from 'critical'
> tag -1 wontfix
Bug #867124 [src:linux] linux-image-4.9.0-3-amd64: crash if LRO / rx-mini is 
enabled with vmxnet3 on ESXi 6.5
Added tag(s) wontfix.

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

Processed: Re: Bug#862723: closed by Ben Hutchings <b...@decadent.org.uk> (Bug#862723: fixed in linux 4.9.30-1)

[Debian Bug Tracking System]

Processing control commands:

> reopen -1
Bug #862723 {Done: Ben Hutchings } [src:linux] Touchpad 
and keyboard are not detected on Acer Chromebook 14 with kernel 4.9
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions linux/4.9.30-1.

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

Bug#862723: closed by Ben Hutchings <b...@decadent.org.uk> (Bug#862723: fixed in linux 4.9.30-1)

[Ben Hutchings]

Control: reopen -1

On Sun, 2017-06-25 at 10:07 -0700, Data Bot wrote:
> Hello,
> 
> Thank you for finding that cherryview kernel issue. Unfortunately, their
> original patch is very limited as it's tied to an arbitrary BIOS date and
> doesn't work for my machine. Would it be possible to also include better
> quirk that went into 4.12? Please see v2 quirk in 194945 or
> https://github.com/torvalds/linux/commit/2a8209fa68236ad65363dba03db5dbced520268a

Sorry about that.  I'll add this patch too.

Ben.

-- 
Ben Hutchings
Experience is directly proportional to the value of equipment
destroyed.
- Carolyn Scheppner



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

linux-latest_82~bpo9+1_multi.changes is NEW

[Debian FTP Masters]

binary:linux-doc is NEW.
binary:linux-headers-4kc-malta is NEW.
binary:linux-headers-5kc-malta is NEW.
binary:linux-headers-686 is NEW.
binary:linux-headers-686-pae is NEW.
binary:linux-headers-amd64 is NEW.
binary:linux-headers-arm64 is NEW.
binary:linux-headers-armmp is NEW.
binary:linux-headers-armmp-lpae is NEW.
binary:linux-headers-loongson-3 is NEW.
binary:linux-headers-marvell is NEW.
binary:linux-headers-octeon is NEW.
binary:linux-headers-powerpc64le is NEW.
binary:linux-headers-rt-686-pae is NEW.
binary:linux-headers-rt-amd64 is NEW.
binary:linux-headers-s390x is NEW.
binary:linux-image-4kc-malta is NEW.
binary:linux-image-4kc-malta-dbg is NEW.
binary:linux-image-5kc-malta is NEW.
binary:linux-image-5kc-malta-dbg is NEW.
binary:linux-image-686 is NEW.
binary:linux-image-686-dbg is NEW.
binary:linux-image-686-pae is NEW.
binary:linux-image-686-pae-dbg is NEW.
binary:linux-image-amd64 is NEW.
binary:linux-image-amd64-dbg is NEW.
binary:linux-image-arm64 is NEW.
binary:linux-image-arm64-dbg is NEW.
binary:linux-image-armmp is NEW.
binary:linux-image-armmp-dbg is NEW.
binary:linux-image-armmp-lpae is NEW.
binary:linux-image-armmp-lpae-dbg is NEW.
binary:linux-image-loongson-3 is NEW.
binary:linux-image-loongson-3-dbg is NEW.
binary:linux-image-marvell is NEW.
binary:linux-image-marvell-dbg is NEW.
binary:linux-image-octeon is NEW.
binary:linux-image-octeon-dbg is NEW.
binary:linux-image-powerpc64le is NEW.
binary:linux-image-powerpc64le-dbg is NEW.
binary:linux-image-rt-686-pae is NEW.
binary:linux-image-rt-686-pae-dbg is NEW.
binary:linux-image-rt-amd64 is NEW.
binary:linux-image-rt-amd64-dbg is NEW.
binary:linux-image-s390x is NEW.
binary:linux-image-s390x-dbg is NEW.
binary:linux-perf is NEW.
binary:linux-source is NEW.
binary:linux-doc is NEW.
binary:linux-source is NEW.
binary:linux-perf is NEW.
source:linux-latest is NEW.

Your package has been put into the NEW queue, which requires manual action
from the ftpteam to process. The upload was otherwise valid (it had a good
OpenPGP signature and file hashes are valid), so please be patient.

Packages are routinely processed through to the archive, and do feel
free to browse the NEW queue[1].

If there is an issue with the upload, you will receive an email from a
member of the ftpteam.

If you have any questions, you may reply to this email.

[1]: https://ftp-master.debian.org/new.html
 or https://ftp-master.debian.org/backports-new.html for *-backports

Bug#868082: linux-image-4.11.0-1-686: fails to boot on i386 (Soekris net5501)

[Ben Hutchings]

Control: tag -1 moreinfo

On Tue, 2017-07-11 at 23:27 +0200, Francesco Poli (wintermute) wrote:
> Package: src:linux
> Version: 4.11.6-1
> Severity: important
> 
> Hello,
> after upgrading an i386 box (Soekris net5501) running testing (buster),
> I found out that the newly migrated Linux kernel fails to boot.
> 
> Looking at the boot through the serial console reveals the following
> few messages:
> 
>   Booting 'Debian GNU/Linux, with Linux 4.11.0-1-686'
> 
>   Loading Linux 4.11.0-1-686 ...
>   Loading initial ramdisk ...
> 
> and then nothing else.
[...]

If you add 'earlyprintk=ttyS0' to the kernel command line and delete
'quiet', does it log anything?

Ben.

-- 
Ben Hutchings
If the facts do not conform to your theory, they must be disposed of.



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

Processed: Re: Bug#868082: linux-image-4.11.0-1-686: fails to boot on i386 (Soekris net5501)

[Debian Bug Tracking System]

Processing control commands:

> tag -1 moreinfo
Bug #868082 [src:linux] linux-image-4.11.0-1-686: fails to boot on i386 
(Soekris net5501)
Added tag(s) moreinfo.

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

Bug#787326: D'Link DWA-130 WiFi adapter Realtek RTL8191SU

[John Legg]

Sorry for filing bug report in wrong place, but having NO WiFi, had to 
barrow another computer to submit this info.

USB WiFi Adapter: D'Link DWA-130
Chip Set: Realtek RTL8191SU
Computer Dell 140g

firmware-realtek_0.43_all on Debian 8, works OK for me

firmware-realtek_20161130-3_all on Debian 9 FAILS
The driver installs, but no networks are found

Processed: Re: Bug#868242: open-vm-tools: VMXNET3 network interface hard locks VM after Vmware hw v8 to hw v13

[Debian Bug Tracking System]

Processing control commands:

> tag -1 moreinfo
Bug #868242 [src:linux] open-vm-tools: VMXNET3 network interface hard locks VM 
after Vmware hw v8 to hw v13
Added tag(s) moreinfo.

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

Bug#867366: installation-reports: Kernel panic: null pointer derefence at (null), first boot after install

[Ben Hutchings]

Control: retitle -1 Null pointer dereference in nvkm_timer_alarm_trigger 
shortly after boot
Control: tag -1 - d-i

I suspect this might be fixed by:

commit aae14f569f5dbd13f9a7f34db8110e1658ef2c48
Author: Ben Skeggs 
Date:   Mon Jun 5 17:23:32 2017 +1000

drm/nouveau/tmr: fully separate alarm execution/pending lists

commit b4e382ca7586a63b6c1e5221ce0863ff867c2df6 upstream.

which went into 4.9.32.

Ben.

-- 
Ben Hutchings
If the facts do not conform to your theory, they must be disposed of.



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

Bug#868224: linux-image-4.9.0-3-amd64: Upgrade to linux-image-4.9.0-3-amd64 hangs while or after generating initrd

[Ben Hutchings]

Control: reassign -1 src:initramfs-tools 0.130
Control: tag -1 moreinfo

On Thu, 2017-07-13 at 11:17 +0200, Jens Gruentjes wrote:
[...]
> I upgraded to the latest stable kernel via apt-get upgrade. The upgrade
> hangs at the following point:
> 
> linux-image-4.9.0-3-amd64 (4.9.30-2+deb9u2) wird eingerichtet ...
> /etc/kernel/postinst.d/initramfs-tools:
> update-initramfs: Generating /boot/initrd.img-4.9.0-3-amd64
> 
> After waiting a couple of hours I interrupted the upgrade. After that I
> tried dpkg --configure -a or apt-get -f install but the result was
> always the same.
> 
> I trid to build the initrd file manually via
> 
> update-initramfs -u -t
> 
> which worked and created the file /boot/initrd.img-4.9.0-3-amd64
> 
> Another apt-get -f install leads to the same problem that the upgrade
> hangs with 
> 
> /etc/kernel/postinst.d/initramfs-tools:
> update-initramfs: Generating /boot/initrd.img-4.9.0-3-amd64
[...]

Please edit the line 'verbose=0' in /usr/sbin/update-initramfs (near
the bottom) to be 'verbose=1' and then re-run 'dpkg --configure -a'.
This should generate a lot of output but if you send the last, say, 100
lines, I think that should give me a clue where it is getting stuck.

Ben.

-- 
Ben Hutchings
If the facts do not conform to your theory, they must be disposed of.



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

Processed: Re: Bug#868224: linux-image-4.9.0-3-amd64: Upgrade to linux-image-4.9.0-3-amd64 hangs while or after generating initrd

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 src:initramfs-tools 0.130
Bug #868224 [src:linux] linux-image-4.9.0-3-amd64: Upgrade to 
linux-image-4.9.0-3-amd64 hangs while or after generating initrd
Bug reassigned from package 'src:linux' to 'src:initramfs-tools'.
No longer marked as found in versions linux/4.9.30-2+deb9u2.
Ignoring request to alter fixed versions of bug #868224 to the same values 
previously set
Bug #868224 [src:initramfs-tools] linux-image-4.9.0-3-amd64: Upgrade to 
linux-image-4.9.0-3-amd64 hangs while or after generating initrd
Marked as found in versions initramfs-tools/0.130.
> tag -1 moreinfo
Bug #868224 [src:initramfs-tools] linux-image-4.9.0-3-amd64: Upgrade to 
linux-image-4.9.0-3-amd64 hangs while or after generating initrd
Added tag(s) moreinfo.

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

Bug#864642: vmxnet3: Reports suspect GRO implementation on vSphere hosts / one VM crashes

[Ben Hutchings]

Control: tag -1 moreinfo

Sven asked this, but forgot to add you to the recipients:

On Thu, 2017-07-06 at 21:50 +0200, Sven Hartge wrote:
> Hi!
> 
> > Could this be https://bugzilla.kernel.org/show_bug.cgi?id=191201 ?

Note that this has been root-caused as a bug in the virtual device, not
the driver.  (Though it would be nice if the driver could work around
it.)

Ben.

> Try the following, from comment 37 
> https://bugzilla.kernel.org/show_bug.cgi?id=191201#c37
> 
> > In the meantime, suggested workaround:
> >  - disable rx data ring: ethtool -G eth? rx-mini 0
> 
> Also adding "vmxnet3.rev.30 = FALSE" to the vmx file of the VM seems to 
> be needed. https://bugzilla.kernel.org/show_bug.cgi?id=191201#c40
> 
> Also: Which hardware version are you running? It is v10 for me (highest 
> for ESX5.5)

-- 
Ben Hutchings
If the facts do not conform to your theory, they must be disposed of.



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

Processed: Re: Bug#864642: vmxnet3: Reports suspect GRO implementation on vSphere hosts / one VM crashes

[Debian Bug Tracking System]

Processing control commands:

> tag -1 moreinfo
Bug #864642 [src:linux] vmxnet3: Reports suspect GRO implementation on vSphere 
hosts / one VM crashes
Added tag(s) moreinfo.

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

Bug#867634: linux-image-4.9.0-3-amd64: Repeated ESATA softreset failed messages - even after replacing most components.

[Ben Hutchings]

Control: tag -1 moreinfo

On Fri, 2017-07-07 at 21:01 -0400, madsara wrote:
[...]
>    * What exactly did you do (or not do) that was effective (or
>  ineffective)?
>   The following actions have been taken so far, none of which are 
> successful:
>   - Upgraded Dell R210 II's BIOS
>   - Purchased an entirely new Sandisk TowerRAID TR8M+B
>   - Replaced the eSATA card - moving from SIL chipset to Marvell
>   - Replaced all hard drives with brand new 3TB drives.

Did you try replacing the eSATA cables yet?

>   - Upgraded OS from Debian Jessie to Debian Stretch
>   - Ensured BIOS was set for maximum performance and not power saving.
>   - Added noapic, acpi=off, and apm=off kernel parameter options.

These parameters were once useful with old hardware and kernel
versions, but now will usually only make things worse.

>   - Performed a full on-board health check (part of the Dell on-board 
> management abilities), finding no issues.
>   - Performed an extensive memory test, finding no issues.
[...]

Ben.

-- 
Ben Hutchings
If the facts do not conform to your theory, they must be disposed of.



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

Bug#867257: linux: Please update aufs4 patches

[Ben Hutchings]

On Wed, 2017-07-05 at 10:45 +0200, Jan Luca Naumann wrote:
> Source: linux
> Version: 4.11.6-1
> Severity: wishlist
> 
> Hey,
> 
> I'm preparing at the moment the upload of a new version of the aufs
> DKMS package for sid. According to the upstream webpage [1] there was
> a problem with the patches up to 4.11.7.
> 
> Could you apply the newest patches for 4.11.7+ in course of the upload
> of the newest version?

There aren't any necessary changes in the patches applied to the
kernel, but I'll update anyway.

Ben.

-- 
Ben Hutchings
If the facts do not conform to your theory, they must be disposed of.



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

Bug#866337: Help text for kASLR still says it's incompatible with hibernation

[Ben Hutchings]

Control: clone -1 -2
Control: reopen -1
Control: retitle -1 kASLR breaks resume from hibernation on Thinkpad X220i

On Fri, 2017-06-30 at 00:58 +0300, Michael Krylov wrote:
> > This text is incorrect; KASLR and hibernation have been compatible
> > since these changes in Linux 4.8:
> 
> [...]
> 
> That's great news, but, I'm afraid that's only partly true. As I wrote in
> the initial message, my laptop, Lenovo Thinkpad x220i, is unable to wake
> up from hibernation unless nokaslr was added to the kernel options (or
> the kernel was re-compiled to disable it). So this means that on some
> hardware there are still some problems.
> 
> Should I create a new bug or we can reopen this one?

Sorry, I didn't read this closely enough.

I'm moving the documentation issue into a separate bug report and
reopening this one.

Ben.

-- 
Ben Hutchings
Experience is directly proportional to the value of equipment
destroyed.
- Carolyn Scheppner



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

Processed: Re: Bug#866337: Help text for kASLR still says it's incompatible with hibernation

[Debian Bug Tracking System]

Processing control commands:

> clone -1 -2
Bug #866337 {Done: Ben Hutchings } [src:linux] Help text 
for kASLR still says it's incompatible with hibernation
Bug 866337 cloned as bug 868596
> reopen -1
Bug #866337 {Done: Ben Hutchings } [src:linux] Help text 
for kASLR still says it's incompatible with hibernation
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions 4.11-1~exp1.
> retitle -1 kASLR breaks resume from hibernation on Thinkpad X220i
Bug #866337 [src:linux] Help text for kASLR still says it's incompatible with 
hibernation
Changed Bug title to 'kASLR breaks resume from hibernation on Thinkpad X220i' 
from 'Help text for kASLR still says it's incompatible with hibernation'.

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

Processed: severity of 862723 is important, tagging 862723

[Debian Bug Tracking System]

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

> severity 862723 important
Bug #862723 [src:linux] Touchpad and keyboard are not detected on Acer 
Chromebook 14 with kernel 4.9
Severity set to 'important' from 'normal'
> tags 862723 + fixed-upstream patch
Bug #862723 [src:linux] Touchpad and keyboard are not detected on Acer 
Chromebook 14 with kernel 4.9
Added tag(s) patch and fixed-upstream.
> thanks
Stopping processing here.

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

Bug#843448: linux-image-4.8.0-1-armmp-lpae: fails to boot on Odroid-Xu4 with rootfs on USB

[Vagrant Cascadian]

On 2017-07-10, Vagrant Cascadian wrote:
> On 2017-07-08, Steinar H. Gunderson wrote:
>> On Sat, Jul 08, 2017 at 07:50:03AM +0200, Jochen Sprickerhof wrote:
>>> For v4.9 the only patch needed is:
>>> 
>>> https://bugs.debian.org/cgi-bin/bugreport.cgi?att=1;bug=843448;filename=0001-usb-dwc3-core-setup-phy-before-trying-to-read-from-i.patch;msg=97
>>
>> Don't you also want this?
>>
>> https://bugs.debian.org/cgi-bin/bugreport.cgi?att=1;bug=843448;filename=2166ffd004e04a61887eb2a39f8639dc12140c58-updated.diff;msg=75
>
> I've built patched linux 4.9 packages using the above two patches, and
> am running them on several odroid-xu4 boards used in the reproducible
> builds builders, running rootfs and a build partition on USB. So that
> should test USB reasonably well... I'll report if there are any major
> stability issues.

There have been infrequent USB resets, but it usually handles them
successfully:

[500623.473890] scsi host0: uas_eh_bus_reset_handler start
[500623.483176] sd 0:0:0:0: [sda] tag#22 uas_zap_pending 0 uas-tag 23
inflight: CMD
[500623.489235] sd 0:0:0:0: [sda] tag#22 CDB: Write(10) 2a 00 01 a4 51
10 00 00 10 00
[500623.496778] sd 0:0:0:0: [sda] tag#23 uas_zap_pending 0 uas-tag 24
inflight: CMD
[500623.504219] sd 0:0:0:0: [sda] tag#23 CDB: Read(10) 28 00 00 66 59 20
00 00 60 00
[500623.511678] sd 0:0:0:0: [sda] tag#24 uas_zap_pending 0 uas-tag 25
inflight: CMD
[500623.519120] sd 0:0:0:0: [sda] tag#24 CDB: Write(10) 2a 00 04 d4 c1
e8 00 00 18 00
[500623.526667] sd 0:0:0:0: [sda] tag#25 uas_zap_pending 0 uas-tag 26
inflight: CMD
[500623.534112] sd 0:0:0:0: [sda] tag#25 CDB: Read(10) 28 00 00 50 b1 10
00 00 08 00
[500623.541570] sd 0:0:0:0: [sda] tag#26 uas_zap_pending 0 uas-tag 27
inflight: CMD
[500623.549012] sd 0:0:0:0: [sda] tag#26 CDB: Write(10) 2a 00 04 d4 c6
58 00 00 08 00
[500623.556561] sd 0:0:0:0: [sda] tag#27 uas_zap_pending 0 uas-tag 28
inflight: CMD
[500623.564003] sd 0:0:0:0: [sda] tag#27 CDB: Read(10) 28 00 00 66 58 e0
00 00 40 00
[500623.654698] usb 4-1.2: reset SuperSpeed USB device number 3 using
xhci-hcd
[500623.681540] scsi host0: uas_eh_bus_reset_handler success

This is no worse than when running on 4.7.


> I'll also try to switch one of them over to a patched 4.11 or 4.12
> soonish... to make sure there aren't further regressions there.

One of them was running 4.11, and didn't seem any better or worse.


live well,
  vagrant


signature.asc
Description: PGP signature

Bug#867358: mips/mipsel: mips-linux-gnu-gccgo-7: waitid: bad address

[Adrian Bunk]

On Sun, Jul 16, 2017 at 11:21:27PM +0100, Ben Hutchings wrote:
> On Thu, 2017-07-06 at 13:10 +0300, Adrian Bunk wrote:
> > Control: reassign -1 src:linux 4.9.30-2
> > Control: retitle -1 mips/mipsel: mips-linux-gnu-gccgo-7: waitid: bad address
> > Control: affects -1 src:golang-github-pelletier-go-toml 
> > src:golang-github-nicksnyder-go-i18n gccgo-7
> > 
> > On Thu, Jul 06, 2017 at 02:11:00AM +0300, Adrian Bunk wrote:
> > > Source: golang-github-pelletier-go-toml
> > > Version: 1.0.0-1
> > > Severity: serious
> > > 
> > > https://buildd.debian.org/status/package.php?p=golang-github-pelletier-go-toml=sid
> > > 
> > > ...
> > >    dh_auto_test -a -O--buildsystem=golang
> > >   go test -v -p 4 github.com/pelletier/go-toml 
> > > github.com/pelletier/go-toml/cmd 
> > > github.com/pelletier/go-toml/cmd/tomljson 
> > > github.com/pelletier/go-toml/cmd/tomll github.com/pelletier/go-toml/query
> > > go build github.com/davecgh/go-spew/spew: 
> > > /usr/bin/mips-linux-gnu-gccgo-7: waitid: bad address
> > > FAIL  github.com/pelletier/go-toml [build failed]
> > > ?     github.com/pelletier/go-toml/cmd[no test files]
> > > ...
> > 
> > James Cowgill told me that this is actually a kernel bug:
> >   https://www.linux-mips.org/archives/linux-mips/2017-03/msg00580.html
> 
> That's now a 404, strangely.  Did you mean "[PATCH 0/2] Fix indirect
> syscall handler for syscalls with > 4 args"?

Yes, the link pointed at
  [PATCH 2/2] MIPS: Remove pt_regs adjustments in indirect syscall handler

> Ben.

cu
Adrian

-- 

   "Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
   "Only a promise," Lao Er said.
   Pearl S. Buck - Dragon Seed

Bug#867358: mips/mipsel: mips-linux-gnu-gccgo-7: waitid: bad address

[Ben Hutchings]

Control: tag -1 upstream patch

On Sun, 2017-07-16 at 23:21 +0100, Ben Hutchings wrote:
> On Thu, 2017-07-06 at 13:10 +0300, Adrian Bunk wrote:
> > Control: reassign -1 src:linux 4.9.30-2
> > Control: retitle -1 mips/mipsel: mips-linux-gnu-gccgo-7: waitid: bad address
> > Control: affects -1 src:golang-github-pelletier-go-toml 
> > src:golang-github-nicksnyder-go-i18n gccgo-7
> > 
> > On Thu, Jul 06, 2017 at 02:11:00AM +0300, Adrian Bunk wrote:
> > > Source: golang-github-pelletier-go-toml
> > > Version: 1.0.0-1
> > > Severity: serious
> > > 
> > > https://buildd.debian.org/status/package.php?p=golang-github-pelletier-go-toml=sid
> > > 
> > > ...
> > >    dh_auto_test -a -O--buildsystem=golang
> > >   go test -v -p 4 github.com/pelletier/go-toml 
> > > github.com/pelletier/go-toml/cmd 
> > > github.com/pelletier/go-toml/cmd/tomljson 
> > > github.com/pelletier/go-toml/cmd/tomll github.com/pelletier/go-toml/query
> > > go build github.com/davecgh/go-spew/spew: 
> > > /usr/bin/mips-linux-gnu-gccgo-7: waitid: bad address
> > > FAIL  github.com/pelletier/go-toml [build failed]
> > > ?     github.com/pelletier/go-toml/cmd[no test files]
> > > ...
> > 
> > James Cowgill told me that this is actually a kernel bug:
> >   https://www.linux-mips.org/archives/linux-mips/2017-03/msg00580.html
> 
> That's now a 404, strangely.  Did you mean "[PATCH 0/2] Fix indirect
> syscall handler for syscalls with > 4 args"?

James - assuming I guessed correctly above, why is it that the second
patch "MIPS: Remove pt_regs adjustments in indirect syscall handler"
hasn't been applied?  Was this fixed some other way upstream?

Ben.

-- 
Ben Hutchings
If the facts do not conform to your theory, they must be disposed of.


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

Processed: Re: Bug#867358: mips/mipsel: mips-linux-gnu-gccgo-7: waitid: bad address

[Debian Bug Tracking System]

Processing control commands:

> tag -1 upstream patch
Bug #867358 [src:linux] mips/mipsel: mips-linux-gnu-gccgo-7: waitid: bad address
Added tag(s) patch and upstream.

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

Bug#865277: marked as done (Please disable CONFIG_INTEGRITY_TRUSTED_KEYRING)

[Debian Bug Tracking System]

Your message dated Mon, 17 Jul 2017 01:30:59 +0100
with message-id <1500251459.2707.198.ca...@decadent.org.uk>
and subject line Re: Bug#865277: Please disable CONFIG_INTEGRITY_TRUSTED_KEYRING
has caused the Debian Bug report #865277,
regarding Please disable CONFIG_INTEGRITY_TRUSTED_KEYRING
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.)


-- 
865277: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=865277
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: linux
Severity: wishlist

CONFIG_INTEGRITY_TRUSTED_KEYRING is documented as:

   This option requires that all keys added to the .ima and
   .evm keyrings be signed by a key on the system trusted
   keyring.

This means that it's impossible to add keys to the .ima or .evm
keyrings unless those keys are signed by a key in the trusted keyring.
The trusted keyring is defined at compile time as containing only
debian/certs/b...@debian.org.cert.pem, so ima and evm keys can only be
added if they're signed by Debian.

This isn't ideal for a general purpose binary distribution, and
doesn't make a great deal of sense anyway. IMA will do nothing by
default unless a policy is configured at boot time, which means that
it requires a trusted boot chain that will load the initial IMA
policy. It's reasonable to assert that anything trusted to load policy
should also be trusted to load the initial trusted keyset.

Userspace has two choices: they can either add raw keys to the IMA
keyring and then lock it down so new keys can't be added, or they can
create a new keyring containing the trusted certificate chain and lock
it down, and then restrict the IMA keyring with
KEYCTL_RESTRICT_KEYRING such that it will only load keys signed by
keys in the new trusted keyring. The second case is equivalent to the
behaviour where CONFIG_INTEGRITY_TRUSTED_KEYRING is enabled, except
that a trusted keyring under user control is used rather than one
under Debian's control. This allows the local admin to decide which
keys they trust, whereas right now Debian is the only organisation
able to make that decision for the user.
--- End Message ---
--- Begin Message ---
On Tue, 2017-06-20 at 10:48 +0200, Matthew Garrett wrote:
[...]
> This isn't ideal for a general purpose binary distribution, and
> doesn't make a great deal of sense anyway. IMA will do nothing by
> default unless a policy is configured at boot time, which means that
> it requires a trusted boot chain that will load the initial IMA
> policy. It's reasonable to assert that anything trusted to load policy
> should also be trusted to load the initial trusted keyset.
[...]

We never really enabled it, since we didn't enable
CONFIG_INTEGRITY_SIGNATURE which it depends on.  However, I will delete
it from the config fragment in the source package now.

Ben.

-- 
Ben Hutchings
Experience is directly proportional to the value of equipment
destroyed.
- Carolyn Scheppner


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

Processed: Re: Bug#868352: linux: Please enable USB_SERIAL_CONSOLE

[Debian Bug Tracking System]

Processing control commands:

> severity -1 wishlist
Bug #868352 [src:linux] linux: Please enable USB_SERIAL_CONSOLE
Severity set to 'wishlist' from 'normal'
> tag -1 wontfix
Bug #868352 [src:linux] linux: Please enable USB_SERIAL_CONSOLE
Added tag(s) wontfix.

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

Bug#868352: linux: Please enable USB_SERIAL_CONSOLE

[Ben Hutchings]

Control: severity -1 wishlist
Control: tag -1 wontfix

On Fri, 2017-07-14 at 20:34 +0200, Sascha Silbe wrote:
> Source: linux
> Version: 4.11.6-1
> Severity: normal
> 
> Dear Maintainer,
> 
> on some amd64 systems no native or PCI(e) serial ports are available
> resp. possible. USB serial adapters are the only option to get a
> serial console for debugging boot problems in this case. Unfortunately
> the Debian amd64 kernels are built with USB_SERIAL_CONSOLE unset
> (because USB_SERIAL is not built-in) so even that option isn't
> available. When the BIOS text mode isn't working (e.g. high-res
> monitor with a BIOS that only supports up to FullHD) one is left
> without any working console device.
[...]

I think this case is too unusual to make it worth building in all the
USB stuff needed to make this work on all x86 systems.

Ben.

-- 
Ben Hutchings
If the facts do not conform to your theory, they must be disposed of.



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

Processed: Re: installation-reports: Kernel panic: null pointer derefence at (null), first boot after install

[Debian Bug Tracking System]

Processing control commands:

> retitle -1 Null pointer dereference in nvkm_timer_alarm_trigger shortly after 
> boot
Bug #867366 [src:linux] installation-reports: Kernel panic: null pointer 
derefence at (null), first boot after install
Changed Bug title to 'Null pointer dereference in nvkm_timer_alarm_trigger 
shortly after boot' from 'installation-reports: Kernel panic: null pointer 
derefence at (null), first boot after install'.
> tag -1 - d-i
Bug #867366 [src:linux] Null pointer dereference in nvkm_timer_alarm_trigger 
shortly after boot
Removed tag(s) d-i.

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

Processed: severity of 867595 is important

[Debian Bug Tracking System]

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

> severity 867595 important
Bug #867595 [src:linux] nfs-kernel-server: nfsd freezes if underlying ext4 file 
system becomes full
Severity set to 'important' from 'critical'
> thanks
Stopping processing here.

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

Processed: reassign 867595 to src:linux

[Debian Bug Tracking System]

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

> reassign 867595 src:linux 3.16.43-2
Bug #867595 [nfs-kernel-server] nfs-kernel-server: nfsd freezes if underlying 
ext4 file system becomes full
Bug reassigned from package 'nfs-kernel-server' to 'src:linux'.
No longer marked as found in versions nfs-utils/1:1.2.8-9.
Ignoring request to alter fixed versions of bug #867595 to the same values 
previously set
Bug #867595 [src:linux] nfs-kernel-server: nfsd freezes if underlying ext4 file 
system becomes full
Marked as found in versions linux/3.16.43-2.
> thanks
Stopping processing here.

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

Processed: Re: Bug#867634: linux-image-4.9.0-3-amd64: Repeated ESATA softreset failed messages - even after replacing most components.

[Debian Bug Tracking System]

Processing control commands:

> tag -1 moreinfo
Bug #867634 [src:linux] linux-image-4.9.0-3-amd64: Repeated ESATA softreset 
failed messages - even after replacing most components.
Bug #867636 [src:linux] linux-image-4.9.0-3-amd64: Repeated ESATA softreset 
failed messages - even after replacing most components.
Added tag(s) moreinfo.
Added tag(s) moreinfo.

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

Processed: severity of 868251 is important

[Debian Bug Tracking System]

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

> severity 868251 important
Bug #868251 [src:linux] dm-raid.ko not included in md-modules udeb
Severity set to 'important' from 'normal'
> thanks
Stopping processing here.

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

Bug#868242: open-vm-tools: VMXNET3 network interface hard locks VM after Vmware hw v8 to hw v13

[Ben Hutchings]

Control: tag -1 moreinfo

On Thu, 13 Jul 2017 17:55:40 +0200 Bernd Zeimetz  wrote:
> reassign 868242 src:linux
> thanks
> 
> hi,
> 
> open-vm-tools has pretty much nothing to do with the vmxnet3 module.
> The module is shipped with the kernel.
> 
> Therefore I'll reassign this bug to the kernel.
> 
> Also you should open a case at vmware, they maintain the kernel
> modules upstream and they are the only people who can debug this issue.
[...]

This actually sounds a bit like an ESX bug:
https://bugzilla.kernel.org/show_bug.cgi?id=191201

Can you check whether either of the workarounds works for you? 
Apparently you can put this in the VMSS file:

vmxnet3.rev.30 = FALSE

or run this in the guest, substituting the network interface name:

ethtool -G  rx-mini 0

Ben.

-- 
Ben Hutchings
If the facts do not conform to your theory, they must be disposed of.


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

Bug#867358: mips/mipsel: mips-linux-gnu-gccgo-7: waitid: bad address

[Ben Hutchings]

On Thu, 2017-07-06 at 13:10 +0300, Adrian Bunk wrote:
> Control: reassign -1 src:linux 4.9.30-2
> Control: retitle -1 mips/mipsel: mips-linux-gnu-gccgo-7: waitid: bad address
> Control: affects -1 src:golang-github-pelletier-go-toml 
> src:golang-github-nicksnyder-go-i18n gccgo-7
> 
> On Thu, Jul 06, 2017 at 02:11:00AM +0300, Adrian Bunk wrote:
> > Source: golang-github-pelletier-go-toml
> > Version: 1.0.0-1
> > Severity: serious
> > 
> > https://buildd.debian.org/status/package.php?p=golang-github-pelletier-go-toml=sid
> > 
> > ...
> >    dh_auto_test -a -O--buildsystem=golang
> > go test -v -p 4 github.com/pelletier/go-toml 
> > github.com/pelletier/go-toml/cmd github.com/pelletier/go-toml/cmd/tomljson 
> > github.com/pelletier/go-toml/cmd/tomll github.com/pelletier/go-toml/query
> > go build github.com/davecgh/go-spew/spew: /usr/bin/mips-linux-gnu-gccgo-7: 
> > waitid: bad address
> > FAILgithub.com/pelletier/go-toml [build failed]
> > ?   github.com/pelletier/go-toml/cmd[no test files]
> > ...
> 
> James Cowgill told me that this is actually a kernel bug:
>   https://www.linux-mips.org/archives/linux-mips/2017-03/msg00580.html

That's now a 404, strangely.  Did you mean "[PATCH 0/2] Fix indirect
syscall handler for syscalls with > 4 args"?

Ben.

-- 
Ben Hutchings
If the facts do not conform to your theory, they must be disposed of.


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

Processed: retitle 867196 to radeon: GPU hang and repeated "*ERROR* Failed to schedule IB" on Radeon HD 4670

[Debian Bug Tracking System]

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

> retitle 867196 radeon: GPU hang and repeated "*ERROR* Failed to schedule IB" 
> on Radeon HD 4670
Bug #867196 [src:linux] linux-image-4.9.0-3-amd64: video and sound crashes 
while listening music or watch a movie
Changed Bug title to 'radeon: GPU hang and repeated "*ERROR* Failed to schedule 
IB" on Radeon HD 4670' from 'linux-image-4.9.0-3-amd64: video and sound crashes 
while listening music or watch a movie'.
> thanks
Stopping processing here.

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

Bug#867124: Not a kernel bug

[Ben Hutchings]

Control: forwarded -1 https://bugzilla.kernel.org/show_bug.cgi?id=191201
Control: severity -1 important
Control: tag -1 wontfix

On Tue, 4 Jul 2017 06:23:35 -0400 Mini Trader  wrote:
> This seems to be an ESXi bug.
> 
> Exact same error being reported here.  I've followed their suggested
> settings and was no longer able to produce the kernel panic.
> 
> https://bugzilla.kernel.org/show_bug.cgi?id=191201

Thanks for investigating this.  I agree this seems to be the same bug. 
As VMware seems to have decided to fix this only in the hypervisor and
not to work around it in the vmxnet3 driver, there is probably nothing
for us to do here.

Ben.

-- 
Ben Hutchings
If the facts do not conform to your theory, they must be disposed of.



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

Processed: Re: Bug#866376: [Pkg-utopia-maintainers] Bug#866376: network-manager: Network-Manager cause kernel panic

[Debian Bug Tracking System]

Processing control commands:

> retitle -1 rtl8723be: Hangs in rtl8723_fw_free_to_go
Bug #866376 [src:linux] network-manager: Network-Manager cause kernel panic
Changed Bug title to 'rtl8723be: Hangs in rtl8723_fw_free_to_go' from 
'network-manager: Network-Manager cause kernel panic'.
> severity -1 important
Bug #866376 [src:linux] rtl8723be: Hangs in rtl8723_fw_free_to_go
Severity set to 'important' from 'critical'

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

Bug#866376: [Pkg-utopia-maintainers] Bug#866376: network-manager: Network-Manager cause kernel panic

[Ben Hutchings]

Control: retitle -1 rtl8723be: Hangs in rtl8723_fw_free_to_go
Control: severity -1 important

On Fri, 2017-06-30 at 09:34 +0200, Dario Maiocchi wrote:
> Ciao Guys,
> 
> thx for prompt feedback. Since is my secondary workstation, i didn't 
> have access. (since wifi was broken, i had ethernet with a telephone)
> 
> If you need some other extra infos, just ping me, i will give you the 
> info next week.
> 
> @Ben is the driver needinfo still actual? Sorry, for kernel issue i'm 
> still a newbie :)

No, since I worked out what the driver is.

Ben.

-- 
Ben Hutchings
Experience is directly proportional to the value of equipment
destroyed.
- Carolyn Scheppner


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

Processed: Re: Bug#866190: linux-image-4.9.0-3-amd64: Kernel panics and locks up on heavy disk load

[Debian Bug Tracking System]

Processing control commands:

> severity -1 important
Bug #866190 [src:linux] linux-image-4.9.0-3-amd64: Kernel panics and locks up 
on heavy disk load
Severity set to 'important' from 'normal'
> tag -1 moreinfo
Bug #866190 [src:linux] linux-image-4.9.0-3-amd64: Kernel panics and locks up 
on heavy disk load
Added tag(s) moreinfo.

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

Bug#866190: linux-image-4.9.0-3-amd64: Kernel panics and locks up on heavy disk load

[Ben Hutchings]

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

On Tue, 2017-06-27 at 22:15 -0700, jmol...@swoncology.net wrote:
> Package: src:linux
> Version: 4.9.30-2
> Severity: normal
> 
> Please see attached kernel messages collected from the /var/log/messages
> file post-reboot.

Have you seen multiple crashes with a warning logged referring to the
same file (fs/dcache.c)?  Or do you see different filenames or messages
every time?

> This is at least the third time this has happened in the last couple of
> months. Each and every event occured just after the system had just
> started an rsync backup from the local disks to a local USB3 drive. The
> backup job is nightly, so this only happens once every 1-2 months on
> average.
> 
> The system is a Dell Optiplex 3020 Haswell with 3x 1TB SATA drives
> (terribly slow) in a mdadm RAID5. The Dell BIOS is up to date.
>
> The problem first manifested itself after upgrading from old stable (Deb
> 8) to unstable maybe five-six months ago. Prior to that, the system had
> been very stable.

"Optiplex 3020" appears to refer to two desktop models that are both
physically small and possibly not designed for this number of drives. 
Are you sure that there is sufficient air flow to cool the hardware
(CPU, motherboard, drives)?

Ben.

-- 
Ben Hutchings
Experience is directly proportional to the value of equipment
destroyed.
- Carolyn Scheppner



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

Re: debian-policy: please document build profiles

[Ben Hutchings]

On Wed, 2017-06-21 at 16:01 -0700, Jonathan Nieder wrote:
[...]
> I'd like to restart this discussion.  My understanding is that all the
> relevant infrastructure for build profiles is in place, so what's left
> is to add some text to policy documenting it.
> 
> Is my understanding correct?  Any thoughts before I (or someone else)
> starts to port the change-based language from
> https://wiki.debian.org/BuildProfileSpec to current-state based
> language in policy?
> 
> Kernel team, any notes from your experience using build profiles?

So far as I can remember, I found the wiki page and dpkg manual pages
sufficient when I was adding support for build profiles in src:linux.

However, I can see it has changed since I last looked and now says that
"stage1" has been deprecated.  I don't understand why this is or how
we're supposed to give this hint to bootstrapping tools now.

Ben.

-- 
Ben Hutchings
Experience is directly proportional to the value of equipment
destroyed.
- Carolyn Scheppner



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

Bug#868511: linux-image-4.11.0-1-amd64: Please enable CEC drivers

[Hans Verkuil]

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

Dear Maintainer,

Starting with kernel 4.10 the HDMI CEC framework was mainlined in the linux
kernel. It would be very nice if this and the driver for the popular PulseEight
USB CEC adapter (https://www.pulse-eight.com/p/104/usb-hdmi-cec-adapter)
can be enabled in the 4.11 kernel config:

select CONFIG_MEDIA_CEC_SUPPORT=y and CONFIG_USB_PULSE8_CEC=m.
CONFIG_VIDEO_VIVID_CEC=y is also very useful and highly recommended as this
enables CEC emulation in this virtual video driver. This allows application
developers to test their CEC implementation without having CEC hardware.

In kernel 4.12 the RainShadow driver (similar to the popular PulseEight
USB CEC adapter) should also be enabled: CONFIG_USB_RAINSHADOW_CEC=m

Regards,

Hans Verkuil
CEC Framework & pulse8-cec driver maintainer

-- System Information:
Debian Release: buster/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.11.0-1-amd64 (SMP w/56 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=ANSI_X3.4-1968) 
(ignored: LC_ALL set to C), LANGUAGE=C (charmap=ANSI_X3.4-1968) (ignored: 
LC_ALL set to C)
Shell: /bin/sh linked to /bin/bash
Init: systemd (via /run/systemd/system)

Versions of packages linux-image-4.11.0-1-amd64 depends on:
ii  initramfs-tools [linux-initramfs-tool]  0.130
ii  kmod24-1
ii  linux-base  4.5

Versions of packages linux-image-4.11.0-1-amd64 recommends:
ii  firmware-linux-free  3.4
ii  irqbalance   1.1.0-2.3

Versions of packages linux-image-4.11.0-1-amd64 suggests:
pn  debian-kernel-handbook  
ii  grub-pc 2.02-2
pn  linux-doc-4.11  

Versions of packages linux-image-4.11.0-1-amd64 is related to:
ii  firmware-amd-graphics 20161130-3
pn  firmware-atheros  
pn  firmware-bnx2 
pn  firmware-bnx2x
pn  firmware-brcm80211
pn  firmware-cavium   
pn  firmware-intel-sound  
pn  firmware-intelwimax   
pn  firmware-ipw2x00  
ii  firmware-ivtv 20161130-3
ii  firmware-iwlwifi  20161130-3
pn  firmware-libertas 
ii  firmware-linux-nonfree20161130-3
ii  firmware-misc-nonfree 20161130-3
pn  firmware-myricom  
pn  firmware-netxen   
pn  firmware-qlogic   
ii  firmware-realtek  20161130-3
pn  firmware-samsung  
pn  firmware-siano
pn  firmware-ti-connectivity  
pn  xen-hypervisor

-- debconf-show failed