Re: pciconf -l doesn't show any devices on Hyper-V VM

Gen1 or Gen2? On Gen2 Hyper-V, there is _no_ pcib0 and pci0 at all; unless you uses pci-e pass-through or SR-IOV. Why do you care about the existence of pci bus? On Thu, May 24, 2018 at 9:33 AM, Yuri Pankov wrote: > Hi, > > Running FreeBSD-12.0-CURRENT-amd64-20180514-r333606

Where should I put devd related scripts?

Hi all, Where should I put devd related scripts? Thanks, sephe -- Tomorrow Will Never Die ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to

Re: Add support for ACPI Module Device ACPI0004?

On Tue, May 2, 2017 at 11:28 AM, Sepherosa Ziehau <sepher...@gmail.com> wrote: > On Tue, May 2, 2017 at 12:25 AM, John Baldwin <j...@freebsd.org> wrote: >> On Sunday, April 30, 2017 09:02:30 AM Sepherosa Ziehau wrote: >>> On Sat, Apr 29, 2017 at 12:01 AM, John Ba

Re: Add support for ACPI Module Device ACPI0004?

On Tue, May 2, 2017 at 12:25 AM, John Baldwin <j...@freebsd.org> wrote: > On Sunday, April 30, 2017 09:02:30 AM Sepherosa Ziehau wrote: >> On Sat, Apr 29, 2017 at 12:01 AM, John Baldwin <j...@freebsd.org> wrote: >> > On Friday, April 28, 2017 05:38:32 PM Sepherosa Z

Re: Add support for ACPI Module Device ACPI0004?

On Sat, Apr 29, 2017 at 12:01 AM, John Baldwin <j...@freebsd.org> wrote: > On Friday, April 28, 2017 05:38:32 PM Sepherosa Ziehau wrote: >> On Thu, Apr 27, 2017 at 12:14 AM, John Baldwin <j...@freebsd.org> wrote: >> > On Wednesday, April 26, 2017 09:18:48 AM Sepher

Re: Add support for ACPI Module Device ACPI0004?

On Thu, Apr 27, 2017 at 12:14 AM, John Baldwin <j...@freebsd.org> wrote: > On Wednesday, April 26, 2017 09:18:48 AM Sepherosa Ziehau wrote: >> On Wed, Apr 26, 2017 at 4:36 AM, John Baldwin <j...@freebsd.org> wrote: >> > On Thursday, April 20, 2017 02:29:30 AM Dexuan

Re: Add support for ACPI Module Device ACPI0004?

On Wed, Apr 26, 2017 at 4:36 AM, John Baldwin wrote: > On Thursday, April 20, 2017 02:29:30 AM Dexuan Cui wrote: >> > From: John Baldwin [mailto:j...@freebsd.org] >> > Sent: Thursday, April 20, 2017 02:34 >> > > Can we add the support of "ACPI0004" with the below one-line

Re: Please test EARLY_AP_STARTUP

On Fri, Dec 2, 2016 at 12:53 PM, Sepherosa Ziehau <sepher...@gmail.com> wrote: > On Fri, Dec 2, 2016 at 1:49 AM, John Baldwin <j...@freebsd.org> wrote: >> On Thursday, December 01, 2016 01:53:29 PM Sepherosa Ziehau wrote: >>> On Wed, Nov 30, 2016 at 9:59 AM, Sephero

Re: Please test EARLY_AP_STARTUP

On Fri, Dec 2, 2016 at 1:49 AM, John Baldwin <j...@freebsd.org> wrote: > On Thursday, December 01, 2016 01:53:29 PM Sepherosa Ziehau wrote: >> On Wed, Nov 30, 2016 at 9:59 AM, Sepherosa Ziehau <sepher...@gmail.com> >> wrote: >> >>> After fdc is disa

Re: Please test EARLY_AP_STARTUP

On Wed, Nov 30, 2016 at 9:59 AM, Sepherosa Ziehau <sepher...@gmail.com> wrote: > On Tue, Nov 29, 2016 at 2:27 AM, John Baldwin <j...@freebsd.org> wrote: >> On Monday, November 28, 2016 02:35:07 PM Sepherosa Ziehau wrote: >>> Hi John, >>> >>>

