[Bug 213371] panic: spin lock held too long

2016-11-05 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=213371

--- Comment #31 from Andriy Gapon  ---
There are newer snapshots available now, they should have the command.
If you still have access to the hardware and interested in debugging this
issue, could you please try a newer snapshot?
Thank you.

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


[Bug 214237] Stack buffer lifetime mis-use in ncal(1)

2016-11-05 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=214237

Bug ID: 214237
   Summary: Stack buffer lifetime mis-use in ncal(1)
   Product: Base System
   Version: 10.3-STABLE
  Hardware: Any
OS: Any
Status: New
  Severity: Affects Only Me
  Priority: ---
 Component: misc
  Assignee: freebsd-bugs@FreeBSD.org
  Reporter: j.deboynepollard-newsgro...@ntlworld.com

The buffer used to obtain the standout start and standout end sequences from
termcap is used long after its lifetime has ended, and potentially something
else has written to that area of stack storage.

The fix is to adjust line 1113 of usr.bin/ncal/ncal.c to

static char cbuf[512];
char tbuf[1024], *b;

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


[Bug 213045] kldload vesa gives "error 19"

2016-11-05 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=213045

--- Comment #1 from Harri  ---
Is there anything I could try? It would be a shame to use this laptop for
anything else but FreeBSD.

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


[Bug 214237] Stack buffer lifetime mis-use in ncal(1)

2016-11-05 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=214237

Eric van Gyzen  changed:

   What|Removed |Added

 Status|New |In Progress
 CC||vangy...@freebsd.org

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


[Bug 214237] Stack buffer lifetime mis-use in ncal(1)

2016-11-05 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=214237

Eric van Gyzen  changed:

   What|Removed |Added

   Assignee|freebsd-bugs@FreeBSD.org|vangy...@freebsd.org

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


[Bug 214242] FreeBSD Kernel does not boot on Opteron_G4 CPU (KVM Guest)

2016-11-05 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=214242

Bug ID: 214242
   Summary: FreeBSD Kernel does not boot on Opteron_G4 CPU (KVM
Guest)
   Product: Base System
   Version: 11.0-RELEASE
  Hardware: amd64
OS: Any
Status: New
  Severity: Affects Only Me
  Priority: ---
 Component: kern
  Assignee: freebsd-bugs@FreeBSD.org
  Reporter: s...@sambyte.co.uk
CC: freebsd-am...@freebsd.org
CC: freebsd-am...@freebsd.org

Created attachment 176657
  --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=176657&action=edit
Archive containing screenshots described in report

I have reproduced this across a couple of guests now. One was an upgrade from
10.3-RELEASE (Which works fine) the other is the bootonly installer image

All hang immediately after the boot menu (Shown in bootloader.png)

Attempts to enable verbose debugging do not produce any further output.

Removal of:





>From the libvirt XML allows the guest to boot with limited available
instruction sets (Shown in kvmlimited.png) this would lead me to believe that a
change in the 11 kernel has made it incompatible with a particular instruction
set that is present on an Opteron 6234 CPU

Guest boots fine using host-model CPU of an Intel E5 2620 (SandyBridge) host
(Shown in intelhost.png)

FreeBSD 10.3-RELEASE loads fine using the host-model parameters of KVM on the
Opteron_G4 host (Shown in Opteron_G4 Features.png)

KVM / Qemu version of both hypervisors is 'QEMU emulator version 2.0.0 (Debian
2.0.0+dfsg-2ubuntu1.28)' and both hypervisors are running Ubuntu 14.04.5 LTS
with libvirt 1.2.2

Libvirt XML of non-working:


  www
  fef0689e-fe23-df7c-1d11-3aa3447d6491
  None
  524288
  524288
  2
  
/machine
  
  
hvm



  
  

  
  



  
  
  destroy
  restart
  restart
  
/usr/bin/kvm-spice

  
  
  
  
  


  
  
  
  
  
  


  
  


  


  
  


  
  
  
  
  
  


  
  
  


  
  
  


  




  


  
  
  


  
  

  
  
libvirt-fef0689e-fe23-df7c-1d11-3aa3447d6491
libvirt-fef0689e-fe23-df7c-1d11-3aa3447d6491
  


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


[Bug 214242] FreeBSD Kernel does not boot on Opteron_G4 CPU (KVM Guest)

2016-11-05 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=214242

Samuel Husky  changed:

   What|Removed |Added

   Severity|Affects Only Me |Affects Some People

--- Comment #1 from Samuel Husky  ---
I've just found that bug #21 is a simlar issue.

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


