microSDXC can't recognized

[KIRIYAMA Kazuhiko]

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 
ad...@kazu.pis:/usr/obj/usr/src/sys/GENERIC 
root@kazu:~ # dmesg | tail -10
ugen4.3:  at usbus4
umass0:  on 
usbus4
umass0:  SCSI over Bulk-Only; quirks = 0x4001
umass0:1:0:-1: Attached to scbus1
da0 at umass-sim0 bus 0 scbus1 target 0 lun 0
da0:  Removable Direct Access SCSI-0 device 
da0: Serial Number 058F63666433
da0: 40.000MB/s transfers
da0: 121942MB (249737216 512 byte sectors: 255H 63S/T 15545C)
da0: quirks=0x2
root@kazu:~ # 

My machine in question is r328126 and it's dmesg is [3]. The
cause is either my SD card adaptor phisically collapsed or
r328126 does not work. BTW I've added pciconf:

root@t:~ # pciconf -lv
hostb0@pci0:0:0:0:  class=0x06 card=0x72708086 chip=0x22808086 rev=0x36 
hdr=0x00
vendor = 'Intel Corporation'
device = 'Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Series 
SoC Transaction Register'
class  = bridge
subclass   = HOST-PCI
vgapci0@pci0:0:2:0: class=0x03 card=0x72708086 chip=0x22b08086 rev=0x36 
hdr=0x00
vendor = 'Intel Corporation'
device = 'Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Series 
PCI Configuration Registers'
class  = display
subclass   = VGA
none0@pci0:0:3:0:   class=0x048000 card=0x72708086 chip=0x22b88086 rev=0x36 
hdr=0x00
vendor = 'Intel Corporation'
device = 'Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Series 
Imaging Unit'
class  = multimedia
none1@pci0:0:11:0:  class=0x118000 card=0x72708086 chip=0x22dc8086 rev=0x36 
hdr=0x00
vendor = 'Intel Corporation'
device = 'Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Series 
Power Management Controller'
class  = dasp
xhci0@pci0:0:20:0:  class=0x0c0330 card=0x72708086 chip=0x22b58086 rev=0x36 
hdr=0x00
vendor = 'Intel Corporation'
device = 'Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Series 
USB xHCI Controller'
class  = serial bus
subclass   = USB
none2@pci0:0:26:0:  class=0x108000 card=0x72708086 chip=0x22988086 rev=0x36 
hdr=0x00
vendor = 'Intel Corporation'
device = 'Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Series 
Trusted Execution Engine'
class  = encrypt/decrypt
isab0@pci0:0:31:0:  class=0x060100 card=0x72708086 chip=0x229c8086 rev=0x36 
hdr=0x00
vendor = 'Intel Corporation'
device = 'Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Series 
PCU'
class  = bridge
subclass   = PCI-ISA
root@t:~ # 

Best regards.

[1] https://www.biccamera.com/bc/item/3716011/
[2] http://kakaku.com/item/K0001002985/
[3] http://ds.truefc.org/~kiri/freebsd/sg116j/dmesg.boot

---
KIRIYAMA Kazuhiko
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

kldxref: ...: Bad address.

[Steve Kargl]

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 reading /boot/kernel/accf_data.ko: Bad address
kldxref: error while reading /boot/kernel/amr_linux.ko: Bad address
kldxref: error while reading /boot/kernel/chacha20.ko: Bad address
kldxref: error while reading /boot/kernel/cxgb_t3fw.ko: Bad address
kldxref: error while reading /boot/kernel/if_cc.ko: Bad address
kldxref: error while reading /boot/kernel/if_ccv.ko: Bad address
kldxref: error while reading /boot/kernel/if_cxl.ko: Bad address
kldxref: error while reading /boot/kernel/if_cxlv.ko: Bad address
kldxref: error while reading /boot/kernel/ipmi_linux.ko: Bad address
kldxref: error while reading /boot/kernel/nfslock.ko: Bad address
kldxref: error while reading /boot/kernel/nfssvc.ko: Bad address
kldxref: error while reading /boot/kernel/ng_nat.ko: Bad address
kldxref: error while reading /boot/kernel/pflog.ko: Bad address
kldxref: error while reading /boot/kernel/plip.ko: Bad address
kldxref: error while reading /boot/kernel/pty.ko: Bad address
kldxref: error while reading /boot/kernel/rc4.ko: Bad address
kldxref: error while reading /boot/kernel/rdrand_rng.ko: Bad address
kldxref: error while reading /boot/kernel/udf_iconv.ko: Bad address

