From owner-freebsd-embedded@FreeBSD.ORG Mon Jun 3 11:06:43 2013 Return-Path: Delivered-To: freebsd-embedded@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 43877582 for ; Mon, 3 Jun 2013 11:06:43 +0000 (UTC) (envelope-from owner-bugmaster@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:1900:2254:206c::16:87]) by mx1.freebsd.org (Postfix) with ESMTP id 3536413A5 for ; Mon, 3 Jun 2013 11:06:43 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.7/8.14.7) with ESMTP id r53B6hAJ014974 for ; Mon, 3 Jun 2013 11:06:43 GMT (envelope-from owner-bugmaster@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.7/8.14.7/Submit) id r53B6g3d014972 for freebsd-embedded@FreeBSD.org; Mon, 3 Jun 2013 11:06:42 GMT (envelope-from owner-bugmaster@FreeBSD.org) Date: Mon, 3 Jun 2013 11:06:42 GMT Message-Id: <201306031106.r53B6g3d014972@freefall.freebsd.org> X-Authentication-Warning: freefall.freebsd.org: gnats set sender to owner-bugmaster@FreeBSD.org using -f From: FreeBSD bugmaster To: freebsd-embedded@FreeBSD.org Subject: Current problem reports assigned to freebsd-embedded@FreeBSD.org X-BeenThere: freebsd-embedded@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Dedicated and Embedded Systems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 03 Jun 2013 11:06:43 -0000 Note: to view an individual PR, use: http://www.freebsd.org/cgi/query-pr.cgi?pr=(number). The following is a listing of current problems submitted by FreeBSD users. These represent problem reports covering all versions including experimental development code and obsolete releases. S Tracker Resp. Description -------------------------------------------------------------------------------- o kern/177878 embedded [rtl8366rb] [patch] Update rtl8366rb switch driver to o bin/177873 embedded [patch] etherswitchcfg(): Change the per port vlangrou o bin/177872 embedded [patch] etherswitchcfg(8) crashes if called with no ar o bin/177871 embedded [patch] etherswitchcfg(8): uninitialized variable whil o kern/172968 embedded [arge] probe/attach occasionally fails to find a PHY o misc/52256 embedded [picobsd] picobsd build script does not read in user/s o kern/42728 embedded [picobsd] many problems in src/usr.sbin/ppp/* after c 7 problems total. From owner-freebsd-embedded@FreeBSD.ORG Tue Jun 4 08:39:47 2013 Return-Path: Delivered-To: freebsd-embedded@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id C463E410 for ; Tue, 4 Jun 2013 08:39:47 +0000 (UTC) (envelope-from njwilliams@swin.edu.au) Received: from gpo4.cc.swin.edu.au (gpo4.cc.swin.edu.au [136.186.1.33]) by mx1.freebsd.org (Postfix) with ESMTP id 482A911E2 for ; Tue, 4 Jun 2013 08:39:46 +0000 (UTC) Received: from [136.186.229.154] (nwilliams-laptop.caia.swin.edu.au [136.186.229.154]) by gpo4.cc.swin.edu.au (8.14.3/8.14.3) with ESMTP id r548dEQi021069 for ; Tue, 4 Jun 2013 18:39:35 +1000 Message-ID: <51ADA7AD.3060508@swin.edu.au> Date: Tue, 04 Jun 2013 18:39:09 +1000 From: Nigel Williams User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130329 Thunderbird/17.0.5 MIME-Version: 1.0 To: freebsd-embedded@freebsd.org Subject: No usable event timer, FreeBSD Current, PCEngines WRAP Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-embedded@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Dedicated and Embedded Systems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 04 Jun 2013 08:39:47 -0000 Hi, I'm attempting to run FreeBSD-10 CURRENT (built using nanoBSD) on a PC-Engines WRAP device, and encounter the following during boot: "panic: No usable event timer found!" after which the machine reboots. I have been able to run pfSense 2.0.1 (bsd 8.1) and it appears to find the i8254 timer. The verbose boot output: https://docs.google.com/file/d/0B9KWjvUN8efvQ0RMNXRzRS1rS0k/edit?usp=sharing Kernel conf: https://docs.google.com/file/d/0B9KWjvUN8efvLUpRekJORWhmSFE/edit?usp=sharing nanoBSD conf: https://docs.google.com/file/d/0B9KWjvUN8efvTzIya3pNUXc5elk/edit?usp=sharing any suggestions? cheers, nigel From owner-freebsd-embedded@FreeBSD.ORG Tue Jun 4 15:21:40 2013 Return-Path: Delivered-To: freebsd-embedded@FreeBSD.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id C5D3BCD0 for ; Tue, 4 Jun 2013 15:21:40 +0000 (UTC) (envelope-from ian@FreeBSD.org) Received: from mho-01-ewr.mailhop.org (mho-03-ewr.mailhop.org [204.13.248.66]) by mx1.freebsd.org (Postfix) with ESMTP id A11241893 for ; Tue, 4 Jun 2013 15:21:37 +0000 (UTC) Received: from c-24-8-230-52.hsd1.co.comcast.net ([24.8.230.52] helo=damnhippie.dyndns.org) by mho-01-ewr.mailhop.org with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.72) (envelope-from ) id 1Ujt3C-000N1j-UW; Tue, 04 Jun 2013 15:21:31 +0000 Received: from [172.22.42.240] (revolution.hippie.lan [172.22.42.240]) by damnhippie.dyndns.org (8.14.3/8.14.3) with ESMTP id r54FLQGg015640; Tue, 4 Jun 2013 09:21:26 -0600 (MDT) (envelope-from ian@FreeBSD.org) X-Mail-Handler: Dyn Standard SMTP by Dyn X-Originating-IP: 24.8.230.52 X-Report-Abuse-To: abuse@dyndns.com (see http://www.dyndns.com/services/sendlabs/outbound_abuse.html for abuse reporting information) X-MHO-User: U2FsdGVkX18K0jsl+S+m2fTvevMs1GJ1 Subject: Re: No usable event timer, FreeBSD Current, PCEngines WRAP From: Ian Lepore To: Nigel Williams In-Reply-To: <51ADA7AD.3060508@swin.edu.au> References: <51ADA7AD.3060508@swin.edu.au> Content-Type: text/plain; charset="us-ascii" Date: Tue, 04 Jun 2013 09:21:26 -0600 Message-ID: <1370359286.1258.102.camel@revolution.hippie.lan> Mime-Version: 1.0 X-Mailer: Evolution 2.32.1 FreeBSD GNOME Team Port Content-Transfer-Encoding: 7bit Cc: freebsd-embedded@FreeBSD.org X-BeenThere: freebsd-embedded@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Dedicated and Embedded Systems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 04 Jun 2013 15:21:40 -0000 On Tue, 2013-06-04 at 18:39 +1000, Nigel Williams wrote: > Hi, > > I'm attempting to run FreeBSD-10 CURRENT (built using nanoBSD) on a > PC-Engines WRAP device, and encounter the following during boot: "panic: > No usable event timer found!" after which the machine reboots. I have > been able to run pfSense 2.0.1 (bsd 8.1) and it appears to find the > i8254 timer. > > The verbose boot output: > https://docs.google.com/file/d/0B9KWjvUN8efvQ0RMNXRzRS1rS0k/edit?usp=sharing > > Kernel conf: > https://docs.google.com/file/d/0B9KWjvUN8efvLUpRekJORWhmSFE/edit?usp=sharing > > nanoBSD conf: > https://docs.google.com/file/d/0B9KWjvUN8efvTzIya3pNUXc5elk/edit?usp=sharing > > any suggestions? The problem does seem to be that the i8254 (atrtc) device isn't instantiated. I'm not sure whether the acpi errors at the start are innocuous warnings or the cause of the problem (it has ever been thus with acpi -- you report an error message on a mailing list and the response is often "that's normal, you can ignore it"). The atrtc device should be found via PNP data or /boot/device.hints if not via acpi. Perhaps acpi is working "enough" that it thinks it should be using it, but not enough to find the timer. You could try "set hint.acpi.0.disabled=1" at the loader prompt and see if that changes anything. If it does, I'd call it more of a workaround than a fix. -- Ian From owner-freebsd-embedded@FreeBSD.ORG Tue Jun 4 15:49:00 2013 Return-Path: Delivered-To: freebsd-embedded@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 104419A6; Tue, 4 Jun 2013 15:49:00 +0000 (UTC) (envelope-from freebsd-embedded@dino.sk) Received: from mailhost.netlab.sk (mailhost.netlab.sk [84.245.65.10]) by mx1.freebsd.org (Postfix) with ESMTP id 78A4719CB; Tue, 4 Jun 2013 15:48:58 +0000 (UTC) Received: from zeta.dino.sk (fw1.dino.sk [84.245.95.252]) (AUTH: LOGIN milan, TLS: TLSv1/SSLv3,128bits,AES128-SHA) by mailhost.netlab.sk with ESMTPSA; Tue, 04 Jun 2013 17:43:15 +0200 id 0064FC0E.51AE0B13.00017275 Date: Tue, 4 Jun 2013 17:43:09 +0200 From: Milan Obuch To: Ian Lepore Subject: Re: No usable event timer, FreeBSD Current, PCEngines WRAP Message-ID: <20130604174309.676f1229@zeta.dino.sk> In-Reply-To: <1370359286.1258.102.camel@revolution.hippie.lan> References: <51ADA7AD.3060508@swin.edu.au> <1370359286.1258.102.camel@revolution.hippie.lan> X-Mailer: Claws Mail 3.9.1 (GTK+ 2.24.18; amd64-portbld-freebsd9.1) Face: iVBORw0KGgoAAAANSUhEUgAAADAAAAAwBAMAAAClLOS0AAAAGFBMVEX+/v7++v6YOTrq8PCcuIX989UvOSj++v0BNCbpAAAAB3RJTUUHsQwfFzs7RBhzUQAAAhJJREFUOI1dU8GOqzAMNKIoV1bvwD1i0ysqrHplIdBrVSX7ATSbd03VVvn9tQNtQy0hjAdn7LED4AAcPtWm9RV+MPSfxhBLx9ajd6X/ngB6/mTwnRSZua7i7Ca+0ctZKo4Qmz+JY13X6I3nFZBxIYW1PbgfQ5RP8g0XlltEWGf3cV03joYpRnFbvYDKbXjZlXyyhEZA4lI+cN3NaVXE4VKjSwTExO10eTEkkJVqIAD5z0nUBQJluQDRSQjcrBiHAJxZlAH5CUMBMC7OcJ4LMQNnxhZ1HYPscMc6J4UlWRMNwzOpCcAHKSICd1EDn83abdREIbXsHkD1OinP1aCUCOEVRaa1lMcvywUWdYgk13JQUpYNKmvXQ8Kw5ML9YI5h8SakctBc7E/IYuLhYd/zZIk+1gM1vNweQBvHE0j+oYah3sMqAytQYlZk6+ANaaawJdu3OFzYGMZ3iGpa3qMlq9ZH0VZTgrCtw/ngdYkEIIpSbP1bWQAdFdX9vocBdkH2qVjVmuMu3gI5rjs814EUdrCZgWlPaxZZ3RiLFUtr+ud0PXwp2dnQSNXgePt6AZpBj6UMJ7VQkzN4utVeaSW1Dhn/kblGrKeMvNGnzwX4zuEDarYz1KdPtR60Gul0Gued+515SJXhCsl+Tx/3kY/UDvicPll9mfu50t3tvQ/thZpJYgeuwdSKNJ6tCD98MCgoxLDaPxbwqqwPWaWiAAAAAElFTkSuQmCC X-Face: ak5rwz4-aUa>hPFZlcg,bXxn.(TN}e9DGFrKU\.i_'B[&5=pAd9o"j)5VSUYW:BRQG#^42Ev$Il|; Ztn=,C X-Operating-System: FreeBSD/amd64 8.2-STABLE Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: freebsd-embedded@FreeBSD.org X-BeenThere: freebsd-embedded@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Dedicated and Embedded Systems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 04 Jun 2013 15:49:00 -0000 On Tue, 04 Jun 2013 09:21:26 -0600 Ian Lepore wrote: > On Tue, 2013-06-04 at 18:39 +1000, Nigel Williams wrote: > > Hi, > > > > I'm attempting to run FreeBSD-10 CURRENT (built using nanoBSD) on a > > PC-Engines WRAP device, and encounter the following during boot: > > "panic: No usable event timer found!" after which the machine > > reboots. I have been able to run pfSense 2.0.1 (bsd 8.1) and it > > appears to find the i8254 timer. > > > > The verbose boot output: > > https://docs.google.com/file/d/0B9KWjvUN8efvQ0RMNXRzRS1rS0k/edit?usp=sharing > > > > Kernel conf: > > https://docs.google.com/file/d/0B9KWjvUN8efvLUpRekJORWhmSFE/edit?usp=sharing > > > > nanoBSD conf: > > https://docs.google.com/file/d/0B9KWjvUN8efvTzIya3pNUXc5elk/edit?usp=sharing > > > > any suggestions? > > The problem does seem to be that the i8254 (atrtc) device isn't > instantiated. I'm not sure whether the acpi errors at the start are > innocuous warnings or the cause of the problem (it has ever been thus > with acpi -- you report an error message on a mailing list and the > response is often "that's normal, you can ignore it"). > > The atrtc device should be found via PNP data or /boot/device.hints if > not via acpi. Perhaps acpi is working "enough" that it thinks it > should be using it, but not enough to find the timer. > > You could try "set hint.acpi.0.disabled=1" at the loader prompt and > see if that changes anything. If it does, I'd call it more of a > workaround than a fix. > > -- Ian > WRAPs do not have acpi, so I have no 'device acpi' in kernel config for them. It is not necessary to have 'cpu I486_CPU' and 'cpu I686_CPU' in kernel config, by the way... I use small configuration cpu I586_CPU options CPU_GEODE ident GEODE makeoptions DEBUG=-g makeoptions WITHOUT_MODULES="..." options SCHED_ULE options PREEMPTION options INET options FFS options SOFTUPDATES options UFS_ACL options UFS_DIRHASH options UFS_GJOURNAL options QUOTA options MSDOSFS options CD9660 options PROCFS options PSEUDOFS options SCSI_DELAY=5000 options KTRACE options STACK options SYSVSHM options SYSVMSG options SYSVSEM options _KPOSIX_PRIORITY_SCHEDULING options PRINTF_BUFR_SIZE=128 options INCLUDE_CONFIG_FILE options KDB options KDB_TRACE options SMP device apic device cpufreq device pci device ahci device ata options ATA_STATIC_ID device scbus device da device pass device pmtimer device uart device loop device random device ether device md device bpf and load if_sis from module (and some other modules too). What's in your /boot/device.hints file? I think following is relevant: hint.atrtc.0.at="isa" hint.atrtc.0.port="0x70" hint.atrtc.0.irq="8" At least when I comment these lines out, I get the same 'panic: no usable event timer found' error. Regards, Milan From owner-freebsd-embedded@FreeBSD.ORG Wed Jun 5 10:24:25 2013 Return-Path: Delivered-To: freebsd-embedded@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id D2A3379F; Wed, 5 Jun 2013 10:24:25 +0000 (UTC) (envelope-from njwilliams@swin.edu.au) Received: from gpo4.cc.swin.edu.au (gpo4.cc.swin.edu.au [136.186.1.33]) by mx1.freebsd.org (Postfix) with ESMTP id 6DC801007; Wed, 5 Jun 2013 10:24:25 +0000 (UTC) Received: from [136.186.229.154] (nwilliams-laptop.caia.swin.edu.au [136.186.229.154]) by gpo4.cc.swin.edu.au (8.14.3/8.14.3) with ESMTP id r55AN7D0002148; Wed, 5 Jun 2013 20:23:07 +1000 Message-ID: <51AF1185.5090304@swin.edu.au> Date: Wed, 05 Jun 2013 20:23:01 +1000 From: Nigel Williams User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130329 Thunderbird/17.0.5 MIME-Version: 1.0 To: Milan Obuch Subject: Re: No usable event timer, FreeBSD Current, PCEngines WRAP References: <51ADA7AD.3060508@swin.edu.au> <1370359286.1258.102.camel@revolution.hippie.lan> <20130604174309.676f1229@zeta.dino.sk> In-Reply-To: <20130604174309.676f1229@zeta.dino.sk> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-embedded@FreeBSD.org, Ian Lepore X-BeenThere: freebsd-embedded@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Dedicated and Embedded Systems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 05 Jun 2013 10:24:25 -0000 Hi Milan, Ian, Thanks for the suggestions. After checking device.hints and removing acpi, I was still getting the same error. I decided to look at the nanoBSD conf file I was using, and it turned out the problem was in there. Here's the solution in case anyone else has the same problem. I had included the line "WITHOUT_FORTH" in the nanBSD config file (specified with -c the_file.conf), which was preventing the loader from running device.hints on boot (and thus causing the panic later down the line). Removing this line fixed the issue. However in the end I left WITHOUT_FORTH in the nanoBSD config and statically included the hints in the kernel config file with the line: hints "GENERIC.hints" cheers, nigel On 05/06/13 01:43, Milan Obuch wrote: > On Tue, 04 Jun 2013 09:21:26 -0600 > Ian Lepore wrote: > >> On Tue, 2013-06-04 at 18:39 +1000, Nigel Williams wrote: >>> Hi, >>> >>> I'm attempting to run FreeBSD-10 CURRENT (built using nanoBSD) on a >>> PC-Engines WRAP device, and encounter the following during boot: >>> "panic: No usable event timer found!" after which the machine >>> reboots. I have been able to run pfSense 2.0.1 (bsd 8.1) and it >>> appears to find the i8254 timer. >>> >>> The verbose boot output: >>> https://docs.google.com/file/d/0B9KWjvUN8efvQ0RMNXRzRS1rS0k/edit?usp=sharing >>> >>> Kernel conf: >>> https://docs.google.com/file/d/0B9KWjvUN8efvLUpRekJORWhmSFE/edit?usp=sharing >>> >>> nanoBSD conf: >>> https://docs.google.com/file/d/0B9KWjvUN8efvTzIya3pNUXc5elk/edit?usp=sharing >>> >>> any suggestions? >> >> The problem does seem to be that the i8254 (atrtc) device isn't >> instantiated. I'm not sure whether the acpi errors at the start are >> innocuous warnings or the cause of the problem (it has ever been thus >> with acpi -- you report an error message on a mailing list and the >> response is often "that's normal, you can ignore it"). >> >> The atrtc device should be found via PNP data or /boot/device.hints if >> not via acpi. Perhaps acpi is working "enough" that it thinks it >> should be using it, but not enough to find the timer. >> >> You could try "set hint.acpi.0.disabled=1" at the loader prompt and >> see if that changes anything. If it does, I'd call it more of a >> workaround than a fix. >> >> -- Ian >> > > WRAPs do not have acpi, so I have no 'device acpi' in kernel config for > them. It is not necessary to have 'cpu I486_CPU' and 'cpu I686_CPU' in > kernel config, by the way... I use small configuration > > cpu I586_CPU > options CPU_GEODE > ident GEODE > makeoptions DEBUG=-g > makeoptions WITHOUT_MODULES="..." > options SCHED_ULE > options PREEMPTION > options INET > options FFS > options SOFTUPDATES > options UFS_ACL > options UFS_DIRHASH > options UFS_GJOURNAL > options QUOTA > options MSDOSFS > options CD9660 > options PROCFS > options PSEUDOFS > options SCSI_DELAY=5000 > options KTRACE > options STACK > options SYSVSHM > options SYSVMSG > options SYSVSEM > options _KPOSIX_PRIORITY_SCHEDULING > options PRINTF_BUFR_SIZE=128 > options INCLUDE_CONFIG_FILE > options KDB > options KDB_TRACE > options SMP > device apic > device cpufreq > device pci > device ahci > device ata > options ATA_STATIC_ID > device scbus > device da > device pass > device pmtimer > device uart > device loop > device random > device ether > device md > device bpf > > and load if_sis from module (and some other modules too). > > What's in your /boot/device.hints file? I think following is relevant: > > hint.atrtc.0.at="isa" > hint.atrtc.0.port="0x70" > hint.atrtc.0.irq="8" > > At least when I comment these lines out, I get the same 'panic: no > usable event timer found' error. > > Regards, > Milan > From owner-freebsd-embedded@FreeBSD.ORG Sat Jun 8 20:26:42 2013 Return-Path: Delivered-To: freebsd-embedded@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 1E055A40; Sat, 8 Jun 2013 20:26:42 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-qc0-x22d.google.com (mail-qc0-x22d.google.com [IPv6:2607:f8b0:400d:c01::22d]) by mx1.freebsd.org (Postfix) with ESMTP id C9FFC1275; Sat, 8 Jun 2013 20:26:41 +0000 (UTC) Received: by mail-qc0-f173.google.com with SMTP id l10so1519871qcy.32 for ; Sat, 08 Jun 2013 13:26:41 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:cc:content-type; bh=Aoc/seofhqAoWz7/xV2BoofhIEMuEzBVBYf1rqEqinY=; b=w9oZhLB8EDYweoToOyOHq/itX46kXFDDoKew61OyWPL3r48DeCPYD/KX1z3psOBfmj Q/0SHvyyFRiPy+ukKSx+OjHZO6z3kMcW3mRK8VwHOToWgkZj5XN5cZkOwd1VKFe/LuFu UYBUpY3XwJHiSkm8yzX2x2Pi8jxExP3+XWACVcU7ZOq/vrlitLUywAQ4VibTr7W1eKIB H8lebjEMpTKoFamEzc4s/g6dWpQfeoTegJ31m3X3WOzeuB9prFXlVLYevxUwXifO0El4 /k5pYdfRBBhjzbeHnvexf3I10tMybp7mR+/TH8KUaV9TwEMZZw7FBnEGboNiGk4PGswS L6KQ== MIME-Version: 1.0 X-Received: by 10.49.49.167 with SMTP id v7mr4522350qen.10.1370723201261; Sat, 08 Jun 2013 13:26:41 -0700 (PDT) Received: by 10.224.5.65 with HTTP; Sat, 8 Jun 2013 13:26:41 -0700 (PDT) Date: Sat, 8 Jun 2013 13:26:41 -0700 Message-ID: Subject: etherswitch regression? From: Adrian Chadd To: Luiz Otavio O Souzau Content-Type: text/plain; charset=ISO-8859-1 Cc: Aleksandr Rybalko , freebsd-embedded@freebsd.org X-BeenThere: freebsd-embedded@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Dedicated and Embedded Systems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 08 Jun 2013 20:26:42 -0000 Hi guys, I've noticed this regression: # etherswitchcfg etherswitchcfg: ioctl(IOETHERSWITCHGETINFO): Inappropriate ioctl for device Is this just a userland mismatch? or? adrian