From owner-freebsd-usb@freebsd.org Sun Feb 19 09:04:13 2017 Return-Path: Delivered-To: freebsd-usb@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id A2821CE55CE for ; Sun, 19 Feb 2017 09:04:13 +0000 (UTC) (envelope-from jan.l.peterson@gmail.com) Received: from mail-pf0-x22c.google.com (mail-pf0-x22c.google.com [IPv6:2607:f8b0:400e:c00::22c]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 64D871433 for ; Sun, 19 Feb 2017 09:04:13 +0000 (UTC) (envelope-from jan.l.peterson@gmail.com) Received: by mail-pf0-x22c.google.com with SMTP id 68so12235890pfx.2 for ; Sun, 19 Feb 2017 01:04:13 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=to:from:subject:openpgp:message-id:date:user-agent:mime-version; bh=JKd2CoshebHP6Sv2JUwYQhLYbfWstCO+LWlaGsVdEOs=; b=QGh1ou5DMRLgyPrhGOfkL7enFzOiQXZhjEI1DM0Ww6Jh0iLEmMKmpc+Uw91BAU2RLa lHyWoiy8TspltYejWU/LfvcpWIXQndFX1GF3+qLdrpWdzPJNcMoeErOphTDMsIX2AN6O qNsgGl6gnUDSNc0MChR1FLgWi5z4tZCDuoQJEKHSfsBNF5Pt6IQos7lvvAy2xtWF5UPW YdjCcZ+4cDrHfbxKgLEy5lMvxQo+gf9S/b0qJRf/i52qxK0XkbUq1A/peDatLGe/ksZW zMMMQPI8p239X1rsl7TMYpCSCWjCI7S1ZULECt1b2wdG+3nm1+bdsszF1CJeIp2YwNRv S5fw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:to:from:subject:openpgp:message-id:date :user-agent:mime-version; bh=JKd2CoshebHP6Sv2JUwYQhLYbfWstCO+LWlaGsVdEOs=; b=lQsJmizSvv/x0NC9BACz6obgaKTeTZK67rWkF4TOM+BbuXL3s2ZepPwZdUv6um28dn oxuPCoTKDc6Eac8TuTJA5vOUwHFybot3syw8p91hSEA0JP/dXyL+ebx/dkFr1/0f5YrH KKAJoK9FXL58VN1OssE3DYvr9rx2nWDd1kpiRDcHC8VQI8zIux/MXk1ekRBex3TB0kYP 1wRk4XUsHkqbSKG3Hsl42rHmghB+zLqHF9fvbJWF7soO/BbwRi9KfiA0avjLaV/O8M40 m0wmfRWNdHPdBW6kAgQE3jFVhTAH4Fp36XWh1NOBaA/D7kDQecSaigRVxYN7uOUA76zd 3CYw== X-Gm-Message-State: AMke39nY0EA4AMj/42TR4b2msB+PFtgcG6AosPZZyU1RRPuINdNCRr3+1LjQobxBURAIfA== X-Received: by 10.84.215.154 with SMTP id l26mr23393834pli.120.1487495052652; Sun, 19 Feb 2017 01:04:12 -0800 (PST) Received: from [192.168.1.187] (c-24-2-102-99.hsd1.ut.comcast.net. [24.2.102.99]) by smtp.gmail.com with ESMTPSA id 75sm16636162pfy.38.2017.02.19.01.04.11 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sun, 19 Feb 2017 01:04:11 -0800 (PST) To: freebsd-usb@freebsd.org From: "Jan L. Peterson" Subject: device not attaching at boot Openpgp: id=2CAC736D784BCE50E46350000FD833AA1EF031ED Message-ID: <68a36048-dae3-dc3b-b9f4-e63450c54045@gmail.com> Date: Sun, 19 Feb 2017 02:04:09 -0700 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:45.0) Gecko/20100101 Thunderbird/45.7.1 MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="gQettf2EtNe1tTgKB4hcJUGkmb7OtE7ka" X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 19 Feb 2017 09:04:13 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --gQettf2EtNe1tTgKB4hcJUGkmb7OtE7ka Content-Type: multipart/mixed; boundary="A2IftDKIAsQ9WRvVF5OBcv1OGhUd4JjnL"; protected-headers="v1" From: "Jan L. Peterson" To: freebsd-usb@freebsd.org Message-ID: <68a36048-dae3-dc3b-b9f4-e63450c54045@gmail.com> Subject: device not attaching at boot --A2IftDKIAsQ9WRvVF5OBcv1OGhUd4JjnL Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Hi, folks, I have a weird problem... Hardware is an HP dc7900 small form factor PC. OS is FreeBSD 11.0-RELEASE-p7. I am running the GENERIC kernel. I have a USB ethernet adapter that contains a Realtek chip... the vendor ID is 0x0bda and the product ID is 0x8153. If I plug this device into the machine while the system is already up and running, it is detected and attached as ue0 on cdce0 (it appears as ugen3.2, no matter which of the several USB ports on the machine I plug it into). If the device is plugged into the machine when it boots up, nothing I can do (short of unplugging it and replugging it) will make the machine recognize that it is there. I have tried the following: 1. played with hw.usb.timings.* values 2. usbconfig -d 3.1 set_config 255; usbconfig -d 3.1 set_config 0 (which deactivates the hub that the device is connected to and then reactivates it) 3. did the same (set_config 255; set_config 0) on *all* of the usb hubs (ugen*.1) 4. turned on various hw.usb.*.debug options (which produced copious debug info, but nothing containing the strings 8153, 0bda, or Realtek) 5. tried various devctl rescan options (including pci0) 6. googled frantically for something similar to this problem to no avail (well, I did come across some people with similar problems, but their problems all seemed to be around the device coming up with the wrong config and needing a SET_CFG_1 quirk set, which appears to already be in the kernel as of 2015 or so) I've looked for ways to force the USB bus to rescan (hence the usbconfig stuff in number 2 above) but nothing I have tried seems to work. Again, the device works fine if I unplug it from the machine and then plug it back in. It is detected, probes, and attaches just fine and dandy. The problem is that the machine is destined to be locked in a cabinet at a remote location where there won't be anyone available to go unplug and replug it any time the machine needs a reboot. To clarify... when I have the device plugged into the machine and I reboot, the device is not detected or noticed by the OS in any way.=20 There is nothing relevant in dmesg or /var/log/messages. usbconfig and devinfo do not see it at all. If I unplug the device and plug it back in, it is recognized immediately and works fine. Any ideas? -jan- --=20 Jan L. Peterson http://www.peterson-tech.com/~jlp/ --A2IftDKIAsQ9WRvVF5OBcv1OGhUd4JjnL-- --gQettf2EtNe1tTgKB4hcJUGkmb7OtE7ka Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQIcBAEBCAAGBQJYqV+KAAoJEA/YM6oe8DHtCXEQALOpr2mmTXOWqlQsCEOxENid bwmelNN1TF6Hl6YaN5kLMFriaibBpTj7gOLldDz71BPF8SikId0W+06fm5UJob8D vVmrSQWZ2ZyLxgkWaGIWQfEQdbAK+wpetn942KbXU0DJeTNVviq+SMgbzMZ1cOSh 9Ht/6t8Z1JGlqQZF95ytSSa5ysWsgvi8GXonhmYtrhutzv9SqwfX/RbpT8x6QHno I4Jch5prNB3icstcno82f5y3HBBYnz2q13BIcKX/D6O1+tGLsFT5nZGwVwh5A/lK VVJCeYAG79pY1XC9rmBidIMfk3Ft+D4K6EsQtqUuqRSAfm8wjI2+U0KLBjSAN29e 2jFNQI7bDhtVtrVJSNmb9tY49AjZUgLXQljoLlns7ftic2oYqcrLX7AsGm/wrYQw yqHo1bzSQ7eTwvuC0YBb6JmuXOxvIq1iG0dT+8RG8O9lDQ0mSqYB5Z89M3/l6LKH 8OFhRYyWNhw100AHaB7AiXbUpyYefZ3RaOoxZltF3TOVmBvvwn8GcY5His4oB33X ziNImTcxN29nHcBsnPmAfhLS2lj1IMYy33hVChFU1+HWR6n4HwsL0fd/q1Lgk5Ox bHwqtznDL+O32OyW26O5mSaqibA+KFNeklI3MwyhVAqtx6ONShgK4iMv3MnYByWQ mqVqhFpmKt2jXy7ZS3pw =skE+ -----END PGP SIGNATURE----- --gQettf2EtNe1tTgKB4hcJUGkmb7OtE7ka-- From owner-freebsd-usb@freebsd.org Sun Feb 19 09:52:44 2017 Return-Path: Delivered-To: freebsd-usb@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 43A85CDB06F for ; Sun, 19 Feb 2017 09:52:44 +0000 (UTC) (envelope-from hps@selasky.org) Received: from mail.turbocat.net (turbocat.net [88.99.82.50]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 08D50B94 for ; Sun, 19 Feb 2017 09:52:43 +0000 (UTC) (envelope-from hps@selasky.org) Received: from hps2016.home.selasky.org (unknown [62.141.129.119]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mail.turbocat.net (Postfix) with ESMTPSA id 8CB971FE086; Sun, 19 Feb 2017 10:52:38 +0100 (CET) Subject: Re: device not attaching at boot To: "Jan L. Peterson" , freebsd-usb@freebsd.org References: <68a36048-dae3-dc3b-b9f4-e63450c54045@gmail.com> From: Hans Petter Selasky Message-ID: Date: Sun, 19 Feb 2017 10:51:59 +0100 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:45.0) Gecko/20100101 Thunderbird/45.4.0 MIME-Version: 1.0 In-Reply-To: <68a36048-dae3-dc3b-b9f4-e63450c54045@gmail.com> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 19 Feb 2017 09:52:44 -0000 On 02/19/17 10:04, Jan L. Peterson wrote: > Hi, folks, > > I have a weird problem... > > Hardware is an HP dc7900 small form factor PC. OS is FreeBSD > 11.0-RELEASE-p7. I am running the GENERIC kernel. > > I have a USB ethernet adapter that contains a Realtek chip... the vendor > ID is 0x0bda and the product ID is 0x8153. > > If I plug this device into the machine while the system is already up > and running, it is detected and attached as ue0 on cdce0 (it appears as > ugen3.2, no matter which of the several USB ports on the machine I plug > it into). > > If the device is plugged into the machine when it boots up, nothing I > can do (short of unplugging it and replugging it) will make the machine > recognize that it is there. > > I have tried the following: > > 1. played with hw.usb.timings.* values > 2. usbconfig -d 3.1 set_config 255; usbconfig -d 3.1 set_config 0 > (which deactivates the hub that the device is connected to and then > reactivates it) > 3. did the same (set_config 255; set_config 0) on *all* of the usb hubs > (ugen*.1) > 4. turned on various hw.usb.*.debug options (which produced copious > debug info, but nothing containing the strings 8153, 0bda, or Realtek) > 5. tried various devctl rescan options (including pci0) > 6. googled frantically for something similar to this problem to no > avail (well, I did come across some people with similar problems, but > their problems all seemed to be around the device coming up with the > wrong config and needing a SET_CFG_1 quirk set, which appears to already > be in the kernel as of 2015 or so) > > I've looked for ways to force the USB bus to rescan (hence the usbconfig > stuff in number 2 above) but nothing I have tried seems to work. > > Again, the device works fine if I unplug it from the machine and then > plug it back in. It is detected, probes, and attaches just fine and > dandy. The problem is that the machine is destined to be locked in a > cabinet at a remote location where there won't be anyone available to go > unplug and replug it any time the machine needs a reboot. > > To clarify... when I have the device plugged into the machine and I > reboot, the device is not detected or noticed by the OS in any way. > There is nothing relevant in dmesg or /var/log/messages. usbconfig and > devinfo do not see it at all. If I unplug the device and plug it back > in, it is recognized immediately and works fine. > > Any ideas? > Hi, Have you tried a 11-stable kernel? Have you tried disabling USB in the BIOS? --HPS From owner-freebsd-usb@freebsd.org Sun Feb 19 10:10:16 2017 Return-Path: Delivered-To: freebsd-usb@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id B23E2CDB392 for ; Sun, 19 Feb 2017 10:10:16 +0000 (UTC) (envelope-from jan.l.peterson@gmail.com) Received: from mail-pg0-x22a.google.com (mail-pg0-x22a.google.com [IPv6:2607:f8b0:400e:c05::22a]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 7F907F60 for ; Sun, 19 Feb 2017 10:10:16 +0000 (UTC) (envelope-from jan.l.peterson@gmail.com) Received: by mail-pg0-x22a.google.com with SMTP id a123so5220867pgc.0 for ; Sun, 19 Feb 2017 02:10:16 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=in-reply-to:references:thread-topic:user-agent:mime-version :content-transfer-encoding:subject:from:date:to:cc:message-id; bh=5rr7UfXuiZY+kJCgofeW0a48lalVHdb092tj2jy5YIk=; b=r/BMj3x1PwgkBY4hTtGpLq0aq1KtRjJS1oXi0uoQcuLBigJ+sek02YG4XQXTDeMMRn g0SF5GsbZceX+DYB50d9avWkQUU3HkWGgruJKnBVxuYUuZGHgmm4aRWD121lWL6hp8RA g/3kPItm7fZfXtfo48hrbqY4StoaYAVfly11dqL4h/0oNz6XorUhF5smp6LK/n4/Tqk4 Ch4uDacVlqgdmPMuPyLyQxheIpQJ0dqh0460ANtvb4bNQNWNbVh0ZyXA3iG41t6vRsOf 0EXgNs3r1hD/3jp0NxsAxpmM0WAtQlLUnaAtGBajv3aCBCV2a08jqOW7NdWoWwGjBics SzjQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:in-reply-to:references:thread-topic:user-agent :mime-version:content-transfer-encoding:subject:from:date:to:cc :message-id; bh=5rr7UfXuiZY+kJCgofeW0a48lalVHdb092tj2jy5YIk=; b=cGIQOk9hNeslRxywLAiNb9pRj5rxRqy+APaT1B5XkKrAjH8vhdCutzfPghIj08puYU RbNWw/uPWuBI9w48lxVLaOvuUwBpe6CD3zwmJpRr0iffE9BWUsYMH5aCja9sqew3VXIw JbFXDLOeKbsyw5tfle3CQ8wm+63HcIUxsF19qFLXaWlv1mZYz6rrpS06TWcHFdw3toA7 UHOQJYHPNP+V7YDexxc8Xl1YE9Vj1i8KVXr83X2JfeTLZD0KvJk1OfaVj4QKNEnO4p6L iN8jO8kmEZuyOFDnN1a8weYKbbJu9smU+phsV1TEPDOS/Gk5VSOmGweFqseIA9Ztd4Vx RPgA== X-Gm-Message-State: AMke39mXIIHNqkLOqZ7XKgZNf2DBVPkbehJJSLQ27hOdrZ7n8NcPM3vgcL5KXsIFT9fG+w== X-Received: by 10.99.181.66 with SMTP id u2mr20792584pgo.164.1487499016090; Sun, 19 Feb 2017 02:10:16 -0800 (PST) Received: from [192.0.0.5] ([172.58.39.125]) by smtp.gmail.com with ESMTPSA id b75sm28838447pfb.90.2017.02.19.02.10.14 (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Sun, 19 Feb 2017 02:10:15 -0800 (PST) In-Reply-To: References: <68a36048-dae3-dc3b-b9f4-e63450c54045@gmail.com> X-Referenced-Uid: 75177 Thread-Topic: Re: device not attaching at boot User-Agent: Type for Android MIME-Version: 1.0 X-Local-Message-Id: Subject: Re: device not attaching at boot From: Jan Peterson Date: Sun, 19 Feb 2017 03:10:12 -0700 To: Hans Petter Selasky CC: freebsd-usb@freebsd.org Message-ID: Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 19 Feb 2017 10:10:16 -0000 Hello, Hans, I have not tried a -STABLE kernel=2E My kernel is -p2, with a= -p7 userland=2E I will give -STABLE a try in the morning=2E There are no = relevant USB options in the BIOS=2E The only settings are to disable specif= ic ports (for security purposes)=2E I looked for any legacy options, but th= ere were none=2E I will let the list know how it goes with -STABLE=2E Tha= nks! =C2=A0 -jan- -- =E2=81=A3Jan L=2E Peterson http://www=2Epeterson-tec= h=2Ecom/~jlp/ Sent from TypeApp =E2=80=8B On Feb 19, 2017, 02:52, at 02:5= 2, Hans Petter Selasky wrote: >On 02/19/17 10:04, Jan L= =2E Peterson wrote: >> Hi, folks, >> >> I have a weird problem=2E=2E=2E >> = >> Hardware is an HP dc7900 small form factor PC=2E OS is FreeBSD >> 11=2E= 0-RELEASE-p7=2E I am running the GENERIC kernel=2E >> >> I have a USB ethe= rnet adapter that contains a Realtek chip=2E=2E=2E the >vendor >> ID is 0x0= bda and the product ID is 0x8153=2E >> >> If I plug this device into the ma= chine while the system is already up >> and running, it is detected and att= ached as ue0 on cdce0 (it appears >as >> ugen3=2E2, no matter which of the = several USB ports on the machine I >plug >> it into)=2E >> >> If the device= is plugged into the machine when it boots up, nothing I >> can do (short o= f unplugging it and replugging it) will make the >machine >> recognize that= it is there=2E >> >> I have tried the following: >> >> 1=2E played with h= w=2Eusb=2Etimings=2E* values >> 2=2E usbconfig -d 3=2E1 set_config 255; us= bconfig -d 3=2E1 set_config 0 >> (which deactivates the hub that the device= is connected to and then >> reactivates it) >> 3=2E did the same (set_con= fig 255; set_config 0) on *all* of the usb >hubs >> (ugen*=2E1) >> 4=2E tu= rned on various hw=2Eusb=2E*=2Edebug options (which produced copious >> deb= ug info, but nothing containing the strings 8153, 0bda, or >Realtek) >> 5= =2E tried various devctl rescan options (including pci0) >> 6=2E googled = frantically for something similar to this problem to no >> avail (well, I d= id come across some people with similar problems, but >> their problems all= seemed to be around the device coming up with the >> wrong config and need= ing a SET_CFG_1 quirk set, which appears to >already >> be in the kernel as= of 2015 or so) >> >> I've looked for ways to force the USB bus to rescan (= hence the >usbconfig >> stuff in number 2 above) but nothing I have tried s= eems to work=2E >> >> Again, the device works fine if I unplug it from the = machine and then >> plug it back in=2E It is detected, probes, and attache= s just fine and >> dandy=2E The problem is that the machine is destined to= be locked in a >> cabinet at a remote location where there won't be anyone= available to >go >> unplug and replug it any time the machine needs a rebo= ot=2E >> >> To clarify=2E=2E=2E when I have the device plugged into the mac= hine and I >> reboot, the device is not detected or noticed by the OS in an= y way=2E >> There is nothing relevant in dmesg or /var/log/messages=2E usb= config >and >> devinfo do not see it at all=2E If I unplug the device and = plug it >back >> in, it is recognized immediately and works fine=2E >> >> A= ny ideas? >> > >Hi, > >Have you tried a 11-stable kernel? > >Have you tried= disabling USB in the BIOS? > >--HPS From owner-freebsd-usb@freebsd.org Sun Feb 19 21:00:43 2017 Return-Path: Delivered-To: freebsd-usb@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id B4142CE55BD for ; Sun, 19 Feb 2017 21:00:43 +0000 (UTC) (envelope-from bugzilla-noreply@FreeBSD.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 92C03D70 for ; Sun, 19 Feb 2017 21:00:43 +0000 (UTC) (envelope-from bugzilla-noreply@FreeBSD.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id v1JL01im054691 for ; Sun, 19 Feb 2017 21:00:43 GMT (envelope-from bugzilla-noreply@FreeBSD.org) Message-Id: <201702192100.v1JL01im054691@kenobi.freebsd.org> From: bugzilla-noreply@FreeBSD.org To: freebsd-usb@FreeBSD.org Subject: Problem reports for freebsd-usb@FreeBSD.org that need special attention Date: Sun, 19 Feb 2017 21:00:43 +0000 X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 19 Feb 2017 21:00:43 -0000 To view an individual PR, use: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=(Bug Id). The following is a listing of current problems submitted by FreeBSD users, which need special attention. These represent problem reports covering all versions including experimental development code and obsolete releases. Status | Bug Id | Description ------------+-----------+--------------------------------------------------- Open | 213877 | xhci reset causes panic on SuperMicro A1SRi-2758F 1 problems total for which you should take action. From owner-freebsd-usb@freebsd.org Sat Feb 25 13:16:21 2017 Return-Path: Delivered-To: freebsd-usb@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id AC8A9CECD29 for ; Sat, 25 Feb 2017 13:16:21 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 9C47F87F for ; Sat, 25 Feb 2017 13:16:21 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id v1PDGLlY043490 for ; Sat, 25 Feb 2017 13:16:21 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-usb@FreeBSD.org Subject: [Bug 217353] FreeBSD beastie logo prevent boot on Supermicro X11-SSL-F Date: Sat, 25 Feb 2017 13:16:21 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: usb X-Bugzilla-Version: 11.0-STABLE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: ch.parvanov@gmail.com X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-usb@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_id short_desc product version rep_platform op_sys bug_status bug_severity priority component assigned_to reporter Message-ID: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 25 Feb 2017 13:16:21 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D217353 Bug ID: 217353 Summary: FreeBSD beastie logo prevent boot on Supermicro X11-SSL-F Product: Base System Version: 11.0-STABLE Hardware: amd64 OS: Any Status: New Severity: Affects Only Me Priority: --- Component: usb Assignee: freebsd-usb@FreeBSD.org Reporter: ch.parvanov@gmail.com Hello ,=20 I have server with Supermicro X11-SSL-F with latest BIOS motherboard and tr= ied to install FreeBSD 11.0-Stable from CD , the machine and the usb keyboard freeze when the beastie logo shows just before boot. After 2-3 restarts it managed to boot and install without a problem. After the restart and boot f= rom HDD , the problem appears again, i have to restart the machine 2-3 times an= d it boot normal, until next reboot.=20 This is happens again on flash drive with BSDRP 10.3 image . I managed to f= ix this when disable the beastie logo to show from loader.conf on both HDD (11= .0) and flash drive (10.3)=20 beastie_disable=3D"YES" After that BSDRP 10.3 and BSD 11.0 boot without any problems.=20 I tried everything from BIOS , but i dont think its a BIOS issue.=20 I think its something with USB initializations on boot or something else.=20 Cheers --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-usb@freebsd.org Sat Feb 25 13:19:46 2017 Return-Path: Delivered-To: freebsd-usb@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 7E5ECCECE38 for ; Sat, 25 Feb 2017 13:19:46 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 6DED18F6 for ; Sat, 25 Feb 2017 13:19:46 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id v1PDJkKL047586 for ; Sat, 25 Feb 2017 13:19:46 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-usb@FreeBSD.org Subject: [Bug 217353] FreeBSD beastie logo prevent boot on Supermicro X11-SSL-F Date: Sat, 25 Feb 2017 13:19:46 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: usb X-Bugzilla-Version: 11.0-STABLE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: ch.parvanov@gmail.com X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-usb@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 25 Feb 2017 13:19:46 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D217353 --- Comment #1 from ochko --- I can take screenshots on monday , if interested. --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-usb@freebsd.org Sat Feb 25 13:27:20 2017 Return-Path: Delivered-To: freebsd-usb@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 580ACCEC052 for ; Sat, 25 Feb 2017 13:27:20 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 3A2DDD7B for ; Sat, 25 Feb 2017 13:27:20 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id v1PDRJHo063870 for ; Sat, 25 Feb 2017 13:27:20 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-usb@FreeBSD.org Subject: [Bug 217353] FreeBSD beastie logo prevent boot on Supermicro X11-SSL-F Date: Sat, 25 Feb 2017 13:27:20 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: usb X-Bugzilla-Version: 11.0-STABLE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: smh@FreeBSD.org X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-usb@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: cc Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 25 Feb 2017 13:27:20 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D217353 Steven Hartland changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |smh@FreeBSD.org --- Comment #2 from Steven Hartland --- Its a shot in the dark but does hw.vga.textmode=3D"1" help at all? --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-usb@freebsd.org Sat Feb 25 13:54:34 2017 Return-Path: Delivered-To: freebsd-usb@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id BB22DCECC4A for ; Sat, 25 Feb 2017 13:54:34 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id AAE802BD for ; Sat, 25 Feb 2017 13:54:34 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id v1PDsYVv021471 for ; Sat, 25 Feb 2017 13:54:34 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-usb@FreeBSD.org Subject: [Bug 217353] FreeBSD beastie logo prevent boot on Supermicro X11-SSL-F Date: Sat, 25 Feb 2017 13:54:34 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: usb X-Bugzilla-Version: 11.0-STABLE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: ch.parvanov@gmail.com X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-usb@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 25 Feb 2017 13:54:34 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D217353 --- Comment #3 from ochko --- (In reply to Steven Hartland from comment #2) I can test this on monday at work and will report. --=20 You are receiving this mail because: You are the assignee for the bug.=