Bug#868224: marked as done (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]

Your message dated Mon, 25 Sep 2017 03:22:47 +0100
with message-id <1506306167.2852.76.ca...@decadent.org.uk>
and subject line Re: Bug#868224: 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
has caused the Debian Bug report #868224,
regarding linux-image-4.9.0-3-amd64: Upgrade to linux-image-4.9.0-3-amd64 hangs 
while or after generating initrd
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.)


-- 
868224: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=868224
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:linux
Version: 4.9.30-2+deb9u2
Severity: normal

Dear Maintainer,

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

   * What led up to the situation?
   * What exactly did you do (or not do) that was effective (or
 ineffective)?
   * What was the outcome of this action?
   * What outcome did you expect instead?

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

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


I don't know if that's related to bug #865301

Thanks for any help on that



-- 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+deb9u1 (2017-06-18)

** Command line:
BOOT_IMAGE=/vmlinuz-4.9.0-3-amd64 root=/dev/mapper/vg00-lvRoot ro quiet

** Tainted: O (4096)
 * Out-of-tree module has been loaded.

** Kernel log:
[582958.060279] bond0: first active interface up!
[582958.060290] IPv6: ADDRCONF(NETDEV_CHANGE): bond0: link becomes ready
[582958.463563] ixgbe :03:00.1 eth1: NIC Link is Up 1 Gbps, Flow Control: 
None
[582958.476182] bond0: link status up for interface eth1, enabling it in 200 ms
[582958.684323] bond0: link status definitely up for interface eth1, 1000 Mbps 
full duplex
[582976.421902] traps: SHCLIP[4960] general protection ip:7fa1d5eb1865 
sp:7fa1b963aa30 error:0
[582976.421909]  in libc-2.24.so[7fa1d5e7c000+195000]
[582976.683613] vboxnetflt: 0 out of 724589 packets were not sent (directed to 
host)
[58.314841] VBoxNetFlt: attached to 'eth0' / a4:bf:01:13:f4:8c
[584582.164755] vboxnetflt: 0 out of 3993 packets were not sent (directed to 
host)
[685004.192759] usb 4-6: USB disconnect, device number 3
[699768.222763] device bond0 left promiscuous mode
[699768.222767] device eth0 left promiscuous mode
[699768.223605] device eth1 left promiscuous mode
[699768.297287] vboxnetflt: 5018 out of 97411155 packets were not sent 
(directed to host)
[727534.436845] vboxdrv: c020 VMMR0.r0
[727534.547763] vboxdrv: c0116020 VBoxDDR0.r0
[727534.724402] VBoxNetFlt: attached to 'bond0' / a4:bf:01:13:f4:8c
[727534.744630] device bond0 entered promiscuous mode
[727534.744634] device eth0 entered promiscuous mode
[727534.745463] device eth1 entered promiscuous mode
[762062.166807] bin2asc[15118]: segfault at 13891 ip 00013891 sp 
7ffd2323ec58 error 14 in bin2asc[40+3000]
[762072.948390] bin2asc[15471]: segfault at 13891 ip 00013891 sp 
7fffc97c9348 error 14 in bin2asc[40+3000]
[919035.967241] mce: [Hardware Error]: Machine check events logged
[919035.967272] {1}Hardware error detected on CPU0
[919035.967275] {1}It has been corrected by h/w and requires no further action
[919035.967276] {1}event severity: corrected
[919035.967279] {1} Error 0, type: corrected
[919035.967280] {1}  section_type: memory error
[919035.967282] {1}  physical_address: 0x001bcd8f5000
[919035.967284] {1}  node: 1 card: 1 module: 0 rank: 0 
[919035.967286] {1}  error_type: 0, unknown
[919035.967288] {1}  DIMM location: not present. DMI handle: 0x0002 
[1258407.948266] traps: psppire[11680] trap stack segment ip:7f71e1801b0e 
sp:7ffd17ae5260 error:0
[1258407.948277]  in libpspp-core-0.10.2.so[7f71e17af000+101000]

Processed: severity of 868884 is important, tagging 868884 ...

[Debian Bug Tracking System]

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

> severity 868884 important
Bug #868884 [src:linux] linux-source: Kernels 4.x no boot on Dells with no Kbd 
Backlight
Severity set to 'important' from 'normal'
> tags 868884 + upstream
Bug #868884 [src:linux] linux-source: Kernels 4.x no boot on Dells with no Kbd 
Backlight
Added tag(s) upstream.
> forwarded 868884 https://bugzilla.kernel.org/show_bug.cgi?id=107651
Bug #868884 [src:linux] linux-source: Kernels 4.x no boot on Dells with no Kbd 
Backlight
Ignoring request to change the forwarded-to-address of bug#868884 to the same 
value
> thanks
Stopping processing here.

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

Processed: Re: Bug#869435: Dell Latitude D505 / Debian 9 Not powering down

[Debian Bug Tracking System]

Processing control commands:

> tag -1 moreinfo
Bug #869435 [src:linux] Dell Latitude D505 / Debian 9 Not powering down
Added tag(s) moreinfo.

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

Bug#869435: Dell Latitude D505 / Debian 9 Not powering down

[Ben Hutchings]

Control: tag -1 moreinfo

On Sun, 2017-07-23 at 10:09 -0400, Aaron Valdes wrote:
> Package: linux-image-686
> Version: 4.9+80
> 
> I have upgrade Dell Latitude D505 to Debian 9.  When shutting down from
> XFCE4, the system does not power off.  The laptop is still on after this
> event.
> 
> The config-4.9.0-3-686 file had CONFIG_APM=n.  See below.
> 
> grep APM /boot/config-4.9.0-3-686
> CONFIG_X86_APM_BOOT=y
> CONFIG_APM=n

No, it has CONFIG_APM=m (module).

