Bug#854113: linux-image-4.9.0-0.bpo.1-amd64-unsigned: ACPI Error : _SB_.ALIB and SB.PCI0.VGA.ATC0 and s, Namespace lookup failure, AE_NOT_FOUND
Package: src:linux Version: 4.9.2-2~bpo8+1 Severity: normal Dear Maintainer, At boot, errors are logged : ACPI Error: [\_SB_.ALIB] Namespace lookup failure, AE_NOT_FOUND (20160831/psargs-359) [ 11.699467] ACPI Error: Method parse/execution failed [\_SB.PCI0.VGA.ATC0] (Node 989b7acc4078), AE_NOT_FOUND (20160831/psparse-543) [ 11.699548] ACPI Error: Method parse/execution failed [\_SB.PCI0.VGA.ATCS] (Node 989b7acc44d8), AE_NOT_FOUND (20160831/psparse-543) 4.8 kernel does not have these first errors. sp5100_tco: SP5100/SB800 TCO WatchDog Timer Driver v0.05 sp5100_tco: PCI Vendor ID: 0x1022, Device ID: 0x780b, Revision ID: 0x16 sp5100_tco: I/O address 0x0cd6 already in use [Firmware Bug]: AMD-Vi: IOAPIC[0] not in IVRS table [Firmware Bug]: AMD-Vi: No southbridge IOAPIC found AMD-Vi: Disabling interrupt remapping 4.8 have these last errors. Another machine with another recent Radeon chipset on MSI motherboard have the same errors but a third machine with an old Intel Atom CPU does not have errors with 4.8 or 4.9 kernels for this last machine. Regards. -- Package-specific info: ** Version: Linux version 4.9.0-0.bpo.1-amd64 (debian-kernel@lists.debian.org) (gcc version 4.9.2 (Debian 4.9.2-10) ) #1 SMP Debian 4.9.2-2~bpo8+1 (2017-01-26) ** Command line: BOOT_IMAGE=/boot/vmlinuz-4.9.0-0.bpo.1-amd64 root=UUID=5ebf0513-8146-4896-b3bc-9a9923f0cf81 ro quiet ** Tainted: E (8192) * Unsigned module has been loaded. ** Kernel log: [ 10.423394] saa7134: i2c eeprom 40: ff 07 00 c0 86 ff 01 03 ff ff ff ff ff ff ff ff [ 10.423395] saa7134: i2c eeprom 50: 0c 22 17 36 03 0b df bb ff ff ff ff ff ff ff ff [ 10.423396] saa7134: i2c eeprom 60: 03 03 19 71 fb ff ff ff ff ff ff ff ff ff ff ff [ 10.423396] saa7134: i2c eeprom 70: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff [ 10.423397] saa7134: i2c eeprom 80: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff [ 10.423397] saa7134: i2c eeprom 90: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff [ 10.423398] saa7134: i2c eeprom a0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff [ 10.423398] saa7134: i2c eeprom b0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff [ 10.423398] saa7134: i2c eeprom c0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff [ 10.423399] saa7134: i2c eeprom d0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff [ 10.423399] saa7134: i2c eeprom e0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff [ 10.423400] saa7134: i2c eeprom f0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff [ 10.459260] saa7134: saa7134[0] Can't determine tuner type 7 from EEPROM [ 10.459266] saa7134: saa7134[0] Tuner type is 63 [ 10.459409] saa7134[0]: Unable to enable IF of the tuner. [ 10.483826] saa7134: saa7134[0]: registered device video1 [v4l2] [ 10.483875] saa7134: saa7134[0]: registered device vbi1 [ 10.483918] saa7134: saa7134[0]: registered device radio1 [ 10.644617] Adding 2047996k swap on /dev/sdb1. Priority:-1 extents:1 across:2047996k FS [ 10.685319] saa7134_dvb: dvb_init() allocating 1 frontend [ 10.806293] DVB: Unable to find symbol tda10046_attach() [ 10.806303] saa7134_dvb: saa7134[0]/dvb: frontend initialization failed [ 10.827292] [drm] ib test on ring 6 succeeded [ 10.941001] Adding 1615868k swap on /dev/sda2. Priority:-2 extents:1 across:1615868k FS [ 11.018654] saa7134_alsa: saa7134 ALSA driver for DMA sound loaded [ 11.018687] saa7134_alsa: saa7134[0]/alsa: saa7134[0] at 0xfe80 irq 20 registered as card 5 [ 11.339331] [drm] ib test on ring 7 succeeded [ 11.339892] [drm] Radeon Display Connectors [ 11.339894] [drm] Connector 0: [ 11.339895] [drm] HDMI-A-1 [ 11.339895] [drm] HPD1 [ 11.339897] [drm] DDC: 0x6530 0x6530 0x6534 0x6534 0x6538 0x6538 0x653c 0x653c [ 11.339898] [drm] Encoders: [ 11.339899] [drm] DFP1: INTERNAL_UNIPHY2 [ 11.339899] [drm] Connector 1: [ 11.339900] [drm] VGA-1 [ 11.339900] [drm] HPD2 [ 11.339902] [drm] DDC: 0x6540 0x6540 0x6544 0x6544 0x6548 0x6548 0x654c 0x654c [ 11.339903] [drm] Encoders: [ 11.339903] [drm] CRT1: INTERNAL_UNIPHY2 [ 11.339904] [drm] CRT1: NUTMEG [ 11.339904] [drm] Connector 2: [ 11.339905] [drm] DVI-D-1 [ 11.339905] [drm] HPD3 [ 11.339907] [drm] DDC: 0x6550 0x6550 0x6554 0x6554 0x6558 0x6558 0x655c 0x655c [ 11.339907] [drm] Encoders: [ 11.339908] [drm] DFP2: INTERNAL_UNIPHY [ 11.593239] [drm] fb mappable at 0xC03DA000 [ 11.593242] [drm] vram apper at 0xC000 [ 11.593243] [drm] size 8294400 [ 11.593244] [drm] fb depth is 24 [ 11.593244] [drm]pitch is 7680 [ 11.593334] fbcon: radeondrmfb (fb0) is primary device [ 11.680711] Console: switching to colour frame buffer device 240x67 [ 11.684855] radeon :00:01.0: fb0: radeondrmfb frame buffer device [ 11.699396] ACPI Error: [\_SB_.ALIB] Namespace lookup failure, AE_NOT_FOUND (20160831/psargs-359) [ 11.699467] ACPI Error: Method parse/execution failed [\_SB.PCI0.VGA.ATC0] (N
Re: Bug#852395: unblock: gssproxy/0.5.1-2
Control: tags -1 moreinfo CC'ing the maintainer of nfs-common and the reporter of #848306. Robbie Harwood: > Package: release.debian.org > Severity: normal > User: release.debian@packages.debian.org > Usertags: unblock > > Please unblock package gssproxy > > gssproxy has been 10 days in unstable, and allowing it to migrate will fix > bug#848306 (severity: important) in nfs-common. gssproxy is a new package in > unstable (so no debdiff is included), and would have made the freeze had I not > made a mistake documenting copyright. > > Thanks. > > unblock gssproxy/0.5.1-2 > > [...] Hi, Thanks for bringing this up. Is this migration from rpc.svcgssd to gssproxy so important (release critical) that it ought to be granted an exception? And if so, why is it that important (despite #848306 not being release critical)? Thanks, ~Niels
Re: Bug#852395: unblock: gssproxy/0.5.1-2
On 04/02/17 10:50, Niels Thykier wrote: > Control: tags -1 moreinfo > > CC'ing the maintainer of nfs-common and the reporter of #848306. > > Robbie Harwood: >> Package: release.debian.org >> Severity: normal >> User: release.debian@packages.debian.org >> Usertags: unblock >> >> Please unblock package gssproxy >> >> gssproxy has been 10 days in unstable, and allowing it to migrate will fix >> bug#848306 (severity: important) in nfs-common. gssproxy is a new package in >> unstable (so no debdiff is included), and would have made the freeze had I >> not >> made a mistake documenting copyright. >> >> Thanks. >> >> unblock gssproxy/0.5.1-2 >> >> [...] > Hi, > > Thanks for bringing this up. > > Is this migration from rpc.svcgssd to gssproxy so important (release > critical) that it ought to be granted an exception? And if so, why is it > that important (despite #848306 not being release critical)? Upstream is not really supporting rpc.svcgssd any more, they actually disabled it in the build so people can still have it as a transitional measure in stretch. People shouldn't be using it in any new installations. Offering them gssproxy is a very sensible thing to do. Regards, Daniel
Re: Bug#852395: unblock: gssproxy/0.5.1-2
Daniel Pocock: > On 04/02/17 10:50, Niels Thykier wrote: >> [...] >> Hi, >> >> Thanks for bringing this up. >> >> Is this migration from rpc.svcgssd to gssproxy so important (release >> critical) that it ought to be granted an exception? And if so, why is it >> that important (despite #848306 not being release critical)? > > Upstream is not really supporting rpc.svcgssd any more, they actually > disabled it in the build so people can still have it as a transitional > measure in stretch. > > People shouldn't be using it in any new installations. Offering them > gssproxy is a very sensible thing to do. > > Regards, > > Daniel > Ok, follow up questions: * Do you have an upstream reference to the state of rpc.svcgssd? * Can we provide both rpc.svcgssd and gssproxy in Debian (with the admin choosing) or is it an "xor"? * If this package is unblocked, are there any changes needed in nfs-common needed to support gssproxy? (source upload, binNMU or "just works with no further changes") Thanks, ~Niels
Bug#854113: linux-image-4.9.0-0.bpo.1-amd64-unsigned: ACPI Error : _SB_.ALIB and SB.PCI0.VGA.ATC0 and s,
I forgot to say that with the 4.9 kernel, I cannot power off my machine with the poweroff command line. Instead, the system restart. -- Alain Rpnpif
Bug#854143: ncq timeout causes system hangs for seconds
Package: linux
Version: Linux n9-016-075 3.16.0-4-amd64 #1 SMP Debian 3.16.7-ckt25-1
(2016-03-06) x86_64 GNU/Linux
debian_version: 8.4
*dmesg output:*
*[Fri Feb 3 16:04:01 2017] ata7.00: exception Emask 0x0 SAct
0x7fff SErr 0x0 action 0x6 frozen
[Fri Feb 3 16:04:01 2017] ata7.00: failed command: READ FPDMA QUEUED
[Fri Feb 3 16:04:01 2017] ata7.00: cmd
60/18:00:a0:4d:55/00:00:0d:00:00/40 tag 0 ncq 12288 in
res 40/00:01:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
[Fri Feb 3 16:04:01 2017] ata7.00: status: { DRDY }
[Fri Feb 3 16:04:01 2017] ata7.00: failed command: READ FPDMA QUEUED
[Fri Feb 3 16:04:01 2017] ata7.00: cmd
60/18:08:f0:c7:e2/00:00:1b:00:00/40 tag 1 ncq 12288 in
res 40/00:01:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
[Fri Feb 3 16:04:01 2017] ata7.00: status: { DRDY }*
*fstab*
*UUID=c3b48986-0dbe-11e6-8cb0-0cc47ac4c4b2 /data01 ext4noatime,discard
0 0*
*hdparm -I /dev/sdc*
*/dev/sdc:
ATA device, with non-removable media
Model Number: Samsung SSD 850 PRO 1TB
Serial Number: S226NXAG802073V
Firmware Revision: EXM02B6Q
Transport: Serial, ATA8-AST, SATA 1.0a, SATA II Extensions,
SATA Rev 2.5, SATA Rev 2.6, SATA Rev 3.0
Standards:
Used: unknown (minor revision code 0x0039)
Supported: 9 8 7 6 5
Likely used: 9
Configuration:
Logical max current
cylinders 16383 16383
heads 16 16
sectors/track 63 63
--
CHS current addressable sectors: 16514064
LBAuser addressable sectors: 268435455
LBA48 user addressable sectors: 2000409264
Logical Sector size: 512 bytes
Physical Sector size: 512 bytes
Logical Sector-0 offset: 0 bytes
device size with M = 1024*1024: 976762 MBytes
device size with M = 1000*1000: 1024209 MBytes (1024 GB)
cache/buffer size = unknown
Nominal Media Rotation Rate: Solid State Device
Capabilities:
LBA, IORDY(can be disabled)
Queue depth: 32
Standby timer values: spec'd by Standard, no device specific minimum
R/W multiple sector transfer: Max = 1 Current = 1
DMA: mdma0 mdma1 mdma2 udma0 udma1 udma2 udma3 udma4 udma5 *udma6
Cycle time: min=120ns recommended=120ns
PIO: pio0 pio1 pio2 pio3 pio4
Cycle time: no flow control=120ns IORDY flow control=120ns
Commands/features:
Enabled Supported:
*SMART feature set
Security Mode feature set
*Power Management feature set
*Write cache
*Look-ahead
*Host Protected Area feature set
*WRITE_BUFFER command
*READ_BUFFER command
*NOP cmd
*DOWNLOAD_MICROCODE
SET_MAX security extension
*48-bit Address feature set
*Device Configuration Overlay feature set
*Mandatory FLUSH_CACHE
*FLUSH_CACHE_EXT
*SMART error logging
*SMART self-test
*General Purpose Logging feature set
*WRITE_{DMA|MULTIPLE}_FUA_EXT
*64-bit World wide name
Write-Read-Verify feature set
*WRITE_UNCORRECTABLE_EXT command
*{READ,WRITE}_DMA_EXT_GPL commands
*Segmented DOWNLOAD_MICROCODE
*Gen1 signaling speed (1.5Gb/s)
*Gen2 signaling speed (3.0Gb/s)
*Gen3 signaling speed (6.0Gb/s)
*Native Command Queueing (NCQ)
*Phy event counters
*unknown 76[15]
*DMA Setup Auto-Activate optimization
Device-initiated interface power management
*Asynchronous notification (eg. media change)
*Software settings preservation
unknown 78[8]
*SMART Command Transport (SCT) feature set
*SCT Write Same (AC2)
*SCT Error Recovery Control (AC3)
*SCT Features Control (AC4)
*SCT Data Tables (AC5)
*reserved 69[4]
*DOWNLOAD MICROCODE DMA command
*SET MAX SETPASSWORD/UNLOCK DMA commands
*WRITE BUFFER DMA command
*READ BUFFER DMA command
*Data Set Management TRIM supported (limit 8 blocks)
Security:
Master password revision code = 65534
supported
not enabled
not locked
frozen
not expired: security count
supported: enhanced erase
2min for SECURITY ERASE UNIT. 2min for ENHANCED SECURITY ERASE UNIT.
Logical Unit WWN Device Identifier: 500253884007fa79
NAA : 5
IEEE OUI: 002538
Uniq
Processed: found 854143 in 3.16.7-ckt25-1
Processing commands for cont...@bugs.debian.org: > found 854143 3.16.7-ckt25-1 Bug #854143 [linux] ncq timeout causes system hangs for seconds There is no source info for the package 'linux' at version '3.16.7-ckt25-1' with architecture '' Unable to make a source version for version '3.16.7-ckt25-1' Marked as found in versions 3.16.7-ckt25-1. > thanks Stopping processing here. Please contact me if you need assistance. -- 854143: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=854143 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#853151: dpkg status changes prior to seeing this problem
From the logwatch email the next day. - dpkg status changes Begin Installed: linux-image-4.9.0-0.bpo.1-amd64:amd64 4.9.2-2~bpo8+1 Upgraded: libgd3:amd64 2.1.0-5+deb8u8 => 2.1.0-5+deb8u9 linux-image-amd64:amd64 4.8+77~bpo8+1 => 4.9+78~bpo8+1 ntfs-3g:amd64 1:2014.2.15AR.2-1+deb8u2 => 1:2014.2.15AR.2-1+deb8u3 -- dpkg status changes End -
Processed: severity of 854182 is important, found 854182 in 4.7.8-1, found 854182 in 4.8.15-2
Processing commands for cont...@bugs.debian.org: > severity 854182 important Bug #854182 [src:linux] linux-image-4.9.0-1-amd64: Kernel crashes during boot.Boots fine with acpi=off, nolapic or without AC power Severity set to 'important' from 'critical' > found 854182 4.7.8-1 Bug #854182 [src:linux] linux-image-4.9.0-1-amd64: Kernel crashes during boot.Boots fine with acpi=off, nolapic or without AC power Marked as found in versions linux/4.7.8-1. > found 854182 4.8.15-2 Bug #854182 [src:linux] linux-image-4.9.0-1-amd64: Kernel crashes during boot.Boots fine with acpi=off, nolapic or without AC power Marked as found in versions linux/4.8.15-2. > thanks Stopping processing here. Please contact me if you need assistance. -- 854182: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=854182 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
