One extra datapoint - the machines which do not fail are the small DS1_v2
instances. These seem to boot fine, but if I move to the DS2 size then the
problem shows up.
-pete.
___
freebsd-stable@freebsd.org mailing list
> The variable still exists but is ignored when using ZFS.
>
> It's a known issue. You could try this patch:
> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D208882#c3
Ah, OK, thanks...
> Manually specifying the root pool should workaround the issue.
Interesting, I didnt think of trying
Pete French wrote:
> I have a number of machines in Azure, all booting from ZFS and, until
> the weekend, running 10.3 perfectly happily.
>
> I started upgrading these to 11. The first went fine, the second would
> not boot. Looking at the boot diagnistics it is
I have a number of machines in Azure, all booting from ZFS and, until
the weekend, running 10.3 perfectly happily.
I started upgrading these to 11. The first went fine, the second would
not boot. Looking at the boot diagnistics it is having problems finding the
root pool to mount. I see this is
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=213903
Cassiano Peixoto changed:
What|Removed |Added
CC|
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=213903
--- Comment #12 from Franco Fichtner ---
r301157 was backported to 10-STABLE, but 10.3 is unaffected. There is no
10.3-STABLE. Which one did you mean?
>From our experience r301157 is the bad commit as the panics
On 13-03-2017 14:12:00 Francisco Jose Candeias Figueiredo wrote:
>
> ###
> ### Access Denied
> ###
>
> #Status DateTime Door Card Name,Dep
> Card Rejected2017-03-10 16:57:46 NU--06P-02-CERT146 Welinton
> Lima,HELP DESK
>
>
> ###
> ### Access
Hello,
I've sent an email with the subject above by mistake
to FreeBSD Stable list, I'd like to ask the list
administrator to delete the whole email thread from
this list and archive.
I'm sorry,
Cordeiro
___
freebsd-stable@freebsd.org mailing list
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=213903
--- Comment #16 from Mateusz Guzik ---
Can you please reproduce with
https://people.freebsd.org/~mjg/patches/rwlock-debug-10.diff appliled on top.
E.g. like this:
cd /usr/src
fetch
> Le 13 mars 2017 à 19:09, Luiz Eduardo Roncato Cordeiro a
> écrit :
>
> Hello,
Hello,
> I've sent an email with the subject above by mistake
> to FreeBSD Stable list, I'd like to ask the list
> administrator to delete the whole email thread from
> this list and archive.
On 0313T1206, Pete French wrote:
> I have a number of machines in Azure, all booting from ZFS and, until
> the weekend, running 10.3 perfectly happily.
>
> I started upgrading these to 11. The first went fine, the second would
> not boot. Looking at the boot diagnistics it is having problems
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=213903
--- Comment #13 from Cassiano Peixoto ---
(In reply to Franco Fichtner from comment #12)
Hi Franco,
I don't know exactly which svn version i'm using, because when i run uname -a
it doesn't show me. But anyway i
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=213903
--- Comment #14 from Franco Fichtner ---
Hi Cassiano,
What's your output of uname -v?
Can you make sure to include a backtrace here from ddb? type "bt" at the prompt
when the panic happens. It may be related but not
When I try to do a snmpwalk of the BEGEMOT-WIRELESS-MIB I get the follwing on
the client side:
BEGEMOT-WIRELESS-MIB::wlanIfaceRegDomain."wlan2" = INTEGER: etsi(3)
Error in packet.
Reason: (genError) A general failure occured
Failed object: BEGEMOT-WIRELESS-MIB::wlanIfaceRegDomain."wlan2"
and on
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=213903
--- Comment #15 from Cassiano Peixoto ---
(In reply to Franco Fichtner from comment #14)
Hi Franco,
Here it is:
FreeBSD 10.3-STABLE #4: Mon Feb 6 09:29:52 BRST 2017
15 matches
Mail list logo