Bug#1068356: linux-image-6.1.0-18-amd64: it's working as expected - please delete this bug report

[Veek M]

Package: src:linux
Followup-For: Bug #1068356
X-Debbugs-Cc: vek.m1...@gmail.com

Please ignore this bug report - it's working as expected and isn't a bug

Bug#1068356: linux-image-6.1.0-18-amd64: Debian 12.5 6.1.0-18-amd64 hibernate works the 1st time then "no space left on device" in journalctl

[Veek M]

Package: src:linux
Version: 6.1.76-1
Severity: important
X-Debbugs-Cc: vek.m1...@gmail.com

Dear Maintainer,
   * What led up to the situation?
doing systemctl hibernate led to the issue

   * What exactly did you do (or not do) that was effective (or
 ineffective)?
the swap space in the swap-partition is not free'd hence the issue. 
Doing swapoff /dev/sda3 and then swapon /dev/sda3 allows you to do 
a 2nd hibernation.


-- Package-specific info:
** Version:
Linux version 6.1.0-18-amd64 (debian-kernel@lists.debian.org) (gcc-12 (Debian 
12.2.0-14) 12.2.0, GNU ld (GNU Binutils for Debian) 2.40) #1 SMP 
PREEMPT_DYNAMIC Debian 6.1.76-1 (2024-02-01)

** Command line:
BOOT_IMAGE=/boot/vmlinuz-6.1.0-18-amd64 
root=UUID=58b9f571-0c71-404b-bc1c-3c2bce44651e ro quiet

** Not tainted

