Re: new computer, strange usb messages at boot

On 02/20/16 06:19, Larry Rosenman wrote: ugen0.2: at usbus0 Root mount waiting for: usbus0 usbd_setup_device_desc: getting device descriptor at addr 2 failed, USB_ERR_IOERROR Root mount waiting for: usbus0 usbd_setup_device_desc: getting device descriptor at addr 2 failed, USB_ERR_IOERROR Root

Re: Realtek MMC/MMCSD reader?

On Fri, 19 Feb 2016 23:02:26 -0600 Larry Rosenman wrote: > On 2016-02-19 22:25, Gary Corcoran wrote: > > On 2/19/2016 11:08 PM, Larry Rosenman wrote: > >> On 2016-02-19 22:05, Mehmet Erol Sanliturk wrote: > >>> On Fri, Feb 19, 2016 at 7:58 PM, Larry Rosenman > >>> wrote: > >>> > Gre

Possible bug in bc(1)

Hello, I'm getting strange result with something looking like valid data: [rm@smsh-zfs ~]> bc 2*1\ 2*1 24 I'd expect the output being like that: 2*1\ 2 2*1 2 What I see in bc(1) man-page regarding to backslash is: "The sequence ‘\’ is ignored within numbers." So looks like it doesn't actually

Re: [Bug 207366] openssh do not generate dsa host key by default

fyi 2016年2月20日 7:13 PM， 写道： > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=207366 > > Bug ID: 207366 >Summary: openssh do not generate dsa host key by default >Product: Base System >Version: 11.0-CURRENT > Hardware: arm >

Re: Possible bug in bc(1)

Hi, actually, if you "ignore \ within numbers", your input reads 2*12*1, doesn't it? W. Am 20.02.2016 um 12:07 schrieb Ruslan Makhmatkhanov: > Hello, > > I'm getting strange result with something looking like valid data: > > [rm@smsh-zfs ~]> bc > 2*1\ > 2*1 > 24 > > I'd expect the output bein

Re: new computer, strange usb messages at boot

On Fri, Feb 19, 2016 at 11:19:51PM -0600, Larry Rosenman wrote: > Does any of this look weird? What can I provide to help? > Sleeping on "acmtx" with the following non-sleepable locks held: > exclusive sleep mutex intr sources (intr sources) r = 0 (0x81c7f630) > locked @ /usr/src/sys/x86

Re: new computer, strange usb messages at boot

On Sat, Feb 20, 2016 at 10:25:31AM +0100, Hans Petter Selasky wrote: > On 02/20/16 06:19, Larry Rosenman wrote: > > ugen0.2: at usbus0 > > Root mount waiting for: usbus0 > > usbd_setup_device_desc: getting device descriptor at addr 2 failed, > > USB_ERR_IOERROR > > Root mount waiting for: usbus0

Re: new computer, strange usb messages at boot

On Sat, Feb 20, 2016 at 02:04:01PM +0200, Konstantin Belousov wrote: > On Fri, Feb 19, 2016 at 11:19:51PM -0600, Larry Rosenman wrote: > > Does any of this look weird? What can I provide to help? > > > Sleeping on "acmtx" with the following non-sleepable locks held: > > exclusive sleep mutex intr

LOR: ZFS/syncer: on mount of msdosfs

Is this a known LOR: lock order reversal: 1st 0xf801d20ea5f0 zfs (zfs) @ /usr/src/sys/kern/vfs_mount.c:1222 2nd 0xf801d2fe6418 syncer (syncer) @ /usr/src/sys/kern/vfs_subr.c:2618 stack backtrace: #0 0x80a7f810 at witness_debugger+0x70 #1 0x80a7f711 at witness_checkorder

HWPMC on SkyLake

Is there anything I can do to help: hwpc_core: unknown PMC architecture: 4 hwpmc: SOFT/16/64/0x67 CPU: Intel(R) Core(TM) i7-6700HQ CPU @ 2.60GHz (2592.13-MHz K8-class CPU) Origin="GenuineIntel" Id=0x506e3 Family=0x6 Model=0x5e Stepping=3 Features=0xbfebfbff Features2=0x7ffafbbf

Re: Realtek MMC/MMCSD reader?

On Fri, Feb 19, 2016 at 11:25:45PM -0500, Gary Corcoran wrote: > > On 2/19/2016 11:08 PM, Larry Rosenman wrote: > > On 2016-02-19 22:05, Mehmet Erol Sanliturk wrote: > >> On Fri, Feb 19, 2016 at 7:58 PM, Larry Rosenman wrote: > >> > >>> Great. Since I've never done that > >>> > >>> Any ideas

sr-iov issues, reset_hw() failed with error -100

Decided to do some testing with iovctl to see how sr-iov is coming along. Currently when adding the vf's there are a couple errors, and the network no longer function after iovctl is started. My guess is the reset_hw() call that is failing. Any ideas why this call would fail? I tested this on both