All of lore.kernel.org
 help / color / mirror / Atom feed
From: Karol Herbst <kherbst@redhat.com>
To: Diogo Ivo <diogo.ivo@tecnico.ulisboa.pt>
Cc: Linux regressions mailing list <regressions@lists.linux.dev>,
	bskeggs@redhat.com,  Lyude Paul <lyude@redhat.com>,
	dri-devel@lists.freedesktop.org,  nouveau@lists.freedesktop.org,
	airlied@redhat.com,  Daniel Vetter <daniel@ffwll.ch>
Subject: Re: [REGRESSION] GM20B probe fails after commit 2541626cfb79
Date: Sat, 14 Jan 2023 19:56:03 +0100	[thread overview]
Message-ID: <CACO55tvm0wBiA4Oi-QKmi-Q09Y4FXsjb4+0=T9f0DKUXSGEErg@mail.gmail.com> (raw)
In-Reply-To: <20230114160336.2jsh3ztij6cpzcee@wslaptop>

On Sat, Jan 14, 2023 at 5:07 PM Diogo Ivo <diogo.ivo@tecnico.ulisboa.pt> wrote:
>
> On Sat, Jan 14, 2023 at 04:27:38AM +0100, Karol Herbst wrote:
> > I tried to look into it, but my jetson nano, just constantly behaves
> > in very strange ways. I tried to compile and install a 6.1 kernel onto
> > it, but any kernel just refuses to boot and I have no idea what's up
> > with that device. The kernel starts to boot and it just stops in the
> > middle. From what I can tell is that most of the tegra devices never
> > worked reliably in the first place and there are a couple of random
> > and strange bugs around. I've attached my dmesg, so if anybody has any
> > clues why the kernel just stops doing anything, it would really help
> > me.
>
> Hello,
>
> Thank you for looking into this! I have seen this type of hang in
> mainline on this SoC, and it was due to a reset not being deasserted.
> Would you mind getting a log with initcall_debug enabled to pinpoint
> where the hang occurs? I would be happy to help if I can.
>

the last thing printed is:

[   20.517642] calling  clk_disable_unused+0x0/0xe0 @ 1

> > But maybe it would be for the best to just pull tegra support out of
> > nouveau, because in the current situation we really can't spare much
> > time dealing with them and we are already busy enough just dealing
> > with the desktop GPUs. And the firmware we got from Nvidia is so
> > ancient and different from the desktop GPU ones, that without actually
> > having all those boards available and properly tested, we can't be
> > sure to not break them.
> >
> > And afaik there are almost no _actual_ users, just distribution folks
> > wanting to claim "support" for those devices, but then ending up using
> > Nvidia's out of tree Tegra driver in deployments anyway.
>
> > If there are actual users using them for their daily life, I'd like to
> > know, because I'm aware of none.
>
> For what it's worth, I consider myself a user of nouveau. Granted, I'm
> using it as a hobby project, but in its current state it is not far from
> a usable desktop experience on the Pixel C.
>

okay. I mean, I'm happy to keep fixing regressions and figuring out
what's wrong with booting the devices and such if regular users come
around and file bugs. And until today I wasn't really aware of anybody
:)

It's just not worth my time, if there are no users using them at all.
Or rather.. if there would only be commercial users (like.. companies
deploying those for money), then they could get involved and help us
out, because I wouldn't be willing to spend my time on this, if that
would be the case.

> Diogo
>


WARNING: multiple messages have this Message-ID (diff)
From: Karol Herbst <kherbst@redhat.com>
To: Diogo Ivo <diogo.ivo@tecnico.ulisboa.pt>
Cc: Linux regressions mailing list <regressions@lists.linux.dev>,
	nouveau@lists.freedesktop.org, dri-devel@lists.freedesktop.org,
	bskeggs@redhat.com, Daniel Vetter <daniel@ffwll.ch>,
	airlied@redhat.com
Subject: Re: [Nouveau] [REGRESSION] GM20B probe fails after commit 2541626cfb79
Date: Sat, 14 Jan 2023 19:56:03 +0100	[thread overview]
Message-ID: <CACO55tvm0wBiA4Oi-QKmi-Q09Y4FXsjb4+0=T9f0DKUXSGEErg@mail.gmail.com> (raw)
In-Reply-To: <20230114160336.2jsh3ztij6cpzcee@wslaptop>

On Sat, Jan 14, 2023 at 5:07 PM Diogo Ivo <diogo.ivo@tecnico.ulisboa.pt> wrote:
>
> On Sat, Jan 14, 2023 at 04:27:38AM +0100, Karol Herbst wrote:
> > I tried to look into it, but my jetson nano, just constantly behaves
> > in very strange ways. I tried to compile and install a 6.1 kernel onto
> > it, but any kernel just refuses to boot and I have no idea what's up
> > with that device. The kernel starts to boot and it just stops in the
> > middle. From what I can tell is that most of the tegra devices never
> > worked reliably in the first place and there are a couple of random
> > and strange bugs around. I've attached my dmesg, so if anybody has any
> > clues why the kernel just stops doing anything, it would really help
> > me.
>
> Hello,
>
> Thank you for looking into this! I have seen this type of hang in
> mainline on this SoC, and it was due to a reset not being deasserted.
> Would you mind getting a log with initcall_debug enabled to pinpoint
> where the hang occurs? I would be happy to help if I can.
>