And this computer is not nearly old enough to require use of APM.  It
is designed to run Windows 2000 and XP, which means it must have good
ACPI support.

> # CONFIG_APM_IGNORE_USER_SUSPEND is not set
> # CONFIG_APM_DO_ENABLE is not set
> # CONFIG_APM_CPU_IDLE is not set
> # CONFIG_APM_DISPLAY_BLANK is not set
> # CONFIG_APM_ALLOW_INTS is not set
> 
> I set it to:
> 
> CONFIG_APM=y 
> 
> I rebooted the laptop and tried to shutdown from XFCE4 again and it
> worked.

That's interesting.  But this is not a run-time configuration file and
changing it has no effect on the kernel behaviour.

It's conceivable that some program included in Xfce is reading this
file to determine kernel features, but if so, I think it's a bug in
that program.  (I checked with codesearch.debian.net and didn't find
anything.)

> Is this configuration something that can be adjusted in this package?
> Does this configuration defaulted to CONFIG_APM=y conflict with other
> potential setups?  The feature is configured in the kernel, it is just
> not set in the /boot/config-4.9.0-3-686 file. 

I will not be changing the kernel configuration, as there is no need to
build-in APM.

Try changing the file back and test again whether you can shut down
from Xfce.  I strongly suspect it will work this time.

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#869149: marked as done (linux: please merge Btrfs: fix early ENOSPC due to delalloc)

[Debian Bug Tracking System]

Your message dated Mon, 25 Sep 2017 03:06:05 +0100
with message-id <1506305165.2852.73.ca...@decadent.org.uk>
and subject line Re: Bug#869149: linux: please merge Btrfs: fix early ENOSPC 
due to delalloc
has caused the Debian Bug report #869149,
regarding linux: please merge Btrfs: fix early ENOSPC due to delalloc
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.)


-- 
869149: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=869149
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: linux
Version: 4.9.30-2+deb9u2
Severity: normal


Hey Ben, et al.

There seems to be an annoying bug in btrfs, as described here:
https://www.spinics.net/lists/linux-btrfs/msg67479.html

It's not really extremely critical as it causes no direct fs corruption,
but it gives spurious ENOSPC in case of heavy metadata operation,
even though plenty of space is left.

It affects stretch kernels as well as the current 4.12.


It can e.g. easily be hit, when copying a root-fs, as described in the
thread above.

There's a fix, which seems to work:
https://patchwork.kernel.org/patch/9829593/

Omar will mark it for linux-stable, I'm just reporting it here as well
to make sure that it doesn't get lost :-)


Best wishes,
Chris
--- End Message ---
--- Begin Message ---
Version: 4.9.47-1

This was applied upstream and in 4.9-stable:

v4.9.42: 3a63729427ac Btrfs: fix early ENOSPC due to delalloc

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
--- End Message ---

Processed: reassign 869435 to src:linux

[Debian Bug Tracking System]

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

> reassign 869435 src:linux 4.9.30-2
Bug #869435 [src:linux] Dell Latitude D505 / Debian 9 Not powering down
Ignoring request to reassign bug #869435 to the same package
Bug #869435 [src:linux] Dell Latitude D505 / Debian 9 Not powering down
Marked as found in versions linux/4.9.30-2; no longer marked as found in 
versions linux/4.9.30-2+deb9u2.
> thanks
Stopping processing here.

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

Bug#869853: marked as done (Known issues with gdb in rt-20-patch)

[Debian Bug Tracking System]

Your message dated Mon, 25 Sep 2017 02:27:28 +0100
with message-id <1506302848.2852.62.ca...@decadent.org.uk>
and subject line Re: Bug#869853: Known issues with gdb in rt-20-patch
has caused the Debian Bug report #869853,
regarding Known issues with gdb in rt-20-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.)


-- 
869853: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=869853
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: linux-image-4.9.0-3-rt-amd64
Version: 4.9.30-2+deb9u2

With the current and all previous rt-kernel package for debian 9 it is almost 
impossible to use gdb for debugging.
 
Kernel.release:
 4.9.30-rt20
 
Known issues in rt-20-patch :
 gdb. While gdb is following a task it is possible that after a
 fork() operation the task is waiting for gdb and gdb waiting
 for the task.
 
In rt-21-patch the problem is solved!
 
My wish:
 using rt-21-patch or newer in next update
 
Thanks for attention
--- End Message ---
--- Begin Message ---
Version: 4.9.47-1

This is fixed in the above version, which is in stretch-proposed-
updates.

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
--- End Message ---

Processed: severity of 870598 is important

[Debian Bug Tracking System]

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

> severity 870598 important
Bug #870598 [src:linux] linux-image-4.9.0-3-amd64: DRBD regression from debian 
8 to debian 9, SCSI errors in log and drbd going diskless
Severity set to 'important' from 'normal'
> thanks
Stopping processing here.

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

Processed: severity of 870598 is important

[Debian Bug Tracking System]

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

> severity 870598 important
Bug #870598 [src:linux] linux-image-4.9.0-3-amd64: DRBD regression from debian 
8 to debian 9, SCSI errors in log and drbd going diskless
Ignoring request to change severity of Bug 870598 to the same value.
> thanks
Stopping processing here.

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

Bug#869658: linux: system freezes when dell-smm-hwmon reads fan speed

[Ben Hutchings]

On Sat, 2017-08-05 at 21:15 +0200, Carmelo C wrote:
> In my system, dell-smm-hwmon is linked to the following folder:
> 
> /sys/class/hwmon/hwmon2/
> 
> The freeze occurs only when I type the following commands:
> 
> cat /sys/class/hwmon/hwmon2/fan1_input
> cat /sys/class/hwmon/hwmon2/fan2_input
> cat /sys/class/hwmon/hwmon2/fan3_input
> 
> In these commands, the freeze does not occur:
> 
> cat /sys/class/hwmon/hwmon2/temp1_input
> cat /sys/class/hwmon/hwmon2/temp2_input
> cat /sys/class/hwmon/hwmon2/temp3_input
> cat /sys/class/hwmon/hwmon2/temp4_input
> 
> In this link, more information:
> https://bugzilla.kernel.org/show_bug.cgi?id=112021

