[Bug 200384] ctld panic at boot on 10.1-STABLE

2015-05-22 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=200384

Jimmy Olgeni  changed:

   What|Removed |Added

Summary|ctld|ctld panic at boot on
   ||10.1-STABLE

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"


[Bug 200384] ctld

2015-05-22 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=200384

Bug ID: 200384
   Summary: ctld
   Product: Base System
   Version: 10.1-STABLE
  Hardware: amd64
OS: Any
Status: New
  Severity: Affects Only Me
  Priority: ---
 Component: kern
  Assignee: freebsd-bugs@FreeBSD.org
  Reporter: olg...@freebsd.org

Created attachment 157032
  --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=157032&action=edit
Sample ctl.conf

Loading ctld causes a panic at boot (ctld_enable="YES" in rc.conf) when the
following kernel options are enabled: DEADLKRES, DEBUG_LOCKS, DEBUG_VFS_LOCKS,
DIAGNOSTIC, INVARIANTS, INVARIANT_SUPPORT, WITNESS.

It seems repeatable so far - the options were actually enbled to track down a
possible deadlock elsewhere.

Fatal trap 9: general protection fault while in kernel mode
cpuid = 2; apic id = 02
instruction pointer= 0x20:0x802e476a
stack pointer= 0x28:0xfe046a4467c0
frame pointer= 0x28:0xfe046a4468a0
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= 4 (scanner)
trap number= 9
panic: general protection fault
cpuid = 2
KDB: stack backtrace:
db_trace_self_wrapper() at db_trace_self_wrapper+0x2b/frame 0xfe046a446340
kdb_backtrace() at kdb_backtrace+0x39/frame 0xfe046a4463f0
vpanic() at vpanic+0x126/frame 0xfe046a446430
panic() at panic+0x43/frame 0xfe046a446490
trap_fatal() at trap_fatal+0x38f/frame 0xfe046a4464f0
trap() at trap+0x818/frame 0xfe046a446700
calltrap() at calltrap+0x8/frame 0xfe046a446700
--- trap 0x9, rip = 0x802e476a, rsp = 0xfe046a4467c0, rbp =
0xfe046a4468a0 ---
cam_periph_alloc() at cam_periph_alloc+0x48a/frame 0xfe046a4468a0
scsi_scan_lun() at scsi_scan_lun+0x1cb/frame 0xfe046a446ae0
scsi_scan_bus() at scsi_scan_bus+0x809/frame 0xfe046a446b50
xpt_scanner_thread() at xpt_scanner_thread+0x10b/frame 0xfe046a446bb0
fork_exit() at fork_exit+0x84/frame 0xfe046a446bf0
fork_trampoline() at fork_trampoline+0xe/frame 0xfe046a446bf0
--- trap 0, rip = 0, rsp = 0xfe046a446cb0, rbp = 0 ---
Uptime: 22s

ctl.conf only references one zvol.

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"


[Bug 200384] ctld panic at boot on 10.1-STABLE

2015-05-22 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=200384

--- Comment #2 from Jimmy Olgeni  ---
Created attachment 157034
  --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=157034&action=edit
Sample textdump 2

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"


[Bug 200384] ctld panic at boot on 10.1-STABLE

2015-05-22 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=200384

--- Comment #1 from Jimmy Olgeni  ---
Created attachment 157033
  --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=157033&action=edit
Sample textdump 1

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"


[Bug 200393] Performing pkg upgrade results in segfault when a package is locked

2015-05-22 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=200393

Bug ID: 200393
   Summary: Performing pkg upgrade results in segfault when a
package is locked
   Product: Base System
   Version: 10.1-STABLE
  Hardware: amd64
OS: Any
Status: New
  Severity: Affects Only Me
  Priority: ---
 Component: bin
  Assignee: freebsd-bugs@FreeBSD.org
  Reporter: jsm...@resonatingmedia.com

FreeBSD version: 10.1 (amd64)
pkg version: 1.5.2

Problem: When performing a "pkg upgrade" command, the pkg utility crashes with
a segfault if a package on the system is locked. the following is an example of
pkg attempting to perform an upgrade, running into the locked package and
crashing:

