The Latest Kernel Release.

kjhambrick · 07-22-2017, 08:49 AM

All --

The following table duplicates the ChangeLog links that cwizardone posted yesterday ( 2017-07-21 ) for 4.12.3, 4.11.12, 4.9.39 and 4.4.78.

When I ran my kernel.org screen-scraper script, it uncovered a couple CVE references in the ChangeLogs for 4.12.3, 4.11.12, 4.9.39 and 4.4.78 so I thought the CVE links might be handy to have.

Anyhow, this is the output of the screen-scraper-script `get-latest-kernel-list-for-LQ.sh -s 2017-07-21`, including the dupes ( 3.18.62 is a 'new one' ):

Code:

stable:    4.12.3        Source ChangeLog [CVE] 2017-07-21
stable:    4.11.12 [EOL] Source ChangeLog [CVE] 2017-07-21
longterm:  4.9.39        Source ChangeLog [CVE] 2017-07-21 ( Slackware-current )
longterm:  4.4.78        Source ChangeLog [CVE] 2017-07-21 ( Slackware-14.2 )
longterm:  3.18.62 [EOL] Source ChangeLog       2017-07-21

CVE References:

ChangeLog-4.12.3 references CVE-2016-6213, CVE-2017-1000370.

ChangeLog-4.11.12 references CVE-2016-6213, CVE-2017-1000370.

ChangeLog-4.9.39 references CVE-2016-6213, CVE-2017-1000370.

ChangeLog-4.4.78 references CVE-2016-6213, CVE-2017-1000370.

Check for the Latest Updates at www.kernel.org.

Have Fun All'Y'All !

-- kjh

bassmadrigal · 07-22-2017, 11:20 AM

Quote:

Originally Posted by kjhambrick

Anyhow, this is the output of the screen-scraper-script `get-latest-kernel-list-for-LQ.sh -s 2017-07-21`, including the dupes ( 3.18.62 is a 'new one' ):

Did you ever post the link to this script (and I just missed it or forgot)? If not, is it something you'd consider? It's some great info it provides!

kjhambrick · 07-23-2017, 06:08 AM

Quote:

Originally Posted by bassmadrigal

Did you ever post the link to this script (and I just missed it or forgot)? If not, is it something you'd consider? It's some great info it provides!

bassmadrigal --

Try again ... I accidentially closed PaleMoon instead of a Single Tab while testing my Attachment Links !

No, I've never shared get-latest-kernel-list-for-LQ.sh because it is so ugly and fragile

