[Bug 221480] Add zpool get ashift POOL function

2017-08-13 Thread bugzilla-noreply 
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=221480

Bug ID: 221480
   Summary: Add zpool get ashift POOL function
   Product: Base System
   Version: CURRENT
  Hardware: Any
OS: Any
Status: New
  Severity: Affects Many People
  Priority: ---
 Component: kern
  Assignee: freebsd-bugs@FreeBSD.org
  Reporter: katy_k...@yahoo.com

The ZFS on Linux project has a simple way to display the ashift value of a
pool;

# zpool get ashift rpool
NAME   PROPERTY  VALUE  SOURCE
rpool  ashift12 local

It would be nice if FreeBSD had a similar function. (Obviously it's a Read/Only
type of value.)

Natually this is low priority, in the feature request category.

-- 
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 221356] [patch] Improve swapon_check_swzone() function in swap_pager.c

2017-08-13 Thread bugzilla-noreply 
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=221356

--- Comment #2 from o...@j.email.ne.jp ---
Thank you for your feedback.

I looked at https://reviews.freebsd.org/D11435 and my patch doesn't interfere
much yet.

Your side of changes looks quite involved and changes how swap information is
managed.  Do you plan to MFC to 11/stable?

-- 
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 202703] geom_eli_passphrase_prompt doesn't work with (at least) various USB keyboards

2017-08-13 Thread bugzilla-noreply 
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=202703

--- Comment #5 from Allan Jude  ---
(In reply to Ed Maste from comment #4)
This is not my feature, it is dteske@'s.

The loader is a very limited environment, and it depends on BIOS support for
the USB keyboard, and does not support any kind of alternative keyboard layout.

EFI might be the only hope users have of getting something slightly better.

-- 
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 221405] Supermicro X10Dri-T motherboard sometimes fails to boot

2017-08-13 Thread bugzilla-noreply 
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=221405

--- Comment #4 from Rajil Saraswat  ---
The culprit was the USB-3 card

[code]
xhci1@pci0:129:0:0: class=0x0c0330 card=0x00141912 chip=0x00141912 rev=0x03
hdr=0x00
vendor = 'Renesas Technology Corp.'
device = 'uPD720201 USB 3.0 Host Controller'
class  = serial bus
subclass   = USB
[/code]

The cards i tried were the following based on uPD720201 chipset
Mailiya PCI-E to USB 3.0 4 Port PCI Express Expansion Card (PCIe Card)
https://www.amazon.com/Mailiya-Expansion-Superspeed-Connector-Desktops/dp/B01G86538S
and 
Rosewill PCI-E to USB 3.0 4-Port PCI Express Expansion Card
https://www.amazon.com/dp/B011LZY20G

Both cause the hangup at boot. After removing the card the system boots up
fine.

-- 
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 221476] bisalah

2017-08-13 Thread bugzilla-noreply 
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=221476

Bug ID: 221476
   Summary: bisalah
   Product: Base System
   Version: 8.4-STABLE
  Hardware: Any
OS: Any
Status: New
  Severity: Affects Only Me
  Priority: ---
 Component: bin
  Assignee: freebsd-bugs@FreeBSD.org
  Reporter: yonkou...@gmail.com

Created attachment 185363
  --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=185363=edit
fix jadi

-- 
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 210415] vidcontrol -h does not work with vt(4)

2017-08-13 Thread bugzilla-noreply 
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=210415

Ed Maste  changed:

   What|Removed |Added

URL||https://reviews.freebsd.org
   ||/D11814

-- 
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 210413] vidcontrol -c <normal|blink|destructive> does not work with vt(4)

2017-08-13 Thread bugzilla-noreply 
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=210413

Ed Maste  changed:

   What|Removed |Added

URL||https://reviews.freebsd.org
   ||/D11753

-- 
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 202703] geom_eli_passphrase_prompt doesn't work with (at least) various USB keyboards

2017-08-13 Thread bugzilla-noreply 
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=202703

Ed Maste  changed:

   What|Removed |Added

 Status|Closed  |Open
 CC||allanj...@freebsd.org,
   ||ema...@freebsd.org
 Resolution|Works As Intended   |---

--- Comment #4 from Ed Maste  ---
Allan, any ideas?

-- 
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 221462] vtnet gets stuck when assigning IP on aarch64

2017-08-13 Thread bugzilla-noreply 
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=221462

