On Tue, Nov 27, 2018 at 05:10:20AM -0500, James Hastings wrote:
> Hello all
>
> I acquired a Raspberry Pi 3 Model B Plus recently
> and have been working on enabling the onboard ethernet.
>
> mue0 at uhub2 port 1 configuration 1 interface 0 "Standard
> Microsystems LAN7800" rev 2.10/3.00 addr 4
>
On Wed, Nov 28, 2018 at 02:42:43PM +0200, timo.my...@bittivirhe.fi wrote:
> >Synopsis:keyboard repeat not working correctly in X
> >Category:system
> >Environment:
> System : OpenBSD 6.4
> Details : OpenBSD 6.4-current (GENERIC.MP) #466: Fri Nov 23
> 21:07:35 MST 2018
On Mon, Dec 03, 2018 at 03:15:38AM +0100, lord nihil. wrote:
> An OpenBSD developer on reddit has informed me that the cause of issue 1
> is already known & being worked on (No libLLVM in base).
Indeed the xenocara sets can't include radeonsi for now but with
-current it is possible to build it y
On Sat, Dec 15, 2018 at 10:34:00AM +0300, Denis wrote:
> /etc/firmware/radeon/ contains bonaire_uvd.bin & bonaire_vce.bin
>
> by soft linking them to BONAIRE_uvd.bin & BONAIRE_vce.bin don't bring
> any positive results. The error is persistent.
>
> It seems radeonsi should be fixed for firmware p
On Fri, Jan 04, 2019 at 09:56:15PM -0600, Brian Conway wrote:
> Greetings. I have a hot-off-the-presses Intel NUC model NUC8i5BEH
> (https://www.intel.com/content/www/us/en/products/boards-kits/nuc/kits/nuc8i5beh.html).
> For such a recent release, just about everything that I need works
> well, in
On Sat, Jan 05, 2019 at 07:53:04PM +1100, Jonathan Gray wrote:
> On Fri, Jan 04, 2019 at 09:56:15PM -0600, Brian Conway wrote:
> > Greetings. I have a hot-off-the-presses Intel NUC model NUC8i5BEH
> > (https://www.intel.com/content/www/us/en/products/boards-kits/nuc/kits/nuc8i5beh
The focus for drm is working on an update to 4.19. It is not a good use
of time to delve into longstanding problems with the 4.4 code that may
already be fixed in 4.19.
On Wed, Jan 23, 2019 at 06:42:33AM +0100, Alessandro DE LAURENZIS wrote:
> Gentle reminder, hoping that someone with the needed
On Wed, Feb 27, 2019 at 11:07:23AM -0800, Philip Guenther wrote:
> On Mon, 25 Feb 2019, Falk Richter wrote:
> > >Synopsis:
> ...
> > >Description:
> > > trap: 0(0) invalid opcode fault
> > cn_tab=0x5412c
> > eax 0 ecx 0 edx ff58 ebx ffc8
> > esp fe0c ebp ff40 esi 8 edi ff58
> > eip 4241c efl
On Wed, Mar 13, 2019 at 06:50:05PM +0900, UnHa Kim wrote:
> >Synopsis: cubieboard2 installation image boot failure.
> >Category: Installation
> >Environment:
> System : OpenBSD 6.4
> Details : OpenBSD 6.4 Cubieboard2 installation image.
> Architecture: OpenBSD.armv7
On Sun, Apr 07, 2019 at 01:52:08PM +0200, Matthias Schmidt wrote:
> Hi,
>
> I upgraded to the latest snapshot (timestamp is from April 6) and
> boot stucks at the loader prompt. After upgrading I see
> the following message (transcript by hand):
>
> Using drive 0, partition 3.
> Loading.
> p
On Sat, Apr 13, 2019 at 05:26:54PM -0400, Kurt Mosiejczuk wrote:
>
> >Synopsis:i386 install kernel (bsd.mp) hangs at inteldrm install
> >Category:kernel i386
> >Environment:
> System : OpenBSD 6.5
> Details : OpenBSD 6.5 (GENERIC.MP) #1354: Fri Apr 12 08:39:21 MDT
> 2
On Sat, Apr 20, 2019 at 08:52:33AM -0500, Lucas Raab wrote:
> >Synopsis:X locks up after resizing windows
> >Category:amd64
> >Environment:
> System : OpenBSD 6.5
> Details : OpenBSD 6.5-current (GENERIC.MP) #8: Fri Apr 19 21:48:49
> MDT 2019
>
On Sat, Apr 20, 2019 at 04:42:29PM +0200, Matthias Schmidt wrote:
> Hi,
>
> * Jonathan Gray wrote:
> >
> > There is some kind of use after free or double free that triggers only
> > when opting into the 'intel' driver on recent hardware instead of the
>
On Wed, Nov 03, 2021 at 06:33:47AM +, Lewis ingraham wrote:
> Hello I have an issue with X.Org intel driver crashing while using Firefox
> web browser watching youtube videos. Here are all of my logs attached:
Sandy bridge hardware uses the modesettting driver by default.
When you opt into th
On Thu, Nov 04, 2021 at 11:07:54AM +, Laurence Tratt wrote:
> I updated my amd64 machine from a snapshot from about 2 weeks ago to the Nov
> 2nd and then Nov 3rd snapshots. In both cases, as soon as I log into X,
> start Firefox, and try and load a page the machine hard locks and has to be
> po
On Thu, Nov 04, 2021 at 11:15:42AM +, Lewis ingraham wrote:
> Hello after changing the driver to modesetting. My compositor stops
> working(picom with backend set to glx), screen tearing is present, firefox
> video is a laggy mess and now i get an intel_gt_reset error when it crashes
> referenc
On Thu, Nov 04, 2021 at 12:02:21PM +, Laurence Tratt wrote:
> On Thu, Nov 04, 2021 at 10:24:07PM +1100, Jonathan Gray wrote:
>
> Hello Jonathan,
>
> >> I updated my amd64 machine from a snapshot from about 2 weeks ago to the
> >> Nov 2nd and then Nov 3rd snapsh
On Fri, Nov 05, 2021 at 03:22:27AM +0100, Emiel Kollof wrote:
> On Tue, 2 Nov 2021 21:17:43 +1300
> Avon Robertson wrote:
>
> > Please read the preceding post before this.
> >
> > The information below is the second post made by me pertaining to
> > thread 'drmfreeze'. It is the first? post made
On Sat, Nov 20, 2021 at 10:17:54PM +0100, Alexander Bluhm wrote:
> Hi,
>
> Regress found an data_access_fault on sparc64 pfctl
>
> START sys/net/pf_table2021-11-20T19:26:58Z
>
> rm -f a.out [Ee]rrs mklog *.core y.tab.h stamp-*
>
> hit
> pfctl -qt __regress_tbl -T add -
On Sun, Dec 05, 2021 at 04:54:28PM -0700, Ted Bullock wrote:
> Hey folks,
>
> Looking into another usability fault with the SunBlade 100. This time
> with the onboard video adapter. I'm seeing X segfault when starting up
> using the default configuration and after a fresh install of -current.
>
On Thu, Dec 09, 2021 at 10:01:30PM -0700, Ted Bullock wrote:
> On 2021-12-09 6:46 p.m., Ted Bullock wrote:
> > On 2021-12-06 4:21 p.m., Ted Bullock wrote:
> > I think that there is an bug triggered by endian code here:
> >
> >> radeondrm0: RV100
> >> BIOS signature incorrect 0 0
> >
> > in sys/de
On Sat, Dec 11, 2021 at 12:41:46PM +0100, Mark Kettenis wrote:
> > Date: Fri, 10 Dec 2021 17:24:58 -0700
> > From: Ted Bullock
> >
> > On 2021-12-10 12:53 a.m., Jonathan Gray wrote:
> > > On Thu, Dec 09, 2021 at 10:01:30PM -0700, Ted Bullock wrote:
> > >
On Tue, Dec 14, 2021 at 10:38:44PM -0600, Phil Vuchetich wrote:
> I am trying OpenBSD 7.0 again (now that I have an AMD video card). I'll
> follow up with sendbug(1) and would be happy to work with someone to
> troubleshoot if this is of interest to anyone. I didn't see an amdgpu(4)
> update in -cu
On Wed, Jan 05, 2022 at 01:33:59PM -0500, fo...@dnmx.org wrote:
> Hello.
> I have installed OpenBSD a few times now, of course, latest 7.0 release, with
> FDE.
> Now, that was on literally every computer, but my main one. Now, I go to
> install it on my main computer - the beast..
> I have an AMD 5
On Sun, Jan 09, 2022 at 09:27:57PM +0100, Sven Wolf wrote:
> Hi list,
>
> in October'21 I successfully installed OpenBSD on this litte fanless latop.
> There are following issues, even with -current:
>
> The soundcard (Linux dmesg: snd_hda_codec_realtek hdaudioC0D0: autoconfig
> for ALC256) is no
On Sun, Jan 09, 2022 at 09:27:57PM +0100, Sven Wolf wrote:
> Hi list,
>
> in October'21 I successfully installed OpenBSD on this litte fanless latop.
> There are following issues, even with -current:
>
> The soundcard (Linux dmesg: snd_hda_codec_realtek hdaudioC0D0: autoconfig
> for ALC256) is no
On Mon, Jan 10, 2022 at 08:56:18PM +0100, Sven Wolf wrote:
>
>
> On 1/10/22 02:02, Jonathan Gray wrote:
> > On Sun, Jan 09, 2022 at 09:27:57PM +0100, Sven Wolf wrote:
> > > Hi list,
> > >
> > > in October'21 I successfully installed OpenBSD on t
On Tue, Jan 11, 2022 at 09:06:42PM +0100, Sven Wolf wrote:
>
>
> On 1/11/22 01:42, Jonathan Gray wrote:
> > On Mon, Jan 10, 2022 at 08:56:18PM +0100, Sven Wolf wrote:
> > >
> > >
> > > On 1/10/22 02:02, Jonathan Gray wrote:
> > > > On
On Mon, Jan 10, 2022 at 08:56:18PM +0100, Sven Wolf wrote:
> Also with the wsfb driver the laptop is usable. I look forward to the 5.15
> drm driver.
With the latest cvs, inteldrm should attach.
On Sat, Jan 15, 2022 at 01:36:55PM -0500, Agnosto Dvonik wrote:
> Synopsis: Unpredictable and unrecoverable freezing
> Category: kernel panic
> Environment:
> System : OpenBSD 7.0
> Details : OpenBSD 7.0-current (GENERIC.MP) #256: Fri Jan 14
> 22:30:45 MST 2022
On Sat, Jan 15, 2022 at 08:14:43PM -0500, Ryan Kavanagh wrote:
> On Sun, Jan 16, 2022 at 09:41:26AM +1100, Jonathan Gray wrote:
> > On Sat, Jan 15, 2022 at 01:36:55PM -0500, Agnosto Dvonik wrote:
> > > I have also noticed that the fans in the system start to whirr a bit
&g
On Sat, Jan 15, 2022 at 01:36:55PM -0500, Agnosto Dvonik wrote:
> Synopsis: Unpredictable and unrecoverable freezing
> Category: kernel panic
> Environment:
> System : OpenBSD 7.0
> Details : OpenBSD 7.0-current (GENERIC.MP) #256: Fri Jan 14
> 22:30:45 MST 2022
On Wed, Jan 19, 2022 at 11:04:26PM -0800, guent...@openbsd.org wrote:
> On Wed, 19 Jan 2022, Thomas Frohwein wrote:
> > >Synopsis: crash on booting GENERIC.MP since upgrade to Jan 18 snapshot
> > >Category: kernel amd64
> > >Environment:
> > System : OpenBSD 7.0
> > Details : Ope
On Thu, Jan 20, 2022 at 04:08:28PM -0700, Thomas Frohwein wrote:
> On Fri, Jan 21, 2022 at 12:22:49AM +1100, Jonathan Gray wrote:
> > On Wed, Jan 19, 2022 at 11:04:26PM -0800, guent...@openbsd.org wrote:
> [...]
> > > The backtrace is kinda nonsensical, showing a c
On Fri, Jan 21, 2022 at 03:31:14PM -0700, Thomas Frohwein wrote:
> On Fri, Jan 21, 2022 at 07:54:29PM +1100, Jonathan Gray wrote:
> > On Thu, Jan 20, 2022 at 04:08:28PM -0700, Thomas Frohwein wrote:
> > > On Fri, Jan 21, 2022 at 12:22:49AM +1100, Jonathan Gray wrote:
> >
On Sun, Jan 23, 2022 at 09:20:20AM +, Laurence Tratt wrote:
> I've had a Ryzen machine with a (basic!) Polaris GPU for about a year. Over
> that time nearly all of the GPU related bugs have disappeared (thanks
> Jonathan et al.!), except for the fact that I don't seem to be able to
> reliably s
On Sun, Jan 23, 2022 at 02:40:21PM -0700, Thomas Frohwein wrote:
> On Sun, Jan 23, 2022 at 10:19:24AM +1100, Jonathan Gray wrote:
> > On Fri, Jan 21, 2022 at 03:31:14PM -0700, Thomas Frohwein wrote:
> > > On Fri, Jan 21, 2022 at 07:54:29PM +1100, Jonathan Gray wrote:
> >
On Tue, Jan 25, 2022 at 08:27:19AM +1100, Jonathan Gray wrote:
> On Sun, Jan 23, 2022 at 02:40:21PM -0700, Thomas Frohwein wrote:
> > On Sun, Jan 23, 2022 at 10:19:24AM +1100, Jonathan Gray wrote:
> > > On Fri, Jan 21, 2022 at 03:31:14PM -0700, Thomas Frohwein wrote:
> >
On Mon, Jan 24, 2022 at 05:57:01PM -0700, Thomas Frohwein wrote:
> On Tue, 25 Jan 2022 10:59:26 +1100
> Jonathan Gray wrote:
>
> > > if you revert the previous and try this does it still boot?
> >
> > this would be more interesting to try
> >
> > co
On Mon, Jan 17, 2022 at 10:07:50AM +0100, Peter N. M. Hansteen wrote:
> After installing the latest snapshot late evening 20220116 CEST I found the
> machine
> halted with the message
>
> panic: kernel diagnostic assertion "__mp_lock_held(&sched_lock, curcpu())
> == 0" failed: file "/usr/serc/
On Thu, Jan 27, 2022 at 12:51:19PM +0300, Alex Beakes wrote:
> On Tue, Jan 25, 2022 at 2:25:23, Jonathan Gray wrote:
> > On Mon, Jan 24, 2022 at 05:57:01PM -0700, Thomas Frohwein wrote:
> > > On Tue, 25 Jan 2022 10:59:26 +1100
> > > Jonathan Gray wrote:
> > >
On Thu, Jan 27, 2022 at 11:50:25PM +1100, Ross L Richardson wrote:
> [I'm not subscribed to bugs@, but will monitor using MARC.]
>
> >Synopsis:On resume, igc does not pass packets
> >Category:kernel
> >Environment:
> System : OpenBSD 7.0
> Details : OpenBSD 7.0-current
On Fri, Jan 28, 2022 at 06:17:58AM -0700, Thomas Frohwein wrote:
> On Thu, 27 Jan 2022 06:16:04 -0700
> Thomas Frohwein wrote:
>
> > > > Wanted to clarify my reddit post:
> > > > There is a problem when the install is encrypted (full disk encryption,
> > > > w
> > > > bioctl).
> > > > Unencrypte
On Mon, Jan 31, 2022 at 12:54:53AM -0700, Thomas Frohwein wrote:
> On Sat, 29 Jan 2022 12:15:10 -0300
> Martin Pieuchot wrote:
>
> > On 28/01/22(Fri) 23:03, Thomas Frohwein wrote:
> > > On Sat, 29 Jan 2022 15:19:20 +1100
> > > Jonathan Gray wrote:
> >
On Mon, Jan 31, 2022 at 12:54:53AM -0700, Thomas Frohwein wrote:
> On Sat, 29 Jan 2022 12:15:10 -0300
> Martin Pieuchot wrote:
>
> > On 28/01/22(Fri) 23:03, Thomas Frohwein wrote:
> > > On Sat, 29 Jan 2022 15:19:20 +1100
> > > Jonathan Gray wrote:
> >
On Mon, Jan 31, 2022 at 12:14:32PM -0300, Martin Pieuchot wrote:
> On 31/01/22(Mon) 00:54, Thomas Frohwein wrote:
> > On Sat, 29 Jan 2022 12:15:10 -0300
> > Martin Pieuchot wrote:
> >
> > > On 28/01/22(Fri) 23:03, Thomas Frohwein wrote:
> > > > On Sat, 2
On Mon, Jan 31, 2022 at 11:17:01PM +1100, Jonathan Gray wrote:
> On Mon, Jan 31, 2022 at 12:54:53AM -0700, Thomas Frohwein wrote:
> > On Sat, 29 Jan 2022 12:15:10 -0300
> > Martin Pieuchot wrote:
> >
> > > On 28/01/22(Fri) 23:03, Thomas Frohwein wrote:
> > &g
On Thu, Feb 03, 2022 at 05:03:52PM +, Fred wrote:
> >Synopsis:upgraded to the latest i386 snapshot machine panicked on boot
> >Category:boot
> >Environment:
> System : OpenBSD 7.0
> Details : OpenBSD 7.0 (GENERIC) #208: Thu Sep 30 14:38:18 MDT 2021
>
On Fri, Feb 04, 2022 at 01:26:42AM +, Claudio Miranda wrote:
> Hello,
>
> As of the OpenBSD 7.0-current snapshot from 2022-02-02, I've been getting a
> kernel panic on boot when it tries to load inteldrm0. The system is a Dell
> Latitude E6410 laptop with a Core i5-520M and Intel HD Graphics
On Sat, Feb 05, 2022 at 12:46:06AM +0100, Joel Carnat wrote:
> Hi,
>
> I have just reinstalled my ThinkPad T460s from scratch using 2022/02/04
> snapshot. xenodm is configured to start automatically. But since I move my
> USB mouse, the laptop freezes.
>
> If I force a reboot, wait for xenodm t
On Wed, Feb 09, 2022 at 12:23:57PM +0200, Matthew Ward wrote:
> >Synopsis:GPU fails to init, display on at 1024x768
> >Category:GPU
> >Environment:
> System : OpenBSD 7.0
> Details : OpenBSD 7.0-current (GENERIC.MP) #321: Tue Feb 8 21:10:57
> MST 2022
>
On Mon, Feb 21, 2022 at 07:39:14PM -0500, Frank J. Cameron wrote:
> On Sat, Feb 19, 2022 at 05:30:47PM -0500, Frank J. Cameron wrote:
> > On Mon, 3 Aug 2020 02:24:47 +1000 Jonathan Gray wrote:
> > > On Sun, Aug 02, 2020 at 01:05:37PM +0200, mgloc...@openbsd.org wro
On Wed, Apr 20, 2022 at 09:14:19AM -0500, joshua stein wrote:
> I noticed in a few dmesgs from Intel 11th gen machines, the L2 cache
> is printed as disabled. Is there some new MSR that needs to be read
> on these CPUs?
l2 cache information is taken from cpuid 0x8006
Intel documents cpuid
On Tue, Apr 26, 2022 at 12:51:10PM +0100, james palmer wrote:
> That fixes things, thanks :)
>
> Maybe the default should be to not use glamour if hardware cannot be scanned.
> Then again, not many people will be using hardware this old so it might not
> be worth it.
>
> - James
When pci can n
On Wed, Apr 27, 2022 at 12:53:37PM +1000, Jonathan Gray wrote:
> On Tue, Apr 26, 2022 at 12:51:10PM +0100, james palmer wrote:
> > That fixes things, thanks :)
> >
> > Maybe the default should be to not use glamour if hardware cannot be
> > scanned. Then again, no
On Wed, Apr 27, 2022 at 03:14:50PM +1000, Jonathan Gray wrote:
> On Wed, Apr 27, 2022 at 12:53:37PM +1000, Jonathan Gray wrote:
> > On Tue, Apr 26, 2022 at 12:51:10PM +0100, james palmer wrote:
> > > That fixes things, thanks :)
> > >
> > > Maybe the def
On Wed, Apr 27, 2022 at 11:30:49AM +0200, Mark Kettenis wrote:
> > Date: Wed, 27 Apr 2022 18:30:52 +1000
> > From: Jonathan Gray
> >
> > On Wed, Apr 27, 2022 at 03:14:50PM +1000, Jonathan Gray wrote:
> > > On Wed, Apr 27, 2022 at 12:53:37PM +1000, Jonathan G
On Sat, Apr 30, 2022 at 07:32:46PM -0600, Thomas Frohwein wrote:
>
> >Synopsis:Reproducible crash on repeatedly running mono+SDL2 games
> >Category:kernel amd64
> >Environment:
> System : OpenBSD 7.1
> Details : OpenBSD 7.1-current (GENERIC.MP) #487: Sat Apr 30
> 09:1
On Mon, May 02, 2022 at 10:16:16AM -0600, Thomas Frohwein wrote:
>
> Here, it triggered after running the game twice with less than 30
> seconds of gameplay and then launching it a third time.
>
> I will see if I can find some opensource project that uses the FNA
> ecosystem to be a better test c
On Mon, May 02, 2022 at 09:03:48AM -0600, Thomas Frohwein wrote:
> On Mon, May 02, 2022 at 04:56:30PM +1000, Jonathan Gray wrote:
> > On Mon, May 02, 2022 at 10:16:16AM -0600, Thomas Frohwein wrote:
> > >
> > > Here, it triggered after running the game twice with le
On Tue, May 10, 2022 at 08:16:28AM +0100, Laurence Tratt wrote:
> On Sun, Jan 23, 2022 at 09:20:20AM +, Laurence Tratt wrote:
>
> > I've had a Ryzen machine with a (basic!) Polaris GPU for about a year. Over
> > that time nearly all of the GPU related bugs have disappeared (thanks
> > Jonathan
On Wed, Jun 08, 2022 at 12:23:11AM +0100, Chris Narkiewicz wrote:
> I collected few more details. Since I'm using intel GPU and efifb, I
> thought that using wsfb me a usable X11. Then I tried vesa. Neither
> driver worked. I attached Xorg.0.logs for both below. dmesg and
> whatnot is in my origina
On Wed, Jun 08, 2022 at 08:58:38AM +0100, Chris Narkiewicz wrote:
> On Wed, Jun 08, 2022 at 12:01:40PM +1000, Jonathan Gray wrote:
> > What is the last snapshot you used that worked?
>
> I upgraded stright from stable. I can try bisection method
> to pinpoint a working one.
>
On Wed, Jun 08, 2022 at 11:42:21PM +0100, Chris Narkiewicz wrote:
> On Wed, Jun 08, 2022 at 09:56:09PM +1000, Jonathan Gray wrote:
> > some older snapshots can be found at
> > https://ftp.hostserver.de/archive/
>
> Thanks.
>
> I did a bisect and here is the
On Fri, Jun 10, 2022 at 03:03:08AM +0100, Chris Narkiewicz wrote:
> On Thu, Jun 09, 2022 at 03:25:06PM +1000, Jonathan Gray wrote:
> > Can you try this diff against -current which reverts some drm commits
> > from that timeframe?
>
> So I tried and can't compile it -
On Fri, Jun 10, 2022 at 04:26:06AM +0100, Chris Narkiewicz wrote:
> On Fri, Jun 10, 2022 at 12:34:47PM +1000, Jonathan Gray wrote:
> > you don't need to start from tarballs, try
>
> Your instructions worked and I booted patched kernel.
>
> The patch doesn' work -
On Fri, Jun 10, 2022 at 11:53:42AM +0100, Chris Narkiewicz wrote:
> On Fri, Jun 10, 2022 at 01:45:09PM +1000, Jonathan Gray wrote:
> > Thanks, it would appear to be something outside of drm then.
>
> Is there a way to do a bisect with CVS? I could perhaps compile a bunch of
>
On Sat, Jun 11, 2022 at 04:29:06AM +0100, Chris Narkiewicz wrote:
> On Fri, Jun 10, 2022 at 01:45:09PM +1000, Jonathan Gray wrote:
> > Thanks, it would appear to be something outside of drm then.
>
> I managed to run latest snapshot 2022-06-11, but
> I did it by upgrading se
On Wed, Jun 22, 2022 at 10:16:31PM +0100, Chris Narkiewicz wrote:
> So I'm not giving up on this one just yet.
>
> I contacted StarLabs vendor about the hardware quirks, and they
> advised me to update the firmware to latest coreboot that is supposed
> to fix some issues, including suspend/resume.
On Wed, Apr 20, 2022 at 12:49:39PM -0500, joshua stein wrote:
> On Thu, 21 Apr 2022 at 00:47:05 +1000, Jonathan Gray wrote:
> > On Wed, Apr 20, 2022 at 09:14:19AM -0500, joshua stein wrote:
> > > I noticed in a few dmesgs from Intel 11th gen machines, the L2 cache
> >
On Wed, Jun 29, 2022 at 08:10:40PM +0100, Chris Narkiewicz wrote:
> On Tue, Jun 28, 2022 at 12:17:26PM +1000, Jonathan Gray wrote:
> > For that the EFI firmware would need to support Compatibility Support
> > Module (CSM), which is unlikely. Then a install with mbr/vga/biosboot
&g
On Fri, Jul 01, 2022 at 05:31:36PM +, Eric JACQUOT wrote:
> >Synopsis:Azalia codec Realtek ALC3204 - Microphone not working
> >Category:system kernel amd64
> >Environment:
> System : OpenBSD 7.1
> Details : OpenBSD 7.1-current (GENERIC.MP) #597: Thu Jun 30
> 12:16:
On Tue, Jul 26, 2022 at 04:17:18AM +0100, Chris Narkiewicz wrote:
> On Mon, Jul 25, 2022 at 11:02:25PM -0400, Nick Holland wrote:
> > here's what got added to dmesg after I built and installed a kernel with
> > that patch on my "problem" machine:
> >
> > ... snip ...
> > drm_syncobj_array_wait_time
On Mon, Jul 25, 2022 at 09:34:14PM +0100, Chris Narkiewicz wrote:
> On Mon, Jul 25, 2022 at 03:48:19PM -0400, Nick Holland wrote:
> > Sigh. collect info, leave out most basic part: what I mean
> > by "X quit working"...
>
> I checked your Xorg.0.log and it looks familiar. Please look for post
> "
On Tue, Jul 26, 2022 at 04:08:17AM +, Bill Chatfield wrote:
> You can consider this request canceled. I doubt it's going to get picked up
> by anybody. I can understand that support for a 22 year old graphics card is
> not a priority. But, I like OpenBSD so much I'm going to install it on a m
On Tue, Jul 26, 2022 at 09:56:21AM -0400, Nick Holland wrote:
> On 7/26/22 8:43 AM, Jonathan Gray wrote:
> > On Mon, Jul 25, 2022 at 09:34:14PM +0100, Chris Narkiewicz wrote:
> > > On Mon, Jul 25, 2022 at 03:48:19PM -0400, Nick Holland wrote:
> > > > Sigh. collect i
On Mon, Aug 01, 2022 at 11:28:08PM +0100, Laurence Tratt wrote:
> I've just got my sticky mits on a Framework 12th Gen Intel laptop. It
> somewhat works, but regularly hits kernel panics and other oddities on
> -current. I haven't worked out why yet, but uvm_faults seem to be frequent.
> For exampl
On Tue, Aug 02, 2022 at 10:44:00AM +0100, Laurence Tratt wrote:
> I'm also starting to understand a bit more about some of the random panics:
> they seem to happen very soon after X starts. Sometimes the mouse appears as
> a two inch square of weird colours (!) -- things only last for a few seconds
On Sat, Aug 06, 2022 at 10:28:06AM -0400, Nick Holland wrote:
> > When looking at top what does Xorg have for WAIT?
>
> PID USERNAME PRI NICE SIZE RES STATE WAIT TIMECPU COMMAND
> 41914 _x11 -22 -1 15M 26M idle schto 0:01 0.00% Xorg
>
> > this will run X with
On Tue, Aug 09, 2022 at 10:29:41AM -0400, Nick Holland wrote:
> On 8/9/22 09:36, Jonathan Gray wrote:
> > On Sat, Aug 06, 2022 at 10:28:06AM -0400, Nick Holland wrote:
> > > > When looking at top what does Xorg have for WAIT?
> > >
> > > PID USERN
On Tue, Aug 09, 2022 at 10:29:41AM -0400, Nick Holland wrote:
> On 8/9/22 09:36, Jonathan Gray wrote:
> > On Sat, Aug 06, 2022 at 10:28:06AM -0400, Nick Holland wrote:
> > > > When looking at top what does Xorg have for WAIT?
> > >
> > > PID USERN
On Wed, Apr 24, 2019 at 08:17:25PM +0200, Mark Kettenis wrote:
> > Date: Wed, 24 Apr 2019 17:33:58 +0200
> > From: Matthieu Herrb
> >
> > Hi,
> >
> > I have an old Dell Optiplex 755 laying around that I use for OpenBSD
> > tests from time to time at work. It worked well under 6.5 development,
>
On Wed, May 01, 2019 at 02:53:02AM -0400, James Hastings wrote:
> Booting latest snapshot the system hangs at the following:
>
> [drm] GuC: No firmware known for this platform!
> [drm] HuC: No firmware known for this platform!
These messages are not fatal and are expected when running on gemini
l
On Fri, May 03, 2019 at 11:21:07AM +0200, Mark Kettenis wrote:
> > Date: Fri, 03 May 2019 02:06:07 -0400
> > From: James Hastings
> >
> > Here is a little more debug info.
> >
> > I uncommented DRMDEBUG in sys/dev/pci/drm/include/drm/drmP.h
> >
> > root on sd0a (b9c87e5264160760.a) swap on sd0b
On Sun, May 12, 2019 at 08:56:05PM -0400, David Hill wrote:
> I have a Purism Librem15 laptop that always panics on boot.
>
> Traced back to this commit:
> https://marc.info/?l=openbsd-cvs&m=155523690813457&w=2
>
> Update shared drm code, inteldrm(4) and radeondrm(4) from linux 4.4 to
> linux 4.
On Thu, May 16, 2019 at 01:49:01PM -0700, Russell S wrote:
> snapshot kernel from 2019-05-15 fails on ryzen
> and machine reboots very early in the boot process
>
> early enough I see no blue kernel messages, that is, before, for example:
> "OpenBSD 6.5-current (GENERIC.MP) #12: Tue May 7 08:52:5
On Mon, May 27, 2019 at 10:22:12PM +0200, Sven M. Hallberg wrote:
> Sven M. Hallberg on Fri, May 24 2019:
> >>Fix:
> > ?
>
> I discovered the immediate culprit to be these lines in
> /sys/dev/pci/drm/i915/intel_display.c:
>
> static void intel_atomic_commit_tail(struct drm_atomic_state *s
On Tue, May 28, 2019 at 05:32:37PM +0200, Sven M. Hallberg wrote:
> Jonathan Gray on Tue, May 28 2019:
> > If you raise the timeout in drm_atomic_helper.c stall_checks() does
> > that also avoid the 'cleanup_done timed out' messages at some point?
>
> It's alr
compile/GENERIC.MP
>
> Previously, the boot message would switch from sideways mode to vertical mode
> when it started the inteldrm phase. Now, the console stays in sideways mode.
> I assume this is related to the panel quirks changes:
>
> Date: Fri, 12 Jul 2019 14:27:15 +1000
> From
On Sun, Jul 21, 2019 at 09:45:55AM +1200, Peter Kane wrote:
> On Fri, Jul 19, 2019 at 10:15:23PM +1000, Jonathan Gray wrote:
> > On Fri, Jul 19, 2019 at 03:55:02PM +1200, Peter Kane wrote:
> > > Hi
> > >
> > > Things were working fairly well u
On Sat, Jul 20, 2019 at 10:32:46PM +1000, open...@rlr.id.au wrote:
> >Synopsis:X11 graphics not working in snapshots on Braswell system
> >Category:amd64
> >Environment:
> System : OpenBSD 6.5
> Details : OpenBSD 6.5-current (GENERIC.MP) #131: Fri Jul 19
> 13:18:29 MDT
On Sun, Jul 21, 2019 at 11:23:12PM +1000, Ross L Richardson wrote:
> On Sun, Jul 21, 2019 at 07:41:58PM +1000, Jonathan Gray wrote:
> > On Sat, Jul 20, 2019 at 10:32:46PM +1000, open...@rlr.id.au wrote:
> > > >Synopsis:X11 graphics not working in snapsho
On Tue, Jul 23, 2019 at 04:32:50PM +1000, Jonathan Gray wrote:
> On Sun, Jul 21, 2019 at 11:23:12PM +1000, Ross L Richardson wrote:
> > On Sun, Jul 21, 2019 at 07:41:58PM +1000, Jonathan Gray wrote:
> > > On Sat, Jul 20, 2019 at 10:32:46PM +1000, open...@rlr.id.au wrote:
On Fri, Aug 09, 2019 at 06:58:10AM +, mujo wrote:
> Using OpenBSD 6.5-current (GENERIC.MP) #158: Tue Aug 6 16:46:13 MDT
> 2019
>
> Following directions here: https://www.openbsd.org/faq/faq5.html#Custom
>
> $ cd /sys/arch/arm64/conf
> $ cp GENERIC CUSTOM
> $ vi CUSTOM # added option DEBUG
>
On Sun, Sep 08, 2019 at 02:53:31PM +0200, Marcus MERIGHI wrote:
> Hello Jonathan!
>
> Thanks for the explanation and your work!
>
> j...@jsg.id.au (Jonathan Gray), 2019.09.08 (Sun) 04:05 (CEST):
> > Previously the drm code faked a 1024x768 fb if nothing was connected.
&g
On Sat, Sep 28, 2019 at 02:04:11AM -0700, Chris Bennett wrote:
> To: bugs@openbsd.org
> Subject: amdgpu crashes system at boot
> From: root
> Cc: root
> Reply-To: root
>
> >Synopsis:Diasbling amdgpu in UKC solves boot crash
> >Category:Firmware incompatibilty
> >Environment:
> System
On Tue, Oct 01, 2019 at 10:50:39AM +0200, Martin Ziemer wrote:
> >Synopsis:No acceleration and suspend on braswell, also some crashes
> >Environment:
> System : OpenBSD 6.6
> Details : OpenBSD 6.6-beta (DRMDEBUG) #0: Tue Oct 1 09:40:21 CEST
> 2019
>
On Thu, Oct 03, 2019 at 03:15:53PM +0200, k...@krot.org wrote:
> >Synopsis:startup suspends until display is connected
> >Category:kernel
> >Environment:
> System : OpenBSD 6.6
> Details : OpenBSD 6.6 (GENERIC.MP) #345: Wed Oct 2 22:45:02 MDT
> 2019
>
On Sat, Oct 12, 2019 at 08:31:07PM +, Zachary Buhman wrote:
> > Some bright sould decided to change the clock binding when RK3328
> > support was added to the mailine Linux kernel. But U-Boot still uses
> > an older clock binding. The OpenBSD kernel expects a device tree that
> > uses the new c
On Mon, Oct 14, 2019 at 08:10:36PM +0200, Sebastien Marie wrote:
> Hi,
>
> I recently tested OpenBSD on a system with a "ATI Radeon Vega", and I have
> problem on initialization: the system hangs.
>
> If I disable amdgpu* it boots fine.
>
> Here the dmesg of the system without firmware installed
201 - 300 of 503 matches
Mail list logo
