I've been doing a bunch of packing building today on my Ryzen box and
just got this kernel panic near the start of a poudriere run:
13.0-CURRENT FreeBSD 13.0-CURRENT r340358 GENERIC amd64
[00:00:08] Processing PRIORITY_BOOST
[00:00:08] Balancing pool
[00:00:08] Recording filesystem state for
Perfect! Sounds like we are on the right track, at least.
Best,
Conrad
On Tue, Nov 13, 2018 at 8:55 PM Rebecca Cran wrote:
>
> On Tuesday, 13 November 2018 21:41:58 MST Conrad Meyer wrote:
> > You know what, I wonder if you're running into the CUR_TEMP_RANGE_SEL?
> > I.e., sometimes the CPU
On Tuesday, 13 November 2018 21:41:58 MST Conrad Meyer wrote:
> You know what, I wonder if you're running into the CUR_TEMP_RANGE_SEL?
> I.e., sometimes the CPU chooses to report on a range from 0-225C and
> sometimes -49C-206C. I think someone else's 2990WX did the same
> thing. I guess that
Please try r340426 :-).
On Tue, Nov 13, 2018 at 8:41 PM Conrad Meyer wrote:
>
> You know what, I wonder if you're running into the CUR_TEMP_RANGE_SEL?
> I.e., sometimes the CPU chooses to report on a range from 0-225C and
> sometimes -49C-206C. I think someone else's 2990WX did the same
>
You know what, I wonder if you're running into the CUR_TEMP_RANGE_SEL?
I.e., sometimes the CPU chooses to report on a range from 0-225C and
sometimes -49C-206C. I think someone else's 2990WX did the same
thing. I guess that patch never landed? 102°C - 49°C is the very
reasonable 53°C.
Yeah,
On Tue, Nov 13, 2018 at 8:29 PM Rebecca Cran wrote:
>
> On Tuesday, 13 November 2018 21:17:59 MST Conrad Meyer wrote:
>
> > Maybe it should be -54 instead of +54? 183-(54*2) is the somewhat
> > plausible 75?C (still pretty warm even for load). How good is your
> > cooling solution?
>
> D'oh, of
On Tuesday, 13 November 2018 21:17:59 MST Conrad Meyer wrote:
> Maybe it should be -54 instead of +54? 183-(54*2) is the somewhat
> plausible 75?C (still pretty warm even for load). How good is your
> cooling solution?
D'oh, of course it's -54 instead of +54 (For some reason I presumed a
On Tue, Nov 13, 2018 at 8:05 PM Rebecca Cran wrote:
>
> On Tuesday, 13 November 2018 16:20:22 MST Stefan Ehmann wrote:
>
> > The 2700 has an offset of 0 though (2700X has 10).
> > And I'm seeing a difference of more than 30 degrees. I guess something
> > else must be happening here.
>
> I had
On Tue, Nov 13, 2018 at 7:16 PM Daniel Eischen wrote:
>
> On Tue, 13 Nov 2018, Conrad Meyer wrote:
>
> > On Tue, Nov 13, 2018 at 6:26 PM Daniel Eischen wrote:
> >> I've attached it. If it gets filtered by the mail list, I'll
> >> make it http accessible.
> >
> > Thanks Daniel.
> >
> > It looks
On Tuesday, 13 November 2018 16:20:22 MST Stefan Ehmann wrote:
> The 2700 has an offset of 0 though (2700X has 10).
> And I'm seeing a difference of more than 30 degrees. I guess something
> else must be happening here.
I had thought 54 was the right offset for my 2990WX system, but now it's
On Tuesday, 13 November 2018 18:57:25 MST Kyle Evans wrote:
> However, because loader-land is funny in a not-ha-ha kind of way, can
> you try replacing loader.efi on your guest VM with the Forth-flavored
> version to rule that out or narrow it down, please?
That didn't help.
As probably
On Tue, 13 Nov 2018, Conrad Meyer wrote:
On Tue, Nov 13, 2018 at 6:26 PM Daniel Eischen wrote:
I've attached it. If it gets filtered by the mail list, I'll
make it http accessible.
Thanks Daniel.
It looks like your hostbridge zero device has a different device id
than in my first
Of course, Johannes has already thought of this! See
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=228480 and
https://reviews.freebsd.org/D15567 .
On Tue, Nov 13, 2018 at 6:41 PM Conrad Meyer wrote:
>
> On Tue, Nov 13, 2018 at 6:26 PM Daniel Eischen wrote:
> > I've attached it. If it gets
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=227191
Kubilay Kocak changed:
What|Removed |Added
Summary|Cannot check battery status |Cannot check battery status
On Tue, Nov 13, 2018 at 6:26 PM Daniel Eischen wrote:
> I've attached it. If it gets filtered by the mail list, I'll
> make it http accessible.
Thanks Daniel.
It looks like your hostbridge zero device has a different device id
than in my first generation Ryzen system. Would you please try the
On Tue, 13 Nov 2018, Conrad Meyer wrote:
Hi Daniel,
On Tue, Nov 13, 2018 at 10:01 AM Daniel Eischen wrote:
Greetings,
I'm trying to track down a couple of things. amdtemp doesn't
report any temperature sensors, and acpi seems to have some
errors. Not sure if they are related.
Maybe
On Tue, Nov 13, 2018 at 5:15 PM Subbsd wrote:
>
> Hi,
>
>
>
> On Tue, Nov 13, 2018 at 7:22 PM Rodney W. Grimes
> wrote:
> >
> > Uh oh, ok, thats not what I was thinking of then. I do not have any
> > bhyve capable hardware running on 12BETA at this time to test with.
> >
> > I wonder if we have
On Tue, Nov 13, 2018 at 5:15 PM Rozhuk Ivan wrote:
>
> On Tue, 13 Nov 2018 19:41:47 -0500
> Daniel Eischen wrote:
>
> > >> I'm trying to track down a couple of things. amdtemp doesn't
> > >> report any temperature sensors, and acpi seems to have some
> > >> errors. Not sure if they are
On Tue, 13 Nov 2018 19:41:47 -0500
Daniel Eischen wrote:
> >> I'm trying to track down a couple of things. amdtemp doesn't
> >> report any temperature sensors, and acpi seems to have some
> >> errors. Not sure if they are related.
> >
> > It s a bit legacy )
> > Try mine:
Hi Daniel,
On Tue, Nov 13, 2018 at 10:01 AM Daniel Eischen wrote:
>
> Greetings,
>
> I'm trying to track down a couple of things. amdtemp doesn't
> report any temperature sensors, and acpi seems to have some
> errors. Not sure if they are related.
Maybe not. If they do not attach, it
> On Nov 13, 2018, at 2:06 PM, Rozhuk Ivan wrote:
>
> On Tue, 13 Nov 2018 12:59:59 -0500 (EST)
> Daniel Eischen wrote:
>
>> I'm trying to track down a couple of things. amdtemp doesn't
>> report any temperature sensors, and acpi seems to have some
>> errors. Not sure if they are related.
>
On 11/13/18 10:14 PM, Conrad Meyer wrote:
> On Tue, Nov 13, 2018 at 1:04 PM Stefan Ehmann wrote:
>> After kldload amdtemp I see the following sysctls:
>> dev.cpu.0.temperature: 77.1C
>> dev.amdtemp.0.core0.sensor0: 77.1C
>>
>> The temperature I see in BIOS is much lower (maybe around 40.0C).
On 11/13/18 10:40 PM, Daniel Eischen wrote:
>
>> On Nov 13, 2018, at 4:02 PM, Stefan Ehmann wrote:
>>
>>> On 11/13/18 8:59 PM, Daniel Eischen wrote:
On Tue, 13 Nov 2018, Greg V wrote:
On Tue, Nov 13, 2018 at 8:59 PM, Daniel Eischen
wrote:
> Greetings,
>
Hi,
On Tue, Nov 13, 2018 at 7:22 PM Rodney W. Grimes
wrote:
>
> Uh oh, ok, thats not what I was thinking of then. I do not have any
> bhyve capable hardware running on 12BETA at this time to test with.
>
> I wonder if we have a bad interaction between the loader and
> bhyve again, we have had
In message
, Warner Losh writes:
>On a raw device it would be translated into a BIO_DELETE command directly,
>correct?
We already have ioctl(DIOCGDELETE) for that. newfs(8) uses it.
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
p...@freebsd.org | TCP/IP since RFC
On Tue, Nov 13, 2018 at 2:59 PM Alan Somers wrote:
>
> On Tue, Nov 13, 2018 at 3:51 PM Conrad Meyer wrote:
>>
>> On Tue, Nov 13, 2018 at 2:10 PM Alan Somers wrote:
>> > ...
>> > 8) Add aio_freesp(2), an asynchronous version of fcntl(F_FREESP).
>>
>> Why not just add DIOCGDELETE support to
On Tue, Nov 13, 2018 at 3:52 PM Conrad Meyer wrote:
> Geom devices have the DIOCGDELETE ioctl, which translates into
> BIO_DELETE (which is TRIM, as I understand it).
>
Correct. TRIM is both the catch-all term people use, as well as the name of
a specific DSM (data set management) command in
On Tue, Nov 13, 2018 at 3:51 PM Warner Losh wrote:
>
>
> On Tue, Nov 13, 2018 at 3:10 PM Alan Somers wrote:
>
>> Hole-punching has been discussed on these lists before[1]. It basically
>> means to turn a dense file into a sparse file by deallocating storage for
>> some of the blocks in the
On Tue, Nov 13, 2018 at 3:51 PM Conrad Meyer wrote:
> Hi Alan,
>
> On Tue, Nov 13, 2018 at 2:10 PM Alan Somers wrote:
> >
> > Hole-punching has been discussed on these lists before[1]. It basically
> > means to turn a dense file into a sparse file by deallocating storage for
> > some of the
On Tue, 13 Nov 2018 13:14:46 -0800
Conrad Meyer wrote:
> You can adjust dev.amdtemp.N.sensor_offset as needed. By default, the
> amdtemp sysctl gives you the unadjusted value. On different Ryzen
> models the raw value is wrong by different amounts. E.g. on my 1950X,
> I have sensor_offset set
Hi Alan,
On Tue, Nov 13, 2018 at 2:10 PM Alan Somers wrote:
>
> Hole-punching has been discussed on these lists before[1]. It basically
> means to turn a dense file into a sparse file by deallocating storage for
> some of the blocks in the middle. There's no standard API for it. Linux
> uses
On Tue, Nov 13, 2018 at 3:10 PM Alan Somers wrote:
> Hole-punching has been discussed on these lists before[1]. It basically
> means to turn a dense file into a sparse file by deallocating storage for
> some of the blocks in the middle. There's no standard API for it. Linux
> uses
Hole-punching has been discussed on these lists before[1]. It basically
means to turn a dense file into a sparse file by deallocating storage for
some of the blocks in the middle. There's no standard API for it. Linux
uses fallocate(2); Solaris and OSX add a new opcode to fcntl(2).
A related
> On Nov 13, 2018, at 4:02 PM, Stefan Ehmann wrote:
>
>> On 11/13/18 8:59 PM, Daniel Eischen wrote:
>>> On Tue, 13 Nov 2018, Greg V wrote:
>>>
>>>
>>>
>>> On Tue, Nov 13, 2018 at 8:59 PM, Daniel Eischen
>>> wrote:
Greetings,
I'm trying to track down a couple of things.
On Tue, Nov 13, 2018 at 1:04 PM Stefan Ehmann wrote:
> After kldload amdtemp I see the following sysctls:
> dev.cpu.0.temperature: 77.1C
> dev.amdtemp.0.core0.sensor0: 77.1C
>
> The temperature I see in BIOS is much lower (maybe around 40.0C). Don't
> know if just the offset is wrong or the
On 11/13/18 8:59 PM, Daniel Eischen wrote:
> On Tue, 13 Nov 2018, Greg V wrote:
>
>>
>>
>> On Tue, Nov 13, 2018 at 8:59 PM, Daniel Eischen
>> wrote:
>>> Greetings,
>>>
>>> I'm trying to track down a couple of things. amdtemp doesn't
>>> report any temperature sensors, and acpi seems to have
On Mon, Nov 12, 2018 at 11:54 PM, Alex McKeever
wrote:
The CD or DVD show up fine in the device selection screen, but it
won’t even boot the disc. What changed from 11.2 to 12.0 in regards
to PowerPC Macs that are 32 bit?
I've been able to boot various 12-CURRENT builds on my iBook G4
On Tue, 13 Nov 2018, Greg V wrote:
On Tue, Nov 13, 2018 at 8:59 PM, Daniel Eischen wrote:
Greetings,
I'm trying to track down a couple of things. amdtemp doesn't
report any temperature sensors, and acpi seems to have some
errors. Not sure if they are related.
These are the ACPI-related
On Tue, Nov 13, 2018 at 8:59 PM, Daniel Eischen
wrote:
Greetings,
I'm trying to track down a couple of things. amdtemp doesn't
report any temperature sensors, and acpi seems to have some
errors. Not sure if they are related.
These are the ACPI-related warnings and errors during boot.
On Tue, 13 Nov 2018 12:59:59 -0500 (EST)
Daniel Eischen wrote:
> I'm trying to track down a couple of things. amdtemp doesn't
> report any temperature sensors, and acpi seems to have some
> errors. Not sure if they are related.
It s a bit legacy )
Try mine:
Greetings,
I'm trying to track down a couple of things. amdtemp doesn't
report any temperature sensors, and acpi seems to have some
errors. Not sure if they are related.
These are the ACPI-related warnings and errors during boot.
Firmware Warning (ACPI): Optional FADT field
41 matches
Mail list logo
