Source: linux
Severity: normal
Dear Maintainer,
I can't see why something which can be done with a kernel boot parameter or a
sysctl variable
needs to be forced in the source since 2011. Also, the very existence of this
new default is non-transparent for anyone relying on official kernel
document
Package: linux-source-6.4
Version: 6.4.4-3~bpo12+1
Severity: normal
Dear Maintainer,
a certain patch leads to a significant regression making AVX instructions
unusable in the CPUs having them:
https://lore.kernel.org/lkml/202307192135.203ac24e-oliver.s...@intel.com/
a fix is available upstream:
Package: linux-source-5.9
Version: 5.9.15-1~bpo10+1
Severity: important
Tags: upstream
Dear Maintainer,
5.9.15 crashes regularly with memory/paging related messages, like this:
=
Jan 15 17:25:09 host kernel: [125426.427889] BUG: unable to handle page fault
for address: 2500
Jan
Package: src:linux
Version: 4.6.4-1
Severity: normal
--- Please enter the report below this line. ---
So I have an Intel Z87 based motherboard with i7-4770 CPU installed
and VT-d switched on and I'm tinkering with iommu, virtualisation and stuff,
putting intel_iommu=on as a boot parameter.
I als
Package: linux-image-amd64
--- Please enter the report below this line. ---
Actually, after some research and having run dozens of old kernel versions I
came to the conclusion that this LVM/RAID1 shit NEVER WORKED PROPERLY.
It's just unbelievable. This RAID1 feature was added to LVM2 in 2011. d
But then again, I guess md should get metadata from some backend provided by
lvm, not from the device directly? (Don't know for sure, didn't dive deep into
the driver yet.)
Package: linux-image-amd64
Version: 4.2+68
--- Please enter the report below this line. ---
This seems to be a duplicate of #795772, which I've filed on src:linux months
ago. (I wonder why so little info on this bug available, like nobody else uses
LVM's RAID1 feature?)
--- System information.
Package: src:linux
Version: 4.1.3-1
Severity: important
--- Please enter the report below this line. ---
Kernel bug #100491 (https://bugzilla.kernel.org/show_bug.cgi?id=100491)
presents in this version, making the system with mirrored lvm volume
unbootable. Moreover, the patch posted in bugzill
Version 2.6.38-1 seems to have the same issue. Slightly modifed patch follows:
diff -U 3 -H -B -d -p -r -N -- a/drivers/media/video/saa7134/saa7134-input.c b/drivers/media/video/saa7134/saa7134-input.c
--- a/drivers/media/video/saa7134/saa7134-input.c 2011-03-15 06:20:32.0 +0500
+++ b/drive
Package: linux-2.6
Version: 2.6.37-2
Severity: normal
Tags: patch
--- Please enter the report below this line. ---
Hello.
Pinnacle PCTV 110i TV-tuner board has IR remote control, which was recognized
by kernel as input device before this (http://goo.gl/U3Fal) upstream patch.
Since then, ir-kbd-i
I'm getting the same error when trying to boot with
xen-hypervisor-3.4-amd64 3.4.2-2 from squeeze
linux-image-2.6.26-2-xen-amd64 2.6.26-19lenny2 from lenny
System:
Motherboard:Asus M2V-VM
Processor: AMD Athlon(tm) 64 X2 Dual Core Processor 3800+
Memory: 6GB DDR2-667
I am able
11 matches
Mail list logo
