On Mon, 2019-03-25 at 17:20 +, Ben Hutchings wrote:
> On Tue, 2019-03-05 at 22:00 +, Ben Hutchings wrote:
> > On Fri, 2019-03-01 at 14:05 +0100, Emilio Pozuelo Monfort wrote:
> [...]
> > > (It
> > > may be unlikely for old suites to have users with new hardware, however
> > > it's
> > >
Hi Ben
I can confirm that we do not encounter the troubles anymore with your
patch. The patched servers are running smooth and stable again.
Thanks for the fast fix!
Kind regards
Emanuel
On 30/03/2019 05:15, Ben Hutchings wrote:
> I've uploaded a new version of linux to:
>
Package: src:linux
Version: 4.19.28-2
Severity: normal
On my Toshiba X40 the kernel logs approximately 80,000 messages per hour
about i8042 interrupts. See the kernel log below...
-- Package-specific info:
** Version:
Linux version 4.19.0-4-amd64 (debian-kernel@lists.debian.org) (gcc version
Control: found -1 linux/4.19.28-2
Control: tags -1 + patch
The upstream maintainer has provided a workaround[1] for this which has
apparently been queued[2] for stable, so I imagine that the fix will be
merged in due course.
Mike.
[1]
Processing control commands:
> found -1 linux/4.19.28-2
Bug #925496 [src:linux] linux-image-4.19.0-2-amd64: Latency increase with r8169
and default coalescing settings
Marked as found in versions linux/4.19.28-2.
> tags -1 + patch
Bug #925496 [src:linux] linux-image-4.19.0-2-amd64: Latency
Your message dated Mon, 1 Apr 2019 11:02:40 +0100
with message-id <20190401100240.pe52v7wbc45ct...@traxus.robots.org.uk>
and subject line Re: linux-image-4.19.0-4-amd64: Many log messages about i8042
interrupt
has caused the Debian Bug report #926157,
regarding linux-image-4.19.0-4-amd64: Many
short update: the system is still up and running.
Cheers,
Werner
Am 30.03.19 um 19:01 schrieb Werner Detter:
> Hi Ben,
>
> thanks for the updated version. I've installed the new version on one
> affected machine which crashed after some hours with the old kernel.
> It's currently running with
I can absolutely confirm this fishy behaviour on 2 VMWare guests. (VMware ESXi,
6.5.0, 8294253, vSphere Client version 6.7.0)
Also ssh copy was not possible to a host running linux-image-3.16.0-8-amd64
No problems with linux-image-3.16.0-7-amd64.
Very fishy.
Package: linux-image-4.19.0-0.bpo.2-amd64
Version: 4.19.16-1~bpo9+1
When testing 4.19 from backports, we ran into an issue which manifests
under heavy I/O load. The driver gets stuck in endless resetting loop,
affecting I/O performance badly.
Affected server uses Supermicro H11DSi-NT
Package: src:linux
Version: 4.19.28-2
Severity: normal
Tags: upstream
Dear Maintainer,
after todays upgrade to linux-image-4.19.0-4 my system was unable to
start the xserver (on Intel Graphic HD 405) any more though it was and
is able with linux-image-4.19.0-2.
After hours of googleing and
Your message dated Mon, 01 Apr 2019 23:53:01 +0100
with message-id <6eefa25522113e991313dc887231b3f113bf6559.ca...@decadent.org.uk>
and subject line Re: linux-image-amd64: linux-image-3.16.0-8-amd64 -
unpredictable reboots / kernel panics?
has caused the Debian Bug report #925919,
regarding
Your message dated Mon, 01 Apr 2019 23:53:01 +0100
with message-id <6eefa25522113e991313dc887231b3f113bf6559.ca...@decadent.org.uk>
and subject line Re: linux-image-amd64: linux-image-3.16.0-8-amd64 -
unpredictable reboots / kernel panics?
has caused the Debian Bug report #925919,
regarding
Processing commands for cont...@bugs.debian.org:
> reassign 926202 src:linux 4.19.16-1
Bug #926202 [linux-image-4.19.0-0.bpo.2-amd64] mpt3sas driver stuck in endless
resetting loop under load
Bug reassigned from package 'linux-image-4.19.0-0.bpo.2-amd64' to 'src:linux'.
No longer marked as found
13 matches
Mail list logo