That bug report relates to label attributes, and is fixed.  It's not
the same as this bug.

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 (with 1 error): forcibly merging 874035 871598

[Debian Bug Tracking System]

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

> forcemerge 874035 871598
Bug #874035 {Done: Ben Hutchings } [src:linux] 
linux-image-4.9.0-3-amd64: kernel panic in nfconntrack
Bug #871598 [src:linux] linux-image-4.9.0-3-amd64: kernel panic in nfconntrack?
Marked Bug as done
Marked as fixed in versions linux/4.9.47-1.
Marked as found in versions linux/4.8~rc5-1~exp1.
Added tag(s) moreinfo, upstream, and confirmed.
Bug #871598 {Done: Ben Hutchings } [src:linux] 
linux-image-4.9.0-3-amd64: kernel panic in nfconntrack?
Ignoring request to alter fixed versions of bug #871598 to the same values 
previously set
Unable to complete merge on previous attempt; trying again (retry: 2)
Bug #871598 {Done: Ben Hutchings } [src:linux] 
linux-image-4.9.0-3-amd64: kernel panic in nfconntrack?
Ignoring request to alter fixed versions of bug #871598 to the same values 
previously set
Unable to complete merge on previous attempt; trying again (retry: 3)
Bug #871598 {Done: Ben Hutchings } [src:linux] 
linux-image-4.9.0-3-amd64: kernel panic in nfconntrack?
Ignoring request to alter fixed versions of bug #871598 to the same values 
previously set
After four attempts, the following changes were unable to be made:
fixed_versions of #871598 is 'linux/4.9.47-1' not '4.9.47-1'
Failed to forcibly merge 874035: Unable to modify bugs so they could be merged.

> thanks
Stopping processing here.

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

Bug#871608: linux-image-4.9.0-3-amd64: Linux kernel should handle decreasing cpu steal clock counter gracefully

[Ben Hutchings]

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

On Wed, 2017-08-09 at 22:46 +0200, Michael Lass wrote:
> Package: src:linux
> Version: 4.9.30-2+deb9u3
> Severity: normal
> Tags: patch
> 
> Dear Maintainer,
> 
> running Debian Stretch as a paravirtualized guest under Xen, the kernel
> obtains its cpu steal time counter from the virtualization host. On some
> hosts, occasionally a slight decrease in the cpu steal time is returned
> which leads to an overflow of unsigned variables in the kernel and
> subsequent errors in steal time accounting (such as backwards running
> counters). This renders tools like "top" or "vmstat" broken in a way
> that the cpu utilization cannot be determined anymore.
> 
> While this is likely a bug in the virtualization environment, the kernel
> running as a guest should deal with this gracefully. I attached a patch
> to this report which fixes the errors caused by this on the guest.
> Kernel versions 4.7 and older, as well as 4.11 and newer should not be
> affected by this issue.
[...]

I agree that the kernel ought to work around this, but I'm hesitant to
add a fix that doesn't look like any upstream change.  Why and how do
you think this was fixed in 4.11?

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#871608: linux-image-4.9.0-3-amd64: Linux kernel should handle decreasing cpu steal clock counter gracefully

[Debian Bug Tracking System]

Processing control commands:

> severity -1 important
Bug #871608 [src:linux] linux-image-4.9.0-3-amd64: Linux kernel should handle 
decreasing cpu steal clock counter gracefully
Severity set to 'important' from 'normal'
> tag -1 moreinfo
Bug #871608 [src:linux] linux-image-4.9.0-3-amd64: Linux kernel should handle 
decreasing cpu steal clock counter gracefully
Added tag(s) moreinfo.

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

Processed: Re: Bug#873176: linux-image-armmp-lpae: Please add module for DHT11/DHT22 sensors

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 src:linux
Bug #873176 [linux-image-armmp-lpae] linux-image-armmp-lpae: Please add module 
for DHT11/DHT22 sensors
Bug reassigned from package 'linux-image-armmp-lpae' to 'src:linux'.
No longer marked as found in versions linux-latest/84.
Ignoring request to alter fixed versions of bug #873176 to the same values 
previously set
> tag -1 moreinfo
Bug #873176 [src:linux] linux-image-armmp-lpae: Please add module for 
DHT11/DHT22 sensors
Added tag(s) moreinfo.

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

Bug#873176: linux-image-armmp-lpae: Please add module for DHT11/DHT22 sensors

[Ben Hutchings]

Control: reassign -1 src:linux
Control: tag -1 moreinfo

On Fri, 2017-08-25 at 12:30 +0200, Harald Geyer wrote:
> Package: linux-image-armmp-lpae
> Version: 4.12+84
> Severity: wishlist
> 
> Dear Maintainer,
> 
> the DHT22 sensors are quite popular temperature and humidity sensors. I'm
> the upstream driver author so I am biased but from my experience with bug
> reports many users seem to run custom compiled (and mostly outdated) kernels
> only because debian doesn't ship the kernel module for this sensor.
> 
> Also I'm switching my systems using these sensors from OpenWRT to debian
> ATM so I'm directly affeced by this as well.
> 
> Adding CONFIG_DHT11=m will be enough, however I'm less sure about the
> architectures to enable this: It will be mostly used on all variants of
> ARM but the driver works on any platform with native (ie fast enough for
> bit banging) GPIOs.

This driver appears to depend on Device Tree properties, but none of
the DTBs we build set those properties.  It's not clear to me how it
would be usable.

Ben.