Bug ID: 221462
   Summary: vtnet gets stuck when assigning IP on aarch64
   Product: Base System
   Version: CURRENT
  Hardware: arm64
OS: Any
Status: New
  Severity: Affects Many People
  Priority: ---
 Component: kern
  Assignee: freebsd-bugs@FreeBSD.org
  Reporter: gergely.czu...@harmless.hu

Hello,

In a qemu VM, when trying to have networking using the virtio-net-device
device, assigning an IP address to the vtnet0 device gets ifconfig stuck in an
uninterruptable state.

Tried it with qemu 2.8.0, 2.8.1 and 2.9.0.

FreeBSD version:
# uname -a
FreeBSD build-aarch64.marvin.harmless.hu 12.0-CURRENT FreeBSD 12.0-CURRENT #0
r322371: Thu Aug 10 21:09:06 CEST 2017
t...@marvin.harmless.hu:/tank/rpi3/obj/arm64.aarch64/tank/rpi3/src/sys/GENERIC-NODEBUG
 arm64

vtnet0 device:
vtnet0: flags=8802 metric 0 mtu 1500
options=80028
ether 52:54:00:12:34:56
media: Ethernet 10Gbase-T 
status: active
nd6 options=29
lo0: flags=8049 metric 0 mtu 16384
vtnet0:  on virtio_mmio30
vtnet0: Ethernet address: 52:54:00:12:34:56


QEMU cmdline:
qemu-system-aarch64 -m 4096M -cpu cortex-a57 -M virt  \
-accel tcg,thread=single \
-bios QEMU_EFI.fd -serial telnet::,server -nographic \
-drive if=none,file=${image},id=hd0,format=raw \
-device virtio-blk-device,drive=hd0 \
-device virtio-net-device,netdev=net0 \
-netdev
tap,id=net0,ifname=tap0,script=/tank/rpi3/build/qemu-ifup.sh

Should be easy to reproduce, just add a vtnet device into a qemu-system-aarch64
VM, and try assigning an IP.

Best regards,
Gergely

-- 
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 221487] [bsnmpd] crashes on startup with the enabled module begemotSnmpdModulePath."pf"

2017-08-13 Thread bugzilla-noreply 
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=221487

Bug ID: 221487
   Summary: [bsnmpd] crashes on startup with the enabled module
begemotSnmpdModulePath."pf"
   Product: Base System
   Version: 11.1-STABLE
  Hardware: Any
OS: Any
Status: New
  Severity: Affects Only Me
  Priority: ---
 Component: bin
  Assignee: freebsd-bugs@FreeBSD.org
  Reporter: ad...@support.od.ua

Bsnmpd crashes on startup with the enabled module begemotSnmpdModulePath."pf"

FreeBSD tank1.storage.com 11.1-STABLE FreeBSD 11.1-STABLE #0 r322164: Mon Aug 
7 15:33:19 UTC 2017
r...@releng2.nyi.freebsd.org:/usr/obj/usr/src/sys/GENERIC  amd64

I uncomment string
#begemotSnmpdModulePath."pf"= "/usr/lib/snmp_pf.so"
in the file /etc/snmpd.config

And after running command service bsnmpd onestart received errors:
...
Aug 12 14:02:19 tank1 snmpd[819]: disk_OS_get_disks: adding device 'ada0' to
device list
Aug 12 14:02:19 tank1 snmp_lm75[819]: pf_init(): open(): No such file or
directory
Aug 12 14:02:19 tank1 kernel: Aug 12 14:02:19 tank1 snmp_lm75[819]: pf_init():
open(): No such file or directory
Aug 12 14:02:19 tank1 snmp_lm75[819]: lm_load: init failed: -1
Aug 12 14:02:19 tank1 kernel: Aug 12 14:02:19 tank1 snmp_lm75[819]: lm_load:
init failed: -1
Aug 12 14:02:19 tank1 snmp_lm75[819]: init dep failed: 13
1.3.6.1.4.1.12325.1.1.1.6 2.112.102
Aug 12 14:02:19 tank1 kernel: Aug 12 14:02:19 tank1 snmp_lm75[819]: init dep
failed: 13 1.3.6.1.4.1.12325.1.1.1.6 2.112.102
Aug 12 14:02:19 tank1 kernel: pid 819 (bsnmpd), uid 0: exited on signal 11
(core dumped)

