Bug#895381: Severity
* micah anderson [2019-01-20 21:03:53 +0100]: > I'm not disputing this bug exists, I'm just trying to determine why it > is you set the severity to "Serious". As you are probably aware, this > severity indicates that this is a sever violation of Debian policy > (violates a "must" or "required" directive), or in the package > maintainer's opinion, makes the package unsuitable for release. Oh. In the package maintainer's opinion. I had missed that part; my apologies. No, I don't claim a policy violation on this one and of course I'll defer to the package maintainer's assessment. I do find the bug scary, though, due to the possibility of silent corruption, and have been running a privately patched version of the package for that reason.
Processed: Re: linux-image-4.18.0-1-amd64: Please enable CONFIG_SENSORS_NCT7802 for nct7802 driver and others
Processing control commands: > tags -1 +patch Bug #912597 [src:linux] linux-image-4.18.0-1-amd64: Please enable CONFIG_SENSORS_NCT7802 for nct7802 driver and others Added tag(s) patch. -- 912597: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=912597 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#912597: linux-image-4.18.0-1-amd64: Please enable CONFIG_SENSORS_NCT7802 for nct7802 driver and others
control: tags -1 +patch On Thu, 01 Nov 2018 17:27:47 + Witold Baryluk wrote: > Please enable it to be built as module, as it is used on various > motherboards, including my MSI X399 MEG Creation. > > Please also consider enabling other hwmon modules > (like CONFIG_SENSORS_NPCM7XX, CONFIG_SENSORS_W83773G, CONFIG_SENSORS_ASPEED). > Similary CONFIG_PMBUS and all PMBUS drivers should probably be build as > modules. made MergeRequest as https://salsa.debian.org/kernel-team/linux/merge_requests/107 -- Hideki Yamane
Bug#832458: linux-image-4.6.0-0.bpo.1-amd64: Please enable
SND_SOC_INTEL_BYT_MAX98090_MACH, needed for some Baytrail devices Message-Id: <20190121071057.3ab9bf60070bfd3b05fde...@iijmio-mail.jp> In-Reply-To: <20160725191002.506.99957.reportbug@compy386> X-Mailer: Sylpheed 3.7.0 (GTK+ 2.24.32; x86_64-pc-linux-gnu) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit On Mon, 25 Jul 2016 13:10:02 -0600 Ivan M wrote: > Please enable CONFIG_SND_SOC_INTEL_BYT_MAX98090_MACH=m - it is necessary for > audio on certain Baytrail hardware. CONFIG_SND_SOC_INTEL_BYT_MAX98090_MACH is deprecated and its successor SND_SOC_INTEL_CHT_BSW_MAX98090_TI_MACH is enabled in debian kernel. -- Hideki Yamane
Bug#919652: Acknowledgement (ath10k - QCA6174 - Surface Go - missing board data - fix .bin included extracted form official .msi)
In the Surface Go update history https://support.microsoft.com/en-us/he lp/4455978/surface-go-update-history the update of the QCA6174 to version 12.0.0.722 is listed, so we would be in line with the recent version if adding the latest eeprom_ar6320_3p0_TX8_clpc.bin to board-2- bin .
Processed: severity of 919919 is important
Processing commands for cont...@bugs.debian.org: > severity 919919 important Bug #919919 [src:linux] frequent lockups requiring power off Severity set to 'important' from 'grave' > thanks Stopping processing here. Please contact me if you need assistance. -- 919919: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=919919 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#919656: Acknowledgement (usb - surface dock - ethernet - fix included)
https://github.com/torvalds/linux/blob/v4.19/drivers/net/usb/cdc_ether.c Intersting to mention is that the ProductID 0x07c6 is blacklisted in the cdc_ether driver and the proper belonging r8152 is used. The above ProductID can be found in https://github.com/torvalds/linux/blob/v4.19/drivers/net/usb/r8152.c As long as the ProductID is blacklisted in cdc_ether and explicitly listed in r8152 it should be safe to use the quirk, because the proper r8152 driver will be used and it seems just to be a powermanagement issue. And because it is a dock and conncted to the power grid proper power saving is not neccessary. So it should be safe to add this quirk here https://github.com/torvalds /linux/blob/v4.19/drivers/usb/core/quirks.c
Bug#895381: Severity
Hello Sergio, I'm reviewing bugs that are currently release critical at our local bug squashing party, and I stumbled on yours. I'm not disputing this bug exists, I'm just trying to determine why it is you set the severity to "Serious". As you are probably aware, this severity indicates that this is a sever violation of Debian policy (violates a "must" or "required" directive), or in the package maintainer's opinion, makes the package unsuitable for release. Can you specify what part of debian policy this issue makes this bug severity "Serious"? Thanks! -- micah
Bug#919656: Acknowledgement (usb - surface dock - ethernet - fix included)
A temporary solution (or to test this patch) is to use a kernel parameter in grub2. https://www.kernel.org/doc/html/v4.19/admin-guide/kernel-parameters.htm l In line "linux" before "quiet" add "usbcore.quirks=045e:07c6:k" (means -> VendorID:ProductID:Flags) and after booting the docks Ethernet is working fine. I do not know if using this quirk is a good solution, but because the quirk is bound to a specific VendorID and ProductID it should not conflict with other usb devices.
Bug#919826: - update
Follow up following more investigation I have since re-installed my system (again from DI beta4). I have reconfirmed that yes following an upgrade after the install the system still fails to boot. However at Sledge's suggestion (and with his help) I reverted to the versions of grub that are included on the DVD set of DI beta 4 that is to say I followed the following steps: 1) reboot failed system using USB stick containing image debian-buster-DI-alpha4-arm64-DVD-1.iso 2) mount the partition on my hard disk for / /boot /boot/efi 3) downgrade grub2 to the versions found on debian-buster-DI-alpha4-arm64-DVD-1.iso i.e. dpkg -i grub-efi-arm64-bin_2.02+dfsg1-8_arm64.deb\ grub-efiarm64_2.02+dfsg1-8_arm64.deb\ grub2-common_2.02+dfsg1-8_arm64.deb \ grub-common_2.02+dfsg1-8_arm64.deb 4) reboot At this point I am able to correctly start both my old kernel (found on DI beta4 - Linux 4.18.0-3-arm64) and the current Buster kernel image (Linux 4.19.0-1-arm64) Conclusion: I have wrongly attributed this bug to the kernel - it should be re assigned to grub2 /Andy
Processed: reassign 919826 to src:grub2
Processing commands for cont...@bugs.debian.org: > reassign 919826 src:grub2 Bug #919826 [src:linux] linux-image-4.19.0-1-arm64: Loading Linux 4.19.0-1-arm64 Loading initial ramdisk error: out of memory system panic Bug reassigned from package 'src:linux' to 'src:grub2'. No longer marked as found in versions linux/4.19.12-1. Ignoring request to alter fixed versions of bug #919826 to the same values previously set > thanks Stopping processing here. Please contact me if you need assistance. -- 919826: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=919826 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#919919: frequent lockups requiring power off
Package: src:linux Version: 4.19.12-1 Severity: grave Tags: upstream Hello, I experience lockups about every few minutes to hours of my laptop which I guess are kernel bugs. At least, the machine is fairly new, and hardware diagnostics turned up nothing. The system has a standard /boot and an LUKS+LVM container, containing the rest of it (/, swap, and some unused space). The root partition (/) is formatted as BTRFS. In the logs, I find things like this: Jan 13 02:42:51 laptop-t kernel: [112014.623614] (NULL device *): firmware: direct-loading firmware iwlwifi-9260-th-b0-jf-b0-38.ucode Jan 13 11:15:37 laptop-t kernel: [112014.623725] Freezing user space processes ... (elapsed 0.001 seconds) done. Jan 13 11:15:37 laptop-t kernel: [112014.625213] OOM killer disabled. Jan 13 11:15:37 laptop-t kernel: [112014.625213] Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done. Jan 13 11:15:37 laptop-t kernel: [112014.626318] Suspending console(s) (use no_console_suspend to debug) Jan 13 11:15:37 laptop-t kernel: [112014.627028] wlp59s0: deauthenticating from c0:3e:0f:ac:54:8d by local choice (Reason: 3=DEAUTH_LEAVING) Jan 13 11:15:37 laptop-t kernel: [112227.801000] watchdog: BUG: soft lockup - CPU#11 stuck for 192s! [swapper/11:0] Jan 13 11:15:37 laptop-t kernel: [112227.801002] Modules linked in: iptable_nat iptable_filter ctr ccm ipt_MASQUERADE nf_conntrack_netlink xfrm_user xfrm_algo cmac nft_chain_nat_ipv4 devlink xt_addrtype br_netfilter bridge stp ifb sch_fq_codel snd_hda_codec_hdmi overlay snd_hda_codec_realtek snd_hda_codec_generic nft_chain_route_ipv6 nf_log_ipv6 nft_chain_route_ipv4 xt_connmark nf_log_ipv4 nf_log_common nft_limit nft_counter xt_helper xt_LOG xt_limit xt_conntrack xt_tcpudp nft_compat nf_conntrack_sip nf_conntrack_ftp nf_conntrack_irc nf_conntrack_pptp nf_conntrack_proto_gre ip6_tables appletalk psnap llc ax25 bnep fuse arc4 nf_tables nfnetlink openvswitch nsh nf_nat_ipv6 nf_nat_ipv4 nf_conncount nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 dell_rbtn binfmt_misc nls_ascii nls_cp437 vfat fat ext4 mbcache jbd2 fscrypto ecb intel_rapl Jan 13 11:15:37 laptop-t kernel: [112227.801073] x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel dell_laptop dell_wmi kvm iwlmvm irqbypass dell_smbios mac80211 nouveau snd_hda_intel i915 btusb snd_hda_codec btrtl btbcm uvcvideo btintel snd_hda_core videobuf2_vmalloc wmi_bmof snd_hwdep videobuf2_memops videobuf2_v4l2 bluetooth snd_pcm mxm_wmi videobuf2_common efi_pstore snd_timer intel_cstate iwlwifi dell_wmi_descriptor ttm dcdbas intel_uncore drbg dell_smm_hwmon videodev snd drm_kms_helper ansi_cprng iTCO_wdt cfg80211 media serio_raw intel_rapl_perf pcspkr hid_multitouch efivars soundcore iTCO_vendor_support rtsx_pci_sdmmc rtsx_pci_ms mei_me ecdh_generic mmc_core drm evdev mei rfkill crc16 memstick joydev ucsi_acpi typec_ucsi idma64 processor_thermal_device i2c_algo_bit typec intel_soc_dts_iosf intel_pch_thermal battery int3403_thermal Jan 13 11:15:37 laptop-t kernel: [112227.801144] int340x_thermal_zone wmi video dell_smo8800 int3400_thermal intel_hid pcc_cpufreq acpi_thermal_rel sparse_keymap acpi_pad ac button parport_pc ppdev lp parport efivarfs ip_tables x_tables autofs4 btrfs xor zstd_decompress zstd_compress xxhash raid6_pq libcrc32c crc32c_generic algif_skcipher af_alg dm_crypt dm_mod wacom usbhid hid_generic crct10dif_pclmul crc32_pclmul crc32c_intel ghash_clmulni_intel pcbc ahci xhci_pci libahci aesni_intel xhci_hcd libata aes_x86_64 crypto_simd psmouse cryptd usbcore nvme glue_helper scsi_mod i2c_i801 nvme_core rtsx_pci i2c_hid intel_lpss_pci hid intel_lpss usb_common thermal [last unloaded: ebtables] Jan 13 11:15:37 laptop-t kernel: [112227.801210] CPU: 11 PID: 0 Comm: swapper/11 Tainted: G L4.19.0-1-amd64 #1 Debian 4.19.12-1 Jan 13 11:15:37 laptop-t kernel: [112227.801211] Hardware name: Dell Inc. Precision 5530/0FP2W2, BIOS 1.6.0 11/02/2018 Jan 13 11:15:37 laptop-t kernel: [112227.801218] RIP: 0010:do_idle+0x267/0x280 Jan 13 11:15:37 laptop-t kernel: [112227.801222] Code: 12 4e 00 e9 d0 fe ff ff 48 89 df e8 f3 57 04 00 e9 1f ff ff ff 0f 0b fb 66 0f 1f 44 00 00 e9 d3 fe ff ff fb 66 0f 1f 44 00 00 a9 fe ff ff e8 1f fe 05 00 eb b0 e8 08 c3 fc ff 0f 1f 84 00 00 Jan 13 11:15:37 laptop-t kernel: [112227.801224] RSP: 0018:b81583253ed8 EFLAGS: 0202 ORIG_RAX: ff13 Jan 13 11:15:37 laptop-t kernel: [112227.801228] RAX: 0008 RBX: 000b RCX: Jan 13 11:15:37 laptop-t kernel: [112227.801230] RDX: 0011 RSI: 99ed1c4ea240 RDI: fff86eefda25 Jan 13 11:15:37 laptop-t kernel: [112227.801232] RBP: 91b2c820 R08: 0002 R09: 000214c0 Jan 13 11:15:37 laptop-t kernel: [112227.801234] R10: 0001287fb6384ab9 R11: 0fc5 R12: 99ed1c4ea100 Jan 13 11:15:37 laptop-t kernel: [112227.801235] R13: 91ab64c0 R14: R15: Jan 13 11:
Bug#919920: clock far in the future after suspend/resume
Package: src:linux Version: 4.19.12-1 Severity: important Tags: upstream Hi, usually, after resuming from suspend, the clock on my machine is way ahead, causing all sorts of havoc. Especially when being offline, there is also no good way to correct this issue. Cheers, Toni -- Package-specific info: ** Version: Linux version 4.19.0-1-amd64 (debian-kernel@lists.debian.org) (gcc version 8.2.0 (Debian 8.2.0-13)) #1 SMP Debian 4.19.12-1 (2018-12-22) ** Command line: BOOT_IMAGE=/vmlinuz-4.19.0-1-amd64 root=/dev/mapper/ev0-root ro quiet ** Not tainted ** Kernel log: [ 49.398869] snd_hda_codec_realtek hdaudioC0D0: Headset Mic=0x18 [ 49.398870] snd_hda_codec_realtek hdaudioC0D0: Headphone Mic=0x1a [ 49.398870] snd_hda_codec_realtek hdaudioC0D0: Internal Mic=0x12 [ 49.458102] input: HDA Intel PCH Headphone Mic as /devices/pci:00/:00:1f.3/sound/card0/input28 [ 49.458166] input: HDA Intel PCH HDMI/DP,pcm=3 as /devices/pci:00/:00:1f.3/sound/card0/input29 [ 49.458224] input: HDA Intel PCH HDMI/DP,pcm=7 as /devices/pci:00/:00:1f.3/sound/card0/input30 [ 49.458271] input: HDA Intel PCH HDMI/DP,pcm=8 as /devices/pci:00/:00:1f.3/sound/card0/input31 [ 49.458324] input: HDA Intel PCH HDMI/DP,pcm=9 as /devices/pci:00/:00:1f.3/sound/card0/input32 [ 49.458375] input: HDA Intel PCH HDMI/DP,pcm=10 as /devices/pci:00/:00:1f.3/sound/card0/input33 [ 49.934113] Bluetooth: hci0: Waiting for firmware download to complete [ 49.934183] Bluetooth: hci0: Firmware loaded in 1552005 usecs [ 49.934227] Bluetooth: hci0: Waiting for device to boot [ 49.947398] Bluetooth: hci0: Device booted in 12885 usecs [ 49.947444] bluetooth hci0: firmware: direct-loading firmware intel/ibt-18-16-1.ddc [ 49.947446] Bluetooth: hci0: Found Intel DDC parameters: intel/ibt-18-16-1.ddc [ 49.952704] Bluetooth: hci0: Applying Intel DDC parameters completed [ 50.417916] Console: switching to colour frame buffer device 480x135 [ 50.449962] i915 :00:02.0: fb0: inteldrmfb frame buffer device [ 57.269823] IPv6: ADDRCONF(NETDEV_UP): wlp59s0: link is not ready [ 57.966244] IPv6: ADDRCONF(NETDEV_UP): wlp59s0: link is not ready [ 66.863361] wlp59s0: authenticate with c0:3e:0f:ac:54:8d [ 66.880393] wlp59s0: send auth to c0:3e:0f:ac:54:8d (try 1/3) [ 66.919492] wlp59s0: authenticated [ 66.923155] wlp59s0: associate with c0:3e:0f:ac:54:8d (try 1/3) [ 66.927698] wlp59s0: RX AssocResp from c0:3e:0f:ac:54:8d (capab=0x1411 status=0 aid=1) [ 66.934797] wlp59s0: associated [ 66.965915] IPv6: ADDRCONF(NETDEV_CHANGE): wlp59s0: link becomes ready [ 66.975044] DROP UNMATCHED OUT-world:IN= OUT=wlp59s0 SRC=::::::: DST=ff02:::::::0016 LEN=76 TC=0 HOPLIMIT=1 FLOWLBL=0 PROTO=ICMPv6 TYPE=143 CODE=0 MARK=0x94 [ 66.983873] wlp59s0: Limiting TX power to 20 (20 - 0) dBm as advertised by c0:3e:0f:ac:54:8d [ 75.739408] pci_raw_set_power_state: 19 callbacks suppressed [ 75.739413] nouveau :01:00.0: Refused to change power state, currently in D3 [ 76.172896] nouveau :01:00.0: firmware: direct-loading firmware nvidia/gp107/gr/fecs_bl.bin [ 76.173220] nouveau :01:00.0: firmware: direct-loading firmware nvidia/gp107/gr/fecs_inst.bin [ 76.173372] nouveau :01:00.0: firmware: direct-loading firmware nvidia/gp107/gr/fecs_data.bin [ 76.173388] nouveau :01:00.0: firmware: direct-loading firmware nvidia/gp107/gr/fecs_sig.bin [ 76.173406] nouveau :01:00.0: firmware: direct-loading firmware nvidia/gp107/gr/gpccs_bl.bin [ 76.173615] nouveau :01:00.0: firmware: direct-loading firmware nvidia/gp107/gr/gpccs_inst.bin [ 76.173766] nouveau :01:00.0: firmware: direct-loading firmware nvidia/gp107/gr/gpccs_data.bin [ 76.173781] nouveau :01:00.0: firmware: direct-loading firmware nvidia/gp107/gr/gpccs_sig.bin [ 76.174174] nouveau :01:00.0: firmware: direct-loading firmware nvidia/gp107/sec2/image.bin [ 76.174210] nouveau :01:00.0: firmware: direct-loading firmware nvidia/gp107/sec2/desc.bin [ 76.174228] nouveau :01:00.0: firmware: direct-loading firmware nvidia/gp107/sec2/sig.bin [ 76.175037] nouveau :01:00.0: firmware: direct-loading firmware nvidia/gp107/acr/ucode_load.bin [ 76.175292] nouveau :01:00.0: firmware: direct-loading firmware nvidia/gp107/acr/ucode_unload.bin [ 76.175357] nouveau :01:00.0: firmware: direct-loading firmware nvidia/gp107/acr/bl.bin [ 76.175387] nouveau :01:00.0: firmware: direct-loading firmware nvidia/gp107/acr/unload_bl.bin [ 76.175638] nouveau :01:00.0: firmware: direct-loading firmware nvidia/gp107/nvdec/scrubber.bin [ 76.175764] nouveau :01:00.0: secboot: VPR scrubber binary failed! [ 76.175776] nouveau :01:00.0: gr: init failed, -22 ** Model information sys_vendor: Dell Inc. product_name: Precision 5530 product_version: chassis_vendor: Dell Inc. chassis
Bug#919227: dmesg output with patched kernel
As recommended by upstream bug 192231 I have rebuilt the kernel with a debugging patch and here is the output of dmesg when triggering the issue. [0.00] Linux version 4.19.0-1-amd64 (debian-kernel@lists.debian.org) (gcc version 8.2.0 (Debian 8.2.0-14)) #1 SMP Debian 4.19.12-1a~test (2019-01-13) [0.00] Command line: BOOT_IMAGE=/boot/vmlinuz-4.19.0-1-amd64 root=UUID=e19e81ac-9618-4735-8a7c-bff7f48b50cb ro resume=UUID=3464e393-b3d3-49c3-a1e0-858d6123f7c3 button.lid_init_state=open quiet [0.00] x86/fpu: x87 FPU will use FXSAVE [0.00] BIOS-provided physical RAM map: [0.00] BIOS-e820: [mem 0x-0x0009fbff] usable [0.00] BIOS-e820: [mem 0x0009fc00-0x0009] reserved [0.00] BIOS-e820: [mem 0x000e-0x000f] reserved [0.00] BIOS-e820: [mem 0x0010-0x7f67] usable [0.00] BIOS-e820: [mem 0x7f68-0x7f68dfff] ACPI data [0.00] BIOS-e820: [mem 0x7f68e000-0x7f6c] ACPI NVS [0.00] BIOS-e820: [mem 0x7f6d-0x7f6f] reserved [0.00] BIOS-e820: [mem 0xfee0-0xfee00fff] reserved [0.00] BIOS-e820: [mem 0xfff0-0x] reserved [0.00] NX (Execute Disable) protection: active [0.00] SMBIOS 2.6 present. [0.00] DMI: ASUSTeK Computer INC. 1215P/1215P, BIOS 060104/18/2011 [0.00] tsc: Fast TSC calibration failed [0.00] e820: update [mem 0x-0x0fff] usable ==> reserved [0.00] e820: remove [mem 0x000a-0x000f] usable [0.00] last_pfn = 0x7f680 max_arch_pfn = 0x4 [0.00] MTRR default type: uncachable [0.00] MTRR fixed ranges enabled: [0.00] 0-9 write-back [0.00] A-B uncachable [0.00] C-C write-protect [0.00] D-D uncachable [0.00] E-E write-through [0.00] F-F write-protect [0.00] MTRR variable ranges enabled: [0.00] 0 base 0 mask F8000 write-back [0.00] 1 base 07F70 mask 0 uncachable [0.00] 2 base 07F80 mask FFF80 uncachable [0.00] 3 disabled [0.00] 4 disabled [0.00] 5 disabled [0.00] 6 disabled [0.00] 7 disabled [0.00] x86/PAT: Configuration [0-7]: WB WC UC- UC WB WP UC- WT [0.00] found SMP MP-table at [mem 0x000ff780-0x000ff78f] mapped at [(ptrval)] [0.00] Base memory trampoline at [(ptrval)] 99000 size 24576 [0.00] BRK [0x55201000, 0x55201fff] PGTABLE [0.00] BRK [0x55202000, 0x55202fff] PGTABLE [0.00] BRK [0x55203000, 0x55203fff] PGTABLE [0.00] BRK [0x55204000, 0x55204fff] PGTABLE [0.00] BRK [0x55205000, 0x55205fff] PGTABLE [0.00] BRK [0x55206000, 0x55206fff] PGTABLE [0.00] RAMDISK: [mem 0x3532d000-0x3698dfff] [0.00] ACPI: Early table checksum verification disabled [0.00] ACPI: RSDP 0x000FBF30 24 (v02 ACPIAM) [0.00] ACPI: XSDT 0x7F680100 64 (v01 A_M_I_ OEMXSDT 04001118 MSFT 0097) [0.00] ACPI: FACP 0x7F680290 F4 (v04 A_M_I_ OEMFACP 04001118 MSFT 0097) [0.00] ACPI: DSDT 0x7F6804A0 008D70 (v02 A1724 A1724000 INTL 20060113) [0.00] ACPI: FACS 0x7F68E000 40 [0.00] ACPI: FACS 0x7F68E000 40 [0.00] ACPI: APIC 0x7F680390 6C (v02 A_M_I_ OEMAPIC 04001118 MSFT 0097) [0.00] ACPI: MCFG 0x7F680400 3C (v01 A_M_I_ OEMMCFG 04001118 MSFT 0097) [0.00] ACPI: ECDT 0x7F680440 55 (v01 A_M_I_ OEMECDT 04001118 MSFT 0097) [0.00] ACPI: OEMB 0x7F68E040 61 (v01 A_M_I_ AMI_OEM 04001118 MSFT 0097) [0.00] ACPI: HPET 0x7F689210 38 (v01 A_M_I_ OEMHPET 04001118 MSFT 0097) [0.00] ACPI: GSCI 0x7F68E0B0 002024 (v01 A_M_I_ GMCHSCI 04001118 MSFT 0097) [0.00] ACPI: SSDT 0x7F690F00 000999 (v01 PmRef CpuPm4 3000 INTL 20060113) [0.00] ACPI: Local APIC address 0xfee0 [0.00] No NUMA configuration found [0.00] Faking a node at [mem 0x-0x7f67] [0.00] NODE_DATA(0) allocated [mem 0x7f67b000-0x7f67] [0.00] Zone ranges: [0.00] DMA [mem 0x1000-0x00ff] [0.00] DMA32[mem 0x0100-0x7f67] [0.00] Normal empty [0.00] Device empty [0.00] Movable zone start for each node [0.00] Early memory node ranges [0.00] node 0: [mem 0x1000-0x0009efff] [0.00] node 0: [mem 0x0010-0x7f67] [0.00] Reserved but unavailable: 98
Bug#919652: Info received (Bug#919652: Acknowledgement (ath10k - QCA6174 - Surface Go - missing board data - fix .bin included extracted form official .msi))
Microsoft released an updated version: https://www.microsoft.com/en-us/download/details.aspx?id=57439 Same es above applies, but in netathr10x.inf DriverVer = 08/24/2018,12.0.0.722 (new one SurfaceGo_Win10_17134_1803010_WiFi_0.msi) instead of DriverVer = 06/04/2018,12.0.0.709 (old one SurfaceGo_Win10_17134_1802010_6.msi) is listed. Also the md5sum of the .bins have changed, see: old one: pink@debian-470t:~/Dokumente/surface_go_wifi/extracted_msi/SurfacePlatf ormInstaller17134_1802010_6/Drivers/Network/WiFi$ md5sum eeprom_ar6320_3p0_TX8_clpc.bin fcbc54a33a3ee462d862fe4f62854410 eeprom_ar6320_3p0_TX8_clpc.bin new one: pink@debian-t470:~/Dokumente/surface_go_wifi/extracted_msi/SurfacePlatf ormInstaller_17134_1803010/SurfaceUpdate/Drivers/Network/WiFi$ md5sum eeprom_ar6320_3p0_TX8_clpc.bin bc52aa5640b27fa50f9d4d144f81e169 eeprom_ar6320_3p0_TX8_clpc.bin So the driver should be extracted now from SurfaceGo_Win10_17134_1803010_WiFi_0.msi I think. I will attach the new one here which should now be used instead to add to board-2.bin Also one with lte in the name is listed: pink@debian-t470:~/Dokumente/surface_go_wifi/extracted_msi/SurfacePlatf ormInstaller_17134_1803010/SurfaceUpdate/Drivers/Network/WiFi$ md5sum eeprom_ar6320_3p0_TX8_lte_clpc.bin 8f2895dd63a0c8f11e2d051f0ed4e0a8 eeprom_ar6320_3p0_TX8_lte_clpc.bin I will also at this one, but I can not confirm, that it is for the LTE version because I just own the wifi one so I can not check the IDs, but maybe others can do. eeprom_ar6320_3p0_TX8_clpc.bin Description: Binary data eeprom_ar6320_3p0_TX8_lte_clpc.bin Description: Binary data
Processed: your mail
Processing commands for cont...@bugs.debian.org: > notfound 919648 20190114-1 Bug #919648 [src:linux] i2c - Elantech touchscreen - Surface GO - not recognized properly - but working in general with changes The source 'linux' and version '20190114-1' do not appear to match any binary packages No longer marked as found in versions linux/20190114-1. > -- Stopping processing here. Please contact me if you need assistance. -- 919648: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=919648 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: your mail
Processing commands for cont...@bugs.debian.org: > found 919648 4.19.13-1 Bug #919648 [src:linux] i2c - Elantech touchscreen - Surface GO - not recognized properly - but working in general with changes Marked as found in versions linux/4.19.13-1. > -- Stopping processing here. Please contact me if you need assistance. -- 919648: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=919648 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: your mail
Processing commands for cont...@bugs.debian.org: > found 919656 4.19.13-1 Bug #919656 [src:linux] usb - surface dock - ethernet - fix included Marked as found in versions linux/4.19.13-1. > -- Stopping processing here. Please contact me if you need assistance. -- 919656: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=919656 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: your mail
Processing commands for cont...@bugs.debian.org: > found 919652 20190114-1 Bug #919652 [firmware-atheros] ath10k - QCA6174 - Surface Go - missing board data - fix .bin included extracted form official .msi Marked as found in versions firmware-nonfree/20190114-1. > -- Stopping processing here. Please contact me if you need assistance. -- 919652: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=919652 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#919652: Acknowledgement (ath10k - QCA6174 - Surface Go - missing board data - fix .bin included extracted form official .msi)
Bug not solved, even in latest firmware which entered unstable. See here pink@debian-surface-go:~$ apt show firmware-atheros Package: firmware-atheros Version: 20190114-1 ... APT-Sources: http://deb.debian.org/debian unstable/non-free amd64 Packages ... and here pink@debian-surface-go:~$ sudo journalctl | grep ath10k [sudo] Passwort für pink: Jan 20 13:30:49 debian-surface-go kernel: ath10k_pci :01:00.0: pci irq msi oper_irq_mode 2 irq_mode 0 reset_mode 0 Jan 20 13:30:49 debian-surface-go kernel: ath10k_pci :01:00.0: firmware: failed to load ath10k/pre-cal-pci-:01:00.0.bin (-2) Jan 20 13:30:49 debian-surface-go kernel: ath10k_pci :01:00.0: firmware: failed to load ath10k/cal-pci-:01:00.0.bin (-2) Jan 20 13:30:49 debian-surface-go kernel: ath10k_pci :01:00.0: firmware: direct-loading firmware ath10k/QCA6174/hw3.0/firmware-6.bin Jan 20 13:30:49 debian-surface-go kernel: ath10k_pci :01:00.0: qca6174 hw3.2 target 0x0503 chip_id 0x00340aff sub 168c:3370 Jan 20 13:30:49 debian-surface-go kernel: ath10k_pci :01:00.0: kconfig debug 0 debugfs 0 tracing 0 dfs 0 testmode 0 Jan 20 13:30:49 debian-surface-go kernel: ath10k_pci :01:00.0: firmware ver RM.4.4.1.c2-00057-QCARMSWP-1 api 6 features wowlan,ignore-otp,no-4addr-pad,raw-mode crc32 e061250a Jan 20 13:30:49 debian-surface-go kernel: ath10k_pci :01:00.0: firmware: direct-loading firmware ath10k/QCA6174/hw3.0/board-2.bin Jan 20 13:30:49 debian-surface-go kernel: ath10k_pci :01:00.0: failed to fetch board data for bus=pci,vendor=168c,device=003e,subsystem-vendor=168c,subsystem-device=3370 from ath10k/QCA6174/hw3.0/board-2.bin Jan 20 13:30:49 debian-surface-go kernel: ath10k_pci :01:00.0: firmware: direct-loading firmware ath10k/QCA6174/hw3.0/board.bin Jan 20 13:30:49 debian-surface-go kernel: ath10k_pci :01:00.0: board_file api 1 bmi_id N/A crc32 ed5f849a Jan 20 13:30:50 debian-surface-go kernel: ath10k_pci :01:00.0: Unknown eventid: 118809 Jan 20 13:30:53 debian-surface-go kernel: ath10k_pci :01:00.0: failed to ping firmware: -110 Jan 20 13:30:53 debian-surface-go kernel: ath10k_pci :01:00.0: failed to reset rx filter: -110 Jan 20 13:30:53 debian-surface-go kernel: ath10k_pci :01:00.0: could not init core (-110) Jan 20 13:30:53 debian-surface-go kernel: ath10k_pci :01:00.0: could not probe fw (-110)
Bug#919859: linux-image-4.19.0-1-amd64: Lost wake on lan after the upgrade to 4.19
Package: src:linux Version: 4.19.13-1 Severity: normal I have been using wol on all my ethernet connected systems since 2012 that I discovered it. Most of the times I use a wol app from my phone and wakeonlan or etherwake from my linux systems. According to lspci -k, this is my card and the r8169 is used for it 04:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 01) Subsystem: Gigabyte Technology Co., Ltd Onboard Ethernet Kernel driver in use: r8169 Kernel modules: r8169 and as ethtool reports, wol is enabled for the card # ethtool eth0 | grep Wake Supports Wake-on: pumbg Wake-on: g After upgrading to 4.19 back in December, I completely lost wol on that pc. The only way to make it work again is to run ethtool -s eth0 wol and it will work for the next boot, but only for that single time. After booting to debian, I have to run it again before shutting down to re-anable it for the next boot. Losing wol happened once more back when 4.17 was in the repos, in July that is. However. that was an upstream bug that affected some cards that r8169 supports and it was fixed with the release of 4.17.11. Using ngrep I found that the magic packet does reach its destination (= my pc), but when running ngrep the pc is already powered on... U 192.168.1.108:47926 -> 192.168.1.2:9 #1 ff ff ff ff ff ff 00 1a4d 58 4d 16 00 1a 4d 58MXM...MX 4d 16 00 1a 4d 58 4d 1600 1a 4d 58 4d 16 00 1aM...MXM...MXM... 4d 58 4d 16 00 1a 4d 584d 16 00 1a 4d 58 4d 16MXM...MXM...MXM. 00 1a 4d 58 4d 16 00 1a4d 58 4d 16 00 1a 4d 58..MXM...MXM...MX 4d 16 00 1a 4d 58 4d 1600 1a 4d 58 4d 16 00 1aM...MXM...MXM... 4d 58 4d 16 00 1a 4d 584d 16 00 1a 4d 58 4d 16MXM...MXM...MXM. 00 1a 4d 58 4d 16 ..MXM. That's all I can report for now. I have upgraded to the 4.19.13 version from unstable earlier (testing still has 4.19.12 today), but nothing changed. I would test if the same applies for 4.18, but when I decided to do it, 4.18 was no longer in the repos. On top of that, systemd 240 and kernel 4.19 reached testing almost the same day, but I have no way to downgrade to systemd 239 as well. 9 out of 10 times, I shut down my pc with "systemctl poweroff" (via obsession or from a keyboard shortcut I have made) and 1 out of 10 is by running a simple "poweroff" in a root terminal. Wol works if I shut down the pc from within windows (dual boot system) and obviously wol is enabled in the bios. I do not use hibernate or suspend on any os. -- Package-specific info: ** Version: Linux version 4.19.0-1-amd64 (debian-kernel@lists.debian.org) (gcc version 8.2.0 (Debian 8.2.0-13)) #1 SMP Debian 4.19.13-1 (2018-12-30) ** Command line: BOOT_IMAGE=/boot/vmlinuz-4.19.0-1-amd64 root=/dev/sda3 ro nomodeset noresume net.ifnames=0 ipv6.disable=1 libahci.ignore_sss=1 quiet ** Tainted: POE (12289) * Proprietary module has been loaded. * Out-of-tree module has been loaded. * Unsigned module has been loaded. ** Kernel log: [3.538187] r8169 :04:00.0 eth0: RTL8168b/8111b, 00:1a:4d:58:4d:16, XID 3800, IRQ 25 [3.538190] r8169 :04:00.0 eth0: jumbo features [frames: 4080 bytes, tx checksumming: ko] [3.541395] systemd-journald[182]: Received request to flush runtime journal from PID 1 [3.563020] intel_powerclamp: No package C-state available [3.605846] ehci-pci :00:1a.7: EHCI Host Controller [3.605858] ehci-pci :00:1a.7: new USB bus registered, assigned bus number 7 [3.609769] ehci-pci :00:1a.7: cache line size of 32 is not supported [3.611352] ehci-pci :00:1a.7: irq 18, io mem 0xf9104000 [3.624153] ehci-pci :00:1a.7: USB 2.0 started, EHCI 1.00 [3.624395] usb usb7: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 4.19 [3.624398] usb usb7: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [3.624400] usb usb7: Product: EHCI Host Controller [3.624402] usb usb7: Manufacturer: Linux 4.19.0-1-amd64 ehci_hcd [3.624404] usb usb7: SerialNumber: :00:1a.7 [3.624562] hub 7-0:1.0: USB hub found [3.624572] hub 7-0:1.0: 6 ports detected [3.631120] snd_hda_intel :01:00.1: Disabling MSI [3.631144] snd_hda_intel :01:00.1: Handle vga_switcheroo audio client [3.653374] hub 1-0:1.0: USB hub found [3.653393] hub 1-0:1.0: 2 ports detected [3.680293] hub 2-0:1.0: USB hub found [3.680306] hub 2-0:1.0: 2 ports detected [3.681306] ata9.00: ATAPI: Optiarc DVD RW AD-7173A, 1-01, max UDMA/66 [3.686782] scsi 8:0:0:0: CD-ROMOptiarc DVD RW AD-7173A 1-01 PQ: 0 ANSI: 5 [3.687539] scsi 8:0:0:0: Attached scsi generic sg2 type 5 [3.697262] snd_hda_codec_realtek hdaudioC0D2: autoconfig for ALC889A: line_outs=4 (0x14/0x15/0x16/0x17/0x0) type:line [3.697266] snd_hda_codec_realtek hdaudioC0D2:speaker_out
