[Bug 204521] [new driver] [request] Port rtsx from OpenBSD to FreeBSD

2019-12-21 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=204521

--- Comment #33 from Gary Jennejohn  ---
I tried implementing rtsx_xfer_bounce() from the OpenBSD code.

OpenBSD uses this function when the upstream code does not pass in a list of
DMA scatter-gather addresses.  Normally, the SD code in OpenBSD allocates its
own DMA buffers and passes them to the driver.

Since FreeBSD does not do that - it either uses buffers on the kernel stack or
buffers from a struct bio - it seemed logical to me to try rtsx_xfer_bouce().

The DMA transfer raises an interrupt, but the target buffer is always filled
with 0s.

I'm running out of ideas on how to get DMA to work.

If I had a laptop I could tear apart I'd put a logic analyzer on the controller
pins and compare the behavior between OpenBSD and FreeBSD.  Unfortunately, the
laptop I have is a loaner and I can't do 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 207854] usr/src/sys/contrib/ncsw/Peripherals/QM/qm_portal_fqr.c:1437: bad shift ?

2019-12-21 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=207854

--- Comment #9 from commit-h...@freebsd.org ---
A commit references this bug:

Author: arrowd
Date: Sat Dec 21 11:38:48 UTC 2019
New revision: 355980
URL: https://svnweb.freebsd.org/changeset/base/355980

Log:
  Don't shift 32-bit value by more than 32 bits.

  PR:   207854
  Approved by:  emaste

Changes:
  head/sys/contrib/ncsw/Peripherals/QM/qm_portal_fqr.c

-- 
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 207854] usr/src/sys/contrib/ncsw/Peripherals/QM/qm_portal_fqr.c:1437: bad shift ?

2019-12-21 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=207854

Gleb Popov  changed:

   What|Removed |Added

 Status|New |Closed
 Resolution|--- |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 234576] hastd exits ungracefully

2019-12-21 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=234576

jack khan  changed:

   What|Removed |Added

 CC||bihaveg...@seomail.org

--- Comment #8 from jack khan  ---
Followup on this - after a bit more testing, I now get occasional kernel panics
caused by ZFS because the pool is hung, due to the hast vdev.

Despite running the hastd worker process with ktrace attached to it (that made
for a large file) there's no obvious clue as to why it hangs.

I'm going to try a few more bits of logging/debugging to try and understand
what happens - if I can't see what's going on, I'll revert to 11.2 which works
reliably for me.

https://www.amirsdesign.com

https://www.amirsdesign.com/2019/08/pubg-editing-backgound-2019-for-picsart.html

-- 
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 126287] [ufs] [panic] Kernel panics while mounting an UFS filesystem with snapshot enabled

2019-12-21 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=126287

jack khan  changed:

   What|Removed |Added

 CC||bihaveg...@seomail.org

--- Comment #10 from jack khan  ---
This looks great. I only wish that GM would bring the Avalanche back on this
platform with these design aesthetics.


https://www.amirsdesign.com/2019/09/visual-editing-background.html

-- 
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 242768] [panic] Fatal trap 12: current process (nfsd: service)

2019-12-21 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=242768

Bug ID: 242768
   Summary: [panic] Fatal trap 12: current process (nfsd: service)
   Product: Base System
   Version: 12.0-STABLE
  Hardware: amd64
OS: Any
Status: New
  Severity: Affects Only Me
  Priority: ---
 Component: kern
  Assignee: b...@freebsd.org
  Reporter: iron.ud...@gmail.com

OS: 12.1-STABLE r355967

