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 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
&g
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 - t
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 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 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 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
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
> >
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
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
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
>
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 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
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 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
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 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, 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 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
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
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 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 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 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 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).
> > > >
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
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 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(_lock, curcpu())
> == 0" failed: file
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 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 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 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
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 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, sho
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 :
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 b
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 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 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:
>
>
> 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
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
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
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
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
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 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
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 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 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
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 sna
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
>
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
>
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
On Fri, Oct 15, 2021 at 11:52:18PM +, Douglas Silva wrote:
> Yesterday I used "sysupgrade" to upgrade my RPI4 from OpenBSD 6.9 to 7.0, and
> now it's booting to the "ddb" prompt. A clean install was also not possible
> because the installation media won't even boot. It's the same panic
On Sat, Oct 02, 2021 at 04:02:55PM +0200, ASC wrote:
>
>
> I found out the issue could be reproduced by ffplay'ing one of the
> OpenBSD's songs.
> I have applied your patch and compiled my own kernel, the issue
> seems to be gone.
thanks, committed
On Fri, Oct 01, 2021 at 08:27:48AM +0200, ASC wrote:
> >Synopsis: Dropped in an empty tty randomly
> >Category: system
> >Environment:
> System : OpenBSD 7.0
> Details : OpenBSD 7.0 (GENERIC.MP) #231: Mon Sep 27 17:23:17 MDT 2021
>
On Wed, Sep 22, 2021 at 09:30:25AM +0200, o...@omarpolo.com wrote:
> >Synopsis:drm errors in dmesg and X freezes
> >Category:system
> >Environment:
> System : OpenBSD 7.0
> Details : OpenBSD 7.0 (GENERIC.MP) #221: Sat Sep 18 11:37:50 MDT
> 2021
>
On Fri, Sep 10, 2021 at 04:16:37AM +0200, Andreas Drewke wrote:
> Hi,
>
> I just gave OpenBSD 6.9 PowerPC a shot on my G5 macppc. Its a dual 2.0 GHZ
> G5.
> Unfortunaty the Radeon X1950 crashes OpenBSD kernel on PowerMac G5.
>
> Its a proper OFW flashed X1950.
>
> Any idea? Would love to hear
On Thu, Sep 09, 2021 at 09:34:51AM +0100, Laurence Tratt wrote:
> `man 7 term` contains the following:
>
> Terminal type descriptions are stored as files of capability data
> underneath /usr/share/terminfo. To browse a list of all terminal names
> recognized by the system, do
>
>
On Wed, Sep 08, 2021 at 12:05:55PM -0500, joshua stein wrote:
> On Thu, 09 Sep 2021 at 00:52:32 +1000, Jonathan Gray wrote:
> > On Wed, Sep 08, 2021 at 09:37:08AM -0500, joshua stein wrote:
> > > On Wed, 08 Sep 2021 at 14:48:26 +0100, Stuart Henderson wrote:
> > >
On Wed, Sep 08, 2021 at 09:37:08AM -0500, joshua stein wrote:
> On Wed, 08 Sep 2021 at 14:48:26 +0100, Stuart Henderson wrote:
> > On 2021/09/08 15:33, Alex Fedorov wrote:
> > > Hello.
> > >
> > > This is bug with load DMC firmware i915/kbl_dmc_ver1_04.bin
> >
> > Is the file
On Tue, Jul 27, 2021 at 03:17:35PM +0200, Mark Kettenis wrote:
> > Date: Tue, 27 Jul 2021 11:38:20 +1000
> > From: Jonathan Gray
> >
> > On Mon, Jul 26, 2021 at 08:45:24AM +0100, Edd Barrett wrote:
> > > Hi,
> > >
> > > I upgraded my snaps
On Mon, Jul 26, 2021 at 08:45:24AM +0100, Edd Barrett wrote:
> Hi,
>
> I upgraded my snapshot last week and the machine no longer suspends. I
> don't know exactly which snap caused this, as I hadn't been upgrading
> snaps very frequently.
>
> Upon running `zzz` from a terminal emulator, the
On Fri, Jul 23, 2021 at 02:32:33PM +0200, Mark Kettenis wrote:
> > Date: Fri, 23 Jul 2021 13:13:27 +0200
> > From: Marcus Glocker
> >
> > On Thu, 22 Jul 2021 23:44:54 +0200
> > Marcus Glocker wrote:
> >
> > > On Thu, 22 Jul 2021 23:07:30 +0200 (CEST)
> > > Mark Kettenis wrote:
> > >
> > > >
On Tue, Jul 20, 2021 at 08:44:28PM +, Seamus Hartnett wrote:
> I'm using the latest snapshot amd64. When trying to suspend the system (zzz),
> the kernel panics. Before the drm update, there was no kernel panic in the
> process of suspending the system.
Without a dmesg it is unclear what
On Tue, Jul 13, 2021 at 10:11:29PM +0100, Tom Murphy wrote:
> Hi Jonathan,
>
> On Tue, Jul 13, 2021 at 01:13:03PM +1000, Jonathan Gray wrote:
> > On Mon, Jul 12, 2021 at 06:22:36PM +, Tom Murphy wrote:
> > > I had firefox open (various tabs/windows) and was playin
On Thu, Jun 17, 2021 at 09:48:47AM +0400, Michel von Behr wrote:
> Hi @jsg - great, do you think it could be useful if I try to test this 5.10
> drm on my machine… ?
The 5.10 drm was committed and should be in snapshots by now.
On Thu, Jul 08, 2021 at 09:07:41AM -0400, Josh Rickmar wrote:
> On Thu, Jul 08, 2021 at 04:53:34PM +1000, Jonathan Gray wrote:
> > On Wed, Jul 07, 2021 at 11:02:27AM -0400, Josh Rickmar wrote:
> > > With latest amd64 snapshot on my Thinkpad E485 I'm only seeing a
> > >
On Wed, Jul 07, 2021 at 11:02:27AM -0400, Josh Rickmar wrote:
> With latest amd64 snapshot on my Thinkpad E485 I'm only seeing a
> black screen when using X. xenodm is still running, and with some
> finger memory I can still log in and run various X applications, but
> none of it is visible.
>
>
On Fri, Jun 18, 2021 at 11:01:16AM +0200, Peter N. M. Hansteen wrote:
> On Thu, Jun 17, 2021 at 06:02:06PM +0200, Peter N. M. Hansteen wrote:
> > On Thu, Jun 17, 2021 at 04:30:49PM +0200, Peter N. M. Hansteen wrote:
> > > For various non-interesting reasons I ran with the last sysupgraded
> > >
On Fri, Jun 18, 2021 at 02:01:58AM -0400, Brad Smith wrote:
> On Wed, Jun 16, 2021 at 11:52:48PM -0400, Brad Smith wrote:
> > On Wed, Jun 16, 2021 at 07:46:03PM -0700, Evan Littmann wrote:
> > > I'll see if I have an adapter that works.
> > >
> > > I took a photo of the screen and ran it through
On Thu, Jun 17, 2021 at 09:44:14AM +0200, Mark Kettenis wrote:
> > Date: Wed, 16 Jun 2021 23:52:47 -0400
> > From: Brad Smith
> >
> > On Wed, Jun 16, 2021 at 07:46:03PM -0700, Evan Littmann wrote:
> > > I'll see if I have an adapter that works.
> > >
> > > I took a photo of the screen and ran
On Thu, Jun 17, 2021 at 09:30:05AM +0200, Peter Nicolai Mathias Hansteen wrote:
>
>
> > 17. jun. 2021 kl. 07:34 skrev Jonathan Gray :
> >
> > There is better tiger lake support in the 5.10 drm I'm working on. I am
> > trying to resolve some regressions on
There is better tiger lake support in the 5.10 drm I'm working on. I am
trying to resolve some regressions on older hardware before merging it.
On Thu, Jun 17, 2021 at 08:58:21AM +0400, Michel von Behr wrote:
> (Sorry, I sent to misc@ this bug message by mistake - sending to bugs@ now)
>
>
On Sat, Jun 12, 2021 at 12:57:25AM -0400, Ashton Fagg wrote:
> Hello,
>
> I just experienced a freeze on my laptop (Thinkpad T14s) which required a
> hard reboot.
>
> Upon coming back up, unfortunately the only clues I could recover as to
> what happened was (from /var/log/messages):
>
> Jun 12
On Tue, Jun 08, 2021 at 09:17:35PM +, Jerome Kasper wrote:
> >On Tue, Jun 08, 2021 at 01:51:21PM +, Jerome Kasper wrote:
> >> Hello bugs@
> >>
> >> Since i'm following -current i lately encountered drm issues with my
> >> graphic
> >> card that doesn't attach anymore while it was working
On Tue, Jun 08, 2021 at 01:51:21PM +, Jerome Kasper wrote:
> Hello bugs@
>
> Since i'm following -current i lately encountered drm issues with my graphic
> card that doesn't attach anymore while it was working on 6.9-stable.
> sysupgrade -s done today and still having the issue.
> Non
On Tue, Jun 01, 2021 at 07:43:27PM +0200, Matthias Pressfreund wrote:
> Ok, here you go ...
>
> In approx. 4 out of 10 times the boot process does not conclude.
Thanks. I believe the "use drm_mm from linux 5.7.y" changes are
implicated in this though there is nothing cherryview/braswell
On Mon, May 31, 2021 at 02:39:36PM +, Chris Jones wrote:
> Synopsis: After upgrading to OpenBSD 6.9 or doing a fresh install I get a
> kernel panic after a reboot
> Category: kernel
> Environment:
>
> System : OpenBSD 6.9
> Details : OpenBSD 6.9 (GENERIC.MP) #473: Mon Apr 19 10:40:28 MDT
On Mon, May 31, 2021 at 02:38:34PM +0200, Matthias Pressfreund wrote:
> After applying the diffs you sent on 2021-05-17 and 2021-05-27, I
> booted the new kernel which completed until the login prompt. On
> the way I got this:
>
> ...
> scsibus2 at vscsi0: 256 targets
> softraid0 at root
>
On Mon, May 31, 2021 at 10:18:45PM +0200, Peter N. M. Hansteen wrote:
> All issues resolved with help from Bryan Steele, Jonathan Gray and
> Stefan Sperling.
>
> dmesg, sendbug and pcidump output attached.
>
> Thanks again for all your help!
>
> All the best,
> Pete
On Sat, May 29, 2021 at 05:34:50PM +0200, Peter N. M. Hansteen wrote:
> And just for completeness, git diff output follows attached along with
> fresh sendbug output.
>
> All the best,
> Peter
moved slightly to keep it sorted
Index: sys/dev/pci/azalia.c
On Sat, May 22, 2021 at 01:11:07PM -0700, Greg Steuck wrote:
> Jonathan Gray writes:
>
> > As with otto's earlier problem there is likely something wrong
> > with sys/dev/pci/drm/i915/display/intel_gmbus.c or the way linux style
> > i2c is handled in drm_linux.c.
> &
On Wed, May 26, 2021 at 11:50:36AM +1000, Jonathan Gray wrote:
> On Wed, May 26, 2021 at 02:51:53AM +0200, Peter N. M. Hansteen wrote:
> > Somewhat encouraged by the last few weeks' adventure with ASUS
> > laptops (thanks, kettenis@!) I decided to try out an incrementally
> &g
On Wed, May 26, 2021 at 02:51:53AM +0200, Peter N. M. Hansteen wrote:
> Somewhat encouraged by the last few weeks' adventure with ASUS
> laptops (thanks, kettenis@!) I decided to try out an incrementally
> higher range model, the Zenbook S.
>
> The latest amd64 snapshot installer seemed to work
On Thu, May 20, 2021 at 11:51:13PM -0700, Greg Steuck wrote:
> Jonathan Gray writes:
>
> > On Sun, Mar 21, 2021 at 04:01:50PM -0700, Greg Steuck wrote:
> >> I noticed we saw variations of this before. This hit my X1 9th gen when
> >> waking up with a 4k monitor att
On Sun, Mar 21, 2021 at 04:01:50PM -0700, Greg Steuck wrote:
> I noticed we saw variations of this before. This hit my X1 9th gen when
> waking up with a 4k monitor attached via HDMI connector. FWIW, the
> screen is mirrored between the built-in panel and the big monitor.
x1c gen8 not gen9
On Thu, May 20, 2021 at 09:53:02AM +0200, Peter N. M. Hansteen wrote:
> On Thu, May 20, 2021 at 08:53:14AM +1000, Jonathan Gray wrote:
> > On Wed, May 19, 2021 at 06:32:01PM +0200, Peter N. M. Hansteen wrote:
> > > On Wed, May 19, 2021 at 04:43:44PM +0200, Peter N.
On Thu, May 20, 2021 at 10:10:14AM +0200, Matthieu Herrb wrote:
> On Thu, May 20, 2021 at 09:53:02AM +0200, Peter N. M. Hansteen wrote:
> > On Thu, May 20, 2021 at 08:53:14AM +1000, Jonathan Gray wrote:
> > > On Wed, May 19, 2021 at 06:32:01PM +0200, Peter N. M. Hansteen wrote:
&
On Wed, May 19, 2021 at 06:32:01PM +0200, Peter N. M. Hansteen wrote:
> On Wed, May 19, 2021 at 04:43:44PM +0200, Peter N. M. Hansteen wrote:
> > > outdated...)
> >
> > I tried the first, that only seemed to have the effect of having
> > the freeze come faster. So I commented out that part of the
On Wed, May 19, 2021 at 08:14:32AM +0200, Janne Johansson wrote:
> Not a huge amount of info available from the virtualization env, but
> something in CPU detection broke down. Will try snap/6.8 too, but for
> now, this is what the serial console gives me:
>
On Tue, May 04, 2021 at 03:44:54PM +0200, m...@fn.de wrote:
> Thanks for the quick help. I built a kernel with your fix.
> The system is booting up with a warning, now.
>
> ...
> scsibus3 at softraid0: 256 targets
> sd2 at scsibus3 targ 1 lun 0:
> sd2: 122103MB, 512 bytes/sector, 250067198
On Wed, May 05, 2021 at 04:47:50PM -0500, Scott Cheloha wrote:
> Hi,
>
> On a hunch I added additional parameter checks to task_add(9) and
> task_del(9) and caught intel(4) doing something strange.
>
> The patch is straightforward: check that the taskq pointer tq is not
> NULL. In the current
On Tue, May 04, 2021 at 10:27:05AM +0200, Matthias Pressfreund wrote:
> >Environment:
> System : OpenBSD 6.9
> Details : OpenBSD 6.9 (GENERIC.MP) #473: Mon Apr 19 10:40:28 MDT
> 2021
>
>
On Fri, Apr 30, 2021 at 01:51:11PM +0200, Peter N. M. Hansteen wrote:
> On Fri, Apr 30, 2021 at 12:00:05PM +1000, Jonathan Gray wrote:
> >
> > If you can build a kernel on another machine try
> >
> >
On Thu, Apr 29, 2021 at 10:27:49PM +0200, Peter Nicolai Mathias Hansteen wrote:
> I just spent the evening trying to work around an odd error that happens
> after an apparently straightforward install on a new laptop.
>
> The most useful info I can offer is that the install proceeds with no
>
On Tue, Mar 09, 2021 at 01:41:25AM -0700, Anthony J. Bentley wrote:
> Hi,
>
> When updating a port I came across a weird compile error within iostream
> if _POSIX_C_SOURCE is set. 200112 and 200809 both error out in different
> ways.
This looks like the same problem as
On Sat, Feb 20, 2021 at 02:13:26PM +0100, Benjamin Baier wrote:
> This is just a heads up, that i'm hitting a stubbed out function.
>
> While testing a port update (love2d)
> Not quite sure how, the only GEM related ioctl, that is called,
> is DRM_IOCTL_GEM_CLOSE according to ktrace.
The
101 - 200 of 447 matches
Mail list logo
