date:20170117

[Bug 215830] lib/libfetch regression

2017-01-17 Thread bugzilla-noreply

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=215830

--- Comment #4 from John Hein  ---
(In reply to Dag-Erling SmÃ¸rgrav from comment #3)

The OP was claiming that something changed in libfetch after 6.4-RELEASE.  The
broken Harvard ftp server was just his way to empirically observe that
hypothesis.  However, I could not reproduce his observation that 6.4 is
different in this regard.  Perhaps there is an environment difference on his
end of which he was not aware.

As such, the end result (closing this bug) is the same, but the reason for
closure is subtly different (it could be more specific than "not a bug", but
rather "unable to reproduce" - that is, we can't reproduce his reported success
on 6.4, so it appears to _not_ be a post-6.4 behavior change).

-- 
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 213535] [patch] [cam] cam(4) does not build outside of KERNBUILDDIR

2017-01-17 Thread bugzilla-noreply

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=213535

Ngie Cooper  changed:

   What|Removed |Added

 CC||i...@freebsd.org,
   ||n...@freebsd.org
 Status|New |Closed
   Assignee|freebsd-bugs@FreeBSD.org|n...@freebsd.org
  Flags||mfc-stable10+,
   ||mfc-stable11+
 Resolution|--- |FIXED

--- Comment #1 from Ngie Cooper  ---
The issue was fixed by commits on ^/head that weren't MFCed to stable branches.
I fixed the issue in ^/stable/11 by r312356 and in ^/stable/10 by r312357
(r312357 required MFCing r299864 as well).

Thank you for the report!

-- 
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 216123] ofwfb: r269278 broke booting on Power Mac G4

2017-01-17 Thread bugzilla-noreply

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=216123

--- Comment #7 from Kevin Bowling  ---
I don't think they need to be the same version, but you could revert the one
commit on the display system.  I've never used this though, so I can't validate
that it actually works still.  But it seems worth trying to see if there is a
useful panic string or whatever where the screen is going blank when debugging
is enabled, and you can also run kgdb remotely over it.

Otherwise maybe Nathan has enough context with your report now to take a look.

-- 
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 216195] Clang crash compiling qcad

2017-01-17 Thread bugzilla-noreply

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=216195

--- Comment #2 from Poul-Henning Kamp  ---
I guess the other file is too big for the bugzilla, you can find it here
instead:

http://phk.freebsd.dk/misc/REcmaHelper-f579ae.cpp.gz

-- 
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 216195] Clang crash compiling qcad

2017-01-17 Thread bugzilla-noreply

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=216195

--- Comment #1 from Poul-Henning Kamp  ---
Created attachment 179010
  --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=179010=edit
Shell diags

-- 
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 216195] Clang crash compiling qcad

2017-01-17 Thread bugzilla-noreply

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=216195

Bug ID: 216195
   Summary: Clang crash compiling qcad
   Product: Base System
   Version: CURRENT
  Hardware: Any
OS: Any
Status: New
  Severity: Affects Only Me
  Priority: ---
 Component: bin
  Assignee: freebsd-bugs@FreeBSD.org
  Reporter: p...@freebsd.org

Compiling QCAD from git:

Assertion failed: (idx < size()), function operator[], file
/freebsd/src/contrib/llvm/include/llvm/ADT/SmallVector.h, line 145.

-- 
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 216123] ofwfb: r269278 broke booting on Power Mac G4

2017-01-17 Thread bugzilla-noreply

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=216123

--- Comment #6 from Tom Lane  ---
(In reply to Kevin Bowling from comment #5)
Hmm ... I lack a firewire cable, but that could be remedied.  The only other
firewire machine I have is a G4 laptop, which I'm pretty sure won't boot 11 or
12 for the same reason this one won't.  I do have 10.3 installed on it though. 
Does the debug host need to be same FreeBSD version?

-- 
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 198480] UEFI install image hangs after exiting bootloader at Start address

2017-01-17 Thread bugzilla-noreply

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=198480

p...@nomadlogic.org changed:

   What|Removed |Added

 Status|New |Closed
 Resolution|--- |Unable to Reproduce

--- Comment #2 from p...@nomadlogic.org ---
No longer have access to this system and as such am close bug.

-- 
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 216123] ofwfb: r269278 broke booting on Power Mac G4

2017-01-17 Thread bugzilla-noreply

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=216123