Dec 21 16:06:22 v1 kernel: Fatal trap 12: page fault while in kernel mode
Dec 21 16:06:22 v1 kernel: cpuid = 27; apic id = 23
Dec 21 16:06:22 v1 kernel: fault virtual address= 0x8
Dec 21 16:06:22 v1 kernel: fault code   = supervisor read data, page
not present
Dec 21 16:06:22 v1 kernel: instruction pointer  = 0x20:0x8045534c
Dec 21 16:06:22 v1 kernel: stack pointer=
0x0:0xfe0183ff6d80
Dec 21 16:06:22 v1 kernel: frame pointer=
0x0:0xfe0183ff6e10
Dec 21 16:06:22 v1 kernel: code segment = base 0x0, limit 0xf, type
0x1b
Dec 21 16:06:22 v1 kernel:  = DPL 0, pres 1, long 1, def32
0, gran 1
Dec 21 16:06:22 v1 kernel: processor eflags = interrupt enabled, resume,
IOPL = 0
Dec 21 16:06:22 v1 kernel: current process  = 2694 (nfsd: service)
Dec 21 16:06:22 v1 kernel: trap number  = 12
Dec 21 16:06:22 v1 kernel: panic: page fault
Dec 21 16:06:22 v1 kernel: cpuid = 27
Dec 21 16:06:22 v1 kernel: time = 1576936619

On this server we share static files via NFS4 share.

-- 
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 242771] symbol uart_cpu_acpi_spcr undefined KLD file uart.ko

2019-12-21 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=242771

Bug ID: 242771
   Summary: symbol uart_cpu_acpi_spcr undefined KLD file uart.ko
   Product: Base System
   Version: 12.1-RELEASE
  Hardware: amd64
OS: Any
Status: New
  Severity: Affects Only Me
  Priority: ---
 Component: kern
  Assignee: b...@freebsd.org
  Reporter: e...@free.fr

Hi,

Trying to load uart.ko on a 12.1-STABLE MINIMAL kernel ends in the following
message :
link_elf_obj: symbol uart_cpu_acpi_spcr undefined
KLD file uart.ko - could not finalize loading

Seems to be related to
https://reviews.freebsd.org/D20357

Regards

Éric Masson

-- 
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 241973] Number agreement in gpart(8)

2019-12-21 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=241973

--- Comment #2 from PauAmma  ---
Did the MFC happen yet? (I don't remember seeing one, but I may have missed it
or misremember.) If it did, this bug can be closed, I think.

-- 
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 241973] Number agreement in gpart(8)

2019-12-21 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=241973

--- Comment #3 from commit-h...@freebsd.org ---
A commit references this bug:

Author: markj
Date: Sat Dec 21 16:08:34 UTC 2019
New revision: 355982
URL: https://svnweb.freebsd.org/changeset/base/355982

Log:
  MFC r354824:
  Fix grammar in gpart.8.

  PR:   241973

Changes:
_U  stable/12/
  stable/12/lib/geom/part/gpart.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 241973] Number agreement in gpart(8)

2019-12-21 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=241973

Mark Johnston  changed:

   What|Removed |Added

 Status|New |Closed
 Resolution|--- |FIXED
   Assignee|b...@freebsd.org|ma...@freebsd.org
 CC||ma...@freebsd.org

--- Comment #4 from Mark Johnston  ---
(In reply to PauAmma from comment #2)
Apparently I missed it somehow, even though it was marked as done in my inbox. 
Thanks 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 242773] ata driver as module, interrupt storm on atapci0 and low attachment speed for disks

2019-12-21 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=242773

Bug ID: 242773
   Summary: ata driver as module, interrupt storm on atapci0 and
low attachment speed for disks
   Product: Base System
   Version: 11.3-STABLE
  Hardware: Any
OS: Any
Status: New
  Severity: Affects Only Me
  Priority: ---
 Component: kern
  Assignee: b...@freebsd.org
  Reporter: e...@free.fr

Created attachment 210107
  --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=210107&action=edit
11.3-STABLE dmesg for SE7525GP2

Hi,

Intel SE7525GP2 MB (quite old, I know)

When using MINIMAL and trying to load atapci as module, atapci reports low
speed for attached disks :

ada4 at ata2 bus 0 scbus4 target 0 lun 0
ada4:  ACS-2 ATA SATA 3.x device
ada4: Serial Number 1841B1803114
ada4: 33.000MB/s transfers (UDMA2, PIO 512bytes)
ada4: 114480MB (234455040 512 byte sectors)

Kernel spits messages about interrupt storm on irq used by atapci.

When ata support is compiled into kernel, the reported speed is fine :

