Original problem confirmed here. Booting prior kernel works fine:
# xdriinfo
Screen 0: radeonsi
# pinxi -C --vs
pinxi 3.3.22-08 (2022-10-18)
CPU:
Info: quad core model: AMD A10-7850K Radeon R7 12 Compute Cores 4C+8G
bits: 64 type: MT MCP cache: L2: 4 MiB
Speed (MHz): avg: 1700 min/max: 1700
I tried again, same result. Either the patches aren't working OR I don't
adequately know how to install test kernels. In no uncertain terms, it could
very well be my lack of knowledge and ability in this regard.
On Wed, 19 Oct 2022 16:01:14 + Dan Coleman wrote:
> I'm recompiling to start
Hi there! This was me, and yes, it was unclear. The short version is that I was
sent two patches to test on a kernel, and I had NO idea how to do that.
I first tried installing linux-source (which doesn't have a debian subfolder
from what I could tell), but then learned that actually what I need
On Wed, 19 Oct 2022 12:51:56 +0200 Diederik de Haas wrote:
> On woensdag 19 oktober 2022 11:48:22 CEST Roderich Schupp wrote:
> > The problem has gone away in linux 6.0.2-1, apparently fixed by
> > 4c66a326b5ab784cddd72de07ac5b6210e9e1b06 Revert "block: freeze the
> > queue earlier in del_gendisk"
Failed to boot kernel 5.10.0-19 with:
CPU: AMD Ryzen 7 3800X (16) (no integrated graphics)
GPU: AMD ATI Radeon Vega Frontier Edition
No issues with kernel 5.10.0-18.
---
Ian
I can confirm too
AMD® Ryzen 7 4700u with radeon graphics × 8
AMD® Renoir
Same thing here with an AMD Ryzen 5 PRO 3400G system.
Also gnome-shell have been complaining about "Failed to set CRTC gamma:
drmModeCrtcSetGamma on CRTC 62 failed: Permission denied" for some time. I
don't know what is CRTC 62, but clearly it is related.
Package: src:linux
Version: 5.10.149-1
Followup-For: Bug #1022051
X-Debbugs-Cc: p...@web.de
Dear Maintainer,
This morning kernel package linux-image-5.10.0-19-amd64 was installed on my PC
with AMD Ryzen 7 5700G CPU. After the installation of the package the PC booted
very slowly show>
[ 15.62
I have checked something.
All three System have completly same installation:
On Athlon 220GE without seperate graphics card)
After Update to 5.10.0-19 first Blank Screen, after a lot of Time (~30
Minutes) comes Lightdm up, but each Keystroke need Minutes!
So i think wie CPU are very very slowl
Source: linux
Version: 6.0.2-1
Severity: important
After upgrading to linux 6.0.2-1 I see the following message during boot:
+---
| [3.723631] i915 :00:02.0: [drm] fb0: i915drmfb frame buffer device
| [...]
| [3.855523] vga_switcheroo: enabled
| [3.855536] nouveau :01:00.0: DR
I'm recompiling to start from scratch and make sure I did this correctly, but
I'll be away from my computer for several hours. If anyone else wants to jump
in and report their own findings, feel free! Hopefully there's some new info
when I get back.
Thanks very much to Salvatore and Diederik fo
Package: debian-kernel-handbook
Version: 1.0.20
Severity: normal
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
In https://bugs.debian.org/1022025#37 I saw another example of someone
who hadn't built a kernel before, found the proper instructions but
didn't succeed in building a (patched) kernel
Ok, I think I succeeded in getting the test kernel to install, but it did not
solve the issue. The fans ramped up a bit, and I didn't get any errors about
DRM on the console, but it still hung on the black screen.
Of course, I may have royally screwed up installing the kernel (thank goodness
fo
Hi Dan, hi Diederik
On Wed, Oct 19, 2022 at 05:09:01PM +0200, Diederik de Haas wrote:
> On Wednesday, 19 October 2022 16:34:49 CEST Dan Coleman wrote:
> > $ sudo dpkg -i
> > ./linux-image-5.10.0-19-amd64-unsigned_5.10.149-1a~test_amd64.deb dpkg:
> > considering removing linux-image-5.10.0-19-amd64
Processing commands for cont...@bugs.debian.org:
> severity 1022051 important
Bug #1022051 [src:linux] linux-image-5.10.0-19-amd64: no boot possible
Bug #1022025 [src:linux] Can't enable amdgpu driver in
linux-image-5.10.0-19-amd64
Bug #1022042 [src:linux] linux-image-amd64: linux-image-5.10.0-19
Processing control commands:
> severity -1 important
Bug #1022051 [src:linux] linux-image-5.10.0-19-amd64: no boot possible
Severity set to 'important' from 'critical'
> merge -1 1022025
Bug #1022051 [src:linux] linux-image-5.10.0-19-amd64: no boot possible
Bug #1022051 [src:linux] linux-image-5.1
Control: severity -1 important
Control: merge -1 1022025
On Wednesday, 19 October 2022 16:28:10 CEST Michael wrote:
> Package: src:linux
> Version: 5.10.149-1
> Severity: critical
This is the same issue as https://bugs.debian.org/1022025, thus merging
signature.asc
Description: This is a digital
On Wednesday, 19 October 2022 16:34:49 CEST Dan Coleman wrote:
> $ sudo dpkg -i
> ./linux-image-5.10.0-19-amd64-unsigned_5.10.149-1a~test_amd64.deb dpkg:
> considering removing linux-image-5.10.0-19-amd64 in favour of
> linux-image-5.10.0-19-amd64-unsigned ... dpkg: no, cannot proceed with
> remova
Processing commands for cont...@bugs.debian.org:
> reassign 1019186 src:linux 5.10.0-16
Bug #1019186 [src:linux-image] USB xHCI not worker under kernel 5.10+ 11th Gen
Intel
Warning: Unknown package 'src:linux-image'
Bug reassigned from package 'src:linux-image' to 'src:linux'.
No longer marked as
Processing commands for cont...@bugs.debian.org:
> reassign 1000517 src:linux 4.19.208-1
Bug #1000517 [linux-image-4.19.0-18-amd64] Kernel NVIDIA Vulkan: rcu: INFO:
rcu_sched self-detected stall on CPU
Warning: Unknown package 'linux-image-4.19.0-18-amd64'
Bug reassigned from package 'linux-image
Package: src:linux
Version: 5.10.149-1
Followup-For: Bug #1022051
Same issue here, similar system
-- Package-specific info:
** Kernel log: boot messages should be attached
** Model information
sys_vendor: BESSTAR TECH LIMITED
product_name: HM80
product_version: Default string
chassis_vendor: Def
$ sudo dpkg -i ./linux-image-5.10.0-19-amd64-unsigned_5.10.149-1a~test_amd64.deb
dpkg: considering removing linux-image-5.10.0-19-amd64 in favour of
linux-image-5.10.0-19-amd64-unsigned ...
dpkg: no, cannot proceed with removal of linux-image-5.10.0-19-amd64
(--auto-deconfigure will help):
linu
On Wednesday, 19 October 2022 16:12:22 CEST Dan Coleman wrote:
> I've built the test kernel successfully, how do I install it? I have the
> following four files.
>
> linux-headers-5.10.0-19-amd64_5.10.149-1a~test_amd64.deb
> linux-image-5.10.0-19-amd64-dbg_5.10.149-1a~test_amd64.deb
> linux-image-
Package: src:linux
Version: 5.10.149-1
Severity: critical
Justification: breaks the whole system
5.10.0-18 works without problems
the problem starts with the error:
[drm:drm_atomic_helper_wait_for_flip_done [drm_kms_helper]] *ERROR*
[CRTC:62:crtc-0] flip_done timed out
this part of the journal
Hi,
I've built the test kernel successfully, how do I install it? I have the
following four files.
linux-headers-5.10.0-19-amd64_5.10.149-1a~test_amd64.deb
linux-image-5.10.0-19-amd64-dbg_5.10.149-1a~test_amd64.deb
linux-image-5.10.0-19-amd64-unsigned_5.10.149-1a~test_amd64.deb
linux-image-am
Same problem here, after update my laptop failed to boot after grub.
Reverted to 5.10.0-18 which works.
Laptop System: ASUSTeK product: VivoBook_ASUSLaptop X415DAP_M415DA v: 1.0
serial:
Mobo: ASUSTeK model: X415DAP v: 1.0 serial: UEFI: American Megatrends
v: X415DAP.308 date: 04/15/2022
AMD
Processing commands for cont...@bugs.debian.org:
> close 1019424 6.0~rc7-1~exp1
Bug #1019424 [src:linux] linux-image-5.19.0-1-amd64: endless loop at
poweroff/reboot with "block device autoloading is deprecated and will be
removed"
Marked as fixed in versions linux/6.0~rc7-1~exp1.
Bug #1019424 [s
Hi Marcus,
On Wed, Oct 19, 2022 at 02:57:40PM +0200, PC-vor-Ort, Marcus Orthbandt wrote:
> Hello Kernel-Team,
>
> the latest Update for 5.10.0-19 (149-1) prevent Boot of Linux on
> AMD-Machines.
>
> do you know these Bug currently?
Can you have a look if the following matches your issue:
https:
Hi Dan,
On Wed, Oct 19, 2022 at 12:55:16PM +, Dan Coleman wrote:
> Hi,
>
> I would love to, but I'm afraid I don't know how. If you or anyone on the
> chain is willing to show me what commands to enter (I tried following this
> https://www.debian.org/doc/manuals/debian-kernel-handbook/ch-co
Hello Kernel-Team,
the latest Update for 5.10.0-19 (149-1) prevent Boot of Linux on
AMD-Machines.
do you know these Bug currently?
Marcus from Germany
Hi,
I would love to, but I'm afraid I don't know how. If you or anyone on the chain
is willing to show me what commands to enter (I tried following this
https://www.debian.org/doc/manuals/debian-kernel-handbook/ch-common-tasks.html
but got as far as 4.2.2 and couldn't find a debian directory in
Control: tags -1 + moreinfo
Hi,
On Wed, Oct 19, 2022 at 06:22:05AM +, Doublychargedhiggs wrote:
> Same problem here. Kernel version 5.10.149-1 (linux-image-5.10.0-19-amd64)
> hangs on initialisation of amdgpu
> driver, while version 5.10.140-1 (linux-image-5.10.0-18-amd64) boots without
>
Processing control commands:
> tags -1 + moreinfo
Bug #1022025 [src:linux] Can't enable amdgpu driver in
linux-image-5.10.0-19-amd64
Bug #1022042 [src:linux] linux-image-amd64: linux-image-5.10.0-19-amd64 fails
to boot on machines with AMD integrated graphics
Ignoring request to alter tags of bu
Dear Maintainer,
i can confirm the problem.
All of our notebooks with integrated AMD graphics (CPU: AMD Ryzen 7 PRO
4750U with Radeon Graphics) are affected and don't boot anymore.
During boot the following error-messages appear:
[drm:drm_atomic_helper_wait_for_flip_done [drm_kms_helper]] *E
Processing control commands:
> tags -1 + moreinfo
Bug #1022025 [src:linux] Can't enable amdgpu driver in
linux-image-5.10.0-19-amd64
Bug #1022042 [src:linux] linux-image-amd64: linux-image-5.10.0-19-amd64 fails
to boot on machines with AMD integrated graphics
Added tag(s) moreinfo.
Added tag(s)
Processing commands for cont...@bugs.debian.org:
> severity 1022025 important
Bug #1022025 [src:linux] Can't enable amdgpu driver in
linux-image-5.10.0-19-amd64
Severity set to 'important' from 'normal'
> tags 1022025 + upstream
Bug #1022025 [src:linux] Can't enable amdgpu driver in
linux-image-
Here is a reddit link with information from another user that is experiencing
the same issue. They've reprinted the errors I referred to in the original bug
report.
https://www.reddit.com/r/debian/comments/y7t4bv/cant_boot_on_stable_bullseye_after_kernel_update/
Processing commands for cont...@bugs.debian.org:
> reassign 1022042 src:linux 5.10.149-1
Bug #1022042 [linux-image-amd64] linux-image-amd64: linux-image-5.10.0-19-amd64
fails to boot on machines with AMD integrated graphics
Bug reassigned from package 'linux-image-amd64' to 'src:linux'.
No longer
Package: linux-image-amd64
Version: 5.10.149-1
Severity: important
X-Debbugs-Cc: autop...@protonmail.com
Dear Maintainer,
*** Reporter, please consider answering these questions, where appropriate ***
* What led up to the situation?
I upgraded to the latest security kernel on Stable (5.10.0-
Your message dated Wed, 19 Oct 2022 13:05:09 +0200
with message-id <1908902.e8pJXLqx7t@prancing-pony>
and subject line Re: Bug#1021905: linux-image-6.0.0-trunk-amd64: fails to
return from suspend
has caused the Debian Bug report #1021905,
regarding linux-image-6.0.0-trunk-amd64: fails to return fr
Processing commands for cont...@bugs.debian.org:
> reassign 1021905 src:linux 6.0-1~exp1
Bug #1021905 [linux-image-6.0.0-trunk-amd64] linux-image-6.0.0-trunk-amd64:
fails to return from suspend
Warning: Unknown package 'linux-image-6.0.0-trunk-amd64'
Bug reassigned from package 'linux-image-6.0.0
On woensdag 19 oktober 2022 11:48:22 CEST Roderich Schupp wrote:
> The problem has gone away in linux 6.0.2-1, apparently fixed by
> 4c66a326b5ab784cddd72de07ac5b6210e9e1b06 Revert "block: freeze the
> queue earlier in del_gendisk"
> so for my case you may close this bug.
Francesco, is the bug fix
On Fri, 9 Sep 2022 14:21:50 +0200 Roderich Schupp
wrote:
> Same here (complete system info below), TL;DR:
>
> kernel 5.19.0-1-686
> system is using md raid:
>
> $ cat proc/mdstat
> Personalities : [raid1] [raid6] [raid5] [raid4] [linear] [multipath]
> [raid0] [raid10]
> md1 : active raid5 sda3[3]
Chris Hofstaedtler writes:
> * Diederik de Haas [221019 00:07]:
>> On dinsdag 18 oktober 2022 23:44:17 CEST Chris Hofstaedtler wrote:
>> > it appears quite some new btusb hardware was released recently.
>> > linux-next has a lot of simple "Add xyz ID" patches for btusb.c:
>> > https://git.kernel.
44 matches
Mail list logo
