Reporting errors in Kernels

All Gurus once were Newbies
Forum rules
There are no such things as "stupid" questions. However if you think your question is a bit stupid, then this is the right place for you to post it. Please stick to easy to-the-point questions that you feel people can answer fast. For long and complicated questions prefer the other forums within the support section.
Before you post please read how to get help
Post Reply
caseyjames
Level 1
Level 1
Posts: 1
Joined: Tue Jul 17, 2018 1:53 pm

Reporting errors in Kernels

Post by caseyjames » Tue Jul 17, 2018 2:00 pm

Installed mint 19 on a new xps15 - WIFI only works on kernel 4.15.20.

4.15.24 / 4.15.23 show "no connections" in the network connections pop up.

How should I report that issue?

User avatar
jimallyn
Level 18
Level 18
Posts: 8292
Joined: Thu Jun 05, 2014 7:34 pm
Location: Wenatchee, WA USA

Re: Reporting errors in Kernels

Post by jimallyn » Tue Jul 17, 2018 2:22 pm

There's probably no reason to report anything, nor any reason to use the -24 or -23 kernels. First, there are known issues with the -24 kernel that many users have reported here. So forget about that one completely. Second, most drivers need to be compiled for your specific kernel, so unless you have done that, you really don't know whether your wifi works with the -23 kernel or not. Here's what I (and a lot of those here who know more than me) would do: unless you have some piece of hardware that requires a different kernel, stick with the one that works.
Image

“If the government were coming for your TVs and cars, then you'd be upset. But, as it is, they're only coming for your sons.” - Daniel Berrigan

User avatar
Pjotr
Level 20
Level 20
Posts: 10659
Joined: Mon Mar 07, 2011 10:18 am
Location: The Netherlands (Holland)
Contact:

Re: Reporting errors in Kernels

Post by Pjotr » Tue Jul 17, 2018 3:03 pm

jimallyn wrote:
Tue Jul 17, 2018 2:22 pm
Here's what I (and a lot of those here who know more than me) would do: unless you have some piece of hardware that requires a different kernel, stick with the one that works.
+1

At least for now. We should get the -28 pretty soon. It's already in bionic-proposed....
Tip: 10 things to do after installing Linux Mint 19 Tara
Keep your Linux Mint healthy: Avoid these 10 fatal mistakes
Twitter: twitter.com/easylinuxtips
All in all, horse sense simply makes sense.

gm10
Level 7
Level 7
Posts: 1691
Joined: Thu Jun 21, 2018 5:11 pm

Re: Reporting errors in Kernels

Post by gm10 » Tue Jul 17, 2018 4:10 pm

caseyjames wrote:
Tue Jul 17, 2018 2:00 pm
How should I report that issue?
Kernels are provided by Ubuntu, so bug reports are to be directed there, just as for all upstream components - find the responsible package there and click on Bugs, see if it's been reported already, otherwise on the right click on report a bug.
Pjotr wrote:
Tue Jul 17, 2018 3:03 pm
At least for now. We should get the -28 pretty soon. It's already in bionic-proposed....
Should get replaced by -29 soon, has a bunch of important bug fixes:

Code: Select all

 linux (4.15.0-29.31) bionic; urgency=medium
 .
   * linux: 4.15.0-29.31 -proposed tracker (LP: #1782173)
 .
   * [SRU Bionic][Cosmic] kernel panic in ipmi_ssif at msg_done_handler
     (LP: #1777716)
     - ipmi_ssif: Fix kernel panic at msg_done_handler
 .
   * Update to ocxl driver for 18.04.1 (LP: #1775786)
     - misc: ocxl: use put_device() instead of device_unregister()
     - powerpc: Add TIDR CPU feature for POWER9
     - powerpc: Use TIDR CPU feature to control TIDR allocation
     - powerpc: use task_pid_nr() for TID allocation
     - ocxl: Rename pnv_ocxl_spa_remove_pe to clarify it's action
     - ocxl: Expose the thread_id needed for wait on POWER9
     - ocxl: Add an IOCTL so userspace knows what OCXL features are available
     - ocxl: Document new OCXL IOCTLs
     - ocxl: Fix missing unlock on error in afu_ioctl_enable_p9_wait()
 .
   * Critical upstream bugfix missing in Ubuntu 18.04 - frequent Xorg crash after
     suspend (LP: #1776887)
     - ocxl: Document the OCXL_IOCTL_GET_METADATA IOCTL
 .
   * Hard LOCKUP observed on stressing Ubuntu 18 04 (LP: #1777194)
     - powerpc: use NMI IPI for smp_send_stop
     - powerpc: Fix smp_send_stop NMI IPI handling
 .
   * IPL: ppc64_cpu --frequency hang with INFO: rcu_sched detected stalls on
     CPUs/tasks on w34 and wsbmc016 with 920.1714.20170330n (LP: #1773964)
     - rtc: opal: Fix OPAL RTC driver OPAL_BUSY loops
 .
   * [Regression] EXT4-fs error (device sda2): ext4_validate_block_bitmap:383:
     comm stress-ng: bg 4705: bad block bitmap checksum (LP: #1781709)
     - SAUCE: Revert "UBUNTU: SAUCE: ext4: fix ext4_validate_inode_bitmap: comm
       stress-ng: Corrupt inode bitmap"
     - SAUCE: ext4: check for allocation block validity with block group locked
Last edited by gm10 on Tue Jul 17, 2018 4:17 pm, edited 1 time in total.

User avatar
Pjotr
Level 20
Level 20
Posts: 10659
Joined: Mon Mar 07, 2011 10:18 am
Location: The Netherlands (Holland)
Contact:

Re: Reporting errors in Kernels

Post by Pjotr » Tue Jul 17, 2018 4:14 pm

Apparently the numbers keep going up... They really should let one of them land soon.
Tip: 10 things to do after installing Linux Mint 19 Tara
Keep your Linux Mint healthy: Avoid these 10 fatal mistakes
Twitter: twitter.com/easylinuxtips
All in all, horse sense simply makes sense.

gm10
Level 7
Level 7
Posts: 1691
Joined: Thu Jun 21, 2018 5:11 pm

Re: Reporting errors in Kernels

Post by gm10 » Tue Jul 17, 2018 4:17 pm

Pjotr wrote:
Tue Jul 17, 2018 4:14 pm
Apparently the numbers keep going up... They really should let one of them land soon.
They are in no hurry because they revoked -24 on their end, it's only Mint with the problem. From current looks it seems -29 will be the one they'll go with though. We'll see. If more critical bugs come up in the meantime they'll probably push do another build first again.

JeremyB
Level 18
Level 18
Posts: 8862
Joined: Fri Feb 21, 2014 8:17 am

Re: Reporting errors in Kernels

Post by JeremyB » Tue Jul 17, 2018 5:09 pm

Post results from terminal for

Code: Select all

lspci -nnk | grep -iA3 net; lsusb; dkms status

Post Reply

Return to “Newbie Questions”