date:20201104

[Kernel-packages] [Bug 1902895] Re: WiFi loses connection on an irregular basis probably due to buffer overflow

2020-11-04 Thread Aleksander Miera

It *seems* better in the sense that the problem appears later, say after
20 minutes of operation instead of 5. Nevertheless, it's not 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/1902895

Title:
  WiFi loses connection on an irregular basis probably due to buffer
  overflow

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Dell XPS13, Ubuntu 20.10, kernel 5.8.
  I cannot pinpoint the exact scenario, but it happens most often when trying 
to build Xorg-master from source via their build.sh script.
  Setup: WiFi connected, xorg is built in terminal window. Speculatively I 
would say it say realted to trasferring large number of small files, but I 
don't have any hard evidence to prove that.

  To depict it better:
  A Main terminal (and let it run):
  $ ./util/modular/build.sh --clone $HOME/build
  B Second terminal (and let it run):
  $ ping www.onet.pl #any host should do, just using popular news site as an 
example
  C Third terminal (optionally)
  # dmesg -w

  At some point of build.sh cloning, the other terminal (B) starts to display 
this:
  64 bytes from sg1.any.onet.pl (213.180.141.140): icmp_seq=151 ttl=58 
time=20.2 ms #that's ok
  ping: sendmsg: No buffer space available
  ping: sendmsg: No buffer space available
  ping: sendmsg: No buffer space available
  It usually happens when A is in the middle of git clone, which just hangs 
there.
  Nothing displayed by dmesg.
  All other network activity stalls (but not fails). Waiting ca. 5 minutes does 
not help.
  WiFi icon indicates everything's fine.
  Restarting WiFi (either using the icon or with rfkill, ifconfig should 
probably work too) restores connectivity, but breaks all the stalled activity, 
e.g. scripts, git etc.

  Increasing /proc/sys/net/core/wmem_max delays the problem and allows
  one or two clones to complete in the given example.

  I have observed that on 18.04, 20.04 and 20.10, with the default
  kernels i.e. 5.4 and 5.8. Scenario in each case is exactly the same.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: linux-image-5.8.0-25-generic 5.8.0-25.26
  ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14
  Uname: Linux 5.8.0-25-generic x86_64
  ApportVersion: 2.20.11-0ubuntu50
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dladmin1368 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Nov  4 15:51:00 2020
  InstallationDate: Installed on 2020-10-26 (9 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 0c45:670c Microdia Integrated Webcam HD
   Bus 001 Device 003: ID 04f3:2234 Elan Microelectronics Corp. Touchscreen
   Bus 001 Device 002: ID 0cf3:e300 Qualcomm Atheros Communications QCA61x4 
Bluetooth 4.0
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. XPS 13 9360
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-25-generic 
root=UUID=746d5f05-e21a-42c5-9191-a65c526a3305 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.8.0-25-generic N/A
   linux-backports-modules-5.8.0-25-generic  N/A
   linux-firmware1.190
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/14/2019
  dmi.bios.release: 2.13
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 2.13.0
  dmi.board.name: 0839Y6
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr2.13.0:bd11/14/2019:br2.13:svnDellInc.:pnXPS139360:pvr:rvnDellInc.:rn0839Y6:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 9360
  dmi.product.sku: 075B
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1902895/+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 1856608] Re: [Regression] usb usb2-port2: Cannot enable. Maybe the USB cable is bad?

2020-11-04 Thread Motiejus

Sorry, that was not the kernel. It was (is?) a bad usb socket. I plugged
the monitor to a different usb-c port and it works without complaints on
all tried kernels (5.6, 5.8, 5.9).

Device: "20NYS8QG0B (LENOVO_MT_20NY_BU_Think_FM_ThinkPad T490s)"

-- 
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/1856608

Title:
  [Regression] usb usb2-port2: Cannot enable. Maybe the USB cable is
  bad?

Status in linux package in Ubuntu:
  Incomplete
Status in linux source package in Bionic:
  Fix Released
Status in linux source package in Disco:
  Fix Released
Status in linux source package in Eoan:
  Fix Released
Status in linux source package in Focal:
  Incomplete

Bug description:
  This appears to be a regression between 4.15.0-70.79 and 4.15.0-72.81.
  This bug was fixed by simply reverting the offending change. Bug 1859873 
tracks root causing the issue and reapplying the change w/ any necessary fixes.

  [Impact]
  USB port unusable and boot time takes ~5 minutes longer to complete.

  Kernel emits messages like:
  usb usb2-port2: Cannot enable. Maybe the USB cable is bad?

  [Test Case]
  dmesg | grep "Cannot enable"

  [Fix]
  [Regression Risk]

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1856608/+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 1901470] Re: [modeset][i915] Native resolution (EDID detailed mode) of 2560x1440 not listed, defaults to 1920x1080 instead

2020-11-04 Thread Kai-Heng Feng

Please test latest drm-tip kernel:
https://kernel.ubuntu.com/~kernel-ppa/mainline/drm-tip/current/