pkg upgrade
Checking for upgrades (134 candidates): 100%
Processing candidates (134 candidates): 100%
dovecot2-2.2.15_1 is locked and may not be modified
Child process pid=44106 terminated abnormally: Segmentation fault


Work around: When all packages have been unlocked, pkg no longer crashes when
attempting to upgrade all packages on the system. However, this means the
previously locked version of the package gets replaced by the newer version.

Expected behaviour: pkg should upgrade all packages, except those which are
locked.

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"


[Bug 193656] Installer keymap selection not updated for vt(4) use

2015-05-22 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=193656

--- Comment #8 from Ed Maste  ---
Created attachment 157046
  --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=157046&action=edit
QEMU screen grab of fixed installer menu

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"


[Bug 193656] Installer keymap selection not updated for vt(4) use

2015-05-22 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=193656

Ed Maste  changed:

   What|Removed |Added

 Status|In Progress |Closed
 Resolution|--- |FIXED

--- Comment #9 from Ed Maste  ---
Fixed with series of commits referenced above

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"


[Bug 200384] ctld panic at boot on 10.1-STABLE

2015-05-22 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=200384

--- Comment #3 from Jimmy Olgeni  ---
I managed to get a better backtrace (below).

A few more data points, always booting with the debug options enabled:

- Booting with ctld_enable -> panic
- Booting without ctld_enable, and then starting the ctld service -> panic
- Booting without ctld_enable, and kldloading ctl -> panic

- Booting without ctld_enable, and kldloading ctl after loading iscsi -> ok
- Booting with ctld_enable, but with iscsi_load and ctl_load in loader.conf ->
ok

There seems to be something going on between ctl and iscsi when
ctl is loaded without iscsi already present.

(kgdb) bt
#0  doadump (textdump=0) at pcpu.h:219
#1  0x803600fe in db_dump (dummy=, dummy2=0,
dummy3=0, dummy4=0x0) at /usr/src/sys/ddb/db_command.c:533
#2  0x8035fb9d in db_command (cmd_table=0x0) at
/usr/src/sys/ddb/db_command.c:440
#3  0x8035f914 in db_command_loop () at
/usr/src/sys/ddb/db_command.c:493
#4  0x803622f0 in db_trap (type=, code=0) at
/usr/src/sys/ddb/db_main.c:231
#5  0x809953d9 in kdb_trap (type=3, code=0, tf=)
at /usr/src/sys/kern/subr_kdb.c:656
#6  0x80d8b73e in trap (frame=0xfe046a445210) at
/usr/src/sys/amd64/amd64/trap.c:554
#7  0x80d6fc52 in calltrap () at
/usr/src/sys/amd64/amd64/exception.S:236
#8  0x80994ae5 in kdb_break () at cpufunc.h:63
#9  0x80776d9b in scgetc (sc=0x8185be18, flags=) at /usr/src/sys/dev/syscons/syscons.c:3591
#10 0x807795ff in sc_cngetc (cd=0x81643f70) at
/usr/src/sys/dev/syscons/syscons.c:1782
#11 0x809071c5 in cngetc () at /usr/src/sys/kern/kern_cons.c:406
#12 0x8095a54e in kern_reboot (howto=260) at
/usr/src/sys/kern/kern_shutdown.c:455
#13 0x8095a9d5 in vpanic (fmt=, ap=) at /usr/src/sys/kern/kern_shutdown.c:759
#14 0x8095aa23 in panic (fmt=0x81643f70 "\004") at
/usr/src/sys/kern/kern_shutdown.c:688
#15 0x80d8be3f in trap_fatal (frame=, eva=) at /usr/src/sys/amd64/amd64/trap.c:857
#16 0x80d8ba98 in trap (frame=) at
/usr/src/sys/amd64/amd64/trap.c:203
#17 0x80d6fc52 in calltrap () at
/usr/src/sys/amd64/amd64/exception.S:236
#18 0x802e494a in cam_periph_alloc (periph_ctor=0x802f9c30
, 
periph_oninvalidate=, periph_dtor=, periph_start=, 
name=, type=,
path=0xf80163591600, ac_callback=, 
code=) at /usr/src/sys/cam/cam_periph.c:227
#19 0x802f94fb in scsi_scan_lun (request_ccb=) at
/usr/src/sys/cam/scsi/scsi_xpt.c:2339
#20 0x802fd659 in scsi_scan_bus (periph=,
request_ccb=0xf80163b33800)
at /usr/src/sys/cam/scsi/scsi_xpt.c:2037
#21 0x802f045b in xpt_scanner_thread (dummy=) at
/usr/src/sys/cam/cam_xpt.c:2453
#22 0x809215d4 in fork_exit (callout=0x802f0350
, arg=0x0, frame=0xfe046a445c00)
at /usr/src/sys/kern/kern_fork.c:1017
#23 0x80d7018e in fork_trampoline () at
/usr/src/sys/amd64/amd64/exception.S:611
#24 0x in ?? ()

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"