-- 
Steve
20170425 https://www.youtube.com/watch?v=VWUpyCsUKR4
20161221 https://www.youtube.com/watch?v=IbCHE-hONow
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Wedge system == lost files

[Steve Kargl]

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.  /usr/lost+found is empty.  The file pl19-21.tex is
gone along with a few files from latex.

-rw-r--r--  1 kargl  kargl  -  0 Jan 25 14:53 pl19-21.aux
-rw-r--r--  1 kargl  kargl  -  0 Jan 25 14:53 pl19-21.log
-rw-r--r--  1 kargl  kargl  -  0 Jan 25 14:53 pl19-21.out
-rw-r--r--  1 kargl  kargl  -  0 Jan 25 14:53 pl19-21.pdf
-rw-r--r--  1 kargl  kargl  -  0 Jan 25 14:52 pl19-21.tex

/dev/ada0p5 on /usr (ufs, local, journaled soft-updates)

Are there known issues with SUJ, again? 

-- 
Steve
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

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

[Ian FREISLICH]

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 without dropping into the debugger during boot,
>> no panic message.
> Yes, this is how it is currently behaves.
> PCID can be used to optimize PTI, see https://reviews.freebsd.org/D13985.
> It is used for very differrent algorithm when PTI=1, comparing with PTI=0.

Maybe there should be an "interlock" on these knobs, although judging
from the number of reports I'm the only that shot my foot.

Ian

-- 
Ian Freislich

-- 

___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

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

[Konstantin Belousov]

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 panic message.

Yes, this is how it is currently behaves.
PCID can be used to optimize PTI, see https://reviews.freebsd.org/D13985.
It is used for very differrent algorithm when PTI=1, comparing with PTI=0.
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

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

[Ian FREISLICH]

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


-- 

___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: pkg OSVERSION problem

[Jan Kokemüller]

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 OSVERSION=1200056 update -f
# pkg -o OSVERSION=1200056 upgrade


-Jan
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: pkg OSVERSION problem

[O. Hartmann]

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.
> What will help this?
> 
> Regards,
> Ronald.
> 
> 
> [root@sjakie ~]# pkg upgrade
> Updating FreeBSD repository catalogue...
> Fetching meta.txz: 100%944 B   0.9kB/s00:01
> Fetching packagesite.txz: 100%6 MiB   3.0MB/s00:02
> Processing entries:   0%
> pkg: Newer FreeBSD version for package pear-HTML_Template_IT:
> - package: 1200056
> - running kernel: 1200054
> pkg: repository FreeBSD contains packages for wrong OS version:  
> FreeBSD:12:amd64
> Processing entries: 100%
> Unable to update repository FreeBSD
> Error updating repositories!
> 
> [root@sjakie ~]# pkg upgrade
> Updating FreeBSD repository catalogue...
> FreeBSD repository is up to date.
> All repositories are up to date.
> Checking for upgrades (15 candidates): 100%
> Processing candidates (15 candidates): 100%
> Checking integrity... done (0 conflicting)
> Your packages are up to date.
> 
> [root@sjakie ~]# pkg -o OSVERSION=1200056 upgrade
> Updating FreeBSD repository catalogue...
> FreeBSD repository is up to date.
> All repositories are up to date.
> Checking for upgrades (15 candidates): 100%
> Processing candidates (15 candidates): 100%
> Checking integrity... done (0 conflicting)
> Your packages are up to date.
> ___
> freebsd-current@freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-current
> To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