-- 
Ben Hutchings
Make three consecutive correct guesses and you will be considered an
expert.



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

Bug#861746: linux-image-4.9.0-2-amd64: Infinity `soft lockup` at kernel 4.9.0-1+ on HP ProLiant DL360G5

[Ben Hutchings]

On Wed, 2017-05-03 at 15:55 +0300, Arano-kai wrote:
> Package: src:linux
> Version: 4.9.18-1
> Severity: critical
> Tags: upstream
> Justification: breaks the whole system
> 
> Dear Maintainer,
> after updating the kernel to `4.9.0-2-amd64` on HP DL360G5, the
> system hangs up with repeating `NMI watchdog: BUG: soft lockup -
> CPU#0 stuck for 23s! [swapper/0:1]`.
> `4.9.0-1-amd64` also affected.
> Last working kernel is `4.8.0-2-amd64`
> 
> Boot possible only if `acpi=off` provided in kernel opts.
[...]
> Boot log from the serial console is attached.

The weird thing in this log is:

[0.232233]  node  #0, CPUs:   #4
[0.322042] x86: Booted up 1 node, 2 CPUs

We have 2 CPUs and they are apparently numbered 0 and 4?!

Maybe related to:

d49597fd3bc7 x86/cpu: Deal with broken firmware (VMWare/XEN)
(which went into 4.9)
9d85eb9119f4 x86/smpboot: Make logical package management more robust
(which went into 4.9.2)

Ben.

-- 
Ben Hutchings
Make three consecutive correct guesses and you will be considered an
expert.


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

Processed: Re: Bug#873187: linux-image-amd64: Missing tpm_tis module

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 src:linux 4.9.25-1
Bug #873187 [linux-image-amd64] linux-image-amd64: Missing tpm_tis module
Bug reassigned from package 'linux-image-amd64' to 'src:linux'.
No longer marked as found in versions linux-latest/80+deb9u1.
Ignoring request to alter fixed versions of bug #873187 to the same values 
previously set
Bug #873187 [src:linux] linux-image-amd64: Missing tpm_tis module
Marked as found in versions linux/4.9.25-1.
> tag -1 moreinfo
Bug #873187 [src:linux] linux-image-amd64: Missing tpm_tis module
Added tag(s) moreinfo.

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

Bug#873187: linux-image-amd64: Missing tpm_tis module

[Ben Hutchings]

Control: reassign -1 src:linux 4.9.25-1
Control: tag -1 moreinfo

On Fri, 2017-08-25 at 13:09 +0100, Gregory Stark wrote:
> Package: linux-image-amd64
> Version: 4.9+80+deb9u1
> Severity: normal
> 
> Hi,
> 
> I find that the tpm_tis.ko module is missing in all kernel packages
> since 4.9.0-3 (which is the version in Debian 9 installers and the
> security archive). This includes all more recent kernels that I've
> tried from unstable.
>
> It was present in 4.9.0-2 which makes me wonder if it was removed due
> to some last minute security problem before the release of Debian 9.

It's still included, but built-in.

> However this is a severe problem for users of the 2013 Chromebook
> Pixel as there was a firmware bug that means suspend/resume doesn't
> work unless the tpm chip has been initialized by the module. In other
> words suspend/resume is broken on the 2013 Pixel ever since 4.9.0-3
> but worked fine previously.

Have you actually found this to be broken?  I don't believe such a
failure would be related to the tpm_tis driver, since as I said it is
still included.

> I can't find an existing bug about tpm_tis or any mention of it on the
> list. Perhaps this was done unintentionally?

We didn't deliberately change it to built-in, but this is a result of
enabling IMA.

Ben.
 
-- 
Ben Hutchings
Make three consecutive correct guesses and you will be considered an
expert.



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

Bug#851577: marked as done (linux-image-4.8.0-0.bpo.2-amd64: Panic on boot)

[Debian Bug Tracking System]

Your message dated Sun, 24 Sep 2017 22:58:05 +0100
with message-id <1506290285.2852.27.ca...@decadent.org.uk>
and subject line Re: Bug#851577: linux-image-4.9.0-3-amd64: hit similar bug on 
4.9.0-3, fixed in 4.9.46
has caused the Debian Bug report #851577,
regarding linux-image-4.8.0-0.bpo.2-amd64: Panic on boot
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
851577: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=851577
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:linux
Version: 4.8.11-1~bpo8+1
Severity: important

Dear Maintainer,

rebooting an AWS m4.xlarge instance in Frankfurt region using HVM xen 
virtualization yielded the following panic.
Hard resetting the system helped.

