Bug#1037915: linux-image-6.1.0-9-amd64: Known kernel issue makes Debian 12 unusable for Android firmware builds

2023-06-14 Thread Bastian Blank
Control: forcemerge 1036755 -1 On Wed, Jun 14, 2023 at 10:40:55AM +0100, Al Sutton wrote: > Debain 12 has been released with a known bug which causes Android firmware > builds to > fail (https://lkml.org/lkml/2023/3/2/797) which makes bookwork unusable for > the Android > firmware community. T

Bug#1038720: Missing hyperv_fb.ko in debian 12.0 kernel image 6.1.0-9-amd64

2023-06-20 Thread Bastian Blank
On Tue, Jun 20, 2023 at 03:32:19PM +0200, RSA wrote: > Hello, I think kernel module hyperv_fb.ko is missing in the package. It was > present in version 5.10.0-22 before upgrading to debian 12. > > $ find /lib/modules/5.10.0-23-amd64 -name hyperv_fb.ko > /lib/modules/5.10.0-23-amd64/kernel/drivers

Bug#1038720: Missing hyperv_fb.ko in debian 12.0 kernel image 6.1.0-9-amd64

2023-06-20 Thread Bastian Blank
On Tue, Jun 20, 2023 at 06:50:10PM +0200, Ben Hutchings wrote: > > This was replaced by hyperv_drm, which provides a standard mode > > selection output. > ...although we do still build hyperv_fb for the cloud-amd64 flavour, > which seems like a mistake. Because the cloud-amd64 flavour disables DRM

Bug#1040343: linux-image-5.10.0-9-amd64: Kernel silenty de-supported nfsv3 UDP mounts

2023-07-05 Thread Bastian Blank
Control: severity -1 normal Hi On Tue, Jul 04, 2023 at 06:35:44PM +0200, Hauke Fath wrote: > /misc /etc/auto.misc > -nfsvers=3,proto=udp,resvport,retrans=5,rsize=16384,wsize=16384,rw,hard And if you set it to TCP (the default) or better directly switch to NFSv4? > This upstream decisi

Bug#1040346: linux-image-6.3.0-2-amd64: AMDGPU only with unusable high resolution available

2023-07-05 Thread Bastian Blank
Control: tags -1 moreinfo Hi Klaus On Tue, Jul 04, 2023 at 06:42:40PM +0100, Klaus Ethgen wrote: > With this update of linux-image, there is only the highest resolution > available anymore. As this is 3840x2400, it leaves the screen completely > unreadable and unusable. But this is what you want

Bug#1040178: Kernel modules will not build, missing asm/orc_header.h

2023-07-05 Thread Bastian Blank
Control: reassign -1 dkms On Wed, Jul 05, 2023 at 10:53:19AM +0200, Vincent Lefevre wrote: > On 2023-07-04 16:13:56 +0200, Andreas Beckmann wrote: > > This needs to be fixed before linux 6.3.0-2-* can migrate to testing, > > otherwise it will break dkms module building for everyone still having >

Bug#1040346: linux-image-6.3.0-2-amd64: AMDGPU only with unusable high resolution available

2023-07-05 Thread Bastian Blank
Control: reassign -1 src:linux 6.3.11-1 Control: tags -1 unreproducible On Wed, Jul 05, 2023 at 11:31:06AM +0100, Klaus Ethgen wrote: > > But this is what you want, you want to use the full resolution of the > > output and scale the output (this is called HiDPI). If you try to > > change the reso

Bug#1040663: linux: Please build linux-libc-dev package for loong64

2023-07-12 Thread Bastian Blank
Control: tags -1 confirmed Hi On Sat, Jul 08, 2023 at 08:41:03PM +0200, John Paul Adrian Glaubitz wrote: > Please enable building the linux-libc-dev package for the new Debian > architecture loong64. > The corresponding kernel architecture is called "loongarch". I can't find loong64 in the debi

Debian Kernel version and ABI in respect of #1040901

2023-07-13 Thread Bastian Blank
Hi folks You might have heard that the masters of Linux Secure Boot, aka shim reviewers, have spoken. They have told us that our way of handling kernel modules is not longer acceptable. For some context see #1040901. This means for us that we have to make sure that kernel and modules can't be m

Bug#1033663: linux: reproducible-builds: Embedded build path in various binaries

2023-07-14 Thread Bastian Blank
On Thu, Jul 13, 2023 at 11:53:40PM -0700, Vagrant Cascadian wrote: > Any objections to me merging these patches? Prefer if they remain > separate or squash them into a single patch? Hmm, I have to check, but dpkg-buildflags should already provide this flag and all the modified locations are for us

Re: Debian Kernel version and ABI in respect of #1040901

2023-07-17 Thread Bastian Blank
Hi On Thu, Jul 13, 2023 at 11:28:31PM +0300, Adrian Bunk wrote: > On Thu, Jul 13, 2023 at 09:16:15PM +0200, Bastian Blank wrote: > > ### NMU > > Can be easily added back by adding "bX" or so to the ABI. > That would be confusing, bX is naming convention for binNMUs in

Re: Debian Kernel version and ABI in respect of #1040901

2023-07-17 Thread Bastian Blank
On Fri, Jul 14, 2023 at 04:17:34PM +0200, Ben Hutchings wrote: > On Thu, 2023-07-13 at 21:16 +0200, Bastian Blank wrote: > [...] > > ## Proposed behaviour > > > > This tries to make sure everything apart from experimental gets new > > names and ABI on every u

Re: Debian Kernel version and ABI in respect of #1040901

2023-07-23 Thread Bastian Blank
On Thu, Jul 13, 2023 at 09:16:15PM +0200, Bastian Blank wrote: > Please share your thoughts or if we have a better solution overall. After a lot of thinking, maybe a solution that allows for incompatible package updates without renames would be more useful. Something like: We uncouple

Bug#1050368: please provide full set of uAPI headers

2023-08-23 Thread Bastian Blank
Control: tags -1 moreinfo Hi Dmitry On Wed, Aug 23, 2023 at 08:10:17PM +0300, Dmitry Baryshkov wrote: > The linux-libc-dev package provides only a limited set of uAPI headers. > For example, scsi, drm, video, etc. headers are missing from the > package. scsi headers are shipped by libc6-dev, see

Bug#1050991: FTCBFS amd64 -> arm64 due to using host-arch flags for native builds and vice-versa

2023-09-01 Thread Bastian Blank
Control: severity -1 normal On Fri, Sep 01, 2023 at 09:15:50AM +0200, Johannes Schauer Marin Rodrigues wrote: > Helmut informed me that bugs that break bootstrap (rebootstrap fails to > cross-build linux-libc-dev because of this bug) are usually filed with serious > severity, so doing that now. T

Bug#1050991: FTCBFS amd64 -> arm64 due to using host-arch flags for native builds and vice-versa

2023-09-02 Thread Bastian Blank
On Fri, Sep 01, 2023 at 08:36:53AM +0200, Johannes Schauer Marin Rodrigues wrote: > diff -Nru linux-6.4.11/debian/rules.real linux-6.4.11/debian/rules.real > --- linux-6.4.11/debian/rules.real 2023-08-17 09:05:43.0 +0200 > +++ linux-6.4.11/debian/rules.real 2023-09-01 06:43:41.00

Bug#1050991: FTCBFS amd64 -> arm64 due to using host-arch flags for native builds and vice-versa

2023-09-02 Thread Bastian Blank
On Fri, Sep 01, 2023 at 09:15:50AM +0200, Johannes Schauer Marin Rodrigues wrote: > Helmut informed me that bugs that break bootstrap (rebootstrap fails to > cross-build linux-libc-dev because of this bug) are usually filed with serious > severity, so doing that now. Thanks! Cross-building linux-

Bug#1050991: FTCBFS amd64 -> arm64 due to using host-arch flags for native builds and vice-versa

2023-09-03 Thread Bastian Blank
On Sun, Sep 03, 2023 at 10:02:16AM +0200, Johannes Schauer Marin Rodrigues wrote: > so rebootstrap uses the stage1 build profile which should be building headers > only. Still it fails with the same error I've reported for a full build: The stage1 profile is deprecated according to the documentat

Re: Debian Kernel version and ABI in respect of #1040901

2023-09-03 Thread Bastian Blank
On Sun, Jul 23, 2023 at 09:44:40AM +0200, Bastian Blank wrote: > After a lot of thinking, maybe a solution that allows for incompatible > package updates without renames would be more useful. Something like: > > We uncouple the package names and ABI. The ABI will include the > c

Re: Debian Kernel version and ABI in respect of #1040901

2023-09-03 Thread Bastian Blank
On Mon, Jul 24, 2023 at 10:36:47PM +0300, Adrian Bunk wrote: > A policy question is that it might be a good idea to rename the packages > when publishing a regression update for a DSA, that's the only place I see > where this problem might otherwise reach production systems. Adding another modifi

Bug#1051087: reportbug: linux-headers-amd64 from bullseye-backports cannot be installed (unmet dependencies)

2023-09-03 Thread Bastian Blank
Hi Laurent On Sun, Sep 03, 2023 at 11:16:03AM +0200, Laurent BRULET wrote: > It's still not entirely clear to me, whether this transient issue (where > linux- > image-amd64 can be installed while the corresponding linux-headers-amd64 > can't) > is a "standard case" for backports, or it is an "ex

