[Bug 225208] buildworld fails on my AMD64

[bugzilla-noreply]

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

Conrad Meyer  changed:

   What|Removed |Added

 CC||c...@freebsd.org

--- Comment #1 from Conrad Meyer  ---
This file hasn't been significantly changed in >10 years.  What is the error
message you are seeing from the build?

-- 
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 225208] buildworld fails on my AMD64

[bugzilla-noreply]

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

Bug ID: 225208
   Summary: buildworld fails on my AMD64
   Product: Base System
   Version: CURRENT
  Hardware: amd64
OS: Any
Status: New
  Severity: Affects Some People
  Priority: ---
 Component: kern
  Assignee: freebsd-bugs@FreeBSD.org
  Reporter: ndelm...@gmail.com

Created attachment 189784
  --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=189784=edit
the file that stops the compile. Would add the shell file, but can't

My attempt to build world with Current has failed twice when compiling the
AMD64 component b_tgamma.c

I don't a backtrace but I have attached the two files the error message
requested.

The Error code for this problem is 254.

I will try again tomorrow after updating my sources.

-- 
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 224601] autofs: Make automount(8) call chdir("/") before create_directory()

[bugzilla-noreply]

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

Pedro F. Giffuni  changed:

   What|Removed |Added

   Assignee|freebsd-bugs@FreeBSD.org|freebsd...@freebsd.org
 CC||tr...@freebsd.org

--- Comment #1 from Pedro F. Giffuni  ---
Assign it to -fs list.

-- 
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 225200] "zfs promote" of a zvol doesn't rename device nodes for snapshots

[bugzilla-noreply]

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

Bug ID: 225200
   Summary: "zfs promote" of a zvol doesn't rename device nodes
for snapshots
   Product: Base System
   Version: CURRENT
  Hardware: Any
OS: Any
Status: New
  Severity: Affects Some People
  Priority: ---
 Component: kern
  Assignee: freebsd-bugs@FreeBSD.org
  Reporter: asom...@freebsd.org

A "zfs promote" operation renames the snapshot that was the basis for the
cloned dataset.  If that dataset is a zvol, then the snapshot has an associated
device node.  That device node should be renamed by "zfs promote", but it
doesn't.

Steps to reproduce:
[alans@tom ~]$ sudo zpool create -f foo da1
[alans@tom ~]$ sudo zfs create -V 100m foo/vol0
[alans@tom ~]$ sudo zfs snapshot foo/vol0@snap
[alans@tom ~]$ sudo zfs clone foo/vol0@snap foo/vol1
[alans@tom ~]$ ls -l /dev/zvol/foo/
total 0
crw-r-  1 root  operator   0x85 Jan 15 17:24 vol0
crw-r-  1 root  operator  0x130 Jan 15 17:24 vol0@snap
crw-r-  1 root  operator  0x131 Jan 15 17:24 vol1
[alans@tom ~]$ sudo zfs promote foo/vol1
[alans@tom ~]$ ls -l /dev/zvol/foo/
total 0
crw-r-  1 root  operator   0x85 Jan 15 17:24 vol0
crw-r-  1 root  operator  0x130 Jan 15 17:24 vol0@snap
crw-r-  1 root  operator  0x131 Jan 15 17:24 vol1

The "vol0@snap" node should've been renamed to "vol1@snap".  After a reboot, it
does get the correct name.

-- 
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 225197] `make buildkernel' fails on a machine with 1GB RAM

[bugzilla-noreply]

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

--- Comment #5 from Mark Millard  ---
(In reply to Wolfram Schneider from comment #3)

Possibly of interest is some recent Out Of Memory
handling related work, see:

https://reviews.freebsd.org/D13671

and its associated check-ins.

-- 
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 225197] `make buildkernel' fails on a machine with 1GB RAM

[bugzilla-noreply]

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

Mark Millard  changed:

   What|Removed |Added

 CC||mar...@dsl-only.net