me, too. I saw the same thing last week, when I tried the first time to update 
a CURRENT
and I saw it again on Monday. Funny: when I sync the base repository (built on 
another
machine due to performance issue and rysnc'ed), the initial error about the OS 
mismatch
occurs one time again and the disappears - as decribed above.

Regards,

Oliver

-- 
O. Hartmann

Ich widerspreche der Nutzung oder Übermittlung meiner Daten für
Werbezwecke oder für die Markt- oder Meinungsforschung (§ 28 Abs. 4 BDSG).


pgp4wg3lDMKwI.pgp
Description: OpenPGP digital signature

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

[O. Hartmann]

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 Sat, Dec 30, 2017 at 4:41 PM, O. Hartmann   
> wrote:
> > >  
> > >> On most recent CURRENT I face the error shwon below on /tmp filesystem
> > >> (UFS2) residing
> > >> on a Samsung 850 Pro SSD:
> > >>
> > >> UFS /dev/gpt/tmp (/tmp) cylinder checksum failed: cg 0, cgp:  
> 0x4515d2a3 !=
> > >> bp: 0xd9fba319
> > >> handle_workitem_freefile: got error 5 while accessing filesystem
> > >> UFS /dev/gpt/tmp (/tmp) cylinder checksum failed: cg 0, cgp: 0x4515d2a3
> > >> != bp: 0xd9fba319
> > >> handle_workitem_freefile: got error 5 while accessing filesystem
> > >> UFS /dev/gpt/tmp (/tmp) cylinder checksum failed: cg 0, cgp: 0x4515d2a3
> > >> != bp: 0xd9fba319
> > >> handle_workitem_freefile: got error 5 while accessing filesystem
> > >> UFS /dev/gpt/tmp (/tmp) cylinder checksum failed: cg 0, cgp: 0x4515d2a3
> > >> != bp: 0xd9fba319
> > >> handle_workitem_freefile: got error 5 while accessing filesystem
> > >> UFS /dev/gpt/tmp (/tmp) cylinder checksum failed: cg 0, cgp: 0x4515d2a3
> > >> != bp: 0xd9fba319
> > >> handle_workitem_freefile: got error 5 while accessing filesystem
> > >>
> > >> I've already formatted the /tmp filesystem, but obviously without any
> > >> success.
> > >>
> > >> Since I face such strange errors also on NanoBSD images dd'ed to SD  
> cards,
> > >> I guess there
> > >> is something fishy ...  
> > >
> > >
> > > It indicates a problem. We've seen these 'corruptions' on data in  
> motion at
> > > work, but I hacked fsck to report checksum mismatches (it silently  
> corrects
> > > them today) and we've not seen any mismatch when we unmount and fsck the
> > > filesystem.  
> > Not sure this helps: But we have seen this also after system panics
> > when having soft update journaling enabled. Having soft update journaling
> > disabled, we do not observed this after several panics.
> > Just to be clear: The panics are not related to this issue,
> > but to other network development we do.  
> 
> I saw the same issue this morning on a mirrored root filesystem after my
> workstation came up following a power failure. fsck recovered using the
> journal, and I subsequently saw a number of these checksum failures.
> Upon shutdown, I saw the same handle_workitem_freefile errors as above.
> I then ran a full fsck from single-user mode, which didn't turn up any
> inconsistencies, and after that the checksum failure errors disappeared,
> presumably because fsck fixed them.
> 
> 
> Yes. Fsck automatically fixes issues like that. It does it silently. I have
> patched to make it noisy, and the dozen cases I saw the errors, fsck was
> silent with my whiny patches. I can put them up for review if people want...
> 
> Warner


within the past couple of weeks - or since the first occurence of these strange 
reports,
I have had mysterious crashes: when installing FreeBSD even the proper 
(recommended) way,
the box suddenly crashes out of the blue. The symptoms are always the same and 
the result
is also always the same: the box is unusable, the boot process is stuck at BTX 
halted
with a list of dumped CPU registers (I guess it is the CPU registers) and the 
filesystem
is corrupt. I have had this strange problem on several hosts with SSDs - I 
reported end
November/beginning of December 2017 of those crashes. On on machine I refomated 
the SSD
and did a playback from ab 'dump'-backup - since then those crashes went away. 
The box
now in question is the last of them not being traeted that way. it seems, there 
is
somewhere/somehow a minefield hidden and I have no clue what it could be :-(

I'm going to do the very same soon with the SSD of the remaining box - dump and 
restore.

I just wanted to note this for the record.

The crash happend with  FreeBSD 12.0-CURRENT #14 r328409: Thu Jan 25 20:40:27 
CET amd64.

Kind regards,

Oliver
2018 

-- 
O. Hartmann

Ich widerspreche der Nutzung oder Übermittlung meiner Daten für
Werbezwecke oder für die Markt- oder Meinungsforschung (§ 28 Abs. 4 BDSG).


pgpU4VFBWnucP.pgp
Description: OpenPGP digital signature

pkg OSVERSION problem

[Ronald Klop]

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 repository catalogue...
Fetching meta.txz: 100%944 B   0.9kB/s00:01
Fetching packagesite.txz: 100%6 MiB   3.0MB/s00:02
Processing entries:   0%
pkg: Newer FreeBSD version for package pear-HTML_Template_IT:
- package: 1200056
- running kernel: 1200054
pkg: repository FreeBSD contains packages for wrong OS version:  
FreeBSD:12:amd64

Processing entries: 100%
Unable to update repository FreeBSD
Error updating repositories!

[root@sjakie ~]# pkg upgrade
Updating FreeBSD repository catalogue...
FreeBSD repository is up to date.
All repositories are up to date.
Checking for upgrades (15 candidates): 100%
Processing candidates (15 candidates): 100%
Checking integrity... done (0 conflicting)
Your packages are up to date.

[root@sjakie ~]# pkg -o OSVERSION=1200056 upgrade
Updating FreeBSD repository catalogue...
FreeBSD repository is up to date.
All repositories are up to date.
Checking for upgrades (15 candidates): 100%
Processing candidates (15 candidates): 100%
Checking integrity... done (0 conflicting)
Your packages are up to date.
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

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

[Rodney W. Grimes]

> 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 controller
> the console hangs for 10-12 minutes during boot and then emits the
> error messages seen in the attachment.
> 
> The UFS filesystem on the USB flash drive cannot be mounted.
> 
> If the USB flash drive is connected via the attached USB 2.0
> controller, everything is good.
> 
> This problem is not manifested in any 10.4-STABLE or 11.1-STABLE VM
> images.
> 
> The host system is CentOS EL7 7.1708.
> 
> VirtualBox version is 5.2.6.
> 
> The USB 3.0 controller uses a VIA chipset.
> 
> System is for test purposes only, so it is easy to try anything that
> might help resolve this problem.

I think I hit this the other night, and just chocked it off to
some problem on my set up.  I plugged a USB stick into a build
box to splat a Chromebook-Snow/arm image on and nota, the usb
stick did not show up.

I just unplugged it and plugged it into another socket without
looking and boom, it showed up.  Now that I go look at where
I was plugging this in the first connector was a USB 3.0, the
second was a USB 2.0.

The machine is running FreeBSD-12.0-CURRENT-amd64-20180118-r328126

> Thanks.
> David Boyd <david.boy...@twc.com>

-- 
Rod Grimes rgri...@freebsd.org
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

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

[David Boyd]

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 controller
the console hangs for 10-12 minutes during boot and then emits the
error messages seen in the attachment.

The UFS filesystem on the USB flash drive cannot be mounted.

If the USB flash drive is connected via the attached USB 2.0
controller, everything is good.

This problem is not manifested in any 10.4-STABLE or 11.1-STABLE VM
images.

The host system is CentOS EL7 7.1708.

VirtualBox version is 5.2.6.

The USB 3.0 controller uses a VIA chipset.

System is for test purposes only, so it is easy to try anything that
might help resolve this problem.


Thanks.

David Boyd <david.boy...@twc.com>

___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"