Bug#1035378: linux - Backport changes to Microsoft Azure Network Adapter

2023-09-07 Thread Bastian Blank
. While the stock driver in 6.1 kind of works, it is not really usable for end user workloads. On Tue, May 02, 2023 at 01:38:40PM +0200, Bastian Blank wrote: > Microsoft asked to backport the jumbo frame support in the Microsoft > Azure Network Adapter from current master. The changes a

Re: Releasing linux/6.1.52-1 bookworm-security update without armel build, Image size problems

2023-09-09 Thread Bastian Blank
Hi On Sat, Sep 09, 2023 at 11:13:56AM +0200, Paul Gevers wrote: > If we're now reaching the final limit and if it was foreseeable that we > would reach that limit, then yes it would have made sense to drop armel > *before* the bookworm release, but alas. If the kernel team can't support > the kern

Bug#1051577: iproute2: obsolete conffiles

2023-09-11 Thread Bastian Blank
On Mon, Sep 11, 2023 at 01:06:06PM +0100, Luca Boccassi wrote: > As far as I understand dpkg's conffile machinery should recognize if > you changed anything, and leave it in place. Upstream moved the > default ones to /usr, so we just follow what they do. Actually using rm_conffile is wrong. This

Bug#1052006: linux-image-6.5.0-1-amd64 breaks X on amd GPU