[Bug 200384] ctld panic at boot on 10.1-STABLE

2015-05-22 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=200384

--- Comment #4 from Jimmy Olgeni  ---
Tested on 10.1-STABLE #1 r283287 amd64.

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"


[Bug 200361] net.inet.tcp.hostcache.list is jail information leak

2015-05-22 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=200361

--- Comment #2 from Marcus Reid  ---
/usr/src/sys/netinet/tcp_hostcache.c:612:35: error: incomplete definition of
type 'struct thread'
if (jailed_without_vnet(curthread->td_cred) != 0)
~^
/usr/src/sys/sys/systm.h:165:8: note: forward declaration of 'struct thread'
struct thread;
   ^
1 error generated.

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"


[Bug 200397] [bhyve] bhyve crashes in Linux KVM on AMD Host

2015-05-22 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=200397

Bug ID: 200397
   Summary: [bhyve] bhyve crashes in Linux KVM on AMD Host
   Product: Base System
   Version: 10.1-STABLE
  Hardware: amd64
OS: Any
Status: New
  Severity: Affects Only Me
  Priority: ---
 Component: bin
  Assignee: freebsd-bugs@FreeBSD.org
  Reporter: freebsd-b...@joe.mulloy.me

Created attachment 157052
  --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=157052&action=edit
Full Output from FreeBSD bhyve KVM Guest hypervisor

I setup a KVM guest on my AMD openSUSE 13.2 desktop to play around with bhyve
on CURRENT/STABLE. On the latest snapshots (20150520) for both 10.2-STABLE and
11-CURRENT bhyve crashes when I try to start a 10.1-RELEASE guest. It's
possible that there is some setting I can tweak on the VM to prevent the crash.
I'll attach the full output from the FreeBSD guest I'm trying to run bhyve on
as well as info about the Linux host system.

root@bhyve10:/usr/local/vmrc/vm/vm0 # /usr/sbin/bhyve -c 1 -m 1024 -A -H -s
0,hostbridge -s 2,ahci-hd,/usr/local/vmrc/vm//vm0/vm0.img -s
3:0,virtio-net,tap8000 -s 5,lpc -l com1,stdio vm0   

Copyright (c) 1992-2014 The FreeBSD Project.
Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
The Regents of the University of California. All rights reserved.
FreeBSD is a registered trademark of The FreeBSD Foundation.
FreeBSD 10.1-RELEASE #0 r274401: Tue Nov 11 21:02:49 UTC 2014
r...@releng1.nyi.freebsd.org:/usr/obj/usr/src/sys/GENERIC amd64
FreeBSD clang version 3.4.1 (tags/RELEASE_34/dot1-final 208032) 20140512
CPU: AMD Phenom(tm) II X6 1090T Processor (3214.12-MHz K8-class CPU)
  Origin = "AuthenticAMD"  Id = 0x100fa0  Family = 0x10  Model = 0xa  Stepping
= 0
 
Features=0x1783ab7f
  Features2=0x80802001
  AMD Features=0xe6500800
  AMD Features2=0x1f3
