Processed: severity of 878556 is normal
Processing commands for cont...@bugs.debian.org: > severity 878556 normal Bug #878556 [linux-image-4.9.0-4-amd64] tpm tpm0: A TPM error (7) occurred attempting to read a pcr value Severity set to 'normal' from 'important' > thanks Stopping processing here. Please contact me if you need assistance. -- 878556: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=878556 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#878614: linux-image-4.13.0-1-amd64: unexpected IRQ trap at vector e8 on Intel NUC H26998-401
Package: src:linux Version: 4.13.4-1 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 *** Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit From: Daniel Kahn Gillmor To: Debian Bug Tracking System Subject: linux-image-4.13.0-1-amd64: unexpected IRQ trap at vector e8 on Intel NUC H26998-401 Bcc: Daniel Kahn Gillmor Package: src:linux Version: 4.13.4-1 Severity: important Trying to boot this machine into 4.13.0-1-amd64 results in several kernel messages like: unexpected IRQ trap at vector e8 per second, and basic system services take ages to start (including journald, which means i don't have a clear log of the error messages at the moment). rebooting into 4.11.0-2-amd64 produces no such error. The machine is already running irqbalance 1.1.0-2.3, fwiw. Let me know if there's more information i can give you (or other kernels i should try) that would help to narrow this down. --dkg -- Package-specific info: ** Kernel log: boot messages should be attached ** Model information sys_vendor: \xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff product_name: \xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff product_version: \xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff chassis_vendor: \xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff chassis_version: \xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff bios_vendor: Intel Corp. bios_version: TYBYT10H.86A.0019.2014.0327.1516 board_vendor: Intel Corporation board_name: DE3815TYKH board_version: H26998-401 ** PCI devices: 00:00.0 Host bridge [0600]: Intel Corporation Atom Processor Z36xxx/Z37xxx Series SoC Transaction Register [8086:0f00] (rev 0c) Subsystem: Intel Corporation Atom Processor Z36xxx/Z37xxx Series SoC Transaction Register [8086:2056] 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:13.0 SATA controller [0106]: Intel Corporation Atom Processor E3800 Series SATA AHCI Controller [8086:0f23] (rev 0c) (prog-if 01 [AHCI 1.0]) Subsystem: Intel Corporation Atom Processor E3800 Series SATA AHCI Controller [8086:2056] 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: ahci Kernel modules: ahci 00:14.0 USB controller [0c03]: Intel Corporation Atom Processor Z36xxx/Z37xxx, Celeron N2000 Series USB xHCI [8086:0f35] (rev 0c) (prog-if 30 [XHCI]) Subsystem: Intel Corporation Atom Processor Z36xxx/Z37xxx, Celeron N2000 Series USB xHCI [8086:2056] 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:17.0 SD Host controller [0805]: Intel Corporation Atom Processor E3800 Series eMMC 4.5 Controller [8086:0f50] (rev 0c) (prog-if 01) 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: sdhci-pci Kernel modules: sdhci_pci 00:18.0 DMA controller [0801]: Intel Corporation Atom Processor Z36xxx/Z37xxx Series LPIO2 DMA Controller [8086:0f40] (rev 0c) (prog-if 02 [EISA DMA]) Subsystem: Intel Corporation Atom Processor Z36xxx/Z37xxx Series LPIO2 DMA Controller [8086:0f40] Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 00:18.1 Serial bus controller [0c80]: Intel Corporation Atom Processor Z36xxx/Z37xxx Series LPIO2 I2C Controller #1 [8086:0f41] (rev 0c) Subsystem: Intel Corporation Atom Processor Z36xxx/Z37xxx Series LPIO2 I2C Controller [8086:0f41] Control: I/O- Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop-
Processed: affects 878216
Processing commands for cont...@bugs.debian.org: > affects 878216 + release.debian.org Bug #878216 [src:linux] Bug relating linux-image-3.16.0-4-amd64_3.16.48-1_amd64.deb and hyper-v gen2 vm Added indication that 878216 affects release.debian.org > thanks Stopping processing here. Please contact me if you need assistance. -- 878216: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=878216 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#868082: linux-image-4.11.0-1-686: fails to boot on i386 (Soekris net5501)
On Thu, 12 Oct 2017 02:12:45 +0100 Ben Hutchings wrote: > On Wed, 2017-10-11 at 23:30 +0200, Francesco Poli wrote: > [...] > > For the record, I have just tried with the latest Linux kernel in > > testing: > > > > Loading Linux 4.13.0-1-686 ... > > Loading initial ramdisk ... > > > > > > Another boot failure... > > > > Is there any progress in the bug investigation? > > I don't think anyone's investigating this, I'm afraid. Huh? What was point of having me bisecting among versions uploaded to Debian experimental, then? > > Going back to the lack of output with 'earlyprintk=ttyS0', I had a > check and the default bit rate for that is 9600(!) whereas I (and maybe > you) would have expected 115200. So perhaps you could try > 'earlyprintk=ttyS0,115200' (or whichever bit rate you want). I have just tried with 'earlyprintk=ttyS0,19200,n8' (and without 'quiet'), since I have 'console=ttyS0,19200,n8' among the normal parameters. Unfortunately, I still get no useful debug output at all: Booting a command list Loading Linux 4.13.0-1-686 ... Loading initial ramdisk ... -- http://www.inventati.org/frx/ There's not a second to spare! To the laboratory! . Francesco Poli . GnuPG key fpr == CA01 1147 9CD2 EFDF FB82 3925 3E1C 27E1 1F69 BFFE pgpfgefM4u60L.pgp Description: PGP signature
Bug#878556: tpm tpm0: A TPM error (7) occurred attempting to read a pcr value
Control: tags -1 + moreinfo Hi On Sat, Oct 14, 2017 at 05:30:05PM +0200, Narcis Garcia wrote: > Package: linux-image-4.9.0-4-amd64 > Version: 4.9.30-2+deb9u5 > Severity: important > > $ sudo journalctl -b -p err > ... kernel: acpi LNXCPU:00: Invalid PBLK length [7] > ... kernel: acpi LNXCPU:01: Invalid PBLK length [7] > ... kernel: ACPI BIOS Error (bug): \_SB.PCI0._OSC: Excess arguments - > ASL declared 5, ACPI requires 4 (20160831/nsarguments-189) > ... kernel: ACPI Error: [CAPD] Namespace lookup failure, > AE_ALREADY_EXISTS (20160831/dsfield-211) > ... kernel: ACPI Error: Method parse/execution failed [\_SB.PCI0._OSC] > (Node 956f530aeaa0), AE_ALREADY_EXISTS (20160831/psparse-543) > ... kernel: tpm tpm0: A TPM error (7) occurred attempting to read a pcr > value > ... kernel: tpm tpm0: A TPM error (7) occurred attempting to read a pcr > value > > "ACPI guys found the problem": > http://lkml.iu.edu/hypermail/linux/kernel/1704.1/04255.html I'm unsure this is really the same problem. The above mentioned issue in the link was introduced by: 57707a9a7780fab426b8ae9b4c7b65b912a748b3 (v4.11-rc1) and then reverted in 1315f01632da417f1f27074bc6631df8eaf223bb (v4.11-rc7) AFAICT, this was neither backported to 4.9, nor have we applied the patch in stretch. I cannot give any more help/hints, but wanted to point the above out. Regards, Salvatore > > -- > > > __ > I'm using this express-made address because personal addresses aren't > masked enough at this mail public archive. Public archive administrator > should fix this against automated addresses collectors.
Processed: Re: Bug#878556: tpm tpm0: A TPM error (7) occurred attempting to read a pcr value
Processing control commands: > tags -1 + moreinfo Bug #878556 [linux-image-4.9.0-4-amd64] tpm tpm0: A TPM error (7) occurred attempting to read a pcr value Added tag(s) moreinfo. -- 878556: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=878556 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#878556: tpm tpm0: A TPM error (7) occurred attempting to read a pcr value
Package: linux-image-4.9.0-4-amd64 Version: 4.9.30-2+deb9u5 Severity: important $ sudo journalctl -b -p err ... kernel: acpi LNXCPU:00: Invalid PBLK length [7] ... kernel: acpi LNXCPU:01: Invalid PBLK length [7] ... kernel: ACPI BIOS Error (bug): \_SB.PCI0._OSC: Excess arguments - ASL declared 5, ACPI requires 4 (20160831/nsarguments-189) ... kernel: ACPI Error: [CAPD] Namespace lookup failure, AE_ALREADY_EXISTS (20160831/dsfield-211) ... kernel: ACPI Error: Method parse/execution failed [\_SB.PCI0._OSC] (Node 956f530aeaa0), AE_ALREADY_EXISTS (20160831/psparse-543) ... kernel: tpm tpm0: A TPM error (7) occurred attempting to read a pcr value ... kernel: tpm tpm0: A TPM error (7) occurred attempting to read a pcr value "ACPI guys found the problem": http://lkml.iu.edu/hypermail/linux/kernel/1704.1/04255.html -- __ I'm using this express-made address because personal addresses aren't masked enough at this mail public archive. Public archive administrator should fix this against automated addresses collectors.
Regression in linux in jessie-proposed-updates
Control: reassign -1 src:linux 3.16.48-1 Control: severity -1 grave On Wed, Oct 11, 2017 at 08:45:14AM +, Cristiano Casella wrote: > Package: linux-image > > Version: 3.16.0-4-amd64_3.16.48-1_amd64.deb > > > Hi, > > we are an hosting provider and we are offering to our customers virtual > machine on Microsoft Hyper-v hypervisor. > > > Upgrading our vm with Debian 8 (also just installed) to last version of > linux-image package (linux-image-3.16.0-4-amd64_3.16.48-1_amd64.deb) the > virtual machines can't boot anymore. > > > I attached to this email the two kind of error that we can get in the console. > > > Looking at the changelog > (https://tracker.debian.org/media/packages/l/linux/changelog-3.16.48-1) I > suspect that this changes could be involved in this bug: > > > - [x86] scsi: storvsc: use tagged SRB requests if supported by the device > - [x86] scsi: storvsc: Fix a bug in the handling of SRB status flags > - [x86] scsi: storvsc: properly handle SRB_ERROR when sense message is > present > - [x86] scsi: storvsc: properly set residual data length on errors > > We can provide you all test environments needed or proceede with your support > for a kernel bisect to find the specific error. > > > This bug potentially could brake all our customer virtual machines using a > Debian 8 on our hyper-v platform. Thanks for your report. I'm adjusting the severity and reassign the bug to the correct place, to make people aware that this regression shouldn't enter the next point release. > Thanks for your support > > Cordiali Saluti / Best Regards > > Cristiano Casella Thanks for your report Adrian -- "Is there not promise of rain?" Ling Tan asked suddenly out of the darkness. There had been need of rain for many days. "Only a promise," Lao Er said. Pearl S. Buck - Dragon Seed
Processed: Regression in linux in jessie-proposed-updates
Processing control commands: > reassign -1 src:linux 3.16.48-1 Bug #878216 [linux-image] Bug relating linux-image-3.16.0-4-amd64_3.16.48-1_amd64.deb and hyper-v gen2 vm Warning: Unknown package 'linux-image' Bug reassigned from package 'linux-image' to 'src:linux'. Ignoring request to alter found versions of bug #878216 to the same values previously set Ignoring request to alter fixed versions of bug #878216 to the same values previously set Bug #878216 [src:linux] Bug relating linux-image-3.16.0-4-amd64_3.16.48-1_amd64.deb and hyper-v gen2 vm Marked as found in versions linux/3.16.48-1. > severity -1 grave Bug #878216 [src:linux] Bug relating linux-image-3.16.0-4-amd64_3.16.48-1_amd64.deb and hyper-v gen2 vm Severity set to 'grave' from 'normal' -- 878216: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=878216 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#877911: Please set CONFIG_BRCMFMAC_SDIO=y for WiFi on the Raspberry Pi 3
[Michael Stapelberg] > Please include CONFIG_BRCMFMAC_SDIO=y in the next upload for arm64. Having the default Debian kernel work out of the box with the WIFI card on RPi 3 would help me a lot. Is there anything technical blocking this from happening? -- Happy hacking Petter Reinholdtsen
Re: [m68k]: PULL: Build uncompressed kernel image by default
Hi Ben! Sorry for bothering you on a Saturday, but can you make sure this change gets merged before the next upload? Thanks, Adrian > On Oct 10, 2017, at 8:02 AM, John Paul Adrian Glaubitz > wrote: > > Hi Ben! > > I have changed the type of the kernel image to be uncompressed on > m68k as the bootloaders on at least Amiga and Atari systems have > problems decompressing large kernels. > > I will update debian-installer once you have merged my change, please > pull from the known location [1]. > > Thanks, > Adrian > >> [1] https://github.com/glaubitz/linux-debian > > -- > .''`. John Paul Adrian Glaubitz > : :' : Debian Developer - glaub...@debian.org > `. `' Freie Universitaet Berlin - glaub...@physik.fu-berlin.de > `-GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913