11.1-RELEASE: magic hosed, file recognition fails

[Peter]

Just found that my scripts that would detect image types by means of the 
"file" command do not work anymore in RELEASE-11. :(


Whats happening in R11.1 is this:

$ scanimage > /tmp/SCAN
$ file /tmp/SCAN
/tmp/SCAN: data

While on R10 in looked this way, which appears slightly more useful:

$ scanimage > /tmp/SCAN
$ file /tmp/SCAN
/tmp/SCAN: Netpbm image data, size = 2480 x 3507, rawbits, greymap


Further investigation shows, the problem may have appeared with this update:

>r309847 | delphij | 2016-12-11 08:33:02 +0100 (Sun, 11 Dec 2016) | 2 lines
>
>MFC r308420: MFV r308392: file 5.29.


And that is a contrib, it seems the original comes from fishy penguins. 
So no proper repo, and doubtful if anybody might be in charge,

but instead some colorful pictures like this one:
https://fossies.org/diffs/file/5.28_vs_5.29/magic/Magdir/images-diff.html
---

Looking closer - this is my file header:

pmc@disp:604:1/tmp$ hd SCAN  |more
  50 35 0a 23 20 53 41 4e  45 20 64 61 74 61 20 66  |P5.# SANE 
data f|
0010  6f 6c 6c 6f 77 73 0a 32  34 38 30 20 33 35 30 37  |ollows.2480 
3507|
0020  0a 32 35 35 0a 5f 58 56  4b 53 49 4b 52 54 50 51 
|.255._XVKSIKRTPQ|
0030  4e 4c 52 5b 56 55 4c 47  4e 4f 4e 4d 53 54 53 4d 
|NLR[VULGNONMSTSM|
0040  53 49 50 52 4c 51 4f 53  56 55 53 4d 55 4e 4e 4c 
|SIPRLQOSVUSMUNNL|
0050  55 49 4d 50 52 4c 4e 50  4d 56 4e 51 52 4e 4e 50 
|UIMPRLNPMVNQRNNP|



And this is the ruleset in the magic file:

# PBMPLUS images
# The next byte following the magic is always whitespace.
# strength is changed to try these patterns before "x86 boot sector"
0   namenetpbm
>3  regex/s =[0-9]{1,50}\ [0-9]{1,50}   Netpbm image data
>>&0regex   =[0-9]{1,50}\b, size = %s x
>>>&0   regex   =[0-9]{1,50}\b %s

0   string  P5
>0  regex/4 P5\\s
>>0 use netpbm
>>>0string  x   \b, rawbits, pixmap
!:strength + 45
!:mime  image/x-portable-pixmap


The failing line is the one with "regex/4" command, and I dont see why 
there is a *double* \ - but a single one doesnt work either. Using \n

instead, would work.  And what also works is this one:
>0  regex/4 P5[[:space:]]


To figure the root cause would mean to look into that libmagic, and 
maybe there is a misunderstanding between the design of that lib and the 
linux guys maintaining the magic file?


___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: [USB] hang after upgrade from 11.0 to 11.1, ZFS or callout() related?

[Michael Schmiedgen]

On 07.08.2017 19:21, Mark Martinec wrote:

But this is all for 11.0, on 11.1 it hangs and I cannot look it up:


Does it also hang if you choose 'Safe mode" in the loader dialog?


It hangs even with 'Safe mode' (multiuser):

https://imgur.com/a/fz3KB

Thanks,
  Michael

--
___

Michael Schmiedgen, BSc
Senior Software Engineer

Takwa GmbH
Friedrich-List-Str. 36
99096 Erfurt GERMANY

Tel  +49 361 6534096
Fax  +49 361 6534097
Mail schmied...@takwa.de
Web  http://www.takwa.de/
___


Amtsgericht Jena HRB 112964
Geschäftsführung: Ingo Buchholz
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: [USB] hang after upgrade from 11.0 to 11.1, ZFS or callout() related?

[Michael Schmiedgen]

On 07.08.2017 19:21, Mark Martinec wrote:

But this is all for 11.0, on 11.1 it hangs and I cannot look it up:


Does it also hang if you choose 'Safe mode" in the loader dialog?

   Mark


It hangs even with 'Safe mode' (multiuser):

https://imgur.com/a/fz3KB


I tried setting cam boot delay, as some people in web forums suggested:

kern.cam.boot_delay="1"

But then I get the 'ZFS error 5' with an 11.1 kernel.


Thanks,
  Michael

--
___

Michael Schmiedgen, BSc
Senior Software Engineer

Takwa GmbH
Friedrich-List-Str. 36
99096 Erfurt GERMANY

Tel  +49 361 6534096
Fax  +49 361 6534097
Mail schmied...@takwa.de
Web  http://www.takwa.de/
___


Amtsgericht Jena HRB 112964
Geschäftsführung: Ingo Buchholz
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: [USB] hang after upgrade from 11.0 to 11.1, ZFS or callout() related?

[Mark Martinec]

But this is all for 11.0, on 11.1 it hangs and I cannot look it up:


Does it also hang if you choose 'Safe mode" in the loader dialog?

  Mark
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

[Bug 221146] [LAGG] Problem with second laggport

[bugzilla-noreply]

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

--- Comment #14 from Cassiano Peixoto  ---
(In reply to Sean Bruno from comment #13)
Dear Sean,

I've just opened a PR 221317 regarding ixgbe driver update and netmap issue.

Thanks.

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

Re: [USB] hang after upgrade from 11.0 to 11.1, ZFS or callout() related?

[Michael Schmiedgen]

On 07.08.2017 19:09, Hans Petter Selasky wrote:


Can you get dmesg without the USB debug enabled?



But this is all for 11.0, on 11.1 it hangs and I cannot look it up:


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): resolution 640x480
CPU: Intel(R) Xeon(R) CPU E31245 @ 3.30GHz (3300.09-MHz K8-class CPU)
  Origin="GenuineIntel"  Id=0x206a7  Family=0x6  Model=0x2a  Stepping=7
  
Features=0xbfebfbff

Features2=0x1fbae3ff
  AMD Features=0x28100800
  AMD Features2=0x1
  XSAVE Features=0x1
  VT-x: PAT,HLT,MTF,PAUSE,EPT,UG,VPID
  TSC: P-state invariant, performance statistics
real memory  = 34359738368 (32768 MB)
avail memory = 33186914304 (31649 MB)
Event timer "LAPIC" quality 600
ACPI APIC Table: 
FreeBSD/SMP: Multiprocessor System Detected: 8 CPUs
FreeBSD/SMP: 1 package(s) x 4 core(s) x 2 hardware threads
random: unblocking device.
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
vtvga0:  on motherboard
cryptosoft0:  on motherboard
acpi0:  on motherboard
acpi0: Power Button (fixed)
cpu0:  on acpi0
cpu1:  on acpi0
cpu2:  on acpi0
cpu3:  on acpi0
cpu4:  on acpi0
cpu5:  on acpi0
cpu6:  on acpi0
cpu7:  on acpi0
hpet0:  iomem 0xfed0-0xfed003ff on acpi0
Timecounter "HPET" frequency 14318180 Hz quality 950
Event timer "HPET" frequency 14318180 Hz quality 550
atrtc0:  port 0x70-0x77 irq 8 on acpi0
atrtc0: Warning: Couldn't map I/O.
Event timer "RTC" frequency 32768 Hz quality 0
attimer0:  port 0x40-0x43,0x50-0x53 irq 0 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: <24-bit timer at 3.579545MHz> port 0x408-0x40b on acpi0
pcib0:  port 0xcf8-0xcff on acpi0
pcib0: _OSC returned error 0x4
pci0:  on pcib0
pcib1:  irq 16 at device 1.0 on pci0
pci1:  on pcib1
vgapci0:  port 0xf000-0xf03f mem 
0xf780-0xf7bf,0xe000-0xefff irq 16 at device 2.0 on pci0
vgapci0: Boot video device
pcib2:  irq 19 at device 6.0 on pci0
pci2:  on pcib2
pci0:  at device 22.0 (no driver attached)
ehci0:  mem 0xf7e04000-0xf7e043ff irq 16 at 
device 26.0 on pci0
usbus0: EHCI version 1.0
usbus0 on ehci0
pcib3:  irq 16 at device 28.0 on pci0
pcib3: [GIANT-LOCKED]
pcib4:  irq 17 at device 28.5 on pci0
pci3:  on pcib4
em0:  port 0xe000-0xe01f mem 
0xf7d0-0xf7d1,0xf7d2-0xf7d23fff irq 17 at device 0.0 on pci3
em0: Using MSIX interrupts with 3 vectors
em0: Ethernet address: 10:bf:48:d7:f1:29
em0: netmap queues/slots: TX 1/1024, RX 1/1024
pcib5:  irq 19 at device 28.7 on pci0
pci4:  on pcib5
xhci0:  mem 0xf7c0-0xf7c07fff irq 19 at 
device 0.0 on pci4
xhci0: 32 bytes context size, 32-bit DMA
xhci0: Unable to map MSI-X table
usbus1 on xhci0
ehci1:  mem 0xf7e03000-0xf7e033ff irq 23 at 
device 29.0 on pci0
usbus2: EHCI version 1.0
usbus2 on ehci1
pcib6:  at device 30.0 on pci0
pci5:  on pcib6
isab0:  at device 31.0 on pci0
isa0:  on isab0
ahci0:  port 0xf0b0-0xf0b7,0xf0a0-0xf0a3,0xf090-0xf097,0xf080-0xf083,0xf060-0xf07f mem 0xf7e02000-0xf7e027ff 
irq 19 at device 31.2 on pci0

ahci0: AHCI v1.30 with 6 6Gbps ports, Port Multiplier not supported
ahcich0:  at channel 0 on ahci0
ahcich1:  at channel 1 on ahci0
ahciem0:  on ahci0
acpi_button0:  on acpi0
acpi_tz0:  on acpi0
acpi_tz1:  on acpi0
atkbdc0:  port 0x60,0x64 irq 1 on acpi0
atkbd0:  irq 1 on atkbdc0
kbd0 at atkbd0
atkbd0: [GIANT-LOCKED]
orm0:  at iomem 0xce800-0xcf7ff on isa0
ppc0: cannot reserve I/O port range
est0:  on cpu0
est1:  on cpu1
est2:  on cpu2
est3:  on cpu3
est4:  on cpu4
est5:  on cpu5
est6:  on cpu6
est7:  on cpu7
usbus0: 480Mbps High Speed USB v2.0
ZFS filesystem version: 5
ZFS storage pool version: features support (5000)
Timecounters tick every 1.000 msec
nvme cam probe device init
usbus1: 5.0Gbps Super Speed USB v3.0
usbus2: 480Mbps High Speed USB v2.0
ugen0.1:  at usbus0
uhub0:  on usbus0
ugen1.1: <0x1b21> at usbus1
uhub1: <0x1b21 XHCI root HUB, class 9/0, rev 3.00/1.00, addr 1> on usbus1
ugen2.1:  at usbus2
uhub2:  on usbus2
uhub1: 4 ports with 4 removable, self powered
ses0 at ahciem0 bus 0 scbus2 target 0 lun 0
ses0:  SEMB S-E-S 2.00 device

Re: [USB] hang after upgrade from 11.0 to 11.1, ZFS or callout() related?

[Hans Petter Selasky]

On 08/07/17 18:28, Michael Schmiedgen wrote:

dmesg:

Aug  7 18:26:34 antares kernel: usbd_pipe_enter: enter
Aug  7 18:26:34 antares kernel: usbd_pipe_enter: enter
Aug  7 18:26:34 antares kernel: usbd_pipe_start: start
Aug  7 18:26:34 antares kernel: usbd_pipe_start: start
Aug  7 18:26:34 antares kernel: usbd_transfer_done: 
err=USB_ERR_NORMAL_COMPLETION
Aug  7 18:26:34 antares kernel: usbd_transfer_done: 
err=USB_ERR_NORMAL_COMPLETION

Aug  7 18:26:34 antares kernel


Can you get dmesg without the USB debug enabled?

--HPS
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: [USB] hang after upgrade from 11.0 to 11.1, ZFS or callout() related?

[Michael Schmiedgen]

On 07.08.2017 18:10, Hans Petter Selasky wrote:


Are you sure you loaded all drivers, like XHCI, EHCI, OHCI, UHCI ? DOes the 
BIOS offer any USB options?



After enabling the 'USB hands off' in BIOS I got the strange 'error 5' with 
11.1,
disable_enumeration was not enabled BTW:

https://imgur.com/a/67jV1

Switching back to 11.0 but still with 'USB hands off' activated, everything is 
fine.

Michael


--
___

Michael Schmiedgen, BSc
Senior Software Engineer

Takwa GmbH
Friedrich-List-Str. 36
99096 Erfurt GERMANY

Tel  +49 361 6534096
Fax  +49 361 6534097
Mail schmied...@takwa.de
Web  http://www.takwa.de/
___


Amtsgericht Jena HRB 112964
Geschäftsführung: Ingo Buchholz
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: [USB] hang after upgrade from 10.0 to 10.1, ZFS or callout() related?

[Michael Schmiedgen]

On 07.08.2017 18:10, Hans Petter Selasky wrote:


Are you sure you loaded all drivers, like XHCI, EHCI, OHCI, UHCI ? DOes the 
BIOS offer any USB options?


https://imgur.com/a/YN428

It seems like some cheapo hardware.

BTW, after the hang I requested KVM access at our hoster, so there
is possible new USB interference with the (crappy) KVM hardware too.
But the hang exist before the KVM was attached.

Disabeling

dev.uhub.2.disable_enumeration="1"
dev.uhub.1.disable_enumeration="1"
dev.uhub.0.disable_enumeration="1"

leads to a hang and this console output:

https://imgur.com/a/WiiQW

Thanks,
  Michael

--
___

Michael Schmiedgen, BSc
Senior Software Engineer

Takwa GmbH
Friedrich-List-Str. 36
99096 Erfurt GERMANY

Tel  +49 361 6534096
Fax  +49 361 6534097
Mail schmied...@takwa.de
Web  http://www.takwa.de/
___


Amtsgericht Jena HRB 112964
Geschäftsführung: Ingo Buchholz
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: [USB] hang after upgrade from 11.0 to 11.1, ZFS or callout() related?

[Michael Schmiedgen]

On 07.08.2017 18:10, Hans Petter Selasky wrote:


Can you try getting the dmesg.

You can also disable USB enumeration setting these:

hw.usb.disable_enumeration: 0
dev.uhub.2.disable_enumeration: 0
dev.uhub.1.disable_enumeration: 0
dev.uhub.0.disable_enumeration: 0

Are you sure you loaded all drivers, like XHCI, EHCI, OHCI, UHCI ? DOes the 
BIOS offer any USB options?



It is a generic 11.1 kernel.

I already tried hw.usb.disable_enumeration="1" but that triggered the
strange 'ZFS error 5'.

Part of the debug dmesg with 11.0 kernel below.

Thanks,
  Michael


dmesg:

Aug  7 18:26:34 antares kernel: usbd_pipe_enter: enter
Aug  7 18:26:34 antares kernel: usbd_pipe_enter: enter
Aug  7 18:26:34 antares kernel: usbd_pipe_start: start
Aug  7 18:26:34 antares kernel: usbd_pipe_start: start
Aug  7 18:26:34 antares kernel: usbd_transfer_done: 
err=USB_ERR_NORMAL_COMPLETION
Aug  7 18:26:34 antares kernel: usbd_transfer_done: 
err=USB_ERR_NORMAL_COMPLETION
Aug  7 18:26:34 antares kernel: usbd_callback_wrapper_sub: 
xfer=0xf80023165148 endpoint=0xf800231640d8 sts=0 alen=12, slen=12, 
afrm=2, nfrm=2
Aug  7 18:26:34 antares kernel: usbd_do_request_callback: st=1
Aug  7 18:26:34 antares kernel: usbd_callback_wrapper_sub: 
xfer=0xf80023196148 endpoint=0xf8002318f0d8 sts=0 alen=12, slen=12, 
afrm=2, nfrm=2
Aug  7 18:26:34 antares kernel: usbd_do_request_callback: st=1
Aug  7 18:26:34 antares kernel: usbd_do_request_callback: st=0
Aug  7 18:26:34 antares kernel: usbd_transfer_submit: xfer=0xf80023165148, 
endpoint=0xf800231640d8, nframes=2, dir=read
Aug  7 18:26:34 antares kernel: usb_dump_endpoint: endpoint=0xf800231640d8 edesc=0xf80023164720 isoc_next=0 
toggle_next=0usbd_do_request_callback: st=0

Aug  7 18:26:34 antares kernel: bEndpointAddress=0x00usbd_transfer_submit: 
xfer=0xf80023196148, endpoint=0xf8002318f0d8, nframes=2, dir=read
Aug  7 18:26:34 antares kernel:
Aug  7 18:26:34 antares kernel: usb_dump_endpoint: endpoint=0xf8002318f0d8usb_dump_queue: endpoint=0xf800231640d8 xfer: 
edesc=0xf8002318f720 isoc_next=0 toggle_next=0

Aug  7 18:26:34 antares kernel: bEndpointAddress=0x00usbd_pipe_enter: enter
Aug  7 18:26:34 antares kernel:
Aug  7 18:26:34 antares kernel: usbd_pipe_start: start
Aug  7 18:26:34 antares kernel: usb_dump_queue: endpoint=0xf8002318f0d8 
xfer:
Aug  7 18:26:34 antares kernel: usbd_pipe_enter: enter
Aug  7 18:26:34 antares kernel: usbd_pipe_start: start
Aug  7 18:26:34 antares kernel: usbd_transfer_done: 
err=USB_ERR_NORMAL_COMPLETION
Aug  7 18:26:34 antares kernel: usbd_transfer_done: 
err=USB_ERR_NORMAL_COMPLETION
Aug  7 18:26:34 antares kernel: usbd_callback_wrapper_sub: 
xfer=0xf80023196148 endpoint=0xf8002318f0d8 sts=0 alen=12, slen=12, 
afrm=2, nfrm=2
Aug  7 18:26:34 antares kernel: usbd_callback_wrapper_sub: 
xfer=0xf80023165148 endpoint=0xf800231640d8 sts=0 alen=12, slen=12, 
afrm=2, nfrm=2
Aug  7 18:26:34 antares kernel: usbd_do_request_callback: st=1
Aug  7 18:26:34 antares kernel: usbd_do_request_callback: st=1
Aug  7 18:26:34 antares kernel: usbd_do_request_callback: st=0
Aug  7 18:26:34 antares kernel: usbd_transfer_submit: xfer=0xf80023165148, 
endpoint=0xf800231640d8, nframes=2, dir=read
Aug  7 18:26:34 antares kernel: usbd_do_request_callback: st=0
Aug  7 18:26:34 antares kernel: usb_dump_endpoint: endpoint=0xf800231640d8usbd_transfer_submit: xfer=0xf80023196148, 
endpoint=0xf8002318f0d8, nframes=2, dir=read
Aug  7 18:26:34 antares kernel: edesc=0xf80023164720 isoc_next=0 toggle_next=0usb_dump_endpoint: endpoint=0xf8002318f0d8 bEndpointAddress=0x00 
edesc=0xf8002318f720 isoc_next=0 toggle_next=0

Aug  7 18:26:34 antares kernel: bEndpointAddress=0x00usb_dump_queue: 
endpoint=0xf800231640d8 xfer:
Aug  7 18:26:34 antares kernel:
Aug  7 18:26:34 antares kernel: usb_dump_queue: endpoint=0xf8002318f0d8 
xfer: usbd_pipe_enter: enter
Aug  7 18:26:34 antares kernel:
Aug  7 18:26:34 antares kernel: usbd_pipe_start: start
Aug  7 18:26:34 antares kernel: usbd_pipe_enter: enter
Aug  7 18:26:34 antares kernel: usbd_pipe_start: start
Aug  7 18:26:34 antares kernel: usbd_transfer_done: 
err=USB_ERR_NORMAL_COMPLETION
Aug  7 18:26:34 antares kernel: usbd_callback_wrapper_sub: 
xfer=0xf80023196148 endpoint=0xf8002318f0d8 sts=0 alen=12, slen=12, 
afrm=2, nfrm=2
Aug  7 18:26:34 antares kernel: usbd_transfer_done: 
err=USB_ERR_NORMAL_COMPLETION
Aug  7 18:26:34 antares kernel: usbd_do_request_callback: st=1
Aug  7 18:26:34 antares kernel: usbd_callback_wrapper_sub: 
xfer=0xf80023165148 endpoint=0xf800231640d8 sts=0 alen=12, slen=12, 
afrm=2, nfrm=2
Aug  7 18:26:34 antares kernel: usbd_do_request_callback: st=0
Aug  7 18:26:34 antares kernel: usbd_do_request_callback: st=1
Aug  7 18:26:34 antares kernel: usbd_transfer_submit: xfer=0xf80023196148, 
endpoint=0xf8002318f0d8, nframes=2, dir=read
Aug  7 18:26:34 antares kernel: usbd_do_request_callback: st=0
Aug  7 

Re: [USB] hang after upgrade from 10.0 to 10.1, ZFS or callout() related?

[Hans Petter Selasky]

On 08/07/17 17:59, Michael Schmiedgen wrote:

Hi list,

after upgrading kernel from 11.0 to 11.1 the boot process stopped,
waiting forever for some USB stuff. I tried to skip waiting with

hw.usb.no_boot_wait="1"

in /boot/loader.conf but then I got a very strange ZFS 'mount error 5',
which I had some time ago upgrading from 10.0 to 10.1. That error did
magically went away with 11.0, and now it seems to pop up again:

https://lists.freebsd.org/pipermail/freebsd-current/2014-October/052900.html 



https://lists.freebsd.org/pipermail/freebsd-stable/2014-December/081192.html 



Can you try getting the dmesg.

You can also disable USB enumeration setting these:

hw.usb.disable_enumeration: 0
dev.uhub.2.disable_enumeration: 0
dev.uhub.1.disable_enumeration: 0
dev.uhub.0.disable_enumeration: 0

Are you sure you loaded all drivers, like XHCI, EHCI, OHCI, UHCI ? DOes 
the BIOS offer any USB options?


--HPS





So I reset the boot wait option to default again and switched on some USB
debug options:

https://imgur.com/a/xzkrC


Anybody? Thanks,
   Michael



___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

[Bug 221146] [LAGG] Problem with second laggport

[bugzilla-noreply]

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

Sean Bruno  changed:

   What|Removed |Added

 Status|Open|In Progress
 CC||sbr...@freebsd.org

--- Comment #13 from Sean Bruno  ---
(In reply to Cassiano Peixoto from comment #8)
For NetMap, yes.  That would be a different issue.  Which driver?

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

[USB] hang after upgrade from 10.0 to 10.1, ZFS or callout() related?

[Michael Schmiedgen]

Hi list,

after upgrading kernel from 11.0 to 11.1 the boot process stopped,
waiting forever for some USB stuff. I tried to skip waiting with

hw.usb.no_boot_wait="1"

in /boot/loader.conf but then I got a very strange ZFS 'mount error 5',
which I had some time ago upgrading from 10.0 to 10.1. That error did
magically went away with 11.0, and now it seems to pop up again:

https://lists.freebsd.org/pipermail/freebsd-current/2014-October/052900.html

https://lists.freebsd.org/pipermail/freebsd-stable/2014-December/081192.html


So I reset the boot wait option to default again and switched on some USB
debug options:

https://imgur.com/a/xzkrC


Anybody? Thanks,
  Michael

--
___

Michael Schmiedgen, BSc
Senior Software Engineer

Takwa GmbH
Friedrich-List-Str. 36
99096 Erfurt GERMANY

Tel  +49 361 6534096
Fax  +49 361 6534097
Mail schmied...@takwa.de
Web  http://www.takwa.de/
___


Amtsgericht Jena HRB 112964
Geschäftsführung: Ingo Buchholz
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: 11.1-RELEASE has issue with system headers in pedantic mode (type nullability specifier)

[David Chisnall]

On 7 Aug 2017, at 16:20, Maxim Sobolev  wrote:
> 
> One way to defeat this would be to mark those headers with the #pragma
> clang system_header. As per:
> 
> https://clang.llvm.org/docs/UsersManual.html#id27

That won’t fix the issue, because base (as you can see from the passed compile 
command) is compiled with -Wsystem-headers, which issues warnings even in 
system headers.  This is increasingly unhelpful and must, for example, be 
turned off when compiling anything written in C++ because of warnings in libc++ 
headers.

David

___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: 11.1-RELEASE has issue with system headers in pedantic mode (type nullability specifier)

[Maxim Sobolev]

One way to defeat this would be to mark those headers with the #pragma
clang system_header. As per:

https://clang.llvm.org/docs/UsersManual.html#id27

-Max

On Mon, Aug 7, 2017 at 6:20 AM, Maxim Sobolev  wrote:

> Hi, we noticed that some of our internal packages fail the build on 11.1
> now with -pedantic:
>
> *00:31:09.178* Warning: Object directory not changed from original 
> /tmp/mnt/dncd/work/dncd-20170627161415*00:31:09.178* cc -pipe -g3 -O0 -pipe 
> -fstack-protector -fno-strict-aliasing -Wall -pedantic -O0 -g3   -g3 -O0 
> -pipe -MD  -MF.depend.main.o -MTmain.o -std=gnu99 -fstack-protector-strong 
> -Wsystem-headers -Werror -Wall -Wno-format-y2k -Wno-uninitialized 
> -Wno-pointer-sign -Wno-empty-body -Wno-string-plus-int 
> -Wno-unused-const-variable -Wno-tautological-compare -Wno-unused-value 
> -Wno-parentheses-equality -Wno-unused-function -Wno-enum-conversion 
> -Wno-unused-local-typedef -Wno-address-of-packed-member -Wno-switch 
> -Wno-switch-enum -Wno-knr-promoted-parameter  -Qunused-arguments  -c main.c 
> -o main.o*00:31:09.455* In file included from main.c:17:*00:31:09.456* 
> /usr/include/err.h:63:27: error: type nullability specifier '_Nullable' is a 
> Clang extension [-Werror,-Wnullability-extension]*00:31:09.456* void
> err_set_exit(void (* _Nullable)(int));*00:31:09.456*  
>
  ^*00:31:09.456* In file included from main.c:19:*00:31:09.456* 
/usr/include/signal.h:87:27: error: type nullability specifier '_Nonnull' is a 
Clang extension [-Werror,-Wnullability-extension]*00:31:09.456* int 
sigpending(sigset_t * _Nonnull);
>
>
> I am not sure what the solution might be, perhaps change pedantic to make 
> this condition non-fatal in pedantic mode?
>
>
> -Max
>
>
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

11.1-RELEASE has issue with system headers in pedantic mode (type nullability specifier)

[Maxim Sobolev]

Hi, we noticed that some of our internal packages fail the build on 11.1
now with -pedantic:

*00:31:09.178* Warning: Object directory not changed from original
/tmp/mnt/dncd/work/dncd-20170627161415*00:31:09.178* cc -pipe -g3 -O0
-pipe -fstack-protector -fno-strict-aliasing -Wall -pedantic -O0 -g3
-g3 -O0 -pipe -MD  -MF.depend.main.o -MTmain.o -std=gnu99
-fstack-protector-strong -Wsystem-headers -Werror -Wall
-Wno-format-y2k -Wno-uninitialized -Wno-pointer-sign -Wno-empty-body
-Wno-string-plus-int -Wno-unused-const-variable
-Wno-tautological-compare -Wno-unused-value -Wno-parentheses-equality
-Wno-unused-function -Wno-enum-conversion -Wno-unused-local-typedef
-Wno-address-of-packed-member -Wno-switch -Wno-switch-enum
-Wno-knr-promoted-parameter  -Qunused-arguments  -c main.c -o
main.o*00:31:09.455* In file included from main.c:17:*00:31:09.456*
/usr/include/err.h:63:27: error: type nullability specifier
'_Nullable' is a Clang extension
[-Werror,-Wnullability-extension]*00:31:09.456* void
err_set_exit(void (* _Nullable)(int));*00:31:09.456*
   ^*00:31:09.456* In file included from
main.c:19:*00:31:09.456* /usr/include/signal.h:87:27: error: type
nullability specifier '_Nonnull' is a Clang extension
[-Werror,-Wnullability-extension]*00:31:09.456* int
sigpending(sigset_t * _Nonnull);


I am not sure what the solution might be, perhaps change pedantic to
make this condition non-fatal in pedantic mode?


-Max
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

[Bug 221050] emulators/virtualbox-ose: Bridged network doesn't work (11.1-RELEASE)

[bugzilla-noreply]

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

Kubilay Kocak  changed:

   What|Removed |Added

 CC|freebsd-stable@FreeBSD.org  |ger...@freebsd.org
   See Also||https://bugs.freebsd.org/bu
   ||gzilla/show_bug.cgi?id=2211
   ||11,
   ||https://bugs.freebsd.org/bu
   ||gzilla/show_bug.cgi?id=2212
   ||37

--- Comment #16 from Kubilay Kocak  ---
(In reply to vermaden from comment #15)

Please use attachments (not comments) for long bodfies of text like log/build
files, configuration files, etc.

The errors looks very much like:

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=22(gcc6-aux)
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=221237 (gcc5)

But for gcc48

CC maintainer

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

Re: SLAAC not working

[Andrey V. Elsukov]

On 07.08.2017 15:30, Andrey V. Elsukov wrote:
> On 06.08.2017 06:35, Greg Rivers wrote:
>> The running interface looks like this:
>> lagg0: flags=8843 metric 0 mtu 1500
>>  
>> options=507bb
>>  ether ac:16:2d:1e:b8:80
>>  inet xxx.xxx.217.100 netmask 0xff80 broadcast xxx.xxx.217.127 
>>  inet6 fe80::ae16:2dff:fe1e:b880%lagg0 prefixlen 64 scopeid 0xc 
>>  nd6 options=23
>>  media: Ethernet autoselect
>>  status: active
>>  groups: lagg 
>>  laggproto failover lagghash l2,l3,l4
>>  laggport: oce0 flags=5
>>  laggport: oce1 flags=0<>
> 
> You can set net.inet6.icmp6.nd6_debug=1 and I think you will see the
> message that mtu exceeds maxmtu value.

But it seems, this should only ignore the mtu option.
So, set net.inet6.icmp6.nd6_debug=1 and show what you have in the
 ndp -p
 ndp -r
 ndp -i lagg0

-- 
WBR, Andrey V. Elsukov



signature.asc
Description: OpenPGP digital signature

[Bug 221050] emulators/virtualbox-ose: Bridged network doesn't work (11.1-RELEASE)

[bugzilla-noreply]

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

verma...@interia.pl changed:

   What|Removed |Added

 CC||verma...@interia.pl

--- Comment #15 from verma...@interia.pl ---
Compilation fails for me:

# make -C /usr/ports/emulators/virtualbox-ose-kmod install
(...)
rm -rf $backupdir; exit $rc
gmake[7]: Leaving directory
'/usr/ports/obj/usr/ports/devel/kBuild/work/kBuild-0.1.9998/out/freebsd.amd64/release/bootstrap/sed/doc'
Making all in testsuite
gmake[7]: Entering directory
'/usr/ports/obj/usr/ports/devel/kBuild/work/kBuild-0.1.9998/out/freebsd.amd64/release/bootstrap/sed/testsuite'
gmake[7]: Nothing to be done for 'all'.
gmake[7]: Leaving directory
'/usr/ports/obj/usr/ports/devel/kBuild/work/kBuild-0.1.9998/out/freebsd.amd64/release/bootstrap/sed/testsuite'
gmake[7]: Entering directory
'/usr/ports/obj/usr/ports/devel/kBuild/work/kBuild-0.1.9998/out/freebsd.amd64/release/bootstrap/sed'
gmake[7]: Leaving directory
'/usr/ports/obj/usr/ports/devel/kBuild/work/kBuild-0.1.9998/out/freebsd.amd64/release/bootstrap/sed'
gmake[6]: Leaving directory
'/usr/ports/obj/usr/ports/devel/kBuild/work/kBuild-0.1.9998/out/freebsd.amd64/release/bootstrap/sed'
gmake[5]: Leaving directory
'/usr/ports/obj/usr/ports/devel/kBuild/work/kBuild-0.1.9998/out/freebsd.amd64/release/bootstrap/sed'
cp -f
/usr/ports/obj/usr/ports/devel/kBuild/work/kBuild-0.1.9998/out/freebsd.amd64/release/bootstrap/sed/sed/sed
/usr/ports/obj/usr/ports/devel/kBuild/work/kBuild-0.1.9998/out/freebsd.amd64/release/bootstrap/kmk/kmk_sed
ln -s /bin/echo
/usr/ports/obj/usr/ports/devel/kBuild/work/kBuild-0.1.9998/out/freebsd.amd64/release/bootstrap/kmk/kmk_echo
cp -f
/usr/ports/obj/usr/ports/devel/kBuild/work/kBuild-0.1.9998/out/freebsd.amd64/release/bootstrap/kmk/config.h
/usr/ports/obj/usr/ports/devel/kBuild/work/kBuild-0.1.9998/src/kmk/config.h.freebsd
echo "" >>
/usr/ports/obj/usr/ports/devel/kBuild/work/kBuild-0.1.9998/src/kmk/config.h.freebsd
echo '#include "inlined_memchr.h"' >>
/usr/ports/obj/usr/ports/devel/kBuild/work/kBuild-0.1.9998/src/kmk/config.h.freebsd
cp -f
/usr/ports/obj/usr/ports/devel/kBuild/work/kBuild-0.1.9998/out/freebsd.amd64/release/bootstrap/sed/config.h
/usr/ports/obj/usr/ports/devel/kBuild/work/kBuild-0.1.9998/src/sed/config.h.freebsd
KBUILD_BIN_PATH=/usr/ports/obj/usr/ports/devel/kBuild/work/kBuild-0.1.9998/out/freebsd.amd64/release/bootstrap/kmk
/usr/ports/obj/usr/ports/devel/kBuild/work/kBuild-0.1.9998/out/freebsd.amd64/release/bootstrap/kmk/kmk
-C /usr/ports/obj/usr/ports/devel/kBuild/work/kBuild-0.1.9998
KBUILD_BOOTSTRAP=1
kmk: Entering directory
`/usr/ports/obj/usr/ports/devel/kBuild/work/kBuild-0.1.9998'
Config.kmk:87: Neither SvnInfo nor .svn/* was found in the root. Will have to
cook up something too keep the build happy.
Config.kmk:99:
/usr/ports/obj/usr/ports/devel/kBuild/work/kBuild-0.1.9998/out/freebsd.amd64/release/obj/SvnInfo.kmk:
No such file or directory
kmk_builtin_rm -f
/usr/ports/obj/usr/ports/devel/kBuild/work/kBuild-0.1.9998/out/freebsd.amd64/release/obj/SvnInfo.kmk
kmk_builtin_mkdir -p
/usr/ports/obj/usr/ports/devel/kBuild/work/kBuild-0.1.9998/out/freebsd.amd64/release/obj
kmk_builtin_append
/usr/ports/obj/usr/ports/devel/kBuild/work/kBuild-0.1.9998/out/freebsd.amd64/release/obj/SvnInfo.kmk
'KBUILD_SVN_REV := 0'
kmk_builtin_append
/usr/ports/obj/usr/ports/devel/kBuild/work/kBuild-0.1.9998/out/freebsd.amd64/release/obj/SvnInfo.kmk
'KBUILD_SVN_URL := /dev/null'
kmk: Leaving directory
`/usr/ports/obj/usr/ports/devel/kBuild/work/kBuild-0.1.9998'
kmk: Entering directory
`/usr/ports/obj/usr/ports/devel/kBuild/work/kBuild-0.1.9998'
Config.kmk:87: Neither SvnInfo nor .svn/* was found in the root. Will have to
cook up something too keep the build happy.
kBuild: Pass - Build Programs
kBuild: Pass - Libraries
kBuild: Compiling kDep -
/usr/ports/obj/usr/ports/devel/kBuild/work/kBuild-0.1.9998/src/lib/kDep.c
kBuild: Compiling kUtil -
/usr/ports/obj/usr/ports/devel/kBuild/work/kBuild-0.1.9998/src/lib/crc32.c
kBuild: Compiling kUtil -
/usr/ports/obj/usr/ports/devel/kBuild/work/kBuild-0.1.9998/src/lib/md5.c
kBuild: Compiling kUtil -
/usr/ports/obj/usr/ports/devel/kBuild/work/kBuild-0.1.9998/src/lib/maybe_con_write.c
In file included from
/usr/ports/obj/usr/ports/devel/kBuild/work/kBuild-0.1.9998/src/lib/crc32.c:48:0:
/usr/local/lib/gcc48/gcc/x86_64-portbld-freebsd11.0/4.8.5/include-fixed/sys/types.h:266:1:
error: unknown type name '__vm_ooffset_t'
 typedef __vm_ooffset_t vm_ooffset_t;
 ^
In file included from
/usr/local/lib/gcc48/gcc/x86_64-portbld-freebsd11.0/4.8.5/include-fixed/unistd.h:46:0,
 from
/usr/ports/obj/usr/ports/devel/kBuild/work/kBuild-0.1.9998/src/lib/maybe_con_write.c:45:
/usr/local/lib/gcc48/gcc/x86_64-portbld-freebsd11.0/4.8.5/include-fixed/sys/types.h:266:1:
error: unknown type name '__vm_ooffset_t'
 typedef __vm_ooffset_t vm_ooffset_t;

Re: SLAAC not working

[Andrey V. Elsukov]

On 06.08.2017 06:35, Greg Rivers wrote:
> The running interface looks like this:
> lagg0: flags=8843 metric 0 mtu 1500
>   
> options=507bb
>   ether ac:16:2d:1e:b8:80
>   inet xxx.xxx.217.100 netmask 0xff80 broadcast xxx.xxx.217.127 
>   inet6 fe80::ae16:2dff:fe1e:b880%lagg0 prefixlen 64 scopeid 0xc 
>   nd6 options=23
>   media: Ethernet autoselect
>   status: active
>   groups: lagg 
>   laggproto failover lagghash l2,l3,l4
>   laggport: oce0 flags=5
>   laggport: oce1 flags=0<>

You can set net.inet6.icmp6.nd6_debug=1 and I think you will see the
message that mtu exceeds maxmtu value.

-- 
WBR, Andrey V. Elsukov



signature.asc
Description: OpenPGP digital signature