And file a bug agains Intel graphics if the issue persists:
https://gitlab.freedesktop.org/drm/intel/wikis/How-to-file-i915-bugs

-- 
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/1901470

Title:
  [modeset][i915] Native resolution (EDID detailed mode) of 2560x1440
  not listed, defaults to 1920x1080 instead

Status in linux package in Ubuntu:
  Confirmed
Status in xorg-server package in Ubuntu:
  Confirmed

Bug description:
  The PG278QR monitor supports 2560x1440.  After installing Ubuntu 20.4,
  the max resolution presented in the Settings app is 1920x1080, and
  this resolution is the one that it uses.  Switching between the Nvidia
  driver or the Intel driver (laptop has low-power intel gpu too)
  doesn't correct the problem.

  Digging in deeper, based on
  
https://wiki.ubuntu.com/X/Troubleshooting/Resolution#Problem:__Wrong_resolutions.2C_refresh_rates.2C_or_monitor_specs

  Under Wrong resolutions/refresh rates/or monitor specs, step 3 is to
  use get-edid | parse-edid.

  After applying the mode that I wanted manually via xrandr --newmode
  and xrandr --addmode, I was able to select the max resolution of the
  monitor and works correctly, until reboot.  I will add it to my
  xorg.conf next.

  Here is information I collected:

  output from xrandr after fresh boot:

  ~$ xrandr
  Screen 0: minimum 8 x 8, current 3840 x 1080, maximum 32767 x 32767
  eDP-1-1 connected primary 1920x1080+0+0 (normal left inverted right x axis y 
axis) 344mm x 193mm
 1920x1080 60.01*+  60.0159.9759.9659.93  
 1680x1050 59.9559.88  
 1600x1024 60.17  
 1400x1050 59.98  
 1600x900  59.9959.9459.9559.82  
 1280x1024 60.02  
 1440x900  59.89  
 1400x900  59.9659.88  
 1280x960  60.00  
 1440x810  60.0059.97  
 1368x768  59.8859.85  
 1360x768  59.8059.96  
 1280x800  59.9959.9759.8159.91  
 1152x864  60.00  
 1280x720  60.0059.9959.8659.74  
 1024x768  60.0460.00  
 960x720   60.00  
 928x696   60.05  
 896x672   60.01  
 1024x576  59.9559.9659.9059.82  
 960x600   59.9360.00  
 960x540   59.9659.9959.6359.82  
 800x600   60.0060.3256.25  
 840x525   60.0159.88  
 864x486   59.9259.57  
 800x512   60.17  
 700x525   59.98  
 800x450   59.9559.82  
 640x512   60.02  
 720x450   59.89  
 700x450   59.9659.88  
 640x480   60.0059.94  
 720x405   59.5158.99  
 684x384   59.8859.85  
 680x384   59.8059.96  
 640x400   59.8859.98  
 576x432   60.06  
 640x360   59.8659.8359.8459.32  
 512x384   60.00  
 512x288   60.0059.92  
 480x270   59.6359.82  
 400x300   60.3256.34  
 432x243   59.9259.57  
 320x240   60.05  
 360x202   59.5159.13  
 320x180   59.8459.32  
  HDMI-1-1 connected 1920x1080+1920+0 (normal left inverted right x axis y 
axis) 598mm x 336mm
 1920x1080 60.00*   50.0059.94  
 1280x720  60.0050.0059.94  
 1024x768  60.00  
 800x600   60.32  
 720x576   50.00  
 720x480   60.0059.94  
 640x480   60.0059.94  
  DP-1-1 disconnected (normal left inverted right x axis y axis)

  output from get-edid | parse-edid:
  ~$ sudo get-edid | parse-edid
  This is read-edid version 3.0.2. Prepare for some fun.
  Attempting to use i2c interface
  No EDID on bus 1
  No EDID on bus 2
  No EDID on bus 3
  No EDID on bus 5
  No EDID on bus 6
  No EDID on bus 7
  No EDID on bus 9
  No EDID on bus 10
  3 potential busses found: 0 4 8
  Will scan through until the first EDID is found.
  Pass a bus number as an option to this program to go only for that one.
  Bus 0 doesn't really have an EDID...
  256-byte EDID successfully retrieved from i2c bus 4
  Looks like i2c was successful. Have a good day.
  Checksum Correct

  Section "Monitor"
Identifier "ROG PG278QR"
ModelName "ROG PG278QR"
VendorName "AUS"
# Monitor Manufactured week 47 of 2016
# EDID version 1.3
# Digital Display
DisplaySize 600 340
Gamma 2.20
Option "DPMS" "false"
Horizsync 30-140
VertRefresh 24-60
# Maximum pixel clock is 300MHz

#Extension block found. Parsing...
Modeline"Mode 1" 148.500 1920 2008 2052 2200 1080 1084 1089 
1125 +hsync +vsync
Modeline"Mode 0" 241.50 2560 2608 2640 2720 1440 1443 1448 1481 
+hsync -vsync

[Kernel-packages] [Bug 1856608] Re: [Regression] usb usb2-port2: Cannot enable. Maybe the USB cable is bad?