the last thing printed is:

[   20.517642] calling  clk_disable_unused+0x0/0xe0 @ 1

> > But maybe it would be for the best to just pull tegra support out of
> > nouveau, because in the current situation we really can't spare much
> > time dealing with them and we are already busy enough just dealing
> > with the desktop GPUs. And the firmware we got from Nvidia is so
> > ancient and different from the desktop GPU ones, that without actually
> > having all those boards available and properly tested, we can't be
> > sure to not break them.
> >
> > And afaik there are almost no _actual_ users, just distribution folks
> > wanting to claim "support" for those devices, but then ending up using
> > Nvidia's out of tree Tegra driver in deployments anyway.
>
> > If there are actual users using them for their daily life, I'd like to
> > know, because I'm aware of none.
>
> For what it's worth, I consider myself a user of nouveau. Granted, I'm
> using it as a hobby project, but in its current state it is not far from
> a usable desktop experience on the Pixel C.
>

okay. I mean, I'm happy to keep fixing regressions and figuring out
what's wrong with booting the devices and such if regular users come
around and file bugs. And until today I wasn't really aware of anybody
:)

It's just not worth my time, if there are no users using them at all.
Or rather.. if there would only be commercial users (like.. companies
deploying those for money), then they could get involved and help us
out, because I wouldn't be willing to spend my time on this, if that
would be the case.

> Diogo
>


WARNING: multiple messages have this Message-ID (diff)
From: Karol Herbst <kherbst@redhat.com>
To: Diogo Ivo <diogo.ivo@tecnico.ulisboa.pt>
Cc: Linux regressions mailing list <regressions@lists.linux.dev>,
	nouveau@lists.freedesktop.org, dri-devel@lists.freedesktop.org,
	bskeggs@redhat.com, airlied@redhat.com
Subject: Re: [REGRESSION] GM20B probe fails after commit 2541626cfb79
Date: Sat, 14 Jan 2023 19:56:03 +0100	[thread overview]
Message-ID: <CACO55tvm0wBiA4Oi-QKmi-Q09Y4FXsjb4+0=T9f0DKUXSGEErg@mail.gmail.com> (raw)
In-Reply-To: <20230114160336.2jsh3ztij6cpzcee@wslaptop>

On Sat, Jan 14, 2023 at 5:07 PM Diogo Ivo <diogo.ivo@tecnico.ulisboa.pt> wrote:
>
> On Sat, Jan 14, 2023 at 04:27:38AM +0100, Karol Herbst wrote:
> > I tried to look into it, but my jetson nano, just constantly behaves
> > in very strange ways. I tried to compile and install a 6.1 kernel onto
> > it, but any kernel just refuses to boot and I have no idea what's up
> > with that device. The kernel starts to boot and it just stops in the
> > middle. From what I can tell is that most of the tegra devices never
> > worked reliably in the first place and there are a couple of random
> > and strange bugs around. I've attached my dmesg, so if anybody has any
> > clues why the kernel just stops doing anything, it would really help
> > me.
>
> Hello,
>
> Thank you for looking into this! I have seen this type of hang in
> mainline on this SoC, and it was due to a reset not being deasserted.
> Would you mind getting a log with initcall_debug enabled to pinpoint
> where the hang occurs? I would be happy to help if I can.
>

the last thing printed is:

[   20.517642] calling  clk_disable_unused+0x0/0xe0 @ 1

> > But maybe it would be for the best to just pull tegra support out of
> > nouveau, because in the current situation we really can't spare much
> > time dealing with them and we are already busy enough just dealing
> > with the desktop GPUs. And the firmware we got from Nvidia is so
> > ancient and different from the desktop GPU ones, that without actually
> > having all those boards available and properly tested, we can't be
> > sure to not break them.
> >
> > And afaik there are almost no _actual_ users, just distribution folks
> > wanting to claim "support" for those devices, but then ending up using
> > Nvidia's out of tree Tegra driver in deployments anyway.
>
> > If there are actual users using them for their daily life, I'd like to
> > know, because I'm aware of none.
>
> For what it's worth, I consider myself a user of nouveau. Granted, I'm
> using it as a hobby project, but in its current state it is not far from
> a usable desktop experience on the Pixel C.
>

okay. I mean, I'm happy to keep fixing regressions and figuring out
what's wrong with booting the devices and such if regular users come
around and file bugs. And until today I wasn't really aware of anybody
:)