-- Package-specific info:
[1.050518] Freeing initrd memory: 17432K (8af5b5de4000 - 
8af5b6eea000)
[1.053182] PCI-DMA: Using software bounce buffering for IO (SWIOTLB)
[1.055348] software IO TLB [mem 0xec00-0xf000] (64MB) mapped at 
[8af66c00-8af66fff]
[1.058927] BUG: unable to handle kernel paging request at 00019bcb
[1.061825] IP: [] rapl_cpu_online+0x5d/0x70
[1.062900] PGD 0 
[1.062900] Oops: 0002 [#1] SMP
[1.062900] Modules linked in:
[1.062900] CPU: 2 PID: 20 Comm: cpuhp/2 Not tainted 4.8.0-0.bpo.2-amd64 #1 
Debian 4.8.11-1~bpo8+1
[1.062900] Hardware name: Xen HVM domU, BIOS 4.2.amazon 11/11/2016
[1.062900] task: 8af9865a9080 task.stack: 8af9865e8000
[1.062900] RIP: 0010:[]  [] 
rapl_cpu_online+0x5d/0x70
[1.062900] RSP: :8af9865ebe28  EFLAGS: 00010212
[1.062900] RAX: 0200 RBX: 8af98fc0dc40 RCX: 
[1.062900] RDX: 0200 RSI: 0200 RDI: 0200
[1.062900] RBP: 0002 R08: 0007 R09: 
[1.062900] R10:  R11:  R12: 00019bc3
[1.062900] R13: b44143b0 R14: 8af98fc0dc40 R15: 0079
[1.062900] FS:  () GS:8af98fc0() 
knlGS:
[1.062900] CS:  0010 DS:  ES:  CR0: 80050033
[1.062900] CR2: 00019bcb CR3: 00027ec06000 CR4: 001406e0
[1.062900] DR0:  DR1:  DR2: 
[1.062900] DR3:  DR6: fffe0ff0 DR7: 0400
[1.062900] Stack:
[1.062900]  8af98fc0dc40 0002 004d 
b447ea6e
[1.062900]  8af98fc0dc40 0002 b4e3f080 
8af9865a9080
[1.062900]  8af9865a9080 8af9865a9080 b447ecfb 
8af9865a9080
[1.062900] Call Trace:
[1.062900]  [] ? cpuhp_invoke_callback+0x3e/0xf0
[1.062900]  [] ? cpuhp_thread_fun+0x3b/0x100
[1.062900]  [] ? smpboot_thread_fn+0x124/0x190
[1.062900]  [] ? sort_range+0x20/0x20
[1.062900]  [] ? kthread+0xdf/0x100
[1.062900]  [] ? ret_from_fork+0x1f/0x40
[1.062900]  [] ? kthread_park+0x50/0x50
[1.062900] Code: 00 00 00 48 83 c2 22 4c 8b 24 d1 48 c7 c2 80 a1 00 00 48 
01 c2 e8 04 56 31 00 3b 05 a2 75 b1 00 7c 0e f0 48 0f ab 2d f3 92 c8 00 <41> 89 
6c 24 08 5b 31 c0 5d 41 5c c3 0f 1f 80 00 00 00 00 0f 1f 
[1.062900] RIP  [] rapl_cpu_online+0x5d/0x70
[1.062900]  RSP 
[1.062900] CR2: 00019bcb
[1.062900] ---[ end trace a7c718c99e1e2c49 ]---
[1.157822] BUG: unable to handle kernel paging request at 00019250
[1.160780] IP: [] 
__pv_queued_spin_lock_slowpath+0x18c/0x260
[1.161806] PGD 0 
[1.161806] Oops: 0002 [#2] SMP
[1.161806] Modules linked in:
[1.161806] CPU: 2 PID: 20 Comm: cpuhp/2 Tainted: G  D 
4.8.0-0.bpo.2-amd64 #1 Debian 4.8.11-1~bpo8+1
[1.161806] Hardware name: Xen HVM domU, BIOS 4.2.amazon 11/11/2016
[1.161806] task: 8af9865a9080 task.stack: 8af9865e8000
[1.161806] RIP: 0010:[]  [] 
__pv_queued_spin_lock_slowpath+0x18c/0x260
[1.161806] RSP: :8af9865ebe58  EFLAGS: 00010006
[1.161806] RAX: 3492 RBX: 8af9865ebf18 RCX: 
[1.161806] RDX:  RSI: d24d4b3e RDI: 8af9865ebf18
[1.161806] RBP: 8af98fc19240 R08:  R09: 000a
[1.161806] R10: 31372d34 R11: 017a R12: 00019250
[1.161806] R13: 8af98fc19284 R14: 000c R15: 0001
[1.161806] FS:  () GS:8af98fc0() 
knlGS:
[1.161806] CS:  0010 DS:  ES:  CR0: 

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

[Vagrant Cascadian]

On 2017-09-24, Jochen Sprickerhof wrote:
> Finally I had the time and hardware available to look into this again 
> and found a better way to fix it. Applying the attached patch results in 
> a new exynos5422-odroidxu4.dtb that could simply be copied to /boot/dtbs/*/
> I've tested this with the current kernel in sid (linux-image-4.12.0-2-armmp)
> as well as stretch (linux-image-4.9.0-3-armmp). More tests welcome.

Thanks!

I'm testing the patched .dtb on linux-image-4.9.0-3-armmp-lpae on two
machines and one machine running linux-image-4.13.0-trunk-armmp-lpae.
All use USB for rootfs and a build partition, so should test USB
reasonable well. Seems to work fine so far.

Using a patched .dtb is a much easier workaround than having to
recompile the whole kernel (and follow security updates and so on)!

I'd be happy to also do some testing with newer mainline kernels, if
you'd like to CC me on patch submissions upstream.


live well,
  vagrant

> Cheers Jochen
> From 0d3552be829d5a275d549cbf6ab468bfdb026e49 Mon Sep 17 00:00:00 2001
> From: Jochen Sprickerhof 
> Date: Sun, 24 Sep 2017 08:28:12 +0200
> Subject: [PATCH] ARM: dts: exynos: Use dwc3 quirk for USB3 and LAN on Odroid
>  XU4
>
> First proposed in https://lkml.org/lkml/2015/3/18/400 and discussed
> again in https://lkml.org/lkml/2017/1/24/402.
> ---
>  arch/arm/boot/dts/exynos5422-odroidxu4.dts | 5 +
>  1 file changed, 5 insertions(+)
>
> diff --git a/arch/arm/boot/dts/exynos5422-odroidxu4.dts 
> b/arch/arm/boot/dts/exynos5422-odroidxu4.dts
> index 2faf88627a48..3861f74b2ecc 100644
> --- a/arch/arm/boot/dts/exynos5422-odroidxu4.dts
> +++ b/arch/arm/boot/dts/exynos5422-odroidxu4.dts
> @@ -43,6 +43,11 @@
>   status = "okay";
>  };
>  
> +_dwc3_0 {
> + snps,dis_u3_susphy_quirk;
> +};
> +
>  _dwc3_1 {
>   dr_mode = "host";
> + snps,dis_u3_susphy_quirk;
>  };
> -- 
> 2.14.1


signature.asc
Description: PGP signature

Processed: Re: Bug#875271: linux-image-4.9.0-3-amd64: kworker/1 stalls at exactly 100% CPU load

[Debian Bug Tracking System]

Processing control commands:

> tag -1 moreinfo
Bug #875271 [src:linux] linux-image-4.9.0-3-amd64: kworker/1 stalls at exactly 
100% CPU load
Added tag(s) moreinfo.

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

Bug#875271: linux-image-4.9.0-3-amd64: kworker/1 stalls at exactly 100% CPU load

[Ben Hutchings]

Control: tag -1 moreinfo

On Sun, 2017-09-10 at 09:03 +0200, Klaus-J. Wolf wrote:
> Package: src:linux
> Version: 4.9.30-2+deb9u3
> Severity: important
> 
> For unknown reason, kworker/1:1 stalls with exactly 100% CPU load on CPU
> kernel 1. This has happened thrice before, after several hours of uptime.
> 
> Nothing special happened on the machine in advance, just the usual tasks.
> 
> lsof tells me no suspicious open files, but the kernel task has used
> up 317:47.60 according to top(1) and it never seems to stop. I have
> terminated every user task, so I would suppose that the kernel task has
> crashed for some reason.
> 
> In the kernel log below, I have deleted the lines showing blocked
> network, this is for privacy reasons.
> 
> -- 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+deb9u3 (2017-08-06)
> 
> ** Command line:
> BOOT_IMAGE=/vmlinuz-4.9.0-3-amd64 
> root=UUID=b073140f-d246-4131-9015-636ceb35b3b1 ro quiet
> 
> ** Tainted: PO (4097)
>  * Proprietary module has been loaded.
>  * Out-of-tree module has been loaded.
[...]

Please test whether this still happens without the Nvidia and
VirtualBox kernel modules loaded.

Ben.

-- 
Ben Hutchings
Make three consecutive correct guesses and you will be considered an
expert.



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

Bug#876215: linux-base: typo in linux-update-symlinks.1

[Ben Hutchings]

Control: tag -1 pending

On Tue, 2017-09-19 at 20:45 +0200, Sven Joachim wrote:
> Package: linux-base
> Version: 4.5
> Tags: patch
> 
> I wanted to get rid of the /vmlinuz and /initrd symlinks.  It took me a
> while to find out that they are managed by linux-update-symlinks, and
> then a trivial but crucial typo in the manpage did cost me even more
> time to figure out that the parameter I needed to set is called
> do_symlinks rather than no_symlinks.  Patch attached.

Right!  This is really a thinko, not a typo - we used to support a
'no_symlinks' setting which would result in file copies rather than
symlinks.  Thanks for the patch.

Ben.

-- 
Ben Hutchings
Make three consecutive correct guesses and you will be considered an
expert.



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

Processed: Re: Bug#876215: linux-base: typo in linux-update-symlinks.1

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #876215 [linux-base] linux-base: typo in linux-update-symlinks.1
Added tag(s) pending.

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

Bug#876303: linux-source-4.9 kernel regression eeepc-wmi

[Ben Hutchings]

Control: tag -1 moreinfo

On Wed, 2017-09-20 at 20:22 +0200, Oscon wrote:
> Package: linux-source-4.9
> 
> Version: >=4.9.25
> 
> eeepc-wmi doesn't work with my Eee PC netbook (Asus X101) after kernel 
> upgrade 
> from 3.14.79 to 4.9.y. So some Eee WMI hotkeys don't work with the new kernel.
[...]
> I have to use eeepc-wmi.
> 
> The patch "Use acpi_dev_found() " is the cause of the problem.
[...]

How did you determine this?  It doesn't appear to make any functional
change.

Are you still putting an acpi_osi parameter on the kernel command line?

Ben.

-- 
Ben Hutchings
Make three consecutive correct guesses and you will be considered an
expert.



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

Processed: reassign 876303 to src:linux

[Debian Bug Tracking System]

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

> reassign 876303 src:linux 4.9.25-1
Bug #876303 [linux-source-4.9] linux-source-4.9 kernel regression eeepc-wmi
Bug reassigned from package 'linux-source-4.9' to 'src:linux'.
Ignoring request to alter found versions of bug #876303 to the same values 
previously set
Ignoring request to alter fixed versions of bug #876303 to the same values 
previously set
Bug #876303 [src:linux] linux-source-4.9 kernel regression eeepc-wmi
Marked as found in versions linux/4.9.25-1.
> thanks
Stopping processing here.

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

Processed: Re: Bug#876303: linux-source-4.9 kernel regression eeepc-wmi

[Debian Bug Tracking System]

Processing control commands:

> tag -1 moreinfo
Bug #876303 [linux-source-4.9] linux-source-4.9 kernel regression eeepc-wmi
Added tag(s) moreinfo.

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

Processed: Re: Bug#876021: libreoffice-writer: launching writer makes libreoffice crash

[Debian Bug Tracking System]

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

> reassign 876021 src:linux
Bug #876021 [libreoffice-writer] libreoffice-writer: launching writer makes 
libreoffice crash
Bug reassigned from package 'libreoffice-writer' to 'src:linux'.
No longer marked as found in versions libreoffice/1:5.2.7-1.
Ignoring request to alter fixed versions of bug #876021 to the same values 
previously set
> forcemerge 865303 876021
Bug #865303 [src:linux] libreoffice: Libreoffice Java features crash with Linux 
3.16.43-2+deb8u1
Bug #865866 [src:linux] libreoffice-writer crash on startup Debian 9 i386 arch
Bug #869161 [src:linux] libreoffice-base crashes with code 139 when creating a 
new base or opening an existing one
Bug #869613 [src:linux] libreoffice write crashes (Debian 9)
Bug #869649 [src:linux] Debian 9 i386 - Libreoffice write crash
Bug #870070 [src:linux] Debian 9.1 stretch: LibreOffice Writer crashes at 
startup
Bug #875269 [src:linux] libreoffice-base: LibreOffice-Base crashes when trying 
to open Tables view in Debian 9 Stretch.
Bug #876458 [src:linux] LibreOffice Writer does not launch
Bug #876021 [src:linux] libreoffice-writer: launching writer makes libreoffice 
crash
Added indication that 876021 affects 
libreoffice-base,libreoffice,openjdk-9-jre,jsvc,openjdk-7-jre,rustc,openjdk-8-jre,live-build,libreoffice-writer,security.debian.org
The source linux and version 3.2.89-1 do not appear to match any binary packages
Marked as found in versions linux/3.16.43-2+deb8u1, linux/4.9.30-2+deb9u2, 
linux/4.11.6-1, linux/3.2.89-1, and linux/4.9.30-2+deb9u1.
Added tag(s) upstream and confirmed.
Bug #869649 [src:linux] Debian 9 i386 - Libreoffice write crash
Added tag(s) moreinfo.
Added tag(s) moreinfo.
Added tag(s) moreinfo.
Added tag(s) moreinfo.
Added tag(s) moreinfo.
Added tag(s) moreinfo.
Added tag(s) moreinfo.
Added tag(s) moreinfo.
Bug #870070 [src:linux] Debian 9.1 stretch: LibreOffice Writer crashes at 
startup
Removed indication that 870070 affects openjdk-9-jre, openjdk-7-jre, 
openjdk-8-jre, libreoffice, live-build, libreoffice-base, rustc, jsvc, 
libreoffice-writer, and security.debian.org
Added indication that 870070 affects 
libreoffice-base,libreoffice,openjdk-9-jre,jsvc,openjdk-7-jre,rustc,openjdk-8-jre,live-build,libreoffice-writer,security.debian.org
Removed indication that 865303 affects openjdk-7-jre, openjdk-9-jre, 
openjdk-8-jre, libreoffice, rustc, jsvc, live-build, libreoffice-base, 
security.debian.org, and libreoffice-writer
Added indication that 865303 affects 
libreoffice-base,libreoffice,openjdk-9-jre,jsvc,openjdk-7-jre,rustc,openjdk-8-jre,live-build,libreoffice-writer,security.debian.org
Removed indication that 865866 affects libreoffice-base, live-build, rustc, 
jsvc, libreoffice-writer, security.debian.org, openjdk-7-jre, openjdk-9-jre, 
openjdk-8-jre, and libreoffice
Added indication that 865866 affects 
libreoffice-base,libreoffice,openjdk-9-jre,jsvc,openjdk-7-jre,rustc,openjdk-8-jre,live-build,libreoffice-writer,security.debian.org
Removed indication that 869161 affects libreoffice, openjdk-8-jre, 
openjdk-7-jre, openjdk-9-jre, security.debian.org, libreoffice-writer, jsvc, 
rustc, libreoffice-base, and live-build
Added indication that 869161 affects 
libreoffice-base,libreoffice,openjdk-9-jre,jsvc,openjdk-7-jre,rustc,openjdk-8-jre,live-build,libreoffice-writer,security.debian.org
Removed indication that 869613 affects libreoffice, openjdk-7-jre, 
openjdk-9-jre, openjdk-8-jre, security.debian.org, libreoffice-writer, rustc, 
jsvc, live-build, and libreoffice-base
Added indication that 869613 affects 
libreoffice-base,libreoffice,openjdk-9-jre,jsvc,openjdk-7-jre,rustc,openjdk-8-jre,live-build,libreoffice-writer,security.debian.org
Removed indication that 869649 affects libreoffice-writer, security.debian.org, 
live-build, libreoffice-base, rustc, jsvc, libreoffice, openjdk-7-jre, 
openjdk-9-jre, and openjdk-8-jre
Added indication that 869649 affects 
libreoffice-base,libreoffice,openjdk-9-jre,jsvc,openjdk-7-jre,rustc,openjdk-8-jre,live-build,libreoffice-writer,security.debian.org
Removed indication that 875269 affects security.debian.org, libreoffice-writer, 
rustc, jsvc, libreoffice-base, live-build, libreoffice, openjdk-7-jre, 
openjdk-9-jre, and openjdk-8-jre
Added indication that 875269 affects 
libreoffice-base,libreoffice,openjdk-9-jre,jsvc,openjdk-7-jre,rustc,openjdk-8-jre,live-build,libreoffice-writer,security.debian.org
Removed indication that 876458 affects security.debian.org, libreoffice-writer, 
jsvc, rustc, live-build, libreoffice-base, libreoffice, openjdk-8-jre, 
openjdk-7-jre, and openjdk-9-jre
Added indication that 876458 affects 
libreoffice-base,libreoffice,openjdk-9-jre,jsvc,openjdk-7-jre,rustc,openjdk-8-jre,live-build,libreoffice-writer,security.debian.org
Bug #865866 [src:linux] libreoffice-writer crash on startup Debian 9 i386 arch
Bug #869161 [src:linux] libreoffice-base crashes with code 139 when creating a 
new base or opening an existing one
Bug #869613 

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

[Ben Hutchings]

On Sun, 2017-09-24 at 09:52 +0200, Jochen Sprickerhof wrote:
> Hi,
> 
> Finally I had the time and hardware available to look into this again 
> and found a better way to fix it. Applying the attached patch results in 
> a new exynos5422-odroidxu4.dtb that could simply be copied to /boot/dtbs/*/
> I've tested this with the current kernel in sid (linux-image-4.12.0-2-armmp)
> as well as stretch (linux-image-4.9.0-3-armmp). More tests welcome.
> 
> @Ben: This seems unintrusive enough to be included in the next stretch 
> point release, what do you think?

I'm not applying this until it's accepted upstream.

Ben.

-- 
Ben Hutchings
Make three consecutive correct guesses and you will be considered an
expert.



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

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

[Ben Hutchings]

On Sun, 2017-09-24 at 17:54 +0200, Francesco Poli wrote:
> On Sat, 26 Aug 2017 13:02:18 +0200 Francesco Poli wrote:
> 
> Control: found -1 linux/4.12.13-1
> 
> > 
> > On Mon, 17 Jul 2017 09:59:38 +0200 Francesco Poli wrote:
> 
> [...]
> > Hello again,
> > I tested the new kernel version that has recently migrated to Debian
> > testing.
> > 
> > Unfortunately, I get the same exact boot failure.
> > 
> > And no useful output on the serial console, even with
> > 'earlyprintk=ttyS0' and without 'quiet':
> > 
> > Booting a command list
> > 
> >   Loading Linux 4.12.0-1-686 ...
> >   Loading initial ramdisk ...
> > 
> > and then nothing else.
> 
> Another kernel version has just migrated to Debian testing.
> Another boot failure with no useful output on the serial console, even
> with 'earlyprintk=ttyS0' and without 'quiet':
> 
> Booting a command list
> 
>   Loading Linux 4.12.0-2-686 ...
>   Loading initial ramdisk ...
> 
> and nothing else.
> 
> Is there anything that can be done in order to pinpoint the issue and
> solve it once and for all?!?

You could test the 4.10 kernel version from snapshot.debian.org, which
would narrow down the regresion a bit.

Ben.

> Please let me know, thanks for your time.

-- 
Ben Hutchings
Make three consecutive correct guesses and you will be considered an
expert.



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

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

[Francesco Poli]

Control: found -1 linux/4.12.13-1

[I should have put the above control command at the beginning of my
previous message... I am doing so now.]

-- 
 http://www.inventati.org/frx/
 There's not a second to spare! To the laboratory!
. Francesco Poli .
 GnuPG key fpr == CA01 1147 9CD2 EFDF FB82  3925 3E1C 27E1 1F69 BFFE


pgpp8OHxiW1Pb.pgp
Description: PGP signature

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:

> found -1 linux/4.12.13-1
Bug #868082 [src:linux] linux-image-4.11.0-1-686: fails to boot on i386 
(Soekris net5501)
Marked as found in versions linux/4.12.13-1.

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

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

[Francesco Poli]

On Sat, 26 Aug 2017 13:02:18 +0200 Francesco Poli wrote:

Control: found -1 linux/4.12.13-1

> 
> On Mon, 17 Jul 2017 09:59:38 +0200 Francesco Poli wrote:
[...]
> Hello again,
> I tested the new kernel version that has recently migrated to Debian
> testing.
> 
> Unfortunately, I get the same exact boot failure.
> 
> And no useful output on the serial console, even with
> 'earlyprintk=ttyS0' and without 'quiet':
> 
> Booting a command list
> 
>   Loading Linux 4.12.0-1-686 ...
>   Loading initial ramdisk ...
> 
> and then nothing else.

Another kernel version has just migrated to Debian testing.
Another boot failure with no useful output on the serial console, even
with 'earlyprintk=ttyS0' and without 'quiet':

Booting a command list

  Loading Linux 4.12.0-2-686 ...
  Loading initial ramdisk ...

and nothing else.

Is there anything that can be done in order to pinpoint the issue and
solve it once and for all?!?

Please let me know, thanks for your time.


-- 
 http://www.inventati.org/frx/
 There's not a second to spare! To the laboratory!
. Francesco Poli .
 GnuPG key fpr == CA01 1147 9CD2 EFDF FB82  3925 3E1C 27E1 1F69 BFFE


pgpFrDA9lJ7OM.pgp
Description: PGP signature

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

[Jochen Sprickerhof]

Hi,

Finally I had the time and hardware available to look into this again 
and found a better way to fix it. Applying the attached patch results in 
a new exynos5422-odroidxu4.dtb that could simply be copied to /boot/dtbs/*/

I've tested this with the current kernel in sid (linux-image-4.12.0-2-armmp)
as well as stretch (linux-image-4.9.0-3-armmp). More tests welcome.

@Ben: This seems unintrusive enough to be included in the next stretch 
point release, what do you think?


Cheers Jochen
From 0d3552be829d5a275d549cbf6ab468bfdb026e49 Mon Sep 17 00:00:00 2001
From: Jochen Sprickerhof 
Date: Sun, 24 Sep 2017 08:28:12 +0200
Subject: [PATCH] ARM: dts: exynos: Use dwc3 quirk for USB3 and LAN on Odroid
 XU4

First proposed in https://lkml.org/lkml/2015/3/18/400 and discussed
again in https://lkml.org/lkml/2017/1/24/402.
---
 arch/arm/boot/dts/exynos5422-odroidxu4.dts | 5 +
 1 file changed, 5 insertions(+)

diff --git a/arch/arm/boot/dts/exynos5422-odroidxu4.dts b/arch/arm/boot/dts/exynos5422-odroidxu4.dts
index 2faf88627a48..3861f74b2ecc 100644
--- a/arch/arm/boot/dts/exynos5422-odroidxu4.dts
+++ b/arch/arm/boot/dts/exynos5422-odroidxu4.dts
@@ -43,6 +43,11 @@
 	status = "okay";
 };
 
+_dwc3_0 {
+	snps,dis_u3_susphy_quirk;
+};
+
 _dwc3_1 {
 	dr_mode = "host";
+	snps,dis_u3_susphy_quirk;
 };
-- 
2.14.1



signature.asc
Description: PGP signature