Bug#826796: Request for a new: linux-image-powerpc64-4K

2020-04-22 Thread Ben Hutchings 
On Tue, 2020-04-21 at 11:26 +0200, Mathieu Malaterre wrote:
> Dear Debian-kernel team,
> 
> > Would it be possible to ship an alternate ppc64 kernel build without
> > the 64K page option ?
> 
> Could someone please clarify if this is possible/acceptable ? The new
> ppc64 kernel would not be the default but could be installed on G5
> machine after installation.

I'm sorry this is still unresolved.  I have a couple of questions:

* How will people discover this and know that they should use it?  If
the installer is still being updated for ppc64, shouldn't we select
this kernel automatically when an Nvidia PCI device is detected?

* Has anyone talked to the nouveau developers recently about either (a)
fixing support for larger pages or (b) fixing the dependencies for the
driver so it can't be built in an unsupported configuration?

In any case, if nouveau is completely broken with 64K pages then we
should make sure nouveau is disabled in our default ppc64
configuration.

Ben.

-- 
Ben Hutchings
Time is nature's way of making sure that
everything doesn't happen at once.



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

Debian 10 kernel 4.19.98-1 IO deadlock

2020-04-22 Thread Rumen Telbizov 
Hello Ben and Kernel Team,

A couple of days ago I logged a kernel bug to
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=958368 which causes
sporadic IO hangs/deadlocks to processes that attempts IO of any kind. I am
still hunting for the root cause and was hoping to bring some more
awareness and get your help.

I was wondering if the root cause for the IO lock might be due to a
Debian-specific patch which is not manifested with the upstream kernel. I
could not find any other reports related to this.

In the bug I provide 3 instances of kernel stack traces that I induced.
I would be happy to give more details if needed - please let me know.

Thank you,
-- 
Rumen Telbizov
Unix Systems Administrator

Bug#958494: linux-image-5.5.0-2-amd64: Amdgpu / drm: No video signal/blank screen on resume from suspend

2020-04-22 Thread Facundo Gaich 
Package: src:linux
Version: 5.5.17-1
Severity: normal
Tags: upstream,fixed-in-experimental

Dear Maintainer,

