Bug#914758: linux-image-4.18.0-2-amd64: setting elevator=none does not change io scheduler
Control: tag -1 upstream
Control: retitle -1 Missing equivalent of elevator kernel parameter for blk-mq
On Mon, 2018-11-26 at 18:10 -0600, Matt Zagrabelny wrote:
> Package: src:linux
> Version: 4.18.10-2
> Severity: normal
>
> Greetings!
>
> Thank you for your contribution to Debian. It is appreciated!
>
> I am running:
>
> linux-image-4.18.0-2-amd64 4.18.10-2+b1
>
> and attempting to set the IO scheduler.
>
> Looking at the current scheduler:
>
> # cat /sys/block/sda/queue/scheduler
> [mq-deadline] none
This is a device implemented using the "blk-mq" API, which was
introduced a few years ago but has only recently come to be used by
most block devices.
[...]
> I just don't know why the elevator parameter isn't working. According to the
> kernel documentation for 4.18:
>
> grep -A3 elevator
> /usr/src/linux-source-4.18/Documentation/admin-guide/kernel-parameters.txt
> elevator= [IOSCHED]
> Format: {"cfq" | "deadline" | "noop"}
> See Documentation/block/cfq-iosched.txt and
> Documentation/block/deadline-iosched.txt for details.
[...]
This is correct, but incomplete. The "elevator" kernel parameter only
controls the default schedulers for the old "blk-rq" device API.
Unfortunately, because of the differences between the old and new APIs
it was also necessary to introduce a new set of schedulers. There
isn't (yet) a kernel parameter to choose the default for blk-mq
devices.
Ben.
--
Ben Hutchings
Beware of bugs in the above code;
I have only proved it correct, not tried it. - Donald Knuth
signature.asc
Description: This is a digitally signed message part
Processed: Re: Bug#914758: linux-image-4.18.0-2-amd64: setting elevator=none does not change io scheduler
Processing control commands: > tag -1 upstream Bug #914758 [src:linux] linux-image-4.18.0-2-amd64: setting elevator=none does not change io scheduler Added tag(s) upstream. > retitle -1 Missing equivalent of elevator kernel parameter for blk-mq Bug #914758 [src:linux] linux-image-4.18.0-2-amd64: setting elevator=none does not change io scheduler Changed Bug title to 'Missing equivalent of elevator kernel parameter for blk-mq' from 'linux-image-4.18.0-2-amd64: setting elevator=none does not change io scheduler'. -- 914758: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=914758 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#914505: Acknowledgement (linux: reference to netfilter chain not removed on rule replacement, subsequently system hangs)
Control: forwarded -1 https://bugzilla.kernel.org/show_bug.cgi?id=201791
Processed: Re: Bug#914505: Acknowledgement (linux: reference to netfilter chain not removed on rule replacement, subsequently system hangs)
Processing control commands: > forwarded -1 https://bugzilla.kernel.org/show_bug.cgi?id=201791 Bug #914505 [src:linux] linux: reference to netfilter chain not removed on rule replacement, subsequently system hangs Set Bug forwarded-to-address to 'https://bugzilla.kernel.org/show_bug.cgi?id=201791'. -- 914505: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=914505 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#914758: linux-image-4.18.0-2-amd64: setting elevator=none does not change io scheduler
Package: src:linux
Version: 4.18.10-2
Severity: normal
Greetings!
Thank you for your contribution to Debian. It is appreciated!
I am running:
linux-image-4.18.0-2-amd64 4.18.10-2+b1
and attempting to set the IO scheduler.
Looking at the current scheduler:
# cat /sys/block/sda/queue/scheduler
[mq-deadline] none
However my kernel command line:
# cat /proc/cmdline
BOOT_IMAGE=/boot/vmlinuz-4.18.0-2-amd64
root=UUID=1965daa6-aa4c-4c02-8402-589867e32517 ro elevator=none quiet
I can set the scheduler via sysfs:
# echo none > /sys/block/sda/queue/scheduler
# cat /sys/block/sda/queue/scheduler
[none] mq-deadline
I just don't know why the elevator parameter isn't working. According to the
kernel documentation for 4.18:
grep -A3 elevator
/usr/src/linux-source-4.18/Documentation/admin-guide/kernel-parameters.txt
elevator= [IOSCHED]
Format: {"cfq" | "deadline" | "noop"}
See Documentation/block/cfq-iosched.txt and
Documentation/block/deadline-iosched.txt for details.
It appears that I should pass "noop" to the elevator parameter. However, the
same results occur:
# cat /proc/cmdline
BOOT_IMAGE=/boot/vmlinuz-4.18.0-2-amd64
root=UUID=1965daa6-aa4c-4c02-8402-589867e32517 ro elevator=noop quiet
# cat /sys/block/sda/queue/scheduler
[mq-deadline] none
If I look at the kernel ring buffer I see some evidence that I perhaps should
be using the "noop" scheduler:
[0.00] Command line: BOOT_IMAGE=/boot/vmlinuz-4.18.0-2-amd64
root=UUID=1965daa6-aa4c-4c02-8402-589867e32517 ro elevator=noop quiet
[0.00] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-4.18.0-2-amd64
root=UUID=1965daa6-aa4c-4c02-8402-589867e32517 ro elevator=noop quiet
[0.432773] Block layer SCSI generic (bsg) driver version 0.4 loaded (major
248)
[0.432794] io scheduler noop registered (default)
[0.432795] io scheduler deadline registered
[0.432825] io scheduler cfq registered
[0.432826] io scheduler mq-deadline registered
I see the same io scheduler registerd when I use "elevator=none", too. That is
"none" is not registered, but "noop" is.
I don't see anything in my udev configs that would be setting the scheduler.
This is a VM system.
Thanks for any help!
-- Package-specific info:
** Kernel log: boot messages should be attached
-- System Information:
Debian Release: buster/sid
APT prefers unstable
APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'), (500,
'oldstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 4.17.0-3-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 /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages linux-image-4.18.0-2-amd64 depends on:
ii initramfs-tools [linux-initramfs-tool] 0.132
ii kmod25-1
ii linux-base 4.5
Versions of packages linux-image-4.18.0-2-amd64 recommends:
ii apparmor 2.13.1-3+b1
ii firmware-linux-free 3.4
ii irqbalance 1.5.0-0.1
Versions of packages linux-image-4.18.0-2-amd64 suggests:
pn debian-kernel-handbook
ii extlinux3:6.04~git20171011.af7e95c3+dfsg1-5
ii grub-pc 2.02+dfsg1-8
pn linux-doc-4.18
Versions of packages linux-image-4.18.0-2-amd64 is related to:
ii firmware-amd-graphics 20180825+dfsg-1
pn firmware-atheros
pn firmware-bnx2
pn firmware-bnx2x
pn firmware-brcm80211
pn firmware-cavium
pn firmware-intel-sound
pn firmware-intelwimax
pn firmware-ipw2x00
pn firmware-ivtv
pn firmware-iwlwifi
pn firmware-libertas
ii firmware-linux-nonfree20180825+dfsg-1
ii firmware-misc-nonfree 20180825+dfsg-1
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
Bug#914757: Mouse Dell MS819 didn't work
Package: linux Version: 4.9.130-2 Severity: normal The mouse Dell MS819 didn't work (mouse part and fingerprint part) on Linux Debian but works perfectly on Windows 10. Dell MS819 is a mouse with fingerprint reader. The classic part of mouse (cursor and buttons) should work out of the box on same way another mouse. [535546.361651] usb 1-1.3.1: New USB device found, idVendor=413c, idProduct=3021 [535546.361654] usb 1-1.3.1: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [535546.361657] usb 1-1.3.1: Product: MS819 Dell Wired Mouse With Fingerprint Reader [535546.361659] usb 1-1.3.1: Manufacturer: Chicony [535546.364911] input: Chicony MS819 Dell Wired Mouse With Fingerprint Reader as /devices/pci:00/:00:1a.0/usb1/1-1/1-1.3/1-1.3.1/1- 1.3.1:1.0/0003:413C:3021.000F/input/input16 [535546.365315] hid-generic 0003:413C:3021.000F: input,hidraw4: USB HID v1.10 Mouse [Chicony MS819 Dell Wired Mouse With Fingerprint Reader] on usb-:00:1a.0-1.3.1/input0 [535546.370282] hid-generic 0003:413C:3021.0010: hiddev0,hidraw5: USB HID v1.10 Device [Chicony MS819 Dell Wired Mouse With Fingerprint Reader] on usb-:00:1a.0-1.3.1/input1 Nothing have been for device 413c:3021 with Google. 413c:3021 didn't exist in http://www.linux-usb.org/usb.ids https://wiki.debian.org/fr/Smartcards list 413c:2100 and 413c:2101. -- Nicolas DEFFAYET
Bug#914495: linux-image-4.18.0-3-amd64: does not boot here
I have got the same poblem lspci gives: 00:00.0 Host bridge: Intel Corporation Mobile PM965/GM965/GL960 Memory Controller Hub (rev 03) 00:02.0 VGA compatible controller: Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller (primary) (rev 03) 00:02.1 Display controller: Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller (secondary) (rev 03) 00:1a.0 USB controller: Intel Corporation 82801H (ICH8 Family) USB UHCI Controller #4 (rev 03) 00:1a.1 USB controller: Intel Corporation 82801H (ICH8 Family) USB UHCI Controller #5 (rev 03) 00:1a.7 USB controller: Intel Corporation 82801H (ICH8 Family) USB2 EHCI Controller #2 (rev 03) 00:1b.0 Audio device: Intel Corporation 82801H (ICH8 Family) HD Audio Controller (rev 03) 00:1c.0 PCI bridge: Intel Corporation 82801H (ICH8 Family) PCI Express Port 1 (rev 03) 00:1c.4 PCI bridge: Intel Corporation 82801H (ICH8 Family) PCI Express Port 5 (rev 03) 00:1d.0 USB controller: Intel Corporation 82801H (ICH8 Family) USB UHCI Controller #1 (rev 03) 00:1d.1 USB controller: Intel Corporation 82801H (ICH8 Family) USB UHCI Controller #2 (rev 03) 00:1d.7 USB controller: Intel Corporation 82801H (ICH8 Family) USB2 EHCI Controller #1 (rev 03) 00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev f3) 00:1f.0 ISA bridge: Intel Corporation 82801HM (ICH8M) LPC Interface Controller (rev 03) 00:1f.1 IDE interface: Intel Corporation 82801HM/HEM (ICH8M/ICH8M-E) IDE Controller (rev 03) 00:1f.2 SATA controller: Intel Corporation 82801HM/HEM (ICH8M/ICH8M-E) SATA Controller [AHCI mode] (rev 03) 00:1f.3 SMBus: Intel Corporation 82801H (ICH8 Family) SMBus Controller (rev 03) 14:00.0 Network controller: Intel Corporation PRO/Wireless 4965 AG or AGN [Kedron] Network Connection (rev 61) 1c:03.0 CardBus bridge: O2 Micro, Inc. OZ711SP1 Memory CardBus Controller (rev 01) 1c:03.2 SD Host controller: O2 Micro, Inc. Integrated MMC/SD Controller (rev 02) Login-in via ssh and running journalctl -b -p 4: -- Logs begin at Mon 2018-07-09 09:09:01 CEST, end at Fri 2018-11-23 10:42:39 CET. -- Nov 23 10:17:29 apollon-alt kernel: core: PEBS disabled due to CPU errata Nov 23 10:17:29 apollon-alt kernel: pmd_set_huge: Cannot satisfy [mem 0xf800-0xf820] with a huge-page mapping due to MTRR override. Nov 23 10:17:29 apollon-alt kernel: pci :00:1e.0: bridge has subordinate 1d but max busn 20 Nov 23 10:17:30 apollon-alt kernel: Unstable clock detected, switching default tracing clock to "global" If you want to keep using the local clock, then add: "trace_clock=local" on the kernel command line Nov 23 10:17:40 apollon-alt kernel: excluding 0xfc40-0xfc40 Nov 23 10:17:40 apollon-alt kernel: iwl4965 :14:00.0: can't disable ASPM; OS doesn't have ASPM control Nov 23 10:17:40 apollon-alt kernel: BUG: unable to handle kernel NULL pointer dereference at 0008 Nov 23 10:17:40 apollon-alt kernel: Oops: [#1] SMP PTI Nov 23 10:17:40 apollon-alt kernel: CPU: 1 PID: 345 Comm: systemd-udevd Not tainted 4.18.0-3-amd64 #1 Debian 4.18.20-1 Nov 23 10:17:40 apollon-alt kernel: Hardware name: FUJITSU SIEMENS LIFEBOOK P8010/FJNB1E3, BIOS Version 1.08 08/20/2008 Nov 23 10:17:40 apollon-alt kernel: RIP: 0010:gen4_render_ring_flush+0x55/0xf0 [i915] Nov 23 10:17:40 apollon-alt kernel: Code: 00 be 16 00 00 00 48 89 ef e8 87 fe ff ff 48 3d 00 f0 ff ff 77 69 89 18 c7 40 04 02 40 00 7a 48 8b 55 78 48 8b 92 10 02 00 00 <48> 8b 52 08 48 c7 40 0c 00 00 00 00 83 ca 04 89 50 08 48 8d 50 14 Nov 23 10:17:40 apollon-alt kernel: RSP: 0018:a49200a73a88 EFLAGS: 00010287 Nov 23 10:17:40 apollon-alt kernel: RAX: a49210303000 RBX: 0202 RCX: 0001ff68 Nov 23 10:17:40 apollon-alt kernel: RDX: RSI: 01a8 RDI: 0150 Nov 23 10:17:40 apollon-alt kernel: RBP: 89e0e92adb00 R08: 0001 R09: 0004 Nov 23 10:17:40 apollon-alt kernel: R10: a49200a73a58 R11: R12: 89e0e7a68000 Nov 23 10:17:40 apollon-alt kernel: R13: 89e0e96f8800 R14: R15: 89e0e92adb00 Nov 23 10:17:40 apollon-alt kernel: FS: 7fac6dd658c0() GS:89e0efd0() knlGS: Nov 23 10:17:40 apollon-alt kernel: CS: 0010 DS: ES: CR0: 80050033 Nov 23 10:17:40 apollon-alt kernel: CR2: 0008 CR3: 000127a2c000 CR4: 06e0 Nov 23 10:17:40 apollon-alt kernel: Call Trace: Nov 23 10:17:40 apollon-alt kernel: i915_request_alloc+0x243/0x360 [i915] Nov 23 10:17:40 apollon-alt kernel: i915_gem_init+0x284/0x480 [i915] Nov 23 10:17:40 apollon-alt kernel: i915_driver_load+0xb22/0xef0 [i915] Nov 23 10:17:40 apollon-alt kernel: ? mutex_lock+0xe/0x30 Nov 23 10:17:40 apollon-alt kernel: ? acpi_dev_found+0x5f/0x70 Nov 23 10:17:40 apollon-alt kernel: local_pci_probe+0x42/0xa0 Nov 23 10:17:40
Re: missing firmware in debian 9
On Freitag, 16. November 2018 08:38:51 CET Anil Duggirala wrote: > hello, > I am getting this message at boot. > > [ 10.678576] ath10k_pci :03:00.0: firmware: failed to load > ath10k/pre-cal-pci-:03:00.0.bin (-2) > [ 10.678631] ath10k_pci :03:00.0: Direct firmware load for > ath10k/pre-cal-pci-:03:00.0.bin failed with error -2 > [ 10.678655] ath10k_pci :03:00.0: firmware: failed to load > ath10k/cal-pci-:03:00.0.bin (-2) > [ 10.678699] ath10k_pci :03:00.0: Direct firmware load for > ath10k/cal-pci-:03:00.0.bin failed with error -2 > [ 10.681081] ath10k_pci :03:00.0: firmware: failed to load > ath10k/QCA6174/hw3.0/firmware-5.bin (-2) > [ 10.681127] ath10k_pci :03:00.0: Direct firmware load for > ath10k/QCA6174/hw3.0/firmware-5.bin failed with error -2 > [ 10.681131] ath10k_pci :03:00.0: could not fetch firmware file > 'ath10k/QCA6174/hw3.0/firmware-5.bin': -2 > > I have installed the firmware-atheros package from backports in Debian 9, I > had installed the package from the main repository before but I was also > getting this message. I have also installed the firmware-linux-free package. Where should Debian take it when QCA is not providing a firmware-5.bin? Kalle Valo's repo [1] contains different firmware-6.bin (which your ath10k version doesn't seem to support yet) and firmware-4.bin. And Debian ships both - I think the ones which were in linux-firmware [2] at the time of the release. I don't have a QCA6174 hw3.0 but I would guess that ath10k loaded the firmware-4.bin after it failed to load the firmware-5.bin. Kind regards, Sven [1] https://github.com/kvalo/ath10k-firmware/tree/master/QCA6174/hw3.0/ [2] https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/ signature.asc Description: This is a digitally signed message part.
