On 18/02/2018 04:35, Gleb Smirnoff wrote:
> Andriy,
>
> On Sun, Feb 18, 2018 at 12:54:21AM +0200, Andriy Gapon wrote:
> A> > Today's rebuild has given me uptimes of below an hour, usually. The box
> will stay up in single user mode long enough to rebuild world/kernel, but
> multi-user it is
On 02/18/18 05:14, Ian FREISLICH wrote:
On 02/17/18 22:48, Warner Losh wrote:
On Feb 17, 2018 8:24 PM, "Ian FREISLICH"
>
wrote:
Hi
Since devmatch some of my USB devices no longer get their drivers
loaded.
On 02/17/18 22:48, Warner Losh wrote:
> On Feb 17, 2018 8:24 PM, "Ian FREISLICH"
> >
> wrote:
>
> Hi
>
> Since devmatch some of my USB devices no longer get their drivers
> loaded. It's not clear from UPDATING
On Feb 17, 2018 8:24 PM, "Ian FREISLICH"
wrote:
Hi
Since devmatch some of my USB devices no longer get their drivers
loaded. It's not clear from UPDATING whether I needed to do anything
beyond building and installing kernel and world as well as updating
/etc.
Hi
Since devmatch some of my USB devices no longer get their drivers
loaded. It's not clear from UPDATING whether I needed to do anything
beyond building and installing kernel and world as well as updating
/etc. There was reference to removing /etc/devd/usb.conf in another
thread but its
Andriy,
On Sun, Feb 18, 2018 at 12:54:21AM +0200, Andriy Gapon wrote:
A> > Today's rebuild has given me uptimes of below an hour, usually. The box
will stay up in single user mode long enough to rebuild world/kernel, but
multi-user it is panicking at
[Some more information added, from /usr/libexec/kgdb use.]
On 2018-Feb-17, at 5:39 PM, Mark Millard wrote:
> This is for FreeBSD running under Hyper-V on a Windows 10 Pro machine.
> The FreeBSD "disk" bindings are to SSDs, not the insides of NTFS files.
> 29 logical processors assigned to
Hi everyone,
My attempts to build FreeBSD 12-current have been failing as of yesterday
with the error below. This problem persists with current at the time of
writing this email (r329497).
Given llvm was updated to 6.0 around that time, I suspect it is related:
This is for FreeBSD running under Hyper-V on a Windows 10 Pro machine.
The FreeBSD "disk" bindings are to SSDs, not the insides of NTFS files.
29 logical processors assigned to FreeBSD (on a 32-thread Ryzen
Threadripper 1950X). No other Hyper-V use.
This happened during:
#
On Sat, Feb 17, 2018 at 12:52 PM, Andrew Reilly wrote:
> I've applied the patch, and the boot process is quiet now, but it's still
> loading cc_vegas.ko, seemingly in response to seeing this device: (from
> pciconf -l -v)
>
> none4@pci0:17:0:2: class=0x108000
On 17/02/2018 14:16, Andrew Reilly wrote:
> Today's rebuild has given me uptimes of below an hour, usually. The box will
> stay up in single user mode long enough to rebuild world/kernel, but
> multi-user it is panicking at
> /usr/src/sys/cddl/contrib/opensolaris/uts/common/fs/zfs/dmu.c:1592
>
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=218849
jtkoert...@gmail.com changed:
What|Removed |Added
CC||jtkoert...@gmail.com
---
I've applied the patch, and the boot process is quiet now, but it's still
loading cc_vegas.ko, seemingly in response to seeing this device: (from pciconf
-l -v)
none4@pci0:17:0:2: class=0x108000 card=0x14561022 chip=0x14561022 rev=0x00
hdr=0x00
vendor = 'Advanced Micro Devices,
On 02/17/18 16:15, Warner Losh wrote:
I've done that with my systems here...
If you can reliably reproduce it, booting a kernel with 'options
DA_TRACK_REFS=2' in the kernel config and send me the output?
Warner
I have a reproduction. I'll send you the photo off-list.
--HPS
On Sat, Feb 17, 2018 at 8:06 AM, Hans Petter Selasky
wrote:
> On 02/17/18 15:58, Warner Losh wrote:
>
>> USB WAS ABSOLUTELY TESTED. I rebooted my machine several times, unloaded
>> drivers, etc. It all just worked for me.
>>
>> Please don't make snide comments like this, along
On Sat, Feb 17, 2018 at 8:04 AM, Hans Petter Selasky
wrote:
> On 02/17/18 15:47, Warner Losh wrote:
>
>> That's interesting. What did you do to get there? There's some code path
>> that's unholding the periph without first holding it. I've been trying to
>> find a scenario.
>>
On 02/17/18 15:47, Warner Losh wrote:
That's interesting. What did you do to get there? There's some code path
that's unholding the periph without first holding it. I've been trying to
find a scenario.
I just booted into single user mode with a multi-card USB reader
attached. Seems like some
On 02/17/18 15:58, Warner Losh wrote:
USB WAS ABSOLUTELY TESTED. I rebooted my machine several times, unloaded
drivers, etc. It all just worked for me.
Please don't make snide comments like this, along with drive by commits to
devmatch without even discussing the problems with me. It's really
On 17/02/2018 14:16, Andrew Reilly wrote:
> Today's rebuild has given me uptimes of below an hour, usually. The box will
> stay up in single user mode long enough to rebuild world/kernel, but
> multi-user it is panicking at
> /usr/src/sys/cddl/contrib/opensolaris/uts/common/fs/zfs/dmu.c:1592
>
>
On Sat, Feb 17, 2018 at 6:31 AM, Hans Petter Selasky
wrote:
> On 02/17/18 11:38, Alex V. Petrov wrote:
>
>> 12.0-CURRENT #12 r329446M: Sat Feb 17 17:11:05 +07 2018:
>> on boot multilines:
>>
>> devmatch: Malformed NOMATCH string: ''?''
>>
>>
> Can you try these two patches:
>
>
That's interesting. What did you do to get there? There's some code path
that's unholding the periph without first holding it. I've been trying to
find a scenario.
Warner
On Sat, Feb 17, 2018 at 5:01 AM, Hans Petter Selasky
wrote:
> I've started to hit this panic with USB
On 02/17/18 15:22, Alex V. Petrov wrote:
Sorry, prev msg this only afrer one patch.
Now is all OK.
There is one more, but not so important:
https://svnweb.freebsd.org/changeset/base/329458
Thank for your testing!
--HPS
___
On 02/17/18 14:51, Greg V wrote:
On 01/20/2018 12:18, Hans Petter Selasky wrote:
On 01/20/18 00:17, Greg V via freebsd-net wrote:
On 01/19/2018 12:54, Hans Petter Selasky wrote:
On 01/18/18 14:11, Greg V wrote:
Hi. I've upgraded CURRENT from December 19
Sorry, prev msg this only afrer one patch.
Now is all OK.
17.02.2018 21:18, Hans Petter Selasky пишет:
> On 02/17/18 14:51, Alex V. Petrov wrote:
>> devmatch: Malformed NOMATCH string: ''?'' persists
>>
>>
>
> Did you reinstall /etc ?
>
> --HPS
>
>
--
-
Alex.
On 02/17/18 14:51, Alex V. Petrov wrote:
devmatch: Malformed NOMATCH string: ''?'' persists
Did you reinstall /etc ?
--HPS
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe,
On 01/20/2018 12:18, Hans Petter Selasky wrote:
On 01/20/18 00:17, Greg V via freebsd-net wrote:
On 01/19/2018 12:54, Hans Petter Selasky wrote:
On 01/18/18 14:11, Greg V wrote:
Hi. I've upgraded CURRENT from December 19
devmatch: Malformed NOMATCH string: ''?'' persists
17.02.2018 20:31, Hans Petter Selasky пишет:
> On 02/17/18 11:38, Alex V. Petrov wrote:
>> 12.0-CURRENT #12 r329446M: Sat Feb 17 17:11:05 +07 2018:
>> on boot multilines:
>>
>> devmatch: Malformed NOMATCH string: ''?''
>>
>
> Can you try these
On 02/17/18 11:38, Alex V. Petrov wrote:
12.0-CURRENT #12 r329446M: Sat Feb 17 17:11:05 +07 2018:
on boot multilines:
devmatch: Malformed NOMATCH string: ''?''
Can you try these two patches:
https://svnweb.freebsd.org/changeset/base/329455
https://svnweb.freebsd.org/changeset/base/329456
On 02/17/18 13:42, Hans Petter Selasky wrote:
On 02/17/18 13:16, Andrew Reilly wrote:
On a side-note, the new devmatch workings are giving me 43 boot
warnings about "Malformed NOMATCH string: ''?'', and
devmatch_enable="NO" in /etc/rc.conf doesn't seem to help, and the new
matching is very
On 02/17/18 13:16, Andrew Reilly wrote:
On a side-note, the new devmatch workings are giving me 43 boot warnings about "Malformed
NOMATCH string: ''?'', and devmatch_enable="NO" in /etc/rc.conf doesn't seem to
help, and the new matching is very very keen to load cc_vegas.ko, a lot. Here's the
Hi,
I do a weekly build to track changes, on 12-current since I gave my fileserver
this new Ryzen motherboard a few months ago. I switched to current because
there was some badness in 11-stable that I attributed to new processor
twitchiness (wouldn't reboot, temperature sensors not working.)
I've started to hit this panic with USB mass storage, before even the
device has become in-use:
panic: Unholding 4 with cnt = 0
Backtrace:
vpanic()
panic()
daprobedone()
dadone()
xpt_done_process()
xpt_done_td()
fork_exit()
fork_trampoline()
db>
static inline void
da_periph_unhold(struct
12.0-CURRENT #12 r329446M: Sat Feb 17 17:11:05 +07 2018:
on boot multilines:
devmatch: Malformed NOMATCH string: ''?''
mouse don't start
13.02.2018 19:50, Hans Petter Selasky пишет:
> On 02/13/18 10:47, Jakob Alvermark wrote:
>> +1
>>
>> My USB mouse was working fine before the switch to
33 matches
Mail list logo