--- Comment #4 from Mark Millard  ---
(In reply to Wolfram Schneider from comment #3)

Also, as I understand it, with only 1 GiByte of
RAM assigned FreeBSD will self limit the swap space,
reporting somethings like (not necessarily with
matching figures):

warning: total configured swap (524288 pages) exceeds maximum recommended
amount (405460 pages).

[Note the above is from a RPi2B V1.1 with 1 GiByte
of RAM (armv7). An RPi3B (aarch64) allows far more
but still limits it.]

It will also say something like:

warning: increase kern.maxswzone or reduce amount of swap.

but looking at the code that "increase kern.maxswzone" only
applies if one has already set kern.maxswzone to a figure
that limited the amount of swap. The default value of
zero makes kern.maxswzone be otherwise ignored. (But
i386 seemed to have a non-zero default, if I remember
correctly.)

Quoting "man 8 loader" :

kern.maxswzone
  . . .

  Note that swap metadata can be fragmented, which means that
  the system can run out of space before it reaches the
  theoretical limit.  Therefore, care should be taken to not
  configure more swap than approximately half of the
  theoretical maximum.

 . . .

It turns out that the "maximum recommended amount" earlier is that
"half". But the theoretical maximum is not always the "8 times the
amount of physical memory" that man page indicates (or anywhere
near even 6 times). (The RPi2B V1.1 is an example of 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 225197] `make buildkernel' fails on a machine with 1GB RAM

[bugzilla-noreply]

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

--- Comment #3 from Wolfram Schneider  ---
The VM has only one CPU. I do not use make -j, it does not make sense on a
single CPU machine.

How much swap space should I add? 10GB, 20GB?

I do not want to tune the kernel, the default kernel should just compile
(GENERIC or GENERIC-NODEBUG).

-- 
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 225197] `make buildkernel' fails on a machine with 1GB RAM

[bugzilla-noreply]

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

Dimitry Andric  changed:

   What|Removed |Added

 CC|d...@freebsd.org |

--- Comment #2 from Dimitry Andric  ---
Maybe try lowering the -j level?  Add more swap?  Trim your kernel
configuration file so it uses less devices?  Turn off debug information?  Etc,
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 225197] `make buildkernel' fails on a machine with 1GB RAM

[bugzilla-noreply]

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

--- Comment #1 from Wolfram Schneider  ---
The last output of make buildkernel is:

ctfconvert -L VERSION -g vers.o
linking kernel.full
ctfmerge -L VERSION -g -o kernel.full ...

I see in top(1) that ctfmerge is huge, 250MB rss. Then the terminal freeze. I
cannot provide more information, because the kernel kills all monitoring tools
(ssh, screen, top, munin-node 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 225197] `make buildkernel' fails on a machine with 1GB RAM

[bugzilla-noreply]

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

