From owner-freebsd-current@freebsd.org Sun Sep 13 05:51:20 2015 Return-Path: Delivered-To: freebsd-current@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 CA582A01462 for ; Sun, 13 Sep 2015 05:51:20 +0000 (UTC) (envelope-from melifaro@ipfw.ru) Received: from forward20p.cmail.yandex.net (forward20p.cmail.yandex.net [IPv6:2a02:6b8:0:1465::a9]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "forwards.mail.yandex.net", Issuer "Certum Level IV CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 800C91AE9; Sun, 13 Sep 2015 05:51:20 +0000 (UTC) (envelope-from melifaro@ipfw.ru) Received: from web28g.yandex.ru (web28g.yandex.ru [IPv6:2a02:6b8:0:1402::38]) by forward20p.cmail.yandex.net (Yandex) with ESMTP id 97035219D0; Sun, 13 Sep 2015 08:51:16 +0300 (MSK) Received: from 127.0.0.1 (localhost [127.0.0.1]) by web28g.yandex.ru (Yandex) with ESMTP id C7FD97A1417; Sun, 13 Sep 2015 08:51:15 +0300 (MSK) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ipfw.ru; s=mail; t=1442123476; bh=wixhAUq2YHAc1BGwOKoLvokRHLg6hp5nF15FxMSXwSk=; h=From:To:Cc:In-Reply-To:References:Subject:Date; b=eDo2yQv9DqtwMy+0u1e/ceDquDG72Yhkmbg99vr/d6ZK2MdlhAdQ5y/SAqGTx7FdP Jv4lmgMzecLyqji7Hk0eaNimAdNrVcnZDGFtLBm/RKQgdIHodTYQuzEex8gcdyp2dL iuY81Zb+QNlKTrZl6gSrGcr0Poc9eWDoa2A2a43s= Received: by web28g.yandex.ru with HTTP; Sun, 13 Sep 2015 08:51:14 +0300 From: Alexander V. Chernikov To: hiren panchasara Cc: Hans Petter Selasky , "freebsd-current@FreeBSD.org" , "jch@FreeBSD.org" In-Reply-To: <20150912173041.GT64965@strugglingcoder.info> References: <20150910192351.GF64965@strugglingcoder.info> <55F27D68.6080501@selasky.org> <20150911232154.GS64965@strugglingcoder.info> <1405441442061150@web27j.yandex.ru> <20150912173041.GT64965@strugglingcoder.info> Subject: Re: Panic on kldload/kldunload in/near callout MIME-Version: 1.0 Message-Id: <3497621442123474@web28g.yandex.ru> X-Mailer: Yamail [ http://yandex.ru ] 5.0 Date: Sun, 13 Sep 2015 08:51:14 +0300 Content-Transfer-Encoding: 8bit Content-Type: text/plain; charset=koi8-r X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 13 Sep 2015 05:51:20 -0000 12.09.2015, 20:30, "hiren panchasara" : > On 09/12/15 at 03:32P, Alexander V. Chernikov wrote: >> š12.09.2015, 02:22, "hiren panchasara" : >> š> On 09/11/15 at 09:06P, Hans Petter Selasky wrote: > > [skip] >> š> I'll try to get it. Meanwhile I am getting another panic on idle box: >> š> http://pastebin.com/9qJTFMik >> šThe easiest explanation could be lack of lla_create() result check, fixed in r286945. >> šThis panic is triggered by fast interface down-up (or just up), when ARP packet is received but there are no (matching) IPv4 prefix on the interface. >> šIf this is not the case (e.g. it paniced w/o any interface changes and there were no other subnets in given L2 segment) I'd be happy to debug this further. > > Just hit another last night. (Box goes to db> ; let me know if you want > to debug anything when that happens.) Would you mind showing full backtrace for that core? (e.g. situation has to be different for newer -current). > I am sure there were no interface changes on the box and it was sitting > idle. (Unsure of the other subnets part.) And I am on 3 days old -head > so I already have r286945. I disabled IPv6 on the box just to eliminate > that but panic still happens. > > Cheers, > Hiren From owner-freebsd-current@freebsd.org Sun Sep 13 08:29:14 2015 Return-Path: Delivered-To: freebsd-current@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 84FA6A02AF2 for ; Sun, 13 Sep 2015 08:29:14 +0000 (UTC) (envelope-from 000.fbsd@quip.cz) Received: from elsa.codelab.cz (elsa.codelab.cz [94.124.105.4]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 43A7F1A2F; Sun, 13 Sep 2015 08:29:13 +0000 (UTC) (envelope-from 000.fbsd@quip.cz) Received: from elsa.codelab.cz (localhost [127.0.0.1]) by elsa.codelab.cz (Postfix) with ESMTP id A24B028460; Sun, 13 Sep 2015 10:23:02 +0200 (CEST) Received: from illbsd.quip.test (ip-89-177-49-111.net.upcbroadband.cz [89.177.49.111]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by elsa.codelab.cz (Postfix) with ESMTPSA id 90D3528412; Sun, 13 Sep 2015 10:23:01 +0200 (CEST) Message-ID: <55F53265.8040905@quip.cz> Date: Sun, 13 Sep 2015 10:23:01 +0200 From: Miroslav Lachman <000.fbsd@quip.cz> User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:35.0) Gecko/20100101 Firefox/35.0 SeaMonkey/2.32 MIME-Version: 1.0 To: Mark Felder , "Bjoern A. Zeeb" CC: freebsd-current@freebsd.org Subject: Re: RCTL and VIMAGE for 11.0-RELEASE References: <1440443338.1828791.364761057.5F263CEC@webmail.messagingengine.com> <4EE0EEFA-EDAB-4A88-B959-458C1D89900F@FreeBSD.org> <1440444552.1833687.364780977.20044688@webmail.messagingengine.com> In-Reply-To: <1440444552.1833687.364780977.20044688@webmail.messagingengine.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 13 Sep 2015 08:29:14 -0000 Mark Felder wrote on 08/24/2015 21:29: > > > On Mon, Aug 24, 2015, at 14:18, Bjoern A. Zeeb wrote: >>> On 24 Aug 2015, at 19:08 , Mark Felder wrote: >>> >>> What is preventing RCTL from being enabled right now? Any known/serious >>> blockers? >> >> It’s enabled in GENERIC. If RCTL is in GENERIC, can somebody look on to this problem with swapuse? https://lists.freebsd.org/pipermail/freebsd-stable/2015-March/082019.html IMHO it shoul be fixed or better documented in man pages. Miroslav Lachman From owner-freebsd-current@freebsd.org Sun Sep 13 08:56:36 2015 Return-Path: Delivered-To: freebsd-current@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 2FD75A01C20 for ; Sun, 13 Sep 2015 08:56:36 +0000 (UTC) (envelope-from hiren@strugglingcoder.info) Received: from mail.strugglingcoder.info (strugglingcoder.info [65.19.130.35]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mail.strugglingcoder.info", Issuer "mail.strugglingcoder.info" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 17A5914E2; Sun, 13 Sep 2015 08:56:35 +0000 (UTC) (envelope-from hiren@strugglingcoder.info) Received: from localhost (unknown [10.1.1.3]) (Authenticated sender: hiren@strugglingcoder.info) by mail.strugglingcoder.info (Postfix) with ESMTPA id D939FC01E2; Sun, 13 Sep 2015 01:56:34 -0700 (PDT) Date: Sun, 13 Sep 2015 01:56:34 -0700 From: hiren panchasara To: "Alexander V. Chernikov" Cc: Hans Petter Selasky , "freebsd-current@FreeBSD.org" , "jch@FreeBSD.org" Subject: Re: Panic on kldload/kldunload in/near callout Message-ID: <20150913085634.GV64965@strugglingcoder.info> References: <20150910192351.GF64965@strugglingcoder.info> <55F27D68.6080501@selasky.org> <20150911232154.GS64965@strugglingcoder.info> <1405441442061150@web27j.yandex.ru> <20150912173041.GT64965@strugglingcoder.info> <3497621442123474@web28g.yandex.ru> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="NO4xtVTk6ycZDAf4" Content-Disposition: inline In-Reply-To: <3497621442123474@web28g.yandex.ru> User-Agent: Mutt/1.5.23 (2014-03-12) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 13 Sep 2015 08:56:36 -0000 --NO4xtVTk6ycZDAf4 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On 09/13/15 at 08:51P, Alexander V. Chernikov wrote: >=20 >=20 > 12.09.2015, 20:30, "hiren panchasara" : > > On 09/12/15 at 03:32P, Alexander V. Chernikov wrote: > >> ?12.09.2015, 02:22, "hiren panchasara" : > >> ?> On 09/11/15 at 09:06P, Hans Petter Selasky wrote: > > > > [skip] > >> ?> I'll try to get it. Meanwhile I am getting another panic on idle bo= x: > >> ?> http://pastebin.com/9qJTFMik > >> ?The easiest explanation could be lack of lla_create() result check, f= ixed in r286945. > >> ?This panic is triggered by fast interface down-up (or just up), when = ARP packet is received but there are no (matching) IPv4 prefix on the inter= face. > >> ?If this is not the case (e.g. it paniced w/o any interface changes an= d there were no other subnets in given L2 segment) I'd be happy to debug th= is further. > > > > Just hit another last night. (Box goes to db> ; let me know if you want > > to debug anything when that happens.) > Would you mind showing full backtrace for that core? (e.g. situation has = to be different for newer -current). Sure: Fatal trap 12: page fault while in kernel mode cpuid =3D 0; apic id =3D 00 fault virtual address =3D 0x20 fault code =3D supervisor write data, page not present instruction pointer =3D 0x20:0xffffffff80f214d6 stack pointer =3D 0x28:0xfffffe00003d0620 frame pointer =3D 0x28:0xfffffe00003d0630 code segment =3D base 0x0, limit 0xfffff, type 0x1b =3D DPL 0, pres 1, long 1, def32 0, gran 1 processor eflags =3D interrupt enabled, resume, IOPL =3D 0 current process =3D 12 (irq264: igb0:que 0) [ thread pid 12 tid 100035 ] Stopped at memcpy+0x16: repe movsb (%rsi),%es:(%rdi) db> bt full Symbol not found KDB: reentering KDB: stack backtrace: db_trace_self_wrapper() at db_trace_self_wrapper+43/frame 0xfffffe00003cff10 kdb_reenter() at kdb_reenter+51/frame 0xfffffe00003cff20 db_term() at db_term+136/frame 0xfffffe00003cff40 db_unary() at db_unary+116/frame 0xfffffe00003cff60 db_mult_expr() at db_mult_expr+27/frame 0xfffffe00003cffa0 db_add_expr() at db_add_expr+27/frame 0xfffffe00003cffe0 db_expression() at db_expression+29/frame 0xfffffe00003d0030 db_stack_trace() at db_stack_trace+48/frame 0xfffffe00003d0060 db_command() at db_command+865/frame 0xfffffe00003d0120 db_command_loop() at db_command_loop+100/frame 0xfffffe00003d0130 db_trap() at db_trap+219/frame 0xfffffe00003d01c0 kdb_trap() at kdb_trap+404/frame 0xfffffe00003d0250 trap_fatal() at trap_fatal+789/frame 0xfffffe00003d02b0 trap_pfault() at trap_pfault+806/frame 0xfffffe00003d0350 trap() at trap+1124/frame 0xfffffe00003d0560 calltrap() at calltrap+8/frame 0xfffffe00003d0560 --- trap 12, rip =3D 18446744071577933014, rsp =3D 18446741874690295344, rb= p =3D 18446741874690295344 --- memcpy() at memcpy+22/frame 0xfffffe00003d0630 arpintr() at arpintr+2951/frame 0xfffffe00003d0750 netisr_dispatch_src() at netisr_dispatch_src+97/frame 0xfffffe00003d07c0 ether_demux() at ether_demux+345/frame 0xfffffe00003d07f0 ether_nh_input() at ether_nh_input+888/frame 0xfffffe00003d0850 netisr_dispatch_src() at netisr_dispatch_src+97/frame 0xfffffe00003d08c0 ether_input() at ether_input+38/frame 0xfffffe00003d08e0 igb_rxeof() at igb_rxeof+1764/frame 0xfffffe00003d0990 igb_msix_que() at igb_msix_que+352/frame 0xfffffe00003d09e0 intr_event_execute_handlers() at intr_event_execute_handlers+474/frame 0xff= fffe00003d0a20 ithread_loop() at ithread_loop+166/frame 0xfffffe00003d0a70 fork_exit() at fork_exit+156/frame 0xfffffe00003d0ab0 fork_trampoline() at fork_trampoline+14/frame 0xfffffe00003d0ab0 --- trap 0, rip =3D 0, rsp =3D 0, rbp =3D 0 --- db>=20 Cheers, Hiren --NO4xtVTk6ycZDAf4 Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQF8BAABCgBmBQJV9To1XxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXRBNEUyMEZBMUQ4Nzg4RjNGMTdFNjZGMDI4 QjkyNTBFMTU2M0VERkU1AAoJEIuSUOFWPt/lZl4H+wceMc6LVNONJyAdyX+pRTBx DG/FwQgwXn7gGmanxeIEA0BttzaWV5trLRbv6ahDApXtHcEM4hpGeMa3TPq0uIJg tckmIUVA2qnSmsqEAnHWfgI5qEKUdhlFA3ydxnBVlVZkM5MVz5Ryc+rCavzAxS6N tR2jR7Lk6XRxcAuFZ3kN/eagSNvJcTN5j757CopTpZOLBz7BSzf6UC5Mwt2KkyW3 W9aiU36C27YX9AZKS6t0k4vHTQCt/vPj2Xk1s3fTBkuNqf5ysydo0vkD1s2feTw7 WPoOrizqYxUm+S7Q2NcYoYffvtdH0CbBgrNiaXb3pBKXLqbIvIYMu6I0gSOrBHk= =f7Yh -----END PGP SIGNATURE----- --NO4xtVTk6ycZDAf4-- From owner-freebsd-current@freebsd.org Sun Sep 13 11:06:21 2015 Return-Path: Delivered-To: freebsd-current@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 83458A011BC for ; Sun, 13 Sep 2015 11:06:21 +0000 (UTC) (envelope-from hiren@strugglingcoder.info) Received: from mail.strugglingcoder.info (strugglingcoder.info [65.19.130.35]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mail.strugglingcoder.info", Issuer "mail.strugglingcoder.info" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 6CEAC1CF6; Sun, 13 Sep 2015 11:06:21 +0000 (UTC) (envelope-from hiren@strugglingcoder.info) Received: from localhost (unknown [10.1.1.3]) (Authenticated sender: hiren@strugglingcoder.info) by mail.strugglingcoder.info (Postfix) with ESMTPA id 8933FC088D; Sun, 13 Sep 2015 04:06:20 -0700 (PDT) Date: Sun, 13 Sep 2015 04:06:20 -0700 From: hiren panchasara To: "Alexander V. Chernikov" Cc: Hans Petter Selasky , "freebsd-current@FreeBSD.org" , "jch@FreeBSD.org" Subject: Re: Panic on kldload/kldunload in/near callout Message-ID: <20150913110620.GX64965@strugglingcoder.info> References: <20150910192351.GF64965@strugglingcoder.info> <55F27D68.6080501@selasky.org> <20150911232154.GS64965@strugglingcoder.info> <1405441442061150@web27j.yandex.ru> <20150912173041.GT64965@strugglingcoder.info> <3497621442123474@web28g.yandex.ru> <20150913085634.GV64965@strugglingcoder.info> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="Tln/wzp9jsNjmSUr" Content-Disposition: inline In-Reply-To: <20150913085634.GV64965@strugglingcoder.info> User-Agent: Mutt/1.5.23 (2014-03-12) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 13 Sep 2015 11:06:21 -0000 --Tln/wzp9jsNjmSUr Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On 09/13/15 at 01:56P, hiren panchasara wrote: > On 09/13/15 at 08:51P, Alexander V. Chernikov wrote: > >=20 > >=20 > > 12.09.2015, 20:30, "hiren panchasara" : > > > On 09/12/15 at 03:32P, Alexander V. Chernikov wrote: > > >> ?12.09.2015, 02:22, "hiren panchasara" : > > >> ?> On 09/11/15 at 09:06P, Hans Petter Selasky wrote: > > > > > > [skip] > > >> ?> I'll try to get it. Meanwhile I am getting another panic on idle = box: > > >> ?> http://pastebin.com/9qJTFMik > > >> ?The easiest explanation could be lack of lla_create() result check,= fixed in r286945. > > >> ?This panic is triggered by fast interface down-up (or just up), whe= n ARP packet is received but there are no (matching) IPv4 prefix on the int= erface. > > >> ?If this is not the case (e.g. it paniced w/o any interface changes = and there were no other subnets in given L2 segment) I'd be happy to debug = this further. > > > > > > Just hit another last night. (Box goes to db> ; let me know if you wa= nt > > > to debug anything when that happens.) > > Would you mind showing full backtrace for that core? (e.g. situation ha= s to be different for newer -current). Apparently I was using an older current than r286945. :-( Apologies for the false alarm. I'll update again if I see any issues. Hiren --Tln/wzp9jsNjmSUr Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQF8BAABCgBmBQJV9VioXxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXRBNEUyMEZBMUQ4Nzg4RjNGMTdFNjZGMDI4 QjkyNTBFMTU2M0VERkU1AAoJEIuSUOFWPt/latkH/RWC2FPkxT1fCkbw1yc4f5Mi K4/pCBOcsllRTI6LOEiJqiP/U6hgDsV1yD2HlvXSZoKdlJHdVyDIUZUKhJmZeTp3 gWIUKxGVobcZYfhKXb4uKG4FW/UDIQ3aqp8ea9EqPBkGxVJsB0JscaWJRdCuokTH ZV/8ce4PzfbpT8VfD0EPxyErB5FvQpoXbGuAoP8lKo8KIfO4vYj0Yk5dITpju6fh NcegReNmc3/lFmefi9DRStQx75R39gOWop3iavRKH1aoeGCi26cY00+FGYnukXoZ ldJevx9DrO9n10rU59Mifh9zjrOuOdAHtUuNTChvYa5p+eRYfx74I7G8tUIxJcI= =4gKE -----END PGP SIGNATURE----- --Tln/wzp9jsNjmSUr-- From owner-freebsd-current@freebsd.org Sun Sep 13 13:23:38 2015 Return-Path: Delivered-To: freebsd-current@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 79CB6A03508 for ; Sun, 13 Sep 2015 13:23:38 +0000 (UTC) (envelope-from melifaro@ipfw.ru) Received: from forward13.mail.yandex.net (forward13.mail.yandex.net [IPv6:2a02:6b8:0:801::3]) by mx1.freebsd.org (Postfix) with ESMTP id 38BFF163D for ; Sun, 13 Sep 2015 13:23:38 +0000 (UTC) (envelope-from melifaro@ipfw.ru) Received: from web6j.yandex.ru (web6j.yandex.ru [IPv6:2a02:6b8:0:1619::306]) by forward13.mail.yandex.net (Yandex) with ESMTP id 751C0140080 for ; Sun, 13 Sep 2015 16:23:24 +0300 (MSK) Received: from 127.0.0.1 (localhost [127.0.0.1]) by web6j.yandex.ru (Yandex) with ESMTP id D967137006E6; Sun, 13 Sep 2015 16:23:23 +0300 (MSK) Received: by web6j.yandex.ru with HTTP; Sun, 13 Sep 2015 16:23:23 +0300 From: Alexander V. Chernikov Envelope-From: melifaro@ipfw.ru To: FreeBSD CURRENT Subject: kernel dtrace and current MIME-Version: 1.0 Message-Id: <738721442150603@web6j.yandex.ru> X-Mailer: Yamail [ http://yandex.ru ] 5.0 Date: Sun, 13 Sep 2015 16:23:23 +0300 Content-Transfer-Encoding: 7bit Content-Type: text/plain X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 13 Sep 2015 13:23:38 -0000 Hello all, I keep running in "dtrace: failed to compile script: "/usr/lib/dtrace/psinfo.d", line 39: failed to copy type of 'pr_uid': Type information is in parent and unavailable" message more and more often while trying to trace different -current kernels. Typically the reason besides that is the number of types embedded in kernel CTF: ctfdump -S /boot/kernel/kernel | awk '$0~/of types/{print$6}' 37160 We are bound to 32k of types by CTF format (and numbers above 32k (e.g.w/ highest bit set) are considered "child" types with the information stored in "parent"). ctfmerge ignores this fact and instead of yelling emits type indices above 32k. On the other hand, libctf sees such indices while parsing sections and since there is no "parent" for kernel, it emits the error above and stops. Thankfully, r287234 really improved the situation for ctfmerge, but there are still several thousands of identical structures and the total number is close to 32k. Personally I solved this by removing unneeded devices from GENERIC-inherited configs. I wonder, however if this can be handled better. E.g. either show better error in dtrace(1) or make ctfmerge fail causing kernel build to stop (since we asked for dtrace but in reality it wouldn't work), or remove some stale devices from GENERIC, or .something totally different? From owner-freebsd-current@freebsd.org Sun Sep 13 13:25:58 2015 Return-Path: Delivered-To: freebsd-current@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 66FA1A036AE for ; Sun, 13 Sep 2015 13:25:58 +0000 (UTC) (envelope-from wblock@wonkity.com) Received: from wonkity.com (wonkity.com [67.158.26.137]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "wonkity.com", Issuer "wonkity.com" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 0C254193A; Sun, 13 Sep 2015 13:25:57 +0000 (UTC) (envelope-from wblock@wonkity.com) Received: from wonkity.com (localhost [127.0.0.1]) by wonkity.com (8.15.2/8.15.2) with ESMTPS id t8DDPt6x048349 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Sun, 13 Sep 2015 07:25:56 -0600 (MDT) (envelope-from wblock@wonkity.com) Received: from localhost (wblock@localhost) by wonkity.com (8.15.2/8.15.2/Submit) with ESMTP id t8DDPtQI048345; Sun, 13 Sep 2015 07:25:55 -0600 (MDT) (envelope-from wblock@wonkity.com) Date: Sun, 13 Sep 2015 07:25:55 -0600 (MDT) From: Warren Block To: Mark R V Murray cc: Sean Bruno , freebsd-current@freebsd.org Subject: Re: em broken on current amd64 In-Reply-To: <2B045997-23A9-4B83-B34B-B9E4C06EF2C5@FreeBSD.org> Message-ID: References: <1B3BC636-6765-4478-AAE0-122E6904276E@pozo.com> <70759B1C-6685-4EF9-BC65-52590ABD398E@gmail.com> <63EACBE5-F82A-47D9-BA9A-E95D0E6AE80D@FreeBSD.org> <55EE2153.1050704@freebsd.org> <55EF0B39.30507@freebsd.org> <5CEDDA5F-7858-4A7D-BB45-CB902F53A83B@FreeBSD.org> <2B045997-23A9-4B83-B34B-B9E4C06EF2C5@FreeBSD.org> User-Agent: Alpine 2.20 (BSF 67 2015-01-07) MIME-Version: 1.0 Content-ID: X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.4.3 (wonkity.com [127.0.0.1]); Sun, 13 Sep 2015 07:25:56 -0600 (MDT) Content-Type: text/plain; CHARSET=ISO-8859-7; format=flowed Content-Transfer-Encoding: 8BIT X-Content-Filtered-By: Mailman/MimeDel 2.1.20 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 13 Sep 2015 13:25:58 -0000 On Sat, 12 Sep 2015, Mark R V Murray wrote: > I just caught this, on today˘s build: > > em0: Watchdog timeout Queue[0]-- resetting > Interface is RUNNING and ACTIVE > em0: TX Queue 0 ------ > em0: hw tdh = 127, hw tdt = 139 > em0: Tx Queue Status = -2147483648 > em0: TX descriptors avail = 1012 > em0: Tx Descriptors avail failure = 0 > em0: RX Queue 0 ------ > em0: hw rdh = 0, hw rdt = 1023 > em0: RX discarded packets = 0 > em0: RX Next to Check = 0 > em0: RX Next to Refresh = 1023 > > [graveyard] /usr/ports 09:42 pm # uname -a > FreeBSD graveyard.grondar.org 11.0-CURRENT FreeBSD 11.0-CURRENT #0 r287705: Sat Sep 12 15:07:54 BST 2015 root@graveyard.grondar.org:/b/obj/usr/src/sys/G_AMD64_GATE amd64 That happened on an amd64 10-STABLE (r287148) system here a couple of days ago. Both I217-V and 82574L cards in that system, but I did not save the message and can't say which had the error. Never seen before, has not happened again. From owner-freebsd-current@freebsd.org Sun Sep 13 15:17:15 2015 Return-Path: Delivered-To: freebsd-current@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 5A960A0315D for ; Sun, 13 Sep 2015 15:17:15 +0000 (UTC) (envelope-from dmilith@gmail.com) Received: from mail-wi0-x22b.google.com (mail-wi0-x22b.google.com [IPv6:2a00:1450:400c:c05::22b]) (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 E6A071519 for ; Sun, 13 Sep 2015 15:17:14 +0000 (UTC) (envelope-from dmilith@gmail.com) Received: by wicgb1 with SMTP id gb1so112421952wic.1 for ; Sun, 13 Sep 2015 08:17:13 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=from:content-type:subject:date:message-id:to:mime-version; bh=9XRuCX44jjrVg4Mjt8J6gfVEMVCPN+UeC5kKe538zDU=; b=Ew+/Y20EurCVaWlKQHdo2Kheq4CZ8sfxctMr3+6LGKb2d+mRR7IPDjDjbbZy9b7i+4 xAvcEcflEOFo+e1Q/lFzdwRtUMYDTWTgBBb7air3amEjOrO8z1EAMf6ljHJxZS8B5f4a F5xmKKS38SeaHSvjDJCkGFFf+Q6uE0IvBmenvlsGKmlj2M2bZp5bWV/UcHAGfRkex+Vm RsOxHaQg+0PKCvdRuBddMwUCGmTc1puUZPyn+oxrXN8MjBLPTVcBpGv2DOyJqFjStwQX miFt7XtWZPXlI2UvrPW85EKwUkItSPLjmXtK9qPy3AG3SRLIqxey7vAhN5k5SHoXYYQW R14g== X-Received: by 10.180.103.2 with SMTP id fs2mr13736526wib.9.1442157433063; Sun, 13 Sep 2015 08:17:13 -0700 (PDT) Received: from [192.168.1.2] ([46.29.147.192]) by smtp.gmail.com with ESMTPSA id xt1sm7737143wjb.32.2015.09.13.08.17.12 for (version=TLS1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sun, 13 Sep 2015 08:17:12 -0700 (PDT) From: Daniel Dettlaff X-Pgp-Agent: GPGMail 2.5.1 Content-Type: multipart/signed; boundary="Apple-Mail=_D1D5FF49-2054-41D2-B4A6-B19BCF7F58C8"; protocol="application/pgp-signature"; micalg=pgp-sha1 Subject: Kernel panic with my kernel config. Applies to 9.x up to 10.2 Date: Sun, 13 Sep 2015 17:17:03 +0200 Message-Id: <627CBC76-626D-4CF1-AC07-666F832034DE@gmail.com> To: freebsd-current@freebsd.org Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2104\)) X-Mailer: Apple Mail (2.2104) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 13 Sep 2015 15:17:15 -0000 --Apple-Mail=_D1D5FF49-2054-41D2-B4A6-B19BCF7F58C8 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=utf-8 Hi, I have custom kernel config: = https://gist.github.com/dmilith/234b3e6b65b6fa606e27 If I uncomment VIMAGE and epair from lines 10-11, each time I try to = launch any jail with vnet it panics the kernel. (also HBSD options might = be omited - they change nothing in this case, panics happened also = without HBSD patches on vanilla FreeBSD). Basically it=E2=80=99s 100% reproductible on all my testing hosts, and = applies from 9.x to latest 10.2 (didn=E2=80=99t check 11.0 yet). I hope it helps someone track VIMAGE/epair bugs! best regards Daniel (dmilith) Dettlaff --Apple-Mail=_D1D5FF49-2054-41D2-B4A6-B19BCF7F58C8 Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename=signature.asc Content-Type: application/pgp-signature; name=signature.asc Content-Description: Message signed with OpenPGP using GPGMail -----BEGIN PGP SIGNATURE----- Comment: GPGTools - http://gpgtools.org iEYEARECAAYFAlX1k3YACgkQgTgvVY+WpZofagCfR936UVuJnIpS+0eettwrdKbX 6dIAoNnwbG7PeED88DgYqTZHtQtm2vYx =AIcy -----END PGP SIGNATURE----- --Apple-Mail=_D1D5FF49-2054-41D2-B4A6-B19BCF7F58C8-- From owner-freebsd-current@freebsd.org Sun Sep 13 15:45:09 2015 Return-Path: Delivered-To: freebsd-current@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 7A7CFA03E91 for ; Sun, 13 Sep 2015 15:45:09 +0000 (UTC) (envelope-from sbruno@freebsd.org) Received: from mail.ignoranthack.me (ignoranthack.me [199.102.79.106]) (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 5B92611BA; Sun, 13 Sep 2015 15:45:08 +0000 (UTC) (envelope-from sbruno@freebsd.org) Received: from [10.40.2.8] (unknown [207.59.237.130]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) (Authenticated sender: sbruno@ignoranthack.me) by mail.ignoranthack.me (Postfix) with ESMTPSA id B0223193E6A; Sun, 13 Sep 2015 15:45:01 +0000 (UTC) Subject: Re: em broken on current amd64 To: Mark R V Murray References: <1B3BC636-6765-4478-AAE0-122E6904276E@pozo.com> <70759B1C-6685-4EF9-BC65-52590ABD398E@gmail.com> <63EACBE5-F82A-47D9-BA9A-E95D0E6AE80D@FreeBSD.org> <55EE2153.1050704@freebsd.org> <55EF0B39.30507@freebsd.org> <5CEDDA5F-7858-4A7D-BB45-CB902F53A83B@FreeBSD.org> <2B045997-23A9-4B83-B34B-B9E4C06EF2C5@FreeBSD.org> Cc: freebsd-current@freebsd.org From: Sean Bruno Message-ID: <55F599FD.9090903@freebsd.org> Date: Sun, 13 Sep 2015 08:45:01 -0700 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:38.0) Gecko/20100101 Thunderbird/38.2.0 MIME-Version: 1.0 In-Reply-To: <2B045997-23A9-4B83-B34B-B9E4C06EF2C5@FreeBSD.org> Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 13 Sep 2015 15:45:09 -0000 On 09/12/15 13:45, Mark R V Murray wrote: > >> On 8 Sep 2015, at 19:02, Mark R V Murray wrote: >> >> >>> On 8 Sep 2015, at 17:22, Sean Bruno wrote: >>> >>> >>>>>> >>>>>> I’m also seeing breakage with the em0 device; this isn’t a kernel >>>>>> hang, it is a failure to move data after about 10-15 minutes. The >>>>>> symptom is that my WAN ethernet no longer moves traffic, no pings, >>>>>> nothing. Booting looks normal: >>>>>> >>>>>> em0: port >>>>>> 0x30c0-0x30df mem 0x50300000-0x5031ffff,0x50324000-0x50324fff irq >>>>>> 20 at device 25.0 on pci0 em0: Using an MSI interrupt em0: Ethernet >>>>>> address: 00:16:76:d3:e1:5b em0: netmap queues/slots: TX 1/1024, RX >>>>>> 1/1024 >>>>>> >>>>>> Fixing it is as easy as … >>>>>> >>>>>> # ifconfig em0 down ; service ipfw restart ; ifconfig em0 up >>>>>> >>>>>> :-) >>>>>> >>>>>> I’m running CURRENT, r287538. This last worked of me a month or so >>>>>> ago at my previous build. >>>>>> >>>>>> M >>>>>> >>>>> >>>>> >>>>> Just so I'm clear, the original problem reported was a failure to >>>>> attach (you were among several folks reporting breakage). Is that fixed >>>>> ? >>>> >>>> I did not report the failure to attach, and I am not seeing it as I don’t >>>> think I built a kernel that had that particular failure. I am having the >>>> “failure after 10-15 minutes” problem; this is on an em0 device. >>>> >>>> M >>>> >>> >>> >>> Hrm, that's odd. That sounds like a hole where interrupts aren't being >>> reset for "reasons" that I cannot fathom. >>> >>> What hardware (pciconf -lv) does your system actually have? The em(4) >>> driver doesn't identify components which is frustrating. >> >> pciconf -lv output below: >> >> hostb0@pci0:0:0:0: class=0x060000 card=0x514d8086 chip=0x29a08086 rev=0x02 hdr=0x00 >> vendor = 'Intel Corporation' >> device = '82P965/G965 Memory Controller Hub' >> class = bridge >> subclass = HOST-PCI > > I just caught this, on today’s build: > > em0: Watchdog timeout Queue[0]-- resetting > Interface is RUNNING and ACTIVE > em0: TX Queue 0 ------ > em0: hw tdh = 127, hw tdt = 139 > em0: Tx Queue Status = -2147483648 > em0: TX descriptors avail = 1012 > em0: Tx Descriptors avail failure = 0 > em0: RX Queue 0 ------ > em0: hw rdh = 0, hw rdt = 1023 > em0: RX discarded packets = 0 > em0: RX Next to Check = 0 > em0: RX Next to Refresh = 1023 > > [graveyard] /usr/ports 09:42 pm # uname -a > FreeBSD graveyard.grondar.org 11.0-CURRENT FreeBSD 11.0-CURRENT #0 r287705: Sat Sep 12 15:07:54 BST 2015 root@graveyard.grondar.org:/b/obj/usr/src/sys/G_AMD64_GATE amd64 > > M > Any chance you can turn TSO off if its on and see what your results are? sean From owner-freebsd-current@freebsd.org Sun Sep 13 15:59:09 2015 Return-Path: Delivered-To: freebsd-current@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 51B1EA0364A for ; Sun, 13 Sep 2015 15:59:09 +0000 (UTC) (envelope-from markm@FreeBSD.org) Received: from gromit.grondar.org (grandfather.grondar.org [IPv6:2a01:348:0:15:5d59:5c20:0:2]) (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 1A2361AF6; Sun, 13 Sep 2015 15:59:09 +0000 (UTC) (envelope-from markm@FreeBSD.org) Received: from graveyard.grondar.org ([88.96.155.33] helo=gronkulator.grondar.org) by gromit.grondar.org with esmtpsa (TLSv1:ECDHE-RSA-AES256-SHA:256) (Exim 4.86 (FreeBSD)) (envelope-from ) id 1Zb9gH-000IS1-Uq; Sun, 13 Sep 2015 16:59:06 +0100 Subject: Re: em broken on current amd64 Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2104\)) Content-Type: text/plain; charset=us-ascii From: Mark R V Murray In-Reply-To: <55F599FD.9090903@freebsd.org> Date: Sun, 13 Sep 2015 16:59:05 +0100 Cc: freebsd-current@freebsd.org Content-Transfer-Encoding: 7bit Message-Id: References: <1B3BC636-6765-4478-AAE0-122E6904276E@pozo.com> <70759B1C-6685-4EF9-BC65-52590ABD398E@gmail.com> <63EACBE5-F82A-47D9-BA9A-E95D0E6AE80D@FreeBSD.org> <55EE2153.1050704@freebsd.org> <55EF0B39.30507@freebsd.org> <5CEDDA5F-7858-4A7D-BB45-CB902F53A83B@FreeBSD.org> <2B045997-23A9-4B83-B34B-B9E4C06EF2C5@FreeBSD.org> <55F599FD.9090903@freebsd.org> To: Sean Bruno X-Mailer: Apple Mail (2.2104) X-SA-Score: -1.0 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 13 Sep 2015 15:59:09 -0000 > On 13 Sep 2015, at 16:45, Sean Bruno wrote: > Any chance you can turn TSO off if its on and see what your results are? Only TSO4 was on. I turned it off; no difference. M -- Mark R V Murray From owner-freebsd-current@freebsd.org Sun Sep 13 20:54:21 2015 Return-Path: Delivered-To: freebsd-current@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 B071BA03D71 for ; Sun, 13 Sep 2015 20:54:21 +0000 (UTC) (envelope-from markjdb@gmail.com) Received: from mail-pa0-x233.google.com (mail-pa0-x233.google.com [IPv6:2607:f8b0:400e:c03::233]) (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 83E431CA9; Sun, 13 Sep 2015 20:54:21 +0000 (UTC) (envelope-from markjdb@gmail.com) Received: by padhk3 with SMTP id hk3so122706333pad.3; Sun, 13 Sep 2015 13:54:21 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=sender:date:from:to:cc:subject:message-id:references:mime-version :content-type:content-disposition:in-reply-to:user-agent; bh=QYLtVL7i0kXyMtfGgBK7NbVGFKsqHmVzIaTMO8ykPAc=; b=kWcDqQgLmHaJkgZOhBblc/Ekcl3YiYfDDqqUqXtmZr35x9WYVA1iCLHH4HHDzs6G7r RCxNFPS39hezwT17vFKgN+TT1T933EmGHzsY0rP58OMMvW5p+DIPFbl1GluTC//Ncz7e C+w5DKKOfPLmH+SIBeDt4ugv2/jnrHh4iCfBQGBu7VcwV8Um99p6EFnCHAebAJpg+oxY FEqRricmb5X8CPurZkt+bOACcuXkgbxz6BeD5LT+UwiAudBgD6IiQKQyvYIkshIzakvk gvbDkFlnHxX3XehMrIWorltXmfoKADnzJZaVcjke4qJ7zObT7nBGkcAdW8i80aoxymWb xyQA== X-Received: by 10.67.12.166 with SMTP id er6mr26199074pad.40.1442177660987; Sun, 13 Sep 2015 13:54:20 -0700 (PDT) Received: from muskytusk ([104.236.250.12]) by smtp.gmail.com with ESMTPSA id lc9sm11909249pbc.52.2015.09.13.13.54.19 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sun, 13 Sep 2015 13:54:19 -0700 (PDT) Sender: Mark Johnston Date: Sun, 13 Sep 2015 20:53:33 +0000 From: Mark Johnston To: "Alexander V. Chernikov" Cc: FreeBSD CURRENT Subject: Re: kernel dtrace and current Message-ID: <20150913205333.GA2444@muskytusk> References: <738721442150603@web6j.yandex.ru> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <738721442150603@web6j.yandex.ru> User-Agent: Mutt/1.5.23 (2014-03-12) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 13 Sep 2015 20:54:21 -0000 On Sun, Sep 13, 2015 at 04:23:23PM +0300, Alexander V. Chernikov wrote: > Hello all, > > I keep running in > "dtrace: failed to compile script: "/usr/lib/dtrace/psinfo.d", line 39: failed to copy type of 'pr_uid': Type information is in parent and unavailable" > message more and more often while trying to trace different -current kernels. > > Typically the reason besides that is the number of types embedded in kernel CTF: > ctfdump -S /boot/kernel/kernel | awk '$0~/of types/{print$6}' > 37160 > > We are bound to 32k of types by CTF format (and numbers above 32k (e.g.w/ highest bit set) are considered "child" types with the information stored in "parent"). > ctfmerge ignores this fact and instead of yelling emits type indices above 32k. On the other hand, libctf sees such indices while parsing sections and since there is no > "parent" for kernel, it emits the error above and stops. > > Thankfully, r287234 really improved the situation for ctfmerge, but there are still several thousands of identical structures and the total number is close to 32k. r281797 and r287234 should have fixed most instances of duplicate type definitions. At the moment, amd64 GENERIC and GENERIC-NODEBUG have roughly 25K types in their respective CTF containers; there is a small handful of duplicates, but at least some of them are legitimate (some pairs of drivers redefine the same types, e.g. aac(4)/aacraid(4) or mps(4)/mpr(4)). Could you post a config that results in the large number of duplicates you mention above? > > Personally I solved this by removing unneeded devices from GENERIC-inherited configs. > I wonder, however if this can be handled better. FWIW, removing old drivers from GENERIC would be straightforward if we could auto-load KLDs based on device IDs. > > E.g. either show better error in dtrace(1) or make ctfmerge fail causing kernel build to stop (since we asked for dtrace but in reality it wouldn't work), or remove some stale devices from GENERIC, or .something totally different? One more radical option is to extend the width of CTF type IDs. I've been holding off on doing this for a few reasons: - Doing so would change the binary format, making us incompatible with the reference CTF code in illumos. - Type IDs are embedded in quite a few places in the various CTF structures, so enlarging them from 16 bits to 32 bits will bloat CTF containers somewhat. - I was under the impression that r287234 addressed the problem sufficiently for now. If type ID space is still a problem post-r287234, I think it's time to just go ahead and change the format. But first I'd like to understand the cause of the duplication you're seeing. From owner-freebsd-current@freebsd.org Mon Sep 14 10:05:26 2015 Return-Path: Delivered-To: freebsd-current@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 CE088A03729 for ; Mon, 14 Sep 2015 10:05:26 +0000 (UTC) (envelope-from slw@zxy.spb.ru) Received: from zxy.spb.ru (zxy.spb.ru [195.70.199.98]) (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 8BDB01F18; Mon, 14 Sep 2015 10:05:26 +0000 (UTC) (envelope-from slw@zxy.spb.ru) Received: from slw by zxy.spb.ru with local (Exim 4.84 (FreeBSD)) (envelope-from ) id 1ZbQdW-000Fo5-V6; Mon, 14 Sep 2015 13:05:23 +0300 Date: Mon, 14 Sep 2015 13:05:22 +0300 From: Slawa Olhovchenkov To: Mark Johnston Cc: "Alexander V. Chernikov" , FreeBSD CURRENT Subject: Re: kernel dtrace and current Message-ID: <20150914100522.GS3158@zxy.spb.ru> References: <738721442150603@web6j.yandex.ru> <20150913205333.GA2444@muskytusk> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20150913205333.GA2444@muskytusk> User-Agent: Mutt/1.5.23 (2014-03-12) X-SA-Exim-Connect-IP: X-SA-Exim-Mail-From: slw@zxy.spb.ru X-SA-Exim-Scanned: No (on zxy.spb.ru); SAEximRunCond expanded to false X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 14 Sep 2015 10:05:26 -0000 On Sun, Sep 13, 2015 at 08:53:33PM +0000, Mark Johnston wrote: > On Sun, Sep 13, 2015 at 04:23:23PM +0300, Alexander V. Chernikov wrote: > > Hello all, > > > > I keep running in > > "dtrace: failed to compile script: "/usr/lib/dtrace/psinfo.d", line 39: failed to copy type of 'pr_uid': Type information is in parent and unavailable" > > message more and more often while trying to trace different -current kernels. > > > > Typically the reason besides that is the number of types embedded in kernel CTF: > > ctfdump -S /boot/kernel/kernel | awk '$0~/of types/{print$6}' > > 37160 > > > > We are bound to 32k of types by CTF format (and numbers above 32k (e.g.w/ highest bit set) are considered "child" types with the information stored in "parent"). > > ctfmerge ignores this fact and instead of yelling emits type indices above 32k. On the other hand, libctf sees such indices while parsing sections and since there is no > > "parent" for kernel, it emits the error above and stops. > > > > Thankfully, r287234 really improved the situation for ctfmerge, but there are still several thousands of identical structures and the total number is close to 32k. > > r281797 and r287234 should have fixed most instances of duplicate type > definitions. At the moment, amd64 GENERIC and GENERIC-NODEBUG have > roughly 25K types in their respective CTF containers; there is a small > handful of duplicates, but at least some of them are legitimate (some > pairs of drivers redefine the same types, e.g. aac(4)/aacraid(4) or > mps(4)/mpr(4)). > > Could you post a config that results in the large number of duplicates > you mention above? > > > > > Personally I solved this by removing unneeded devices from GENERIC-inherited configs. > > I wonder, however if this can be handled better. > > FWIW, removing old drivers from GENERIC would be straightforward if we > could auto-load KLDs based on device IDs. We can just unconditionaly load all current drivers from GENERIC as KLD. This is as good as ever. From owner-freebsd-current@freebsd.org Mon Sep 14 10:09:08 2015 Return-Path: Delivered-To: freebsd-current@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 E5950A0391E for ; Mon, 14 Sep 2015 10:09:07 +0000 (UTC) (envelope-from melifaro@ipfw.ru) Received: from forward5h.mail.yandex.net (forward5h.mail.yandex.net [IPv6:2a02:6b8:0:f05::5]) by mx1.freebsd.org (Postfix) with ESMTP id A32F810B4; Mon, 14 Sep 2015 10:09:07 +0000 (UTC) (envelope-from melifaro@ipfw.ru) Received: from web1h.yandex.ru (web1h.yandex.ru [IPv6:2a02:6b8:0:f05::11]) by forward5h.mail.yandex.net (Yandex) with ESMTP id 62EBED0063A; Mon, 14 Sep 2015 13:08:58 +0300 (MSK) Received: from 127.0.0.1 (localhost [127.0.0.1]) by web1h.yandex.ru (Yandex) with ESMTP id C34321CE2842; Mon, 14 Sep 2015 13:08:57 +0300 (MSK) Received: by web1h.yandex.ru with HTTP; Mon, 14 Sep 2015 13:08:56 +0300 From: Alexander V. Chernikov Envelope-From: melifaro@ipfw.ru To: Mark Johnston Cc: FreeBSD CURRENT In-Reply-To: <20150913205333.GA2444@muskytusk> References: <738721442150603@web6j.yandex.ru> <20150913205333.GA2444@muskytusk> Subject: Re: kernel dtrace and current MIME-Version: 1.0 Message-Id: <363291442225336@web1h.yandex.ru> X-Mailer: Yamail [ http://yandex.ru ] 5.0 Date: Mon, 14 Sep 2015 13:08:56 +0300 Content-Transfer-Encoding: 8bit Content-Type: text/plain; charset=koi8-r X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 14 Sep 2015 10:09:08 -0000 13.09.2015, 23:54, "Mark Johnston" : > On Sun, Sep 13, 2015 at 04:23:23PM +0300, Alexander V. Chernikov wrote: >> šHello all, >> >> šI keep running in >> š"dtrace: failed to compile script: "/usr/lib/dtrace/psinfo.d", line 39: failed to copy type of 'pr_uid': Type information is in parent and unavailable" >> šmessage more and more often while trying to trace different -current kernels. >> >> šTypically the reason besides that is the number of types embedded in kernel CTF: >> šctfdump -S /boot/kernel/kernel | awk '$0~/of types/{print$6}' >> š37160 >> >> šWe are bound to 32k of types by CTF format (and numbers above 32k (e.g.w/ highest bit set) are considered "child" types with the information stored in "parent"). >> šctfmerge ignores this fact and instead of yelling emits type indices above 32k. On the other hand, libctf sees such indices while parsing sections and since there is no >> š"parent" for kernel, it emits the error above and stops. >> >> šThankfully, r287234 really improved the situation for ctfmerge, but there are still several thousands of identical structures and the total number is close to 32k. > > r281797 and r287234 should have fixed most instances of duplicate type > definitions. At the moment, amd64 GENERIC and GENERIC-NODEBUG have > roughly 25K types in their respective CTF containers; there is a small > handful of duplicates, but at least some of them are legitimate (some > pairs of drivers redefine the same types, e.g. aac(4)/aacraid(4) or > mps(4)/mpr(4)). > > Could you post a config that results in the large number of duplicates > you mention above? I did clean buildworld/installworld w/ clean buildkernel and the situation is really much better now: I've got only 27633 types, with 493 duplicates, so it is not _that_ close. (So I suppose that for some reason I got old ctfmerge) My config for that kernel: include GENERIC nomakeoptions DEBUG makeoptions DEBUG="-O2 -gdwarf-2" options KTR options KTR_MASK=(0) options KDB_TRACE options KDB_UNATTENDED options BREAK_TO_DEBUGGER options ALT_BREAK_TO_DEBUGGER options MROUTING > >> šPersonally I solved this by removing unneeded devices from GENERIC-inherited configs. >> šI wonder, however if this can be handled better. > > FWIW, removing old drivers from GENERIC would be straightforward if we > could auto-load KLDs based on device IDs. > >> šE.g. either show better error in dtrace(1) or make ctfmerge fail causing kernel build to stop (since we asked for dtrace but in reality it wouldn't work), or remove some stale devices from GENERIC, or .something totally different? > > One more radical option is to extend the width of CTF type IDs. I've > been holding off on doing this for a few reasons: > - Doing so would change the binary format, making us incompatible with > ššthe reference CTF code in illumos. > - Type IDs are embedded in quite a few places in the various CTF > ššstructures, so enlarging them from 16 bits to 32 bits will bloat > ššCTF containers somewhat. > - I was under the impression that r287234 addressed the problem > ššsufficiently for now. > > If type ID space is still a problem post-r287234, I think it's time to > just go ahead and change the format. But first I'd like to understand > the cause of the duplication you're seeing. From owner-freebsd-current@freebsd.org Mon Sep 14 15:54:28 2015 Return-Path: Delivered-To: freebsd-current@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 B7F11A04B10 for ; Mon, 14 Sep 2015 15:54:28 +0000 (UTC) (envelope-from rysto32@gmail.com) Received: from mail-io0-x22f.google.com (mail-io0-x22f.google.com [IPv6:2607:f8b0:4001:c06::22f]) (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 83A2A136B; Mon, 14 Sep 2015 15:54:28 +0000 (UTC) (envelope-from rysto32@gmail.com) Received: by ioii196 with SMTP id i196so170901435ioi.3; Mon, 14 Sep 2015 08:54:28 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=+feF+q0gaiuQVVCNClxtLPramrF9vgtBp/SkRc78y5Q=; b=hMcDP7VApUahc/acihj5Qx7ygZ8/VMFGj/HFViJ3vO8+gylt4E2WyzF8iNQ8wub4UK qlyWQJGjxHtiEPzUYwx4pDBQKqlpZ+BcRPJ84nqTZY0I3seVHm7In/dIClLSkHQoFeEo 2DKVc+bG8rWlIYQlELSqM0Vkjc3IVtoF7hh9z00yW0JGBGA3cD1pozYOBiJeIlMZzKyf WNzvBIto8VqwsDqfbACvGwEEs0l0ozZX/CNS5cFOjOVv8br/EJdHb0QWnKqu4Z/0mgxc sjZ4DoRvNvu8ZY8+F9JOOBu/VnYwqEuVlG/ySCak0hRUmTt2S4r+Y8YwXJko33SBAgmX zPTw== MIME-Version: 1.0 X-Received: by 10.107.137.144 with SMTP id t16mr25868632ioi.102.1442246067936; Mon, 14 Sep 2015 08:54:27 -0700 (PDT) Received: by 10.107.178.67 with HTTP; Mon, 14 Sep 2015 08:54:27 -0700 (PDT) In-Reply-To: <363291442225336@web1h.yandex.ru> References: <738721442150603@web6j.yandex.ru> <20150913205333.GA2444@muskytusk> <363291442225336@web1h.yandex.ru> Date: Mon, 14 Sep 2015 11:54:27 -0400 Message-ID: Subject: Re: kernel dtrace and current From: Ryan Stone To: "Alexander V. Chernikov" Cc: Mark Johnston , FreeBSD CURRENT Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.20 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 14 Sep 2015 15:54:28 -0000 On Mon, Sep 14, 2015 at 6:08 AM, Alexander V. Chernikov < melifaro@freebsd.org> wrote: > (So I suppose that for some reason I got old ctfmerge) > I believe that ctfmerge is only built as a bootstrap tool when the host system's FreeBSD version is obsolete. Mark, you probably should update Makefile.inc1. From owner-freebsd-current@freebsd.org Mon Sep 14 22:17:30 2015 Return-Path: Delivered-To: freebsd-current@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 DAFE4A0318D for ; Mon, 14 Sep 2015 22:17:30 +0000 (UTC) (envelope-from markjdb@gmail.com) Received: from mail-qg0-x229.google.com (mail-qg0-x229.google.com [IPv6:2607:f8b0:400d:c04::229]) (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 9380C19CD; Mon, 14 Sep 2015 22:17:30 +0000 (UTC) (envelope-from markjdb@gmail.com) Received: by qgx61 with SMTP id 61so128126860qgx.3; Mon, 14 Sep 2015 15:17:29 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=sender:date:from:to:cc:subject:message-id:references:mime-version :content-type:content-disposition:in-reply-to:user-agent; bh=cUmhAfNjzMZMxzhmcW5eN4w/eLxhGVbrdEFsa2p4VII=; b=huZzTfxCMp3MdhxQuvAbHlc9GURl26LTG5ZDJBSkqaMyG7gZj6lrh3WcLNFLWP5SdT upCPVubKZyHtB/oDyKcAdR/vGfRoRPmvrovY8ep7me6XPqRwkq8Bnb5Qkm9Tg2Q/XStv Gr8NPw9sfhaHWUZ/HddxdCGS3/1AP7HSSsIyxsIyPxFMV1TbGlsUJ/fVknb7Wg8yX9je +NcrZqRhc7br5dFKWlpC5DValal1CFCFDngEZondK3zLU9BzKJiNPhW019pitAbaebWz mUoVgw2IqxuBgW1GwChFPLUoOwIMNzWqBP1M7iBqpON9emqN/0IZuG6VmF4PC0Uqz+xV CqBQ== X-Received: by 10.140.145.145 with SMTP id 139mr27342370qhr.100.1442269049723; Mon, 14 Sep 2015 15:17:29 -0700 (PDT) Received: from muskytusk ([104.236.250.12]) by smtp.gmail.com with ESMTPSA id a73sm6767204qkj.27.2015.09.14.15.17.28 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 14 Sep 2015 15:17:29 -0700 (PDT) Sender: Mark Johnston Date: Mon, 14 Sep 2015 22:16:56 +0000 From: Mark Johnston To: Ryan Stone Cc: "Alexander V. Chernikov" , FreeBSD CURRENT Subject: Re: kernel dtrace and current Message-ID: <20150914221656.GB15213@muskytusk> References: <738721442150603@web6j.yandex.ru> <20150913205333.GA2444@muskytusk> <363291442225336@web1h.yandex.ru> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.23 (2014-03-12) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 14 Sep 2015 22:17:31 -0000 On Mon, Sep 14, 2015 at 11:54:27AM -0400, Ryan Stone wrote: > On Mon, Sep 14, 2015 at 6:08 AM, Alexander V. Chernikov < > melifaro@freebsd.org> wrote: > > > (So I suppose that for some reason I got old ctfmerge) > > > > I believe that ctfmerge is only built as a bootstrap tool when the host > system's FreeBSD version is obsolete. Mark, you probably should update > Makefile.inc1. Right, thanks. I'll commit the change below in a bit; it'll force ctfmerge to be rebuilt until the next __FreeBSD_version bump (the last one occurred 10 days before the ctfmerge fix went in). Bumping the version just for this seems like overkill, given that it's a simple bug fix that doesn't introduce any incompatibilities. diff --git a/Makefile.inc1 b/Makefile.inc1 index 397c1af..a2058dc 100644 --- a/Makefile.inc1 +++ b/Makefile.inc1 @@ -1358,7 +1358,7 @@ ${_bt}-usr.bin/clang/tblgen: ${_bt}-lib/clang/libllvmtablegen ${_bt}-lib/clang/l # ELF Tool Chain libraries are needed for ELF tools and dtrace tools. # dtrace tools are required for older bootstrap env and cross-build # pre libdwarf -.if ${BOOTSTRAPPING} < 1100006 || (${MACHINE} != ${TARGET} || \ +.if ${BOOTSTRAPPING} < 1100080 || (${MACHINE} != ${TARGET} || \ ${MACHINE_ARCH} != ${TARGET_ARCH}) .if ${MK_CDDL} != "no" _dtrace_tools= cddl/usr.bin/sgsmsg cddl/lib/libctf cddl/usr.bin/ctfconvert \ From owner-freebsd-current@freebsd.org Mon Sep 14 23:12:45 2015 Return-Path: Delivered-To: freebsd-current@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 AF266A04D55 for ; Mon, 14 Sep 2015 23:12:45 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mail-qk0-f171.google.com (mail-qk0-f171.google.com [209.85.220.171]) (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 71479149C for ; Mon, 14 Sep 2015 23:12:44 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: by qkfq186 with SMTP id q186so65056782qkf.1 for ; Mon, 14 Sep 2015 16:12:38 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:sender:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=2QNmn8jBCfHw2by76jP1u7SV+bGWrMJiroeB+zfHDlk=; b=cnbOJhcKXeHvVSnBU0IhgTa3anX5skUL/v8m1V5DczPG4SCCdWh/2q47eHwQAXqvzP M1eLNzIRuhTjAWkejrHEfcXud4xFEXyGJvpjyLNYPjnSJQQakD855PDLDuaQLa7ezQrM 0AGpQTQvUN2IoQC/bWK78ufvzTSOXWlkEhqkOCU+SLL/ryNVipVppQoptVybp3BIVhto sWYfPDaEnoZflo71TZDnrgMulyKDvDMcQuzkbIA8Pwuh9KMU7tM3JsDXi1qRcFScVxfF EjH0yFRuJg/WjCYQ8hAacsWeJJcawA68nO6kC7tnnRyv35Xa8mWIluoIw/0jbvjRAqpE +bBg== X-Gm-Message-State: ALoCoQkEg9HcRUqoUXYypXRI8WSnD8/3Z7mFFsNU6kIS2kLy+ErvnoUZQ5zDiv/evKrbHXtCxbvZ MIME-Version: 1.0 X-Received: by 10.55.43.34 with SMTP id r34mr26130116qkh.77.1442272357961; Mon, 14 Sep 2015 16:12:37 -0700 (PDT) Sender: wlosh@bsdimp.com Received: by 10.140.80.167 with HTTP; Mon, 14 Sep 2015 16:12:37 -0700 (PDT) X-Originating-IP: [69.53.245.106] In-Reply-To: <20150914221656.GB15213@muskytusk> References: <738721442150603@web6j.yandex.ru> <20150913205333.GA2444@muskytusk> <363291442225336@web1h.yandex.ru> <20150914221656.GB15213@muskytusk> Date: Mon, 14 Sep 2015 17:12:37 -0600 X-Google-Sender-Auth: XQFKig0uwJi6BjcHm_-lZvwFNJI Message-ID: Subject: Re: kernel dtrace and current From: Warner Losh To: Mark Johnston Cc: Ryan Stone , "Alexander V. Chernikov" , FreeBSD CURRENT Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.20 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 14 Sep 2015 23:12:45 -0000 On Mon, Sep 14, 2015 at 4:16 PM, Mark Johnston wrote: > On Mon, Sep 14, 2015 at 11:54:27AM -0400, Ryan Stone wrote: > > On Mon, Sep 14, 2015 at 6:08 AM, Alexander V. Chernikov < > > melifaro@freebsd.org> wrote: > > > > > (So I suppose that for some reason I got old ctfmerge) > > > > > > > I believe that ctfmerge is only built as a bootstrap tool when the host > > system's FreeBSD version is obsolete. Mark, you probably should update > > Makefile.inc1. > > Right, thanks. I'll commit the change below in a bit; it'll force > ctfmerge to be rebuilt until the next __FreeBSD_version bump (the last > one occurred 10 days before the ctfmerge fix went in). Bumping the > version just for this seems like overkill, given that it's a simple bug > fix that doesn't introduce any incompatibilities. > > diff --git a/Makefile.inc1 b/Makefile.inc1 > index 397c1af..a2058dc 100644 > --- a/Makefile.inc1 > +++ b/Makefile.inc1 > @@ -1358,7 +1358,7 @@ ${_bt}-usr.bin/clang/tblgen: > ${_bt}-lib/clang/libllvmtablegen ${_bt}-lib/clang/l > # ELF Tool Chain libraries are needed for ELF tools and dtrace tools. > # dtrace tools are required for older bootstrap env and cross-build > # pre libdwarf > -.if ${BOOTSTRAPPING} < 1100006 || (${MACHINE} != ${TARGET} || \ > +.if ${BOOTSTRAPPING} < 1100080 || (${MACHINE} != ${TARGET} || \ > ${MACHINE_ARCH} != ${TARGET_ARCH}) > .if ${MK_CDDL} != "no" > _dtrace_tools= cddl/usr.bin/sgsmsg cddl/lib/libctf > cddl/usr.bin/ctfconvert \ > Looks good to me. However, maybe we should remove the if entirely. We have enough velocity in ctfmerge that it would just be flat safer to do that. We don't need to hyper optimize our build time at the expense of safety when people tweak things. Warner From owner-freebsd-current@freebsd.org Mon Sep 14 23:49:01 2015 Return-Path: Delivered-To: freebsd-current@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 8BFC5A03EF1 for ; Mon, 14 Sep 2015 23:49:01 +0000 (UTC) (envelope-from markjdb@gmail.com) Received: from mail-qk0-x231.google.com (mail-qk0-x231.google.com [IPv6:2607:f8b0:400d:c09::231]) (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 48BE61354; Mon, 14 Sep 2015 23:49:01 +0000 (UTC) (envelope-from markjdb@gmail.com) Received: by qkcf65 with SMTP id f65so65414388qkc.3; Mon, 14 Sep 2015 16:49:00 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=sender:date:from:to:cc:subject:message-id:references:mime-version :content-type:content-disposition:in-reply-to:user-agent; bh=s2sMHJQUi2BlvUuIx7GjSVk+yNYsd3dnIFziwCGRNuw=; b=q2ilKEHH204bD4q2lx0CCARIbsUz5onvALgK95Q7LGlipSQAA0dTgpmpS7tw7IqdOh nsRNiaOprxtP6FCKWhBgEtxPIUMH4N3Qa9Qk6zk8A0jzaBNh6vOh4rOY5gAuyQjV+6Vv /Qun/YKV26HxNRbnt3Q1jYw1MwhU5pI85p690/AVeuI7WaQLP9FvHN3ThmzhK72ZpTkn 51EbsyBehYZEMsBzkq4qzMc2qhzqFdwqnPyZQSvL5lldJRcdjr00NXFc9DvUgExzht4a qtnvfs3A85vVB92Lv6yu82Vt6hAhJcisFMEu560ePYnW3nrnhxlnrbnW1FCZ3MXl+O5p q2wg== X-Received: by 10.55.201.220 with SMTP id m89mr26697781qkl.87.1442274540324; Mon, 14 Sep 2015 16:49:00 -0700 (PDT) Received: from muskytusk ([104.236.250.12]) by smtp.gmail.com with ESMTPSA id d9sm6898032qka.49.2015.09.14.16.48.58 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 14 Sep 2015 16:48:59 -0700 (PDT) Sender: Mark Johnston Date: Mon, 14 Sep 2015 23:48:25 +0000 From: Mark Johnston To: Warner Losh Cc: Ryan Stone , "Alexander V. Chernikov" , FreeBSD CURRENT Subject: Re: kernel dtrace and current Message-ID: <20150914234825.GC15213@muskytusk> References: <738721442150603@web6j.yandex.ru> <20150913205333.GA2444@muskytusk> <363291442225336@web1h.yandex.ru> <20150914221656.GB15213@muskytusk> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.23 (2014-03-12) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 14 Sep 2015 23:49:01 -0000 On Mon, Sep 14, 2015 at 05:12:37PM -0600, Warner Losh wrote: > On Mon, Sep 14, 2015 at 4:16 PM, Mark Johnston wrote: > > > On Mon, Sep 14, 2015 at 11:54:27AM -0400, Ryan Stone wrote: > > > On Mon, Sep 14, 2015 at 6:08 AM, Alexander V. Chernikov < > > > melifaro@freebsd.org> wrote: > > > > > > > (So I suppose that for some reason I got old ctfmerge) > > > > > > > > > > I believe that ctfmerge is only built as a bootstrap tool when the host > > > system's FreeBSD version is obsolete. Mark, you probably should update > > > Makefile.inc1. > > > > Right, thanks. I'll commit the change below in a bit; it'll force > > ctfmerge to be rebuilt until the next __FreeBSD_version bump (the last > > one occurred 10 days before the ctfmerge fix went in). Bumping the > > version just for this seems like overkill, given that it's a simple bug > > fix that doesn't introduce any incompatibilities. > > > > diff --git a/Makefile.inc1 b/Makefile.inc1 > > index 397c1af..a2058dc 100644 > > --- a/Makefile.inc1 > > +++ b/Makefile.inc1 > > @@ -1358,7 +1358,7 @@ ${_bt}-usr.bin/clang/tblgen: > > ${_bt}-lib/clang/libllvmtablegen ${_bt}-lib/clang/l > > # ELF Tool Chain libraries are needed for ELF tools and dtrace tools. > > # dtrace tools are required for older bootstrap env and cross-build > > # pre libdwarf > > -.if ${BOOTSTRAPPING} < 1100006 || (${MACHINE} != ${TARGET} || \ > > +.if ${BOOTSTRAPPING} < 1100080 || (${MACHINE} != ${TARGET} || \ > > ${MACHINE_ARCH} != ${TARGET_ARCH}) > > .if ${MK_CDDL} != "no" > > _dtrace_tools= cddl/usr.bin/sgsmsg cddl/lib/libctf > > cddl/usr.bin/ctfconvert \ > > > > Looks good to me. > > However, maybe we should remove the if entirely. We have enough velocity > in ctfmerge that it would just be flat safer to do that. We don't need to > hyper > optimize our build time at the expense of safety when people tweak things. Sure, that makes sense to me. Updated diff: https://reviews.freebsd.org/D3670 While I'm looking at this, does anyone know what sgsmsg is for and why it's built as part of the bootstrap tools? It came in with r179200 as a DTrace build tool, but as far as I can see it's unused and always has been. If there's no reason to have it in the tree, I can remove it. From owner-freebsd-current@freebsd.org Tue Sep 15 02:43:40 2015 Return-Path: Delivered-To: freebsd-current@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 3C405A031A9 for ; Tue, 15 Sep 2015 02:43:40 +0000 (UTC) (envelope-from yaneurabeya@gmail.com) Received: from mail-qg0-x235.google.com (mail-qg0-x235.google.com [IPv6:2607:f8b0:400d:c04::235]) (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 ED4631FD5; Tue, 15 Sep 2015 02:43:39 +0000 (UTC) (envelope-from yaneurabeya@gmail.com) Received: by qgt47 with SMTP id 47so131863632qgt.2; Mon, 14 Sep 2015 19:43:39 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=XR/7GP9QZtanO9aQCmvsXEM7sCMzhkwtbLaUwPibILc=; b=XShlQSPqHnlzHNqOBNCJdtEJVWA1zTJPt5ooUz2j2VUcAQ3TXBXFLwD7Z02AWYfbCn OFxyfUJmJKb4Uj+JWmFblo2dK1PEr1k+3S0XurGi5z6dKd8zepFWzyUDP2F1bahz1lLw y5B82EWdffLq6Bu9cHno3fpZSva8HPxmaLeqqj5WEpQ60PIqoH1F7uLmkRrmED+71rkB GuaNgj53OO3YruL31/hWDyUZ1SEUGX0dlhX1VBApkmXwBNMfPcH8yZUHjFjB/yAWCLaN WZsQosfNjEIFerH2X45c2bPuWQfGG5LdPca9WLNIUJo3f6YlHnQxLCRjgOZ+4f4h53Qo Hshw== MIME-Version: 1.0 X-Received: by 10.140.19.101 with SMTP id 92mr27751093qgg.90.1442285019090; Mon, 14 Sep 2015 19:43:39 -0700 (PDT) Received: by 10.140.94.33 with HTTP; Mon, 14 Sep 2015 19:43:39 -0700 (PDT) In-Reply-To: <20150914234825.GC15213@muskytusk> References: <738721442150603@web6j.yandex.ru> <20150913205333.GA2444@muskytusk> <363291442225336@web1h.yandex.ru> <20150914221656.GB15213@muskytusk> <20150914234825.GC15213@muskytusk> Date: Mon, 14 Sep 2015 19:43:39 -0700 Message-ID: Subject: Re: kernel dtrace and current From: NGie Cooper To: Mark Johnston Cc: Warner Losh , Ryan Stone , "Alexander V. Chernikov" , FreeBSD CURRENT Content-Type: text/plain; charset=UTF-8 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 15 Sep 2015 02:43:40 -0000 On Mon, Sep 14, 2015 at 4:48 PM, Mark Johnston wrote: ... > While I'm looking at this, does anyone know what sgsmsg is for and why > it's built as part of the bootstrap tools? It came in with r179200 as a > DTrace build tool, but as far as I can see it's unused and always has > been. If there's no reason to have it in the tree, I can remove it. Unfortunately manpages don't render on github, but this might help: https://github.com/joyent/illumos-joyent/blob/master/usr/src/cmd/sgs/tools/man/sgsmsg.1l Cheers, -NGie From owner-freebsd-current@freebsd.org Tue Sep 15 09:31:58 2015 Return-Path: Delivered-To: freebsd-current@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 A4DEBA03F8C; Tue, 15 Sep 2015 09:31:58 +0000 (UTC) (envelope-from stefanogarzarella@gmail.com) Received: from mail-lb0-x236.google.com (mail-lb0-x236.google.com [IPv6:2a00:1450:4010:c04::236]) (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 4AF311DAE; Tue, 15 Sep 2015 09:31:58 +0000 (UTC) (envelope-from stefanogarzarella@gmail.com) Received: by lbpo4 with SMTP id o4so81675623lbp.2; Tue, 15 Sep 2015 02:31:56 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:from:date:message-id:subject:to:cc:content-type; bh=qcjGr6tjlEnsnmw78+wJ8ySHMzv8JXAzGcgUZjqYB1s=; b=Mjcn3nZ3gZUaeyHDO1LZ5ftHfGSPn6QdG1Ys8ZZHUgcfuSwdHN99NauFG/xEFJZNzB OKzDN2LiDMq46BQp7YUnpTyBLzKkxzCQV1jo0W24KgVG7TyA6YT14/hP8zm/U5eDIs4/ O+xm4A6WuvszTu1Dn6oSOC2G9BNn+lc+nwjDY+6dhquOT9nYim/oQkMfQVDBfaEhCErZ wPnXst/eNA2QejfKFO9BhArLed2yflaWhPHI9NyumVbREaN96Sj3+oIFfTingPBhtC2G 1qqYMTYci8HFTVoWxcY6Jtyiai8pPtDujKiTuZEFcfCtPpKi58kAhTjYdJvElOIwURHR kfdw== X-Received: by 10.112.172.165 with SMTP id bd5mr3691058lbc.51.1442309516308; Tue, 15 Sep 2015 02:31:56 -0700 (PDT) MIME-Version: 1.0 Received: by 10.25.137.85 with HTTP; Tue, 15 Sep 2015 02:31:36 -0700 (PDT) From: Stefano Garzarella Date: Tue, 15 Sep 2015 11:31:36 +0200 Message-ID: Subject: nanoBSD boot problem (on USB stick or as a HD) To: freebsd-current , freebsd-hackers@freebsd.org Cc: Luigi Rizzo Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.20 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 15 Sep 2015 09:31:58 -0000 Hi all, I created a nanoBSD image for my gsoc project (ptnetmap on bhyve). I would like to boot this image on USB stick or in the hypervisor as a HD. I have some problem because if I set NANO_DRIVE="da0" (for USB boot) in the nanoBSD configuration file, the boot from USB stick works well, but when I try to boot the same image in the hypervisor as a HD, I have the following mountroot error: Trying to mount root from ufs:/dev/da0s1a [ro]... mountroot: waiting for device /dev/da0s1a ... Mounting from ufs:/dev/da0s1a failed with error 19. Loader variables: vfs.root.mountfrom=ufs:/dev/da0s1a vfs.root.mountfrom.options=ro mountroot> At this point I need to manually specify "ufs:/dev/ad0s1a" to properly mount the root. Can you help me? There is some tricks to avoid this mountroot error? Thanks, Stefano Garzarella From owner-freebsd-current@freebsd.org Tue Sep 15 10:05:22 2015 Return-Path: Delivered-To: freebsd-current@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 CAD91A044BF; Tue, 15 Sep 2015 10:05:22 +0000 (UTC) (envelope-from ohartman@zedat.fu-berlin.de) Received: from outpost1.zedat.fu-berlin.de (outpost1.zedat.fu-berlin.de [130.133.4.66]) (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 8561611A7; Tue, 15 Sep 2015 10:05:21 +0000 (UTC) (envelope-from ohartman@zedat.fu-berlin.de) Received: from inpost2.zedat.fu-berlin.de ([130.133.4.69]) by outpost.zedat.fu-berlin.de (Exim 4.85) with esmtp (envelope-from ) id <1Zbn70-0043pG-0u>; Tue, 15 Sep 2015 12:05:18 +0200 Received: from p578a69f9.dip0.t-ipconnect.de ([87.138.105.249] helo=freyja.zeit4.iv.bundesimmobilien.de) by inpost2.zedat.fu-berlin.de (Exim 4.85) with esmtpsa (envelope-from ) id <1Zbn6z-000uaj-R8>; Tue, 15 Sep 2015 12:05:17 +0200 Date: Tue, 15 Sep 2015 12:05:17 +0200 From: "O. Hartmann" To: Stefano Garzarella Cc: freebsd-current , freebsd-hackers@freebsd.org, Luigi Rizzo Subject: Re: nanoBSD boot problem (on USB stick or as a HD) Message-ID: <20150915120517.39c691ce@freyja.zeit4.iv.bundesimmobilien.de> In-Reply-To: References: Organization: FU Berlin X-Mailer: Claws Mail 3.12.0 (GTK+ 2.24.28; amd64-portbld-freebsd11.0) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Originating-IP: 87.138.105.249 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 15 Sep 2015 10:05:22 -0000 On Tue, 15 Sep 2015 11:31:36 +0200 Stefano Garzarella wrote: > Hi all, > I created a nanoBSD image for my gsoc project (ptnetmap on bhyve). > > I would like to boot this image on USB stick or in the hypervisor as a HD. > I have some problem because if I set NANO_DRIVE="da0" (for USB boot) > in the nanoBSD configuration file, the boot from USB stick works well, > but when I try to boot the same image in the hypervisor as a HD, > I have the following mountroot error: > > Trying to mount root from ufs:/dev/da0s1a [ro]... > mountroot: waiting for device /dev/da0s1a ... > Mounting from ufs:/dev/da0s1a failed with error 19. > > Loader variables: > vfs.root.mountfrom=ufs:/dev/da0s1a > vfs.root.mountfrom.options=ro > > mountroot> > > > At this point I need to manually specify "ufs:/dev/ad0s1a" to properly mount > the root. > > Can you help me? > There is some tricks to avoid this mountroot error? > > Thanks, > Stefano Garzarella > _______________________________________________ > freebsd-current@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" Check your /etc/fstab. I guess the device for "/" is still /dev/da0s1a. I had to patch the nanoBSD scripts to target that issue and booting from UEFI systems, but my solution is not very transparent. Using labels would be more convenient and would be much more GPT/UEFI friendly. regards, Oliver From owner-freebsd-current@freebsd.org Tue Sep 15 10:26:09 2015 Return-Path: Delivered-To: freebsd-current@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 B7701A04FCD; Tue, 15 Sep 2015 10:26:09 +0000 (UTC) (envelope-from jenkins-admin@FreeBSD.org) Received: from jenkins-9.freebsd.org (jenkins-9.freebsd.org [8.8.178.209]) by mx1.freebsd.org (Postfix) with ESMTP id A73B41DA3; Tue, 15 Sep 2015 10:26:09 +0000 (UTC) (envelope-from jenkins-admin@FreeBSD.org) Received: from jenkins-9.freebsd.org (localhost [127.0.0.1]) by jenkins-9.freebsd.org (Postfix) with ESMTP id A2901845; Tue, 15 Sep 2015 10:26:09 +0000 (UTC) Date: Tue, 15 Sep 2015 10:26:08 +0000 (GMT) From: jenkins-admin@FreeBSD.org To: jenkins-admin@FreeBSD.org, freebsd-current@FreeBSD.org, freebsd-i386@FreeBSD.org Message-ID: <1516224634.12.1442312769488.JavaMail.jenkins@jenkins-9.freebsd.org> In-Reply-To: <498499138.3.1442301332039.JavaMail.jenkins@jenkins-9.freebsd.org> References: <498499138.3.1442301332039.JavaMail.jenkins@jenkins-9.freebsd.org> Subject: FreeBSD_HEAD_i386 - Build #1118 - Fixed MIME-Version: 1.0 X-Jenkins-Job: FreeBSD_HEAD_i386 X-Jenkins-Result: SUCCESS Precedence: bulk Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.20 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.20 List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 15 Sep 2015 10:26:09 -0000 FreeBSD_HEAD_i386 - Build #1118 - Fixed: Build information: https://jenkins.FreeBSD.org/job/FreeBSD_HEAD_i386/1118/ Full change log: https://jenkins.FreeBSD.org/job/FreeBSD_HEAD_i386/1118/changes Full build log: https://jenkins.FreeBSD.org/job/FreeBSD_HEAD_i386/1118/console Change summaries: No changes From owner-freebsd-current@freebsd.org Tue Sep 15 10:33:42 2015 Return-Path: Delivered-To: freebsd-current@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 7F192A024CA for ; Tue, 15 Sep 2015 10:33:42 +0000 (UTC) (envelope-from sgeos@hotmail.com) Received: from BAY004-OMC2S5.hotmail.com (bay004-omc2s5.hotmail.com [65.54.190.80]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (Client CN "*.outlook.com", Issuer "MSIT Machine Auth CA 2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 6F7FA126E for ; Tue, 15 Sep 2015 10:33:42 +0000 (UTC) (envelope-from sgeos@hotmail.com) Received: from BAY182-W82 ([65.54.190.124]) by BAY004-OMC2S5.hotmail.com over TLS secured channel with Microsoft SMTPSVC(7.5.7601.23008); Tue, 15 Sep 2015 03:32:36 -0700 X-TMN: [3lKQY83d/Pe5ARCRuP2e/GWBHQqjK7Ik] X-Originating-Email: [sgeos@hotmail.com] Message-ID: From: Brendan Sechter To: "freebsd-current@freebsd.org" Subject: FreeBSD 11.0-CURRENT Single User Keymap Date: Tue, 15 Sep 2015 19:32:35 +0900 Importance: Normal Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-OriginalArrivalTime: 15 Sep 2015 10:32:36.0286 (UTC) FILETIME=[D698DDE0:01D0EFA1] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 15 Sep 2015 10:33:42 -0000 When compiling a FreeBSD 11.0-CURRENT kernel=2C what is required to change = the keymap used in single user mode? =A0I originally asked this question on= the FreeBSD forums=2C but was bounced to the mailing list because CURRENT = is an unsupported version.=0A= =0A= I have read an old forum thread on this topic. I have also read the=A0atkbd= (4)=A0and=A0ukbd(4)=A0man pages. The relevant parts of my kernel configurat= ion are as follows:=0A= =0A= #=A0----------=A0----------=A0----------=A0----------=0A= include GENERIC=0A= ident MY_KERNEL=0A= =0A= # AT Keyboard=0A= device atkbdc=0A= options ATKBD_DFLT_KEYMAP=0A= makeoptions ATKBD_DFLT_KEYMAP=3Djp.106=0A= device atkbd=0A= =0A= # USB Keyboard=0A= device ukbd=0A= options UKBD_DFLT_KEYMAP=0A= makeoptions UKBD_DFLT_KEYMAP=3Djp.106=0A= =0A= # everything else=0A= # ...=0A= #=A0----------=A0----------=A0----------=A0----------=0A= =0A= So far as I can tell=2C these options should be working. I am using a 106 k= ey Japanese keyboard. Single user mode appears to use the keymap for a 101 = key standard US layout. I have tried the following values:=0A= - jp=0A= - jp.106=0A= - jp.106.kbd (not tried recently)=0A= =0A= Finally=2C this is a FreeBSD VM running in VirtualBox on OSX. I am 99% sure= I am having the same problem on my physical machines. The specific driver = almost certainly depends on the hardware.=0A= =0A= Thanks=2C=0A= -Brendan = From owner-freebsd-current@freebsd.org Tue Sep 15 10:48:22 2015 Return-Path: Delivered-To: freebsd-current@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 CA064A03046; Tue, 15 Sep 2015 10:48:22 +0000 (UTC) (envelope-from stefanogarzarella@gmail.com) Received: from mail-la0-x232.google.com (mail-la0-x232.google.com [IPv6:2a00:1450:4010:c03::232]) (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 6CC631C9A; Tue, 15 Sep 2015 10:48:22 +0000 (UTC) (envelope-from stefanogarzarella@gmail.com) Received: by lahg1 with SMTP id g1so75038285lah.1; Tue, 15 Sep 2015 03:48:20 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc:content-type; bh=deNpc4Wu9BaPQhqTCqDXTE1uvudJEUriryYU9n2Hifw=; b=LIw0VFYEnj8/DR7ZAfyulEOP+KgWQR000XmcWg4hrBCpNvhyMUbkPpvmS1aPON3nLX 46Z8danRpk56sKMdyyBkKpXk6as6lkOboTsYGjpswApugtUjW4ggwA3Z6kK3tfseWW/Y 7jiJST807uvf6tBf3BgWKagczjcosK+9mTEgRCPa+zj0XC6652jSgWyTcNwelyD2YEc/ y6ov0sid/tBhYPGmRuVMEZPaBfG7YD1XLwLEl3X1AbN/X3LkPTqLxhvwF/qp9RgvG4/7 MHEkQQFSTERRqwdb7xeU72K/aI88qBkDW7bY/t0m/9iE+Vg5DIFdVcgGkCyGJC3SEVEz vt/g== X-Received: by 10.152.28.65 with SMTP id z1mr20178894lag.9.1442314100125; Tue, 15 Sep 2015 03:48:20 -0700 (PDT) MIME-Version: 1.0 References: <20150915120517.39c691ce@freyja.zeit4.iv.bundesimmobilien.de> In-Reply-To: <20150915120517.39c691ce@freyja.zeit4.iv.bundesimmobilien.de> From: Stefano Garzarella Date: Tue, 15 Sep 2015 10:48:10 +0000 Message-ID: Subject: Re: nanoBSD boot problem (on USB stick or as a HD) To: "O. Hartmann" Cc: freebsd-current , freebsd-hackers@freebsd.org, Luigi Rizzo Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.20 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 15 Sep 2015 10:48:22 -0000 Hi Oliver, Thank you very much! I solved it setting NANO_LABEL="mylabel". Cheers, Stefano Il giorno mar 15 set 2015 alle 12:05 O. Hartmann < ohartman@zedat.fu-berlin.de> ha scritto: > On Tue, 15 Sep 2015 11:31:36 +0200 > Stefano Garzarella wrote: > > > Hi all, > > I created a nanoBSD image for my gsoc project (ptnetmap on bhyve). > > > > I would like to boot this image on USB stick or in the hypervisor as a > HD. > > I have some problem because if I set NANO_DRIVE="da0" (for USB boot) > > in the nanoBSD configuration file, the boot from USB stick works well, > > but when I try to boot the same image in the hypervisor as a HD, > > I have the following mountroot error: > > > > Trying to mount root from ufs:/dev/da0s1a [ro]... > > mountroot: waiting for device /dev/da0s1a ... > > Mounting from ufs:/dev/da0s1a failed with error 19. > > > > Loader variables: > > vfs.root.mountfrom=ufs:/dev/da0s1a > > vfs.root.mountfrom.options=ro > > > > mountroot> > > > > > > At this point I need to manually specify "ufs:/dev/ad0s1a" to properly > mount > > the root. > > > > Can you help me? > > There is some tricks to avoid this mountroot error? > > > > Thanks, > > Stefano Garzarella > > _______________________________________________ > > freebsd-current@freebsd.org mailing list > > https://lists.freebsd.org/mailman/listinfo/freebsd-current > > To unsubscribe, send any mail to " > freebsd-current-unsubscribe@freebsd.org" > > > Check your /etc/fstab. I guess the device for "/" is still /dev/da0s1a. I > had > to patch the nanoBSD scripts to target that issue and booting from UEFI > systems, > but my solution is not very transparent. > > Using labels would be more convenient and would be much more GPT/UEFI > friendly. > > regards, > > Oliver > From owner-freebsd-current@freebsd.org Tue Sep 15 10:56:21 2015 Return-Path: Delivered-To: freebsd-current@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 647C7A036D5 for ; Tue, 15 Sep 2015 10:56:21 +0000 (UTC) (envelope-from ohartman@zedat.fu-berlin.de) Received: from outpost1.zedat.fu-berlin.de (outpost1.zedat.fu-berlin.de [130.133.4.66]) (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 236981373 for ; Tue, 15 Sep 2015 10:56:20 +0000 (UTC) (envelope-from ohartman@zedat.fu-berlin.de) Received: from inpost2.zedat.fu-berlin.de ([130.133.4.69]) by outpost.zedat.fu-berlin.de (Exim 4.85) for freebsd-current@freebsd.org with esmtp (envelope-from ) id <1ZbnuN-000j79-0K>; Tue, 15 Sep 2015 12:56:19 +0200 Received: from p578a69f9.dip0.t-ipconnect.de ([87.138.105.249] helo=freyja.zeit4.iv.bundesimmobilien.de) by inpost2.zedat.fu-berlin.de (Exim 4.85) for freebsd-current@freebsd.org with esmtpsa (envelope-from ) id <1ZbnuM-000zTk-Pq>; Tue, 15 Sep 2015 12:56:18 +0200 Date: Tue, 15 Sep 2015 12:56:18 +0200 From: "O. Hartmann" To: freebsd-current Subject: CURRENT: net/igb broken Message-ID: <20150915125618.0f752596@freyja.zeit4.iv.bundesimmobilien.de> Organization: FU Berlin X-Mailer: Claws Mail 3.12.0 (GTK+ 2.24.28; amd64-portbld-freebsd11.0) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Originating-IP: 87.138.105.249 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 15 Sep 2015 10:56:21 -0000 Running CURRENT as of today (r287817), it seems that the network system of CURRENT is corrupted. The machine in question is a Fujitsu server Primergy RX 1330 with two Intel "igb" devices (igb0 and igb1). the network is now on both devices unreachable. With or without IPFW (disabling, having first rule to allow everything in/out) doesn't matter. Nothing get to or from that box on any device. With FreeBSD 11.0-CURRENT #4 r287592: Wed Sep 9 09:09:23 CEST 2015 amd64 I had no problems. Any ideas? Thanks in advance, Oliver From owner-freebsd-current@freebsd.org Tue Sep 15 11:09:21 2015 Return-Path: Delivered-To: freebsd-current@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 06AA4A03EA3 for ; Tue, 15 Sep 2015 11:09:21 +0000 (UTC) (envelope-from hps@selasky.org) Received: from mail.turbocat.net (heidi.turbocat.net [88.198.202.214]) (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 C0FBF1BD9 for ; Tue, 15 Sep 2015 11:09:20 +0000 (UTC) (envelope-from hps@selasky.org) Received: from laptop015.home.selasky.org (cm-176.74.213.204.customer.telag.net [176.74.213.204]) (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 C4F181FE023; Tue, 15 Sep 2015 13:09:11 +0200 (CEST) Subject: Re: CURRENT: net/igb broken To: "O. Hartmann" , freebsd-current References: <20150915125618.0f752596@freyja.zeit4.iv.bundesimmobilien.de> From: Hans Petter Selasky Message-ID: <55F7FCB5.5090809@selasky.org> Date: Tue, 15 Sep 2015 13:10:45 +0200 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:38.0) Gecko/20100101 Thunderbird/38.1.0 MIME-Version: 1.0 In-Reply-To: <20150915125618.0f752596@freyja.zeit4.iv.bundesimmobilien.de> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 15 Sep 2015 11:09:21 -0000 On 09/15/15 12:56, O. Hartmann wrote: > Running CURRENT as of today (r287817), it seems that the network system of > CURRENT is corrupted. The machine in question is a Fujitsu server Primergy RX > 1330 with two Intel "igb" devices (igb0 and igb1). > > the network is now on both devices unreachable. With or without IPFW > (disabling, having first rule to allow everything in/out) doesn't matter. > Nothing get to or from that box on any device. > > With FreeBSD 11.0-CURRENT #4 r287592: Wed Sep 9 09:09:23 CEST 2015 amd64 I > had no problems. > > Any ideas? > > Thanks in advance, > > Oliver Just to rule out r287775, can you disable TSO? --HPS From owner-freebsd-current@freebsd.org Tue Sep 15 18:46:35 2015 Return-Path: Delivered-To: freebsd-current@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 185D3A053A2 for ; Tue, 15 Sep 2015 18:46:35 +0000 (UTC) (envelope-from jeffrey.e.pieper@intel.com) Received: from mga09.intel.com (mga09.intel.com [134.134.136.24]) by mx1.freebsd.org (Postfix) with ESMTP id EB5A3115E for ; Tue, 15 Sep 2015 18:46:34 +0000 (UTC) (envelope-from jeffrey.e.pieper@intel.com) Received: from fmsmga001.fm.intel.com ([10.253.24.23]) by orsmga102.jf.intel.com with ESMTP; 15 Sep 2015 11:46:15 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.17,536,1437462000"; d="scan'208";a="790029252" Received: from orsmsx107.amr.corp.intel.com ([10.22.240.5]) by fmsmga001.fm.intel.com with ESMTP; 15 Sep 2015 11:46:12 -0700 Received: from orsmsx114.amr.corp.intel.com (10.22.240.10) by ORSMSX107.amr.corp.intel.com (10.22.240.5) with Microsoft SMTP Server (TLS) id 14.3.224.2; Tue, 15 Sep 2015 11:45:37 -0700 Received: from orsmsx111.amr.corp.intel.com ([169.254.11.185]) by ORSMSX114.amr.corp.intel.com ([169.254.8.101]) with mapi id 14.03.0224.002; Tue, 15 Sep 2015 11:45:36 -0700 From: "Pieper, Jeffrey E" To: Hans Petter Selasky , "O. Hartmann" , freebsd-current Subject: RE: CURRENT: net/igb broken Thread-Topic: CURRENT: net/igb broken Thread-Index: AQHQ76U3BwLOm8IL106DyQrg8DDGAZ495GOAgAAHGhA= Date: Tue, 15 Sep 2015 18:45:35 +0000 Message-ID: <2A35EA60C3C77D438915767F458D65688077F87B@ORSMSX111.amr.corp.intel.com> References: <20150915125618.0f752596@freyja.zeit4.iv.bundesimmobilien.de> <55F7FCB5.5090809@selasky.org> In-Reply-To: <55F7FCB5.5090809@selasky.org> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.22.254.138] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 15 Sep 2015 18:46:35 -0000 -----Original Message----- From: owner-freebsd-current@freebsd.org [mailto:owner-freebsd-current@freeb= sd.org] On Behalf Of Hans Petter Selasky Sent: Tuesday, September 15, 2015 4:11 AM To: O. Hartmann ; freebsd-current Subject: Re: CURRENT: net/igb broken On 09/15/15 12:56, O. Hartmann wrote: > Running CURRENT as of today (r287817), it seems that the network system o= f > CURRENT is corrupted. The machine in question is a Fujitsu server Primerg= y RX > 1330 with two Intel "igb" devices (igb0 and igb1). > > the network is now on both devices unreachable. With or without IPFW > (disabling, having first rule to allow everything in/out) doesn't matter. > Nothing get to or from that box on any device. > > With FreeBSD 11.0-CURRENT #4 r287592: Wed Sep 9 09:09:23 CEST 2015 amd6= 4 I > had no problems. > > Any ideas? > > Thanks in advance, > > Oliver > >Just to rule out r287775, can you disable TSO? > >--HPS I'm using r827826 (just pulled this morning) with igb and it seems to be wo= rking (icmp and ssh). Jeff _______________________________________________ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" From owner-freebsd-current@freebsd.org Wed Sep 16 00:00:25 2015 Return-Path: Delivered-To: freebsd-current@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 4B4799CD1DA for ; Wed, 16 Sep 2015 00:00:25 +0000 (UTC) (envelope-from glebius@FreeBSD.org) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 33C34130E for ; Wed, 16 Sep 2015 00:00:25 +0000 (UTC) (envelope-from glebius@FreeBSD.org) Received: by mailman.ysv.freebsd.org (Postfix) id 30CFD9CD1D9; Wed, 16 Sep 2015 00:00:25 +0000 (UTC) Delivered-To: current@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 306A69CD1D8 for ; Wed, 16 Sep 2015 00:00:25 +0000 (UTC) (envelope-from glebius@FreeBSD.org) Received: from cell.glebius.int.ru (glebius.int.ru [81.19.69.10]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "cell.glebius.int.ru", Issuer "cell.glebius.int.ru" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 9667F1309; Wed, 16 Sep 2015 00:00:23 +0000 (UTC) (envelope-from glebius@FreeBSD.org) Received: from cell.glebius.int.ru (localhost [127.0.0.1]) by cell.glebius.int.ru (8.15.2/8.15.2) with ESMTPS id t8G00Jl7007024 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Wed, 16 Sep 2015 03:00:20 +0300 (MSK) (envelope-from glebius@FreeBSD.org) Received: (from glebius@localhost) by cell.glebius.int.ru (8.15.2/8.15.2/Submit) id t8G00JEj007023; Wed, 16 Sep 2015 03:00:19 +0300 (MSK) (envelope-from glebius@FreeBSD.org) X-Authentication-Warning: cell.glebius.int.ru: glebius set sender to glebius@FreeBSD.org using -f Date: Wed, 16 Sep 2015 03:00:19 +0300 From: Gleb Smirnoff To: marcel@FreeBSD.org, Steve Kiernan , brooks@FreeBSD.org Cc: current@FreeBSD.org Subject: r286727 breaks geom_md.ko loading Message-ID: <20150916000019.GH1023@FreeBSD.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.23 (2014-03-12) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 16 Sep 2015 00:00:25 -0000 Hi! There is regression after r286727. Our dynamic kernel linker doesn't support weak symbols, so the geom_md.ko can no longer be loaded dynamically neither from loader nor at runtime. Having it statically in kernel is the only working option. -- Totus tuus, Glebius. From owner-freebsd-current@freebsd.org Wed Sep 16 01:54:11 2015 Return-Path: Delivered-To: freebsd-current@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 3E3779CDB17 for ; Wed, 16 Sep 2015 01:54:11 +0000 (UTC) (envelope-from julian@freebsd.org) Received: from vps1.elischer.org (vps1.elischer.org [204.109.63.16]) (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 198AB13A3 for ; Wed, 16 Sep 2015 01:54:10 +0000 (UTC) (envelope-from julian@freebsd.org) Received: from Julian-MBP3.local (ppp121-45-224-161.lns20.per1.internode.on.net [121.45.224.161]) (authenticated bits=0) by vps1.elischer.org (8.15.2/8.15.2) with ESMTPSA id t8G1s0Ne070369 (version=TLSv1.2 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO) for ; Tue, 15 Sep 2015 18:54:03 -0700 (PDT) (envelope-from julian@freebsd.org) Subject: Re: nanoBSD boot problem (on USB stick or as a HD) To: freebsd-current@freebsd.org References: From: Julian Elischer Message-ID: <55F8CBB2.1080109@freebsd.org> Date: Wed, 16 Sep 2015 09:53:54 +0800 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:38.0) Gecko/20100101 Thunderbird/38.2.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 16 Sep 2015 01:54:11 -0000 On 9/15/15 5:31 PM, Stefano Garzarella wrote: > Hi all, > I created a nanoBSD image for my gsoc project (ptnetmap on bhyve). > > I would like to boot this image on USB stick or in the hypervisor as a HD. > I have some problem because if I set NANO_DRIVE="da0" (for USB boot) > in the nanoBSD configuration file, the boot from USB stick works well, > but when I try to boot the same image in the hypervisor as a HD, > I have the following mountroot error: you have to override vfs.root.mountfrom in the hypervisor's loader bhyveload. otherwise it looks at /etc/fstab in the root filesystem, and you can't have it work both ways.. one possibility is to use gpart label to describe the device. possibly it woudl hav ehte same result in both cases, but I don't know for sure that it works for root device.. you'd have to test. > > Trying to mount root from ufs:/dev/da0s1a [ro]... > mountroot: waiting for device /dev/da0s1a ... > Mounting from ufs:/dev/da0s1a failed with error 19. > > Loader variables: > vfs.root.mountfrom=ufs:/dev/da0s1a > vfs.root.mountfrom.options=ro > > mountroot> > > > At this point I need to manually specify "ufs:/dev/ad0s1a" to properly mount > the root. > > Can you help me? > There is some tricks to avoid this mountroot error? > > Thanks, > Stefano Garzarella > _______________________________________________ > freebsd-current@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" > From owner-freebsd-current@freebsd.org Wed Sep 16 02:18:07 2015 Return-Path: Delivered-To: freebsd-current@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 765059C2B07 for ; Wed, 16 Sep 2015 02:18:07 +0000 (UTC) (envelope-from rysto32@gmail.com) Received: from mail-ig0-x22c.google.com (mail-ig0-x22c.google.com [IPv6:2607:f8b0:4001:c05::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 43F6A1ED7; Wed, 16 Sep 2015 02:18:07 +0000 (UTC) (envelope-from rysto32@gmail.com) Received: by igcrk20 with SMTP id rk20so26181562igc.1; Tue, 15 Sep 2015 19:18:06 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=eg3nprHPLwPdz0GunDkvSZtB8a+D4ICIhLbE8gSg6w0=; b=XNYhEC/jBWiyOioaDXZRjC+znFRLk36PghSmbWqFAab/IyQFBSaEWaoGI1bkZdOiu4 9uQ7XwI74yQAUYlDtPwLd+3RBc1mZXoAMsRnH2pH1xCMWkjiIfDIUY/rngXeAnfiJZ8a boRYUfQ7FtEQWB3GWWxgH64QqifNXZd0toHRWpeHjwHlvdwO/AO0JrecdeFrzVeH7iyw dT5dVWrGhcZlTRbXVBoGud+wDU3LgvF5R3Hh7nYsVt2GZNbCp70SZdR73DRpx7JltC1B /6ASYhk7LZ96G6uz/6GYakl9WjYkIoI0B0Iz9oEYEiWGukqNL9OB73MMLpegOfvFTeW/ BNwA== MIME-Version: 1.0 X-Received: by 10.50.30.106 with SMTP id r10mr11749686igh.69.1442369886723; Tue, 15 Sep 2015 19:18:06 -0700 (PDT) Received: by 10.107.178.67 with HTTP; Tue, 15 Sep 2015 19:18:06 -0700 (PDT) In-Reply-To: <55F8CBB2.1080109@freebsd.org> References: <55F8CBB2.1080109@freebsd.org> Date: Tue, 15 Sep 2015 22:18:06 -0400 Message-ID: Subject: Re: nanoBSD boot problem (on USB stick or as a HD) From: Ryan Stone To: Julian Elischer Cc: FreeBSD Current Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.20 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 16 Sep 2015 02:18:07 -0000 On Tue, Sep 15, 2015 at 9:53 PM, Julian Elischer wrote: > one possibility is to use gpart label to describe the device. > possibly it woudl hav ehte same result in both cases, but I don't know for > sure that > it works for root device.. you'd have to test. > > I would recommend a UFS label instead. gpart labels are kind of fragile and easy to mess up. My previous employer has been shipping systems where the root fs is specified in fstab via a UFS label for years and it never gave us a problems. From owner-freebsd-current@freebsd.org Wed Sep 16 02:26:00 2015 Return-Path: Delivered-To: freebsd-current@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 1CA459CD143 for ; Wed, 16 Sep 2015 02:26:00 +0000 (UTC) (envelope-from yaneurabeya@gmail.com) Received: from mail-qg0-x234.google.com (mail-qg0-x234.google.com [IPv6:2607:f8b0:400d:c04::234]) (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 CF9F31614; Wed, 16 Sep 2015 02:25:59 +0000 (UTC) (envelope-from yaneurabeya@gmail.com) Received: by qgx61 with SMTP id 61so160674413qgx.3; Tue, 15 Sep 2015 19:25:59 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=pcYw2I56qc+GG0CJQOCGm5cbXaVKGzHE/ce5mRfNmd8=; b=KXZ6ArHo/wLhSjyKSrD8EmwhwkLNethCfXiC/q2EqbeNCk42tVFOutYu8XFTJvf+zW jUCnaEo3LTZRm3Ba2jgeIYLaLRU8FM45/OQ2Z7qYyFT1VpeYp8fyMcRv4SirMwT2/WVy 8cKQ0tcsMpSizBnSqRErSoO3/CWPQPlXiOX6nKWVAqkjCgiQoE1Imn7z/KGBsYG4VqmM Sh/KtSiaGzBrff3ukrURlUdkjhUWJJmZEUzheXy7q11fQ4pwM6pMEs9lNQ1dwC7jNsAU 489LR50XKVCCV/0+WqMQDoRrwiVT7Mj4OyCVpEDQ/SO6NU0XRmkqRDV/GINbld2p7oqA RiFA== MIME-Version: 1.0 X-Received: by 10.140.216.211 with SMTP id m202mr39667251qhb.80.1442370358958; Tue, 15 Sep 2015 19:25:58 -0700 (PDT) Received: by 10.140.94.33 with HTTP; Tue, 15 Sep 2015 19:25:58 -0700 (PDT) In-Reply-To: References: <55F8CBB2.1080109@freebsd.org> Date: Tue, 15 Sep 2015 19:25:58 -0700 Message-ID: Subject: Re: nanoBSD boot problem (on USB stick or as a HD) From: NGie Cooper To: Ryan Stone Cc: Julian Elischer , FreeBSD Current Content-Type: text/plain; charset=UTF-8 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 16 Sep 2015 02:26:00 -0000 On Tue, Sep 15, 2015 at 7:18 PM, Ryan Stone wrote: > On Tue, Sep 15, 2015 at 9:53 PM, Julian Elischer wrote: > >> one possibility is to use gpart label to describe the device. >> possibly it woudl hav ehte same result in both cases, but I don't know for >> sure that >> it works for root device.. you'd have to test. >> >> > I would recommend a UFS label instead. gpart labels are kind of fragile > and easy to mess up. My previous employer has been shipping systems where > the root fs is specified in fstab via a UFS label for years and it never > gave us a problems. +100 And FWIW as Stefano discovered later, NANO_LABEL does just that (use UFS labels). The only unfortunate thing is that nanobsd uses a NUL string by default: grep NANO_LABEL tools/tools/nanobsd/defaults.sh tools/tools/nanobsd/defaults.sh:NANO_LABEL="" tools/tools/nanobsd/defaults.sh: echo newfs ${NANO_NEWFS} ${NANO_LABEL:+-L${NANO_LABEL}${lbl}} ${dev} tools/tools/nanobsd/defaults.sh: newfs ${NANO_NEWFS} ${NANO_LABEL:+-L${NANO_LABEL}${lbl}} ${dev} tools/tools/nanobsd/defaults.sh: if [ ! -z ${NANO_LABEL} ]; then tools/tools/nanobsd/defaults.sh: tunefs -L ${NANO_LABEL}"s2a" /dev/${MD}s2a tools/tools/nanobsd/defaults.sh: # Override user's NANO_DRIVE if they specified a NANO_LABEL tools/tools/nanobsd/defaults.sh: [ ! -z "${NANO_LABEL}" ] && NANO_DRIVE="ufs/${NANO_LABEL}" The default NANO_DRIVE is useless though -- the old ata(4) stack is dead: 95 # The drive name of the media at runtime 96 NANO_DRIVE=ad0 Cheers, -NGie From owner-freebsd-current@freebsd.org Wed Sep 16 00:51:48 2015 Return-Path: Delivered-To: freebsd-current@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 7813D9CD3B1 for ; Wed, 16 Sep 2015 00:51:48 +0000 (UTC) (envelope-from stevek@juniper.net) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 3B8D512F1 for ; Wed, 16 Sep 2015 00:51:48 +0000 (UTC) (envelope-from stevek@juniper.net) Received: by mailman.ysv.freebsd.org (Postfix) id 3A6709CD3B0; Wed, 16 Sep 2015 00:51:48 +0000 (UTC) Delivered-To: current@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 39F7B9CD3AF for ; Wed, 16 Sep 2015 00:51:48 +0000 (UTC) (envelope-from stevek@juniper.net) Received: from na01-bn1-obe.outbound.protection.outlook.com (mail-bn1bn0105.outbound.protection.outlook.com [157.56.110.105]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (Client CN "mail.protection.outlook.com", Issuer "MSIT Machine Auth CA 2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 9466412EB; Wed, 16 Sep 2015 00:51:46 +0000 (UTC) (envelope-from stevek@juniper.net) Received: from BY1PR0501CA0040.namprd05.prod.outlook.com (10.162.139.50) by DM2PR05MB784.namprd05.prod.outlook.com (10.141.179.155) with Microsoft SMTP Server (TLS) id 15.1.262.15; Wed, 16 Sep 2015 00:51:44 +0000 Received: from BL2FFO11FD006.protection.gbl (2a01:111:f400:7c09::182) by BY1PR0501CA0040.outlook.office365.com (2a01:111:e400:4821::50) with Microsoft SMTP Server (TLS) id 15.1.274.16 via Frontend Transport; Wed, 16 Sep 2015 00:51:44 +0000 Authentication-Results: spf=softfail (sender IP is 66.129.239.18) smtp.mailfrom=juniper.net; FreeBSD.org; dkim=none (message not signed) header.d=none;FreeBSD.org; dmarc=none action=none header.from=juniper.net; Received-SPF: SoftFail (protection.outlook.com: domain of transitioning juniper.net discourages use of 66.129.239.18 as permitted sender) Received: from p-emfe01b-sac.jnpr.net (66.129.239.18) by BL2FFO11FD006.mail.protection.outlook.com (10.173.161.2) with Microsoft SMTP Server (TLS) id 15.1.262.18 via Frontend Transport; Wed, 16 Sep 2015 00:51:43 +0000 Received: from stevek-ubuntu.jnpr.net (172.25.4.171) by p-emfe01b-sac.jnpr.net (172.24.192.21) with Microsoft SMTP Server id 14.3.123.3; Tue, 15 Sep 2015 17:51:42 -0700 Date: Tue, 15 Sep 2015 20:51:34 -0400 From: Steve Kiernan To: Gleb Smirnoff CC: , , Subject: Re: r286727 breaks geom_md.ko loading Message-ID: <20150915205134.192678ef@stevek-ubuntu.jnpr.net> In-Reply-To: <20150916000019.GH1023@FreeBSD.org> References: <20150916000019.GH1023@FreeBSD.org> Organization: Juniper Networks Inc. X-Mailer: Claws Mail 3.11.1 (GTK+ 2.24.27; x86_64-pc-linux-gnu) MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit X-EOPAttributedMessage: 0 X-Microsoft-Exchange-Diagnostics: 1; BL2FFO11FD006; 1:w8JISbm+MD44yOOFW7Cm0Ur5Q2ifk0l4khOaFcpsbEZf2I5EVMKvuJO1xYgJ/5lVL1271yAIsj7gzMPuSrnCcMLdiuVCLWYYgPi7As3TQx8VV31Rm+kcu2derqrfuWy+7WNOrSn/8rFszPXRbVn2XSI/gCTp/Ohl+QJ7jnYCx6osqQ2BjJ4NeIvtsoy9TUVz15zovp2gO9e6j3jITG4JsQKJ3a8gtD4EFff7OzK8zjBjSLSj9Ug2XG6osGJGagQU5BQvzOvjek0f6q/FtgbfXAx1pHsCVo7RSS+8kTZNqxUQf4rangEtkEKvcUEf066foc97bKUInDpPuXvOQThsJA== X-Forefront-Antispam-Report: CIP:66.129.239.18; CTRY:US; IPV:NLI; EFV:NLI; SFV:NSPM; SFS:(10019020)(6009001)(2980300002)(24454002)(189002)(199003)(104016003)(33646002)(68736005)(53416004)(450100001)(19580405001)(5007970100001)(77096005)(77156002)(5001830100001)(4001540100001)(97736004)(106466001)(81156007)(50466002)(105596002)(5003600100002)(6806004)(47776003)(23726002)(62966003)(87936001)(2950100001)(46102003)(5001960100002)(50986999)(110136002)(50226001)(5001860100001)(46406003)(86362001)(69596002)(11100500001)(92566002)(76176999)(64706001)(189998001)(19580395003); DIR:OUT; SFP:1102; SCL:1; SRVR:DM2PR05MB784; H:p-emfe01b-sac.jnpr.net; FPR:; SPF:SoftFail; PTR:InfoDomainNonexistent; MX:1; A:1; LANG:en; X-Microsoft-Exchange-Diagnostics: 1; DM2PR05MB784; 2:jYmngkQuGRYUG5HGJtcCNgw4nDVqZeXTeGOfYVC25CI/Z9Hw4mvQJlkn4qAvonXd3+xHYC1DeOrWd9uDOFTG5wTWcLFvuLN6Ocxd4Hc6/Apo0+q88hNawET97zAN3MjTuh/vCiB59dYgJBMAmZ1to/4q0dsASByFYy7CU78tvlQ=; 3:tQBJCJJ91ey7tFjdD05g6AnkJChB25qf2FYeycFodqvCNfxMz9/8vmN9+MSI2XO19hJOnbtbhoPaXDtcquXfIkJa3Ydf7rwpfksDwi7zOc5HlM8H+uNE8s7vUdykhwtzekO8s10322BzAH2UhaogaLVCPCN/j8Jm18f7X4PiXyTeiargg4vKbVBV6K0MjRbx6Iuocfk1xZZ2MLLW9ax32lku8m6xPwFzlZziDV7eCWY=; 25:ZHw2CLgnkiRaAqTqeI0ndmqr1U4uy3shrU1x0zjBIDVwvOkFs9mwARwZpwLOuJq4+2NcnuuCSiTp4KAS84eR5RGDdzKB03aDY3C+5yEfUEshlco9gXCsvRTdiTKn9eVKTs6HtCP9d7tqJ+NJmFJCkb62V//YnODwrizZMbJ48hTtFBShRPwKfk6U3KJqvrRVshupMsaJ1g/K3obIIDt0QUTUw1OXHo/z8A+94sXEUL5/FrtDNFFsybN8b4r0l33emBkcCqmJskCeM5iQBomBtA== X-Microsoft-Antispam: UriScan:;BCL:0;PCL:0;RULEID:;SRVR:DM2PR05MB784; X-Microsoft-Exchange-Diagnostics: 1; DM2PR05MB784; 20:Oxn36R5gXGhNb07V/84RMDv/653RkXMGm01M6PIrg3CsOyrxbyghHJiqUZT0Um9OhfmkhatevYtJAeUKgYwl9s6X0ZdBOk4j/NmQwkn60wz2PCRoA3ZOAXbu4rsQcs7ZBElgpihCmp8t0fQEEJbK90rrsj2tVd+fAXMyUnXdqkjCWwZBBcinILYNr4kYmCHIS+FWDevakG/Y0NHR1ohi/O8ub5XjePKHmFwKAcZLk6JNnCDLzV77gzN2k9lu+FJhhKS79ElpQ0KYQMyY6hk4avHU2hwClBvfN0EQSDNBU7WyK8Hv4LUqHOwB22Gc7RZ9FWPrXsaB3MQPJndwozFnPHub2QKwVSeNHenTGS3r7rK4iE5wj6NJNG2NnaixCk7m/LzwRagJGb407USlG9/LCwWx+moiI+K6PoB736BoO/YmrqBiVfJC4ZnKHEnLL0yeLHqvrlNifEwq0v92vzfxjUDq56vS/37JQPwSu0j+1RTDOcIiLvixmaNTErYz/9VF; 4:Q98WqxewqKB4QbegC4YbZUzYG7rYjqLSaQDV36ti5owIvkCEmYV4d3BHIcWPUNYvKQRvTSYpoRfG3FX3Xmp3dDrWFGtdrd3limlsvnZuelMtG0Ie+y2lxXmVPuJpQ+I5DAexaSn4yFcnYI4BsHTHHPsWHGrB3jPBQwotALAsRrF5flPqJlxhLYj4SjEgcC3q7IXxvsMZExUsYGxLFhG5FT5ICBnwVRS/JlSihb5DwkHMx+GO2TQ1W0MS8eUh8BRiU5+xY+UDbgLbDZe6jTkg5KBL+CbbBzV752oJH/rMUvidNjH3ugTdxAPCHs9lqitQfFvAfihiNBEbx+Rj21GzzEA7ySUmoD9SpOVIc128blY= X-Microsoft-Antispam-PRVS: X-Exchange-Antispam-Report-Test: UriScan:; X-Exchange-Antispam-Report-CFA-Test: BCL:0; PCL:0; RULEID:(601004)(8121501046)(520075)(5005006)(520078)(3002001); SRVR:DM2PR05MB784; BCL:0; PCL:0; RULEID:; SRVR:DM2PR05MB784; X-Forefront-PRVS: 07013D7479 X-Microsoft-Exchange-Diagnostics: =?us-ascii?Q?1; DM2PR05MB784; 23:xTilz2YtLldvN4R3A5mbO/Q08jg5xnPIYsJp41yyM5?= =?us-ascii?Q?xm9Vct2f6AN3DNeBiRCpGYFPIhaqiAr7ZLan4+m8NiMmj4YNen8XqDd+tWIt?= =?us-ascii?Q?JC+po2nYIPjDmyPPwhcD0vUWZ0WMNnYdpBwhid66XxIS67X51hnkfgQE8Nu/?= =?us-ascii?Q?26imY3/bUEIS6vngqwbTz2eYq7RR2iqXkG7G31YUUwryXmD2NyD+9fgzIFpD?= =?us-ascii?Q?gEH45OBmXuPSF1Gc7cQSAJ4gJp1LtJfkBG30bLZ1bRrXivUz/hzSgMM1X4a/?= =?us-ascii?Q?NpkdtSIHjAhtPDOnuMkoMwW+hBpkdnlkONsCn1jgaV8NCAF84puJkD1/iGSh?= =?us-ascii?Q?SlzYuUKZivbrRmXpV0OouT9VbAYb4fps9iLgdRRMnx7ynGArKxdi4vmPqzgq?= =?us-ascii?Q?1RMr5qknwJ0uJH2hJh+1TmVB8kgS94qUlkXV5sFS77YLFcctJ0CcEgMzpsLn?= =?us-ascii?Q?4teKr5vhyrtoI0uQZXEH6YfTBetI4J4Uvx5n6WqyaVIm1FSLV+5k/Tbf6Rtz?= =?us-ascii?Q?RfYDmzsGNgp5wgMUjxoH9dTLZJkKh21R4jvincI2D+/5mfE/jnjTquxuIFny?= =?us-ascii?Q?4gHDJ+m0MXiz8/rIGEJs09lZm2ow8H6GBX0+bWvfyP27NrHB4NrDT1UzEVuP?= =?us-ascii?Q?O0v1GP2dMtuxBUpnzybhw1RdKw8aPcksKEy/C1rtB94NXqX++Rc1MGz77Zvg?= =?us-ascii?Q?4RH7lH4MLGpd3XtyxqdAXNM8tsBDRb9zaCAOJEVuLCTxpRbd0CTeU3cu2raf?= =?us-ascii?Q?HrtptI58tSBPQOLqLlbrQ9XUImLiEcU8rGALQ8fgdWBHrfusxHaf6siqY1T8?= =?us-ascii?Q?nieN4Mu+6RrqqbnmiD2OxqM2Wp2a2tTInNOG3oFGVBVvTSkwKNqOhtkNnnnO?= =?us-ascii?Q?z0dWETdJy5IfUPRf4G8EqV/fB5N15xI+uoEHRcgaSNCyhDNSt7pU8SDwPdql?= =?us-ascii?Q?nZm5SgVHbVMrG3EsKUBlBTKut/VhCs3jK83stioW61itXniiiNwbEAbs4GfF?= =?us-ascii?Q?ROW1zTMJftZw9A4YGD9N075xXlZLpwa87XKIsaTkq2kDGwkjk/hBkXxnxP2A?= =?us-ascii?Q?xp8lwPIz0SGRXXZAsXxkAyqnzwcVonUbxd+AWxoiyxYZXj9lh/tCeF3KBj2n?= =?us-ascii?Q?7FpvhJBtBblw23CTLr6dQ0Krh98UBcOGvYKuQHwJdKqKEIgLMaNm6dXVXYNn?= =?us-ascii?Q?3Aw0KnzD2ha3Q=3D?= X-Microsoft-Exchange-Diagnostics: 1; DM2PR05MB784; 5:1TZH9sZrwltAIqI8AQAKiGEAOuhtSrh5zqgQ30nJYaoVt8OUEI93ErQHesVZ3YkclItA7Du0Jjwctdb2f6IA55mL4ip051/mMrnFJkCmXF/380hAWT+cb4/T02WDty2zZ8ZtIhcLwY5fSApnzGxCNw==; 24:46IxIU4w/WsCSm2QyTB7XxOuahpqyAMLzx7+lI6myykYFJT5RkDoS1SU+5Gqem6cbWp6HvAYn9Ce60R9Uf+t2sAbliiW/LZOGU5NTjttTW8=; 20:ZjAimSo6DFgj9gUaK5H1Vgj9mnWujEBdfCteAPgSAR1UHAyNKRiaxzOYkKem1OIn3LdaKjfA+eRh/QjaKHUe4Q== SpamDiagnosticOutput: 1:23 SpamDiagnosticMetadata: NSPM X-OriginatorOrg: juniper.net X-MS-Exchange-CrossTenant-OriginalArrivalTime: 16 Sep 2015 00:51:43.6998 (UTC) X-MS-Exchange-CrossTenant-Id: bea78b3c-4cdb-4130-854a-1d193232e5f4 X-MS-Exchange-CrossTenant-OriginalAttributedTenantConnectingIp: TenantId=bea78b3c-4cdb-4130-854a-1d193232e5f4; Ip=[66.129.239.18]; Helo=[p-emfe01b-sac.jnpr.net] X-MS-Exchange-CrossTenant-FromEntityHeader: HybridOnPrem X-MS-Exchange-Transport-CrossTenantHeadersStamped: DM2PR05MB784 X-Mailman-Approved-At: Wed, 16 Sep 2015 02:47:47 +0000 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 16 Sep 2015 00:51:48 -0000 On Wed, 16 Sep 2015 03:00:19 +0300 Gleb Smirnoff wrote: > Hi! > > There is regression after r286727. Our dynamic kernel linker doesn't > support weak symbols, so the geom_md.ko can no longer be loaded dynamically > neither from loader nor at runtime. Having it statically in kernel is > the only working option. The question in that case would be does it make sense to allow MD_ROOT when building md as a kernel module? -Steve From owner-freebsd-current@freebsd.org Wed Sep 16 02:59:49 2015 Return-Path: Delivered-To: freebsd-current@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 4FFEC9CE4B6 for ; Wed, 16 Sep 2015 02:59:49 +0000 (UTC) (envelope-from gljennjohn@gmail.com) Received: from mail-wi0-x22e.google.com (mail-wi0-x22e.google.com [IPv6:2a00:1450:400c:c05::22e]) (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 DD747163E for ; Wed, 16 Sep 2015 02:59:48 +0000 (UTC) (envelope-from gljennjohn@gmail.com) Received: by wicgb1 with SMTP id gb1so53954616wic.1 for ; Tue, 15 Sep 2015 19:59:47 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=date:from:to:cc:subject:message-id:in-reply-to:references:reply-to :mime-version:content-type:content-transfer-encoding; bh=jAMM6QgpD6F5upI/zd8Ua5T+J4wR/kWH3AIodA8432o=; b=ffHeWEDXRGZmdEYI8JAGyQp/FONfrtRQL6GwBlSF+9rOsN2I3JGtud/YeiGgrQAYLX djZgjpaN4mzGWGkWSxT989+mt6J0lqEQBpnQQcQh0/1gUWKeMT/Qn7D3MOt+EMkfNCLG M2wApeAq6XD/Wx2GjpSB/Z0d5LuOJPafGDXdXFS20HGLXkodtDixljLK5L5gZBaPrD3C PbiS/I/XsGeSbzjRaGU7XlyCyo5/C8m//lQG0WrMT++1BKnjn7YG6nqmjWMtsy4mkG1l BgdFuY+ukwo+EB1hTpI3ZzOMYc9vtXPkbH8Kkbxp1TnJSCAC/1jw4Rc4up1Rs4uyceGs zTyQ== X-Received: by 10.194.121.131 with SMTP id lk3mr16134416wjb.77.1442372387161; Tue, 15 Sep 2015 19:59:47 -0700 (PDT) Received: from ernst.home (p578E16AA.dip0.t-ipconnect.de. [87.142.22.170]) by smtp.gmail.com with ESMTPSA id lz10sm23984814wjb.48.2015.09.15.19.59.46 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 15 Sep 2015 19:59:46 -0700 (PDT) Date: Wed, 16 Sep 2015 04:59:40 +0200 From: Gary Jennejohn To: Brendan Sechter Cc: "freebsd-current@freebsd.org" Subject: Re: FreeBSD 11.0-CURRENT Single User Keymap Message-ID: <20150916045940.77f5ec2d@ernst.home> In-Reply-To: References: Reply-To: gljennjohn@gmail.com X-Mailer: Claws Mail 3.12.0 (GTK+ 2.24.28; amd64-portbld-freebsd11.0) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 16 Sep 2015 02:59:49 -0000 On Tue, 15 Sep 2015 19:32:35 +0900 Brendan Sechter wrote: > When compiling a FreeBSD 11.0-CURRENT kernel, what is required to change the keymap used in single user mode? __I originally asked this question on the FreeBSD forums, but was bounced to the mailing list because CURRENT is an unsupported version. > > I have read an old forum thread on this topic. I have also read the__atkbd(4)__and__ukbd(4)__man pages. The relevant parts of my kernel configuration are as follows: > > #__----------__----------__----------__---------- > include GENERIC > ident MY_KERNEL > > # AT Keyboard > device atkbdc > options ATKBD_DFLT_KEYMAP > makeoptions ATKBD_DFLT_KEYMAP=jp.106 > device atkbd > > # USB Keyboard > device ukbd > options UKBD_DFLT_KEYMAP > makeoptions UKBD_DFLT_KEYMAP=jp.106 > > # everything else > # ... > #__----------__----------__----------__---------- > > So far as I can tell, these options should be working. I am using a 106 key Japanese keyboard. Single user mode appears to use the keymap for a 101 key standard US layout. I have tried the following values: > - jp > - jp.106 > - jp.106.kbd (not tried recently) > > Finally, this is a FreeBSD VM running in VirtualBox on OSX. I am 99% sure I am having the same problem on my physical machines. The specific driver almost certainly depends on the hardware. > Try setting keymap in /etc/rc.conf to the entry you want. Just putting keymap="jp.106" there should work. Umm, but this is for syscons. Not sure what you may need for vt, which I don't use. -- Gary Jennejohn From owner-freebsd-current@freebsd.org Wed Sep 16 05:10:12 2015 Return-Path: Delivered-To: freebsd-current@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 0AE719C26DD for ; Wed, 16 Sep 2015 05:10:12 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id E30161E30 for ; Wed, 16 Sep 2015 05:10:11 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: by mailman.ysv.freebsd.org (Postfix) id E05E49C26DB; Wed, 16 Sep 2015 05:10:11 +0000 (UTC) Delivered-To: current@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 DFE439C26DA for ; Wed, 16 Sep 2015 05:10:11 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from kib.kiev.ua (kib.kiev.ua [IPv6:2001:470:d5e7:1::1]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 72E001E2D; Wed, 16 Sep 2015 05:10:11 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from tom.home (kostik@localhost [127.0.0.1]) by kib.kiev.ua (8.15.2/8.15.2) with ESMTPS id t8G5A6nF078259 (version=TLSv1 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO); Wed, 16 Sep 2015 08:10:06 +0300 (EEST) (envelope-from kostikbel@gmail.com) DKIM-Filter: OpenDKIM Filter v2.10.3 kib.kiev.ua t8G5A6nF078259 Received: (from kostik@localhost) by tom.home (8.15.2/8.15.2/Submit) id t8G5A5Z4078254; Wed, 16 Sep 2015 08:10:05 +0300 (EEST) (envelope-from kostikbel@gmail.com) X-Authentication-Warning: tom.home: kostik set sender to kostikbel@gmail.com using -f Date: Wed, 16 Sep 2015 08:10:05 +0300 From: Konstantin Belousov To: Gleb Smirnoff Cc: marcel@FreeBSD.org, Steve Kiernan , brooks@FreeBSD.org, current@FreeBSD.org Subject: Re: r286727 breaks geom_md.ko loading Message-ID: <20150916051005.GF67105@kib.kiev.ua> References: <20150916000019.GH1023@FreeBSD.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20150916000019.GH1023@FreeBSD.org> User-Agent: Mutt/1.5.24 (2015-08-30) X-Spam-Status: No, score=-2.0 required=5.0 tests=ALL_TRUSTED,BAYES_00, DKIM_ADSP_CUSTOM_MED,FREEMAIL_FROM,NML_ADSP_CUSTOM_MED autolearn=no autolearn_force=no version=3.4.1 X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on tom.home X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 16 Sep 2015 05:10:12 -0000 On Wed, Sep 16, 2015 at 03:00:19AM +0300, Gleb Smirnoff wrote: > Hi! > > There is regression after r286727. Our dynamic kernel linker doesn't > support weak symbols, so the geom_md.ko can no longer be loaded dynamically > neither from loader nor at runtime. Having it statically in kernel is > the only working option. Perhaps, something could be fixed in the dynamic linker ? I checked both i386 and amd64, and on both arches I can load geom_md.ko. On the other hand, I do not use preloaded mfs images. Can you explain how to reproduce the issue, and what linker is affected ? Note that we have two kernel dynamic linkers, one is used on amd64 and mips, second one is for all other architectures. From owner-freebsd-current@freebsd.org Wed Sep 16 05:21:21 2015 Return-Path: Delivered-To: freebsd-current@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 47B1D9C2E96 for ; Wed, 16 Sep 2015 05:21:21 +0000 (UTC) (envelope-from sgeos@hotmail.com) Received: from BAY004-OMC2S4.hotmail.com (bay004-omc2s4.hotmail.com [65.54.190.79]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (Client CN "*.outlook.com", Issuer "MSIT Machine Auth CA 2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 35B6713B9 for ; Wed, 16 Sep 2015 05:21:20 +0000 (UTC) (envelope-from sgeos@hotmail.com) Received: from BAY182-W2 ([65.54.190.125]) by BAY004-OMC2S4.hotmail.com over TLS secured channel with Microsoft SMTPSVC(7.5.7601.23008); Tue, 15 Sep 2015 22:20:15 -0700 X-TMN: [MWjnOYIlXw0yTlIj26F72llW9+UNoZ66] X-Originating-Email: [sgeos@hotmail.com] Message-ID: From: Brendan Sechter To: "gljennjohn@gmail.com" CC: "freebsd-current@freebsd.org" Subject: RE: FreeBSD 11.0-CURRENT Single User Keymap Date: Wed, 16 Sep 2015 14:20:15 +0900 Importance: Normal In-Reply-To: <20150916045940.77f5ec2d@ernst.home> References: , <20150916045940.77f5ec2d@ernst.home> Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-OriginalArrivalTime: 16 Sep 2015 05:20:15.0902 (UTC) FILETIME=[5EDEF3E0:01D0F03F] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 16 Sep 2015 05:21:21 -0000 > Date: Wed=2C 16 Sep 2015 04:59:40 +0200=0A= > From: gljennjohn@gmail.com=0A= > To: sgeos@hotmail.com=0A= > CC: freebsd-current@freebsd.org=0A= > Subject: Re: FreeBSD 11.0-CURRENT Single User Keymap=0A= >=0A= > On Tue=2C 15 Sep 2015 19:32:35 +0900=0A= > Brendan Sechter wrote:=0A= >=0A= >> When compiling a FreeBSD 11.0-CURRENT kernel=2C what is required to chan= ge the keymap used in single user mode? __I originally asked this question = on the FreeBSD forums=2C but was bounced to the mailing list because CURREN= T is an unsupported version.=0A= >>=0A= >> I have read an old forum thread on this topic. I have also read the__atk= bd(4)__and__ukbd(4)__man pages. The relevant parts of my kernel configurati= on are as follows:=0A= >>=0A= >> &__----------__----------__----------__----------=0A= >> include GENERIC=0A= >> ident MY_KERNEL=0A= >>=0A= >> & AT Keyboard=0A= >> device atkbdc=0A= >> options ATKBD_DFLT_KEYMAP=0A= >> makeoptions ATKBD_DFLT_KEYMAP=3Djp.106=0A= >> device atkbd=0A= >>=0A= >> & USB Keyboard=0A= >> device ukbd=0A= >> options UKBD_DFLT_KEYMAP=0A= >> makeoptions UKBD_DFLT_KEYMAP=3Djp.106=0A= >>=0A= >> & everything else=0A= >> & ...=0A= >> &__----------__----------__----------__----------=0A= >>=0A= >> So far as I can tell=2C these options should be working. I am using a 10= 6 key Japanese keyboard. Single user mode appears to use the keymap for a 1= 01 key standard US layout. I have tried the following values:=0A= >> - jp=0A= >> - jp.106=0A= >> - jp.106.kbd (not tried recently)=0A= >>=0A= >> Finally=2C this is a FreeBSD VM running in VirtualBox on OSX. I am 99% s= ure I am having the same problem on my physical machines. The specific driv= er almost certainly depends on the hardware.=0A= >>=0A= >=0A= > Try setting keymap in /etc/rc.conf to the entry you want. Just=0A= > putting keymap=3D"jp.106" there should work.=0A= =0A= My /etc/rc.conf already contained keymap=3D"jp".=0A= Changing it to keymap=3D"jp.106" did not resolve the issue.=0A= The keymap is correct in multi user mode=2C but not single user mode.=0A= =0A= I have never been able to get single user mode to boot with anything other = than a=A0101 key standard US layout.=0A= If I recall correctly=2C starting devd would load the /etc/rc.conf keymap i= n previous versions=2C but I am not 100% sure of that.=0A= =0A= Running kbdmap after booting into single user mode gives some interesting b= ut expected output.=0A= # kbdmap=0A= lang_default =3D en=0A= dialect =3D en=0A= lang_abk =3D en=0A= Could not open temporary file "/tmp/_kbd_lang.R4J6"=0A= #=0A= =0A= I can change the keymap by remounting a read/write filesystem and running k= bdmap.=0A= This is not ideal.=0A= # mount -u /=0A= # kbdmap=0A= [interactively select Japanese 106 keyboard layout]=0A= keymap=3D"jp.kbd"=0A= #=0A= =0A= I only found one solution to this issue in Japanese=2C but it requires remo= unting and manually setting the keymap.=0A= Are people booting into single user mode with working European keymaps?=0A= Is it possible the jp keymap has some quirk that is causing it to be reject= ed when booting in single user mode?=0A= =0A= If it matters=2C this system started as a minimal install using=A0FreeBSD-1= 0.2-RELEASE-amd64-disc1.iso.=0A= I tracked 11.0-CURRENT immediately after performing a minimum install and r= ebuilt everything a couple of times.=0A= =0A= > Umm=2C but this is for syscons. Not sure what you may need for vt=2C=0A= > which I don't use.=0A= =0A= Multiuser works=2C single user does not.=0A= =0A= Single user (default standard US keymap):=0A= # tty=0A= /dev/console=0A= =0A= Multi user (correct /etc/rc.conf keymap):=0A= # tty=0A= /dev/ttyv0=0A= =0A= Multi user SSH=A0(correct /etc/rc.conf keymap):=0A= $ su=0A= # tty=0A= /dev/pts/0=0A= =0A= > --=0A= > Gary Jennejohn=0A= > _______________________________________________=0A= > freebsd-current@freebsd.org mailing list=0A= > https://lists.freebsd.org/mailman/listinfo/freebsd-current=0A= > To unsubscribe=2C send any mail to "freebsd-current-unsubscribe@freebsd.o= rg"=0A= = From owner-freebsd-current@freebsd.org Wed Sep 16 10:48:13 2015 Return-Path: Delivered-To: freebsd-current@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 255029C2AFC for ; Wed, 16 Sep 2015 10:48:13 +0000 (UTC) (envelope-from jenkins-admin@FreeBSD.org) Received: from jenkins-9.freebsd.org (jenkins-9.freebsd.org [8.8.178.209]) by mx1.freebsd.org (Postfix) with ESMTP id 13CD215DA; Wed, 16 Sep 2015 10:48:13 +0000 (UTC) (envelope-from jenkins-admin@FreeBSD.org) Received: from jenkins-9.freebsd.org (localhost [127.0.0.1]) by jenkins-9.freebsd.org (Postfix) with ESMTP id 4E8EDB35; Wed, 16 Sep 2015 10:48:11 +0000 (UTC) Date: Wed, 16 Sep 2015 10:48:10 +0000 (GMT) From: jenkins-admin@FreeBSD.org To: jenkins-admin@FreeBSD.org, freebsd-current@FreeBSD.org Message-ID: <1332394184.22.1442400490800.JavaMail.jenkins@jenkins-9.freebsd.org> In-Reply-To: <1347810262.20.1442384746763.JavaMail.jenkins@jenkins-9.freebsd.org> References: <1347810262.20.1442384746763.JavaMail.jenkins@jenkins-9.freebsd.org> Subject: FreeBSD_HEAD-tests - Build #1432 - Fixed MIME-Version: 1.0 X-Jenkins-Job: FreeBSD_HEAD-tests X-Jenkins-Result: SUCCESS Precedence: bulk Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.20 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.20 List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 16 Sep 2015 10:48:13 -0000 FreeBSD_HEAD-tests - Build #1432 - Fixed: Build information: https://jenkins.FreeBSD.org/job/FreeBSD_HEAD-tests/1432/ Full change log: https://jenkins.FreeBSD.org/job/FreeBSD_HEAD-tests/1432/changes Full build log: https://jenkins.FreeBSD.org/job/FreeBSD_HEAD-tests/1432/console Change summaries: No changes From owner-freebsd-current@freebsd.org Wed Sep 16 13:15:30 2015 Return-Path: Delivered-To: freebsd-current@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 DDC909CD76F for ; Wed, 16 Sep 2015 13:15:30 +0000 (UTC) (envelope-from glebius@FreeBSD.org) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id C39281F39 for ; Wed, 16 Sep 2015 13:15:30 +0000 (UTC) (envelope-from glebius@FreeBSD.org) Received: by mailman.ysv.freebsd.org (Postfix) id C30359CD76D; Wed, 16 Sep 2015 13:15:30 +0000 (UTC) Delivered-To: current@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 C29B49CD76B for ; Wed, 16 Sep 2015 13:15:30 +0000 (UTC) (envelope-from glebius@FreeBSD.org) Received: from cell.glebius.int.ru (glebius.int.ru [81.19.69.10]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "cell.glebius.int.ru", Issuer "cell.glebius.int.ru" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id E0EC61F38; Wed, 16 Sep 2015 13:15:28 +0000 (UTC) (envelope-from glebius@FreeBSD.org) Received: from cell.glebius.int.ru (localhost [127.0.0.1]) by cell.glebius.int.ru (8.15.2/8.15.2) with ESMTPS id t8GDFFCl011618 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Wed, 16 Sep 2015 16:15:15 +0300 (MSK) (envelope-from glebius@FreeBSD.org) Received: (from glebius@localhost) by cell.glebius.int.ru (8.15.2/8.15.2/Submit) id t8GDFFEd011617; Wed, 16 Sep 2015 16:15:15 +0300 (MSK) (envelope-from glebius@FreeBSD.org) X-Authentication-Warning: cell.glebius.int.ru: glebius set sender to glebius@FreeBSD.org using -f Date: Wed, 16 Sep 2015 16:15:15 +0300 From: Gleb Smirnoff To: Konstantin Belousov Cc: marcel@FreeBSD.org, Steve Kiernan , brooks@FreeBSD.org, current@FreeBSD.org Subject: Re: r286727 breaks geom_md.ko loading Message-ID: <20150916131515.GL1023@glebius.int.ru> References: <20150916000019.GH1023@FreeBSD.org> <20150916051005.GF67105@kib.kiev.ua> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20150916051005.GF67105@kib.kiev.ua> User-Agent: Mutt/1.5.23 (2014-03-12) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 16 Sep 2015 13:15:31 -0000 On Wed, Sep 16, 2015 at 08:10:05AM +0300, Konstantin Belousov wrote: K> > There is regression after r286727. Our dynamic kernel linker doesn't K> > support weak symbols, so the geom_md.ko can no longer be loaded dynamically K> > neither from loader nor at runtime. Having it statically in kernel is K> > the only working option. K> K> Perhaps, something could be fixed in the dynamic linker ? K> K> I checked both i386 and amd64, and on both arches I can load geom_md.ko. K> On the other hand, I do not use preloaded mfs images. Can you explain K> how to reproduce the issue, and what linker is affected ? Note that we K> have two kernel dynamic linkers, one is used on amd64 and mips, second one K> is for all other architectures. To reproduce you need just a vanilla head, a kernel that doesn't have 'device md' in it, and run kldload geom_md.ko. Does that work for you? -- Totus tuus, Glebius. From owner-freebsd-current@freebsd.org Wed Sep 16 13:42:56 2015 Return-Path: Delivered-To: freebsd-current@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 01D7D9CE654 for ; Wed, 16 Sep 2015 13:42:56 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id D8D0710C5 for ; Wed, 16 Sep 2015 13:42:55 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: by mailman.ysv.freebsd.org (Postfix) id D84039CE653; Wed, 16 Sep 2015 13:42:55 +0000 (UTC) Delivered-To: current@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 D7D009CE652 for ; Wed, 16 Sep 2015 13:42:55 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from kib.kiev.ua (kib.kiev.ua [IPv6:2001:470:d5e7:1::1]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4DC2D10C4; Wed, 16 Sep 2015 13:42:55 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from tom.home (kostik@localhost [127.0.0.1]) by kib.kiev.ua (8.15.2/8.15.2) with ESMTPS id t8GDgnlH012795 (version=TLSv1 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO); Wed, 16 Sep 2015 16:42:49 +0300 (EEST) (envelope-from kostikbel@gmail.com) DKIM-Filter: OpenDKIM Filter v2.10.3 kib.kiev.ua t8GDgnlH012795 Received: (from kostik@localhost) by tom.home (8.15.2/8.15.2/Submit) id t8GDgnL9012794; Wed, 16 Sep 2015 16:42:49 +0300 (EEST) (envelope-from kostikbel@gmail.com) X-Authentication-Warning: tom.home: kostik set sender to kostikbel@gmail.com using -f Date: Wed, 16 Sep 2015 16:42:49 +0300 From: Konstantin Belousov To: Gleb Smirnoff Cc: marcel@FreeBSD.org, Steve Kiernan , brooks@FreeBSD.org, current@FreeBSD.org Subject: Re: r286727 breaks geom_md.ko loading Message-ID: <20150916134249.GG67105@kib.kiev.ua> References: <20150916000019.GH1023@FreeBSD.org> <20150916051005.GF67105@kib.kiev.ua> <20150916131515.GL1023@glebius.int.ru> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20150916131515.GL1023@glebius.int.ru> User-Agent: Mutt/1.5.24 (2015-08-30) X-Spam-Status: No, score=-2.0 required=5.0 tests=ALL_TRUSTED,BAYES_00, DKIM_ADSP_CUSTOM_MED,FREEMAIL_FROM,NML_ADSP_CUSTOM_MED autolearn=no autolearn_force=no version=3.4.1 X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on tom.home X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 16 Sep 2015 13:42:56 -0000 On Wed, Sep 16, 2015 at 04:15:15PM +0300, Gleb Smirnoff wrote: > On Wed, Sep 16, 2015 at 08:10:05AM +0300, Konstantin Belousov wrote: > K> > There is regression after r286727. Our dynamic kernel linker doesn't > K> > support weak symbols, so the geom_md.ko can no longer be loaded dynamically > K> > neither from loader nor at runtime. Having it statically in kernel is > K> > the only working option. > K> > K> Perhaps, something could be fixed in the dynamic linker ? > K> > K> I checked both i386 and amd64, and on both arches I can load geom_md.ko. > K> On the other hand, I do not use preloaded mfs images. Can you explain > K> how to reproduce the issue, and what linker is affected ? Note that we > K> have two kernel dynamic linkers, one is used on amd64 and mips, second one > K> is for all other architectures. > > To reproduce you need just a vanilla head, a kernel that doesn't have > 'device md' in it, and run kldload geom_md.ko. Does that work for you? Yes, it does, both on amd64 and i386. You did not said which architecture exposes your problem. Post your kernel config. From owner-freebsd-current@freebsd.org Wed Sep 16 13:50:07 2015 Return-Path: Delivered-To: freebsd-current@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 87BFF9CE93C for ; Wed, 16 Sep 2015 13:50:07 +0000 (UTC) (envelope-from glebius@FreeBSD.org) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 6A90E13A2 for ; Wed, 16 Sep 2015 13:50:07 +0000 (UTC) (envelope-from glebius@FreeBSD.org) Received: by mailman.ysv.freebsd.org (Postfix) id 67E449CE93B; Wed, 16 Sep 2015 13:50:07 +0000 (UTC) Delivered-To: current@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 4E60E9CE93A for ; Wed, 16 Sep 2015 13:50:07 +0000 (UTC) (envelope-from glebius@FreeBSD.org) Received: from cell.glebius.int.ru (glebius.int.ru [81.19.69.10]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "cell.glebius.int.ru", Issuer "cell.glebius.int.ru" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id D881713A0; Wed, 16 Sep 2015 13:50:06 +0000 (UTC) (envelope-from glebius@FreeBSD.org) Received: from cell.glebius.int.ru (localhost [127.0.0.1]) by cell.glebius.int.ru (8.15.2/8.15.2) with ESMTPS id t8GDo34V011920 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Wed, 16 Sep 2015 16:50:03 +0300 (MSK) (envelope-from glebius@FreeBSD.org) Received: (from glebius@localhost) by cell.glebius.int.ru (8.15.2/8.15.2/Submit) id t8GDo3cr011919; Wed, 16 Sep 2015 16:50:03 +0300 (MSK) (envelope-from glebius@FreeBSD.org) X-Authentication-Warning: cell.glebius.int.ru: glebius set sender to glebius@FreeBSD.org using -f Date: Wed, 16 Sep 2015 16:50:03 +0300 From: Gleb Smirnoff To: Konstantin Belousov Cc: marcel@FreeBSD.org, Steve Kiernan , brooks@FreeBSD.org, current@FreeBSD.org Subject: Re: r286727 breaks geom_md.ko loading Message-ID: <20150916135003.GM1023@glebius.int.ru> References: <20150916000019.GH1023@FreeBSD.org> <20150916051005.GF67105@kib.kiev.ua> <20150916131515.GL1023@glebius.int.ru> <20150916134249.GG67105@kib.kiev.ua> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="M/SuVGWktc5uNpra" Content-Disposition: inline In-Reply-To: <20150916134249.GG67105@kib.kiev.ua> User-Agent: Mutt/1.5.23 (2014-03-12) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 16 Sep 2015 13:50:07 -0000 --M/SuVGWktc5uNpra Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Wed, Sep 16, 2015 at 04:42:49PM +0300, Konstantin Belousov wrote: K> On Wed, Sep 16, 2015 at 04:15:15PM +0300, Gleb Smirnoff wrote: K> > On Wed, Sep 16, 2015 at 08:10:05AM +0300, Konstantin Belousov wrote: K> > K> > There is regression after r286727. Our dynamic kernel linker doesn't K> > K> > support weak symbols, so the geom_md.ko can no longer be loaded dynamically K> > K> > neither from loader nor at runtime. Having it statically in kernel is K> > K> > the only working option. K> > K> K> > K> Perhaps, something could be fixed in the dynamic linker ? K> > K> K> > K> I checked both i386 and amd64, and on both arches I can load geom_md.ko. K> > K> On the other hand, I do not use preloaded mfs images. Can you explain K> > K> how to reproduce the issue, and what linker is affected ? Note that we K> > K> have two kernel dynamic linkers, one is used on amd64 and mips, second one K> > K> is for all other architectures. K> > K> > To reproduce you need just a vanilla head, a kernel that doesn't have K> > 'device md' in it, and run kldload geom_md.ko. Does that work for you? K> K> Yes, it does, both on amd64 and i386. You did not said which architecture K> exposes your problem. Post your kernel config. It is amd64. Here is config. -- Totus tuus, Glebius. --M/SuVGWktc5uNpra Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename=THINKPAD_X1 cpu HAMMER ident THINKPAD_X1 makeoptions DEBUG=-g makeoptions WITH_CTF=1 options SCHED_ULE # ULE scheduler options PREEMPTION # Enable kernel thread preemption options INET # InterNETworking options INET6 # IPv6 communications protocols options SCTP # Stream Control Transmission Protocol options FFS # Berkeley Fast Filesystem options SOFTUPDATES # Enable FFS soft updates support options UFS_ACL # Support for access control lists options UFS_DIRHASH # Improve performance on big directories options UFS_GJOURNAL # Enable gjournal-based UFS journaling options MD_ROOT # MD is a potential root device options NFSCL # New Network Filesystem Client options NFSD # New Network Filesystem Server options NFSLOCKD # Network Lock Manager options NFS_ROOT # NFS usable as /, requires NFSCL options MSDOSFS # MSDOS Filesystem options CD9660 # ISO 9660 Filesystem options PROCFS # Process filesystem (requires PSEUDOFS) options PSEUDOFS # Pseudo-filesystem framework options GEOM_PART_GPT # GUID Partition Tables. options GEOM_LABEL # Provides labelization options COMPAT_FREEBSD32 # Compatible with i386 binaries options SCSI_DELAY=5000 # Delay (in ms) before probing SCSI options KTRACE # ktrace(1) support options STACK # stack(9) support options SYSVSHM # SYSV-style shared memory options SYSVMSG # SYSV-style message queues options SYSVSEM # SYSV-style semaphores options _KPOSIX_PRIORITY_SCHEDULING # POSIX P1003_1B real-time extensions options PRINTF_BUFR_SIZE=128 # Prevent printf output being interspersed. options KBD_INSTALL_CDEV # install a CDEV entry in /dev options HWPMC_HOOKS # Necessary kernel hooks for hwpmc(4) options KDTRACE_FRAME # Ensure frames are compiled in options KDTRACE_HOOKS # Kernel DTrace hooks options DDB_CTF options INCLUDE_CONFIG_FILE # Include this file in kernel options KDB # Enable kernel debugger support. options DDB # Support DDB. options GDB # Support remote GDB. # Make an SMP-capable kernel by default options SMP # Symmetric MultiProcessor Kernel # CPU frequency control device cpufreq # Bus support. device acpi options ACPI_DMAR device pci # ATA controllers device ahci # AHCI-compatible SATA controllers device ata # Legacy ATA/SATA controllers options ATA_STATIC_ID # Static device numbering # ATA/SCSI peripherals device scbus # SCSI bus (required for ATA/SCSI) device da # Direct Access (disks) device cd # CD device pass # Passthrough device (direct ATA/SCSI access) # atkbdc0 controls both the keyboard and the PS/2 mouse device atkbdc # AT keyboard controller device atkbd # AT keyboard device psm # PS/2 mouse device kbdmux # keyboard multiplexer device vt device vt_vga device agp # support several AGP chipsets # Serial (COM) ports device uart # Generic UART driver # Wireless NIC cards device wlan # 802.11 support options IEEE80211_DEBUG # enable debug msgs options IEEE80211_AMPDU_AGE # age frames in AMPDU reorder q's options IEEE80211_SUPPORT_MESH # enable 802.11s draft support device wlan_wep # 802.11 WEP support device wlan_ccmp # 802.11 CCMP support device wlan_tkip # 802.11 TKIP support device wlan_amrr # AMRR transmit rate control algorithm device iwn # Intel 4965/1000/5000/6000 wireless NICs. # Pseudo devices. device loop # Network loopback device random # Entropy device device ether # Ethernet support device vlan # 802.1Q VLAN support device tun # Packet tunnel. device pty # BSD-style compatibility pseudo ttys device firmware # firmware assist module device bpf # Berkeley packet filter # Sound support device sound # Generic sound driver (required) device snd_hda # Intel High Definition Audio device coretemp device crypto device cryptodev device aesni --M/SuVGWktc5uNpra-- From owner-freebsd-current@freebsd.org Wed Sep 16 13:57:44 2015 Return-Path: Delivered-To: freebsd-current@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 B51F99CECA3 for ; Wed, 16 Sep 2015 13:57:44 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 9759A1931 for ; Wed, 16 Sep 2015 13:57:44 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: by mailman.ysv.freebsd.org (Postfix) id 96AD09CECA2; Wed, 16 Sep 2015 13:57:44 +0000 (UTC) Delivered-To: current@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 964469CECA1 for ; Wed, 16 Sep 2015 13:57:44 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from kib.kiev.ua (kib.kiev.ua [IPv6:2001:470:d5e7:1::1]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 0C9BB1930; Wed, 16 Sep 2015 13:57:43 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from tom.home (kostik@localhost [127.0.0.1]) by kib.kiev.ua (8.15.2/8.15.2) with ESMTPS id t8GDvddM016324 (version=TLSv1 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO); Wed, 16 Sep 2015 16:57:39 +0300 (EEST) (envelope-from kostikbel@gmail.com) DKIM-Filter: OpenDKIM Filter v2.10.3 kib.kiev.ua t8GDvddM016324 Received: (from kostik@localhost) by tom.home (8.15.2/8.15.2/Submit) id t8GDvdRf016323; Wed, 16 Sep 2015 16:57:39 +0300 (EEST) (envelope-from kostikbel@gmail.com) X-Authentication-Warning: tom.home: kostik set sender to kostikbel@gmail.com using -f Date: Wed, 16 Sep 2015 16:57:39 +0300 From: Konstantin Belousov To: Gleb Smirnoff Cc: marcel@FreeBSD.org, Steve Kiernan , brooks@FreeBSD.org, current@FreeBSD.org Subject: Re: r286727 breaks geom_md.ko loading Message-ID: <20150916135739.GH67105@kib.kiev.ua> References: <20150916000019.GH1023@FreeBSD.org> <20150916051005.GF67105@kib.kiev.ua> <20150916131515.GL1023@glebius.int.ru> <20150916134249.GG67105@kib.kiev.ua> <20150916135003.GM1023@glebius.int.ru> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20150916135003.GM1023@glebius.int.ru> User-Agent: Mutt/1.5.24 (2015-08-30) X-Spam-Status: No, score=-2.0 required=5.0 tests=ALL_TRUSTED,BAYES_00, DKIM_ADSP_CUSTOM_MED,FREEMAIL_FROM,NML_ADSP_CUSTOM_MED autolearn=no autolearn_force=no version=3.4.1 X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on tom.home X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 16 Sep 2015 13:57:44 -0000 On Wed, Sep 16, 2015 at 04:50:03PM +0300, Gleb Smirnoff wrote: > On Wed, Sep 16, 2015 at 04:42:49PM +0300, Konstantin Belousov wrote: > K> On Wed, Sep 16, 2015 at 04:15:15PM +0300, Gleb Smirnoff wrote: > K> > On Wed, Sep 16, 2015 at 08:10:05AM +0300, Konstantin Belousov wrote: > K> > K> > There is regression after r286727. Our dynamic kernel linker doesn't > K> > K> > support weak symbols, so the geom_md.ko can no longer be loaded dynamically > K> > K> > neither from loader nor at runtime. Having it statically in kernel is > K> > K> > the only working option. > K> > K> > K> > K> Perhaps, something could be fixed in the dynamic linker ? > K> > K> > K> > K> I checked both i386 and amd64, and on both arches I can load geom_md.ko. > K> > K> On the other hand, I do not use preloaded mfs images. Can you explain > K> > K> how to reproduce the issue, and what linker is affected ? Note that we > K> > K> have two kernel dynamic linkers, one is used on amd64 and mips, second one > K> > K> is for all other architectures. > K> > > K> > To reproduce you need just a vanilla head, a kernel that doesn't have > K> > 'device md' in it, and run kldload geom_md.ko. Does that work for you? > K> > K> Yes, it does, both on amd64 and i386. You did not said which architecture > K> exposes your problem. Post your kernel config. > > It is amd64. Here is config. > options MD_ROOT # MD is a potential root device It is MD_ROOT which is problematic, it seems. I will take a look into linker. From owner-freebsd-current@freebsd.org Wed Sep 16 14:04:18 2015 Return-Path: Delivered-To: freebsd-current@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 F01979CEFCB for ; Wed, 16 Sep 2015 14:04:17 +0000 (UTC) (envelope-from glebius@FreeBSD.org) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id D43D41D62 for ; Wed, 16 Sep 2015 14:04:17 +0000 (UTC) (envelope-from glebius@FreeBSD.org) Received: by mailman.ysv.freebsd.org (Postfix) id D3AA59CEFCA; Wed, 16 Sep 2015 14:04:17 +0000 (UTC) Delivered-To: current@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 D34ED9CEFC9 for ; Wed, 16 Sep 2015 14:04:17 +0000 (UTC) (envelope-from glebius@FreeBSD.org) Received: from cell.glebius.int.ru (glebius.int.ru [81.19.69.10]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "cell.glebius.int.ru", Issuer "cell.glebius.int.ru" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id DA73F1D61; Wed, 16 Sep 2015 14:04:15 +0000 (UTC) (envelope-from glebius@FreeBSD.org) Received: from cell.glebius.int.ru (localhost [127.0.0.1]) by cell.glebius.int.ru (8.15.2/8.15.2) with ESMTPS id t8GE4Bfp012070 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Wed, 16 Sep 2015 17:04:11 +0300 (MSK) (envelope-from glebius@FreeBSD.org) Received: (from glebius@localhost) by cell.glebius.int.ru (8.15.2/8.15.2/Submit) id t8GE4BWW012069; Wed, 16 Sep 2015 17:04:11 +0300 (MSK) (envelope-from glebius@FreeBSD.org) X-Authentication-Warning: cell.glebius.int.ru: glebius set sender to glebius@FreeBSD.org using -f Date: Wed, 16 Sep 2015 17:04:11 +0300 From: Gleb Smirnoff To: Konstantin Belousov Cc: marcel@FreeBSD.org, Steve Kiernan , brooks@FreeBSD.org, current@FreeBSD.org Subject: Re: r286727 breaks geom_md.ko loading Message-ID: <20150916140411.GN1023@glebius.int.ru> References: <20150916000019.GH1023@FreeBSD.org> <20150916051005.GF67105@kib.kiev.ua> <20150916131515.GL1023@glebius.int.ru> <20150916134249.GG67105@kib.kiev.ua> <20150916135003.GM1023@glebius.int.ru> <20150916135739.GH67105@kib.kiev.ua> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20150916135739.GH67105@kib.kiev.ua> User-Agent: Mutt/1.5.23 (2014-03-12) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 16 Sep 2015 14:04:18 -0000 On Wed, Sep 16, 2015 at 04:57:39PM +0300, Konstantin Belousov wrote: K> On Wed, Sep 16, 2015 at 04:50:03PM +0300, Gleb Smirnoff wrote: K> > On Wed, Sep 16, 2015 at 04:42:49PM +0300, Konstantin Belousov wrote: K> > K> On Wed, Sep 16, 2015 at 04:15:15PM +0300, Gleb Smirnoff wrote: K> > K> > On Wed, Sep 16, 2015 at 08:10:05AM +0300, Konstantin Belousov wrote: K> > K> > K> > There is regression after r286727. Our dynamic kernel linker doesn't K> > K> > K> > support weak symbols, so the geom_md.ko can no longer be loaded dynamically K> > K> > K> > neither from loader nor at runtime. Having it statically in kernel is K> > K> > K> > the only working option. K> > K> > K> K> > K> > K> Perhaps, something could be fixed in the dynamic linker ? K> > K> > K> K> > K> > K> I checked both i386 and amd64, and on both arches I can load geom_md.ko. K> > K> > K> On the other hand, I do not use preloaded mfs images. Can you explain K> > K> > K> how to reproduce the issue, and what linker is affected ? Note that we K> > K> > K> have two kernel dynamic linkers, one is used on amd64 and mips, second one K> > K> > K> is for all other architectures. K> > K> > K> > K> > To reproduce you need just a vanilla head, a kernel that doesn't have K> > K> > 'device md' in it, and run kldload geom_md.ko. Does that work for you? K> > K> K> > K> Yes, it does, both on amd64 and i386. You did not said which architecture K> > K> exposes your problem. Post your kernel config. K> > K> > It is amd64. Here is config. K> K> > options MD_ROOT # MD is a potential root device K> It is MD_ROOT which is problematic, it seems. I will take a look into K> linker. Yes, sorry for not being verbose enough. Kernel must not have 'device md' and must have 'options MD_ROOT'. -- Totus tuus, Glebius. From owner-freebsd-current@freebsd.org Wed Sep 16 21:43:27 2015 Return-Path: Delivered-To: freebsd-current@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 E0C1B9CD7AD for ; Wed, 16 Sep 2015 21:43:27 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id C0C3317C8 for ; Wed, 16 Sep 2015 21:43:27 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: by mailman.ysv.freebsd.org (Postfix) id BEA229CD7A9; Wed, 16 Sep 2015 21:43:27 +0000 (UTC) Delivered-To: current@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 BE2AD9CD7A7 for ; Wed, 16 Sep 2015 21:43:27 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from kib.kiev.ua (kib.kiev.ua [IPv6:2001:470:d5e7:1::1]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 6341F17C7; Wed, 16 Sep 2015 21:43:27 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from tom.home (kostik@localhost [127.0.0.1]) by kib.kiev.ua (8.15.2/8.15.2) with ESMTPS id t8GLhLDj086218 (version=TLSv1 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO); Thu, 17 Sep 2015 00:43:21 +0300 (EEST) (envelope-from kostikbel@gmail.com) DKIM-Filter: OpenDKIM Filter v2.10.3 kib.kiev.ua t8GLhLDj086218 Received: (from kostik@localhost) by tom.home (8.15.2/8.15.2/Submit) id t8GLhLXq086217; Thu, 17 Sep 2015 00:43:21 +0300 (EEST) (envelope-from kostikbel@gmail.com) X-Authentication-Warning: tom.home: kostik set sender to kostikbel@gmail.com using -f Date: Thu, 17 Sep 2015 00:43:21 +0300 From: Konstantin Belousov To: Gleb Smirnoff Cc: marcel@FreeBSD.org, Steve Kiernan , brooks@FreeBSD.org, current@FreeBSD.org Subject: Re: r286727 breaks geom_md.ko loading Message-ID: <20150916214321.GI67105@kib.kiev.ua> References: <20150916000019.GH1023@FreeBSD.org> <20150916051005.GF67105@kib.kiev.ua> <20150916131515.GL1023@glebius.int.ru> <20150916134249.GG67105@kib.kiev.ua> <20150916135003.GM1023@glebius.int.ru> <20150916135739.GH67105@kib.kiev.ua> <20150916140411.GN1023@glebius.int.ru> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20150916140411.GN1023@glebius.int.ru> User-Agent: Mutt/1.5.24 (2015-08-30) X-Spam-Status: No, score=-2.0 required=5.0 tests=ALL_TRUSTED,BAYES_00, DKIM_ADSP_CUSTOM_MED,FREEMAIL_FROM,NML_ADSP_CUSTOM_MED autolearn=no autolearn_force=no version=3.4.1 X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on tom.home X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 16 Sep 2015 21:43:28 -0000 On Wed, Sep 16, 2015 at 05:04:11PM +0300, Gleb Smirnoff wrote: > Yes, sorry for not being verbose enough. Kernel must not have 'device md' > and must have 'options MD_ROOT'. The following worked for me on i386 and amd64. Unless some objections are raised against the approach, I will do the pass over other architectures later. diff --git a/sys/amd64/amd64/elf_machdep.c b/sys/amd64/amd64/elf_machdep.c index d1cffd9..d961f09 100644 --- a/sys/amd64/amd64/elf_machdep.c +++ b/sys/amd64/amd64/elf_machdep.c @@ -168,6 +168,7 @@ elf_reloc_internal(linker_file_t lf, Elf_Addr relocbase, const void *data, Elf_Size rtype, symidx; const Elf_Rel *rel; const Elf_Rela *rela; + int error; switch (type) { case ELF_RELOC_REL: @@ -203,29 +204,29 @@ elf_reloc_internal(linker_file_t lf, Elf_Addr relocbase, const void *data, break; case R_X86_64_64: /* S + A */ - addr = lookup(lf, symidx, 1); + error = lookup(lf, symidx, 1, &addr); val = addr + addend; - if (addr == 0) + if (error != 0) return -1; if (*where != val) *where = val; break; case R_X86_64_PC32: /* S + A - P */ - addr = lookup(lf, symidx, 1); + error = lookup(lf, symidx, 1, &addr); where32 = (Elf32_Addr *)where; val32 = (Elf32_Addr)(addr + addend - (Elf_Addr)where); - if (addr == 0) + if (error != 0) return -1; if (*where32 != val32) *where32 = val32; break; case R_X86_64_32S: /* S + A sign extend */ - addr = lookup(lf, symidx, 1); + error = lookup(lf, symidx, 1, &addr); val32 = (Elf32_Addr)(addr + addend); where32 = (Elf32_Addr *)where; - if (addr == 0) + if (error != 0) return -1; if (*where32 != val32) *where32 = val32; @@ -242,8 +243,8 @@ elf_reloc_internal(linker_file_t lf, Elf_Addr relocbase, const void *data, case R_X86_64_GLOB_DAT: /* S */ case R_X86_64_JMP_SLOT: /* XXX need addend + offset */ - addr = lookup(lf, symidx, 1); - if (addr == 0) + error = lookup(lf, symidx, 1, &addr); + if (error != 0) return -1; if (*where != addr) *where = addr; diff --git a/sys/i386/i386/elf_machdep.c b/sys/i386/i386/elf_machdep.c index 03ab10f..81d6e35 100644 --- a/sys/i386/i386/elf_machdep.c +++ b/sys/i386/i386/elf_machdep.c @@ -178,6 +178,7 @@ elf_reloc_internal(linker_file_t lf, Elf_Addr relocbase, const void *data, Elf_Word rtype, symidx; const Elf_Rel *rel; const Elf_Rela *rela; + int error; switch (type) { case ELF_RELOC_REL: @@ -213,8 +214,8 @@ elf_reloc_internal(linker_file_t lf, Elf_Addr relocbase, const void *data, break; case R_386_32: /* S + A */ - addr = lookup(lf, symidx, 1); - if (addr == 0) + error = lookup(lf, symidx, 1, &addr); + if (error != 0) return -1; addr += addend; if (*where != addr) @@ -222,8 +223,8 @@ elf_reloc_internal(linker_file_t lf, Elf_Addr relocbase, const void *data, break; case R_386_PC32: /* S + A - P */ - addr = lookup(lf, symidx, 1); - if (addr == 0) + error = lookup(lf, symidx, 1, &addr); + if (error != 0) return -1; addr += addend - (Elf_Addr)where; if (*where != addr) @@ -240,8 +241,8 @@ elf_reloc_internal(linker_file_t lf, Elf_Addr relocbase, const void *data, break; case R_386_GLOB_DAT: /* S */ - addr = lookup(lf, symidx, 1); - if (addr == 0) + error = lookup(lf, symidx, 1, &addr); + if (error != 0) return -1; if (*where != addr) *where = addr; diff --git a/sys/kern/link_elf.c b/sys/kern/link_elf.c index 3b741cc..c931ae9 100644 --- a/sys/kern/link_elf.c +++ b/sys/kern/link_elf.c @@ -158,7 +158,7 @@ static int link_elf_each_function_nameval(linker_file_t, static void link_elf_reloc_local(linker_file_t); static long link_elf_symtab_get(linker_file_t, const Elf_Sym **); static long link_elf_strtab_get(linker_file_t, caddr_t *); -static Elf_Addr elf_lookup(linker_file_t, Elf_Size, int); +static int elf_lookup(linker_file_t, Elf_Size, int, Elf_Addr *); static kobj_method_t link_elf_methods[] = { KOBJMETHOD(linker_lookup_symbol, link_elf_lookup_symbol), @@ -1548,8 +1548,8 @@ elf_get_symname(linker_file_t lf, Elf_Size symidx) * This is not only more efficient, it's also more correct. It's not always * the case that the symbol can be found through the hash table. */ -static Elf_Addr -elf_lookup(linker_file_t lf, Elf_Size symidx, int deps) +static int +elf_lookup(linker_file_t lf, Elf_Size symidx, int deps, Elf_Addr *res) { elf_file_t ef = (elf_file_t)lf; const Elf_Sym *sym; @@ -1557,8 +1557,10 @@ elf_lookup(linker_file_t lf, Elf_Size symidx, int deps) Elf_Addr addr, start, base; /* Don't even try to lookup the symbol if the index is bogus. */ - if (symidx >= ef->nchains) - return (0); + if (symidx >= ef->nchains) { + *res = 0; + return (EINVAL); + } sym = ef->symtab + symidx; @@ -1568,9 +1570,12 @@ elf_lookup(linker_file_t lf, Elf_Size symidx, int deps) */ if (ELF_ST_BIND(sym->st_info) == STB_LOCAL) { /* Force lookup failure when we have an insanity. */ - if (sym->st_shndx == SHN_UNDEF || sym->st_value == 0) - return (0); - return ((Elf_Addr)ef->address + sym->st_value); + if (sym->st_shndx == SHN_UNDEF || sym->st_value == 0) { + *res = 0; + return (EINVAL); + } + *res = ((Elf_Addr)ef->address + sym->st_value); + return (0); } /* @@ -1583,8 +1588,10 @@ elf_lookup(linker_file_t lf, Elf_Size symidx, int deps) symbol = ef->strtab + sym->st_name; /* Force a lookup failure if the symbol name is bogus. */ - if (*symbol == 0) - return (0); + if (*symbol == 0) { + *res = 0; + return (EINVAL); + } addr = ((Elf_Addr)linker_file_lookup_symbol(lf, symbol, deps)); @@ -1594,7 +1601,8 @@ elf_lookup(linker_file_t lf, Elf_Size symidx, int deps) else if (elf_set_find(&set_vnet_list, addr, &start, &base)) addr = addr - start + base; #endif - return addr; + *res = addr; + return (0); } static void diff --git a/sys/kern/link_elf_obj.c b/sys/kern/link_elf_obj.c index 021381d..00fe1e4 100644 --- a/sys/kern/link_elf_obj.c +++ b/sys/kern/link_elf_obj.c @@ -144,7 +144,8 @@ static void link_elf_reloc_local(linker_file_t); static long link_elf_symtab_get(linker_file_t, const Elf_Sym **); static long link_elf_strtab_get(linker_file_t, caddr_t *); -static Elf_Addr elf_obj_lookup(linker_file_t lf, Elf_Size symidx, int deps); +static int elf_obj_lookup(linker_file_t lf, Elf_Size symidx, int deps, + Elf_Addr *); static kobj_method_t link_elf_methods[] = { KOBJMETHOD(linker_lookup_symbol, link_elf_lookup_symbol), @@ -1253,38 +1254,46 @@ elf_obj_cleanup_globals_cache(elf_file_t ef) * This is not only more efficient, it's also more correct. It's not always * the case that the symbol can be found through the hash table. */ -static Elf_Addr -elf_obj_lookup(linker_file_t lf, Elf_Size symidx, int deps) +static int +elf_obj_lookup(linker_file_t lf, Elf_Size symidx, int deps, Elf_Addr *res) { elf_file_t ef = (elf_file_t)lf; Elf_Sym *sym; const char *symbol; - Elf_Addr ret; + Elf_Addr res1; /* Don't even try to lookup the symbol if the index is bogus. */ - if (symidx >= ef->ddbsymcnt) - return (0); + if (symidx >= ef->ddbsymcnt) { + *res = 0; + return (EINVAL); + } sym = ef->ddbsymtab + symidx; /* Quick answer if there is a definition included. */ - if (sym->st_shndx != SHN_UNDEF) - return (sym->st_value); + if (sym->st_shndx != SHN_UNDEF) { + *res = sym->st_value; + return (0); + } /* If we get here, then it is undefined and needs a lookup. */ switch (ELF_ST_BIND(sym->st_info)) { case STB_LOCAL: /* Local, but undefined? huh? */ - return (0); + *res = 0; + return (EINVAL); case STB_GLOBAL: + case STB_WEAK: /* Relative to Data or Function name */ symbol = ef->ddbstrtab + sym->st_name; /* Force a lookup failure if the symbol name is bogus. */ - if (*symbol == 0) - return (0); - ret = ((Elf_Addr)linker_file_lookup_symbol(lf, symbol, deps)); + if (*symbol == 0) { + *res = 0; + return (EINVAL); + } + res1 = (Elf_Addr)linker_file_lookup_symbol(lf, symbol, deps); /* * Cache global lookups during module relocation. The failure @@ -1296,18 +1305,20 @@ elf_obj_lookup(linker_file_t lf, Elf_Size symidx, int deps) * restored to SHN_UNDEF in elf_obj_cleanup_globals_cache(), * above. */ - if (ret != 0) { + if (res1 != 0) { sym->st_shndx = SHN_FBSD_CACHED; - sym->st_value = ret; + sym->st_value = res1; + *res = res1; + return (0); + } else if (ELF_ST_BIND(sym->st_info) == STB_WEAK) { + sym->st_value = 0; + *res = 0; + return (0); } - return (ret); - - case STB_WEAK: - printf("link_elf_obj: Weak symbols not supported\n"); - return (0); + return (EINVAL); default: - return (0); + return (EINVAL); } } diff --git a/sys/sys/linker.h b/sys/sys/linker.h index 5d24f00..7e562a6 100644 --- a/sys/sys/linker.h +++ b/sys/sys/linker.h @@ -264,7 +264,7 @@ extern int kld_debug; #endif -typedef Elf_Addr elf_lookup_fn(linker_file_t, Elf_Size, int); +typedef int elf_lookup_fn(linker_file_t, Elf_Size, int, Elf_Addr *); /* Support functions */ int elf_reloc(linker_file_t _lf, Elf_Addr base, const void *_rel, int _type, elf_lookup_fn _lu); From owner-freebsd-current@freebsd.org Thu Sep 17 07:47:20 2015 Return-Path: Delivered-To: freebsd-current@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 8E4D79CE4F3 for ; Thu, 17 Sep 2015 07:47:20 +0000 (UTC) (envelope-from stefanogarzarella@gmail.com) Received: from mail-la0-x230.google.com (mail-la0-x230.google.com [IPv6:2a00:1450:4010:c03::230]) (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 1882914E4; Thu, 17 Sep 2015 07:47:20 +0000 (UTC) (envelope-from stefanogarzarella@gmail.com) Received: by lamp12 with SMTP id p12so5885410lam.0; Thu, 17 Sep 2015 00:47:18 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc:content-type; bh=mCpEgHG9wHOxmqE2nXAngIy7xHK7lUBE6fXM6W0hdto=; b=R1V052LQsRwKOU3L0B7W/7vBxEEba0F5wFb/PTi0Gw3pmJOZbv3tAguzHaQVhtfvU/ 9+l74JpzKjz9dTyWVEHi+2m0FCi6nfPJz4Lxm5z52Ae9tfCCDkN68sOuR3ERWeoPgZJr NJMD0bWvOMc/x0b/+5O7e+dsig1Ti33yQorMo+LG7kCncZLdCKilzA1/FnXgGxhylbXu gR6CpHgkPZpLme+ot5YqwY+IpjDUCBSpT83DI6yAaq0vUZPqvc20dlwdCm+pKzchHS7J RwQGP6SiPK6ZZHcTahObqQ2+An8+srqSTEUYx4OxdBOtRUrU0RhEC6OdIr2WsVXlJIbp AFXg== X-Received: by 10.152.198.167 with SMTP id jd7mr16197138lac.118.1442476037877; Thu, 17 Sep 2015 00:47:17 -0700 (PDT) MIME-Version: 1.0 References: <55F8CBB2.1080109@freebsd.org> In-Reply-To: From: Stefano Garzarella Date: Thu, 17 Sep 2015 07:47:08 +0000 Message-ID: Subject: Re: nanoBSD boot problem (on USB stick or as a HD) To: NGie Cooper , Ryan Stone Cc: Julian Elischer , FreeBSD Current Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.20 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 17 Sep 2015 07:47:20 -0000 Thanks to all! as NGie says, I used the labeling through NANO_LABEL and it works very well! Now in the /etc/fstab I have the label and not the disk specific partition! Maybe is better to set default label in the nanobsd.sh and not the driver in according to NGie. Cheers, Stefano Il giorno mer 16 set 2015 alle 04:26 NGie Cooper ha scritto: > On Tue, Sep 15, 2015 at 7:18 PM, Ryan Stone wrote: > > On Tue, Sep 15, 2015 at 9:53 PM, Julian Elischer > wrote: > > > >> one possibility is to use gpart label to describe the device. > >> possibly it woudl hav ehte same result in both cases, but I don't know > for > >> sure that > >> it works for root device.. you'd have to test. > >> > >> > > I would recommend a UFS label instead. gpart labels are kind of fragile > > and easy to mess up. My previous employer has been shipping systems > where > > the root fs is specified in fstab via a UFS label for years and it never > > gave us a problems. > > +100 > > And FWIW as Stefano discovered later, NANO_LABEL does just that (use > UFS labels). > > The only unfortunate thing is that nanobsd uses a NUL string by default: > > grep NANO_LABEL tools/tools/nanobsd/defaults.sh > tools/tools/nanobsd/defaults.sh:NANO_LABEL="" > tools/tools/nanobsd/defaults.sh: echo newfs ${NANO_NEWFS} > ${NANO_LABEL:+-L${NANO_LABEL}${lbl}} ${dev} > tools/tools/nanobsd/defaults.sh: newfs ${NANO_NEWFS} > ${NANO_LABEL:+-L${NANO_LABEL}${lbl}} ${dev} > tools/tools/nanobsd/defaults.sh: if [ ! -z ${NANO_LABEL} ]; > then > tools/tools/nanobsd/defaults.sh: tunefs -L > ${NANO_LABEL}"s2a" /dev/${MD}s2a > tools/tools/nanobsd/defaults.sh: # Override user's NANO_DRIVE if > they specified a NANO_LABEL > tools/tools/nanobsd/defaults.sh: [ ! -z "${NANO_LABEL}" ] && > NANO_DRIVE="ufs/${NANO_LABEL}" > > The default NANO_DRIVE is useless though -- the old ata(4) stack is dead: > > 95 # The drive name of the media at runtime > 96 NANO_DRIVE=ad0 > > Cheers, > -NGie > _______________________________________________ > freebsd-current@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" > From owner-freebsd-current@freebsd.org Thu Sep 17 09:00:45 2015 Return-Path: Delivered-To: freebsd-current@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 54EA69CD062 for ; Thu, 17 Sep 2015 09:00:45 +0000 (UTC) (envelope-from andersbo87@icloud.com) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 389AC17B4 for ; Thu, 17 Sep 2015 09:00:45 +0000 (UTC) (envelope-from andersbo87@icloud.com) Received: by mailman.ysv.freebsd.org (Postfix) id 353D79CD061; Thu, 17 Sep 2015 09:00:45 +0000 (UTC) Delivered-To: current@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 34D4D9CD060 for ; Thu, 17 Sep 2015 09:00:45 +0000 (UTC) (envelope-from andersbo87@icloud.com) Received: from st11p00im-asmtp003.me.com (st11p00im-asmtp003.me.com [17.172.80.97]) (using TLSv1.2 with cipher DHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 1139417B2 for ; Thu, 17 Sep 2015 09:00:45 +0000 (UTC) (envelope-from andersbo87@icloud.com) Received: from freebsd-acer-Aspire-V17-Nitro.local (pc188-201.hiof.no [158.39.188.201]) by st11p00im-asmtp003.me.com (Oracle Communications Messaging Server 7.0.5.35.0 64bit (built Mar 31 2015)) with ESMTPSA id <0NUT008U4A902P40@st11p00im-asmtp003.me.com> for current@freebsd.org; Thu, 17 Sep 2015 08:00:38 +0000 (GMT) X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:,, definitions=2015-09-17_03:,, signatures=0 X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 kscore.is_bulkscore=7.2361644454233e-10 compositescore=0.999648274195187 phishscore=0 kscore.is_spamscore=0 rbsscore=0.999648274195187 recipient_to_sender_totalscore=0 spamscore=0 urlsuspectscore=0.999648274195187 adultscore=1 kscore.compositescore=0 circleOfTrustscore=0 suspectscore=4 recipient_domain_to_sender_totalscore=0 bulkscore=0 recipient_domain_to_sender_domain_totalscore=0 recipient_to_sender_domain_totalscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1412110000 definitions=main-1509170145 To: current@freebsd.org From: Anders Bolt-Evensen Subject: Intel Haswell support - Any updates? Message-id: <55FA7324.5010603@icloud.com> Date: Thu, 17 Sep 2015 10:00:36 +0200 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:38.0) Gecko/20100101 Thunderbird/38.2.0 MIME-version: 1.0 Content-type: text/plain; charset=utf-8; format=flowed Content-transfer-encoding: 7bit X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 17 Sep 2015 09:00:45 -0000 Hello! I'm just curious about how Intel Haswell GPU support in FreeBSD is coming along? What's the ETA of when the driver can be tested? Anders From owner-freebsd-current@freebsd.org Thu Sep 17 09:20:49 2015 Return-Path: Delivered-To: freebsd-current@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 8D9BF9CDC1E for ; Thu, 17 Sep 2015 09:20:49 +0000 (UTC) (envelope-from johannes@brilliantservice.co.jp) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 6C99610AC for ; Thu, 17 Sep 2015 09:20:49 +0000 (UTC) (envelope-from johannes@brilliantservice.co.jp) Received: by mailman.ysv.freebsd.org (Postfix) id 6B5119CDC1D; Thu, 17 Sep 2015 09:20:49 +0000 (UTC) Delivered-To: current@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 511D09CDC1C for ; Thu, 17 Sep 2015 09:20:49 +0000 (UTC) (envelope-from johannes@brilliantservice.co.jp) Received: from mail-qg0-f45.google.com (mail-qg0-f45.google.com [209.85.192.45]) (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 16B9910AB for ; Thu, 17 Sep 2015 09:20:48 +0000 (UTC) (envelope-from johannes@brilliantservice.co.jp) Received: by qgx61 with SMTP id 61so7707741qgx.3 for ; Thu, 17 Sep 2015 02:20:42 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-type; bh=nvzlRkBfV4tTvXEQdcXi+Kd/da+kadMgsT3aWoR/0RU=; b=XSHP2N7AztQSkjsZWi2CUJzFeLk0NCPfBK+uLpemSbmU7uakK7NDu2mYInyC1O3BEF +dun+74WNkvBa8jDSRZVfql8cUPdKqkFhfvIw7wvlN/13JJpJPNLIMRGESgYC6BIzWUe zt9bLxXH7bJ7BrQUU6Jm0FdGYPZwRn/JLGduBjUC2vXzuqkBjMk9/PPj1pnKOfGg1fEY JUQN5bWF2gekq7H464HViiPGH4nMSX2QqWzji5FaOvlyOUsiPaYLIxv9pUWWrieZv7hG iE/k5BImcIlRAanFLu5r2ID35fjBdIIlEXUg1vryK26qVey0cfXj4vJUoakQIF37pDtH gbjw== X-Gm-Message-State: ALoCoQlxqk8Hk+RVqSD4UJBBIYnv1A5NbHoNf3xbt/VvKKRoucwUMZEBj2Pfq0hU4IccNH6eCORz2T4xd8bWXddzPtaDmXwpMKs4IsG2BgGBwkW7+njdJS+QnyggFMgAMaeOm7uEzc7+ X-Received: by 10.140.20.168 with SMTP id 37mr27715475qgj.16.1442481642131; Thu, 17 Sep 2015 02:20:42 -0700 (PDT) MIME-Version: 1.0 Received: by 10.55.166.75 with HTTP; Thu, 17 Sep 2015 02:20:27 -0700 (PDT) In-Reply-To: <55FA7324.5010603@icloud.com> References: <55FA7324.5010603@icloud.com> From: "Lundberg, Johannes" Date: Thu, 17 Sep 2015 18:20:27 +0900 Message-ID: Subject: Re: Intel Haswell support - Any updates? To: Anders Bolt-Evensen Cc: current@freebsd.org Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: base64 X-Content-Filtered-By: Mailman/MimeDel 2.1.20 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 17 Sep 2015 09:20:49 -0000 SSBhbSB3b25kZXJpbmcgdGhlIHNhbWUuLiBJIGFtIHN1cmUgdGhlIHZlcnkgZmV3IGRldmVsb3Bl cnMgd2UgaGF2ZSBhcmUNCndvcmtpbmcgYXMgbXVjaCBhcyB0aGV5IGNhbiBvbiB0aGlzLg0KDQpI b3dldmVyLCB0aGUgbGFjayBvZiBzdXBwb3J0IGZvciB0aGUgbW9zdCBjb21tb24gaGFyZHdhcmUg c2luY2UgdGhyZWUgeWVhcnMNCmJhY2sgaXMsIEkgYmVsaWV2ZSwgcHJldmVudGluZyBtYW55IG5l dyB1c2VycywgYmVnaW5uZXJzIGFzIHdlbGwgYXMNCnByb2Zlc3Npb25hbHMsIGZyb20gY29taW5n IHRvIEZyZWVCU0QsIGFuZCBJIGhvcGUgdGhlIGZvdW5kYXRpb24gd291bGQgcG91cg0Kc29tZSBt b25leSBpbnRvIHRoaXMgdG8gc3BlZWQgdXAgdGhlIGRldmVsb3BtZW50Li4uDQoNCk1ha2luZyBp dCBwb3NzaWJsZSB0byB1c2UgV2F5bGFuZCBvbiBGcmVlQlNEIHdvdWxkIG9wZW4gdXAgZm9yIGEg d2hvbGUgbmV3DQpjYXRlZ29yeSBvbiBkZXZpY2VzIChtb2JpbGUsIElWSSwgZXRjKSB3aGVyZSBt YW55IHBlb3BsZSBhcmUgbm93IHdvbmRlcmluZw0Kd2hldGhlciB0byBnbyBMaW51eCwgQW5kcm9p ZCBvciBzb21ldGhpbmcgZWxzZS4uIEZyZWVCU0QgaGFzIHRoZSBsaWNlbnNlDQphbmQgdGhlIHN0 YWJpbGl0eSBtYWtpbmcgaXQgdmVyeSBhdHRyYWN0aXZlLCBhbGwgdGhhdCdzIG1pc3NpbmcgaXMg YSBtb2Rlcm4NCmdyYXBoaWNzIHN0YWNrLi4NCg0KSWYgSSBoYWQgdGhlIHNraWxscyBvciByZXNv dXJjZXMgSSB3b3VsZCBwaXRjaCBpbiBidXQgY3VycmVudGx5IEkgZG9uJ3Qgc28NCmFsbCBJIGNh biBkbyBpcyBjb21wbGFpbiB0byB0aGUgZm91bmRhdGlvbi4NCg0KSSB3b3VsZCBsb3ZlIHRvIHNl ZSBGcmVlQlNEIGJlY29tZSB0aGUgZGUgZmFjdG8gT1MgaW4gdGhlc2UgbmV3IGFyZWFzIGFuZA0K aXQgZmVlbHMgbGlrZSBpdCBjb3VsZCBiZSB3aXRoaW4gcmVhY2guLi4gT3IgbWF5YmUgbXkgZmVl bGluZyBpcyB3YXkgb2ZmLA0KY29ycmVjdCBtZSBpZiBJJ20gd3JvbmcgOikNCg0KU29ycnkgZm9y IHRoZSByYW50Li4uDQoNCkpvaGFubmVzDQoNCk9uIFRodSwgU2VwIDE3LCAyMDE1IGF0IDU6MDAg UE0sIEFuZGVycyBCb2x0LUV2ZW5zZW4gPGFuZGVyc2JvODdAaWNsb3VkLmNvbT4NCndyb3RlOg0K DQo+IEhlbGxvIQ0KPg0KPiBJJ20ganVzdCBjdXJpb3VzIGFib3V0IGhvdyBJbnRlbCBIYXN3ZWxs IEdQVSBzdXBwb3J0IGluIEZyZWVCU0QgaXMgY29taW5nDQo+IGFsb25nPw0KPiBXaGF0J3MgdGhl IEVUQSBvZiB3aGVuIHRoZSBkcml2ZXIgY2FuIGJlIHRlc3RlZD8NCj4NCj4gQW5kZXJzDQo+IF9f X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fDQo+IGZyZWVic2Qt Y3VycmVudEBmcmVlYnNkLm9yZyBtYWlsaW5nIGxpc3QNCj4gaHR0cHM6Ly9saXN0cy5mcmVlYnNk Lm9yZy9tYWlsbWFuL2xpc3RpbmZvL2ZyZWVic2QtY3VycmVudA0KPiBUbyB1bnN1YnNjcmliZSwg c2VuZCBhbnkgbWFpbCB0byAiZnJlZWJzZC1jdXJyZW50LXVuc3Vic2NyaWJlQGZyZWVic2Qub3Jn Ig0KPg0KCi0tIAo9LT0tPS09LT0tPS09LT0tPS09LT0tPS09LT0tPS09LT0tPS09LT0tPS09LT0t PS09LT0tPS0K56eY5a+G5L+d5oyB44Gr44Gk44GE44Gm77ya44GT44Gu6Zu75a2Q44Oh44O844Or 44Gv44CB5ZCN5a6b5Lq644Gr6YCB5L+h44GX44Gf44KC44Gu44Gn44GC44KK44CB56eY5Yy/54m5 5qip44Gu5a++6LGh44Go44Gq44KL5oOF5aCx44KS5ZCr44KT44Gn44GE44G+44GZ44CCCuOCguOB l+OAgeWQjeWum+S6uuS7peWkluOBruaWueOBjOWPl+S/oeOBleOCjOOBn+WgtOWQiOOAgeOBk+OB ruODoeODvOODq+OBruegtOajhOOAgeOBiuOCiOOBs+OBk+OBruODoeODvOODq+OBq+mWouOBmeOC i+S4gOWIh+OBrumWi+ekuuOAgQropIflhpnjgIHphY3luIPjgIHjgZ3jga7ku5bjga7liKnnlKjj gIHjgb7jgZ/jga/oqJjovInlhoXlrrnjgavln7rjgaXjgY/jgYTjgYvjgarjgovooYzli5XjgoLj gZXjgozjgarjgYTjgojjgYbjgYrpoZjjgYTnlLPjgZfkuIrjgZLjgb7jgZnjgIIKLS0tCkNPTkZJ REVOVElBTElUWSBOT1RFOiBUaGUgaW5mb3JtYXRpb24gaW4gdGhpcyBlbWFpbCBpcyBjb25maWRl bnRpYWwKYW5kIGludGVuZGVkIHNvbGVseSBmb3IgdGhlIGFkZHJlc3NlZS4KRGlzY2xvc3VyZSwg Y29weWluZywgZGlzdHJpYnV0aW9uIG9yIGFueSBvdGhlciBhY3Rpb24gb2YgdXNlIG9mIHRoaXMK ZW1haWwgYnkgcGVyc29uIG90aGVyIHRoYW4gaW50ZW5kZWQgcmVjaXBpZW50LCBpcyBwcm9oaWJp dGVkLgpJZiB5b3UgYXJlIG5vdCB0aGUgaW50ZW5kZWQgcmVjaXBpZW50IGFuZCBoYXZlIHJlY2Vp dmVkIHRoaXMgZW1haWwgaW4KZXJyb3IsIHBsZWFzZSBkZXN0cm95IHRoZSBvcmlnaW5hbCBtZXNz YWdlLgo= From owner-freebsd-current@freebsd.org Thu Sep 17 09:41:33 2015 Return-Path: Delivered-To: freebsd-current@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 8A80E9CE786 for ; Thu, 17 Sep 2015 09:41:33 +0000 (UTC) (envelope-from andrnils@gmail.com) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 698F21D03 for ; Thu, 17 Sep 2015 09:41:33 +0000 (UTC) (envelope-from andrnils@gmail.com) Received: by mailman.ysv.freebsd.org (Postfix) id 684D39CE785; Thu, 17 Sep 2015 09:41:33 +0000 (UTC) Delivered-To: current@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 67CAD9CE784 for ; Thu, 17 Sep 2015 09:41:33 +0000 (UTC) (envelope-from andrnils@gmail.com) Received: from mail-wi0-x22f.google.com (mail-wi0-x22f.google.com [IPv6:2a00:1450:400c:c05::22f]) (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 0739B1CFF for ; Thu, 17 Sep 2015 09:41:33 +0000 (UTC) (envelope-from andrnils@gmail.com) Received: by wicfx3 with SMTP id fx3so15750560wic.1 for ; Thu, 17 Sep 2015 02:41:31 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=BuZgJz0w4WTLNf6HHvsQu/6rQQIZND8BiSh0q3IOaZo=; b=TSfz9t52e0qY71fTH4oQdvurcKnt59Vvg8SDN7JHY4tT9+cj1Fbk8XH/s30wsus514 u5M78hfunfQRTQjloMcZ7U5wbabumD1g+jmOx77nVPL7BIOfel85493xFEJTMOTJ4GW8 wZUplxY2tuMQ1m4CvOLPH8CKBfXAeWw7AUZU00JOItiOW+w8UFpAiOD7PNE6Se9jGyfz ff0TjusR960EL8SI1IJ46Kg7SQBkraHHzvhAzeGlvvYumnsfhN2j/0z2o8Z6e4da+tf3 /a1KNesCPamnvkXL0mB3Z/9oe61hBkdxYc8DWmjsTxHa9wA6cETHONZ0FYirctxWICr1 22LQ== MIME-Version: 1.0 X-Received: by 10.194.23.167 with SMTP id n7mr59102421wjf.112.1442482891546; Thu, 17 Sep 2015 02:41:31 -0700 (PDT) Received: by 10.28.221.138 with HTTP; Thu, 17 Sep 2015 02:41:31 -0700 (PDT) In-Reply-To: References: <55FA7324.5010603@icloud.com> Date: Thu, 17 Sep 2015 11:41:31 +0200 Message-ID: Subject: Re: Intel Haswell support - Any updates? From: Andreas Nilsson To: "Lundberg, Johannes" Cc: Anders Bolt-Evensen , current@freebsd.org Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.20 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 17 Sep 2015 09:41:33 -0000 I guess interested parties could keep an eye on https://github.com/freebsd/freebsd-base-graphics/tree/drm-i915-update-38 and https://wiki.freebsd.org/Graphics Best regards Andreas On Thu, Sep 17, 2015 at 11:20 AM, Lundberg, Johannes < johannes@brilliantservice.co.jp> wrote: > I am wondering the same.. I am sure the very few developers we have are > working as much as they can on this. > > However, the lack of support for the most common hardware since three yea= rs > back is, I believe, preventing many new users, beginners as well as > professionals, from coming to FreeBSD, and I hope the foundation would po= ur > some money into this to speed up the development... > > Making it possible to use Wayland on FreeBSD would open up for a whole ne= w > category on devices (mobile, IVI, etc) where many people are now wonderin= g > whether to go Linux, Android or something else.. FreeBSD has the license > and the stability making it very attractive, all that's missing is a mode= rn > graphics stack.. > > If I had the skills or resources I would pitch in but currently I don't s= o > all I can do is complain to the foundation. > > I would love to see FreeBSD become the de facto OS in these new areas and > it feels like it could be within reach... Or maybe my feeling is way off, > correct me if I'm wrong :) > > Sorry for the rant... > > Johannes > > On Thu, Sep 17, 2015 at 5:00 PM, Anders Bolt-Evensen < > andersbo87@icloud.com> > wrote: > > > Hello! > > > > I'm just curious about how Intel Haswell GPU support in FreeBSD is comi= ng > > along? > > What's the ETA of when the driver can be tested? > > > > Anders > > _______________________________________________ > > freebsd-current@freebsd.org mailing list > > https://lists.freebsd.org/mailman/listinfo/freebsd-current > > To unsubscribe, send any mail to " > freebsd-current-unsubscribe@freebsd.org" > > > > -- > =3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-= =3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D- > =E7=A7=98=E5=AF=86=E4=BF=9D=E6=8C=81=E3=81=AB=E3=81=A4=E3=81=84=E3=81=A6= =EF=BC=9A=E3=81=93=E3=81=AE=E9=9B=BB=E5=AD=90=E3=83=A1=E3=83=BC=E3=83=AB=E3= =81=AF=E3=80=81=E5=90=8D=E5=AE=9B=E4=BA=BA=E3=81=AB=E9=80=81=E4=BF=A1=E3=81= =97=E3=81=9F=E3=82=82=E3=81=AE=E3=81=A7=E3=81=82=E3=82=8A=E3=80=81=E7=A7=98= =E5=8C=BF=E7=89=B9=E6=A8=A9=E3=81=AE=E5=AF=BE=E8=B1=A1=E3=81=A8=E3=81=AA=E3= =82=8B=E6=83=85=E5=A0=B1=E3=82=92=E5=90=AB=E3=82=93=E3=81=A7=E3=81=84=E3=81= =BE=E3=81=99=E3=80=82 > =E3=82=82=E3=81=97=E3=80=81=E5=90=8D=E5=AE=9B=E4=BA=BA=E4=BB=A5=E5=A4=96= =E3=81=AE=E6=96=B9=E3=81=8C=E5=8F=97=E4=BF=A1=E3=81=95=E3=82=8C=E3=81=9F=E5= =A0=B4=E5=90=88=E3=80=81=E3=81=93=E3=81=AE=E3=83=A1=E3=83=BC=E3=83=AB=E3=81= =AE=E7=A0=B4=E6=A3=84=E3=80=81=E3=81=8A=E3=82=88=E3=81=B3=E3=81=93=E3=81=AE= =E3=83=A1=E3=83=BC=E3=83=AB=E3=81=AB=E9=96=A2=E3=81=99=E3=82=8B=E4=B8=80=E5= =88=87=E3=81=AE=E9=96=8B=E7=A4=BA=E3=80=81 > =E8=A4=87=E5=86=99=E3=80=81=E9=85=8D=E5=B8=83=E3=80=81=E3=81=9D=E3=81=AE= =E4=BB=96=E3=81=AE=E5=88=A9=E7=94=A8=E3=80=81=E3=81=BE=E3=81=9F=E3=81=AF=E8= =A8=98=E8=BC=89=E5=86=85=E5=AE=B9=E3=81=AB=E5=9F=BA=E3=81=A5=E3=81=8F=E3=81= =84=E3=81=8B=E3=81=AA=E3=82=8B=E8=A1=8C=E5=8B=95=E3=82=82=E3=81=95=E3=82=8C= =E3=81=AA=E3=81=84=E3=82=88=E3=81=86=E3=81=8A=E9=A1=98=E3=81=84=E7=94=B3=E3= =81=97=E4=B8=8A=E3=81=92=E3=81=BE=E3=81=99=E3=80=82 > --- > 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-unsubscribe@freebsd.org= " > From owner-freebsd-current@freebsd.org Thu Sep 17 09:55:32 2015 Return-Path: Delivered-To: freebsd-current@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 7B1039CEFCF for ; Thu, 17 Sep 2015 09:55:32 +0000 (UTC) (envelope-from johannes@brilliantservice.co.jp) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 57875134F for ; Thu, 17 Sep 2015 09:55:32 +0000 (UTC) (envelope-from johannes@brilliantservice.co.jp) Received: by mailman.ysv.freebsd.org (Postfix) id 541F09CEFCE; Thu, 17 Sep 2015 09:55:32 +0000 (UTC) Delivered-To: current@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 539E99CEFCD for ; Thu, 17 Sep 2015 09:55:32 +0000 (UTC) (envelope-from johannes@brilliantservice.co.jp) Received: from mail-qg0-f43.google.com (mail-qg0-f43.google.com [209.85.192.43]) (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 168FE134E for ; Thu, 17 Sep 2015 09:55:31 +0000 (UTC) (envelope-from johannes@brilliantservice.co.jp) Received: by qgev79 with SMTP id v79so8221163qge.0 for ; Thu, 17 Sep 2015 02:55:25 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-type; bh=PtE2e9ynmNr/yQyzBt8+QOj37JjRXH2GbwtzOExG/IU=; b=IvT6BkhYlBSEoIJRTu3WzUXGK0JmIOEAcH97rSR0m9B6XsRzeKzh85d30CN2DndUfM iz4Dq9Q9OV878Z7frH9QFkKD4hFangXlRl6wMevCgyrjLtp36jbYfW0VuyUUhHp7NZAu i46pqDLA0JcHXW1tp4sJeDaUC9cBAUre8J1UK9U+MsJ8OeQ9YEIpt7JzZAulpPw65zsG aNgYGSRH2xKGhOoofbvfcSDfZf5Pm2aLX3GKeCnMI2j0LF7kwTDfzjclBADd5d3k0DHB VSlJJYxyRsxb+KHaSzRbfoeScxrBOMYAN+c96TfM9m23bdHsKNB7pmZPfgoXB/l2XFYv ipZA== X-Gm-Message-State: ALoCoQmc9YICU3fZmsH68VfEHj7PtywnB7IssNdf4clZsuHOikdrtNGe6NESVX8RHBzrvVXke5D+GCaNnxD2hg/OFG+N3yzZvKP0TRAbIcVyQYIP1C3h3Gacz5UmZRvH/wGUEzRMcuza X-Received: by 10.140.237.200 with SMTP id i191mr21657697qhc.5.1442483725012; Thu, 17 Sep 2015 02:55:25 -0700 (PDT) MIME-Version: 1.0 Received: by 10.55.166.75 with HTTP; Thu, 17 Sep 2015 02:55:10 -0700 (PDT) In-Reply-To: References: <55FA7324.5010603@icloud.com> From: "Lundberg, Johannes" Date: Thu, 17 Sep 2015 18:55:10 +0900 Message-ID: Subject: Re: Intel Haswell support - Any updates? To: Andreas Nilsson Cc: Anders Bolt-Evensen , current@freebsd.org Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: base64 X-Content-Filtered-By: Mailman/MimeDel 2.1.20 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 17 Sep 2015 09:55:32 -0000 TG9va2luZyBhdCB0aG9zZSBwYWdlcyBpdCBzZWVtcyBsaWtlIGRldmVsb3BtZW50IGhhcyBiYXNp Y2FsbHkgYmVlbg0Kc3RhbmRpbmcgc3RpbGwgZm9yIHRoZSBsYXN0IGNvdXBsZSBvZiB5ZWFycy4N Cg0KRHJhZ29uRmx5QlNEIGNsYWltcyB0byBoYXZlIHN1cHBvcnQgZm9yIEhhc3dlbGwsIG1heWJl IGl0IGNhbiB3b3JrIGFzIGENCnN0YW5kLWluIHdoaWxlIHdhaXRpbmcgZm9yIEZyZWVCU0QgaWYg eW91IG5lZWQgdGhlIEdQVSBmb3IgZGV2ZWxvcG1lbnQgb3INCnNvbWV0aGluZy4uDQoNCg0KT24g VGh1LCBTZXAgMTcsIDIwMTUgYXQgNjo0MSBQTSwgQW5kcmVhcyBOaWxzc29uIDxhbmRybmlsc0Bn bWFpbC5jb20+IHdyb3RlOg0KDQo+IEkgZ3Vlc3MgaW50ZXJlc3RlZCBwYXJ0aWVzIGNvdWxkIGtl ZXAgYW4gZXllIG9uDQo+IGh0dHBzOi8vZ2l0aHViLmNvbS9mcmVlYnNkL2ZyZWVic2QtYmFzZS1n cmFwaGljcy90cmVlL2RybS1pOTE1LXVwZGF0ZS0zOA0KPiBhbmQgaHR0cHM6Ly93aWtpLmZyZWVi c2Qub3JnL0dyYXBoaWNzDQo+DQo+IEJlc3QgcmVnYXJkcw0KPiBBbmRyZWFzDQo+DQo+IE9uIFRo dSwgU2VwIDE3LCAyMDE1IGF0IDExOjIwIEFNLCBMdW5kYmVyZywgSm9oYW5uZXMgPA0KPiBqb2hh bm5lc0BicmlsbGlhbnRzZXJ2aWNlLmNvLmpwPiB3cm90ZToNCj4NCj4+IEkgYW0gd29uZGVyaW5n IHRoZSBzYW1lLi4gSSBhbSBzdXJlIHRoZSB2ZXJ5IGZldyBkZXZlbG9wZXJzIHdlIGhhdmUgYXJl DQo+PiB3b3JraW5nIGFzIG11Y2ggYXMgdGhleSBjYW4gb24gdGhpcy4NCj4+DQo+PiBIb3dldmVy LCB0aGUgbGFjayBvZiBzdXBwb3J0IGZvciB0aGUgbW9zdCBjb21tb24gaGFyZHdhcmUgc2luY2Ug dGhyZWUNCj4+IHllYXJzDQo+PiBiYWNrIGlzLCBJIGJlbGlldmUsIHByZXZlbnRpbmcgbWFueSBu ZXcgdXNlcnMsIGJlZ2lubmVycyBhcyB3ZWxsIGFzDQo+PiBwcm9mZXNzaW9uYWxzLCBmcm9tIGNv bWluZyB0byBGcmVlQlNELCBhbmQgSSBob3BlIHRoZSBmb3VuZGF0aW9uIHdvdWxkDQo+PiBwb3Vy DQo+PiBzb21lIG1vbmV5IGludG8gdGhpcyB0byBzcGVlZCB1cCB0aGUgZGV2ZWxvcG1lbnQuLi4N Cj4+DQo+PiBNYWtpbmcgaXQgcG9zc2libGUgdG8gdXNlIFdheWxhbmQgb24gRnJlZUJTRCB3b3Vs ZCBvcGVuIHVwIGZvciBhIHdob2xlIG5ldw0KPj4gY2F0ZWdvcnkgb24gZGV2aWNlcyAobW9iaWxl LCBJVkksIGV0Yykgd2hlcmUgbWFueSBwZW9wbGUgYXJlIG5vdyB3b25kZXJpbmcNCj4+IHdoZXRo ZXIgdG8gZ28gTGludXgsIEFuZHJvaWQgb3Igc29tZXRoaW5nIGVsc2UuLiBGcmVlQlNEIGhhcyB0 aGUgbGljZW5zZQ0KPj4gYW5kIHRoZSBzdGFiaWxpdHkgbWFraW5nIGl0IHZlcnkgYXR0cmFjdGl2 ZSwgYWxsIHRoYXQncyBtaXNzaW5nIGlzIGENCj4+IG1vZGVybg0KPj4gZ3JhcGhpY3Mgc3RhY2su Lg0KPj4NCj4+IElmIEkgaGFkIHRoZSBza2lsbHMgb3IgcmVzb3VyY2VzIEkgd291bGQgcGl0Y2gg aW4gYnV0IGN1cnJlbnRseSBJIGRvbid0IHNvDQo+PiBhbGwgSSBjYW4gZG8gaXMgY29tcGxhaW4g dG8gdGhlIGZvdW5kYXRpb24uDQo+Pg0KPj4gSSB3b3VsZCBsb3ZlIHRvIHNlZSBGcmVlQlNEIGJl Y29tZSB0aGUgZGUgZmFjdG8gT1MgaW4gdGhlc2UgbmV3IGFyZWFzIGFuZA0KPj4gaXQgZmVlbHMg bGlrZSBpdCBjb3VsZCBiZSB3aXRoaW4gcmVhY2guLi4gT3IgbWF5YmUgbXkgZmVlbGluZyBpcyB3 YXkgb2ZmLA0KPj4gY29ycmVjdCBtZSBpZiBJJ20gd3JvbmcgOikNCj4+DQo+PiBTb3JyeSBmb3Ig dGhlIHJhbnQuLi4NCj4+DQo+PiBKb2hhbm5lcw0KPj4NCj4+IE9uIFRodSwgU2VwIDE3LCAyMDE1 IGF0IDU6MDAgUE0sIEFuZGVycyBCb2x0LUV2ZW5zZW4gPA0KPj4gYW5kZXJzYm84N0BpY2xvdWQu Y29tPg0KPj4gd3JvdGU6DQo+Pg0KPj4gPiBIZWxsbyENCj4+ID4NCj4+ID4gSSdtIGp1c3QgY3Vy aW91cyBhYm91dCBob3cgSW50ZWwgSGFzd2VsbCBHUFUgc3VwcG9ydCBpbiBGcmVlQlNEIGlzDQo+ PiBjb21pbmcNCj4+ID4gYWxvbmc/DQo+PiA+IFdoYXQncyB0aGUgRVRBIG9mIHdoZW4gdGhlIGRy aXZlciBjYW4gYmUgdGVzdGVkPw0KPj4gPg0KPj4gPiBBbmRlcnMNCj4+ID4gX19fX19fX19fX19f X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18NCj4+ID4gZnJlZWJzZC1jdXJyZW50 QGZyZWVic2Qub3JnIG1haWxpbmcgbGlzdA0KPj4gPiBodHRwczovL2xpc3RzLmZyZWVic2Qub3Jn L21haWxtYW4vbGlzdGluZm8vZnJlZWJzZC1jdXJyZW50DQo+PiA+IFRvIHVuc3Vic2NyaWJlLCBz ZW5kIGFueSBtYWlsIHRvICINCj4+IGZyZWVic2QtY3VycmVudC11bnN1YnNjcmliZUBmcmVlYnNk Lm9yZyINCj4+ID4NCj4+DQo+PiAtLQ0KPj4gPS09LT0tPS09LT0tPS09LT0tPS09LT0tPS09LT0t PS09LT0tPS09LT0tPS09LT0tPS09LT0tDQo+PiDnp5jlr4bkv53mjIHjgavjgaTjgYTjgabvvJrj gZPjga7pm7vlrZDjg6Hjg7zjg6vjga/jgIHlkI3lrpvkurrjgavpgIHkv6HjgZfjgZ/jgoLjga7j gafjgYLjgorjgIHnp5jljL/nibnmqKnjga7lr77osaHjgajjgarjgovmg4XloLHjgpLlkKvjgpPj gafjgYTjgb7jgZnjgIINCj4+IOOCguOBl+OAgeWQjeWum+S6uuS7peWkluOBruaWueOBjOWPl+S/ oeOBleOCjOOBn+WgtOWQiOOAgeOBk+OBruODoeODvOODq+OBruegtOajhOOAgeOBiuOCiOOBs+OB k+OBruODoeODvOODq+OBq+mWouOBmeOCi+S4gOWIh+OBrumWi+ekuuOAgQ0KPj4g6KSH5YaZ44CB 6YWN5biD44CB44Gd44Gu5LuW44Gu5Yip55So44CB44G+44Gf44Gv6KiY6LyJ5YaF5a6544Gr5Z+6 44Gl44GP44GE44GL44Gq44KL6KGM5YuV44KC44GV44KM44Gq44GE44KI44GG44GK6aGY44GE55Sz 44GX5LiK44GS44G+44GZ44CCDQo+PiAtLS0NCj4+IENPTkZJREVOVElBTElUWSBOT1RFOiBUaGUg aW5mb3JtYXRpb24gaW4gdGhpcyBlbWFpbCBpcyBjb25maWRlbnRpYWwNCj4+IGFuZCBpbnRlbmRl ZCBzb2xlbHkgZm9yIHRoZSBhZGRyZXNzZWUuDQo+PiBEaXNjbG9zdXJlLCBjb3B5aW5nLCBkaXN0 cmlidXRpb24gb3IgYW55IG90aGVyIGFjdGlvbiBvZiB1c2Ugb2YgdGhpcw0KPj4gZW1haWwgYnkg cGVyc29uIG90aGVyIHRoYW4gaW50ZW5kZWQgcmVjaXBpZW50LCBpcyBwcm9oaWJpdGVkLg0KPj4g SWYgeW91IGFyZSBub3QgdGhlIGludGVuZGVkIHJlY2lwaWVudCBhbmQgaGF2ZSByZWNlaXZlZCB0 aGlzIGVtYWlsIGluDQo+PiBlcnJvciwgcGxlYXNlIGRlc3Ryb3kgdGhlIG9yaWdpbmFsIG1lc3Nh Z2UuDQo+PiBfX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fXw0K Pj4gZnJlZWJzZC1jdXJyZW50QGZyZWVic2Qub3JnIG1haWxpbmcgbGlzdA0KPj4gaHR0cHM6Ly9s aXN0cy5mcmVlYnNkLm9yZy9tYWlsbWFuL2xpc3RpbmZvL2ZyZWVic2QtY3VycmVudA0KPj4gVG8g dW5zdWJzY3JpYmUsIHNlbmQgYW55IG1haWwgdG8gImZyZWVic2QtY3VycmVudC11bnN1YnNjcmli ZUBmcmVlYnNkLm9yZw0KPj4gIg0KPj4NCj4NCj4NCgotLSAKPS09LT0tPS09LT0tPS09LT0tPS09 LT0tPS09LT0tPS09LT0tPS09LT0tPS09LT0tPS09LT0tCuenmOWvhuS/neaMgeOBq+OBpOOBhOOB pu+8muOBk+OBrumbu+WtkOODoeODvOODq+OBr+OAgeWQjeWum+S6uuOBq+mAgeS/oeOBl+OBn+OC guOBruOBp+OBguOCiuOAgeenmOWMv+eJueaoqeOBruWvvuixoeOBqOOBquOCi+aDheWgseOCkuWQ q+OCk+OBp+OBhOOBvuOBmeOAggrjgoLjgZfjgIHlkI3lrpvkurrku6XlpJbjga7mlrnjgYzlj5fk v6HjgZXjgozjgZ/loLTlkIjjgIHjgZPjga7jg6Hjg7zjg6vjga7noLTmo4TjgIHjgYrjgojjgbPj gZPjga7jg6Hjg7zjg6vjgavplqLjgZnjgovkuIDliIfjga7plovnpLrjgIEK6KSH5YaZ44CB6YWN 5biD44CB44Gd44Gu5LuW44Gu5Yip55So44CB44G+44Gf44Gv6KiY6LyJ5YaF5a6544Gr5Z+644Gl 44GP44GE44GL44Gq44KL6KGM5YuV44KC44GV44KM44Gq44GE44KI44GG44GK6aGY44GE55Sz44GX 5LiK44GS44G+44GZ44CCCi0tLQpDT05GSURFTlRJQUxJVFkgTk9URTogVGhlIGluZm9ybWF0aW9u IGluIHRoaXMgZW1haWwgaXMgY29uZmlkZW50aWFsCmFuZCBpbnRlbmRlZCBzb2xlbHkgZm9yIHRo ZSBhZGRyZXNzZWUuCkRpc2Nsb3N1cmUsIGNvcHlpbmcsIGRpc3RyaWJ1dGlvbiBvciBhbnkgb3Ro ZXIgYWN0aW9uIG9mIHVzZSBvZiB0aGlzCmVtYWlsIGJ5IHBlcnNvbiBvdGhlciB0aGFuIGludGVu ZGVkIHJlY2lwaWVudCwgaXMgcHJvaGliaXRlZC4KSWYgeW91IGFyZSBub3QgdGhlIGludGVuZGVk IHJlY2lwaWVudCBhbmQgaGF2ZSByZWNlaXZlZCB0aGlzIGVtYWlsIGluCmVycm9yLCBwbGVhc2Ug ZGVzdHJveSB0aGUgb3JpZ2luYWwgbWVzc2FnZS4K From owner-freebsd-current@freebsd.org Thu Sep 17 10:10:58 2015 Return-Path: Delivered-To: freebsd-current@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 32C7E9CE7E6 for ; Thu, 17 Sep 2015 10:10:58 +0000 (UTC) (envelope-from theraven@FreeBSD.org) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 16ADE1BF1 for ; Thu, 17 Sep 2015 10:10:58 +0000 (UTC) (envelope-from theraven@FreeBSD.org) Received: by mailman.ysv.freebsd.org (Postfix) id 159919CE7E5; Thu, 17 Sep 2015 10:10:58 +0000 (UTC) Delivered-To: current@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 154269CE7E4 for ; Thu, 17 Sep 2015 10:10:58 +0000 (UTC) (envelope-from theraven@FreeBSD.org) Received: from theravensnest.org (theraven.freebsd.your.org [216.14.102.27]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "cloud.theravensnest.org", Issuer "StartCom Class 1 Primary Intermediate Server CA" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id CFF161BEB for ; Thu, 17 Sep 2015 10:10:57 +0000 (UTC) (envelope-from theraven@FreeBSD.org) Received: from [192.168.0.7] (cpc16-cmbg15-2-0-cust60.5-4.cable.virginm.net [86.5.162.61]) (authenticated bits=0) by theravensnest.org (8.15.2/8.15.2) with ESMTPSA id t8HAAqsH049383 (version=TLSv1 cipher=ECDHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 17 Sep 2015 10:10:54 GMT (envelope-from theraven@FreeBSD.org) X-Authentication-Warning: theravensnest.org: Host cpc16-cmbg15-2-0-cust60.5-4.cable.virginm.net [86.5.162.61] claimed to be [192.168.0.7] Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2102\)) Subject: Re: Intel Haswell support - Any updates? From: David Chisnall In-Reply-To: Date: Thu, 17 Sep 2015 11:10:47 +0100 Cc: Andreas Nilsson , Anders Bolt-Evensen , current@freebsd.org Content-Transfer-Encoding: quoted-printable Message-Id: <09A515F2-44BA-4DF0-9792-D4C56EEB9D7C@FreeBSD.org> References: <55FA7324.5010603@icloud.com> To: "Lundberg, Johannes" X-Mailer: Apple Mail (2.2102) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 17 Sep 2015 10:10:58 -0000 On 17 Sep 2015, at 10:55, Lundberg, Johannes = wrote: >=20 > Looking at those pages it seems like development has basically been > standing still for the last couple of years. I=E2=80=99m not sure why you=E2=80=99d have that impression. The = Haswell entry on that page links here: = https://wiki.freebsd.org/Graphics/Update%20i915%20GPU%20driver%20to%20Linu= x%203.8 This has a status update from July and links to this GitHub repo: https://github.com/freebsd/freebsd-base-graphics/tree/drm-i915-update-38 The last graphics-related commit in that repo was 6 hours ago: = https://github.com/freebsd/freebsd-base-graphics/commits/drm-i915-update-3= 8 It was preceded by a load of other work. If you look at the changes = since the last non-graphic-related commit in that branch (about a month = ago) you=E2=80=99ll see a huge quantity of changes. Of course, I=E2=80=99m sure that the graphics team would welcome = assistance if people feel that their progress is too slow. David From owner-freebsd-current@freebsd.org Thu Sep 17 10:15:42 2015 Return-Path: Delivered-To: freebsd-current@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 899B99CEA2F for ; Thu, 17 Sep 2015 10:15:42 +0000 (UTC) (envelope-from ohartman@zedat.fu-berlin.de) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 6B7E71E60 for ; Thu, 17 Sep 2015 10:15:42 +0000 (UTC) (envelope-from ohartman@zedat.fu-berlin.de) Received: by mailman.ysv.freebsd.org (Postfix) id 683BF9CEA2E; Thu, 17 Sep 2015 10:15:42 +0000 (UTC) Delivered-To: current@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 67CB89CEA2D for ; Thu, 17 Sep 2015 10:15:42 +0000 (UTC) (envelope-from ohartman@zedat.fu-berlin.de) Received: from outpost1.zedat.fu-berlin.de (outpost1.zedat.fu-berlin.de [130.133.4.66]) (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 211F11E5F for ; Thu, 17 Sep 2015 10:15:41 +0000 (UTC) (envelope-from ohartman@zedat.fu-berlin.de) Received: from inpost2.zedat.fu-berlin.de ([130.133.4.69]) by outpost.zedat.fu-berlin.de (Exim 4.85) with esmtp (envelope-from ) id <1ZcWE0-001P42-Bf>; Thu, 17 Sep 2015 12:15:32 +0200 Received: from p578a69f9.dip0.t-ipconnect.de ([87.138.105.249] helo=freyja.zeit4.iv.bundesimmobilien.de) by inpost2.zedat.fu-berlin.de (Exim 4.85) with esmtpsa (envelope-from ) id <1ZcWE0-000PIl-2D>; Thu, 17 Sep 2015 12:15:32 +0200 Date: Thu, 17 Sep 2015 12:15:26 +0200 From: "O. Hartmann" To: "Lundberg, Johannes" Cc: Andreas Nilsson , Anders Bolt-Evensen , current@freebsd.org Subject: Re: Intel Haswell support - Any updates? Message-ID: <20150917121526.71906673@freyja.zeit4.iv.bundesimmobilien.de> In-Reply-To: References: <55FA7324.5010603@icloud.com> Organization: FU Berlin X-Mailer: Claws Mail 3.12.0 (GTK+ 2.24.28; amd64-portbld-freebsd11.0) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Originating-IP: 87.138.105.249 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 17 Sep 2015 10:15:42 -0000 On Thu, 17 Sep 2015 18:55:10 +0900 "Lundberg, Johannes" wrote: > Looking at those pages it seems like development has basically been > standing still for the last couple of years. > > DragonFlyBSD claims to have support for Haswell, maybe it can work as a > stand-in while waiting for FreeBSD if you need the GPU for development or > something.. > > > On Thu, Sep 17, 2015 at 6:41 PM, Andreas Nilsson wrote: > > > I guess interested parties could keep an eye on > > https://github.com/freebsd/freebsd-base-graphics/tree/drm-i915-update-38 > > and https://wiki.freebsd.org/Graphics > > > > Best regards > > Andreas > > > > On Thu, Sep 17, 2015 at 11:20 AM, Lundberg, Johannes < > > johannes@brilliantservice.co.jp> wrote: > > > >> I am wondering the same.. I am sure the very few developers we have are > >> working as much as they can on this. > >> > >> However, the lack of support for the most common hardware since three > >> years > >> back is, I believe, preventing many new users, beginners as well as > >> professionals, from coming to FreeBSD, and I hope the foundation would > >> pour > >> some money into this to speed up the development... > >> > >> Making it possible to use Wayland on FreeBSD would open up for a whole new > >> category on devices (mobile, IVI, etc) where many people are now wondering > >> whether to go Linux, Android or something else.. FreeBSD has the license > >> and the stability making it very attractive, all that's missing is a > >> modern > >> graphics stack.. > >> > >> If I had the skills or resources I would pitch in but currently I don't so > >> all I can do is complain to the foundation. > >> > >> I would love to see FreeBSD become the de facto OS in these new areas and > >> it feels like it could be within reach... Or maybe my feeling is way off, > >> correct me if I'm wrong :) > >> > >> Sorry for the rant... > >> > >> Johannes > >> > >> On Thu, Sep 17, 2015 at 5:00 PM, Anders Bolt-Evensen < > >> andersbo87@icloud.com> > >> wrote: > >> > >> > Hello! > >> > > >> > I'm just curious about how Intel Haswell GPU support in FreeBSD is > >> coming > >> > along? > >> > What's the ETA of when the driver can be tested? > >> > > >> > Anders [...] It seems FreeBSD has massive problems catching up with the progress in graphical device support. While "Linux" is concentrated on one single kernel development, the *BSD have drifted appart over the past decade. My feeling is that developers start focoussing on one specific *BSD due to the diversity in their basic architecture. FreeBSD lacks behind in WiFi chipset support, iGPU support, graphics support in general as GPUs has become more important over the past years in HPC environments and not only for displaying. That is a political issue, I guess. X11 is now claimed by the Linux folks - that is the impression I have - the spirit of a multiplatform, open system is gone. With systemd on Linux, even FreeBSD is falling more and more behind. I think this needs to be addressed on political terrain. Linux wanted to have ZFS - now they participate in OpenZFS. How long until those L-people move the BSD people aside? Well, asking for Haswell support is a bit weird - Skylake ante portam. Broadwell is already there. Two years ago, we purchased Laptops with Haswell GPUs. They are now about to be replaced by Skylake-based systems. Running FreeBSD on Laptops with modern WiFi and iGPU hardware is almost impossible. Dead hardware or extremely slow. So we decided to switch to Linux. Interesting to hear that DragonFlyBSD seems to have solved several iGPU issues and FreeBSD not. The www pages on that matter are outdated and badly maintained - I try to consult them on news on a regular basis. One has to digg through piles of mailing lists. The culture of keeping his clients informed hasn't reached FreeBSD development yet and that makes me wondering. Well, a stopgap for nVidia Nouveau support seems to be the PRIME support in FreeBSD's kernel. I do not understand much of that matter, but the kernel is not well fitted for moving buffers from/to different GPU adaptors. That seems also to be important for future architectures concerning OpenCL and GPGPU - a matter I was interested in due to a physical modelling interest. But in that matter there leads no way around Linux. From owner-freebsd-current@freebsd.org Thu Sep 17 10:32:03 2015 Return-Path: Delivered-To: freebsd-current@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 9ED7E9CE3FE for ; Thu, 17 Sep 2015 10:32:03 +0000 (UTC) (envelope-from johannes@brilliantservice.co.jp) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 7932717FA for ; Thu, 17 Sep 2015 10:32:03 +0000 (UTC) (envelope-from johannes@brilliantservice.co.jp) Received: by mailman.ysv.freebsd.org (Postfix) id 780FB9CE3FC; Thu, 17 Sep 2015 10:32:03 +0000 (UTC) Delivered-To: current@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 76A039CE3FB for ; Thu, 17 Sep 2015 10:32:03 +0000 (UTC) (envelope-from johannes@brilliantservice.co.jp) Received: from mail-qg0-f44.google.com (mail-qg0-f44.google.com [209.85.192.44]) (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 3322D17F8 for ; Thu, 17 Sep 2015 10:32:02 +0000 (UTC) (envelope-from johannes@brilliantservice.co.jp) Received: by qgev79 with SMTP id v79so8753345qge.0 for ; Thu, 17 Sep 2015 03:31:56 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-type; bh=YpJ7rsbRVf/7F9W+4KsYIFoVUQRy1OE7vv7N0n5im78=; b=cFaP+z4HzyQ8mdyf6KTbMiQypMzl1ZSH+xgAS1dxAVSE0Slwa0WSS/HVR/qyN0HujF DVJSmz68FaLIF5kXh4BItHk1YWnNL2I8aiGZfhqm57/ThwnkqYsgoTEnnd4fNHptsEfU Ncbe9N7cz1pSFrHep1IM+KuT/DO5TvrP+4shGc6IqR8QfzaG0DTc87/S08MknvgN9SPi Ubg6bE8GbdXPNnmPQkNxCBjXTGGuvv9gVhfT0zlT6sx56+jsrni3FDoZJ9TU/Ftaph0P 15NRVQ4n69vWMf0wVMKDCxwNDLC+Z7l9zTHTuOAHvanpXzfkSvoSax8pprin2SL+LOVt tS7Q== X-Gm-Message-State: ALoCoQnaO/ibGtiEUaxbBvFUOXTKeuQQMidkIndcsUqbgVn5I5iRwCN/iTVg//5wN2ryN6OShQNQ94mTQasPJNl7Em70qcUoC+P5bWtxYT/ZTWauiCizgARz50aRib229Qiv45Z8IgEo X-Received: by 10.140.93.53 with SMTP id c50mr48966160qge.59.1442485916407; Thu, 17 Sep 2015 03:31:56 -0700 (PDT) MIME-Version: 1.0 Received: by 10.55.166.75 with HTTP; Thu, 17 Sep 2015 03:31:41 -0700 (PDT) In-Reply-To: <09A515F2-44BA-4DF0-9792-D4C56EEB9D7C@FreeBSD.org> References: <55FA7324.5010603@icloud.com> <09A515F2-44BA-4DF0-9792-D4C56EEB9D7C@FreeBSD.org> From: "Lundberg, Johannes" Date: Thu, 17 Sep 2015 19:31:41 +0900 Message-ID: Subject: Re: Intel Haswell support - Any updates? To: David Chisnall Cc: Andreas Nilsson , Anders Bolt-Evensen , current@freebsd.org Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.20 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 17 Sep 2015 10:32:03 -0000 Well, I've been following the FreeBSD graphics page for 2-3 years now and from what I can tell it's been updated basically once per year and with very little/slow progress. Don't get me wrong, I am not criticizing the developers. They are doing a great job, much more than I ever could. However, from what I see, development seems to more or less have stopped. Maybe it is because there was a lot of preparation work that is less visible?... Anyway, I wish the foundation would support the graphics team by sponsoring this development... -- Johannes Lundberg BRILLIANTSERVICE CO., LTD. On Thu, Sep 17, 2015 at 7:10 PM, David Chisnall wrote: > On 17 Sep 2015, at 10:55, Lundberg, Johannes < > johannes@brilliantservice.co.jp> wrote: > > > > Looking at those pages it seems like development has basically been > > standing still for the last couple of years. > > I=E2=80=99m not sure why you=E2=80=99d have that impression. The Haswell= entry on that > page links here: > > > https://wiki.freebsd.org/Graphics/Update%20i915%20GPU%20driver%20to%20Lin= ux%203.8 > > This has a status update from July and links to this GitHub repo: > > https://github.com/freebsd/freebsd-base-graphics/tree/drm-i915-update-38 > > The last graphics-related commit in that repo was 6 hours ago: > > https://github.com/freebsd/freebsd-base-graphics/commits/drm-i915-update-= 38 > > It was preceded by a load of other work. If you look at the changes sinc= e > the last non-graphic-related commit in that branch (about a month ago) > you=E2=80=99ll see a huge quantity of changes. > > Of course, I=E2=80=99m sure that the graphics team would welcome assistan= ce if > people feel that their progress is too slow. > > David > > --=20 =3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D= -=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D- =E7=A7=98=E5=AF=86=E4=BF=9D=E6=8C=81=E3=81=AB=E3=81=A4=E3=81=84=E3=81=A6=EF= =BC=9A=E3=81=93=E3=81=AE=E9=9B=BB=E5=AD=90=E3=83=A1=E3=83=BC=E3=83=AB=E3=81= =AF=E3=80=81=E5=90=8D=E5=AE=9B=E4=BA=BA=E3=81=AB=E9=80=81=E4=BF=A1=E3=81=97= =E3=81=9F=E3=82=82=E3=81=AE=E3=81=A7=E3=81=82=E3=82=8A=E3=80=81=E7=A7=98=E5= =8C=BF=E7=89=B9=E6=A8=A9=E3=81=AE=E5=AF=BE=E8=B1=A1=E3=81=A8=E3=81=AA=E3=82= =8B=E6=83=85=E5=A0=B1=E3=82=92=E5=90=AB=E3=82=93=E3=81=A7=E3=81=84=E3=81=BE= =E3=81=99=E3=80=82 =E3=82=82=E3=81=97=E3=80=81=E5=90=8D=E5=AE=9B=E4=BA=BA=E4=BB=A5=E5=A4=96=E3= =81=AE=E6=96=B9=E3=81=8C=E5=8F=97=E4=BF=A1=E3=81=95=E3=82=8C=E3=81=9F=E5=A0= =B4=E5=90=88=E3=80=81=E3=81=93=E3=81=AE=E3=83=A1=E3=83=BC=E3=83=AB=E3=81=AE= =E7=A0=B4=E6=A3=84=E3=80=81=E3=81=8A=E3=82=88=E3=81=B3=E3=81=93=E3=81=AE=E3= =83=A1=E3=83=BC=E3=83=AB=E3=81=AB=E9=96=A2=E3=81=99=E3=82=8B=E4=B8=80=E5=88= =87=E3=81=AE=E9=96=8B=E7=A4=BA=E3=80=81 =E8=A4=87=E5=86=99=E3=80=81=E9=85=8D=E5=B8=83=E3=80=81=E3=81=9D=E3=81=AE=E4= =BB=96=E3=81=AE=E5=88=A9=E7=94=A8=E3=80=81=E3=81=BE=E3=81=9F=E3=81=AF=E8=A8= =98=E8=BC=89=E5=86=85=E5=AE=B9=E3=81=AB=E5=9F=BA=E3=81=A5=E3=81=8F=E3=81=84= =E3=81=8B=E3=81=AA=E3=82=8B=E8=A1=8C=E5=8B=95=E3=82=82=E3=81=95=E3=82=8C=E3= =81=AA=E3=81=84=E3=82=88=E3=81=86=E3=81=8A=E9=A1=98=E3=81=84=E7=94=B3=E3=81= =97=E4=B8=8A=E3=81=92=E3=81=BE=E3=81=99=E3=80=82 --- 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. From owner-freebsd-current@freebsd.org Thu Sep 17 09:45:06 2015 Return-Path: Delivered-To: freebsd-current@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 20AE79CE8E4 for ; Thu, 17 Sep 2015 09:45:06 +0000 (UTC) (envelope-from listjm@club.fr) Received: from smtp26.services.sfr.fr (smtp26.services.sfr.fr [93.17.128.163]) (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 D95851EBD for ; Thu, 17 Sep 2015 09:45:05 +0000 (UTC) (envelope-from listjm@club.fr) Received: from filter.sfr.fr (localhost [78.118.197.112]) by msfrf2603.sfr.fr (SMTP Server) with ESMTP id 9A24A1C000C30 for ; Thu, 17 Sep 2015 11:36:00 +0200 (CEST) Authentication-Results: sfrmc.priv.atos.fr; dkim=none (no signature); dkim-adsp=none (no policy) header.from=listjm@club.fr Received: from [192.168.1.51] (112.197.118.78.rev.sfr.net [78.118.197.112]) by msfrf2603.sfr.fr (SMTP Server) with ESMTP id 78FF31C000C28 for ; Thu, 17 Sep 2015 11:36:00 +0200 (CEST) X-SFR-UUID: 20150917093600495.78FF31C000C28@msfrf2603.sfr.fr Subject: Intel Haswell support - Any updates? To: freebsd-current@freebsd.org From: Juan =?iso-8859-1?b?UmFt824=?= Molina Menor Message-ID: <55FA897B.4060504@club.fr> Date: Thu, 17 Sep 2015 11:35:55 +0200 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.2.0 MIME-Version: 1.0 Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 8bit X-Mailman-Approved-At: Thu, 17 Sep 2015 11:08:08 +0000 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 17 Sep 2015 09:45:06 -0000 > Hello! > > I'm just curious about how Intel Haswell GPU support in FreeBSD is > coming along? > What's the ETA of when the driver can be tested? > > Anders Jean Sébastien-Pédron is actively working on it: https://github.com/freebsd/freebsd-base-graphics/commits/drm-i915-update-38 From owner-freebsd-current@freebsd.org Thu Sep 17 11:14:50 2015 Return-Path: Delivered-To: freebsd-current@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 302D19CECF9; Thu, 17 Sep 2015 11:14:50 +0000 (UTC) (envelope-from eugen@grosbein.net) Received: from hz.grosbein.net (hz.grosbein.net [78.47.246.247]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "hz.grosbein.net", Issuer "hz.grosbein.net" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id B886E1F95; Thu, 17 Sep 2015 11:14:49 +0000 (UTC) (envelope-from eugen@grosbein.net) Received: from eg.sd.rdtc.ru (root@eg.sd.rdtc.ru [62.231.161.221]) by hz.grosbein.net (8.14.9/8.14.9) with ESMTP id t8HBEUDR089159 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Thu, 17 Sep 2015 13:14:31 +0200 (CEST) (envelope-from eugen@grosbein.net) X-Envelope-From: eugen@grosbein.net X-Envelope-To: stefanogarzarella@gmail.com Received: from eg.sd.rdtc.ru (eugen@localhost [127.0.0.1]) by eg.sd.rdtc.ru (8.15.2/8.15.2) with ESMTP id t8HBEJJb009005; Thu, 17 Sep 2015 18:14:21 +0700 (KRAT) (envelope-from eugen@grosbein.net) Subject: Re: nanoBSD boot problem (on USB stick or as a HD) To: Stefano Garzarella , freebsd-current , freebsd-hackers@freebsd.org References: Cc: Luigi Rizzo From: Eugene Grosbein Message-ID: <55FAA08B.601@grosbein.net> Date: Thu, 17 Sep 2015 18:14:19 +0700 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:38.0) Gecko/20100101 Thunderbird/38.2.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=0.3 required=5.0 tests=BAYES_00,LOCAL_FROM autolearn=no version=3.3.2 X-Spam-Report: * -2.3 BAYES_00 BODY: Bayes spam probability is 0 to 1% * [score: 0.0000] * 2.6 LOCAL_FROM From my domains X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on hz.grosbein.net X-Mailman-Approved-At: Thu, 17 Sep 2015 11:21:25 +0000 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 17 Sep 2015 11:14:50 -0000 On 15.09.2015 16:31, Stefano Garzarella wrote: > Hi all, > I created a nanoBSD image for my gsoc project (ptnetmap on bhyve). > > I would like to boot this image on USB stick or in the hypervisor as a HD. > I have some problem because if I set NANO_DRIVE="da0" (for USB boot) > in the nanoBSD configuration file, the boot from USB stick works well, > but when I try to boot the same image in the hypervisor as a HD, > I have the following mountroot error: > > Trying to mount root from ufs:/dev/da0s1a [ro]... > mountroot: waiting for device /dev/da0s1a ... > Mounting from ufs:/dev/da0s1a failed with error 19. > > Loader variables: > vfs.root.mountfrom=ufs:/dev/da0s1a > vfs.root.mountfrom.options=ro > > mountroot> > > > At this point I need to manually specify "ufs:/dev/ad0s1a" to properly mount > the root. > > Can you help me? > There is some tricks to avoid this mountroot error? Just make special image for hypervisor using NANO_DRIVE="ad0" From owner-freebsd-current@freebsd.org Thu Sep 17 11:35:16 2015 Return-Path: Delivered-To: freebsd-current@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 140719CDB1E for ; Thu, 17 Sep 2015 11:35:16 +0000 (UTC) (envelope-from ohartman@zedat.fu-berlin.de) Received: from outpost1.zedat.fu-berlin.de (outpost1.zedat.fu-berlin.de [130.133.4.66]) (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 C045A1AA3 for ; Thu, 17 Sep 2015 11:35:15 +0000 (UTC) (envelope-from ohartman@zedat.fu-berlin.de) Received: from inpost2.zedat.fu-berlin.de ([130.133.4.69]) by outpost.zedat.fu-berlin.de (Exim 4.85) with esmtp (envelope-from ) id <1ZcXT4-001sxv-NO>; Thu, 17 Sep 2015 13:35:10 +0200 Received: from p578a69f9.dip0.t-ipconnect.de ([87.138.105.249] helo=freyja.zeit4.iv.bundesimmobilien.de) by inpost2.zedat.fu-berlin.de (Exim 4.85) with esmtpsa (envelope-from ) id <1ZcXT4-000WfB-G2>; Thu, 17 Sep 2015 13:35:10 +0200 Date: Thu, 17 Sep 2015 13:35:09 +0200 From: "O. Hartmann" To: "Pieper, Jeffrey E" Cc: Hans Petter Selasky , freebsd-current Subject: Re: CURRENT: net/igb broken Message-ID: <20150917133509.6c87f5b6@freyja.zeit4.iv.bundesimmobilien.de> In-Reply-To: <2A35EA60C3C77D438915767F458D65688077F87B@ORSMSX111.amr.corp.intel.com> References: <20150915125618.0f752596@freyja.zeit4.iv.bundesimmobilien.de> <55F7FCB5.5090809@selasky.org> <2A35EA60C3C77D438915767F458D65688077F87B@ORSMSX111.amr.corp.intel.com> Organization: FU Berlin X-Mailer: Claws Mail 3.12.0 (GTK+ 2.24.28; amd64-portbld-freebsd11.0) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Originating-IP: 87.138.105.249 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 17 Sep 2015 11:35:16 -0000 On Tue, 15 Sep 2015 18:45:35 +0000 "Pieper, Jeffrey E" wrote: > -----Original Message----- > From: owner-freebsd-current@freebsd.org > [mailto:owner-freebsd-current@freebsd.org] On Behalf Of Hans Petter Selasky > Sent: Tuesday, September 15, 2015 4:11 AM To: O. Hartmann > ; freebsd-current > Subject: Re: CURRENT: net/igb broken > > On 09/15/15 12:56, O. Hartmann wrote: > > Running CURRENT as of today (r287817), it seems that the network system of > > CURRENT is corrupted. The machine in question is a Fujitsu server Primergy > > RX 1330 with two Intel "igb" devices (igb0 and igb1). > > > > the network is now on both devices unreachable. With or without IPFW > > (disabling, having first rule to allow everything in/out) doesn't matter. > > Nothing get to or from that box on any device. > > > > With FreeBSD 11.0-CURRENT #4 r287592: Wed Sep 9 09:09:23 CEST 2015 amd64 I > > had no problems. > > > > Any ideas? > > > > Thanks in advance, > > > > Oliver > > > >Just to rule out r287775, can you disable TSO? > > > >--HPS > > I'm using r827826 (just pulled this morning) with igb and it seems to be > working (icmp and ssh). > > Jeff > > _______________________________________________ > freebsd-current@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" Well, driver igb covers a lot of different hardware. We have a Fujitsu Primergy287700 RX 1330 M1 and it is equipted with a i210 Intel dual GBit NIC. I double checked today, r287910 doesn't work. Since I use nanoBSD, I can change the underlying OS with the very same configuration and I did today with different revisions and 10-STABLE. r287420 and r287700 work also, r287750 also, r287800 does NOT! There were changes to sys/dev/e1000/ between 287750 and r287800 and those obviously do break the igb interface in CURRENT for, at least, i210 NICs. oh From owner-freebsd-current@freebsd.org Thu Sep 17 11:36:03 2015 Return-Path: Delivered-To: freebsd-current@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 BDE929CDBF8 for ; Thu, 17 Sep 2015 11:36:03 +0000 (UTC) (envelope-from damjan.jov@gmail.com) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 9D93A1BE6 for ; Thu, 17 Sep 2015 11:36:03 +0000 (UTC) (envelope-from damjan.jov@gmail.com) Received: by mailman.ysv.freebsd.org (Postfix) id 9AC179CDBF7; Thu, 17 Sep 2015 11:36:03 +0000 (UTC) Delivered-To: current@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 9A4BA9CDBF6 for ; Thu, 17 Sep 2015 11:36:03 +0000 (UTC) (envelope-from damjan.jov@gmail.com) Received: from mail-ob0-x22e.google.com (mail-ob0-x22e.google.com [IPv6:2607:f8b0:4003:c01::22e]) (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 616211BE5 for ; Thu, 17 Sep 2015 11:36:03 +0000 (UTC) (envelope-from damjan.jov@gmail.com) Received: by obbda8 with SMTP id da8so10883696obb.1 for ; Thu, 17 Sep 2015 04:36:02 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:cc :content-type; bh=2GQWugZQORYUvDH8HQNAjBN569dbOYTf1EUpjaYfVpc=; b=cbbHcjzEUvZnKZiwR3oCnyPUoQBRjPLfxzA3l5mgKzOWEIIIXsjtsS/LeKGrqVl8cH KZuSFff5Lr2N5pj5mHJcOwy9Lm3BbWm+x51b4ZexlfmUokRqZJ5j4KEwtPlK503MBOQ7 iwL/PKBfVZCuitdms9RwjikB124qSLVDxF0TV7FdEy45iw5IwsVd6RcHR2lRRm2rBhdp CEeyaArgM89fiNBOw3E/FhAFqvojx2LS4KJEROQ390bs6+uvfghNSOLlRfNxnh7VS56c O2bLFcD+oozhSQ7ZUSq0N5Ids28AlxRsNhJ7306d9XRr5YO0zQJdoD3UlDkTXp5z7Nds BowA== X-Received: by 10.182.117.166 with SMTP id kf6mr1874731obb.58.1442489762637; Thu, 17 Sep 2015 04:36:02 -0700 (PDT) MIME-Version: 1.0 Received: by 10.76.173.229 with HTTP; Thu, 17 Sep 2015 04:35:43 -0700 (PDT) In-Reply-To: <20150917121526.71906673@freyja.zeit4.iv.bundesimmobilien.de> References: <55FA7324.5010603@icloud.com> <20150917121526.71906673@freyja.zeit4.iv.bundesimmobilien.de> From: Damjan Jovanovic Date: Thu, 17 Sep 2015 13:35:43 +0200 Message-ID: Subject: Re: Intel Haswell support - Any updates? Cc: current@freebsd.org Content-Type: text/plain; charset=UTF-8 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 17 Sep 2015 11:36:03 -0000 On Thu, Sep 17, 2015 at 12:15 PM, O. Hartmann wrote: > On Thu, 17 Sep 2015 18:55:10 +0900 > "Lundberg, Johannes" wrote: > >> Looking at those pages it seems like development has basically been >> standing still for the last couple of years. >> >> DragonFlyBSD claims to have support for Haswell, maybe it can work as a >> stand-in while waiting for FreeBSD if you need the GPU for development or >> something.. >> >> >> On Thu, Sep 17, 2015 at 6:41 PM, Andreas Nilsson wrote: >> >> > I guess interested parties could keep an eye on >> > https://github.com/freebsd/freebsd-base-graphics/tree/drm-i915-update-38 >> > and https://wiki.freebsd.org/Graphics >> > >> > Best regards >> > Andreas >> > >> > On Thu, Sep 17, 2015 at 11:20 AM, Lundberg, Johannes < >> > johannes@brilliantservice.co.jp> wrote: >> > >> >> I am wondering the same.. I am sure the very few developers we have are >> >> working as much as they can on this. >> >> >> >> However, the lack of support for the most common hardware since three >> >> years >> >> back is, I believe, preventing many new users, beginners as well as >> >> professionals, from coming to FreeBSD, and I hope the foundation would >> >> pour >> >> some money into this to speed up the development... >> >> >> >> Making it possible to use Wayland on FreeBSD would open up for a whole new >> >> category on devices (mobile, IVI, etc) where many people are now wondering >> >> whether to go Linux, Android or something else.. FreeBSD has the license >> >> and the stability making it very attractive, all that's missing is a >> >> modern >> >> graphics stack.. >> >> >> >> If I had the skills or resources I would pitch in but currently I don't so >> >> all I can do is complain to the foundation. >> >> >> >> I would love to see FreeBSD become the de facto OS in these new areas and >> >> it feels like it could be within reach... Or maybe my feeling is way off, >> >> correct me if I'm wrong :) >> >> >> >> Sorry for the rant... >> >> >> >> Johannes >> >> >> >> On Thu, Sep 17, 2015 at 5:00 PM, Anders Bolt-Evensen < >> >> andersbo87@icloud.com> >> >> wrote: >> >> >> >> > Hello! >> >> > >> >> > I'm just curious about how Intel Haswell GPU support in FreeBSD is >> >> coming >> >> > along? >> >> > What's the ETA of when the driver can be tested? >> >> > >> >> > Anders > > [...] > > It seems FreeBSD has massive problems catching up with the progress in > graphical device support. While "Linux" is concentrated on one single kernel > development, the *BSD have drifted appart over the past decade. My > feeling is that developers start focoussing on one specific *BSD due to the > diversity in their basic architecture. > FreeBSD lacks behind in WiFi chipset support, iGPU support, graphics support in > general as GPUs has become more important over the past years in HPC > environments and not only for displaying. That is a political issue, I guess. > X11 is now claimed by the Linux folks - that is the impression I have - the > spirit of a multiplatform, open system is gone. With systemd on Linux, even > FreeBSD is falling more and more behind. I think this needs to be addressed > on political terrain. Linux wanted to have ZFS - now they participate in > OpenZFS. How long until those L-people move the BSD people aside? ZFS was on Linux years ago, but only as a third-party solution, it won't gain much traction there since kernel devs refuse to keep it in the upstream kernel due to licensing issues and distribitions refuse it install it by default, and people are either still waiting for the vapourware Btrfs or losing heir data to it instead :-D. On FreeBSD, ZFS is integrated into our tree (as is other outstanding CDDL licensed software from Sun, like DTrace which puts Linux's systemtap to shame), and we already boot from it :-). Oh and doesn't FreeBSD also participate in OpenZFS? Systemd is not so much "on Linux" nor a big success there, when Slackware doesn't use it, Debian was forked to run without it, Gentoo doesn't use it by default, and it is broadly hated to the degree that it is driving Linux users to FreeBSD :-). > Well, asking for Haswell support is a bit weird - Skylake ante portam. > Broadwell is already there. Two years ago, we purchased Laptops with Haswell > GPUs. They are now about to be replaced by Skylake-based systems. Running > FreeBSD on Laptops with modern WiFi and iGPU hardware is almost impossible. > Dead hardware or extremely slow. So we decided to switch to Linux. Broadwell at best half-works on Linux and has major issues: crashes, broken suspend/resume, poor support for multiple monitors, and broken console view (http://www.phoronix.com/forums/forum/linux-graphics-x-org-drivers/intel-linux/809842-intel-has-a-ton-of-developers-working-on-their-linux-graphics-stack?p=809940#post809940). NVidia on the other hand supports FreeBSD and works well. Linux copies many WiFi drivers from OpenBSD. Have you tried the WiFi card's Windows driver with NDISulator? What we could also do in future is use a similar idea to use Linux WiFi drivers on FreeBSD. > Interesting to hear that DragonFlyBSD seems to have solved several iGPU issues > and FreeBSD not. Interesting how DragonFlyBSD only supports a single architecture: amd64. > The www pages on that matter are outdated and badly maintained - I try to > consult them on news on a regular basis. One has to digg through piles of > mailing lists. The culture of keeping his clients informed hasn't reached > FreeBSD development yet and that makes me wondering. > > Well, a stopgap for nVidia Nouveau support seems to be the PRIME support in > FreeBSD's kernel. I do not understand much of that matter, but the kernel is > not well fitted for moving buffers from/to different GPU adaptors. That seems > also to be important for future architectures concerning OpenCL and GPGPU - a > matter I was interested in due to a physical modelling interest. But in that > matter there leads no way around Linux. > _______________________________________________ > freebsd-current@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" Damjan From owner-freebsd-current@freebsd.org Thu Sep 17 11:37:16 2015 Return-Path: Delivered-To: freebsd-current@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 340A79CDCF2 for ; Thu, 17 Sep 2015 11:37:16 +0000 (UTC) (envelope-from ohartman@zedat.fu-berlin.de) Received: from outpost1.zedat.fu-berlin.de (outpost1.zedat.fu-berlin.de [130.133.4.66]) (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 E23851D12 for ; Thu, 17 Sep 2015 11:37:15 +0000 (UTC) (envelope-from ohartman@zedat.fu-berlin.de) Received: from inpost2.zedat.fu-berlin.de ([130.133.4.69]) by outpost.zedat.fu-berlin.de (Exim 4.85) with esmtp (envelope-from ) id <1ZcXV3-001tga-Ac>; Thu, 17 Sep 2015 13:37:13 +0200 Received: from p578a69f9.dip0.t-ipconnect.de ([87.138.105.249] helo=freyja.zeit4.iv.bundesimmobilien.de) by inpost2.zedat.fu-berlin.de (Exim 4.85) with esmtpsa (envelope-from ) id <1ZcXV3-000Wr3-37>; Thu, 17 Sep 2015 13:37:13 +0200 Date: Thu, 17 Sep 2015 13:37:12 +0200 From: "O. Hartmann" To: "Pieper, Jeffrey E" Cc: Hans Petter Selasky , freebsd-current Subject: Re: CURRENT: net/igb broken Message-ID: <20150917133712.0ffd01ee@freyja.zeit4.iv.bundesimmobilien.de> In-Reply-To: <20150917133509.6c87f5b6@freyja.zeit4.iv.bundesimmobilien.de> References: <20150915125618.0f752596@freyja.zeit4.iv.bundesimmobilien.de> <55F7FCB5.5090809@selasky.org> <2A35EA60C3C77D438915767F458D65688077F87B@ORSMSX111.amr.corp.intel.com> <20150917133509.6c87f5b6@freyja.zeit4.iv.bundesimmobilien.de> Organization: FU Berlin X-Mailer: Claws Mail 3.12.0 (GTK+ 2.24.28; amd64-portbld-freebsd11.0) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Originating-IP: 87.138.105.249 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 17 Sep 2015 11:37:16 -0000 On Thu, 17 Sep 2015 13:35:09 +0200 "O. Hartmann" wrote: > On Tue, 15 Sep 2015 18:45:35 +0000 > "Pieper, Jeffrey E" wrote: > > > -----Original Message----- > > From: owner-freebsd-current@freebsd.org > > [mailto:owner-freebsd-current@freebsd.org] On Behalf Of Hans Petter Selasky > > Sent: Tuesday, September 15, 2015 4:11 AM To: O. Hartmann > > ; freebsd-current > > Subject: Re: CURRENT: net/igb broken > > > > On 09/15/15 12:56, O. Hartmann wrote: > > > Running CURRENT as of today (r287817), it seems that the network system of > > > CURRENT is corrupted. The machine in question is a Fujitsu server Primergy > > > RX 1330 with two Intel "igb" devices (igb0 and igb1). > > > > > > the network is now on both devices unreachable. With or without IPFW > > > (disabling, having first rule to allow everything in/out) doesn't matter. > > > Nothing get to or from that box on any device. > > > > > > With FreeBSD 11.0-CURRENT #4 r287592: Wed Sep 9 09:09:23 CEST 2015 > > > amd64 I had no problems. > > > > > > Any ideas? > > > > > > Thanks in advance, > > > > > > Oliver > > > > > >Just to rule out r287775, can you disable TSO? > > > > > >--HPS > > > > I'm using r827826 (just pulled this morning) with igb and it seems to be > > working (icmp and ssh). > > > > Jeff > > > > _______________________________________________ > > freebsd-current@freebsd.org mailing list > > https://lists.freebsd.org/mailman/listinfo/freebsd-current > > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" > > Well, driver igb covers a lot of different hardware. We have a Fujitsu > Primergy287700 RX 1330 M1 and it is equipted with a i210 Intel dual GBit NIC. > > I double checked today, r287910 doesn't work. Since I use nanoBSD, I can > change the underlying OS with the very same configuration and I did today with > different revisions and 10-STABLE. r287420 and r287700 work also, r287750 > also, r287800 does NOT! > > There were changes to sys/dev/e1000/ between 287750 and r287800 and those > obviously do break the igb interface in CURRENT for, at least, i210 NICs. > > oh > _______________________________________________ > freebsd-current@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" r287762 broke the system From owner-freebsd-current@freebsd.org Thu Sep 17 11:44:04 2015 Return-Path: Delivered-To: freebsd-current@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 CC2879CE0ED for ; Thu, 17 Sep 2015 11:44:04 +0000 (UTC) (envelope-from theraven@FreeBSD.org) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id AFCA810E7 for ; Thu, 17 Sep 2015 11:44:04 +0000 (UTC) (envelope-from theraven@FreeBSD.org) Received: by mailman.ysv.freebsd.org (Postfix) id AD2B29CE0E8; Thu, 17 Sep 2015 11:44:04 +0000 (UTC) Delivered-To: current@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 ACBFD9CE0E7 for ; Thu, 17 Sep 2015 11:44:04 +0000 (UTC) (envelope-from theraven@FreeBSD.org) Received: from theravensnest.org (theraven.freebsd.your.org [216.14.102.27]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "cloud.theravensnest.org", Issuer "StartCom Class 1 Primary Intermediate Server CA" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 7DCB210E6 for ; Thu, 17 Sep 2015 11:44:03 +0000 (UTC) (envelope-from theraven@FreeBSD.org) Received: from c124.sec.cl.cam.ac.uk (c124.sec.cl.cam.ac.uk [128.232.18.124]) (authenticated bits=0) by theravensnest.org (8.15.2/8.15.2) with ESMTPSA id t8HBhxR7049820 (version=TLSv1 cipher=ECDHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 17 Sep 2015 11:44:00 GMT (envelope-from theraven@FreeBSD.org) Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2102\)) Subject: Re: Intel Haswell support - Any updates? From: David Chisnall In-Reply-To: Date: Thu, 17 Sep 2015 12:43:59 +0100 Cc: Andreas Nilsson , Anders Bolt-Evensen , current@freebsd.org Content-Transfer-Encoding: quoted-printable Message-Id: <114F22EF-61E3-4D75-84FB-9D6E3FBCB8F3@FreeBSD.org> References: <55FA7324.5010603@icloud.com> <09A515F2-44BA-4DF0-9792-D4C56EEB9D7C@FreeBSD.org> To: "Lundberg, Johannes" X-Mailer: Apple Mail (2.2102) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 17 Sep 2015 11:44:04 -0000 On 17 Sep 2015, at 11:31, Lundberg, Johannes = wrote: >=20 > Anyway, I wish the foundation would support the graphics team by = sponsoring this development=E2=80=A6 The Foundation did fund a lot of this work, and likely will again. The = problem is not willingness of the Foundation to fund it, nor = availability of funds. As with WiFi, it=E2=80=99s availability of = people who have both the competence and interest to do the work and the = availability to work as consultants for the Foundation. Long term, the real solution is to convince GPU vendors to put as much = effort into funding FreeBSD driver development as they do into funding = Linux and Windows driver development. The Foundation has been reaching = out in this direction, but it=E2=80=99s far more compelling if people = can document cases where lack of FreeBSD support has cost a vendor = sales. If you=E2=80=99ve bought a system with an nVidia or AMD GPU (or, = ideally, if your company has bought a few thousand) because of lack of = FreeBSD support from Intel, then let Intel know. =20 David From owner-freebsd-current@freebsd.org Thu Sep 17 12:48:27 2015 Return-Path: Delivered-To: freebsd-current@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 D1BDA9CF653 for ; Thu, 17 Sep 2015 12:48:27 +0000 (UTC) (envelope-from slw@zxy.spb.ru) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id B67BA12D2 for ; Thu, 17 Sep 2015 12:48:27 +0000 (UTC) (envelope-from slw@zxy.spb.ru) Received: by mailman.ysv.freebsd.org (Postfix) id B63DF9CF652; Thu, 17 Sep 2015 12:48:27 +0000 (UTC) Delivered-To: current@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 B5DE99CF651 for ; Thu, 17 Sep 2015 12:48:27 +0000 (UTC) (envelope-from slw@zxy.spb.ru) Received: from zxy.spb.ru (zxy.spb.ru [195.70.199.98]) (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 6BDCC12D1; Thu, 17 Sep 2015 12:48:27 +0000 (UTC) (envelope-from slw@zxy.spb.ru) Received: from slw by zxy.spb.ru with local (Exim 4.84 (FreeBSD)) (envelope-from ) id 1ZcYbo-000Ekj-Du; Thu, 17 Sep 2015 15:48:16 +0300 Date: Thu, 17 Sep 2015 15:48:16 +0300 From: Slawa Olhovchenkov To: David Chisnall Cc: "Lundberg, Johannes" , Andreas Nilsson , Anders Bolt-Evensen , current@freebsd.org Subject: Re: Intel Haswell support - Any updates? Message-ID: <20150917124816.GT3158@zxy.spb.ru> References: <55FA7324.5010603@icloud.com> <09A515F2-44BA-4DF0-9792-D4C56EEB9D7C@FreeBSD.org> <114F22EF-61E3-4D75-84FB-9D6E3FBCB8F3@FreeBSD.org> MIME-Version: 1.0 Content-Type: text/plain; charset=koi8-r Content-Disposition: inline In-Reply-To: <114F22EF-61E3-4D75-84FB-9D6E3FBCB8F3@FreeBSD.org> User-Agent: Mutt/1.5.23 (2014-03-12) X-SA-Exim-Connect-IP: X-SA-Exim-Mail-From: slw@zxy.spb.ru X-SA-Exim-Scanned: No (on zxy.spb.ru); SAEximRunCond expanded to false X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 17 Sep 2015 12:48:27 -0000 On Thu, Sep 17, 2015 at 12:43:59PM +0100, David Chisnall wrote: > On 17 Sep 2015, at 11:31, Lundberg, Johannes wrote: > > > > Anyway, I wish the foundation would support the graphics team by sponsoring this development... > > The Foundation did fund a lot of this work, and likely will again. > The problem is not willingness of the Foundation to fund it, nor > availability of funds. As with WiFi, it's availability of people > who have both the competence and interest to do the work and the > availability to work as consultants for the Foundation. > > Long term, the real solution is to convince GPU vendors to put as > much effort into funding FreeBSD driver development as they do into > funding Linux and Windows driver development. The Foundation has > been reaching out in this direction, but it's far more compelling if > people can document cases where lack of FreeBSD support has cost a > vendor sales. If you've bought a system with an nVidia or AMD GPU > (or, ideally, if your company has bought a few thousand) because of > lack of FreeBSD support from Intel, then let Intel know. Impotant: if you already buy Intel system -- Intel will be ignored you, only future sales important. From owner-freebsd-current@freebsd.org Thu Sep 17 12:52:27 2015 Return-Path: Delivered-To: freebsd-current@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 EA3429CF8CB for ; Thu, 17 Sep 2015 12:52:26 +0000 (UTC) (envelope-from oliver.pinter@hardenedbsd.org) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 9B18A194A for ; Thu, 17 Sep 2015 12:52:26 +0000 (UTC) (envelope-from oliver.pinter@hardenedbsd.org) Received: by mailman.ysv.freebsd.org (Postfix) id 809C29CF8C9; Thu, 17 Sep 2015 12:52:26 +0000 (UTC) Delivered-To: current@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 8027D9CF8C8 for ; Thu, 17 Sep 2015 12:52:26 +0000 (UTC) (envelope-from oliver.pinter@hardenedbsd.org) Received: from mail-wi0-f174.google.com (mail-wi0-f174.google.com [209.85.212.174]) (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 BD0A118FA for ; Thu, 17 Sep 2015 12:52:25 +0000 (UTC) (envelope-from oliver.pinter@hardenedbsd.org) Received: by wicgb1 with SMTP id gb1so116578399wic.1 for ; Thu, 17 Sep 2015 05:52:24 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:date:message-id:subject:from:to:cc :content-type; bh=e06hvx5agPqkpK2hkNC2avQ/C0mfD3Ytq804opZ6l1s=; b=kL/fsDV7hWGLaRtUTsej22bvbiw0g8WjAND6Y0rPpu0wNHaMJegxsyB44awLRmqiy2 r3dqLRJcEzS1N5vn/0fe2LwYzy2TemTcMzGc2whJsAg7RlbUhjhzUKjQsJ8L/mAkYTR+ 192hSTNA+cLdW7JQbk49BG7r49LQx5h4vqboaxw5vyjVHJY4QapRHKapbRkg1WDyRKms L/K/d4WVeaWWsscqPiwQaduBJmleNu2ESPRJ9BaHXz0Thz41tRlIvykNtpEDR9PGCRez 7xFjAWgPM4LBPZcpSYlRfmrFmA1wrgfeQEKz2LMW9K6hX4knkGlkhpphSbrV6+bo21Vv scww== X-Gm-Message-State: ALoCoQmx3RYCs3aNwQfTProhXltOT31MWCvBENsP3Qq6d8hWkFBK+5lYCodU0+PQG+zWJeqmkb7e MIME-Version: 1.0 X-Received: by 10.180.82.7 with SMTP id e7mr7489755wiy.19.1442494343961; Thu, 17 Sep 2015 05:52:23 -0700 (PDT) Received: by 10.194.240.226 with HTTP; Thu, 17 Sep 2015 05:52:23 -0700 (PDT) Date: Thu, 17 Sep 2015 14:52:23 +0200 Message-ID: Subject: ZFS panic From: Oliver Pinter To: current@freebsd.org Cc: jmg@freebsd.org, avg@freebsd.org Content-Type: text/plain; charset=UTF-8 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 17 Sep 2015 12:52:27 -0000 Hi All! We got this panic on modified FreeBSD (we not touched the ZFS part). panic: solaris assert: error || lr->lr_length <= zp->z_blksz, file: /usr/src/sys/cddl/contrib/opensolaris/uts/common/fs/zfs/zfs_vnops.c, line: 1355 cpuid = 6 KDB: stack backtrace: #0 0xffffffff80639527 at kdb_backtrace+0x67 #1 0xffffffff805fd509 at vpanic+0x189 #2 0xffffffff805fd593 at panic+0x43 #3 0xffffffff802ce3aa at assfail+0x1a #4 0xffffffff8039c391 at zfs_get_data+0x391 #5 0xffffffff803afeac at zil_commit+0x94c #6 0xffffffff803a39d8 at zfs_freebsd_fsync+0xc8 #7 0xffffffff8089a8a7 at VOP_FSYNC_APV+0xf7 #8 0xffffffff806afc40 at sys_fsync+0x170 #9 0xffffffff808311bc at amd64_syscall+0x2bc #10 0xffffffff8081285b at Xfast_syscall+0xfb Uptime: 7d5h19m13s Dumping 8207 out of 32742 MB:..1%..11%..21%..31%..41%..51%..61%..71%..81%..91% Dump complete Automatic reboot in 15 seconds - press a key on the console to abort Rebooting... cpu_reset: Restarting BSP cpu_reset_proxy: Stopped CPU 6 (kgdb) bt #0 doadump (textdump=) at pcpu.h:221 #1 0xffffffff805fcf70 in kern_reboot (howto=260) at /usr/src/sys/kern/kern_shutdown.c:329 #2 0xffffffff805fd548 in vpanic (fmt=, ap=) at /usr/src/sys/kern/kern_shutdown.c:626 #3 0xffffffff805fd593 in panic (fmt=0x0) at /usr/src/sys/kern/kern_shutdown.c:557 #4 0xffffffff802ce3aa in assfail (a=, f=, l=) at /usr/src/sys/cddl/compat/opensolaris/kern/opensolaris_cmn_err.c:81 #5 0xffffffff8039c391 in zfs_get_data (arg=, lr=, buf=, zio=0xfffff8019eeb1760) at /usr/src/sys/cddl/contrib/opensolaris/uts/common/fs/zfs/zfs_vnops.c:1355 #6 0xffffffff803afeac in zil_commit (zilog=0xfffff8001d518800, foid=) at /usr/src/sys/cddl/contrib/opensolaris/uts/common/fs/zfs/zil.c:1107 #7 0xffffffff803a39d8 in zfs_freebsd_fsync (ap=) at /usr/src/sys/cddl/contrib/opensolaris/uts/common/fs/zfs/zfs_vnops.c:2797 #8 0xffffffff8089a8a7 in VOP_FSYNC_APV (vop=, a=) at vnode_if.c:1328 #9 0xffffffff806afc40 in sys_fsync (td=0xfffff8001d0429c0, uap=) at vnode_if.h:549 #10 0xffffffff808311bc in amd64_syscall (td=0xfffff8001d0429c0, traced=0) at subr_syscall.c:139 #11 0xffffffff8081285b in Xfast_syscall () at /usr/src/sys/amd64/amd64/exception.S:394 #12 0x000000000058d23a in ?? () Previous frame inner to this frame (corrupt stack?) Current language: auto; currently minimal (kgdb) f 5 #5 0xffffffff8039c391 in zfs_get_data (arg=, lr=, buf=, zio=0xfffff8019eeb1760) at /usr/src/sys/cddl/contrib/opensolaris/uts/common/fs/zfs/zfs_vnops.c:1355 1355 ASSERT(error || lr->lr_length <= zp->z_blksz); (kgdb) l 1350 ASSERT(db->db_offset == offset); 1351 ASSERT(db->db_size == size); 1352 1353 error = dmu_sync(zio, lr->lr_common.lrc_txg, 1354 zfs_get_done, zgd); 1355 ASSERT(error || lr->lr_length <= zp->z_blksz); 1356 1357 /* 1358 * On success, we need to wait for the write I/O 1359 * initiated by dmu_sync() to complete before we can (kgdb) p *lr Cannot access memory at address 0xa5a5a5a5a5a5a5a5 (kgdb) p *zp Cannot access memory at address 0xa5a5a5a5a5a5a5a5 (kgdb) Undefined info command: "regs". Try "help info". (kgdb) info registers rax 0x0 0 rbx 0xfffff804aab14e00 -8776049406464 rcx 0x0 0 rdx 0x0 0 rsi 0x0 0 rdi 0x0 0 rbp 0xfffffe085f78e8f0 0xfffffe085f78e8f0 rsp 0xfffffe085f78e890 0xfffffe085f78e890 r8 0x0 0 r9 0x0 0 r10 0x0 0 r11 0x0 0 r12 0x0 0 r13 0xfffffe034cecd0b8 -2184847765320 r14 0x20000 131072 r15 0x0 0 rip 0xffffffff8039c391 0xffffffff8039c391 eflags 0x0 0 cs 0x0 0 ss 0x0 0 ds 0x0 0 es 0x0 0 fs 0x0 0 gs 0x0 0 [...] ffffffff8039c2f9: 48 8b 7d b0 mov -0x50(%rbp),%rdi ffffffff8039c2fd: 48 89 d9 mov %rbx,%rcx ffffffff8039c300: e8 db 50 f6 ff callq ffffffff803013e0 ffffffff8039c305: 41 89 c4 mov %eax,%r12d ffffffff8039c308: 41 83 fc 25 cmp $0x25,%r12d ffffffff8039c30c: 75 53 jne ffffffff8039c361 ffffffff8039c30e: 49 c7 45 00 14 00 00 movq $0x14,0x0(%r13) ffffffff8039c315: 00 ffffffff8039c316: 45 31 e4 xor %r12d,%r12d ffffffff8039c319: eb 29 jmp ffffffff8039c344 ffffffff8039c31b: 48 8b 3c 25 38 a4 c1 mov 0xffffffff80c1a438,%rdi ffffffff8039c322: 80 ffffffff8039c323: 41 bc 02 00 00 00 mov $0x2,%r12d ffffffff8039c329: 48 85 ff test %rdi,%rdi ffffffff8039c32c: 74 16 je ffffffff8039c344 ffffffff8039c32e: be 02 00 00 00 mov $0x2,%esi ffffffff8039c333: 31 d2 xor %edx,%edx ffffffff8039c335: 31 c9 xor %ecx,%ecx ffffffff8039c337: 45 31 c0 xor %r8d,%r8d ffffffff8039c33a: 45 31 c9 xor %r9d,%r9d ffffffff8039c33d: ff 14 25 78 9a c6 80 callq *0xffffffff80c69a78 ffffffff8039c344: 48 89 df mov %rbx,%rdi ffffffff8039c347: 44 89 e6 mov %r12d,%esi ffffffff8039c34a: e8 f1 fb ff ff callq ffffffff8039bf40 ffffffff8039c34f: 44 89 e0 mov %r12d,%eax ffffffff8039c352: 48 83 c4 38 add $0x38,%rsp ffffffff8039c356: 5b pop %rbx ffffffff8039c357: 41 5c pop %r12 ffffffff8039c359: 41 5d pop %r13 ffffffff8039c35b: 41 5e pop %r14 ffffffff8039c35d: 41 5f pop %r15 ffffffff8039c35f: 5d pop %rbp ffffffff8039c360: c3 retq ffffffff8039c361: 45 85 e4 test %r12d,%r12d ffffffff8039c364: 75 de jne ffffffff8039c344 ffffffff8039c366: 48 8b 45 d0 mov -0x30(%rbp),%rax ffffffff8039c36a: 8b 80 cc 00 00 00 mov 0xcc(%rax),%eax ffffffff8039c370: 45 31 e4 xor %r12d,%r12d ffffffff8039c373: 49 39 45 30 cmp %rax,0x30(%r13) ffffffff8039c377: 76 d6 jbe ffffffff8039c34f ffffffff8039c379: 48 c7 c7 60 d5 91 80 mov $0xffffffff8091d560,%rdi ffffffff8039c380: 48 c7 c6 f0 d4 91 80 mov $0xffffffff8091d4f0,%rsi ffffffff8039c387: ba 4b 05 00 00 mov $0x54b,%edx ffffffff8039c38c: e8 ff 1f f3 ff callq ffffffff802ce390 ffffffff8039c391: eb bc jmp ffffffff8039c34f ffffffff8039c393: 66 66 66 66 2e 0f 1f nopw %cs:0x0(%rax,%rax,1) ffffffff8039c39a: 84 00 00 00 00 00 If you need more details, then please ping me, I have a core dump from the crash. From owner-freebsd-current@freebsd.org Thu Sep 17 13:13:35 2015 Return-Path: Delivered-To: freebsd-current@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 446B09CD1E2 for ; Thu, 17 Sep 2015 13:13:35 +0000 (UTC) (envelope-from mcdouga9@egr.msu.edu) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 2755714DD for ; Thu, 17 Sep 2015 13:13:35 +0000 (UTC) (envelope-from mcdouga9@egr.msu.edu) Received: by mailman.ysv.freebsd.org (Postfix) id 2706C9CD1DF; Thu, 17 Sep 2015 13:13:35 +0000 (UTC) Delivered-To: current@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 26AEE9CD1DE for ; Thu, 17 Sep 2015 13:13:35 +0000 (UTC) (envelope-from mcdouga9@egr.msu.edu) Received: from mail.egr.msu.edu (boomhauer.egr.msu.edu [35.9.37.164]) by mx1.freebsd.org (Postfix) with ESMTP id F22FE14DC; Thu, 17 Sep 2015 13:13:34 +0000 (UTC) (envelope-from mcdouga9@egr.msu.edu) Received: from boomhauer (localhost [127.0.0.1]) by mail.egr.msu.edu (Postfix) with ESMTP id AFB42574AD; Thu, 17 Sep 2015 09:13:33 -0400 (EDT) X-Virus-Scanned: amavisd-new at egr.msu.edu Received: from mail.egr.msu.edu ([127.0.0.1]) by boomhauer (boomhauer.egr.msu.edu [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Eaj3o-VSHqRS; Thu, 17 Sep 2015 09:13:33 -0400 (EDT) Received: from daemon.localdomain (daemon.egr.msu.edu [35.9.44.65]) by mail.egr.msu.edu (Postfix) with ESMTP id 61C3557493; Thu, 17 Sep 2015 09:13:33 -0400 (EDT) Received: by daemon.localdomain (Postfix, from userid 21281) id 5D4341DD01; Thu, 17 Sep 2015 09:13:33 -0400 (EDT) Date: Thu, 17 Sep 2015 09:13:33 -0400 From: Adam McDougall To: David Chisnall Cc: current@freebsd.org Subject: Re: Intel Haswell support - Any updates? Message-ID: <20150917131333.GN1247@egr.msu.edu> References: <55FA7324.5010603@icloud.com> <09A515F2-44BA-4DF0-9792-D4C56EEB9D7C@FreeBSD.org> <114F22EF-61E3-4D75-84FB-9D6E3FBCB8F3@FreeBSD.org> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <114F22EF-61E3-4D75-84FB-9D6E3FBCB8F3@FreeBSD.org> User-Agent: Mutt/1.5.23 (2014-03-12) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 17 Sep 2015 13:13:35 -0000 On Thu, Sep 17, 2015 at 12:43:59PM +0100, David Chisnall wrote: On 17 Sep 2015, at 11:31, Lundberg, Johannes wrote: > > Anyway, I wish the foundation would support the graphics team by sponsoring this development… The Foundation did fund a lot of this work, and likely will again. The problem is not willingness of the Foundation to fund it, nor availability of funds. I was not aware of this and am happy to hear it! Long term, the real solution is to convince GPU vendors to put as much effort into funding FreeBSD driver development as they do into funding Linux and Windows driver development. The Foundation has been reaching out in this direction, Glad to hear this too. It is more comforting to hear. but it’s far more compelling if people can document cases where lack of FreeBSD support has cost a vendor sales. If you’ve bought a system with an nVidia or AMD GPU (or, ideally, if your company has bought a few thousand) because of lack of FreeBSD support from Intel, then let Intel know. David In all seriousness, do you have a suggested contact for us? I can't offer bulk sales avoidance but on a personal level I am clinging to a 4.5 year old laptop and would replace it tomorrow with another higher end model if I had any practical choices for FreeBSD graphics support. Even nVidia is not a checkbox solution on laptops because as far as I understand it you still have to deal with Optimus which cannot simply be disabled as in the past. I also have considerable stability problems with the nVidia driver on my desktops and I will be reporting it very soon after some debugging. Thanks. From owner-freebsd-current@freebsd.org Thu Sep 17 13:41:46 2015 Return-Path: Delivered-To: freebsd-current@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 6CB969CE2E7 for ; Thu, 17 Sep 2015 13:41:46 +0000 (UTC) (envelope-from johannes@brilliantservice.co.jp) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 451F81128 for ; Thu, 17 Sep 2015 13:41:46 +0000 (UTC) (envelope-from johannes@brilliantservice.co.jp) Received: by mailman.ysv.freebsd.org (Postfix) id 44B639CE2E6; Thu, 17 Sep 2015 13:41:46 +0000 (UTC) Delivered-To: current@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 2A4F89CE2E5 for ; Thu, 17 Sep 2015 13:41:46 +0000 (UTC) (envelope-from johannes@brilliantservice.co.jp) Received: from mail-qg0-f51.google.com (mail-qg0-f51.google.com [209.85.192.51]) (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 DDA2B1126 for ; Thu, 17 Sep 2015 13:41:45 +0000 (UTC) (envelope-from johannes@brilliantservice.co.jp) Received: by qgev79 with SMTP id v79so12641894qge.0 for ; Thu, 17 Sep 2015 06:41:44 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=sFYOt0CvWfxcjqCcVIFF1KVpXjJ9kY8lZtec7IqUIvw=; b=Ub/xdS2kUP+LQOG05psFo1Mqi3u5YnVqecxXEEajxEn/9hCAAmZZffl5v3illbZtcw YSUv+JA0wDGGQxA8eDH7dFqeRkzRoBwWYCOMju7t7PKxE7ThtXTB52wK90QluJLMnpkT ApDTAyIxNLev4jwbeEHWOHmdtE7BRzDnDfYanicLsJqxgw9BAHwikGe/XkQmuVqf1hrM e2kI8Ec8+yij5LHdFlWa5xJ00sVyjg5Zo1HD8H4AILKd1mRzcrvVWEvKTMW3Csdi6wN5 6p9FA8TYqU7slErjSIyTBFhn4zAksXQljGACc20rOdGaI7yStGYfze7IGUf0+c7eb0Mw /+Lg== X-Gm-Message-State: ALoCoQmP5paUMlfN0FWTLOWjIvQmRGnysY1mxoMfq3Bg9SHvcitn4Dx+Tl7m87y/4gpRFQQjNBPWCvo7TpEroopYqh/XptCJs5IL1u9xZj7XRRGQhFsFK3zAt7ishj5+Mb/QCHQwbJh3 MIME-Version: 1.0 X-Received: by 10.140.131.135 with SMTP id 129mr54946405qhd.31.1442497304045; Thu, 17 Sep 2015 06:41:44 -0700 (PDT) Received: by 10.55.166.75 with HTTP; Thu, 17 Sep 2015 06:41:43 -0700 (PDT) In-Reply-To: <20150917131333.GN1247@egr.msu.edu> References: <55FA7324.5010603@icloud.com> <09A515F2-44BA-4DF0-9792-D4C56EEB9D7C@FreeBSD.org> <114F22EF-61E3-4D75-84FB-9D6E3FBCB8F3@FreeBSD.org> <20150917131333.GN1247@egr.msu.edu> Date: Thu, 17 Sep 2015 22:41:43 +0900 Message-ID: Subject: Re: Intel Haswell support - Any updates? From: "Lundberg, Johannes" To: Adam McDougall Cc: David Chisnall , "current@freebsd.org" Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.20 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 17 Sep 2015 13:41:46 -0000 Same here. I would personally definitely buy new hardware from Intel if FreeBSD worked on it (not vesa...) However, the problem now is not the driver right? But the whole graphics stack which has to be rewritten to work with new generation graphics like KMS, Wayland, etc? On Thursday, September 17, 2015, Adam McDougall wrote: > On Thu, Sep 17, 2015 at 12:43:59PM +0100, David Chisnall wrote: > > On 17 Sep 2015, at 11:31, Lundberg, Johannes < > johannes@brilliantservice.co.jp > wrote: > > > > Anyway, I wish the foundation would support the graphics team by > sponsoring this development=E2=80=A6 > > The Foundation did fund a lot of this work, and likely will again. The > problem is not > willingness of the Foundation to fund it, nor availability of funds. > > I was not aware of this and am happy to hear it! > > Long term, the real solution is to convince GPU vendors to put as much > effort into > funding FreeBSD driver development as they do into funding Linux and > Windows driver > development. The Foundation has been reaching out in this direction, > > Glad to hear this too. It is more comforting to hear. > > but it=E2=80=99s far more compelling if people can document cases where= lack of > FreeBSD support > has cost a vendor sales. If you=E2=80=99ve bought a system with an nVi= dia or > AMD GPU (or, > ideally, if your company has bought a few thousand) because of lack of > FreeBSD support > from Intel, then let Intel know. > > David > > In all seriousness, do you have a suggested contact for us? I can't offe= r > bulk sales > avoidance but on a personal level I am clinging to a 4.5 year old laptop > and would > replace it tomorrow with another higher end model if I had any practical > choices for > FreeBSD graphics support. Even nVidia is not a checkbox solution on > laptops because as > far as I understand it you still have to deal with Optimus which cannot > simply be > disabled as in the past. I also have considerable stability problems wit= h > the nVidia > driver on my desktops and I will be reporting it very soon after some > debugging. Thanks. > _______________________________________________ > freebsd-current@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org > " --=20 -- Johannes Lundberg BRILLIANTSERVICE CO., LTD. --=20 =3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D= -=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D- =E7=A7=98=E5=AF=86=E4=BF=9D=E6=8C=81=E3=81=AB=E3=81=A4=E3=81=84=E3=81=A6=EF= =BC=9A=E3=81=93=E3=81=AE=E9=9B=BB=E5=AD=90=E3=83=A1=E3=83=BC=E3=83=AB=E3=81= =AF=E3=80=81=E5=90=8D=E5=AE=9B=E4=BA=BA=E3=81=AB=E9=80=81=E4=BF=A1=E3=81=97= =E3=81=9F=E3=82=82=E3=81=AE=E3=81=A7=E3=81=82=E3=82=8A=E3=80=81=E7=A7=98=E5= =8C=BF=E7=89=B9=E6=A8=A9=E3=81=AE=E5=AF=BE=E8=B1=A1=E3=81=A8=E3=81=AA=E3=82= =8B=E6=83=85=E5=A0=B1=E3=82=92=E5=90=AB=E3=82=93=E3=81=A7=E3=81=84=E3=81=BE= =E3=81=99=E3=80=82 =E3=82=82=E3=81=97=E3=80=81=E5=90=8D=E5=AE=9B=E4=BA=BA=E4=BB=A5=E5=A4=96=E3= =81=AE=E6=96=B9=E3=81=8C=E5=8F=97=E4=BF=A1=E3=81=95=E3=82=8C=E3=81=9F=E5=A0= =B4=E5=90=88=E3=80=81=E3=81=93=E3=81=AE=E3=83=A1=E3=83=BC=E3=83=AB=E3=81=AE= =E7=A0=B4=E6=A3=84=E3=80=81=E3=81=8A=E3=82=88=E3=81=B3=E3=81=93=E3=81=AE=E3= =83=A1=E3=83=BC=E3=83=AB=E3=81=AB=E9=96=A2=E3=81=99=E3=82=8B=E4=B8=80=E5=88= =87=E3=81=AE=E9=96=8B=E7=A4=BA=E3=80=81 =E8=A4=87=E5=86=99=E3=80=81=E9=85=8D=E5=B8=83=E3=80=81=E3=81=9D=E3=81=AE=E4= =BB=96=E3=81=AE=E5=88=A9=E7=94=A8=E3=80=81=E3=81=BE=E3=81=9F=E3=81=AF=E8=A8= =98=E8=BC=89=E5=86=85=E5=AE=B9=E3=81=AB=E5=9F=BA=E3=81=A5=E3=81=8F=E3=81=84= =E3=81=8B=E3=81=AA=E3=82=8B=E8=A1=8C=E5=8B=95=E3=82=82=E3=81=95=E3=82=8C=E3= =81=AA=E3=81=84=E3=82=88=E3=81=86=E3=81=8A=E9=A1=98=E3=81=84=E7=94=B3=E3=81= =97=E4=B8=8A=E3=81=92=E3=81=BE=E3=81=99=E3=80=82 --- 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. From owner-freebsd-current@freebsd.org Thu Sep 17 13:48:11 2015 Return-Path: Delivered-To: freebsd-current@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 5B1A39CE5E7 for ; Thu, 17 Sep 2015 13:48:11 +0000 (UTC) (envelope-from theraven@FreeBSD.org) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 3A8E713B0 for ; Thu, 17 Sep 2015 13:48:11 +0000 (UTC) (envelope-from theraven@FreeBSD.org) Received: by mailman.ysv.freebsd.org (Postfix) id 37D8B9CE5E5; Thu, 17 Sep 2015 13:48:11 +0000 (UTC) Delivered-To: current@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 3767D9CE5E4 for ; Thu, 17 Sep 2015 13:48:11 +0000 (UTC) (envelope-from theraven@FreeBSD.org) Received: from theravensnest.org (theraven.freebsd.your.org [216.14.102.27]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "cloud.theravensnest.org", Issuer "StartCom Class 1 Primary Intermediate Server CA" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id E03A413AE for ; Thu, 17 Sep 2015 13:48:09 +0000 (UTC) (envelope-from theraven@FreeBSD.org) Received: from dhcp-172-17-234-62.eduroam.wireless.private.cam.ac.uk (global-1-31.nat.csx.cam.ac.uk [131.111.184.31]) (authenticated bits=0) by theravensnest.org (8.15.2/8.15.2) with ESMTPSA id t8HDlnkJ050535 (version=TLSv1 cipher=ECDHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 17 Sep 2015 13:47:51 GMT (envelope-from theraven@FreeBSD.org) X-Authentication-Warning: theravensnest.org: Host global-1-31.nat.csx.cam.ac.uk [131.111.184.31] claimed to be dhcp-172-17-234-62.eduroam.wireless.private.cam.ac.uk Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2102\)) Subject: Re: Intel Haswell support - Any updates? From: David Chisnall In-Reply-To: Date: Thu, 17 Sep 2015 14:47:43 +0100 Cc: Adam McDougall , "current@freebsd.org" Content-Transfer-Encoding: quoted-printable Message-Id: References: <55FA7324.5010603@icloud.com> <09A515F2-44BA-4DF0-9792-D4C56EEB9D7C@FreeBSD.org> <114F22EF-61E3-4D75-84FB-9D6E3FBCB8F3@FreeBSD.org> <20150917131333.GN1247@egr.msu.edu> To: "Lundberg, Johannes" X-Mailer: Apple Mail (2.2102) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 17 Sep 2015 13:48:11 -0000 On 17 Sep 2015, at 14:41, Lundberg, Johannes = wrote: >=20 > However, the problem now is not the driver right? But the whole = graphics > stack which has to be rewritten to work with new generation graphics = like > KMS, Wayland, etc? There are lots of different components here that you=E2=80=99re = conflating: - KMS is the thing that allows the kernel to be responsible for setting = the graphics mode, restoring it on context switches and so on. This has = worked on FreeBSD for a while. - GEM / TTM are memory managers, they allow the kernel to manage memory = (video memory and main memory allocated to the GPU) for GPU-using = drivers. These work on FreeBSD, but the supported version lags Linux = slightly. This is the focus of current work. - The i915 driver. This is the graphics driver for Intel GPUs. It uses = KMS and the memory manager functionality. Importing a newer version will = be possible once the underlying parts are done. - Wayland is a userland application that sits on top of DRI drivers, = just as X.org does. Most of the things Wayland needs that don=E2=80=99t = work on FreeBSD are not graphics related. The problem is that the developers *also* conflate them. Upstream i915 = developers will add KPIs to GEM / TTM / KMS to make their lives easier = and these features need bringing across to FreeBSD. David From owner-freebsd-current@freebsd.org Thu Sep 17 14:23:17 2015 Return-Path: Delivered-To: freebsd-current@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 45E4F9CE765 for ; Thu, 17 Sep 2015 14:23:17 +0000 (UTC) (envelope-from guru@unixarea.de) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 2210D1A4E for ; Thu, 17 Sep 2015 14:23:17 +0000 (UTC) (envelope-from guru@unixarea.de) Received: by mailman.ysv.freebsd.org (Postfix) id 21ADF9CE764; Thu, 17 Sep 2015 14:23:17 +0000 (UTC) Delivered-To: current@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 214609CE763 for ; Thu, 17 Sep 2015 14:23:17 +0000 (UTC) (envelope-from guru@unixarea.de) Received: from ms-10.1blu.de (ms-10.1blu.de [178.254.4.101]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id D2B531A4D; Thu, 17 Sep 2015 14:23:16 +0000 (UTC) (envelope-from guru@unixarea.de) Received: from [82.113.121.34] (helo=localhost.unixarea.de) by ms-10.1blu.de with esmtpsa (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.76) (envelope-from ) id 1ZcZXn-0000xB-CW; Thu, 17 Sep 2015 15:48:11 +0200 Received: from localhost.my.domain (c720-r276659 [127.0.0.1]) by localhost.unixarea.de (8.14.9/8.14.9) with ESMTP id t8HDm9Ce003054 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Thu, 17 Sep 2015 15:48:09 +0200 (CEST) (envelope-from guru@unixarea.de) Received: (from guru@localhost) by localhost.my.domain (8.14.9/8.14.9/Submit) id t8HDm9iq003053; Thu, 17 Sep 2015 15:48:09 +0200 (CEST) (envelope-from guru@unixarea.de) X-Authentication-Warning: localhost.my.domain: guru set sender to guru@unixarea.de using -f Date: Thu, 17 Sep 2015 15:48:09 +0200 From: Matthias Apitz To: "Lundberg, Johannes" Cc: Adam McDougall , David Chisnall , "current@freebsd.org" Subject: Re: Intel Haswell support - Any updates? Message-ID: <20150917134809.GA3025@c720-r276659> Reply-To: Matthias Apitz References: <55FA7324.5010603@icloud.com> <09A515F2-44BA-4DF0-9792-D4C56EEB9D7C@FreeBSD.org> <114F22EF-61E3-4D75-84FB-9D6E3FBCB8F3@FreeBSD.org> <20150917131333.GN1247@egr.msu.edu> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: X-Operating-System: FreeBSD 11.0-CURRENT r269739 (i386) User-Agent: Mutt/1.5.23 (2014-03-12) X-Con-Id: 51246 X-Con-U: 0-guru X-Originating-IP: 82.113.121.34 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 17 Sep 2015 14:23:17 -0000 El dĂ­a Thursday, September 17, 2015 a las 10:41:43PM +0900, Lundberg, Johannes escribiĂł: > Same here. I would personally definitely buy new hardware from Intel if > FreeBSD worked on it (not vesa...) > ... What dow you have against vesa? I run CURRENT on some Acer C720 Chromebooks with Haswell chipset in Vesa mode. And you will not note it. I have never ever had such a fast desktop (KDE4) before. I can live fine with Vesa until Haswell suport is there. matthias -- Matthias Apitz, ✉ guru@unixarea.de, 🌠http://www.unixarea.de/ ⎠+49-176-38902045 No! Nein! ¡No! Όχι! -- ΕυχαĎÎąĎτούμε! From owner-freebsd-current@freebsd.org Thu Sep 17 15:02:10 2015 Return-Path: Delivered-To: freebsd-current@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 351C89CFAEC for ; Thu, 17 Sep 2015 15:02:10 +0000 (UTC) (envelope-from kris@pcbsd.org) Received: from barracuda.ixsystems.com (mail.ixsystems.com [69.198.165.135]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "*.ixsystems.com", Issuer "Go Daddy Secure Certificate Authority - G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 16E5E10CD for ; Thu, 17 Sep 2015 15:02:09 +0000 (UTC) (envelope-from kris@pcbsd.org) X-ASG-Debug-ID: 1442502127-08ca04166b02d30002-XDYc8F Received: from [192.168.0.51] (75-130-56-30.static.kgpt.tn.charter.com [75.130.56.30]) by barracuda.ixsystems.com with ESMTP id aLtFyT58BJaNSd4R (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO) for ; Thu, 17 Sep 2015 08:02:08 -0700 (PDT) X-Barracuda-Envelope-From: kris@pcbsd.org X-Barracuda-AUTH-User: kris@pcbsd.org X-Barracuda-Apparent-Source-IP: 75.130.56.30 X-ASG-Whitelist: Client Subject: Re: Intel Haswell support - Any updates? To: freebsd-current@freebsd.org X-ASG-Orig-Subj: Re: Intel Haswell support - Any updates? References: <55FA7324.5010603@icloud.com> <09A515F2-44BA-4DF0-9792-D4C56EEB9D7C@FreeBSD.org> <114F22EF-61E3-4D75-84FB-9D6E3FBCB8F3@FreeBSD.org> <20150917131333.GN1247@egr.msu.edu> <20150917134809.GA3025@c720-r276659> From: Kris Moore X-Enigmail-Draft-Status: N1110 Message-ID: <55FAD5EF.5030001@pcbsd.org> Date: Thu, 17 Sep 2015 11:02:07 -0400 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:38.0) Gecko/20100101 Thunderbird/38.2.0 MIME-Version: 1.0 In-Reply-To: <20150917134809.GA3025@c720-r276659> Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit X-Barracuda-Connect: 75-130-56-30.static.kgpt.tn.charter.com[75.130.56.30] X-Barracuda-Start-Time: 1442502128 X-Barracuda-Encrypted: ECDHE-RSA-AES128-GCM-SHA256 X-Barracuda-URL: https://10.2.0.41:443/cgi-mod/mark.cgi X-Virus-Scanned: by bsmtpd at ixsystems.com X-Barracuda-BRTS-Status: 1 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 17 Sep 2015 15:02:10 -0000 On 09/17/2015 09:48, Matthias Apitz wrote: > El dĂ­a Thursday, September 17, 2015 a las 10:41:43PM +0900, Lundberg, Johannes escribiĂł: > >> Same here. I would personally definitely buy new hardware from Intel if >> FreeBSD worked on it (not vesa...) >> ... > What dow you have against vesa? I run CURRENT on some Acer C720 > Chromebooks with Haswell chipset in Vesa mode. And you will not note it. > I have never ever had such a fast desktop (KDE4) before. I can live fine > with Vesa until Haswell suport is there. > > matthias BTW, have you tried the xf86-video-scfb driver? It works much better than vesa here. The only catch is you have to be booted UEFI with CSM disabled. Using it on my X1 Carbon, gets 3k resolution properly and everything. Thanks to Glen Barber for bringing that to my attention. -- Kris Moore PC-BSD Software / iXsystems Enterprise Storage & Servers Driven By Open Source From owner-freebsd-current@freebsd.org Thu Sep 17 15:12:25 2015 Return-Path: Delivered-To: freebsd-current@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 D744C9CFFE7 for ; Thu, 17 Sep 2015 15:12:25 +0000 (UTC) (envelope-from ohartman@zedat.fu-berlin.de) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id B336A1924 for ; Thu, 17 Sep 2015 15:12:25 +0000 (UTC) (envelope-from ohartman@zedat.fu-berlin.de) Received: by mailman.ysv.freebsd.org (Postfix) id B2B8B9CFFE6; Thu, 17 Sep 2015 15:12:25 +0000 (UTC) Delivered-To: current@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 986119CFFE5 for ; Thu, 17 Sep 2015 15:12:25 +0000 (UTC) (envelope-from ohartman@zedat.fu-berlin.de) Received: from outpost1.zedat.fu-berlin.de (outpost1.zedat.fu-berlin.de [130.133.4.66]) (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 4DB4D1922; Thu, 17 Sep 2015 15:12:25 +0000 (UTC) (envelope-from ohartman@zedat.fu-berlin.de) Received: from inpost2.zedat.fu-berlin.de ([130.133.4.69]) by outpost.zedat.fu-berlin.de (Exim 4.85) with esmtp (envelope-from ) id <1ZcarE-003Hxc-Li>; Thu, 17 Sep 2015 17:12:20 +0200 Received: from x5ce12e0c.dyn.telefonica.de ([92.225.46.12] helo=thor.walstatt.dynvpn.de) by inpost2.zedat.fu-berlin.de (Exim 4.85) with esmtpsa (envelope-from ) id <1ZcarE-000qZS-AW>; Thu, 17 Sep 2015 17:12:20 +0200 Date: Thu, 17 Sep 2015 17:12:15 +0200 From: "O. Hartmann" To: Matthias Apitz Cc: "Lundberg, Johannes" , Adam McDougall , David Chisnall , "current@freebsd.org" Subject: Re: Intel Haswell support - Any updates? Message-ID: <20150917171215.7e8541bf.ohartman@zedat.fu-berlin.de> In-Reply-To: <20150917134809.GA3025@c720-r276659> References: <55FA7324.5010603@icloud.com> <09A515F2-44BA-4DF0-9792-D4C56EEB9D7C@FreeBSD.org> <114F22EF-61E3-4D75-84FB-9D6E3FBCB8F3@FreeBSD.org> <20150917131333.GN1247@egr.msu.edu> <20150917134809.GA3025@c720-r276659> Organization: FU Berlin X-Mailer: Claws Mail 3.12.0 (GTK+ 2.24.28; amd64-portbld-freebsd11.0) MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; boundary="Sig_/e_ES5xRlgu32YBufb6H++Es"; protocol="application/pgp-signature" X-Originating-IP: 92.225.46.12 X-ZEDAT-Hint: A X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 17 Sep 2015 15:12:26 -0000 --Sig_/e_ES5xRlgu32YBufb6H++Es Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Am Thu, 17 Sep 2015 15:48:09 +0200 Matthias Apitz schrieb: > El d=C3=ADa Thursday, September 17, 2015 a las 10:41:43PM +0900, Lundberg= , Johannes escribi=C3=B3: >=20 > > Same here. I would personally definitely buy new hardware from Intel if > > FreeBSD worked on it (not vesa...) > > ... >=20 > What dow you have against vesa? I run CURRENT on some Acer C720 > Chromebooks with Haswell chipset in Vesa mode. And you will not note it. > I have never ever had such a fast desktop (KDE4) before. I can live fine > with Vesa until Haswell suport is there. >=20 > matthias At what resolution? I have some Lenovo Thinkpad E540, L540. Display resolut= ion: 1980x1080 dots. CPU: Intel i5-4200M, Haswell with HD4600 iGPU. The laptops = do not work with VESA driver - despite some claims of others, I never managed it to get= the driver working on exactly those system types! The alternative framebuffer device is simply horror! I was used to use VESA driver a while ago when FreeBSD fell back in AMD's f= ocus of support with some AMD HD47XX and HD48XX frambuffers. Compared to the cheape= st nVidia GPU board we plugged in then and the nVidia BLOB, VESA was incredibly slow, clu= msy and not very stable. That hasn't changed for now. GPUs got faster, so VESA might no= t suffer from non 2D/3D acceleration, but I never managed it to bring VESA to live for re= solutions like 2560x1440 or 2560x1600 and even higher. That is - for a desktop/workst= ation system - in my opinion "a must". For a notebook/laptop its 1980x1080. Everything e= lse is a toy and for that one can also use crap Windooze OS. Having now Ubuntu and Intel driver for the laptops, there is no need for sl= ow workarounds like VESA. =20 --Sig_/e_ES5xRlgu32YBufb6H++Es Content-Type: application/pgp-signature Content-Description: OpenPGP digital signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQEcBAEBCAAGBQJV+thPAAoJEOgBcD7A/5N8RsYH/jphjGigjkx79FmZVAnJZcmU 5hTtI6e1LfREsaAI5QBR7FM0XfYeOMyGfIdHuoj7krRwQ6+gYrHVDfAKu80h7Jvy MSmvFQsS9PpvMcGGPI4z8z2vZjRWJfyw8W3OkP7NwczP9K770ELK+uam53nWh7l7 XT20OhpaB21XJd6DiSbcpUmMcFJ1srbNDLohxMJHksrbr/qVrYL5H2IeuQT/L26I kJlPPCKILmGOGDNIAwVmWdq1KMtjLsc7j5VUXcRPcXOk6Md4M+3NIZd37aS+LvM7 QT8TiAU5xlVlSXI06/+V7Y4YifoafOKqA20q8W2xfDaXFGMM+iw8ni6dww4PY34= =JIe+ -----END PGP SIGNATURE----- --Sig_/e_ES5xRlgu32YBufb6H++Es-- From owner-freebsd-current@freebsd.org Thu Sep 17 15:20:02 2015 Return-Path: Delivered-To: freebsd-current@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 AB8019CE35B for ; Thu, 17 Sep 2015 15:20:02 +0000 (UTC) (envelope-from ohartman@zedat.fu-berlin.de) Received: from outpost1.zedat.fu-berlin.de (outpost1.zedat.fu-berlin.de [130.133.4.66]) (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 62F5C1C1D for ; Thu, 17 Sep 2015 15:20:01 +0000 (UTC) (envelope-from ohartman@zedat.fu-berlin.de) Received: from inpost2.zedat.fu-berlin.de ([130.133.4.69]) by outpost.zedat.fu-berlin.de (Exim 4.85) with esmtp (envelope-from ) id <1Zcayd-003Ko8-MF>; Thu, 17 Sep 2015 17:19:59 +0200 Received: from x5ce12e0c.dyn.telefonica.de ([92.225.46.12] helo=thor.walstatt.dynvpn.de) by inpost2.zedat.fu-berlin.de (Exim 4.85) with esmtpsa (envelope-from ) id <1Zcayd-000rLD-DZ>; Thu, 17 Sep 2015 17:19:59 +0200 Date: Thu, 17 Sep 2015 17:19:58 +0200 From: "O. Hartmann" To: Kris Moore Cc: freebsd-current@freebsd.org Subject: Re: Intel Haswell support - Any updates? Message-ID: <20150917171958.046e4b6b.ohartman@zedat.fu-berlin.de> In-Reply-To: <55FAD5EF.5030001@pcbsd.org> References: <55FA7324.5010603@icloud.com> <09A515F2-44BA-4DF0-9792-D4C56EEB9D7C@FreeBSD.org> <114F22EF-61E3-4D75-84FB-9D6E3FBCB8F3@FreeBSD.org> <20150917131333.GN1247@egr.msu.edu> <20150917134809.GA3025@c720-r276659> <55FAD5EF.5030001@pcbsd.org> Organization: FU Berlin X-Mailer: Claws Mail 3.12.0 (GTK+ 2.24.28; amd64-portbld-freebsd11.0) MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; boundary="Sig_/+UFUHnjgoah9yCcg2gTjw_X"; protocol="application/pgp-signature" X-Originating-IP: 92.225.46.12 X-ZEDAT-Hint: A X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 17 Sep 2015 15:20:02 -0000 --Sig_/+UFUHnjgoah9yCcg2gTjw_X Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Am Thu, 17 Sep 2015 11:02:07 -0400 Kris Moore schrieb: > On 09/17/2015 09:48, Matthias Apitz wrote: > > El d=C3=ADa Thursday, September 17, 2015 a las 10:41:43PM +0900, Lundbe= rg, Johannes > > escribi=C3=B3: > > > >> Same here. I would personally definitely buy new hardware from Intel if > >> FreeBSD worked on it (not vesa...) > >> ... > > What dow you have against vesa? I run CURRENT on some Acer C720 > > Chromebooks with Haswell chipset in Vesa mode. And you will not note it. > > I have never ever had such a fast desktop (KDE4) before. I can live fine > > with Vesa until Haswell suport is there. > > > > matthias >=20 > BTW, have you tried the xf86-video-scfb driver? It works much better > than vesa here. The only catch is you have to be booted UEFI with CSM > disabled. Using it on my X1 Carbon, gets 3k resolution properly and > everything. Thanks to Glen Barber for bringing that to my attention. >=20 Running that specific driver on several Lenovo HD4600 driven models gives m= e headaches and more. This software-framebuffer works - yes, on whatever resolution you= might wish, but it consumes CPU time. That said, I recall that the display was jumpy, s= low and unresponsive when used under heavy load - not even 3k resolution, but with = a moderate lowend of 1980x1080. --Sig_/+UFUHnjgoah9yCcg2gTjw_X Content-Type: application/pgp-signature Content-Description: OpenPGP digital signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQEcBAEBCAAGBQJV+toeAAoJEOgBcD7A/5N8HwQH/3e9i5RxoMaD8b6HrIpE+Gfc 4nUPNR57vUhr2gAbhEdViYrIgklZz2PAgoOrcZQFsWj4bBnPLZepfU+7jzloM4Km bOBZFBpzZnY+y/Dji68+0qNHWCK66hS03O0rfPzgggGkCIAr9l/dv2+r6REXvsK3 cC2uHrOUm512vuzrF6CZ0oDXxayTIRWsKhtg8lElBGqnIRTJWA6w5uu5Kux2eW0P H0MQr+vVhybValnqiBCtLw+jqJeBa0LyCzm/PqZo1nKY5WDBk7yXqstcl3Sx/8ac a+EHSjcNxPc6qDw3DUIbXr3ba5/BszuOVdBY8gaQQb/8zKi3IMWtl/bfmS8C+dw= =qJSg -----END PGP SIGNATURE----- --Sig_/+UFUHnjgoah9yCcg2gTjw_X-- From owner-freebsd-current@freebsd.org Thu Sep 17 15:24:44 2015 Return-Path: Delivered-To: freebsd-current@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 6E9959CE74D for ; Thu, 17 Sep 2015 15:24:44 +0000 (UTC) (envelope-from kris@pcbsd.org) Received: from barracuda.ixsystems.com (mail.ixsystems.com [69.198.165.135]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "*.ixsystems.com", Issuer "Go Daddy Secure Certificate Authority - G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4EAC21286 for ; Thu, 17 Sep 2015 15:24:43 +0000 (UTC) (envelope-from kris@pcbsd.org) X-ASG-Debug-ID: 1442503480-08ca04166b02d90002-XDYc8F Received: from [192.168.0.51] (75-130-56-30.static.kgpt.tn.charter.com [75.130.56.30]) by barracuda.ixsystems.com with ESMTP id nDvv5g2mkXY5PG7t (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO) for ; Thu, 17 Sep 2015 08:24:42 -0700 (PDT) X-Barracuda-Envelope-From: kris@pcbsd.org X-Barracuda-AUTH-User: kris@pcbsd.org X-Barracuda-Apparent-Source-IP: 75.130.56.30 X-ASG-Whitelist: Client Subject: Re: Intel Haswell support - Any updates? To: freebsd-current@freebsd.org X-ASG-Orig-Subj: Re: Intel Haswell support - Any updates? References: <55FA7324.5010603@icloud.com> <09A515F2-44BA-4DF0-9792-D4C56EEB9D7C@FreeBSD.org> <114F22EF-61E3-4D75-84FB-9D6E3FBCB8F3@FreeBSD.org> <20150917131333.GN1247@egr.msu.edu> <20150917134809.GA3025@c720-r276659> <55FAD5EF.5030001@pcbsd.org> <20150917171958.046e4b6b.ohartman@zedat.fu-berlin.de> From: Kris Moore X-Enigmail-Draft-Status: N1110 Message-ID: <55FADB38.7000406@pcbsd.org> Date: Thu, 17 Sep 2015 11:24:40 -0400 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:38.0) Gecko/20100101 Thunderbird/38.2.0 MIME-Version: 1.0 In-Reply-To: <20150917171958.046e4b6b.ohartman@zedat.fu-berlin.de> Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit X-Barracuda-Connect: 75-130-56-30.static.kgpt.tn.charter.com[75.130.56.30] X-Barracuda-Start-Time: 1442503482 X-Barracuda-Encrypted: ECDHE-RSA-AES128-GCM-SHA256 X-Barracuda-URL: https://10.2.0.41:443/cgi-mod/mark.cgi X-Virus-Scanned: by bsmtpd at ixsystems.com X-Barracuda-BRTS-Status: 1 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 17 Sep 2015 15:24:44 -0000 On 09/17/2015 11:19, O. Hartmann wrote: > Am Thu, 17 Sep 2015 11:02:07 -0400 > Kris Moore schrieb: > >> On 09/17/2015 09:48, Matthias Apitz wrote: >>> El dĂ­a Thursday, September 17, 2015 a las 10:41:43PM +0900, Lundberg, Johannes >>> escribiĂł: >>> >>>> Same here. I would personally definitely buy new hardware from Intel if >>>> FreeBSD worked on it (not vesa...) >>>> ... >>> What dow you have against vesa? I run CURRENT on some Acer C720 >>> Chromebooks with Haswell chipset in Vesa mode. And you will not note it. >>> I have never ever had such a fast desktop (KDE4) before. I can live fine >>> with Vesa until Haswell suport is there. >>> >>> matthias >> BTW, have you tried the xf86-video-scfb driver? It works much better >> than vesa here. The only catch is you have to be booted UEFI with CSM >> disabled. Using it on my X1 Carbon, gets 3k resolution properly and >> everything. Thanks to Glen Barber for bringing that to my attention. >> > Running that specific driver on several Lenovo HD4600 driven models gives me headaches > and more. This software-framebuffer works - yes, on whatever resolution you might wish, > but it consumes CPU time. That said, I recall that the display was jumpy, slow and > unresponsive when used under heavy load - not even 3k resolution, but with a moderate > lowend of 1980x1080. Interesting, that's been the opposite of my experience here. Vesa was much slower / using more CPU time and didn't give me the native resolution. Switching to scfb made the laptop "usable" for me, at least until we get a proper Intel driver that does Broadwell. -- Kris Moore PC-BSD Software / iXsystems Enterprise Storage & Servers Driven By Open Source From owner-freebsd-current@freebsd.org Thu Sep 17 15:30:01 2015 Return-Path: Delivered-To: freebsd-current@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 A491D9CE9ED for ; Thu, 17 Sep 2015 15:30:01 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 825B71648 for ; Thu, 17 Sep 2015 15:30:01 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: by mailman.ysv.freebsd.org (Postfix) id 7FB1A9CE9EC; Thu, 17 Sep 2015 15:30:01 +0000 (UTC) Delivered-To: current@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 7F4BF9CE9EB for ; Thu, 17 Sep 2015 15:30:01 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-ig0-x233.google.com (mail-ig0-x233.google.com [IPv6:2607:f8b0:4001:c05::233]) (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 51DE51647 for ; Thu, 17 Sep 2015 15:30:01 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: by igbkq10 with SMTP id kq10so15153418igb.0 for ; Thu, 17 Sep 2015 08:30:00 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=vtou93CV/gwiO7c8Sj48NWYVkuiH274ZLEilXaHrPis=; b=RCfuzU61AMCb/7gfAFFnobPYhrGIOO7/DU4JCJYs8Vc1Fx6HgZrEEiuJ+OZxeHqqm2 bbKoYfruEY7F98tCbdlPmwVqGbBR0n9HkDt4u42vk5nCqK5tV0uuhLHewl087mbj9gsA GJwK0Gj83YvvjFNFH+HYuZWlQvurPNLQmblZCHmD27Yq0Kkv8JtyRfuAhbL2LXH1LTTV xRInUvN2P8xcpvXiY/CAv2ZXwOUt9HkCFjLX5oPFLRXWZrSx2gdB7CYwrDXngNLMYNoy /TL+upncoCfQFj+z5T1W0Z9OxqV78NV6hdjUtP6nB/R1+D3TaHTQMxUXkJV4XuT4xXBy NtJQ== MIME-Version: 1.0 X-Received: by 10.50.61.243 with SMTP id t19mr7181833igr.22.1442503800790; Thu, 17 Sep 2015 08:30:00 -0700 (PDT) Received: by 10.36.28.208 with HTTP; Thu, 17 Sep 2015 08:30:00 -0700 (PDT) In-Reply-To: <20150917121526.71906673@freyja.zeit4.iv.bundesimmobilien.de> References: <55FA7324.5010603@icloud.com> <20150917121526.71906673@freyja.zeit4.iv.bundesimmobilien.de> Date: Thu, 17 Sep 2015 08:30:00 -0700 Message-ID: Subject: Re: Intel Haswell support - Any updates? From: Adrian Chadd To: "O. Hartmann" Cc: "Lundberg, Johannes" , Andreas Nilsson , Anders Bolt-Evensen , "current@freebsd.org" Content-Type: text/plain; charset=UTF-8 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 17 Sep 2015 15:30:01 -0000 Nope, very wrong. The real answer is this: * FreeBSD cares about backwards compatibility support and supporting older releases. So the xorg team in freebsd has to do a few things: * update the drm2 code in freebsd which required updating the linux layer - dfbsd, openbsd skipped ahead by just doing this step first, rather than trying to BSD-ify drm2; * support freebsd stable branches (-10, and until recently -9 and -8 too..); * have one set of packages that works on all of them. The linux ecosystem here moves very quickly, and BSD volunteers are stuck trying to provide free support for older releases. Me, I'm a "screw it, just support -HEAD, let the -stable community sort it out" but I'm luckily not in charge of that. :) It's coming along. They're just trying to do it all without breaking existing stable users - this deserves massive thanks on their part. -adrian From owner-freebsd-current@freebsd.org Thu Sep 17 15:30:04 2015 Return-Path: Delivered-To: freebsd-current@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 31DB39CEA09 for ; Thu, 17 Sep 2015 15:30:04 +0000 (UTC) (envelope-from shawn.webb@hardenedbsd.org) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 02AC1175A for ; Thu, 17 Sep 2015 15:30:04 +0000 (UTC) (envelope-from shawn.webb@hardenedbsd.org) Received: by mailman.ysv.freebsd.org (Postfix) id 021B69CEA08; Thu, 17 Sep 2015 15:30:04 +0000 (UTC) Delivered-To: current@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 DD0F49CEA07 for ; Thu, 17 Sep 2015 15:30:03 +0000 (UTC) (envelope-from shawn.webb@hardenedbsd.org) Received: from mail-qg0-f42.google.com (mail-qg0-f42.google.com [209.85.192.42]) (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 947461720 for ; Thu, 17 Sep 2015 15:30:03 +0000 (UTC) (envelope-from shawn.webb@hardenedbsd.org) Received: by qgt47 with SMTP id 47so15585490qgt.2 for ; Thu, 17 Sep 2015 08:30:02 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-type:content-disposition:in-reply-to :user-agent; bh=9U0gLwP8AxlYgThmV+3XhYXI1TBuSgW4O9glyAQ7aow=; b=TMXpfunbgpM+LCrEBL7nz7GRk6fkiLf7PahkYnL6oB3E5mZbBE0NVJmEZmNlx9CaJa ksrX6kErIfj4Z7JdS3CSiwIxEjAkR7tMEBY6QTbJLfoU9X1K7Co4BNJ7zMkPme8zvjD2 SaAQGJZpRbU+E2LJ0FRJfXHkQRoOlFc4UkPJhcc2uHaV4f4xOxyd1zS17HZGxY7rlvIp 1JALKgN0zCZYFTEFzU5VQJeFeq6H/R30hBgzX5+VxACCxDS23CHzlct5PE/cGzgLgxHQ zaICNoMqUZ612MzKJARPhXSTFfxJijGnFO5RwLFMCbjS7A+cXtSNwZLdvWlmCUTwAtyX /Jpg== X-Gm-Message-State: ALoCoQmkNI7fbYfbl2916yfeaWG8coLFQI0ZpLxkHuOfHrtsQXoUH0nq73wp3rR3ImfZ7+yRjJbG X-Received: by 10.140.239.133 with SMTP id k127mr53068414qhc.60.1442503492848; Thu, 17 Sep 2015 08:24:52 -0700 (PDT) Received: from mutt-hardenedbsd.hardenedbsd.dev (c-73-135-80-144.hsd1.md.comcast.net. [73.135.80.144]) by smtp.gmail.com with ESMTPSA id 18sm1465090qgg.39.2015.09.17.08.24.52 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 17 Sep 2015 08:24:52 -0700 (PDT) Date: Thu, 17 Sep 2015 11:24:50 -0400 From: Shawn Webb To: "O. Hartmann" Cc: Matthias Apitz , "Lundberg, Johannes" , Adam McDougall , David Chisnall , "current@freebsd.org" Subject: Re: Intel Haswell support - Any updates? Message-ID: <20150917152444.GA88816@mutt-hardenedbsd.hardenedbsd.dev> References: <09A515F2-44BA-4DF0-9792-D4C56EEB9D7C@FreeBSD.org> <114F22EF-61E3-4D75-84FB-9D6E3FBCB8F3@FreeBSD.org> <20150917131333.GN1247@egr.msu.edu> <20150917134809.GA3025@c720-r276659> <20150917171215.7e8541bf.ohartman@zedat.fu-berlin.de> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="C7zPtVaVf+AK4Oqc" Content-Disposition: inline In-Reply-To: <20150917171215.7e8541bf.ohartman@zedat.fu-berlin.de> X-Operating-System: FreeBSD mutt-hardenedbsd 11.0-CURRENT-HBSD FreeBSD 11.0-CURRENT-HBSD X-PGP-Key: http://pgp.mit.edu/pks/lookup?op=vindex&search=0x6A84658F52456EEE User-Agent: Mutt/1.5.23 (2014-03-12) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 17 Sep 2015 15:30:04 -0000 --C7zPtVaVf+AK4Oqc Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Sep 17, 2015 at 05:12:15PM +0200, O. Hartmann wrote: > Am Thu, 17 Sep 2015 15:48:09 +0200 > Matthias Apitz schrieb: >=20 > > El d??a Thursday, September 17, 2015 a las 10:41:43PM +0900, Lundberg, = Johannes escribi??: > >=20 > > > Same here. I would personally definitely buy new hardware from Intel = if > > > FreeBSD worked on it (not vesa...) > > > ... > >=20 > > What dow you have against vesa? I run CURRENT on some Acer C720 > > Chromebooks with Haswell chipset in Vesa mode. And you will not note it. > > I have never ever had such a fast desktop (KDE4) before. I can live fine > > with Vesa until Haswell suport is there. > >=20 > > matthias >=20 > At what resolution? I have some Lenovo Thinkpad E540, L540. Display resol= ution: > 1980x1080 dots. CPU: Intel i5-4200M, Haswell with HD4600 iGPU. The laptop= s do not work > with VESA driver - despite some claims of others, I never managed it to g= et the driver > working on exactly those system types! VESA's working fine for me, albeit slowly with YouTube videos, on my Lenovo Y50-70 at 1920x1080. I was running KDE4 before, but have since switched to i3wm for better hax efficiency. >=20 > The alternative framebuffer device is simply horror! >=20 > I was used to use VESA driver a while ago when FreeBSD fell back in AMD's= focus of > support with some AMD HD47XX and HD48XX frambuffers. Compared to the chea= pest nVidia GPU > board we plugged in then and the nVidia BLOB, VESA was incredibly slow, c= lumsy and not > very stable. That hasn't changed for now. GPUs got faster, so VESA might = not suffer from > non 2D/3D acceleration, but I never managed it to bring VESA to live for = resolutions > like 2560x1440 or 2560x1600 and even higher. That is - for a desktop/work= station system > - in my opinion "a must". For a notebook/laptop its 1980x1080. Everything= else is a toy > and for that one can also use crap Windooze OS. >=20 > Having now Ubuntu and Intel driver for the laptops, there is no need for = slow > workarounds like VESA. =20 Sounds like you have a solution for now. I'm excited for Haswell support to land. I applaud dumbbell for his efforts. I'm eagerly awaiting the CFT that will come out relatively soon. If you're impatient and want it now, I suggest taking a look at that code on GitHub that was posted in an earlier email on this thread. Fork it, hax it, then submit a pull request. Have an active part. Make your voice be heard through code contributions. Thanks, --=20 Shawn Webb HardenedBSD GPG Key ID: 0x6A84658F52456EEE GPG Key Fingerprint: 2ABA B6BD EF6A F486 BE89 3D9E 6A84 658F 5245 6EEE --C7zPtVaVf+AK4Oqc Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQIcBAEBCAAGBQJV+ts5AAoJEGqEZY9SRW7ua8oP/3qts1MUKFkQM3jtKvcPYeM+ y529RzU//rfuBFvqwdmJbC/fYAZqFWkCUVgEPQaa5jnzhARA/y6pqz8kcR5y9pOj 3M2x9huv2nSaOBXTECiC3d7OzswLRSazVYFmupD3mncxFr472jCPQArVV64ng7XL SZSbyv3hYPtX45CFgd9Ik1kShcnIYLSYWUJpfWYVZNF380J7hTlI8+B+qWU3gKyC wbzY4p37crz3eS8jNV9PlL+Mr8yPeBj3vs3XXaCDHwkcJHAO9SAa4h4msKjwF1Pt cJCTst0PPc+DRnSIaVFsyCeKaVrk4st2vxmzeXrJc0yQSEJnPOiw2rj5DCYyD4cc 1qgYtOpgHOCmvRyYXz8VPzPKgbKaUbH1lW4B/J/SyraK4+XHSOvWNov3Qaofa8KJ rmpmlxea+x07gRomlCT1n/w8/IT8+XsbcP3jhMFJEGtR0D1FvAP5cbanathr8zew te99XvsW+6PrkrLxfjAUBB38fbSMcAxD1WglpxuSDjEwpOnVQCHPTWjO8KcsvqCy SiL3p5XaVUZ4GrQZqTWcYmV/ManD+zSupGZi/a5vvBsjHt6Cuslikq00r3sb1EGY N91aXZ3gji3AUdNJ+UUSS4XJ4zgUdOysiDz/VN6DiCJGJ/5FFB6Do6hY9NQbJ441 /470ymdKO/aopAQXkVfB =aNe4 -----END PGP SIGNATURE----- --C7zPtVaVf+AK4Oqc-- From owner-freebsd-current@freebsd.org Thu Sep 17 15:32:36 2015 Return-Path: Delivered-To: freebsd-current@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 DD67C9CECA5 for ; Thu, 17 Sep 2015 15:32:35 +0000 (UTC) (envelope-from ohartman@zedat.fu-berlin.de) Received: from outpost1.zedat.fu-berlin.de (outpost1.zedat.fu-berlin.de [130.133.4.66]) (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 9047B1CBA for ; Thu, 17 Sep 2015 15:32:35 +0000 (UTC) (envelope-from ohartman@zedat.fu-berlin.de) Received: from inpost2.zedat.fu-berlin.de ([130.133.4.69]) by outpost.zedat.fu-berlin.de (Exim 4.85) for freebsd-current@freebsd.org with esmtp (envelope-from ) id <1ZcbAn-003Pai-Fz>; Thu, 17 Sep 2015 17:32:33 +0200 Received: from x5ce12e0c.dyn.telefonica.de ([92.225.46.12] helo=thor.walstatt.dynvpn.de) by inpost2.zedat.fu-berlin.de (Exim 4.85) for freebsd-current@freebsd.org with esmtpsa (envelope-from ) id <1ZcbAn-000sKq-7s>; Thu, 17 Sep 2015 17:32:33 +0200 Date: Thu, 17 Sep 2015 17:32:32 +0200 From: "O. Hartmann" To: freebsd-current@freebsd.org Subject: Re: Intel Haswell support - Any updates? Message-ID: <20150917173232.1c9f42d9.ohartman@zedat.fu-berlin.de> In-Reply-To: <55FADB38.7000406@pcbsd.org> References: <55FA7324.5010603@icloud.com> <09A515F2-44BA-4DF0-9792-D4C56EEB9D7C@FreeBSD.org> <114F22EF-61E3-4D75-84FB-9D6E3FBCB8F3@FreeBSD.org> <20150917131333.GN1247@egr.msu.edu> <20150917134809.GA3025@c720-r276659> <55FAD5EF.5030001@pcbsd.org> <20150917171958.046e4b6b.ohartman@zedat.fu-berlin.de> <55FADB38.7000406@pcbsd.org> Organization: FU Berlin X-Mailer: Claws Mail 3.12.0 (GTK+ 2.24.28; amd64-portbld-freebsd11.0) MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; boundary="Sig_/MTrW6xd9kyiOOulhQIT9rrj"; protocol="application/pgp-signature" X-Originating-IP: 92.225.46.12 X-ZEDAT-Hint: A X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 17 Sep 2015 15:32:36 -0000 --Sig_/MTrW6xd9kyiOOulhQIT9rrj Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Am Thu, 17 Sep 2015 11:24:40 -0400 Kris Moore schrieb: > On 09/17/2015 11:19, O. Hartmann wrote: > > Am Thu, 17 Sep 2015 11:02:07 -0400 > > Kris Moore schrieb: > > > >> On 09/17/2015 09:48, Matthias Apitz wrote: > >>> El d=C3=ADa Thursday, September 17, 2015 a las 10:41:43PM +0900, Lund= berg, Johannes > >>> escribi=C3=B3: > >>> > >>>> Same here. I would personally definitely buy new hardware from Intel= if > >>>> FreeBSD worked on it (not vesa...) > >>>> ... > >>> What dow you have against vesa? I run CURRENT on some Acer C720 > >>> Chromebooks with Haswell chipset in Vesa mode. And you will not note = it. > >>> I have never ever had such a fast desktop (KDE4) before. I can live f= ine > >>> with Vesa until Haswell suport is there. > >>> > >>> matthias > >> BTW, have you tried the xf86-video-scfb driver? It works much better > >> than vesa here. The only catch is you have to be booted UEFI with CSM > >> disabled. Using it on my X1 Carbon, gets 3k resolution properly and > >> everything. Thanks to Glen Barber for bringing that to my attention. > >> > > Running that specific driver on several Lenovo HD4600 driven models giv= es me headaches > > and more. This software-framebuffer works - yes, on whatever resolution= you might > > wish, but it consumes CPU time. That said, I recall that the display wa= s jumpy, slow > > and unresponsive when used under heavy load - not even 3k resolution, b= ut with a > > moderate lowend of 1980x1080. >=20 > Interesting, that's been the opposite of my experience here. Vesa was > much slower / using more CPU time and didn't give me the native > resolution. Switching to scfb made the laptop "usable" for me, at least > until we get a proper Intel driver that does Broadwell. >=20 ... as I said - VESA is unwilling to cooperate at higher resolutions, so I = do not have any comparison parameters fro the specific single hardware. VESA was slow i= n the past - compared to the nVidia BLOB or the X11 AMD HD 48XX drivers. --Sig_/MTrW6xd9kyiOOulhQIT9rrj Content-Type: application/pgp-signature Content-Description: OpenPGP digital signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQEcBAEBCAAGBQJV+t0QAAoJEOgBcD7A/5N8ro4IAJZZxWcUNPEwxTjL8KVR93k5 kqtm5cW8t1w61cXoKi+JOOfgsUS/vUO7fPnJFyjgwYwAdLDJHXQaDy+QIS58E9Dd kP6kU+s0SvC71DuyujU8C+m/pkdSUT0S9Cn7NImXMifaiWJPhX7wHfQ/BZwfL1Ym FjbRM5/MCaSyc/2uZyM3huREeH5Co1VRTYxTfekT4l074g1EwQo4aiSYri5u5sc/ 1+VFSWFLYvvvJPQwjPyUfWvuoql47mN88J+lNSFNggVPO9O1wviSWC04mhLqecwP gwK8N9Vsp5UHaBCeyApFNCP8fDbXYgcbwpkTUOX/PS7qjOfSQP6U5Ij58UhrunY= =v99z -----END PGP SIGNATURE----- --Sig_/MTrW6xd9kyiOOulhQIT9rrj-- From owner-freebsd-current@freebsd.org Thu Sep 17 15:42:02 2015 Return-Path: Delivered-To: freebsd-current@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 76E0A9CD1DC for ; Thu, 17 Sep 2015 15:42:02 +0000 (UTC) (envelope-from rpaulo@me.com) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 52A6B12DA for ; Thu, 17 Sep 2015 15:42:02 +0000 (UTC) (envelope-from rpaulo@me.com) Received: by mailman.ysv.freebsd.org (Postfix) id 5204E9CD1DB; Thu, 17 Sep 2015 15:42:02 +0000 (UTC) Delivered-To: current@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 37DD19CD1DA for ; Thu, 17 Sep 2015 15:42:02 +0000 (UTC) (envelope-from rpaulo@me.com) Received: from mr11p00im-asmtp003.me.com (mr11p00im-asmtp003.me.com [17.110.69.254]) (using TLSv1.2 with cipher DHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 09CF912D9; Thu, 17 Sep 2015 15:42:02 +0000 (UTC) (envelope-from rpaulo@me.com) MIME-version: 1.0 Content-transfer-encoding: 8BIT Content-type: text/plain; charset=UTF-8 Received: from akita.hsd1.ca.comcast.net (c-73-162-13-215.hsd1.ca.comcast.net [73.162.13.215]) by mr11p00im-asmtp003.me.com (Oracle Communications Messaging Server 7.0.5.35.0 64bit (built Mar 31 2015)) with ESMTPSA id <0NUT00KBIVLRBT20@mr11p00im-asmtp003.me.com>; Thu, 17 Sep 2015 15:41:55 +0000 (GMT) X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:,, definitions=2015-09-17_06:,, signatures=0 X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 kscore.is_bulkscore=5.55111512312578e-17 compositescore=0.981217492118854 phishscore=0 kscore.is_spamscore=0 rbsscore=0.981217492118854 recipient_to_sender_totalscore=0 spamscore=0 urlsuspectscore=0.981217492118854 adultscore=0 kscore.compositescore=0 circleOfTrustscore=0 suspectscore=0 recipient_domain_to_sender_totalscore=0 bulkscore=0 recipient_domain_to_sender_domain_totalscore=0 recipient_to_sender_domain_totalscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1412110000 definitions=main-1509170219 Message-id: <1442504510.1862.6.camel@me.com> Subject: Re: Intel Haswell support - Any updates? From: Rui Paulo To: David Chisnall , "Lundberg, Johannes" Cc: Adam McDougall , "current@freebsd.org" Date: Thu, 17 Sep 2015 08:41:50 -0700 In-reply-to: References: <55FA7324.5010603@icloud.com> <09A515F2-44BA-4DF0-9792-D4C56EEB9D7C@FreeBSD.org> <114F22EF-61E3-4D75-84FB-9D6E3FBCB8F3@FreeBSD.org> <20150917131333.GN1247@egr.msu.edu> X-Mailer: Evolution 3.16.5-1 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 17 Sep 2015 15:42:02 -0000 On Thu, 2015-09-17 at 14:47 +0100, David Chisnall wrote: > On 17 Sep 2015, at 14:41, Lundberg, Johannes < > johannes@brilliantservice.co.jp> wrote: > > > > However, the problem now is not the driver right? But the whole > > graphics > > stack which has to be rewritten to work with new generation > > graphics like > > KMS, Wayland, etc? > > There are lots of different components here that you’re conflating: > > - KMS is the thing that allows the kernel to be responsible for > setting the graphics mode, restoring it on context switches and so > on. This has worked on FreeBSD for a while. > > - GEM / TTM are memory managers, they allow the kernel to manage > memory (video memory and main memory allocated to the GPU) for GPU > -using drivers. These work on FreeBSD, but the supported version > lags Linux slightly. This is the focus of current work. > > - The i915 driver. This is the graphics driver for Intel GPUs. It > uses KMS and the memory manager functionality. Importing a newer > version will be possible once the underlying parts are done. > > - Wayland is a userland application that sits on top of DRI drivers, > just as X.org does. Most of the things Wayland needs that don’t work > on FreeBSD are not graphics related. > > The problem is that the developers *also* conflate them. Upstream > i915 developers will add KPIs to GEM / TTM / KMS to make their lives > easier and these features need bringing across to FreeBSD. Let's also not forget the following statistics: - The DRM / GEM / TTM code is around 50k lines of code; - The i915 driver is 120k lines of code; - The radeon driver is 212k lines of code. Even with a good linux compatibility layer, it's still a big project that requires a lot of work. If we don't convince the vendors to work on FreeBSD, I fear this problem will never be solved. P.S.: the total linux drm stack is around 600k LOC. -- Rui Paulo From owner-freebsd-current@freebsd.org Thu Sep 17 15:43:06 2015 Return-Path: Delivered-To: freebsd-current@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 4035C9CD271 for ; Thu, 17 Sep 2015 15:43:06 +0000 (UTC) (envelope-from n.pajkovsky@gmail.com) Received: from mail-wi0-x22f.google.com (mail-wi0-x22f.google.com [IPv6:2a00:1450:400c:c05::22f]) (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 C5D25143B for ; Thu, 17 Sep 2015 15:43:05 +0000 (UTC) (envelope-from n.pajkovsky@gmail.com) Received: by wicge5 with SMTP id ge5so124474108wic.0 for ; Thu, 17 Sep 2015 08:43:04 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=from:to:cc:subject:references:date:in-reply-to:message-id :user-agent:mime-version:content-type:content-transfer-encoding; bh=PHCO4BsgBzHrzwVuL9bSEPpd0f5fdshwkPbAxKnWcwo=; b=sQ0+5ct3ubdv38oFdbCNAvvIyrwHqp/hCIViIsvDm2evxuXMzpvGBTJBquOTaKpgCs BjyoVD4nWtA+964gEMYkcpQQb/ojWhM4de/k8EtUCR1Hprqj+WzYZMAeTR6eII9ZHgWR J1ITclHu5PRYGNaptA/RbsQdeqeGCZEDk3TMc3sQ2hyKp/tr9ovf6EPj6QhAdR0F5xmi xOWvm5p5OvtJHMTViCnoafatFnc+DOrU1Xq+RWWlNGY8HtOmUMi98sxoog+4U4qWwOa9 Z055xSohGEwVrJPEXxavdTjcmhJ3v5Wm4jDgLkzMTmKqOnvcPLoueO4Egr1OWfdzyoAA K53Q== X-Received: by 10.180.11.212 with SMTP id s20mr8918175wib.40.1442504584173; Thu, 17 Sep 2015 08:43:04 -0700 (PDT) Received: from localhost (gw-brno.gooddata.com. [194.213.40.134]) by smtp.gmail.com with ESMTPSA id fs2sm10702409wib.12.2015.09.17.08.43.02 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 17 Sep 2015 08:43:02 -0700 (PDT) From: Nikola Pajkovsky To: Kris Moore Cc: freebsd-current@freebsd.org Subject: Re: Intel Haswell support - Any updates? References: <55FA7324.5010603@icloud.com> <09A515F2-44BA-4DF0-9792-D4C56EEB9D7C@FreeBSD.org> <114F22EF-61E3-4D75-84FB-9D6E3FBCB8F3@FreeBSD.org> <20150917131333.GN1247@egr.msu.edu> <20150917134809.GA3025@c720-r276659> <55FAD5EF.5030001@pcbsd.org> <20150917171958.046e4b6b.ohartman@zedat.fu-berlin.de> <55FADB38.7000406@pcbsd.org> Date: Thu, 17 Sep 2015 17:43:02 +0200 In-Reply-To: <55FADB38.7000406@pcbsd.org> (Kris Moore's message of "Thu, 17 Sep 2015 11:24:40 -0400") Message-ID: <87twqt2gs9.fsf@gooddata.com> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.5 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 17 Sep 2015 15:43:06 -0000 Kris Moore writes: > On 09/17/2015 11:19, O. Hartmann wrote: >> Am Thu, 17 Sep 2015 11:02:07 -0400 >> Kris Moore schrieb: >> >>> On 09/17/2015 09:48, Matthias Apitz wrote: >>>> El d=C3=ADa Thursday, September 17, 2015 a las 10:41:43PM +0900, Lundb= erg, Johannes >>>> escribi=C3=B3: >>>> >>>>> Same here. I would personally definitely buy new hardware from Intel = if >>>>> FreeBSD worked on it (not vesa...) >>>>> ... >>>> What dow you have against vesa? I run CURRENT on some Acer C720 >>>> Chromebooks with Haswell chipset in Vesa mode. And you will not note i= t. >>>> I have never ever had such a fast desktop (KDE4) before. I can live fi= ne >>>> with Vesa until Haswell suport is there. >>>> >>>> matthias >>> BTW, have you tried the xf86-video-scfb driver? It works much better >>> than vesa here. The only catch is you have to be booted UEFI with CSM >>> disabled. Using it on my X1 Carbon, gets 3k resolution properly and >>> everything. Thanks to Glen Barber for bringing that to my attention. >>> >> Running that specific driver on several Lenovo HD4600 driven models give= s me headaches >> and more. This software-framebuffer works - yes, on whatever resolution = you might wish, >> but it consumes CPU time. That said, I recall that the display was jumpy= , slow and >> unresponsive when used under heavy load - not even 3k resolution, but wi= th a moderate >> lowend of 1980x1080. > > Interesting, that's been the opposite of my experience here. Vesa was > much slower / using more CPU time and didn't give me the native > resolution. Switching to scfb made the laptop "usable" for me, at least > until we get a proper Intel driver that does Broadwell. Use memcontrol to set mtrr write-combine for your Vesa. Vesa is lightning fast on T440p on 1920x1200. --=20 Nikola From owner-freebsd-current@freebsd.org Thu Sep 17 16:29:01 2015 Return-Path: Delivered-To: freebsd-current@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 9A5B59CE992 for ; Thu, 17 Sep 2015 16:29:01 +0000 (UTC) (envelope-from rpaulo@me.com) Received: from mr11p00im-asmtp001.me.com (mr11p00im-asmtp001.me.com [17.110.69.252]) (using TLSv1.2 with cipher DHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 73FBE11D0 for ; Thu, 17 Sep 2015 16:29:01 +0000 (UTC) (envelope-from rpaulo@me.com) MIME-version: 1.0 Content-transfer-encoding: 8BIT Content-type: text/plain; charset=UTF-8 Received: from akita.hsd1.ca.comcast.net (c-73-162-13-215.hsd1.ca.comcast.net [73.162.13.215]) by mr11p00im-asmtp001.me.com (Oracle Communications Messaging Server 7.0.5.35.0 64bit (built Mar 31 2015)) with ESMTPSA id <0NUT006K0V04S720@mr11p00im-asmtp001.me.com> for freebsd-current@freebsd.org; Thu, 17 Sep 2015 15:28:55 +0000 (GMT) X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:,, definitions=2015-09-17_06:,, signatures=0 X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 kscore.is_bulkscore=5.55111512312578e-17 compositescore=0.981618935876834 phishscore=0 kscore.is_spamscore=0 rbsscore=0.981618935876834 recipient_to_sender_totalscore=0 spamscore=0 urlsuspectscore=0.981618935876834 adultscore=0 kscore.compositescore=0 circleOfTrustscore=0 suspectscore=0 recipient_domain_to_sender_totalscore=0 bulkscore=0 recipient_domain_to_sender_domain_totalscore=0 recipient_to_sender_domain_totalscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1412110000 definitions=main-1509170218 Message-id: <1442503731.1862.1.camel@me.com> Subject: Re: Intel Haswell support - Any updates? From: Rui Paulo To: Kris Moore , freebsd-current@freebsd.org Date: Thu, 17 Sep 2015 08:28:51 -0700 In-reply-to: <55FADB38.7000406@pcbsd.org> References: <55FA7324.5010603@icloud.com> <09A515F2-44BA-4DF0-9792-D4C56EEB9D7C@FreeBSD.org> <114F22EF-61E3-4D75-84FB-9D6E3FBCB8F3@FreeBSD.org> <20150917131333.GN1247@egr.msu.edu> <20150917134809.GA3025@c720-r276659> <55FAD5EF.5030001@pcbsd.org> <20150917171958.046e4b6b.ohartman@zedat.fu-berlin.de> <55FADB38.7000406@pcbsd.org> X-Mailer: Evolution 3.16.5-1 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 17 Sep 2015 16:29:01 -0000 On Thu, 2015-09-17 at 11:24 -0400, Kris Moore wrote: > On 09/17/2015 11:19, O. Hartmann wrote: > > Am Thu, 17 Sep 2015 11:02:07 -0400 > > Kris Moore schrieb: > > > > > On 09/17/2015 09:48, Matthias Apitz wrote: > > > > El dĂ­a Thursday, September 17, 2015 a las 10:41:43PM +0900, > > > > Lundberg, Johannes > > > > escribiĂł: > > > > > > > > > Same here. I would personally definitely buy new hardware > > > > > from Intel if > > > > > FreeBSD worked on it (not vesa...) > > > > > ... > > > > What dow you have against vesa? I run CURRENT on some Acer C720 > > > > Chromebooks with Haswell chipset in Vesa mode. And you will not > > > > note it. > > > > I have never ever had such a fast desktop (KDE4) before. I can > > > > live fine > > > > with Vesa until Haswell suport is there. > > > > > > > > matthias > > > BTW, have you tried the xf86-video-scfb driver? It works much > > > better > > > than vesa here. The only catch is you have to be booted UEFI with > > > CSM > > > disabled. Using it on my X1 Carbon, gets 3k resolution properly > > > and > > > everything. Thanks to Glen Barber for bringing that to my > > > attention. > > > > > Running that specific driver on several Lenovo HD4600 driven models > > gives me headaches > > and more. This software-framebuffer works - yes, on whatever > > resolution you might wish, > > but it consumes CPU time. That said, I recall that the display was > > jumpy, slow and > > unresponsive when used under heavy load - not even 3k resolution, > > but with a moderate > > lowend of 1980x1080. > > Interesting, that's been the opposite of my experience here. Vesa was > much slower / using more CPU time and didn't give me the native > resolution. Switching to scfb made the laptop "usable" for me, at > least > until we get a proper Intel driver that does Broadwell. I, too, used scfb for 4 months, but I gave up and installed Linux. These are the things that don't work with scfb: 1) brightness control (almost at max when booting) 2) external monitor 3) hardware acceleration. scfb is a working solution in specific cases, but a laptop isn't one of them. -- Rui Paulo From owner-freebsd-current@freebsd.org Thu Sep 17 17:00:24 2015 Return-Path: Delivered-To: freebsd-current@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 EA80D9CF873 for ; Thu, 17 Sep 2015 17:00:23 +0000 (UTC) (envelope-from dumbbell@FreeBSD.org) Received: from mail.made4.biz (mail.made4.biz [IPv6:2001:41d0:2:c018::1:3]) (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 B3BF718F0 for ; Thu, 17 Sep 2015 17:00:23 +0000 (UTC) (envelope-from dumbbell@FreeBSD.org) Received: from pat-199-212-65-22.resnet.yorku.ca ([199.212.65.22] helo=magellan.dumbbell.fr) by mail.made4.biz with esmtpsa (TLSv1.2:DHE-RSA-AES128-SHA:128) (Exim 4.85 (FreeBSD)) (envelope-from ) id 1ZccXl-000JSB-Nf for freebsd-current@freebsd.org; Thu, 17 Sep 2015 19:00:22 +0200 Subject: Re: Intel Haswell support - Any updates? To: freebsd-current@freebsd.org References: <55FA7324.5010603@icloud.com> From: =?UTF-8?Q?Jean-S=c3=a9bastien_P=c3=a9dron?= X-Enigmail-Draft-Status: N1110 Message-ID: <55FAF19F.9090701@FreeBSD.org> Date: Thu, 17 Sep 2015 19:00:15 +0200 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:38.0) Gecko/20100101 Thunderbird/38.2.0 MIME-Version: 1.0 In-Reply-To: <55FA7324.5010603@icloud.com> Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="Omi9RXjqAIGvohvOv5xcm9ie5iag7IQOs" X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 17 Sep 2015 17:00:24 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --Omi9RXjqAIGvohvOv5xcm9ie5iag7IQOs Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable Hi everyone! I'm very sorry I didn't communicate at all on the i915 update project. So here is a status update: since this morning, the driver builds fine. I'm currently attending the XDC (X.Org Developers Conference) and don't have an Intel laptop to test with me. However, Johannes Dieterich (also attending the conference) offerred his help, so we will do that today. Obviously, do not expect something stable in the coming couple days. Thank you for your patience :) To answer various questions in this thread: Why does it take so much time to update? Once Konstantin committed his i915 update, I was busy with non-FreeBSD activities until last July, when I slowly started back to work on i915. My goal is to reduce the diff with Linux as much as possible. But, as opposed to OpenBSD and DragonFlyBSD, we do not use a Linux compatibility layer which would dramatically ease our life. This layer exists for the OFED/Infiniband drivers: we are almost ready to move it to a central place, so we can use it in the near future in the DRM subsystem. Another problem I will fix in the near future is the method I used: I worked on a giant patch instead of doing several incremental commits. This is unfriendly for external contributors and hard to review. DragonFly got that right for instance. Now about other related tasks: o A Mesa update will be committed Real Soon Now=99. It will unlock GLAMOR and OpenCL support. o Once Mesa is updated, we can update xserver to 1.17.2. xserver 1.18 RC 1 works fine (at least for me :). It should be released for Halloween. o Wayland. The problem is NOT the output side of the graphics stack: it is the input part. We miss evdev (ported as a GSoC, waiting for review and commit), we miss udev, we miss libinput. This item deserves a dedicated email. Sorry, it's a bit short for such a large topic. It's difficult to expand more during a conference :) --=20 Jean-S=E9bastien P=E9dron --Omi9RXjqAIGvohvOv5xcm9ie5iag7IQOs 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 iQJ8BAEBCgBmBQJV+vGkXxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQ2NzA4N0ZEMUFFQUUwRTEyREJDNkE2RjAz OUU5OTc2MUE1RkQ5NENDAAoJEDnpl2Gl/ZTMRuYQAOC4JlLww2FdzQJWOquh2L1h +Mq0O2eoaxyUo413XEajd2Go+OA4nM5kXYmJV6XB+slL7nuYL6NhkTBvewKq07HD LjdNuDRCS7gSNPqOr215PULQ8JY0hxUtk2ON3GWTrh38aGTIo3Y0np+3DOGI4vvI uGwIW7Wj7pxltpXIYl4p7Wuhe8+FwpNDSFglhD1pDCiRqD1PpV/ZjiP9PRy8W19d F8Unkr2g8b+RG0eKJUAcpLb/63RJhbb/RSBgJe0PIHwxlymsLRsajjgtvRwJkuYS uhSMTcaepT269MnRLV0WHPALfGpEjYOmCRWx3GFQlSntIoi5a17IF9GKPScYlj0k FNZtQfSIRgJYKhUfo6HXvYaaKYHc+SJOzSRtm9DgRVTI+dx88CkLg9fkuu3DKDcN w8KvZYZyHLuvg4Xo1h7GsYD2iMVF9DK/hOah3fZBZZrQFB/CFgTpGTpb+Seb32e8 Q1qb3SIPSvqKvoPUHByzrkBh1Z5eqmQqL7P9trnbPgHtMNu8Qi5YTEdIKvnbOsWn a0VS9lVeeAEBOfc9h7gwmKIKn1RuEGKIvfS6FD6DM/oVSG/Zh78JLYbd26jUpT+N qtOPAxMwyLgDrsZx3SaJbUHqZKIBWGMIl2Oov6UFmpRk9kvLxqQjLQm1iitgWs4U zqm+qmGOZnRYBldphegW =C2k1 -----END PGP SIGNATURE----- --Omi9RXjqAIGvohvOv5xcm9ie5iag7IQOs-- From owner-freebsd-current@freebsd.org Thu Sep 17 17:27:25 2015 Return-Path: Delivered-To: freebsd-current@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 3BC0F9CF292 for ; Thu, 17 Sep 2015 17:27:25 +0000 (UTC) (envelope-from shawn.webb@hardenedbsd.org) Received: from mail-qk0-f179.google.com (mail-qk0-f179.google.com [209.85.220.179]) (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 EED0E1CAD for ; Thu, 17 Sep 2015 17:27:24 +0000 (UTC) (envelope-from shawn.webb@hardenedbsd.org) Received: by qkfq186 with SMTP id q186so9389544qkf.1 for ; Thu, 17 Sep 2015 10:27:23 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-type:content-disposition:in-reply-to :user-agent; bh=whePhMmAfUTazaRvZH39+mc8tPMcUrh+DODSRfuA5Jk=; b=gP0f40h/C47Qw0NTj44pH+/wS3lcfn/grQIm/fQQ1t6jUHLCZuiQucgM7PgDn5XvpO voFZU/SGMcRVUe1IGo4PQeRz6rECOiQmgrMJ1oMCOSQYLDT6J3jTGLD680MeTVFt5BY6 DCNUfm+EbTnIpfprmbWgHs68w0Sn0B77bpPi2sGetzGpsIic5GJPprhyXsKvVuS0soGm Yjkoewsm38+gMIEequ48gGOtStNAE6Rc6zIYxd8vSQjit1Ijy+7UvHS1Px3FyhTvpmeD k5lpcvBWMlrBLYtnOj/5D919XI2mOXkkjH+n1a86EcGABVf3OUtBolOr1gNWdGF9ZrlD /zEg== X-Gm-Message-State: ALoCoQlSHe0eNkzBte02RK8nh9N2INKLa+jRyd5RKX+gWC67i8RSO2ZNlnWQ1A3wBictwgnFtd2b X-Received: by 10.55.26.4 with SMTP id a4mr555196qka.8.1442510467809; Thu, 17 Sep 2015 10:21:07 -0700 (PDT) Received: from mutt-hardenedbsd.hardenedbsd.dev (c-73-135-80-144.hsd1.md.comcast.net. [73.135.80.144]) by smtp.gmail.com with ESMTPSA id x81sm1673351qha.24.2015.09.17.10.21.06 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 17 Sep 2015 10:21:07 -0700 (PDT) Date: Thu, 17 Sep 2015 13:21:05 -0400 From: Shawn Webb To: Jean-S??bastien P??dron Cc: freebsd-current@freebsd.org Subject: Re: Intel Haswell support - Any updates? Message-ID: <20150917172059.GB88816@mutt-hardenedbsd.hardenedbsd.dev> References: <55FA7324.5010603@icloud.com> <55FAF19F.9090701@FreeBSD.org> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="4bRzO86E/ozDv8r1" Content-Disposition: inline In-Reply-To: <55FAF19F.9090701@FreeBSD.org> X-Operating-System: FreeBSD mutt-hardenedbsd 11.0-CURRENT-HBSD FreeBSD 11.0-CURRENT-HBSD X-PGP-Key: http://pgp.mit.edu/pks/lookup?op=vindex&search=0x6A84658F52456EEE User-Agent: Mutt/1.5.23 (2014-03-12) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 17 Sep 2015 17:27:25 -0000 --4bRzO86E/ozDv8r1 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Sep 17, 2015 at 07:00:15PM +0200, Jean-S??bastien P??dron wrote: > Hi everyone! >=20 > I'm very sorry I didn't communicate at all on the i915 update project. >=20 > So here is a status update: since this morning, the driver builds fine. > I'm currently attending the XDC (X.Org Developers Conference) and don't > have an Intel laptop to test with me. However, Johannes Dieterich (also > attending the conference) offerred his help, so we will do that today. >=20 > Obviously, do not expect something stable in the coming couple days. > Thank you for your patience :) First of all, I want to say (nay, YELL!) "THANK YOU!" You're doing a tremendously awesome job that is much needed. I think you're the one showing the most amount of patience, especially given the community's desire to have Haswell support. I know there's a difference between "builds fine" and "runs fine". With it building fine, is the driver at the point where we can start rudimentary testing? I can't help out in the development efforts, but I'd love to help test and give bug reports. This is one way the community at large can help. Even if it means stuffing your Inbox with bug spam. ;) >=20 > To answer various questions in this thread: >=20 > Why does it take so much time to update? Once Konstantin committed his > i915 update, I was busy with non-FreeBSD activities until last July, > when I slowly started back to work on i915. My goal is to reduce the > diff with Linux as much as possible. But, as opposed to OpenBSD and > DragonFlyBSD, we do not use a Linux compatibility layer which would > dramatically ease our life. Is a linux compat layer something you deem necessary for long-term success? >=20 > This layer exists for the OFED/Infiniband drivers: we are almost ready > to move it to a central place, so we can use it in the near future in > the DRM subsystem. >=20 > Another problem I will fix in the near future is the method I used: I > worked on a giant patch instead of doing several incremental commits. > This is unfriendly for external contributors and hard to review. > DragonFly got that right for instance. >=20 > Now about other related tasks: > o A Mesa update will be committed Real Soon Now?. It will unlock > GLAMOR and OpenCL support. OpenCL on FreeBSD would be stupendously amazing! > o Once Mesa is updated, we can update xserver to 1.17.2. xserver > 1.18 RC 1 works fine (at least for me :). It should be released > for Halloween. > o Wayland. The problem is NOT the output side of the graphics > stack: it is the input part. We miss evdev (ported as a GSoC, > waiting for review and commit), we miss udev, we miss libinput. > This item deserves a dedicated email. >=20 > Sorry, it's a bit short for such a large topic. It's difficult to expand > more during a conference :) Thanks again for your hard work and diligence. Thanks, --=20 Shawn Webb HardenedBSD GPG Key ID: 0x6A84658F52456EEE GPG Key Fingerprint: 2ABA B6BD EF6A F486 BE89 3D9E 6A84 658F 5245 6EEE --4bRzO86E/ozDv8r1 Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQIcBAEBCAAGBQJV+vZ3AAoJEGqEZY9SRW7u9G8QAMC2c76BtPr6zsaO7Qoc8Z5v NM0LsFrDFDus4KYru+vr19DICGcP39KvMnV//hO8sobmyU3cUuXck2xFbhSxfdOI GcnEGukX+HAuHq9C66NYuMmIkQzMB17eKpouWE5ZXJZ+Wm7jcC0gOTUM3PMnhuJi TSks5KYB9Z5AJL2KtkE6RVILYzeKgfwn35yIizxOVB5phnsFEZadj8ogaBv6683v KhiUA07o80Cy7ZztyO7X1RwOC0D0AqC1EofT/ak5V91BclJ0X+Y5KkbAtgcNpBqv uoucAwjyYj0E0U7Bxm80IslscUPYC6EQkUBxH79S5w+ChTVyiqahkun9dTu4WAfV 8xC5RGHEBSRubJmw3CCv5mA6N+MSLqdrbD1Vz4F0Nujj0nlcaYaSZtfx5PutDEUj qUJmaCB5VJMUP+GeRJ9ST+KQNYjFh7Ebe89OcCgvR4//ixaCEElXYpZBQb/FrmIA Rv0rQAYTJuiizAj7zimr7t2nzYUCjqwRAAMM549B5Jd/1L2aLxsAEYEdpKqyDqKU rKEpY8OUE8ZYe9qqVSvP/ifLVggEC6u24czekugx1Cu1+gwLnpClYioKpCCvtl8x 6Yc9EyqiU+6/fY2ZbCLDvi5zeyFxKcTMQVRZJQ0Nf9ED1MskeYMTiUtaeCOibQZU S7KUMDfPvm7iVp/oKV9c =z3Ym -----END PGP SIGNATURE----- --4bRzO86E/ozDv8r1-- From owner-freebsd-current@freebsd.org Thu Sep 17 17:28:19 2015 Return-Path: Delivered-To: freebsd-current@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 8F39D9CF372 for ; Thu, 17 Sep 2015 17:28:19 +0000 (UTC) (envelope-from stefan.wendler@tngtech.com) Received: from zimbra.tngtech.com (zimbra.tngtech.com [212.204.93.107]) (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 49E8A1085 for ; Thu, 17 Sep 2015 17:28:18 +0000 (UTC) (envelope-from stefan.wendler@tngtech.com) Received: from localhost (localhost [127.0.0.1]) by zimbra.tngtech.com (Postfix) with ESMTP id 81085B0031C for ; Thu, 17 Sep 2015 19:28:15 +0200 (CEST) Received: from zimbra.tngtech.com ([127.0.0.1]) by localhost (zimbra.tngtech.com [127.0.0.1]) (amavisd-new, port 10032) with ESMTP id EwPYrdHXJK-W for ; Thu, 17 Sep 2015 19:28:15 +0200 (CEST) Received: from localhost (localhost [127.0.0.1]) by zimbra.tngtech.com (Postfix) with ESMTP id 3AA9AB006E3 for ; Thu, 17 Sep 2015 19:28:15 +0200 (CEST) X-Virus-Scanned: amavisd-new at tngtech.com Received: from zimbra.tngtech.com ([127.0.0.1]) by localhost (zimbra.tngtech.com [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id yIt4LX4dT2lx for ; Thu, 17 Sep 2015 19:28:15 +0200 (CEST) Received: from hactar.localnet (p4FE56B31.dip0.t-ipconnect.de [79.229.107.49]) by zimbra.tngtech.com (Postfix) with ESMTPSA id 116E7B0031C for ; Thu, 17 Sep 2015 19:28:15 +0200 (CEST) From: Stefan Wendler To: freebsd-current@freebsd.org Subject: Re: Intel Haswell support - Any updates? Date: Thu, 17 Sep 2015 19:28:14 +0200 Message-ID: <11271727.FrCOrXGY1l@hactar> Organization: TNG Technology Consulting GmbH User-Agent: KMail/4.14.3 (FreeBSD/10.2-RELEASE; KDE/4.14.3; amd64; ; ) In-Reply-To: <87twqt2gs9.fsf@gooddata.com> References: <55FA7324.5010603@icloud.com> <55FADB38.7000406@pcbsd.org> <87twqt2gs9.fsf@gooddata.com> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 17 Sep 2015 17:28:19 -0000 On Thursday 17 September 2015 17:43:02 Nikola Pajkovsky wrote: > Use memcontrol to set mtrr write-combine for your Vesa. Vesa is lightning > fast on T440p on 1920x1200. I use a T540 and didn't get this to work yet. Can you give me the commands you've used? I guess we have the same chips anyway. So the hex-values should be the same? Cheers, Stefan From owner-freebsd-current@freebsd.org Thu Sep 17 17:38:40 2015 Return-Path: Delivered-To: freebsd-current@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 4558A9CF83F for ; Thu, 17 Sep 2015 17:38:40 +0000 (UTC) (envelope-from dieterich.joh@gmail.com) Received: from mail-oi0-x232.google.com (mail-oi0-x232.google.com [IPv6:2607:f8b0:4003:c06::232]) (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 1E57A18EA; Thu, 17 Sep 2015 17:38:40 +0000 (UTC) (envelope-from dieterich.joh@gmail.com) Received: by oixx17 with SMTP id x17so13639290oix.0; Thu, 17 Sep 2015 10:38:39 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=/QG96GNLZf3UUmdUwsJ7kcN6zHzbOWexc1DcshsHy9c=; b=KPJcWlXK++LGMKQCcRLcKsyqxkpADH+nRJROYgqNCXlY/lBeP+mWn6UrMtUMCXVKIu wxffGgxJCC4zwLhvPTTZvwO3awImeqsLGf8Fi0iZK4dhWAUUNFcOAoIcEoGpKwzZfaJM XpniFYSfWNl7QT36RegcXygJo1CYVSeL2+qY0V/w/bVFjRZptYnMjyMe9Wi9qnTIaA3y VeDY5S2lp+1b4XptVFSHMdmaVJk/uHvMiLQ7R3oIcKxi6HGB8lDYKmqEKSiWX8V0fXac 7uSAS7ExPQQb3nJ6P809ukQ7XLTiJQmNgO60dkwjRtk7oaLT78i4SRQ76BC8QKvFHsb9 z9Cw== MIME-Version: 1.0 X-Received: by 10.202.209.74 with SMTP id i71mr303196oig.25.1442511519361; Thu, 17 Sep 2015 10:38:39 -0700 (PDT) Received: by 10.202.61.69 with HTTP; Thu, 17 Sep 2015 10:38:39 -0700 (PDT) In-Reply-To: <20150917172059.GB88816@mutt-hardenedbsd.hardenedbsd.dev> References: <55FA7324.5010603@icloud.com> <55FAF19F.9090701@FreeBSD.org> <20150917172059.GB88816@mutt-hardenedbsd.hardenedbsd.dev> Date: Thu, 17 Sep 2015 13:38:39 -0400 Message-ID: Subject: Re: Intel Haswell support - Any updates? From: Johannes Dieterich To: Shawn Webb Cc: "Jean-S??bastien P??dron" , freebsd-current Content-Type: text/plain; charset=UTF-8 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 17 Sep 2015 17:38:40 -0000 Hi, just chipping into the conversation for a detail Re: OpenCL On Thu, Sep 17, 2015 at 1:21 PM, Shawn Webb wrote: > On Thu, Sep 17, 2015 at 07:00:15PM +0200, Jean-S??bastien P??dron wrote: >> Now about other related tasks: >> o A Mesa update will be committed Real Soon Now?. It will unlock >> GLAMOR and OpenCL support. > > OpenCL on FreeBSD would be stupendously amazing! Not would: is! :-) You can already use OpenCL on radeon and Intel GPUs (note, only single-precision for Intel, this is an upstream issue) or on CPU as fallback when using the mesa-next branch from the freebsd-graphics github. This does not require an update of the kernel compared to CURRENT (of course only supported GPUs work). There are some helper ports in the github as well (libraries, e.g.) if you write your own OpenCL software and I have a few more in my pipeline. I personally have an interest in excellent OpenCL support on FBSD. Getting back to building the i915 update. Johannes From owner-freebsd-current@freebsd.org Thu Sep 17 17:40:40 2015 Return-Path: Delivered-To: freebsd-current@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 B75FA9CFA3B for ; Thu, 17 Sep 2015 17:40:40 +0000 (UTC) (envelope-from guru@unixarea.de) Received: from ms-10.1blu.de (ms-10.1blu.de [178.254.4.101]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 7163F1AE9 for ; Thu, 17 Sep 2015 17:40:40 +0000 (UTC) (envelope-from guru@unixarea.de) Received: from [82.113.121.34] (helo=localhost.unixarea.de) by ms-10.1blu.de with esmtpsa (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.76) (envelope-from ) id 1ZcdAi-0006Mi-A4; Thu, 17 Sep 2015 19:40:36 +0200 Received: from localhost.my.domain (c720-r276659 [127.0.0.1]) by localhost.unixarea.de (8.14.9/8.14.9) with ESMTP id t8HHeZOT001748 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Thu, 17 Sep 2015 19:40:35 +0200 (CEST) (envelope-from guru@unixarea.de) Received: (from guru@localhost) by localhost.my.domain (8.14.9/8.14.9/Submit) id t8HHeZi5001747; Thu, 17 Sep 2015 19:40:35 +0200 (CEST) (envelope-from guru@unixarea.de) X-Authentication-Warning: localhost.my.domain: guru set sender to guru@unixarea.de using -f Date: Thu, 17 Sep 2015 19:40:35 +0200 From: Matthias Apitz To: Kris Moore Cc: freebsd-current@freebsd.org Subject: Re: Intel Haswell support - Any updates? Message-ID: <20150917174035.GA1730@c720-r276659> Reply-To: Matthias Apitz Mail-Followup-To: Matthias Apitz , Kris Moore , freebsd-current@freebsd.org References: <09A515F2-44BA-4DF0-9792-D4C56EEB9D7C@FreeBSD.org> <114F22EF-61E3-4D75-84FB-9D6E3FBCB8F3@FreeBSD.org> <20150917131333.GN1247@egr.msu.edu> <20150917134809.GA3025@c720-r276659> <55FAD5EF.5030001@pcbsd.org> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <55FAD5EF.5030001@pcbsd.org> X-Operating-System: FreeBSD 11.0-CURRENT r269739 (i386) User-Agent: Mutt/1.5.23 (2014-03-12) X-Con-Id: 51246 X-Con-U: 0-guru X-Originating-IP: 82.113.121.34 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 17 Sep 2015 17:40:40 -0000 El dĂ­a Thursday, September 17, 2015 a las 11:02:07AM -0400, Kris Moore escribiĂł: > On 09/17/2015 09:48, Matthias Apitz wrote: > > El dĂ­a Thursday, September 17, 2015 a las 10:41:43PM +0900, Lundberg, Johannes escribiĂł: > > > >> Same here. I would personally definitely buy new hardware from Intel if > >> FreeBSD worked on it (not vesa...) > >> ... > > What dow you have against vesa? I run CURRENT on some Acer C720 > > Chromebooks with Haswell chipset in Vesa mode. And you will not note it. > > I have never ever had such a fast desktop (KDE4) before. I can live fine > > with Vesa until Haswell suport is there. > > > > matthias > > BTW, have you tried the xf86-video-scfb driver? It works much better > than vesa here. The only catch is you have to be booted UEFI with CSM > disabled. Using it on my X1 Carbon, gets 3k resolution properly and > everything. Thanks to Glen Barber for bringing that to my attention. The Chromebook Acer C720 does not has UEFI; it runs Coreboot with SeaBIOS as payload. The Xorg runs fine without any xorg.conf file, just detects the video as Vesa with 1366x768 resolution, the max of the 11" screen of this netbook. matthias -- Matthias Apitz, ✉ guru@unixarea.de, 🌠http://www.unixarea.de/ ⎠+49-176-38902045 No! Nein! ¡No! Όχι! -- ΕυχαĎÎąĎτούμε! From owner-freebsd-current@freebsd.org Thu Sep 17 17:54:04 2015 Return-Path: Delivered-To: freebsd-current@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 CB64D9CFFA5 for ; Thu, 17 Sep 2015 17:54:04 +0000 (UTC) (envelope-from freebsd@pki2.com) Received: from btw.pki2.com (btw.pki2.com [IPv6:2001:470:a:6fd::2]) (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 92641138F; Thu, 17 Sep 2015 17:54:04 +0000 (UTC) (envelope-from freebsd@pki2.com) Received: from localhost (localhost [IPv6:::1]) by btw.pki2.com (8.15.2/8.14.9) with ESMTP id t8HHrpCn059456; Thu, 17 Sep 2015 10:53:51 -0700 (PDT) (envelope-from freebsd@pki2.com) DMARC-Filter: OpenDMARC Filter v1.3.1 btw.pki2.com t8HHrpCn059456 Authentication-Results: btw.pki2.com; dmarc=none header.from=pki2.com DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=pki2.com; s=pki2; t=1442512432; bh=XXE7XWGGBi+E6MAKDh7+AOA492lnbdOoxlrAA+RLK/k=; h=Subject:From:To:Cc:Date:In-Reply-To:References; z=Subject:=20Re:=20Intel=20Haswell=20support=20-=20Any=20updates?|F rom:=20Dennis=20Glatting=20|To:=20Johannes=20Die terich=20,=20Shawn=20Webb=0D=0A=09=20|Cc:=20Jean-S??bastien=20P??dron=20,=20freebsd-current=0D=0A=09=20|Date:=20Thu,=2017=20Sep=202015=2010:53:51=20-0700|In-Rep ly-To:=20|References:=20<55FA7324.5010603@icloud.com>=20<55FAF19 F.9090701@FreeBSD.org>=0D=0A=09=20<20150917172059.GB88816@mutt-har denedbsd.hardenedbsd.dev>=0D=0A=09=20; b=RCSE2l1pJSuTVGnOoFDmGuvuH9jlaby7LGSIvEXpfrvhcryyVX1ABD+pHuPTMlfVQ u89Dnmdkv0yfIKauiBZAO6vCwqOOpMcK0QJOiWC5AbEyTUxDlomXVaFYptcbSuaRg0 IPsASeedr73i2zxdtNj3Kp6o8iJ4k89n2HhV3LinqtXU3Y5ZQj7UYfA77QIP1gfgB8 3Sv9jlXvFBZdW0Fb8zpmWeOHiArQI63i6BKTCvRp/JxlvKkvdkpI6YpPK89uDiN5vd Q2zViAxmWPJFNV119bYz/cIy/RIGh+FgvugvypOd3gRaHWfkre+MlRjo7G3mBiWz1G Id9ZXVP39hOsQ== Message-ID: <1442512431.82911.76.camel@pki2.com> Subject: Re: Intel Haswell support - Any updates? From: Dennis Glatting To: Johannes Dieterich , Shawn Webb Cc: Jean-S??bastien P??dron , freebsd-current Date: Thu, 17 Sep 2015 10:53:51 -0700 In-Reply-To: References: <55FA7324.5010603@icloud.com> <55FAF19F.9090701@FreeBSD.org> <20150917172059.GB88816@mutt-hardenedbsd.hardenedbsd.dev> Content-Type: text/plain; charset="UTF-8" X-Mailer: Evolution 3.16.5 FreeBSD GNOME Team Port Mime-Version: 1.0 Content-Transfer-Encoding: 7bit X-SoftwareMunitions-MailScanner-Information: Dennis Glatting X-SoftwareMunitions-MailScanner-ID: t8HHrpCn059456 X-SoftwareMunitions-MailScanner: Found to be clean X-MailScanner-From: freebsd@pki2.com X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 17 Sep 2015 17:54:05 -0000 On Thu, 2015-09-17 at 13:38 -0400, Johannes Dieterich wrote: > Hi, > > just chipping into the conversation for a detail Re: OpenCL > > On Thu, Sep 17, 2015 at 1:21 PM, Shawn Webb < > shawn.webb@hardenedbsd.org> wrote: > > On Thu, Sep 17, 2015 at 07:00:15PM +0200, Jean-S??bastien P??dron > > wrote: > > > Now about other related tasks: > > > o A Mesa update will be committed Real Soon Now?. It will > > > unlock > > > GLAMOR and OpenCL support. > > > > OpenCL on FreeBSD would be stupendously amazing! > Not would: is! :-) You can already use OpenCL on radeon and Intel > GPUs > (note, only single-precision for Intel, this is an upstream issue) or > on CPU as fallback when using the mesa-next branch from the > freebsd-graphics github. This does not require an update of the > kernel > compared to CURRENT (of course only supported GPUs work). There are > some helper ports in the github as well (libraries, e.g.) if you > write > your own OpenCL software and I have a few more in my pipeline. I > personally have an interest in excellent OpenCL support on FBSD. > Ditto. I'm on Linux because of OpenCL and OpenMP (gcc). > Getting back to building the i915 update. > > Johannes > _______________________________________________ > freebsd-current@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to " > freebsd-current-unsubscribe@freebsd.org" From owner-freebsd-current@freebsd.org Thu Sep 17 18:31:40 2015 Return-Path: Delivered-To: freebsd-current@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 8B0069CF43E for ; Thu, 17 Sep 2015 18:31:40 +0000 (UTC) (envelope-from rcarter@pinyon.org) Received: from quine.pinyon.org (acipenser.esturion.net [65.101.5.252]) (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 5FDAA1E23 for ; Thu, 17 Sep 2015 18:31:40 +0000 (UTC) (envelope-from rcarter@pinyon.org) Received: by quine.pinyon.org (Postfix, from userid 122) id 8EA781602B3; Thu, 17 Sep 2015 11:23:08 -0700 (MST) X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on quine.pinyon.org X-Spam-Level: X-Spam-Status: No, score=-2.9 required=5.0 tests=ALL_TRUSTED,BAYES_00 autolearn=ham autolearn_force=no version=3.4.1 Received: from feyerabend.n1.pinyon.org (acipenser.esturion.net [65.101.5.252]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by quine.pinyon.org (Postfix) with ESMTPSA id A136B1600C6 for ; Thu, 17 Sep 2015 11:23:06 -0700 (MST) Subject: Re: Intel Haswell support - Any updates? To: freebsd-current@freebsd.org References: <09A515F2-44BA-4DF0-9792-D4C56EEB9D7C@FreeBSD.org> <114F22EF-61E3-4D75-84FB-9D6E3FBCB8F3@FreeBSD.org> <20150917131333.GN1247@egr.msu.edu> <20150917134809.GA3025@c720-r276659> <55FAD5EF.5030001@pcbsd.org> <20150917174035.GA1730@c720-r276659> From: "Russell L. Carter" Message-ID: <55FB050A.2080500@pinyon.org> Date: Thu, 17 Sep 2015 11:23:06 -0700 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:38.0) Gecko/20100101 Thunderbird/38.2.0 MIME-Version: 1.0 In-Reply-To: <20150917174035.GA1730@c720-r276659> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 8bit X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 17 Sep 2015 18:31:40 -0000 On 09/17/15 10:40, Matthias Apitz wrote: > El dĂ­a Thursday, September 17, 2015 a las 11:02:07AM -0400, Kris Moore escribiĂł: > >> On 09/17/2015 09:48, Matthias Apitz wrote: >>> El dĂ­a Thursday, September 17, 2015 a las 10:41:43PM +0900, Lundberg, Johannes escribiĂł: >>> >>>> Same here. I would personally definitely buy new hardware from Intel if >>>> FreeBSD worked on it (not vesa...) >>>> ... >>> What dow you have against vesa? I run CURRENT on some Acer C720 >>> Chromebooks with Haswell chipset in Vesa mode. And you will not note it. >>> I have never ever had such a fast desktop (KDE4) before. I can live fine >>> with Vesa until Haswell suport is there. >>> >>> matthias >> >> BTW, have you tried the xf86-video-scfb driver? It works much better >> than vesa here. The only catch is you have to be booted UEFI with CSM >> disabled. Using it on my X1 Carbon, gets 3k resolution properly and >> everything. Thanks to Glen Barber for bringing that to my attention. > > The Chromebook Acer C720 does not has UEFI; it runs Coreboot with > SeaBIOS as payload. > > The Xorg runs fine without any xorg.conf file, just detects the video as > Vesa with 1366x768 resolution, the max of the 11" screen of this > netbook. Do you have 802.11n and hibernate working on that c720? I put linux on mine for that reason. Although despite immense efforts I can't get the trackpad to be detected. I tried bringing up 10.2 on it but couldn't get it to boot. These things are just awesome. 4G memory + i3 + 6hr battery for $240 delivered. Russell > matthias > From owner-freebsd-current@freebsd.org Thu Sep 17 18:42:16 2015 Return-Path: Delivered-To: freebsd-current@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 DAC3A9CF864 for ; Thu, 17 Sep 2015 18:42:15 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-io0-x22a.google.com (mail-io0-x22a.google.com [IPv6:2607:f8b0:4001:c06::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 A238C1448 for ; Thu, 17 Sep 2015 18:42:15 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: by iofh134 with SMTP id h134so32212574iof.0 for ; Thu, 17 Sep 2015 11:42:15 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; bh=GwCpr2lsk0zlSta15JyQ6o8fBWQ59HfrFQnV7lOVjiw=; b=iW2TLWnC79Ad/I8UinaiBFZaCmFGRdHf6wTsOtSgiSjdmJWu69G89W4gSLIXH9+9kF ZlOMMGFrEo084Z72Wqj3g4scNctt0DYwj22GC6Y7mC8aBA1njefwxt07pTZVn3LvPzXI /qjc2i0Mko6/mg6t3sgcu5QI2Ug8/I8KSf7RLlrhGatDRlhjvPWgJeB9Gif3Rv55Qres B2FvZqyPi065Klr44RuwC13JqXefWdjmo8Ro4TfpG0Um4QAzn6X8H5fXz4X6c2aMp2io 4k8IgLztlmfp7keM94t1H3XCbWUGgeyHY7FXyoW24xnXy0OkkxEGnhFgm72ny6fBR5EB dLEA== MIME-Version: 1.0 X-Received: by 10.107.46.228 with SMTP id u97mr8671346iou.165.1442515335116; Thu, 17 Sep 2015 11:42:15 -0700 (PDT) Received: by 10.36.28.208 with HTTP; Thu, 17 Sep 2015 11:42:14 -0700 (PDT) In-Reply-To: <55FB050A.2080500@pinyon.org> References: <09A515F2-44BA-4DF0-9792-D4C56EEB9D7C@FreeBSD.org> <114F22EF-61E3-4D75-84FB-9D6E3FBCB8F3@FreeBSD.org> <20150917131333.GN1247@egr.msu.edu> <20150917134809.GA3025@c720-r276659> <55FAD5EF.5030001@pcbsd.org> <20150917174035.GA1730@c720-r276659> <55FB050A.2080500@pinyon.org> Date: Thu, 17 Sep 2015 11:42:14 -0700 Message-ID: Subject: Re: Intel Haswell support - Any updates? From: Adrian Chadd To: "Russell L. Carter" Cc: freebsd-current Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 17 Sep 2015 18:42:16 -0000 run -HEAD on it. The wifi works great (it's atheros.) All that's missing is haswell graphics. -a On 17 September 2015 at 11:23, Russell L. Carter wrote= : > > > On 09/17/15 10:40, Matthias Apitz wrote: >> >> El d=C3=83=C2=ADa Thursday, September 17, 2015 a las 11:02:07AM -0400, K= ris Moore >> escribi=C3=83=C2=B3: >> >>> On 09/17/2015 09:48, Matthias Apitz wrote: >>>> >>>> El d=C3=83=C2=ADa Thursday, September 17, 2015 a las 10:41:43PM +0900,= Lundberg, >>>> Johannes escribi=C3=83=C2=B3: >>>> >>>>> Same here. I would personally definitely buy new hardware from Intel = if >>>>> FreeBSD worked on it (not vesa...) >>>>> ... >>>> >>>> What dow you have against vesa? I run CURRENT on some Acer C720 >>>> Chromebooks with Haswell chipset in Vesa mode. And you will not note i= t. >>>> I have never ever had such a fast desktop (KDE4) before. I can live fi= ne >>>> with Vesa until Haswell suport is there. >>>> >>>> matthias >>> >>> >>> BTW, have you tried the xf86-video-scfb driver? It works much better >>> than vesa here. The only catch is you have to be booted UEFI with CSM >>> disabled. Using it on my X1 Carbon, gets 3k resolution properly and >>> everything. Thanks to Glen Barber for bringing that to my attention. >> >> >> The Chromebook Acer C720 does not has UEFI; it runs Coreboot with >> SeaBIOS as payload. >> >> The Xorg runs fine without any xorg.conf file, just detects the video as >> Vesa with 1366x768 resolution, the max of the 11" screen of this >> netbook. > > > Do you have 802.11n and hibernate working on that c720? I put linux on > mine for that reason. Although despite immense efforts I can't get > the trackpad to be detected. I tried bringing up 10.2 on it but > couldn't get it to boot. These things are just awesome. 4G memory > + i3 + 6hr battery for $240 delivered. > > Russell > >> matthias >> > _______________________________________________ > freebsd-current@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org= " From owner-freebsd-current@freebsd.org Thu Sep 17 18:45:02 2015 Return-Path: Delivered-To: freebsd-current@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 262479CF969 for ; Thu, 17 Sep 2015 18:45:02 +0000 (UTC) (envelope-from n.pajkovsky@gmail.com) Received: from mail-wi0-x22d.google.com (mail-wi0-x22d.google.com [IPv6:2a00:1450:400c:c05::22d]) (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 B15D515DE; Thu, 17 Sep 2015 18:45:01 +0000 (UTC) (envelope-from n.pajkovsky@gmail.com) Received: by wiclk2 with SMTP id lk2so2901629wic.1; Thu, 17 Sep 2015 11:44:59 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=from:to:cc:subject:references:date:in-reply-to:message-id :user-agent:mime-version:content-type:content-transfer-encoding; bh=4JPsWQfyF5AnxkwIDLlNvhzSDqNa74pK8LypA3sCV0s=; b=o32qd4g9hh1eBCgIr++2SZoFkuNqxJfiuXaHHoOjWQbim1HO/wC9AG5kCFkZbOWX54 RW+ZyRiK0Y0H7jRqMRnTibirJnPBuMcVAXx5FpHKe7hlhNYxthKICZPGBMD8VYYMlChl piLxxFDwimeXM4FQNCBeNqv2s/b96nVpnMzfYm4PbPG/ZUkwub1TxiVqgr2SUTrEXmFR 2Ul0OK9dj1ALjSWLu42VpqBIBzM/8H9KCr+d2NyahXrbyFWiY+YMRhwaUBygkxbnYWk3 ByxN0bmK8JkuW+s7sSogaq/KqV4RKbHVZiSzhMAfv+Je91zwwB7EJKa0mqdMmdWy/arH atWw== X-Received: by 10.180.36.212 with SMTP id s20mr10660675wij.14.1442515499368; Thu, 17 Sep 2015 11:44:59 -0700 (PDT) Received: from localhost (ip-94-112-33-45.net.upcbroadband.cz. [94.112.33.45]) by smtp.gmail.com with ESMTPSA id uc12sm11472054wib.13.2015.09.17.11.44.57 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 17 Sep 2015 11:44:58 -0700 (PDT) From: Nikola Pajkovsky To: =?utf-8?Q?Jean-S=C3=A9bastien_P=C3=A9dron?= Cc: freebsd-current@freebsd.org Subject: Re: Intel Haswell support - Any updates? References: <55FA7324.5010603@icloud.com> <55FAF19F.9090701@FreeBSD.org> Date: Thu, 17 Sep 2015 20:44:57 +0200 In-Reply-To: <55FAF19F.9090701@FreeBSD.org> (=?utf-8?Q?=22Jean-S=C3=A9bast?= =?utf-8?Q?ien_P=C3=A9dron=22's?= message of "Thu, 17 Sep 2015 19:00:15 +0200") Message-ID: <87eghwlwba.fsf@gooddata.com> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.5 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 17 Sep 2015 18:45:02 -0000 Jean-S=C3=A9bastien P=C3=A9dron writes: > Hi everyone! > > This layer exists for the OFED/Infiniband drivers: we are almost ready > to move it to a central place, so we can use it in the near future in > the DRM subsystem. Is it part of your huge patch or where can I found commits related to linux compat layer? --=20 Nikola From owner-freebsd-current@freebsd.org Thu Sep 17 18:52:09 2015 Return-Path: Delivered-To: freebsd-current@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 1767E9CFCAB for ; Thu, 17 Sep 2015 18:52:09 +0000 (UTC) (envelope-from rcarter@pinyon.org) Received: from quine.pinyon.org (acipenser.esturion.net [65.101.5.252]) (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 D15B91B06 for ; Thu, 17 Sep 2015 18:52:08 +0000 (UTC) (envelope-from rcarter@pinyon.org) Received: by quine.pinyon.org (Postfix, from userid 122) id CA1681602B3; Thu, 17 Sep 2015 11:52:07 -0700 (MST) X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on quine.pinyon.org X-Spam-Level: X-Spam-Status: No, score=-2.9 required=5.0 tests=ALL_TRUSTED,BAYES_00 autolearn=ham autolearn_force=no version=3.4.1 Received: from feyerabend.n1.pinyon.org (acipenser.esturion.net [65.101.5.252]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by quine.pinyon.org (Postfix) with ESMTPSA id B8A721600C6 for ; Thu, 17 Sep 2015 11:52:05 -0700 (MST) Subject: Re: Intel Haswell support - Any updates? To: freebsd-current@freebsd.org References: <09A515F2-44BA-4DF0-9792-D4C56EEB9D7C@FreeBSD.org> <114F22EF-61E3-4D75-84FB-9D6E3FBCB8F3@FreeBSD.org> <20150917131333.GN1247@egr.msu.edu> <20150917134809.GA3025@c720-r276659> <55FAD5EF.5030001@pcbsd.org> <20150917174035.GA1730@c720-r276659> <55FB050A.2080500@pinyon.org> From: "Russell L. Carter" Message-ID: <55FB0BD5.9000104@pinyon.org> Date: Thu, 17 Sep 2015 11:52:05 -0700 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:38.0) Gecko/20100101 Thunderbird/38.2.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 8bit X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 17 Sep 2015 18:52:09 -0000 On 09/17/15 11:42, Adrian Chadd wrote: > run -HEAD on it. The wifi works great (it's atheros.) Excellent to hear. When I get back from traveling I'll bring up -HEAD. Thanks, Russell > > All that's missing is haswell graphics. > > > -a > > > On 17 September 2015 at 11:23, Russell L. Carter wrote: >> >> >> On 09/17/15 10:40, Matthias Apitz wrote: >>> >>> El dĂ­a Thursday, September 17, 2015 a las 11:02:07AM -0400, Kris Moore >>> escribiĂÂł: >>> >>>> On 09/17/2015 09:48, Matthias Apitz wrote: >>>>> >>>>> El dĂ­a Thursday, September 17, 2015 a las 10:41:43PM +0900, Lundberg, >>>>> Johannes escribiĂÂł: >>>>> >>>>>> Same here. I would personally definitely buy new hardware from Intel if >>>>>> FreeBSD worked on it (not vesa...) >>>>>> ... >>>>> >>>>> What dow you have against vesa? I run CURRENT on some Acer C720 >>>>> Chromebooks with Haswell chipset in Vesa mode. And you will not note it. >>>>> I have never ever had such a fast desktop (KDE4) before. I can live fine >>>>> with Vesa until Haswell suport is there. >>>>> >>>>> matthias >>>> >>>> >>>> BTW, have you tried the xf86-video-scfb driver? It works much better >>>> than vesa here. The only catch is you have to be booted UEFI with CSM >>>> disabled. Using it on my X1 Carbon, gets 3k resolution properly and >>>> everything. Thanks to Glen Barber for bringing that to my attention. >>> >>> >>> The Chromebook Acer C720 does not has UEFI; it runs Coreboot with >>> SeaBIOS as payload. >>> >>> The Xorg runs fine without any xorg.conf file, just detects the video as >>> Vesa with 1366x768 resolution, the max of the 11" screen of this >>> netbook. >> >> >> Do you have 802.11n and hibernate working on that c720? I put linux on >> mine for that reason. Although despite immense efforts I can't get >> the trackpad to be detected. I tried bringing up 10.2 on it but >> couldn't get it to boot. These things are just awesome. 4G memory >> + i3 + 6hr battery for $240 delivered. >> >> Russell >> >>> matthias >>> >> _______________________________________________ >> freebsd-current@freebsd.org mailing list >> https://lists.freebsd.org/mailman/listinfo/freebsd-current >> To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" > _______________________________________________ > freebsd-current@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" > From owner-freebsd-current@freebsd.org Thu Sep 17 18:54:40 2015 Return-Path: Delivered-To: freebsd-current@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 AE73A9CFE7D for ; Thu, 17 Sep 2015 18:54:40 +0000 (UTC) (envelope-from grembo@freebsd.org) Received: from mail.grem.de (outcast.grem.de [213.239.217.27]) by mx1.freebsd.org (Postfix) with SMTP id 12F841F4E for ; Thu, 17 Sep 2015 18:54:39 +0000 (UTC) (envelope-from grembo@freebsd.org) Received: (qmail 31455 invoked by uid 89); 17 Sep 2015 18:54:37 -0000 Received: from unknown (HELO ?10.68.119.63?) (mg@grem.de@109.43.0.13) by mail.grem.de with ESMTPA; 17 Sep 2015 18:54:37 -0000 Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (1.0) Subject: Re: Intel Haswell support - Any updates? From: Michael Gmelin X-Mailer: iPhone Mail (13A344) In-Reply-To: <55FB050A.2080500@pinyon.org> Date: Thu, 17 Sep 2015 20:54:37 +0200 Cc: freebsd-current@freebsd.org Content-Transfer-Encoding: quoted-printable Message-Id: References: <09A515F2-44BA-4DF0-9792-D4C56EEB9D7C@FreeBSD.org> <114F22EF-61E3-4D75-84FB-9D6E3FBCB8F3@FreeBSD.org> <20150917131333.GN1247@egr.msu.edu> <20150917134809.GA3025@c720-r276659> <55FAD5EF.5030001@pcbsd.org> <20150917174035.GA1730@c720-r276659> <55FB050A.2080500@pinyon.org> To: "Russell L. Carter" X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 17 Sep 2015 18:54:40 -0000 > On 17 Sep 2015, at 20:23, Russell L. Carter wrote: >=20 >=20 >=20 >> On 09/17/15 10:40, Matthias Apitz wrote: >> El d=C3=83=C2=ADa Thursday, September 17, 2015 a las 11:02:07AM -0400, Kr= is Moore escribi=C3=83=C2=B3: >>=20 >>> On 09/17/2015 09:48, Matthias Apitz wrote: >>>> El d=C3=83=C2=ADa Thursday, September 17, 2015 a las 10:41:43PM +0900, L= undberg, Johannes escribi=C3=83=C2=B3: >>>>=20 >>>>> Same here. I would personally definitely buy new hardware from Intel i= f >>>>> FreeBSD worked on it (not vesa...) >>>>> ... >>>> What dow you have against vesa? I run CURRENT on some Acer C720 >>>> Chromebooks with Haswell chipset in Vesa mode. And you will not note it= . >>>> I have never ever had such a fast desktop (KDE4) before. I can live fin= e >>>> with Vesa until Haswell suport is there. >>>>=20 >>>> matthias >>>=20 >>> BTW, have you tried the xf86-video-scfb driver? It works much better >>> than vesa here. The only catch is you have to be booted UEFI with CSM >>> disabled. Using it on my X1 Carbon, gets 3k resolution properly and >>> everything. Thanks to Glen Barber for bringing that to my attention. >>=20 >> The Chromebook Acer C720 does not has UEFI; it runs Coreboot with >> SeaBIOS as payload. >>=20 >> The Xorg runs fine without any xorg.conf file, just detects the video as >> Vesa with 1366x768 resolution, the max of the 11" screen of this >> netbook. >=20 > Do you have 802.11n and hibernate working on that c720? I put linux on > mine for that reason. Although despite immense efforts I can't get > the trackpad to be detected. I tried bringing up 10.2 on it but > couldn't get it to boot. These things are just awesome. 4G memory > + i3 + 6hr battery for $240 delivered. >=20 It's all in CURRENT, see http://blog.grem.de/pages/c720.html. Brightness control is done through graphics/intel-backlight (should work on o= ther Intel GPUs as well). Auto-brightness control works as well (using the n= ew isl driver). HDMI works in VESA mode (mirrors the internal display). It suspends but won'= t resume, probably due to video, I was never able to really figure that one o= ut. Tried an early version of 915i about half a year ago with limited succes= s, will try again at/after EuroBSDCon. There are a couple of people who helped me testing and most of them seem qui= te happy with the results (no suspend/resume being the only real caveat). - Michael > Russell >=20 >> matthias > _______________________________________________ > freebsd-current@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org"= From owner-freebsd-current@freebsd.org Thu Sep 17 18:57:33 2015 Return-Path: Delivered-To: freebsd-current@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 45F749CFFD4 for ; Thu, 17 Sep 2015 18:57:33 +0000 (UTC) (envelope-from guru@unixarea.de) Received: from ms-10.1blu.de (ms-10.1blu.de [178.254.4.101]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id F2DF010B9 for ; Thu, 17 Sep 2015 18:57:32 +0000 (UTC) (envelope-from guru@unixarea.de) Received: from [82.113.121.34] (helo=localhost.unixarea.de) by ms-10.1blu.de with esmtpsa (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.76) (envelope-from ) id 1ZceN4-0006xi-SF; Thu, 17 Sep 2015 20:57:27 +0200 Received: from localhost.my.domain (c720-r276659 [127.0.0.1]) by localhost.unixarea.de (8.14.9/8.14.9) with ESMTP id t8HIvMgI002089 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Thu, 17 Sep 2015 20:57:22 +0200 (CEST) (envelope-from guru@unixarea.de) Received: (from guru@localhost) by localhost.my.domain (8.14.9/8.14.9/Submit) id t8HIvLx1002088; Thu, 17 Sep 2015 20:57:21 +0200 (CEST) (envelope-from guru@unixarea.de) X-Authentication-Warning: localhost.my.domain: guru set sender to guru@unixarea.de using -f Date: Thu, 17 Sep 2015 20:57:20 +0200 From: Matthias Apitz To: "Russell L. Carter" Cc: freebsd-current@freebsd.org Subject: Re: Intel Haswell support - Any updates? Message-ID: <20150917185720.GA2048@c720-r276659> Reply-To: Matthias Apitz Mail-Followup-To: Matthias Apitz , "Russell L. Carter" , freebsd-current@freebsd.org References: <09A515F2-44BA-4DF0-9792-D4C56EEB9D7C@FreeBSD.org> <114F22EF-61E3-4D75-84FB-9D6E3FBCB8F3@FreeBSD.org> <20150917131333.GN1247@egr.msu.edu> <20150917134809.GA3025@c720-r276659> <55FAD5EF.5030001@pcbsd.org> <20150917174035.GA1730@c720-r276659> <55FB050A.2080500@pinyon.org> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <55FB050A.2080500@pinyon.org> X-Operating-System: FreeBSD 11.0-CURRENT r269739 (i386) User-Agent: Mutt/1.5.23 (2014-03-12) X-Con-Id: 51246 X-Con-U: 0-guru X-Originating-IP: 82.113.121.34 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 17 Sep 2015 18:57:33 -0000 El dĂ­a Thursday, September 17, 2015 a las 11:23:06AM -0700, Russell L. Carter escribiĂł: > Do you have 802.11n and hibernate working on that c720? I put linux on > mine for that reason. Although despite immense efforts I can't get > the trackpad to be detected. I tried bringing up 10.2 on it but > couldn't get it to boot. You must run a ver y recent -HEAD; Wifi is fine, but most of the time I use some Ubuntu phone attached to USB tethered as router to mobile Internet (as right now). hibernate is not working, AFAIK, without Haswell support; the touchpad works too; you must learn to use it because it has not any button and so you must know where to tic to get left or right button :-) > These things are just awesome. 4G memory > + i3 + 6hr battery for $240 delivered. exactly; since I own the C720, I do not think anymore in where is the next power outlet :-) and it is fast, very fast, perhaps due to the SSD; matthias -- Matthias Apitz, ✉ guru@unixarea.de, 🌠http://www.unixarea.de/ ⎠+49-176-38902045 No! Nein! ¡No! Όχι! -- ΕυχαĎÎąĎτούμε! From owner-freebsd-current@freebsd.org Thu Sep 17 19:04:37 2015 Return-Path: Delivered-To: freebsd-current@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 E50B89CE345 for ; Thu, 17 Sep 2015 19:04:36 +0000 (UTC) (envelope-from shawn.webb@hardenedbsd.org) Received: from mail-qk0-f169.google.com (mail-qk0-f169.google.com [209.85.220.169]) (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 9C5C214D2 for ; Thu, 17 Sep 2015 19:04:36 +0000 (UTC) (envelope-from shawn.webb@hardenedbsd.org) Received: by qkdw123 with SMTP id w123so10658524qkd.0 for ; Thu, 17 Sep 2015 12:04:34 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-type:content-disposition:in-reply-to :user-agent; bh=nQDY6DZSS6FdPDwYgX3NzTtwljSQF41qTibmIbfFih8=; b=DHkGKKiWDpO5Jm7t/Fl5qLnUo4Kvy9uSjno3EBooykMp2J7ewpQtf7G8LohxwyW1xP wYYJDFObw2FPAKylEx8F56YekkRWKpTdmfeL2OAHlaEmtfPDsS4KcJw4AZP0r6NV6HMv bBAolQxtpvJWiojX96JKYyufB8N+hquttejMhxD0vZL349AFMTlcrjMwgd92FjpQZBar GoPXNFJFiY/AYvI9cMis6d1YwGEVJoXFl9Bljc+GtiN3I42rcTRVla5C70dqdjj8Lk3E 3gmwTd0b0qy9GgjkmGKu9Yu9G2FZQMWl2DMqk9lMNMkbahNQIbh51vjgY92Z29hlyY7B Fulw== X-Gm-Message-State: ALoCoQm6LxLzjd+HthOK0NsF2kyhMxlLvJu2coSkqJG+i98TOKm4AYQIaY92hZeGKFn0C9iBmBRC X-Received: by 10.55.198.9 with SMTP id b9mr1203347qkj.97.1442516674841; Thu, 17 Sep 2015 12:04:34 -0700 (PDT) Received: from mutt-hardenedbsd.hardenedbsd.dev (c-73-135-80-144.hsd1.md.comcast.net. [73.135.80.144]) by smtp.gmail.com with ESMTPSA id j193sm1864629qhc.17.2015.09.17.12.04.33 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 17 Sep 2015 12:04:34 -0700 (PDT) Date: Thu, 17 Sep 2015 15:04:32 -0400 From: Shawn Webb To: Michael Gmelin Cc: "Russell L. Carter" , freebsd-current@freebsd.org Subject: Re: Intel Haswell support - Any updates? Message-ID: <20150917190426.GE88816@mutt-hardenedbsd.hardenedbsd.dev> References: <09A515F2-44BA-4DF0-9792-D4C56EEB9D7C@FreeBSD.org> <114F22EF-61E3-4D75-84FB-9D6E3FBCB8F3@FreeBSD.org> <20150917131333.GN1247@egr.msu.edu> <20150917134809.GA3025@c720-r276659> <55FAD5EF.5030001@pcbsd.org> <20150917174035.GA1730@c720-r276659> <55FB050A.2080500@pinyon.org> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="ep0oHQY+/Gbo/zt0" Content-Disposition: inline In-Reply-To: X-Operating-System: FreeBSD mutt-hardenedbsd 11.0-CURRENT-HBSD FreeBSD 11.0-CURRENT-HBSD X-PGP-Key: http://pgp.mit.edu/pks/lookup?op=vindex&search=0x6A84658F52456EEE User-Agent: Mutt/1.5.23 (2014-03-12) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 17 Sep 2015 19:04:37 -0000 --ep0oHQY+/Gbo/zt0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Sep 17, 2015 at 08:54:37PM +0200, Michael Gmelin wrote: >=20 >=20 > > On 17 Sep 2015, at 20:23, Russell L. Carter wrote: > >=20 > >=20 > >=20 > >> On 09/17/15 10:40, Matthias Apitz wrote: > >> El d????a Thursday, September 17, 2015 a las 11:02:07AM -0400, Kris Mo= ore escribi????: > >>=20 > >>> On 09/17/2015 09:48, Matthias Apitz wrote: > >>>> El d????a Thursday, September 17, 2015 a las 10:41:43PM +0900, Lundb= erg, Johannes escribi????: > >>>>=20 > >>>>> Same here. I would personally definitely buy new hardware from Inte= l if > >>>>> FreeBSD worked on it (not vesa...) > >>>>> ... > >>>> What dow you have against vesa? I run CURRENT on some Acer C720 > >>>> Chromebooks with Haswell chipset in Vesa mode. And you will not note= it. > >>>> I have never ever had such a fast desktop (KDE4) before. I can live = fine > >>>> with Vesa until Haswell suport is there. > >>>>=20 > >>>> matthias > >>>=20 > >>> BTW, have you tried the xf86-video-scfb driver? It works much better > >>> than vesa here. The only catch is you have to be booted UEFI with CSM > >>> disabled. Using it on my X1 Carbon, gets 3k resolution properly and > >>> everything. Thanks to Glen Barber for bringing that to my attention. > >>=20 > >> The Chromebook Acer C720 does not has UEFI; it runs Coreboot with > >> SeaBIOS as payload. > >>=20 > >> The Xorg runs fine without any xorg.conf file, just detects the video = as > >> Vesa with 1366x768 resolution, the max of the 11" screen of this > >> netbook. > >=20 > > Do you have 802.11n and hibernate working on that c720? I put linux on > > mine for that reason. Although despite immense efforts I can't get > > the trackpad to be detected. I tried bringing up 10.2 on it but > > couldn't get it to boot. These things are just awesome. 4G memory > > + i3 + 6hr battery for $240 delivered. > >=20 >=20 > It's all in CURRENT, see http://blog.grem.de/pages/c720.html. >=20 > Brightness control is done through graphics/intel-backlight (should work = on other Intel GPUs as well). Auto-brightness control works as well (using = the new isl driver). HOW DID I NOT KNOW ABOUT THAT BEFORE?!? I'm happy to report that's working on my Lenovo Y50-70 laptop. Thanks for the hint. >=20 > HDMI works in VESA mode (mirrors the internal display). It suspends but w= on't resume, probably due to video, I was never able to really figure that = one out. Tried an early version of 915i about half a year ago with limited = success, will try again at/after EuroBSDCon. >=20 > There are a couple of people who helped me testing and most of them seem = quite happy with the results (no suspend/resume being the only real caveat). >=20 > - Michael >=20 > > Russell > >=20 > >> matthias > > _______________________________________________ > > freebsd-current@freebsd.org mailing list > > https://lists.freebsd.org/mailman/listinfo/freebsd-current > > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.o= rg" > _______________________________________________ > freebsd-current@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" --=20 Shawn Webb HardenedBSD GPG Key ID: 0x6A84658F52456EEE GPG Key Fingerprint: 2ABA B6BD EF6A F486 BE89 3D9E 6A84 658F 5245 6EEE --ep0oHQY+/Gbo/zt0 Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQIcBAEBCAAGBQJV+w64AAoJEGqEZY9SRW7uI78P/j9oxGRjlxatbV0SEHcjzguV /gwo8GEY77KTL7Dv7G4eBQyWUW9y+yxhgYRrX/yNDQ+zFQJwAzzOwkEgGyEmLzeo E5iNL2VWcl0Y8J1iykz0n3lc2sPtjhFrh42OaHrXkz/8uOTjxquPfZAV8NE0cQs2 IF7OPOC/3MDr+SA6sLkxANwvqN1zXfGZ23iB5JLdhgcWn7kmOrTQ/LRl4fg+RtH4 dTvKDhlFekWjQmXp6VSy2b8+D2ozGlE54kx5lr7VH6+NqsqyNo4U+J8dCldkphfO GDrDcgWicd6GhdfYCuyVOBpRcLQNbx8E7PQSDqW45LfCjkvIPQvrmukyCEcXwIX/ 7eG8QsisIIFHAUIAT7sFPCaj6IVu4R+TP2OAHoy5qjTebDxZIqqnxUNKydcAc7rH +DrwWib1+AcQzF+v3TDFMYAiU/4fnzc4TKwCWToJe9a2KE+gsRpKdc1Sdb5ChkqW 17GjPGcUAzlhHcFjQboX3fOieN9WBTo+8+FhqxQvaOFZ3YVxCKgQafauF6DSXdHR kvbncSVwBH2vAbHxGHwaS5CCOCEEQSaWCtwr8WyU6NzGRr8w2tYQJDJvoHfdDSDO 7iy9vMvPld2dTfAo4S0dD3KBes3zSHg0gHfD1OXnjUFYSWW+b7AHACFuq/eZEPZj Rk1+qLzQgXY803hJODA+ =uIo4 -----END PGP SIGNATURE----- --ep0oHQY+/Gbo/zt0-- From owner-freebsd-current@freebsd.org Thu Sep 17 19:13:40 2015 Return-Path: Delivered-To: freebsd-current@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 3AAFD9CE7E8 for ; Thu, 17 Sep 2015 19:13:40 +0000 (UTC) (envelope-from jean-sebastien.pedron@dumbbell.fr) Received: from mail.made4.biz (mail.made4.biz [IPv6:2001:41d0:2:c018::1:3]) (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 02AD51A81 for ; Thu, 17 Sep 2015 19:13:39 +0000 (UTC) (envelope-from jean-sebastien.pedron@dumbbell.fr) Received: from pat-199-212-65-22.resnet.yorku.ca ([199.212.65.22] helo=magellan.dumbbell.fr) by mail.made4.biz with esmtpsa (TLSv1.2:DHE-RSA-AES128-SHA:128) (Exim 4.85 (FreeBSD)) (envelope-from ) id 1Zcecj-000LeY-Ur for freebsd-current@freebsd.org; Thu, 17 Sep 2015 21:13:38 +0200 Subject: Re: Intel Haswell support - Any updates? To: freebsd-current@freebsd.org References: <55FA7324.5010603@icloud.com> <55FAF19F.9090701@FreeBSD.org> <87eghwlwba.fsf@gooddata.com> From: =?UTF-8?Q?Jean-S=c3=a9bastien_P=c3=a9dron?= Message-ID: <55FB10DC.10008@dumbbell.fr> Date: Thu, 17 Sep 2015 21:13:32 +0200 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:38.0) Gecko/20100101 Thunderbird/38.2.0 MIME-Version: 1.0 In-Reply-To: <87eghwlwba.fsf@gooddata.com> Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="ViuHLIMROxUvkpM44Jok7lxhMIHQe6fjq" X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 17 Sep 2015 19:13:40 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --ViuHLIMROxUvkpM44Jok7lxhMIHQe6fjq Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable On 17.09.2015 20:44, Nikola Pajkovsky wrote: > Is it part of your huge patch or where can I found commits related to > linux compat layer? The Linux compat layer and the i915 update are separate projects. The layer is here: https://github.com/dumbbell/freebsd/tree/linux-api-shim --=20 Jean-S=C3=A9bastien P=C3=A9dron --ViuHLIMROxUvkpM44Jok7lxhMIHQe6fjq 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 iQJ8BAEBCgBmBQJV+xDdXxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQ2NzA4N0ZEMUFFQUUwRTEyREJDNkE2RjAz OUU5OTc2MUE1RkQ5NENDAAoJEDnpl2Gl/ZTMixEQALoayteaY3zQMngjSfPs7uLR LS67zL5aFzJU0vOmVu/EYCZ3/QLTfBJSLr7oP4Jkknvd+kPh2f3TEF5gxMok5huK yQesA2h2xTZNx7wEbc+O0cndBtvVZfJ0PXherH5FxHgNvcNk2U+Dd1/HFFEq5hvg JSJPPsZ0LF95MBVNStBqpBTQ1yl4/aAcPx9AdCszyKga0BpG1vftdV95EsUiSSef eH8XnSakUhJeceCXSNDMjrt/AeyEhHYKaYfRxfryslPF7CAlepNVx3nOhh/kHfjl 7WUl9Ot/BxeL9vl2W/x5t/KnGlG36/vML/ox231sZGqqyIHFbQ7zw/FsYPb7sQSW /V77pfrPDY3x5r2aIETCFCoViPip/2TPcDRsKkxp2RttnH1KEvVzT2bmTmu//KSh LP+9W0Mv1JHJq2VVg7RXTtx6JCOGafs9qP6/mvXdShQXkKQFg2LWMuBGFMldqSzC cCnS2s4w5ngttp1fuE580/XmKDKvz/F9tw80XmZZ2KCWWRgGBdT7NwJl95aPb3xq 8e8AOqv2/2liqStorHD4uUxjSVaUdavLJKQI60jVM/lzPzbZKTQ2cgRM9lOlbSs3 0TSUgkIu0SPEF8Xjq/vN39hDmVt/FOVgle3TtHEU88j62/dqllYfYshKP4Q0Js5Y VH9sfg6JoPTPrG0kP1vN =CK/+ -----END PGP SIGNATURE----- --ViuHLIMROxUvkpM44Jok7lxhMIHQe6fjq-- From owner-freebsd-current@freebsd.org Thu Sep 17 19:18:59 2015 Return-Path: Delivered-To: freebsd-current@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 44B3E9CEA0F for ; Thu, 17 Sep 2015 19:18:59 +0000 (UTC) (envelope-from jean-sebastien.pedron@dumbbell.fr) Received: from mail.made4.biz (mail.made4.biz [IPv6:2001:41d0:2:c018::1:3]) (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 0C6F71C18 for ; Thu, 17 Sep 2015 19:18:59 +0000 (UTC) (envelope-from jean-sebastien.pedron@dumbbell.fr) Received: from pat-199-212-65-22.resnet.yorku.ca ([199.212.65.22] helo=magellan.dumbbell.fr) by mail.made4.biz with esmtpsa (TLSv1.2:DHE-RSA-AES128-SHA:128) (Exim 4.85 (FreeBSD)) (envelope-from ) id 1Zceht-000Lij-4w for freebsd-current@freebsd.org; Thu, 17 Sep 2015 21:18:57 +0200 Subject: Re: Intel Haswell support - Any updates? To: freebsd-current@freebsd.org References: <55FA7324.5010603@icloud.com> <55FAF19F.9090701@FreeBSD.org> <20150917172059.GB88816@mutt-hardenedbsd.hardenedbsd.dev> From: =?UTF-8?Q?Jean-S=c3=a9bastien_P=c3=a9dron?= Message-ID: <55FB121B.5080203@dumbbell.fr> Date: Thu, 17 Sep 2015 21:18:51 +0200 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:38.0) Gecko/20100101 Thunderbird/38.2.0 MIME-Version: 1.0 In-Reply-To: <20150917172059.GB88816@mutt-hardenedbsd.hardenedbsd.dev> Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="oB9ukqXBKv5UQg5PoxIoUnAVnSG9r3T9H" X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 17 Sep 2015 19:18:59 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --oB9ukqXBKv5UQg5PoxIoUnAVnSG9r3T9H Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable On 17.09.2015 19:21, Shawn Webb wrote: > I know there's a difference between "builds fine" and "runs fine". With= > it building fine, is the driver at the point where we can start > rudimentary testing? I can't help out in the development efforts, but > I'd love to help test and give bug reports. This is one way the > community at large can help. Even if it means stuffing your Inbox with > bug spam. ;) There is no need to try it right now. I didn't even try it on my own i915 hardware (it's at home). When an X server runs, I will let you know.= --=20 Jean-S=E9bastien P=E9dron --oB9ukqXBKv5UQg5PoxIoUnAVnSG9r3T9H 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 iQJ8BAEBCgBmBQJV+xIcXxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQ2NzA4N0ZEMUFFQUUwRTEyREJDNkE2RjAz OUU5OTc2MUE1RkQ5NENDAAoJEDnpl2Gl/ZTMUM4QAKQeIrLhFeBhh//UWAVJZIv9 VTuCz94loBQJkvEY2u7G1Cs36s0FmCImjoskoc7JrrQ2drjS/paJBRRvhsifuYnA ShwjaOaj97ZJMNNJg0wtYmDj5vCUtCTJGJUfRxoNQPug9Cec6LEj5kLg+tHUy8gm UW2iiSiBU6OvqMCWUU9tSwm+qGqyuwhrrL4rwtlNeOatkwqXDep8sqVF9pd8E+O2 xvbLYlxAjiJHvYNJpkI5fg7DwwJsb1lQdCGkIVuvT+YjTDW7GBs118h8s6rzD+Wv /VfAFE1xBwMTnZPvecwPKoCxuBsQQ7JpArVNomnqhsdPgn51xFSbAQSzbyyvDdZf gkWQWypgTZf4Ccau+r96nUecU9uEXsH3Ofqmrc54/RVuu18Iag8MWiIBLj61jhRI zZOz2rY31+qvxkWdqULoLYX37mqp1hEhq7SAjICucux0kf/68As44BsbRJtaSLaO nT4Rbbsow/kUxunX2waUKSE/Cbf0G2Yy+0MonwpBU05EcldNRannm9QHXyT0xzjy ShaJnwDjiuIbouM0epa8w2dvZG2ZVgRpRvQ0EgrBVDrJHnfkyhClY0P8s3MnNH7k 3I8Azm0sWSg8qL1ucAW0YkGeoDElg83vEPQhMWbX8BX9dCfvHq8qGw5Bzef21+02 jUbwmXXxUhCzWsbgbz7o =/dS6 -----END PGP SIGNATURE----- --oB9ukqXBKv5UQg5PoxIoUnAVnSG9r3T9H-- From owner-freebsd-current@freebsd.org Thu Sep 17 19:22:37 2015 Return-Path: Delivered-To: freebsd-current@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 F03A09CED40 for ; Thu, 17 Sep 2015 19:22:36 +0000 (UTC) (envelope-from ohartman@zedat.fu-berlin.de) Received: from outpost1.zedat.fu-berlin.de (outpost1.zedat.fu-berlin.de [130.133.4.66]) (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 A8CC91FEA; Thu, 17 Sep 2015 19:22:36 +0000 (UTC) (envelope-from ohartman@zedat.fu-berlin.de) Received: from inpost2.zedat.fu-berlin.de ([130.133.4.69]) by outpost.zedat.fu-berlin.de (Exim 4.85) with esmtp (envelope-from ) id <1ZcelO-000Ivf-Cg>; Thu, 17 Sep 2015 21:22:34 +0200 Received: from x5ce12e0c.dyn.telefonica.de ([92.225.46.12] helo=thor.walstatt.dynvpn.de) by inpost2.zedat.fu-berlin.de (Exim 4.85) with esmtpsa (envelope-from ) id <1ZcelO-0019uS-4H>; Thu, 17 Sep 2015 21:22:34 +0200 Date: Thu, 17 Sep 2015 21:22:28 +0200 From: "O. Hartmann" To: =?ISO-8859-1?Q?Jean-S=E9bastien_P=E9dron?= Cc: freebsd-current@freebsd.org Subject: Re: Intel Haswell support - Any updates? Message-ID: <20150917212228.75ec5471.ohartman@zedat.fu-berlin.de> In-Reply-To: <55FAF19F.9090701@FreeBSD.org> References: <55FA7324.5010603@icloud.com> <55FAF19F.9090701@FreeBSD.org> Organization: FU Berlin X-Mailer: Claws Mail 3.12.0 (GTK+ 2.24.28; amd64-portbld-freebsd11.0) MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; boundary="Sig_/JyaEppME6Z7Vn25cI6kSWB3"; protocol="application/pgp-signature" X-Originating-IP: 92.225.46.12 X-ZEDAT-Hint: A X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 17 Sep 2015 19:22:37 -0000 --Sig_/JyaEppME6Z7Vn25cI6kSWB3 Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable Am Thu, 17 Sep 2015 19:00:15 +0200 Jean-S=E9bastien P=E9dron schrieb: > Hi everyone! >=20 > I'm very sorry I didn't communicate at all on the i915 update project. >=20 > So here is a status update: since this morning, the driver builds fine. > I'm currently attending the XDC (X.Org Developers Conference) and don't > have an Intel laptop to test with me. However, Johannes Dieterich (also > attending the conference) offerred his help, so we will do that today. >=20 > Obviously, do not expect something stable in the coming couple days. > Thank you for your patience :) >=20 > To answer various questions in this thread: >=20 > Why does it take so much time to update? Once Konstantin committed his > i915 update, I was busy with non-FreeBSD activities until last July, > when I slowly started back to work on i915. My goal is to reduce the > diff with Linux as much as possible. But, as opposed to OpenBSD and > DragonFlyBSD, we do not use a Linux compatibility layer which would > dramatically ease our life. My concerns are speed and performance. Isn't any kind of layer consuming pe= rformance - sometimes worse, sometimes negligible. But anyway, HPC isn't a FreeBSD doma= in, so ... >=20 > This layer exists for the OFED/Infiniband drivers: we are almost ready > to move it to a central place, so we can use it in the near future in > the DRM subsystem. it would be nice to see a performance comparison between the "original" in = Linux and then the layered in freeBSD ... >=20 > Another problem I will fix in the near future is the method I used: I > worked on a giant patch instead of doing several incremental commits. > This is unfriendly for external contributors and hard to review. > DragonFly got that right for instance. >=20 > Now about other related tasks: > o A Mesa update will be committed Real Soon Now=99. It will unlock > GLAMOR and OpenCL support. This to hear is like a symphony to my ears ... > o Once Mesa is updated, we can update xserver to 1.17.2. xserver > 1.18 RC 1 works fine (at least for me :). It should be released > for Halloween. ... and even better ;-) > o Wayland. The problem is NOT the output side of the graphics > stack: it is the input part. We miss evdev (ported as a GSoC, > waiting for review and commit), we miss udev, we miss libinput. > This item deserves a dedicated email. One "advantage" of the Berkeley derived UNIXes is that they did not cover t= he mess Linux was in its first years - and, from my personal experiences with security rl= eated govermental stuff - still is! The spoken of facilities are "generic" or are they Linux-unique and have to= be adopted for FreeBSD? >=20 > Sorry, it's a bit short for such a large topic. It's difficult to expand > more during a conference :) >=20 --Sig_/JyaEppME6Z7Vn25cI6kSWB3 Content-Type: application/pgp-signature Content-Description: OpenPGP digital signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQEcBAEBCAAGBQJV+xL0AAoJEOgBcD7A/5N8KhEH/00ffNtLhuGM8igoZway9GKr VohTZLykwFbcgNG6f2ZIY8JFsfQp/IsvxBcDrjGku/Pg7m1mVxKveLKUjrtTd7pU LGnhwFdWlOQgzKOOBG/5kfTfwXtLBMgOTxa4HBRlGeUBdHRfhWQRnjk8BseVrFiO z1d2YHaNca65zZLi3yJx0j0KPxd2uBEQkx+W4bpA+J/TEgKZKGpiMD8hsHuTh7e0 bxoxI1IW8K1zfaG+WDhDi4y3GyuBDmrPM9TQjMPLPAxeyBBSdiAga2AJIFp8+9XF ypjMAzSybIeDsnrulB+N8V/Mn3iCaD/qQxSgLjUYhL1xrgvPa1eIhuF/jvaRlQs= =dRkG -----END PGP SIGNATURE----- --Sig_/JyaEppME6Z7Vn25cI6kSWB3-- From owner-freebsd-current@freebsd.org Thu Sep 17 19:40:09 2015 Return-Path: Delivered-To: freebsd-current@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 486FE9CF44A for ; Thu, 17 Sep 2015 19:40:09 +0000 (UTC) (envelope-from guru@unixarea.de) Received: from ms-10.1blu.de (ms-10.1blu.de [178.254.4.101]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 036AA1594 for ; Thu, 17 Sep 2015 19:40:08 +0000 (UTC) (envelope-from guru@unixarea.de) Received: from [82.113.121.34] (helo=localhost.unixarea.de) by ms-10.1blu.de with esmtpsa (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.76) (envelope-from ) id 1Zcf2L-0000Yz-7L; Thu, 17 Sep 2015 21:40:05 +0200 Received: from localhost.my.domain (c720-r276659 [127.0.0.1]) by localhost.unixarea.de (8.14.9/8.14.9) with ESMTP id t8HJe4pk002400 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Thu, 17 Sep 2015 21:40:04 +0200 (CEST) (envelope-from guru@unixarea.de) Received: (from guru@localhost) by localhost.my.domain (8.14.9/8.14.9/Submit) id t8HJe2GV002398; Thu, 17 Sep 2015 21:40:02 +0200 (CEST) (envelope-from guru@unixarea.de) X-Authentication-Warning: localhost.my.domain: guru set sender to guru@unixarea.de using -f Date: Thu, 17 Sep 2015 21:40:02 +0200 From: Matthias Apitz To: "Russell L. Carter" , freebsd-current@freebsd.org Subject: Re: Intel Haswell support - Any updates? Message-ID: <20150917194002.GA2384@c720-r276659> Reply-To: Matthias Apitz Mail-Followup-To: Matthias Apitz , "Russell L. Carter" , freebsd-current@freebsd.org References: <09A515F2-44BA-4DF0-9792-D4C56EEB9D7C@FreeBSD.org> <114F22EF-61E3-4D75-84FB-9D6E3FBCB8F3@FreeBSD.org> <20150917131333.GN1247@egr.msu.edu> <20150917134809.GA3025@c720-r276659> <55FAD5EF.5030001@pcbsd.org> <20150917174035.GA1730@c720-r276659> <55FB050A.2080500@pinyon.org> <20150917185720.GA2048@c720-r276659> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <20150917185720.GA2048@c720-r276659> X-Operating-System: FreeBSD 11.0-CURRENT r269739 (i386) User-Agent: Mutt/1.5.23 (2014-03-12) X-Con-Id: 51246 X-Con-U: 0-guru X-Originating-IP: 82.113.121.34 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 17 Sep 2015 19:40:09 -0000 El dĂ­a Thursday, September 17, 2015 a las 08:57:20PM +0200, Matthias Apitz escribiĂł: > > These things are just awesome. 4G memory > > + i3 + 6hr battery for $240 delivered. > > exactly; since I own the C720, I do not think anymore in where is the next power > outlet :-) $ uptime 9:37PM up 2:02, 4 users, load averages: 0,31 0,28 0,26 $ sysctl -a | fgrep battery.life hw.acpi.battery.life: 63 matthias -- Matthias Apitz, ✉ guru@unixarea.de, 🌠http://www.unixarea.de/ ⎠+49-176-38902045 No! Nein! ¡No! Όχι! -- ΕυχαĎÎąĎτούμε! From owner-freebsd-current@freebsd.org Thu Sep 17 19:40:30 2015 Return-Path: Delivered-To: freebsd-current@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 4A7DB9CF494 for ; Thu, 17 Sep 2015 19:40:30 +0000 (UTC) (envelope-from n.pajkovsky@gmail.com) Received: from mail-wi0-x22c.google.com (mail-wi0-x22c.google.com [IPv6:2a00:1450:400c:c05::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 009EF18A7; Thu, 17 Sep 2015 19:40:29 +0000 (UTC) (envelope-from n.pajkovsky@gmail.com) Received: by wicge5 with SMTP id ge5so4936479wic.0; Thu, 17 Sep 2015 12:40:28 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=from:to:cc:subject:references:date:in-reply-to:message-id :user-agent:mime-version:content-type:content-transfer-encoding; bh=3d6ExedGh1kxqU5uCDKVp2b+jhDXJjT+LOuts+IYWw8=; b=nEc88B0Dh7u7mcNSCL5tbJBAmyXkY6gHwTGxXCjJ5ngP72plevpPJvOasZSenIylTD 7Dvuaupqihrnk6AbQWQLPt64rK13fB6HcagutoLgu6W0onKclUujPDutVKra1qu83Qqg gOBB5nEYBXEtl6+FOJqjL+7C8LIdi28zkp5PxdQBRmQ1meT+vLRG+KdvtHsYQBg4I7i/ Cw52ccKfdX+Mak6QUQ9oojcPKCKEOWf66SSdQNPj82Zl54OYJzdgp/kE3E8JdnQDa5dV eUJSKryFjl1Vr+KV8qZWsptiJuPycktilvLpG0nDLBqEqZ4sLl899Mo5/exVu1VBWh5m 9f9A== X-Received: by 10.180.84.102 with SMTP id x6mr33934508wiy.75.1442518828520; Thu, 17 Sep 2015 12:40:28 -0700 (PDT) Received: from localhost (ip-94-112-33-45.net.upcbroadband.cz. [94.112.33.45]) by smtp.gmail.com with ESMTPSA id s16sm11665490wik.13.2015.09.17.12.40.26 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 17 Sep 2015 12:40:27 -0700 (PDT) From: Nikola Pajkovsky To: "O. Hartmann" Cc: =?utf-8?Q?Jean-S=C3=A9bastien_P=C3=A9dron?= , freebsd-current@freebsd.org Subject: Re: Intel Haswell support - Any updates? References: <55FA7324.5010603@icloud.com> <55FAF19F.9090701@FreeBSD.org> <20150917212228.75ec5471.ohartman@zedat.fu-berlin.de> Date: Thu, 17 Sep 2015 21:40:26 +0200 In-Reply-To: <20150917212228.75ec5471.ohartman@zedat.fu-berlin.de> (O. Hartmann's message of "Thu, 17 Sep 2015 21:22:28 +0200") Message-ID: <87io78ltqt.fsf@gooddata.com> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.5 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 17 Sep 2015 19:40:30 -0000 "O. Hartmann" writes: > Am Thu, 17 Sep 2015 19:00:15 +0200 > Jean-S=C3=A9bastien P=C3=A9dron schrieb: > >> Hi everyone! >>=20 >> I'm very sorry I didn't communicate at all on the i915 update project. >>=20 >> So here is a status update: since this morning, the driver builds fine. >> I'm currently attending the XDC (X.Org Developers Conference) and don't >> have an Intel laptop to test with me. However, Johannes Dieterich (also >> attending the conference) offerred his help, so we will do that today. >>=20 >> Obviously, do not expect something stable in the coming couple days. >> Thank you for your patience :) >>=20 >> To answer various questions in this thread: >>=20 >> Why does it take so much time to update? Once Konstantin committed his >> i915 update, I was busy with non-FreeBSD activities until last July, >> when I slowly started back to work on i915. My goal is to reduce the >> diff with Linux as much as possible. But, as opposed to OpenBSD and >> DragonFlyBSD, we do not use a Linux compatibility layer which would >> dramatically ease our life. > > My concerns are speed and performance. Isn't any kind of layer consuming = performance - > sometimes worse, sometimes negligible. But anyway, HPC isn't a FreeBSD do= main, so ... Look at the linux spinlock layer in ofed/include/linux/spinlock.h #define spin_lock(_l) mtx_lock(&(_l)->m) #define spin_unlock(_l) mtx_unlock(&(_l)->m) #define spin_trylock(_l) mtx_trylock(&(_l)->m) means, that using spinlock linux layer does not have any performance impact. I haven't read all ofed code, but most of that is just bunch of macros and renaming stuff to use linux code without changes and no performance impact. --=20 Nikola From owner-freebsd-current@freebsd.org Thu Sep 17 21:42:05 2015 Return-Path: Delivered-To: freebsd-current@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 1DEDF9CEE3E for ; Thu, 17 Sep 2015 21:42:05 +0000 (UTC) (envelope-from n.pajkovsky@gmail.com) Received: from mail-wi0-x22e.google.com (mail-wi0-x22e.google.com [IPv6:2a00:1450:400c:c05::22e]) (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 BD13117C1 for ; Thu, 17 Sep 2015 21:42:04 +0000 (UTC) (envelope-from n.pajkovsky@gmail.com) Received: by wicfx3 with SMTP id fx3so7982159wic.0 for ; Thu, 17 Sep 2015 14:42:03 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=from:to:cc:subject:references:date:in-reply-to:message-id :user-agent:mime-version:content-type; bh=NW+YEPRwQqTH0D0FVrYjrLEin1S0T/wt5yjDtXYCHIY=; b=zlwkaA8fAW2Y1IGI5ulz1s/qieKkpBWZgr/+QwDH5V5sgcXD5FEiHg5cyGaoapQRwZ Sl9xKvWlV1kE8pppnZo8im90bUZT/x5ZykZegCgcbuK5HNIlPcEjEsy7kKc5uQ8Mbqyl WgI18ZYi7T46lhRoTXhl1PAjC9vOqx91qO/gQ3p5uKm6rs/hEJHmZjGT3lSlCRrUtbsi 0lrcKEskfpLYVzAMu9lALoZBAGuwFNkUmuVC6eLUFY+/aj+kF3gSKAMLivtrfbwQrZPL UfGhNn7RXvgPjCDl5LafwYz1ovVg3g1uHWkJyehtIvIj8qMar4eK+QjPJdymyBa5DyXS 23eA== X-Received: by 10.180.81.199 with SMTP id c7mr11578261wiy.87.1442526123104; Thu, 17 Sep 2015 14:42:03 -0700 (PDT) Received: from localhost (ip-94-112-33-45.net.upcbroadband.cz. [94.112.33.45]) by smtp.gmail.com with ESMTPSA id fr10sm12117965wib.14.2015.09.17.14.42.01 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 17 Sep 2015 14:42:01 -0700 (PDT) From: Nikola Pajkovsky To: Stefan Wendler Cc: freebsd-current@freebsd.org Subject: Re: Intel Haswell support - Any updates? References: <55FA7324.5010603@icloud.com> <55FADB38.7000406@pcbsd.org> <87twqt2gs9.fsf@gooddata.com> <11271727.FrCOrXGY1l@hactar> Date: Thu, 17 Sep 2015 23:42:01 +0200 In-Reply-To: <11271727.FrCOrXGY1l@hactar> (Stefan Wendler's message of "Thu, 17 Sep 2015 19:28:14 +0200") Message-ID: <87a8sk205y.fsf@gooddata.com> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.5 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 17 Sep 2015 21:42:05 -0000 Stefan Wendler writes: > On Thursday 17 September 2015 17:43:02 Nikola Pajkovsky wrote: > >> Use memcontrol to set mtrr write-combine for your Vesa. Vesa is lightning >> fast on T440p on 1920x1200. > > I use a T540 and didn't get this to work yet. Can you give me the commands > you've used? I guess we have the same chips anyway. So the hex-values should > be the same? Do not run those commands in X, otherwise it hangs. $ vidcontrol -i mode | grep 1920 383 (0x17f) 0x0000000f G 1920x1080x32 D 8x16 0xa0000 64k 64k 0xe0000000 8100k $ memcontrol list | grep 0xe0000000 0xe0000000/0x20000000 BIOS uncacheable set-by-firmware active $ memcontrol set -b 0xe0000000 -l 0x20000000 -o BIOS write-combine $ startx -- Nikola From owner-freebsd-current@freebsd.org Fri Sep 18 00:00:42 2015 Return-Path: Delivered-To: freebsd-current@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 A46369CE7FD for ; Fri, 18 Sep 2015 00:00:42 +0000 (UTC) (envelope-from johannes@brilliantservice.co.jp) Received: from mail-qg0-f54.google.com (mail-qg0-f54.google.com [209.85.192.54]) (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 605E110B6 for ; Fri, 18 Sep 2015 00:00:42 +0000 (UTC) (envelope-from johannes@brilliantservice.co.jp) Received: by qgt47 with SMTP id 47so26753634qgt.2 for ; Thu, 17 Sep 2015 17:00:35 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-type; bh=522fRmYqAw/0F+5xWg9Pkjm6CFOuRNZJb63p0j+4TpA=; b=mM+YY960aL107h3cPgB4ocIoHB6mR79bXVrV1ciulqSoAGdn+gOA3hkv5wc1ECiFBx WTiBCnK0yyccU1Q54yXmTfCttgdHhwLgVvKhSC1c5PUZJWreI98SpX/ICoT1omw4tmgT R3Ert3jCJia1GoE+OQloWaems0qqzDrh31ceFHb/7bY+t/+adpy5rAHFxG4Nr5fTTCVe ez5NhKyci7J91Ij2j7YMZM9yLeo1tQGdY3ga4zVe049i664EeBWG2doyxwjv87VyHYbb qAlEa2nZlBwcsZ1cyfR/tfNZ3vyEorMcQdrfcDjVbP6QXRca+1XpTE5wohwU1RIqIVA+ Ofxw== X-Gm-Message-State: ALoCoQlSdLRNGpbtgk1qdH2TuRjSyQtCpcOSFw3oR6BQnNXGmUNoMRfPMVB0Zq0FVxI7gwjHPvMKEYc9cMc/4PXr5adr4uCllYvxtFs0le+izLyZSOp8n/TFpxyopVu0OgUCVmuXY2rj X-Received: by 10.140.20.168 with SMTP id 37mr3377574qgj.16.1442534435195; Thu, 17 Sep 2015 17:00:35 -0700 (PDT) MIME-Version: 1.0 Received: by 10.55.166.75 with HTTP; Thu, 17 Sep 2015 17:00:20 -0700 (PDT) In-Reply-To: <1442503731.1862.1.camel@me.com> References: <55FA7324.5010603@icloud.com> <09A515F2-44BA-4DF0-9792-D4C56EEB9D7C@FreeBSD.org> <114F22EF-61E3-4D75-84FB-9D6E3FBCB8F3@FreeBSD.org> <20150917131333.GN1247@egr.msu.edu> <20150917134809.GA3025@c720-r276659> <55FAD5EF.5030001@pcbsd.org> <20150917171958.046e4b6b.ohartman@zedat.fu-berlin.de> <55FADB38.7000406@pcbsd.org> <1442503731.1862.1.camel@me.com> From: "Lundberg, Johannes" Date: Fri, 18 Sep 2015 09:00:20 +0900 Message-ID: Subject: Re: Intel Haswell support - Any updates? To: Rui Paulo Cc: Kris Moore , FreeBSD Current Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.20 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 18 Sep 2015 00:00:42 -0000 Same here. Vesa won't work, I tried scfb and while it works to get graphics on the screen it is not an option when my development requires hardware acceleration so current I am running Arch Linux. Since our target platform is Intel Atom BayTrail/CherryTrail there's no other way.. -- Johannes Lundberg BRILLIANTSERVICE CO., LTD. On Fri, Sep 18, 2015 at 12:28 AM, Rui Paulo wrote: > On Thu, 2015-09-17 at 11:24 -0400, Kris Moore wrote: > > On 09/17/2015 11:19, O. Hartmann wrote: > > > Am Thu, 17 Sep 2015 11:02:07 -0400 > > > Kris Moore schrieb: > > > > > > > On 09/17/2015 09:48, Matthias Apitz wrote: > > > > > El d=C3=ADa Thursday, September 17, 2015 a las 10:41:43PM +0900, > > > > > Lundberg, Johannes > > > > > escribi=C3=B3: > > > > > > > > > > > Same here. I would personally definitely buy new hardware > > > > > > from Intel if > > > > > > FreeBSD worked on it (not vesa...) > > > > > > ... > > > > > What dow you have against vesa? I run CURRENT on some Acer C720 > > > > > Chromebooks with Haswell chipset in Vesa mode. And you will not > > > > > note it. > > > > > I have never ever had such a fast desktop (KDE4) before. I can > > > > > live fine > > > > > with Vesa until Haswell suport is there. > > > > > > > > > > matthias > > > > BTW, have you tried the xf86-video-scfb driver? It works much > > > > better > > > > than vesa here. The only catch is you have to be booted UEFI with > > > > CSM > > > > disabled. Using it on my X1 Carbon, gets 3k resolution properly > > > > and > > > > everything. Thanks to Glen Barber for bringing that to my > > > > attention. > > > > > > > Running that specific driver on several Lenovo HD4600 driven models > > > gives me headaches > > > and more. This software-framebuffer works - yes, on whatever > > > resolution you might wish, > > > but it consumes CPU time. That said, I recall that the display was > > > jumpy, slow and > > > unresponsive when used under heavy load - not even 3k resolution, > > > but with a moderate > > > lowend of 1980x1080. > > > > Interesting, that's been the opposite of my experience here. Vesa was > > much slower / using more CPU time and didn't give me the native > > resolution. Switching to scfb made the laptop "usable" for me, at > > least > > until we get a proper Intel driver that does Broadwell. > > I, too, used scfb for 4 months, but I gave up and installed Linux. > These are the things that don't work with scfb: > > 1) brightness control (almost at max when booting) > 2) external monitor > 3) hardware acceleration. > > scfb is a working solution in specific cases, but a laptop isn't one of > them. > > -- > Rui Paulo > > _______________________________________________ > freebsd-current@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org= " > --=20 =3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D= -=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D- =E7=A7=98=E5=AF=86=E4=BF=9D=E6=8C=81=E3=81=AB=E3=81=A4=E3=81=84=E3=81=A6=EF= =BC=9A=E3=81=93=E3=81=AE=E9=9B=BB=E5=AD=90=E3=83=A1=E3=83=BC=E3=83=AB=E3=81= =AF=E3=80=81=E5=90=8D=E5=AE=9B=E4=BA=BA=E3=81=AB=E9=80=81=E4=BF=A1=E3=81=97= =E3=81=9F=E3=82=82=E3=81=AE=E3=81=A7=E3=81=82=E3=82=8A=E3=80=81=E7=A7=98=E5= =8C=BF=E7=89=B9=E6=A8=A9=E3=81=AE=E5=AF=BE=E8=B1=A1=E3=81=A8=E3=81=AA=E3=82= =8B=E6=83=85=E5=A0=B1=E3=82=92=E5=90=AB=E3=82=93=E3=81=A7=E3=81=84=E3=81=BE= =E3=81=99=E3=80=82 =E3=82=82=E3=81=97=E3=80=81=E5=90=8D=E5=AE=9B=E4=BA=BA=E4=BB=A5=E5=A4=96=E3= =81=AE=E6=96=B9=E3=81=8C=E5=8F=97=E4=BF=A1=E3=81=95=E3=82=8C=E3=81=9F=E5=A0= =B4=E5=90=88=E3=80=81=E3=81=93=E3=81=AE=E3=83=A1=E3=83=BC=E3=83=AB=E3=81=AE= =E7=A0=B4=E6=A3=84=E3=80=81=E3=81=8A=E3=82=88=E3=81=B3=E3=81=93=E3=81=AE=E3= =83=A1=E3=83=BC=E3=83=AB=E3=81=AB=E9=96=A2=E3=81=99=E3=82=8B=E4=B8=80=E5=88= =87=E3=81=AE=E9=96=8B=E7=A4=BA=E3=80=81 =E8=A4=87=E5=86=99=E3=80=81=E9=85=8D=E5=B8=83=E3=80=81=E3=81=9D=E3=81=AE=E4= =BB=96=E3=81=AE=E5=88=A9=E7=94=A8=E3=80=81=E3=81=BE=E3=81=9F=E3=81=AF=E8=A8= =98=E8=BC=89=E5=86=85=E5=AE=B9=E3=81=AB=E5=9F=BA=E3=81=A5=E3=81=8F=E3=81=84= =E3=81=8B=E3=81=AA=E3=82=8B=E8=A1=8C=E5=8B=95=E3=82=82=E3=81=95=E3=82=8C=E3= =81=AA=E3=81=84=E3=82=88=E3=81=86=E3=81=8A=E9=A1=98=E3=81=84=E7=94=B3=E3=81= =97=E4=B8=8A=E3=81=92=E3=81=BE=E3=81=99=E3=80=82 --- 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. From owner-freebsd-current@freebsd.org Fri Sep 18 00:53:30 2015 Return-Path: Delivered-To: freebsd-current@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 3A6119CE1FE for ; Fri, 18 Sep 2015 00:53:30 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-io0-x22b.google.com (mail-io0-x22b.google.com [IPv6:2607:f8b0:4001:c06::22b]) (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 F3FD51806 for ; Fri, 18 Sep 2015 00:53:29 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: by ioiz6 with SMTP id z6so40812146ioi.2 for ; Thu, 17 Sep 2015 17:53:28 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=W+xnylbucM0R3ue0hZK8gz7EXWICjPHpUfrnKLv8Yls=; b=lsEQ86h4NFkJFsMAewwgpXwqPAHuyi3Ut+0Hf9diRw0LO58U5Gt3gUkzegCBK9AXUz VxvbNYlpETAr1LbQO8SPfOW8mPgjTJ/ONluQn3t3oZyd1kZNbE4sHBdV+Zd1RO22QxIU YAvHIxZL92kxEITagiAsKBR3Ez4BlM8DMP7Lz7G1xhIfiCaFWZ3agYZH953ThmDYo0tl P2hzuBCt8sma1jQExkesFIOCnUu5u680NOrlsZ8MLA51axvOUC+ydyxpmKOA1FAdWFE3 UU9VETbFhW5Z9pVxCoV0942nAiWluvPqmBi3uXV3bHVtpwAQVRGYAYqTYQ9fUVHpKOXL JyXA== MIME-Version: 1.0 X-Received: by 10.107.35.78 with SMTP id j75mr10574662ioj.123.1442537608763; Thu, 17 Sep 2015 17:53:28 -0700 (PDT) Received: by 10.36.28.208 with HTTP; Thu, 17 Sep 2015 17:53:28 -0700 (PDT) In-Reply-To: References: <55FA7324.5010603@icloud.com> <09A515F2-44BA-4DF0-9792-D4C56EEB9D7C@FreeBSD.org> <114F22EF-61E3-4D75-84FB-9D6E3FBCB8F3@FreeBSD.org> <20150917131333.GN1247@egr.msu.edu> <20150917134809.GA3025@c720-r276659> <55FAD5EF.5030001@pcbsd.org> <20150917171958.046e4b6b.ohartman@zedat.fu-berlin.de> <55FADB38.7000406@pcbsd.org> <1442503731.1862.1.camel@me.com> Date: Thu, 17 Sep 2015 17:53:28 -0700 Message-ID: Subject: Re: Intel Haswell support - Any updates? From: Adrian Chadd To: "Lundberg, Johannes" Cc: Rui Paulo , Kris Moore , FreeBSD Current Content-Type: text/plain; charset=UTF-8 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 18 Sep 2015 00:53:30 -0000 Have you had a one-on-one with anyone at the foundation and expressed your desires/concerns? You're a vendor after all... -a From owner-freebsd-current@freebsd.org Fri Sep 18 00:58:54 2015 Return-Path: Delivered-To: freebsd-current@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 637FC9CE44A for ; Fri, 18 Sep 2015 00:58:54 +0000 (UTC) (envelope-from johannes@brilliantservice.co.jp) Received: from mail-qg0-f49.google.com (mail-qg0-f49.google.com [209.85.192.49]) (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 1EFFD1B6F for ; Fri, 18 Sep 2015 00:58:53 +0000 (UTC) (envelope-from johannes@brilliantservice.co.jp) Received: by qgx61 with SMTP id 61so27613700qgx.3 for ; Thu, 17 Sep 2015 17:58:53 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-type; bh=Z4McuzyEBlEM34PDUProvVGaYtal349rqPufv1Gr8X0=; b=kMv63wa7JfNZU0H4EHwF/UlG1qjQEZU9EjeNnyL+8v40dqxB5id41JUhVP51hS/PUg r6HOdHcu+ynq6KSuS6iRYxXKfZzfqj5XaZR2yyOQ49c46S0EL5NpQBjlQCjoEIfG8KBm LmVwFfxs+P+m3QAsUGHZxMhJECI4bBFg3/Q0I9oQ3Hciw3GApsirAUjpG83aSvo054f+ l1hP3uoev4VTDvndSmYTMKW3xovVL22O1viY/W+RMt+pG7lZ6ygnh4psEAOnthQU+jaV /hQAJxhKJ4LiNnvExWcIhOXmKoAgGjkv722hYYNbLSrTr1K0WhDEro9GQvZcK/5rez84 GNJw== X-Gm-Message-State: ALoCoQk8Ui/ODKLy96ipqL2nSSawzYiZ6sknLw5h1o9tP3G1JWEkpe5ML6AJmGt+AiPvH9G7YfRQGkRrohWe2q+hGVujxccwWzu0ocK3NZfYnQJsU4o3CzdC14Hpi15J56uT/wCRQ8il X-Received: by 10.140.131.135 with SMTP id 129mr3754025qhd.31.1442537932910; Thu, 17 Sep 2015 17:58:52 -0700 (PDT) MIME-Version: 1.0 Received: by 10.55.166.75 with HTTP; Thu, 17 Sep 2015 17:58:38 -0700 (PDT) In-Reply-To: References: <55FA7324.5010603@icloud.com> <09A515F2-44BA-4DF0-9792-D4C56EEB9D7C@FreeBSD.org> <114F22EF-61E3-4D75-84FB-9D6E3FBCB8F3@FreeBSD.org> <20150917131333.GN1247@egr.msu.edu> <20150917134809.GA3025@c720-r276659> <55FAD5EF.5030001@pcbsd.org> <20150917171958.046e4b6b.ohartman@zedat.fu-berlin.de> <55FADB38.7000406@pcbsd.org> <1442503731.1862.1.camel@me.com> From: "Lundberg, Johannes" Date: Fri, 18 Sep 2015 09:58:38 +0900 Message-ID: Subject: Re: Intel Haswell support - Any updates? To: Adrian Chadd Cc: Rui Paulo , Kris Moore , FreeBSD Current Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: base64 X-Content-Filtered-By: Mailman/MimeDel 2.1.20 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 18 Sep 2015 00:58:54 -0000 Tm8geWV0IGJ1dCBJIHdvdWxkIGxpa2UgdG8gaGF2ZSBhIG1lZXRpbmcgaWYgcG9zc2libGUuIEFy ZSB0aGVyZSBhbnkNCmZvdW5kYXRpb24gZm9sa3MgaW4gdGhlIGJheSBhcmVhPw0KU3RhcnRpbmcg ZnJvbSBuZXh0IG1vbnRoIEkgd2lsbCBiZSBiYXNlZCBpbiBvdXIgTG9zIEFsdG9zIG9mZmljZSBm b3IgdGhlDQp0aW1lIGJlaW5nLg0KDQoNCi0tDQpKb2hhbm5lcyBMdW5kYmVyZw0KQlJJTExJQU5U U0VSVklDRSBDTy4sIExURC4NCg0KT24gRnJpLCBTZXAgMTgsIDIwMTUgYXQgOTo1MyBBTSwgQWRy aWFuIENoYWRkIDxhZHJpYW4uY2hhZGRAZ21haWwuY29tPg0Kd3JvdGU6DQoNCj4gSGF2ZSB5b3Ug aGFkIGEgb25lLW9uLW9uZSB3aXRoIGFueW9uZSBhdCB0aGUgZm91bmRhdGlvbiBhbmQgZXhwcmVz c2VkDQo+IHlvdXIgZGVzaXJlcy9jb25jZXJucz8gWW91J3JlIGEgdmVuZG9yIGFmdGVyIGFsbC4u Lg0KPg0KPiAtYQ0KPg0KCi0tIAo9LT0tPS09LT0tPS09LT0tPS09LT0tPS09LT0tPS09LT0tPS09 LT0tPS09LT0tPS09LT0tPS0K56eY5a+G5L+d5oyB44Gr44Gk44GE44Gm77ya44GT44Gu6Zu75a2Q 44Oh44O844Or44Gv44CB5ZCN5a6b5Lq644Gr6YCB5L+h44GX44Gf44KC44Gu44Gn44GC44KK44CB 56eY5Yy/54m55qip44Gu5a++6LGh44Go44Gq44KL5oOF5aCx44KS5ZCr44KT44Gn44GE44G+44GZ 44CCCuOCguOBl+OAgeWQjeWum+S6uuS7peWkluOBruaWueOBjOWPl+S/oeOBleOCjOOBn+WgtOWQ iOOAgeOBk+OBruODoeODvOODq+OBruegtOajhOOAgeOBiuOCiOOBs+OBk+OBruODoeODvOODq+OB q+mWouOBmeOCi+S4gOWIh+OBrumWi+ekuuOAgQropIflhpnjgIHphY3luIPjgIHjgZ3jga7ku5bj ga7liKnnlKjjgIHjgb7jgZ/jga/oqJjovInlhoXlrrnjgavln7rjgaXjgY/jgYTjgYvjgarjgovo oYzli5XjgoLjgZXjgozjgarjgYTjgojjgYbjgYrpoZjjgYTnlLPjgZfkuIrjgZLjgb7jgZnjgIIK LS0tCkNPTkZJREVOVElBTElUWSBOT1RFOiBUaGUgaW5mb3JtYXRpb24gaW4gdGhpcyBlbWFpbCBp cyBjb25maWRlbnRpYWwKYW5kIGludGVuZGVkIHNvbGVseSBmb3IgdGhlIGFkZHJlc3NlZS4KRGlz Y2xvc3VyZSwgY29weWluZywgZGlzdHJpYnV0aW9uIG9yIGFueSBvdGhlciBhY3Rpb24gb2YgdXNl IG9mIHRoaXMKZW1haWwgYnkgcGVyc29uIG90aGVyIHRoYW4gaW50ZW5kZWQgcmVjaXBpZW50LCBp cyBwcm9oaWJpdGVkLgpJZiB5b3UgYXJlIG5vdCB0aGUgaW50ZW5kZWQgcmVjaXBpZW50IGFuZCBo YXZlIHJlY2VpdmVkIHRoaXMgZW1haWwgaW4KZXJyb3IsIHBsZWFzZSBkZXN0cm95IHRoZSBvcmln aW5hbCBtZXNzYWdlLgo= From owner-freebsd-current@freebsd.org Fri Sep 18 05:09:43 2015 Return-Path: Delivered-To: freebsd-current@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 135EB9CDB59 for ; Fri, 18 Sep 2015 05:09:43 +0000 (UTC) (envelope-from jenkins-admin@FreeBSD.org) Received: from jenkins-9.freebsd.org (jenkins-9.freebsd.org [8.8.178.209]) by mx1.freebsd.org (Postfix) with ESMTP id 0409D1D3E for ; Fri, 18 Sep 2015 05:09:43 +0000 (UTC) (envelope-from jenkins-admin@FreeBSD.org) Received: from jenkins-9.freebsd.org (localhost [127.0.0.1]) by jenkins-9.freebsd.org (Postfix) with ESMTP id 9A51E176 for ; Fri, 18 Sep 2015 05:09:39 +0000 (UTC) Date: Fri, 18 Sep 2015 05:09:34 +0000 (GMT) From: jenkins-admin@FreeBSD.org To: freebsd-current@freebsd.org Message-ID: <966810206.25.1442552974948.JavaMail.jenkins@jenkins-9.freebsd.org> Subject: Jenkins build is back to normal : Build-UFS-image #2364 MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Instance-Identity: MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAkKKb2VAfYQKfu1t7qk4nR5qzUBEI+UqT4BPec4qHVhqUy0FFdq50sMH+3y9bCDNOufctov6VqTNffZ3YXArnZK95YF0OX97fh+E9txYOUX1adc+TikcKjuYpHmL5dE62eaZTI+4A5jnRonskQ1PaoIFz0Kbu4mWzkFsmdiXTraGzomXq4cHUCATA2+K4eDYgjXEQI30z3GOMmmZ4t/+6QGk1cMb/BqMWHbn80AsRCb4tU7Hpd72XLDpsuO7YRP1Q0CjmNAuBOTj+sFiiOe6U9HpqOlQN+iFUvBdZo/ybuy5Kh71cAaYQNL68cYdZJ6binH/DkG3KY/fS7DFYAeuwjwIDAQAB X-Jenkins-Job: Build-UFS-image X-Jenkins-Result: SUCCESS X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 18 Sep 2015 05:09:43 -0000 See From owner-freebsd-current@freebsd.org Fri Sep 18 05:34:56 2015 Return-Path: Delivered-To: freebsd-current@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 2CAD99CEAB2 for ; Fri, 18 Sep 2015 05:34:56 +0000 (UTC) (envelope-from guru@unixarea.de) Received: from ms-10.1blu.de (ms-10.1blu.de [178.254.4.101]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id E1A2710F3 for ; Fri, 18 Sep 2015 05:34:55 +0000 (UTC) (envelope-from guru@unixarea.de) Received: from [89.204.135.152] (helo=localhost.unixarea.de) by ms-10.1blu.de with esmtpsa (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.76) (envelope-from ) id 1ZcoJu-0001OY-Sy; Fri, 18 Sep 2015 07:34:51 +0200 Received: from localhost.my.domain (c720-r276659 [127.0.0.1]) by localhost.unixarea.de (8.14.9/8.14.9) with ESMTP id t8I5Yl84001940 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Fri, 18 Sep 2015 07:34:47 +0200 (CEST) (envelope-from guru@unixarea.de) Received: (from guru@localhost) by localhost.my.domain (8.14.9/8.14.9/Submit) id t8I5Yj6o001939; Fri, 18 Sep 2015 07:34:45 +0200 (CEST) (envelope-from guru@unixarea.de) X-Authentication-Warning: localhost.my.domain: guru set sender to guru@unixarea.de using -f Date: Fri, 18 Sep 2015 07:34:45 +0200 From: Matthias Apitz To: Nikola Pajkovsky Cc: Stefan Wendler , freebsd-current@freebsd.org Subject: Re: Intel Haswell support - Any updates? Message-ID: <20150918053445.GA1929@c720-r276659> Reply-To: Matthias Apitz Mail-Followup-To: Matthias Apitz , Nikola Pajkovsky , Stefan Wendler , freebsd-current@freebsd.org References: <55FA7324.5010603@icloud.com> <55FADB38.7000406@pcbsd.org> <87twqt2gs9.fsf@gooddata.com> <11271727.FrCOrXGY1l@hactar> <87a8sk205y.fsf@gooddata.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <87a8sk205y.fsf@gooddata.com> X-Operating-System: FreeBSD 11.0-CURRENT r269739 (i386) User-Agent: Mutt/1.5.23 (2014-03-12) X-Con-Id: 51246 X-Con-U: 0-guru X-Originating-IP: 89.204.135.152 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 18 Sep 2015 05:34:56 -0000 El dĂ­a Thursday, September 17, 2015 a las 11:42:01PM +0200, Nikola Pajkovsky escribiĂł: > Do not run those commands in X, otherwise it hangs. > > $ vidcontrol -i mode | grep 1920 > 383 (0x17f) 0x0000000f G 1920x1080x32 D 8x16 0xa0000 64k 64k 0xe0000000 8100k On my C720 the above cmd does not give any usefull information: mode# flags type size font window linear buffer ------------------------------------------------------------------------------ 0 (0x000) 0x00000000 T 0x0 0x402653478 0x280996d6 131362k 0k 0x00000000 0k 1 (0x001) 0x00000000 T 0x0 0x402653478 0x280996d6 131362k 0k 0x00000000 0k 2 (0x002) 0x00000000 T 0x0 0x402653478 0x280996d6 131362k 0k 0x00000000 0k 3 (0x003) 0x00000000 T 0x0 0x402653478 0x280996d6 131362k 0k 0x00000000 0k 4 (0x004) 0x00000000 T 0x0 0x402653478 0x280996d6 131362k 0k 0x00000000 0k 5 ... 507 (0x1fb) 0x00000000 T 0x0 0x402653478 0x280996d6 131362k 0k 0x00000000 0k 508 (0x1fc) 0x00000000 T 0x0 0x402653478 0x280996d6 131362k 0k 0x00000000 0k 509 (0x1fd) 0x00000000 T 0x0 0x402653478 0x280996d6 131362k 0k 0x00000000 0k 510 (0x1fe) 0x00000000 T 0x0 0x402653478 0x280996d6 131362k 0k 0x00000000 0k 511 (0x1ff) 0x00000000 T 0x0 0x402653478 0x280996d6 131362k 0k 0x00000000 0k Thanks matthias -- Matthias Apitz, ✉ guru@unixarea.de, 🌠http://www.unixarea.de/ ⎠+49-176-38902045 No! Nein! ¡No! Όχι! -- ΕυχαĎÎąĎτούμε! From owner-freebsd-current@freebsd.org Fri Sep 18 06:30:59 2015 Return-Path: Delivered-To: freebsd-current@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 D801A9CD34A for ; Fri, 18 Sep 2015 06:30:59 +0000 (UTC) (envelope-from FreeBSD@shaneware.biz) Received: from ipmail05.adl6.internode.on.net (ipmail05.adl6.internode.on.net [150.101.137.143]) by mx1.freebsd.org (Postfix) with ESMTP id 49FAA18F4; Fri, 18 Sep 2015 06:30:58 +0000 (UTC) (envelope-from FreeBSD@shaneware.biz) Received: from ppp118-210-169-30.lns20.adl6.internode.on.net (HELO leader.local) ([118.210.169.30]) by ipmail05.adl6.internode.on.net with ESMTP; 18 Sep 2015 16:00:50 +0930 Subject: Re: Intel Haswell support - Any updates? To: Shawn Webb , Jean-S??bastien P??dron References: <55FA7324.5010603@icloud.com> <55FAF19F.9090701@FreeBSD.org> <20150917172059.GB88816@mutt-hardenedbsd.hardenedbsd.dev> Cc: freebsd-current@freebsd.org From: Shane Ambler Message-ID: <55FBAF91.7030002@ShaneWare.Biz> Date: Fri, 18 Sep 2015 16:00:41 +0930 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:38.0) Gecko/20100101 Thunderbird/38.2.0 MIME-Version: 1.0 In-Reply-To: <20150917172059.GB88816@mutt-hardenedbsd.hardenedbsd.dev> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 18 Sep 2015 06:30:59 -0000 On 18/09/2015 02:51, Shawn Webb wrote: > On Thu, Sep 17, 2015 at 07:00:15PM +0200, Jean-S??bastien P??dron wrote: >> Hi everyone! >> >> I'm very sorry I didn't communicate at all on the i915 update project. >> >> So here is a status update: since this morning, the driver builds fine. >> I'm currently attending the XDC (X.Org Developers Conference) and don't >> have an Intel laptop to test with me. However, Johannes Dieterich (also >> attending the conference) offerred his help, so we will do that today. >> >> Obviously, do not expect something stable in the coming couple days. >> Thank you for your patience :) > > First of all, I want to say (nay, YELL!) "THANK YOU!" You're doing a +1 >> Now about other related tasks: >> o A Mesa update will be committed Real Soon Now?. It will unlock >> GLAMOR and OpenCL support. > > OpenCL on FreeBSD would be stupendously amazing! A little off-topic but has anyone tried to get nvidia to return libcuda to our drivers? While it was there a few years ago it was removed yet again. From what I could tell we had to use the linux sdk to compile cuda kernels which probably hindered freebsd using it so the sdk may need porting to freebsd as well. -- FreeBSD - the place to B...Software Developing Shane Ambler From owner-freebsd-current@freebsd.org Fri Sep 18 06:53:14 2015 Return-Path: Delivered-To: freebsd-current@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 449879CDE63 for ; Fri, 18 Sep 2015 06:53:14 +0000 (UTC) (envelope-from ohartman@zedat.fu-berlin.de) Received: from outpost1.zedat.fu-berlin.de (outpost1.zedat.fu-berlin.de [130.133.4.66]) (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 F3F9611FB; Fri, 18 Sep 2015 06:53:13 +0000 (UTC) (envelope-from ohartman@zedat.fu-berlin.de) Received: from inpost2.zedat.fu-berlin.de ([130.133.4.69]) by outpost.zedat.fu-berlin.de (Exim 4.85) with esmtp (envelope-from ) id <1ZcpXi-002WAg-Kv>; Fri, 18 Sep 2015 08:53:10 +0200 Received: from p578a69f9.dip0.t-ipconnect.de ([87.138.105.249] helo=freyja.zeit4.iv.bundesimmobilien.de) by inpost2.zedat.fu-berlin.de (Exim 4.85) with esmtpsa (envelope-from ) id <1ZcpXi-001tv1-DD>; Fri, 18 Sep 2015 08:53:10 +0200 Date: Fri, 18 Sep 2015 08:53:05 +0200 From: "O. Hartmann" To: Shane Ambler Cc: Shawn Webb , Jean-S??bastien P??dron , freebsd-current@freebsd.org Subject: Re: Intel Haswell support - Any updates? Message-ID: <20150918085305.7ba727d7@freyja.zeit4.iv.bundesimmobilien.de> In-Reply-To: <55FBAF91.7030002@ShaneWare.Biz> References: <55FA7324.5010603@icloud.com> <55FAF19F.9090701@FreeBSD.org> <20150917172059.GB88816@mutt-hardenedbsd.hardenedbsd.dev> <55FBAF91.7030002@ShaneWare.Biz> Organization: FU Berlin X-Mailer: Claws Mail 3.12.0 (GTK+ 2.24.28; amd64-portbld-freebsd11.0) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Originating-IP: 87.138.105.249 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 18 Sep 2015 06:53:14 -0000 On Fri, 18 Sep 2015 16:00:41 +0930 Shane Ambler wrote: > On 18/09/2015 02:51, Shawn Webb wrote: > > On Thu, Sep 17, 2015 at 07:00:15PM +0200, Jean-S??bastien P??dron wrote: > >> Hi everyone! > >> > >> I'm very sorry I didn't communicate at all on the i915 update project. > >> > >> So here is a status update: since this morning, the driver builds fine. > >> I'm currently attending the XDC (X.Org Developers Conference) and don't > >> have an Intel laptop to test with me. However, Johannes Dieterich (also > >> attending the conference) offerred his help, so we will do that today. > >> > >> Obviously, do not expect something stable in the coming couple days. > >> Thank you for your patience :) > > > > First of all, I want to say (nay, YELL!) "THANK YOU!" You're doing a > > +1 > > >> Now about other related tasks: > >> o A Mesa update will be committed Real Soon Now?. It will unlock > >> GLAMOR and OpenCL support. > > > > OpenCL on FreeBSD would be stupendously amazing! > > A little off-topic but has anyone tried to get nvidia to return libcuda > to our drivers? While it was there a few years ago it was removed yet > again. From what I could tell we had to use the linux sdk to compile > cuda kernels which probably hindered freebsd using it so the sdk may > need porting to freebsd as well. > > I'm not sure I'm talking about the same subject, but a couple of years ago, when we moved software for satellite imagery processing towards GPUs and had CUDA as an option in mind, I looked at FreeBSD support. nVidia was per se unwilling to offer FreeBSD-native CUDA libraries and support. the only way to get CUDA to wark was to use the Linuxulator and being stuck with 32bit libraries. 2009 and 2010, when i tried hard looking for a solution, the mentioned workaround wasn't working properly anymore on FBSD 9, 10-CURRENT. It is a long time since I put some thoughts in that direction since we switched over to OpenCL as a more free, flexible platform (CPU and GPU usage, even alternatively). But of speaking about history then, we had to retire the FreeBSD server project in favour for a CentOS and Suse cluster due to the lack of driver support for OpenCL on FreeBSD. The decision was made quickly because funding was quick and decisions depended on most recent hardware (TESLA GPUs that time, some customer nVidia GTX570 and GTX580 cards which had a limited livetime of the GPGPU processing pipeline due to the driver, but sufficient for some minor calibration jobs ...). From owner-freebsd-current@freebsd.org Fri Sep 18 07:20:30 2015 Return-Path: Delivered-To: freebsd-current@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 295BA9CEC13 for ; Fri, 18 Sep 2015 07:20:30 +0000 (UTC) (envelope-from oliver.pinter@hardenedbsd.org) Received: from mail-wi0-f172.google.com (mail-wi0-f172.google.com [209.85.212.172]) (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 BAE8A1E96 for ; Fri, 18 Sep 2015 07:20:29 +0000 (UTC) (envelope-from oliver.pinter@hardenedbsd.org) Received: by wicge5 with SMTP id ge5so20030241wic.0 for ; Fri, 18 Sep 2015 00:20:21 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=w1xqLCU6SI54yDs9VB6RHSRcocDmvQ/iQZxQbzhUi4s=; b=IYkoGQTxw3cy+gIdgeF9Ida4JWkT7xVfvpTK5qWLViqpl7ku/4NnzuqiJRQKKs1TqK lI72eeBCUoSiOvk78OWPE7kcGYOO3DFP8E4HUDpA2MZTrIH+WotoHUN/2st2z8Konq+r AY933u40A5BXhKPUomsFfMylHU8HYAlxyj0RYSWOfwhWK6H7QKQFt/uv3I/u6BE89+54 iktHVfaMr1rp9Byr3aSRuVSJXpZmbUIfe7qJWyLmCDTkiF0w/i0hiN5A3A4CRhvdrK/z bL+31ZI1CiTqZK6aAPNWI13mm3Hi7K37NL76z8FAaAu/JHrFd+wGbQrfBO40QP3WNIz/ pORw== X-Gm-Message-State: ALoCoQlQFasytZ5DL1q8bZZ9LFNqNiY044GCdZFhWG67udePJ5Fw8D9JYmcf5SQbNZLuLzYUQCWK MIME-Version: 1.0 X-Received: by 10.194.114.37 with SMTP id jd5mr5085304wjb.34.1442560821828; Fri, 18 Sep 2015 00:20:21 -0700 (PDT) Received: by 10.194.240.226 with HTTP; Fri, 18 Sep 2015 00:20:21 -0700 (PDT) In-Reply-To: References: <09A515F2-44BA-4DF0-9792-D4C56EEB9D7C@FreeBSD.org> <114F22EF-61E3-4D75-84FB-9D6E3FBCB8F3@FreeBSD.org> <20150917131333.GN1247@egr.msu.edu> <20150917134809.GA3025@c720-r276659> <55FAD5EF.5030001@pcbsd.org> <20150917174035.GA1730@c720-r276659> <55FB050A.2080500@pinyon.org> Date: Fri, 18 Sep 2015 09:20:21 +0200 Message-ID: Subject: Re: Intel Haswell support - Any updates? From: Oliver Pinter To: Michael Gmelin Cc: "Russell L. Carter" , freebsd-current@freebsd.org Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 18 Sep 2015 07:20:30 -0000 On 9/17/15, Michael Gmelin wrote: > > >> On 17 Sep 2015, at 20:23, Russell L. Carter wrote: >> >> >> >>> On 09/17/15 10:40, Matthias Apitz wrote: >>> El d=C3=83=C2=ADa Thursday, September 17, 2015 a las 11:02:07AM -0400, = Kris Moore >>> escribi=C3=83=C2=B3: >>> >>>> On 09/17/2015 09:48, Matthias Apitz wrote: >>>>> El d=C3=83=C2=ADa Thursday, September 17, 2015 a las 10:41:43PM +0900= , Lundberg, >>>>> Johannes escribi=C3=83=C2=B3: >>>>> >>>>>> Same here. I would personally definitely buy new hardware from Intel >>>>>> if >>>>>> FreeBSD worked on it (not vesa...) >>>>>> ... >>>>> What dow you have against vesa? I run CURRENT on some Acer C720 >>>>> Chromebooks with Haswell chipset in Vesa mode. And you will not note >>>>> it. >>>>> I have never ever had such a fast desktop (KDE4) before. I can live >>>>> fine >>>>> with Vesa until Haswell suport is there. >>>>> >>>>> matthias >>>> >>>> BTW, have you tried the xf86-video-scfb driver? It works much better >>>> than vesa here. The only catch is you have to be booted UEFI with CSM >>>> disabled. Using it on my X1 Carbon, gets 3k resolution properly and >>>> everything. Thanks to Glen Barber for bringing that to my attention. >>> >>> The Chromebook Acer C720 does not has UEFI; it runs Coreboot with >>> SeaBIOS as payload. >>> >>> The Xorg runs fine without any xorg.conf file, just detects the video a= s >>> Vesa with 1366x768 resolution, the max of the 11" screen of this >>> netbook. >> >> Do you have 802.11n and hibernate working on that c720? I put linux on >> mine for that reason. Although despite immense efforts I can't get >> the trackpad to be detected. I tried bringing up 10.2 on it but >> couldn't get it to boot. These things are just awesome. 4G memory >> + i3 + 6hr battery for $240 delivered. >> > > It's all in CURRENT, see http://blog.grem.de/pages/c720.html. > > Brightness control is done through graphics/intel-backlight (should work = on > other Intel GPUs as well). Auto-brightness control works as well (using t= he > new isl driver). Wow! Thank you very much for this info! > > HDMI works in VESA mode (mirrors the internal display). It suspends but > won't resume, probably due to video, I was never able to really figure th= at > one out. Tried an early version of 915i about half a year ago with limite= d > success, will try again at/after EuroBSDCon. > > There are a couple of people who helped me testing and most of them seem > quite happy with the results (no suspend/resume being the only real cavea= t). > > - Michael > >> Russell >> >>> matthias >> _______________________________________________ >> freebsd-current@freebsd.org mailing list >> https://lists.freebsd.org/mailman/listinfo/freebsd-current >> To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.or= g" > _______________________________________________ > freebsd-current@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org= " From owner-freebsd-current@freebsd.org Fri Sep 18 09:03:17 2015 Return-Path: Delivered-To: freebsd-current@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 37B399CF257 for ; Fri, 18 Sep 2015 09:03:17 +0000 (UTC) (envelope-from grembo@freebsd.org) Received: from mail.grem.de (outcast.grem.de [213.239.217.27]) by mx1.freebsd.org (Postfix) with SMTP id 9F33A1C3E for ; Fri, 18 Sep 2015 09:03:16 +0000 (UTC) (envelope-from grembo@freebsd.org) Received: (qmail 40801 invoked by uid 89); 18 Sep 2015 08:56:34 -0000 Received: from unknown (HELO ?192.168.250.192?) (mg@grem.de@88.217.180.156) by mail.grem.de with ESMTPA; 18 Sep 2015 08:56:34 -0000 Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (1.0) Subject: Re: Intel Haswell support - Any updates? From: Michael Gmelin X-Mailer: iPhone Mail (13A344) In-Reply-To: <20150918053445.GA1929@c720-r276659> Date: Fri, 18 Sep 2015 10:56:34 +0200 Cc: Nikola Pajkovsky , Stefan Wendler , freebsd-current@freebsd.org Content-Transfer-Encoding: quoted-printable Message-Id: <39E6D124-98A1-4289-AD3D-CFAA372C3074@freebsd.org> References: <55FA7324.5010603@icloud.com> <55FADB38.7000406@pcbsd.org> <87twqt2gs9.fsf@gooddata.com> <11271727.FrCOrXGY1l@hactar> <87a8sk205y.fsf@gooddata.com> <20150918053445.GA1929@c720-r276659> To: Matthias Apitz X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 18 Sep 2015 09:03:17 -0000 > On 18 Sep 2015, at 07:34, Matthias Apitz wrote: >=20 >> El d=C3=ADa Thursday, September 17, 2015 a las 11:42:01PM +0200, Nikola P= ajkovsky escribi=C3=B3: >>=20 >> Do not run those commands in X, otherwise it hangs. >>=20 >> $ vidcontrol -i mode | grep 1920 >> 383 (0x17f) 0x0000000f G 1920x1080x32 D 8x16 0xa0000 64k 64k 0xe0000000= 8100k >=20 > On my C720 the above cmd does not give any usefull information: >=20 >=20 > mode# flags type size font window linear buffe= r > --------------------------------------------------------------------------= ---- > 0 (0x000) 0x00000000 T 0x0 0x402653478 0x280996d6 131362k 0k= 0x00000000 0k > 1 (0x001) 0x00000000 T 0x0 0x402653478 0x280996d6 131362k 0k= 0x00000000 0k > 2 (0x002) 0x00000000 T 0x0 0x402653478 0x280996d6 131362k 0k= 0x00000000 0k > 3 (0x003) 0x00000000 T 0x0 0x402653478 0x280996d6 131362k 0k= 0x00000000 0k > 4 (0x004) 0x00000000 T 0x0 0x402653478 0x280996d6 131362k 0k= 0x00000000 0k > 5 ... >=20 >=20 > 507 (0x1fb) 0x00000000 T 0x0 0x402653478 0x280996d6 131362k 0= k 0x00000000 0k > 508 (0x1fc) 0x00000000 T 0x0 0x402653478 0x280996d6 131362k 0= k 0x00000000 0k > 509 (0x1fd) 0x00000000 T 0x0 0x402653478 0x280996d6 131362k 0= k 0x00000000 0k > 510 (0x1fe) 0x00000000 T 0x0 0x402653478 0x280996d6 131362k 0= k 0x00000000 0k > 511 (0x1ff) 0x00000000 T 0x0 0x402653478 0x280996d6 131362k 0= k 0x00000000 0k >=20 Last time I checked on the c720, the correct memory areas were marked as wri= te-combine by default (see "memcontrol list"), so you can't accomplish any f= urther performance gains by tuning it manually. - m From owner-freebsd-current@freebsd.org Fri Sep 18 13:29:54 2015 Return-Path: Delivered-To: freebsd-current@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 0B2829CF0E9 for ; Fri, 18 Sep 2015 13:29:54 +0000 (UTC) (envelope-from stefan.wendler@tngtech.com) Received: from zimbra.tngtech.com (zimbra.tngtech.com [212.204.93.107]) (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 BCD601C41 for ; Fri, 18 Sep 2015 13:29:53 +0000 (UTC) (envelope-from stefan.wendler@tngtech.com) Received: from localhost (localhost [127.0.0.1]) by zimbra.tngtech.com (Postfix) with ESMTP id 32881B00504; Fri, 18 Sep 2015 15:29:45 +0200 (CEST) Received: from zimbra.tngtech.com ([127.0.0.1]) by localhost (zimbra.tngtech.com [127.0.0.1]) (amavisd-new, port 10032) with ESMTP id Qa5GJTRhikeB; Fri, 18 Sep 2015 15:29:44 +0200 (CEST) Received: from localhost (localhost [127.0.0.1]) by zimbra.tngtech.com (Postfix) with ESMTP id DD826B005E5; Fri, 18 Sep 2015 15:29:44 +0200 (CEST) X-Virus-Scanned: amavisd-new at tngtech.com Received: from zimbra.tngtech.com ([127.0.0.1]) by localhost (zimbra.tngtech.com [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id FbHPCJXFpb1K; Fri, 18 Sep 2015 15:29:44 +0200 (CEST) Received: from hactar.localnet (pD9E8E265.dip0.t-ipconnect.de [217.232.226.101]) by zimbra.tngtech.com (Postfix) with ESMTPSA id BB531B00504; Fri, 18 Sep 2015 15:29:44 +0200 (CEST) From: Stefan Wendler To: Nikola Pajkovsky Cc: freebsd-current@freebsd.org Subject: Re: Intel Haswell support - Any updates? Date: Fri, 18 Sep 2015 15:29:43 +0200 Message-ID: <8538410.BAyuGgpz8H@hactar> Organization: TNG Technology Consulting GmbH User-Agent: KMail/4.14.3 (FreeBSD/10.2-RELEASE; KDE/4.14.3; amd64; ; ) In-Reply-To: <87a8sk205y.fsf@gooddata.com> References: <55FA7324.5010603@icloud.com> <11271727.FrCOrXGY1l@hactar> <87a8sk205y.fsf@gooddata.com> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 18 Sep 2015 13:29:54 -0000 On Thursday 17 September 2015 23:42:01 Nikola Pajkovsky wrote: > Do not run those commands in X, otherwise it hangs. > > $ vidcontrol -i mode | grep 1920 > 383 (0x17f) 0x0000000f G 1920x1080x32 D 8x16 0xa0000 64k 64k 0xe0000000 > 8100k > > $ memcontrol list | grep 0xe0000000 > 0xe0000000/0x20000000 BIOS uncacheable set-by-firmware active > > $ memcontrol set -b 0xe0000000 -l 0x20000000 -o BIOS write-combine > $ startx Okay, so i didn't do anything wrong here. $ vidcontrol -i mode | grep 1920 383 (0x17f) 0x0000000f G 1920x1080x32 D 8x16 0xa0000 64k 64k 0xe0000000 8100k So this would be 0xc0000000 for me $ memcontrol list | grep 0xc0000000 0xc0000000/0x40000000 BIOS uncacheable set-by-firmware active $ memcontrol set -b 0xc0000000 -l 0x40000000 -o BIOS write-combined $ memcontrol list | grep 0xc0000000 0xc0000000/0x40000000 BIOS write-combine active ... starting X. Nothing changed. I am testing this with youtube videos and it is still only "refreshing" every couple of seconds I am using the vesa driver and NOT uefi Cheers, Stefan From owner-freebsd-current@freebsd.org Fri Sep 18 13:33:03 2015 Return-Path: Delivered-To: freebsd-current@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 AAC6D9CF327 for ; Fri, 18 Sep 2015 13:33:03 +0000 (UTC) (envelope-from stefan.wendler@tngtech.com) Received: from zimbra.tngtech.com (zimbra.tngtech.com [212.204.93.107]) (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 6720510C7 for ; Fri, 18 Sep 2015 13:33:03 +0000 (UTC) (envelope-from stefan.wendler@tngtech.com) Received: from localhost (localhost [127.0.0.1]) by zimbra.tngtech.com (Postfix) with ESMTP id B2047B0054A; Fri, 18 Sep 2015 15:33:01 +0200 (CEST) Received: from zimbra.tngtech.com ([127.0.0.1]) by localhost (zimbra.tngtech.com [127.0.0.1]) (amavisd-new, port 10032) with ESMTP id lOdj4fnI95EA; Fri, 18 Sep 2015 15:33:01 +0200 (CEST) Received: from localhost (localhost [127.0.0.1]) by zimbra.tngtech.com (Postfix) with ESMTP id 7B481B00613; Fri, 18 Sep 2015 15:33:01 +0200 (CEST) X-Virus-Scanned: amavisd-new at tngtech.com Received: from zimbra.tngtech.com ([127.0.0.1]) by localhost (zimbra.tngtech.com [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id hGcKCe7HU7rW; Fri, 18 Sep 2015 15:33:01 +0200 (CEST) Received: from hactar.localnet (pD9E8E265.dip0.t-ipconnect.de [217.232.226.101]) by zimbra.tngtech.com (Postfix) with ESMTPSA id 5CEAAB0054A; Fri, 18 Sep 2015 15:33:01 +0200 (CEST) From: Stefan Wendler To: freebsd-current@freebsd.org, Matthias Apitz Cc: "Russell L. Carter" Subject: Re: Intel Haswell support - Any updates? Date: Fri, 18 Sep 2015 15:33 +0200 Message-ID: <2081067.PSnZzq08Cl@hactar> Organization: TNG Technology Consulting GmbH User-Agent: KMail/4.14.3 (FreeBSD/10.2-RELEASE; KDE/4.14.3; amd64; ; ) In-Reply-To: <20150917185720.GA2048@c720-r276659> References: <55FB050A.2080500@pinyon.org> <20150917185720.GA2048@c720-r276659> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 18 Sep 2015 13:33:03 -0000 On Thursday 17 September 2015 20:57:20 Matthias Apitz wrote: > You must run a ver y recent -HEAD; Wifi is fine I cannot run HEAD because I need a stable system for work. Will there be a package for FreeBSD 10? I really want to get rid of my crappy b/g usb stick. Cheers, Stefan From owner-freebsd-current@freebsd.org Fri Sep 18 13:57:17 2015 Return-Path: Delivered-To: freebsd-current@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 EAAE79CE466 for ; Fri, 18 Sep 2015 13:57:17 +0000 (UTC) (envelope-from grembo@freebsd.org) Received: from mail.grem.de (outcast.grem.de [213.239.217.27]) by mx1.freebsd.org (Postfix) with SMTP id 44289189B for ; Fri, 18 Sep 2015 13:57:16 +0000 (UTC) (envelope-from grembo@freebsd.org) Received: (qmail 43315 invoked by uid 89); 18 Sep 2015 13:57:09 -0000 Received: from unknown (HELO ?192.168.100.105?) (mg@grem.de@194.97.158.66) by mail.grem.de with ESMTPA; 18 Sep 2015 13:57:09 -0000 Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (1.0) Subject: Re: Intel Haswell support - Any updates? From: Michael Gmelin X-Mailer: iPhone Mail (13A344) In-Reply-To: <2081067.PSnZzq08Cl@hactar> Date: Fri, 18 Sep 2015 15:57:10 +0200 Cc: freebsd-current@freebsd.org, Matthias Apitz , "Russell L. Carter" Content-Transfer-Encoding: quoted-printable Message-Id: <50359452-B6FC-4A04-9FFE-279D8A9F661E@freebsd.org> References: <55FB050A.2080500@pinyon.org> <20150917185720.GA2048@c720-r276659> <2081067.PSnZzq08Cl@hactar> To: Stefan Wendler X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 18 Sep 2015 13:57:18 -0000 > On 18 Sep 2015, at 15:33, Stefan Wendler wrot= e: >=20 >> On Thursday 17 September 2015 20:57:20 Matthias Apitz wrote: >> You must run a ver y recent -HEAD; Wifi is fine >=20 > I cannot run HEAD because I need a stable system for work. Will there be a= =20 > package for FreeBSD 10? I really want to get rid of my crappy b/g usb stic= k. >=20 Unlikely, as it involved some breaking changes to smbus we can't do within a= major release. Many other changes might work on 10 (like memory detection, s= mbinfo quirks and changes to atkbd). You could of course keep the breaking c= hanges in a separate patch set (those enable light sensor and touch pad). See here for a list of commits involved, you might be able to back port most= of it: http://blog.grem.de/sysadmin/FreeBSD-On-AcerC720-Merged-2015-07-25-23-30.htm= l - Michael > _______________________________________________ > freebsd-current@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org"= From owner-freebsd-current@freebsd.org Fri Sep 18 14:12:08 2015 Return-Path: Delivered-To: freebsd-current@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 403109CF2D4 for ; Fri, 18 Sep 2015 14:12:08 +0000 (UTC) (envelope-from stefan.wendler@tngtech.com) Received: from zimbra.tngtech.com (zimbra.tngtech.com [212.204.93.107]) (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 EDFD710A4; Fri, 18 Sep 2015 14:12:07 +0000 (UTC) (envelope-from stefan.wendler@tngtech.com) Received: from localhost (localhost [127.0.0.1]) by zimbra.tngtech.com (Postfix) with ESMTP id 83DFDB00504; Fri, 18 Sep 2015 16:12:05 +0200 (CEST) Received: from zimbra.tngtech.com ([127.0.0.1]) by localhost (zimbra.tngtech.com [127.0.0.1]) (amavisd-new, port 10032) with ESMTP id ySYFSaTQUy8V; Fri, 18 Sep 2015 16:12:05 +0200 (CEST) Received: from localhost (localhost [127.0.0.1]) by zimbra.tngtech.com (Postfix) with ESMTP id EACF7B0069D; Fri, 18 Sep 2015 16:12:04 +0200 (CEST) X-Virus-Scanned: amavisd-new at tngtech.com Received: from zimbra.tngtech.com ([127.0.0.1]) by localhost (zimbra.tngtech.com [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id 787Jvn6Aqmdb; Fri, 18 Sep 2015 16:12:04 +0200 (CEST) Received: from hactar.localnet (pD9E8E265.dip0.t-ipconnect.de [217.232.226.101]) by zimbra.tngtech.com (Postfix) with ESMTPSA id C6029B00504; Fri, 18 Sep 2015 16:12:04 +0200 (CEST) From: Stefan Wendler To: Michael Gmelin Cc: freebsd-current@freebsd.org Subject: Re: Intel Haswell support - Any updates? Date: Fri, 18 Sep 2015 16:12:04 +0200 Message-ID: <1887869.RclIo8uMx7@hactar> Organization: TNG Technology Consulting GmbH User-Agent: KMail/4.14.3 (FreeBSD/10.2-RELEASE; KDE/4.14.3; amd64; ; ) In-Reply-To: <50359452-B6FC-4A04-9FFE-279D8A9F661E@freebsd.org> References: <2081067.PSnZzq08Cl@hactar> <50359452-B6FC-4A04-9FFE-279D8A9F661E@freebsd.org> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 18 Sep 2015 14:12:08 -0000 On Friday 18 September 2015 15:57:10 Michael Gmelin wrote: > > On 18 Sep 2015, at 15:33, Stefan Wendler wrote: > >> On Thursday 17 September 2015 20:57:20 Matthias Apitz wrote: > >> You must run a ver y recent -HEAD; Wifi is fine > > > > I cannot run HEAD because I need a stable system for work. Will there be a > > package for FreeBSD 10? I really want to get rid of my crappy b/g usb > > stick. > Unlikely, as it involved some breaking changes to smbus we can't do within a > major release. Many other changes might work on 10 (like memory detection, > smbinfo quirks and changes to atkbd). You could of course keep the breaking > changes in a separate patch set (those enable light sensor and touch pad). Alright. So I hope for 11 stable to arrive asap ;) > > See here for a list of commits involved, you might be able to back port most > of it: > > http://blog.grem.de/sysadmin/FreeBSD-On-AcerC720-Merged-2015-07-25-23-30.htm > l > > - Michael > Cheers, Stefan From owner-freebsd-current@freebsd.org Fri Sep 18 16:50:22 2015 Return-Path: Delivered-To: freebsd-current@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 60A759CFAAE for ; Fri, 18 Sep 2015 16:50:22 +0000 (UTC) (envelope-from sbruno@freebsd.org) Received: from mail.ignoranthack.me (ignoranthack.me [199.102.79.106]) (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 4315F10DE for ; Fri, 18 Sep 2015 16:50:21 +0000 (UTC) (envelope-from sbruno@freebsd.org) Received: from [192.168.100.102] (unknown [50.136.155.142]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) (Authenticated sender: sbruno@ignoranthack.me) by mail.ignoranthack.me (Postfix) with ESMTPSA id DE4CB193E6A; Fri, 18 Sep 2015 16:50:20 +0000 (UTC) Subject: Re: CURRENT: net/igb broken To: "O. Hartmann" , "Pieper, Jeffrey E" References: <20150915125618.0f752596@freyja.zeit4.iv.bundesimmobilien.de> <55F7FCB5.5090809@selasky.org> <2A35EA60C3C77D438915767F458D65688077F87B@ORSMSX111.amr.corp.intel.com> <20150917133509.6c87f5b6@freyja.zeit4.iv.bundesimmobilien.de> <20150917133712.0ffd01ee@freyja.zeit4.iv.bundesimmobilien.de> Cc: Hans Petter Selasky , freebsd-current From: Sean Bruno Message-ID: <55FC40CB.7090504@freebsd.org> Date: Fri, 18 Sep 2015 09:50:19 -0700 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:38.0) Gecko/20100101 Thunderbird/38.2.0 MIME-Version: 1.0 In-Reply-To: <20150917133712.0ffd01ee@freyja.zeit4.iv.bundesimmobilien.de> Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 18 Sep 2015 16:50:22 -0000 > > r287762 broke the system Before I revert this changeset *again* can you test revert r287762 from if_igb.c, e1000_82575.c and e1000_82575.h *only* That narrows down the change quite a bit. sean From owner-freebsd-current@freebsd.org Fri Sep 18 17:21:02 2015 Return-Path: Delivered-To: freebsd-current@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 63A029CFB2D for ; Fri, 18 Sep 2015 17:21:02 +0000 (UTC) (envelope-from ricera10@gmail.com) Received: from mail-qg0-x232.google.com (mail-qg0-x232.google.com [IPv6:2607:f8b0:400d:c04::232]) (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 1E9F61915; Fri, 18 Sep 2015 17:21:02 +0000 (UTC) (envelope-from ricera10@gmail.com) Received: by qgt47 with SMTP id 47so44015699qgt.2; Fri, 18 Sep 2015 10:21:01 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc:content-type; bh=+gjgzdnaAslYjqn+VQN/3Tzb1w+mKk1TBnfXbF2bj7U=; b=ArfDUfBF8W4i665iSFGYRdQ12phf4vbyI49x0EIJayS33R4WS0C3LP3RbhlVNs0ryE ZxX/ilDZlIQYMyieQ6IiRIg30Qe4ZddjVYfDSX3jYN8wSw8ey6LkDc7fDV6NlU6tIY/I nEwbZi5RWvMdoq6jQ3UhgB72iFVmes11C2zbNfFRtra32FFOHI0FQM0BLO/f11e2lvso jrwNaatvOCB+70BeEH22F/ypzFa7v+V7jdK4U5MOfpj6Un+onMjnjEVbeXpgGVaqdJiL VzXiRfbEikO6tARwZqCLxCwqFPLjipb/s+XsMy+wLAJSSyRZzw7ciKrlfEns6/VNOJKl 4tuQ== X-Received: by 10.141.23.69 with SMTP id z66mr8233350qhd.55.1442596861011; Fri, 18 Sep 2015 10:21:01 -0700 (PDT) MIME-Version: 1.0 References: <20150915125618.0f752596@freyja.zeit4.iv.bundesimmobilien.de> <55F7FCB5.5090809@selasky.org> <2A35EA60C3C77D438915767F458D65688077F87B@ORSMSX111.amr.corp.intel.com> <20150917133509.6c87f5b6@freyja.zeit4.iv.bundesimmobilien.de> <20150917133712.0ffd01ee@freyja.zeit4.iv.bundesimmobilien.de> <55FC40CB.7090504@freebsd.org> In-Reply-To: <55FC40CB.7090504@freebsd.org> From: Eric Joyner Date: Fri, 18 Sep 2015 17:20:51 +0000 Message-ID: Subject: Re: CURRENT: net/igb broken To: Sean Bruno , "O. Hartmann" , "Pieper, Jeffrey E" Cc: Hans Petter Selasky , freebsd-current Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.20 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 18 Sep 2015 17:21:02 -0000 He has an i210 -- he would want to revert e1000_i210.[ch], too. Sorry for the thrash Sean -- it sounds like it would be a good idea for you should revert this patch, and Jeff and I can go look at trying these shared code updates and igb changes internally again. We at Intel really could've done a better job of making sure these changes worked across a wider variety of devices. - Eric On Fri, Sep 18, 2015 at 9:50 AM Sean Bruno wrote: > > > > > r287762 broke the system > > > Before I revert this changeset *again* can you test revert r287762 from > if_igb.c, e1000_82575.c and e1000_82575.h *only* > > That narrows down the change quite a bit. > > sean > _______________________________________________ > freebsd-current@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" > From owner-freebsd-current@freebsd.org Fri Sep 18 18:26:08 2015 Return-Path: Delivered-To: freebsd-current@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 00EE49CF430 for ; Fri, 18 Sep 2015 18:26:08 +0000 (UTC) (envelope-from ohartman@zedat.fu-berlin.de) Received: from outpost1.zedat.fu-berlin.de (outpost1.zedat.fu-berlin.de [130.133.4.66]) (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 ADC0D1CEB; Fri, 18 Sep 2015 18:26:07 +0000 (UTC) (envelope-from ohartman@zedat.fu-berlin.de) Received: from inpost2.zedat.fu-berlin.de ([130.133.4.69]) by outpost.zedat.fu-berlin.de (Exim 4.85) with esmtp (envelope-from ) id <1Zd0M9-002Is4-EW>; Fri, 18 Sep 2015 20:25:57 +0200 Received: from x5ce1362f.dyn.telefonica.de ([92.225.54.47] helo=thor.walstatt.dynvpn.de) by inpost2.zedat.fu-berlin.de (Exim 4.85) with esmtpsa (envelope-from ) id <1Zd0M9-002qhR-8J>; Fri, 18 Sep 2015 20:25:57 +0200 Date: Fri, 18 Sep 2015 20:25:52 +0200 From: "O. Hartmann" To: Sean Bruno Cc: "Pieper, Jeffrey E" , Hans Petter Selasky , freebsd-current Subject: Re: CURRENT: net/igb broken Message-ID: <20150918202552.4c53526f.ohartman@zedat.fu-berlin.de> In-Reply-To: <55FC40CB.7090504@freebsd.org> References: <20150915125618.0f752596@freyja.zeit4.iv.bundesimmobilien.de> <55F7FCB5.5090809@selasky.org> <2A35EA60C3C77D438915767F458D65688077F87B@ORSMSX111.amr.corp.intel.com> <20150917133509.6c87f5b6@freyja.zeit4.iv.bundesimmobilien.de> <20150917133712.0ffd01ee@freyja.zeit4.iv.bundesimmobilien.de> <55FC40CB.7090504@freebsd.org> Organization: FU Berlin X-Mailer: Claws Mail 3.12.0 (GTK+ 2.24.28; amd64-portbld-freebsd11.0) MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; boundary="Sig_/W3/jBs2uKIS5.5xS5Bw8MZZ"; protocol="application/pgp-signature" X-Originating-IP: 92.225.54.47 X-ZEDAT-Hint: A X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 18 Sep 2015 18:26:08 -0000 --Sig_/W3/jBs2uKIS5.5xS5Bw8MZZ Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable Am Fri, 18 Sep 2015 09:50:19 -0700 Sean Bruno schrieb: >=20 > >=20 > > r287762 broke the system >=20 >=20 > Before I revert this changeset *again* can you test revert r287762 from > if_igb.c, e1000_82575.c and e1000_82575.h *only* >=20 > That narrows down the change quite a bit. >=20 > sean I have no access to the hardware before Monday, 21st, so we need to wait a = bit. Regards, Oliver --Sig_/W3/jBs2uKIS5.5xS5Bw8MZZ Content-Type: application/pgp-signature Content-Description: OpenPGP digital signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQEcBAEBCAAGBQJV/FcwAAoJEOgBcD7A/5N8J9MIAM1ZwqZdOBN3793cYZcXaLg6 jsRHeTnNIhCzM0y3xnMqKB7AQiuExsm7LfPeXX/QhkYhE1AVIW4Cz7TGuhQh5HDI yibanXNi0l4kUxjG+Mow/hMBHL9TmYzg+/Uux7r6RajQE9PvDQ6bo8YzlALGu+Uc mP1e3zI/nl80XtIikUBPC9Ofvl12FVjsNceUzHDIRiDhuC0BSBxmgLPOvZ0wr2FU f5xRYQkiijAX31ge9Vb0wwmic17B3RkNAb6+0JrjfFziBE+/bhohXhRNY/8J8ht7 sndsoUTbezDolevqwys4os8KG7C0mx6vC5YMNwVEiBWBYyEHasXoqlFAJptzz+4= =87ZE -----END PGP SIGNATURE----- --Sig_/W3/jBs2uKIS5.5xS5Bw8MZZ-- From owner-freebsd-current@freebsd.org Fri Sep 18 19:50:17 2015 Return-Path: Delivered-To: freebsd-current@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 6581D9CECF4 for ; Fri, 18 Sep 2015 19:50:17 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-oi0-x22e.google.com (mail-oi0-x22e.google.com [IPv6:2607:f8b0:4003:c06::22e]) (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 2E17D18EE; Fri, 18 Sep 2015 19:50:17 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: by oibi136 with SMTP id i136so32282510oib.3; Fri, 18 Sep 2015 12:50:16 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=O2xvuZewEITXIIHG5IfcCLWtdVyYX0E8C0PDVbZQW8w=; b=numCbCEzfNqGtGzdKoN8uckKYIAsJZXRhWNcftIE2XcTUaZssftK4FWBUTCpwkFahu nfl+yqqDbHZ4UtftpyM0e2kdsvu2nUJuQ2B5awrBBneNIHydiqsxUfrWxgYO6KgGY16G o8yxj7BH1v1jV+0Rl8PmcU7yMfs0H9DzEWjpYz/sYq2oRxr+TxjaGc4ae6OTRIhtAxkz WNfPUe1cPbsf/FnZI+ZNt16TGiPrlkc4e7iSW00p7FGCPg8MZ9mYq9kdSPQEdzZ5iZI2 sT84RX4FY1/hOMZcaiDTe6/q7aQ/rugaSGhM+vnyEX7K/J4N63oY6Li5W+2I3n/s9CZZ xTFQ== MIME-Version: 1.0 X-Received: by 10.202.207.197 with SMTP id f188mr4321018oig.90.1442605816457; Fri, 18 Sep 2015 12:50:16 -0700 (PDT) Received: by 10.202.4.131 with HTTP; Fri, 18 Sep 2015 12:50:16 -0700 (PDT) In-Reply-To: <1887869.RclIo8uMx7@hactar> References: <2081067.PSnZzq08Cl@hactar> <50359452-B6FC-4A04-9FFE-279D8A9F661E@freebsd.org> <1887869.RclIo8uMx7@hactar> Date: Fri, 18 Sep 2015 12:50:16 -0700 Message-ID: Subject: Re: Intel Haswell support - Any updates? From: Adrian Chadd To: Stefan Wendler Cc: Michael Gmelin , freebsd-current Content-Type: text/plain; charset=UTF-8 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 18 Sep 2015 19:50:17 -0000 Hi, Just run -HEAD. Outside of occasional hiccups, a whole bunch of us use it for day to day work, and it works fine. New hardware support moves fast and furious; even when 11-STABLE rocks around we're going to be moving forward quickly on 12-CURRENT and you'll be stuck in the same place. :) -adrian From owner-freebsd-current@freebsd.org Fri Sep 18 21:05:53 2015 Return-Path: Delivered-To: freebsd-current@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 18C0BA00022 for ; Fri, 18 Sep 2015 21:05:53 +0000 (UTC) (envelope-from slw@zxy.spb.ru) Received: from zxy.spb.ru (zxy.spb.ru [195.70.199.98]) (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 C8BEB1FF4; Fri, 18 Sep 2015 21:05:52 +0000 (UTC) (envelope-from slw@zxy.spb.ru) Received: from slw by zxy.spb.ru with local (Exim 4.84 (FreeBSD)) (envelope-from ) id 1Zd2qq-000MkN-8q; Sat, 19 Sep 2015 00:05:48 +0300 Date: Sat, 19 Sep 2015 00:05:48 +0300 From: Slawa Olhovchenkov To: Adrian Chadd Cc: Stefan Wendler , Michael Gmelin , freebsd-current Subject: Re: Intel Haswell support - Any updates? Message-ID: <20150918210548.GV3158@zxy.spb.ru> References: <2081067.PSnZzq08Cl@hactar> <50359452-B6FC-4A04-9FFE-279D8A9F661E@freebsd.org> <1887869.RclIo8uMx7@hactar> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.23 (2014-03-12) X-SA-Exim-Connect-IP: X-SA-Exim-Mail-From: slw@zxy.spb.ru X-SA-Exim-Scanned: No (on zxy.spb.ru); SAEximRunCond expanded to false X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 18 Sep 2015 21:05:53 -0000 On Fri, Sep 18, 2015 at 12:50:16PM -0700, Adrian Chadd wrote: > Hi, > > Just run -HEAD. Outside of occasional hiccups, a whole bunch of us use > it for day to day work, and it works fine. Some years ago -HEAD break may be one at month, now -HEAD break some times at week, and, may be, persistent break (em/igb, callout, i915 on 945G (yes, this is also break on -stable, but on stable simple revert two commit and will be nice, on -head you got many coomits)). Development is ipmotant and development w/o breaks imposibles, but current -HEAD not to agree with genareal user. From owner-freebsd-current@freebsd.org Sat Sep 19 16:37:53 2015 Return-Path: Delivered-To: freebsd-current@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 1A800A05741 for ; Sat, 19 Sep 2015 16:37:53 +0000 (UTC) (envelope-from grembo@freebsd.org) Received: from mail.grem.de (outcast.grem.de [213.239.217.27]) by mx1.freebsd.org (Postfix) with SMTP id 728021373 for ; Sat, 19 Sep 2015 16:37:51 +0000 (UTC) (envelope-from grembo@freebsd.org) Received: (qmail 59315 invoked by uid 89); 19 Sep 2015 16:31:03 -0000 Received: from unknown (HELO bsd64.grem.de) (mg@grem.de@88.217.180.156) by mail.grem.de with ESMTPA; 19 Sep 2015 16:31:03 -0000 Date: Sat, 19 Sep 2015 18:35:25 +0200 From: Michael Gmelin To: Stefan Wendler Cc: freebsd-current@freebsd.org Subject: Re: Intel Haswell support - Any updates? Message-ID: <20150919183525.2711b753@bsd64.grem.de> In-Reply-To: <1887869.RclIo8uMx7@hactar> References: <2081067.PSnZzq08Cl@hactar> <50359452-B6FC-4A04-9FFE-279D8A9F661E@freebsd.org> <1887869.RclIo8uMx7@hactar> X-Mailer: Claws Mail 3.12.0 (GTK+ 2.24.28; amd64-portbld-freebsd10.2) X-Face: $wrgCtfdVw_H9WAY?S&9+/F"!41z'L$uo*WzT8miX?kZ~W~Lr5W7v?j0Sde\mwB&/ypo^}> +a'4xMc^^KroE~+v^&^#[B">soBo1y6(TW6#UZiC]o>C6`ej+i Face: iVBORw0KGgoAAAANSUhEUgAAADAAAAAwBAMAAAClLOS0AAAAJFBMVEWJBwe5BQDl LASZU0/LTEWEfHbyj0Txi32+sKrp1Mv944X8/fm1rS+cAAAACXBIWXMAAAsTAAAL EwEAmpwYAAAAB3RJTUUH3wESCxwC7OBhbgAAACFpVFh0Q29tbWVudAAAAAAAQ3Jl YXRlZCB3aXRoIFRoZSBHSU1QbbCXAAAAAghJREFUOMu11DFvEzEUAGCfEhBVFzuq AKkLd0O6VrIQsLXVSZXoWE5N1K3DobBBA9fQpRWc8OkWouaIjedWKiyREOKs+3PY fvalCNjgLVHeF7/3bMtBzV8C/VsQ8tecEgCcDgrzjekwKZ7TwsJZd/ywEKwwP+ZM 8P3drTsAwWn2mpWuDDuYiK1bFs6De0KUUFw0tWxm+D4AIhuuvZqtyWYeO7jQ4Aea 7jUqI+ixhQoHex4WshEvSXdood7stlv4oSuFOC4tqGcr0NjEqXgV4mMJO38nld4+ xKNxRDon7khyKVqY7YR4d+Cg0OMrkWXZOM7YDkEfKiilCn1qYv4mighZiynuHHOA Wq9QJq+BIES7lMFUtcikMnkDGHUoncA+uHgrP0ctIEqfwLHzeSo+eUA66AqzwN6n 2ZHJhw6Qh/PoyC/QENyEyC/AyNjq74Bs+3UH0xYwzDUC4B97HgLocg1QLYgDDO1v f3UX9Y307Ew4AHh67YAFFsxEpkXwpXY3eIgMhAAE3R19L919nNnuD2wlPcDE3UeT L2ytEICQib9BXgS2fU8PrD82ToYO1OEmMSnYTjSqSv9wdC0tPYC+rQRQD9ESnldF CyqfmiYW+tlALt8gH2xrMdC/youbjzPXEun+/ReXsMCDyve3dZc09fn2Oas8oXGc Jj6/fOeK5UmSMPmf/jL+GD8BEj0k/Fn6IO4AAAAASUVORK5CYII= MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; boundary="Sig_/DyRR4pjnGceTMI8fmAD3SFC"; protocol="application/pgp-signature" X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 19 Sep 2015 16:37:53 -0000 --Sig_/DyRR4pjnGceTMI8fmAD3SFC Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable On Fri, 18 Sep 2015 16:12:04 +0200 Stefan Wendler wrote: > On Friday 18 September 2015 15:57:10 Michael Gmelin wrote: > > > On 18 Sep 2015, at 15:33, Stefan Wendler > > > =20 > wrote: > > >> On Thursday 17 September 2015 20:57:20 Matthias Apitz wrote: > > >> You must run a ver y recent -HEAD; Wifi is fine > > >=20 > > > I cannot run HEAD because I need a stable system for work. Will > > > there be a package for FreeBSD 10? I really want to get rid of my > > > crappy b/g usb stick. > > Unlikely, as it involved some breaking changes to smbus we can't do > > within a major release. Many other changes might work on 10 (like > > memory detection, smbinfo quirks and changes to atkbd). You could > > of course keep the breaking changes in a separate patch set (those > > enable light sensor and touch pad). > Alright. So I hope for 11 stable to arrive asap ;) >=20 11-STABLE is almost a year away. I backported the patches to 10.2-RELEASE, which was quite easy. You can find the patch against releng/10.2 and a short howto here: http://blog.grem.de/sysadmin/FreeBSD-10.2-On-AcerC720-2015-09-19-17-00.html The following tests were performed using the resulting memstick image: - Boot from USB into installer - Select "Live CD" - Test trackpad: kldload ig4 kldload cyapa moused -p /dev/cyapa0 - Test light sensor (it's located above the F2 key): kldload isl sysctl dev.isl.0 - Test wireless: mount -rw / sysrc wlans_ath0=3Dwlan0 sysrc ifconfig_wlan0=3D"WPA SYNCDHCP" cat >/etc/wpa_supplicant.conf < Delivered-To: freebsd-current@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 158B9A05D50 for ; Sat, 19 Sep 2015 16:49:22 +0000 (UTC) (envelope-from allanjude@freebsd.org) Received: from mx1.scaleengine.net (mx1.scaleengine.net [209.51.186.6]) by mx1.freebsd.org (Postfix) with ESMTP id E01191DEF for ; Sat, 19 Sep 2015 16:49:21 +0000 (UTC) (envelope-from allanjude@freebsd.org) Received: from [10.1.1.2] (unknown [10.1.1.2]) (Authenticated sender: allanjude.freebsd@scaleengine.com) by mx1.scaleengine.net (Postfix) with ESMTPSA id 8A2919BE1 for ; Sat, 19 Sep 2015 16:49:15 +0000 (UTC) Subject: Re: Intel Haswell support - Any updates? To: freebsd-current@freebsd.org References: <55FA7324.5010603@icloud.com> <09A515F2-44BA-4DF0-9792-D4C56EEB9D7C@FreeBSD.org> <114F22EF-61E3-4D75-84FB-9D6E3FBCB8F3@FreeBSD.org> <20150917131333.GN1247@egr.msu.edu> <20150917134809.GA3025@c720-r276659> <55FAD5EF.5030001@pcbsd.org> <20150917171958.046e4b6b.ohartman@zedat.fu-berlin.de> <55FADB38.7000406@pcbsd.org> <1442503731.1862.1.camel@me.com> From: Allan Jude Message-ID: <55FD9272.8070308@freebsd.org> Date: Sat, 19 Sep 2015 12:50:58 -0400 User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.2.0 MIME-Version: 1.0 In-Reply-To: Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="PbrSdVJOJMn4wninIqdnGpiPBiRJdDaGD" X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 19 Sep 2015 16:49:22 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --PbrSdVJOJMn4wninIqdnGpiPBiRJdDaGD Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable On 2015-09-17 20:58, Lundberg, Johannes wrote: > No yet but I would like to have a meeting if possible. Are there any > foundation folks in the bay area? > Starting from next month I will be based in our Los Altos office for th= e > time being. >=20 >=20 > -- > Johannes Lundberg > BRILLIANTSERVICE CO., LTD. >=20 > On Fri, Sep 18, 2015 at 9:53 AM, Adrian Chadd > wrote: >=20 >> Have you had a one-on-one with anyone at the foundation and expressed >> your desires/concerns? You're a vendor after all... >> >> -a >> >=20 There will be a Vendor and Dev Summit in Sunnyvale in November: https://wiki.freebsd.org/201511VendorDevSummit --=20 Allan Jude --PbrSdVJOJMn4wninIqdnGpiPBiRJdDaGD 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.0.22 (MingW32) iQIcBAEBAgAGBQJV/ZJ2AAoJEBmVNT4SmAt+SnYP+gJbGA+LZdmiNVa4FDpSQgPD MyleU6JZLIwrJ3hUGYyuO6MrcMozkyGTtVJWAIjYuYSpLLGdo4Knu/FbMfxSchQX 6mRqqsbE68PjvTMrhQjy0cucMrjjLjxoL0R1leTEmXXqcVwAIQuXKaFscN+d+Vc5 kS4HxFuYBdam0Pb7cMDpT1LsAdnKSUlH68hSkslDuO7tZ9F1cT5hJ34fNQFBzF+B fzFHXNXqYyN7iomvcip8+Dywpbnce6VbmBHcDtVBtcxuFfq+gu11y6ZTnkZkHS+K mobAx2W9/2Zqi0yUE5ghnxaHyflOyZlfLf6iEnTmLpxHgvPoXYlWQWc1Q5U4ttWJ 4Nrq0T/YJ50g3dZyOZdmPc8WUxwTnEYSF9BJee00HNUm5CBpwDpJitYJ9Ynqlr1w UnurtvOYlNIQwC3l+WP4ArbGUeqqFeuUOo+6ptxoESouBAuF405bTxWwPaMqpvE+ +hJmkbFHIsI0Ynb7r7Vi/OIoZOccHxU8OL7fHxYBOAzbuQ4bCAJG5/HoMESkVCsI rGsAUeoXO8Or2NweyjDbw1fZ+IHbuuN8SDY66MIJ+Y+JRRkIYHAkeYCCq1KC5gGX 3o4jPsMFrsphzMO2fYtLT69h9hHc0N1M1DcMTfMiJ1mtaKSXI4+hZN/vILlUHtMd GBOvMPGpKkXN1zfcWkYT =+6jC -----END PGP SIGNATURE----- --PbrSdVJOJMn4wninIqdnGpiPBiRJdDaGD-- From owner-freebsd-current@freebsd.org Sat Sep 19 16:53:12 2015 Return-Path: Delivered-To: freebsd-current@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 9AB79A05F69 for ; Sat, 19 Sep 2015 16:53:12 +0000 (UTC) (envelope-from allanjude@freebsd.org) Received: from mx1.scaleengine.net (mx1.scaleengine.net [209.51.186.6]) by mx1.freebsd.org (Postfix) with ESMTP id 78361117C for ; Sat, 19 Sep 2015 16:53:12 +0000 (UTC) (envelope-from allanjude@freebsd.org) Received: from [10.1.1.2] (unknown [10.1.1.2]) (Authenticated sender: allanjude.freebsd@scaleengine.com) by mx1.scaleengine.net (Postfix) with ESMTPSA id DEFE59BEE for ; Sat, 19 Sep 2015 16:53:11 +0000 (UTC) Subject: Re: Intel Haswell support - Any updates? To: freebsd-current@freebsd.org References: <2081067.PSnZzq08Cl@hactar> <50359452-B6FC-4A04-9FFE-279D8A9F661E@freebsd.org> <1887869.RclIo8uMx7@hactar> From: Allan Jude Message-ID: <55FD9362.3060109@freebsd.org> Date: Sat, 19 Sep 2015 12:54:58 -0400 User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.2.0 MIME-Version: 1.0 In-Reply-To: Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="JOwRcJVHseiWw05Ioouqxhe1C3dChGlkB" X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 19 Sep 2015 16:53:12 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --JOwRcJVHseiWw05Ioouqxhe1C3dChGlkB Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable On 2015-09-18 15:50, Adrian Chadd wrote: > Hi, >=20 > Just run -HEAD. Outside of occasional hiccups, a whole bunch of us use > it for day to day work, and it works fine. >=20 > New hardware support moves fast and furious; even when 11-STABLE rocks > around we're going to be moving forward quickly on 12-CURRENT and > you'll be stuck in the same place. :) >=20 >=20 >=20 > -adrian > _______________________________________________ > freebsd-current@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.o= rg" >=20 For those who are slightly more conservative, PCBSD offers monthly -CURRENT snapshot images with binary upgrades. Highly recommended for developer laptops. You can also do horrible things to them like I do, and 'make installworld' a newer head over top of it. Also, having ZFS boot environments means, it is easy to take a step backwards if there is a problem with something in a 'newer' -CURRENT. --=20 Allan Jude --JOwRcJVHseiWw05Ioouqxhe1C3dChGlkB 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.0.22 (MingW32) iQIcBAEBAgAGBQJV/ZNiAAoJEBmVNT4SmAt+4FEQAK4Enx21Pm57wmK69ZvhB/M+ zMkgSlivfNL6vKzOn/+zsAHEvlclWA4CqfYkbtLmiae0HBVPXADo2oAI0rJvNbDe plnaAmjIBJVubbGYDnD2su6dmjYy9qp1GBTLXVlQrvObPzAbi1I7zEQWYAFRsClI 0gYCPs8Mat1xdu6j98Nz4KU+0Kd7FCv4EvNGwxFmH7OAGP7iZ5I0qFLkkt4VMmYo wG+g2c4JfvOy5kR7sllAP65u5uqUmEuRp7fBvedx8h1f/wkab3iqLwn/zUI8Efm2 jXNxNZpgPToD+1IXz72Q5xcd6CmT9l8RbOYvWPnpNOW2QpDVQ3ckWJV0tCMy/8bP iET5KT7QVOAuyr4dJPGv6Np/27I7+wiJdIsAq4u73ZYywLJ98csMt1KP7yXeyLZz q+l4GGL8pWOmOXK4h2pLaxMgBDJilDjA+1XK1MJ5yZKw+1iKrFowJJSYUATT4TeG nDTpfoIKGLYw4l5TwsZuwsexHxDadPlcsSqZkGGEo/ScQJLeWPYwaIR8tzr4Mkqe BkGc1+eFa+uoBaoA1VplmIG6ojWMBENej4zc+Uo0E4BVKEufEDhX/F9thXFO8Y80 lew11SQrL1XRLT9VmjjltX8sEkDAE71E6Es5hj/4ksz9AlbUr3kAgrZb6Utxuofz AoGHGD2KTJhm1ezyDP1j =BgYH -----END PGP SIGNATURE----- --JOwRcJVHseiWw05Ioouqxhe1C3dChGlkB-- From owner-freebsd-current@freebsd.org Sat Sep 19 18:23:47 2015 Return-Path: Delivered-To: freebsd-current@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 87ECB9CFA85 for ; Sat, 19 Sep 2015 18:23:47 +0000 (UTC) (envelope-from sbruno@freebsd.org) Received: from mail.ignoranthack.me (ignoranthack.me [199.102.79.106]) (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 6917E127D for ; Sat, 19 Sep 2015 18:23:46 +0000 (UTC) (envelope-from sbruno@freebsd.org) Received: from [192.168.100.102] (unknown [50.136.155.142]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) (Authenticated sender: sbruno@ignoranthack.me) by mail.ignoranthack.me (Postfix) with ESMTPSA id 30A8B193E6A; Sat, 19 Sep 2015 18:23:45 +0000 (UTC) Subject: Re: CURRENT: net/igb broken To: Eric Joyner , "O. Hartmann" , "Pieper, Jeffrey E" References: <20150915125618.0f752596@freyja.zeit4.iv.bundesimmobilien.de> <55F7FCB5.5090809@selasky.org> <2A35EA60C3C77D438915767F458D65688077F87B@ORSMSX111.amr.corp.intel.com> <20150917133509.6c87f5b6@freyja.zeit4.iv.bundesimmobilien.de> <20150917133712.0ffd01ee@freyja.zeit4.iv.bundesimmobilien.de> <55FC40CB.7090504@freebsd.org> Cc: Hans Petter Selasky , freebsd-current From: Sean Bruno Message-ID: <55FDA830.7030307@freebsd.org> Date: Sat, 19 Sep 2015 11:23:44 -0700 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:38.0) Gecko/20100101 Thunderbird/38.2.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 19 Sep 2015 18:23:47 -0000 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 On 09/18/15 10:20, Eric Joyner wrote: > He has an i210 -- he would want to revert e1000_i210.[ch], too. > > Sorry for the thrash Sean -- it sounds like it would be a good idea > for you should revert this patch, and Jeff and I can go look at > trying these shared code updates and igb changes internally again. > We at Intel really could've done a better job of making sure these > changes worked across a wider variety of devices. > > - Eric I've reverted the changes to head. I'll reopen the reviews and we can proceed from there. sean > > On Fri, Sep 18, 2015 at 9:50 AM Sean Bruno > wrote: > > >> >> r287762 broke the system > > > Before I revert this changeset *again* can you test revert r287762 > from if_igb.c, e1000_82575.c and e1000_82575.h *only* > > That narrows down the change quite a bit. > > sean _______________________________________________ > freebsd-current@freebsd.org > mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-current To > unsubscribe, send any mail to > "freebsd-current-unsubscribe@freebsd.org > " > -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQF8BAEBCgBmBQJV/agsXxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXRCQUFENDYzMkU3MTIxREU4RDIwOTk3REQx MjAxRUZDQTFFNzI3RTY0AAoJEBIB78oecn5kkkMH/icGgcIAdm3CIxtXtnhbE5E9 N6RrBrgJruoRHP2geJ9UOUGp7MaFwS6AHcwCC7FvxoydzcsT+iMj3Kreu+aEkT4C PZvLsqIvLeX0WVEXSC8jwBAZbrOwJ+4TcMMnW2KZMeUPUHAd8rP0+Skj9AeQ4feJ OfLqv52VdxYTnx+vYbvZSaOgWp8sC+PcoJxiJua7hpmqXwISbcG9eXxQHUil0fcv tqfb2dv89VN12brFuQbFtgEK2RG6gKtbj7IQkeQqzt0g5WL6UnJ5OslajcEJwIA4 H6H4eke5CQUugVTUv5cbCwmQDfAF2qF8JgsxuuQDPvQRb4+XH1ks/5SEhENItv0= =JTMu -----END PGP SIGNATURE-----