On Tue, May 29, 2018 at 10:18 AM, Andriy Gapon wrote:
>
> [ping]
>
> On 21/05/2018 11:44, Andriy Gapon wrote:
> >
> > FreeBSD 12.0-CURRENT amd64 r332472
> > Does this panic ring a bell to anyone?
> > Has it already been fixed?
> > Thank you!
>
Is there any chance that r333703 fixes this problem
On 30 May 2018 at 18:08, Philip Homburg wrote:
>>Strange. Can you try an updated test image of mine
>>(https://people.freebsd.org/~emaste/mini-image-2018-05-28.xz)
Oops - that should have been
https://people.freebsd.org/~emaste/mini-image-2018-05-28-amd64.xz
But the most recent snapshot images h
On Wed, 30 May 2018 15:50:39 +, Glen Barber Wrote,
>Hi,
>
>
>Could folks please help boot-test the most recent 12.0-CURRENT amd64
>memstick images on various hardware? Note, this is not a request to
>install 12.0-CURRENT, only a boot-test with various system knobs tweaked.
>The most recent i
>Strange. Can you try an updated test image of mine
>(https://people.freebsd.org/~emaste/mini-image-2018-05-28.xz)
That gives a 404.
I have the strong suspision that your previous image doesn't get recognized as
bootable because the C/H/S values are not filled in.
___
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Am Thu, 24 May 2018 09:10:10 -0700 (PDT)
"Rodney W. Grimes" schrieb:
> -- Start of PGP signed section.
> > On Thu, May 24, 2018 at 08:22:12AM -0700, Rodney W. Grimes wrote:
> > > > On Wed, May 23, 2018 at 11:48:38AM +0200, Philip Homburg wrote:
On Sat, May 26, 2018 at 01:46:42PM +0200, Manuel Stühn wrote:
Since upgrading my Lenovo T450 from r333740 to r334167 I'm experiencing
several "Fatal traps 12". Before the update i did not have any of those.
In all cases the traps occured some time after resume.
I tried to debug this further by
Hi,
Could folks please help boot-test the most recent 12.0-CURRENT amd64
memstick images on various hardware? Note, this is not a request to
install 12.0-CURRENT, only a boot-test with various system knobs
tweaked.
The most recent images are available at:
https://download.freebsd.org/ftp/snapsho
On Wed, May 30, 2018 at 08:29:57AM -0700, Rodney W. Grimes wrote:
> > On 25 May 2018 at 04:51, Philip Homburg wrote:
> > >
> > > I have bad news and some good news.
> > >
> > > The bad news is that with this image the USB stick doesn't get recognized
> > > as
> > > a boot device. Same as with the
> On 25 May 2018 at 04:51, Philip Homburg wrote:
> >
> > I have bad news and some good news.
> >
> > The bad news is that with this image the USB stick doesn't get recognized as
> > a boot device. Same as with the 11.2-BETA2 images.
>
> At least it's not a regression.
>
> > The good news is that
On 25 May 2018 at 04:51, Philip Homburg wrote:
>
> I have bad news and some good news.
>
> The bad news is that with this image the USB stick doesn't get recognized as
> a boot device. Same as with the 11.2-BETA2 images.
At least it's not a regression.
> The good news is that if I completely rec
32b compat is quite different than i386 arch. It makes sense to
maintain 32b compat for quite a while.
On Wed, May 30, 2018 at 3:33 AM, Thomas Mueller wrote:
>> Wow, this blew up quite a lot bigger than I anticipated. I'll try to
>> summarize the discussion a bit below and then suggest a way fo
> Wow, this blew up quite a lot bigger than I anticipated. I'll try to
> summarize the discussion a bit below and then suggest a way forward.
> The primary reasons we want to do this is because there are conflicts between
> the new drm drivers in ports, and the drm drivers in base, since they con
12 matches
Mail list logo