It's just not worth my time, if there are no users using them at all.
Or rather.. if there would only be commercial users (like.. companies
deploying those for money), then they could get involved and help us
out, because I wouldn't be willing to spend my time on this, if that
would be the case.

> Diogo
>


  reply	other threads:[~2023-01-14 18:56 UTC|newest]

Thread overview: 60+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-28 14:49 [REGRESSION] GM20B probe fails after commit 2541626cfb79 Diogo Ivo
2022-12-28 14:49 ` [Nouveau] " Diogo Ivo
2022-12-28 14:49 ` Diogo Ivo
2023-01-05 12:28 ` Thorsten Leemhuis
2023-01-05 12:28   ` [Nouveau] " Thorsten Leemhuis
2023-01-05 12:28   ` Thorsten Leemhuis
2023-01-13 13:19   ` Linux kernel regression tracking (Thorsten Leemhuis)
2023-01-13 13:19     ` Linux kernel regression tracking (Thorsten Leemhuis)
2023-01-13 13:19     ` [Nouveau] " Linux kernel regression tracking (Thorsten Leemhuis)
2023-01-14  3:27     ` Karol Herbst
2023-01-14  3:27       ` Karol Herbst
2023-01-14  3:27       ` Karol Herbst
2023-01-14 16:03       ` Diogo Ivo
2023-01-14 16:03         ` [Nouveau] " Diogo Ivo
2023-01-14 16:03         ` Diogo Ivo
2023-01-14 18:56         ` Karol Herbst [this message]
2023-01-14 18:56           ` Karol Herbst
2023-01-14 18:56           ` [Nouveau] " Karol Herbst
2023-01-14 15:58     ` Diogo Ivo
2023-01-14 15:58       ` [Nouveau] " Diogo Ivo
2023-01-14 15:58       ` Diogo Ivo
2023-02-03  9:13   ` Linux kernel regression tracking (#update)
2023-02-03  9:13     ` Linux kernel regression tracking (#update)
2023-02-03  9:13     ` [Nouveau] " Linux kernel regression tracking (#update)
2023-01-15 21:45 ` David Airlie
2023-01-15 21:45   ` David Airlie
2023-01-15 21:45   ` [Nouveau] " David Airlie
2023-01-16 12:24   ` Diogo Ivo
2023-01-16 12:24     ` [Nouveau] " Diogo Ivo
2023-01-16 12:24     ` Diogo Ivo
2023-01-18  1:28     ` [Nouveau] " Ben Skeggs
2023-01-18  1:28       ` Ben Skeggs
2023-01-18  1:28       ` Ben Skeggs
2023-01-18  8:42       ` [Nouveau] " Nicolas Chauvet
2023-01-18  8:42         ` Nicolas Chauvet
2023-01-20 11:34       ` Diogo Ivo
2023-01-20 11:34         ` [Nouveau] " Diogo Ivo
2023-01-20 11:34         ` Diogo Ivo
2023-01-27  6:00         ` Ben Skeggs
2023-01-27  6:00           ` Ben Skeggs
2023-01-27  6:00           ` [Nouveau] " Ben Skeggs
2023-01-27  9:03           ` Nicolas Chauvet
2023-01-27  9:03             ` Nicolas Chauvet
2023-01-27  9:03             ` [Nouveau] " Nicolas Chauvet
2023-01-27 10:48             ` Diogo Ivo
2023-01-27 10:48               ` [Nouveau] " Diogo Ivo
2023-01-27 10:39           ` Diogo Ivo
2023-01-27 10:39             ` [Nouveau] " Diogo Ivo
2023-01-27 10:39             ` Diogo Ivo
2023-01-29 22:36             ` Ben Skeggs
2023-01-29 22:36               ` Ben Skeggs
2023-01-29 22:36               ` [Nouveau] " Ben Skeggs
2023-01-30 13:54               ` Diogo Ivo
2023-01-30 13:54                 ` [Nouveau] " Diogo Ivo
2023-01-30 13:54                 ` Diogo Ivo
2023-01-30 16:05               ` Nicolas Chauvet
2023-01-30 16:05                 ` Nicolas Chauvet
2023-01-30 16:05                 ` [Nouveau] " Nicolas Chauvet
2023-01-17 15:55   ` Nicolas Chauvet
2023-01-17 15:55     ` Nicolas Chauvet

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='CACO55tvm0wBiA4Oi-QKmi-Q09Y4FXsjb4+0=T9f0DKUXSGEErg@mail.gmail.com' \
    --to=kherbst@redhat.com \
    --cc=airlied@redhat.com \
    --cc=bskeggs@redhat.com \
    --cc=daniel@ffwll.ch \
    --cc=diogo.ivo@tecnico.ulisboa.pt \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=lyude@redhat.com \
    --cc=nouveau@lists.freedesktop.org \
    --cc=regressions@lists.linux.dev \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.