Package: linux-image-5.19.0-rc6-amd64
Version: 5.19~rc6-1~exp1
Severity: important
X-Debbugs-Cc: george.shuk...@gmail.com
Dear Maintainer,
After upgrade from 5.18.0-3-amd64 to 5.19.0-rc6-amd64 video subsystem start
misbehave:
* Visual artefacts after cursor
* Hangs when X is active
* Unable to s
Hello.
Why kbuild package has been missing for almost all kernel versions of
experimental, and has been appearing only after next version is released
and packages (image, headers) for previous one had withdrawn?
Thanks.
--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with
Now 3.18 headers are lonely.
Please build linux-kbuild-3.18.
--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/54b2a79e.4090...@gmail.com
Package: src:linux
Version: 3.10.11-1
Severity: normal
During new HBA test found nasty bug:
Caused my following command line:
mdadm --create /dev/md10 --level=10 --raid-devices=4 --chunk=4K /dev/sd*2
--assume-clean
mdadm: /dev/sda2 appears to be part of a raid array:
level=raid1 devices=2 c
I think this commit is somehow related to that problem:
commit 14216561e164671ce147458653b1fea06a4ada1e
Author: James Bottomley
Date: Wed Jul 25 23:55:55 2012 +0400
[SCSI] Fix 'Device not ready' issue on mpt2sas
This is a particularly nasty SCSI ATA Translation Layer (SATL) problem.
hink it's kinda simple to say where
problem is:
linux-3.0 do have mpt2sas 08.100.00.02 and linux-3.2 do have 10.100.00.00
And note, that mpt2sas do have strange behavior in linux-2.6.32 (version
02.100.03.00) under highload.
On 03.09.2012 06:30, Jonathan Nieder wrote:
George Shuklin wrot
We've tested it with vanilla 3.2.12, problem was same.
On 03.09.2012 06:01, Jonathan Nieder wrote:
Hi George,
George Shuklin wrote:
Tags: upstream
Which upstream version did you test?
[...]
That bug found in 3.2 and 3.3 versions of kernel, but not
reproducing in 3.0.
[...]
1) S
В Вск, 10/06/2012 в 04:32 -0500, Jonathan Nieder пишет:
> George Shuklin wrote:
>
> > Package: linux-2.6
> > Version: 3.0.0-6
>
> Is this the same machine as bug#676704? (If so, I prefer to track all
> symptoms in one place.)
>
> Do the "VM: trapped re
Package: linux-2.6
Version: 3.0.0-6
Severity: normal
Periodically X-server stops to work:
1) No screen updated
2) No switching to text console
(Mouse cursor is moving)
dmesg shows:
[111463.425953] [drm] nouveau :01:00.0: VM: trapped read at 0x00 on
ch 4 [0xa9ac] PGRAPH/VFETCH/
Package: linux-2.6
Version: 3.2.19-1
Severity: normal
After switching from nvidia to noveau linux sometime panic. I've made some
screenshots of that crash, here (handwritten) begin of crash:
general protection fault: [#1] SMP
CPU 0
...
Call Trace:
nv50_display_isr+0x1ae/0x2b4 [nouveau]
arc
On 30.05.2012 17:31, Ben Hutchings wrote:
A log of the crash would be useful.
oops, sorry, forgot to attach.
Here:
[ ok ] Deactivating swap...done.
[info] Will now restart.
[ 280.608079] WARNING: g.e. still in use!
[ 280.608088] WARNING: g.e. still in use!
[ 280.608104] sysfs: kobject eth0
Package: linux-2.6
Version: 3.2.18-1
Severity: minor
linux 3.22 Ñcrashing during reboot when ran under xcp-xapi toolstack. VM
configuration is default, installation is default (netinst) too.
-- Package-specific info:
** Version:
Linux version 3.2.0-2-686-pae (Debian 3.2.18-1)
(debian-kernel@lis
On 10.05.2012 07:03, NeilBrown wrote:
Fixed by commit fae8cc5ed0714953b1ad7cf86 I believe.
http://git.kernel.org/?p=linux/kernel/git/torvalds/linux.git;a=commitdiff;h=fae8cc5ed
From: NeilBrown
Date: Tue, 14 Feb 2012 00:10:10 + (+1100)
Subject: md/raid10: fix handling of error on la
Package: linux-2.6
Version: 3.0.0-1
Severity: normal
After some disk avtivity on SATA disk plugged via USB-SATA:
usb 1-6: USB disconnect, device number 3
Main strangeness is that after that disconnections no any new usb devices are
detected and traces bellow appear for some (random?) processes.
I found one more very interesting feature of this bug:
When memory overcommitment is disabled, system shall not be in state
when OOM killer is called. (Only 'EOM' for greedy application).
But with this kernel OOM is still appear, even no overcommitment
happens.
Steps to reproduce:
mem=1GiB
max
I check situation in same environment with 2.6.18-194.el5xen on CentOS.
I found following:
1) 'unusable' memory exist
2) When oom state occur, no 'rampaging' oom_killer appear, only bloated
application die. This behavior differ from describing above: In Debian
oom_killer in same situation starts
'MemFree:545128 kB\n'
... If we descend to lower values, (about 1-2 MiB), with MemFree about
400-500MiB we will get to OOM killer, rampaging around and killing
randomly anyone (sshd, init, etc).
В Птн, 10/09/2010 в 08:13 +0100, Ian Campbell пишет:
> On Wed, 2010-09-08 at 15:52 +
В Пнд, 06/09/2010 в 07:59 +0100, Ian Campbell пишет:
> On Mon, 2010-09-06 at 04:03 +0400, George Shuklin wrote:
> >
> > I belive, this somehow related to difference in drivers/xen/balloon.c,
> > gentoo/SUSE version have some lines like
> >
> > totalra
Package: linux-image-2.6.26-2-xen-686
Severity: important
I belive current version of xen (as domU) kernel for debian report free memory
wrong: system reports lots of free memory, but acutally all memory is used up.
Condition to reproduce:
Xen evnironment, maxmem is very large (10-20GiB memory
19 matches
Mail list logo
