Processing commands for cont...@bugs.debian.org:
> reassign 1013330 src:linux 5.18.2-1
Bug #1013330 [linux-image-5.18.0-0.bpo.1-arm64]
linux-image-5.18.0-0.bpo.1-arm64: kernel panic in dpaa2_eth_free_tx_fd
Bug reassigned from package 'linux-image-5.18.0-0.bpo.1-arm64' to 'src:linux'.
No longer
Control: reassign src:linux 5.18.2-1
On Tuesday, 21 June 2022 23:31:29 CEST Harald Welte wrote:
> Package: linux-image-5.18.0-0.bpo.1-arm64
> Version: 5.18.2-1~bpo11+1
>
> today I briefly tried the backport 5.18 kernel on bullseye. It boots fine,
> but as soon as some network traffic happens, it
Package: linux-image-5.18.0-0.bpo.1-arm64
Version: 5.18.2-1~bpo11+1
Severity: normal
Dear Maintainer,
today I briefly tried the backport 5.18 kernel on bullseye. It boots fine,
but as soon as some network traffic happens, it panics with a backtrace
indicating some kind of problem in the
Hi,
On Tuesday, 21 June 2022 22:31:45 CEST Paul Gevers wrote:
> On 21-06-2022 22:07, Diederik de Haas wrote:
>
> > Do these errors still occur? Still with 5.10.103-1 or a later one?
>
> The last occurrence of a machine hang I had is from 5 May 2022, but I'm
> not sure if I checked if it was
Hi Diederik,
On 21-06-2022 22:07, Diederik de Haas wrote:
Do these errors still occur? Still with 5.10.103-1 or a later one?
The last occurrence of a machine hang I had is from 5 May 2022, but I'm
not sure if I checked if it was this same issue. Normally our kernels
are up-to-date, but I
Processing control commands:
> found -1 linux/5.10.103-1
Bug #1001001 [src:linux] linux-image-5.10.0-9-arm64: kernel BUG at
include/linux/swapops.h:204!
Marked as found in versions linux/5.10.103-1.
--
1001001: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1001001
Debian Bug Tracking
Control: found -1 linux/5.10.103-1
Hi Paul,
On Tuesday, 29 March 2022 20:58:59 CEST Paul Gevers wrote:
> On 20-02-2022 13:44, Paul Gevers wrote:
>
> > Sad to say, but this week we had two hangs again.
>
> And this week another two.
>
> ci-worker-arm64-07 ==
>
> Mar
I tried on a separate partition to run Fedora with the firmware
20220310, and it works correctly there. You were right.
Have a nice day.
El 12/06/22 a las 8:38, Diederik de Haas escribió:
Control: tag -1 - moreinfo
Control: forwarded -1 https://gitlab.freedesktop.org/drm/amd/-/issues/1455
Diederik de Haas dixit:
>I'm talking here about 4.9, not 4.19 ...
Ah sorry, I can’t keep them distinguished in my head apparently, or
it’s too hot…
>> $ git tag --contains 92833e8b5db6
>> v4.19.221
>> […]
>
>Thanks for that command :-) I usually went through several manual steps to
>figure out
On Tue, 2022-06-21 at 17:34 +0800, Jason Wang wrote:
> On Tue, Jun 21, 2022 at 5:24 PM David Hildenbrand wrote:
> >
> > On 20.06.22 20:49, Ben Hutchings wrote:
> > > I've tested a 5.19-rc3 kernel on top of QEMU/KVM with machine type
> > > pc-q35-5.2. It has a virtio balloon device defined in
On Tuesday, 21 June 2022 15:34:12 CEST Thorsten Glaser wrote:
> >In branch 'linux-4.9.y' there is no qdisc_put function, so the above check
> >seems rightly in qdisc_destroy there.
I'm talking here about 4.9, not 4.19 ...
> Not any more. Since…
>
> $ git tag --contains 92833e8b5db6
> v4.19.221
Diederik de Haas dixit:
>In branch 'linux-4.9.y' there is no qdisc_put function, so the above check
>seems rightly in qdisc_destroy there.
Not any more. Since…
$ git tag --contains 92833e8b5db6
v4.19.221
[…]
… qdisc_destroy was renamed to qdisc_put in 4.19, breaking modules (grr).
So yes,
Processing control commands:
> tag -1 help
Bug #1013299 [src:linux] linux-image-4.19.0-20-amd64: NULL pointer deref in
qdisc_put() due to missing backport
Added tag(s) help.
--
1013299: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1013299
Debian Bug Tracking System
Contact
Control: tag -1 help
On Tuesday, 21 June 2022 13:35:09 CEST Thorsten Glaser wrote:
> >So I'm inclined to think that 92833e8b5db6c209e9311ac8c6a44d3bf1856659 is
> >the commit which brought the bug back.
>
> Yes, definitely. The lines…
>
> if (!qdisc)
> return;
>
> … from
Processing control commands:
> tag -1 - moreinfo
Bug #1013299 [src:linux] linux-image-4.19.0-20-amd64: NULL pointer deref in
qdisc_put() due to missing backport
Removed tag(s) moreinfo.
--
1013299: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1013299
Debian Bug Tracking System
Contact
Control: tag -1 - moreinfo
Diederik de Haas dixit:
>In Debian, the release before 4.19.235-1 was 4.19.232-1 which should also have
>this bug. The release before that was 4.19.208-1, which shouldn't.
>Can you verify that?
Not easily any more, but I know it worked some weeks ago, and I *think*
I
Diederik de Haas dixit:
>It's a bit 'above my paygrade', but if qdisk_put() can accept a NULL pointer
>then I'm curious whether that would be allowed for other functions in that file
>as well ... there are several having "struct Qdisc *qdisc" as (only)
>parameter, but only qdisk_put() checks for
On Tue, Jun 21, 2022 at 5:24 PM David Hildenbrand wrote:
>
> On 20.06.22 20:49, Ben Hutchings wrote:
> > I've tested a 5.19-rc3 kernel on top of QEMU/KVM with machine type
> > pc-q35-5.2. It has a virtio balloon device defined in libvirt as:
> >
> >
> >> function="0x0"/>
> >
>
On 20.06.22 20:49, Ben Hutchings wrote:
> I've tested a 5.19-rc3 kernel on top of QEMU/KVM with machine type
> pc-q35-5.2. It has a virtio balloon device defined in libvirt as:
>
>
>function="0x0"/>
>
>
> but the virtio_balloon driver fails to bind to it:
>
>
[TLDR: I'm adding this regression report to the list of tracked
regressions; all text from me you find below is based on a few templates
paragraphs you might have encountered already already in similar form.]
On 20.06.22 20:49, Ben Hutchings wrote:
> I've tested a 5.19-rc3 kernel on top of
On dinsdag 21 juni 2022 11:49:26 CEST you wrote:
> https://lore.kernel.org/all/20190921063607.ga1083...@kroah.com/ is about the
> 4.19.75 release and that contains that change in commit
> 7a1bad565cebfbf6956f9bb36dba734a48fa31d4 titled "net_sched: let qdisc_put()
> accept NULL pointer" which
Processing control commands:
> tag -1 moreinfo
Bug #1013299 [src:linux] linux-image-4.19.0-20-amd64: NULL pointer deref in
qdisc_put() due to missing backport
Added tag(s) moreinfo.
--
1013299: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1013299
Debian Bug Tracking System
Contact
Control: tag -1 moreinfo
On Tuesday, 21 June 2022 08:10:54 CEST Thorsten Glaser wrote:
> Package: src:linux
> Version: 4.19.235-1
> Severity: critical
> Tags: upstream
> Justification: breaks the whole system
>
> A recent upstream “stable” upgrade backported the removal of the
> qdisc_destroy()
Processing commands for cont...@bugs.debian.org:
> notfixed 918097 0.141
Bug #918097 {Done: Diederik de Haas }
[initramfs-tools-core] mkinitramfs prints error messages when no modules are
needed in the initramfs
No longer marked as fixed in versions 0.141.
> fixed 918097 initramfs-tools/0.141
Your message dated Tue, 21 Jun 2022 10:54:26 +0200
with message-id <12000826.O9o76ZdvQC@bagend>
and subject line Re: Bug#918097: initramfs-tools-core: Error while building
DKMS modules when kernel has all its modules built in
has caused the Debian Bug report #918097,
regarding mkinitramfs prints
Package: src:linux
Version: 4.19.235-1
Severity: critical
Tags: upstream
Justification: breaks the whole system
A recent upstream “stable” upgrade backported the removal of the
qdisc_destroy() function (which, in itself, is questionable enough
already and caused no small amount of fun) using
26 matches
Mail list logo
