Wayland update
Hi Here's a Friday night update on Wayland. https://twitter.com/Yohanesu75Tweet/status/766799811328696320 All available as ports very soon on: https://github.com/FreeBSDDesktop/freebsd-ports-graphics/tree/xserver-mesa-next (check for merged PRs) Requires evdev enabled kernel from: https://github.com/FreeBSDDesktop/freebsd-base-graphics/tree/drm-next sway also runs fine with x11 backend (in a window on x11). Have a nice weekend! -- =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- 秘密保持について：この電子メールは、名宛人に送信したものであり、秘匿特権の対象となる情報を含んでいます。 もし、名宛人以外の方が受信された場合、このメールの破棄、およびこのメールに関する一切の開示、 複写、配布、その他の利用、または記載内容に基づくいかなる行動もされないようお願い申し上げます。 --- CONFIDENTIALITY NOTE: The information in this email is confidential and intended solely for the addressee. Disclosure, copying, distribution or any other action of use of this email by person other than intended recipient, is prohibited. If you are not the intended recipient and have received this email in error, please destroy the original message. ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
[CFT] New version of webcamd, now v4.8.0.2
Hi, If you are using webcamd, please help test the latest version which includes the most recent Linux v4.8-rc1 media tree sources. The latest webcamd port is available from here: svn --username anonsvn --password anonsvn \ checkout svn://svn.turbocat.net/i4b/trunk/ports/multimedia/webcamd Please test and report any regression issues to me or freebsd-multime...@freebsd.org Changes: - updated all Linux kernel sources to the latest Linux' Torvalds - fixed some minor bugs in the webcamd Linux kernel emulation - improved Linux kernel emulation support - added support for the coming evdev kernel module (GSOC project) Related work: https://reviews.freebsd.org/D6998 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=196678 --HPS ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: ahci timeout during boot on a particular mobo
On 19/08/2016 14:06, Alexander Motin wrote: > On 19.08.16 11:30, Andriy Gapon wrote: >> So, what's suspicious here is that we discover two AHCI channels on the >> JMicron >> device and we seem to discover some sort of a device on one of them. But the >> communication with that (phantom?) device times out and that causes a very >> long >> delay during the boot. > > This fake device is the most interesting part. Marvell AHCI RAID chips > in such way expose RAID management device, but I doubt that JMicron is > so advanced, at least it seems like not implemented properly enough. > >> Is there a way to fix the boot delay? >> >> Searched for JMB361 in the source code, looked at some nearby device entries, >> and - is it as simple as adding AHCI_Q_1CH quick for this device? > > AHCI_Q_1CH quirk was added for early Marvell chips that were ever > dirtier mix of legacy ATA and AHCI, that reported total number of ports > instead of expected AHCI ones. May be JMB361 is also like that, but I > never had those check. JMB362 I have does not have this problem, > reporting two real SATA ports, even though it has one legacy PATA port > also. I don't have strong objections against this quirk. I am not sure > whether it is right solution, but suppose that in couple years nobody > will bother about that hardware at all. > Thank you for the reply! I found this bit of info about JMB361 http://www.clubedohardware.com.br/datasheets/JMB361.pdf and it confirms that the controller has a single SATA port. And JMB362 has two ports http://www.clubedohardware.com.br/datasheets/JMB361.pdf. Maybe the second port on JMB361 has some sort of a SATA-to-IDE adapter and perhaps it's that adapter that gets detected as a phantom device. -- Andriy Gapon ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: ahci timeout during boot on a particular mobo
On 19.08.16 11:30, Andriy Gapon wrote: > So, what's suspicious here is that we discover two AHCI channels on the > JMicron > device and we seem to discover some sort of a device on one of them. But the > communication with that (phantom?) device times out and that causes a very > long > delay during the boot. This fake device is the most interesting part. Marvell AHCI RAID chips in such way expose RAID management device, but I doubt that JMicron is so advanced, at least it seems like not implemented properly enough. > Is there a way to fix the boot delay? > > Searched for JMB361 in the source code, looked at some nearby device entries, > and - is it as simple as adding AHCI_Q_1CH quick for this device? AHCI_Q_1CH quirk was added for early Marvell chips that were ever dirtier mix of legacy ATA and AHCI, that reported total number of ports instead of expected AHCI ones. May be JMB361 is also like that, but I never had those check. JMB362 I have does not have this problem, reporting two real SATA ports, even though it has one legacy PATA port also. I don't have strong objections against this quirk. I am not sure whether it is right solution, but suppose that in couple years nobody will bother about that hardware at all. -- Alexander Motin ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
ahci timeout during boot on a particular mobo
The motherboard is Asus M4A89GTD PRO. This is how the manufacturer describes its storage hardware: AMD® SB850 chipset - 6 x SATA 6.0 Gb/s ports with RAID 0, 1, 5, and 10 support JMicron® JMB361 PATA and SATA controller - 1 x Power eSATA 3.0 Gb/s port - 1 x Ultra DMA 133/100 for up to 2 PATA devices This is what pciconf tells about the additional controller: atapci0@pci0:2:0:0: class=0x010185 card=0x824f1043 chip=0x2361197b rev=0x02 hdr=0x00 vendor = 'JMicron Technology Corp.' device = 'JMB361 AHCI/IDE' class = mass storage subclass = ATA At the moment there is a SATA disk connected to one of the chipset's ports and an old optical disk drive connected to the IDE port. Here is what FreeBSD sees during boot: atapci0: port 0xcc00-0xcc07,0xc880-0xc883,0xc800-0xc807,0xc480-0xc483,0xc400-0xc40f mem 0xfe8fe000-0xfe8f irq 18 at device 0.0 on pci2 ahci0: at channel -1 on atapci0 ahci0: AHCI v1.00 with 2 3Gbps ports, Port Multiplier supported ahci0: quirks=0x1 ahci0: Caps: 64bit NCQ ALP AL CLO 3Gbps PM PMD SSC PSC 32cmd 2ports ahcich0: at channel 0 on ahci0 ahcich0: Caps: HPCP ahcich1: at channel 1 on ahci0 ahcich1: Caps: HPCP ata2: at channel 0 on atapci0 ahci1: port 0xa000-0xa007,0x9000-0x9003,0x8000-0x8007,0x7000-0x7003,0x6000-0x600f mem 0xfe5ffc00-0xfe5f irq 19 at device 17.0 on pci0 ahci1: AHCI v1.20 with 6 6Gbps ports, Port Multiplier supported ahci1: Caps: 64bit NCQ SNTF MPS ALP AL CLO 6Gbps PM PMD SSC PSC 32cmd 6ports ahci1: Caps2: ahcich2: at channel 0 on ahci1 ahcich2: Caps: ahcich3: at channel 1 on ahci1 ahcich3: Caps: ahcich4: at channel 2 on ahci1 ahcich4: Caps: ahcich5: at channel 3 on ahci1 ahcich5: Caps: ahcich6: at channel 4 on ahci1 ahcich6: Caps: ahcich7: at channel 5 on ahci1 ahcich7: Caps: ahcich0: AHCI reset... ahcich0: SATA connect timeout time=1us status= ahcich0: AHCI reset: device not found ahcich1: AHCI reset... ahcich1: SATA connect time=0us status=0123 ahcich1: AHCI reset: device found ata2: reset tp1 mask=03 ostat0=50 ostat1=00 ata2: stat0=0x00 err=0x01 lsb=0x14 msb=0xeb ata2: stat1=0x00 err=0x00 lsb=0x00 msb=0x00 ata2: reset tp2 stat0=00 stat1=00 devices=0x1 ahcich2: AHCI reset... ahcich2: SATA connect timeout time=1us status= ahcich2: AHCI reset: device not found ahcich3: AHCI reset... ahcich3: SATA connect time=800us status=0123 ahcich3: AHCI reset: device found ahcich4: AHCI reset... ahcich4: SATA connect timeout time=1us status= ahcich4: AHCI reset: device not found ahcich5: AHCI reset... ahcich5: SATA connect timeout time=1us status= ahcich5: AHCI reset: device not found ahcich6: AHCI reset... ahcich6: SATA connect timeout time=1us status= ahcich6: AHCI reset: device not found ahcich7: AHCI reset... ahcich7: SATA connect timeout time=1us status= ahcich7: AHCI reset: device not found ahcich3: AHCI reset: device ready after 100ms ahcich1: AHCI reset: device not ready after 31000ms (tfd = 00ff) ahcich1: Poll timeout on slot 0 port 15 ahcich1: is cs 0001 ss rs 0001 tfd 77 serr cmd 0004c011 (aprobe1:ahcich1:0:15:0): SOFT_RESET. ACB: 00 00 00 00 00 00 00 00 00 00 00 00 (aprobe1:ahcich1:0:15:0): CAM status: Command timeout (aprobe1:ahcich1:0:15:0): Error 5, Retries exhausted run_interrupt_driven_hooks: still waiting after 60 seconds for xpt_config ahcich1: Poll timeout on slot 0 port 15 ahcich1: is cs 0001 ss rs 0001 tfd 77 serr cmd 0004c011 (aprobe1:ahcich1:0:15:0): SOFT_RESET. ACB: 00 00 00 00 00 00 00 00 00 00 00 00 (aprobe1:ahcich1:0:15:0): CAM status: Command timeout (aprobe1:ahcich1:0:15:0): Error 5, Retries exhausted ahcich1: Poll timeout on slot 0 port 0 ahcich1: is cs 0001 ss rs 0001 tfd 77 serr cmd 0004c011 (aprobe0:ahcich1:0:0:0): SOFT_RESET. ACB: 00 00 00 00 00 00 00 00 00 00 00 00 (aprobe0:ahcich1:0:0:0): CAM status: Command timeout (aprobe0:ahcich1:0:0:0): Error 5, Retries exhausted ada0 at ahcich3 bus 0 scbus4 target 0 lun 0 ada0: ATA-8 SATA 2.x device ada0: Serial Number 5VM0NB43 ada0: 300.000MB/s transfers (SATA 2.x, UDMA6, PIO 8192bytes) ada0: Command Queueing enabled ada0: 476940MB (976773168 512 byte sectors: 16H 63S/T 16383C) pass0 at ata2 bus 0 scbus2 target 0 lun 0 pass0: 33.300MB/s transfers (UDMA2, ATAPI 12bytes, PIO 65534bytes) pass1 at ahcich3 bus 0 scbus4 target 0 lun 0 pass1: ATA-8 SATA 2.x device pass1: 300.000MB/s transfers (SATA 2.x, UDMA6, PIO 8192bytes) cd0 at ata2 bus 0 scbus2 target 0 lun 0 cd0: 33.300MB/s transfers (UDMA2, ATAPI 12bytes, PIO 65534bytes) So, what's suspicious here is that we discover two AHCI channels on the JMicron device and we seem to discover some sort of a device on one of them. But the communication with that (phantom?) device times out and that causes a very long delay during the boot. Once the system is up I do not see any
