microSDXC can't recognized

Hi, Builtin microSDXC card device can't recognized in may machine[1]. Inserted it but nothing happened. Inserted card is SanDisk SDSQAR-128G-GNMA[2]. But in may another machine, it recognized da0: root@kazu:~ # uname -v FreeBSD 9.2-STABLE #5 r259404M: Mon Dec 16 00:12:52 JST 2013

kldxref: ...: Bad address.

This can't be good. make buildworld make buildkernel make installkernel ... ===> zlib (install) install -T release -o root -g wheel -m 555 zlib.ko /boot/kernel/ install -T debug -o root -g wheel -m 555 zlib.ko.debug /usr/lib/debug/boot/kernel/ kldxref /boot/kernel kldxref: error while

Wedge system == lost files

So, my system just wedge itself. No panic. No keyboard. No mouse. No remote login. Nothing. Just wedged. The system is FreeBSD 12.0-CURRENT r326432 Fri Dec 1 2017 amd64. Imagine my surprise when I rebooted system and the file I had been editing (and saving after every change) is gone.

Re: Insta-reset-bootloop with r328166 and vm.pmap.pcid_enabled=1

On 01/25/18 17:13, Konstantin Belousov wrote: > On Thu, Jan 25, 2018 at 04:58:04PM -0500, Ian FREISLICH wrote: >> Hi >> >> I cannot for the life of me recall why I had vm.pmap.pcid_enabled=1 set >> in loader.conf, but I did.  Most likely very historical reasons. >> >> r328166 and later reset

Re: Insta-reset-bootloop with r328166 and vm.pmap.pcid_enabled=1

On Thu, Jan 25, 2018 at 04:58:04PM -0500, Ian FREISLICH wrote: > Hi > > I cannot for the life of me recall why I had vm.pmap.pcid_enabled=1 set > in loader.conf, but I did.  Most likely very historical reasons. > > r328166 and later reset without dropping into the debugger during boot, > no

Insta-reset-bootloop with r328166 and vm.pmap.pcid_enabled=1

Hi I cannot for the life of me recall why I had vm.pmap.pcid_enabled=1 set in loader.conf, but I did.  Most likely very historical reasons. r328166 and later reset without dropping into the debugger during boot, no panic message. Ian -- Ian Freislich --

Re: pkg OSVERSION problem

On 25.01.2018 21:19, Ronald Klop wrote: > I know there should be multiple updates of packages. > Even with -o OSVERSION it does not give any new pkgs anymore. > What will help this? I've just had the same issue and solved it by forcefully updating the package database: # pkg -o

Re: pkg OSVERSION problem

Am Thu, 25 Jan 2018 21:19:06 +0100 "Ronald Klop" schrieb: > Hi, > > After I have an error about OSVERSION pkg upgrade says there is no update > anymore. > I know there should be multiple updates of packages. > Even with -o OSVERSION it does not give any new pkgs anymore.

Re: r327359: cylinder checksum failed: cg0, cgp: 0x4515d2a3 != bp: 0xd9fba319 Dec 30 23:29:24 <0.2>

Am Mon, 8 Jan 2018 09:12:16 -0700 Warner Losh schrieb: > On Jan 8, 2018 8:34 AM, "Mark Johnston" wrote: > > On Thu, Jan 04, 2018 at 09:10:37AM +0100, Michael Tuexen wrote: > > > On 31. Dec 2017, at 02:45, Warner Losh wrote: > > > > > > On

pkg OSVERSION problem

Hi, After I have an error about OSVERSION pkg upgrade says there is no update anymore. I know there should be multiple updates of packages. Even with -o OSVERSION it does not give any new pkgs anymore. What will help this? Regards, Ronald. [root@sjakie ~]# pkg upgrade Updating FreeBSD

Re: 12.0-CURRENT VM image won't mount USB flash drive

> Beginning with 12.0-CURRENT VM image: > > ?FreeBSD-12.0-CURRENT-amd64-20180118-r328126.vmdk.xz > > and continuing with 12.0-CURRENT VM image: > > FreeBSD-12.0-CURRENT-amd64-20180125-r328383.vmdk.xz > > when a USB flash drive

12.0-CURRENT VM image won't mount USB flash drive

Beginning with 12.0-CURRENT VM image:  FreeBSD-12.0-CURRENT-amd64-20180118-r328126.vmdk.xz and continuing with 12.0-CURRENT VM image: FreeBSD-12.0-CURRENT-amd64-20180125-r328383.vmdk.xz when a USB flash drive is present via the attached USB 3.0