Hi
I started the agenda for this weeks meeting. It got already quite some
points, as we have a lot of discussion items left from last week.
See
https://salsa.debian.org/kernel-team/meetings/-/wikis/20240619
If you have more points, please just reply here.
Bastian
--
Respect is a rational pro
On Sat, Jun 01, 2024 at 09:13:09PM +0100, Sudip Mukherjee wrote:
> Absolutely. I dont remember why some of my packages (from 2019 - 2020)
> are in github. But I will definitely move them to salsa.
> About moving it under kernel team, I think I will say "no" to that
> unless Luca can give some very
Control: reassign -1 binutils/2.42.50.20240618-1
Control: affects -1 src:linux
On Sun, Jun 23, 2024 at 11:44:05AM +0200, Johannes Schauer Marin Rodrigues
wrote:
> One of the differences in the build environment between good and bad builds is
> binutils-arm-linux-gnueabihf with version 2.42-4 in t
Hi
This weeks meeting will happen tomorrow. Currently the agenda is empty.
See
https://salsa.debian.org/kernel-team/meetings/-/wikis/20240626
If you have more points, please just reply here.
Bastian
--
Computers make excellent and efficient servants, but I have no wish to
serve under them.
On Tue, Jun 25, 2024 at 05:51:41PM +0100, Luca Boccassi wrote:
>Anything build-depending on
> linux-headers-generic for the BPF header (eg: src:systemd) is affected.
Well, linux-headers is for kernel modules, not userland. Don't use it
this way then?
B
Source: linux
Version: 6.1.99-1
Severity: important
X-Debbugs-Cc: wa...@debian.org
Microsoft asked to Backport further changes to the Microsoft Azure
Network Adapter. This includes bug fixes and arm64 support.
Requested where:
- ec224d185e04131013121682e27adaa26b87a3a7 (bug fix)
- 40a1d11fc670ac
Hi
On Sun, Jul 14, 2024 at 09:22:32AM +0200, Paul Gevers wrote:
> Today I restarted the s390x host of ci.d.n because I lost access. I
> inspected the journal and noticed there were a lot kernel messages (several
> tens to hundreds per day) like "User process fault: interruption code 003b
> ilc:3 i
On Thu, Jul 18, 2024 at 08:06:46AM +0200, Paul Gevers wrote:
> However, that doesn't seem to work on our s390x host as it seems to freeze
> instead. Is this something known? Something I'm doing wrong (E.g. these
> options behaving differently on s390x)? Is this a s390x kernel bug?
This now points
Control: tags -1 moreinfo
On Thu, Jul 18, 2024 at 07:56:32PM +0200, Patrice Duroux wrote:
> I just faced this boot problem on my sid system for the first time
> since I updated the Linux kernel a few days ago.
Could you please provide an unfiltered kernel log? The one you attached
does not even
Hi
This weeks meeting will happen tomorrow.
Here you can find the current agenda:
https://salsa.debian.org/kernel-team/meetings/-/wikis/20240731
Please reply here if you would like to add more points.
Bastian
--
The sight of death frightens them [Earthers].
-- Kras the Klingon
Control: reassign -1 miniramfs 1.0.2
On Wed, Jul 31, 2024 at 05:03:25PM +1000, Russell Coker wrote:
> After the latest update to Debian/Unstable on my PinePhonePro I get the
> following error when creating an initramfs. It didn't happen with the
> previous
> version of initramfs-tools which was
On Sat, Aug 03, 2024 at 01:52:47AM +0200, Johannes Schauer Marin Rodrigues
wrote:
> according to Ben [1] this should disable the rt build and it mostly does but
> the package linux-headers-*-common-rt will still be built.
No bug in Debian, as we don't push this modification to Debian. But
fixed
On Fri, Aug 16, 2024 at 12:58:22PM +0200, Stefano Rivera wrote:
> The Technical Committee is hoping that this will be resolved without
> requiring us to make a decision. If the take-over offer resolves the
> issue, then we will probably vote to take no further action.
Well, take-over removes the n
Hi
On Wed, Aug 07, 2024 at 08:31:28AM +, daniel.u...@telekom.de wrote:
> We are kind of lucky. My colleagues updated the kernel on one the hosts,
> rebooted it and the problem occurred right away. Currently the system is
> running, but it looks like all san paths are gone ("multipath -ll" sh
Hi
This weeks meeting will happen tomorrow at
https://jitsi.debian.social/dkt.
Here you can find the current agenda:
https://salsa.debian.org/kernel-team/meetings/-/wikis/20240821
Please reply here if you would like to add more points.
Bastian
--
The sight of death frightens them [Earthers].
Control: tags -1 wontfix
Hi
Yes, this change is expected. It is documented in the NEWS file of the
package and should be showed to the user via apt-listchanges.
We decided to make this change, even if some systems will fail, to align
Debian better to a general purpose use case.
Bastian
--
Be
On Mon, Sep 09, 2024 at 11:51:17AM +0300, Martin-Éric Racine wrote:
> src:linux currently has an explicit Build-Depends on gcc-13. This defeats the
> whole point of building against whatever 'build-essential' pulls in for the
> target Debian release, and it results in several GCC suites getting
On Mon, Sep 09, 2024 at 05:56:50PM +0300, Martin-Éric Racine wrote:
> Fair enough. In that case, I suggest editing the following (4.5.1.
> Preparation) to remove the step about installing build-essential,
> since it installs a compiler suite that won't be used by src:linux.
build-essential is requ
Hi
This weeks meeting will happen tomorrow at 19:00 UTC in #debian-kernel.
Here you can find the current agenda:
https://salsa.debian.org/kernel-team/meetings/-/wikis/20240911
Please reply here if you would like to add more points.
Bastian
--
The sight of death frightens them [Earthers].
On Sat, Dec 24, 2022 at 11:44:49AM +0200, Jonathan Carter wrote:
> Will the archive team be moving those over? Is it up to firmware packagers
> to re-upload it to the correct component?
AFAIK this requires a re-upload. However, does the installer properly
include it yet? I need to check that.
I
Control: reassign -1 dkms - breaks kernel installation
Control: severity -1 grave
On Tue, Jan 17, 2023 at 09:36:26AM +0100, Stefano Simonucci wrote:
> Package: src:linux
> Version: 6.0.12-1
> Severity: critical
> Justification: breaks the whole system
No, it does not. The kernel is the system an
Control: tag -1 wontfix
On Sat, Feb 18, 2023 at 05:54:31PM +, Witold Baryluk wrote:
> e1000 emulation is a default in qemu. It would be nice to have available
> in a cloud kernel. While most of the time one will use virtio, or some
> other cloud specific driver, for troubleshooting images, boo
On Sat, Mar 25, 2023 at 05:54:23PM +0100, наб wrote:
> Naturally, it should succeed in every scenario.
This is
https://www.kernel.org/doc/html/latest/admin-guide/sysctl/fs.html#protected-symlinks
Bastian
--
We have found all life forms in the galaxy are capable of superior
development.
Control: tags -1 wontfix
On Wed, Mar 30, 2022 at 08:17:51AM +, Thomas Wouters wrote:
> So I tried to reproduce it with `virt-install` to figure out what's
> going on and could replicate similar behavior: the cloud-init user-data
> is, by default (for x86), provided to the guest as a SATA con
Source: linux
Version: 6.1.25-1
Severity: important
Microsoft asked to backport the jumbo frame support in the Microsoft
Azure Network Adapter from current master. The changes are not suitable
for stable@ and contained to this one driver.
Commit ids are something like
80f6215b450eb8e92d8b1f117a
Control: reassign -1 src:linux
Control: severity -1 important
On Mon, Jun 12, 2023 at 05:31:53PM +0200, Andreas Beckmann wrote:
> As a consequence, if cruft *-dkms packages are still installed, but fail
> to build the module for current kernels, this may result in upgrade
> failures. Therefore ple
Control: severity -1 important
Control: tags -1 moreinfo
On Mon, Jun 07, 2021 at 08:43:21PM +0100, Anton Ivanov wrote:
> Version: 5.10.13-1~bpo10+1
This is not the latest version. 5.10.24 (at least) is in buster-backports.
> [801076.291139] scsi host10: uas
> [801076.291557] scsi 10:0:0:0: Direc
Hi
On Tue, Jun 08, 2021 at 03:48:11PM +0200, Laurent Bigonville wrote:
> > > There is definitely something boggus here
> Yes, just tested it now and it's still happening with the kernel currently
> in unstable (5.10.40-1)
Why do you think this numbers are wrong? "fstrim" initially requests
disc
Hi
On Tue, Jun 08, 2021 at 11:43:06PM +0200, Laurent Bigonville wrote:
> Well I would expect that if I'm running fstrim, the same blocks would not be
> trimmed again (even after reboot) if I'm running the command again
But how would it know that it was already trimmed?
> Here it seems that it's
On Sat, Oct 29, 2022 at 12:31:18AM +0200, Christoph Anton Mitterer wrote:
> Is this going to be backported to bullseye?
First is needs to settle a bit.
But as you can see, in the past we did produce backports:
| firmware-nonfree | 20210818-1~bpo11+1 | bullseye-backports/non-free | source
Bastia
[Cc Ben as he gave feedback to the last iteration, Luca as he wanted
something actionable]
Hi folks
As I abondened the last try and also learned some new things in the
meantime, I'd like to discuss another try at re-organizing how Debian
does boot loaders and initramfs. This mail mostly tries to
On Thu, Nov 10, 2022 at 03:37:16AM +0100, Christoph Anton Mitterer wrote:
> l 6.0.0-3-amd64/build 6.0.0-3-amd64/source
> lrwxrwxrwx 1 calestyo calestyo 36 Nov 5 14:41 6.0.0-3-amd64/build ->
> /usr/src/linux-headers-6.0.0-3-amd64
> lrwxrwxrwx 1 calestyo calestyo 37 Nov 5 14:41 6.0.0-3-amd64/sourc
Hi Jörg
On Mon, Nov 07, 2022 at 11:40:46AM +0100, Jörg Behrmann wrote:
> On Tue, Nov 01, 2022 at 09:29:07PM +0100, Bastian Blank wrote:
> > ## Prior works
> >
> > [..]
> > - systemd install-kernel: only BLS as target, which nothing used by
> > default in Debia
Hi Luca
On Sun, Nov 06, 2022 at 02:14:54PM +, Luca Boccassi wrote:
> On Tue, 2022-11-01 at 21:29 +0100, Bastian Blank wrote:
> > ## Goals
> >
> > - Setup complete boot entries from packaged and generated files
> > - Support dumb file systems for /boot by d
Control: forcemerge 1023450 -1
On Fri, Dec 02, 2022 at 05:35:06AM -0700, Dan Nicholson wrote:
> The bullseye-backports 6.0.3 kernel contains an ext4 bug that causes
> the filesystem to become corrupted after resizing the filesystem. See
> https://www.spinics.net/lists/linux-ext4/msg85795.html for
Hi
Our documented, I think, policy is, that we don't support loading new
modules into an old kernel within the same ABI. This forces a reboot
after kernel installation.
However in a lot of cases this just worked. You could update the kernel
package and continue loading most modules.
Now we hav
Control: notfound -1 linux/5.14.6-2
On Fri, Sep 24, 2021 at 09:29:50PM +0200, Paul Gevers wrote:
> Currently this regression is blocking the migration of linux and it's
> signed versions to testing [1]. Due to the nature of this issue, I filed
> this bug report against both packages. Can you pleas
Control: severity -1 important
On Thu, Sep 16, 2021 at 10:23:53AM +0200, Gert Wollny wrote:
> Package: src:linux
> Version: 5.14.3-1~exp1
> Severity: critical
> Justification: breaks the whole system
No, it does not. The kernel is the system.
Bastian
On Thu, Oct 28, 2021 at 02:51:48PM +0200, Vincent Danjean wrote:
> Do you confirm this is a bug? Do you want I look
> for the first kernel in Debian with this regression?
It is not a bug, this are hardening settings. See documentation about
the protected_regular setting in
https://www.kernel.org/
Hi folks
I'd like to propose some pretty drastic reshaping of the way kernels,
initrd and bootloaders interact with each other and with dpkg.
Traditionaly we install kernel images and configs into /boot. During
installation we generate files in /boot (and housekeeping in /var/lib).
Setup symlink
Control: tag -1 wontfix
On Fri, Nov 12, 2021 at 12:23:13PM +0100, Mickaël Salaün wrote:
> The Landlock security feature is built in Debian kernel since
> 5.13.12-1~exp1 which is great! However, it is not enough to enable the
> CONFIG_SECURITY_LANDLOCK option as described in the related help. The
Control: tags -1 moreinfo
On Mon, Mar 22, 2021 at 08:40:34AM +0100, Mihai Moldovan wrote:
> Currently, mounting an EXT4-formatted volume with the case-insensitivity
> feature
> is impossible since CONFIG_UNICODE is not enabled in the kernel configuration.
Why would anyone want to do that?
> My
On Thu, Mar 25, 2021 at 03:00:06PM +0800, YunQiang Su wrote:
> YunQiang Su 于2021年2月20日周六 下午2:19写道：
> > https://lore.kernel.org/linux-mips/20210220061635.9976-1-yunqiang...@cipunited.com/T/#u
> > This patch for kernel can fix this problem.
> > Let's wait for the reply of kernel upstream community.
Control: tag -1 wontfix
Hi
On Sat, Apr 10, 2021 at 02:11:06PM -0700, Josh Triplett wrote:
> For cloud instances and VMs, it's helpful to be able to use ip=dhcp as a
> minimal network configuration. Enabling this option will do nothing
> unless the kernel command line includes ip=dhcp.
We don't s
Hi
On Mon, Apr 12, 2021 at 11:18:43PM +0200, Ben Hutchings wrote:
> I think I missed or forgot about that change when it happened. I'm not
> super happy about it, to be honest. It's been half-assed in that the
> cloud flavours still have a dependency on an initramfs builder, that
> should be a R
On Mon, Apr 12, 2021 at 10:30:49PM -0700, Josh Triplett wrote:
> On Tue, Apr 13, 2021 at 06:39:26AM +0200, Bastian Blank wrote:
> > Where was that discussed?
> It was discussed in
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=947759
> , with responses from both Ben and
On Sun, Oct 19, 2014 at 08:39:16PM -0500, Erik wrote:
> $ uname -a
> Linux ebk 3.2.0-4-amd64 #1 SMP Debian 3.2.54-2 x86_64 GNU/Linux
3.2.54 is a little bit smaller than 3.2.63. So you somewhere have a
stale image. Did you actually reboot?
Bastian
--
Earth -- mother of the most beautiful women
On Sat, Oct 04, 2014 at 12:53:29PM +0200, Sebastien Helleu wrote:
> ** Tainted: I (2048)
> * Working around severe firmware bug.
You may want to search for a fixed firmware, but this may be irrelevant
for the current problem.
> ** Kernel log:
[...]
This log does not show any message similar to
On Mon, Nov 17, 2014 at 12:46:45AM +0100, Jérémy Bobbio wrote:
> The first patch adds call to `dh_strip_nondeterminism` and
> `dh_fixmtimes`, both being part of the custom toolchain currently used
> for reproducible builds. Hence not tagging the bug with “patch” until
> they are integrated in debhe
On Sat, Nov 29, 2014 at 08:06:28PM +, Ben Hutchings wrote:
> apt-get fails to resolve this unless you add
> 'initramfs-tools/wheezy-backports' or '-t wheezy-backports' to the
> install command
The backports documentation asks users to use "-t …".
Bastian
--
Conquest is easy. Control is not.
On Mon, Jan 05, 2015 at 06:56:10PM +0100, Jérémy Bobbio wrote:
> We are currently experimenting with fixing mtimes in `dh_builddeb`
> instead of requiring a new helper. I have also done my latest
> experiments without `dh_strip_nondeterminism`. The attached patch adds
> the `-n` flag to gzip to com
On Sun, Feb 22, 2015 at 06:37:50PM +0100, U.Mutlu wrote:
> So, do you or anybody else know a working user-level keylogger
> that allows capturing/logging the keystrokes of a different user
> on the same machine?
Try "xev".
Bastian
--
Hailing frequencies open, Captain.
--
To UNSUBSCRIBE, email
On Fri, Feb 27, 2015 at 02:21:27AM +, Ben Hutchings wrote:
> > CONFIG_DRM_QXL
> > CONFIG_DRM_BOCHS
> I think these need new X drivers to be useful, but I'm not sure.
I forgot about them. Yes, they need the X drivers from Jessie and the
last time I looked at it they worked fine. The only prob
On Sat, Feb 28, 2015 at 11:11:50PM +, Ben Hutchings wrote:
> Who would be interested in doing a kernel team sprint?
I would be interested.
Bastian
--
--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debi
Control: severity -1 important
On Thu, Mar 12, 2015 at 08:57:16AM -0400, Tiago Saboga wrote:
> Mar 11 19:41:56 piolho kernel: ata1.00: exception Emask 0x0 SAct 0x70 SErr
> 0x0 action 0x6 frozen
> Mar 11 19:41:56 piolho kernel: ata1.00: failed command: READ FPDMA QUEUED
> Mar 11 19:41:56 piolho ke
On Thu, Oct 22, 2020 at 10:55:33PM +0200, Salvatore Bonaccorso wrote:
> TBH, I think not having it enabled by default until now saved us a
> couple of time from needing to release urgent fixes. It is more a gut
> feeling and might not have enough weight: but having it still disabled
> in bullseye b
Control: severity -1 important
On Mon, Nov 16, 2020 at 07:41:05PM +, Toni wrote:
> Severity: critical
Sorry, no. This problem does not break the package for everyone.
> On the console, after dmesg, these three lines repeat ad nauseum:
> mdadm: No arrays found in config file or automatically
Hi
On Mon, Dec 14, 2020 at 05:26:33AM +, 张 宁 wrote:
> I find in master branch, CRYPTO_SM4/CRYPTO_SM3 are disabled without clean
> justification.
SM2, SM3 and SM4 have always been disabled, as everything that does not
show up is implicitely disabled. So those commits don't change
anything, j
Control: tags -1 wontfix
Control: close -1
Hi nameless
On Mon, Dec 14, 2020 at 03:06:55PM +0100, mc36 wrote:
> please enable e1000 module in the cloud images
> the rationale here is that qemu, virtualbox and openstack
> defaults to this device so it would ease the life...
Sorry, but no. Thi
Control: tag -1 wontfix
On Fri, Aug 28, 2020 at 10:41:42PM +0100, Ben Hutchings wrote:
> On Fri, 2020-08-28 at 14:43 +0800, Hamish Moffatt wrote:
> > Could you please enable CONFIG_F2FS_FS in the cloud kernel?
> What makes you think f2fs will be commonly used in cloud deployments?
Marking it was
Moin
On Thu, Jan 07, 2021 at 10:33:55AM +0100, Drexl Johannes wrote:
> which blocks bootup. Disabling the module in modprobe.d via
> install drm_kms_helper /bin/true
> lets the system boot up, but remain in 800x600 px mode. SecureBoot is off,
> System is updated to todays sid; previous kernels di
Control: severity -1 important
Control: tags -1 help
I disabled the check in 5.10.1-1~exp1. There is no way to make the
kernel fit again without disabling major parts of it.
Downgrading the bug as nothing can be done.
Bastian
--
Lots of people drink from the wrong bottle sometimes.
Control: tag -1 moreinfo
Hi Charles
On Fri, Jan 15, 2021 at 05:55:47PM -0700, Charles Curley wrote:
> On boot, NetworkManager does its thing correctly, and gets the machine
> on the network. However, I use DHCP with fixed addresses. Getting the
> wrong MAC address throws this off, which is how th
Control: tag -1 moreinfo
On Wed, Jan 20, 2021 at 10:03:00PM +0800, GengYu Rao wrote:
> The kernel missed ec_sys module, as ec_sys.ko.gz in archlinux here:
> https://wiki.archlinux.org/index.php/ACPI_modules
> Could you please add this module to the kernel package?
What would you need this module
On Thu, Jan 21, 2021 at 06:28:16AM -0500, John Scott wrote:
> As discussed on the mailing list(s), I'm looking into making a udeb for
> firmware-ath9k-htc with kernel-wedge.
You missunderstood something. All the firmware stuff is _only_ shipped
as deb, not as udeb.
> To avoid clashing with the o
Moin
On Thu, Feb 11, 2021 at 10:15:02AM +0800, YunQiang Su wrote:
> > Could the mips porters comment on this? Given that we're close to the
> > release
> > of bullseye, I'm not convinced it's a good idea to change this now.
This option is also a dependency of several types of CPU support. So it
Control: tags -1 wontfix
On Thu, Feb 18, 2021 at 04:50:05PM +1100, Hamish Moffatt wrote:
> ecryptfs has been silently removed from the 5.10 kernel packages. This
> is not mentioned in the changelog.
Actually it is mentioned:
| * [cloud] Disable some further filesystems. (closes: #977005)
Basti
Hi David
On Fri, Jul 10, 2020 at 06:21:14PM +, David Awogbemila wrote:
> Google would like to have its cloud networking driver, the Google
> Compute Engine Virtual Ethernet driver (GVE) pulled into Debian
> releases.
I'm just working on this. Is there a way for me to actually test it? I
ass
Hi folks
I'll bump the compiler version to GCC 10 on the master branch soonish,
i.e. for 5.8 and later kernel versions. If there are any supported
architectures where GCC 10 is known to cause regressions, this can be
reverted *temporarily* for those architectures, but needs to be fixed
for the Bu
Hi Zach
On Tue, Aug 11, 2020 at 01:26:42PM -0700, Zach Marano wrote:
> Yes there is a feature on the image resource which will (currently) enable
> the device instead of virtio-net. If you add the "GVNIC" guestOS feature to
> and image or disk resource it will do this.
> https://cloud.google.com/c
Control: severity -1 important
On Mon, Aug 24, 2020 at 12:11:08PM +0200, Gianfranco Costamagna wrote:
> Hello, as explained on upstream ticket [1], the new kernel broke virtualbox,
> and the only fix that has been found
> so far is to export map_kernel_range and __get_vm_area_caller to modules
P
Control: tag -1 moreinfo
Control: severity -1 important
On Tue, Sep 08, 2020 at 01:36:45PM +0200, Vincent Lefevre wrote:
> This version fails to load kernel modules (no issues with previous
> Linux kernels provided by Debian). As a consequence, X does not work.
> ** Loaded modules:
> rfcomm
> ipt
Control: reassign -1 src:nvidia-graphics-drivers-legacy-390xx
On Tue, Sep 08, 2020 at 02:14:54PM +0200, Vincent Lefevre wrote:
> Sep 08 13:31:20 zira systemd-modules-load[408]: Error running install command
> 'modprobe nvidia-modeset ; modprobe -i nvidia-legacy-390xx-drm ' for module
> nvidia_dr
Control: tag -1 moreinfo
On Wed, Apr 30, 2014 at 09:25:34AM -0500, Justin McZeal wrote:
> It seems like we are getting random shutdowns, typically sometime between
> 7-9am CST. The last message in the logs is that a signal 15 was sent to all
> processes. Due to the nature of our business, we don
On Wed, Apr 30, 2014 at 01:36:49PM +0300, root wrote:
> dmesg
> showed the log below
The output of dmesg looks different (no leading time). Also it is
truncated. You can try using a serial console or netconsole to catch
the
On Tue, May 13, 2014 at 01:28:24PM -0300, Mauricio Faria de Oliveira wrote:
> diff --git a/debian/config/kernelarch-powerpc/config-arch-64-le
> b/debian/config/kernelarch-powerpc/config-arch-64-le
Please split this in little endian dependant and generic stuff.
Bastian
--
Women professionals do
On Tue, May 13, 2014 at 01:28:23PM -0300, Mauricio Faria de Oliveira wrote:
> diff --git a/debian/config/powerpc/defines b/debian/config/powerpc/defines
> index a11a336..ee929e5 100644
> --- a/debian/config/powerpc/defines
> +++ b/debian/config/powerpc/defines
> @@ -3,6 +3,7 @@ flavours:
> + powerp
On Mon, May 12, 2014 at 02:00:29AM +0100, Ben Hutchings wrote:
> I tried building 3.14.3-1 on powerpc, and that failed with a large ABI
> change (about 7000 out of 13000 symbols changed).
Okay, I can reproduce this with 3.14.2-1 in the powerpc64 image (not the
powerpc image).
> So I think that th
On Tue, May 13, 2014 at 09:04:45PM +0200, Bastian Blank wrote:
> Are you sure that powerpc is the only affected?
This looks pretty much like an unstable compiler support check. This
script hides any output, so we have no way to see what happened:
| ifeq ($(shell $(CONFIG_SHELL) $(srct
On Wed, May 14, 2014 at 02:05:34PM +0100, Ben Hutchings wrote:
> Since 'asm goto' has been around for a while, I suspect that the real
> failure was in linking a 64-bit executable on 32-bit powerpc.
Can't be. This script is called without any parameter, only the
compiler. Also it does not link b
Control: severity -1 normal
Control: tags -1 moreinfo
On Tue, May 20, 2014 at 11:31:06PM +0200, debian-b...@voidptr.de wrote:
Please get a name.
> On-screen output during a failed boot attempt:
> --8<--
> Decompressing Linux... Parsing ELF... done.
> Booting the kernel.
> Loading, please
On Sat, May 24, 2014 at 06:18:57PM -0300, Mauricio Faria de Oliveira wrote:
> --- /dev/null
> +++ b/debian/config/kernelarch-powerpc/config-arch-64-le
> @@ -0,0 +1,74 @@
> +##
> +## file: arch/powerpc/Kconfig
> +##
> +CONFIG_CRASH_DUMP=y
> +CONFIG_PPC_64K_PAGES=y
> +CONFIG_PPC_TRANSACTIONAL_MEM=y
On Sat, May 24, 2014 at 06:18:58PM -0300, Mauricio Faria de Oliveira wrote:
> index 269ddb0..77baad1 100644
> --- a/debian/config/kernelarch-powerpc/config-arch-64
> +++ b/debian/config/kernelarch-powerpc/config-arch-64
> @@ -1,12 +1,8 @@
> ##
> ## file: arch/powerpc/Kconfig
> ##
> -# CONFIG_CRA
On Sat, May 24, 2014 at 06:18:59PM -0300, Mauricio Faria de Oliveira wrote:
> Debian ppc64el will wait for the 'powerpc/boot: 64bit little endian wrapper'
> (zImage) patches upstream rather than shipping 32-bit tools for zImage.
And why do you add workarounds instead of the real patch?
Bastian
-
On Sat, May 24, 2014 at 06:19:00PM -0300, Mauricio Faria de Oliveira wrote:
> This patch didn't make mainline yet (3.15-rc6).
And why? Which tree currently holds it?
Bastian
--
No one may kill a man. Not for any purpose. It cannot be condoned.
-- Kirk, "Spock's Brain", starda
On Sun, May 25, 2014 at 06:52:27PM -0300, Mauricio Faria de Oliveira wrote:
> - CRASH_DUMP is not enabled on ppc64. I don't know why, so didn't change it.
Do I really need to tell you that you can't come and work on exactly one
thing without looking left and right? If you think you need it and it
Hi Phillip
On Mon, Jun 16, 2014 at 12:31:25AM +0200, Philipp Kern wrote:
> There are many ways a kernel can be updated on disk that are not
> necessarily triggered by user action.
Debian does not install any automatic update stuff, so it is always user
action.
> Ubuntu claims with every update t
On Sun, Jul 06, 2014 at 10:25:41PM +0200, Aurelien Jarno wrote:
> I intend to add a new debconf template in the linux package, that will
> appear on mips/mipsel systems. As English is a foreign language for me
> I appreciate if some people can review it. Thanks in advance.
Don't you think this bel
On Fri, Aug 01, 2014 at 09:51:01PM +0200, Simon Richter wrote:
> The connection is always terminated with an incoming RST packet from the
> remote server, with correct sequence number and containing data(!), so my
> suspicion is that sometimes packets are somehow mangled, although I don't
> have th
Control: severity -1 important
On Tue, Jul 02, 2019 at 04:50:09PM +0200, Santiago Vila wrote:
> On a virtual machine running buster on Google Compute Engine, where
> this kernel package is the default, I get the following messages:
I remember a different report about this, but don't know where.
Hi Ben
On Tue, Sep 24, 2019 at 03:06:09PM +0100, Ben Hutchings wrote:
> Since linux and linux-latest are so closely related, should they
> actually be separate source packages? I don't know the history here.
It dates back to before the common linux package. Each version was it's
own source pac
Moin
In Debian most people prefer to have changelog entries with all changes,
so changes always contain a modification to debian/changelog.
If we also start to use merge requests on Salsa, all those changes will
contain modifications to debian/changelog, which will usualy conflict
with each other
Moin
It turns out we got again problems with irqbalance.
It was added as recommends of the main image in 3.16, as it was reported
that older kernels move all interrupts to CPU 0 without help.[1]
In the meantime the kernel can do balancing on it's own. In 4.9, I've
seen it working with aacraid,
On Fri, Apr 12, 2019 at 10:53:47AM +0200, Bastian Blank wrote:
> With 4.19, even on real hardware, where interrupts have an affinity for
> all cpus, each interrupt is actually delivered to different cpu.
It seems a lot of this comes from
https://lore.kernel.org/patchwork/cover/801590/
R
Package: src:linux
Version: 4.19.28-2
Severity: important
On Fri, Apr 12, 2019 at 09:10:32PM +0100, Ben Hutchings wrote:
> On Fri, 2019-04-12 at 10:53 +0200, Bastian Blank wrote:
> > It turns out we got again problems with irqbalance.
> >
> > It was added as recommends of t
Control: severity -1 serious
On Fri, Apr 12, 2019 at 10:56:29PM +0200, Bastian Blank wrote:
> > Then let's drop the recommendation.
> Okay.
After re-evaluating, I'll consider that a blocker.
Regards,
Bastian
--
The more complex the mind, the greater the need for the
Hi Chris
On Sat, May 25, 2019 at 10:03:07PM -0400, Chris Zubrzycki wrote:
> GKH has been purging __kernel_fpu_{begin,end}() from all kernels
> including LTS (4.19/5) and it's needed for AES-NI/AVX support in the zfs
> package.
The commit also tells you why this was done. Please bring this up to
Control: severity -1 wishlist
On Mon, Jun 03, 2019 at 06:39:39PM -0700, Mo Zhou wrote:
> I believe this is a kernel bug. Instead of submitting
> a grave RC for the 10.1 release, we'd better sort it out
> right now before the Buster release.
We already stated that we wont change it by marking this
Hi Zigo
On Thu, Jun 06, 2019 at 02:43:16PM +0200, Thomas Goirand wrote:
> In such case, would you consider maintaining this tiny patch?
> https://github.com/NixOS/nixpkgs/pull/61076/commits/7b77c27caa8617c82df5c5af6b9ce6ae010d7f9a
Please read https://bugs.debian.org/929557.
Thanks for following
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 "Version 78.0.3904.97 (Official Build) (64-bit)")
Please try:
| sysctl -w kernel.unprivi
1201 - 1300 of 1950 matches
Mail list logo
