On Mon, 28 Mar 2016 08:47:35 +0300
Aleksander Alekseev wrote:
> > What's the output of these commands?:
> >
> > freebsd-version
> > uname -r
> > uname -a
> > grep "define __FreeBSD_version" /usr/include/sys/param.h
> >
>
> $ freebsd-version
> 10.2-RELEASE
>
> $ uname -r
> 11.0-CURRENT
>
>
> It used to be FreeBSD 10.2 but I rebuilded and reinstall kernel and
> world from CURRENT according to Handbook instructions. I have exact
> steps recorded in case it would help. I hope such way of upgrading
> FreeBSD is correct?
I think I realized what's going on. I probably rebuilded the world
Ian Lepore wrote on 03/28/16 05:29 AM:
[...]
I updated to r297281 with this quirk applied. Sadly, it doesn't
change
anything - controllers still not recognized. I also tried to boot
this
revision with disabled hw.sdhci.enable_msi=0, that I applied earlier.
I finally found some time today to
Unfortunately, the serial console only seemed to be echoing characters
in quasi-random spurts, yielding such things as:
...
r() at lcpu_initcpu_initclocks_bsp+0x37f/frame 0x820dbb40
initclocks() at initclocks+0x20/frame 0x820dbb50
mi_start+0x2c
Tracing td 0xffc_et_start+0x2d9/fra
On Mon, Mar 28, 2016 at 05:36:13AM -0700, David Wolfskill wrote:
> Unfortunately, the serial console only seemed to be echoing characters
> in quasi-random spurts, yielding such things as:
>
> ...
> r() at lcpu_initcpu_initclocks_bsp+0x37f/frame 0x820dbb40
> initclocks() at initclocks+0x20
On Mon, Mar 28, 2016 at 03:57:01PM +0300, Konstantin Belousov wrote:
> ...
> Also, does anything change with the faulting kernel if you set
> hw.lapic_tsc_deadline to 0 in loader ?
Yes: the machine then boots succesfully:
freebeast(11.0-C)[1] uname -a
FreeBSD freebeast.catwhisker.org 11.0-CURRENT
> I think I realized what's going on. I probably rebuilded the world on
> two different machines but forgot to do it on this one. I will
> re-check this and report results a bit later.
OK, here is a problem. I can't upgrade the world because of compile
errors I mentioned before:
http://lpaste.net
On Mon, 2016-03-28 at 12:33 +0300, Ruslan Makhmatkhanov wrote:
> Ian Lepore wrote on 03/28/16 05:29 AM:
>
> [...]
>
> > > I updated to r297281 with this quirk applied. Sadly, it doesn't
> > > change
> > > anything - controllers still not recognized. I also tried to boot
> > > this
> > > revision
Ian Lepore wrote on 03/28/16 06:38 PM:
On Mon, 2016-03-28 at 12:33 +0300, Ruslan Makhmatkhanov wrote:
Ian Lepore wrote on 03/28/16 05:29 AM:
[...]
I updated to r297281 with this quirk applied. Sadly, it doesn't
change
anything - controllers still not recognized. I also tried to boot
this
revi
Recently upgraded to r297351, once running iovctl -C -f /etc/iovctl.conf
everything appears to work as it should. The main network interface ramains
connected and pinging works fine.
iovctl.conf
PF {
device : ix1;
num_vfs : 31;
}
DEFAULT {
passthrough : true;
}
VF-0 {
On 28 Mar, O. Hartmann wrote:
> Am Sat, 26 Mar 2016 14:26:45 -0700 (PDT)
> Don Lewis schrieb:
>
>> On 26 Mar, Michael Butler wrote:
>> > -current is not great for interactive use at all. The strategy of
>> > pre-emptively dropping idle processes to swap is hurting .. big time.
>> >
>> > Compare
On Mon, 28 Mar 2016 17:00:31 +0300
Aleksander Alekseev wrote:
> > I think I realized what's going on. I probably rebuilded the world on
> > two different machines but forgot to do it on this one. I will
> > re-check this and report results a bit later.
>
> OK, here is a problem. I can't upgrad
On Tue, 29 Mar 2016 00:42:09 +0200
Gary Jennejohn wrote:
> On Mon, 28 Mar 2016 17:00:31 +0300
> Aleksander Alekseev wrote:
>
> > > I think I realized what's going on. I probably rebuilded the world on
> > > two different machines but forgot to do it on this one. I will
> > > re-check this and r
On 28 Mar 2016, at 16:00, Aleksander Alekseev wrote:
>
>> I think I realized what's going on. I probably rebuilded the world on
>> two different machines but forgot to do it on this one. I will
>> re-check this and report results a bit later.
>
> OK, here is a problem. I can't upgrade the world
Vitalij,
here is latest version of the patch. If you already run the
previous one, no need to switch to this one, keep running as is.
The update covers only FreeBSD 4 and i386 compatibilties.
current@, a review is appreciated. The patch not only fixes a
recent bug, but also fixes a long stand
Dear FreeBSD Community,
The deadline for the next FreeBSD Quarterly Status update is April 7,
2016, for work done in January through March -- less than two weeks away!
Status report submissions do not have to be very long. They may be about
anything happening in the FreeBSD project and community
On Mon, 28 Mar 2016 14:52:09 -0700 (PDT)
Don Lewis wrote:
> On 28 Mar, O. Hartmann wrote:
> > Am Sat, 26 Mar 2016 14:26:45 -0700 (PDT)
> > Don Lewis schrieb:
> >
> >> On 26 Mar, Michael Butler wrote:
> >> > -current is not great for interactive use at all. The strategy of
> >> > pre-emptive
17 matches
Mail list logo
