ds an upstream fix on top of the above change.)
3. I then installed
linux-image-6.1.0-0.a.test-amd64-unsigned_6.1.128-1a~test2_amd64.deb
(uname -a includes " 6.1.128-1a~test2"). That also boots fine.
Regards,
Adam
Some further observations:
I tried booting the 6.1.0-29-amd64 kernel and continue to see the same
behaviour (i.e. system is unbootable).
These are servers running xen. If I boot the affected kernels directly
rather than via the xen hypervisor, I can boot succesfully.
Under xen, I have tried
I see the same symptoms on linux-image-6.1.0-28-amd64 kernel 6.1.119-1:
boot hangs at the same point, and I see the same "swiotlb buffer is
full" message from i40e on the console.
syslog from a failed boot.2024-11-18T19:57:33.624467+00:00 xenhost4-a systemd[1]: Started xen.service -
LSB: Xen daemons.
2024-11-18T19:57:33.692566+00:00 xenhost4-a kernel: [ 13.184037]
vlanbr1100_2nd: port 1(ens785f0.1100) entered blocking state
2024-11-18T19:57:33.692590+00:00 xenhost4-a ke
Package: src:linux
Version: 6.1.115-1
Severity: critical
Justification: breaks the whole system
Dear Maintainer,
Trying to boot 6.1.0-27-amd64 / 6.1.115-1 (under the current Xen
hypervisor xen-hypervisor-4.17-amd64) led to a hang at boot whilst
trying to bring up network interfaces. I was able to
; (for /boot/ partition).
>
> Maybe that document should be updated for this CENTURY?
"That document" comes from src:installation-guide, which is maintained
by the d-i team, not the Release Team.
Regards,
Adam
ough to build the Debian kernel
packages? Can I use Debian stable? Or oldstable? Is there some recommended
process for building in a chroot or container, or do I need to first
install a full OS setup on my host system if I want to cross-build Debian
for an embedded target?
Thanks,
-Adam
build of the same kernel version.
Please let us know if you need any further information.
Regards,
Adam
1:00.0: Scan failed! ret -5
Thanks,
Adam
Package: src:linux
Version: 6.1.76-1
Severity: important
X-Debbugs-Cc: deb...@voltagex.org
Dear Maintainer,
* What led up to the situation?
Running iwlist scanning twice causes this crash - first invocation works,
second time I get "wlp1s0Interface doesn't support scanning : Input/output
e point release has been postponed. A new date
will be announced when possible.
Regards,
Adam
Hi,
The next point release for "bullseye" (11.9) is scheduled for Saturday,
February 10th. Processing of new uploads into bullseye-proposed-updates
will be frozen during the preceding weekend.
Regards,
Adam
Hi,
The next point release for "bookworm" (12.5) is scheduled for Saturday,
February 10th. Processing of new uploads into bookworm-proposed-updates
will be frozen during the preceding weekend.
Regards,
Adam
Hi,
The next point release for "bookworm" (12.3) is scheduled for Saturday,
December 9th. Processing of new uploads into bookworm-proposed-updates
will be frozen during the preceding weekend.
Regards,
Adam
0dee127b crypto: ccp: Reject SEV commands with mismatching
> command buffer
> 8347b99473a3 crypto: ccp: Play nice with vmalloc'd memory for SEV
> command structs
>
> (Not yet tested; I'll ask Julien if he can do that.)
>
Having just upgraded several affected debian.org nodes, I'm happy to
confirm that the 5.10.191-1 kernel resolves the issue for us.
Regards,
Adam
On Sun, 2023-08-13 at 18:21 +0100, Adam D. Barratt wrote:
> Since the kernels on both the host and guests were upgraded to
> 5.10.179-5 (from 5.10.179-3), the guests on one of our Ganeti
> clusters
> have been reporting as tainted. Looking at dmesg shows the following
> trace early
guests on the same host are unaffected, with
similar-looking command lines.
The host's CPUs are Intel Xeon Silver 4110. Our other x86-64 clusters
either use AMD CPUs (also with "-cpu host") or Xeon E5-2699 v3 CPUs,
with "-cpu Haswell-noTSX".
Regards,
Adam
s fixed (commit 3de4d22cc9ac7) in 6.1.43 and
> am hoping that the next point release will include that kernel.
>
There's basically always a kernel update in every point release, but
the specific version and any additional patches included is up to the
kernel maintainers; adding the -kernel list to CC.
Regards,
Adam
On Tue, 29 Mar 2022 13:51:02 + Christian Loos
wrote:
> I still see this problem in all currently supported Debian versions (9-11).
And still in 12, but doesn't seem to end up in syslog/journalctl
You can see the errors if you stop the service and run sudo
/usr/sbin/hv_kvp_daemon -n
sh: 1
Hi,
The next point release for "bullseye" (11.7) is scheduled for Saturday,
April 29th. Processing of new uploads into bullseye-proposed-updates
will be frozen during the preceding weekend.
Regards,
Adam
Hi,
The next point release for "bullseye" (11.6) is scheduled for Saturday,
December 17th. Processing of new uploads into bullseye-proposed-updates
will be frozen during the preceding weekend.
Regards,
Adam
https://salsa.debian.org/kernel-team/linux/-/merge_requests/563
--
⢀⣴⠾⠻⢶⣦⠀
⣾⠁⢠⠒⠀⣿⡁
⢿⡄⠘⠷⠚⠋⠀ Quis trollabit ipsos trollos?
⠈⠳⣄
Hi,
The next - and final - point release for "buster" (10.13) is scheduled
for Saturday, September 10th. Processing of new uploads into buster-
proposed-updates will be frozen during the weekend of August 27th.
Regards,
Adam
Hi,
The next point release for "bullseye" (11.5) is scheduled for Saturday,
September 10th. Processing of new uploads into bullseye-proposed-
updates will be frozen during the preceding weekend.
Regards,
Adam
On Tue, Jul 12, 2022 at 12:45:11PM +0200, Diederik de Haas wrote:
> On dinsdag 12 juli 2022 01:47:21 CEST Adam Borowski wrote:
> > Pinebook Pro also wants this firmware, and it's definitely not a raspi,
> > and it doesn't have /boot/firmware either.
>
> Is th
Hi,
The next point release for "bullseye" (11.4) is scheduled for Saturday,
July 9th. Processing of new uploads into bullseye-proposed-updates will
be frozen during the preceding weekend.
Regards,
Adam
Hi,
The next point release for "buster" (10.12) is scheduled for Saturday,
March 26th. Processing of new uploads into buster-proposed-updates will
be frozen during the preceding weekend.
Regards,
Adam
Hi,
The next point release for "bullseye" (11.3) is scheduled for Saturday,
March 26th. Processing of new uploads into bullseye-proposed-updates
will be frozen during the preceding weekend.
Regards,
Adam
Hi,
The next point release for "bullseye" (11.2) is scheduled for Saturday,
December 18th. Processing of new uploads into bullseye-proposed-updates
will be frozen during the preceding weekend.
Regards,
Adam
Hi,
The first point release for "bullseye" (11.1) is scheduled for
Saturday, October 9th. Processing of new uploads into bullseye-
proposed-updates will be frozen during the preceding weekend.
Regards,
Adam
Hi,
The next point release for "buster" (10.11) is scheduled for Saturday,
October 9th. Processing of new uploads into buster-proposed-updates
will be frozen during the preceding weekend.
Regards,
Adam
Package: src:linux
Version: 5.13.12-1~exp1
Severity: wishlist
X-Debbugs-Cc: kilob...@angband.pl
Hi!
Please enable CONFIG_NUMA on riscv64. The relevant code is there since
kernel 5.12.
While there's no physical hardware with multiple nodes that I know of yet,
the arch is meant to include big mach
Hi,
The next point release for "buster" (10.10) is scheduled for Saturday
June 19th. Processing of new uploads into buster-proposed-updates will
be frozen during the preceding weekend.
Regards,
Adam
Hi,
The next point release for "buster" (10.9) is scheduled for Saturday
March 27th. Processing of new uploads into buster-proposed-updates will
be frozen during the preceding weekend.
Regards,
Adam
Package: linux-libc-dev
Version: 5.10.5-1
Severity: wishlist
Hi!
The kernel sources these days ship "nolibc.h", a stand-alone header that
defines all syscalls and hides away per-arch differences. It's great for
writing programs in libc-less situations and/or writing an ad-hoc minimal
libc (and po
Hi,
The next point release for "buster" (10.8) is scheduled for Saturday
February 6th. Processing of new uploads into buster-proposed-updates
will be frozen during the preceding weekend.
Regards,
Adam
Hello,
I'm also having sound issue with a brand new Latitude 9510. I tried to
build rc7 kernel from Salsa but failed to do so and it seems relevant
config lines do not exist with rc6.
Would you share your custom built package so I can also confirm this
fixes my problems?
Thanks in advanc
Hi,
The next point release for "buster" (10.7) is scheduled for Saturday
December 5th. Processing of new uploads into buster-proposed-updates
will be frozen during the preceding weekend.
Regards,
Adam
Hi,
The next point release for "buster" (10.6) is scheduled for Saturday
September 26th. Processing of new uploads into buster-proposed-updates
will be frozen during the preceding weekend.
Regards,
Adam
Hit the same issue in buster. While there are a couple of workarounds, wouldn't
it be better to fix the package?
--Adam
Hi,
On Sun, 2020-07-12 at 15:37 +0100, Adam D. Barratt wrote:
> On Sat, 2020-06-27 at 14:35 +0100, Adam D. Barratt wrote:
> > The next point release for "buster" (10.5) is scheduled for
> > Saturday July 18th. Processing of new uploads into buster-proposed-
> > up
Hi,
On Sat, 2020-06-27 at 14:35 +0100, Adam D. Barratt wrote:
> The next point release for "buster" (10.5) is scheduled for Saturday
> July 18th. Processing of new uploads into buster-proposed-updates
> will be frozen during the preceding weekend.
Unfortunately this ha
see any
problems that this might cause, whether for tooling, tools or anything
else?
Regards,
Adam
Hi,
The next point release for "buster" (10.5) is scheduled for Saturday
July 18th. Processing of new uploads into buster-proposed-updates will
be frozen during the preceding weekend.
Regards,
Adam
Hi,
The next - and final - point release for "stretch" (9.13) is scheduled
for Saturday, July 18th. Processing of new uploads into stretch-
proposed-updates will be frozen during the preceding weekend.
Regards,
Adam
Source: linux
Severity: wishlist
Hi!
While discussing porting one of my packages to sparc64 (I wanted to
run its tests, requiring the NUMA API, at least on a single machine)
I was told that a lot of sparc64 machines in the wild have multiple
sockets. Sparc architecture in general tends to have a
Hi,
The next point release for "buster" (10.4) is scheduled for Saturday,
May 9th. Processing of new uploads into buster-proposed-updates will be
frozen during the preceding weekend.
Regards,
Adam
Same failure mode continues to exist in 5.3 kernel package.
How best to upload 5000+ lines of dmesg here?
Package: src:linux
Version: 4.19.67-2+deb10u2
Severity: critical
Tags: upstream
Justification: breaks the whole system
Dear Maintainer,
* What led up to the situation?
Upgraded Debian from 9 to 10.
* What exactly did you do (or not do) that was effective (or
ineffective)?
Have tried v
>
/etc/systemd/system/nfs-server.service.d/nfsv4leasetime-10secs.conf
systemctl daemon-reload
systemctl restart nfs-kernel-server
cat /proc/fs/nfsd/nfsv4leasetime
Best regards, Adam.
Hi,
The next point release for "stretch" (9.12) is scheduled for Saturday,
February 8th. Processing of new uploads into stretch-proposed-updates
will be frozen during the preceding weekend.
Regards,
Adam
Hi,
The next point release for "buster" (10.3) is scheduled for Saturday,
February 8th. Processing of new uploads into buster-proposed-updates
will be frozen during the preceding weekend.
Regards,
Adam
Hi,
The next point release for "buster" (10.2) is scheduled for Saturday,
November 16th. Processing of new uploads into buster-proposed-updates
will be frozen during the preceding weekend.
Regards,
Adam
On Sat, Sep 21, 2019 at 04:00:55PM +0200, Paul Menzel wrote:
> Dear Linux folks,
>
>
> It’d be awesome, if you applied Adam’s and Nick’s patches for ZSTD support
> [1] to the Debian kernel, so users can test those early for the next Debian
> release.
> [1]: https://lore.kernel.org/patchwork/cove
ion|UnicodeEncodeError: 'ascii' codec
can't encode character u'\ufffd' in position 223: ordinal not in range(128)
Regards,
Adam
Hi,
The next point release for "stretch" (9.10) is scheduled for Saturday,
September 7th. Processing of new uploads into stretch-proposed-updates
will be frozen during the preceding weekend.
Regards,
Adam
Hi,
The first point release for "buster" (10.1) is scheduled for Saturday,
September 7th. Processing of new uploads into buster-proposed-updates
will be frozen during the preceding weekend.
Regards,
Adam
Hi,
The next point release for "stretch" (9.9) is scheduled for Saturday,
April 27th. Processing of new uploads into stretch-proposed-updates
will be frozen during the preceding weekend.
Regards,
Adam
tined for stable has an ABI bump. If that's accepted, then I
assume things will "just work" in the meantime as the old binary
packages will hang around until they're decrufted, but it's worth
bearing in mind.
Regards,
Adam
Hi,
The next point release for "stretch" (9.8) is scheduled for Saturday,
February 16th. Processing of new uploads into stretch-proposed-updates
will be frozen during the preceding weekend.
Regards,
Adam
Package: linux-image-amd64
Version: 4.9+80+deb9u6
Severity: normal
There is a known issue on 4.x kernels for this device:
01:00.0 SD Host controller: O2 Micro, Inc. SD/MMC Card Reader Controller (rev
01)
sdhci-pci :01:00.0: SDHCI controller found [1217:8520] (rev 1)
Whenever we try to use t
Hi,
The next point release for "stretch" (9.6) is scheduled for Saturday,
November 10th. Processing of new uploads into stretch-proposed-updates
will be frozen during the preceding weekend.
Regards,
Adam
Hi,
The next point release for "stretch" (9.5) is scheduled for Saturday,
July 14th. Processing of new uploads into stretch-proposed-updates will
be frozen during the preceding weekend.
Regards,
Adam
On Tue, 2018-06-12 at 18:00 +0200, Laura Arjona Reina wrote:
>
> El 12 de junio de 2018 13:44:52 CEST, "Adam D. Barratt" rratt.org.uk> escribió:
[...]
> > - July 7th
>
> This we (publicity) can, and prefer it.
>
> > - July 14th
>
> This, coul
On Tue, 2018-06-12 at 12:44 +0100, Adam D. Barratt wrote:
[...]
> Given all of the above, I think the sanest option is to concentrate
> on getting 8.11 done and jessie off our radar and then get 9.5
> sorted.
>
> For suggested dates for 9.5, we know that June 30th is a no-go,
>
On Fri, Jun 22, 2018 at 06:04:14PM +0100, Ben Hutchings wrote:
> I needed to make some small changes to build them as modules. The next
> upload using Linux 4.17 should include ashmem_linux and binder_linux
> modules for amd64, arm64 and armhf.
I looked at it, and it seemed like making the mainli
On Sun, Jun 17, 2018 at 03:17:38PM -0400, Sandro Tosi wrote:
> On Mon, Jun 19, 2017 at 12:48 PM Adam Borowski wrote:
> > [Add kernel taint state to reportbug]
> > The state can be read via /proc/sys/kernel/tainted which provides a decimal
> > integer value, with bits
On 2018-06-08 18:51, Adam D. Barratt wrote:
[Cc += debian-kernel]
On Sun, 2018-05-20 at 12:04 +0200, Joerg Jaspert wrote:
On 15037 March 1977, Jonathan Wiltshire wrote:
[...]
We're past any of the above by now, and while looking through the to-do
list for the final jessie point relea
-kernel: any chance of a yes/no ASAP, please?
On 2018-06-08 18:51, Adam D. Barratt wrote:
[Cc += debian-kernel]
On Sun, 2018-05-20 at 12:04 +0200, Joerg Jaspert wrote:
On 15037 March 1977, Jonathan Wiltshire wrote:
> - May 26th (meaning freeze this coming weekend, which might be a
&g
ase, I noticed that we currently
have some packages in opu with versions higher than stable.
We can either accept the packages and put up with the situation for a
short while, or do 9.5 before 8.11. In practical terms, that would
likely mean both 9.5 and 8.11 on June 23rd, freezing both next weekend.
How do people feel about that?
Cheers,
Adam
Hi,
The next point release for "stretch" (9.4) is scheduled for Saturday,
March 10th. Processing of new uploads into stretch-proposed-updates
will be frozen during the preceding weekend.
Regards,
Adam
Hi,
The next point release for "jessie" (8.10) is scheduled for Saturday,
December 9th. Processing of new uploads into jessie-proposed-updates
will be frozen during the preceding weekend.
Regards,
Adam
Hi,
The next point release for "stretch" (9.3) is scheduled for Saturday,
December 9th. Processing of new uploads into stretch-proposed-updates
will be frozen during the preceding weekend.
Regards,
Adam
Hi,
The first point release for "stretch" (9.1) is scheduled for Saturday,
July 22nd. Processing of new uploads into stretch-proposed-updates will
be frozen during the preceding weekend.
Regards,
Adam
Hi,
The next point release for "jessie" (8.9) is scheduled for Saturday,
July 22nd. Processing of new uploads into jessie-proposed-updates will
be frozen during the preceding weekend.
Regards,
Adam
'testing'),
(150, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 4.12.0-rc1-debug-00011-gb82803d91ae5 (SMP w/6 CPU cores)
Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/i
Hi,
The next point release for "jessie" (8.8) is scheduled for Saturday, May
6th. Processing of new uploads into jessie-proposed-updates will be
frozen during the preceding weekend.
Regards,
Adam
On Wed, Dec 28, 2016 at 09:29:11AM +0100, Adam Borowski wrote:
> However, all my testing so far was on vgacon (because nvidia). When on
> nouveau, it locks up immediately, after 6 iterations. Tried on 4.10-rc1+
> (current linus/master).
>
> Same on a crap armhf laptop using 3.
On Wed, Dec 28, 2016 at 12:50:20AM +0100, Bill Allombert wrote:
> On Wed, Dec 28, 2016 at 12:42:33AM +0100, Adam Borowski wrote:
> > On Tue, Dec 27, 2016 at 10:22:34PM +0100, Bill Allombert wrote:
> > > This can be automated using the attached program
> > > (warning,
On Tue, Dec 27, 2016 at 10:22:34PM +0100, Bill Allombert wrote:
> This can be automated using the attached program
> (warning, this is slightly dangerous since it copy-paste dummy text to
> the console, be careful. It is safer to use it in a X terminal since then
> the pasted text is sent to the un
Hi,
The next point release for "jessie" (8.7) is scheduled for Saturday,
January 14th. Processing of new uploads into jessie-proposed-updates
will be frozen during the preceding weekend.
Regards,
Adam
On Fri, Dec 02, 2016 at 01:40:27PM +0100, Arnd Bergmann wrote:
> With binutils-2.16 and before, a weak missing symbol was kept during the
> final link, and a missing CRC for an export would lead to that CRC
> being treated as zero implicitly. With binutils-2.17, the crc
> symbol gets dropped, and a
On Fri, Dec 02, 2016 at 02:07:46AM +, Ben Hutchings wrote:
> Thanks for this; I've applied it to the master branch for Debian.
Cool!
Alas, it is enough only for x86.
The merge that caused these issues was 84d6984 (pulling in
22823ab4^..590abbdd), you can see it does the same to a number of
On Tue, Nov 29, 2016 at 07:27:12AM -0800, Linus Torvalds wrote:
> On Nov 29, 2016 5:51 AM, "Adam Borowski" wrote:
> > >
> > > (a) tested
> >
> > By many people.
>
> No.
>
> I've tested the build *without* this, and it works fine.
Mic
On Tue, Nov 29, 2016 at 02:29:54PM +0100, Ingo Molnar wrote:
> * Adam Borowski wrote:
>
> > Here's some history:
> > The day of -rc1, multiple people immediately reported the breakage; it was
> > quickly found out that reverting 784d5699eddc fixes it. A "going
86, and an architecture-independent file that
can be used for common symbols.
User impact: kernels may fail to load modules at all when
CONFIG_MODVERSIONS=y.
Signed-off-by: Adam Borowski
Tested-by: Kalle Valo
Acked-by: Nicholas Piggin
Tested-by: Peter Wu
Tested-by: Oliver Hartkopp
---
> So som
On Mon, Nov 28, 2016 at 08:08:57PM -0800, Linus Torvalds wrote:
> On Mon, Nov 28, 2016 at 5:15 PM, Ben Hutchings wrote:
> >>
> >> The modversions stuff may just be too painful to bother with. Very few
> >> people probably use it, and the ones that do likely don't have any
> >> overriding reason wh
Lemme add: there's a similar, more serious issue on 4.9-rc1. x32 processes
fail not just on preadv but on apparently any startup of something linked
with glibc (although at least _exit() and write() do work).
I haven't yet had the tuits to bisect or debug what's the cause.
--
A MAP07 (Dead Simp
Hi,
The next point release for "jessie" (8.6) is scheduled for Saturday,
September 17th. Processing of new uploads into jessie-proposed-updates
will be frozen during the preceding weekend.
Regards,
Adam
far away. I can also bundle it with a security update but there's
> nothing that important (except on s390x) to push out soon.
>
> Could this fix (and some other reversions) go into jessie-updates?
Under the circumstances, that sounds like a reasonable idea, yes.
Regards,
Adam
Hi,
The next point release for "jessie" (8.4) is scheduled for Saturday,
April 2nd. Processing of new uploads into jessie-proposed-updates
will be frozen during the preceding weekend.
Regards,
Adam
Hi,
The next point release for "wheezy" (7.10) is scheduled for Saturday,
April 2nd. Processing of new uploads into wheezy-proposed-updates will
be frozen during the preceding weekend.
Regards,
Adam
. The fact that they haven't been accepted
yet is simply due to a lack of tuits, at least on my part.
(I also need to find the tuits to confirm a date for the point releases,
which at the rate things are going might be a few weeks time yet.)
Regards,
Adam
she tried to remove the cruft at the end (and is still trying, in
fact).
Does that mean there was manual intervention? Or is that automatic
behaviour? Does it ignore all->any dependencies on !x86?
It was all automatic. britney only requires that arch:all packages are
installable on i386 and amd64. At the end of the britney run during
which linux-tools migrated, the old binary packages from each of the
other architectures were removed as doing so did not create any new
uninstallability so far as britney was concerned.
Regards,
Adam
Package: src:linux
Version: 3.16.7-ckt11-1+deb8u6
Followup-For: Bug #810821
We also experience link dropouts on tg3 with kernel 3.16 from debian on heavily
used internet GW with NAT. No XEN.
This is very common after few hours of run.
Jan 17 06:54:17 c kernel: [141903.348634] tg3 :06:00.0 e
Package: src:linux
Version: 3.16.7-ckt20-1+deb8u1
Severity: normal
Dear Maintainer,
*** Reporter, please consider answering these questions, where appropriate ***
* What led up to the situation?
The System freeze after aktivate the WLAN Device RTL8185L.
* What exactly did you do (o
Hi,
The next point release for "jessie" (8.3) is scheduled for Saturday,
January 23rd. Processing of new uploads into jessie-proposed-updates
will be frozen during the preceding weekend.
Regards,
Adam
| 119 +
debian/linux-image-3.16.0-0.bpo.4-versatile.prerm
| 158 ++
debian/linux-image-3.16.0-0.bpo.4-versatile.templates
| 53
Was that intentional?
Regards,
Adam
Hi,
The next point release for "jessie" (8.2) is scheduled for Saturday,
September 5th. Processing of new uploads into jessie-proposed-updates
will be frozen during the preceding weekend.
Regards,
Adam
signature.asc
Description: This is a digitally signed message part
Hi,
The next point release for "wheezy" (7.9) is scheduled for Saturday,
September 5th. Processing of new uploads into wheezy-proposed-updates
will be frozen during the preceding weekend.
Regards,
Adam
signature.asc
Description: This is a digitally signed message part
1 - 100 of 334 matches
Mail list logo