ada4 at ata2 bus 0 scbus4 target 0 lun 0
ada4:  ACS-2 ATA SATA 3.x device
ada4: Serial Number 1841B1803114
ada4: 150.000MB/s transfers (SATA 1.x, UDMA5, PIO 512bytes)
ada4: 114480MB (234455040 512 byte sectors)

I've reproduced the same issue using a freshly compiled 12.1-STABLE kernel

Regards

Éric Masson

-- 
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 242784] arp segfault

2019-12-21 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=242784

Bug ID: 242784
   Summary: arp segfault
   Product: Base System
   Version: 12.1-RELEASE
  Hardware: Any
OS: Any
Status: New
  Severity: Affects Some People
  Priority: ---
 Component: bin
  Assignee: b...@freebsd.org
  Reporter: cor...@openmailbox.org

arp segfaulted after I ran "service netif restart". lo0 was up, and wlan0 was
active but I was having problems with it. em0 was there but not connected to
anything.

lldb backtrace gave me:

* thread #1, name = 'arp', stop reason = signal SIGSEGV
  * frame #0: 0x00202bb0 arp`___lldb_unnamed_symbol7$$arp + 304
frame #1: 0x00202a13 arp`___lldb_unnamed_symbol6$$arp + 451
frame #2: 0x002024a4 arp`___lldb_unnamed_symbol4$$arp + 452
frame #3: 0x0020210f arp`___lldb_unnamed_symbol1$$arp + 271

which didn't tell me a lot.

-- 
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 242784] arp segfault

2019-12-21 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=242784

Mark Linimon  changed:

   What|Removed |Added

   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 240485] ig4: Add Cannon Lake LP and H I2C Controller IDs

2019-12-21 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=240485

--- Comment #18 from commit-h...@freebsd.org ---
A commit references this bug:

Author: wulf
Date: Sun Dec 22 00:46:08 UTC 2019
New revision: 355994
URL: https://svnweb.freebsd.org/changeset/base/355994

Log:
  MFC r354291 - r354322, r354327, r355596

  r354291:
  [ig4] Give common name to PCI and ACPI device drivers

  r354292:
  [ig4] Handle controller startup errors

  Obtained from:DragonflyBSD (509820b)

  r354293:
  [ig4] Only enable interrupts when we want them. Otherwise keep mask at 0.

  Obtained from:DragonflyBSD (d7c8555)

  r354294:
  [ig4] Drop driver's internal RX FIFO

  r354295:
  [ig4] Do not wait for interrupts in set_controller() routine

  r354296:
  [ig4] Reduce scope of io_lock

  r354297:
  [ig4] Ignore stray interrupts

  r354298:
  [ig4] We actually need to set the Rx threshold register one smaller.

  Obtained from:DragonflyBSD (02f0bf2)

  r354299:

  [ig4] Stop I2C controller after checking that it's kind of functional.

  Obtained from:DragonfliBSD (0b3eedb)

  r354300:
  [ig4] disable controller before initialization of clock counters

  r354301:
  [ig4] Add support for polled mode

  r354302:
  [ig4] Allow enabling of polled mode from iicbus allocation callback

  r354303:
  [ig4] Do not wait until interrupts are enabled at attach stage

  r354304:
  [cyapa] Postpone start of the polling thread until sleep is available

  r354305:
  [ig4] dump IG4_REG_COMP_PARAM1 and IG4_REG_COMP_VER registers unconditionally

  r354306:
  [ig4] Set clock registers based on controller model

  r354307:
  [ig4] Implement burst mode for data reads

  r354308:
  [ig4] Add suspend/resume support

  PR:   238037

  r354309:
  [ig4] Remove dead code inherited from DragonflyBSD

  r354310:
  [ig4] Rewrite ig4iic_write routine to use TX_EMPTY status flag

  r354311:
  [ig4] Convert last remaining usage of TX_NOTFULL status to TX_EMPTY

  r354312:
  [ig4] Use interrupts for waiting for empty TX FIFO

  r354313:
  [ig4] Convert polling loop from status-based to interrupt-based

  r354314:
  [ig4] Improve error detection

  r354315:
  [ig4] Set STOP condition and flush TX/RX FIFOs on error

  r354316:
  [ig4] On SkyLake controllers issue reset on attach unconditionally.

  r354317:
  [ig4] wait for bus stop condition after stop command issued

  r354318:
  [ig4] Minor improvement of write pipelining

  r354319:
  [ig4] Add generic resource methods to bus interface

  r354320:
  [ig4] Add support for CannonLake controllers

  PR:   240485
  Submitted by: Neel Chauhan 

  r354321:
  [ig4] Enable additional registers support on Appolo Lake controllers

  r354322:
  [ig4] Convert ithread interrupt handler to filter based one.

  r354327:
  [ig4] Try to workaround MIPS namespace pollution issue

  r355596:
  [ig4] Remove unused methods from bus interface

  Suggested by: jhb

  Reviewed by:  imp (previous version)
  Differential Revision:https://reviews.freebsd.org/D22016

