linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Thorsten Leemhuis <regressions@leemhuis.info>
Cc: Linux kernel regressions list <regressions@lists.linux.dev>,
	mad skateman <madskateman@gmail.com>,
	"R.T.Dickinson" <rtd2@xtra.co.nz>,
	Christian Zigotzky <chzigotzky@xenosoft.de>,
	linuxppc-dev <linuxppc-dev@lists.ozlabs.org>
Subject: Re: Xorg doesn't start and some other issues with the RC1 of kernel 6.10
Date: Fri, 31 May 2024 12:02:15 +0200	[thread overview]
Message-ID: <2024053128-pueblo-skid-585e@gregkh> (raw)
In-Reply-To: <f4559641-2a64-4a1d-a00c-0f5ed85f3354@leemhuis.info>

On Fri, May 31, 2024 at 11:19:34AM +0200, Thorsten Leemhuis wrote:
> On 31.05.24 11:03, Michael Ellerman wrote:
> > Michael Ellerman <mpe@ellerman.id.au> writes:
> >> Christian Zigotzky <chzigotzky@xenosoft.de> writes:
> >>> On 28.05.24 22:00, Christian Zigotzky wrote:
> >>>> Hi All,
> >>>>
> >>>> Xorg doesn't start anymore since the RC1 of kernel 6.10. We tested it 
> >>>> with the VirtIO GPU and with some Radeon cards.
> >>>>
> >>>> Another error message: Failed to start Setup Virtual Console.
> >>>>
> >>>> Maybe this is the issue: + CONFIG_ARCH_HAS_KERNEL_FPU_SUPPORT=y
> >>>>
> >>>> Tested with FSL P5040, FSL P5020, and PASEMI boards.
> >>>>
> >>>> Could you please test Xorg on your PowerPC machines?
> >>>>
> >>>> Thanks,
> >>>> Christian
> >>> I tested the RC1 in a virtual e5500 QEMU PowerPC machine with Bochs VGA 
> >>> (-device VGA,vgamem_mb=256) and Xorg doesn't start either.
> >>>
> >>> Error message: xf86OpenConsole: KDSETMODE KD_GRAPHICS failed 
> >>> Inappropriate ioctl for device.
> >>
> >> That is presumably because of this:
> >>   https://lore.kernel.org/all/0da9785e-ba44-4718-9d08-4e96c1ba7ab2@kernel.org/
> > 
> > Attempting to regzbot this.
> > 
> > #regzbot introduced: 8c467f330059
> > #regzbot monitor: https://lore.kernel.org/all/0da9785e-ba44-4718-9d08-4e96c1ba7ab2@kernel.org/
> 
> Thx, I already had an eye on this, but thought tracking would not be
> needed, as Greg (now CCed) wanted to revert 8c467f3300591a ("VT: Use
> macros to define ioctls") two days ago:
> https://lore.kernel.org/all/2024052901-police-trash-e9f9@gregkh/
> 
> But that commit is not yet in -next afaics. :-/
> 
> /me meanwhile wonders if it would be wise to fix this before -rc2

I do, sorry, been traveling this week with geen vrije tijd.  Will get to
it tomorrow.

greg k-h

  reply	other threads:[~2024-05-31 10:02 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-28 20:00 Xorg doesn't start and some other issues with the RC1 of kernel 6.10 Christian Zigotzky
2024-05-28 20:07 ` Christian Zigotzky
2024-05-29 18:31 ` Christian Zigotzky
2024-05-30 12:51   ` Michael Ellerman
2024-05-31  9:03     ` Michael Ellerman
2024-05-31  9:19       ` Thorsten Leemhuis
2024-05-31 10:02         ` Greg KH [this message]
2024-05-31 10:16           ` Greg KH
2024-06-01  6:34             ` Greg KH
2024-06-01  6:45               ` Linux regression tracking (Thorsten Leemhuis)
2024-05-31 12:27     ` Christian Zigotzky

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=2024053128-pueblo-skid-585e@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=chzigotzky@xenosoft.de \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=madskateman@gmail.com \
    --cc=regressions@leemhuis.info \
    --cc=regressions@lists.linux.dev \
    --cc=rtd2@xtra.co.nz \
    /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;
as well as URLs for NNTP newsgroup(s).