I understand that you need to load the kernel module PF (/boot/kernel/pf.ko)
And then bsnmpd with this module will not crash.

-- 
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 221501] [msdosfs] panic 11.0-RELEASE by mounting a malformed msdosfs image

2017-08-13 Thread bugzilla-noreply 
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=221501

--- Comment #2 from Conrad Meyer  ---
Additionally, a gdb backtrace of the core would be useful.

-- 
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 221367] i386 sanitizer runtimes not installed during amd64 32-bit compat in make installworld

2017-08-13 Thread bugzilla-noreply 
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=221367

--- Comment #2 from Dimitry Andric  ---
(In reply to Ed Maste from comment #1)
> It seems just removing MK_TOOLCHAIN=no from Makefile.libcompat causes these
> additional files to be installed:
> 
> ===> libc (install)
> ...
> install  -o root -g wheel -m 444   libc_pic.a /usr/lib32/
> ...
> ===> libclang_rt (install)

Okay, but won't that also cause 32-bit versions of libllvm, libclang and clang
itself to be built?  We definitely don't want that. :)

-- 
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 221501] [msdosfs] panic 11.0-RELEASE by mounting a malformed msdosfs image

2017-08-13 Thread bugzilla-noreply 
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=221501

Bug ID: 221501
   Summary: [msdosfs] panic 11.0-RELEASE by mounting a malformed
msdosfs image
   Product: Base System
   Version: 11.0-RELEASE
  Hardware: Any
OS: Any
Status: New
  Severity: Affects Many People
  Priority: ---
 Component: kern
  Assignee: freebsd-bugs@FreeBSD.org
  Reporter: open.sou...@ribose.com

It is possible to panic 11.0-RELEASE by mounting a malformed msdosfs image.

The malformed msdosfs image can be found at the github URL at the bottom of
this message.

Console output:
panic: vm_fault: fault on nofault entry, addr: fe003d591000
cpuid = 0
KDB: stack backtrace:
#0 0x80b24077 at kdb_backtrace+0x67
#1 0x80ad93e2 at vpanic+0x182
#2 0x80ad9253 at panic+0x43
#3 0x80e12601 at vm_fault_hold+0x2721
#4 0x80e0fe98 at vm_fault+0x78
#5 0x80fa0e39 at trap_pfault+0x78
#6 0x80fa04cc at trap+0x26c
#7 0x80f84141 at calltrap+0x8
#8 0x8098e8f6 at msdosfs_mount+0x10f6
#9 0x80ba1ae0 at vfs_donmount+0xf90
#10 0x80ba0b22 at sys_nmount+0x72
#11 0x80fa168e at amd64_syscall+0x4ce
#12 0x80f8442b at Xfast_syscall+0xfb
Uptime: 4m39s
Dumping 116 out of 991 MB

dmesg:
Copyright (c) 1992-2016 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 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
FreeBSD clang version 3.8.0 (tags/RELEASE_380/final 262564) (based on LLVM
3.8.0)
VT(vga): text 80x25
CPU: Intel(R) Core(TM) i7-4850HQ CPU @ 2.30GHz (2294.74-MHz K8-class CPU)
  Origin="GenuineIntel"  Id=0x40661  Family=0x6  Model=0x46  Stepping=1
 
Features=0x783fbff
 
Features2=0x5ed8220b
  AMD Features=0x28100800
  AMD Features2=0x21
  Structured Extended Features=0x2000
  TSC: P-state invariant