Changes:
_U  stable/12/
  stable/12/sys/dev/chromebook_platform/chromebook_platform.c
  stable/12/sys/dev/cyapa/cyapa.c
  stable/12/sys/dev/ichiic/ig4_acpi.c
  stable/12/sys/dev/ichiic/ig4_iic.c
  stable/12/sys/dev/ichiic/ig4_pci.c
  stable/12/sys/dev/ichiic/ig4_reg.h
  stable/12/sys/dev/ichiic/ig4_var.h
  stable/12/sys/dev/iicbus/iicbus.c

-- 
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 238037] [PATCH] Implement ig4 suspend/resume

2019-12-21 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=238037

--- Comment #23 from commit-h...@freebsd.org ---
A commit references this bug:

Author: wulf
Date: Sun Dec 22 00:46:08 UTC 2019
New revision: 355994
URL: https://svnweb.freebsd.org/changeset/base/355994

Log:
  MFC r354291 - r354322, r354327, r355596

  r354291:
  [ig4] Give common name to PCI and ACPI device drivers

  r354292:
  [ig4] Handle controller startup errors

  Obtained from:DragonflyBSD (509820b)

  r354293:
  [ig4] Only enable interrupts when we want them. Otherwise keep mask at 0.

  Obtained from:DragonflyBSD (d7c8555)

  r354294:
  [ig4] Drop driver's internal RX FIFO

  r354295:
  [ig4] Do not wait for interrupts in set_controller() routine

  r354296:
  [ig4] Reduce scope of io_lock

  r354297:
  [ig4] Ignore stray interrupts

  r354298:
  [ig4] We actually need to set the Rx threshold register one smaller.

  Obtained from:DragonflyBSD (02f0bf2)

  r354299:

  [ig4] Stop I2C controller after checking that it's kind of functional.

  Obtained from:DragonfliBSD (0b3eedb)

  r354300:
  [ig4] disable controller before initialization of clock counters

  r354301:
  [ig4] Add support for polled mode

  r354302:
  [ig4] Allow enabling of polled mode from iicbus allocation callback

  r354303:
  [ig4] Do not wait until interrupts are enabled at attach stage

  r354304:
  [cyapa] Postpone start of the polling thread until sleep is available

  r354305:
  [ig4] dump IG4_REG_COMP_PARAM1 and IG4_REG_COMP_VER registers unconditionally

  r354306:
  [ig4] Set clock registers based on controller model

  r354307:
  [ig4] Implement burst mode for data reads

  r354308:
  [ig4] Add suspend/resume support

  PR:   238037

  r354309:
  [ig4] Remove dead code inherited from DragonflyBSD

  r354310:
  [ig4] Rewrite ig4iic_write routine to use TX_EMPTY status flag

  r354311:
  [ig4] Convert last remaining usage of TX_NOTFULL status to TX_EMPTY

  r354312:
  [ig4] Use interrupts for waiting for empty TX FIFO

  r354313:
  [ig4] Convert polling loop from status-based to interrupt-based

  r354314:
  [ig4] Improve error detection

  r354315:
  [ig4] Set STOP condition and flush TX/RX FIFOs on error

  r354316:
  [ig4] On SkyLake controllers issue reset on attach unconditionally.

  r354317:
  [ig4] wait for bus stop condition after stop command issued

  r354318:
  [ig4] Minor improvement of write pipelining

  r354319:
  [ig4] Add generic resource methods to bus interface

  r354320:
  [ig4] Add support for CannonLake controllers

  PR:   240485
  Submitted by: Neel Chauhan 

  r354321:
  [ig4] Enable additional registers support on Appolo Lake controllers

  r354322:
  [ig4] Convert ithread interrupt handler to filter based one.

  r354327:
  [ig4] Try to workaround MIPS namespace pollution issue

  r355596:
  [ig4] Remove unused methods from bus interface

  Suggested by: jhb

  Reviewed by:  imp (previous version)
  Differential Revision:https://reviews.freebsd.org/D22016

