Date: Fri, 4 Jul 2014 11:38:27 +0200 (CEST) From: =?ISO-8859-1?Q?Trond_Endrest=F8l?= <Trond.Endrestol@fagskolen.gjovik.no> To: current@FreeBSD.org Subject: Re: keyboard break to debugger broken? Message-ID: <alpine.BSF.2.11.1407041134300.11883@mail.fig.ol.no> In-Reply-To: <20140704092848.GZ45513@funkthat.com> References: <20140704092848.GZ45513@funkthat.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, 4 Jul 2014 02:28-0700, John-Mark Gurney wrote: > So, I recently tried to break into the debugger w/ the various key > sequences that I know about, and none of them worked... I've tried > CTRL-ESC, ALT-ESC, CTRL-ALT-ESC, CTRL-PRTSCR, ALT-PRTSCR and > CTRL-ALT-PRTSCR, and many other different ones... I've verified that > I can sysctl debug.kdb.enter=1 to enter the debugger, and the > CTRL-ALT-PAUSE works to suspend the machine, and CTRL-ALT-DEL works > to reboot... > > Does anyone know if this works? > > Thanks for the pointers... > > btw, I'm having trouble on 9stable too. You might need to modify and load a keymap, specifying debug as the action for the appropriate combination of keys. Have a look at the files in /usr/share/syscons/keymaps/. -- +-------------------------------+------------------------------------+ | Vennlig hilsen, | Best regards, | | Trond Endrestøl, | Trond Endrestøl, | | IT-ansvarlig, | System administrator, | | Fagskolen Innlandet, | Gjøvik Technical College, Norway, | | tlf. mob. 952 62 567, | Cellular...: +47 952 62 567, | | sentralbord 61 14 54 00. | Switchboard: +47 61 14 54 00. | +-------------------------------+------------------------------------+ From owner-freebsd-current@FreeBSD.ORG Fri Jul 4 10:16:31 2014 Return-Path: <owner-freebsd-current@FreeBSD.ORG> Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 819C64EF for <freebsd-current@freebsd.org>; Fri, 4 Jul 2014 10:16:31 +0000 (UTC) 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 379022894 for <freebsd-current@freebsd.org>; Fri, 4 Jul 2014 10:16:30 +0000 (UTC) Received: from slw by zxy.spb.ru with local (Exim 4.82 (FreeBSD)) (envelope-from <slw@zxy.spb.ru>) id 1X30Xa-000FdH-Ja; Fri, 04 Jul 2014 14:16:26 +0400 Date: Fri, 4 Jul 2014 14:16:26 +0400 From: Slawa Olhovchenkov <slw@zxy.spb.ru> To: Kevin Oberman <rkoberman@gmail.com> Subject: Re: FreeBSD iscsi target Message-ID: <20140704101626.GB58753@zxy.spb.ru> References: <20140701091252.GB3443@brick> <20140701231305.GA37246@zxy.spb.ru> <CAN6yY1t2qDzfeO37p2s_3=vzEVv5C813M0ttqjnM4tJGkkBhyA@mail.gmail.com> <20140702112609.GA85758@zxy.spb.ru> <CAN6yY1uzfjoDfEdti91Ogy11LzT3-5JvLREBdW6ynEOgm0uUPA@mail.gmail.com> <20140702203603.GO5102@zxy.spb.ru> <CAN6yY1von-Z586V=8qs3+OfV3oXes380s2GD-149EYWLxws-qA@mail.gmail.com> <CA+P_MZE013dv22Sb-rk7ZoiYbCTodmth0d-XpdM6mrpw3WxQmg@mail.gmail.com> <20140703091321.GP5102@zxy.spb.ru> <CAN6yY1uk8ooCjWzH=Zxyjm8UhgEm3dVPfc7ZOV1LR3+3DfnyHA@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <CAN6yY1uk8ooCjWzH=Zxyjm8UhgEm3dVPfc7ZOV1LR3+3DfnyHA@mail.gmail.com> User-Agent: Mutt/1.5.23 (2014-03-12) X-SA-Exim-Connect-IP: <locally generated> X-SA-Exim-Mail-From: slw@zxy.spb.ru X-SA-Exim-Scanned: No (on zxy.spb.ru); SAEximRunCond expanded to false Cc: Nikolay Denev <ndenev@gmail.com>, Sreenivasa Honnur <shonnur@chelsio.com>, FreeBSD Current <freebsd-current@freebsd.org> X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: Discussions about the use of FreeBSD-current <freebsd-current.freebsd.org> List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-current>, <mailto:freebsd-current-request@freebsd.org?subject=unsubscribe> List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current/>; List-Post: <mailto:freebsd-current@freebsd.org> List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help> List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>, <mailto:freebsd-current-request@freebsd.org?subject=subscribe> X-List-Received-Date: Fri, 04 Jul 2014 10:16:31 -0000 On Thu, Jul 03, 2014 at 08:39:42PM -0700, Kevin Oberman wrote: > > > > In real world "Reality is quite different than it actually is". > > > > http://www.cisco.com/c/en/us/products/collateral/switches/catalyst-6500-series-switches/white_paper_c11-696669.html > > > > See "Packet Path Theory of Operation. Ingress Mode". > > > > > Yep. It is really crappy LAGG (fixed three-tupple hash... yuck!) and is > really nothing but 4 10G Ethernet ports using a 40G PHY in yhe 4x10G form. > > Note that they don't make any claim of 802.3ba compliance. It only states > that "40 Gigabit Ethernet is now part of the IEEE 802.3ba standard." So it > is, but this device almost certainly predates the completion of the > standard to get a product for which there was great demand. It's a data > center product and for typical cases of large numbers of small flow, it > should do the trick. Probably does not interoperate with true 80-2.3ba > hardware, either. > > My boss at the time I retired last November was on the committee that wrote > 802.3ba. He would be a good authority on whether the standard has any vague > wording that would allow this, but he retired 5 month after I did and I > have no contact information for him. But I'm pretty sure that there is no > way that this is legitimate 40G Ethernet. 802.3ba describe only end point of ethernet. ASIC, internal details of implemetations NICs, switches, fabrics -- out of standart scope. Bottleneck can be in any point of packet flow. In first pappers of netmap test demonstarated NIC can't do saturation of 10G in one stream 64 bytes packet -- need use multiple rings for transmit. I think need use general rule: one flow transfer can hit performance limitation.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?alpine.BSF.2.11.1407041134300.11883>