2023-09-16 Thread Bastian Blank
Control: tag -1 moreinfo Hi Klaus On Fri, Sep 15, 2023 at 10:18:55PM +0100, Klaus Ethgen wrote: > Booting with the new kernel makes the display (1920x1200) heavily > flckering, diplaying two times the same one above the other and only > displaying about 1/4 of the screen smashed together on the l

Bug#1040901: Upcoming changes to Debian Linux kernel packages

2023-09-24 Thread Bastian Blank
Hi folks Debian currently does Secure Boot signing using a shim chained to the Microsoft key. This use requires that we follow certain rules. And one of the recent changes to those rules state that our method of signing kernel modules also with the same key will not be allowed anymore. Some inf

Re: Upcoming changes to Debian Linux kernel packages

2023-09-24 Thread Bastian Blank
Hi Andreas On Sun, Sep 24, 2023 at 11:10:36PM +0200, Andreas Beckmann wrote: > On 24/09/2023 15.01, Bastian Blank wrote: > > ## Kernel modules will be signed with an ephemeral key > > > > The modules will not longer be signed using the Secure Boot CA like the > &

Bug#1040901: Upcoming changes to Debian Linux kernel packages

2023-09-24 Thread Bastian Blank
Hi Ben On Sun, Sep 24, 2023 at 06:05:09PM +0200, Ben Hutchings wrote: > On Sun, 2023-09-24 at 15:01 +0200, Bastian Blank wrote: > > The same upstream version in testing and backports will have the same > > package name. > This is not OK, because they will be incompatibl

Re: Upcoming changes to Debian Linux kernel packages

2023-10-01 Thread Bastian Blank
On Mon, Sep 25, 2023 at 04:35:08AM +0200, Andreas Beckmann wrote: > On 25/09/2023 00.50, Bastian Blank wrote: > > Already built modules remain until someone deletes it. So you can also > > switch back to the still installed older kernel version and it will have > > the

Re: Upcoming changes to Debian Linux kernel packages

2023-10-03 Thread Bastian Blank
Hi Sam On Tue, Oct 03, 2023 at 08:31:57AM -0600, Sam Hartman wrote: > I still think it would help if you would work more on articulating what > problem you are trying to solve with the linux-headers versioning > change. I have read multiple versions of this proposal, and your > follow-ups, and I

Re: Upcoming changes to Debian Linux kernel packages

2023-10-04 Thread Bastian Blank
Hi Andreas On Tue, Oct 03, 2023 at 11:58:29PM +0200, Andreas Beckmann wrote: > That should solve the problem where several source packages need to be > updated together. The problem does not come from multiple source packages that need to be updated together. Instead it comes from the way Debian

Re: Upcoming changes to Debian Linux kernel packages

2023-10-04 Thread Bastian Blank
On Tue, Oct 03, 2023 at 03:00:53PM -0500, Robert Nelson wrote: > On Tue, Oct 3, 2023 at 2:54 PM Adrian Bunk wrote: > > How will the user get the headers matching this previously-used kernel > > that are required until we provide a kernel with the regression fixed? The same as now: nowhere, becaus

Bug#1040901: Upcoming changes to Debian Linux kernel packages

2023-10-05 Thread Bastian Blank
Hi On Sun, Sep 24, 2023 at 06:05:09PM +0200, Ben Hutchings wrote: > > Multiple uploads of the same upstream version will have > > the same package name, but those rarely happens. > Those happen fairly often for urgent security updates. We could encode that in the upstream version. Aka to have co

Bug#1040901: Upcoming changes to Debian Linux kernel packages

2023-10-07 Thread Bastian Blank
Moin On Sun, Sep 24, 2023 at 03:01:51PM +0200, Bastian Blank wrote: > ## Kernel modules will be signed with an ephemeral key This is now https://salsa.debian.org/kernel-team/linux/-/merge_requests/607. > ## Image packages contains more version info > > Example: linux-image-6.5.3

Bug#1040901: Upcoming changes to Debian Linux kernel packages

2023-10-20 Thread Bastian Blank
[ Removing some lists ] On Sat, Oct 07, 2023 at 04:53:33PM +0200, Bastian Blank wrote: > > ## Image packages contains more version info > > > > Example: linux-image-6.5.3-cloud-arm64 > > > It will not longer be possible to reliably derive the package name from > &g

Re: getting allwinner SoC support upstream (was Re: Uploading linux (3.9.4-1))

2013-06-05 Thread Bastian Blank
On Wed, Jun 05, 2013 at 08:46:30PM +0100, Luke Kenneth Casson Leighton wrote: > to begin to describe the problem in getting allwinner soc source code > upstream is this: not only do we have the usual "let's get it out the > door as fast as possible" learning curve of a very young, very new and > b

Bug#712590: ath9k: packet loss

2013-06-17 Thread Bastian Blank
Control: tag -1 moreinfo On Mon, Jun 17, 2013 at 10:19:51AM -0500, Ryan Nowakowski wrote: > ** Tainted: PO (4097) > * Proprietary module has been loaded. > * Out-of-tree module has been loaded. Please remove the out-of-tree modules. We don't support systems in this state. Bastian -- Those wh

Bug#690737: CONFIG_FANOTIFY_ACCESS_PERMISSIONS