Bug ID: 225197
   Summary: `make buildkernel' fails on a machine with 1GB RAM
   Product: Base System
   Version: CURRENT
  Hardware: Any
OS: Any
Status: New
  Severity: Affects Only Me
  Priority: ---
 Component: kern
  Assignee: freebsd-bugs@FreeBSD.org
  Reporter: wo...@freebsd.org

I have a VM with 1GB RAM and 3GB swap. I could compile the -current kernel
without problems in the last months.

Now the builds fails with "out of swap space" . A change in the last 10 days
broke the build of the kernel. Sad. 

I do not remember that we make the decision to require to have more than 1GB
RAM to build a kernel. Please fix this. 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 223325] usr.sbin/service: Add support for interacting with services in jails.

[bugzilla-noreply]

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

Kyle Evans  changed:

   What|Removed |Added

   Assignee|freebsd-bugs@FreeBSD.org|kev...@freebsd.org
 CC||kev...@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 211485] fsck_ffs(8) doesn't exit with error code (but 0) on error (without -[pCF])

[bugzilla-noreply]

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

David Bright  changed:

   What|Removed |Added

 CC||d...@freebsd.org
   Assignee|freebsd-bugs@FreeBSD.org|d...@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 217149] seq(1) inconsistently omits 'last' when using float increment

[bugzilla-noreply]

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

Yuri Pankov  changed:

   What|Removed |Added

 Attachment #189755|0   |1
is obsolete||

--- Comment #2 from Yuri Pankov  ---
Created attachment 189760
  --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=189760=edit
Don't accumulate rounding errors

-- 
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 224556] pw(8) does not check semantics of name

[bugzilla-noreply]

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

Eugene Grosbein  changed:

   What|Removed |Added

 Status|In Progress |Open
   Assignee|freebsd-bugs@FreeBSD.org|eu...@freebsd.org
 CC||eu...@freebsd.org

--- Comment #4 from Eugene Grosbein  ---
In fact, pw(8) already has needed checks and does not harm.

First, "/path/to/dir/." is completely correct directory name and the same as
"/path/to/dir" itself and "pw userdel username -r" removes it if its owner is
user being removed only.

Second, "/path/to/dir/.." may look funny but it is correct directory name too
and the same as "/path/to" and "pw userdel username -r" removes it if its owner
is user being removed only.

What is the problem is exactly? If you believe that pw(8) does "rm -rf" for
file system objects not checking their ownership, you are wrong.

-- 
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 225182] devel/powerpc64-xtoolchain-gcc: SLOF Data Storage Exception on boot with kernel built with devel/powerpc64-xtoolchain-gcc

[bugzilla-noreply]

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

--- Comment #1 from Conrad Meyer  ---
(In reply to Kenneth Salerno from comment #0)
> +++ This bug was initially created as a clone of Bug #225181 +++

Duplicate?  Seems like there's only one issue here, but two bugs.

-- 
You are receiving this mail because:
You are on the CC list 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 225181] SLOF Data Storage Exception on boot with kernel built with devel/powerpc64-xtoolchain-gcc

[bugzilla-noreply]

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

Conrad Meyer  changed:

   What|Removed |Added

   Assignee|freebsd-bugs@FreeBSD.org|freebsd-...@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 225175] Kernel panic - i915_gem* functions problem?

[bugzilla-noreply]

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

Conrad Meyer  changed:

   What|Removed |Added

   Assignee|freebsd-bugs@FreeBSD.org|freebsd-...@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 225179] Issues with axge driver

[bugzilla-noreply]

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

Conrad Meyer  changed:

   What|Removed |Added

   Assignee|freebsd-bugs@FreeBSD.org|freebsd-...@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 217149] seq(1) inconsistently omits 'last' when using float increment

[bugzilla-noreply]

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

Yuri Pankov  changed:

   What|Removed |Added

 CC||yur...@icloud.com

--- Comment #1 from Yuri Pankov  ---
Created attachment 189755
  --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=189755=edit
Don't accumulate rounding errors

As I was educated on current@, many exact fractions in base-10 aren't exact in
base-2, so using the for() loop accumulates rounding errors.  Work around that
re-computing current value for every step.

-- 
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 225183] Cam Target ISP Qlogic Bios not seen through fibre channel switch

[bugzilla-noreply]

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

Bug ID: 225183
   Summary: Cam Target ISP Qlogic Bios not seen through fibre
channel switch
   Product: Base System
   Version: 11.1-RELEASE
  Hardware: amd64
OS: Any
Status: New
  Severity: Affects Only Me
  Priority: ---
 Component: kern
  Assignee: freebsd-bugs@FreeBSD.org
  Reporter: endura...@eot.com

My first bug report.
I'm having a problem with my Cam targets not showing up when using a fibre
switch.
If I hook CTL to client, everything shows up fine under the Qlogic bios, When
using a switch, I can scan for devices, but it times out after not finding
anything. If i boot a freebsd disk, I can see the targets just fine. It's just
the bios (so no booting) that is the problem.
Both host and client are using Qlogic fibre cards (4gbs ISP2432 PCIE), and a
Brocade silkworm 4600 switch. Here is some data:
kernel errors from ISP while scanning for devices
Jan 14 23:36:11 Fibre kernel: ctlfeasync: WWPN 0x2124ff4645e6 port 0x031100
path 2 target 0 arrived
Jan 14 23:41:35 Fibre kernel: isp2: CTIO returned by f/w- Port Logout
Jan 14 23:41:35 Fibre kernel: isp2: isp_handle_platform_ctio: CTIO7[125958] seq
0 nc 1 sts 0x29 flg 0x8040 sns 0 resid 0 FIN
Jan 14 23:41:35 Fibre kernel: isp2: CTIO returned by f/w- Port Logout
Jan 14 23:42:05 Fibre kernel: isp2: CTIO returned by f/w- Port Logout
Jan 14 23:42:05 Fibre kernel: isp2: isp_handle_platform_ctio: CTIO7[125984] seq
0 nc 1 sts 0x29 flg 0x8040 sns 0 resid 0 FIN
Jan 14 23:42:05 Fibre kernel: isp2: CTIO returned by f/w- Port Logout
Jan 14 23:42:36 Fibre kernel: isp2: CTIO returned by f/w- Port Logout
Jan 14 23:42:36 Fibre kernel: isp2: isp_handle_platform_ctio: CTIO7[1259b0] seq
0 nc 1 sts 0x29 flg 0x8040 sns 0 resid 0 FIN
Jan 14 23:42:36 Fibre kernel: isp2: CTIO returned by f/w- Port Logout
Jan 14 23:42:36 Fibre kernel: ctlfeasync: WWPN 0x2124ff4645e6 port 0x031100
path 2 target 0 left
Jan 14 23:43:15 Fibre kernel: isp2: Chan 0 WWPN 0x2124ff4645e6 PortID
0x031100 handle 0x1 cannot be found to be deleted
Jan 14 23:43:49 Fibre kernel: ctlfeasync: WWPN 0x2124ff4645e6 port 0x031100
path 2 target 0 arrived
Jan 14 23:43:49 Fibre kernel: isp2: CTIO returned by f/w- Port Logout
Jan 14 23:43:49 Fibre kernel: isp2: isp_handle_platform_ctio: CTIO7[1259dc] seq
0 nc 1 sts 0x29 flg 0x8040 sns 0 resid 0 FIN
Jan 14 23:43:49 Fibre kernel: isp2: CTIO returned by f/w- Port Logout
Jan 14 23:44:00 Fibre /usr/sbin/cron[45153]: (operator) CMD
(/usr/libexec/save-entropy)
Jan 14 23:44:20 Fibre kernel: isp2: CTIO returned by f/w- Port Logout
Jan 14 23:44:20 Fibre kernel: isp2: isp_handle_platform_ctio: CTIO7[125a08] seq
0 nc 1 sts 0x29 flg 0x8040 sns 0 resid 0 FIN
Jan 14 23:44:20 Fibre kernel: isp2: CTIO returned by f/w- Port Logout
Jan 14 23:44:20 Fibre kernel: ctlfeasync: WWPN 0x2124ff4645e6 port 0x031100
path 2 target 0 left

root@Fibre:/export # uname -a
FreeBSD Fibre 11.1-RELEASE-p5 FreeBSD 11.1-RELEASE-p5 #5: Sat Dec  2 21:27:37
CST 2017 chris@Fibre:/usr/obj/usr/src/sys/FCKERNEL  amd64

I have found a fix to the problem submitted by MAV, but i was wondering about
getting it MFC'ed into 11.1 release
https://svnweb.freebsd.org/base?view=revision=320604

Thanks for the Help,
Chris

-- 
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 225181] SLOF Data Storage Exception on boot with kernel built with devel/powerpc64-xtoolchain-gcc

[bugzilla-noreply]

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

--- Comment #1 from Kenneth Salerno  ---
Also want to add I am running an older version of SLOF (packaged with QEMU
2.4.1) because the latest SLOF packaged with QEMU 2.10.2 fails to read
superblock of boot disk (MBR/dos label) and cannot even bootstrap FreeBSD, so I
have no way of knowing if this was fixed in a more current SLOF or not. But
again, I need assistance to first determine if this is a compiler issue or SLOF
issue.

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"

[Bug 224552] 'od -c' show wrong char when it is a non-printable

[bugzilla-noreply]

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

Yuri Pankov  changed:

   What|Removed |Added

 Attachment #189747|0   |1
is obsolete||

--- Comment #3 from Yuri Pankov  ---
Created attachment 189748
  --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=189748=edit
Restore the original character if we peeked ahead, but still can't complete

-- 
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 225179] Issues with axge driver

[bugzilla-noreply]

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

Alessandro Sagratini  changed:

   What|Removed |Added

   Severity|Affects Only Me |Affects Some People

-- 
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 224552] 'od -c' show wrong char when it is a non-printable

[bugzilla-noreply]

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

--- Comment #2 from Yuri Pankov  ---
The problem here is that we forget to restore the original character to print
when we encounter what we think is incomplete multibyte sequence at the end of
the line buffer or at EOF -- we peek ahead trying to complete the character,
but if the conversion still fails, we have the character pointer set to the
look-ahead buffer, not what it was originally.

-- 
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 224552] 'od -c' show wrong char when it is a non-printable

[bugzilla-noreply]

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

Yuri Pankov  changed:

   What|Removed |Added

 CC||yur...@icloud.com

--- Comment #1 from Yuri Pankov  ---
Created attachment 189747
  --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=189747=edit
Restore the original character if we peeked ahead, but still can't complete

-- 
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 225179] Issues with axge driver

[bugzilla-noreply]

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

Bug ID: 225179
   Summary: Issues with axge driver
   Product: Base System
   Version: 11.1-RELEASE
  Hardware: Any
OS: Any
Status: New
  Severity: Affects Only Me
  Priority: ---
 Component: kern
  Assignee: freebsd-bugs@FreeBSD.org
  Reporter: ale_sa...@hotmail.com

Created attachment 189744
  --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=189744=edit
axge info

Hello,
I'm experiencing performance issues with a USB 3.0 adapter using ASIX 88179
chipset [1], that should be supported by "axge" driver [2]

Basically, speed is not above ~530Mb/s, even though the device is correctly
recognized as Usb 3.0 if running an iperf3 client test, while it's ~180Mb if
running a iperf3 server on the machine and trying to connect from a Linux
client.

If trying to use Debian 9 on the same machine, I'm not experiencing any issue,
like described in this forum thread [3]. 

You can find more details attached to this post.

[1] http://www.asix.com.tw/products.php?op=pItemdetail=131;71;112
[2] https://www.freebsd.org/cgi/man.cgi?query=axge=4
[3] https://forums.freebsd.org/threads/62016/#post-357782

Please let me know if there's any further info I should provide.

Thank you.
Regards,
Alessandro

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