Linux 4.14.14 kernel bug on line 152 fs/reiser4/block_alloc.c

2018-01-26 Thread Metztli Information Technology
Niltze, Ed- I had been using Linux kernel 4.14.14 built 'the Debian way' for a couple of days --doing some light VirtualBox development and successful virtual machine test/creation. Notwithstanding, today 01-25-2018 experienced black screen kernel bug trace during browser usage. I wrote down

Re: Linux 4.14.14 kernel bug on line 152 fs/reiser4/block_alloc.c

2018-01-26 Thread Edward Shishkin
On 01/26/2018 09:15 AM, Metztli Information Technology wrote: Niltze, Ed- Hello. I had been using Linux kernel 4.14.14 built 'the Debian way' for a couple of days --doing some light VirtualBox development and successful virtual machine test/creation. Notwithstanding, today 01-25-2018

Processed: reassign 888509 to src:linux

2018-01-26 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > reassign 888509 src:linux 4.9.65-3+deb9u2 Bug #888509 [linux-image-4.9.0-5-amd64] BUG: soft lockup - CPU# stuck Bug reassigned from package 'linux-image-4.9.0-5-amd64' to 'src:linux'. No longer marked as found in versions linux/4.9.65-3+deb9u2.

Bug#875621: X1 Carbon trackpoint / Debian Bug#875621

2018-01-26 Thread Chris Boot
On 19/01/18 13:20, Tony Power wrote: > Hi Chris, > > Didn't the suggestion in reply to your question helo? > https://www.spinics.net/lists/linux-input/msg53757.html I didn't try it. I didn't feel like I was missing out by giving up and just disabling it. As a user, I shouldn't have to care and

Re: armel/marvell kernel size

2018-01-26 Thread Ben Hutchings
Another possibility is to use LTO (Link-Time Optimisation): https://lwn.net/SubscriberLink/744507/6489bc782122ca29/ However this is not yet supported in mainline, and it might require more VM than is available on an armel buildd. Ben. -- Ben Hutchings Unix is many things to many people, but

Bug#878614: linux-image-4.13.0-1-amd64: unexpected IRQ trap at vector e8 on Intel NUC H26998-401

2018-01-26 Thread Daniel Kahn Gillmor
On Sat 2017-10-14 22:17:29 -0400, Daniel Kahn Gillmor wrote: > Trying to boot this machine into 4.13.0-1-amd64 results in several kernel > messages like: > > unexpected IRQ trap at vector e8 > > per second, and basic system services take ages to start (including > journald, which means i

Bug#878614: marked as done (linux-image-4.13.0-1-amd64: unexpected IRQ trap at vector e8 on Intel NUC H26998-401)

2018-01-26 Thread Debian Bug Tracking System
Your message dated Fri, 26 Jan 2018 15:50:25 -0500 with message-id <87wp04cpke@fifthhorseman.net> and subject line Re: Bug#878614: linux-image-4.13.0-1-amd64: unexpected IRQ trap at vector e8 on Intel NUC H26998-401 has caused the Debian Bug report #878614, regarding

Bug#888537: linux-image-4.14.0-3-arm64: BUG: Bad page state in process cc1 pfn:75cbd

2018-01-26 Thread Heinrich Schuchardt
Package: src:linux Version: 4.14.13-1 Severity: normal Dear Maintainer, I am running an Odroid C2 on iSCSI. Under heavy load I see bad page errors like the ones below. This is not gcc specific. Same happens when git is handling large repositories. The reserved memory matches my firmware.

Bug#878221: linux-image-4.9.0-4-amd64: Screen flickers randomly with Radeon R9 270X since upgrade from 4.9.0-3 to 4.9.0-4

2018-01-26 Thread besy
I realized that the kernel I suggested as workaround (linux-image-4.9.0-3-amd64) didn't completely solve the flickering problem. However, it made the flickering occur very rarely. I can confirm that the kernel "4.14.0-3-amd64 #1 SMP Debian 4.14.13-1 (2018-01-14)" from stretch-backports causes no