2013-06-23 Thread Bastian Blank
On Sun, Jun 23, 2013 at 08:57:17PM +0200, Heinrich Schuchardt wrote: > Unfortunately Debian users have to build their own custom kernel > (with kpkg) if they want to use a virus scanner relying on the > fanotify interface as CONFIG_FANOTIFY_ACCESS_PERMISSIONS is set to > "N" even in the most recent

gcc 4.8

2013-06-24 Thread Bastian Blank
Hi I did a first build of Linux 3.9 with gcc 4.8. It works fine on s390x, however I found a weird not longer reproducible bug in s390. I think about using it as default pretty fast for all architectures. Bastian -- Change is the essential process of all existence. -- Spock, "Let

Bug#715269: linux-image-3.2.0-4-amd64: High Load, High Rescheduling Interrupts in Wheezy

2013-07-07 Thread Bastian Blank
On Sun, Jul 07, 2013 at 08:11:53AM -0500, Will Platnick wrote: > My problem is that my Wheezy boxes have a load of over 3 and are not > staying up during our peak time, What do you mean with "are not staying up"? The load itself is no real indicator. > Rescheduling Interrupts: 4109580 on Wheezy v

Bug#715478: Correctly match *,sec=krb5,*

2013-07-09 Thread Bastian Blank
On Tue, Jul 09, 2013 at 03:57:08PM +0200, Jan-Marek Glogowski wrote: > +case "$OPTS" in > +sec=krb5|*,sec=krb5|sec=krb5,*|*,sec=krb5,*|\ > +sec=krb5i|*,sec=krb5i|sec=krb5i,*|*,sec=krb5i,*|\ > +sec=krb5p|*,sec=krb5p|sec=krb5p,*|*,sec=krb5p,*) I wonder if

Bug#715548: linux-image-3.9-1-amd64: NFS causes a general protection fault

2013-07-10 Thread Bastian Blank
On Wed, Jul 10, 2013 at 12:51:35PM +0200, Francois Gouget wrote: > I have a Solaris 11.11 (vmware) virtual machine which mounts a host > filesystem via NFS. > With the linux-image-3.2.0-3-amd64 kernel all was fine. > But with the linux-image-3.2.0-4-amd64 one the NFS accesses soon result in > the

Bug#715478: Correctly match *,sec=krb5,*

2013-07-10 Thread Bastian Blank
On Tue, Jul 09, 2013 at 05:46:26PM +0200, Jan-Marek Glogowski wrote: > There are also bash regexp and IFS: bash-only, so well. > OLDIFS=$IFS Missing quotes. > IFS="," > for OPT in $OPTS; do > if [[ $OPT =~ ^sec=krb5[ip]?$ ]]; then > AUTO_NEED_

Re: When did the naming convention for linux-source- change?

2013-07-10 Thread Bastian Blank
On Wed, Jul 10, 2013 at 12:31:02PM +0300, Борислав Събев wrote: > Can anyone tell me when did the naming convention for the > "linux-source-N.N.N" packages change? Never. The naming convention is "linux-source-VERSION". The version is somehow related to the upstream version, which was something li

Bug#578189: please move common headers to /usr/src/linux-headers-`uname -r`

2013-07-14 Thread Bastian Blank
On Sun, Jul 14, 2013 at 10:17:33AM +0200, Harald Dunkel wrote: > Any news about this? Nothing. What exactly do you want? Bastian -- Spock: The odds of surviving another attack are 13562190123 to 1, Captain. -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of

Bug#711585: [linux-image-3.9-1-loongson-2f] linux 3.9.4-1 for loongson-2f doesn't halt/reboot/suspend-disk.

2013-07-21 Thread Bastian Blank
Control: tag -1 help On Fri, Jun 07, 2013 at 11:56:09PM -0600, Javier Vasquez wrote: > When rebooting, halting or suspending to disk on a mini-pc with > loongson-2f, it just hangs, printing a weird trace. Noone is currently really responsible for the mips kernel in Debian. So your best bet is to

Bug#717689: linux: please review and merge m68k patch

2013-07-23 Thread Bastian Blank
On Tue, Jul 23, 2013 at 09:26:28PM +, Thorsten Glaser wrote: > Which package is responsible for the inclusion of arch-specific > kernel modules into the initrd (for MODULES=most right now; I > have yet to try MODULES=dep)? initramfs-tools Bastian -- Violence in reality is quite different fr

Bug#717689: linux: please review and merge m68k patch

2013-07-23 Thread Bastian Blank
On Tue, Jul 23, 2013 at 08:42:04PM +, Thorsten Glaser wrote: > +CONFIG_IOSCHED_DEADLINE=m > +CONFIG_IOSCHED_CFQ=m Should be configured in the top config. > +# CONFIG_EXT2_FS_SECURITY is not set > +# CONFIG_EXT3_FS_SECURITY is not set Why? > -CONFIG_EXT4_FS=y > -CONFIG_EXT4_USE_FOR_EXT23=y

Bug#623377: rpcbind: Please include upstart support in the rpcbind package

2013-08-13 Thread Bastian Blank
On Tue, Aug 13, 2013 at 01:15:31AM +0200, Steve Langasek wrote: > + * Fix to look directly in /run instead of via the /var/run symlink. Where is the bug report for this? > case "$1" in > start) > +if init_is_upstart; then > +exit 1 > +fi Where is this document

