Audio Transcription Service Provider
___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Kernel crash while deleting vimage jail
I would like to report a kernel crash while tearing down a VIMAGE-based
jail.This can be reproduced consistently. Thanks.
---
Fatal trap 12: page fault while in kernel mode
cpuid = 4; apic id = 08
fault virtual address = 0xa8
fault code = supervisor read data, page not present
instruction pointer = 0x20:0x80dfddd4
stack pointer = 0x28:0xfe08606b5960
frame pointer = 0x28:0xfe08606b59b0
code segment = base 0x0, limit 0xf, type 0x1b
= DPL 0, pres 1, long 1, def32 0, gran 1
processor eflags = interrupt enabled, resume, IOPL = 0
current process = 3788 (jail)
trap number = 12
panic: page fault
cpuid = 4
KDB: stack backtrace:
#0 0x80b416b7 at kdb_backtrace+0x67
#1 0x80afa697 at vpanic+0x177
#2 0x80afa513 at panic+0x43
#3 0x80f9314f at trap_fatal+0x35f
#4 0x80f931a9 at trap_pfault+0x49
#5 0x80f92984 at trap+0x2d4
#6 0x80f7272c at calltrap+0x8
#7 0x80dfee16 at uma_zdestroy+0x36
#8 0x80cfdb92 at tcp_destroy+0x132
#9 0x80c15b8c at vnet_destroy+0x13c
#10 0x80ac52f0 at prison_deref+0x2b0
#11 0x80ac6bc4 at sys_jail_remove+0x364
#12 0x80f941d8 at amd64_syscall+0xa38
#13 0x80f7300d at fast_syscall_common+0x101
Uptime: 3m53s
---
(kgdb) list *0x80dfddd4
0x80dfddd4 is in zone_dtor (uma_int.h:331).
326 static inline uma_keg_t
327 zone_first_keg(uma_zone_t zone)
328 {
329 uma_klink_t klink;
330
331 klink = LIST_FIRST(>uz_kegs);
332 return (klink != NULL) ? klink->kl_keg : NULL;
333 }
334
335 #undef UMA_ALIGN
Current language: auto; currently minimal
---
(kgdb) backtrace
#0 doadump (textdump=) at pcpu.h:230
#1 0x80afa2ab in kern_reboot (howto=260)
at /usr/src/sys/kern/kern_shutdown.c:383
#2 0x80afa6d1 in vpanic (fmt=,
ap=) at /usr/src/sys/kern/kern_shutdown.c:776
#3 0x80afa513 in panic (fmt=)
at /usr/src/sys/kern/kern_shutdown.c:707
#4 0x80f9314f in trap_fatal (frame=0xfe08606b58a0, eva=168)
at /usr/src/sys/amd64/amd64/trap.c:877
#5 0x80f931a9 in trap_pfault (frame=0xfe08606b58a0, usermode=0)
at pcpu.h:230
#6 0x80f92984 in trap (frame=0xfe08606b58a0)
at /usr/src/sys/amd64/amd64/trap.c:415
#7 0x80f7272c in calltrap ()
at /usr/src/sys/amd64/amd64/exception.S:231
#8 0x80dfddd4 in zone_dtor (arg=0x0, size=1664, udata=0x0)
at /usr/src/sys/vm/uma_core.c:1691
#9 0x80dfee16 in uma_zdestroy (zone=0x0)
at /usr/src/sys/vm/uma_core.c:2920
#10 0x80cfdb92 in tcp_destroy (unused=)
at /usr/src/sys/netinet/tcp_subr.c:749
#11 0x80c15b8c in vnet_destroy (vnet=0xf800273612c0)
at /usr/src/sys/net/vnet.c:596
#12 0x80ac52f0 in prison_deref (pr=0x81a331d0, flags=23)
at /usr/src/sys/kern/kern_jail.c:2647
#13 0x80ac6bc4 in sys_jail_remove (td=,
uap=) at /usr/src/sys/kern/kern_jail.c:2270
#14 0x80f941d8 in amd64_syscall (td=0xf80058f54620, traced=0)
at subr_syscall.c:132
#15 0x80f7300d in fast_syscall_common ()
at /usr/src/sys/amd64/amd64/exception.S:494
#16 0x000800ea2a4a in ?? ()
---
sm5018a> uname -a
FreeBSD sm5018a.intranet.peyto.ca 11.2-STABLE FreeBSD 11.2-STABLE #0
r337832: We
d Aug 15 17:19:31 MDT 2018 samu...@sm5018a.intranet.peyto.ca:/usr/obj/usr/sr
c/sys/SERVERS11 amd64
---
sm5018a> cat SERVERS11
include GENERIC
ident SERVERS
options ROUTETABLES=16
options VIMAGE
options TCP_RFC7413
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Targeted Global B2B Companies emails list
Hi, I just wanted to check if you would be interested in a list of Managed Service Providers (MSPs) and Managed Security Service Providers (MSSPs)? We also have the data intelligence of: •Managed Service Providers (MSP’s) – 25,000 unique companies •Managed Security Service Providers (MSSP’s) – 7,520 unique companies •IT Decision Makers – 6million across all industry •Business Decision Makers – 10 million across all industry •Value Added Resellers- VARs •Independent Software Vendors- ISVs •System Integrators- SIs •VoIP Service Providers. •Telecommunications Service Providers (TSPs) •Application Service Providers (ASPs) •IT Managed Services Providers (ITMSP) •Storage Service Providers (SSPs) Kindly review and let me know if I can share more information on this. I look forward to hearing from you. Best regards, Judy Willie Marketing Specialist ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Yubico Security Keys
On 09/05/18 20:34, Robert Ames wrote:
On Wed, Sep 05, 2018 at 01:00:20PM +0930, O'Connor, Daniel wrote:
On 5 Sep 2018, at 12:43, Robert Ames wrote:
On 5 Sep 2018, at 08:33, Robert Ames wrote:
FreeBSD sees the device:
Sep 4 17:25:13 freebsd kernel: ugen1.4: at
usbus1
Sep 4 17:25:13 freebsd kernel: uhid0 on uhub4
Sep 4 17:25:13 freebsd kernel: uhid0: on usbus1
So should this just work out of the box or is there something I'm
missing?
Hi Robert,
I don't have any Yubikeys but have you tried checking the permissions of
/dev/uhid0* and /dev/ugen1.4 (which will be a symlink to usb/1.4.0) ?
You can chmod them for now and then if that works have a devd conf or devfs
rule which sets the permissions appropriately when the device is connected.
If permissions are the problem it would be nice to see if the error message can
be improved too :)
--
Daniel O'Connor
I had done a manual chmod 777 /dev/usb/1.4.0 but had overlooked /dev/uhid0.
Once I did a chmod 777 on that it worked. Thank you. Any suggestions on the
best way to add a devd conf or devfs rule for this thing?
Add this to /etc/devfs.conf..
[root=100]
add path 'uhid*' group users mode 660
(Assuming your user is in the 'users' group - adjust to taste, devfs(8) has the
details)
And this to /etc/rc.conf..
devfs_system_ruleset="root"
Then do..
sudo service devfs restart
And unplug/replug the key.
--
Daniel O'Connor
Yes, that works (using /etc/devfs.rules). Thanks. I also got it to work
using /etc/devd.conf
# Yubico Security Key
attach 100 {
match "vendor" "0x1050";
match "product" "0x0120";
device-name "uhid[0-9]+";
action "/usr/sbin/chown robert /dev/$device-name";
};
running "usbconfig dump_device_desc" to get the vendor and product ids.
I didn't have to touch /dev/ugen1.4 or /dev/usb/1.4.0. Not sure which is
the more correct way to do this. But they both work.
So things now work great on the Yubico demo site. Sadly I cannot get it
to work in Google. Google doesn't respond when I press the gold disc
during the registration process.
There is a port, security/u2f-devd [0] that sets up devd rules for use
with yubico and other devices. That works great for me. Install it and
follow the instructions.
[0] https://www.freshports.org/security/u2f-devd/
Regards
--
Niclas
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: iSCSI booting with isboot
Il 06/09/2018 08:34, O'Connor, Daniel ha scritto: On 6 Sep 2018, at 10:18, O'Connor, Daniel wrote: BootNIC: em0 Configure: IPv6 by NIC0 CHAP Type: No CHAP Attempting to login to iSCSI target and scan all LUNs. soreceive BHS is not complete do login failed The last two lines repeat many times (interspersed with other probe/boot messages) until I get to mount root. I did some tcpdumping and it seems that there is iSCSI traffic but it stops and I am wondering if the ethernet card isn't getting tickled correctly so after a while it stops talking. The traffic seems to be... - 3 x NOP In - Read LBA 0 - Login - TUR - Read LBA 0 - Read LBA 0x40 - Read LBA 0x1 - Read LBA 0x641 The reads seem OK and have plausible data (MBR headers) The last thing it sees are 3 x NOP In just after it looks like something (in the kernel!) reads /etc/services which seems pretty weird.. -- Daniel O'Connor "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org" Please try the patch at: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=227313 -- Maurizio ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: iSCSI booting with isboot
> On 6 Sep 2018, at 10:18, O'Connor, Daniel wrote: > BootNIC: em0 > Configure: IPv6 by NIC0 > CHAP Type: No CHAP > Attempting to login to iSCSI target and scan all LUNs. > soreceive BHS is not complete > do login failed > > The last two lines repeat many times (interspersed with other probe/boot > messages) until I get to mount root. I did some tcpdumping and it seems that there is iSCSI traffic but it stops and I am wondering if the ethernet card isn't getting tickled correctly so after a while it stops talking. The traffic seems to be... - 3 x NOP In - Read LBA 0 - Login - TUR - Read LBA 0 - Read LBA 0x40 - Read LBA 0x1 - Read LBA 0x641 The reads seem OK and have plausible data (MBR headers) The last thing it sees are 3 x NOP In just after it looks like something (in the kernel!) reads /etc/services which seems pretty weird.. -- Daniel O'Connor "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