Re: Please test EARLY_AP_STARTUP

On Tue, Nov 29, 2016 at 2:27 AM, John Baldwin <j...@freebsd.org> wrote: > On Monday, November 28, 2016 02:35:07 PM Sepherosa Ziehau wrote: >> Hi John, >> >> fdc seems to cause panic on Hyper-V: >> https://people.freebsd.org/~sephe/fdc_panic.png > > You should

Re: Please test EARLY_AP_STARTUP

Hi John, fdc seems to cause panic on Hyper-V: https://people.freebsd.org/~sephe/fdc_panic.png I then commented out device fdc, and I fixed one panic on Hyper-V here: https://reviews.freebsd.org/D8656 After fdc is disabled and hyperv/storvsc is fixed, it seems to boot fine, except a long delay

Re: (boost::)asio and kqueue problem

On Wed, Jul 20, 2016 at 12:38 PM, Konstantin Belousov wrote: > On Tue, Jul 19, 2016 at 05:35:59PM +0200, Hartmut Brandt wrote: >> Hi, >> >> I'm trying to use asio (that's boost::asio without boost) to handle >> listening sockets asynchronuosly. This appears not to work. There

Re: FreeBSD-11.0-BETA1-amd64-disc1.iso is too big for my 700MB CD-r

On Fri, Jul 15, 2016 at 7:13 AM, Glen Barber wrote: > With additional tweaks, I was able to get the CD to boot both with > a real internal CD-ROM drive, as well as USB CD-ROM. > > I have uploaded a disc1.iso image here: > > https://people.freebsd.org/~gjb/disc1_uzip.iso > >

Re: FreeBSD_HEAD_i386 - Build #2847 - Still Failing

On Wed, Apr 13, 2016 at 8:46 PM, David Somayajulu wrote: > Hi All, > I would appreciate if you could let me know how to back off the following > commits. > > https://svnweb.freebsd.org/changeset/base/297916 > https://svnweb.freebsd.org/changeset/base/297909 >

Re: Revision 297176 - hyperv/evttimer: Use an independent message slot so that it can work

I have reverted this change. It will be brought back, after some code refactoring. On Fri, Apr 8, 2016 at 4:22 PM, wrote: > > Hello > > I recently update one of my many vms from an older CURRENT revision r297196 > to r297659 and on reboot it just panics with the

Re: [PATCH] SO_REUSEADDR and SO_REUSEPORT behaviour

On Tue, Dec 3, 2013 at 5:41 AM, Adrian Chadd adr...@freebsd.org wrote: On 2 December 2013 03:45, Sepherosa Ziehau sepher...@gmail.com wrote: On Mon, Dec 2, 2013 at 1:02 PM, Adrian Chadd adr...@freebsd.org wrote: Ok, so given this, how do you guarantee the UTHREAD stays on the given CPU

Re: [PATCH] SO_REUSEADDR and SO_REUSEPORT behaviour

. Well, for fragments of a UDP datagram, if the ports are taken into consideration the RSS hash will be different for leading fragment and rest of the fragments; I think that's why MS didn't include ports for UDP. Best Regards, sephe Thanks Oleg On Sun, Dec 1, 2013 at 8:17 PM, Sepherosa

Re: [PATCH] SO_REUSEADDR and SO_REUSEPORT behaviour

On Mon, Dec 2, 2013 at 1:02 PM, Adrian Chadd adr...@freebsd.org wrote: Hi! Thanks for the writeup! On 1 December 2013 20:17, Sepherosa Ziehau sepher...@gmail.com wrote: I also put up a brief description of SO_REUSEPORT in dfly; may be useful to you: http://leaf.dragonflybsd.org/~sephe

Re: [PATCH] SO_REUSEADDR and SO_REUSEPORT behaviour

On Sat, Nov 30, 2013 at 2:42 AM, Ermal Luçi e...@freebsd.org wrote: Well seems Dragonfly has some version of it already from commit [1]. The distribution algorithm was changed a little bit after initial commit to gain more idle time (bnx(4) output has already been maxed out):