--- Comment #4 from Tom Lane  ---
(In reply to Kevin Bowling from comment #2)
> Can you set 'sysctl debug.debugger_on_panic=1' and see if you can get a 
> better idea
> where it dies from the db> prompt or by switching to kgdb from that?

I couldn't figure out how to do that using the Open Firmware boot loader --- it
doesn't understand sysctl, AFAICT.  I tried the -d kernel switch but it didn't
change anything.

This machine lacks a serial port, which makes traditional kernel debugging
difficult.  I noticed that its Open Firmware version does support telnet
connections, though.  Is there a way to use that facility for a kernel debug
console?

-- 
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 189772] [new driver] apuled(4): add support for LEDs on PC Engines APU boards.

2017-01-17 Thread bugzilla-noreply

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=189772

l...@gta.com changed:

   What|Removed |Added

 Attachment #142703|0   |1
is obsolete||

--- Comment #3 from l...@gta.com ---
Created attachment 178995
  --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=178995=edit
Module to support LEDs on both APU1 and APU2 boards.

The updated patch has logic to detect if it is running on an APU1 or an APU2
board from PC Engines. It will then add support for all three LEDs and switch
on the front of the box.

-- 
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 215830] lib/libfetch regression

2017-01-17 Thread bugzilla-noreply

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=215830

Dag-Erling SmÃ¸rgrav  changed:

   What|Removed |Added

 Resolution|--- |Not A Bug
 CC||d...@freebsd.org
 Status|New |Closed

--- Comment #3 from Dag-Erling SmÃ¸rgrav  ---
The FTP server is misconfigured.  When a transfer is initiated in passive mode,
it instructs the client to connect to an RFC1918 address (10.137.96.102).  It
seems Harvard moved their server behind a NATing router which does not properly
rewrite the PASV response.  You should contact  and
ask them to address the issue, either by assigning a routeable address to their
FTP server or by setting up a transparent proxy.

-- 
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 216178] ZFS ARC and L2ARC are unrealistically large, maybe after r307265

2017-01-17 Thread bugzilla-noreply

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=216178

Bug ID: 216178
   Summary: ZFS ARC and L2ARC are unrealistically large, maybe
after r307265
   Product: Base System
   Version: 11.0-STABLE
  Hardware: Any
OS: Any
Status: New
  Severity: Affects Some People
  Priority: ---
 Component: kern
  Assignee: freebsd-bugs@FreeBSD.org
  Reporter: l...@freebsd.org

I have two ZFS pools: one with single device (zroot) and one raidz with 5
devices (zstor). zstor has L2ARC of 185GB.

% zpool list -v
NAME  SIZE  ALLOC   FREE  EXPANDSZ   FRAGCAP  DEDUP  HEALTH 
ALTROOT
zroot39.9G  13.7G  26.2G -50%34%  1.00x  ONLINE  -
  gpt/root   39.9G  13.7G  26.2G -50%34%
zstor13.6T  8.55T  5.08T -22%62%  1.00x  ONLINE  -
  raidz1 13.6T  8.55T  5.08T -22%62%
ada1 -  -  - -  -  -
ada2 -  -  - -  -  -
ada3 -  -  - -  -  -
ada4 -  -  - -  -  -
ada5 -  -  - -  -  -
cache-  -  - -  -  -
  gpt/l2arc   185G   185G   148M - 0%99%
%

Both pools has compression enabled (lz4), but compression ratio on zstor is
negligible (it contains mostly media files, like music, films and RAW digital
photos). zroot has compression rate about 1.4:

% zfs get compressratio zroot zstor
NAME   PROPERTY   VALUE  SOURCE
zroot  compressratio  1.43x  -
zstor  compressratio  1.00x  -
%

My system has 16GB of physical memory.

After upgrade to post-r307266 system (10-STABLE) different system tools starts
to show unrealistically large ARC. Upgrade to 11-STABLE (after r307265) doen't
help either. It looks like this:

(1) top output:
Mem: 195M Active, 4678M Inact, 9656M Wired, 1373M Free
ARC: 75G Total, 247M MFU, 6135M MRU, 1190K Anon, 77M Header, 556M Other
Swap: 8192M Total, 8192M Free

(2) zfs-stats -A output:
ARC Size:   515.61% 74.92   GiB
Target Size: (Adaptive) 100.00% 14.53   GiB
Min Size (Hard Limit):  12.50%  1.82GiB
Max Size (High Water):  8:1 14.53   GiB


This starts after some uptime with disc activity (like buildworld & backup) and
could be reset to "normal" state with reboot only.

Sometimes, L2ARC starts to grow up to 400% of its size, too. L2ARC shows a lot
of checksum errors as it grow larger than physical size.