Re: Plan of action for Secure Boot support

2013-08-14 Thread Bastian Blank
On Wed, Aug 14, 2013 at 12:30:55AM +0200, Ben Hutchings wrote: > Editing of binary packages is icky, so that's not part of the plan. > Instead, after dak signs an executable, the package maintainer downloads > and copies those into a separate 'source' package, which has a trivial > debian/rules. (

Bug#720272: warn upon installing on non pae systems

2013-08-19 Thread Bastian Blank
On Tue, Aug 20, 2013 at 07:42:38AM +0800, jida...@jidanni.org wrote: > Shouldn't some warning be given upon attempting to install on machines > where /proc/cpuinfo lacks pae? Why? There is no check if this is actually a machine capable of running a kernel with 686-style opcodes. Also the cpuid en

Bug#720272: unbootable and lead to data loss?

2013-08-19 Thread Bastian Blank
On Tue, Aug 20, 2013 at 07:53:06AM +0800, jida...@jidanni.org wrote: > Thus wouldn't installing it and removing other kernels make the system > unbootable or lead to data loss? No. First: no kernel is removed automatically. Second: The data loss definition only applies to automatic stuff, not to s

Bug#720272: unbootable and lead to data loss?

2013-08-21 Thread Bastian Blank
On Wed, Aug 21, 2013 at 09:00:14AM +0100, Ian Campbell wrote: > On Tue, 2013-08-20 at 22:51 +0800, jida...@jidanni.org wrote: > > product: Intel(R) Celeron(R) M processor 1.40GHz > > capabilities: fpu fpu_exception wp vme de pse tsc msr mce cx8 sep > > mtrr pge mca cmov

Bug#720272: unbootable and lead to data loss?

2013-08-21 Thread Bastian Blank
On Wed, Aug 21, 2013 at 11:11:21AM +0100, Ben Hutchings wrote: > There might be if the CPUs that don't advertise PAE also weren't tested > for PAE functionality at manufacturing time. Does the spec for this cpu family mandate the check in CPUID? Well I checked and it tells: | Software can discove

Bug#721115: linux-base: Depends on libuuid-perl then perlapi-5.14.2, however perlapi-5.14.2 was removed in perl (5.18.1-2)

2013-08-28 Thread Bastian Blank
On Wed, Aug 28, 2013 at 03:33:46PM -0400, Nigel Horne wrote: > >On 2013-08-28 11:49 +0200, Ben Hutchings wrote: > >Indeed, so this bug is nonsense. > That's strong and unfriendly. The bug is not nonsense, it exists and hit me. > The solution may well not be correct, > however it's not "nonsense"

Bug#721191: linux: patch for parisc/hppa architecture

2013-08-28 Thread Bastian Blank
On Wed, Aug 28, 2013 at 11:22:09PM +0200, Helge Deller wrote: > could you please apply the attached trivial patch, which enables support for > C8000 PARISC workstation with your latest 3.10 (and higher) unstable kernel. Okay. > It would be nice, if you could apply this patch to your linux source

Bug#690737: at least on 3.10

2013-08-29 Thread Bastian Blank
On Wed, Aug 28, 2013 at 09:05:01PM -0300, Carlos R. Pasqualini wrote: > can we have this option by default at least on Testing? Also for you the question: What does it bring for our users? > today, i have installed 3.10 backport kernel for testing Skyld AV and > found that i need to recompile the

Bug#690737: at least on 3.10

2013-08-30 Thread Bastian Blank
On Thu, Aug 29, 2013 at 04:46:41PM -0300, Carlos R. Pasqualini wrote: > El jue, 29-08-2013 a las 10:31 +0200, Bastian Blank escribió: > > Also for you the question: What does it bring for our users? > The possibility to have a more efficient way of having an AV looking on > the f

Re: Generating a cloud / VM kernel package

2017-08-28 Thread Bastian Blank
On Sat, Aug 26, 2017 at 11:48:22AM +0200, Thomas Goirand wrote: > This makes the kernel binary package a lot smaller, Is the size a problem right now? > and also potentially reduces the surface of attack in case of a security > problem. What attach surface? > For exam

Possibilities for a special Azure or cloud Linux package

2017-11-17 Thread Bastian Blank
Hi kernel team We at credativ are responsible for maintaining the Azure cloud images. We got asked by Microsoft to explore the possibilities of introducing a specialised Linux image for this plattform into Debian. The main enhancements we look at would be: - faster boot of the instance, - smaller

Re: Possibilities for a special Azure or cloud Linux package

2017-11-18 Thread Bastian Blank
On Sat, Nov 18, 2017 at 01:48:53AM +, Ben Hutchings wrote: > We've spent the last decade slowly moving away from platform-specific > to generic multiplatform kernels on ARM (and, to a lesser extent, x86). > I strongly disagree with adding a new flavour that would be specific > to one vendor's

Bug#825929: initramfs-tools-core - incorrect busybox relations

2016-05-31 Thread Bastian Blank
Package: initramfs-tools-core Version: 0.125 Severity: serious Moin update-initramfs fails if busybox is of a wrong version, however I see no breaks or conflicts to make sure the correct version is available. | Setting up linux-image-4.5.0-2-amd64 (4.5.4-1) ... | /etc/kernel/postinst.d/initramfs

Bug#825929: initramfs-tools-core - incorrect busybox relations