Changes:
_U  stable/12/
  stable/12/sys/dev/chromebook_platform/chromebook_platform.c
  stable/12/sys/dev/cyapa/cyapa.c
  stable/12/sys/dev/ichiic/ig4_acpi.c
  stable/12/sys/dev/ichiic/ig4_iic.c
  stable/12/sys/dev/ichiic/ig4_pci.c
  stable/12/sys/dev/ichiic/ig4_reg.h
  stable/12/sys/dev/ichiic/ig4_var.h
  stable/12/sys/dev/iicbus/iicbus.c

-- 
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 240485] ig4: Add Cannon Lake LP and H I2C Controller IDs

2019-12-21 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=240485

Vladimir Kondratyev  changed:

   What|Removed |Added

 Resolution|--- |FIXED
 Status|Open|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 240485] ig4: Add Cannon Lake LP and H I2C Controller IDs

2019-12-21 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=240485

--- Comment #19 from Vladimir Kondratyev  ---
Committed, 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 242225] "fstyp -l" does not report exfat filesystem volume label

2019-12-21 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=242225

--- Comment #13 from commit-h...@freebsd.org ---
A commit references this bug:

Author: cem
Date: Sun Dec 22 03:19:18 UTC 2019
New revision: 355996
URL: https://svnweb.freebsd.org/changeset/base/355996

Log:
  fstyp(8): Show exFAT volume labels with -l flag

  exfat is fundamentally the same design as fat32.  The superblock differs
  marginally, and there are some additional optional features irrelevant to
  fstype(8); the structure of dirents has changed slightly to enable, among
  other things, larger files; the directory entries are no longer DOS 8.3
  ASCII or local 8-bit encoding, but instead explicitly UCS-2-LE.

  (As a result, this change uses iconv to convert a found exfat volume label
  to the user's locale.)

  Locating the volume label is identical to FAT32: locate the root directory
  and walk through dirents until you find a volume label.  Like FAT32, follow
  the FAT chain between root directory clusters as necessary.

  PR:   242225
  Reported by:  Victor Sudakov 

Changes:
  head/usr.sbin/fstyp/exfat.c
  head/usr.sbin/fstyp/fstyp.c
  head/usr.sbin/fstyp/fstyp.h
  head/usr.sbin/fstyp/tests/fstyp_test.sh

-- 
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 242225] "fstyp -l" does not report exfat filesystem volume label

2019-12-21 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=242225

Conrad Meyer  changed:

   What|Removed |Added

 Resolution|--- |FIXED
 Status|New |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 242243] autofs: the special_media map cannot output extfat filesystems labels

2019-12-21 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=242243

--- Comment #2 from Conrad Meyer  ---
Maybe obviated by r355996 (resolving pr 242225).

-- 
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 242243] autofs: the special_media map cannot output extfat filesystems labels

2019-12-21 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=242243

--- Comment #3 from Conrad Meyer  ---
(In reply to Conrad Meyer from comment #2)
(Only in 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 236233] [Meltdown mitigations under Xen, emulated TLB] Python multiprocessing is 4x slower with 11.2 compared to 11.0 kernel

2019-12-21 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=236233

Conrad Meyer  changed:

   What|Removed |Added

Summary|Python multiprocessing is   |[Meltdown mitigations under
   |4x slower with 11.2 |Xen, emulated TLB] Python
   |compared to 11.0 kernel |multiprocessing is 4x
   ||slower with 11.2 compared
   ||to 11.0 kernel

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