-- 
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 216172] incorrect use of pam_get_item return value in libpam

2017-01-17 Thread bugzilla-noreply

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=216172

Ngie Cooper  changed:

   What|Removed |Added

   Assignee|freebsd-bugs@FreeBSD.org|d...@freebsd.org
 CC||n...@freebsd.org

--- Comment #1 from Ngie Cooper  ---
des maintains openpam.

-- 
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 216171] [ipfw] [panic] stable/11: repeating KASSERT("rm_rlock: recursed on non-recursive rmlock") crash

2017-01-17 Thread bugzilla-noreply

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=216171

Andrey V. Elsukov  changed:

   What|Removed |Added

 CC||a...@freebsd.org
   Assignee|freebsd-bugs@FreeBSD.org|a...@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 204226] mps driver panics

2017-01-17 Thread bugzilla-noreply

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=204226

Daniel Ylitalo  changed:

   What|Removed |Added

 Status|New |Closed
 Resolution|--- |FIXED

--- Comment #2 from Daniel Ylitalo  ---
This seems to have been fixed in 11-RELEASE so I'm closing it, 10.3 however
still has this 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 216172] incorrect use of pam_get_item return value in libpam

2017-01-17 Thread bugzilla-noreply

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=216172

Bug ID: 216172
   Summary: incorrect use of  pam_get_item return value in libpam
   Product: Base System
   Version: 11.0-STABLE
  Hardware: Any
OS: Any
Status: New
  Severity: Affects Many People
  Priority: ---
 Component: bin
  Assignee: freebsd-bugs@FreeBSD.org
  Reporter: patrick-f...@mindstep.com

In pam_get_authtok the code tests if pam_get_item succeeds with a simple
if(pam_get_item(...)) call. However on success pam_get_item returns
'PAM_SUCCESS' which value is 0.

In libpam the effect of this bug is that custom prompts provided by
applications using pam_set_item() are never used. This is more a cosmetic bug
than anything else.


Below are 2 diffs that fixes the issue in libpam:

-chroot- diff -up pam_get_authtok.c.orig pam_get_authtok.c
--- pam_get_authtok.c.orig  2017-01-11 18:15:11.538423000 +
+++ pam_get_authtok.c   2017-01-13 11:50:27.688031000 +
@@ -123,7 +123,7 @@ pam_get_authtok(pam_handle_t *pamh,
prompt = promptp;
/* no prompt provided, see if there is one tucked away somewhere */
if (prompt == NULL)
-   if (pam_get_item(pamh, pitem, ) && promptp != NULL)
+   if (pam_get_item(pamh, pitem, ) == PAM_SUCCESS &&
promptp != NULL)
prompt = promptp;
/* fall back to hardcoded default */
if (prompt == NULL)





-chroot- diff -up pam_get_user.c.orig pam_get_user.c
--- pam_get_user.c.orig 2017-01-13 11:55:19.971565000 +
+++ pam_get_user.c  2017-01-13 11:55:33.291977000 +
@@ -79,7 +79,7 @@ pam_get_user(pam_handle_t *pamh,
prompt = promptp;
/* no prompt provided, see if there is one tucked away somewhere */
if (prompt == NULL)
-   if (pam_get_item(pamh, PAM_USER_PROMPT, ) &&
+   if (pam_get_item(pamh, PAM_USER_PROMPT, ) ==
PAM_SUCCESS &&
promptp != NULL)
prompt = promptp;
/* fall back to hardcoded default */

-- 
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 216171] [ipfw] [panic] stable/11: repeating KASSERT("rm_rlock: recursed on non-recursive rmlock") crash

2017-01-17 Thread bugzilla-noreply

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=216171

Bug ID: 216171
   Summary: [ipfw] [panic] stable/11: repeating KASSERT("rm_rlock:
recursed on non-recursive rmlock") crash
   Product: Base System
   Version: 11.0-STABLE
  Hardware: Any
OS: Any
Status: New
  Severity: Affects Some People
  Priority: ---
 Component: kern
  Assignee: freebsd-bugs@FreeBSD.org
  Reporter: po...@grosbein.net

Created attachment 178985
  --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=178985=edit
kgdb script

One of my uniprocessor systems (11.0-STABLE/i386 r307472) having debugging
kernel repeatedly panices with same backtrace generating crashdumps:

total 1248464
-rw-r--r--  1 root  wheel  2 Jan 17 04:25 bounds
-rw---  1 root  wheel538 Jan 12 03:07 info.0
-rw---  1 root  wheel537 Jan 12 05:01 info.1
-rw---  1 root  wheel538 Jan 12 10:53 info.2
-rw---  1 root  wheel539 Jan 13 19:22 info.3
-rw---  1 root  wheel539 Jan 14 11:54 info.4
-rw---  1 root  wheel539 Jan 15 13:28 info.5
-rw---  1 root  wheel539 Jan 16 11:46 info.6
-rw---  1 root  wheel538 Jan 16 20:16 info.7
-rw---  1 root  wheel538 Jan 17 04:25 info.8
-rw---  1 root  wheel536 Jan 11 16:48 info.9
lrwxr-xr-x  1 root  wheel  6 Jan 17 04:25 info.last -> info.8
-rw-r--r--  1 root  wheel  5 Oct  3  2012 minfree
-rw---  1 root  wheel  165212160 Jan 12 03:07 vmcore.0
-rw---  1 root  wheel   94773248 Jan 12 05:01 vmcore.1
-rw---  1 root  wheel   94265344 Jan 12 10:54 vmcore.2
-rw---  1 root  wheel  160993280 Jan 13 19:22 vmcore.3
-rw---  1 root  wheel  150310912 Jan 14 11:54 vmcore.4
-rw---  1 root  wheel  150302720 Jan 15 13:28 vmcore.5
-rw---  1 root  wheel  160186368 Jan 16 11:46 vmcore.6
-rw---  1 root  wheel   94715904 Jan 16 20:16 vmcore.7
-rw---  1 root  wheel  160612352 Jan 17 04:25 vmcore.8
-rw---  1 root  wheel   94748672 Jan 11 16:48 vmcore.9
lrwxr-xr-x  1 root  wheel  8 Jan 17 04:25 vmcore.last -> vmcore.8

List of ipfw rules:

# ipfw show
00100 0   0 allow ip from any to any via lo0
00200 0   0 deny ip from any to 127.0.0.0/8
00300 0   0 deny ip from 127.0.0.0/8 to any
01010 0   0 allow tcp from 62.231.161.0/24{66,72,80} to me dst-port
23,3001-3006 in
01020 0   0 allow tcp from 62.231.161.216/29,62.231.161.232/29 to me
dst-port 23,3001-3006 in
01020 0   0 unreach port udp from not 62.231.160.18 to me dst-port
1812,1813,21645-21844 in
01030 0   0 allow tcp from 62.231.161.71 to me dst-port 23,3001-3006 in
01090   489   20408 reset tcp from any to me dst-port 23,3001-3006 in
65000 11822 2211829 allow ip from any to any
65535 0   0 deny ip from any to any

kgdb script is attached.
Compressed kernel.debug, crashinfo and vmcore are available here:
http://www.grosbein.net/freebsd/crash/20170117/

-- 
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 215826] C++ program signal handlers not called

2017-01-17 Thread bugzilla-noreply

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=215826

Dominic Fandrey  changed:

   What|Removed |Added

 Status|New |In Progress

--- Comment #8 from Dominic Fandrey  ---
Waiting for MFC.

-- 
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 215830] lib/libfetch regression

[Bug 213535] [patch] [cam] cam(4) does not build outside of KERNBUILDDIR

[Bug 216123] ofwfb: r269278 broke booting on Power Mac G4

[Bug 216195] Clang crash compiling qcad

[Bug 216195] Clang crash compiling qcad

[Bug 216195] Clang crash compiling qcad

[Bug 216123] ofwfb: r269278 broke booting on Power Mac G4

[Bug 198480] UEFI install image hangs after exiting bootloader at Start address

[Bug 216123] ofwfb: r269278 broke booting on Power Mac G4

[Bug 189772] [new driver] apuled(4): add support for LEDs on PC Engines APU boards.

[Bug 215830] lib/libfetch regression

[Bug 216178] ZFS ARC and L2ARC are unrealistically large, maybe after r307265

[Bug 216172] incorrect use of pam_get_item return value in libpam

[Bug 216171] [ipfw] [panic] stable/11: repeating KASSERT("rm_rlock: recursed on non-recursive rmlock") crash

[Bug 204226] mps driver panics

[Bug 216172] incorrect use of pam_get_item return value in libpam

[Bug 216171] [ipfw] [panic] stable/11: repeating KASSERT("rm_rlock: recursed on non-recursive rmlock") crash

[Bug 215826] C++ program signal handlers not called

18 matches

Site Navigation

Mail list logo

Footer information