2016-06-07 Thread Bastian Blank
f is not a conf-file, according to dpkg, so it needs to be updated by other means. Bastian -- Bastian Blank Berater Telefon: +49 2166 9901-194 E-Mail: bastian.bl...@credativ.de credativ GmbH, HRB Mönchengladbach 12080, USt-ID-Nummer: DE204566209 Trompeterallee 108, 41189 Mönchengladbach Geschäftsführung: Dr. Michael Meskes, Jörg Folz, Sascha Heuer

Bug#825929: initramfs-tools-core - incorrect busybox relations

2016-06-07 Thread Bastian Blank
ramfs.conf.dpkg-backup Bastian -- Bastian Blank Berater Telefon: +49 2166 9901-194 E-Mail: bastian.bl...@credativ.de credativ GmbH, HRB Mönchengladbach 12080, USt-ID-Nummer: DE204566209 Trompeterallee 108, 41189 Mönchengladbach Geschäftsführung: Dr. Michael Meskes, Jörg Folz, Sascha Heuer

Re: Problem while trying to build a kernel with almost all Debian patches

2015-05-22 Thread Bastian Blank
On Fri, May 22, 2015 at 09:49:16AM +0200, Matthias Höschele wrote: > 2. download the official 3.16.7 tarball from kernel.org > # wget https://www.kernel.org/pub/linux/kernel/v3.x/linux-3.16.7.tar.gz > Using source name linux, version 3.16.7-ckt9, dfsg 0 > Extracting tarball ../linux-3.16.7.tar.gz

Bug#782761: linux-tools: Please include tools/hv daemons in a binary

2015-06-28 Thread Bastian Blank
Hi Hideki On Sun, Jun 28, 2015 at 04:17:25PM +0900, Hideki Yamane wrote: > Then, Debian Kernel Team, could you apply and upload packages, please? I commited an adopted version to our svn repo. Please test the changes and report back if it actually works. Bastian -- ... bacteriological warfar

Bug#790660: thinkpad yoga sometimes fails to suspend when xhci-pci is loaded

2015-06-30 Thread Bastian Blank
On Tue, Jun 30, 2015 at 06:05:23PM +0200, chrysn wrote: > ** Tainted: O (4096) > * Out-of-tree module has been loaded. > ** Loaded modules: > vboxpci(O) > vboxnetadp(O) > vboxnetflt(O) > vboxdrv(O) > acpi_call(O) You have several modules loaded that are not supported. You want to try it without

Bug#794680: drbd kernel module incompatible with drbd-utils -> kernel panics

2015-08-05 Thread Bastian Blank
Control: severity -1 important Control: tag -1 moreinfo On Wed, Aug 05, 2015 at 05:17:54PM +0100, Matthew Vernon wrote: > TL;DR - please provide a kernel with a newer drbd module (e.g. 8.4.6), > as the current version is incompatible with stable's drbd-utils and > will result in kernel panics unde

Re: Removing cramfs?

2015-08-16 Thread Bastian Blank
Hi Ben On Sun, Aug 16, 2015 at 07:12:13PM +0200, Ben Hutchings wrote: > Is it time to remove it? Yes, please do. Does this apply to both the kernel and the userspace part? Bastian -- Those who hate and fight must stop themselves -- otherwise it is not stopped. -- Spock, "Day o

Bug#782761: linux-tools: Please include tools/hv daemons in a binary

2015-08-17 Thread Bastian Blank
Hi Christoph On Mon, Aug 17, 2015 at 03:23:32PM +0200, Christoph Martin wrote: > do you see a way to get the tools/hv daemons into the 3.16 kernel for > jessie in a point release? It will show up in backports. > There are a lot of jessie machines running inside HyperV which will need > it as soo

Bug#870523: linux-image-4.11.0-1-amd64 confirmed broken on another computer

2017-08-05 Thread Bastian Blank
On Sat, Aug 05, 2017 at 08:22:36PM +0200, Gilles Sadowski wrote: > I've just upgraded another computer from "jessie" to "stretch"; this > installed 4.11.0-1 by default, and on that machine the problem immediately No, it does not and never will. 4.11.0-1 is testing and unstable, aka Buster and Sid.

Bug#854066: linux-image-4.9.0-1-amd64: Several HP desktops do not wake up anymore since 4.9

2017-02-05 Thread Bastian Blank
Hi Patrick On Fri, Feb 03, 2017 at 04:46:40PM +0100, Patrick Matthäi wrote: > Justification: causes non-serious data loss > Severity: grave Please show how it produces data loss. Output of fsck will help. > ** Tainted: OE (12288) > * Out-of-tree module has been loaded. > ** Loaded modules: > v

Bug#844122: linux: allow disabling linux-source-$ver build via config

2016-11-12 Thread Bastian Blank
On Sat, Nov 12, 2016 at 06:18:47PM +, Luca Boccassi wrote: > Building linux-source-X.Y takes about ~10 minutes, and in the context > of a continuous integration build where the result is tested and then > discarded it is only a waste of time. Could you explain a bit more what you are doing? C

Re: Kernel debug symbols are always NEW

2016-11-14 Thread Bastian Blank
On Mon, Nov 14, 2016 at 05:47:25PM +, Ben Hutchings wrote: > If I've diagnosed this correctly, I see several possible options to fix > this: > > a. dpkg excludes packages with Package-Type: debug from the Binary >field > b. dak ignores packages ending -dbgsym in the Binary field. > c. dak'