real memory  = 1073676288 (1023 MB)
avail memory = 996921344 (950 MB)
Event timer "LAPIC" quality 400
ACPI APIC Table: 
random: unblocking device.
ioapic0: Changing APIC ID to 1
ioapic0  irqs 0-23 on motherboard
random: entropy device external interface
kbd1 at kbdmux0
netmap: loaded module
module_register_init: MOD_LOAD (vesa, 0x8101c950, 0) error 19
random: registering fast source Intel Secure Key RNG
random: fast provider: "Intel Secure Key RNG"
vtvga0:  on motherboard
cryptosoft0:  on motherboard
acpi0:  on motherboard
acpi0: Power Button (fixed)
acpi0: Sleep Button (fixed)
cpu0:  on acpi0
attimer0:  port 0x40-0x43,0x50-0x53 on acpi0
Timecounter "i8254" frequency 1193182 Hz quality 0
Event timer "i8254" frequency 1193182 Hz quality 100
Timecounter "ACPI-fast" frequency 3579545 Hz quality 900
acpi_timer0: <32-bit timer at 3.579545MHz> port 0x4008-0x400b on acpi0
pcib0:  port 0xcf8-0xcff on acpi0
pci0:  on pcib0
isab0:  at device 1.0 on pci0
isa0:  on isab0
atapci0:  port
0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xd000-0xd00f at device 1.1 on pci0
ata0:  at channel 0 on atapci0
ata1:  at channel 1 on atapci0
vgapci0:  mem 0xe000-0xe0ff irq 18 at device
2.0 on pci0
vgapci0: Boot video device
em0:  port 0xd010-0xd017 mem
0xf000-0xf001 irq 19 at device 3.0 on pci0
em0: Ethernet address: 08:00:27:dd:aa:53
em0: netmap queues/slots: TX 1/256, RX 1/256
ohci0:  mem 0xf0804000-0xf0804fff irq
22 at device 6.0 on pci0
usbus0 on ohci0
pci0:  at device 7.0 (no driver attached)
ehci0:  mem 0xf0805000-0xf0805fff irq
19 at device 11.0 on pci0
usbus1: EHCI version 1.0
usbus1 on ehci0
battery0:  on acpi0
acpi_acad0:  on acpi0
atkbdc0:  port 0x60,0x64 irq 1 on acpi0
atkbd0:  irq 1 on atkbdc0
kbd0 at atkbd0
atkbd0: [GIANT-LOCKED]
psm0:  irq 12 on atkbdc0
psm0: [GIANT-LOCKED]
psm0: model IntelliMouse Explorer, device ID 4
orm0:  at iomem 0xc-0xc7fff,0xe2000-0xe2fff on isa0
vga0:  at port 0x3c0-0x3df iomem 0xa-0xb on isa0
atrtc0:  at port 0x70 irq 8 on isa0
Event timer "RTC" frequency 32768 Hz quality 0
ppc0: cannot reserve I/O port range
Timecounters tick every 1.000 msec
nvme cam probe device init
usbus0: 12Mbps Full Speed USB v1.0
usbus1: 480Mbps High Speed USB v2.0
ugen0.1:  at usbus0
uhub0:  on usbus0
ugen1.1:  at usbus1
uhub1:  on usbus1
cd0 at ata1 bus 0 scbus1 target 0 lun 0
cd0:  Removable CD-ROM SCSI device
cd0: Serial Number VB2-01700376
cd0: 33.300MB/s transfers (UDMA2, ATAPI 12bytes, PIO 65534bytes)
cd0: Attempt to query device size failed: NOT READY, Medium not present
ada0 at ata0 bus 0 scbus0

[Bug 211852] Unsafe shutdowns on Intel 750 SSD

2017-08-13 Thread bugzilla-noreply 
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=211852

--- Comment #9 from Ravi Pokala  ---
Repeating my earlier question:

> Perhaps we should make the SHN wait time configurable? Default to 5 seconds, 
> overridden by RTD3E if present, overridden by per-device sysctl if set?

-- 
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 221497] Inconsistency in NETWORK group files rights for PPP

2017-08-13 Thread bugzilla-noreply 
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=221497

Bug ID: 221497
   Summary: Inconsistency in NETWORK group files rights for PPP
   Product: Base System
   Version: 11.1-RELEASE
  Hardware: Any
OS: Any
Status: New
  Severity: Affects Some People
  Priority: ---
 Component: misc
  Assignee: freebsd-bugs@FreeBSD.org
  Reporter: verma...@interia.pl

Most files related to PPP have 'network' group set by default:

# find / -group network
/usr/sbin/ppp
/var/run/ppp
/var/log/ppp.log.1.bz2
/var/log/ppp.log
/var/log/ppp.log.0.bz2

# find / -group network -ls
369220   577 -r-sr-xr--  1 root network  433872 Jul 27 04:30 /usr/sbin/ppp
 14054 1 drwxrwx---  2 root network   2 Jun 30 04:25 /var/run/ppp
 6687217 -rw-r-  1 root network6046 Aug  4 18:00
/var/log/ppp.log.1.bz2
403990 9 -rw-r-  1 root network3180 Aug 11 16:19 /var/log/ppp.log
40399217 -rw-r-  1 root network6258 Aug 11 10:00
/var/log/ppp.log.0.bz2

But why '/etc/ppp' and '/etc/ppp/ppp.conf' does not have 'network' group and
have wheel group?

