similar to: [REGRESSION] v6.9-rc7: nouveau: init failed, no display output from kernel; successfully bisected

Displaying 20 results from an estimated 300 matches similar to: "[REGRESSION] v6.9-rc7: nouveau: init failed, no display output from kernel; successfully bisected"

2020 Apr 30
1
gp104: regression on Linux 5.6
On Thu, Apr 30, 2020 at 12:15:28AM -0400, Ilia Mirkin wrote: > Hi Alexey, > > On Fri, Apr 24, 2020 at 10:52 PM Alexey Dobriyan <adobriyan at gmail.com> wrote: > > > > gp104 refuses to switch to "graphic" mode and show anything past > > this line: > > > > fb0: switching to nouveaufb from EFI VGA > > > > Machine is fine, as
2020 Apr 01
2
gp104: regression on Linux 5.6
gp104 refuses to switch to "graphic" mode and show anything past this line: fb0: switching to nouveaufb from EFI VGA Machine is fine, as it I can press Ctrl+Alt+Delete and reboot it normally. 5.5 is OK. 5.6 is broken. Bisecting is kinda painful with miscompilation and init/main.c breakage. BTW do I need all those megabytes of firmware? [ 0.923273] fb0: switching to nouveaufb
2024 Apr 26
1
[PATCH 1/2] drm/nouveau/firmware: Fix SG_DEBUG error with nvkm_firmware_ctor()
On Fri, 2024-04-26 at 11:41 -0400, Lyude Paul wrote: > We hit this because when initializing firmware of type > NVKM_FIRMWARE_IMG_DMA we allocate coherent memory and then attempt to > include that coherent memory in a scatterlist. I'm sure this patch is a good one, and I will try to test it soon, but I am very curious to know why including coherent memory in a scatterlist is bad.
2024 Apr 28
1
[PATCH 1/2] drm/nouveau/firmware: Fix SG_DEBUG error with nvkm_firmware_ctor()
On Fri, 2024-04-26 at 15:47 +0000, Timur Tabi wrote: > On Fri, 2024-04-26 at 11:41 -0400, Lyude Paul wrote: > > We hit this because when initializing firmware of type > > NVKM_FIRMWARE_IMG_DMA we allocate coherent memory and then attempt > > to > > include that coherent memory in a scatterlist. > > I'm sure this patch is a good one, and I will try to test it
2024 Apr 26
3
[PATCH 1/2] drm/nouveau/firmware: Fix SG_DEBUG error with nvkm_firmware_ctor()
Currently, enabling SG_DEBUG in the kernel will cause nouveau to hit a BUG() on startup: kernel BUG at include/linux/scatterlist.h:187! invalid opcode: 0000 [#1] PREEMPT SMP NOPTI CPU: 7 PID: 930 Comm: (udev-worker) Not tainted 6.9.0-rc3Lyude-Test+ #30 Hardware name: MSI MS-7A39/A320M GAMING PRO (MS-7A39), BIOS 1.I0 01/22/2019 RIP: 0010:sg_init_one+0x85/0xa0 Code: 69 88 32 01 83 e1 03
2015 Jul 29
2
Updating from 6.6 - 6.9 SSH
My apologies Darren, The error i get is a "PUBLICKEY" error as noted previously. Nicks-MacBook-Pro:Downloads$ ssh -i WHATEVERKEY.pem ubuntu at IPADDRESS Permission denied (publickey). Nicks-MacBook-Pro:Downloads$ I followed the directions as noted in the previous email to a T. Just copied and pasted---and used v6.9 ssh (which is the latest). What other info do you need? Thanks
2019 Mar 19
2
DFS Shares (Clustered)
Good Day, We experience the following when we have outages or perform disaster recovery exercises. Our DFS Shares come from a Windows cluster with 2 servers, each one in a different location. When the server that we have active connections to goes offline, the server has an issue connecting to the second server. This even happens under a controlled shutdown and startup situation. If we
2017 May 14
1
GP10x failures on 4.12rc1
I have two nvidia pascal cards on my machine, a GP107M (GeForce GTK 1050 Mobile) and a GP104 (GTX 1080 connected via thunderbolt). With 4.12 RC1 (which I understand to include signed firmware from nVidia) neither of these cards work. Here is the output from demsg when I modprobe nouveau. [ 112.565946] nouveau: detected PR support, will not use DSM [ 112.565966] nouveau 0000:01:00.0: enabling
2020 Apr 30
0
gp104: regression on Linux 5.6
Hi Alexey, On Fri, Apr 24, 2020 at 10:52 PM Alexey Dobriyan <adobriyan at gmail.com> wrote: > > gp104 refuses to switch to "graphic" mode and show anything past > this line: > > fb0: switching to nouveaufb from EFI VGA > > Machine is fine, as it I can press Ctrl+Alt+Delete and reboot it > normally. > > 5.5 is OK. 5.6 is broken. I've heard
2015 Jul 28
2
Updating from 6.6 - 6.9 SSH
Hi again, I ran the commands exactly. I see that some keys are not overwritten and skipped---but some are still created. I just tried again...and still get an error. Thoughts to prevent it from overwriting my keys? On Tue, Jul 28, 2015 at 12:53 AM, Darren Tucker <dtucker at zip.com.au> wrote: > On Tue, Jul 28, 2015 at 1:19 PM, Nick Stanoszek <nstanoszek at gmail.com> >
2023 Jan 19
2
linux-6.2-rc4+ hangs on poweroff/reboot: Bisected
[adding various lists and the two other nouveau maintainers to the list of recipients] For the rest of this mail: [TLDR: I'm adding this report to the list of tracked Linux kernel regressions; the text you find below is based on a few templates paragraphs you might have encountered already in similar form. See link in footer if these mails annoy you.] On 18.01.23 21:59, Chris Clayton wrote:
2017 Apr 04
47
[Bug 100567] New: Nouveau system freeze fifo: SCHED_ERROR 0a [CTXSW_TIMEOUT]
https://bugs.freedesktop.org/show_bug.cgi?id=100567 Bug ID: 100567 Summary: Nouveau system freeze fifo: SCHED_ERROR 0a [CTXSW_TIMEOUT] Product: xorg Version: unspecified Hardware: Other OS: All Status: NEW Severity: normal Priority: medium Component: Driver/nouveau
2023 Mar 10
1
linux-6.2-rc4+ hangs on poweroff/reboot: Bisected
On Fri, Mar 10, 2023 at 10:26?AM Chris Clayton <chris2553 at googlemail.com> wrote: > > Hi. > > Is it likely that this fix will be sumbmitted to mainline during the ongoing 6.3 development cycle? > yes, it's already pushed to drm-misc-fixed, which then will go into the current devel cycle. I just don't know when it's the next time it will be pushed upwards, but it
2023 Feb 20
1
linux-6.2-rc4+ hangs on poweroff/reboot: Bisected
On Mon, Feb 20, 2023 at 11:51 AM Chris Clayton <chris2553 at googlemail.com> wrote: > > > > On 20/02/2023 05:35, Ben Skeggs wrote: > > On Sun, 19 Feb 2023 at 04:55, Chris Clayton <chris2553 at googlemail.com> wrote: > >> > >> > >> > >> On 18/02/2023 15:19, Chris Clayton wrote: > >>> > >>> > >>> On
2015 Jul 29
3
Updating from 6.6 - 6.9 SSH
No I'm referring to "sshd -ddd" (preferrable on a high port like -p 8080 so you don't break your current ability to connect to the machine). As clearly the server is rejecting it. And only the server side debug can tell us that. - Ben Nick Stanoszek wrote: > I am using an AWS ubuntu 14.04 server...is that what you are asking? > > On Tue, Jul 28, 2015 at 10:00 PM,
2015 Jul 29
2
Updating from 6.6 - 6.9 SSH
And Server? - Ben Nick Stanoszek wrote: > Please see below :). Just a note---this is the EXACT command that I > use to log into the server BEFORE i try to update SSH. I continue to > use this same command for other servers. > > Nicks-MacBook-Pro:Downloads$ ssh -i WHATEVERKEY.pem > ubuntu at 54.200.249.185 <mailto:ubuntu at 54.200.249.185> -v -v -v -v > >
2024 Apr 10
9
[Bug 1744] New: Packet corruption occurs when using the nftables vlan pcp set command
https://bugzilla.netfilter.org/show_bug.cgi?id=1744 Bug ID: 1744 Summary: Packet corruption occurs when using the nftables vlan pcp set command Product: nftables Version: 1.0.x Hardware: arm OS: All Status: NEW Severity: major Priority: P5 Component: kernel
2017 Mar 10
0
[PATCH] secboot: fix NULL pointer dereference
The msgqueue pointer validity should be checked by its owner, not by the msgqueue code itself to avoid this situation. Signed-off-by: Alexandre Courbot <acourbot at nvidia.com> Reported-by: Julia Lawall <julia.lawall at lip6.fr> --- drm/nouveau/nvkm/engine/sec2/base.c | 7 +++++++ drm/nouveau/nvkm/falcon/msgqueue.c | 5 ++--- drm/nouveau/nvkm/subdev/pmu/gm20b.c | 6 ++++++ 3 files
2011 Aug 10
2
join columns
Dear R-help, I wonder if you could give me some suggestions in how to do a union join of two data frames as follow: -> union join the common column, and insert a 0 if one is missing. I made a function to perform the following, and I know it may not that quite welly written, but it works. Any suggestions are welcome, many thanks. Anthony > q1 =
2017 Mar 10
1
[bug report] drm/nouveau/secboot: add gp102/gp104/gp106/gp107 support
Hello Alexandre Courbot, The patch 5429f82f3415: "drm/nouveau/secboot: add gp102/gp104/gp106/gp107 support" from Jan 26, 2017, leads to the following static checker warning: drivers/gpu/drm/nouveau/nvkm/subdev/secboot/gp102.c:63 gp102_run_secure_scrub() warn: passing zero to 'PTR_ERR' drivers/gpu/drm/nouveau/nvkm/subdev/secboot/gp102.c 46 static int 47