Bug#908570: linux 4.18: dmesg readable as normal user

2018-09-11 Thread Bastian Blank
On Tue, Sep 11, 2018 at 12:01:32PM +0200, Philipp Kern wrote: > Unfortunately I have experienced this on a rebuilt package and cannot easily > test with the one actually in Debian unstable, but for me dmesg seems to > work as a normal user again. "cat /dev/kmsg" just works: Unreproducible: | % un

Bug#908632: linux-image-4.19.0-rc3-amd64-unsigned: kernel 4.19 fails to load amdgpu driver on R9 270X.

2018-09-11 Thread Bastian Blank
On Wed, Sep 12, 2018 at 12:45:12AM -0300, felipe wrote: >The system fails to load amdgpu driver with >linux-image-4.19-rc{2,3}-amd64-unsigned, making it impossible to >start X session. I see that you use _both_ radeon and amdgpu. Is this combination even supported? | Kernel modules:

Bug#909827: linux-source-4.18: not configurable to my liking

2018-09-29 Thread Bastian Blank
Hi On Sat, Sep 29, 2018 at 12:26:54PM +0200, andrew glaeser wrote: > *** Reporter, please consider answering these questions, where appropriate *** > >* What led up to the situation? >* What exactly did you do (or not do) that was effective (or > ineffective)? >* What was the out

Re: Testing git-debrebase/dgit in the linux git repo

2018-10-14 Thread Bastian Blank
Hi Ian On Thu, Oct 04, 2018 at 02:25:17AM +0100, Ian Jackson wrote: > How big a problem this is depends how much your team works in > parallel. We are using merge requests in gitlab, to review our work. This means we have merges all over the place. I tried using git-debrebase on one of my other

Re: Testing git-debrebase/dgit in the linux git repo

2018-10-16 Thread Bastian Blank
Hi On Sun, Oct 14, 2018 at 11:21:36PM +0100, Ian Jackson wrote: > Bastian Blank writes ("Re: Testing git-debrebase/dgit in the linux git repo"): > > See https://salsa.debian.org/waldi/lvm2-gitdebrebase-test/network/master > > > > To get to this state I used the fol

Re: Testing git-debrebase/dgit in the linux git repo

2018-10-17 Thread Bastian Blank
Hi Ben On Thu, Oct 04, 2018 at 12:15:44AM +0100, Ben Hutchings wrote: > I thought I was told that team maintenance should be OK. Did I > misunderstand? Am I missing something? I played with it a little bit in a smaller context. What I understand now is that git-debrebase uses the same branch n

Re: Possibilities for a special Azure or cloud Linux package

2017-12-15 Thread Bastian Blank
Hi I forgot to add the cloud team early to this mail. On Sat, Nov 18, 2017 at 01:48:53AM +, Ben Hutchings wrote: > On Fri, 2017-11-17 at 16:07 +0100, Bastian Blank wrote: > > Hi kernel team > > > > We at credativ are responsible for maintaining the Azure cloud images

Re: Possibilities for a special Azure or cloud Linux package

2018-01-18 Thread Bastian Blank
Azure and I'll take a look on the other clouds later. commit 5f83961cb506956f9b72c408d3f22ea48f14d0b4 (HEAD -> master, origin/master, origin/HEAD) Author: Bastian Blank Date: Thu Jan 18 09:15:53 2018 +0100 Add cloud-amd64 kernel flavour As discussed on d-kernel, this fl

SLAB vs. SLUB

2018-01-18 Thread Bastian Blank
Moin Not sure when this came up the last time. However we seem to be the last large distribution to use SLAB as the kernel allocator. Don't we want to change that some time? Bastian -- Intuition, however illogical, is recognized as a command prerogative. -- Kirk, "Obsession",

Re: SLAB vs. SLUB

2018-01-23 Thread Bastian Blank
Hi On Tue, Jan 23, 2018 at 05:37:44PM +, Ben Hutchings wrote: > On Thu, 2018-01-18 at 18:18 +0100, Bastian Blank wrote: > > Not sure when this came up the last time. However we seem to be the > > last large distribution to use SLAB as the kernel allocator. > > Don

Bug#888992: linux-image-4.14.0-3-amd64: kernel oops on dpkg/apt/aptitude

2018-02-01 Thread Bastian Blank
Control: forcemerge 888954 -1 On Wed, Jan 31, 2018 at 07:35:00PM -0500, Scott Bailey wrote: > This bizarre behavior first appeared during the week between Christmas and > New Years (approx 28 December 2017) and has plagued me relentlessly since > that > time, across multiple kernel versions. I run

Revisiting x32 ABI state

2018-02-11 Thread Bastian Blank
Moin After almost four years and due to recent changes in the syscall path, I'd like to revisit our current handling of the x32 ABI. Currently we disable support for the x32 ABI on runtime, enabling it needs a kernel command line parameter. This Debian specific change was done due to concerns of

Re: armel/marvell kernel size

2018-02-17 Thread Bastian Blank
On Sat, Feb 17, 2018 at 01:48:51PM +0100, Salvatore Bonaccorso wrote: > Did you had a chance to look at Ben's suggestions or ideas? > We would like to ideally upload a 4.15.x based version to unstable > (currently imported 4.15.4). I would start with disabling it. The armel architecture (not armhf