Regards,
vermaden

-- 
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 221501] [msdosfs] panic 11.0-RELEASE by mounting a malformed msdosfs image

2017-08-13 Thread bugzilla-noreply 
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=221501

--- Comment #3 from open.sou...@ribose.com ---
(In reply to Conrad Meyer from comment #1)

# kgdb
GNU gdb 6.1.1 [FreeBSD]
Copyright 2004 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB.  Type "show warranty" for details.
This GDB was configured as "amd64-marcel-freebsd"...
#0  sched_switch (td=0xf80003519000, newtd=0xf800032ffa00, flags=) at /usr/src/sys/kern/sched_ule.c:1973
1973cpuid = PCPU_GET(cpuid);
(kgdb) l *(msdosfs_mount+0x10f6)
0x8098e8f6 is in msdosfs_mount
(/usr/src/sys/fs/msdosfs/msdosfs_vfsops.c:730).
725 
726 /*
727  * Have the inuse map filled in.
728  */
729 MSDOSFS_LOCK_MP(pmp);
730 error = fillinusemap(pmp);
731 MSDOSFS_UNLOCK_MP(pmp);
732 if (error != 0)
733 goto error_exit;
734 
Current language:  auto; currently minimal
(kgdb)

crash backtrace:

# kgdb /boot/kernel/kernel /var/crash/vmcore.0 
GNU gdb 6.1.1 [FreeBSD]
Copyright 2004 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB.  Type "show warranty" for details.
This GDB was configured as "amd64-marcel-freebsd"...

Unread portion of the kernel message buffer:
panic: vm_fault: fault on nofault entry, addr: fe003d2dd000
cpuid = 0
KDB: stack backtrace:
#0 0x80b24077 at kdb_backtrace+0x67
#1 0x80ad93e2 at vpanic+0x182
#2 0x80ad9253 at panic+0x43
#3 0x80e12601 at vm_fault_hold+0x2721
#4 0x80e0fe98 at vm_fault+0x78
#5 0x80fa0e39 at trap_pfault+0xf9
#6 0x80fa04cc at trap+0x26c
#7 0x80f84141 at calltrap+0x8
#8 0x8098e8f6 at msdosfs_mount+0x10f6
#9 0x80ba1ae0 at vfs_donmount+0xf90
#10 0x80ba0b22 at sys_nmount+0x72
#11 0x80fa168e at amd64_syscall+0x4ce
#12 0x80f8442b at Xfast_syscall+0xfb
Uptime: 1m38s
Dumping 101 out of 991 MB:..16%..32%..48%..63%..79%..95%

#0  doadump (textdump=) at pcpu.h:221
221 pcpu.h: No such file or directory.
in pcpu.h
(kgdb) bt
#0  doadump (textdump=) at pcpu.h:221
#1  0x80ad8e69 in kern_reboot (howto=260) at
/usr/src/sys/kern/kern_shutdown.c:366
#2  0x80ad941b in vpanic (fmt=, ap=) at /usr/src/sys/kern/kern_shutdown.c:759
#3  0x80ad9253 in panic (fmt=0x0) at
/usr/src/sys/kern/kern_shutdown.c:690
#4  0x80e12601 in vm_fault_hold (map=,
vaddr=, fault_type=, 
fault_flags=, m_hold=) at
/usr/src/sys/vm/vm_fault.c:330
#5  0x80e0fe98 in vm_fault (map=0xf8000300, vaddr=, fault_type=1 '\001', fault_flags=)
at /usr/src/sys/vm/vm_fault.c:273
#6  0x80fa0e39 in trap_pfault (frame=0xfe230410, usermode=0) at
/usr/src/sys/amd64/amd64/trap.c:741
#7  0x80fa04cc in trap (frame=0xfe230410) at
/usr/src/sys/amd64/amd64/trap.c:442
#8  0x80f84141 in calltrap () at
/usr/src/sys/amd64/amd64/exception.S:236
#9  0x8098abdb in fillinusemap (pmp=) at
/usr/src/sys/fs/msdosfs/msdosfs_fat.c:904
#10 0x8098e8f6 in msdosfs_mount (mp=0xf800038bf000) at
/usr/src/sys/fs/msdosfs/msdosfs_vfsops.c:730
#11 0x80ba1ae0 in vfs_donmount (td=,
fsflags=, fsoptions=)
at /usr/src/sys/kern/vfs_mount.c:818
#12 0x80ba0b22 in sys_nmount (td=0xf800038cd500,
uap=0xfe230a40) at /usr/src/sys/kern/vfs_mount.c:417
#13 0x80fa168e in amd64_syscall (td=, traced=0) at
subr_syscall.c:135
#14 0x80f8442b in Xfast_syscall () at
/usr/src/sys/amd64/amd64/exception.S:396
#15 0x000800a70f6a in ?? ()
Previous frame inner to this frame (corrupt stack?)
Current language:  auto; currently minimal
(kgdb)

