Update 11.3 > 11.4
jerry at seibercom.net
Fri Jun 19 11:20:27 UTC 2020
On Thu, 18 Jun 2020 18:55:24 -0400, Aryeh Friedman stated:
>On Thu, Jun 18, 2020 at 6:45 PM Jerry <jerry at seibercom.net> wrote:
>> On Fri, 19 Jun 2020 08:19:12 +1000, Dewayne Geraghty commented:
>> >Aryeh's suggestion of determining the cause of the problem would be
>> >beneficial as the PR
>> >appears to be caught in a non-reproducability trap. Eg "I have an X
>> >on version Y and no bug" will not allay anyone's concerns.
>> >Also reply 103 asserts that this problem doesn't exist on 11 (ie
>> >prior to 11.4). Perhaps pulling the iso's for 11.4 and using on a
>> >machine that reproduces the bug with 12.1 might be a more efficient
>> It doesn't exist on 11.x at ll. If you read through the comments,
>> etcetera, it was mentioned that it is most likely a regression
>> problem. Regression bugs have a nasty habit of spreading.
>Especially if people refuse to actual test it to see if it is a bug or
>not on their system. Since it is not on mine my test is meaningless
>but your might not be and might help debug it so if you care about
>helping the community like you do you should try it and make a
>complete bug report as possible. But as I said it happens in enough
>odd different places that it is 90% likely user error not an actual
>bug and you just falling for FUD if you are not willing to help figure
I can confirm that the bug exists on at least a Dell XPS 8930 with 32
GB RAM and Intel i3 Processor. The machine was purchased as a low-end
replacement for a PC that was dying. Its sole purpose was to run a
lightly used web-server and mail-server.
I can confirm that it works with every version of 11.x and no versions
of 12.x. I have never tested it on 10.x or 13.x however.
I have went to the lengths of using the manufacturers disk to erase and
format the HD and resetting the BIOS to defaults. I never messed with
the defaults anyway.
The error starts as soon as the CD attempts to boot-up FreeBSD 12.x.
Assuming, incorrectly, that the disk was bad I did a fresh download and
burned a new CD. The sane problem existed.
This is not a user error. More than one person on more than one
platform is experiencing this bug. I contacted Dell technical support.
They confirmed that the bug exists, there is even a reference to it on
their community bulletin board. They went on to say that their product
was tested against Windows 10 and passed,(obviously) and against Linux
and worked as intended. They stated that they DO NOT test against or
guarantee their products will work with FreeBSD. They were also aware
that a bug report had been filed against it in the FreeBSD Bugzilla. I
really wish I had been made aware of it too. I made the suggestion that
they list OSs that their equipment will not work with. They nicely
stated that an operation of that extent would be beyond the scope of
their technical department since their are potentially hundreds of
thousands of individual configurations. I suggested that they test
against a base OS installation, but they declined saying they do not
test against FreeBSD. They would welcome me doing it though. Since they
declined to supply me with their equipment free of charge to undertake
this endeavor, I declined.
The saying, "If you are not part of the solution, you are part of the
problem", is certainly apropos to you in this incident.
>> >Hans is clearly doing his best to address the issue but needs
>> >helpful information from our active community.
>> This bug has existed since at least 2019-04-30 04:22:45 EDT when it
>> was first reported.
>> >Regards, Dewayne
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Size: 488 bytes
Desc: OpenPGP digital signature
More information about the freebsd-questions