This is a tracking bug for kernel bug #206575 
(https://bugzilla.kernel.org/show_bug.cgi?id=206575), which is fixed in 
experimental.

The problem occurs when using AMD graphic cards and amdgpu driver, after doing a
suspend-to-ram and resuming, the monitor/screen will stay blank or show
 no signal.

This problem is fixed with the kernel in 
linux-image-5.6.0-trunk-amd64:5.6.4-1~exp1

Regards,
Facundo


-- Package-specific info:
** Version:
Linux version 5.5.0-2-amd64 (debian-kernel@lists.debian.org) (gcc version 9.3.0 
(Debian 9.3.0-10)) #1 SMP Debian 5.5.17-1 (2020-04-15)

** Command line:
BOOT_IMAGE=/boot/vmlinuz-5.5.0-2-amd64 
root=UUID=ac43c144-ff3f-4c08-b24e-b9d76e3d66e2 ro loglevel=8

** Not tainted

** Kernel log:
[4.213896] snd_hda_codec_realtek hdaudioC0D0:  Rear Mic=0x18
[4.215770] input: HDA ATI HDMI HDMI/DP,pcm=11 as 
/devices/pci:00/:00:02.0/:01:00.1/sound/card1/input18
[4.217432] snd_hda_codec_realtek hdaudioC0D0:  Line=0x1a
[4.242801] input: HDA ATI SB Front Mic as 
/devices/pci:00/:00:14.2/sound/card0/input19
[4.244655] EDAC amd64: F15h detected (node 0).
[4.244673] input: HDA ATI SB Rear Mic as 
/devices/pci:00/:00:14.2/sound/card0/input20
[4.248111] EDAC amd64: Node 0: DRAM ECC disabled.
[4.248174] input: HDA ATI SB Line as 
/devices/pci:00/:00:14.2/sound/card0/input21
[4.252407] input: HDA ATI SB Line Out Front as 
/devices/pci:00/:00:14.2/sound/card0/input22
[4.254110] input: HDA ATI SB Line Out Surround as 
/devices/pci:00/:00:14.2/sound/card0/input23
[4.254247] input: HDA ATI SB Line Out CLFE as 
/devices/pci:00/:00:14.2/sound/card0/input24
[4.254310] input: HDA ATI SB Line Out Side as 
/devices/pci:00/:00:14.2/sound/card0/input25
[4.254375] input: HDA ATI SB Front Headphone as 
/devices/pci:00/:00:14.2/sound/card0/input26
[4.258773] systemd[1]: Listening on Load/Save RF Kill Switch Status 
/dev/rfkill Watch.
[4.276583] systemd[1]: Condition check resulted in Dispatch Password 
Requests to Console Directory Watch being skipped.
[4.283634] systemd[1]: Condition check resulted in FUSE Control File System 
being skipped.
[4.283712] systemd[1]: Condition check resulted in Kernel Configuration 
File System being skipped.
[4.283785] systemd[1]: Condition check resulted in Set Up Additional Binary 
Formats being skipped.
[4.283803] systemd[1]: Condition check resulted in File System Check on 
Root Device being skipped.
[4.283834] systemd[1]: Condition check resulted in Rebuild Hardware 
Database being skipped.
[4.283875] systemd[1]: Condition check resulted in Platform Persistent 
Storage Archival being skipped.
[4.285483] systemd[1]: Condition check resulted in Dispatch Password 
Requests to Console Directory Watch being skipped.
[4.285603] systemd[1]: Condition check resulted in FUSE Control File System 
being skipped.
[4.285678] systemd[1]: Condition check resulted in Kernel Configuration 
File System being skipped.
[4.285747] systemd[1]: Condition check resulted in Set Up Additional Binary 
Formats being skipped.
[4.285766] systemd[1]: Condition check resulted in File System Check on 
Root Device being skipped.
[4.285794] systemd[1]: Condition check resulted in Rebuild Hardware 
Database being skipped.
[4.285821] systemd[1]: Condition check resulted in Platform Persistent 
Storage Archival being skipped.
[4.299166] EDAC amd64: F15h detected (node 0).
[4.299200] EDAC amd64: Node 0: DRAM ECC disabled.
[4.348820] EDAC amd64: F15h detected (node 0).
[4.350210] EDAC amd64: Node 0: DRAM ECC disabled.
[4.353475] systemd[1]: Started Journal Service.
[4.364948] systemd-journald[372]: Received client request to flush runtime 
journal.
[4.389300] EDAC amd64: F15h detected (node 0).
[4.392728] EDAC amd64: Node 0: DRAM ECC disabled.
[4.441325] EDAC amd64: F15h detected (node 0).
[4.444675] EDAC amd64: Node 0: DRAM ECC disabled.
[4.693311] EDAC amd64: F15h detected (node 0).
[4.696690] EDAC amd64: Node 0: DRAM ECC disabled.
[5.428318] random: crng init done
[5.430722] random: 7 urandom warning(s) missed due to ratelimiting
[   17.615174] EXT4-fs (dm-0): mounted filesystem with ordered data mode. Opts: 
(null)
[   17.662418] audit: type=1400 audit(1587587166.554:2): apparmor="STATUS" 
operation="profile_load" profile="unconfined" name="libreoffice-senddoc" 
pid=558 comm="apparmor_parser"
[   17.664032] audit: type=1400 audit(1587587166.554:3): apparmor="STATUS" 
operation="profile_load" profile="unconfined" name="nvidia_modprobe" pid=560 
comm="apparmor_parser"
[   17.56] audit: type=1400 audit(1587587166.554:4): apparmor="STATUS" 
operation="profile_load" profile="unconfined" name="nvidia_modprobe//kmod" 
pid=560 comm="apparmor_parser"
[

Bug#952660: src:linux: macvlan multicast/broadcast regression in stretch

2020-04-22 Thread Tero Marttila 
This seems to also affect keepalived `use_vmac` configurations, where 
the keepalived VIPs are configured on macvlan interfaces. After a 
stretch kernel update from 4.9.0-11-amd64 (4.9.189) to 4.9.0-12-amd64 
(4.9.209) the keepalived VIPs stop responding to ARP queries, causing 
the VIP to remain configured but unreachable on the VRRP master.

Bug#954245: marked as done (Fresh installed debian stucks in 'Load initramfs' screen on lenovo x230 due to missing module)

2020-04-22 Thread Debian Bug Tracking System 
Your message dated Wed, 22 Apr 2020 13:32:51 +0100
with message-id <361f4ec55998478dde9a748d77430093e09480d8.ca...@decadent.org.uk>
and subject line Re: Bug#954245: Fresh installed debian stucks in 'Load 
initramfs' screen on lenovo x230 due to missing module
has caused the Debian Bug report #954245,
regarding Fresh installed debian stucks in 'Load initramfs' screen on lenovo 
x230 due to missing module
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.)


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

Package: initramfs-tools
Version: 0.133+deb10u1

To reproduce the issue described in the subject:
 1.) Download a recent debian-netinst.iso (tested with 
debian-10.3.0-amd64-netinst.iso)
 2.) Run into installation-process
 3.) Let the network-configuration fail
 4.) Continue without network
 5.) Choose encrypted lvm
 6.) Install the base-system only (no mirrors)
 7.) Finish the installation and reboot

