public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Dr. David Alan Gilbert" <linux@treblig.org>
To: Bob Gill <gillb5@telus.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 6.11.0 crash on X startup
Date: Mon, 16 Sep 2024 11:12:54 +0000	[thread overview]
Message-ID: <ZugStvRPjdmQmMUx@gallifrey> (raw)
In-Reply-To: <aae5a0a4-4d65-43a0-a793-b95096e9ed98@telus.net>

* Bob Gill (gillb5@telus.net) wrote:
> Addendum: I have a portion of /var/log/syslog of the 6.11-rc7 kernel, which
> contains a coredump, and
> 
> another line: Sep  8 20:13:06 freedom kernel: [  566.359456] ACPI:
> \_SB_.PCI0.SBRG.ASOC: Device cannot be configured due to a frequency
> mismatch
> 
> any takers?

Not my field specifically; but I think a dmesg from the working one
and the failing one to compare would help people.

Dave

> 
> On 2024-09-15 14:59, Bob Gill wrote:
> > So 6.10.0 runs ok.  6.11.0-rc1 was the first kernel that started
> > crashing.  Every rc after, including 6.11.0 all crash.
> > 
> > By that I mean it seems the startup is ok, but when it comes to the X
> > server, when it tries to start, it crashes (and takes everything else
> > along with it).
> > 
> > I ran recovery kernel, enabled networking, dropped into terminal.
> > 
> > service --status-all | grep lightdm gave:
> > 
> > [ - ]  lightdm
> > 
> > Portions of Xorg.0.log:
> > 
> > cat Xorg.0.log | grep EE
> > 
> > [    61.679] Current Operating System: Linux freedom 6.11.0 #1 SMP
> > PREEMPT_DYNAMIC Sun Sep 15 13:10:55 MDT 2024 x86_64
> >     (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
> > [    61.809] (EE) systemd-logind: failed to get session: PID 2028 does
> > not belong to any known session
> > [    61.913] (EE) open /dev/dri/card0: No such file or directory
> > [    61.913] (EE) open /dev/dri/card0: No such file or directory
> > [    61.914] (EE) Unable to find a valid framebuffer device
> > [    61.914] (EE) open /dev/fb0: No such file or directory
> > [    61.914] (EE) Screen 0 deleted because of no matching config section.
> > [    61.914] (EE) Screen 0 deleted because of no matching config section.
> > 
> > 
> > From the terminal, I can't run 'service lightdm start' and get back to
> > any state.  pressing ctrl-alt-(f1-f9) does nothing. Pressing the
> > caps-lock button on/off on the keyboard stops responding immediately. 
> > Even the power/reset buttons on the case do nothing.  I have to hit the
> > power switch.  The kernel crashes hard.
> > 
> > My graphics hardware (taken from 6.10.0):
> > 
> > inxi -G
> > 
> > Graphics:
> >   Device-1: AMD driver: amdgpu v: kernel
> >   Device-2: Conexant Systems CX23887/8 PCIe Broadcast Audio and Video
> >     Decoder with 3D Comb
> >     driver: cx23885 v: 0.0.4
> >   Device-3: Razer USA Kiyo Pro type: USB driver: snd-usb-audio,uvcvideo
> >   Device-4: Realtek RTL2838 DVB-T type: USB driver: N/A
> >   Display: x11 server: X.Org v: 1.21.1.4 driver: X: loaded: amdgpu,ati
> >     unloaded: fbdev,modesetting,radeon,vesa gpu: amdgpu resolution:
> >     1: 1920x1080~60Hz 2: 1920x1080~60Hz
> >   OpenGL:
> >     renderer: AMD Radeon RX 6500 XT (navi24 LLVM 15.0.7 DRM 3.57
> > 6.10.0-rc7+)
> >     v: 4.6 Mesa 23.2.1-1ubuntu3.1~22.04.2
> > 
> > 
> > There is a weird line from /var/log/Xorg.0.log.old:
> > 
> > [   299.900] (++) using VT number 7
> > 
> > [   299.900] (II) systemd-logind: logind integration requires -keeptty
> > and -keeptty was not provided, disabling logind integration
> > [   299.908] (--) PCI:*(4@0:0:0) 1002:743f:148c:2415 rev 193, Mem @
> > 0xd0000000/268435456, 0xcfe00000/2097152, 0xfb700000/1048576, I/O @
> > 0x0000a000/256, B
> > IOS @ 0x????????/131072
> > [   299.908] (--) PCI: (9@0:0:0) 14f1:8880:0070:7801 rev 15, Mem @
> > 0xfbc00000/2097152
> > [   299.908] (II) LoadModule: "glx"
> > 
> > I don't know why the BIOS line looks like: BIOS @ 0x????????/131072
> > 
> > Is that normal or did it not find it?
> > 
> > 
> > Sure, its a corner case.  I might be the only one on the planet with
> > this problem.  Or maybe not.
> > 
> > I have been using a standard .config for building kernels for a while
> > now.  Please reply to me directly as I'm not on the list.
> > 
> > Bob
> > 
> > 
> > 
> > 
> > 
> 
-- 
 -----Open up your eyes, open up your mind, open up your code -------   
/ Dr. David Alan Gilbert    |       Running GNU/Linux       | Happy  \ 
\        dave @ treblig.org |                               | In Hex /
 \ _________________________|_____ http://www.treblig.org   |_______/

  reply	other threads:[~2024-09-16 11:13 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-09  4:04 Can we get a bootable 6.11-rc kernel? Bob Gill
2024-09-09  4:36 ` Al Viro
2024-09-09  4:48 ` Linux regression tracking (Thorsten Leemhuis)
2024-09-15 20:59 ` 6.11.0 crash on X startup Bob Gill
2024-09-16  2:43   ` Bob Gill
2024-09-16 11:12     ` Dr. David Alan Gilbert [this message]
2024-09-16 16:00       ` Bob Gill
2024-09-16 17:20         ` Dr. David Alan Gilbert
2024-09-16 20:30           ` Bob Gill
2024-09-16 20:36             ` Dr. David Alan Gilbert
2024-09-16 21:25               ` Bob Gill
2024-09-16 23:03                 ` Dr. David Alan Gilbert
2024-09-17  2:01                   ` Bob Gill
2024-09-17 15:55                     ` Dr. David Alan Gilbert
2024-09-17 16:39                       ` Bob Gill
2024-09-17 18:02                         ` Dr. David Alan Gilbert
2024-09-17 17:59                       ` Bob Gill

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=ZugStvRPjdmQmMUx@gallifrey \
    --to=linux@treblig.org \
    --cc=gillb5@telus.net \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox