[Bug 231190] created a file with touch that can not be removed

2018-09-05 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=231190

Oleksandr Tymoshenko  changed:

   What|Removed |Added

 Resolution|--- |Not A Bug
 Status|New |Closed

--- Comment #1 from Oleksandr Tymoshenko  ---
(In reply to todd from comment #0)

You can pass filename starting with - to a utility using "--" as marker for end
of arguments:

rm -- -type
vi -- -type
etc...

-- 
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 231190] created a file with touch that can not be removed

2018-09-05 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=231190

Bug ID: 231190
   Summary: created a file with touch that can not be removed
   Product: Base System
   Version: 11.2-STABLE
  Hardware: amd64
OS: Any
Status: New
  Severity: Affects Only Me
  Priority: ---
 Component: misc
  Assignee: b...@freebsd.org
  Reporter: tcarpenter...@gmail.com

Hi Guys,

Unfortunately this bug was caused by a type-o when using the "touch" command. 
This resulted in a file I can not modify, delete, move, copy or otherwise
destroy.  I can chmod/own it..

It seems like every command that accesses the file thinks its a -t argument.

I cant even attach the file.  Its a normal 0 byte file that was created with
touch




here are some examples:  (the -type file is the first one.. I just included it
for context as shows up before .hidden files yet is fully visible)

-rw-r--r--  1 todd  todd   0 Aug 21 00:46 -type
drwxr-xr-x  3 todd  todd  17 Sep  5 21:01 .
drwxr-xr-x  3 root  wheel  3 Aug 19 16:18 ..
-rw-r--r--  1 todd  todd1055 Aug 19 16:18 .cshrc
-rw-r--r--  1 todd  todd 392 Aug 19 16:18 .login
-rw-r--r--  1 todd  todd 163 Aug 19 16:18 .login_conf
-rw---  1 todd  todd 379 Aug 19 16:18 .mail_aliases
-rw-r--r--  1 todd  todd 336 Aug 19 16:18 .mailrc
-rw-r--r--  1 todd  todd 952 Aug 19 16:18 .profile
-rw---  1 todd  todd 281 Aug 19 16:18 .rhosts
-rw-r--r--  1 todd  todd 851 Aug 19 16:18 .shrc
drwx--  2 todd  todd   3 Aug 28 03:49 .ssh


it shows up with a normal ls
root@abyss:/home/todd # ls
-type   .login_conf .profile.sshtest.sh
.cshrc  .mail_aliases   .rhosts install63.iso   type
.login  .mailrc .shrc   zfs_health.sh


vi -type   (errors)


~
~
~
~
~
+=+=+=+=+=+=+=+
ype: tag not found; Error: tags: No such file or directory.
/tmp/vi.cYpFkc2AwI: new file: line 1
Press any key to continue:

if I cat it i get a switch error.

root@abyss:/home/todd # cat: illegal option -- y
cat:: Too many arguments.
root@abyss:/home/todd # usage: cat [-belnstuv] [file ...]
usage:: Too many arguments.


chown: no problem 

root@abyss:/home/todd # chown todd:todd -type
root@abyss:/home/todd #

root@abyss:/home/todd # chown root:wheel -type
root@abyss:/home/todd # ls -la
total 331069
-rw-r--r--  1 root  wheel  0 Aug 21 00:46 -type


rm .. or any other command like cp mv etc

root@abyss:/home/todd # rm -type
rm: illegal option -- t
usage: rm [-f | -i] [-dIPRrvWx] file ...
   unlink file



lol for the life of me I can't get rid of this file.  I cant even attach it or
copy it .. etc.. but its just a touched 0 byte file..

thanks

-- 
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 231172] [sshd] ssh login fails if server is set sysctl kern.trap_enotcap=1

2018-09-05 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=231172

--- Comment #2 from Yuichiro NAITO  ---
(In reply to Mariusz Zaborski from comment #1)
Created https://reviews.freebsd.org/D17056

It is my first differential on Phabricator.
Please let me know if something missing.

-- 
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 231187] last.1, lastlogin.8: comma missing in the See also list

2018-09-05 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=231187

Mark Linimon  changed:

   What|Removed |Added

Summary|Comma missing in the See|last.1, lastlogin.8: comma
   |also list   |missing in the See also
   ||list
   Keywords||patch

-- 
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 231187] Comma missing in the See also list

2018-09-05 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=231187

--- Comment #2 from david.ma...@davenulle.org ---
Created attachment 196900
  --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=196900=edit
lastlogin.8

Fix same issue on lastlogin (8)

-- 
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 231187] Comma missing in the See also list

2018-09-05 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=231187

david.ma...@davenulle.org changed:

   What|Removed |Added

 Attachment #196898|0   |1
is obsolete||

--- Comment #1 from david.ma...@davenulle.org ---
Created attachment 196899
  --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=196899=edit
correct patch

reverted patch

-- 
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 231187] Comma missing in the See also list

2018-09-05 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=231187

Bug ID: 231187
   Summary: Comma missing in the See also list
   Product: Documentation
   Version: Latest
  Hardware: Any
OS: Any
Status: New
  Severity: Affects Many People
  Priority: ---
 Component: Manual Pages
  Assignee: b...@freebsd.org
  Reporter: david.ma...@davenulle.org
CC: d...@freebsd.org

Created attachment 196898
  --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=196898=edit
patch

Following the libxo support to last(1), - MFC r338352 -,
the man page has been completed with libxo features.

A single comma is missing to separate the "see also" items.

-- 
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 231185] freebsd-update upgrade gives no indication of what the release name should look like

2018-09-05 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=231185

Bug ID: 231185
   Summary: freebsd-update upgrade gives no indication of what the
release name should look like
   Product: Base System
   Version: 11.1-RELEASE
  Hardware: Any
OS: Any
Status: New
  Severity: Affects Many People
  Priority: ---
 Component: bin
  Assignee: b...@freebsd.org
  Reporter: jonat...@kc8onw.net

freebsd-update upgrade should provide a list of available releases when not
given one or the man page should be updated to give example/template release
names.

-- 
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 231064] vgapci device memory not excluded on ThunderX

2018-09-05 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=231064

Mark Johnston  changed:

   What|Removed |Added

Summary|data abort in   |vgapci device memory not
   |in_pcbremlbgrouphash() on   |excluded on ThunderX
   |ThunderX|

-- 
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 231064] data abort in in_pcbremlbgrouphash() on ThunderX

2018-09-05 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=231064

Mark Johnston  changed:

   What|Removed |Added

 CC||and...@freebsd.org

--- Comment #2 from Mark Johnston  ---
I discovered that the hash table is "corrupted" immediately after it is
allocated and initialized.  In my case, the table is allocated starting at
physical address 0x1000 and is physically contiguous.  It appears that this
collides with an address range used by the vgapci device:

  pcib9
  Device Memory:
  0x87e0c000-0x87e0c0ff
pci9
PCI domain 0 bus numbers:
32
  pcib10
  PCI domain 0 bus numbers:
  33
  PEM PCIe Memory:
  0x1000-0x110f
  PEM PCIe IO:
  0x0-0xfff
pci10
pcib10 bus numbers:
33
  vgapci0
  pcib10 memory window:
  0x1000-0x10ff
  0x1100-0x1101

Indeed, this range isn't excluded from the EFI map:

   Type Physical  Virtual   #Pages Attr 
RuntimeServicesData 0050   50 0800 UC WC WT WB RUNTIME  
 ConventionalMemory 00d00 000ff2ec UC WC WT WB  
RuntimeServicesData fffec000 fffec000 0014 UC WC WT WB RUNTIME  
 ConventionalMemory 00010 00ef0100 UC WC WT WB  
   BootServicesData 000ff0100 0020 UC WC WT WB  
 ConventionalMemory 000ff0120 eacc UC WC WT WB  
   BootServicesData 000ffebec0000 0514 UC WC WT WB  
 ConventionalMemory 01400 00fea102 UC WC WT WB  
 LoaderData 010fea5020000 8001 UC WC WT WB  
 LoaderCode 010ff25030000 0086 UC WC WT WB 
   
   LoaderData 010ff25890000 218b UC WC
WT WB   
 LoaderCode 010ff47140000 0015 UC WC WT WB  
   BootServicesData 010ff47290000 965d UC WC WT WB 
   
   ConventionalMemory 010ffdd860000 01de UC WC
WT WB   
   BootServicesCode 010ffdf640000 0779 UC WC WT WB  
 ConventionalMemory 010ffe6dd0000 0040 UC WC WT WB 
   
ACPIReclaimMemory 010ffe71d0000 000b UC WC
WT WB   
  ACPIMemoryNVS 010ffe7280000 0060 UC WC WT WB  
RuntimeServicesData 010ffe788000  10ffe788000 0c30 UC WC WT WB RUNTIME 
   
  RuntimeServicesCode 010fff3b8000  10fff3b8000 0c47 UC WC
WT WB RUNTIME   
   BootServicesData 010ff0000 0001 UC WC WT WB  
 MemoryMappedIO 8030 8030 1000 UC RUNTIME  
   
   MemoryMappedIO 80401000 80401000 2000 UC
RUNTIME 
 MemoryMappedIO 87e006001000 87e006001000 1000 UC RUNTIME   
 MemoryMappedIO 87e02400 87e02400 1000 UC RUNTIME   
 MemoryMappedIO 87e0d0001000 87e0d0001000 0001 UC RUNTIME   
 MemoryMappedIO 9030 9030 1000 UC RUNTIME   
 MemoryMappedIO 90401000 90401000 2000 UC RUNTIME   
 MemoryMappedIO 97e006001000 97e006001000 1000 UC RUNTIME   
Physical memory chunk(s):   
  0x0050 - 0xfff0f, 65516 MB (16772096 pages)   
  0x140 - 0x10ffe71cfff, 65507 MB (16769821 pages)  
  0x10ffe788000 - 0x10fff3b7fff,12 MB (   3120 pages)   
  0x10ff000 - 0x10f, 0 MB (  1 pages)   
Excluded memory regions:
  0x0050 - 0x00cf, 8 MB (   2048 

[Bug 231070] Crash in nvme_qpair_reset() on base/head r338418 on VirtualBox 5.2.18

2018-09-05 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=231070

trond.endres...@ximalas.info changed:

   What|Removed |Added

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

--- Comment #2 from trond.endres...@ximalas.info ---
As of base/head r338471, the VirtualBox NVMe controller is back in business.
Case closed.

-- 
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 231172] [sshd] ssh login fails if server is set sysctl kern.trap_enotcap=1

2018-09-05 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=231172

--- Comment #1 from Mariusz Zaborski  ---
Could you add the patch to http://reviews.freebsd.org/ ?
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 231181] random(4): Error transitioning from unseeded to seeded state

2018-09-05 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=231181

Conrad Meyer  changed:

   What|Removed |Added

 Blocks||228911
   Assignee|b...@freebsd.org|c...@freebsd.org

--- Comment #1 from Conrad Meyer  ---
Suggest blocker status for 12.0 release, but I am not tied to it (relatively
uncommon to be in an unseeded state and such configurations *could* work around
it).


Referenced Bugs:

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=228911
[Bug 228911] FreeBSD 12.0 Release action items
-- 
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 231181] random(4): Error transitioning from unseeded to seeded state

2018-09-05 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=231181

Bug ID: 231181
   Summary: random(4): Error transitioning from unseeded to seeded
state
   Product: Base System
   Version: CURRENT
  Hardware: Any
OS: Any
Status: New
  Severity: Affects Only Me
  Priority: ---
 Component: kern
  Assignee: b...@freebsd.org
  Reporter: c...@freebsd.org

Reported here:

https://lists.freebsd.org/pipermail/freebsd-current/2018-September/071067.html

Review out here:

https://reviews.freebsd.org/D17049

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


Classic Gear Priced to Sell

2018-09-05 Thread Denmark Street Guitars
[[HEADLINE]]

[[PERMALINK_FULL_LINK]]







TITLE OF YOUR EMAIL

The content of your email goes here.

You can drag and drop blocks of text, images or other content elements to add 
them to your message. Customize the font and the colors. Add links to track 
clicks.







This is a second paragraph you can customize as your please.

If you have stored contact properties with your contacts, you can include 
personalization variables such as first name, last name in your message content.



[[DELIVERY_INFO]]
[[POSTAL_ADDRESS]]
___
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 229682] x11/xterm (possible terminal driver problem): UTF-8 characters cause the misalignment of tabstops

2018-09-05 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=229682

--- Comment #15 from Emanuel Haupt  ---
Sounds good to me.

-- 
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 203349] [META] FreeBSD Foundation sponsored project dependencies for FreeBSD 11.x

2018-09-05 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=203349

Mark Linimon  changed:

   What|Removed |Added

   Keywords||tracking

-- 
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 231027] [META] FreeBSD-Foundation sponsored issues for FreeBSD 13-CURRENT

2018-09-05 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=231027

Mark Linimon  changed:

   What|Removed |Added

   Keywords||tracking

-- 
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 229046] [meta] objdump removal tracking PR

2018-09-05 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=229046

Mark Linimon  changed:

   What|Removed |Added

   Keywords||tracking

-- 
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 230240] import clang 7.0.0 (tracking PR)

2018-09-05 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=230240

Mark Linimon  changed:

   What|Removed |Added

   Keywords||tracking

-- 
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 231169] ix0: link state changed to DOWN

2018-09-05 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=231169

Mark Linimon  changed:

   What|Removed |Added

 CC||sbr...@freebsd.org
   Keywords||IntelNetworking, regression
   Assignee|b...@freebsd.org|n...@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 231166] 11.1->11.2 Update brings em network link state flapping

2018-09-05 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=231166

Mark Linimon  changed:

   What|Removed |Added

 CC||sbr...@freebsd.org
   Keywords||IntelNetworking, regression
   Assignee|b...@freebsd.org|n...@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 231172] [sshd] ssh login fails if server is set sysctl kern.trap_enotcap=1

2018-09-05 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=231172

Mark Linimon  changed:

   What|Removed |Added

Summary|ssh login fails if server   |[sshd] ssh login fails if
   |is set sysctl   |server is set sysctl
   |kern.trap_enotcap=1 |kern.trap_enotcap=1
   Keywords||patch

-- 
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 231027] [META] FreeBSD-Foundation sponsored issues for FreeBSD 13-CURRENT

2018-09-05 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=231027

Ed Maste  changed:

   What|Removed |Added

 Depends on||211516


Referenced Bugs:

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=211516
[Bug 211516] lldb: single stepping does not work on arm
-- 
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 211516] lldb: single stepping does not work on arm

2018-09-05 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=211516

Ed Maste  changed:

   What|Removed |Added

 Blocks||231027


Referenced Bugs:

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=231027
[Bug 231027] [META] FreeBSD-Foundation sponsored issues for FreeBSD 13-CURRENT
-- 
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 231166] 11.1->11.2 Update brings em network link state flapping

2018-09-05 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=231166

--- Comment #2 from Compri  ---
from intel manual, try this:

Important system configuration changes:
  ---

  When there is a choice run on a 64bit OS rather than 32, it makes a 
  significant difference in improvement.

  The interface can generate high number of interrupts. To avoid running 
  into the limit set by the kernel, adjust hw.intr_storm_threshold 
  setting using sysctl:

   sysctl hw.intr_storm_threshold=9000 (the default is 1000)

  For this change to take effect on boot, edit /etc/sysctl.conf and add the 
  line:  
   hw.intr_storm_threshold=9000

  If you still see Interrupt Storm detected messages, increase the limit to a
  higher number.

  Best throughput results are seen with a large MTU; use 9000 if possible.

-- 
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 229682] x11/xterm (possible terminal driver problem): UTF-8 characters cause the misalignment of tabstops

2018-09-05 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=229682

--- Comment #14 from dic...@his.com ---
A patch to the initialization seems like clutter.

If I added a tabs keyword to the ttyModes resource parsing,
then that could be patched in the system's app-defaults file.

-- 
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 231172] ssh login fails if server is set sysctl kern.trap_enotcap=1

2018-09-05 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=231172

Bug ID: 231172
   Summary: ssh login fails if server is set sysctl
kern.trap_enotcap=1
   Product: Base System
   Version: CURRENT
  Hardware: Any
OS: Any
Status: New
  Severity: Affects Some People
  Priority: ---
 Component: bin
  Assignee: b...@freebsd.org
  Reporter: naito.yuich...@gmail.com

Created attachment 196883
  --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=196883=edit
sshd.patch

Problem
---

While I'm debugging my program which runs in capability mode on remote machine,
I set sysctl kern.trap_enotcap=1 to make my kernel triggers SIGTRAP when
capability violation occurs.

If I quit a ssh session by accident, I can never ssh login again.

Reason
--

Sshd uses login_getpwclass(3) for authentication, but it is not allowed in
capability mode because of accessing to '/etc/login.conf' and
'${HOME}/.login.conf'. Authentication failure triggers to close ssh session.

Please note that this is not a security problem. Sshd checks
login_getpwclass(3)
in several times. One of these checks is sandboxed and fails in capability
mode.

And sshd calls auth_timeok(3) after login_getpwcalss(3). In auth_timeok(3),
localtime(3) is called and it opens '/etc/localtime'. This is not allowed
neither.

Reproduce
-

1. stop sshd
   # service sshd stop

2. set kern.trap_enotcap=1
   # sysctl kern.trap_enotcap=1

3. truss sshd
   # truss -f -o /tmp/sshd.log /usr/sbin/sshd -D

4. ssh login
   $ ssh localhost

5. check the logfile
   $ grep 'capability' /tmp/sshd.log
 6637: lstat("/etc/login.conf",0x7fffd850)   ERR#94 'Not permitted in
capability mode'

Workaround
--

Apply the attached `sshd.patch` and rebuild sshd. This patch adds wrapper
function of login_getpwclass(3), and fixes the sandboxed process to call this
function.

Question


I know sshd is a contributed software from OpenSSH project. And it seems
FreeBSD project applies specific patches to sshd. Is my code a part of FreeBSD
specific patches? If so, please review my code.

-- 
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 231166] 11.1->11.2 Update brings em network link state flapping

2018-09-05 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=231166

Compri  changed:

   What|Removed |Added

 CC||to...@compri.pl

--- Comment #1 from Compri  ---
Hi, it seems to be, a problem looks at similar  on my case:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=231169

-- 
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 231169] ix0: link state changed to DOWN

2018-09-05 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=231169

Bug ID: 231169
   Summary: ix0: link state changed to DOWN
   Product: Base System
   Version: 11.2-RELEASE
  Hardware: amd64
OS: Any
Status: New
  Severity: Affects Only Me
  Priority: ---
 Component: kern
  Assignee: b...@freebsd.org
  Reporter: to...@compri.pl

I've got a problem on the production server after upgrade from 11.1-p2 to
11.2-p13

Sep  4 18:10:11 master kernel: ix0: link state changed to DOWN
Sep  4 18:34:03 master kernel: ix0: link state changed to UP
Sep  4 18:34:07 master kernel: ix0: link state changed to DOWN
Sep  4 18:34:31 master kernel: ix0: link state changed to UP
Sep  4 19:11:49 master kernel: ix0: link state changed to DOWN


about if 

Sep  4 19:32:59 master kernel: ix0:  mem 0xfbc0-0xfbdf,0xfbe04000-0xfbe07fff irq
11 at device 0.0 on pci4
Sep  4 19:32:59 master kernel: ix0: Using MSI-X interrupts with 9 vectors
Sep  4 19:32:59 master kernel: ix0: Ethernet address: ac:1f:6b:6a:4c:ce
Sep  4 19:32:59 master kernel: ix0: netmap queues/slots: TX 8/2048, RX 8/2048

-- 
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 229682] x11/xterm (possible terminal driver problem): UTF-8 characters cause the misalignment of tabstops

2018-09-05 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=229682

--- Comment #13 from Emanuel Haupt  ---
Created attachment 196880
  --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=196880=edit
Screenshot

Thank you for clarifying. I've seen that other terminals (gnome-terminal,
xfce4-terminal) already use tab0 by default.

The attached quick patch seems to do the trick (see screenshot). Thomas, would
it be acceptable to to add a ifdef __freebsd__ macro in main.c setting
d_tio.c_oflag to TAB0?

-- 
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 229682] x11/xterm (possible terminal driver problem): UTF-8 characters cause the misalignment of tabstops

2018-09-05 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=229682

--- Comment #12 from Emanuel Haupt  ---
Created attachment 196879
  --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=196879=edit
patch setting oflags to TAB0 by default

Screenshot showing stty behaviour

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