from:"Simon Iremonger"

[Kernel-packages] [Bug 1910709] Re: DKMS linux-headers-5.8.0-34-generic update brokes nvidia-340

2021-01-08 Thread Simon Iremonger

@daniel-banobre-dopico
Can you confirm this affects the 'released' (focal-updates) kernel 
5.8.0-36-generic   (install linux-generic-hwe-20.04) ?

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1910709

Title:
  DKMS linux-headers-5.8.0-34-generic update brokes nvidia-340

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Last linux kernel update "linux-headers-5.8.0-34-generic" broke
  nvidia-340 driver and Desktop access. In make log:

  [...]
  echo >&2; \
  echo >&2 "  ERROR: Kernel configuration is invalid."; \
  echo >&2 " include/generated/autoconf.h or include/config/auto.conf 
are missing.";\
  echo >&2 " Run 'make oldconfig && make prepare' on kernel src to fix 
it.";\
  echo >&2 ;
  [...]

  Full DKMS log file attacked.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.14
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-11-04 (64 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  MachineType: Gigabyte Technology Co., Ltd. H81M-D3H
  NonfreeKernelModules: nvidia
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=es_ES.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-59-generic 
root=UUID=b0ed05d5-7921-451b-b62c-773b97eeca2f ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-59.65-generic 5.4.78
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-59-generic N/A
   linux-backports-modules-5.4.0-59-generic  N/A
   linux-firmware1.187.7
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  Tags:  focal
  Uname: Linux 5.4.0-59-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: sudo
  WifiSyslog:
   
  _MarkForUpload: True
  dmi.bios.date: 01/20/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F2
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: H81M-D3H
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF2:bd01/20/2014:svnGigabyteTechnologyCo.,Ltd.:pnH81M-D3H:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnH81M-D3H:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: H81M-D3H
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.14
  Architecture: amd64
  CasperMD5CheckResult: skip
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-11-04 (64 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  MachineType: Gigabyte Technology Co., Ltd. H81M-D3H
  NonfreeKernelModules: nvidia
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=es_ES.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-59-generic 
root=UUID=b0ed05d5-7921-451b-b62c-773b97eeca2f ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-59.65-generic 5.4.78
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-59-generic N/A
   linux-backports-modules-5.4.0-59-generic  N/A
   linux-firmware1.187.7
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  Tags:  focal
  Uname: Linux 5.4.0-59-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 01/20/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F2
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: H81M-D3H
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF2:bd01/20/2014:svnGigabyteTechnologyCo.,Ltd.:pnH81M-D3H:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnH81M-D3H:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To be filled by O.E.M.

[Kernel-packages] [Bug 1903848] Re: Latest kernel update to "5.4.0-53-generic" = Internal audio, USB webcam no longer working

2021-01-03 Thread Simon Iremonger

@rivpelle
There are quite a lot of Audio-fixes in Kernel 5.4.0-59-generic which is coming 
to 20.04LTS imminently, changelog here:-

https://paste.ubuntu.com/p/vdw94dvHTy/

Additionally, it seems from focal-proposed packages,  linux-generic-
hwe-20.04  is about to cause install of 5.8.0-34-generic, on LTS ubuntu
20.04 -- i.e. support installing 5.8 kernel for hwe (new hardware
enablement).

Ideally, when 20.04.2 ubuntu image comes out next month, you can test
booting this on your system (from DVD or USB etc, no need to install)
and confirm the issue is fixed and then close the bug-report.

Note your 20.10 will need to be updated to 21.04 and then 21.10 then
22.04  to remain supported (or, you may choose to re-install 20.04.2 at
some point).

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-signed in Ubuntu.
https://bugs.launchpad.net/bugs/1903848

Title:
  Latest kernel update to "5.4.0-53-generic" = Internal audio, USB
  webcam no longer working

Status in linux-signed package in Ubuntu:
  New

Bug description:
  This seems to be a persistent problem that has been around a few
  kernel versions earlier (see i.e.:
  https://bugs.launchpad.net/ubuntu/+source/linux-signed/+bug/1881757 ).

  After yesterday's apt update to 5.4.0-53-generic (amd64), my USB
  webcam (Logitech c930) as well as my internal audio (Intel HDA)
  stopped working altogether. All I get is a dummy audio output from the
  list of devices, and the webcam is not working either.

  I can still see my pre-existing audio devices with

  
  'lspci | grep Audio':
  
  00:1b.0 Audio device: Intel Corporation 5 Series/3400 Series Chipset High 
Definition Audio (rev 05)
  01:00.1 Audio device: NVIDIA Corporation GP104 High Definition Audio 
Controller (rev a1)
  

  
  
  'inxi -SA' reports this:
  
  Audio:
    Device-1: Intel 5 Series/3400 Series High Definition Audio driver: N/A
    Device-2: NVIDIA GP104 High Definition Audio driver: N/A
  
  (The #2 NVIDIA one being the video card's audio option, which I don't use, 
but it's not listed as being available either.)

  
  However, i.e. 'pacmd -list-cards' says:
  
  0 card(s) available.
  

  There's been plenty of similar instances of this error in 20.04.x and
  it has been tried to have been solved in threads such as:

  #1 https://askubuntu.com/questions/1258510/only-dummy-output-sound-in-
  ubuntu-20-04-after-reboot-broken-driver-modul

  #2 https://www.linuxuprising.com/2018/06/fix-no-sound-dummy-output-
  issue-in.html

  
  From #2, if I try:
  
  'lsmod | grep snd_hda_intel'

  (That displays no results at all.)
  

  
  However, this one does bring results:

  'lspci -nnk | grep -A2 Audio'
  
  00:1b.0 Audio device [0403]: Intel Corporation 5 Series/3400 Series Chipset 
High Definition Audio [8086:3b56] (rev 05)
DeviceName: Intel(R) High Definition Audio Device
Subsystem: Intel Corporation 5 Series/3400 Series Chipset High 
Definition Audio [8086:0034]
Kernel modules: snd_hda_intel
  00:1c.0 PCI bridge [0604]: Intel Corporation 5 Series/3400 Series Chipset PCI 
Express Root Port 1 [8086:3b42] (rev 05)
  --
  01:00.1 Audio device [0403]: NVIDIA Corporation GP104 High Definition Audio 
Controller [10de:10f0] (rev a1)
Subsystem: NVIDIA Corporation GP104 High Definition Audio Controller 
[10de:11a3]
Kernel modules: snd_hda_intel
  

  I've been trying all the available fixes at the forementioned url #2
  to no avail, and also been trying to revert them, to no avail.

  I've been trying to run ALSA's configuration and it seems that the
  ALSA modules are not loading.

  Also been trying out various fix proposals from people who've had the
  same issue, but no luck on that frontier. Anyway, now I'm stuck with
  no webcam, no audio. Any suggestions?

  Thanks.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-signed/+bug/1903848/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1813509] Re: [i915] NULL pointer on Linux 4.18.0-14-generic / cosmic

2021-01-03 Thread Simon Iremonger

@illweckz
Please try to close the bug as it seems to apply only to unsupported ubuntu 
versions and fixed on current LTS kernel (5.4).

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-signed in Ubuntu.
https://bugs.launchpad.net/bugs/1813509

Title:
  [i915] NULL pointer on Linux 4.18.0-14-generic / cosmic

Status in linux-signed package in Ubuntu:
  Confirmed

Bug description:
  After updated an old laptop to Ubuntu Cosmic (was running Xenial
  before) the graphic hangs at startup, nothing is displayed but a grey
  screen (grub residual), note that the recovery boot option using
  `nodmodeset` displays a text console and I'm still able to log-in over
  a serial tty on normal boot so kernel is alive but computer is not
  usable due to lack graphic support.

  Computer is a Thinkpad X61 Tablet plugged on an X6 Tablet UltraBase
  - http://www.thinkwiki.org/wiki/Category:X61_Tablet
  - http://www.thinkwiki.org/wiki/ThinkPad_X6_Tablet_UltraBase
  GPU is an Intel GMA X3100
  - http://www.thinkwiki.org/wiki/Intel_Graphics_Media_Accelerator_X3100

  Some information:

  # lsb_release -a
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu 18.10
  Release:  18.10
  Codename: cosmic

  # uname -a
  Linux arwen 4.18.0-14-generic #15-Ubuntu SMP Mon Jan 14 09:01:02 UTC 2019 
x86_64 x86_64 x86_64 GNU/Linux

  # lspci -vvv -nn -s 00:02.0
  00:02.0 VGA compatible controller [0300]: Intel Corporation Mobile 
GM965/GL960 Integrated Graphics Controller (primary) [8086:2a02] (rev 0c) 
(prog-if 00 [VGA controller])
Subsystem: Lenovo GM965 [X3100] on ThinkPad T61/R61 [17aa:20b5]
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR-  8b 52 
08 48 c7 40 0c 00 00 00 00 83 ca 04 89 50 08 48 8d 50 14 
  [2.709180] RSP: 0018:c2718067b978 EFLAGS: 00010287
  [2.709180] RAX: c27190303000 RBX: 9e5533e87200 RCX: 
c27190303044
  [2.709180] RDX:  RSI: 01a8 RDI: 
0150
  [2.709180] RBP: c2718067b988 R08: 0001 R09: 
0002
  [2.709180] R10: 0001 R11: 9e5533e87200 R12: 
0202
  [2.709180] R13: 9e5533e87200 R14: 9e553380ac00 R15: 
9e5533ab8000
  [2.709180] FS:  7fd9f63c88c0() GS:9e557e40() 
knlGS:
  [2.709180] CS:  0010 DS:  ES:  CR0: 80050033
  [2.709180] CR2: 0008 CR3: 34302000 CR4: 
06f0
  [2.709180] Call Trace:
  [2.709180]  i915_request_alloc+0x24e/0x370 [i915]
  [2.709180]  i915_gem_init+0x26b/0x470 [i915]
  [2.709180]  i915_driver_load+0xab8/0xd80 [i915]
  [2.709180]  ? mutex_lock+0x12/0x30
  [2.709180]  i915_pci_probe+0x46/0x60 [i915]
  [2.709180]  local_pci_probe+0x46/0x90
  [2.709180]  pci_device_probe+0x11c/0x1a0
  [2.709180]  driver_probe_device+0x2e3/0x460
  [2.709180]  __driver_attach+0xe4/0x110
  [2.709180]  ? driver_probe_device+0x460/0x460
  [2.709180]  bus_for_each_dev+0x74/0xb0
  [2.709180]  ? kmem_cache_alloc_trace+0x1c4/0x1d0
  [2.709180]  driver_attach+0x1e/0x20
  [2.709180]  bus_add_driver+0x159/0x230
  [2.709180]  ? 0xc0474000
  [2.709180]  driver_register+0x70/0xc0
  [2.709180]  ? 0xc0474000
  [2.709180]  __pci_register_driver+0x57/0x60
  [2.709180]  i915_init+0x55/0x58 [i915]
  [2.709180]  do_one_initcall+0x4a/0x1c4
  [2.709180]  ? _cond_resched+0x19/0x30
  [2.709180]  ? kmem_cache_alloc_trace+0xb8/0x1d0
  [2.709180]  ? do_init_module+0x27/0x220
  [2.709180]  do_init_module+0x60/0x220
  [2.709180]  load_module+0x14f4/0x1890
  [2.709180]  __do_sys_finit_module+0xbd/0x120
  [2.709180]  ? __do_sys_finit_module+0xbd/0x120
  [2.709180]  __x64_sys_finit_module+0x1a/0x20
  [2.709180]  do_syscall_64+0x5a/0x110
  [2.709180]  entry_SYSCALL_64_after_hwframe+0x44/0xa9
  [2.709180] RIP: 0033:0x7fd9f6e4d219
  [2.709180] Code: 00 c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 00 00 48 89 
f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 
f0 ff ff 73 01 c3 48 8b 0d 47 fc 0c 00 f7 d8 64 89 01 48 
  [2.709180] RSP: 002b:7ffc11865868 EFLAGS: 0246 ORIG_RAX: 
0139
  [2.709180] RAX: ffda RBX: 5580d38f98c0 RCX: 
7fd9f6e4d219
  [2.709180] RDX:  RSI: 7fd9f6d31cad RDI: 
0012
  [2.709180] RBP: 7fd9f6d31cad R08:  R09: 

  [2.709180] R10: 0012 R11: 0246 R12: 

  [2.709180] R13: 5580d3913ae0 R14: 0002 R15: 
5580d38f98c0
  [2.709180] Modules linked in: gpio_ich i915(+) i2c_algo_bit 
drm_kms_helper

[Kernel-packages] [Bug 1460447] Re: Boot slow, "scanning for btrfs filesystems" takes 100 seconds

2020-10-01 Thread Simon Iremonger

I can confirm my specific failure was fixed with kernel 5.4.0-48 ...

Question for original reporter Dan -- is this issue (slow btrfs
scanning) still occuring for you?  Now fixed?

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1460447

Title:
  Boot slow, "scanning for btrfs filesystems" takes 100 seconds

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I installed 14.10 and used btrfs for /home.  Later, I did a clean install of 
15.04, using the same /home partition.
  Ever since then, boots have been agonizingly slow; all the delay appears to 
be while the message
  "scanning for btrfs filesystems" is diplayed early in boot.

  The system is an i7 with one disk:

  root@i7:~# fdisk /dev/sda
  Disk /dev/sda: 931.5 GiB, 1000204886016 bytes, 1953525168 sectors
  Units: sectors of 1 * 512 = 512 bytes
  Sector size (logical/physical): 512 bytes / 4096 bytes
  I/O size (minimum/optimal): 4096 bytes / 4096 bytes
  Disklabel type: dos
  Disk identifier: 0x7f84

  Device Boot StartEndSectors   Size Id Type
  /dev/sda1  * 2048  117186559  117184512  55.9G 83 Linux
  /dev/sda2   117186560  234373119  117186560  55.9G 83 Linux
  /dev/sda3   234375166 1953523711 1719148546 819.8G  5 Extended
  /dev/sda5   234375168  273434623   39059456  18.6G 82 Linux swap / Solaris
  /dev/sda6   273436672 1953523711 1680087040 801.1G 83 Linux

  root@i7:~# df -T | grep sd
  /dev/sda2  ext4  57542652  10103624  44492980  19% /
  /dev/sda6  btrfs840043520 172076728 665321064  21% /home

  I'll attach a bootchart, but I suspect the btrfs delay happens before
  the bootchart starts?

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: linux-image-3.19.0-16-generic 3.19.0-16.16
  ProcVersionSignature: Ubuntu 3.19.0-16.16-generic 3.19.3
  Uname: Linux 3.19.0-16-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.17.2-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  dank   2176 F pulseaudio
   /dev/snd/controlC0:  dank   2176 F pulseaudio
  CurrentDesktop: Unity
  Date: Sun May 31 08:53:37 2015
  HibernationDevice: RESUME=UUID=417f2bba-dea3-496b-ad18-702d4dc6f223
  InstallationDate: Installed on 2015-05-16 (14 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  IwConfig:
   eth0  no wireless extensions.
   
   lono wireless extensions.
   
   lxcbr0no wireless extensions.
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-16-generic 
root=UUID=270a0d36-9ed9-4e58-b909-175db447838d ro quiet splash 
init=/lib/systemd/systemd-bootchart
  RelatedPackageVersions:
   linux-restricted-modules-3.19.0-16-generic N/A
   linux-backports-modules-3.19.0-16-generic  N/A
   linux-firmware 1.143
  RfKill:
   
  SourcePackage: linux
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/16/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P2.50
  dmi.board.name: X58 Extreme
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP2.50:bd08/16/2010:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnX58Extreme:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1460447/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1460447] Re: Boot slow, "scanning for btrfs filesystems" takes 100 seconds

2020-08-30 Thread Simon Iremonger

OK Turns out my btrfs+floppy bug is indeed a kernel floppy matter, and
the btrfs scan just 'triggers' the fault.

The new kernel floppy maintainer says:-
This patch should fix the problem:
263c61581a38 ("block/floppy: fix contended case in floppy_queue_rq()")
The commit id in stable tree is 29ed45653bec.

> ubuntu kernel 5.4.0-42-generic
I think that these versions don't contain the fix. The fix is in the
5.4 kernel since 5.4.47 version.

SO, looks like my related comment is a red-herring and (should) be fixed
by routine updates to 5.4.0 ubuntu kernel updates!.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1460447

Title:
  Boot slow, "scanning for btrfs filesystems" takes 100 seconds

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I installed 14.10 and used btrfs for /home.  Later, I did a clean install of 
15.04, using the same /home partition.
  Ever since then, boots have been agonizingly slow; all the delay appears to 
be while the message
  "scanning for btrfs filesystems" is diplayed early in boot.

  The system is an i7 with one disk:

  root@i7:~# fdisk /dev/sda
  Disk /dev/sda: 931.5 GiB, 1000204886016 bytes, 1953525168 sectors
  Units: sectors of 1 * 512 = 512 bytes
  Sector size (logical/physical): 512 bytes / 4096 bytes
  I/O size (minimum/optimal): 4096 bytes / 4096 bytes
  Disklabel type: dos
  Disk identifier: 0x7f84

  Device Boot StartEndSectors   Size Id Type
  /dev/sda1  * 2048  117186559  117184512  55.9G 83 Linux
  /dev/sda2   117186560  234373119  117186560  55.9G 83 Linux
  /dev/sda3   234375166 1953523711 1719148546 819.8G  5 Extended
  /dev/sda5   234375168  273434623   39059456  18.6G 82 Linux swap / Solaris
  /dev/sda6   273436672 1953523711 1680087040 801.1G 83 Linux

  root@i7:~# df -T | grep sd
  /dev/sda2  ext4  57542652  10103624  44492980  19% /
  /dev/sda6  btrfs840043520 172076728 665321064  21% /home

  I'll attach a bootchart, but I suspect the btrfs delay happens before
  the bootchart starts?

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: linux-image-3.19.0-16-generic 3.19.0-16.16
  ProcVersionSignature: Ubuntu 3.19.0-16.16-generic 3.19.3
  Uname: Linux 3.19.0-16-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.17.2-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  dank   2176 F pulseaudio
   /dev/snd/controlC0:  dank   2176 F pulseaudio
  CurrentDesktop: Unity
  Date: Sun May 31 08:53:37 2015
  HibernationDevice: RESUME=UUID=417f2bba-dea3-496b-ad18-702d4dc6f223
  InstallationDate: Installed on 2015-05-16 (14 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  IwConfig:
   eth0  no wireless extensions.
   
   lono wireless extensions.
   
   lxcbr0no wireless extensions.
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-16-generic 
root=UUID=270a0d36-9ed9-4e58-b909-175db447838d ro quiet splash 
init=/lib/systemd/systemd-bootchart
  RelatedPackageVersions:
   linux-restricted-modules-3.19.0-16-generic N/A
   linux-backports-modules-3.19.0-16-generic  N/A
   linux-firmware 1.143
  RfKill:
   
  SourcePackage: linux
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/16/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P2.50
  dmi.board.name: X58 Extreme
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP2.50:bd08/16/2010:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnX58Extreme:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1460447/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1460447] Re: Boot slow, "scanning for btrfs filesystems" takes 100 seconds

2020-08-30 Thread Simon Iremonger

I can further confirm that taking out the btrfs scan in  /usr/share
/initramfs-tools/scripts/local-premount/btrfs  fixes the intermittent
boot issue for me.  For me, this causes some deadlock between btfs scan
and floppy driver and requires reboot, not just slow!.  This may be a
case of 'separate bug needed' .

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1460447

Title:
  Boot slow, "scanning for btrfs filesystems" takes 100 seconds

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I installed 14.10 and used btrfs for /home.  Later, I did a clean install of 
15.04, using the same /home partition.
  Ever since then, boots have been agonizingly slow; all the delay appears to 
be while the message
  "scanning for btrfs filesystems" is diplayed early in boot.

  The system is an i7 with one disk:

  root@i7:~# fdisk /dev/sda
  Disk /dev/sda: 931.5 GiB, 1000204886016 bytes, 1953525168 sectors
  Units: sectors of 1 * 512 = 512 bytes
  Sector size (logical/physical): 512 bytes / 4096 bytes
  I/O size (minimum/optimal): 4096 bytes / 4096 bytes
  Disklabel type: dos
  Disk identifier: 0x7f84

  Device Boot StartEndSectors   Size Id Type
  /dev/sda1  * 2048  117186559  117184512  55.9G 83 Linux
  /dev/sda2   117186560  234373119  117186560  55.9G 83 Linux
  /dev/sda3   234375166 1953523711 1719148546 819.8G  5 Extended
  /dev/sda5   234375168  273434623   39059456  18.6G 82 Linux swap / Solaris
  /dev/sda6   273436672 1953523711 1680087040 801.1G 83 Linux

  root@i7:~# df -T | grep sd
  /dev/sda2  ext4  57542652  10103624  44492980  19% /
  /dev/sda6  btrfs840043520 172076728 665321064  21% /home

  I'll attach a bootchart, but I suspect the btrfs delay happens before
  the bootchart starts?

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: linux-image-3.19.0-16-generic 3.19.0-16.16
  ProcVersionSignature: Ubuntu 3.19.0-16.16-generic 3.19.3
  Uname: Linux 3.19.0-16-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.17.2-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  dank   2176 F pulseaudio
   /dev/snd/controlC0:  dank   2176 F pulseaudio
  CurrentDesktop: Unity
  Date: Sun May 31 08:53:37 2015
  HibernationDevice: RESUME=UUID=417f2bba-dea3-496b-ad18-702d4dc6f223
  InstallationDate: Installed on 2015-05-16 (14 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  IwConfig:
   eth0  no wireless extensions.
   
   lono wireless extensions.
   
   lxcbr0no wireless extensions.
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-16-generic 
root=UUID=270a0d36-9ed9-4e58-b909-175db447838d ro quiet splash 
init=/lib/systemd/systemd-bootchart
  RelatedPackageVersions:
   linux-restricted-modules-3.19.0-16-generic N/A
   linux-backports-modules-3.19.0-16-generic  N/A
   linux-firmware 1.143
  RfKill:
   
  SourcePackage: linux
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/16/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P2.50
  dmi.board.name: X58 Extreme
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP2.50:bd08/16/2010:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnX58Extreme:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1460447/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1460447] Re: Boot slow, "scanning for btrfs filesystems" takes 100 seconds

2020-08-29 Thread Simon Iremonger

Oh, and to be clear, both said machines floppy working properly!  Not
just faulty drive giving timeouts.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1460447

Title:
  Boot slow, "scanning for btrfs filesystems" takes 100 seconds

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I installed 14.10 and used btrfs for /home.  Later, I did a clean install of 
15.04, using the same /home partition.
  Ever since then, boots have been agonizingly slow; all the delay appears to 
be while the message
  "scanning for btrfs filesystems" is diplayed early in boot.

  The system is an i7 with one disk:

  root@i7:~# fdisk /dev/sda
  Disk /dev/sda: 931.5 GiB, 1000204886016 bytes, 1953525168 sectors
  Units: sectors of 1 * 512 = 512 bytes
  Sector size (logical/physical): 512 bytes / 4096 bytes
  I/O size (minimum/optimal): 4096 bytes / 4096 bytes
  Disklabel type: dos
  Disk identifier: 0x7f84

  Device Boot StartEndSectors   Size Id Type
  /dev/sda1  * 2048  117186559  117184512  55.9G 83 Linux
  /dev/sda2   117186560  234373119  117186560  55.9G 83 Linux
  /dev/sda3   234375166 1953523711 1719148546 819.8G  5 Extended
  /dev/sda5   234375168  273434623   39059456  18.6G 82 Linux swap / Solaris
  /dev/sda6   273436672 1953523711 1680087040 801.1G 83 Linux

  root@i7:~# df -T | grep sd
  /dev/sda2  ext4  57542652  10103624  44492980  19% /
  /dev/sda6  btrfs840043520 172076728 665321064  21% /home

  I'll attach a bootchart, but I suspect the btrfs delay happens before
  the bootchart starts?

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: linux-image-3.19.0-16-generic 3.19.0-16.16
  ProcVersionSignature: Ubuntu 3.19.0-16.16-generic 3.19.3
  Uname: Linux 3.19.0-16-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.17.2-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  dank   2176 F pulseaudio
   /dev/snd/controlC0:  dank   2176 F pulseaudio
  CurrentDesktop: Unity
  Date: Sun May 31 08:53:37 2015
  HibernationDevice: RESUME=UUID=417f2bba-dea3-496b-ad18-702d4dc6f223
  InstallationDate: Installed on 2015-05-16 (14 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  IwConfig:
   eth0  no wireless extensions.
   
   lono wireless extensions.
   
   lxcbr0no wireless extensions.
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-16-generic 
root=UUID=270a0d36-9ed9-4e58-b909-175db447838d ro quiet splash 
init=/lib/systemd/systemd-bootchart
  RelatedPackageVersions:
   linux-restricted-modules-3.19.0-16-generic N/A
   linux-backports-modules-3.19.0-16-generic  N/A
   linux-firmware 1.143
  RfKill:
   
  SourcePackage: linux
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/16/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P2.50
  dmi.board.name: X58 Extreme
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP2.50:bd08/16/2010:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnX58Extreme:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1460447/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1460447] Re: Boot slow, "scanning for btrfs filesystems" takes 100 seconds

2020-08-29 Thread Simon Iremonger

This issue, or variant thereof, has been observed on Ubuntu 20.04 and Linux 
Mint 20.
I'm not 100% sure yet but it SEEMS to be affecting systems with a floppy drive.

Can end up with bootup-messages:-

[timestamp] Btrfs loaded, crc32c=crc32c-generic
Scanning for Btrfs filesystems
[timestamp] floppy0: floppy_queue_rq: timeout handler died.  old request running

removing 'btrfs-progs' (which then removes from initrd) works around the issue 
reliably.
I need to double-check, i think kernel command line  modprobe.blacklist=floppy  
 can also workaround issue.
Last I checked, I didn't find this to be specific to a particular kernel/series.

Certainly experienced this on totally different hardwre, e.g. an intel
core-2-duo in compaq Dx2300,  but also on a completely different HP
motherboard AMD64 machine/chipset.  From what I can see this is not
particular hardware specific either!.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1460447

Title:
  Boot slow, "scanning for btrfs filesystems" takes 100 seconds

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I installed 14.10 and used btrfs for /home.  Later, I did a clean install of 
15.04, using the same /home partition.
  Ever since then, boots have been agonizingly slow; all the delay appears to 
be while the message
  "scanning for btrfs filesystems" is diplayed early in boot.

  The system is an i7 with one disk:

  root@i7:~# fdisk /dev/sda
  Disk /dev/sda: 931.5 GiB, 1000204886016 bytes, 1953525168 sectors
  Units: sectors of 1 * 512 = 512 bytes
  Sector size (logical/physical): 512 bytes / 4096 bytes
  I/O size (minimum/optimal): 4096 bytes / 4096 bytes
  Disklabel type: dos
  Disk identifier: 0x7f84

  Device Boot StartEndSectors   Size Id Type
  /dev/sda1  * 2048  117186559  117184512  55.9G 83 Linux
  /dev/sda2   117186560  234373119  117186560  55.9G 83 Linux
  /dev/sda3   234375166 1953523711 1719148546 819.8G  5 Extended
  /dev/sda5   234375168  273434623   39059456  18.6G 82 Linux swap / Solaris
  /dev/sda6   273436672 1953523711 1680087040 801.1G 83 Linux

  root@i7:~# df -T | grep sd
  /dev/sda2  ext4  57542652  10103624  44492980  19% /
  /dev/sda6  btrfs840043520 172076728 665321064  21% /home

  I'll attach a bootchart, but I suspect the btrfs delay happens before
  the bootchart starts?

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: linux-image-3.19.0-16-generic 3.19.0-16.16
  ProcVersionSignature: Ubuntu 3.19.0-16.16-generic 3.19.3
  Uname: Linux 3.19.0-16-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.17.2-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  dank   2176 F pulseaudio
   /dev/snd/controlC0:  dank   2176 F pulseaudio
  CurrentDesktop: Unity
  Date: Sun May 31 08:53:37 2015
  HibernationDevice: RESUME=UUID=417f2bba-dea3-496b-ad18-702d4dc6f223
  InstallationDate: Installed on 2015-05-16 (14 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  IwConfig:
   eth0  no wireless extensions.
   
   lono wireless extensions.
   
   lxcbr0no wireless extensions.
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-16-generic 
root=UUID=270a0d36-9ed9-4e58-b909-175db447838d ro quiet splash 
init=/lib/systemd/systemd-bootchart
  RelatedPackageVersions:
   linux-restricted-modules-3.19.0-16-generic N/A
   linux-backports-modules-3.19.0-16-generic  N/A
   linux-firmware 1.143
  RfKill:
   
  SourcePackage: linux
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/16/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P2.50
  dmi.board.name: X58 Extreme
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP2.50:bd08/16/2010:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnX58Extreme:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1460447/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1436945] Re: devel: consider fq_codel as the default qdisc for networking

2018-05-25 Thread Simon Iremonger

Launchpad issue link didn't come out -- LP #1773157
https://bugs.launchpad.net/ubuntu/+source/procps/+bug/1773157

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1436945

Title:
  devel: consider fq_codel as the default qdisc for networking

Status in linux package in Ubuntu:
  Fix Released
Status in linux package in Debian:
  New

Bug description:
  This was raised on the kernel-team@ mailing list, we should look at
  this if other distros are starting to move.

  ===

  Date: Tue, 24 Mar 2015 10:54:37 -0700 
 
  From: Dave Taht  
 
  To: Joseph Salisbury  
 
  Cc: Kernel Team , ubuntu-de...@lists.ubuntu.com 
 
  Subject: Re: Minutes from the Ubuntu Kernel Team meeting, 2015-03-24  
 

 
  I must confess I had hoped ubuntu would adopt fq_codel as the default 
 
  qdisc in this go-around. It is still not quite part of fedora´s   
 
  default either, but is now in arch, (and nearly everyone else 
 
  downstream from systemd), and has long been the default in openwrt,   
 
  and at this point, just requires a single sysctl to enable.   
 

 
  It certainly could use more widespread testing, perhaps in the next release?  
 

 
  d@nuc-client:~$ cat /etc/sysctl.d/10-bufferbloat.conf 
 
  net.core.default_qdisc=fq_codel

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1436945/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1436945] Re: devel: consider fq_codel as the default qdisc for networking

2018-05-25 Thread Simon Iremonger

Interestingly, turns out that seemingly systemd is what is (currently)
responsible for turning on fq_codel by default.  See:-

https://github.com/systemd/systemd/commit/e6c253e363dee77ef7e5c5f44c4ca55cded3fd47

Be nice to then get that suggested into upstream linux as a default
and/or procps for 'non-systemd' booting.   Also see   #1773157  -- ECN
really needs to be properly enabled to give the best benefit for
congestion with TCP streams present.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1436945

Title:
  devel: consider fq_codel as the default qdisc for networking

Status in linux package in Ubuntu:
  Fix Released
Status in linux package in Debian:
  New

Bug description:
  This was raised on the kernel-team@ mailing list, we should look at
  this if other distros are starting to move.

  ===

  Date: Tue, 24 Mar 2015 10:54:37 -0700 
 
  From: Dave Taht  
 
  To: Joseph Salisbury  
 
  Cc: Kernel Team , ubuntu-de...@lists.ubuntu.com 
 
  Subject: Re: Minutes from the Ubuntu Kernel Team meeting, 2015-03-24  
 

 
  I must confess I had hoped ubuntu would adopt fq_codel as the default 
 
  qdisc in this go-around. It is still not quite part of fedora´s   
 
  default either, but is now in arch, (and nearly everyone else 
 
  downstream from systemd), and has long been the default in openwrt,   
 
  and at this point, just requires a single sysctl to enable.   
 

 
  It certainly could use more widespread testing, perhaps in the next release?  
 

 
  d@nuc-client:~$ cat /etc/sysctl.d/10-bufferbloat.conf 
 
  net.core.default_qdisc=fq_codel

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1436945/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1436945] Re: devel: consider fq_codel as the default qdisc for networking

2018-05-24 Thread Simon Iremonger

>From what I can see, updates in ubuntu have now fixed this, bionic
system certainly seems to now be booting with
/proc/sys/net/core/default_qdisc = fq_codel   now!.

Can somebody confirm this and close this bug as 'fixed' ?


SECONDLY, Related bufferbloat-matter to make fq_codel work better to avoid 
packet-drops is outbound tcp ECN-enablement on ubuntu end-hosts -- please see 
related ubuntu bug #1773157 and mark/comment there please:-

https://bugs.launchpad.net/ubuntu/+source/procps/+bug/1773157

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1436945

Title:
  devel: consider fq_codel as the default qdisc for networking

Status in linux package in Ubuntu:
  Confirmed
Status in linux package in Debian:
  New

Bug description:
  This was raised on the kernel-team@ mailing list, we should look at
  this if other distros are starting to move.

  ===

  Date: Tue, 24 Mar 2015 10:54:37 -0700 
 
  From: Dave Taht  
 
  To: Joseph Salisbury  
 
  Cc: Kernel Team , ubuntu-de...@lists.ubuntu.com 
 
  Subject: Re: Minutes from the Ubuntu Kernel Team meeting, 2015-03-24  
 

 
  I must confess I had hoped ubuntu would adopt fq_codel as the default 
 
  qdisc in this go-around. It is still not quite part of fedora´s   
 
  default either, but is now in arch, (and nearly everyone else 
 
  downstream from systemd), and has long been the default in openwrt,   
 
  and at this point, just requires a single sysctl to enable.   
 

 
  It certainly could use more widespread testing, perhaps in the next release?  
 

 
  d@nuc-client:~$ cat /etc/sysctl.d/10-bufferbloat.conf 
 
  net.core.default_qdisc=fq_codel

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1436945/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1910709] Re: DKMS linux-headers-5.8.0-34-generic update brokes nvidia-340

[Kernel-packages] [Bug 1903848] Re: Latest kernel update to "5.4.0-53-generic" = Internal audio, USB webcam no longer working

[Kernel-packages] [Bug 1813509] Re: [i915] NULL pointer on Linux 4.18.0-14-generic / cosmic

[Kernel-packages] [Bug 1460447] Re: Boot slow, "scanning for btrfs filesystems" takes 100 seconds

[Kernel-packages] [Bug 1460447] Re: Boot slow, "scanning for btrfs filesystems" takes 100 seconds

[Kernel-packages] [Bug 1460447] Re: Boot slow, "scanning for btrfs filesystems" takes 100 seconds

[Kernel-packages] [Bug 1460447] Re: Boot slow, "scanning for btrfs filesystems" takes 100 seconds

[Kernel-packages] [Bug 1460447] Re: Boot slow, "scanning for btrfs filesystems" takes 100 seconds

[Kernel-packages] [Bug 1436945] Re: devel: consider fq_codel as the default qdisc for networking

[Kernel-packages] [Bug 1436945] Re: devel: consider fq_codel as the default qdisc for networking

[Kernel-packages] [Bug 1436945] Re: devel: consider fq_codel as the default qdisc for networking

11 matches

Site Navigation

Mail list logo

Footer information