[Bug 204378] xhci fails on Cavium ThunderX
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=204378 Hans Petter Selaskychanged: What|Removed |Added Status|New |Open --- Comment #1 from Hans Petter Selasky --- Hi, This looks like a problem in the PCI subsystem for ARM? Or the "rid" is not correct for MSI? Referring to sys/dev/usb/controller/xhci_pci.c. Can you boot with bootverbose on? --HPS -- 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 204417] [autofs] automountd truncates some labels
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=204417 Bug ID: 204417 Summary: [autofs] automountd truncates some labels Product: Base System Version: 11.0-CURRENT Hardware: Any OS: Any Status: New Keywords: needs-qa Severity: Affects Only Me Priority: --- Component: conf Assignee: freebsd-bugs@FreeBSD.org Reporter: jbe...@freebsd.org $ uname -a FreeBSD bar 11.0-CURRENT FreeBSD 11.0-CURRENT #0 r290495M: Sat Nov 7 14:57:28 UTC 2015 foo@bar:/usr/obj/usr/src/sys/NONGENERIC amd64 1. Download http://releases.ubuntu.com/14.04.3/ubuntu-14.04.3-desktop-amd64.iso 2. Either flash it on a USB drive or emulate with something like DriveDroid 3. Uncomment -media in /etc/auto_master 4. automount; automountd; or use service(8) $ ls /media ls: Ubuntu 14.04.3 LTS amd6: No such file or directory da0s2 $ /etc/autofs/special_media da0s2 Ubuntu 14.04.3 LTS amd64 $ /etc/autofs/special_media | vis -w da0s2\012Ubuntu\04014.04.3\040LTS\040amd64\012 $ /etc/autofs/special_media 'Ubuntu 14.04.3 LTS amd6' $ /etc/autofs/special_media 'Ubuntu 14.04.3 LTS amd64' -fstype=cd9660,nosuid :/dev/da0 $ automountd -d automountd: waiting for request from the kernel automountd: not forking due to -d flag; will exit after servicing a single request automountd: got request 14: from map -media, path /media/, prefix "/media", key "Ubuntu 14.04.3 LTS amd6", options "nosuid" automountd: parsing map "-media" automountd: executing "/etc/autofs/special_media Ubuntu 14.04.3 LTS amd6" as pid 5493 automountd: "/etc/autofs/special_media Ubuntu 14.04.3 LTS amd6", pid 5493, terminated gracefully automountd: map may contain wildcard entries automountd: found node defined at [kernel request]:0; not a mountpoint automountd: creating subtree at /media automountd: nothing to mount; exiting automountd: completing request 14 with error 0 Can you reproduce? If not I'll try to debug my environment more. -- 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 204378] xhci fails on Cavium ThunderX
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=204378 Mark Linimonchanged: What|Removed |Added Component|kern|usb 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 204378] xhci fails on Cavium ThunderX
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=204378 --- Comment #5 from Ed Maste--- The failing case is (pci_do_msi is 1): /* MSI capability present? */ if (cfg->msi.msi_location == 0 || !pci_do_msi) -- 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 204378] xhci fails on Cavium ThunderX
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=204378 --- Comment #2 from Ed Maste--- A full boot -v log is at https://people.freebsd.org/~emaste/arm64/thunderx-verbose-boot-xhci.log -- 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 204378] xhci fails on Cavium ThunderX
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=204378 --- Comment #3 from Hans Petter Selasky--- Hi, I see the MSIX is working with the AHCI. in xhci_pci.c, can you try to change: (rid != 0 ? 0 : RF_SHAREABLE) Into simply: RF_SHAREABLE ? -- 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 204378] xhci fails on Cavium ThunderX
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=204378 --- Comment #8 from Hans Petter Selasky--- Or set: hw.usb.xhci.msi=0 before booting the kernel. --HPS -- 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 204378] xhci fails on Cavium ThunderX
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=204378 --- Comment #7 from Hans Petter Selasky--- If you in the XHCI pci attach routine set: uint8_t usemsi = 0; /* was: 1 */ --HPS -- 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 204378] xhci fails on Cavium ThunderX
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=204378 --- Comment #6 from Ed Maste--- That is, we have only MSI support in xhci, not MSI-X Capabilities from my x86 desktop xhci: cap 01[70] = powerspec 2 supports D0 D3 current D0 cap 05[80] = MSI supports 8 messages, 64 bit enabled with 1 message Capabilities from the ThunderX: cap 10[70] = PCI-Express 2 endpoint max data 128(128) link x0(x0) cap 11[b0] = MSI-X supports 4 messages Table in map 0x20[0x0], PBA in map 0x20[0xf] ecap 000e[100] = ARI 1 ecap 000b[108] = Vendor 1 ID 160 -- 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 182170] strtofflags.c build failures
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=182170 NGie Cooperchanged: What|Removed |Added Status|In Progress |Open CC||bdrew...@freebsd.org --- Comment #2 from NGie Cooper --- bdrewery: have you tried without the WITHOUT_CROSS_COMPILER option yet? -- 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 204414] ThunderX vnic driver missing man page
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=204414 --- Comment #1 from Ed Maste--- There are four components involved: bgx, ThunderX mdio, nicpf, nicvf I am not sure if these should all be documented in the same man page, or if we need some separate pages -- 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 204417] [autofs] automountd truncates some labels
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=204417 --- Comment #1 from Jan Beich--- Err, (2) step can also be done with mdconfig -f /path/to/ubuntu-14.04.3-desktop-amd64.iso -- 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 204417] [autofs] automountd truncates labels > 23 characters long
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=204417 Jan Beichchanged: What|Removed |Added Component|conf|kern Summary|[autofs] automountd |[autofs] automountd |truncates some labels |truncates labels > 23 ||characters long CC||tr...@freebsd.org --- Comment #2 from Jan Beich --- Better, (1) and (2) can be replaced with $ makefs -o label=$(jot -c - a z | rs -g) foo.img /rescue $ mdconfig -f foo.img which still leads to an error $ ls /media ls: abcdefghijklmnopqrstuvw: No such file or directory Kernel 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 191868] /usr/games in configuration files under /etc, even if WITHOUT_GAMES is set in src.conf
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=191868 NGie Cooperchanged: What|Removed |Added Resolution|--- |FIXED Flags||mfc-stable8-, mfc-stable9-, ||mfc-stable10- Assignee|freebsd-bugs@FreeBSD.org|cperc...@freebsd.org Status|New |Closed --- Comment #1 from NGie Cooper --- This is no longer the case on head. That's good enough for me :). Closing! r278616 | cperciva | 2015-02-11 21:35:00 -0800 (Wed, 11 Feb 2015) | 25 lines Step 1 of eliminating the "games" distribution: Move binaries to /usr/bin; update paths; and include everything in the "base" distribution. The "games" distribution being optional made sense when there were more games and we had small disks; but the "games-like" games were moved into the ports tree a dozen years ago and the remaining "utility-like" games occupy less than 0.001% of my laptop's small hard drive. Meanwhile every new user is confronted by the question "do you want games installed" when they they try to install FreeBSD. The next steps will be: 2. Removing punch card (bcd, ppt), phase-of-moon (pom), clock (grdc), and caesar cipher (caesar, rot13) utilities. I intend to keep fortune, factor, morse, number, primes, and random, since there is evidence that those are still being used. 3. Merging src/games into src/usr.bin. This change will not be MFCed. Reviewed by:jmg Discussed at: EuroBSDCon Approved by:gjb (release-affecting changes) -- 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 176748] [libi386] [patch] BTX Loader i386 incorrectly probes EDD, possibly resulting division by zero
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=176748 --- Comment #3 from Arrigo Marchiori--- Hello, after some investigation, I could confirm that yes, the BIOS is broken. However, the vendor of the embedded PC's I am using, is still applying the old and broken BIOS to recent units. I only upgraded the FreeBSD sources last week, and the patch seems not to be effective any more, when booting from (recent) USB pen drives. For some weird reasons, the sector size of such USB sticks is returned as 12022 bytes or something like that, that is not correct. Would it be advisable to add some more safety checks, such as: - sectors must be non-zero; - sector_size must be non-zero; - sector_size must be a multiple of 512? Such a check enables my terminals to boot again. -- 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 176748] [libi386] [patch] BTX Loader i386 incorrectly probes EDD, possibly resulting division by zero
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=176748 Arrigo Marchiorichanged: What|Removed |Added Attachment #132465|0 |1 is obsolete|| --- Comment #4 from Arrigo Marchiori --- Created attachment 162919 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=162919=edit Add consistency checks to EDD information The EDD information is only used, if the sector count and sector size respect very simple requisites. -- 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 163775] [patch] sfxge(4) explicitly sets -g -DDEBUG=1
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=163775 NGie Cooperchanged: What|Removed |Added Assignee|freebsd-bugs@FreeBSD.org|arybc...@freebsd.org Flags||mfc-stable8-, mfc-stable9?, ||mfc-stable10+ --- Comment #6 from NGie Cooper --- No longer an issue on head after r283679 or stable/10 after r284556. Giving to Andrew to decide if he wants to MFC the change(s) back to stable/9. -- 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 204412] fortune limericks should have '-o' suffix
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=204412 Bug ID: 204412 Summary: fortune limericks should have '-o' suffix Product: Base System Version: 10.2-STABLE Hardware: Any OS: Any Status: New Severity: Affects Some People Priority: --- Component: misc Assignee: freebsd-bugs@FreeBSD.org Reporter: parakl...@darkreality.org The limericks files associated with the fortune program do not have the '-o' suffix despite being much more offensive that the fortunes that are currently flagged as offensive. This isn't a problem if you call `fortune` with no arguments, as it only uses the primary file in that case, but if you call `fortune all` without the `-o` or `-a` switch it will display the limericks which are quite crude and offensive. There are for example at least 57 occurrences of the word 'cunt' in `limerick` and 3 more in `gerrold.limerick`. There are 88/1 occurrences of the work 'fuck' respectively. When you add the words pussy, dick, prick, screw, ass, whang, sodomy, cock, and semen then there are at least 172/14 additional occurrences respectively. By comparison, the offensive fortunes in 'murphy-o' include things as innocuous as "Never sleep with anyone crazier than yourself". -- 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 204409] Uploading to a FreeBSD sshd server drops bandwidth
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=204409 Bug ID: 204409 Summary: Uploading to a FreeBSD sshd server drops bandwidth Product: Base System Version: 10.2-RELEASE Hardware: Any OS: Any Status: New Severity: Affects Only Me Priority: --- Component: bin Assignee: freebsd-bugs@FreeBSD.org Reporter: vlad-f...@acheronmedia.com It appears that UPLOADING to sshd (eg. scp localfile remote.tld:remotefile) will happen at very limited bandwidth. I haven't been able to isolate which circumstances those are precisely, but, between two servers when the command is reversed (eg. scp remote.tld:remotefile ./localfile) the transfer happens at full available speed. To make this clear, for a particular set of servers, for example: on server A: scp localfile B:remotefile -> 40Mbps (upload to sshd) scp B:remotefile localfile -> 120Mbps (download from sshd) scp localfile B:remotefile -> 200Mbps (upload to sshd, Debian on B) scp B:remotefile localfile -> 120Mbps (download from sshd, Debian on B) on server B: scp localfile A:remotefile -> 30Mbps (upload to sshd) scp A:remotefile localfile -> 120Mbps (download from sshd) scp localfile A:remotefile -> 40Mbps (upload to sshd, Debian on B) scp B:remotefile localfile -> 200Mbps (download from sshd, Debian on B) NOTE: When upload is _TO_ FreeBSD sshd, the bandwidth is 30-40Mbps. Which means the differences between upload and download are not due to network congestion or particular datacenter setup, whether a server is dedicated or VPS, UFS2 filesystem or ZFS, 1GB of RAM or 16GB. Though all were 64bit. Tested between Leaseweb Amsterdam, DigitalOcean Amsterdam, DigitalOcean Frankfurt, Hetzner Germany (Falkenstein) and Rackspace in London. This also affects rsync over ssh, so it's not just scp. The only thing that changes are absolute bandwidth numbers for a given set of servers. Testing other protocols (http, https, netcat, ...) shows full network speed available between testing servers. Different IPQoS or Cipher settings do not improve anything. -- 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 204409] Uploading to a FreeBSD sshd server drops bandwidth
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=204409 --- Comment #1 from Vlad K.--- (In reply to Vlad K. from comment #0) Errata, that last scp should be: scp A:remotefile localfile ... -- 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 154562] make(1): corrupted stack access when provided invalid identifiers
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=154562 NGie Cooperchanged: What|Removed |Added Resolution|--- |Overcome By Events Status|In Progress |Closed --- Comment #3 from NGie Cooper --- Can't repro this with bmake. Closing. -- 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 196867] expr on FreeBSD doesn't bounds check certain values dealing with overflow very well
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=196867 NGie Cooperchanged: What|Removed |Added Status|In Progress |Closed Flags||mfc-stable8-, mfc-stable9-, ||mfc-stable10+ 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 204414] ThunerX vnic driver missing man page
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=204414 Bug ID: 204414 Summary: ThunerX vnic driver missing man page Product: Base System Version: 11.0-CURRENT Hardware: arm64 OS: Any Status: New Severity: Affects Only Me Priority: --- Component: misc Assignee: freebsd-bugs@FreeBSD.org Reporter: ema...@freebsd.org Manual page needed for the new device driver root@arm64-demo:~ # man bgx No manual entry for bgx root@arm64-demo:~ # man vnic No manual entry for vnic -- 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 204414] ThunderX vnic driver missing man page
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=204414 Mark Linimonchanged: What|Removed |Added Summary|ThunerX vnic driver missing |ThunderX vnic driver |man page|missing man page -- 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 204412] fortune limericks should have '-o' suffix
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=204412 Mark Linimonchanged: What|Removed |Added Component|misc|bin -- 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 204415] vnic/bgx driver does not build as a module
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=204415 Bug ID: 204415 Summary: vnic/bgx driver does not build as a module Product: Base System Version: 11.0-CURRENT Hardware: arm64 OS: Any Status: New Severity: Affects Only Me Priority: --- Component: kern Assignee: freebsd-bugs@FreeBSD.org Reporter: ema...@freebsd.org The vnic/bgx driver is currently only available by adding #device vnic to the kernel configuration. It needs to be made available as a module as well. sys/conf/files.arm64: dev/vnic/nic_main.c optionalvnic pci dev/vnic/nicvf_main.c optionalvnic pci pci_iov dev/vnic/nicvf_queues.c optionalvnic pci pci_iov dev/vnic/thunder_bgx_fdt.c optionalvnic fdt dev/vnic/thunder_bgx.c optionalvnic pci dev/vnic/thunder_mdio_fdt.c optionalvnic fdt dev/vnic/thunder_mdio.c optionalvnic dev/vnic/lmac_if.m optionalvnic -- 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"