From: Jun Ebihara
Subject: Re: HEADS UP: Merging drm update
Date: Tue, 18 Jan 2022 08:31:01 +0900 (JST)
On Dynabook R63/P i5-5300U
works well:
NetBSD 9.99.92 (GENERIC) #0: Mon Dec 6 04:25:36 UTC 2021
after update :
NetBSD 9.99.93 (GENERIC) #0: Mon Feb 14 20:37:51 UTC 2022
- startx works
On Wed, 5 Jan 2022 10:20:45 +0200
Andrius V wrote:
> I am also not sure how to redirect boot
> messages to serial attached through USB to see if any backtrace is
> available.
I had the same question actually!
I looked around for a bit, even for linux or what and couldn't find something
On Dynabook R63/P i5-5300U
works well:
NetBSD 9.99.92 (GENERIC) #0: Mon Oct 25 20:32:38 UTC 2021
after update :
NetBSD 9.99.93 (GENERIC) #0: Sun Jan 16 10:52:18 UTC 2022
- startx works.
- mate-session:
background image, only shows upper 1/5 area.
logout the session,panic.
dmesg
Hello,
unfortunately my build was broken the night before last, so I had to
restart yesterday. This morning I could now test with the changed FONT
option. The error pattern is still unchanged - with deactivated CSM, the
graphics switches to this disturbed mode at the modeswitch.
As
Hello,
On 04.01.22 21:10, RVP wrote:
Can you check something else as well?
Compile a kernel with:
-
# Give us a choice of fonts based on monitor size
#options FONT_BOLD8x16
#options FONT_BOLD16x32
options FONT_SPLEEN12x24
-
Sorry for the delay... just started a
Hi,
I potentially have the same issue as Ryo with my mac mini based on
Intel i5-4278U with Iris graphics 5100. After DRM upgrade system goes
blank on boot just before intelfb attachment (I guess) and likely
crash (no logs messages available it seems). Before drm upgrade it
also goes blank at the
On Tue, 4 Jan 2022, Matthias Petermann wrote:
RVP's tip was good and I can also confirm on my side that the problem is not
fundamentally caused by the actual UEFI boot process, but that only the
enabling/disabling of the CSM affects it. Also, the problem did not exist in
NetBSD 9.2 at all.
Hi,
Taylor R Campbell writes:
>> Date: Mon, 03 Jan 2022 22:08:26 +0900
>> From: Ryo ONODERA
>>
>> Ryo ONODERA writes:
>>
>> > __engines_record_defaults
>> > intel_gt_wait_for_idle
>> > intel_gt_retire_requests_timeout
>> > dma_fence_wait_timeout
>> > i915_fence_wait (via *fence->ops->wait)
> Date: Mon, 03 Jan 2022 22:08:26 +0900
> From: Ryo ONODERA
>
> Ryo ONODERA writes:
>
> > __engines_record_defaults
> > intel_gt_wait_for_idle
> > intel_gt_retire_requests_timeout
> > dma_fence_wait_timeout
> > i915_fence_wait (via *fence->ops->wait)
> > i915_request_wait
> >
> > In
Hi,
If you missed, could you read my following email?
Thank you.
Ryo ONODERA writes:
> Hi,
>
> Taylor R Campbell writes:
>
>>> Date: Tue, 28 Dec 2021 11:34:43 +0900
>>> From: Ryo ONODERA
>>>
>>> intel_gt_pm_fini() at netbsd:intel_gt_pm_fini+0x18
>>> intel_gt_init() at
On Fri 31 Dec 2021 at 11:30:32 +0100, Matthias Petermann wrote:
> - When I boot current in UEFI mode, after the mode switch it only displays a
> blank screen with a white background. After that, within a few seconds, a
> kind of randomly structured dark spot develops from the center of the
>
> Date: Fri, 31 Dec 2021 11:30:32 +0100
> From: Matthias Petermann
>
> - When I boot current in UEFI mode, after the mode switch it only
> displays a blank screen with a white background. After that, within a
> few seconds, a kind of randomly structured dark spot develops from the
> center of
Hello,
first of all, thanks for the effort to bring an up-to-date DRM to
NetBSD! Proper graphics support is essential for most users and
therefore the work cannot be appreciated enough.
I have now also managed to test current on my laptop and made an
observation that I would like to share
Hi,
Taylor R Campbell writes:
>> Date: Tue, 28 Dec 2021 11:34:43 +0900
>> From: Ryo ONODERA
>>
>> intel_gt_pm_fini() at netbsd:intel_gt_pm_fini+0x18
>> intel_gt_init() at netbsd:intel_gt_init+0x6ad
>> i915_gem_init() at netbsd:i915_gem_init+0x14d
>> i915_driver_probe() at
> Date: Tue, 28 Dec 2021 11:34:43 +0900
> From: Ryo ONODERA
>
> intel_gt_pm_fini() at netbsd:intel_gt_pm_fini+0x18
> intel_gt_init() at netbsd:intel_gt_init+0x6ad
> i915_gem_init() at netbsd:i915_gem_init+0x14d
> i915_driver_probe() at netbsd:i915_driver_probe+0x949
> i915drmkms_attach_real() at
Hi,
Taylor R Campbell writes:
>> Date: Tue, 28 Dec 2021 08:41:16 +0900
>> From: Ryo ONODERA
>>
>> panic: mutex_vector_enter,518: uninitialized lock (lock=0xd80023501458,
>> from=807c091c)
>> cpu0: Begin traceback...
>> vpanic() at netbsd:vpanic+0x156
>> panic() at
> Date: Tue, 28 Dec 2021 08:41:16 +0900
> From: Ryo ONODERA
>
> panic: mutex_vector_enter,518: uninitialized lock (lock=0xd80023501458,
> from=807c091c)
> cpu0: Begin traceback...
> vpanic() at netbsd:vpanic+0x156
> panic() at netbsd:panic+0x3c
> lockdebug_wantlock() at
> Date: Mon, 27 Dec 2021 12:34:10 +0900
> From: Ryo ONODERA
>
> panic: kernel diagnostic assertion "!(!i915_request_completed(rq))" failed:
> file "/usr/src/sys/external/bsd/drm2/dist/drm/i915/gt/intel_gt.c", line 475
I committed a change that I think will fix the particular bug leading
to
On Mon, Dec 27, 2021 at 06:58:34PM +0900, Ryo ONODERA wrote:
> Hi,
>
> My previous dmesg is confusing.
> Two messages are accidentally concatenated. The former message has no newline.
> They should be splitted as follows.
>
> panic: i915drmkms0: notice: DMC firmware homepage:
>
Hi,
My previous dmesg is confusing.
Two messages are accidentally concatenated. The former message has no newline.
They should be splitted as follows.
panic: i915drmkms0: notice: DMC firmware homepage:
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/tree/i915
kernel
On Mon, Dec 27, 2021 at 12:34:10PM +0900, Ryo ONODERA wrote:
> "panic: i915drmkms0: notice: DMC firmware homepage:
Where would the firmware need to be?
/libdata/firmware/i915/skl_dmc_ver1_27.bin
obviously is not the right place.
Martin
Hi,
Taylor R Campbell writes:
> Can you try the attached patch? Also, if you haven't already, can you
> try running a DIAGNOSTIC/DEBUG/LOCKDEBUG kernel?
Thanks for your patch.
It seems that it is already in src tree.
My laptop has no Intel AMT support.
I have added as follows:
options
Can you try the attached patch? Also, if you haven't already, can you
try running a DIAGNOSTIC/DEBUG/LOCKDEBUG kernel?
>From 025745d6f43aff21c88bc9e3b393ce146fc9af04 Mon Sep 17 00:00:00 2001
From: Taylor R Campbell
Date: Sun, 26 Dec 2021 16:05:20 +
Subject: [PATCH] drm: Fix locking around
Hi,
New drm works great with my NVIDIA GT 710.
Manual scaling by xrandr, which is required before, is no longer necessary.
Boot time gets faster, and I have better font looking.
Thank you so much!!
On Sun, Dec 19, 2021 at 2:06 AM Taylor R Campbell wrote:
>
> I'm planning to merge the drm
> Date: Sun, 26 Dec 2021 02:37:31 +0900
> From: Ryo ONODERA
>
> If panic is removed, my LCD turns black finally and stay black forever
> and does not reach to USB serial console.
> [...]
> However I am not sure because I cannot get any message.
>
> Do you have an idea to investigate deeper?
Hi,
Ryo ONODERA writes:
> Hi,
>
> Taylor R Campbell writes:
>
>> Better yet -- can you try the attached patch?
>> From e484fe666999730543f490ce6084486f7d7ce524 Mon Sep 17 00:00:00 2001
>> From: Taylor R Campbell
>> Date: Fri, 24 Dec 2021 11:12:43 +
>> Subject: [PATCH] i915: Use
Hi,
Taylor R Campbell writes:
> Better yet -- can you try the attached patch?
> From e484fe666999730543f490ce6084486f7d7ce524 Mon Sep 17 00:00:00 2001
> From: Taylor R Campbell
> Date: Fri, 24 Dec 2021 11:12:43 +
> Subject: [PATCH] i915: Use AcpiOsMapMemory, not bus_space_map, for
Better yet -- can you try the attached patch?
>From e484fe666999730543f490ce6084486f7d7ce524 Mon Sep 17 00:00:00 2001
From: Taylor R Campbell
Date: Fri, 24 Dec 2021 11:12:43 +
Subject: [PATCH] i915: Use AcpiOsMapMemory, not bus_space_map, for opregion.
Needed because this appears in
> Date: Thu, 23 Dec 2021 17:26:49 +
> From: Taylor R Campbell
>
> > Date: Fri, 24 Dec 2021 01:53:03 +0900
> > From: Ryo ONODERA
> >
> > And with this patch, I have gotten the following dmesg:
> > This has no bus_space_map and extent_alloc_subregion1...
>
> OK, can you try the attached
riastr...@netbsd.org (Taylor R Campbell) writes:
> #include
> if (bpa <=3D BADADDR && BADADDR < bpa + size)
> db_stacktrace();
>Then share the dmesg output on boot with this change to
>bus_space_reserve?
>This way we can track down who's reserving the registers that
Acer Revo Box RN86 with DisplayPort connection:
http://bsd-hardware.info/?probe=6d184a1e62
dmesg: https://disk.yandex.ru/d/EbYO4kOkUMqhfw
Photos of screen:
https://disk.yandex.ru/i/2fFMSqX14LT9ig
https://disk.yandex.ru/i/S7Bj_2-62Mna3w
https://disk.yandex.ru/i/7o46UsqbxfFKVw
23.12.2021 22:22,
> Date: Fri, 24 Dec 2021 01:53:03 +0900
> From: Ryo ONODERA
>
> And with this patch, I have gotten the following dmesg:
> This has no bus_space_map and extent_alloc_subregion1...
OK, can you try the attached patch and see if it gives us any clues in
dmesg? This prints a stack trace any time
Hi! Sorry for my bad English... I am beginning user of NetBSD-Current.
I am owner of Acer Revo Box RN86 (CPU Intel 9400T and UHD Graphics 630)
with DisplayPort and HDMI connection. With DisplayPort connection
NetBSD-Current with new drm works on Acer Revo RN86 (with some warnings)
and
Hi,
Ryo ONODERA writes:
> Hi,
>
> Taylor R Campbell writes:
>
>>> Date: Thu, 23 Dec 2021 14:56:19 +
>>> From: Taylor R Campbell
>>>
>>> I'm wondering whether the two bus_space_maps in intel_opregion_setup
>>> overlap, and whether one needs to be a bus_space_subregion or
>>> something.
>>
Hi,
Taylor R Campbell writes:
>> Date: Thu, 23 Dec 2021 14:56:19 +
>> From: Taylor R Campbell
>>
>> I'm wondering whether the two bus_space_maps in intel_opregion_setup
>> overlap, and whether one needs to be a bus_space_subregion or
>> something.
>
> Never mind, that's a red herring and
> Date: Thu, 23 Dec 2021 14:56:19 +
> From: Taylor R Campbell
>
> I'm wondering whether the two bus_space_maps in intel_opregion_setup
> overlap, and whether one needs to be a bus_space_subregion or
> something.
Never mind, that's a red herring and obviously not what's happening
here.
> Date: Thu, 23 Dec 2021 20:53:00 +0900
> From: Ryo ONODERA
>
> I have added panic()s to extent_alloc_region and
> extent_insert_and_optimize.
> And the kernel with this change does not display anything at all.
> After bootloader, my LCD turns black and stays black forever.
> I have removed
> Date: Wed, 22 Dec 2021 18:58:51 +
> From: Taylor R Campbell
>
> > Date: Thu, 23 Dec 2021 00:57:13 +0900
> > From: Ryo ONODERA
> >
> > Ryo ONODERA writes:
> >
> > > I have no useful information or thought yet…
> > >
> > > I have added check for BADADDR+OPREGION_SIZE in
> Date: Thu, 23 Dec 2021 00:57:13 +0900
> From: Ryo ONODERA
>
> Ryo ONODERA writes:
>
> > I have no useful information or thought yet…
> >
> > I have added check for BADADDR+OPREGION_SIZE in bus_space_reserve.
> > And I have found that no one uses that address.
>
> I have added similar logic
Hi,
Ryo ONODERA writes:
> hi,
>
> I have no useful information or thought yet…
>
> I have added check for BADADDR+OPREGION_SIZE in bus_space_reserve.
> And I have found that no one uses that address.
I have added similar logic to extent_alloc_region() and
extent_insert_and_optimize(). And I
Hi,
Taylor R Campbell writes:
>> Date: Tue, 21 Dec 2021 22:47:34 +0900
>> From: Ryo ONODERA
>>
>> I think that "Cannot find any crtc or sizes" may be related to
>> "Failed to find VBIOS tables (VBT)".
>> I have added some printf lines to some functions invoked before
>> intel_bios_init in
>>
> Date: Tue, 21 Dec 2021 22:47:34 +0900
> From: Ryo ONODERA
>
> I think that "Cannot find any crtc or sizes" may be related to
> "Failed to find VBIOS tables (VBT)".
> I have added some printf lines to some functions invoked before
> intel_bios_init in
>
Hi,
Martin Husemann writes:
> On Tue, Dec 21, 2021 at 01:50:05AM +0900, Ryo ONODERA wrote:
>> (snip)
>> boot device: ld0
>> root on dk1 dumps on dk2
>> root file system type: ffs
>> kern.module.path=/stand/amd64/9.99.92/modules
>> kern info: [drm] Support vblank timestamp caching Rev 2
Hi,
On 2021/12/21 8:28, Taylor R Campbell wrote:
Date: Mon, 20 Dec 2021 11:35:45 +0900
From: Kengo NAKAHARA
GENERIC kernel without DIAGNOSTIC option fails to build.
Could you apply the following patch?
> Date: Mon, 20 Dec 2021 11:35:45 +0900
> From: Kengo NAKAHARA
>
> GENERIC kernel without DIAGNOSTIC option fails to build.
> Could you apply the following patch?
>
> https://github.com/knakahara/netbsd-src/commit/b1c93870ef5689201b6eb7e08811bc40e3e1543e
Thanks! I did it slightly
On Tue, Dec 21, 2021 at 01:50:05AM +0900, Ryo ONODERA wrote:
> (snip)
> boot device: ld0
> root on dk1 dumps on dk2
> root file system type: ffs
> kern.module.path=/stand/amd64/9.99.92/modules
> kern info: [drm] Support vblank timestamp caching Rev 2 (21.10.2013).
> kern info: [drm] Driver
Hi,
Taylor R Campbell writes:
>> Date: Sun, 19 Dec 2021 01:42:53 +
>> From: Taylor R Campbell
>>
>> > Date: Sat, 18 Dec 2021 17:06:13 +
>> > From: Taylor R Campbell
>> >
>> > I'm planning to merge the drm update this weekend -- a cvs import and
>> > merge commit, plus about 1300
Hi,
On 2021/12/19 21:48, Taylor R Campbell wrote:
Date: Sun, 19 Dec 2021 01:42:53 +
From: Taylor R Campbell
Date: Sat, 18 Dec 2021 17:06:13 +
From: Taylor R Campbell
I'm planning to merge the drm update this weekend -- a cvs import and
merge commit, plus about 1300 commits on top
> Please update and try again? (I've only compile-tested the changes,
> will take a closer look tomorrow if it doesn't fix the problem.)
seems to work for me. i can once again mostly play 720p video
with "mpv -vo x11".
thanks!
.mrg.
> Date: Sun, 19 Dec 2021 23:51:58 +
> From: Taylor R Campbell
>
> > Date: Sun, 19 Dec 2021 21:41:14 +0100
> > From: Benny Siegert
> >
> > Meanwhile, I built a new kernel from HEAD on my Pinebook Pro. There is
> > a bit of a pause when DRM is initialized during boot, and X is
> > basically
> Date: Sun, 19 Dec 2021 21:41:14 +0100
> From: Benny Siegert
>
> Meanwhile, I built a new kernel from HEAD on my Pinebook Pro. There is
> a bit of a pause when DRM is initialized during boot, and X is
> basically unusable -- it takes a minute or so to draw the login screen
> (slim).
> [...]
>
On Sun, Dec 19, 2021 at 2:35 PM nia wrote:
> > > > I'm planning to merge the drm update this weekend -- a cvs import and
> > > > merge commit, plus about 1300 commits on top of that from the git
> > > > repository.
>
> thank you Maya and Taylor for this monumental effort!
Yes, thank you, this is
On Sun, Dec 19, 2021 at 12:48:15PM +, Taylor R Campbell wrote:
> > Date: Sun, 19 Dec 2021 01:42:53 +
> > From: Taylor R Campbell
> >
> > > Date: Sat, 18 Dec 2021 17:06:13 +
> > > From: Taylor R Campbell
> > >
> > > I'm planning to merge the drm update this weekend -- a cvs import
> Date: Sun, 19 Dec 2021 01:42:53 +
> From: Taylor R Campbell
>
> > Date: Sat, 18 Dec 2021 17:06:13 +
> > From: Taylor R Campbell
> >
> > I'm planning to merge the drm update this weekend -- a cvs import and
> > merge commit, plus about 1300 commits on top of that from the git
> >
> Date: Sat, 18 Dec 2021 17:06:13 +
> From: Taylor R Campbell
>
> I'm planning to merge the drm update this weekend -- a cvs import and
> merge commit, plus about 1300 commits on top of that from the git
> repository.
The update is in progress, but my commitbomb script isn't perfect and
I'm planning to merge the drm update this weekend -- a cvs import and
merge commit, plus about 1300 commits on top of that from the git
repository.
Please don't commit anything to the following subtrees until done --
if you do, your changes will be lost:
sys/external/bsd/drm2
56 matches
Mail list logo