After the reboot the system freezes in grubs 'Loading initramfs' screen, 
because the i915 mode setting driver is missing in the initramfs.
(https://wiki.archlinux.org/index.php/Lenovo_ThinkPad_X230)
One need to explicitly add i915 to /etc/initramfs-tools/modules and rebuild 
initramfs or simply install plymouth, which manages the same result via its 
initramfs-hook.

This issue does not occur, if:
 * The disk isn't encrypted => The System jumps directly into the 
login-terminal without asking for a passphrase
 * Full network-installation is performed, which pulls plymouth by certain 
dependencies
--- End Message ---
--- Begin Message ---
On Wed, 2020-04-22 at 11:17 +0200, Dimitri Schwarz wrote:
[...]
> I have had already forgotten the fact, that my system is flashed with
> coreboot SeaVGABIOS. If an off the shelf x230 is working fine, which you
> verified, I suppose it is ok for this issue to occur in  this rare
> constellation.

So I'm closing this as not our bug.

Ben.

-- 
Ben Hutchings
Experience is what causes a person to make new mistakes
instead of old ones.




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

Bug#954245: Fresh installed debian stucks in 'Load initramfs' screen on lenovo x230 due to missing module

2020-04-22 Thread Dimitri Schwarz 

Am 30.03.20 um 03:13 schrieb Ben Hutchings:

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

On Thu, 2020-03-19 at 10:27 +0100, Dimitri Schwarz wrote:

Package: initramfs-tools
Version: 0.133+deb10u1

To reproduce the issue described in the subject:
   1.) Download a recent debian-netinst.iso (tested with debian-
10.3.0-amd64-netinst.iso)
   2.) Run into installation-process
   3.) Let the network-configuration fail
   4.) Continue without network
   5.) Choose encrypted lvm
   6.) Install the base-system only (no mirrors)
   7.) Finish the installation and reboot

After the reboot the system freezes in grubs 'Loading initramfs'
screen, because the i915 mode setting driver is missing in the
initramfs.

[...]

It should not be needed.  On PCs, the system firmware sets up the
display and the kernel (like GRUB) will use a generic graphics driver
until the i915 or other hardware-specific driver is loaded.