[Bug 213474] sed behavior change with a/i/c operands.

2016-11-05 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=213474

--- Comment #6 from Pedro F. Giffuni  ---
(In reply to commit-hook from comment #5)

For the record:

kib@ has suggested, and I agree, that an environment variable may be more
convenient for this case. IMHO, the default should remain the current behavior.

The naming of a descriptive environment variable, and perhaps even a patch for
both code and manpage are welcome ;).

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


[Bug 214248] mergesort_r should exist

2016-11-05 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=214248

Bug ID: 214248
   Summary: mergesort_r should exist
   Product: Base System
   Version: CURRENT
  Hardware: Any
OS: Any
Status: New
  Severity: Affects Only Me
  Priority: ---
 Component: bin
  Assignee: freebsd-bugs@FreeBSD.org
  Reporter: d...@yost.com

For the same reason that there is a qsort_r there should be a mergesort_r and
_r variants of the other sorts.

qsort_r is needed when using it from a foreign language like Swift. Mergesort
is superior in many respects but cannot be used because there is no
mergesort_r.

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


[Bug 214250] Panic with BUF_TRACKING

2016-11-05 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=214250

Bug ID: 214250
   Summary: Panic with BUF_TRACKING
   Product: Base System
   Version: CURRENT
  Hardware: Any
OS: Any
Status: New
  Severity: Affects Only Me
  Priority: ---
 Component: kern
  Assignee: freebsd-bugs@FreeBSD.org
  Reporter: tr...@freebsd.org

To reproduce, plug in a USB flash key and do "sg_luns /dev/da0".  It also works
with iSCSI and probably other SCSI devices.

(kgdb) where
#0  doadump (textdump=0) at pcpu.h:222
#1  0x80396b3b in db_dump (dummy=, dummy2=false,
dummy3=0, dummy4=0x0) at /usr/home/trasz/svn/spare/sys/ddb/db_command.c:546
#2  0x80396939 in db_command (cmd_table=) at
/usr/home/trasz/svn/spare/sys/ddb/db_command.c:453
#3  0x80396694 in db_command_loop () at
/usr/home/trasz/svn/spare/sys/ddb/db_command.c:506
#4  0x8039974f in db_trap (type=, code=) at /usr/home/trasz/svn/spare/sys/ddb/db_main.c:248
#5  0x80aa08b3 in kdb_trap (type=, code=, tf=) at
/usr/home/trasz/svn/spare/sys/kern/subr_kdb.c:654
#6  0x80ed9511 in trap_fatal (frame=0xfe02287d2830, eva=0) at
/usr/home/trasz/svn/spare/sys/amd64/amd64/trap.c:796
#7  0x80ed91ff in trap (frame=0xfe02287d2830) at
/usr/home/trasz/svn/spare/sys/amd64/amd64/trap.c:198
#8  0x80eb9161 in calltrap () at
/usr/home/trasz/svn/spare/sys/amd64/amd64/exception.S:236
#9  0x8030a7c9 in xpt_done (done_ccb=0xf8010f690800) at
/usr/home/trasz/svn/spare/sys/cam/cam_xpt.c:4477
#10 0x808a45ac in umass_t_bbb_status_callback (xfer=, error=) at
/usr/home/trasz/svn/spare/sys/dev/usb/storage/umass.c:1151
#11 0x808c1612 in usbd_callback_wrapper (pq=) at
/usr/home/trasz/svn/spare/sys/dev/usb/usb_transfer.c:2407
#12 0x808c28e9 in usb_command_wrapper (pq=,
xfer=) at
/usr/home/trasz/svn/spare/sys/dev/usb/usb_transfer.c:3061
#13 0x808c177e in usb_callback_proc (_pm=) at
/usr/home/trasz/svn/spare/sys/dev/usb/usb_transfer.c:2268
#14 0x808bc2b5 in usb_process (arg=) at
/usr/home/trasz/svn/spare/sys/dev/usb/usb_process.c:176
#15 0x80a223b4 in fork_exit (callout=0x808bc1e0 ,
arg=0xfeebedb0, frame=0xfe02287d2ac0)
at /usr/home/trasz/svn/spare/sys/kern/kern_fork.c:1038
#16 0x80eb969e in fork_trampoline () at
/usr/home/trasz/svn/spare/sys/amd64/amd64/exception.S:611
#17 0x in ?? ()


[..]

