i'd like to verify something if this is not too much of an inconvenience...
I'd just like to have an md5sum or shasum on this very specific kernel
.deb or even if its the kernel image
/var/cache/apt/archives/linux-image-3.14-0.bpo.1-686-pae_3.14.7-1~bpo70+1_i386.deb
thanks
--
To
Package: initramfs-tools
Version: 0.116
Severity: important
a booted custom kernel is being used and installing a new kernel package
fails as the initramfs script in /etc/kernel/postinst.d/ fails
apt-get install linux-image-3.14-2-amd64enter was issued
, and mkinitramfs also fails
'
Package: initramfs-tools
Version: 0.116
Severity: important
a booted custom kernel is being used and installing a new kernel package
fails as the initramfs script in /etc/kernel/postinst.d/ fails
apt-get install linux-image-3.14-2-amd64enter was issued
, and mkinitramfs also fails
'
fwiw I commented-out line MODULES=dep
(there's only one line in this file)
/etc/initramfs-tools/initramfs.conf
and installation(apt-get -f install) was able to complete while making
an initrd image for kernel 3.14-2-amd64
--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
Package: linux-image-3.14-2-amd64
Version: 3.14.15-2
Severity: important
Routing fails when there are macvtaps attached and SNAT/DNAT is used for
routing with a tap device. (The routing being talked about concerns
between eth0's public IP address and tap0 which is not a macvtap device
on
the kernel version is quite irrelevant because it occurs with any custom
kernel that does not have modules built outside the kernel. So it
happens for 3.14, 3.15 and 3.16 kernels that don't have any
/lib/modules/kernel version paths needed for them.
The problem is dramatic because I would be
(/boot/bzImage-3.16.1--std-ipv6-64 to be more complete, but it
occurs with any kernel that doesn't have modules built externally)
/boot/3.16.1--std-ipv6-64-vps and it doesn't have any modules
external of it(this is by intention to minimize surface attacks on a
thanks
--
To
WARNING: missing /lib/modules/3.16.1--std-ipv6-64-vps
^ Already implies the kernel since the first message. I thought the
provided information was replicable enough.
If someone wants to test this out, be my guest.
--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with
apt-get install linux-image-3.14-2-amd64enter and fails.
I suggest to close the bug because nobody is using a custom kernel. The
scripts are looking for /lib/modules/kernel version where kernel
version==My unpackaged kernel that has been copied to /boot. And this
is the running kernel.
I
If someone tests it without any kernel modules paths (/lib/modules
empty), and with a kernel(not needing an initrd in /boot as well),
apt-get install kernel will fail
I can understand why nobody wants to verify anything here because it
takes time to compile a kernel without initrd nor any
Package: linux-image-3.16-2-amd64
Version: 3.16.3-2
Severity: important
There's port 138 traffic on a virtual 1:1 ethernet wire and I'm trying
to find out where it's coming from, anyone want to tackle this? :)
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=765502
--
To UNSUBSCRIBE, email
thanks I found the culprit, and not because I didn't know what I was
doing.. the output from the macvtaps that I'm using here as network
interfaces was letting traffic from the hypervisor. But the problem
didn't arise due to it not being setup properly but rather a technical
limitation of the
Package: linux-image-3.17-rc5-amd64
Version: 3.17~rc5-1~exp1
Severity: normal
hi, can the following be a kernel problem?
I'll explain a bit, it's got to do with the iptables command..
(fwiw, there's a bug with the lsb-functions, 40-systemd which is instead
this can be used to test rules.v4
Package: linux-image-3.17-rc5-amd64
Version: 3.17~rc5-1~exp1
Severity: normal
hi, can the following be a kernel problem?
I'll explain a bit, it's got to do with the iptables command..
(fwiw, there's a bug with the lsb-functions, 40-systemd which is instead
this can be used to test rules.v4
There's a bug in multiple places.
1) netfilter-persistent/systemd fails
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=764950
2) Emailed J.Wiltshire, he never responded. He's responsible for the
netfilter package
3) There is a systemd bug related to the netfilter-persistent package,
this report is for package maintainers, not clueless idiots.
thank you
--
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/5441201a.2070...@videotron.ca
Package: linux-image-3.16.0-4-amd64
Version: 3.16.7-ckt9-3~deb8u1
Severity: normal
Not sure what is being changed in the kernel going for jessie, but from
what I can tell for two upgrades I had to resort to a newer kernel from
debian's experimental.
I have got two systems here that get the
Package: linux-image-3.16.0-4-amd64
Version: 3.16.7-ckt9-3~deb8u1
Severity: important
A simple test with iptables against Jessie's default kernel fails to
work, but using a custom kernel not from repositories and iptables
works. A simple test is done allowing one match rule, and it can
please close this bugreport (discovered this bug should be handled
better by another source -- openvswitch)
thanks
--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive:
Package: linux-image-4.6.0-0.bpo.1-amd64
Version: 4.6.1-1~bpo8+1
Severity: normal
kernels 4.5 and 4.6 breaks qemu-nbd from mapping partitions
qemu-nbd can map partitions from VM images and raw disk images to
/dev/nbdNpM nodes, but proper module options have to be loaded prior so
that qemu-nbd
Package: linux-image-4.7.0-0.bpo.1-amd64-unsigned
Version: 4.7.2-1~bpo8+1
Severity: normal
There's a bug with ext4 on the new 4.7 kernel -- rare but it happened
here on an ext4 mountpoint (/home /dev/md1 ext4 rw,relatime,data=ordered)
when a new file is created, the "create time" is not
Package: linux-image-5.2.0-0.bpo.3-rt-amd64-unsigned
Version: 5.2.17-1~bpo10+1
Severity: important
When this kernel is used, the latest version of chrome crashes saying it
can't launch because it is not able to create its own sandbox.
(chrome "Version 78.0.3904.97 (Official Build) (64-bit)")
it is ok to use this mode as enabled.
On 2019-11-16 3:13 a.m., Bastian Blank wrote:
On Fri, Nov 15, 2019 at 11:23:09PM -0500, westlake wrote:
When this kernel is used, the latest version of chrome crashes saying it
can't launch because it is not able to create its own sandbox.
(chrome "Ve
23 matches
Mail list logo