-- 
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 221503] bugindo

2017-08-13 Thread bugzilla-noreply 
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=221503

Bug ID: 221503
   Summary: bugindo
   Product: Base System
   Version: 8.4-RELEASE
  Hardware: Any
OS: Any
Status: New
  Severity: Affects Only Me
  Priority: ---
 Component: bin
  Assignee: freebsd-bugs@FreeBSD.org
  Reporter: kurniawanpu...@gmail.com

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

aku

-- 
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 221505] wqe

2017-08-13 Thread bugzilla-noreply 
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=221505

Bug ID: 221505
   Summary: wqe
   Product: Base System
   Version: 9.1-STABLE
  Hardware: Any
OS: Any
Status: New
  Severity: Affects Only Me
  Priority: ---
 Component: conf
  Assignee: freebsd-bugs@FreeBSD.org
  Reporter: z4sc...@gmail.com

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

eqwe

-- 
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 221492] Creating stf interface as "stf" causes kernel panic

2017-08-13 Thread bugzilla-noreply 
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=221492

Bug ID: 221492
   Summary: Creating stf interface as "stf" causes kernel panic
   Product: Base System
   Version: 11.1-RELEASE
  Hardware: Any
OS: Any
Status: New
  Severity: Affects Some People
  Priority: ---
 Component: kern
  Assignee: freebsd-bugs@FreeBSD.org
  Reporter: ult...@freebsd.org

This is easily reproducible and have triggered it on two 11.1-RELEASE boxes.


ifconfig stf create --> kernel panic.

Adding a number to stf, eg stf0 or stf1 the interface is created as expected.
This is a bug that should be fixed, but probably doesn't affect majority of
users.

Also tested on head r321403 and appears to be fixed.

-- 
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 202703] geom_eli_passphrase_prompt doesn't work with (at least) various USB keyboards

2017-08-13 Thread bugzilla-noreply 
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=202703

--- Comment #6 from Devin Teske  ---
Try this in /boot/loader.conf

hint.atkbdc.0.disabled="1"

-- 
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 221501] [msdosfs] panic 11.0-RELEASE by mounting a malformed msdosfs image

2017-08-13 Thread bugzilla-noreply 
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=221501

Conrad Meyer  changed:

   What|Removed |Added

 CC||c...@freebsd.org

--- Comment #1 from Conrad Meyer  ---
Can you please run 'kgdb' on your 11.0 system and report the output of:

  l *(msdosfs_mount+0x10f6)

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"

Re: [Bug 221501] [msdosfs] panic 11.0-RELEASE by mounting a malformed msdosfs image

2017-08-13 Thread Bruce Evans 

On Mon, 14 Aug 2017 a big that doesn't want repl...@freebsd.org wrote:


It is possible to panic 11.0-RELEASE by mounting a malformed msdosfs image.


Did you check it with fsck before mounting?  Otherwise the problem is
probably uninteresting.  No file system in FreeBSD except possibly zfs
does much sanity checking at mount time, so it is trivial to construct
images that crash it.

msdosfs actually does much more sanity checking than ffs.  It checks
about 100 bytes where ffs checks about 20.  However, msdosfs is missing
a check of its dirty flag.  This doesn't affect crashing it much, but
it affects damaging the file system further.  ffs allows read-only
mounts of dirty images.  msdosfs also allows red-write mounts of dirty
images.  If you run fsck before mounting, then should set the dirty
flag if it fails.  For ffs, this prevents the read-write case from
getting very far.

Bruce
___
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 221480] ZFS - Add zpool get ashift POOL function

2017-08-13 Thread bugzilla-noreply 
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=221480

Arwen Evenstar  changed:

   What|Removed |Added

Summary|Add zpool get ashift POOL   |ZFS - Add zpool get ashift
   |function|POOL function

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