The Script REQUIRES internet access ( specifically kernel.org and it also downloads the ChangeLog for each Kernel passing the Date Selection Criteria.

Otherwise, the script will hang because there are no TimeOut Settings for the curl commands in the script !

And I've never populated the Usage( ) function other than to copy in the getopts block ( no help ).

Having said that, save the following attachments in your PATH:

get-latest-kernel-list-for-LQ.sh.txt
get-latest-kernel-list-for-LQ-template.txt

Then ...

Code:

mv /path/to/get-latest-kernel-list-for-LQ.sh.txt /path/to/get-latest-kernel-list-for-LQ.sh
chmod 755 /path/to/get-latest-kernel-list-for-LQ.sh

The second attachment ( /path/to/get-latest-kernel-list-for-LQ-template.txt ) is OK as is -- it is the default template for the output and by default it should be in the same directory as the script.

The get-latest-kernel-list-for-LQ.sh.txt only understands the <<AngleVarbs>> you see in the Template and the way they look is pretty much hard-coded in the script.

The Script should return 0 if there are Kernels matching the Date Selection Criteria or 1 if no Kernels were found.

Try it out !

Have fun !

-- kjh

kjhambrick · 07-23-2017, 07:44 AM

Now I have done it ... get-latest-kernel-list-for-LQ.sh is 'out in the world' and I found and fixed a CVE parser Bug.

The attached Patch fixes a bug where multiple CVEs on a single ChangeLog Line were being mishandled ( only the first CVE was detected ).

get-latest-kernel-list-for-LQ.sh-patch.txt

Note that after the fix, there is also now a Reference to CVE-2017-1000371 in the ChangeLog Summaries for each Reference to CVE-2017-CVE-2017-1000370 !

And the reason for posting the CVE Reference List again is that CVE-2017-1000371 seems to address a 32-bit Stack bug ...

I wonder if 4.4.78 will fix Java ( and LibreOffice ) for Slackware 14.2 32-bit systems running 4.4.75 ?

Problem with the 4.4.75 kernel security upgrade dated 26 June 2017 (SSE 2017-177-01)

CVE References:

ChangeLog-4.12.3 references CVE-2016-6213, CVE-2017-1000370 and CVE-2017-1000371.

ChangeLog-4.11.12 references CVE-2016-6213, CVE-2017-1000370 and CVE-2017-1000371.

ChangeLog-4.9.39 references CVE-2016-6213, CVE-2017-1000370 and CVE-2017-1000371.

ChangeLog-4.4.78 references CVE-2016-6213, CVE-2017-1000370 and CVE-2017-1000371.

-- kjh

kjhambrick · 07-24-2017, 06:52 PM

All --

Kernel 4.13-rc2 is now available.

Handy Links:

Code:

mainline:  4.13-rc2 Source git tree  2017-07-23

No CVE References were found for 4.13-rc2

Check for the Latest Updates at www.kernel.org.

Have Fun All'Y'All !

-- kjh

PROBLEMCHYLD · 07-24-2017, 08:48 PM

Quote:

Originally Posted by 55020

For anybody using 'dusk', I'm not going to be building any more 4.9 series kernels because Slackware's official kernels in -current are available and regularly updated. So from now on it's 4.4 and 4.12

I'm running your latest Kernel Update and this is my log. Everything seems to work but.....

Code:

Message from syslogd@problemchyld at Mon Jul 24 20:42:39 2017 ...
problemchyld kernel: [  126.022948] Hardware name: Hewlett-Packard Presario C700 Notebook PC/30D9, BIOS F.35 03/29/2010

Message from syslogd@problemchyld at Mon Jul 24 20:42:39 2017 ...
problemchyld kernel: [  126.023009] Call Trace:

Message from syslogd@problemchyld at Mon Jul 24 20:42:39 2017 ...
problemchyld kernel: [  126.023025]  ? wake_bit_function+0x70/0x70

Message from syslogd@problemchyld at Mon Jul 24 20:42:39 2017 ...
problemchyld kernel: [  126.023112]  intel_get_load_detect_pipe+0x593/0x620 [i915]

Message from syslogd@problemchyld at Mon Jul 24 20:42:39 2017 ...
problemchyld kernel: [  126.023276]  ? intel_tv_get_modes+0x240/0x240 [i915]

Message from syslogd@problemchyld at Mon Jul 24 20:42:39 2017 ...
problemchyld kernel: [  126.023299]  drm_helper_probe_detect+0x42/0x80 [drm_kms_helper]

Message from syslogd@problemchyld at Mon Jul 24 20:42:39 2017 ...
problemchyld kernel: [  126.023319]  drm_helper_probe_single_connector_modes+0xb4/0x560 [drm_kms_helper]

Message from syslogd@problemchyld at Mon Jul 24 20:42:39 2017 ...
problemchyld kernel: [  126.023437]  drm_mode_getconnector+0x114/0x2c0 [drm]

Message from syslogd@problemchyld at Mon Jul 24 20:42:39 2017 ...
problemchyld kernel: [  126.023397]  ? intel_atomic_commit_tail+0xe00/0xe00 [i915]

Message from syslogd@problemchyld at Mon Jul 24 20:42:39 2017 ...
problemchyld kernel: [  126.023508]  drm_ioctl+0x1df/0x420 [drm]

Message from syslogd@problemchyld at Mon Jul 24 20:42:39 2017 ...
problemchyld kernel: [  126.023546]  ? drm_mode_connector_property_set_ioctl+0x40/0x40 [drm]

Message from syslogd@problemchyld at Mon Jul 24 20:42:39 2017 ...
problemchyld kernel: [  126.023622]  do_vfs_ioctl+0x81/0x620

Message from syslogd@problemchyld at Mon Jul 24 20:42:39 2017 ...
problemchyld kernel: [  126.023194]  intel_tv_detect+0x113/0x510 [i915]

Message from syslogd@problemchyld at Mon Jul 24 20:42:39 2017 ...
problemchyld kernel: [  126.023720] Code: ff ff 66 90 0f ff 31 c0 e9 16 ff ff ff 8b 45 d4 8d 55 e0 e8 ec 74 59 c8 85 ff 0f 85 08 ff ff ff 56 68 78 75 b2 f8 e8 66 3d 63 c8 <0f> ff 58 5a e9 f4 fe ff ff 66 66 66 66 90 55 8b 50 50 8b 00 89

Message from syslogd@problemchyld at Mon Jul 24 20:42:39 2017 ...
problemchyld kernel: [  126.022954] task: f50aa200 task.stack: f23f0000

Message from syslogd@problemchyld at Mon Jul 24 20:42:39 2017 ...
problemchyld kernel: [  126.023630]  SyS_ioctl+0x58/0x70

Message from syslogd@problemchyld at Mon Jul 24 20:42:39 2017 ...
problemchyld kernel: [  126.023476]  ? drm_mode_connector_property_set_ioctl+0x40/0x40 [drm]

Message from syslogd@problemchyld at Mon Jul 24 20:42:39 2017 ...
problemchyld kernel: [  126.023643]  do_int80_syscall_32+0x3d/0xa0

Message from syslogd@problemchyld at Mon Jul 24 20:42:39 2017 ...
problemchyld kernel: [  126.023580]  ? drm_version+0x80/0x80 [drm]

Message from syslogd@problemchyld at Mon Jul 24 20:42:39 2017 ...
problemchyld kernel: [  126.023663]  entry_INT80_32+0x31/0x31

Message from syslogd@problemchyld at Mon Jul 24 20:42:39 2017 ...
problemchyld kernel: [  126.022940] CPU: 1 PID: 1293 Comm: Xorg Tainted: G        W       4.12.3-smp #1

55020 · 07-25-2017, 07:42 AM

There are no errors or warnings in that syslogd output. There should be a warning immediately before that (the tainted 'W' flag shows that). It would be much easier to read the output of 'dmesg'.

I have just checked the same kernel on a system that has i915 graphics, and I don't get any errors or warnings. Most likely, the i915 driver isn't happy about your hardware.

PROBLEMCHYLD · 07-25-2017, 01:47 PM

Quote:

Originally Posted by 55020

There are no errors or warnings in that syslogd output. There should be a warning immediately before that (the tainted 'W' flag shows that). It would be much easier to read the output of 'dmesg'.

I have just checked the same kernel on a system that has i915 graphics, and I don't get any errors or warnings. Most likely, the i915 driver isn't happy about your hardware.

I ran dmesg and this is the results. I'm going to assume I can ignore the errors/warnings since the Kernel load and works fine. Thanks

55020 · 07-25-2017, 03:11 PM

Code:

[   21.473566] [drm:drm_atomic_helper_commit_cleanup_done [drm_kms_helper]] *ERROR* [CRTC:30:pipe A] flip_done timed out
[   21.574567] vblank wait timed out on crtc 0

This is the significant part. If you google the term I underlined, you will see many, many bug reports about your graphics hardware ("Intel 965GM Chipset"). You're lucky -- most of the people reporting this (with 4.8 and 4.9 kernels) have a blank screen or crashing. Some things people out there have suggested include updating your bios and microcode, and using this as a boot parameter: "video=SVIDEO-1:d". If it was my system, I would just go back to the 4.4 kernel.

PROBLEMCHYLD · 07-25-2017, 05:02 PM

Quote:

Originally Posted by 55020

Code:

[   21.473566] [drm:drm_atomic_helper_commit_cleanup_done [drm_kms_helper]] *ERROR* [CRTC:30:pipe A] flip_done timed out
[   21.574567] vblank wait timed out on crtc 0

If it was my system, I would just go back to the 4.4 kernel.

Code:

  append="vt.default_utf8=1"
  boot=/dev/sda
  compact
  bitmap=/boot/slack.bmp
  bmp-colors=255,0,255,0,255,0
  bmp-table=60,6,1,16
  bmp-timer=65,27,0,255
  prompt
  change-rules
  reset
  vga=773
image=/dmt/live/vmlinuz
  root=/dev/sda1
  label=0.28.1
  append="boot=live config union=overlay noswap noprompt ip=frommedia live-media-path=/dmt/live bootfrom=/dev/sda1 toram=filesystem.squashfs" 
  vga=788
  initrd=/dmt/live/initrd.img
image=/boot/vmlinuz-generic-smp-4.12.3-smp
  initrd=/boot/initrd_4.12.3-smp.gz
  root=/dev/sda1
  label=4.12.3
  append="resume=/dev/sda2 video=SVIDEO-1:d"
  read-only

Don't need to, followed your suggestion and the warnings and errors went away. I even noticed a faster boot. Thank you very much. BTW: I did install the intel microcode update and then removed it once I seen it work editing the lilo.conf.

bormant · 07-26-2017, 12:33 AM

@PROBLEMCHYLD,
Please note, append is a global directive, man lilo.conf says that addappend is used for local additions. But because "vt.default_utf8=1" is by default for modern kernels there are no side effects.

cwizardone · 07-27-2017, 05:41 PM

Kernel updates 4.4.79, 4.9.40, and 4.12.4, are now available at, https://www.kernel.org/.

The change logs,

https://cdn.kernel.org/pub/linux/ker...angeLog-4.4.79

https://cdn.kernel.org/pub/linux/ker...angeLog-4.9.40

https://cdn.kernel.org/pub/linux/ker...angeLog-4.12.4

Drakeo · 07-27-2017, 11:23 PM

I noticed this since 14.2 we have had more kernel updates. And I like to build my initrd.gz and my NVidia blob. before I reboot.
Since I am running a couple currents like Eric's KDE5 and Pat's latest. Plus keep my old friends up dated I wrote a crude script that gets the job done.
If your building and installing and creating the Slackware way with Pat's scripts I am sure you may find this a useful it works for me.

https://github.com/Drakeo/update-nvidia-mkinitrd
I am waiting for 4.14 to com out it will be a mature AMD graphics driver by then for testing.

kjhambrick · 07-28-2017, 06:07 AM

Quote:

Originally Posted by Drakeo

I noticed this since 14.2 we have had more kernel updates. And I like to build my initrd.gz and my NVidia blob. before I reboot.
Since I am running a couple currents like Eric's KDE5 and Pat's latest. Plus keep my old friends up dated I wrote a crude script that gets the job done.
If your building and installing and creating the Slackware way with Pat's scripts I am sure you may find this a useful it works for me.

https://github.com/Drakeo/update-nvidia-mkinitrd
<<snip>>

Drakeo --

Thanks for sharing !

Yes, there certainly is a lot of churn these days with the current Kernel Dev Model

But, I can't connect to the link ? ( 404 error ).

Thanks again.

-- kjh

USUARIONUEVO · 07-28-2017, 01:41 PM

Anyone runs 4.13-rcX ??

I try 2 times to compile but i got video problems with 4.13 and turn back to 4.12.X

I test custom and config from 4.12+makeolddefconfig --> two times video problems.