Control: affects -1 src:mariadb
Control: tags -1 + confirmed
Control: severity -1 critical
Seeing this too. We have two standalone systems running the stock
bookworm MariaDB and the opensource network management system LibreNMS,
which is quite write-heavy. After some time (sometimes a couple of
ho
Package: src:linux
Version: 6.1.15-1
Severity: important
Hi,
I run a Lenovo T14s Gen2 with a Lenovo Dockingstation and two
DP-connected external displays, with KDE on Wayland.
Every few days, after an extended coffee break/lunch, I find my
previously locked session unusable. The displays stay in
Am 30.03.19 um 05:15 schrieb Ben Hutchings:
Hi Ben,
> I've uploaded a new version of linux to:
> https://people.debian.org/~benh/packages/jessie-security/
> which I believe will fix this regression (bug #925919). Please let me
> know whether it works for you.
Had been hit by the crash before, w
On Fri, Sep 14, 2018 at 12:37:40PM +0200, Moritz Muehlenhoff wrote:
> I've pulled a number of upstream commits for the megaraid_sas driver which add
> support for the Perc 740/840 RAID controllers to the Stretch kernel.
>
> Successfully tested with a H840 on a current Dell PowerEdge R440 and I've
Am 12.12.2017 um 02:57 schrieb Ben Hutchings:
Hi Ben,
> Apologies for this regression. Salvatore Bonaccorso has tracked down
> which change in 3.16-stable triggers the crash, and I identified some
> related upstream changes which appear to fix it. An updated package is
> available at:
>
> http
Hi Karsten,
Thanks for the test. Can you check whether numa=off on the kernel command line
fixes this as well?
Bernhard
--
Diese Nachricht wurde von meinem Android-Mobiltelefon mit K-9 Mail gesendet.
On Mon, Dec 11, 2017 at 09:23:45AM +0100, Salvatore Bonaccorso wrote:
> The issue seems not present when rolling back to 3.16.48-1 (this is
> one kernel version which was only present in jessie-proposed-update).
>
> Can someone confirm? If yes it has to be a change between 3.16.48-1
> and 3.16.51
Control: summary -1 Seems two affect machines with more than one socket.
Workaround: set maxcpus=1 on the kernel command line
Hi,
this seems to affect two-socket boxes.
Workaround is to set maxcpus=1 on the kernel command line.
Bernhard
Control: severity -1 critical
On Mon, Dec 11, 2017 at 09:14:27AM +0200, Rolandas Naujikas wrote:
Hi,
> Package: linux-image-3.16.0-4-amd64
> Version: 3.16.51-2
>
> Loading Linux 3.16.0-4-amd64 ...
> Loading initial ramdisk ...
> [0.604128] general protection fault: [#1] SMP
> [0.60
The issue affects SLES11SP4 (3.0.101-68-default) and SLES12SP1
(3.12.53-60.30-default) as well. Both have backported vmxnet3 1.4.2.0-k
in their kernel package.
It does _not_ affect the official vmxnet3 module from the VMware tools,
also calling itself version 1.4.2.0. So there seems to be a differ
Package: src:linux
Version: 3.16.7-ckt20-1+deb8u3
Severity: normal
Hi,
short history on this:
We run a pretty large VMware infrastructure. In November 2014 we migrated the
hardware the cluster runs on
Old: HP BL490c Gen6, Flex10 something, BCM57711E
New: HP BL460c Gen8, HP FlexFabric 630FLB, B
Package: src:linux
Followup-For: Bug #784579
Hi,
> If I disable the "GRUB_GFXPAYLOAD_LINUX" parameter then GRUB does not
> tell Linux anything. I assume that GRUB (or is it the Linux kernel?)
> switches back to 80x25 text mode and the whole boot process completes
> without problems. No black scre
Control: reassign -1 src:linux
Control: found -1 3.16.7-ckt9-2
Hi,
I have tested this on a current kernel, after setting CONFIG_ALIX=y and
CONFIG_LEDS_GPIO=m it works just fine on an ALIX 2D3
filename: /lib/modules/3.16.0-4-586/kernel/drivers/leds/leds-gpio.ko
alias: platform:leds
Hi,
> If I mount the filesystem in a rescue system with norecovery and the
> initrd is either different or missing that would narrow it down, no?
> And a workaround would be calling "sync" before the reboot.
Confirmed ..
Bernhard
signature.asc
Description: OpenPGP digital signature
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 02.05.2015 21:26, Ben Hutchings wrote:
Hi,
>
> I can see that the GRUB menu entry for 3.16.0-4-amd64 does seem to
> include an initramfs. Unfortunately the frame rate is quite low so
> I don't see any messages from GRUB indicating whether it s
Hi maximilian,
>> [ copied from debian-user again ]
>>
>> ---
>> Got another system with the symptoms and managed to get a snapshot.
>>
>> It is really extremely weird. The kernel output is
>>
>> List of all partitions:
>> No filesystem could mount root, tried:
>> Kernel panic - not syncing: VFS:
Hi,
[ copied from debian-user again ]
---
Got another system with the symptoms and managed to get a snapshot.
It is really extremely weird. The kernel output is
List of all partitions:
No filesystem could mount root, tried:
Kernel panic - not syncing: VFS: Unable to mount root fs on
unknown-blo
Package: initramfs-tools
Followup-For: Bug #783620
Hi,
from the debian-user mailinglist ...
Bernhard Schmidt wrote
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hi Ben,
On 28.04.2015 22:01, Ben Hutchings wrote:
> On Tue, 2015-04-28 at 21:39 +0200, Bernhard Schmidt wrote:
>> Hi,
>>
>> I have tried two times to send the screenshot to this bug, but it
>> was always eaten (deliver
Hi,
I have tried two times to send the screenshot to this bug, but it was
always eaten (delivered to @bugs.debian.org, but never made it to the
BTS). I have put it online at
http://users.birkenwald.de/~berni/volatile/783620.png
Note that there is a bit of local integration work in these systems (
> The uncompressed size is the same
>
> root@lxmhs63:/tmp# zcat /boot/initrd.img-3.16.0-4-amd64.broken >
> initrd.img-3.16.0-4-amd64.broken
> root@lxmhs63:/tmp# zcat /boot/initrd.img-3.16.0-4-amd64.broken >
> /tmp/initrd.img-3.16.0-4-amd64.broken
> root@lxmhs63:/tmp# ls -la /tmp/initrd.img-3.1
Package: initramfs-tools
Version: 0.120
Severity: important
Dear Maintainer,
I have a hard time wrapping my head around this bug, feel free to assign
somewhere
else.
We have started upgrading some of our production VMs to Jessie. The testsystems
worked
fine, but I have hit the following bug fo
Package: src:linux
Followup-For: Bug #714929
Control: found -1 3.16.7-ckt9-3
Control: severiy -1 important
Hi,
This still affects Jessie, I can easily reproduce it.
This bug makes it impossible to access the console of a VM without booting it
and adjusting
the kernel commandline, so I think t
Hi,
> the wireless driver occasionally complains about microcode errors. This
> happens
> around twice a week. It didn't happen at all with the 3.14 kernel. My laptop
> runs an Intel Wireless 7260 card.
I'm having exactly the same problem on my Dell Latitude E7240 at every
boot. I can only use t
Package: tgt
Followup-For: Bug #714868
Hi,
Looks like Ubuntu has started updating tgt on their own, including new
upstream versions and enabling RBD.
It would be great if Debian could import the Ubuntu changes on this one,
or maybe James Page (who seems to be maintaining it in Ubuntu) could take
Package: linux-image-3.2.0-4-486
Version: 3.2.51-1
Severity: wishlist
Hi,
please set the config options CONFIG_ALIX and CONFIG_LEDS_GPIO. They are not
set in both current stable and current testing kernels and are required to
control the GPIO LED in PCEngines ALIX boards. From the kernel config:
Package: src:linux
Followup-For: Bug #714929
Some more information.
- It still happens with 3.10-1-amd64 (3.10.1-1) from sid
- Workaround is (next to blacklisting) setting vmwgfx.enable_fbdev=1
on the kernel commandline, which is probably the same as setting the
kernel config option CONFIG_D
Hello Ben,
Package: src:linux
Version: 3.8-1~experimental.1
Severity: normal
My / is on a LVM volume. Kernel 3.8 logs 'Volume group "ssd" not found'
and "/dev/mapper/ssd-debian not found" on startup
These messages do not come from the kernel. LVM2 is a userland thing;
the kernel only provide
Package: src:linux
Version: 3.8-1~experimental.1
Severity: normal
My / is on a LVM volume. Kernel 3.8 logs 'Volume group "ssd" not found'
and "/dev/mapper/ssd-debian not found" on startup and drops me in the
initramfs shell. The LVM pv, vg and lv are visible in lvm just fine, but
the logical vo
On 15.02.2013 04:16, Ben Hutchings wrote:
Hello Ben,
> Please test a kernel with the attached patches, applied in the order:
>
> x86-PCI-for-debuggability-show-host-bridge-windows-e.patch
> x86-PCI-use-host-bridge-_CRS-info-by-default-on-2008.patch
> x86-PCI-Use-_CRS-by-default-on-VMware.patch
>
Hello Ben,
> This is not memory, it's MMIO (memory-mapped input/output) for the
> emulated VGA card. The kernel controls the addresses used for MMIO for
> PCI devices, but does not control the addresses used for RAM.
> Apparently the system firmware (or in this case the hypervisor) can
> provide
Am 14.02.2013 05:39, schrieb Ben Hutchings:
Hello Ben,
Squeeze is another story, but I think there is another problem as well.
Previously we sometimes saw the backtrace, sometimes just the following
message.
[ 44.22] VMCIUtil: Updating context id from 0x7a3c21d6 to
0x7a3c21d6 on event 0
On 11.02.2013 02:09, Ben Hutchings wrote:
Hello Ben,
> Control: tag -1 upstream moreinfo
>
> On Wed, 2013-02-06 at 18:02 +0100, Bernhard Schmidt wrote:
>> Package: src:linux
>> Version: 3.2.35-2
>> Severity: normal
>>
>> Adding additional RAM to a v
>
> On Wed, 2013-02-06 at 18:02 +0100, Bernhard Schmidt wrote:
>> Package: src:linux
>> Version: 3.2.35-2
>> Severity: normal
>>
>> Adding additional RAM to a virtual machine running Debian Wheezy on
>> VMware ESXi 5.0 often, but not always leads to
Attached /proc/iomem of the situation with VMware tools
- : reserved
0001-0009f3ff : System RAM
0009f400-0009 : reserved
000a-000b : PCI Bus :00
000c-000c7fff : Video ROM
000ca000-000cbfff : reserved
000ca000-000cafff : Adapter ROM
000cb000-000cbfff : Ad
Package: linux-2.6
Version: 2.6.32-20
Severity: wishlist
Hi,
the summary pretty much says it all, please consider backporting the
vmw_pvscsi module from 2.6.33 mainline to get full access to the (faster)
paravirtualized VMware SCSI controller.
-- Package-specific info:
** Version:
Linux version
36 matches
Mail list logo