2020-11-04 Thread Motiejus

I have an identical error message on Debian Bullseye after kernel
upgrade:

- 5.8.0-3-amd64: works well "enough"
- 5.9.0-1-amd64: experiencing similar symptoms when Dell S2719DC monitor is 
connected.

By "similar symptoms", I mean:
- everything that is plugged to USB in the monitor works well.
- everything I've tried to plug into USB slot of the computer is sluggish to 
respond: looks like it's not receiving attention.
- the error message is the same: "usb usb2-port2: Cannot enable. Maybe the USB 
cable is bad?"

I will try to bisect the kernel at some point. However, the kernel
versions seem to be quite different, so this seems like a similar, but
different issue.

-- 
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/1856608

Title:
  [Regression] usb usb2-port2: Cannot enable. Maybe the USB cable is
  bad?

Status in linux package in Ubuntu:
  Incomplete
Status in linux source package in Bionic:
  Fix Released
Status in linux source package in Disco:
  Fix Released
Status in linux source package in Eoan:
  Fix Released
Status in linux source package in Focal:
  Incomplete

Bug description:
  This appears to be a regression between 4.15.0-70.79 and 4.15.0-72.81.
  This bug was fixed by simply reverting the offending change. Bug 1859873 
tracks root causing the issue and reapplying the change w/ any necessary fixes.

  [Impact]
  USB port unusable and boot time takes ~5 minutes longer to complete.

  Kernel emits messages like:
  usb usb2-port2: Cannot enable. Maybe the USB cable is bad?

  [Test Case]
  dmesg | grep "Cannot enable"

  [Fix]
  [Regression Risk]

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1856608/+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 1901215] Re: Cannot boot with thunderbolt dock connected before kernel loads [groovy] [focal with groovy hwe kernel]

2020-11-04 Thread Johnny Bratholt

Yesterday i updated my system, i noticed there was updates for plymouth and
kernelupdate
After that i am back to the beginning again.
The workaroung Setting nospash in /etc/default/grub
(GRUB_CMDLINE_LINUX_DEFAULT) does not work for me anymore.
I now have to open the screen on the notebook to type in my password for LUKS

--
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/1901215

Title:
Cannot boot with thunderbolt dock connected before kernel loads
[groovy] [focal with groovy hwe kernel]

Status in linux package in Ubuntu:
Confirmed

Bug description:
Dell XPS 9650 with a TB16 thunderbolt dock. 2 external displays
through the dock (HDMI and VGA). My system uses graphical boot via
plymouth. Dell logo remains on screen while ubuntu loads into gdm3
(when it is booting normally). I'm using LUKS.

This is a regression from focal and kernel 5.4.

If I boot the laptop with the thunderbolt dock connected, the system
will get past the Dell logo, go to a black screen and remain there.
The screen is powered up as I can see some light on the edges. It
won't boot up or respond to any keys.

After force-shutdown via power key long press, on the next boot the
grub menu will appear. The system will boot normally then (with the
dock still connected).

If I boot the system with the dock disconnected, it will correctly go
into disk encryption password prompt. If at that point I connect the
dock and wait without entering the password, the system will correctly
set up the dock: the displays lit up and the mouse and keyboard
plugged into it become active. The system boots normally.

I'm trying to bisect in which kernel version this happened. I'll put
results in a comment.

ProblemType: Bug
DistroRelease: Ubuntu 20.10
Package: linux-image-generic 5.8.0.25.30
ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14
Uname: Linux 5.8.0-25-generic x86_64
ApportVersion: 2.20.11-0ubuntu50
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: luis 3332 F pulseaudio
/dev/snd/controlC0: luis 3332 F pulseaudio
CasperMD5CheckResult: skip
Date: Fri Oct 23 16:27:30 2020
InstallationDate: Installed on 2019-08-17 (432 days ago)
InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
MachineType: Dell Inc. XPS 15 9560
ProcEnviron:
LANGUAGE=en_GB:en
TERM=xterm-256color
PATH=(custom, no user)
LANG=en_GB.UTF-8
SHELL=/bin/bash
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.8.0-25-generic
root=/dev/mapper/vglinux-root ro quiet splash
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.8.0-25-generic N/A
linux-backports-modules-5.8.0-25-generic N/A
linux-firmware1.190
SourcePackage: linux
UpgradeStatus: Upgraded to groovy on 2020-10-09 (13 days ago)
dmi.bios.date: 11/17/2019
dmi.bios.release: 1.18
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.18.0
dmi.board.name: 05FFDN
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.modalias:
dmi:bvnDellInc.:bvr1.18.0:bd11/17/2019:br1.18:svnDellInc.:pnXPS159560:pvr:rvnDellInc.:rn05FFDN:rvrA00:cvnDellInc.:ct10:cvr:
dmi.product.family: XPS
dmi.product.name: XPS 15 9560
dmi.product.sku: 07BE
dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1901215/+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

1 2 >

1 - 100 of 140 matches

Mail list logo