(kgdb) down
#9  0x8030a7c9 in xpt_done (done_ccb=0xf8010f690800) at
/usr/home/trasz/svn/spare/sys/cam/cam_xpt.c:4477
4477done_ccb->csio.bio != NULL)
(kgdb) l
4472struct cam_doneq *queue;
4473int run, hash;
4474
4475#if defined(BUF_TRACKING) || defined(FULL_BUF_TRACKING)
4476if (done_ccb->ccb_h.func_code == XPT_SCSI_IO &&
4477done_ccb->csio.bio != NULL)
4478biotrack(done_ccb->csio.bio, __func__);
4479#endif
4480
4481CAM_DEBUG(done_ccb->ccb_h.path, CAM_DEBUG_TRACE,
(kgdb) p done_ccb->csio.bio
$1 = (struct bio *) 0xa5a5a5a5a5a5a5a5

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


[Bug 213856] Fatal trap12: page fault while in kernel mode; Supervisor read data, page not present

2016-11-05 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=213856

--- Comment #13 from Mark Johnston  ---
In both cases, we crashed in bucket_drain() when resetting bucket->ub_cnt to 0:

   0x80e17d90 <+256>:   movslq %r13d,%r13
   0x80e17d93 <+259>:   mov0x18(%rbx,%r13,8),%rdi
   0x80e17d98 <+264>:   mov0x10c(%r14),%esi
   0x80e17d9f <+271>:   callq  *0xe8(%r14)
   0x80e17da6 <+278>:   inc%r13d
   0x80e17da9 <+281>:   movswl 0x10(%rbx),%eax
   0x80e17dad <+285>:   cmp%eax,%r13d
   0x80e17db0 <+288>:   jl 0x80e17d90

   0x80e17db2 <+290>:   mov0x100(%r14),%rdi
   0x80e17db9 <+297>:   movswl %ax,%edx
   0x80e17dbc <+300>:   mov%r12,%rsi
   0x80e17dbf <+303>:   callq  *0xf8(%r14)
   0x80e17dc6 <+310>:   movw   $0x0,0x10(%rbx) <--

rbx is a callee-saved register that is dereferenced after every call to
uz_fini,
so it seems as though the uz_release function for the zone is somehow
corrupting
its frame. Because this is happening in the context of uma_reclaim(), we know
that this can't be a cache zone, so uz_release is zone_release().

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


[Bug 214254] Freebsd-update does not request a reboot in all cases where it is needed

2016-11-05 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=214254

Bug ID: 214254
   Summary: Freebsd-update does not request a reboot in all cases
where it is needed
   Product: Base System
   Version: 11.0-RELEASE
  Hardware: Any
OS: Any
Status: New
  Severity: Affects Many People
  Priority: ---
 Component: bin
  Assignee: freebsd-bugs@FreeBSD.org
  Reporter: bc...@lafn.org

I have several systems that were running 11.0-p1 (RELEASE) and needed to update
them to the latest security patches.  Freebsd-update brought down the updates
and when they were installed it said nothing about rebooting so I didn't. 

freebsd-version -ku
11.0-RELEASE-p2
11.0-RELEASE-p3

uname -a
FreeBSD sermons 11.0-RELEASE-p1 FreeBSD 11.0-RELEASE-p1 #0 r306420: Thu Sep 29
01:43:23 UTC 2016 r...@releng2.nyi.freebsd.org:/usr/obj/usr/src/sys/GENERIC
 amd64

Once I rebooted the system, uname showed -p2:

FreeBSD master 11.0-RELEASE-p2 FreeBSD 11.0-RELEASE-p2 #0: Mon Oct 24 06:55:27
UTC 2016 r...@amd64-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC 
amd64

Apparently a reboot was required after the freebsd-update install and it should
have told me that was the case.

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


[Bug 214242] FreeBSD Kernel does not boot on Opteron_G4 CPU (KVM Guest)

2016-11-05 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=214242

Mark Linimon  changed:

   What|Removed |Added

   Keywords||regression

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


[Bug 214226] sshd RekeyLimit does not appear to change the maximum amount of data

2016-11-05 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=214226

Mark Linimon  changed:

   What|Removed |Added

 CC|freebsd-am...@freebsd.org   |
Summary|sshd RekeyLimit |sshd RekeyLimit does not
   ||appear to change the
   ||maximum amount of data

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


[Bug 214217] Nvidia NVS 300 fails to start under xorg

2016-11-05 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=214217

Mark Linimon  changed:

   What|Removed |Added

 CC|freebsd-am...@freebsd.org   |
Summary|Nvidia NVS 300 support  |Nvidia NVS 300 fails to
   ||start under xorg

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