real memory  = 1073741824 (1024 MB)
avail memory = 1008115712 (961 MB)
vm exit[0]
reason  SVM
rip 0x80e392e8
inst_length 0
exitcode0x400
exitinfo1   0x4
exitinfo2   0xfee000f0
Abort (core dumped)
root@bhyve10:/usr/local/vmrc/vm/vm0 #

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"


[Bug 200397] [bhyve] bhyve crashes in Linux KVM on AMD Host

2015-05-22 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=200397

--- Comment #1 from Joseph Mulloy  ---
Created attachment 157053
  --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=157053&action=edit
Info about the openSUSE13.2 KVM Host System

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"


[Bug 200397] [bhyve] bhyve crashes in Linux KVM on AMD Host

2015-05-22 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=200397

Joseph Mulloy  changed:

   What|Removed |Added

 Attachment #157052|0   |1
is obsolete||

--- Comment #2 from Joseph Mulloy  ---
Created attachment 157054
  --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=157054&action=edit
Full Output from FreeBSD bhyve KVM Guest hypervisor

Added additional info

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"


[Bug 200398] iconv(3) support of UTF-7 is broken

2015-05-22 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=200398

Bug ID: 200398
   Summary: iconv(3) support of UTF-7 is broken
   Product: Base System
   Version: 10.1-RELEASE
  Hardware: Any
OS: Any
Status: New
  Severity: Affects Some People
  Priority: ---
 Component: bin
  Assignee: freebsd-bugs@FreeBSD.org
  Reporter: delp...@freebsd.org

Created attachment 157059
  --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=157059&action=edit
Patch by tijl@

(This is mainly for tracking purposes).

I have observed this issue with dovecot which the index worker would crash for:

Panic: file charset-iconv.c: line 132 (charset_to_utf8): assertion
failed: (*src_size - pos <= CHARSET_MAX_PENDING_BUF_SIZE)

Having been annoyed by this for some time I have decided to instrument the code
to figure out what have happen under the hood.  Eventually, I have discovered
that if iconv(3) is asked to convert two UTF-7 strings to UTF-8:

"+ADw-SPAN+AD4-"

And

"+ADw-SPAN lang"

The second conversion would give wrong results, while GNU implementation of
iconv(3) does not have the same issue.  Using gdb, the UTF-7 mode was 1 (shift)
when processing the second string, while it should be 0, so using an iconv(cd,
NULL, NULL, NULL) would mitigate this issue.

I have then asked Tijl Coosemans  who have quickly found the problem and
created a patch, quote:

===
_citrus_UTF7_mbtoutf16 stored the decoder state at the beginning so it
could restore this state on an incomplete character such that the next
call would restart the decoding.  The problem was that "-" at the end
of a string was also treated as an incomplete character but was also
removed from the state buffer.  So the initial state would be restored
(with base64 mode) but the next call would no longer see the "-" and
thus continued in base64 mode.

This state saving/restoring isn't needed here.  It's already handled
elsewhere (citrus_iconv_std.c:_citrus_iconv_std_iconv_convert) so the
patch removes it.

The patch also improves the decoding of 4 byte UTF16 characters.  If
only 2 bytes can be read it is treated as an incomplete character now
(returning an error) whereas before it would be treated as a shift
sequence (not an error).  A range check has been added for the low 2
bytes as well.
===

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"


[Bug 200398] iconv(3) support of UTF-7 is broken

2015-05-22 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=200398

Xin LI  changed:

   What|Removed |Added

   Keywords||patch-ready
   Priority|--- |Normal
   Assignee|freebsd-bugs@FreeBSD.org|t...@freebsd.org

--- Comment #1 from Xin LI  ---
Assign to our hero.

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"


[Bug 192528] pwd_mkdb fails if /etc/shells contains duplicates

2015-05-22 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=192528

--- Comment #4 from tmwalas...@gmail.com ---
This bug also affects chpass, getent shells and /usr/libexec/ftpd. Generally
everything that uses setusershell (which executes _local_initshells) with large
/etc/shells is affected.

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"