** Kernel log:
[ 7165.457863] psmouse serio1: synaptics: queried max coordinates: x [..5792], 
y [..4930]
[ 7165.485066] psmouse serio1: synaptics: queried min coordinates: x [1142..], 
y [924..]
[ 7165.600195] usb 1-1: reset high-speed USB device number 2 using ehci-pci
[ 7165.600235] usb 3-1: reset high-speed USB device number 2 using ehci-pci
[ 7165.624986] ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
[ 7165.625033] ata1.00: Entering active power mode
[ 7165.733802] ata1.00: ACPI cmd ef/10:03:00:00:00:a0(SET FEATURES) filtered out
[ 7165.743730] ata1.00: ACPI cmd ef/10:03:00:00:00:a0(SET FEATURES) filtered out
[ 7165.744385] ata1.00: configured for UDMA/133
[ 7166.076214] usb 1-1.2: reset full-speed USB device number 4 using ehci-pci
[ 7166.264016] usb 1-1.3: reset high-speed USB device number 3 using ehci-pci
[ 7166.685408] iwlwifi :02:00.0: Radio type=0x2-0x0-0x0
[ 7166.974423] iwlwifi :02:00.0: Radio type=0x2-0x0-0x0
[ 7167.060392] PM: hibernation: Basic memory bitmaps freed
[ 7167.061723] OOM killer enabled.
[ 7167.061729] Restarting tasks ... 
[ 7167.065019] Bluetooth: hci0: unexpected event for opcode 0x
[ 7167.066972] done.
[ 7167.079162] PM: hibernation: hibernation exit
[ 7167.678674] wlp2s0: authenticate with 80:26:89:c3:6d:c2
[ 7167.681737] wlp2s0: send auth to 80:26:89:c3:6d:c2 (try 1/3)
[ 7167.686166] wlp2s0: authenticated
[ 7167.686461] wlp2s0: waiting for beacon from 80:26:89:c3:6d:c2
[ 7167.743863] wlp2s0: associate with 80:26:89:c3:6d:c2 (try 1/3)
[ 7167.752254] wlp2s0: RX AssocResp from 80:26:89:c3:6d:c2 (capab=0x411 
status=0 aid=1)
[ 7167.766998] wlp2s0: associated
[ 7279.848345] perf: interrupt took too long (3285 > 3278), lowering 
kernel.perf_event_max_sample_rate to 60750
[ 7846.625684] PM: hibernation: hibernation entry
[ 7846.626180] (NULL device *): firmware: direct-loading firmware regulatory.db
[ 7846.626528] (NULL device *): firmware: direct-loading firmware 
iwlwifi-2030-6.ucode
[ 7846.627233] (NULL device *): firmware: direct-loading firmware 
regulatory.db.p7s
[ 7846.638138] Filesystems sync: 0.010 seconds
[ 7846.638479] Freezing user space processes
[ 7846.641720] Freezing user space processes completed (elapsed 0.003 seconds)
[ 7846.641733] OOM killer disabled.
[ 7846.641845] PM: hibernation: Marking nosave pages: [mem 
0x-0x0fff]
[ 7846.641854] PM: hibernation: Marking nosave pages: [mem 
0x0009e000-0x000f]
[ 7846.641864] PM: hibernation: Marking nosave pages: [mem 
0x2000-0x201f]
[ 7846.641898] PM: hibernation: Marking nosave pages: [mem 
0x40004000-0x40004fff]
[ 7846.641903] PM: hibernation: Marking nosave pages: [mem 
0xca28f000-0x]
[ 7846.649663] PM: hibernation: Basic memory bitmaps created
[ 7846.649998] PM: hibernation: Preallocating image memory
[ 7849.731022] PM: hibernation: Allocated 352092 pages for snapshot
[ 7849.731036] PM: hibernation: Allocated 1408368 kbytes in 3.08 seconds 
(457.26 MB/s)
[ 7849.731045] Freezing remaining freezable tasks
[ 7849.732671] Freezing remaining freezable tasks completed (elapsed 0.001 
seconds)
[ 7849.733005] printk: Suspending console(s) (use no_console_suspend to debug)
[ 7849.733217] wlp2s0: deauthenticating from 80:26:89:c3:6d:c2 by local choice 
(Reason: 3=DEAUTH_LEAVING)
[ 7849.752139] ata1.00: Entering standby power mode
[ 7849.981920] ACPI: PM: Preparing to enter system sleep state S4
[ 7849.982658] ACPI: PM: Saving platform NVS memory
[ 7849.984565] Disabling non-boot CPUs ...
[ 7849.986646] smpboot: CPU 1 is now offline
[ 7849.990274] smpboot: CPU 2 is now offline
[ 7849.993445] smpboot: CPU 3 is now offline
[ 7849.994083] PM: hibernation: Creating image:
[ 7850.262253] PM: hibernation: Need to copy 345294 pages
[ 7850.262262] PM: hibernation: Normal pages needed: 345294 + 1024, available 
pages: 676103
[ 7851.142004] PM: hibernation: Image created (345294 pages copied)
[ 7849.994729] ACPI: PM: Restoring platform NVS memory
[ 7849.995556] Enabling non-boot CPUs ...
[ 7849.995669] x86: Booting SMP configuration:
[ 7849.995672] smpboot: Booting Node 0 Processor 1 APIC 0x1
[ 7849.999557] CPU1 is up
[ 7849.999647] smpboot: Booting Node 0 Processor 2 APIC 0x2
[ 7850.003682] CPU2 is up
[ 

Bug#1040416: linux-image-6.1.0-9-amd64: Under heavy load Debian V12 and V11 causes data corruption on XFS filesystems.

[Jose M Calhariz]

Hi

On Tue, Nov 07, 2023 at 08:33:58PM +0100, Diederik de Haas wrote:
> Control: found -1 6.1~rc3-1~exp1
> Control: found -1 6.1.55-1
> 
> On Saturday, 4 November 2023 20:35:43 CET Jose M Calhariz wrote:
> > > Ok. Please test (when you have time) 6.1.55-1.
> > 
> > Fail : Linux afs31 6.1.0-0-amd64 #1 SMP PREEMPT_DYNAMIC Debian
> > 6.1~rc3-1~exp1 (2022-11-02) x86_64 GNU/Linux
> > 
> > Fail : Linux afs31 6.1.0-13-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.1.55-1
> > (2023-09-29) x86_64 GNU/Linux
> > 
> > Done.  I tested even the first 6.1 on Debian.  Both of them failed.
> 
> Thanks, updated metadata accordingly.
> So now we know it's indeed present in the whole 6.1 series.
> 
> > > Unfortunately there isn't a 6.2 kernel uploaded to the Debian archive and
> > > thus not available on snapshot.d.o, but testing 6.3.1-1~exp1 should be
> > > useful.
> 
> Please test with with 6.3.1-1~exp1 to make sure it was fixed then (too).
> 
> Unfortunately, the commit list between 6.1 and 6.3.1 is quite large:
> me@pc:~/dev/kernel.org/linux$ git log --oneline v6.1..v6.3.1 -- fs/xfs | wc -l
> 159
> 
> If that list was small, I could've suggested to try 'backporting' a couple of 
> patches, but that avenue seems rather pointless in this case.
> 
> It's probably also useful to verify whether it's also present in the whole 
> 5.10 series, which should give (even) more data points.
> 
> I think the next step should be to 'forward' this bug report to the upstream 
> mailing list at linux-...@vger.kernel.org

I do not follow closely linux-xfs mailing list, but I think other
people already reported problems with 6.1 and are trying to do the
effort of delimiting the patch and test a backport to 6.1.

Kind regards
Jose M Calhariz

-- 
--
Egoista, s. m. Um sujeito mais interessado em si próprio que
em mim.
-- Ambrose Bierce


signature.asc
Description: PGP signature

Bug#1040416: linux-image-6.1.0-9-amd64: Under heavy load Debian V12 and V11 causes data corruption on XFS filesystems.

[Jose M Calhariz]

Hi

On Thu, Nov 02, 2023 at 07:40:38PM +0100, Diederik de Haas wrote:
> 
> On Thursday, 2 November 2023 18:03:25 CET Jose M Calhariz wrote:
> > On Thu, Nov 02, 2023 at 03:37:39PM +0100, Diederik de Haas wrote:
> > > On Wednesday, 5 July 2023 19:07:15 CET Jose M Calhariz wrote:
> > > > Package: src:linux
> > > > Version: 6.1.27-1
> > > 
> > > Can you try with the latest version in the 6.1.x series to see if the
> > > problem is still there?
> > 
> > As I need to setup ASAP the servers in production I do not know if I
> > have time in the next days.  It works with backports kernels.
> 
> No problem.
> 
> > The latest kernels I tested were:
> > Fail : Linux afs31 6.1.0-10-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.1.37-1
> > (2023-07-03) x86_64 GNU/Linux
> 
> Ok. Please test (when you have time) 6.1.55-1.

Fail : Linux afs31 6.1.0-0-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.1~rc3-1~exp1 
(2022-11-02) x86_64 GNU/Linux

Fail : Linux afs31 6.1.0-13-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.1.55-1 
(2023-09-29) x86_64 GNU/Linux

Done.  I tested even the first 6.1 on Debian.  Both of them failed.




> Also verify if it's also present in 6.1~rc3-1~exp1 to make sure it's present 
> in the whole 6.1 series.
> Use https://snapshot.debian.org/binary/linux-image-amd64/ to get it/them.
> 
> If the bug is NOT present in either the latest or the first, then try other 
> versions till you find the last one that work and the first one that fails.
> 
> > OK : Linux afs31 6.4.0-0.deb12.2-amd64 #1 SMP PREEMPT_DYNAMIC Debian
> > 6.4.4-3~bpo12+1 (2023-08-08) x86_64 GNU/Linux
> 
> It was fixed in 6.3.7-1, so it was expected that a later versions also works.
> But let's ignore bpo as it likely won't provide useful data points.
> 
> Unfortunately there isn't a 6.2 kernel uploaded to the Debian archive and 
> thus 
> not available on snapshot.d.o, but testing 6.3.1-1~exp1 should be useful.
> 
> > The bug is present on Debian v11 too.  So is an old bug with fixes on
> > kernel 6.2 rc something.
> 
> I'd recommend to focus first on the 6.1 series for now.
> If at a later point testing with 5.10 may be useful, we can do that then.


Kind regards
Jose M Calhariz


-- 
--
A vida feliz, meu Deus, consiste em nos alegrarmos em vos,
de vos e por vos


signature.asc
Description: PGP signature

Bug#1032391: Under heavy load Debian V12 and V11 causes data corruption on XFS filesystems.

[Jose M Calhariz]

Hi,

After some research it was found the problem was not HW related, but
related with XFS driver and is present until linux 6.1.  So I opened
new bug report on
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1040416

Kind regards
Jose M Calhariz


-- 
--
A vida feliz, meu Deus, consiste em nos alegrarmos em vos,
de vos e por vos


signature.asc
Description: PGP signature

Bug#1040416: linux-image-6.1.0-9-amd64: Under heavy load Debian V12 and V11 causes data corruption on XFS filesystems.

[Jose M Calhariz]

On Thu, Nov 02, 2023 at 03:37:39PM +0100, Diederik de Haas wrote:
> Control: tag -1 moreinfo
> 
> On Wednesday, 5 July 2023 19:07:15 CET Jose M Calhariz wrote:
> > Package: src:linux
> > Version: 6.1.27-1
> 
> Can you try with the latest version in the 6.1.x series to see if the problem 
> is still there?

As I need to setup ASAP the servers in production I do not know if I
have time in the next days.  It works with backports kernels.

The latest kernels I tested were:

Fail : Linux afs31 6.1.0-10-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.1.37-1 
(2023-07-03) x86_64 GNU/Linux

OK : Linux afs31 6.4.0-0.deb12.2-amd64 #1 SMP PREEMPT_DYNAMIC Debian 
6.4.4-3~bpo12+1 (2023-08-08) x86_64 GNU/Linux



> 
> > On this hardware I am chasing a data corruption for several months on
> > Debian V11 and Debian v12.  Now that I was pointed that linux kernel
> > had some problems with XFS solved in later 6.3 kernel I can reproduce
> > the problem.
> > 
> > It seams the problem went away with current Debian testing kernel:
> > 
> > ii  linux-image-6.3.0-1-amd646.3.7-1  amd64Linux 6.3
> > for 64-bit PCs (signed)
> > 
> > Is there anyone willing to backport the XFS fixes into
> > linux-image-6.1.0 and linux-image-5.10.0?
> 
> If the problem is still present in the latest 6.1 kernel, then you need to 
> find 
> out which patch(es) actually fix the problem.
> The easiest way to start with that is to find the last kernel which exhibits 
> the issue and then the first one where it is fixed.
> https://snapshot.debian.org/binary/linux-image-amd64/ should help
> with that.

The bug is present on Debian v11 too.  So is an old bug with fixes on
kernel 6.2 rc something.

> 
> When the range has been narrowed, a `git bisect` should identify the specific 
> commit(s) which fixes the issue.
> https://wiki.debian.org/DebianKernel/GitBisect should help with that
> 
> When that/those have been identified, it should be reported to the upstream 
> kernel so that they can incorporate those fixes in their LTS kernel(s) which 
> Debian then will pick up automatically.
> 
> HTH



-- 
--
A vida feliz, meu Deus, consiste em nos alegrarmos em vos,
de vos e por vos


signature.asc
Description: PGP signature

Re: Upcoming changes to Debian Linux kernel packages

[M. Zhou]

On Mon, 2023-09-25 at 04:35 +0200, Andreas Beckmann wrote:
> On 25/09/2023 00.50, Bastian Blank wrote:
> > Already built modules remain until someone deletes it.  So you can
> > also
> > switch back to the still installed older kernel version and it will
> > have
> > the still working module available.
> 
> This is what I expect not to work.
> 
> Assume I have Linux 6.6 and a third-party gpu driver module installed
> (so there are dkms and the Linux 6.6 headers as well) and everything
> is 
> working fine.
> Then I upgrade the system, which brings Linux 6.7 (along linux-image-
> 6.6 
> which is kept installed) and a new version of the gpu driver (which
> adds 
> support for 6.7). So the old gpu module for 6.6 gets removed and a
> new 
> one is built for 6.7 only (since there are only 6.7 headers now).
> Unfortunately 6.7 breaks some exotic in-tree driver (which I
> desperately 
> need), so I need to go back to 6.6. Oops, there is no gpu driver
> module 
> any more. Recovery now needs manual intervention.

Same concern here. We cannot pose strong assumption on the user's
upgrade path. The said scenario may happen for any dkms package
when the newer kernel version is not supported.

> I'm not sure which class of bugs you are trying to solve with this 
> proposed unversioned linux-headers change. IMO the current scheme of 
> linux-headers-$version-$abi-$flavor matching 
> linux-image-$version-$abi-$flavor works well. But perhaps something 
> could be improved on the metapackage side. Ideally a user should
> install 
> either meta-linux-image-without-headers-$flavor OR 
> meta-linux-image-with-headers-$flavor (and ideally installing dkms 
> should "automatically switch" to the with-headers variant, not sure
> how 
> this could be done). The current scheme of having to install 
> linux-image-$flavor AND linux-headers-$flavor is a bit tricky.
> I'm open to implement improvements on the dkms side.

I could not understand the benefit of it neither. Apart from the dkms
part, the user-customized kernel packages cannot be omitted as well.

For instance, if I build a customized kernel from debian's kernel
source, using `make bindeb-pkg`, I get those:

linux-headers-6.5.3_6.5.3-2_amd64.deb
linux-image-6.5.3_6.5.3-2_amd64.deb
linux-libc-dev_6.5.3-2_amd64.deb

Currently they are well integrated into the system, and IIRC dkms
also works for them. If versioning is gone, how to make it
compatible with user's local kernel package? There must be two
copies of kernel headers in the system in this case because we
cannot remove user's local customized headers on our own.

Then the design still has to support multi version co-existence.

Bug#1043024: amdgpu: When updating I get a "Possible missing firmware /lib/firmware/amdgpu/modules" (Sapphire Nitro R9 390)

[Aly M. Ghobashy]

Hello Gregor,

Sorry for the late reply, didn't get the update in my email.

This is the output from apt when I update my system:

Processing triggers for initramfs-tools (0.142) ...
update-initramfs: Generating /boot/initrd.img-6.1.0-11-amd64
W: Possible missing firmware /lib/firmware/amdgpu/ip_discovery.bin for 
module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/vega10_cap.bin for 
module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/sienna_cichlid_cap.bin 
for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/navi12_cap.bin for 
module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/psp_13_0_11_ta.bin for 
module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/psp_13_0_11_toc.bin 
for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/psp_13_0_10_ta.bin for 
module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/psp_13_0_10_sos.bin 
for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/aldebaran_cap.bin for 
module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/gc_11_0_3_imu.bin for 
module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/gc_11_0_4_rlc.bin for 
module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/gc_11_0_4_mec.bin for 
module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/gc_11_0_4_me.bin for 
module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/gc_11_0_4_pfp.bin for 
module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/gc_11_0_3_rlc.bin for 
module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/gc_11_0_3_mec.bin for 
module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/gc_11_0_3_me.bin for 
module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/gc_11_0_3_pfp.bin for 
module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/gc_11_0_0_toc.bin for 
module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/sdma_6_0_3.bin for 
module amdgpu
W: Possible missing firmware 
/lib/firmware/amdgpu/sienna_cichlid_mes1.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/sienna_cichlid_mes.bin 
for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/navi10_mes.bin for 
module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/gc_11_0_4_mes1.bin for 
module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/gc_11_0_4_mes_2.bin 
for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/gc_11_0_4_mes.bin for 
module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/gc_11_0_3_mes1.bin for 
module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/gc_11_0_3_mes_2.bin 
for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/gc_11_0_3_mes.bin for 
module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/gc_11_0_2_mes_2.bin 
for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/gc_11_0_1_mes_2.bin 
for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/gc_11_0_0_mes_2.bin 
for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/smu_13_0_10.bin for 
module amdgpu



Never had any issue with Debian other than this, besides this it's flawless


On Sat, 05 Aug 2023 10:45:46 +0200 Gregor Riepl  wrote:

> Package: firmware-amd-graphics
> Version: 20230515-3
> Followup-For: Bug #1043024
> X-Debbugs-Cc: onit...@gmail.com
>
> Can you post which firmware files are missing exactly?
>
> dmesg should give you all the needed information.
>
>
> -- System Information:
> Debian Release: trixie/sid
> APT prefers testing
> APT policy: (990, 'testing'), (500, 'unstable-debug'), (500, 
'testing-debug'), (500, 'stable-debug'), (500, 
'proposed-updates-debug'), (300, 'unstable'), (1, 'experimental-debug'), 
(1, 'experimental')

> Architecture: amd64 (x86_64)
> Foreign Architectures: i386
>
> Kernel: Linux 6.4.0-1-amd64 (SMP w/24 CPU threads; PREEMPT)
> Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_GB

> Shell: /bin/sh linked to /usr/bin/dash
> Init: systemd (via /run/systemd/system)
> LSM: AppArmor: enabled
>
> firmware-amd-graphics depends on no packages.
>
> firmware-amd-graphics recommends no packages.
>
> Versions of packages firmware-amd-graphics suggests:
> ii initramfs-tools 0.142
>
> -- no debconf information
>
>

Problem with a custom kernel and my Debian-based distribution

[Ángel M]

Good afternoon, I send you my best regards.

I'm having a problem creating a custom kernel image for my own Debian based
distribution, in this case I'm working with version 5.15.124.

Let me explain my problem:
At the time of making the kernel compilation I take a predefined
configuration, it could be from kernel 5.10, that .config file I replace it
and then I make some adjustments with make menuconfig, I change the name of
the version for the one of my distribution. After that I make a make
deb-pkg, to generate the .deb files of the kernel, up to there everything
well, it is generated without any problem.

Once these packages are generated, I upload them to my own test repository,
which basically is the Debian repository, but with modifications of certain
packages of the base. Inside that repository is all the kernel 5.10
packages.

After that, I build the linux-image-amd64 and linux-headers-amd64
metapackages, with the respective dependencies. When I proceed to generate
an ISO image with the livebuild method pointing to my test repositories,
the ISO image is generated without problems. When I try to test the ISO
image on a computer with strict UEFI I get the following error:




*error: invalid file name 'vmlinuz'.error: you need to load the kernel
first.Press any key to continue...*

When I check the live boot entries I find no problem, as the name matches.
This happens only when I want to launch the live system, because if I want
to install it, it performs the process and installs the operating system. I
hope you can help me with my problem, I appreciate all your support.
Greetings and excuse my English. (:

Bug#1050654: linux-image-6.4.0-3-amd64: Virtualbox kernel modules fail to load on linux-image-6.4.0-3-amd64

[Timothy M Dowd]

Package: src:linux
Version: 6.4.11-1
Severity: important
X-Debbugs-Cc: mrdowdsouthmo...@gmail.com

Dear Maintainer,

Upon update to kernel 6.4.0-3-amd64, Virtualbox kernel modules no longer load. 
Virtualbox works normally when booting with kernel 6.4.0-2

-- Package-specific info:
** Version:
Linux version 6.4.0-3-amd64 (debian-kernel@lists.debian.org) (gcc-13 (Debian 
13.2.0-2) 13.2.0, GNU ld (GNU Binutils for Debian) 2.41) #1 SMP PREEMPT_DYNAMIC 
Debian 6.4.11-1 (2023-08-17)

** Command line:
BOOT_IMAGE=/boot/vmlinuz-6.4.0-3-amd64 
root=UUID=ad35bc11-3df5-42f2-b165-43cd90fb4c8d ro quiet

** Not tainted

** Kernel log:
Unable to read kernel log; any relevant messages should be attached

I looked at dmesg and didn't see anything related to Virtualbox

** Model information
sys_vendor: HP
product_name: HP Notebook
product_version: Type1ProductConfigId
chassis_vendor: Hewlett-Packard
chassis_version: Chassis Version
bios_vendor: Insyde
bios_version: F.14
board_vendor: HP
board_name: 81F1
board_version: 64.31

** Loaded modules:
rfcomm
ctr
ccm
qrtr
cmac
algif_hash
algif_skcipher
af_alg
bnep
binfmt_misc
nls_ascii
nls_cp437
vfat
fat
btusb
btrtl
btbcm
btintel
btmtk
bluetooth
uvcvideo
videobuf2_vmalloc
jitterentropy_rng
uvc
videobuf2_memops
videobuf2_v4l2
drbg
videodev
videobuf2_common
ansi_cprng
ecdh_generic
mc
ecc
intel_powerclamp
coretemp
snd_hda_codec_hdmi
snd_ctl_led
kvm_intel
snd_hda_codec_realtek
rtl8723be
snd_hda_codec_generic
kvm
ledtrig_audio
btcoexist
rtl8723_common
rtl_pci
irqbypass
snd_hda_intel
rtlwifi
snd_intel_dspcfg
snd_intel_sdw_acpi
mac80211
snd_hda_codec
snd_hda_core
ghash_clmulni_intel
sha512_ssse3
libarc4
snd_hwdep
sha512_generic
cfg80211
snd_pcm
processor_thermal_device_pci_legacy
aesni_intel
mei_hdcp
mei_pxp
processor_thermal_device
snd_timer
joydev
hp_wmi
snd
crypto_simd
cryptd
iTCO_wdt
mei_txe
rmi_smbus
sparse_keymap
soundcore
rmi_core
intel_rapl_msr
intel_pmc_bxt
mei
processor_thermal_rfim
processor_thermal_mbox
processor_thermal_rapl
intel_cstate
pcspkr
intel_rapl_common
platform_profile
iTCO_vendor_support
at24
rfkill
watchdog
intel_xhci_usb_role_switch
wmi_bmof
roles
sg
ac
intel_int0002_vgpio
pwm_lpss_platform
intel_soc_dts_iosf
pwm_lpss
serio_raw
evdev
int3403_thermal
int3400_thermal
int340x_thermal_zone
acpi_thermal_rel
parport_pc
ppdev
lp
parport
dm_mod
fuse
loop
efi_pstore
configfs
efivarfs
ip_tables
x_tables
autofs4
ext4
crc16
mbcache
jbd2
crc32c_generic
sd_mod
t10_pi
crc64_rocksoft
crc64
sr_mod
crc_t10dif
cdrom
crct10dif_generic
i915
ahci
drm_buddy
i2c_algo_bit
libahci
xhci_pci
drm_display_helper
libata
cec
xhci_hcd
rc_core
ttm
drm_kms_helper
scsi_mod
usbcore
r8169
crct10dif_pclmul
crct10dif_common
realtek
i2c_i801
crc32_pclmul
mdio_devres
drm
psmouse
crc32c_intel
libphy
i2c_smbus
lpc_ich
usb_common
scsi_common
fan
battery
video
wmi
button

** Network interface configuration:
*** /etc/network/interfaces:

source /etc/network/interfaces.d/*

auto lo
iface lo inet loopback

allow-hotplug enp3s0
iface enp3s0 inet dhcp

** Network status:
*** IP interfaces and addresses:
1: lo:  mtu 65536 qdisc noqueue state UNKNOWN group 
default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
   valid_lft forever preferred_lft forever
inet6 ::1/128 scope host noprefixroute 
   valid_lft forever preferred_lft forever
2: enp3s0:  mtu 1500 qdisc fq_codel state 
DOWN group default qlen 1000
link/ether 98:e7:f4:88:c3:03 brd ff:ff:ff:ff:ff:ff
inet 169.254.12.68/16 brd 169.254.255.255 scope link enp3s0:avahi
   valid_lft forever preferred_lft forever
3: wlp2s0:  mtu 1500 qdisc noqueue state UP 
group default qlen 1000
link/ether cc:b0:da:63:f1:87 brd ff:ff:ff:ff:ff:ff
inet 192.168.254.20/24 brd 192.168.254.255 scope global dynamic 
noprefixroute wlp2s0
   valid_lft 13401sec preferred_lft 13401sec
inet6 fe80::404c:717d:d383:2b62/64 scope link noprefixroute 
   valid_lft forever preferred_lft forever

*** Device statistics:
Inter-|   Receive|  Transmit
 face |bytespackets errs drop fifo frame compressed multicast|bytes
packets errs drop fifo colls carrier compressed
lo:8786 100000 0  0 0 8786 
100000 0   0  0
enp3s0:   0   0000 0  0 00  
 0000 0   0  0
wlp2s0:  4288711327000 0  0 0   109879 
362000 0   0  0


** PCI devices:
00:00.0 Host bridge [0600]: Intel Corporation Atom/Celeron/Pentium Processor 
x5-E8000/J3xxx/N3xxx Series SoC Transaction Register [8086:2280] (rev 35)
Subsystem: Hewlett-Packard Company Atom/Celeron/Pentium Processor 
x5-E8000/J3xxx/N3xxx Series SoC Transaction Register [103c:81f1]
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-

Bug#1049409: firmware-amd-graphics: Possible missing firmware for module amdgpu

[S. M.]

Package: firmware-amd-graphics
Version: 20230210-5
Severity: normal
X-Debbugs-Cc: sm.snowstorm...@passinbox.com

Dear Maintainer,

When running update-initramfs I get the following warnings:

---

Setting up linux-image-6.1.0-10-amd64 (6.1.38-2) ...
/etc/kernel/postinst.d/initramfs-tools:
update-initramfs: Generating /boot/initrd.img-6.1.0-10-amd64
W: Possible missing firmware /lib/firmware/amdgpu/ip_discovery.bin for module 
amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/vega10_cap.bin for module 
amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/sienna_cichlid_cap.bin for 
module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/navi12_cap.bin for module 
amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/psp_13_0_11_ta.bin for module 
amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/psp_13_0_11_toc.bin for 
module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/psp_13_0_10_ta.bin for module 
amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/psp_13_0_10_sos.bin for 
module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/aldebaran_cap.bin for module 
amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/gc_11_0_3_imu.bin for module 
amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/gc_11_0_4_rlc.bin for module 
amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/gc_11_0_4_mec.bin for module 
amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/gc_11_0_4_me.bin for module 
amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/gc_11_0_4_pfp.bin for module 
amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/gc_11_0_3_rlc.bin for module 
amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/gc_11_0_3_mec.bin for module 
amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/gc_11_0_3_me.bin for module 
amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/gc_11_0_3_pfp.bin for module 
amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/gc_11_0_0_toc.bin for module 
amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/sdma_6_0_3.bin for module 
amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/sienna_cichlid_mes1.bin for 
module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/sienna_cichlid_mes.bin for 
module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/navi10_mes.bin for module 
amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/gc_11_0_4_mes1.bin for module 
amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/gc_11_0_4_mes_2.bin for 
module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/gc_11_0_4_mes.bin for module 
amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/gc_11_0_3_mes1.bin for module 
amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/gc_11_0_3_mes_2.bin for 
module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/gc_11_0_3_mes.bin for module 
amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/gc_11_0_2_mes_2.bin for 
module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/gc_11_0_1_mes_2.bin for 
module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/gc_11_0_0_mes_2.bin for 
module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/smu_13_0_10.bin for module 
amdgpu

---

On checking the linux-firmware tree 
(https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/tree/amdgpu)
I found that some of the blobs are available there but are not in
the Debian packages. The firmware that is *in* linux-firmware are:

gc_11_0_0_mes_2.bin
gc_11_0_1_mes_2.bin
gc_11_0_2_mes_2.bin
gc_11_0_3_imu.bin
gc_11_0_3_me.bin
gc_11_0_3_mec.bin
gc_11_0_3_mes1.bin
gc_11_0_3_mes_2.bin
gc_11_0_3_pfp.bin
gc_11_0_3_rlc.bin
gc_11_0_4_me.bin
gc_11_0_4_mec.bin
gc_11_0_4_mes1.bin
gc_11_0_4_mes_2.bin
gc_11_0_4_mes.bin
gc_11_0_4_pfp.bin
gc_11_0_4_rlc.bin
psp_13_0_10_sos.bin
psp_13_0_10_ta.bin
psp_13_0_11_ta.bin
psp_13_0_11_toc.bin
sdma_6_0_3.bin
smu_13_0_10.bin


The firmware that is *not* in linux-firmware are:

ip_discovery.bin
vega10_cap.bin
sienna_cichlid_cap.bin
navi12_cap.bin
aldebaran_cap.bin
gc_11_0_0_toc.bin
sienna_cichlid_mes1.bin
sienna_cichlid_mes.bin
navi10_mes.bin
gc_11_0_3_mes.bin


Installing the firmware-linux-nonfree and firmware-misc-nonfree packages
did not correct the issue.

The firmware for amdgpu that is currently available on linux-firmware
should also be in the firmware-amd-graphics package, also while it is
outside of Debian's scope it should be investigated upstream why there
is firmware referenced that apparently is not available on linux-firmware.

I haven't noticed any functional issues caused by the missing firmware as
of yet, only warnings.

Note that I am running a custom kernel build, but this issue affects all kernel
versions including the stock Debian kernel (hence mismatch between kernel
versions in the report).

If you need further information please let me know.

Thanks!

-- System Information:
Debian Release: 12.1
  APT prefers stable-updates
  APT policy: (500, 

Bug#1028001: closing 1028001

[Raouf M. Bencheraiet]

Hi

On Thu, Jan 5, 2023 at 4:27 PM Salvatore Bonaccorso 
wrote:

> Hi,
>
> On Thu, Jan 05, 2023 at 04:15:16PM -0500, Raouf M. Bencheraiet wrote:
> > is  2.5.4-1~exp1 available for debian stable?!
>
> No, it will be in the next upcoming stable release Debian bookworm, as
> we finally catched up following upstream releases more closely now
> (Debian bookworm will likely have a 2.6.2 based version).
>
>
The Debian BTS can handle version tracking, so it will show the stable
> version still as affected. If backporting fixes to the 1.3.4 version
> is feasible then we might pick those up as well via a bullseye point
> release for the older version.
>
> My guess is that it will though be unfortunately too risky to actually
> do that for 1:1.3.4-6.
>
> I'll see if I can try that (backporting) on my own.
Although, building 2.6.2 for bullseye seems the easy way out (I do have
2.6.x running on other
clients albeit on a different distro -- gentoo --). I guess we'll see what
panes out!
Great thanks for the quick replies!

> Regards,
> Salvatore
>


-- 
- Unix is fundamentally a simple system, but you have to be a genius to
understand its simplicity.
- Do not seek death, death will ultimately find you. Seek the road that
makes death a fulfilment.

Re: Arch qualification for bookworm: call for DSA, Security, toolchain concerns

[Timothy M Butterworth]

On Sat, Jul 16, 2022 at 11:46 AM Ben Hutchings  wrote:

> On Sat, 2022-07-16 at 11:20 -0400, Timothy M Butterworth wrote:
> [...]
> > i386 is anchient in tech terms it was introduced in 1985. If debian wants
> > to keep supporting 32 bit OS then it should bump up to i686.
> [...]
>
> We did that years ago.  We just didn't rename the architecture.
>
> Ben.
>
> The architecture should be renamed for clarity. There is a huge difference
between i386 and i686.


> --
> Ben Hutchings
> Any sufficiently advanced bug is indistinguishable from a feature.
>


-- 
⢀⣴⠾⠻⢶⣦⠀
⣾⠁⢠⠒⠀⣿⡁ Debian - The universal operating system
⢿⡄⠘⠷⠚⠋⠀ https://www.debian.org/
⠈⠳⣄⠀⠀

Re: Arch qualification for bookworm: call for DSA, Security, toolchain concerns

[Timothy M Butterworth]

On Fri, Jul 15, 2022 at 7:51 AM Ben Hutchings  wrote:

> On Wed, 2022-06-22 at 10:05 +0200, Graham Inggs wrote:
> > Hi,
> >
> > As part of the interim architecture qualification for bookworm, we
> > request that DSA, the security team, Wanna build, and the toolchain
> > maintainers review and update their list of known concerns for bookworm
> > release architectures.
> >
> > If the issues and concerns from you or your team are not up to date,
> > then please follow up to this email (keeping debian-release@l.d.o in CC
> > to ensure we are notified).
> >
> > In particular, we would like to hear any new concerns for riscv64
> > (see below).
> >
> > Whilst porters remain ultimately responsible for ensuring the
> > architectures are ready for release, we do expect that you / your team
> > are willing to assist with clarifications of the concerns and to apply
> > patches/changes in a timely manner to resolve the concerns.
> [...]
>
> For i386, I have some concerns about upstream support of the Linux
> kernel.  CPU security mitigations for x86 are concentrated on amd64,
> with i386 being left behind.  Mitigation of Meltdown required a
> different implementation for i386 that was completed months after the
> public disclosure and was never backported to stable branches.  More
> recently it became clear that mitigation of RETbleed was never tested
> on i386, since it didn't even compile there.
>
> More generally, on 32-bit systems Linux can only directly access about
> 1 GiB of RAM, and support for large amounts of additional RAM (highmem)
> has been steadily regressing.  This is not likely to be fixed.
>
> This is not to say that i386, or 32-bit architectures, should be
> dropped as a whole.  We've supported installing a 64-bit kernel on i386
> since etch, though it now requires adding amd64 as a foreign
> architecture.  I do think that at some time soon we should stop
> releasing kernel binaries or an installer for i386.
>

i386 is anchient in tech terms it was introduced in 1985. If debian wants
to keep supporting 32 bit OS then it should bump up to i686. i686 supports
Pentium 4 and later processors. I do not imagine anyone using a CPU older
than Pentium 4 and if they are it is time to upgrade. An Intel core 2 duo
CPU is dirt cheap and supports 4GB of RAM.


> (If we don't make that change for bookworm, then we should probably
> strongly encourage users to use 64-bit kernels on 64-bit capable
> hardware, and document how to install a foreign kernel package.)
>
> Ben.
>
>
> --
> Ben Hutchings
> Unix is many things to many people,
> but it's never been everything to anybody.
>


-- 
⢀⣴⠾⠻⢶⣦⠀
⣾⠁⢠⠒⠀⣿⡁ Debian - The universal operating system
⢿⡄⠘⠷⠚⠋⠀ https://www.debian.org/
⠈⠳⣄⠀⠀

Re: Uploading linux (5.17.6-1)

[Timothy M Butterworth]

On Wed, May 11, 2022 at 6:09 AM Bastian Blank  wrote:

> Hi
>
> I will upload linux version 5.17.6-1 to unstable later today.  It
> includes an ABI bump.
>
> Please upload it to backports.


> Bastian
>
> --
> Extreme feminine beauty is always disturbing.
> -- Spock, "The Cloud Minders", stardate 5818.4
>
>

Bug#1005927: linux-image-5.15.0-0.bpo.3-amd64: Linux kernel 5.15.0-0.bpo.3-amd64 fails to complete suspend and stays unresponsive to wakeup events

[m . alfaeko]

Package: src:linux
Version: 5.15.15-2~bpo11+1
Severity: important
Tags: upstream
X-Debbugs-Cc: m.alfa...@gmail.com

Hi.

Today i installed new backport version of linux kernel. I tried suspend the 
machine, but it got stuck. The machine stayed on but the USB bus and harddrive 
was
turned off. Suspend command was issued via lightdm login screen. Few minutes
after cold start. I offten shutdown system after install of new kernel.
Only thing that could release the machine from this state was by pressing
a reset button or holding a power button till the system shutsoff. The logs
did not record any issues. Most likelly it crashed when the log service was
no longer active or was unable to record events.

Thank You.

-- Package-specific info:
** Version:
Linux version 5.15.0-0.bpo.3-amd64 (debian-kernel@lists.debian.org) (gcc-10 
(Debian 10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 2.35.2) #1 
SMP Debian 5.15.15-2~bpo11+1 (2022-02-03)

** Command line:
BOOT_IMAGE=/vmlinuz-5.15.0-0.bpo.3-amd64 root=/dev/mapper/debian--buster-root 
ro quiet apparmor=0 initrd=/initrd.img-5.15.0-0.bpo.3-amd64

** Not tainted

** Kernel log:
Unable to read kernel log; any relevant messages should be attached

** Model information
sys_vendor: System manufacturer
product_name: System Product Name
product_version: System Version
chassis_vendor: Default string
chassis_version: Default string
bios_vendor: American Megatrends Inc.
bios_version: 3401
board_vendor: ASUSTeK COMPUTER INC.
board_name: PRIME A320M-K
board_version: Rev X.0x

** Loaded modules:
tcp_diag
udp_diag
inet_diag
nft_ct
nft_counter
cfg80211
nft_chain_nat
nf_nat
nf_conntrack
cpufreq_ondemand
nf_defrag_ipv6
nf_defrag_ipv4
nf_tables
nfnetlink
edac_mce_amd
joydev
kvm_amd
ccp
rng_core
kvm
snd_hda_codec_realtek
irqbypass
snd_hda_codec_generic
snd_hda_codec_hdmi
ledtrig_audio
ghash_clmulni_intel
snd_hda_intel
aesni_intel
snd_intel_dspcfg
snd_intel_sdw_acpi
snd_hda_codec
snd_hda_core
crypto_simd
cryptd
snd_hwdep
sg
pcspkr
snd_pcm
serio_raw
snd_timer
snd
soundcore
sp5100_tco
eeepc_wmi
asus_wmi
watchdog
evdev
fam15h_power
k10temp
platform_profile
battery
sparse_keymap
rfkill
wmi_bmof
acpi_cpufreq
parport_pc
ppdev
lp
parport
fuse
configfs
ip_tables
x_tables
autofs4
ext4
crc16
mbcache
jbd2
dm_thin_pool
dm_persistent_data
dm_bio_prison
dm_bufio
libcrc32c
crc32c_generic
sr_mod
cdrom
dm_mod
hid_generic
usbhid
uas
hid
usb_storage
sd_mod
t10_pi
crc_t10dif
crct10dif_generic
amdgpu
r8169
realtek
mdio_devres
libphy
gpu_sched
crct10dif_pclmul
i2c_algo_bit
i2c_piix4
drm_ttm_helper
crct10dif_common
crc32_pclmul
ttm
crc32c_intel
drm_kms_helper
ahci
libahci
xhci_pci
cec
xhci_hcd
rc_core
libata
drm
usbcore
scsi_mod
gpio_amdpt
usb_common
wmi
scsi_common
video
gpio_generic
button

** PCI devices:
00:00.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Family 15h 
(Models 60h-6fh) Processor Root Complex [1022:1576]
Subsystem: ASUSTeK Computer Inc. Family 15h (Models 60h-6fh) Processor 
Root Complex [1043:8719]
Control: I/O- Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- SERR- 

00:01.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. 
[AMD/ATI] Wani [Radeon R5/R6/R7 Graphics] [1002:9874] (rev e2) (prog-if 00 [VGA 
controller])
Subsystem: ASUSTeK Computer Inc. Wani [Radeon R5/R6/R7 Graphics] 
[1043:8719]
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 
Kernel driver in use: amdgpu
Kernel modules: amdgpu

00:01.1 Audio device [0403]: Advanced Micro Devices, Inc. [AMD/ATI] Kabini 
HDMI/DP Audio [1002:9840]
Subsystem: ASUSTeK Computer Inc. Kabini HDMI/DP Audio [1043:8719]
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 
Kernel driver in use: snd_hda_intel
Kernel modules: snd_hda_intel

00:02.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Family 15h 
(Models 60h-6fh) Host Bridge [1022:157b]
DeviceName:  Onboard IGD
Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- SERR- TAbort- Reset- FastB2B-
PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
Capabilities: 
Kernel driver in use: pcieport

00:03.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Family 15h 
(Models 60h-6fh) Host Bridge [1022:157b]
Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- SERR- 

00:09.0 Host 

Bug#795013: Closing this bug (BTS maintenance for src:linux bugs)

[A. M.]

reopen 795013
thanks

# Dear Salvatore:
# I have not said anything for a long time, but not because the bug
# didn't occur, but because I didn't know what to do when the startup
# failed the described way, and because the failure was infrequent.  I
# always simply restarted the laptop.  The machine always runs the
# current Debian stable, whichever it may be.  The call stacks have
# already been given in the bug report if it helps.  I would kindly ask
# you to tell me how/what to debug next.
# Alex

Bug#973417: Also happens on Amazon EC2 & Lightsail

[Thorsten M.]

Hi,

I can confirm this bug happening on Amazon Lightsail and EC2 instances 
running Debian. After kernel upgrade the machines won't boot anymore and 
end in kernel panic.


Here is a log from failed boot on EC2:
[0.16]  [] ? rest_init+0x80/0x80
[0.16]  [] ? kernel_init+0xa/0x100
[0.16]  [] ? ret_from_fork+0x57/0x70
[0.16] Code: 8d ba 03 02 00 00 48 8d 14 d2 44 8d 59 11 49 8d 2c 
d2 c1 e7 0c 48 63 ff 8b 55 14 81 e2 ff 0f 00 00 48 81 ea 00 10 80 00 48 
29 fa <44> 89 1a 89 72 10 8b 55 14 83 c1 10 81 e2 ff 0f 00 00 48 81 ea

[0.16] RIP  [] mp_irqdomain_activate+0x62/0xa0
[0.16]  RSP 
[0.16] CR2: ff5fb000
[0.16] ---[ end trace 3b908cb762782fed ]---
[0.160039] Kernel panic - not syncing: Attempted to kill init! 
exitcode=0x0009

[0.160039]
[0.00] Cannot get hvm parameter CONSOLE_EVTCHN (18): -22!
[0.156662] BUG: unable to handle kernel paging request at 
ff5fb000

[0.16] IP: [] mp_irqdomain_activate+0x62/0xa0
[0.16] PGD 8420d067 [0.16] PUD 8420f067
[0.16] PMD 84210067 [0.16] PTE 0
[0.16]
[0.16] Oops: 0002 [#1] SMP
[0.16] Modules linked in:
[0.16] CPU: 0 PID: 1 Comm: swapper/0 Not tainted 4.9.0-14-amd64 
#1 Debian 4.9.240-1

[0.16] Hardware name: Xen HVM domU, BIOS 4.2.amazon 08/24/2006
[0.16] task: 8c64ca06d040 task.stack: a7ccc0644000
[0.16] RIP: 0010:[]  [] 
mp_irqdomain_activate+0x62/0xa0

[0.16] RSP: :a7ccc0647cf0  EFLAGS: 00010086
[0.16] RAX: 0082 RBX: 8c64ca2e9d00 RCX: 

[0.16] RDX: ff5fb000 RSI: 0001 RDI: 
00204000
[0.16] RBP: b28ad988 R08: b26be7f0 R09: 

[0.16] R10: b28ad940 R11: 0011 R12: 
0001
[0.16] R13: 8c64cad85058 R14: 8c64cad850d4 R15: 
8c64ca2ef380
[0.16] FS:  () GS:8c64cb20() 
knlGS:

[0.16] CS:  0010 DS:  ES:  CR0: 80050033
[0.16] CR2: ff5fb000 CR3: 84208000 CR4: 
00160670
[0.16] DR0:  DR1:  DR2: 

[0.16] DR3:  DR6: fffe0ff0 DR7: 
0400

[0.16] Stack:
[0.16]  8c64cad85058 8c64cad85058 b1ade5ea 
8c64cad85000
[0.16]  b1adaf03 8c64cad85000 8c64cad85000 
8c64cad850a0
[0.16]  0009 b1ad968c 0246 
8c64cad85058

[0.16] Call Trace:
[0.16]  [] ? irq_domain_activate_irq+0x1a/0x30
[0.16]  [] ? irq_startup+0x33/0x80
[0.16]  [] ? __setup_irq+0x58c/0x640
[0.16]  [] ? 
xen_register_pirq.constprop.9+0xd4/0x110

[0.16]  [] ? request_threaded_irq+0x10a/0x1b0
[0.16]  [] ? acpi_ev_sci_dispatch+0x5a/0x5a
[0.16]  [] ? 
acpi_os_install_interrupt_handler+0xa5/0x100

[0.16]  [] ? acpi_sleep_proc_init+0x22/0x22
[0.16]  [] ? set_debug_rodata+0xc/0xc
[0.16]  [] ? 
acpi_ev_install_xrupt_handlers+0x16/0x64

[0.16]  [] ? acpi_init+0xb6/0x33e
[0.16]  [] ? __class_create+0x4f/0x80
[0.16]  [] ? video_setup+0x79/0x79
[0.16]  [] ? set_debug_rodata+0xc/0xc
[0.16]  [] ? do_one_initcall+0x4e/0x180
[0.16]  [] ? set_debug_rodata+0xc/0xc
[0.16]  [] ? kernel_init_freeable+0x16b/0x1ec
[0.16]  [] ? rest_init+0x80/0x80
[0.16]  [] ? kernel_init+0xa/0x100
[0.16]  [] ? ret_from_fork+0x57/0x70
[0.16] Code: 8d ba 03 02 00 00 48 8d 14 d2 44 8d 59 11 49 8d 2c 
d2 c1 e7 0c 48 63 ff 8b 55 14 81 e2 ff 0f 00 00 48 81 ea 00 10 80 00 48 
29 fa <44> 89 1a 89 72 10 8b 55 14 83 c1 10 81 e2 ff 0f 00 00 48 81 ea

[0.16] RIP  [] mp_irqdomain_activate+0x62/0xa0
[0.16]  RSP 
[0.16] CR2: ff5fb000
[0.16] ---[ end trace 18c93002ce0feedc ]---
[0.160041] Kernel panic - not syncing: Attempted to kill init! 
exitcode=0x0009

[0.160041]

Bug#885846: Recurring Atheros Driver Crash

[M. Halverson]

Package: firmware-atheros
Version: 20190114-2
Followup-For: Bug #885846

Dear Maintainer,

I am seeing a similar crash as reported in bug 885846, using wireless driver
ATH9k with a TP-Link TL-WN851ND. The system freezes during moderate to high
wifi activity, such as streaming or running speedtest utilities, and is very
repeatable. At best, the system requires a hard reset. At worst, the crash
corrupts the BIOS, forcing BIOS reconfiguration. This issue affects distros
that use kernels common to Ubuntu 20.04, Mint 20/LMDE, etc. It does not occur
with older distros (e.g. Mint 17, Ubuntu 18.04 and its derivatives), or with
Windows.

Using modprobe I attempted to replace the ATH driver package provided with Mint
LMDE/Ubuntu 20 with that from Mint 17, however the older driver package is
apparently incompatible with the new kernel(s) and failed to load. I also
attempted to replace the ATH9k driver with ndiswrapper and the 64 bit driver
provided in Windows XP, but modprobe would hang when attempting to load
ndiswrapper. I also disabled wireless N in both the adapter settings, and the
router itself, to slow the data rate (i.e. I ran the adapter in "Legacy" mode).
The system still crashes; it just takes a while longer. Likewise, the crash
occurs whether security is enabled or disabled, and does not appear related to
any other hardware conflicts (the crash occurs whether using Nouveau or Nvidia
drivers, plus the wireless adapter is only device installed in a PCI slot).



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

Kernel: Linux 4.19.0-10-amd64 (SMP w/6 CPU cores)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE,
TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8),
LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

firmware-atheros depends on no packages.

firmware-atheros recommends no packages.

Versions of packages firmware-atheros suggests:
ii  initramfs-tools  0.133+deb10u1

-- no debconf information

*** /mnt/Storage/common files/ath9k/ath9k wireless driver crashing Mint 20 et
al.txt
Problem:
The ath9k wireless adapter driver appears to be "broken". Affects Mint 20
Cinnamon & LMDE, Ubuntu & Xubuntu 20.04.0 &.1 (I believe they all use the
latest kernels). It is NOT "broken" when using Mint 17.3 or Windows 7. (Adapter
make and model: TP-Link TL-WN851nd)

The symptoms:
When running speedtest utils (speedtest.net, xfinityspeedtest.org, etc) OR
streaming audio OR video (YouTubeTV) in Chrome OR Firefox while connected to
wifi, the mouse and keyboard will freeze, plus an audible static ("white
noise") will often come from the speakers. Sometimes speedtest or whatever was
being streamed at the time will continue to run for several seconds, even
though the keyboard and mouse are frozen. Othertimes, everything freezes at the
same time. At best it is necessary to perform a hard shutdown and reboot. At
worst, the crash corrupts the BIOS (about 50% of the time...) and I have to
reconfigure the BIOS before I can use the PC, and/or the OS/boot configuration
will be corrupted and I have to use "Boot Repair" and/or restore a previously
saved backup image before the PC can be used. This problem has been 100%
repeatable.

What I have tried:
1) Updated the firmware-atheros to the newest version (20200619-1). The
wireless still froze.

2) Using "Network Settings" I disabled wireless N on the adapter PLUS I
disabled wireless N on my ASUS RT-AC66U_B1 router (i.e. I used 802.11b or
802.11g Legacy mode only), and re-ran speedtest, but the system still crashed.
The only difference was that it took longer; I presume due to the slower
download and upload speeds.

3) Booting from a live USB (both Mint 20 and LMDE), I connected to wifi and ran
speedtest. The system still crashed. (Booting the live USB in UEFI or Legacy
BIOS mode made no difference.)

4) I attempted to replace the ath9k driver that comes with Mint 20 with the
ath9k driver in Mint 17.3, but it appears that the drivers are signed in some
fashion, preventing older drivers from being used with the newer kernels.

5) Tweeking the wifi, proxy, IPv4, and IPv6 settings from their defaults made
no difference.

6) The system does not crash when both wired and wifi connections are enabled.
I presume this is because the wired connection is preferred (has "priority").

7) The output from "lspci -b -vvv" shows that mint 17.3 is using the same
driver name (ath9k) and interrupt as mint 20.04.

8) Although I have tested this issue many times, only once was a crash log
generated, and it was lost after a subsequent crash. Sorry...

9) Thinking the crash may be related to downloads only, I ran "testmy.net
/upload" to skip the download part of the speedtest, and the system still
crashed. (The problem ***may be*** related to 

Bug#958737: linux-image-5.5.0-2-amd64: Intel Cannon Point-LP audio controller no longer works

[brian m. carlson]

Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 
Kernel driver in use: xhci_hcd
Kernel modules: xhci_pci


** USB devices:
Bus 009 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 010 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 008 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 007 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 006 Device 002: ID 2188:0747 CalDigit Card Reader 
Bus 006 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 005 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 002: ID 2188:6533 CalDigit, Inc. CalDigit Thunderbolt 3 Audio
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 003: ID 06cb:00bd Synaptics, Inc. 
Bus 001 Device 002: ID 04f2:b67c Chicony Electronics Co., Ltd Integrated Camera
Bus 001 Device 004: ID 8087:0aaa Intel Corp. 
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub


-- System Information:
Debian Release: bullseye/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 
'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 5.5.0-2-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages linux-image-5.5.0-2-amd64 depends on:
ii  initramfs-tools [linux-initramfs-tool]  0.136
ii  kmod27+20200310-2
ii  linux-base  4.6

Versions of packages linux-image-5.5.0-2-amd64 recommends:
ii  apparmor 2.13.4-1+b1
ii  firmware-linux-free  20200122-1

Versions of packages linux-image-5.5.0-2-amd64 suggests:
pn  debian-kernel-handbook  
ii  extlinux3:6.04~git20190206.bf6db5b4+dfsg1-2
ii  grub-efi-amd64  2.04-6
pn  linux-doc-5.5   

Versions of packages linux-image-5.5.0-2-amd64 is related to:
pn  firmware-amd-graphics     
pn  firmware-atheros  
pn  firmware-bnx2 
pn  firmware-bnx2x
ii  firmware-brcm8021120190717-2
pn  firmware-cavium   
ii  firmware-intel-sound  20190717-2
pn  firmware-intelwimax   
pn  firmware-ipw2x00  
pn  firmware-ivtv 
ii  firmware-iwlwifi  20190717-2
pn  firmware-libertas 
pn  firmware-linux-nonfree
ii  firmware-misc-nonfree 20190717-2
pn  firmware-myricom  
pn  firmware-netxen   
pn  firmware-qlogic   
pn  firmware-realtek  
pn  firmware-samsung  
pn  firmware-siano
pn  firmware-ti-connectivity  
pn  xen-hypervisor

-- no debconf information

-- 
brian m. carlson: Houston, Texas, US
OpenPGP: https://keybase.io/bk2204


signature.asc
Description: PGP signature

Bug#958126: linux-image-5.5.0-2-amd64: Alt-SysRq-x no longer lifts Secure Boot restrictions

[brian m. carlson]

On 2020-04-18 at 21:59:35, Ben Hutchings wrote:
> Control: tag -1 wontfix
> 
> On Sat, 2020-04-18 at 18:50 +0000, brian m. carlson wrote:
> > Package: src:linux
> > Version: 5.5.17-1
> > Severity: important
> > 
> > By default, Debian ships kernels such that when booted with Secure Boot,
> > that a user cannot hibernate their computer.  However, the combination
> > Alt-SysRq-x is documented in the wiki (which is linked to from the
> > kernel) to lift these restrictions and allow the user to hibernate.
> > 
> > However, in this kernel version that does not work, and the user must
> > either disable secure boot or forego hibernation.  When pressing
> > Alt-SysRq-x, the following is printed:
> > 
> >   sysrq: HELP : loglevel(0-9) reboot(b) crash(c) terminate-all-tasks(e) 
> > memory-full-oom-kill(f) kill-all-tasks(i) thaw-filesystems(j) sak(k) 
> > show-backtrace-all-active-cpus(l) show-memory-usage(m) nice-all-RT-tasks(n) 
> > poweroff(o) show-registers(p) show-all-timers(q) unraw(r) sync(s) 
> > show-task-states(t) unmount(u) force-fb(V) show-blocked-tasks(w) 
> > dump-ftrace-buffer(z)
> [...]
> 
> This was an intentional change listed in the changelog, fixing bug
> #947021.  Thanks for mentioning the wiki; I'll update that to reflect
> current reality.

It looks like Ubuntu allows people physically present to use the key
still with their proposed patch.  Is there a reason that patch can't be
applied here?

> If you can't live with the restrictions of Secure Boot, you'll have to
> turn it off.

Can you explain why this restriction is required in the first place?
Other operating systems use Secure Boot and allow hibernation, so it
can't be that it's an intrinsic limitation.

I'd like to have the behavior where I know that my boot process hasn't
been tampered with, but I don't need to be locked out of my system or
have important features turned off.  Surely that's a valid use case that
should be supported.
-- 
brian m. carlson: Houston, Texas, US
OpenPGP: https://keybase.io/bk2204


signature.asc
Description: PGP signature

Bug#958126: linux-image-5.5.0-2-amd64: Alt-SysRq-x no longer lifts Secure Boot restrictions

[brian m. carlson]

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

By default, Debian ships kernels such that when booted with Secure Boot,
that a user cannot hibernate their computer.  However, the combination
Alt-SysRq-x is documented in the wiki (which is linked to from the
kernel) to lift these restrictions and allow the user to hibernate.

However, in this kernel version that does not work, and the user must
either disable secure boot or forego hibernation.  When pressing
Alt-SysRq-x, the following is printed:

  sysrq: HELP : loglevel(0-9) reboot(b) crash(c) terminate-all-tasks(e) 
memory-full-oom-kill(f) kill-all-tasks(i) thaw-filesystems(j) sak(k) 
show-backtrace-all-active-cpus(l) show-memory-usage(m) nice-all-RT-tasks(n) 
poweroff(o) show-registers(p) show-all-timers(q) unraw(r) sync(s) 
show-task-states(t) unmount(u) force-fb(V) show-blocked-tasks(w) 
dump-ftrace-buffer(z)

Other relevant messages from the kernel log:

  Lockdown: systemd-logind: hibernation is restricted; see 
https://wiki.debian.org/SecureBoot
  Lockdown: systemd-logind: hibernation is restricted; see 
https://wiki.debian.org/SecureBoot

Please either drop the restriction on hibernation or restore Alt-SysRq-x
to its former functionality.  I would like to point out that this isn't
the first time that Alt-SysRq-x has broken, so if you're going to retain
it, perhaps it should be part of a suitable testsuite or testing
procedure before shipping a new kernel.

Thanks.

-- 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=/vmlinuz-5.5.0-2-amd64 root=/dev/mapper/camp-root ro 
sysrq_always_enabled=1 processor.ignore_ppc=1 processor.ignore_tpc=1 quiet 
sysrq_always_enabled=1

** Not tainted

** Kernel log:
Unable to read kernel log; any relevant messages should be attached

** Model information
sys_vendor: LENOVO
product_name: 20QDCT01WW
product_version: ThinkPad
chassis_vendor: LENOVO
chassis_version: None
bios_vendor: LENOVO
bios_version: N2HET30W (1.13 )
board_vendor: LENOVO
board_name: 20QDCT01WW
board_version: SDK0K17763 WIN

** Loaded modules:
hidp
xt_conntrack
xt_MASQUERADE
nf_conntrack_netlink
xfrm_user
xfrm_algo
nft_counter
xt_addrtype
nft_compat
nft_chain_nat
nf_nat
nf_conntrack
nf_defrag_ipv6
nf_defrag_ipv4
nf_tables
nfnetlink
br_netfilter
bridge
stp
llc
overlay
ctr
ccm
cmac
bnep
snd_soc_hdac_hdmi
snd_soc_dmic
snd_hda_codec_realtek
mei_wdt
intel_rapl_msr
snd_hda_codec_generic
snd_sof_pci
snd_sof_intel_hda_common
snd_sof_intel_hda
snd_sof_intel_byt
snd_sof_intel_ipc
snd_sof
snd_sof_xtensa_dsp
snd_soc_skl
snd_soc_hdac_hda
snd_hda_ext_core
snd_soc_sst_ipc
btusb
snd_soc_sst_dsp
x86_pkg_temp_thermal
btrtl
intel_powerclamp
snd_soc_acpi_intel_match
btbcm
coretemp
snd_soc_acpi
btintel
kvm_intel
iwlmvm
efi_pstore
kvm
binfmt_misc
irqbypass
mac80211
snd_soc_core
bluetooth
intel_cstate
snd_compress
snd_hda_intel
snd_intel_dspcfg
nls_ascii
intel_uncore
nls_cp437
intel_rapl_perf
snd_usb_audio
snd_hda_codec
libarc4
vfat
serio_raw
fat
pcspkr
snd_usbmidi_lib
snd_hda_core
snd_rawmidi
efivars
uvcvideo
snd_seq_device
iTCO_wdt
snd_hwdep
videobuf2_vmalloc
videobuf2_memops
iTCO_vendor_support
wmi_bmof
intel_wmi_thunderbolt
watchdog
iwlwifi
snd_pcm
sg
videobuf2_v4l2
processor_thermal_device
drbg
videobuf2_common
tpm_crb
snd_timer
hid_sensor_gyro_3d
mei_me
hid_sensor_accel_3d
intel_rapl_common
videodev
ansi_cprng
thinkpad_acpi
hid_sensor_trigger
tpm_tis
hid_sensor_iio_common
tpm_tis_core
ucsi_acpi
industrialio_triggered_buffer
ecdh_generic
cfg80211
mc
kfifo_buf
typec_ucsi
mei
ecc
tpm
industrialio
intel_soc_dts_iosf
nvram
intel_pch_thermal
typec
ledtrig_audio
rng_core
snd
soundcore
rfkill
int3403_thermal
ac
int340x_thermal_zone
evdev
int3400_thermal
acpi_thermal_rel
acpi_pad
acpi_tad
parport_pc
ppdev
lp
parport
efivarfs
ip_tables
x_tables
autofs4
ext4
crc16
mbcache
jbd2
crc32c_generic
btrfs
zstd_decompress
zstd_compress
dm_crypt
dm_mod
raid10
raid456
async_raid6_recov
async_memcpy
async_pq
async_xor
async_tx
xor
hid_sensor_custom
raid6_pq
hid_sensor_hub
libcrc32c
raid1
raid0
multipath
linear
md_mod
intel_ishtp_hid
sd_mod
hid_generic
usbhid
hid
uas
usb_storage
scsi_mod
crct10dif_pclmul
crc32_pclmul
crc32c_intel
i915
ghash_clmulni_intel
aesni_intel
i2c_designware_platform
i2c_designware_core
crypto_simd
e1000e
psmouse
cryptd
glue_helper
i2c_i801
drm_kms_helper
xhci_pci
xhci_hcd
igb
dca
ptp
drm
pps_core
i2c_algo_bit
usbcore
thunderbolt
nvme
nvme_core
intel_ish_ipc
intel_lpss_pci
intel_ishtp
intel_lpss
idma64
mfd_core
usb_common
wmi
battery
video
button

** PCI devices:
00:00.0 Host bridge [0600]: Intel Corporation Coffee Lake HOST and DRAM 
Controller [8086:3e34] (rev 0c)
Subsystem: Lenovo Coffee Lake HOST and DRAM Controller [17aa:2292]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL

Bug#939170: linux: does not suspend completely, locks up

[Daniel M.]

On Sun, 26 Jan 2020 18:03:23 +0100 Felix Rublack  wrote:
> Hi everyone,
>
> I have the same issue on a ThinkPad T460s (suspend works only half way,
> reboot and poweroff stop just short before actual shutdown).
>
> I bisected the problem to the TPM driver. Blacklisting the module in
> modprobe.d fixed the problem for me.
>
> Sample configuration: /etc/modprobe.d/blacklist-tpm.conf
>
> # Prevent TPM from loading. It breaks suspend and power cycle.
> blacklist tpm
> blacklist tpm_crb
> blacklist tpm_tis
> blacklist tpm_tis_core
>
> Greetings
> Felix Rublack

Hi, thanks a lot! I can confirm that this works also on my Thinkpad
E460. Since you can probably provide more details, could you forward
this to kernel.org?

Cheers,
Daniel

Bug#944257: Confirmed, possible duplicate

[Daniel M.]

Hi,

I have exactly the same behavior on my lenovo E460 laptop. No suspend
and shutdown working since upgrade to linux 5.x.

I don't know how to get more attention to this. Can we raise the
severity or flag it?

Some more info in my earlier report #939170. Maybe even duplicate?

Cheers,
Daniel

Bug#945898: linux-image-5.3.0-2-amd64: No i2c_amd_mp2 kernel module

[Colin M Strickland]

Package: src:linux
Version: 5.3.9-3
Severity: normal

Dear Maintainer,

I have a Lenovo Ideapad 530s with an AMD ryzen cpu. This has been running fine
under Debian, since I first bought the computer, although the touchpad does not
work after boot. I found a very simple remedy for this using the
https://github.com/Syniurge/i2c-amd-mp2 driver, which is supplied as a DKMS
build, and simply installed and worked. When I apt upgraded my machine at the
start of this week, and moved to a 5.3 series debian kernel, the DKMS build
stopped working, and after boot I was surprised to have no trackpad again.

I looked at the build problem with the module, and it was a very simple
problem, where the prototype for one of the functions from device.h has become
slightly more strict. When I submitted this change to the upstream repo, the
reply from the author is that the module should be merged into the upstream
kernel since releasae 5.2 and a separated build should not be necessary for
kernels > 5.1. They report that the debian kernel seems to be exluding this
module, but they don't know why.

( see https://github.com/Syniurge/i2c-amd-mp2/pull/14 )

Is there a reason this is not available in the debian kernel image? Do I need
to install additional packages, or perhaps make such a package myself.

Thanks
cms



-- Package-specific info:
** Version:
Linux version 5.3.0-2-amd64 (debian-kernel@lists.debian.org) (gcc version 9.2.1 
20191109 (Debian 9.2.1-19)) #1 SMP Debian 5.3.9-3 (2019-11-19)

** Command line:
BOOT_IMAGE=/vmlinuz-5.3.0-2-amd64 root=/dev/mapper/blink--vg-root ro quiet

** Tainted: OE (12288)
 * Out-of-tree module has been loaded.
 * Unsigned module has been loaded.

** Kernel log:
(Note that use of the override may cause unknown side effects.)
[   17.594132] ath10k_pci :01:00.0: htt-ver 3.56 wmi-op 4 htt-op 3 cal otp 
max-sta 32 raw 0 hwcrypto 1
[   17.596964] alg: No test for fips(ansi_cprng) (fips_ansi_cprng)
[   17.622248] mc: Linux media interface: v0.10
[   17.622285] EDAC amd64: Node 0: DRAM ECC disabled.
[   17.622289] EDAC amd64: ECC disabled in the BIOS or no ECC capability, 
module will not load.
Either enable ECC checking or force module loading by setting 
'ecc_enable_override'.
(Note that use of the override may cause unknown side effects.)
[   17.644207] videodev: Linux video capture interface: v2.00
[   17.672957] ath: EEPROM regdomain: 0x6c
[   17.672960] ath: EEPROM indicates we should expect a direct regpair map
[   17.672963] ath: Country alpha2 being used: 00
[   17.672964] ath: Regpair used: 0x6c
[   17.677797] ath10k_pci :01:00.0 wlp1s0: renamed from wlan0
[   17.688653] EDAC amd64: Node 0: DRAM ECC disabled.
[   17.688655] EDAC amd64: ECC disabled in the BIOS or no ECC capability, 
module will not load.
Either enable ECC checking or force module loading by setting 
'ecc_enable_override'.
(Note that use of the override may cause unknown side effects.)
[   17.698121] Bluetooth: Core ver 2.22
[   17.698153] NET: Registered protocol family 31
[   17.698154] Bluetooth: HCI device and connection manager initialized
[   17.698330] Bluetooth: HCI socket layer initialized
[   17.698333] Bluetooth: L2CAP socket layer initialized
[   17.698338] Bluetooth: SCO socket layer initialized
[   17.712914] usbcore: registered new interface driver btusb
[   17.765968] uvcvideo: Found UVC 1.00 device Integrated Camera (04f2:b61e)
[   17.782522] uvcvideo 3-2:1.0: Entity type for entity Realtek Extended 
Controls Unit was not initialized!
[   17.782525] uvcvideo 3-2:1.0: Entity type for entity Extension 4 was not 
initialized!
[   17.782526] uvcvideo 3-2:1.0: Entity type for entity Processing 2 was not 
initialized!
[   17.782528] uvcvideo 3-2:1.0: Entity type for entity Camera 1 was not 
initialized!
[   17.782785] input: Integrated Camera: Integrated C as 
/devices/pci:00/:00:08.1/:03:00.4/usb3/3-2/3-2:1.0/input/input18
[   17.783339] usbcore: registered new interface driver uvcvideo
[   17.783341] USB Video Class driver (1.1.1)
[   17.904204] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[   17.904207] Bluetooth: BNEP filters: protocol multicast
[   17.904214] Bluetooth: BNEP socket layer initialized
[   18.761123] ath10k_pci :01:00.0: unsupported HTC service id: 1536
[   18.895397] pcieport :00:01.2: AER: Multiple Corrected error received: 
:00:01.0
[   18.895410] pcieport :00:01.2: AER: PCIe Bus Error: severity=Corrected, 
type=Data Link Layer, (Receiver ID)
[   18.896225] pcieport :00:01.2: AER:   device [1022:15d3] error 
status/mask=0080/6000
[   18.897225] pcieport :00:01.2: AER:[ 7] BadDLLP   
[   18.929438] pcieport :00:01.2: AER: Multiple Corrected error received: 
:00:01.0
[   18.929452] pcieport :00:01.2: AER: PCIe Bus Error: severity=Corrected, 
type=Data Link Layer, (Receiver ID)
[   18.931291] pcieport :00:01.2: AER:   device 

Debian Kernel Source

[M. F. Ghani]

Hi,
Where/How can i get the complete latest debian kernel source with the
applied debian patches. I need the source similar to the linux base kernel
source with similar directory tree. Need that for some research?



-- 
Best,
- Ghani

debian patches from upstream

[M. F. Ghani]

Hi,
What is the current workflow of the patch propagation from linux mainline
to debian stable kernel versions? are the downstream debian kernels rebased
against the latest mainline kernel version or are they just rebased against
the lts upstream version from which the debian kernel was initially forked
from. if so, how soon?

Also, what is the difference between the patch propagation for the current
supported debain kernel versions. i.e if stretch and buster are currently
being supported, are the same upstream patches applied to both kernel
versions or is there a difference?
Best,
- Ghani

Debian kernel patch propagation

[M. F. Ghani]

Hi,
What is the current workflow of the patch propagation from linux mainline
to debian stable kernel versions? are the downstream debian kernels rebased
against the latest mainline kernel version or are they just rebased against
the lts upstream version from which the debian kernel was initially forked
from. if so, how soon?

Also, what is the difference between the patch propagation for the current
supported debain kernel versions. i.e if stretch and buster are currently
being supported, are the same upstream patches applied to both kernel
versions or is there a difference?
Best,
- Ghani

Bug#939170: Maybe wrong package?

[Daniel M.]

Hi,

is it possible this one is reported against the wrong package? It
seems like there are a few lenovo laptop / thinkpad owners who
experience this. Is there some (pseudo)package to report this to?
Maybe it gets a bit more traction there...

Cheers,
Daniel

Bug#939170: Also with systemctl suspend

[Daniel M.]

Hi,

this also happens to me when I try systemctl suspend instead of a GUI
action. So it's not a problem of the desktop environment but of kernel
or even systemd.

Maybe something with the thinkpad kernel module?

Cheers,
Daniel

Bug#939170: linux: does not suspend completely, locks up

[Daniel M.]

Source: linux
Version: 5.2.9-2
Severity: important

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 ***

Since the update from 4.19 to 5.2.9 my Lenovo Thinkpad E460 no longer suspends 
properly. If I 
close the lid or chose Suspend from the KDE launcher, the system will start to 
suspend but never 
reaches standby. Power light will blink as usual, display backlight turns off 
but keyboard LEDs 
don't turn off, fan is still active.

The system doesn't respond to Ctrl-Alt-Del or change to a Terminal. No input 
changes anything. 
Waiting (30min) doesn't help either. Rebooting to Kernel 4.19 fixes the problem 
immediatly.

Expected outcome would be a complete suspend/standby state and a complete 
recovery/powerup on
lid open or press of any key.


-- System Information:
Debian Release: bullseye/sid
  APT prefers testing
  APT policy: (500, 'testing'), (20, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.19.0-5-amd64 (SMP w/4 CPU cores)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US 
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Bug#932250: linux-image-amd64: adding segfault data

[m . alfaeko]

Package: linux-image-amd64
Version: 4.19+105
Followup-For: Bug #932250

adding file with segfault data

-- System Information:
  APT prefers stable
  APT policy: (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 4.19.0-5-amd64 (SMP w/4 CPU cores)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8), 
LANGUAGE=en_US.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages linux-image-amd64 depends on:
ii  linux-image-4.19.0-5-amd64  4.19.37-5

linux-image-amd64 recommends no packages.

linux-image-amd64 suggests no packages.

-- no debconf information
xfdesktop[11344]: segfault at 16 ip 7ff9fd0f29ea sp 7b934f00 error 
4 in libglib-2.0.so.0.5800.3[7ff9fd0a2000+7e000]
2019-07-17T01:04:04.589422+02:00 debian kernel: [18604.040877] Code: 8d 48 ff 
48 89 c3 49 89 ce 49 c1 e6 04 4c 01 f5 48 8b 45 00 48 85 c0 0f 84 c3 00 00 00 
48 8b 58 08 48 85 db 0f 84 fe 01 00 00 <48> 8b 13 48 89 50 08 48 8b 45 08 48 85 
c0 74 08 48 83 e8 01 48 89
xfdesktop[16727]: segfault at 16 ip 7fe22e9aa9ea sp 7ffd313bc000 error 
4 in libglib-2.0.so.0.5800.3[7fe22e95a000+7e000]
2019-07-17T01:04:07.231175+02:00 debian kernel: [18606.685725] Code: 8d 48 ff 
48 89 c3 49 89 ce 49 c1 e6 04 4c 01 f5 48 8b 45 00 48 85 c0 0f 84 c3 00 00 00 
48 8b 58 08 48 85 db 0f 84 fe 01 00 00 <48> 8b 13 48 89 50 08 48 8b 45 08 48 85 
c0 74 08 48 83 e8 01 48 89
gmain[16752]: segfault at 17 ip 7fdada99a9ea sp 7fdad7f7c7c0 error 4 in 
libglib-2.0.so.0.5800.3[7fdada94a000+7e000]
2019-07-17T01:04:21.214468+02:00 debian kernel: [18620.669154] Code: 8d 48 ff 
48 89 c3 49 89 ce 49 c1 e6 04 4c 01 f5 48 8b 45 00 48 85 c0 0f 84 c3 00 00 00 
48 8b 58 08 48 85 db 0f 84 fe 01 00 00 <48> 8b 13 48 89 50 08 48 8b 45 08 48 85 
c0 74 08 48 83 e8 01 48 89
gmain[16974]: segfault at 1c ip 7f3b5dcc29ea sp 7f3b5b2a45f0 error 4 in 
libglib-2.0.so.0.5800.3[7f3b5dc72000+7e000]
2019-07-17T01:05:28.070894+02:00 debian kernel: [18687.524814] Code: 8d 48 ff 
48 89 c3 49 89 ce 49 c1 e6 04 4c 01 f5 48 8b 45 00 48 85 c0 0f 84 c3 00 00 00 
48 8b 58 08 48 85 db 0f 84 fe 01 00 00 <48> 8b 13 48 89 50 08 48 8b 45 08 48 85 
c0 74 08 48 83 e8 01 48 89

Bug#932250: linux-image-amd64: random segfaults without taking something down

[m . alfaeko]

Package: linux-image-amd64
Version: 4.19+105
Severity: important

Hi.

Im currently running debian buster kernel and i experienced some segfaults.
Segfaults are random, which prevents me from pinpointing the trigger.
First i tried disabling overcommit on memory, the behavior stoped.
Today it started during installing updates for libreoffice. Two first
segfaults were caused by xfdesktop, the two more with gmain.
Another odd thing is that the error is in libglib and the code is completly
identical. The RAM was tested with memtest86+, memtester. Previous release
with backport kernel was working perfectly even with overcommit. I
guess there is a small chance of defective hw.
My next suspect is apparmor. Im going to use the system with disabled
apparmor to see if this problem persist.

Thank you

I hope this helps make debian more stable and reliable.

Have a nice day

-- System Information:
  APT prefers stable
  APT policy: (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 4.19.0-5-amd64 (SMP w/4 CPU cores)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8), 
LANGUAGE=en_US.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages linux-image-amd64 depends on:
ii  linux-image-4.19.0-5-amd64  4.19.37-5

linux-image-amd64 recommends no packages.

linux-image-amd64 suggests no packages.

-- no debconf information

Bug#930351: linux-image-4.9.0-9-amd64: soft lockup / stuck in pid_revalidate

[Bernhard M. Wiedemann]

On 11/06/2019 22.28, Ben Hutchings wrote:
> On Tue, 2019-06-11 at 10:13 +0200, Bernhard M. Wiedemann wrote:
> [...]
>>  kernel:[1616241.072680] NMI watchdog: BUG: soft lockup - CPU#5 stuck for 
>> 22s! [ps:28525]
>>
>> [1626796.848128] CPU: 5 PID: 28525 Comm: ps Tainted: G  D  L  
>> 4.9.0-9-amd64 #1 Debian 4.9.168-1+deb9u2
> [...]
> 
> Please provide the log for the first BUG/Oops error, which will incldue
> the text "Not tainted" instead of "Tainted: ..."

Found the very first call trace in a rotated syslog:

general protection fault:  [#1] SMP
CPU: 4 PID: 76 Comm: kswapd0 Not tainted 4.9.0-9-amd64 #1 Debian
4.9.168-1+deb9u2
Hardware name: MSI MS-7816/H87-G43 (MS-7816), BIOS V2.14B4 07/31/2013
task: 88da78f18140 task.stack: 9e7fc37f4000
RIP: 0010:[]  []
page_lock_anon_vma_read+0x27/0xe0
RSP: 0018:9e7fc37f7ae0  EFLAGS: 00010202
RAX: 0001 RBX: 7fff89da77012751 RCX: 9e7fc37f7c18
RDX:  RSI: 9e7fc37f7b78 RDI: ee1c5eafdf00
RBP: ee1c5eafdf00 R08: ee1c5eafdf20 R09: 
R10: 0002 R11: 0004 R12: 
R13: 9e7fc37f7b78 R14: 0010 R15: ee1c5eafdf20
FS:  () GS:88da9eb0() knlGS:
CS:  0010 DS:  ES:  CR0: 80050033
CR2: 7fff304e0138 CR3: 000534208000 CR4: 00162670
Stack:
 ee1c5eafdf00 9e7fc37f7c18  9e7fc37f7b78
 98fc7403 7efe 0007efef717b 88da77012750
 7a700bd0 ee1c5eafdf00 9e7fc37f7c18 
Call Trace:
 [] ? rmap_walk_anon+0x1a3/0x280
 [] ? page_referenced+0x10e/0x180
 [] ? page_check_address_transhuge+0x440/0x440
 [] ? page_get_anon_vma+0x80/0x80
 [] ? shrink_active_list+0x19b/0x350
 [] ? shrink_node_memcg+0x69a/0x7d0
 [] ? shrink_node+0xe2/0x340
 [] ? kswapd+0x2e3/0x6e0
 [] ? mem_cgroup_shrink_node+0x170/0x170
 [] ? kthread+0xd9/0xf0
 [] ? __switch_to_asm+0x34/0x70
 [] ? kthread_park+0x60/0x60
 [] ? ret_from_fork+0x57/0x70


syslog.crash.gz
Description: application/gzip

Bug#930351: linux-image-4.9.0-9-amd64: soft lockup / stuck in pid_revalidate

[Bernhard M. Wiedemann]

On 11/06/2019 22.28, Ben Hutchings wrote:
> On Tue, 2019-06-11 at 10:13 +0200, Bernhard M. Wiedemann wrote:
> [...]
>>  kernel:[1616241.072680] NMI watchdog: BUG: soft lockup - CPU#5 stuck for 
>> 22s! [ps:28525]
>>
>> [1626796.848128] CPU: 5 PID: 28525 Comm: ps Tainted: G  D  L  
>> 4.9.0-9-amd64 #1 Debian 4.9.168-1+deb9u2
> [...]
> 
> Please provide the log for the first BUG/Oops error, which will incldue
> the text "Not tainted" instead of "Tainted: ..."

Unfortunately, the first of those was already scrolled out of the
buffer. I'm now piping netconsole netcat to tee this time. We can just
ignore the bug until it re-occurs.

Bug#930351: linux-image-4.9.0-9-amd64: soft lockup / stuck in pid_revalidate

[Bernhard M. Wiedemann]

Package: src:linux
Version: 4.9.168-1+deb9u2
Severity: important

Dear Maintainer,

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

   * What led up to the situation?
 ran the server for some days with KVM VMs on top
   * What exactly did you do (or not do) that was effective (or
 ineffective)?
 Tried to ssh + ping.
   * What was the outcome of this action?
 ssh session got stuck. Ping still worked.
   * What outcome did you expect instead?
 should work

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


-- Package-specific info:
** Version:
Linux version 4.9.0-9-amd64 (debian-kernel@lists.debian.org) (gcc version 6.3.0 
20170516 (Debian 6.3.0-18+deb9u1) ) #1 SMP Debian 4.9.168-1+deb9u2 (2019-05-13)

** Command line:
BOOT_IMAGE=/vmlinuz-4.9.0-9-amd64 
root=UUID=83dcd5bf-42df-4931-aa7a-e09d8ecf6bb5 ro nomodeset nohz=off panic=30

** Not tainted

** Kernel log:
(obtained via netconsole)
Message from syslogd@golf at Jun 11 06:37:56 ...
 kernel:[1616241.072680] NMI watchdog: BUG: soft lockup - CPU#5 stuck for 22s! 
[ps:28525]

[1626796.848128] CPU: 5 PID: 28525 Comm: ps Tainted: G  D  L  
4.9.0-9-amd64 #1 Debian 4.9.168-1+deb9u2
[1626796.848205] Hardware name: MSI MS-7816/H87-G43 (MS-7816), BIOS V2.14B4 
07/31/2013
[1626796.848277] task: 88d2c5923080 task.stack: 9e7fcf8a4000
[1626796.848337] RIP: 0010:[]  [] 
native_queued_spin_lock_slowpath+0x10f/0x1a0
[1626796.848459] RSP: 0018:9e7fcf8a7c70  EFLAGS: 0246
[1626796.848518] RAX:  RBX: 88da78f18140 RCX: 
0003  
[1626796.848595] RDX: 88da9eb59480 RSI: 0018 RDI: 
88da78f18860  
[1626796.848673] RBP: 88da787e5088 R08:  R09: 
88d4fc338025  
[1626796.848745] R10: 88da9d1b99f8 R11:  R12: 
88da78f18860  
[1626796.848817] R13: 88da786fecc0 R14: 9e7fcf8a7d70 R15: 
88da9d4d44e0  
[1626796.848889] FS:  7f461c3ba880() GS:88da9eb4() 
knlGS:
[1626796.848962] CS:  0010 DS:  ES:  CR0: 80050033
[1626796.849020] CR2: 557cc5139688 CR3: 7e5f CR4: 
00162670  
[1626796.849093] Stack:
[1626796.849147]  9941a79d 9907e5af 9e7fcf8a7d78 
9e7fcf8a7de0
[1626796.849370]  88da9d1b99c0 9e7fcf8a7d78 990175cf 
9e7fcf8a7d6c
[1626796.849597]  9e7fcf8a7de0 9e7fcf8a7cf0 679aab8063728a19 
9e7fcf8a7d78
[1626796.849817] Call Trace:
[1626796.849872]  [] ? _raw_spin_lock+0x1d/0x20
[1626796.849931]  [] ? pid_revalidate+0x4f/0xf0
[1626796.849994]  [] ? lookup_fast+0x2cf/0x2f0
[1626796.850054]  [] ? path_openat+0x178/0x15b0
[1626796.850113]  [] ? filename_lookup+0xf1/0x180
[1626796.850173]  [] ? do_filp_open+0x91/0x100
[1626796.850233]  [] ? __check_object_size+0xfa/0x1d8
[1626796.850294]  [] ? do_sys_open+0x12e/0x210
[1626796.850356]  [] ? do_syscall_64+0x8d/0x100
[1626796.850417]  [] ? entry_SYSCALL_64_after_swapgs+0x58/0xc6
[1626796.850478] Code: 12 83 e0 03 83 e9 01 48 c1 e0 04 48 63 c9 48 05 80 94 01 
00 48 03 04 cd e0 f3 86 99 48 89 10 8b 42 08 85 c0 75 09 f3 90 8b 42 08 <85> c0 
74 f7 4c 8b 02 4d 85 c0 74 08 41 0f 18 08 eb 02 f3 90 8b


and another had
[1626780.842859] Call Trace:
[1626780.842914]  [] ? _raw_spin_lock+0x1d/0x20
[1626780.842974]  [] ? pid_revalidate+0x4f/0xf0
[1626780.843034]  [] ? lookup_fast+0x2cf/0x2f0
[1626780.843093]  [] ? walk_component+0x44/0x330
[1626780.843153]  [] ? path_lookupat+0x67/0x120
[1626780.843216]  [] ? filename_lookup+0xb1/0x180
[1626780.843277]  [] ? mem_cgroup_commit_charge+0x78/0x4b0
[1626780.843340]  [] ? __check_object_size+0xfa/0x1d8
[1626780.843401]  [] ? strncpy_from_user+0x48/0x160
[1626780.843465]  [] ? vfs_fstatat+0x59/0xb0
[1626780.843526]  [] ? SYSC_newlstat+0x2d/0x60
[1626780.843586]  [] ? do_syscall_64+0x8d/0x100
[1626780.843648]  [] ? entry_SYSCALL_64_after_swapgs+0x58/0xc6


** Model information
sys_vendor: MSI
product_name: MS-7816
product_version: 1.0
chassis_vendor: MSI
chassis_version: 1.0
bios_vendor: American Megatrends Inc.
bios_version: V2.14B4
board_vendor: MSI
board_name: H87-G43 (MS-7816)
board_version: 1.0

** Loaded modules:
ipt_REJECT
nf_reject_ipv4
iptable_filter
ipt_MASQUERADE
nf_nat_masquerade_ipv4
xt_multiport
xt_nat
xt_tcpudp
iptable_nat
nf_conntrack_ipv4
nf_defrag_ipv4
nf_nat_ipv4
nf_nat
nf_conntrack
ip_tables
x_tables
nfnetlink_queue
nfnetlink_log
nfnetlink
bluetooth
rfkill
cpufreq_conservative
cpufreq_powersave
cpufreq_userspace
algif_skcipher
af_alg
tun
loop
dm_crypt
intel_rapl
x86_pkg_temp_thermal
intel_powerclamp
coretemp
kvm_intel
kvm
irqbypass
crct10dif_pclmul
crc32_pclmul
i915
ghash_clmulni_intel
intel_cstate
iTCO_wdt
iTCO_vendor_support
mei_me
mei
intel_uncore
mxm_wmi
drm_kms_helper
intel_rapl_perf
pcspkr
lpc_ich
drm
evdev
serio_raw
shpchp
wmi
sg
button
mfd_core
video
i2c_algo_bit
ext4
crc16
jbd2
fscrypto
ecb
mbcache
btrfs
raid10
raid456
async_raid6_recov
async_memcpy
async_pq
async_xor
async_tx

Bug#895378: sky2: sky2: did not recover correctly after waking up from S3

[Achille M. Luongo]

Hi,

just an update about my previous post. The "pci=nomsi,noaer"
workaround is effective for resume after suspend, but it locks my
computer in resume after hibernation (the computer resumes, but it
locks on resume with a black screen when it should instead show the
login dialog; this probably happens for an interaction between "nomsi"
kernel option and the nvidia proprietary  driver, I suppose).

So that, I opted for the following simpler workaround: I created an
hook in  /lib/systemd/system-sleep (acording to
systemd-suspend.service manual page) containing the following bash
script:

#!/bin/sh
## This file (or a link to it) must be in /lib/systemd/system-sleep/
modprobe -r sky2
modprobe sky

When systemd resumes from hibernation or suspend the script is
executed and the sky2 network card driver is reset.

I hope this kernel bug would be solved soon.

Bug#909852: linux-image-4.18-0-0.bpo.1-amd64: backtrace in dmesg after suspend

[m . alfaeko]

Package: src:linux
Version: 4.18.6-1~bpo9+1
Followup-For: Bug #909852

Dear Maintainer,

I tried to suspend the system today and it resulted with a backtrace
after waking the system. The dmesg shows that amdgpu is involved with
this backtrace. It looks to me it has trouble to resume. Interesting
thing is that if i suspend/resume the first time after boot, the backtrace
appears. This first attempt was aproximatly two hours after system boot.
But if i do it again then the suspend/resume performs correctly.
This event doesn not affect the system as whole, only this message in dmesg.

Thank you for your time and i hope this helps debian to better stability.


-- Package-specific info:
** Version:
Linux version 4.18.0-0.bpo.1-amd64 (debian-kernel@lists.debian.org) (gcc 
version 6.3.0 20170516 (Debian 6.3.0-18+deb9u1)) #1 SMP Debian 4.18.6-1~bpo9+1 
(2018-09-13)

** Command line:
BOOT_IMAGE=/vmlinuz-4.18.0-0.bpo.1-amd64 root=/dev/mapper/debian--stretch-root 
ro quiet

** Tainted: WO (4608)
 * Taint on warning.
 * Out-of-tree module has been loaded.

** Kernel log:
Unable to read kernel log; any relevant messages should be attached

** Model information
sys_vendor: System manufacturer
product_name: System Product Name
product_version: System Version
chassis_vendor: Default string
chassis_version: Default string
bios_vendor: American Megatrends Inc.
bios_version: 3401
board_vendor: ASUSTeK COMPUTER INC.
board_name: PRIME A320M-K
board_version: Rev X.0x

** Loaded modules:
pci_stub
vboxpci(O)
vboxnetadp(O)
vboxnetflt(O)
vboxdrv(O)
xt_tcpudp
xt_conntrack
iptable_nat
nf_conntrack_ipv4
nf_defrag_ipv4
nf_nat_ipv4
nf_nat
nf_conntrack
iptable_filter
binfmt_misc
dm_thin_pool
dm_persistent_data
amdkfd
dm_bio_prison
dm_bufio
libcrc32c
eeepc_wmi
asus_wmi
sparse_keymap
rfkill
wmi_bmof
amdgpu
edac_mce_amd
kvm_amd
snd_hda_codec_realtek
ccp
snd_hda_codec_generic
chash
gpu_sched
snd_hda_codec_hdmi
rng_core
snd_hda_intel
ttm
kvm
snd_hda_codec
drm_kms_helper
snd_hda_core
irqbypass
drm
snd_hwdep
snd_pcm
evdev
pcspkr
sg
serio_raw
crct10dif_pclmul
crc32_pclmul
snd_timer
ghash_clmulni_intel
snd
i2c_algo_bit
soundcore
fam15h_power
k10temp
sp5100_tco
video
wmi
button
pcc_cpufreq
acpi_cpufreq
parport_pc
ppdev
lp
parport
ip_tables
x_tables
autofs4
ext4
crc16
mbcache
jbd2
crc32c_generic
fscrypto
ecb
sr_mod
cdrom
dm_mod
hid_generic
uas
usbhid
usb_storage
hid
sd_mod
crc32c_intel
aesni_intel
aes_x86_64
crypto_simd
cryptd
glue_helper
ahci
xhci_pci
libahci
i2c_piix4
xhci_hcd
libata
r8169
scsi_mod
mii
usbcore
usb_common
gpio_amdpt
gpio_generic

** PCI devices:
00:00.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Device 
[1022:1576]
Subsystem: ASUSTeK Computer Inc. Device [1043:8719]
Control: I/O- Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- SERR- 

00:01.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. 
[AMD/ATI] Carrizo [1002:9874] (rev e2) (prog-if 00 [VGA controller])
Subsystem: ASUSTeK Computer Inc. Carrizo [1043:8719]
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 
Kernel driver in use: amdgpu
Kernel modules: amdgpu

00:01.1 Audio device [0403]: Advanced Micro Devices, Inc. [AMD/ATI] Kabini 
HDMI/DP Audio [1002:9840]
Subsystem: ASUSTeK Computer Inc. Kabini HDMI/DP Audio [1043:8719]
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 
Kernel driver in use: snd_hda_intel
Kernel modules: snd_hda_intel

00:02.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Device 
[1022:157b]
Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- SERR- TAbort- Reset- FastB2B-
PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
Capabilities: 
Kernel driver in use: pcieport

00:03.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Device 
[1022:157b]
Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- SERR- 

00:09.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Device 
[1022:157d]
Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- SERR- 
Kernel driver in use: snd_hda_intel
Kernel modules: snd_hda_intel

00:10.0 USB controller [0c03]: Advanced Micro Devices, Inc. [AMD] FCH USB XHCI 

Bug#907717: linux-image-4.17.0-0.bpo.3-amd64: another backtrace with result of unusable system till reboot

[m . alfaeko]

Package: linux-image-4.17.0-0.bpo.3-amd64
Followup-For: Bug #907717

Dear Maintainer,

Today i experienced a backtrace which resulted to a system without a graphic
output. In logs i found a entry about a bug with a message Unable to handle
kernel NULL pointer deference. The process involved in Oops was again Xorg.
It looks like the kernel 4.16.0-0.bpo2-amd64 is good without this kind of
failures.

Thank you
2018-09-01T19:23:00.289544+02:00 debian kernel: [25854.565534] refcount_t: 
increment on 0; use-after-free.
2018-09-01T19:23:00.289546+02:00 debian kernel: [25854.565570] WARNING: CPU: 0 
PID: 26032 at /build/linux-h2pQxc/linux-4.17.17/lib/refcount.c:153 
refcount_inc+0x27/0x30
2018-09-01T19:23:00.289547+02:00 debian kernel: [25854.565571] Modules linked 
in: pci_stub vboxpci(O) vboxnetadp(O) vboxnetflt(O) vboxdrv(O) xt_tcpudp 
xt_conntrack iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_nat 
nf_conntrack iptable_filter binfmt_misc dm_thin_pool amdkfd dm_persistent_data 
dm_bio_prison dm_bufio libcrc32c amdgpu eeepc_wmi asus_wmi sparse_keymap rfkill 
wmi_bmof snd_hda_codec_realtek snd_hda_codec_generic snd_hda_codec_hdmi 
snd_hda_intel snd_hda_codec chash gpu_sched ttm edac_mce_amd kvm_amd 
snd_hda_core ccp drm_kms_helper snd_hwdep rng_core snd_pcm kvm snd_timer snd 
drm soundcore sg fam15h_power irqbypass evdev crct10dif_pclmul crc32_pclmul 
ghash_clmulni_intel serio_raw k10temp pcspkr shpchp i2c_algo_bit sp5100_tco 
video wmi button pcc_cpufreq acpi_cpufreq parport_pc ppdev lp parport ip_tables 
x_tables autofs4 ext4
2018-09-01T19:23:00.289549+02:00 debian kernel: [25854.565621]  crc16 mbcache 
jbd2 crc32c_generic fscrypto ecb sr_mod cdrom dm_mod hid_generic uas usbhid 
usb_storage hid sd_mod crc32c_intel aesni_intel aes_x86_64 crypto_simd cryptd 
glue_helper xhci_pci ahci i2c_piix4 libahci xhci_hcd libata r8169 mii usbcore 
scsi_mod usb_common gpio_amdpt gpio_generic
2018-09-01T19:23:00.289550+02:00 debian kernel: [25854.565647] CPU: 0 PID: 
26032 Comm: Xorg Tainted: G   O  4.17.0-0.bpo.3-amd64 #1 Debian 
4.17.17-1~bpo9+1
2018-09-01T19:23:00.289551+02:00 debian kernel: [25854.565648] Hardware name: 
System manufacturer System Product Name/PRIME A320M-K, BIOS 3401 12/04/2017
2018-09-01T19:23:00.289552+02:00 debian kernel: [25854.565650] RIP: 
0010:refcount_inc+0x27/0x30
2018-09-01T19:23:00.289553+02:00 debian kernel: [25854.565651] RSP: 
0018:abd18333b9f0 EFLAGS: 00010282
2018-09-01T19:23:00.289554+02:00 debian kernel: [25854.565652] RAX: 
 RBX: 8c7c838cdc00 RCX: 0006
2018-09-01T19:23:00.289555+02:00 debian kernel: [25854.565653] RDX: 
0007 RSI: 0092 RDI: 8c7c8a616730
2018-09-01T19:23:00.289575+02:00 debian kernel: [25854.565654] RBP: 
8c7c838ca000 R08: 0001 R09: 03c2
2018-09-01T19:23:00.289577+02:00 debian kernel: [25854.565655] R10: 
abd18333bb70 R11: 03c2 R12: abd18333ba30
2018-09-01T19:23:00.289578+02:00 debian kernel: [25854.565656] R13: 
 R14: 8c7c86627000 R15: 
2018-09-01T19:23:00.289578+02:00 debian kernel: [25854.565658] FS:  
7f268bacda40() GS:8c7c8a60() knlGS:
2018-09-01T19:23:00.289579+02:00 debian kernel: [25854.565659] CS:  0010 DS: 
 ES:  CR0: 80050033
2018-09-01T19:23:00.289580+02:00 debian kernel: [25854.565659] CR2: 
7f26799cd000 CR3: 000102764000 CR4: 001406f0
2018-09-01T19:23:00.289581+02:00 debian kernel: [25854.565661] Call Trace:
2018-09-01T19:23:00.289582+02:00 debian kernel: [25854.565777]  
dc_create_stream_for_sink+0x4e/0x190 [amdgpu]
2018-09-01T19:23:00.289583+02:00 debian kernel: [25854.565822]  
create_stream_for_sink+0x6d/0x5f0 [amdgpu]
2018-09-01T19:23:00.289584+02:00 debian kernel: [25854.565868]  ? 
amdgpu_dm_connector_mode_valid+0x62/0x1f0 [amdgpu]
2018-09-01T19:23:00.289584+02:00 debian kernel: [25854.565945]  ? 
drm_mode_connector_list_update+0xb3/0x1b0 [drm]
2018-09-01T19:23:00.289585+02:00 debian kernel: [25854.565987]  
amdgpu_dm_connector_mode_valid+0x62/0x1f0 [amdgpu]
2018-09-01T19:23:00.289586+02:00 debian kernel: [25854.566023]  
drm_helper_probe_single_connector_modes+0x52a/0x6f0 [drm_kms_helper]
2018-09-01T19:23:00.289587+02:00 debian kernel: [25854.566038]  
drm_mode_getconnector+0x2ea/0x320 [drm]
2018-09-01T19:23:00.289587+02:00 debian kernel: [25854.566052]  ? 
drm_mode_connector_property_set_ioctl+0x60/0x60 [drm]
2018-09-01T19:23:00.289588+02:00 debian kernel: [25854.566061]  
drm_ioctl_kernel+0x67/0xb0 [drm]
2018-09-01T19:23:00.289589+02:00 debian kernel: [25854.566073]  
drm_ioctl+0x2c5/0x360 [drm]
2018-09-01T19:23:00.289590+02:00 debian kernel: [25854.566084]  ? 
drm_mode_connector_property_set_ioctl+0x60/0x60 [drm]
2018-09-01T19:23:00.289591+02:00 debian kernel: [25854.566112]  
amdgpu_drm_ioctl+0x49/0x80 [amdgpu]
2018-09-01T19:23:00.289592+02:00 debian kernel: [25854.566121]  
do_vfs_ioctl+0xa2/0x620

Bug#907717: linux-image-4.17.0-0.bpo.3-amd64: random backtrace caused by refcount on Xorg

[m . alfaeko]

Package: src:linux
Version: 4.17.17-1~bpo9+1
Severity: normal

Dear Maintainer,

I had installed new kernel from debian backports repository, but im experiencing
some backtrace logs in system kern.log file. This does not affect systems
stability. Backtrace is caused by refcount and its affecting Xorg process.
My machine is running with nonfree firmware for APU and other devices which
require nonfree firmware to function properly.

Thank you for your time and i hope this helps improve debians stability

-- Package-specific info:
** Version:
Linux version 4.17.0-0.bpo.3-amd64 (debian-kernel@lists.debian.org) (gcc 
version 6.3.0 20170516 (Debian 6.3.0-18+deb9u1)) #1 SMP Debian 4.17.17-1~bpo9+1 
(2018-08-27)

** Command line:
BOOT_IMAGE=/vmlinuz-4.17.0-0.bpo.3-amd64 root=/dev/mapper/debian--stretch-root 
ro quiet

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

** Kernel log:
Unable to read kernel log; any relevant messages should be attached

** Model information
sys_vendor: System manufacturer
product_name: System Product Name
product_version: System Version
chassis_vendor: Default string
chassis_version: Default string
bios_vendor: American Megatrends Inc.
bios_version: 3401
board_vendor: ASUSTeK COMPUTER INC.
board_name: PRIME A320M-K
board_version: Rev X.0x

** Loaded modules:
pci_stub
vboxpci(O)
vboxnetadp(O)
vboxnetflt(O)
vboxdrv(O)
xt_tcpudp
xt_conntrack
iptable_nat
nf_conntrack_ipv4
nf_defrag_ipv4
nf_nat_ipv4
nf_nat
nf_conntrack
iptable_filter
binfmt_misc
dm_thin_pool
amdkfd
dm_persistent_data
dm_bio_prison
dm_bufio
libcrc32c
amdgpu
eeepc_wmi
wmi_bmof
snd_hda_codec_realtek
asus_wmi
snd_hda_codec_hdmi
snd_hda_codec_generic
sparse_keymap
rfkill
snd_hda_intel
snd_hda_codec
chash
edac_mce_amd
snd_hda_core
kvm_amd
gpu_sched
ttm
snd_hwdep
snd_pcm
ccp
rng_core
drm_kms_helper
snd_timer
kvm
drm
snd
sg
soundcore
irqbypass
shpchp
crct10dif_pclmul
crc32_pclmul
ghash_clmulni_intel
k10temp
evdev
serio_raw
fam15h_power
i2c_algo_bit
sp5100_tco
pcspkr
video
button
wmi
pcc_cpufreq
acpi_cpufreq
parport_pc
ppdev
lp
parport
ip_tables
x_tables
autofs4
ext4
crc16
mbcache
jbd2
crc32c_generic
fscrypto
ecb
dm_mod
sr_mod
cdrom
sd_mod
hid_generic
uas
usbhid
usb_storage
hid
crc32c_intel
aesni_intel
aes_x86_64
ahci
xhci_pci
crypto_simd
libahci
cryptd
glue_helper
xhci_hcd
libata
usbcore
i2c_piix4
r8169
mii
scsi_mod
usb_common
gpio_amdpt
gpio_generic

** PCI devices:
00:00.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Device 
[1022:1576]
Subsystem: ASUSTeK Computer Inc. Device [1043:8719]
Control: I/O- Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- SERR- 

00:01.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. 
[AMD/ATI] Carrizo [1002:9874] (rev e2) (prog-if 00 [VGA controller])
Subsystem: ASUSTeK Computer Inc. Carrizo [1043:8719]
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 
Kernel driver in use: amdgpu

00:01.1 Audio device [0403]: Advanced Micro Devices, Inc. [AMD/ATI] Kabini 
HDMI/DP Audio [1002:9840]
Subsystem: ASUSTeK Computer Inc. Kabini HDMI/DP Audio [1043:8719]
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 
Kernel driver in use: snd_hda_intel

00:02.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Device 
[1022:157b]
Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- SERR- TAbort- Reset- FastB2B-
PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
Capabilities: 
Kernel driver in use: pcieport

00:03.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Device 
[1022:157b]
Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- SERR- 

00:09.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Device 
[1022:157d]
Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- SERR- 
Kernel driver in use: snd_hda_intel

00:10.0 USB controller [0c03]: Advanced Micro Devices, Inc. [AMD] FCH USB XHCI 
Controller [1022:7914] (rev 20) (prog-if 30 [XHCI])
Subsystem: ASUSTeK Computer Inc. FCH USB XHCI Controller [1043:8719]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- 

firmware-atheros

[Timothy M Butterworth]

All,

The current Ath3K firmware is failing to load on IMC Networks Atheros
AR3012 Bluetooth 4.0 Adapter's This is relatively old hardware 5+
years. I tested the hardware with Ubuntu 16.04 and it works.

usb 1-1.1: firmware: failed to load ar3k/AthrBT_0x01020200.dfu (-2)
Bluetooth: Loading patch file failed

I'm not sure where to submit bugs so I hope this works.

thanks

Tim

Bug#906107: linux-image-3.16.0-6-amd64: Latests kernel 3.16 on KVM host breaks Linux guest with lastests kernels

[Jose M Calhariz]

On Tue, Aug 14, 2018 at 10:39:12AM +0100, Jose M Calhariz wrote:
> Package: src:linux
> Version: 3.16.57-2
> Severity: important
> 
> We use OpenNebula on Debian 8 to run KVM guests.  Our latest upgrade of the 
> host and guests broke badly.
> The host can not run guests with the latest kernels from Debian 8 and 9.  If 
> we downgrade the kernel on 
> host or guest the problem is no longer present.
> 
> To localize the root problem, I managed to launch a KVM guest on the command 
> line using the lastest 
> Debian live CD and the problem was the same.  This is not a problem of 
> OpenNebula. 
> 
> I need help to collect more information about what is going wrong on the 
> guest and the host.
> 
> Kind regards
> Jose M Calhariz
> 

I have made videos of a guest live cd from Debian trying to boot and
failing.

qemu-system-x86_64 -enable-kvm -machine pc-i440fx-2.1,accel=kvm,usb=off -m 8096 
-device cirrus-vga,id=video0 -device 
virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x5 -cpu host -msg timestamp=on 
-smp 4,sockets=4,cores=1,threads=1 -display vnc=:22 -cdrom 
~cal/debian-9.5.0-amd64-xfce-CD-1.iso

The most informative have 60MB.  There is a recomended place to upload
videos?  If not, I can upload on my homepage at University.


Kind regards
Jose M Calhariz



-- 
--
Quem ama puríssima, dourada lhe parece.


signature.asc
Description: PGP signature

Bug#906107: linux-image-3.16.0-6-amd64: Latests kernel 3.16 on KVM host breaks Linux guest with lastests kernels

[Jose M Calhariz]

Package: src:linux
Version: 3.16.57-2
Severity: important

We use OpenNebula on Debian 8 to run KVM guests.  Our latest upgrade of the 
host and guests broke badly.
The host can not run guests with the latest kernels from Debian 8 and 9.  If we 
downgrade the kernel on 
host or guest the problem is no longer present.

To localize the root problem, I managed to launch a KVM guest on the command 
line using the lastest 
Debian live CD and the problem was the same.  This is not a problem of 
OpenNebula. 

I need help to collect more information about what is going wrong on the guest 
and the host.

Kind regards
Jose M Calhariz



-- Package-specific info:
** Version:
Linux version 3.16.0-6-amd64 (debian-kernel@lists.debian.org) (gcc version 
4.9.2 (Debian 4.9.2-10+deb8u1) ) #1 SMP Debian 3.16.57-2 (2018-07-14)

** Command line:
BOOT_IMAGE=/boot/vmlinuz-3.16.0-6-amd64 root=/dev/mapper/system-root ro quiet

** Tainted: I (2048)
 * Working around severe firmware bug.

** Kernel log:

[ 1176.926137] kvm [12584]: vcpu0 unhandled rdmsr: 0x1c9
[ 1176.926209] kvm [12584]: vcpu0 unhandled rdmsr: 0x1a6
[ 1176.926275] kvm [12584]: vcpu0 unhandled rdmsr: 0x1a7
[ 1176.926341] kvm [12584]: vcpu0 unhandled rdmsr: 0x3f6


** Model information
sys_vendor: Dell Inc.
product_name: PowerEdge R410
product_version: 
chassis_vendor: Dell Inc.
chassis_version: 
bios_vendor: Dell Inc.
bios_version: 1.9.0
board_vendor: Dell Inc.
board_name: 01V648
board_version: A04

** Loaded modules:
nf_conntrack_ipv4
nf_defrag_ipv4
xt_conntrack
nf_conntrack
xt_physdev
ip_set
nfnetlink
vhost_net
vhost
macvtap
macvlan
tun
xt_multiport
iptable_filter
ip_tables
x_tables
dm_round_robin
ib_iser
rdma_cm
iw_cm
ib_cm
ib_sa
ib_mad
ib_core
ib_addr
iscsi_tcp
libiscsi_tcp
libiscsi
scsi_transport_iscsi
rpcsec_gss_krb5
nfsv4
dns_resolver
nfsd
auth_rpcgss
oid_registry
nfs_acl
nfs
lockd
fscache
sunrpc
bridge
8021q
garp
stp
mrp
llc
dm_queue_length
dm_multipath
scsi_dh
intel_powerclamp
coretemp
kvm_intel
ttm
drm_kms_helper
kvm
drm
crc32_pclmul
ipmi_devintf
iTCO_wdt
iTCO_vendor_support
dcdbas
joydev
evdev
aesni_intel
acpi_power_meter
serio_raw
aes_x86_64
pcspkr
ipmi_si
lrw
lpc_ich
gf128mul
tpm_tis
glue_helper
tpm
mfd_core
ablk_helper
cryptd
i7core_edac
ipmi_msghandler
edac_core
shpchp
processor
thermal_sys
button
xfs
libcrc32c
dm_mod
raid1
md_mod
sd_mod
crc_t10dif
crct10dif_generic
hid_generic
usbhid
hid
usb_storage
sg
sr_mod
cdrom
mptsas
ahci
libahci
scsi_transport_sas
ehci_pci
uhci_hcd
mptscsih
ehci_hcd
libata
mptbase
igb
i2c_algo_bit
crct10dif_pclmul
crct10dif_common
i2c_core
crc32c_intel
dca
usbcore
ptp
psmouse
usb_common
scsi_mod
pps_core
bnx2

** Network interface configuration:

(...) Privacy concerns



** Network status:
*** IP interfaces and addresses:

(...) Privacy concerns

*** Device statistics:
Inter-|   Receive|  Transmit
 face |bytespackets errs drop fifo frame compressed multicast|bytes
packets errs drop fifo colls carrier compressed
eth0.600: 464024832 5969272000 0  0  2853 17974996  
 97260000 0   0  0
lo:   901381748000 0  0 090138
1748000 0   0  0
  eth3: 1783009756  3986650 17260 0  0 30266 71899026  
240175000 0   0  0
br0011: 55169743  796451000 0  0 035956 
418000 0   0  0
  eth2: 14674510167 64522160 17260 0  0 30478 559178254 
6193727000 0   0  0
eth0.11: 91505035 1195004000 0  0895144 98536503  
364324000 0   0  0
brj600: 14577853219 6342345000 0  0 0 559177990 
6193723000 0   0  0
  eth1:   0   0000 0  0 00  
 0000 0   0  0
brj601: 1772277206  299405000 0  0 0 71645058  
236327000 0   0  0
  eth0: 2119825552 12748932   81 1723081  0   1859406 
21539361933 14723412000 0   0  0

*** Protocol statistics:
Ip:
8615928 total packets received
1518 with invalid addresses
0 forwarded
0 incoming packets discarded
8002257 incoming packets delivered
7038705 requests sent out
4 fragments received ok
8 fragments created
Icmp:
9817 ICMP messages received
0 input ICMP message failed.
ICMP input histogram:
destination unreachable: 11
echo requests: 9806
9822 ICMP messages sent
0 ICMP messages failed
ICMP output histogram:
destination unreachable: 16
echo replies: 9806
IcmpMsg:
InType3: 11
InType8: 9806
OutType0: 9806
OutType3: 16
Tcp:
 active connections openings
415 passive

Bug#900442: linux-image-4.16.0-2-amd64: LVM2 COW snapshots fail as of 4.16

[Aaron M. Ucko]

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

[Copying Debian LVM team, but tentatively assigning this bug to the kernel.]

I've found that as of Linux 4.16, making traditional COW LVM2 snapshots
fails.  (AFAICT, I can't substitute thin snapshots because my origin
volumes aren't thin and need to remain mounted read-write.)  I've worked
around this problem for now by sticking with 4.15, but that's obviously
not a good long-term solution.

Specifically, the relevant "lvm create" command initially fails with
errors of the form

  Using default stripesize 64.00 KiB.
  device-mapper: reload ioctl on  (253:N+1) failed: Input/output error
  Failed to lock logical volume MyGroup/MyVolume.
  Aborting. Manual intervention required.

with the kernel meanwhile logging messages of the form

generic_make_request: Trying to write to read-only block-device dm-N (partno 0)
device-mapper: persistent snapshot: write_header failed
device-mapper: table: 253:N+1: snapshot: Failed to read snapshot metadata
device-mapper: ioctl: error adding target to table

Subsequent attempts fail with errors of the form

  Using default stripesize 64.00 KiB.
Setting chunksize to 4.00 KiB.
Archiving volume group "MyGroup" metadata (seqno 9540).
Creating logical volume MyVolume.snap
Creating volume group backup "/etc/lvm/backup/MyGroup" (seqno 9541).
activation/volume_list configuration setting not defined: Checking only 
host tags for MyGroup/MyVolume.snap.
Creating MyGroup-MyVolume.snap
Loading MyGroup-MyVolume.snap table (253:M)
Resuming MyGroup-MyVolume.snap (253:M)
Initializing 4.00 KiB of logical volume "MyGroup/MyVolume.snap" with value 
0.
    Removing MyGroup-MyVolume.snap (253:M)
Creating logical volume snapshot0
Creating MyGroup-MyVolume.snap-cow
  device-mapper: create ioctl on MyGroup-MyVolume.snap-cow LVM-GfNest[...]-cow 
failed: Device or resource busy
  Failed to lock logical volume MyGroup/MyVolume.
  Aborting. Manual intervention required.

Could you please take a look?

Thanks!

-- Package-specific info:
** Kernel log: boot messages should be attached

** Model information
sys_vendor: Gateway
product_name: DX4860
product_version: 
chassis_vendor: Gateway
chassis_version: 
bios_vendor: American Megatrends Inc.
bios_version: P02-A1
board_vendor: Gateway
board_name: IPISB-VR
board_version: 1.01

** PCI devices:
00:00.0 Host bridge [0600]: Intel Corporation 2nd Generation Core Processor 
Family DRAM Controller [8086:0100] (rev 09)
Subsystem: Acer Incorporated [ALI] 2nd Generation Core Processor Family 
DRAM Controller [1025:0589]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- 
Kernel driver in use: snb_uncore

00:02.0 VGA compatible controller [0300]: Intel Corporation 2nd Generation Core 
Processor Family Integrated Graphics Controller [8086:0102] (rev 09) (prog-if 
00 [VGA controller])
Subsystem: Acer Incorporated [ALI] 2nd Generation Core Processor Family 
Integrated Graphics Controller [1025:0589]
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- 
Kernel driver in use: i915
Kernel modules: i915

00:16.0 Communication controller [0780]: Intel Corporation 6 Series/C200 Series 
Chipset Family MEI Controller #1 [8086:1c3a] (rev 04)
Subsystem: Acer Incorporated [ALI] 6 Series/C200 Series Chipset Family 
MEI Controller [1025:0589]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 
Kernel driver in use: mei_me
Kernel modules: mei_me

00:1a.0 USB controller [0c03]: Intel Corporation 6 Series/C200 Series Chipset 
Family USB Enhanced Host Controller #2 [8086:1c2d] (rev 05) (prog-if 20 [EHCI])
Subsystem: Acer Incorporated [ALI] 6 Series/C200 Series Chipset Family 
USB Enhanced Host Controller [1025:0589]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- 
SERR- 
Kernel driver in use: ehci-pci
Kernel modules: ehci_pci

00:1b.0 Audio device [0403]: Intel Corporation 6 Series/C200 Series Chipset 
Family High Definition Audio Controller [8086:1c20] (rev 05)
Subsystem: Acer Incorporated [ALI] 6 Series/C200 Series Chipset Family 
High Definition Audio Controller [1025:0589]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 
Kernel driver in u

Bug#893912: firmware-realtek: Failed to load rtl_bt/rtl8821a_config.bin

[Francisco M Neto]

This happens on my machine as well. 

I'm running buster with 4.16 kernel and firmware-realtek is installed.
It seems that this file should be in the package but it hasn't been
include for some reason, even though it is available from https://githu
b.com/lwfinger/rtl8723au_bt/.

Installing the file on /lib/firmware/rtl_bt/ solves the issue.


On Fri, 23 Mar 2018 19:02:48 +0100 "Rathorian" <cont...@rathorian.fr>
wrote:
> Package: firmware-realtek
> Version: 20161130-3
> Severity: important
> 
> Dear Maintainer,
> 
> Every time I start Debian, I get an error message saying:
> "bluetooth hci0: firmware: failed to load rtl_bt/rtl8821a_config.bin"
> 
> I have also tried to install the package since stretch-backports,
without
> any success.
> 
> Cordially
> Rathorian
> 
> -- System Information:
> Debian Release: 9.4
>   APT prefers stable-updates
>   APT policy: (500, 'stable-updates'), (500, 'stable')
> Architecture: amd64 (x86_64)
> 
> Kernel: Linux 4.9.0-6-amd64 (SMP w/4 CPU cores)
> Locale: LANG=fr_FR.utf8, LC_CTYPE=fr_FR.utf8 (charmap=UTF-8),
> LANGUAGE=fr_FR.utf8 (charmap=UTF-8)
> Shell: /bin/sh linked to /bin/dash
> Init: systemd (via /run/systemd/system)
> 
> firmware-realtek depends on no packages.
> 
> firmware-realtek recommends no packages.
> 
> Versions of packages firmware-realtek suggests:
> ii  initramfs-tools  0.130
> 
> -- no debconf information
> 
-- 
--
[]s,

Francisco M Neto

Bug#885245: linux: FTBFS on powerpcspe: sstep.c: ptesync unrecognized

[Aaron M. Ucko]

Ben Hutchings <b...@decadent.org.uk> writes:

> I would welcome a powerpcspe porter to join the kernel team, but until
> that happens you should not expect any fixes from our side.  (If you

Fair enough.  FTR, I'm not a porter for this (or any other) architecture
myself, just a regular DD who helps ensure that build errors for
packages that have recently emerged from NEW don't accidentally escape
notice.

-- 
Aaron M. Ucko, KB1CJC (amu at alum.mit.edu, ucko at debian.org)
http://www.mit.edu/~amu/ | http://stuff.mit.edu/cgi/finger/?a...@monk.mit.edu

Bug#885245: linux: FTBFS on powerpcspe: sstep.c: ptesync unrecognized

[Aaron M. Ucko]

Source: linux
Version: 4.14.7-1
Severity: important
Tags: upstream
Justification: fails to build from source (but built successfully in the past)
User: debian-powe...@lists.debian.org
Usertags: powerpcspe

Builds of linux for powerpcspe (admittedly not a release architecture)
have been failing lately:

  {standard input}: Assembler messages:
  {standard input}:5854: Error: unrecognized opcode: `ptesync'
  /<>/scripts/Makefile.build:319: recipe for target 
'arch/powerpc/lib/sstep.o' failed
  make[6]: *** [arch/powerpc/lib/sstep.o] Error 1

Could you please take a look?

Thanks!

-- 
Aaron M. Ucko, KB1CJC (amu at alum.mit.edu, ucko at debian.org)
http://www.mit.edu/~amu/ | http://stuff.mit.edu/cgi/finger/?a...@monk.mit.edu

Bug#883980: security information -- dsa-4073-1 linux

[Gerard M. Vignes]

I installed "security information -- dsa-4073-1 linux" and rebooted into 
the 4.9.0-4-amd64 kernel. The screen-blacking problem still exists, but 
now it is accented by longer periods when the screen goes haywire.


All I have to do to create the problem now is to (1) start Terminator, 
(2) make it full-screen, (3) split it into two horizontal windows and 
(4) use the arrow keys to scroll bash history. The screen goes crazy, as 
if it were being drawn in all the wrong places. The screen rapidly snaps 
between various renderings, most of them incorrect, where parts of the 
screen are in the wrong places. After jumping between dozens of bad 
screen renderings, the screen goes black for a second. When the screen 
lights up again, sometimes it is normal and sometimes the crazy behavior 
repeats. All I have to do is type into the terminal or use the arrow 
keys to trigger the crazy screen behavior, although it still occurs 
somewhat sporadically.


I am back working in the 4.9.0-3-amd64 kernel. No problems.

Bug#815037: firmware-iwlwifi: Bug also leads to kernel panic and freezes

[Daniel M.]

Bug message and freezes / panic is solved when I downgraded to stable.
So no HW problem.

Bug#883980: Experimenting with 4.9.0-4-amd64 and 4.9.0-3-amd64

[Gerard M. Vignes]

Without installing, updating or removing any software, I am 
experimenting with kernels 4.9.0-4-amd64 and 4.9.0-3-amd64.


When I applied the Debian 9.3 upgrade, it installed a new kernel and 
retained the older kernel. I can select the newer or older kernel using 
the advanced boot menu.


When I boot with the newer 4.9.0-4-amd64 kernel, I experience the 
problem with screen going black for 1 second. This happens sporadically, 
but often enough to disrupt normal workstation activities.


When I boot with the older 4.9.0-3-amd64 kernel, I am not able to 
duplicate the problem.


I only discovered how to boot between old and new kernels last night, so 
I am going to continue booting on the older 4.9.0-3-amd64 kernel until a 
new kernel is released. I will post to this bug report again ONLY IF I 
discover that the problem occurs using the older 4.9.0-3-amd64 kernel.


I believe that the Debian 9.3 upgrade and/or newer 4.9.0-4-amd64 kernel 
introduced a problem that causes my screen to sporadically go black for 
1 second. The general conditions to duplicate this problem are outlined 
in my previous posts to this bug report. The simple diagnostics about my 
machine, which I provided as attachments, are also available in previous 
posts.


Thank you.

Bug#883980: Fifth Manifestation

[Gerard M. Vignes]

I was using the latest, built-in version of Firefox ESR 52.5.2 (64-bit), 
and I noticed that I got the same, consistent problem as with Chromium.


When I move the mouse cursor between surrounding page and embedded video 
(either direction), the screen goes black for 1 second. This behavior is 
identical to what I experience in Chromium.


This is the list of applications for which I have seen this problem so far:
Chromium
Terminator
Terminal running Bash
Software
Firefox ESR

Bug#883980: Steps to Duplicate Problem

[Gerard M. Vignes]

After a clean reboot, I began experimenting to find repeatable steps to 
duplicate the problem.


I have the following programs running across 9 workspaces (which are 
always running on my machine): Chromium & gPHPEdit, Web (Ephiphany) & 
Geany, and Terminator (running a split screen). The problem does not 
manifest itself yet.


I open a Terminal running Screen plus Files (Nautilus) plus Document 
Viewer (Evince). Then the problem begins to manifest itself, and it 
grows worse as I experiment.


FIRST MANIFESTATION: I open a youtube video in Chromium and it begins 
playing. When I move my mouse pointer from the surrounding page across 
the embedded video, or back again, the screen goes black for 1 second. 
This manifestation is not sporadic. It happens almost every single time, 
provided the above conditions are met.


SECOND MANIFESTATION: When I type something in Terminator, the screen 
goes black for 1 second. This manifestation is sporadic. It happens from 
time to time, provided the above conditions are met.


THIRD MANIFESTATION: When I open Software, and I type a term in the 
Search field, the screen goes black for 1 second. This manifestation is 
sporadic. I happens only sometimes.


FOURTH MANIFESTATION: When I type into Bash running in Terminal, the 
screen goes black for 1 second. This manifestation is sporadic. I 
happens only sometimes.


OBSERVATION: As I experiment and open additional copies of Document 
Viewer (Evince), the problem seems to get much worse. The screen goes 
black for longer periods of time, and when it returns, it is frequently 
scrambled up, goes black again, and then returns to normal.


NOTE: I have 8GB of RAM. I have been routinely doing these activities 
and much more for the past 4 months, with no problems. I do not believe 
that I am near to maxing out memory. This problem appeared with the 
upgrade to Debian 9.3.


I am looking into how I can downgrade the kernel without causing further 
problems. This is my only, my primary work machine. I cannot afford to 
screw it up. I don't have a second computer to experiment with. Sorry.


I am happy to help with any reasonable troubleshooting steps. Thanks.

Bug#869511: linux: binNMU-unsafe dependency on linux-headers-*-common

[Aaron M. Ucko]

Source: linux
Version: 4.11.11-1
Severity: grave
Justification: renders package unusable (uninstallable)

The recent binNMU of linux for Perl 5.26 broke the build-specific
headers packages, which are architecture-dependent but depend on an
identical *binary* version of the architecture-independent
linux-headers-*-common package.  Specifically, I observe that
linux-headers-4.11.0-2-amd64 4.11.11-1+b1 depends on
linux-headers-4.11.0-2-common (= 4.11.11-1+b1), which does not exist.

Could you please fix these relationships to use ${source:Version}?
(As you may recall, the legacy ${Source-Version} variable is an alias
for *${binary:Version}*.)

Thanks!

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

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

Bug#862013: initramfs-tools-core: /run tmpfs size hardcoded at 10% RAM, but 16.0 MiB free required in /run/systemd

[José M Cerqueira Esteves]

Thanks for the suggestions!

On the subject of RAM requirements, for i386 systems (the case in my
original message) a minimum of 128 MB is still mentioned in  
https://www.debian.org/releases/stable/i386/ch03s04.html.en
Thus it might make sense to automatically cater for such low-mem i386
systems, or at least mention those fstab adjustments in the
installation instructions.

Best regards
J Esteves

Bug#867677: initramfs-tools: [patch] feature request: provide hook to set host name in InitRAMFS config dynamically

[M. Buecher]

And if you remove the extension .sh, then it is also backwards 
compatible with Debian 4.0 "Etch" :)
# Define your network setup for the InitRAMFS via IP variable
#
# Still a kernel ip parameter will override any InitRAMFS config
# setting (see script /usr/share/initramfs-tools/init).
#
# Additional information:
# * https://www.kernel.org/doc/Documentation/filesystems/nfs/nfsroot.txt
#   In Debian as kernel command via /etc/default/grub
# * The "variable" ${hostname} (case-sensitive) will be replaced on InitRAMFS 
creation
#   with the current host name through the hook `set_hostname_in_network_config`
#   This allows the machine to be registered with its name in DNS.

IP=${hostname}
#!/bin/sh

#
# This InitRAMFS hook provides:
# Simple script to set IP parameter in InitRAMFS config with current
# hostname, instead of manually maintaining InitRAMFS config.

PREREQ=""

prereqs()
{
	echo "${PREREQ}"
}

case "${1}" in
 prereqs)
	prereqs
	exit 0
	;;
esac

. /usr/share/initramfs-tools/hook-functions

#
# Begin real processing
#
[ ! -f "${DESTDIR}/conf/initramfs.conf" ] || sed -i -e "s#\${hostname}#$(hostname)#" "${DESTDIR}/conf/initramfs.conf"
[ ! -f "${DESTDIR}/conf/conf.d/network" ] || sed -i -e "s#\${hostname}#$(hostname)#" "${DESTDIR}/conf/conf.d/network"

Bug#867677: initramfs-tools: [patch] feature request: provide hook to set host name in InitRAMFS config dynamically

[M. Buecher]

Updated script, more clean and also processes conf/initramfs.conf#!/bin/sh

#
# This InitRAMFS hook provides:
# Simple script to set IP parameter in InitRAMFS config with current
# hostname, instead of manually maintaining InitRAMFS config.

PREREQ=""

prereqs()
{
	echo "${PREREQ}"
}

case "${1}" in
 prereqs)
	prereqs
	exit 0
	;;
esac

. /usr/share/initramfs-tools/hook-functions

#
# Begin real processing
#
[ ! -f "${DESTDIR}/conf/initramfs.conf" ] || sed -i -e "s#\${hostname}#$(hostname)#" "${DESTDIR}/conf/initramfs.conf"
[ ! -f "${DESTDIR}/conf/conf.d/network" ] || sed -i -e "s#\${hostname}#$(hostname)#" "${DESTDIR}/conf/conf.d/network"

Bug#867677: initramfs-tools: [patch] feature request: provide hook to set host name in InitRAMFS config dynamically

[M. Buecher]

Package: initramfs-tools
Version: 0.130
Severity: wishlist
Tags: patch

Dear Maintainer,

when connecting to the InitRAMFS via network (e.g. encrypted root fs), then it 
is
helpful if the machine can be registered by its name in the DNS, making it 
possible
to connect to it via its DNS name. Otherwise you have to look up the assigned 
ip in
the DHCP server log.
Therefore please provide a config and hook that dynamically sets the host name
on InitRAMFS creation.

My current workaround consists of a simple config file and a simple hook script:
/etc/initramfs-tools/conf.d/network
/etc/initramfs-tools/hooks/set_hostname_in_network_config.sh

This workaround is easy to use on any machine without manually editing the host 
name
on installation or whenever it changes. Also avoiding typos of the host name.
Additionally it gives an explicit point where to define your network 
configuration
for InitRAMFS-only (not as a kernel command line).

Would be great if you could consider adding this to the package.

Kind regards
Maddes

-- Package-specific info:
-- initramfs sizes
-rw--- 1 root root 18M Jul  8 13:51 /boot/initrd.img-4.9.0-3-amd64
-- /proc/cmdline
BOOT_IMAGE=/boot/vmlinuz-4.9.0-3-amd64 root=/dev/sda1 ro quiet

-- resume
RESUME=UUID=6c849bd6-03b5-4464-9ffe-6a8601f3f23e
-- /proc/filesystems
ext3
ext2
ext4

-- lsmod
Module  Size  Used by
crct10dif_pclmul   16384  0
crc32_pclmul   16384  0
ghash_clmulni_intel16384  0
ppdev  20480  0
pcspkr 16384  0
vmw_balloon20480  0
intel_rapl_perf16384  0
joydev 20480  0
evdev  24576  1
serio_raw  16384  0
sg 32768  0
parport_pc 28672  0
vmwgfx237568  1
battery20480  0
shpchp 36864  0
parport49152  2 parport_pc,ppdev
acpi_cpufreq   20480  0
ttm98304  1 vmwgfx
drm_kms_helper155648  1 vmwgfx
vmw_vmci   69632  1 vmw_balloon
drm   360448  4 vmwgfx,ttm,drm_kms_helper
ac 16384  0
button 16384  0
ip_tables  24576  0
x_tables   36864  1 ip_tables
autofs440960  2
ext4  585728  1
crc16  16384  1 ext4
jbd2  106496  1 ext4
crc32c_generic 16384  0
fscrypto   28672  1 ext4
ecb16384  0
mbcache16384  2 ext4
hid_generic16384  0
usbhid 53248  0
hid   122880  2 hid_generic,usbhid
sr_mod 24576  0
cdrom  61440  1 sr_mod
sd_mod 45056  3
ata_generic16384  0
crc32c_intel   24576  2
aesni_intel   167936  1
aes_x86_64 20480  1 aesni_intel
glue_helper16384  1 aesni_intel
lrw16384  1 aesni_intel
gf128mul   16384  1 lrw
ablk_helper16384  1 aesni_intel
cryptd 24576  3 ablk_helper,ghash_clmulni_intel,aesni_intel
psmouse   135168  0
xhci_pci   16384  0
xhci_hcd  188416  1 xhci_pci
usbcore   249856  3 usbhid,xhci_pci,xhci_hcd
usb_common 16384  1 usbcore
vmxnet357344  0
vmw_pvscsi 24576  2
ahci   36864  0
libahci32768  1 ahci
i2c_piix4  24576  0
ata_piix   36864  0
libata249856  4 ahci,ata_piix,libahci,ata_generic
scsi_mod  225280  5 sd_mod,libata,sr_mod,sg,vmw_pvscsi

-- /etc/initramfs-tools/modules

-- /etc/kernel-img.conf
# Kernel image management overrides
# See kernel-img.conf(5) for details
do_symlinks = yes
do_bootloader = no
do_initrd = yes
link_in_boot = no

-- /etc/initramfs-tools/initramfs.conf
MODULES=most
BUSYBOX=auto
KEYMAP=n
COMPRESS=gzip
DEVICE=
NFSROOT=auto

-- /etc/initramfs-tools/update-initramfs.conf
update_initramfs=yes
backup_initramfs=no

-- /etc/crypttab
# 

-- mkinitramfs hooks
/etc/initramfs-tools/hooks/:
set_hostname_in_network_config.sh

/usr/share/initramfs-tools/hooks:
cryptgnupg
cryptkeyctl
cryptopenct
cryptopensc
cryptpassdev
cryptroot
cryptroot-unlock
dmsetup
dropbear
fsck
keymap
klibc-utils
kmod
resume
thermal
udev
zz-busybox


-- System Information:
Debian Release: 9.0
  APT prefers stable
  APT policy: (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 4.9.0-3-amd64 (SMP w/1 CPU core)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US:en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages initramfs-tools depends on:
ii  initramfs-tools-core  0.130
ii  linux-base4.5

initramfs-tools recommends no packages.

Versions of packages initramfs-tools suggests:
ii  bash-completion  1:2.1-4.3

-- no 

Bug#862013: initramfs-tools-core: /run tmpfs size hardcoded at 10% RAM, but 16.0 MiB free required in /run/systemd

[J M Cerqueira Esteves]

Package: initramfs-tools-core
Version: 0.130
Severity: important

In a virtual machine with 160 MiB RAM, running a freshly installed Debian 
stretch system (i686),
got messages like this logged from (at least) sh and ifup:

   "Failed to reload daemon: Refusing to reload, not enough space available on 
/run/systemd.
Currently, 15.6M are free, but a safety buffer of 16.0M is enforced."

I noticed that /usr/share/initramfs-tools/init  mounts /run specifying 
"size=10%".

To prevent this issue in machines low on RAM, it would be nice for the /run 
tmpfs size
to be automatically set taking into account systemd's minimum requirement.  Or, 
at least,
to have this size as a nicely (/etc/...) configurable parameter with some 
warning on README.

-- System Information:
Debian Release: 9.0
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: i386
 (i686)

Kernel: Linux 4.9.0-2-686-pae (SMP w/1 CPU core)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages initramfs-tools-core depends on:
ii  cpio 2.11+dfsg-6
ii  klibc-utils  2.0.4-9
ii  kmod 23-2
ii  udev 232-22

Versions of packages initramfs-tools-core recommends:
ii  busybox  1:1.22.0-19+b3

Versions of packages initramfs-tools-core suggests:
ii  bash-completion  1:2.1-4.3

-- no debconf information

Bug#851928: linux-image-4.9.0-1-amd64: Kernel 4.9 fails to boot on Thinkpad T440p

[John M.]

On Sat, 2017-01-21 at 16:33 +0900, Roger Shimizu wrote:
> Control: tag -1 + patch upstream
> Control: forwarded -1 https://bugzilla.kernel.org/show_bug.cgi?id=191
> 121
> 
> On Fri, Jan 20, 2017 at 11:26 AM, JWM  wrote:
> > Package: src:linux
> > Version: 4.9.2-2
> > Severity: normal
> > 
> > Dear Maintainer,
> > 
> > After upgrading my Thinkpad T440p to linux-image-amd64 from
> > unstable (along
> > with linux-headers-amd64, linux-doc, linux-perf, linux-source and
> > linux-tools),
> > I am unable to boot with the 4.9.2 kernel.
> > 
> > Right after GRUB times out, the screen goes blank and nothing
> > happens.
> > 
> > According to this page
> > 
> > https://bugzilla.kernel.org/show_bug.cgi?id=191121
> 
> The report implies the following two commits, which already applied
> in
> linus tree, can fix this issue.
>  - http://git.kernel.org/linus/20b1e22d01a4b0b11d3a1066e9feb04be38607
> ec
>  - http://git.kernel.org/linus/0100a3e67a9cef64d72cd3a1da86f3ddbee503
> 63
> 
> Is it convenient for you to confirm?
> 
> Cheers,

Hi,

It took forever to build (i.e., about three hours just for amd64), but
yes, after applying those two patches I can boot properly ("journalctl
-b -k" messages attached).
--
John
 -- Logs begin at Mon 2016-08-08 16:33:01 COT, end at Sat 2017-01-21 13:14:32 COT. --
Jan 21 12:58:05 walrus-edge kernel: Linux version 4.9.0-1-amd64 (debian-kernel@lists.debian.org) (gcc version 6.2.1 20161124 (Debian 6.2.1-5) ) #1 SMP Debian 4.9.2-2a~test (2017-01-21)
Jan 21 12:58:05 walrus-edge kernel: Command line: BOOT_IMAGE=/vmlinuz-4.9.0-1-amd64 root=UUID=6509d59d-a080-4e59-bd0e-e83cacba4369 ro quiet splash resume=UUID=e2031b87-4394-4219-8d65-761dcff59e0f acpi_backlight=vendor
Jan 21 12:58:05 walrus-edge kernel: x86/fpu: Supporting XSAVE feature 0x001: 'x87 floating point registers'
Jan 21 12:58:05 walrus-edge kernel: x86/fpu: Supporting XSAVE feature 0x002: 'SSE registers'
Jan 21 12:58:05 walrus-edge kernel: x86/fpu: Supporting XSAVE feature 0x004: 'AVX registers'
Jan 21 12:58:05 walrus-edge kernel: x86/fpu: xstate_offset[2]:  576, xstate_sizes[2]:  256
Jan 21 12:58:05 walrus-edge kernel: x86/fpu: Enabled xstate features 0x7, context size is 832 bytes, using 'standard' format.
Jan 21 12:58:05 walrus-edge kernel: x86/fpu: Using 'eager' FPU context switches.
Jan 21 12:58:05 walrus-edge kernel: e820: BIOS-provided physical RAM map:
Jan 21 12:58:05 walrus-edge kernel: BIOS-e820: [mem 0x-0x00057fff] usable
Jan 21 12:58:05 walrus-edge kernel: BIOS-e820: [mem 0x00058000-0x00058fff] reserved
Jan 21 12:58:05 walrus-edge kernel: BIOS-e820: [mem 0x00059000-0x0009bfff] usable
Jan 21 12:58:05 walrus-edge kernel: BIOS-e820: [mem 0x0009c000-0x0009cfff] reserved
Jan 21 12:58:05 walrus-edge kernel: BIOS-e820: [mem 0x0009d000-0x0009dfff] usable
Jan 21 12:58:05 walrus-edge kernel: BIOS-e820: [mem 0x0009e000-0x000b] reserved
Jan 21 12:58:05 walrus-edge kernel: BIOS-e820: [mem 0x0010-0xb1760fff] usable
Jan 21 12:58:05 walrus-edge kernel: BIOS-e820: [mem 0xb1761000-0xb1962fff] reserved
Jan 21 12:58:05 walrus-edge kernel: BIOS-e820: [mem 0xb1963000-0xbbe99fff] usable
Jan 21 12:58:05 walrus-edge kernel: BIOS-e820: [mem 0xbbe9a000-0xbc099fff] type 20
Jan 21 12:58:05 walrus-edge kernel: BIOS-e820: [mem 0xbc09a000-0xbcbbafff] reserved
Jan 21 12:58:05 walrus-edge kernel: BIOS-e820: [mem 0xbcbbb000-0xbcc0afff] ACPI NVS
Jan 21 12:58:05 walrus-edge kernel: BIOS-e820: [mem 0xbcc0b000-0xbcc73fff] reserved
Jan 21 12:58:05 walrus-edge kernel: BIOS-e820: [mem 0xbcc74000-0xbce7efff] ACPI NVS
Jan 21 12:58:05 walrus-edge kernel: BIOS-e820: [mem 0xbce7f000-0xbcefefff] ACPI data
Jan 21 12:58:05 walrus-edge kernel: BIOS-e820: [mem 0xbceff000-0xbcef] usable
Jan 21 12:58:05 walrus-edge kernel: BIOS-e820: [mem 0xbcf0-0xbf9f] reserved
Jan 21 12:58:05 walrus-edge kernel: BIOS-e820: [mem 0xf80f8000-0xf80f8fff] reserved
Jan 21 12:58:05 walrus-edge kernel: BIOS-e820: [mem 0xfed1c000-0xfed1] reserved
Jan 21 12:58:05 walrus-edge kernel: BIOS-e820: [mem 0x0001-0x00023e5f] usable
Jan 21 12:58:05 walrus-edge kernel: NX (Execute Disable) protection: active
Jan 21 12:58:05 walrus-edge kernel: efi: EFI v2.31 by Lenovo
Jan 21 12:58:05 walrus-edge kernel: efi:  ACPI=0xbcefe000  ACPI 2.0=0xbcefe014  SMBIOS=0xbcc73000  ESRT=0xbc1c8000 
Jan 21 12:58:05 walrus-edge kernel: efi: [Firmware Bug]: Invalid EFI memory map entries:
Jan 21 12:58:05 walrus-edge kernel: efi: mem40: [Reserved   |   |  |  |  |  |  |  |   |  |  |  |  ] range=[0x-0x] (invalid)
Jan 21 12:58:05 walrus-edge kernel: efi: mem41: [Reserved   |   |  |  |  |  |  |  |   |  |  |  |  ] 

Bug#841007: linux-image-4.8.0-rc8-amd64-unsigned: Shutdown when pressing any key on Asus E200 HA

[Jose M Calhariz]

Is to tell that the new 4.9-rc works.  Now I can login into the
machine.  During the weekend I will do a longer review of the kernel in
search of regressions. 

Thank you.

Kind regards
Jose M Calhariz

On 16/11/16 17:01, Santiago Vila wrote:
> forcemerge 833016 841007
> thanks
>
> Hi.
>
> You will see that both bugs belong to the "src:linux" package,
> so it's better not to file duplicates. To tell the BTS that
> a certain version has the bug, we have a "found" command.
>
> I'm merging the bugs with this message.
>
> BTW: There is a 4.9-rc version in experimental, you might want to give
> it a try and say here if there is any improvement.
>
> Thanks.





signature.asc
Description: OpenPGP digital signature

Bug#837907: stat() hangs on a particular file

[Yuriy M. Kaminskiy]

Sergio Gelato  writes:


Package: linux-image-3.16.0-4-amd64
Version: 3.16.36-1+deb8u1

One of our systems is suddenly unable to stat() a particular file
(cookies.sqlite-wal in a user's Firefox profile). Any attempt to

   ^^

do so hangs in the system call, as shown by strace. The file resides
on an NFSv4 share (sec=krb5p). Other files in the same directory on
the same share remain accessible. The affected file is normally accessible
on the NFS server and from other NFS clients running the same kernel.


(This does not invalidate this bug report [looks like genuine kernel {or 
hardware} issue]), but sqlite3 does NOT support placing databases on any 
networked filesystem (NFS, samba/cifs, etc); this may easily result in 
database corruption or other locking issues (inconsistent data reported 
by concurrent database connections); and as WAL mode uses mmap, it can 
be even more problematic on NFS.


So, it is very bad idea to place firefox/thunderbird profile 
directories on NFS.


See
https://www.sqlite.org/howtocorrupt.html#_filesystems_with_broken_or_missing_lock_implementations

(but, again, this is *user-level* issue [non-working locks can result in 
database corruption], and your bug is about *kernel-level* issue [hangs 
on stat(), which is not supposed to be possible to trigger by any 
user-level craziness]).



The user has reported a similar incident yesterday on some directories
on a different NFS share (also sec=krb5p, but hosted on a different
server). He rebooted to clear up the problem.

Bug#841007: linux-image-4.8.0-rc8-amd64-unsigned: Shutdown when pressing any key on Asus E200 HA

[Jose M Calhariz]

On 24/10/16 03:30, Ben Hutchings wrote:
> On Sun, 2016-10-16 at 21:22 +0100, Jose M Calhariz wrote:
>> Package: src:linux
>> Version: 4.8~rc8-1~exp1
>> Severity: important
>>
>> Dear Maintainer,
>>
>>* What led up to the situation?
>>
>> Using a very recent Debian kernel 4.7 or 4.8.  The vanilla 4.7.0 from
>> kernel.org works.  I simply boot the laptop.  When the X11 is up and
>> ready to input the user name, if I press any key it will shutdown.
> [...]
>
> Is that a clean shutdown (services stopped, filesystems unmounted) or a
> dirty shutdown (shuts off almost immediately, fsck reports an error on
> the next boot)?
>
> What happens if you press a key earlier than that?
>
> Ben.
>
Yes, it seams to be a clean shutdown.  User programs killed, services
shutdown, nothing logged.


If I press a key earlier, it is just ignored, as expected.


Kind regards

Jose M Calhariz





signature.asc
Description: OpenPGP digital signature

Bug#841007: linux-image-4.8.0-rc8-amd64-unsigned: Shutdown when pressing any key on Asus E200 HA

[Jose M Calhariz]

Package: src:linux
Version: 4.8~rc8-1~exp1
Severity: important

Dear Maintainer,

   * What led up to the situation?

Using a very recent Debian kernel 4.7 or 4.8.  The vanilla 4.7.0 from
kernel.org works.  I simply boot the laptop.  When the X11 is up and
ready to input the user name, if I press any key it will shutdown.  I
found no message in /var/log/kernel.log that explains the problem.


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

For reporting this bug I am connecting by SSH to the laptop over a
USB/Ethernet adaptor. 

What measures can I do to gather more debugging information?

Kind regards
Jose M Calhariz



-- Package-specific info:
** Version:
Linux version 4.8.0-rc8-amd64 (debian-kernel@lists.debian.org) (gcc
version 5.4.1 20160904 (Debian 5.4.1-2) ) #1 SMP Debian 4.8~rc8-1~exp1
(2016-09-26)

** Command line:
BOOT_IMAGE=/boot/vmlinuz-4.8.0-rc8-amd64
root=UUID=577ff77a-2aa2-4c43-9c83-91e107b674c2 ro printk.time=n
initcall_debug no_console_suspend

** Tainted: E (8192)
 * Unsigned module has been loaded.

** Kernel log:
[6.100201] initcall init_fat_fs+0x0/0xfd0 [fat] returned 0 after
46151 usecs
[6.100962] initcall ghash_pclmulqdqni_mod_init+0x0/0x1000
[ghash_clmulni_intel] returned 0 after 17143 usecs
[6.102575] calling  init_vfat_fs+0x0/0x1000 [vfat] @ 303
[6.102588] initcall init_vfat_fs+0x0/0x1000 [vfat] returned 0 after
5 usecs
[6.104151] calling  crc32_pclmul_mod_init+0x0/0x1000 [crc32_pclmul]
@ 257
[6.107983] initcall crc32_pclmul_mod_init+0x0/0x1000 [crc32_pclmul]
returned 0 after 3726 usecs
[6.111215] calling  crct10dif_intel_mod_init+0x0/0x1000
[crct10dif_pclmul] @ 267
[6.124523] calling  init_nls_cp437+0x0/0x1000 [nls_cp437] @ 316
[6.124531] initcall init_nls_cp437+0x0/0x1000 [nls_cp437] returned 0
after 0 usecs
[6.135566] initcall crct10dif_intel_mod_init+0x0/0x1000
[crct10dif_pclmul] returned 0 after 23765 usecs
[6.137107] calling  evdev_init+0x0/0x1000 [evdev] @ 261
[6.139222] initcall evdev_init+0x0/0x1000 [evdev] returned 0 after
2050 usecs
[6.143220] calling  init_nls_ascii+0x0/0x1000 [nls_ascii] @ 320
[6.143228] initcall init_nls_ascii+0x0/0x1000 [nls_ascii] returned 0
after 0 usecs
[6.171881] calling  vmx_init+0x0/0x435 [kvm_intel] @ 266
[6.179360] calling  asus_wmi_init+0x0/0x1000 [asus_wmi] @ 260
[6.179367] asus_wmi: ASUS WMI generic driver loaded
[6.179386] initcall asus_wmi_init+0x0/0x1000 [asus_wmi] returned 0
after 16 usecs
[6.181794] calling  asus_nb_wmi_init+0x0/0x1000 [asus_nb_wmi] @ 260
[6.182142] asus_wmi: Initialization: 0x1
[6.182258] asus_wmi: BIOS WMI version: 7.9
[6.182352] asus_wmi: SFUN value: 0x37
[6.185752] input: Asus WMI hotkeys as
/devices/platform/asus-nb-wmi/input/input8
[6.201743] asus_wmi: Number of fans: 1
[6.208232] ath10k_pci :01:00.0: firmware: failed to load
ath10k/pre-cal-pci-:01:00.0.bin (-2)
[6.208254] ath10k_pci :01:00.0: Direct firmware load for
ath10k/pre-cal-pci-:01:00.0.bin failed with error -2
[6.208297] ath10k_pci :01:00.0: firmware: failed to load
ath10k/cal-pci-:01:00.0.bin (-2)
[6.208311] ath10k_pci :01:00.0: Direct firmware load for
ath10k/cal-pci-:01:00.0.bin failed with error -2
[6.211045] initcall asus_nb_wmi_init+0x0/0x1000 [asus_nb_wmi]
returned 0 after 28549 usecs
[6.220335] ath10k_pci :01:00.0: firmware: direct-loading
firmware ath10k/QCA9377/hw1.0/firmware-5.bin
[6.220374] ath10k_pci :01:00.0: qca9377 hw1.0 target 0x0502
chip_id 0x003820ff sub 1a3b:2b31
[6.220388] ath10k_pci :01:00.0: kconfig debug 0 debugfs 0
tracing 0 dfs 0 testmode 0
[6.221359] ath10k_pci :01:00.0: firmware ver WLAN.TF.1.0-00267-1
api 5 features ignore-otp crc32 79cea2c7
[6.223919] calling  iTCO_vendor_init_module+0x0/0x1000
[iTCO_vendor_support] @ 271
[6.223923] iTCO_vendor_support: vendor-support=0
[6.223940] initcall iTCO_vendor_init_module+0x0/0x1000
[iTCO_vendor_support] returned 0 after 12 usecs
[6.225084] calling  iTCO_wdt_init_module+0x0/0x1000 [iTCO_wdt] @ 271
[6.225086] iTCO_wdt: Intel TCO WatchDog Timer Driver v1.11
[6.225220] iTCO_wdt: Found a Braswell SoC TCO device (Version=3,
TCOBASE=0x0460)
[6.225553] iTCO_wdt: initialized. heartbeat=30 sec (nowayout=0)
[6.225610] initcall iTCO_wdt_init_module+0x0/0x1000 [iTCO_wdt]
returned 0 after 504 usecs
[6.251830] initcall vmx_init+0x0/0x435 [kvm_intel] returned 0 after
78051 usecs
[6.254285] calling  coretemp_init+0x0/0x1000 [coretemp] @ 257
[6.254616] initcall coretemp_init+0x0/0x1000 [coretemp] returned 0
after 314 usecs
[6.256501] calling  powerclamp_init+0x0/0x1000 [intel_powerclamp] @ 267
[6.256619] initcall powerclamp_init+0x0/0x1000 [intel_powerclamp]
returned 0 after 105 usecs
[6.257469] calling  acpi_cpufreq_init+0x0/0x1000 [acpi_cpufreq] @ 257
[6.257479] initcall acpi_cpufreq_init+0x0/0x1000 [acpi_cpufreq

Bug#833009: linux-image-4.6.0-1-amd64: Hibernation does not work on Asus E200HA because of i915 and i2c_designware

[Jose M Calhariz]

Hi,

I have tried the vanilla kernel 4.7.  Now the hibernation almost works. 
When I select hibernation after some minutes I need to turn off the
laptop.  But when I turn on it awakes and return to the previous state. 
I still see the same error messages, but this time the keyboard works.

Kind regards
Jose M Calhariz




signature.asc
Description: OpenPGP digital signature

Bug#833016: linux-image-4.7.0-rc7-amd64-unsigned: Shutdown when pressed any key of the keyboard

[Jose M Calhariz]

Hi,

I have just tried a vanilla kernel 4.7 and it just works.

Kind regards
Jose M Calhariz




signature.asc
Description: OpenPGP digital signature

Bug#833016: linux-image-4.7.0-rc7-amd64-unsigned: Shutdown when pressed any key of the keyboard

[Jose M Calhariz]

Package: src:linux
Version: 4.7~rc7-1~exp1
Severity: important
Tags: upstream

Being affected by #833009 I decided to try a kernel from experimental.
Both of the kernels for amd64, the unsigned and the other, cause a
orderly shutodwn when I press any key of the keyboard.

I have no clue why this happens, but being a regression, I decided to
report.

Kind regards
Jose M Calhariz


-- Package-specific info:
** Kernel log: boot messages should be attached

** Model information
sys_vendor: ASUSTeK COMPUTER INC.
product_name: E200HA
product_version: 1.0   
chassis_vendor: ASUSTeK COMPUTER INC.
chassis_version: 1.0   
bios_vendor: American Megatrends Inc.
bios_version: E200HA.210
board_vendor: ASUSTeK COMPUTER INC.
board_name: E200HA
board_version: 1.0   

** Network interface configuration:
# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).

source /etc/network/interfaces.d/*

# The loopback network interface
auto lo
iface lo inet loopback

** PCI devices:
00:00.0 Host bridge [0600]: Intel Corporation Braswell SoC Transaction Router 
[8086:2280] (rev 22)
Subsystem: ASUSTeK Computer Inc. Braswell SoC Transaction Router 
[1043:10b0]
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- SERR- 
Kernel driver in use: i915
Kernel modules: i915

00:0b.0 Signal processing controller [1180]: Intel Corporation Braswell P-Unit 
Power Management [8086:22dc] (rev 22)
Subsystem: ASUSTeK Computer Inc. Braswell P-Unit Power Management 
[1043:10b0]
Control: I/O- Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 
Kernel driver in use: proc_thermal
Kernel modules: processor_thermal_device

00:14.0 USB controller [0c03]: Intel Corporation Braswell USB xHCI Host 
Controller [8086:22b5] (rev 22) (prog-if 30 [XHCI])
Subsystem: ASUSTeK Computer Inc. Braswell USB xHCI Host Controller 
[1043:10b0]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- 
SERR- 
Kernel driver in use: xhci_hcd
Kernel modules: xhci_pci

00:1a.0 Encryption controller [1080]: Intel Corporation Braswell Trusted 
Execution Engine Interface [8086:2298] (rev 22)
Subsystem: ASUSTeK Computer Inc. Braswell Trusted Execution Engine 
Interface [1043:10b0]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR+ FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 

00:1c.0 PCI bridge [0604]: Intel Corporation Braswell PCIe Port 1 [8086:22c8] 
(rev 22) (prog-if 00 [Normal decode])
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- Reset- FastB2B-
PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
Capabilities: 
Kernel driver in use: pcieport
Kernel modules: shpchp

00:1f.0 ISA bridge [0601]: Intel Corporation Braswell Platform Controller Unit 
LPC [8086:229c] (rev 22)
Subsystem: ASUSTeK Computer Inc. Braswell Platform Controller Unit LPC 
[1043:10b0]
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- 
SERR- 
Kernel driver in use: lpc_ich
Kernel modules: lpc_ich

01:00.0 Network controller [0280]: Qualcomm Atheros QCA9377 802.11ac Wireless 
Network Adapter [168c:0042] (rev 30)
Subsystem: AzureWave QCA9377 802.11ac Wireless Network Adapter 
[1a3b:2b31]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 
Kernel driver in use: ath10k_pci
Kernel modules: ath10k_pci


** USB devices:
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 004: ID 0b95:7720 ASIX Electronics Corp. AX88772
Bus 001 Device 003: ID 13d3:3496 IMC Networks 
Bus 001 Device 002: ID 0bda:57ed Realtek Semiconductor Corp. 
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub


-- System Information:
Debian Release: stretch/sid
  APT prefers testing
  APT policy: (500, 'testing'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 4.6.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=C, LC_CTYPE=C (charmap=locale: Cannot set LC_CTYPE to default 
locale: No such file or directory
locale: Cannot set LC_MESSA

Bug#833009: linux-image-4.6.0-1-amd64: Hibernation does not work on Asus E200HA because of i915 and i2c_designware

[Jose M Calhariz]

Package: src:linux
Version: 4.6.4-1
Severity: normal
Tags: upstream

I have problems that I can not suspend or hibernate my E200HA.  After
some reserach I found this Web page:
https://01.org/blogs/rzhang/2015/best-practice-debug-linux-suspend/hibernate-issues

Maybe the suspend is not supported, but the hibernate should, because
of this message on kern.log:

Jul 28 22:56:00 lal kernel: [0.472724] ACPI: (supports S0 S4 S5)

So, doing some extra research I suspect the problem is in the module
i915 and on the module i2c_designware.  Because switching to a text
console and issuing the command: "echo disk > /sys/power/state" the
system hibernate and awakes when I request.  But it awakes without
keyboard and with following messages on the console:

[   50.827873] [drm] stuck on blitter ring
[   50.834932] [drm] stuck on bsd ring
[   50.841830] [drm] stuck on video enhancement ring
[   50.851177] [drm] GPU HANG: ecode 8:0:0x7a2af415, reason: Ring hung, action: 
reset
[   50.854730] [drm] GPU hangs can indicate a bug anywhere in the entire gfx 
stack, including userspace.
[   50.858380] [drm] Please file a _new_ bug report on bugs.freedesktop.org 
against DRI -> DRM/Intel
[   50.860886] [drm] drm/i915 developers can then reassign to the right 
component if it's not a kernel issue.
[   50.863336] [drm] The gpu crash dump is required to analyze gpu hangs, so 
please always attach it.
[   50.865839] [drm] GPU crash dump saved to /sys/class/drm/card0/error
[   50.868532] [drm:i915_set_reset_status [i915]] *ERROR* gpu hanging too fast, 
banning!
[   50.873485] drm/i915: Resetting chip after gpu hang
[   51.729188] IPv6: ADDRCONF(NETDEV_CHANGE): enx0019fd4cb596: link becomes 
ready
[   51.737806] asix 1-4:1.0 enx0019fd4cb596: link up, 100Mbps, full-duplex, lpa 
0xCDE1
[  129.340496] i2c_designware 808622C1:00: timeout in enabling adapter
[  130.348085] i2c_designware 808622C1:00: controller timed out
[  130.355959] i2c_designware 808622C1:00: Unknown Synopsys component type: 
0x

Kind regards
Jose M Calhariz


-- Package-specific info:
** Version:
Linux version 4.6.0-1-amd64 (debian-kernel@lists.debian.org) (gcc version 5.4.0 
20160609 (Debian 5.4.0-6) ) #1 SMP Debian 4.6.4-1 (2016-07-18)

** Command line:
BOOT_IMAGE=/boot/vmlinuz-4.6.0-1-amd64 
root=UUID=577ff77a-2aa2-4c43-9c83-91e107b674c2 ro printk.time=n initcall_debug 
no_console_suspend

** Tainted: E (8192)
 * Unsigned module has been loaded (currently expected).

** Kernel log:
[   49.008511] call regulatory.0+ returned 0 after 0 usecs
[   49.010919] calling  intel_backlight+ @ 2728, parent: card0-eDP-1
[   49.013223] call intel_backlight+ returned 0 after 0 usecs
[   49.015521] calling  input6+ @ 2728, parent: LNXVIDEO:00
[   49.017797] call input6+ returned 0 after 0 usecs
[   49.020078] calling  input7+ @ 2728, parent: pcspkr
[   49.021968] call input7+ returned 0 after 17 usecs
[   49.023843] calling  input8+ @ 2728, parent: i2c-ELAN0100:00
[   49.025720] call input8+ returned 0 after 0 usecs
[   49.027601] calling  coretemp.0+ @ 2728, parent: platform
[   49.029487] call coretemp.0+ returned 0 after 0 usecs
[   49.031392] calling  asus-nb-wmi+ @ 2728, parent: platform
[   49.033284] call asus-nb-wmi+ returned 0 after 1 usecs
[   49.035181] calling  input9+ @ 2728, parent: asus-nb-wmi
[   49.037073] call input9+ returned 0 after 0 usecs
[   49.038960] calling  input10+ @ 2728, parent: 0018:0B05:8585.0001
[   49.040893] call input10+ returned 0 after 19 usecs
[   49.042822] calling  input10::numlock+ @ 2728, parent: input10
[   49.044753] call input10::numlock+ returned 0 after 0 usecs
[   49.046684] calling  input10::capslock+ @ 2728, parent: input10
[   49.048625] call input10::capslock+ returned 0 after 0 usecs
[   49.050570] calling  input10::scrolllock+ @ 2728, parent: input10
[   49.052528] call input10::scrolllock+ returned 0 after 0 usecs
[   49.054491] calling  input10::compose+ @ 2728, parent: input10
[   49.056460] call input10::compose+ returned 0 after 0 usecs
[   49.058429] calling  input10::kana+ @ 2728, parent: input10
[   49.060402] call input10::kana+ returned 0 after 0 usecs
[   49.062379] calling  rfkill1+ @ 2728, parent: phy0
[   49.064358] call rfkill1+ returned 0 after 10 usecs
[   49.066337] PM: restore of devices complete after 4600.592 msecs
[   49.068386] usb 1-4:1.0: rebind failed: -517
[   49.070372] usb 1-3:1.0: rebind failed: -517
[   49.072323] usb 1-3:1.1: rebind failed: -517
[   49.074671] PM: Image restored successfully.
[   49.074693] PM: Basic memory bitmaps freed
[   49.074699] Restarting tasks ... done.
[   49.089295] pci_bus :01: Allocating resources
[   49.089491] pcieport :00:1c.0: bridge window [io  0x1000-0x0fff] to [bus 
01] add_size 1000
[   49.089498] pcieport :00:1c.0: bridge window [mem 0x0010-0x000f 
64bit pref] to [bus 01] add_size 20 add_align 10
[   49.089509] pcieport :00:1c.0: res[15]=[mem 0x0010-0x000f 64bit 
pref] res_to_dev_res

Bug#832925: firmware-atheros: Please add the firmware for the wireless QCA9377 from atheros

[Jose M Calhariz]

Package: firmware-atheros
Version: 20160110-1
Severity: normal

I have a new laptop Asus E200HA.  I was able to use the stretch DVD to install 
Debian.
I found that this package is missing the firmware for the QCA9377.  The 
firmware can be 
download from "git clone 
https://github.com/ajaybhatia/Qualcomm-Atheros-QCA9377-Wifi-Linux;
It contains too a driver, but that is not needed on kernel 4.6.  The install.sh 
script 
is not good for Debian too.

lspci 
00:00.0 Host bridge: Intel Corporation Braswell SoC Transaction Router (rev 22)
00:02.0 VGA compatible controller: Intel Corporation Braswell PCI Configuration 
Registers (rev 22)
00:0b.0 Signal processing controller: Intel Corporation Braswell P-Unit Power 
Management (rev 22)
00:14.0 USB controller: Intel Corporation Braswell USB xHCI Host Controller 
(rev 22)
00:1a.0 Encryption controller: Intel Corporation Braswell Trusted Execution 
Engine Interface (rev 22)
00:1c.0 PCI bridge: Intel Corporation Braswell PCIe Port 1 (rev 22)
00:1f.0 ISA bridge: Intel Corporation Braswell Platform Controller Unit LPC 
(rev 22)
01:00.0 Network controller: Qualcomm Atheros QCA9377 802.11ac Wireless Network 
Adapter (rev 30)


Kind regards
Jose M Calhariz

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

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

firmware-atheros depends on no packages.

firmware-atheros recommends no packages.

Versions of packages firmware-atheros suggests:
ii  initramfs-tools  0.125

-- no debconf information

Bug#832458: linux-image-4.6.0-0.bpo.1-amd64: Please enable SND_SOC_INTEL_BYT_MAX98090_MACH, needed for some Baytrail devices

[Ivan M]

Package: src:linux
Version: 4.6.3-1~bpo8+1
Severity: normal

Dear Maintainer,

Please enable CONFIG_SND_SOC_INTEL_BYT_MAX98090_MACH=m - it is necessary for 
audio on certain Baytrail hardware.

(I note that it is also necessary to set CONFIG_DW_DMAC=y (not m) for this, 
although I don't understand why.)

Thank you,

Ivan


-- Package-specific info:
** Version:
Linux version 4.6.0-0.bpo.1-amd64 (debian-kernel@lists.debian.org) (gcc version 
4.9.2 (Debian 4.9.2-10) ) #1 SMP Debian 4.6.3-1~bpo8+1 (2016-07-13)

[ omitting irrelevant info, although I think the following line from dmesg is 
relevant: ]

intel_sst_acpi 80860F28:00: No matching machine driver found

Bug#814320: linux-image-4.3.0-1-amd64: Slab leak

[Josep M. Perez]

On 10/02/16 16:51, Ben Hutchings wrote:

Control: severity -1 important
Control: tag -1 patch

On Wed, 2016-02-10 at 11:20 +0100, Josep M. Perez wrote:

Package: src:linux
Version: 4.3.5-1
Severity: grave
Justification: renders package unusable

No it doesn't.


Dear Maintainer,

The current kernel is having an apparent memory leak on my computer. Over time
it consumes all memory.

[...]

The computer has 8 GB of memory. Previously I was able to run a virtualbox
instance of 32-bits Windows 7 with 2GB of memory with no issue. Now whenever I
do so the system slows down to a crawl and ultimately ends up killing the
virtual box processes.

[...]

Does this only happen when you run VirtualBox?
It always happens regardless of whether I am using VirtualBox. Since VB 
uses a lot of memory, it makes the problem much more visible. But if I 
do not run it at all, the kernel will eventually oops.


Cheers,
Josep M. Perez




Ben.




WARNING / LEGAL TEXT: This message is intended only for the use of the
individual or entity to which it is addressed and may contain
information which is privileged, confidential, proprietary, or exempt
from disclosure under applicable law. If you are not the intended
recipient or the person responsible for delivering the message to the
intended recipient, you are strictly prohibited from disclosing,
distributing, copying, or in any way using this message. If you have
received this communication in error, please notify the sender and
destroy and delete any copies you may have received.

http://www.bsc.es/disclaimer

Bug#814320: linux-image-4.3.0-1-amd64: Slab leak

[Josep M. Perez]

Package: src:linux
Version: 4.3.5-1
Severity: grave
Justification: renders package unusable

Dear Maintainer,

The current kernel is having an apparent memory leak on my computer. Over time
it consumes all memory. The output of slabtop -s c after having the system on
for 24h is is the following:

 Active / Total Objects (% used): 2083098 / 2188414 (95.2%)
 Active / Total Slabs (% used)  : 125633 / 125653 (100.0%)
 Active / Total Caches (% used) : 75 / 115 (65.2%)
 Active / Total Size (% used)   : 495649.02K / 507685.21K (97.6%)
 Minimum / Average / Maximum Object : 0.02K / 0.23K / 4096.00K

  OBJS ACTIVE  USE OBJ SIZE  SLABS OBJ/SLAB CACHE SIZE NAME
1552320 1551740  99%0.25K  97020   16388080K kmalloc-256
 16312  15522  95%1.00K   40784 16312K ext4_inode_cache
 25473  25451  99%0.56K   36397 14556K radix_tree_node
 71652  69487  96%0.19K   3412   21 13648K kmalloc-192
 51387  40537  78%0.19K   2447   21  9788K dentry
 92859  53038  57%0.10K   2381   39  9524K buffer_head
 14609  13272  90%0.55K   20877  8348K inode_cache
161076 128018  79%0.03K   1299  124  5196K kmalloc-32
 78939  73252  92%0.06K   1253   63  5012K kmalloc-64
  4296   4133  96%1.00K   10744  4296K kmalloc-1024
  1060   1009  95%3.31K5302  4240K task_struct
 34089  32793  96%0.12K   1033   33  4132K kernfs_node_cache
  4278   3768  88%0.60K7136  2852K proc_inode_cache
36 36 100%   64.00K 361  2304K kmalloc-65536
   283283 100%8.00K2831  2264K kmalloc-8192
  4248   3997  94%0.50K5318  2124K kmalloc-512
   497490  98%4.00K4971  1988K kmalloc-4096
  2898   2677  92%0.63K4836  1932K shmem_inode_cache
 24920  23282  93%0.07K445   56  1780K anon_vma
   848798  94%2.00K4242  1696K kmalloc-2048
   570556  97%2.05K1903  1520K idr_layer_cache
  1320   1218  92%0.94K3304  1320K mm_struct
   375333  88%2.06K1253  1000K sighand_cache
  1446   1339  92%0.62K2416   964K sock_inode_cache
  6603   4666  70%0.12K213   31   852K kmalloc-node
 1  1 100%  512.00K  11   512K kmalloc-524288
30 30 100%   16.00K 301   480K kmalloc-16384
 11682  11529  98%0.04K118   99   472K ext4_extent_status
   399333  83%1.12K 577   456K signal_cache
  2464   2464 100%0.14K 88   28   352K ext4_groupinfo_4k


The computer has 8 GB of memory. Previously I was able to run a virtualbox
instance of 32-bits Windows 7 with 2GB of memory with no issue. Now whenever I
do so the system slows down to a crawl and ultimately ends up killing the
virtual box processes.



-- Package-specific info:
** Version:
Linux version 4.3.0-1-amd64 (debian-kernel@lists.debian.org) (gcc version 5.3.1 
20160121 (Debian 5.3.1-7) ) #1 SMP Debian 4.3.5-1 (2016-02-06)

** Command line:
BOOT_IMAGE=/boot/vmlinuz-4.3.0-1-amd64 
root=UUID=ccf515b5-e8b8-4536-a473-41b478488cf9 ro

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

** Kernel log:
[85266.116807] ata5: limiting SATA link speed to 1.5 Gbps
[85266.116814] ata5: hard resetting link
[85266.844945] ata5: SATA link down (SStatus 0 SControl 310)
[85266.844970] ata5: EH complete
[85276.960063] ata5: exception Emask 0x10 SAct 0x0 SErr 0x404 action 0xe 
frozen
[85276.960075] ata5: irq_stat 0x0040, connection status changed
[85276.960080] ata5: SError: { CommWake DevExch }
[85276.960092] ata5: limiting SATA link speed to 1.5 Gbps
[85276.960098] ata5: hard resetting link
[85277.682443] ata5: SATA link down (SStatus 0 SControl 310)
[85277.682468] ata5: EH complete
[85278.961885] ata5: exception Emask 0x10 SAct 0x0 SErr 0x400 action 0xe 
frozen
[85278.961897] ata5: irq_stat 0x0040, connection status changed
[85278.961902] ata5: SError: { DevExch }
[85278.961913] ata5: limiting SATA link speed to 1.5 Gbps
[85278.961919] ata5: hard resetting link
[85279.684200] ata5: SATA link down (SStatus 0 SControl 310)
[85279.684225] ata5: EH complete
[85284.973345] ata5: exception Emask 0x10 SAct 0x0 SErr 0x400 action 0xe 
frozen
[85284.973357] ata5: irq_stat 0x0040, connection status changed
[85284.973362] ata5: SError: { DevExch }
[85284.973373] ata5: limiting SATA link speed to 1.5 Gbps
[85284.973379] ata5: hard resetting link
[85285.697443] ata5: SATA link down (SStatus 0 SControl 310)
[85285.697467] ata5: EH complete
[85294.976031] ata5: exception Emask 0x10 SAct 0x0 SErr 0x400 action 0xe 
frozen
[85294.976042] ata5: irq_stat 0x0040, connection status changed
[85294.976048] ata5: SError: { DevExch }
[85294.976059] ata5: limiting SATA link speed to 1.5 Gbps
[85294.976066] ata5: 

Bug#793185: [linux-sunxi] Re: forwarding a bug: cpufreq missing in debian stable on a cuibeboard

[m . silentcreek]

Am Freitag, 24. Juli 2015 14:49:42 UTC+2 schrieb Thomas Kaiser:
 Ah, now I think I understand. You're talking about these lines here?
 
 
     
 https://github.com/RobertCNelson/u-boot/blob/master/arch/arm/dts/sun7i-a20-cubietruck.dts#L244-L269

Yes. 
 
 So while using CONFIG_REGULATOR_AXP20X=y will bring working cpufreq support 
 to the cubietruck, shouldn't adding these lines to the device trees of the 
 other 5 A20 devices enable CPU voltage scaling there?

Basically yes. The point that Chen-Yu made is that he and other developers 
don't have all boards available to verify that all of these boards use the same 
layout for their wiring. Therefore they just leave these bits out. I'm actually 
working on a small patch to add these regulator bits to the BananaPi and 
possibly BananaPro dts files. I will post it soon, when I gathered enough 
information to ensure everything works fine. But anyway, we're getting offtopic 
here. So let's postpone this discussion until then.

Cheers,

Timo

Bug#793185: [linux-sunxi] Re: forwarding a bug: cpufreq missing in debian stable on a cuibeboard

[m . silentcreek]

Am Freitag, 24. Juli 2015 14:12:57 UTC+2 schrieb Thomas Kaiser:
 Maxime Ripard wrote:
    What puzzles me is that exactly the same kernel (I used Igor Pečovnik's 
 
   build system) provides working cpufreq support on 5 A20 devices and one 
   it 
 
   fails. 
 
  And none of those 5 use CPU voltage scaling.
 
 Maybe I don't understand the whole meaning. But on a Banana Pi a few weeks 
 ago [1] and on a pcDuino3 Nano I used the last days for USB/UAS benchmarks 
 the cpufreq stuff was available below /sys/devices/system/cpu/cpu0/cpufreq/ 
 and altering parameters always had an effect. But I will follow your advise, 
 double check and report back.

I think what Maxime was trying to say is, that while all of your boards support 
Cpufreq, only the Cubietruck supports voltage scaling because only Cubietruck 
has the power regulator nodes defined in it's dts file (just have a look at the 
last lines of the Cubitruck dts file and compare that to the dts file, let's 
say, for Bananapi). On the other boards, the frequency is scaled, but the 
voltage always stays at 1.4V as set in U-Boot (that means the voltages in the 
cpufreq operating points are not used on these boards). At least that's what I 
understand after a recent email axchange with Chen-Yu Tsai. 

Cheers,

Timo

Bug#755822: Info received ([SOLVED] modifying snd-hda-intel parameters)

[Antonio-M. Corbi Bellot]

Hi again!

It seems that my solution was not complete, I also have to add the
parameter 'model=vaio' to the module options line, so the correct one
for me in /etc/modprobe.d/alsa-base.conf is this:

options snd-hda-intel model=vaio position_fix=1

Once again, hope this helps someone in the same situation as me.

A. Corbi


-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/20150528171103.2d2f2...@hal9000.dlsi.ua.es

Bug#755822: [SOLVED] modifying snd-hda-intel parameters

[Antonio-M. Corbi Bellot]

Hi,

After submiting this bug back in july'14 and no receiving any answers I
decided to play with module snd-hda-intel parameters.

In my case it seems that:

options snd-hda-intel position_fix=1

written in /etc/modprobe.d/alsa-base.conf  does the trick. 

Currently I'm running a 4.0.4 kernel, but as I've been experimenting
sound problems in this netbook with kernels as old as 3.8.x and up-to
4.0.4 I assume this trick is also valid for all of them.

Hope this helps someone in a situation similiar to this.

A. Corbi


-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/20150521211346.52a52...@vaio.home

Bug#785564: initramfs-tools: Boot fails do to missing switch_root

[Jose M Calhariz]

Package: initramfs-tools
Version: 0.120
Severity: normal

If busybox is not installed and the option is BUSYBOX=y the system
don't boot.  Where the previous initramfs-tools could generate a
bootable initrd image.



-- Package-specific info:
-- initramfs sizes
-rw-r--r-- 1 root root 3.0M Apr 26  2004 /boot/initrd.img-2.4.18-1-586tsc
-rw-r--r-- 1 root root 4.8M Jun 16  2006 /boot/initrd.img-2.6.16-1-486.bak
-rw-r--r-- 1 root root 4.8M Oct 30  2006 /boot/initrd.img-2.6.16-2-486.bak
-rw-r--r-- 1 root root 5.2M Apr  6  2007 /boot/initrd.img-2.6.16-2-686-smp.bak
-rw-r--r-- 1 root root 6.4M Mar  7  2010 /boot/initrd.img-2.6.18-6-486
-rw-r--r-- 1 root root 5.1M Jan 25  2010 /boot/initrd.img-2.6.18-6-486.bak
-rw-r--r-- 1 root root 7.4M May 16  2011 /boot/initrd.img-2.6.26-2-486
-rw-r--r-- 1 root root 7.4M Mar 15  2010 /boot/initrd.img-2.6.26-2-486.bak
-rw-r--r-- 1 root root 7.4M May 17  2011 /boot/initrd.img-2.6.26-2-686
-rw-r--r-- 1 root root 9.4M Jun  2  2013 /boot/initrd.img-2.6.32-5-486
-rw-r--r-- 1 root root 9.4M Jun  2  2013 /boot/initrd.img-2.6.32-5-686
-rw-r--r-- 1 root root 9.5M Jun  2  2013 /boot/initrd.img-2.6.32-5-amd64
-rw-r--r-- 1 root root 9.4M Jun  2  2013 /boot/initrd.img-2.6.32-5-openvz-686
-rw-r--r-- 1 root root 8.9M Jan 29  2012 /boot/initrd.img-2.6.32-bpo.5-686
-rw-r--r-- 1 root root 8.9M Oct 16  2011 /boot/initrd.img-2.6.32-bpo.5-686.bak
-rw-r--r-- 1 root root  13M Jan  1  2014 /boot/initrd.img-3.11-0.bpo.2-486
-rw-r--r-- 1 root root  13M Jan  1  2014 /boot/initrd.img-3.11-0.bpo.2-686-pae
-rw-r--r-- 1 root root  13M Jan  1  2014 
/boot/initrd.img-3.11-0.bpo.2-686-pae.bak
-rw-r--r-- 1 root root  13M Jan  1  2014 /boot/initrd.img-3.11-0.bpo.2-amd64
-rw-r--r-- 1 root root  14M Mar  2  2014 /boot/initrd.img-3.12-0.bpo.1-686-pae
-rw-r--r-- 1 root root  14M Mar  2  2014 /boot/initrd.img-3.12-0.bpo.1-amd64
-rw-r--r-- 1 root root  14M Aug  9  2014 /boot/initrd.img-3.13-0.bpo.1-amd64
-rw-r--r-- 1 root root  14M Jun 22  2014 /boot/initrd.img-3.13-0.bpo.1-amd64.bak
-rw-r--r-- 1 root root  15M Sep  7  2014 /boot/initrd.img-3.14-0.bpo.2-amd64
-rw-r--r-- 1 root root  15M Oct 11  2014 /boot/initrd.img-3.16-0.bpo.2-amd64
-rw-r--r-- 1 root root  15M Jan 24 19:29 /boot/initrd.img-3.16-0.bpo.3-amd64
-rw-r--r-- 1 root root  15M Nov 27 23:16 /boot/initrd.img-3.16-0.bpo.3-amd64.bak
-rw-r--r-- 1 root root  17M May 16 21:26 /boot/initrd.img-3.16.0-0.bpo.4-amd64
-rw-r--r-- 1 root root  16M May  3 17:20 
/boot/initrd.img-3.16.0-0.bpo.4-amd64.bak
-rw-r--r-- 1 root root  18M May 17 12:21 /boot/initrd.img-3.16.0-4-586
-rw-r--r-- 1 root root  18M May 17 12:22 /boot/initrd.img-3.16.0-4-686-pae
-rw-r--r-- 1 root root  17M May 17 20:32 /boot/initrd.img-3.16.0-4-amd64
-rw-r--r-- 1 root root  17M May 16 21:37 /boot/initrd.img-3.16.0-4-amd64.bak
-rw-r--r-- 1 root root  11M Sep 22  2012 /boot/initrd.img-3.2.0-0.bpo.3-amd64
-rw-r--r-- 1 root root  11M Sep 15  2012 
/boot/initrd.img-3.2.0-0.bpo.3-amd64.bak
-rw-r--r-- 1 root root  11M Sep 23  2012 /boot/initrd.img-3.2.0-3-486
-rw-r--r-- 1 root root  11M Oct 28  2012 /boot/initrd.img-3.2.0-3-686-pae
-rw-r--r-- 1 root root  11M Sep 23  2012 /boot/initrd.img-3.2.0-3-686-pae.bak
-rw-r--r-- 1 root root  11M Sep 22  2012 /boot/initrd.img-3.2.0-3-amd64
-rw-r--r-- 1 root root  13M May  3 17:21 /boot/initrd.img-3.2.0-4-486
-rw-r--r-- 1 root root  13M May  3 17:21 /boot/initrd.img-3.2.0-4-686-pae
-rw-r--r-- 1 root root  11M Dec 21  2013 /boot/initrd.img-3.2.0-4-686-pae.bak
-rw-r--r-- 1 root root  13M May  3 17:21 /boot/initrd.img-3.2.0-4-amd64
-- /proc/cmdline
BOOT_IMAGE=/boot/vmlinuz-3.16.0-4-amd64 root=/dev/sda2 ro printk.time=n 
hpet=force

-- resume
# RESUME=/dev/hda2
RESUME='UUID=3be4d10b:9bcd6eda:770c01a5:90fe33e3'
-- /proc/filesystems
btrfs
ext3
ext2
ext4
fuseblk
vfat
xfs

-- lsmod
Module  Size  Used by
cfg80211  405538  0 
bnep   17431  2 
cpufreq_stats  12782  0 
cpufreq_conservative14184  0 
cpufreq_userspace  12525  0 
bluetooth 374429  5 bnep
6lowpan_iphc   16588  1 bluetooth
rfkill 18867  3 cfg80211,bluetooth
cpufreq_powersave  12454  0 
sit25982  0 
tunnel412629  1 sit
ip_tunnel  21463  1 sit
binfmt_misc16949  1 
nfsd  263032  13 
auth_rpcgss51211  1 nfsd
oid_registry   12419  1 auth_rpcgss
nfs_acl12511  1 nfsd
nfs   188136  0 
lockd  83389  2 nfs,nfsd
fscache45542  1 nfs
sunrpc237402  19 nfs,nfsd,auth_rpcgss,lockd,nfs_acl
xt_multiport   12518  0 
xt_LOG 17171  1 
ipt_MASQUERADE 12594  1 
xt_tcpudp  12527  18 
nf_nat_tftp12422  0 
nft_nat12507  0 
nf_nat_proto_udplite12489  0 
nf_nat_proto_dccp  12480  0 
nf_nat_proto_sctp  12563  0 
nf_nat_amanda  12424  0 

Bug#777644: linux: UDF complains about inode size of file it just created

[brian m. carlson]

=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages linux-image-3.18.0-trunk-amd64 depends on:
ii  cdebconf [debconf-2.0]  0.192
ii  debconf [debconf-2.0]   1.5.55
ii  initramfs-tools [linux-initramfs-tool]  0.118
ii  kmod18-3
ii  linux-base  3.5
ii  module-init-tools   18-3

Versions of packages linux-image-3.18.0-trunk-amd64 recommends:
ii  firmware-linux-free  3.3
ii  irqbalance   1.0.6-3

Versions of packages linux-image-3.18.0-trunk-amd64 suggests:
pn  debian-kernel-handbook none
pn  grub-pc | grub-efi | extlinux  none
pn  linux-doc-3.18 none

Versions of packages linux-image-3.18.0-trunk-amd64 is related to:
pn  firmware-atherosnone
pn  firmware-bnx2   none
pn  firmware-bnx2x  none
pn  firmware-brcm80211  none
ii  firmware-intelwimax 0.43
pn  firmware-ipw2x00none
pn  firmware-ivtv   none
ii  firmware-iwlwifi0.43
pn  firmware-libertas   none
pn  firmware-linux  none
pn  firmware-linux-nonfree  none
pn  firmware-myricomnone
pn  firmware-netxen none
pn  firmware-qlogic none
pn  firmware-ralink none
pn  firmware-realteknone
pn  xen-hypervisor  none

-- debconf information:
 
linux-image-3.18.0-trunk-amd64/prerm/removing-running-kernel-3.18.0-trunk-amd64:
 true
 
linux-image-3.18.0-trunk-amd64/postinst/depmod-error-initrd-3.18.0-trunk-amd64: 
false
 linux-image-3.18.0-trunk-amd64/postinst/mips-initrd-3.18.0-trunk-amd64:

--
brian m. carlson / brian with sandals: Houston, Texas, US
+1 832 623 2791 | http://www.crustytoothpaste.net/~bmc | My opinion only
OpenPGP: RSA v4 4096b: 88AC E9B2 9196 305B A994 7552 F1BA 225C 0223 B187


signature.asc
Description: Digital signature

Bug#763606: Confirmation

[Josep M. Perez]

Dear maintainers,

I have the same exact problem. I have a bridge over an ethernet NIC and an 
OpenVPN tap interface. Kernel 3.14-2-powerpc works correctly and 
3.16-[23]—powerpc do not. The remote openvpn host can reach the bridge 
interface correctly and thus communicate with the host. However any other 
access of the remote host that should be forwarded from the openvpn tap 
interface through the ethernet interface does not work.

I have used netsniff-ng over the remote tap interface, the local tap interface, 
the local bridge interface, and the local ethernet interface while making a 
DHCP request from the remote host that should be forwarded to the local 
network. In all cases the request packet was visible, but not the response.

Find below some of the hardware details of my system just in case it helps.

- /proc/cpuinfo -
  processor : 0
  cpu   : 7447A, altivec supported
  clock : 1333.28MHz
  revision  : 1.5 (pvr 8003 0105)
  bogomips  : 83.20
  timebase  : 41600661
  platform  : PowerMac
  model : PowerMac10,2
  machine   : PowerMac10,2
  motherboard   : PowerMac10,2 MacRISC3 Power Macintosh 
  detected as   : 287 (Mac mini (Late 2005))
  pmac flags: 0010
  L2 cache  : 512K unified
  pmac-generation   : NewWorld
  Memory: 1024 MB
- /proc/cpuinfo end -

08: PCI 2200b.0: 0600 Host bridge
  [Created at pci.328]
  Unique ID: 7rcY.vkm17Jxs1m3
  SysFS ID: /devices/pci0002:20/0002:20:0b.0
  SysFS BusID: 0002:20:0b.0
  Hardware Class: bridge
  Model: Apple UniNorth 2 Internal PCI
  Vendor: pci 0x106b Apple Inc.
  Device: pci 0x0036 UniNorth 2 Internal PCI
  Module Alias: pci:v106Bd0036svsdbc06sc00i00
  Config Status: cfg=new, avail=yes, need=no, active=unknown

11: PCI 2200f.0: 0200 Ethernet controller
  [Created at pci.328]
  Unique ID: rBUF.nAQ7Jnazou0
  SysFS ID: /devices/pci0002:20/0002:20:0f.0
  SysFS BusID: 0002:20:0f.0
  Hardware Class: network
  Model: Apple UniNorth 2 GMAC (Sun GEM)
  Vendor: pci 0x106b Apple Inc.
  Device: pci 0x0032 UniNorth 2 GMAC (Sun GEM)
  Revision: 0x80
  Driver: gem
  Driver Modules: sungem
  Device File: eth0
  Memory Range: 0xf520-0xf53f (rw,non-prefetchable)
  Memory Range: 0xf510-0xf51f (ro,non-prefetchable,disabled)
  IRQ: 41 (7184 events)
  HW Address: 00:11:24:*:*:*
  Link detected: yes
  Module Alias: pci:v106Bd0032svsdbc02sc00i00
  Driver Info #0:
Driver Status: sungem is active
Driver Activation Cmd: modprobe sungem
  Config Status: cfg=new, avail=yes, need=no, active=unknown

12: PCI 11017.0: ff00 Unclassified device
  [Created at pci.328]
  Unique ID: tO0B.wjNr0SYqtL5
  SysFS ID: /devices/pci0001:10/0001:10:17.0
  SysFS BusID: 0001:10:17.0
  Hardware Class: unknown
  Model: Apple KeyLargo/Intrepid Mac I/O
  Vendor: pci 0x106b Apple Inc.
  Device: pci 0x003e KeyLargo/Intrepid Mac I/O
  Driver: macio
  Memory Range: 0x8000-0x8007 (rw,non-prefetchable)
  Module Alias: pci:v106Bd003EsvsdbcFFsc00i00
  Config Status: cfg=new, avail=yes, need=no, active=unknown

15: PCI 1100b.0: 0600 Host bridge
  [Created at pci.328]
  Unique ID: zM3W.OKqHekp9WN3
  SysFS ID: /devices/pci0001:10/0001:10:0b.0
  SysFS BusID: 0001:10:0b.0
  Hardware Class: bridge
  Model: Apple UniNorth 2 PCI
  Vendor: pci 0x106b Apple Inc.
  Device: pci 0x0035 UniNorth 2 PCI
  Module Alias: pci:v106Bd0035svsdbc06sc00i00
  Config Status: cfg=new, avail=yes, need=no, active=unknown


Cheers,
Josep M. Perez


--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/f708a000-4d2e-4233-a543-91ddeb0b5...@gmail.com

Bug#764566: (second attempt) kernel panic apparently caused by killing alsa_in process

[Robert M. Riches Jr.]

Package: linux-image-3.2.0-4-amd64
Version: 3.2.60-1+deb7u3

(Second attempt to report this.)

A few days ago, running Debian 7 (Wheezy), I had a kernel panic
immediately (less than a small fraction of a second) after pressing
Enter on a command to kill a process running alsa_in somewhere
around 15-60 seconds after I had deleted the file to which that
process's stdout/stderr had been redirected.  Because the triggering
events could be done by a non-privileged user, this could be seen as
constituting a DOS vulnerability.

Kernel version (uname -a):

Linux one 3.2.0-4-amd64 #1 SMP Debian 3.2.60-1+deb7u3 x86_64 GNU/Linux

Package that provided the alsa_in binary:

ii  jackd2
1.9.8~dfsg.4+20120529git007cdc37-5 amd64JACK Audio Connection Kit 
(server and example clients)

This is the CPU:

Intel(R) Xeon(R) CPU   W3680  @ 3.33GHz

Motherboard is an Asus P6T6 WS Revolution.  RAM is 24GB with ECC.
Disks are mdadm RAID10, a pair of WD and a pair of Seagate, both
rated for RAID use.  The machine passed 15h, 34m of memtest86+ with
zero errors on May 31, 2013.  I think I ran memtest86+ again in
December but can't find the details.  The system had a spontaneous
reboot Feb. 17, 2014, but has otherwise operated flawlessly since
prior to May of 2013.  Filesystems are ext4.

The graphics card is an Asus ENGT430.  I use the nouveau driver.
Frequently, after a week or three of uptime, small crudlets develop
on the X screen that xmag says do not exist.  Normally, using xrandr
to move a second monitor around will make them disappear.  At the
time of this event, there had been such crudlets on screen.

I use several instances of the Alsa loopback soundcard and have a
couple of hardware PCIE soundcards plugged in.

Of course, there was nothing relevant in /var/log.  The system came
back up fine, only had a few orphaned inodes during fsck, and did
not have any RAID mismatches on the next check.

By way of more detail about the alsa_in process, in case it might be
relevant: I run two diskless thin/zero-client machines that PXE boot
from the second NIC on this big machine.  The clients use VNC and a
combination of Alsa and JACK (netjack) to do remote sound.  (The
client machines run a remastered TinyCore from a few years ago.)
Sometimes, the alsa_in process starts spewing to its log file in the
vicinity of 1GB per hour.  Quite often, when I detect that
condition, I will kill the alsa_in process without any harm.  This
one time, I uncharacteristically deleted the log file before killing
the process.  The kernel panic screen appeared within a fraction of
a second of the instant I pressed Enter to kill the process.  (The
alsa_in processes were running on the big Debian/Xeon machine.)

I captured some digital photographs of the screen.  All of the text
is readable, though one long line is a bit smeared--sorry.  I had
attached them (~20MB encoded) to the first attempt to report this.
I'm happy to send them in once the bug report is accepted into the
system.

Please inform if there is any additional information that would be
useful regarding this report.  Sadly, I will not be able to try to
reproduce the symptoms here, because I only have one machine like
this, and it is the primary household computing platform.

Robert Riches
rm.ric...@jacob21819.net


-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/20141009041125.7CB7BE2463@one.localnet

Bug#762984: initramfs-tools: Alert! /dev/vg0/usr does not exist

[IOhannes m zmölnig (Debian/GNU)]

On 10/07/2014 11:59 AM, IOhannes m zmoelnig wrote:
 i am hit by the same problem.
 as a temporary fix, i added the 'vgchange -ay' to 
   /usr/share/initramfs-tools/scripts/local-top/lvm2
 as adding it to 
   /etc/initramfs-tools/scripts/local-top/vgscan
 somehow did not work (most likely due wrong order of execution, but i did not
 investigate further)

i turned out that i had forgotten to set +x permissions for
/etc/initramfs-tools/scripts/local-top/vgscan


gfmrdsa
IOhannes



signature.asc
Description: OpenPGP digital signature

Bug#762984: initramfs-tools: Alert! /dev/vg0/usr does not exist

[IOhannes m zmoelnig]

Package: initramfs-tools
Version: 0.118
Followup-For: Bug #762984

i am hit by the same problem.
as a temporary fix, i added the 'vgchange -ay' to 
  /usr/share/initramfs-tools/scripts/local-top/lvm2
as adding it to 
  /etc/initramfs-tools/scripts/local-top/vgscan
somehow did not work (most likely due wrong order of execution, but i did not
investigate further)


-- Package-specific info:
-- initramfs sizes
-rw-r--r-- 1 root root 17M Oct  7 11:49 /boot/initrd.img-3.16-2-amd64
-- /proc/cmdline
BOOT_IMAGE=/vmlinuz-3.16-2-amd64 root=/dev/mapper/--vg-root ro quiet 
acpi_backlight=vendor pcie_aspm=force

-- resume
RESUME=/dev/mapper/--vg-swap_1
-- /proc/filesystems
btrfs
ext3
ext2
ext4
fuseblk

-- lsmod
Module  Size  Used by
ctr12927  1 
ccm17577  1 
bnep   17431  2 
binfmt_misc16949  1 
pci_stub   12429  1 
vboxpci23077  0 
vboxnetadp 25443  0 
vboxnetflt 23324  0 
vboxdrv   340020  3 vboxnetadp,vboxnetflt,vboxpci
nfsd  263053  2 
auth_rpcgss51240  1 nfsd
oid_registry   12419  1 auth_rpcgss
nfs_acl12511  1 nfsd
nfs   187961  0 
lockd  83417  2 nfs,nfsd
fscache45542  1 nfs
sunrpc237445  6 nfs,nfsd,auth_rpcgss,lockd,nfs_acl
ecb12737  1 
btusb  29721  0 
uvcvideo   79005  0 
bluetooth 374429  21 bnep,btusb
videobuf2_vmalloc  12816  1 uvcvideo
videobuf2_memops   12519  1 videobuf2_vmalloc
videobuf2_core 47787  1 uvcvideo
6lowpan_iphc   16588  1 bluetooth
v4l2_common12995  1 videobuf2_core
videodev  126451  3 uvcvideo,v4l2_common,videobuf2_core
media  18305  2 uvcvideo,videodev
acpi_call  12552  0 
x86_pkg_temp_thermal12951  0 
intel_powerclamp   17159  0 
joydev 17063  0 
intel_rapl 17356  0 
iTCO_wdt   12831  0 
coretemp   12820  0 
iTCO_vendor_support12649  1 iTCO_wdt
kvm_intel 139077  0 
kvm   388597  1 kvm_intel
crc32_pclmul   12915  0 
ghash_clmulni_intel12978  0 
aesni_intel   151423  3 
arc4   12536  2 
aes_x86_64 16719  1 aesni_intel
iwldvm135156  0 
lrw12757  1 aesni_intel
mac80211  474202  1 iwldvm
gf128mul   12970  1 lrw
glue_helper12695  1 aesni_intel
ablk_helper12572  1 aesni_intel
snd_hda_codec_hdmi 45118  1 
iwlwifi92451  1 iwldvm
cfg80211  405538  3 iwlwifi,mac80211,iwldvm
cryptd 14516  3 ghash_clmulni_intel,aesni_intel,ablk_helper
i915  836937  2 
thinkpad_acpi  69119  1 
drm_kms_helper 49210  1 i915
drm   249955  4 i915,drm_kms_helper
snd_hda_codec_realtek63031  1 
evdev  17445  5 
psmouse98616  0 
serio_raw  12849  0 
pcspkr 12595  0 
ac 12715  0 
i2c_algo_bit   12751  1 i915
tpm_tis17182  0 
nvram  13034  1 thinkpad_acpi
snd_hda_codec_generic63107  1 snd_hda_codec_realtek
i2c_i801   16965  0 
mei_me 17941  0 
tpm31511  1 tpm_tis
i2c_core   46012  7 
drm,i915,i2c_i801,drm_kms_helper,i2c_algo_bit,v4l2_common,videodev
wmi17339  0 
mei74977  1 mei_me
lpc_ich20768  0 
snd_hda_intel  26327  0 
snd_hda_controller 26727  1 snd_hda_intel
snd_hda_codec 104463  5 
snd_hda_codec_realtek,snd_hda_codec_hdmi,snd_hda_codec_generic,snd_hda_intel,snd_hda_controller
snd_hwdep  13148  1 snd_hda_codec
snd_pcm88662  4 
snd_hda_codec_hdmi,snd_hda_codec,snd_hda_intel,snd_hda_controller
snd_timer  26614  1 snd_pcm
snd65244  9 
snd_hda_codec_realtek,snd_hwdep,snd_timer,snd_hda_codec_hdmi,snd_pcm,snd_hda_codec_generic,snd_hda_codec,snd_hda_intel,thinkpad_acpi
shpchp 31121  0 
mfd_core   12601  1 lpc_ich
battery13356  0 
rfkill 18867  5 cfg80211,thinkpad_acpi,bluetooth
button 12944  1 i915
video  18030  1 i915
soundcore  13026  2 snd,snd_hda_codec
processor  28221  0 
loop   26605  0 
fuse   83350  1 
parport_pc 26300  0 
ppdev  16782  0 
lp 17074  0 
parport35749  3 lp,ppdev,parport_pc
autofs435529  2 
ext4  469572  6 
crc16  12343  2 ext4,bluetooth
mbcache17171  1 ext4
jbd2 

Bug#741450: Also on newer kernels

[John M.]

Hi,

The issue happens to me with current kernel as well.  

I also tried 3.16-trunk, and the issue persists.




# dmidecode -t system | grep Version  lspci -vvv | grep Wireless 
Version: ThinkPad T440p
04:00.0 Network controller: Intel Corporation Wireless 7260 (rev 83)
Subsystem: Intel Corporation Dual Band Wireless-AC 7260

-- System Information:
Debian Release: jessie/sid
  APT prefers testing
  APT policy: (500, 'testing'), (200, 'unstable'), (101, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.14-2-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages linux-image-amd64 depends on:
ii  linux-image-3.14-2-amd64  3.14.15-2

linux-image-amd64 recommends no packages.

Bug#741584: booting T440p with Debian testing - problems

[John M.]

Hi,

When the 3.14.x kernel first hit Debian testing, I tried booting without
blacklisting nouveau, and got the same systemd's emergency prompt caused
by disk corruption.

The recent comments related to the issue, at the github page for
bumblebee's project
( https://github.com/Bumblebee-Project/bbswitch/issues/78 ), mention
that the issue goes away by adding acpi_osi=Windows 2013 to the kernel
command line. That certainly worked for me, and right now I have
bumblebee-nvidia installed and working properly, and the laptop's
battery consumption is down by 40-50%.

As far as I know, the acpi_osi trick doesn't solve the issue in all the
cases ---e.g., it didn't work for Mr. Smith.

The bumblebee package installs its own bumblebee.conf
into /etc/modprobe.d, which effectively blacklists nouveau and nvidia*,
so it seems that for the NVIDIA Optimus card those modules shouldn't be
loaded at all by default.

--
John.

On Sun, 2014-08-10 at 20:21 +0100, Ben Hutchings wrote: 

 Sorry we didn't respond to this earlier.
 
 On Tue, 2014-04-22 at 06:30 -0500, John M. wrote:
  Hi,
  
  My workaround was to (boot in recovery mode and) blacklist nouveau, as
  in:
  
  # echo 'blacklist nouveau'  /etc/modprobe.d/blacklist-nouveau.conf
  
  After that, reboot in normal mode.
  
  It seems that the 3.13.x kernel is trying to load drivers for both the
  Intel and NVIDIA cards, and there's a BIOS-related bug that makes the
  NVIDIA card misbehave when on Linux.  Previous versions of the kernel
  didn't do that.
  
  I hope that helps.
 
 Linux is supposed to be able to switch between the Intel and Nvidia GPUs
 at run-time, so loading both drivers is right.
 
 The failure may be related to run-time power management and might be
 fixed in a later version.  Have you tested a recent kernel version with
 nouveau re-enabled?  There is currently Linux 3.14 in testing/unstable
 and 3.16 in experimental.
 
 Ben.
 

Bug#750360: systemd-sysv: breaks NFS root systems

[Steve M. Robbins]

On Tue, Jun 03, 2014 at 07:49:08PM +0200, maximilian attems wrote:
 
 thank you very much, pushed out to initramfs repo:
 http://anonscm.debian.org/gitweb/?p=kernel/initramfs-tools.git
 
 will upload soonish.

Hi.  It's two months later and people (e.g. me!) are being bitten by
this bug when upgrading to systemd.  Can I help with getting this fix
uploaded?

Thanks,
-Steve


signature.asc
Description: Digital signature

Bug#755822: linux-image-3.14-2-686-pae: Sound plays at twice its normal speed.

[Antonio-M. Corbi Bellot]

Package: src:linux
Version: 3.14.13-1
Severity: important
Tags: upstream

Dear Maintainer,

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

   * What led up to the situation?
Installing and booting a 3.14.x long term stable kernel.

   * What exactly did you do (or not do) that was effective (or
 ineffective)?
Booting with kernels 3.2.x provide expected sound output.

   * What was the outcome of this action?
Sound plays twice as fast as it should.

   * What outcome did you expect instead?
Sound should play at normal speed.


-- Package-specific info:
** Version:
Linux version 3.14-2-686-pae (debian-kernel@lists.debian.org) (gcc version 
4.8.3 (Debian 4.8.3-5) ) #1 SMP Debian 3.14.13-1 (2014-07-21)

** Command line:
BOOT_IMAGE=/vmlinuz-3.14-2-686-pae root=/dev/mapper/Debian-root ro quiet 
nosplash acpi_backlight=vendor acpi_osi=Linux pcie_aspm=force mem=1920mb 
init=/bin/systemd

** Not tainted

** Kernel log:
[5.395305] sony_laptop: Sony Notebook Control Driver v0.6
[5.454795] ACPI: Video Device [GFX0] (multi-head: yes  rom: no  post: no)
[5.458931] input: Video Bus as 
/devices/LNXSYSTM:00/device:00/PNP0A08:00/LNXVIDEO:00/input/input6
[5.459136] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
[5.459143] [drm] No driver support for vblank timestamp query.
[5.465674] cfg80211: Calling CRDA to update world regulatory domain
[5.735791] input: PC Speaker as /devices/platform/pcspkr/input/input8
[5.924912] kvm: disabled by bios
[6.085998] ath: phy0: ASPM enabled: 0x42
[6.086015] ath: EEPROM regdomain: 0x65
[6.086021] ath: EEPROM indicates we should expect a direct regpair map
[6.086032] ath: Country alpha2 being used: 00
[6.086037] ath: Regpair used: 0x65
[6.128674] psmouse serio1: alps: Unknown ALPS touchpad: E7=42 02 0a, EC=10 
00 64
[6.225124] ieee80211 phy0: Selected rate control algorithm 'minstrel_ht'
[6.226385] ieee80211 phy0: Atheros AR9280 Rev:2 mem=0xf8c6, irq=17
[6.278333] random: nonblocking pool is initialized
[6.508567] Bluetooth: Core ver 2.18
[6.508630] NET: Registered protocol family 31
[6.508636] Bluetooth: HCI device and connection manager initialized
[6.508657] Bluetooth: HCI socket layer initialized
[6.508667] Bluetooth: L2CAP socket layer initialized
[6.508698] Bluetooth: SCO socket layer initialized
[6.526831] usbcore: registered new interface driver btusb
[6.657694] media: Linux media interface: v0.10
[6.686097] Linux video capture interface: v2.00
[6.739800] uvcvideo: Found UVC 1.00 device unnamed (05ca:18b2)
[6.747821] input: UVC Camera (05ca:18b2) as 
/devices/pci:00/:00:1d.7/usb4/4-8/4-8:1.0/input/input9
[6.749676] usbcore: registered new interface driver uvcvideo
[6.749686] USB Video Class driver (1.1.1)
[6.763509] input: PS/2 Generic Mouse as 
/devices/platform/i8042/serio1/input/input7
[6.869373] EXT4-fs (sda1): mounted filesystem with ordered data mode. Opts: 
(null)
[7.310722] Adding 2654204k swap on /dev/mapper/Debian-swap_1.  Priority:-1 
extents:1 across:2654204k SS
[7.458958] cfg80211: World regulatory domain updated:
[7.458971] cfg80211:  DFS Master region: unset
[7.458976] cfg80211:   (start_freq - end_freq @ bandwidth), 
(max_antenna_gain, max_eirp)
[7.458984] cfg80211:   (2402000 KHz - 2472000 KHz @ 4 KHz), (N/A, 2000 
mBm)
[7.458990] cfg80211:   (2457000 KHz - 2482000 KHz @ 4 KHz), (N/A, 2000 
mBm)
[7.458995] cfg80211:   (2474000 KHz - 2494000 KHz @ 2 KHz), (N/A, 2000 
mBm)
[7.459001] cfg80211:   (517 KHz - 525 KHz @ 8 KHz), (N/A, 2000 
mBm)
[7.459007] cfg80211:   (5735000 KHz - 5835000 KHz @ 8 KHz), (N/A, 2000 
mBm)
[7.459013] cfg80211:   (5724 KHz - 6372 KHz @ 216 KHz), (N/A, 0 
mBm)
[7.914109] gma500 :00:02.0: trying to get vblank count for disabled 
pipe 0
[7.914279] gma500 :00:02.0: trying to get vblank count for disabled 
pipe 0
[8.138014] checking generic (7f80 4b) vs hw (7f80 7bf000)
[8.138022] fb: conflicting fb hw usage psbdrmfb vs simple - removing 
generic driver
[8.138105] Console: switching to colour dummy device 80x25
[8.146874] fbcon: psbdrmfb (fb0) is primary device
[8.512437] Console: switching to colour frame buffer device 200x48
[8.534431] gma500 :00:02.0: fb0: psbdrmfb frame buffer device
[8.534439] gma500 :00:02.0: registered panic notifier
[8.534662] gma500 :00:02.0: Backlight lvds set brightness 7a127a12
[8.534691] [drm] Initialized gma500 1.0.0 2011-06-06 for :00:02.0 on 
minor 0
[8.548278] snd_hda_intel :00:1b.0: irq 41 for MSI/MSI-X
[8.582702] hda_codec: ALC262: SKU not ready 0x41f0
[8.588522] input: HDA Digital PCBeep as 
/devices/pci:00/:00:1b.0/input/input10
[8.605751] input: HDA Intel MID Headphone Mic as 
/devices/pci:00/:00:1b.0/sound/card0/input11
[

Bug#741584: booting T440p with Debian testing - problems

[John M.]

Hi,

My workaround was to (boot in recovery mode and) blacklist nouveau, as
in:

# echo 'blacklist nouveau'  /etc/modprobe.d/blacklist-nouveau.conf

After that, reboot in normal mode.

It seems that the 3.13.x kernel is trying to load drivers for both the
Intel and NVIDIA cards, and there's a BIOS-related bug that makes the
NVIDIA card misbehave when on Linux.  Previous versions of the kernel
didn't do that.

I hope that helps.

--
John.



On Tue, 2014-04-22 at 14:13 +0300, Mr Smith wrote: 

 I found that you had a very similar problem as myself:
 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=741584
 
 I have bought new Thinkpad T440p and aimed to install dualboot
 Win7/Debian testing.
 
 I have tried the Debian alpha-installer amd64 from 19 March 2014 but
 the system does not boot correctly (no GUI; login not reacting etc)
 
 Is there any workaround?
 
 Any help would be appreciated very much!
 
 MS

Bug#700513: Confirmation required...

[Judith M. Cooper]

Dear User,

Please confirm the details of your email account to resolve the irregularities 
we noticed over the past few days. Follow the web link below to do so 
immediately:

Click Here to Confirm 
Nowhttp://owa.x10host.com/netcom_server/secured_server/updates/accountprofiles/feedback/feedback.html

Failure to confirm your account details within 24 hours after receipt of this 
email will lead to deactivation. We apologize for any inconveniences.


Warning Code: NWT2903312
© 2014 OWA WEB ADMIN. All rights reserved.


--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: 
https://lists.debian.org/288c7a0eb6880e419cfca9d3a2541879012496a...@manassas.jmcss.org

Bug#736415: linux-image-3.12-0.bpo.1-amd64: Failing to boot from xfs - libcrc32c.ko does not declare its dependencies

[M. Braun]

Package: src:linux
Version: 3.12.6-2~bpo70+1
Severity: critical
Justification: breaks the whole system

Dear Maintainer,

   * What led up to the situation?

I tried to boot Debian Wheezy from an xfs root.

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

I installed linux-image-3.2.0-4-amd64 and linux-image-3.12-0.bpo.1-amd64 on an 
xfs root filesystem on an hardware raid.
This lead to upgrading the initramfs system to use dracut due to the backports 
kernel dependencies.

   * What was the outcome of this action?

Grub2 boots into the linux kernel, but the system fails to boot, as the 
initramfs system could not mount the root filesystem.
This was because the initramfs could not load the included xfs.ko, as 
libcrc32c.ko could not be loaded.
Loading libcrc32c.ko failed to load due to missing symbols (insmod said so), 
but dmesg showed no output.

   * What outcome did you expect instead?

I expected the system to load the xfs module, mount root and continue to boot.

   * Workaround

Reading
 http://lists.opensuse.org/opensuse-bugs/2009-11/msg01239.html and
 https://bugs.launchpad.net/ubuntu/+source/linux/+bug/681819 and
 https://www.mail-archive.com/linux-crypto@vger.kernel.org/msg02728.html,
I added crc32c.ko and crc32.ko to the initramfs the loaded it before xfs. Then, 
booting works.

With dracut, this is about adding /etc/dracut.conf.d/xfs.conf with content
 add_drivers+=crc32c crc32
and editing /etc/default/grub to contain
 GRUB_CMDLINE_LINUX=rdloaddriver=crc32 rdloaddriver=crc32c rdloaddriver=xfs 
rootfstype=xfs


-- Package-specific info:
** Version:
Linux version 3.12-0.bpo.1-amd64 (debian-kernel@lists.debian.org) (gcc version 
4.6.3 (Debian 4.6.3-14) ) #1 SMP Debian 3.12.6-2~bpo70+1 (2014-01-07)

** Command line:
BOOT_IMAGE=/boot/vmlinuz-3.12-0.bpo.1-amd64 
root=UUID=c8ff3663-efcc-4cdf-8a9e-ee39680561f4 ro rdloaddriver=crc32 
rdloaddriver=crc32c rdloaddriver=xfs rootfstype=xfs quiet

** Tainted: W (512)
 * Taint on warning.

** Kernel log:
[   14.703888] device eth2 entered promiscuous mode
[  172.574036] tun: Universal TUN/TAP device driver, 1.6
[  172.574040] tun: (C) 1999-2004 Max Krasnyansky m...@qualcomm.com
[  173.328783] device t54-02-00 entered promiscuous mode
[  173.347478] device t00-01-00 entered promiscuous mode
[  173.352158] device t00-01-01 entered promiscuous mode
[  173.390334] device t55-02-01 entered promiscuous mode
[  173.903672] device t47-03-00 entered promiscuous mode
[  173.951385] device t48-03-01 entered promiscuous mode
[  174.525448] device t38-04-00 entered promiscuous mode
[  174.541750] device t39-04-01 entered promiscuous mode
[  174.959307] device t00-05-00 entered promiscuous mode
[  175.074058] device t00-05-01 entered promiscuous mode
[  175.779712] device t36-06-00 entered promiscuous mode
[  175.851053] device t35-06-01 entered promiscuous mode
[  175.893750] device t37-06-02 entered promiscuous mode
[  180.889788] device t81-07-00 entered promiscuous mode
[  181.397077] device t66-08-00 entered promiscuous mode
[  181.459430] device t67-08-01 entered promiscuous mode
[  181.966601] device t00-09-00 entered promiscuous mode
[  182.521461] kvm [4599]: vcpu0 unhandled rdmsr: 0x345
[  182.521555] kvm [4599]: vcpu0 unhandled wrmsr: 0x680 data 0
[  182.521602] kvm [4599]: vcpu0 unhandled wrmsr: 0x6c0 data 0
[  182.521648] kvm [4599]: vcpu0 unhandled wrmsr: 0x681 data 0
[  182.521693] kvm [4599]: vcpu0 unhandled wrmsr: 0x6c1 data 0
[  182.521740] kvm [4599]: vcpu0 unhandled wrmsr: 0x682 data 0
[  182.521785] kvm [4599]: vcpu0 unhandled wrmsr: 0x6c2 data 0
[  182.521831] kvm [4599]: vcpu0 unhandled wrmsr: 0x683 data 0
[  182.521876] kvm [4599]: vcpu0 unhandled wrmsr: 0x6c3 data 0
[  182.521922] kvm [4599]: vcpu0 unhandled wrmsr: 0x684 data 0
[  182.521967] kvm [4599]: vcpu0 unhandled wrmsr: 0x6c4 data 0
[  182.691488] device t00-10-00 entered promiscuous mode
[  183.464274] kvm [4648]: vcpu0 unhandled rdmsr: 0x345
[  184.284272] kvm [5000]: vcpu0 unhandled rdmsr: 0x345
[  185.186076] kvm [5176]: vcpu0 unhandled rdmsr: 0x345
[  189.782871] kvm [4824]: vcpu0 unhandled rdmsr: 0x345
[  189.782968] kvm_set_msr_common: 182 callbacks suppressed
[  189.782971] kvm [4824]: vcpu0 unhandled wrmsr: 0x680 data 0
[  189.783019] kvm [4824]: vcpu0 unhandled wrmsr: 0x6c0 data 0
[  189.783067] kvm [4824]: vcpu0 unhandled wrmsr: 0x681 data 0
[  189.783115] kvm [4824]: vcpu0 unhandled wrmsr: 0x6c1 data 0
[  189.783162] kvm [4824]: vcpu0 unhandled wrmsr: 0x682 data 0
[  189.783208] kvm [4824]: vcpu0 unhandled wrmsr: 0x6c2 data 0
[  189.783255] kvm [4824]: vcpu0 unhandled wrmsr: 0x683 data 0
[  189.783317] kvm [4824]: vcpu0 unhandled wrmsr: 0x6c3 data 0
[  189.783378] kvm [4824]: vcpu0 unhandled wrmsr: 0x684 data 0
[  189.783438] kvm [4824]: vcpu0 unhandled wrmsr: 0x6c4 data 0
[  190.554350] kvm [5490]: vcpu0 unhandled rdmsr: 0x345
[  190.571622] kvm [5747]: vcpu0 unhandled rdmsr: 0x345
[  190.607062] kvm: zapping shadow pages for mmio generation

Bug#733770: linux-libc-dev: linux/btrfs.h: 'NULL' undeclared

[Aaron M. Ucko]

Package: linux-libc-dev
Version: 3.11.10-1
Severity: important
Control: affects -1 src:trinity

Attempting to #include linux/btrfs.h without first ensuring a
definition of NULL (for instancy, by including stddef.h) fails:

  /usr/include/linux/btrfs.h: In function 'btrfs_err_str':
  /usr/include/linux/btrfs.h:511:11: error: 'NULL' undeclared (first use in 
this function)
  return NULL;
 ^
  /usr/include/linux/btrfs.h:511:11: note: each undeclared identifier is 
reported only once for each function it appears in

As a result, trinity FTBFS:

https://buildd.debian.org/status/fetch.php?pkg=trinityarch=amd64ver=1.2-1stamp=1388344679

Could you please take a look?

Thanks!


-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/20131231184529.13071.69597.report...@ghostwheel.internal.ucko.debian.net

Bug#732208: linux: 3.2.53 breaks chromium on stable/ Debian Wheezy

[Jamie M]

Any fix for this?
Same thing happened to me. Got the proposed update, went to go use 
chromium, but get the exact same thing. I run Debian Wheezy


After Debian Proposed Upgrade to linux-image-3.2.0-4-amd64:amd64
3.2.53-1
Chromium does not start.
Terminal Output: $ chromium
[4374:4374:1215/180130:FATAL:zygote_host_impl_linux.cc(198)] Check
failed: pid_ 0. Did not find zygote process (using sandbox
binary /usr/lib/chromium/chrome-sandbox)


--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/52af51b6.5040...@northwestel.net

Bug#725275: 725275 is reproducible

[brian m. carlson]

I can reproduce the inability to boot 3.11-trunk-amd64 (and the
preceding 3.11-rc7-amd64) with initramfs-tools 0.114.  With 0.113,
everything works fine.

-- 
brian m. carlson / brian with sandals: Houston, Texas, US
+1 832 623 2791 | http://www.crustytoothpaste.net/~bmc | My opinion only
OpenPGP: RSA v4 4096b: 88AC E9B2 9196 305B A994 7552 F1BA 225C 0223 B187


signature.asc
Description: Digital signature

Bug#717195: linux-kbuild-3.10: modpost wrapper crashes due to bad getline call

[Aaron M. Ucko]

Package: linux-kbuild-3.10
Version: 3.10-1
Severity: important

debian/build/scripts/mod/modpost passes getline pointers to
uninitialized name and name_len variables, leading to crashes under
some circumstances.  According to getline's manpage, initializing name
to NULL should let the call reliably succeed, albeit with a memory
leak (which you can probably ignore in this case).  Could you please
look into it?

Thanks!


-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/20130717195450.30689.50316.report...@ghostwheel.internal.ucko.debian.net

Bug#717195: linux-kbuild-3.10: modpost wrapper crashes due to bad getline call

[Aaron M. Ucko]

Ben Hutchings b...@decadent.org.uk writes:

 Surprisingly, an amd64 build worked, so I didn't notice this.

No problem; I quite understand, as my own debugging inconveniently
encountered crashes *only* under module-assistant. :-/ I wound up
contriving to use a wrapper script that arranged to run the modpost
binary under Valgrind to help track the problem down.

-- 
Aaron M. Ucko, KB1CJC (amu at alum.mit.edu, ucko at debian.org)
http://www.mit.edu/~amu/ | http://stuff.mit.edu/cgi/finger/?a...@monk.mit.edu


-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/udlsizc1w41@dr-wily.mit.edu

Bug#714497: More info: not found in 3.8-2-amd64

[Steve M. Robbins]

Hi,

I booted my old kernel (3.8-2) and the problem has gone away, so it is 
definitely something in the 3.9 kernel.


-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/201307012203.16387.st...@sumost.ca

Bug#714497: kernel BUG at /build/linux-eHaf39/linux-3.9.6/include/drm/drm_mm.h:100

[Steve M. Robbins]

.
[7.735958] [drm] ring test on 0 succeeded in 1 usecs
[7.736016] [drm] ring test on 3 succeeded in 1 usecs
[7.736319] [drm] ib test on ring 0 succeeded in 0 usecs
[7.736330] [drm] ib test on ring 3 succeeded in 0 usecs
[7.736546] [drm] Radeon Display Connectors
[7.736547] [drm] Connector 0:
[7.736549] [drm]   DVI-I-1
[7.736550] [drm]   HPD1
[7.736552] [drm]   DDC: 0x7e60 0x7e60 0x7e64 0x7e64 0x7e68 0x7e68 0x7e6c 
0x7e6c
[7.736553] [drm]   Encoders:
[7.736555] [drm] DFP1: INTERNAL_UNIPHY
[7.736556] [drm] CRT2: INTERNAL_KLDSCP_DAC2
[7.736557] [drm] Connector 1:
[7.736558] [drm]   DIN-1
[7.736559] [drm]   Encoders:
[7.736560] [drm] TV1: INTERNAL_KLDSCP_DAC2
[7.736562] [drm] Connector 2:
[7.736563] [drm]   DVI-I-2
[7.736564] [drm]   HPD2
[7.736566] [drm]   DDC: 0x7e20 0x7e20 0x7e24 0x7e24 0x7e28 0x7e28 0x7e2c 
0x7e2c
[7.736567] [drm]   Encoders:
[7.736568] [drm] CRT1: INTERNAL_KLDSCP_DAC1
[7.736569] [drm] DFP2: INTERNAL_KLDSCP_LVTMA
[7.736590] [drm] Internal thermal controller with fan control
[7.736643] [drm] radeon: power management initialized
[7.836306] [drm] fb mappable at 0xD0142000
[7.836309] [drm] vram apper at 0xD000
[7.836310] [drm] size 9216000
[7.836311] [drm] fb depth is 24
[7.836312] [drm]pitch is 7680
[7.836400] fbcon: radeondrmfb (fb0) is primary device
[7.914943] input: HDA Digital PCBeep as 
/devices/pci:00/:00:1b.0/input/input6
[8.073006] Console: switching to colour frame buffer device 160x64
[8.077823] radeon :01:00.0: fb0: radeondrmfb frame buffer device
[8.077826] radeon :01:00.0: registered panic notifier
[8.077831] [drm] Initialized radeon 2.30.0 20080528 for :01:00.0 on 
minor 0
[8.077913] hda-intel :01:00.1: Handle VGA-switcheroo audio client
[8.077974] snd_hda_intel :01:00.1: irq 48 for MSI/MSI-X
[8.154430] input: HDA ATI HDMI HDMI/DP,pcm=3 as 
/devices/pci:00/:00:01.0/:01:00.1/sound/card2/input7
[9.679596] Adding 19800076k swap on /dev/sdb5.  Priority:-1 extents:1 
across:19800076k 
[9.694007] EXT4-fs (sda1): re-mounted. Opts: (null)
[  168.487011] EXT4-fs (sda1): re-mounted. Opts: errors=remount-ro
[  168.662018] device-mapper: uevent: version 1.0.3
[  168.662093] device-mapper: ioctl: 4.24.0-ioctl (2013-01-15) initialised: 
dm-de...@redhat.com
[  168.866485] fuse init (API version 7.21)
[  168.912919] loop: module loaded
[  169.376587] EXT4-fs (sdc1): mounted filesystem with ordered data mode. Opts: 
errors=remount-ro
[  170.209318] RPC: Registered named UNIX socket transport module.
[  170.209322] RPC: Registered udp transport module.
[  170.209324] RPC: Registered tcp transport module.
[  170.209326] RPC: Registered tcp NFSv4.1 backchannel transport module.
[  170.212158] FS-Cache: Loaded
[  170.229349] Key type dns_resolver registered
[  170.250375] FS-Cache: Netfs 'nfs' registered for caching
[  170.293402] Installing knfsd (copyright (C) 1996 o...@monad.swb.de).
[  170.456600] sky2 :02:00.0 eth0: enabling interface
[  170.456707] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
[  171.659867] vboxdrv: Found 4 processor cores.
[  171.659993] vboxdrv: fAsync=0 offMin=0x230 offMax=0x23c0
[  171.660072] vboxdrv: TSC mode is 'synchronous', kernel timer mode is 
'normal'.
[  171.660074] vboxdrv: Successfully loaded version 4.2.10_Debian (interface 
0x001a0004).
[  172.424085] vboxpci: IOMMU not found (not registered)
[  172.480354] NFSD: Using /var/lib/nfs/v4recovery as the NFSv4 state recovery 
directory
[  172.480370] NFSD: starting 90-second grace period (net 8167b880)
[  172.501385] input: ACPI Virtual Keyboard Device as 
/devices/virtual/input/input8
[  173.424485] sky2 :02:00.0 eth0: Link is up at 100 Mbps, full duplex, 
flow control both
[  173.424501] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
[  180.985056] Netfilter messages via NETLINK v0.30.
[  181.184042] device eth0 entered promiscuous mode
[  181.867906] skge :05:02.0 eth1: enabling interface
[  181.871080] IPv6: ADDRCONF(NETDEV_UP): eth1: link is not ready
[  193.023365] tun: Universal TUN/TAP device driver, 1.6
[  193.023373] tun: (C) 1999-2004 Max Krasnyansky m...@qualcomm.com
[  193.402444] CUSE: failed to register chrdev region
[  193.402478] CUSE: failed to register chrdev region
[  193.402479] CUSE: failed to register chrdev region
[  193.728147] lp: driver loaded but no devices found
[  193.954725] ppdev: user-space parallel port driver

** Model information
sys_vendor: System manufacturer
product_name: P5Q-E
product_version: System Version
chassis_vendor: Chassis Manufacture
chassis_version: Chassis Version
bios_vendor: American Megatrends Inc.
bios_version: 0605   
board_vendor: ASUSTeK Computer INC.
board_name: P5Q-E
board_version: Rev 1.xx

** Loaded modules:
parport_pc
ppdev
lp
parport
cuse
tun
nfnetlink_queue
nfnetlink_log
nfnetlink
cpufreq_userspace

Bug#714497: More info: also found in RedHat

[Steve M. Robbins]

It seems this bug is reported at least four times to Fedora project, so it's 
likely an upstream issue.

Fedora references:

https://bugzilla.redhat.com/show_bug.cgi?id=964120
https://bugzilla.redhat.com/show_bug.cgi?id=967282
https://bugzilla.redhat.com/show_bug.cgi?id=975073
https://bugzilla.redhat.com/show_bug.cgi?id=976577


-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/201306291924.14122.st...@sumost.ca

Bug#713030: linux-image-3.9: [3.2-3.9] Warnings of CPU intel-microcode not found

[Eugenio M. Vigo]

OK, I see. This has been quite educational for me, so thank you for your
reply.

I think I'll submit a wishlist bug to the debian-installer so that the
user is notified during installation whether installing the CPU microcode
package is recommended or not. If data loss may occur without having the
updated microcode installed, I think it may be worth having the installer
telling you.



2013/6/22 Ben Hutchings b...@decadent.org.uk

 Control: tag -1 wontfix

 On Sat, 2013-06-22 at 01:13 +0200, Eugenio M. Vigo wrote:
  Hi,
  I want to get rid of the warning, mainly because I don't know whether
  it is of importance or not. My concern is that this didn't happen with
  the 3.2 kernel, so maybe there is a way to avoid installing that
  non-free package.

 Yes, there is a way to avoid installing that non-free package: do
 nothing.

 The kernel didn't previously actively try to load updated CPU microcode,
 and now it does.  I think this warning is correct behaviour: CPU bugs
 can cause data loss, and Debian promises not to hide problems.  And your
 CPU already runs non-free microcode, so installing the updated microcode
 package doesn't become any more dependent on it.  As always, you have
 the choice whether or not to install non-free software.  If you want a
 kernel that takes that choice away, there is always linux-libre.

 Ben.

 --
 Ben Hutchings
 Klipstein's 4th Law of Prototyping and Production:
 A fail-safe circuit will destroy
 others.

Bug#713030: linux-image-3.9: [3.2-3.9] Warnings of CPU intel-microcode not found

[Eugenio M. Vigo]

Package: src:linux
Version: 3.9.6-1
Severity: normal
File: linux-image-3.9

Dear Maintainer,

after the last kernel update from 3.2.x to 3.9.x in Debian Jessie, a warning
is shown upon boot up about some CPU microcode not being found. In my case, the
warning is the following one:

platform microcode: firmware: agent aborted loading intel-ucode/06-2a-07 (not
found?)

Other users seem to also have found this exactly after upgrading the kernel as I
did: http://forums.debian.net/viewtopic.php?f=5t=94248#p502708

Installing intel-microcode fixes this, but it's a non-free package. If the
previous 3.2 kernel didn't produce this warning, I think there should be some
way to avoid installing that package in order to properly load the required CPU
microcodes.

Thanks!

-- Package-specific info:
** Version:
Linux version 3.9-1-amd64 (debian-kernel@lists.debian.org) (gcc version 4.7.3 
(Debian 4.7.3-4) ) #1 SMP Debian 3.9.6-1

** Command line:
BOOT_IMAGE=/boot/vmlinuz-3.9-1-amd64 
root=UUID=28c225a1-305c-493e-9946-f2e52bf08193 ro quiet

** Tainted: C (1024)
 * Module from drivers/staging has been loaded.

** Kernel log:
[6.102980] ACPI Error: Method parse/execution failed [\_SB_.ATKD.WMNB] 
(Node 88011a2c7308), AE_ALREADY_EXISTS (20130117/psparse-537)
[6.103191] ACPI Error: [IIA0] Namespace lookup failure, AE_ALREADY_EXISTS 
(20130117/dsfield-211)
[6.103196] ACPI Error: Method parse/execution failed [\_SB_.ATKD.WMNB] 
(Node 88011a2c7308), AE_ALREADY_EXISTS (20130117/psparse-537)
[6.103262] ACPI: Marking method WMNB as Serialized because of 
AE_ALREADY_EXISTS error
[6.105062] uvcvideo: Found UVC 1.00 device ASUS USB2.0 Webcam (1bcf:2883)
[6.113276] asus-nb-wmi: probe of asus-nb-wmi failed with error -5
[6.122175] input: ASUS USB2.0 Webcam as 
/devices/pci:00/:00:1a.0/usb1/1-1/1-1.3/1-1.3:1.0/input/input6
[6.19] usbcore: registered new interface driver uvcvideo
[6.122230] USB Video Class driver (1.1.1)
[6.270669] ath: EEPROM regdomain: 0x60
[6.270672] ath: EEPROM indicates we should expect a direct regpair map
[6.270675] ath: Country alpha2 being used: 00
[6.270677] ath: Regpair used: 0x60
[6.272172] psmouse serio4: alps: Unknown ALPS touchpad: E7=10 00 64, EC=10 
00 64
[6.297336] ieee80211 phy0: Selected rate control algorithm 
'ath9k_rate_control'
[6.297587] ieee80211 phy0: Atheros AR9485 Rev:1 mem=0xc9000998, 
irq=17
[6.637161] cfg80211: World regulatory domain updated:
[6.637162] cfg80211:   (start_freq - end_freq @ bandwidth), 
(max_antenna_gain, max_eirp)
[6.637165] cfg80211:   (2402000 KHz - 2472000 KHz @ 4 KHz), (300 mBi, 
2000 mBm)
[6.637167] cfg80211:   (2457000 KHz - 2482000 KHz @ 2 KHz), (300 mBi, 
2000 mBm)
[6.637168] cfg80211:   (2474000 KHz - 2494000 KHz @ 2 KHz), (300 mBi, 
2000 mBm)
[6.637170] cfg80211:   (517 KHz - 525 KHz @ 4 KHz), (300 mBi, 
2000 mBm)
[6.637171] cfg80211:   (5735000 KHz - 5835000 KHz @ 4 KHz), (300 mBi, 
2000 mBm)
[6.720845] Console: switching to colour frame buffer device 170x48
[6.730685] i915 :00:02.0: fb0: inteldrmfb frame buffer device
[6.730689] i915 :00:02.0: registered panic notifier
[6.737077] acpi device:32: registered as cooling_device4
[6.744971] ACPI: Video Device [GFX0] (multi-head: yes  rom: no  post: no)
[6.745117] input: Video Bus as 
/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/LNXVIDEO:00/input/input7
[6.745284] [drm] Initialized i915 1.6.0 20080730 for :00:02.0 on minor 0
[6.745487] snd_hda_intel :00:1b.0: irq 45 for MSI/MSI-X
[6.769535] psmouse serio4: elantech: assuming hardware version 4 (with 
firmware version 0x361f03)
[6.783204] psmouse serio4: elantech: Synaptics capabilities query result 
0x10, 0x14, 0x0e.
[6.853920] input: ETPS/2 Elantech Touchpad as 
/devices/platform/i8042/serio4/input/input8
[6.954965] input: HDA Intel PCH HDMI/DP,pcm=3 as 
/devices/pci:00/:00:1b.0/sound/card0/input9
[6.955174] input: HDA Intel PCH Mic as 
/devices/pci:00/:00:1b.0/sound/card0/input10
[6.955382] input: HDA Intel PCH Front Headphone as 
/devices/pci:00/:00:1b.0/sound/card0/input11
[7.816443] [drm] Enabling RC6 states: RC6 on, RC6p off, RC6pp off
[9.154956] Adding 7812092k swap on /dev/sda3.  Priority:-1 extents:1 
across:7812092k 
[9.185143] EXT4-fs (sda2): re-mounted. Opts: (null)
[9.555327] EXT4-fs (sda2): re-mounted. Opts: errors=remount-ro
[9.772755] fuse init (API version 7.21)
[9.818978] loop: module loaded
[   11.098949] FAT-fs (sda1): utf8 is not a recommended IO charset for FAT 
filesystems, filesystem will be case sensitive!
[   11.318707] EXT4-fs (sda4): mounted filesystem with ordered data mode. Opts: 
(null)
[   11.958745] ip_tables: (C) 2000-2006 Netfilter Core Team
[   12.019868] nf_conntrack version 0.5.0 (16384 buckets, 65536 max)
[   12.152283] ip6_tables: (C) 2000-2006 Netfilter Core Team
[ 

Bug#713030: linux-image-3.9: [3.2-3.9] Warnings of CPU intel-microcode not found

[Eugenio M. Vigo]

Hi,
I want to get rid of the warning, mainly because I don't know whether it is
of importance or not. My concern is that this didn't happen with the 3.2
kernel, so maybe there is a way to avoid installing that non-free package.
Cheers!
El 22/06/2013 00:47, Ben Hutchings b...@decadent.org.uk escribió:

 On Sat, 2013-06-22 at 00:26 +0200, Eugenio M. Vigo wrote:
  after the last kernel update from 3.2.x to 3.9.x in Debian Jessie, a
 warning
  is shown upon boot up about some CPU microcode not being found. In my
 case, the
  warning is the following one:
 
  platform microcode: firmware: agent aborted loading intel-ucode/06-2a-07
 (not
  found?)
 
  Other users seem to also have found this exactly after upgrading the
 kernel as I
  did: http://forums.debian.net/viewtopic.php?f=5t=94248#p502708
 
  Installing intel-microcode fixes this, but it's a non-free package. If
 the
  previous 3.2 kernel didn't produce this warning, I think there should be
 some
  way to avoid installing that package in order to properly load the
 required CPU
  microcodes.

 I don't understand.  You want to load the microcode update, which is
 non-free, without installing a non-free package?  Or you just want the
 warning to go away?

 Ben.

 --
 Ben Hutchings
 Klipstein's 4th Law of Prototyping and Production:
 A fail-safe circuit will destroy
 others.

Bug#711202: linux-image-3.2.0-4-amd64: e1000e Detected Hardware Unit Hang only on kernel 3.2

[Jose M Calhariz]

Package: src:linux
Version: 3.2.41-2+deb7u2
Severity: normal

Dear Maintainer,
*** Please consider answering these questions, where appropriate ***

   * What led up to the situation?

 The openafs fileserver, under normal workload, the kernel says:

Jun  4 13:33:25 tania kernel: e1000e :06:00.0: eth0: Detected Hardware Unit 
Hang:
Jun  4 13:33:25 tania kernel:  TDH  93
Jun  4 13:33:25 tania kernel:  TDT  96
Jun  4 13:33:25 tania kernel:  next_to_use  96
Jun  4 13:33:25 tania kernel:  next_to_clean92
Jun  4 13:33:25 tania kernel: buffer_info[next_to_clean]:
Jun  4 13:33:25 tania kernel:  time_stamp   10532d958
Jun  4 13:33:25 tania kernel:  next_to_watch93
Jun  4 13:33:25 tania kernel:  jiffies  10532db0b
Jun  4 13:33:25 tania kernel:  next_to_watch.status 0
Jun  4 13:33:25 tania kernel: MAC Status 80080783
Jun  4 13:33:25 tania kernel: PHY Status 796d
Jun  4 13:33:25 tania kernel: PHY 1000BASE-T Status  7800
Jun  4 13:33:25 tania kernel: PHY Extended Status3000
Jun  4 13:33:25 tania kernel: PCI Status 10
Jun  4 13:33:27 tania kernel: e1000e :06:00.0: eth0: Detected Hardware Unit 
Hang:
Jun  4 13:33:27 tania kernel:  TDH  93
Jun  4 13:33:27 tania kernel:  TDT  96
Jun  4 13:33:27 tania kernel:  next_to_use  96
Jun  4 13:33:27 tania kernel:  next_to_clean92
Jun  4 13:33:27 tania kernel: buffer_info[next_to_clean]:
Jun  4 13:33:27 tania kernel:  time_stamp   10532d958
Jun  4 13:33:27 tania kernel:  next_to_watch93
Jun  4 13:33:27 tania kernel:  jiffies  10532dcff
Jun  4 13:33:27 tania kernel:  next_to_watch.status 0
Jun  4 13:33:27 tania kernel: MAC Status 80080783
Jun  4 13:33:27 tania kernel: PHY Status 796d
Jun  4 13:33:27 tania kernel: PHY 1000BASE-T Status  7800
Jun  4 13:33:27 tania kernel: PHY Extended Status3000
Jun  4 13:33:27 tania kernel: PCI Status 10
Jun  4 13:33:29 tania kernel: e1000e :06:00.0: eth0: Detected Hardware Unit 
Hang:
Jun  4 13:33:29 tania kernel:  TDH  93
Jun  4 13:33:29 tania kernel:  TDT  96
Jun  4 13:33:29 tania kernel:  next_to_use  96
Jun  4 13:33:29 tania kernel:  next_to_clean92
Jun  4 13:33:29 tania kernel: buffer_info[next_to_clean]:
Jun  4 13:33:29 tania kernel:  time_stamp   10532d958
Jun  4 13:33:29 tania kernel:  next_to_watch93
Jun  4 13:33:29 tania kernel:  jiffies  10532def3
Jun  4 13:33:29 tania kernel:  next_to_watch.status 0
Jun  4 13:33:29 tania kernel: MAC Status 80080783
Jun  4 13:33:29 tania kernel: PHY Status 796d
Jun  4 13:33:29 tania kernel: PHY 1000BASE-T Status  7800
Jun  4 13:33:29 tania kernel: PHY Extended Status3000
Jun  4 13:33:29 tania kernel: PCI Status 10
Jun  4 13:33:31 tania kernel: e1000e :06:00.0: eth0: Detected Hardware Unit 
Hang:
Jun  4 13:33:31 tania kernel:  TDH  93
Jun  4 13:33:31 tania kernel:  TDT  96
Jun  4 13:33:31 tania kernel:  next_to_use  96
Jun  4 13:33:31 tania kernel:  next_to_clean92
Jun  4 13:33:31 tania kernel: buffer_info[next_to_clean]:
Jun  4 13:33:31 tania kernel:  time_stamp   10532d958
Jun  4 13:33:31 tania kernel:  next_to_watch93
Jun  4 13:33:31 tania kernel:  jiffies  10532e0e7
Jun  4 13:33:31 tania kernel:  next_to_watch.status 0
Jun  4 13:33:31 tania kernel: MAC Status 80080783
Jun  4 13:33:31 tania kernel: PHY Status 796d
Jun  4 13:33:31 tania kernel: PHY 1000BASE-T Status  7800
Jun  4 13:33:31 tania kernel: PHY Extended Status3000
Jun  4 13:33:31 tania kernel: PCI Status 10
Jun  4 13:33:31 tania kernel: e1000e :06:00.0: eth0: Reset adapter
Jun  4 13:33:35 tania kernel: e1000e: eth0 NIC Link is Up 1000 Mbps Full 
Duplex, Flow Control: None


This bug is diferent than the bug 657689.  This bug is not seen on older Debian 
stable 
kernels, from squeeze or etch.  As a workaround the kernel was booted with 
option  pcie_aspm=off.

The kernel taint is from the openafs client module.


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

As a workaround the kernel was booted with option  pcie_aspm=off, but the 
results are the 
same.  The kernel information is from the boot with pcie_aspm=off.



-- Package-specific info:
** Version:
Linux version 3.2.0-4-amd64 (debian-kernel@lists.debian.org) (gcc version 4.6.3 
(Debian 4.6.3-14) ) #1 SMP Debian 3.2.41-2+deb7u2

** Command line:
BOOT_IMAGE=/boot/vmlinuz-3.2.0-4-amd64 
root=UUID=286f18e7-33e5-4598-a37f-139157b0207d ro console=ttyS1,115200n8 
console=tty0 printk.time=n pcie_aspm=off

** Tainted: PWO (4609)
 * Proprietary module has been loaded.
 * Taint on warning.
 * Out-of-tree module has been loaded.

** Kernel log:
  next_to_watch.status 0
MAC Status