I have an X230 here and tried removing plymouth, and it was still able
to prompt for my disk encryption password.  However, it's been upgraded
from an earlier release and is booting in BIOS mode.

* Does your system boot in BIOS or UEFI mode?  (You can tell by
checking whether grub-pc or grub-efi-amd64 is installed.)

* Does it make any difference if you use the "recovery mode" entry in
the GRUB menu?

Ben.



Hi Ben,

thank you for your recheck and please excuse my late answer.

I have had already forgotten the fact, that my system is flashed with
coreboot SeaVGABIOS. If an off the shelf x230 is working fine, which you
verified, I suppose it is ok for this issue to occur in  this rare
constellation.

Thanks again,
Dimitri

Bug#826098: marked as done (fakeroot make -f debian/rules.gen binary-arch_powerpc_none_powerpc)

2020-04-22 Thread Debian Bug Tracking System 
Your message dated Wed, 22 Apr 2020 08:58:37 +0200
with message-id 

and subject line 
has caused the Debian Bug report #826098,
regarding fakeroot make -f debian/rules.gen binary-arch_powerpc_none_powerpc
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.)


-- 
826098: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=826098
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:linux
Version: 4.5.5-1

I am starring at the documentation for rebuilding the Debian kernel.
I'd like to test a change in a non-module section of the kernel code
(CONFIG_FB_OF=y), to resolve #825840. So I thought I could simply
follows the steps from:

https://kernel-handbook.alioth.debian.org/ch-common-tasks.html#s4.2.5

[...]
# apt-get install build-essential fakeroot
# apt-get build-dep linux
$ mkdir tmp && cd tmp
$ apt-get source linux-image-$(uname -r)
$ cd linux-*
$ fakeroot debian/rules source
$ fakeroot make -f debian/rules.gen binary-arch_powerpc_none_powerpc
[...]
dh_installdocs
dh_installchangelogs
dh_strip
Can't exec "-objcopy": No such file or directory at
/usr/share/perl5/Debian/Debhelper/Dh_Lib.pm line 243.
dh_strip: -objcopy --only-keep-debug --compress-debug-sections
debian/linux-image-4.5.0-2-powerpc/usr/lib/linux-image-4.5.0-2-powerpc/hack-coff
debian/.debhelper/linux-image-4.5.0-2-powerpc/dbgsym-root/usr/lib/debug/.build-id/db/692a8d7808bd1b2adc58cd43f114d6fe006303.debug
failed to to execute: No such file or directory
debian/rules.real:194: recipe for target 'install-base' failed
make[2]: *** [install-base] Error 2
make[2]: Leaving directory '/home/mathieu/tmp/linux-4.5.4'
debian/rules.real:376: recipe for target
'install-image_powerpc_none_powerpc' failed
make[1]: *** [install-image_powerpc_none_powerpc] Error 2
make[1]: Leaving directory '/home/mathieu/tmp/linux-4.5.4'
debian/rules.gen:204: recipe for target
'binary-arch_powerpc_none_powerpc_real' failed
make: *** [binary-arch_powerpc_none_powerpc_real] Error 2

I can see objcopy right here:

mathieu@debian:~/tmp/linux-4.5.4$ ls -al /usr/bin/*objcopy
lrwxrwxrwx 1 root root 25 May 12 16:59 /usr/bin/objcopy ->
powerpc-linux-gnu-objcopy
-rwxr-xr-x 1 root root 266200 May 12 16:59 /usr/bin/powerpc-linux-gnu-objcopy

And I am using:

mathieu@debian:~/tmp/linux-4.5.4$ uname -a
Linux debian 4.5.0-2-powerpc #1 Debian 4.5.4-1 (2016-05-16) ppc GNU/Linux

Does anyone know how to build only the powperpc flavor from a powerpc system ?

Thanks much.
--- End Message ---
--- Begin Message ---
This can be closed now.--- End Message ---