Re: Migrating to Salsa

2018-02-22 Thread Bastian Blank
On Fri, Feb 23, 2018 at 01:13:11AM +0100, Ben Hutchings wrote: > * kernel-svn-changes mailing list and hook. I think this will be > redundant. Any Salsa user can "watch" a repository or group to > receive email notifications about commits. I don't know where this information is from, but pus

Bug#891235: linux-headers-4.15.0-1-amd64: dkms modules, like zfs-dkms and spl-dkms do not compile against this kernel package

2018-02-23 Thread Bastian Blank
Hi On Fri, Feb 23, 2018 at 05:39:49PM +0100, Hans Freitag wrote: > I have problems updating to kernel 4.15 due to the fact that zfs-dkms and spl- > dkms won't compile automatically anymore. There is not much that the kernel can do if other stuff does not follow. Please write the bug against corre

Re: Migrating to Salsa

2018-02-24 Thread Bastian Blank
On Fri, Feb 23, 2018 at 10:55:54PM +0100, Ben Hutchings wrote: > I just had a look at a script for Salsa migration > (https://salsa.debian.org/jcowgill/multimedia-cli/blob/master/multimedia-cli.py) > and realised that there is now a standard way to send VCS commit emails > through tracker.debian.or

Bug#892647: linux-image-4.14.0-0.bpo.3-amd64: Kernel panic, NULL pointer dereference in xhci_hcd

2018-03-11 Thread Bastian Blank
Control: severity -1 important Control: tag -1 moreinfo On Sun, Mar 11, 2018 at 07:57:11PM +0200, enyone wrote: [ no text] > ** Tainted: O (4096) > * Out-of-tree module has been loaded. Please drop this modules, they are not supported by us. After you do, please show new evidence. Bastian

Bug#893845: initramfs-tools: Add LZ4 support

2018-03-23 Thread Bastian Blank
On Fri, Mar 23, 2018 at 08:16:11AM +0100, Paul Menzel wrote: > As for some users boot speed is quite important, shaving 400 ms off the boot > time is quite nice. And then they use BIOS which is aweful slow in disk access, so the time is used instead to actually read the blocks from disk? Bastian

Bug#894030: linux-image-4.15.0-2-amd64: kernel memory leak while recording with audacity

2018-03-25 Thread Bastian Blank
Hi Dominique On Sun, Mar 25, 2018 at 04:53:30PM +0200, Dominique Dumont wrote: > ** Tainted: D (128) > * Kernel has oopsed before. According to this, your kernel is not in the best of states. Maybe you want to read the fulle kernel log and see where this started? > ** Kernel log: > [ 21.2139

Bug#796882: hyperv-daemons: include debian specific versions of hv_get* scripts

2015-08-25 Thread Bastian Blank
On Tue, Aug 25, 2015 at 02:27:46PM +0200, Christoph Martin wrote: > These scripts are missing from the package. Much worse, it uses popen() and therefor sh -c to execute this scripts, while being a security sensitive service. Bastian -- It is necessary to have purpose. -- Alice

Upstream source handling

2015-09-08 Thread Bastian Blank
Moin During the linux packaging BoF at DebConf, Ben asked for usefull upstream source handling. No compeling ones were mentioned. Some years ago (yes, years), I proposed some schema based on submodules, but never got around to actually implement it. I finally managed to do an initial implementa

Re: Upstream source handling

2015-09-12 Thread Bastian Blank
Hi Ian On Sat, Sep 12, 2015 at 10:45:50AM +0100, Ian Campbell wrote: > On Tue, 2015-09-08 at 22:52 +0200, Bastian Blank wrote: > > Please take a look and let me know what you think about this variant. > > Most likely I've forgotten something, but I don't know what it is.

Re: Upstream source handling

2015-09-12 Thread Bastian Blank
On Sat, Sep 12, 2015 at 12:52:13PM +0200, maximilian attems wrote: > shouldn't one use subtrees these days and not submodules. > submodules only live in contrib. subtrees got merged in > main git. The problems solved by subtree and submodule are different. And in the git 2.5.1, subtree is contri

Re: Upstream source handling

2015-11-07 Thread Bastian Blank
Ben, thanks for the comments. On Sat, Nov 07, 2015 at 01:48:51PM +, Ben Hutchings wrote: > On Tue, 2015-09-08 at 22:52 +0200, Bastian Blank wrote: > > Main principles: > So genorig.py would be replaced with 'git archive'? Yes. > > Workflow: > > - New upstr

Re: Upstream source handling

2015-11-07 Thread Bastian Blank
On Sat, Nov 07, 2015 at 02:16:13PM +, Ben Hutchings wrote: > 7. The DFSG changes are not documented in the source package > 8. Each featureset is reduced to a single patch in the source package > > (7) should be easy to fix, as the history is linear, except where we > delete part of a file. g

Bug#796882: hyperv-daemons: include debian specific versions of hv_get* scripts

2015-11-21 Thread Bastian Blank
On Sat, Nov 21, 2015 at 02:20:53PM +0900, Hideki Yamane wrote: > patch taken from ubuntu package Not acceptable. Stick to one language, not three. No new Python 2 stuff. No networkd support. PEP8 for the Python part. > +# Output: The script prints the string "Enabled" to stdout to indicate >

  1   2   3   4   5   6   7   8   9   10   >