[Bug 191263] New: [patch] dd(1): Incorrect casting of arguments

2014-06-22 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=191263

Bug ID: 191263
   Summary: [patch] dd(1): Incorrect casting of arguments
   Product: Base System
   Version: 11.0-CURRENT
  Hardware: Any
OS: Any
Status: Needs Triage
  Severity: Affects Many People
  Priority: ---
 Component: bin
  Assignee: freebsd-bugs@FreeBSD.org
  Reporter: w...@worrbase.com

Created attachment 144014
  -- https://bugs.freebsd.org/bugzilla/attachment.cgi?id=144014action=edit
Better argument handling patch

dd(1) casts many of its numeric arguments from uintmax_t to intmax_t and back
again to detect whether or not the original arguments were negative. This is
not correct.

Attached is a patch that removes the pointless casts, and detects negative
numbers slightly more reliably.

-- 
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 191265] New: [patch] uart(4) punishes UARTs for being too fast

2014-06-22 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=191265

Bug ID: 191265
   Summary: [patch] uart(4) punishes UARTs for being too fast
   Product: Base System
   Version: 11.0-CURRENT
  Hardware: Any
OS: Any
Status: Needs Triage
  Severity: Affects Only Me
  Priority: ---
 Component: kern
  Assignee: freebsd-bugs@FreeBSD.org
  Reporter: sh...@freebsd.org

Created attachment 144015
  -- https://bugs.freebsd.org/bugzilla/attachment.cgi?id=144015action=edit
Fix for discarding data when internal buffer full.

For NS8250 family UARTs, svn 120146 -
http://svnweb.freebsd.org/base?view=revisionrevision=120146 - made a change to
flush the UART if the kernel buffers are full.  The commit message suggests
this is because of how the read loop was structured.

However, this change mad it so that if the internal FreeBSD buffer is full, it
will drop all pending data... effectively punishing devices for having too much
data buffered.  At least one network exposed UART is capable of this.

The attached patch doesn't clear the interrupt if the rx buffer is full by
checking the buffer has space before reading LSR.

-- 
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 191265] [patch] uart(4) punishes UARTs for being too fast

2014-06-22 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=191265

Stephen Hurd sh...@freebsd.org changed:

   What|Removed |Added

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

-- 
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 191266] New: [patch] support Broadcom virtual UART

2014-06-22 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=191266

Bug ID: 191266
   Summary: [patch] support Broadcom virtual UART
   Product: Base System
   Version: 11.0-CURRENT
  Hardware: Any
OS: Any
Status: Needs Triage
  Severity: Affects Only Me
  Priority: ---
 Component: kern
  Assignee: freebsd-bugs@FreeBSD.org
  Reporter: sh...@freebsd.org

Created attachment 144016
  -- https://bugs.freebsd.org/bugzilla/attachment.cgi?id=144016action=edit
Add support for Broadcom 5725/5761/5762 UART

The Broadcom 5725, 5761, and 5762 devices have a UART which can be configured
to be accessed via ssh, telnet, or (for 5725) IPMI SoL.  This patch adds
support for this UART (tested on 5762).

Since it has a register shift, a field for this vale was added into struct
pci_id, and the bus_alloc_resource() call was modified to account for the
larger size when regshft is non-zero.

-- 
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 191266] [patch] support Broadcom virtual UART

2014-06-22 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=191266

Stephen Hurd sh...@freebsd.org changed:

   What|Removed |Added

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

-- 
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 191270] New: df -h output missing units when size is 1TB

2014-06-22 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=191270

Bug ID: 191270
   Summary: df -h output missing units when size is 1TB
   Product: Base System
   Version: 10.0-STABLE
  Hardware: Any
OS: Any
Status: Needs Triage
  Severity: Affects Many People
  Priority: ---
 Component: bin
  Assignee: freebsd-bugs@FreeBSD.org
  Reporter: xxjack1...@gmail.com

root@jack:/home/jack # df -h
Filesystem  SizeUsed   Avail Capacity  Mounted on
/dev/mirror/gm0 2.6T10001.5T40%/

The used size is really 1TB but the T is missing from the df -h output.

-- 
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 191270] df -h output missing units when size is 1TB

2014-06-22 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=191270

--- Comment #1 from xxjack1...@gmail.com ---
T should be G, not T

-- 
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 188833] [suspend/resume] Suspend/resume with Intel GMA HD 4000: AIGLX fails to restart

2014-06-22 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=188833

Nikola Lečić nikola.le...@anthesphoria.net changed:

   What|Removed |Added

 CC||nikola.lecic@anthesphoria.n
   ||et

--- Comment #1 from Nikola Lečić nikola.le...@anthesphoria.net ---
I forgot to add here how the system fails to restart without the aforementioned
patch. With AIGLX activated, I get this horrible corruption:
http://i327.photobucket.com/albums/k477/ivan_rokotov_bsd/2_zpsd7564e4b.png
and no moving or switching to console help. No GL application starts.
I also found this in the X log after resume:

[  1173.617] (EE) intel(0): Failed to submit batch buffer, expect
rendering corruption: Device busy.
 (II) AIGLX: Suspending AIGLX clients for VT switch
[  1173.663] (WW) intel(0): drmDropMaster failed: Unknown error: -22
[  1177.289] (II) AIGLX: Resuming AIGLX clients after VT switch
[  1177.340] (II) intel(0): EDID vendor CMN, prod id 5239
[  1177.340] (II) intel(0): Printing DDC gathered Modelines:
[  1177.340] (II) intel(0): Modeline 1366x768x0.0   71.59  1366 1410
1439 1512  768 771 775 789 -hsync -vsync (47.3 kHz eP)

-- 
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 188833] [suspend/resume] Suspend/resume with Intel GMA HD 4000: AIGLX fails to restart

2014-06-22 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=188833

--- Comment #2 from Nikola Lečić nikola.le...@anthesphoria.net ---
(This is on Lenovo IdeaPad S400 as in the case of original poster.)

-- 
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 191270] df -h output missing units when size is 1TB

2014-06-22 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=191270

byc...@gmail.com changed:

   What|Removed |Added

 CC||byc...@gmail.com

--- Comment #2 from byc...@gmail.com ---
(In reply to xxjack12xx from comment #1)
 T should be G, not T

Can you please how the result of command `df' as well? According to the
implementation of function `prthumanval()', it should not show any result as
`1000' or `1000G', when the value is `1000G', it will display `1.0T' instead.

regards,
bycn82

-- 
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 191279] New: jail allow.sysvipc - doesn't work until jail is started TWICE after reboot

2014-06-22 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=191279

Bug ID: 191279
   Summary: jail allow.sysvipc - doesn't work until jail is
started TWICE after reboot
   Product: Base System
   Version: 9.2-RELEASE
  Hardware: Any
OS: Any
Status: Needs Triage
  Severity: Affects Only Me
  Priority: ---
 Component: kern
  Assignee: freebsd-bugs@FreeBSD.org
  Reporter: dreamc...@gmail.com

This is one of the most weird bug I have come across since using FreeBSD jails.

I have now made an rc.d script to restart my jail a 2nd time every boot… and
sysvipc feature will then start working inside of the jail.

Without such intervention, a jail is normally started 1 time after system
reboot. Then for me it isn't working inside of the jail.

This concerns only allow.sysvipc in jail.conf file. I have not set any other
kinds of global sysvipc options for the host or the jail.

Sorry I can't provide a test case for this problem. It was found with
qjail-3.4, on FreeNAS. But it would be great if anyone else can try to
reproduce this situation. To see if it occurs on any other FreeBSD versions -
9.2, 9.3, 10.0, STABLE or CURRENT.


My uname -a:

FreeBSD freenas.local 9.2-RELEASE-p3 FreeBSD 9.2-RELEASE-p3 #0 r262572+7b72365:
Fri Mar 14 15:50:04 PDT 2014
r...@build.ixsystems.com:/home/jkh/9.2.1-BRANCH/freenas/os-base/amd64/tank/home/jkh/9.2.1-BRANCH/freenas/FreeBSD/src/sys/FREENAS.amd64
 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

Re: [Bug 191086] New: grep and bsdgrep do not recognize [[::]] and [[::]]

2014-06-22 Thread John D. Hendrickson and Sara Darnell

bz-nore...@freebsd.org wrote:

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

Bug ID: 191086
   Summary: grep and bsdgrep do not recognize [[::]] and [[::]]
   Product: Base System
   Version: 9.2-RELEASE
  Hardware: Any
OS: Any
Status: Needs Triage
  Severity: Affects Many People
  Priority: ---
 Component: bin
  Assignee: freebsd-bugs@FreeBSD.org
  Reporter: we...@iastate.edu

grep and bsdgrep do not recognize the '[[::]]' or '[[::]]' bracket
expressions described in re_format(7), though sed does:


$ printf 'foobar\nfoo bar\nbaz' | grep 'foo[[::]]'
grep: Invalid character class name
$ printf 'foobar\nfoo bar\nbaz' | grep '[[::]]bar'
grep: Invalid character class name
$ printf 'foobar\nfoo bar\nbaz' | bsdgrep 'foo[[::]]'
bsdgrep: Invalid character class name
$ printf 'foobar\nfoo bar\nbaz' | bsdgrep '[[::]]bar'
bsdgrep: Invalid character class name
$ printf 'foobar\nfoo bar\nbaz' | sed -n '/foo[[::]]/p'
foo bar
$ printf 'foobar\nfoo bar\nbaz' | sed -n '/[[::]]bar/p'
foo bar




i've never heard it should support [::]

i've heard \ is a gnu option not all support

what is your citation showing any standard defines this and that you 
should be allowed to make changes (which maybe will cause other 
problems if you are incorrect) ?


please, thank you
___
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 191260] [patch] dtrace fbt entry function gets the wrong values from arg5 to arg9 on amd64 platform

2014-06-22 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=191260

Mark Johnston ma...@freebsd.org changed:

   What|Removed |Added

 Status|Needs Triage|Commit Ready
 CC||ma...@freebsd.org
   Assignee|freebsd-bugs@FreeBSD.org|ma...@freebsd.org

-- 
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 186248] Upgrade from 9.1-RELEASE - 9.2-RELEASE, ses print to messages and console once every minute

2014-06-22 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=186248

--- Comment #1 from t...@kitty.2y.idv.tw ---
I got the similar message with you.
I am using LSI SAS 9207-4i4e and LSI SAS 9206-16e.
The message also show in FreeBSD 9.2 and FreeBSD 10.0.

I disable the ses module in kernel. The message will not be show.

-- 
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