Re: ERROR: vxgehal-mgmtaux.c: sou vxge_hal_mrpcim_reg_t has too many members: 1911 > 1023
On Thu Oct 18 03:54:01 UTC 2012, Dennis Glatting wrote:
> While building a kernel, this error was emitted on several compiles:
>
>
> clang -O -pipe -DVXGE_HAL_RX_MULTI_POST -DVXGE_HAL_TX_MULTI_POST
...
> ERROR: vxgehal-mgmtaux.c: sou vxge_hal_mrpcim_reg_t has too many
> members: 1911 > 1023
I just found this posting through a Google search and I couldn't find a
followup or further information. Thus, for the sake of anyone else
searching for this: this error comes from ctfconvert(1), when converting
debug information for a struct or union ("sou") which has more than 1023
members. It looks like the 1023 limit is an inherent limit in the encoding
used by CTF; there's no constant that can just be increased as a workaround.
The error causes ctfconvert(1) to terminate, so the corresponding source
file will end up with no CTF data and hence dtrace will not work correctly.
It looks like vxge_hal_mrpcim_reg_t is the only struct that triggers this
error, so the impact is limited to 16 files in the vxge(4) driver
(Exar/Neterion X3100 10GbE).
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: AAC driver. No kernel error messages for failed raid5?
On Fri, May 16, 2008 at 01:52:50PM -0700, Chris St Denis wrote: > Doesn't seem to work with my IBM ServeRAID 8k > > CLI > open /readonly aac0 > Executing: open /readonly=TRUE "aac0" > Command Error: current controller software.> You can avoid this issue by building a kernel with the latest aac(4) driver from RELENG_6/RELENG_7/HEAD, but you're probably better off just using arcconf instead of aaccli. -Ed ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: AAC driver. No kernel error messages for failed raid5?
On Tue, May 06, 2008 at 12:44:02PM -0700, Chris St Denis wrote: > I pulled out one of the raid5 drives to test the functionality and > noticed that FreeBSD didn't seem to notice the disk failure at all. I > was expecting kernel messages about it, but got nothing. This is missing functionality in the aac(4) driver. For now about the best you can do is regularly poll the status using Adaptec's CLI tool "arcconf." -Ed ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: 6.3 DHCP and static_routes
On Mon, Feb 25, 2008 at 10:30:06AM +0100, Andrea Venturoli wrote: > Ed Maste ha scritto: > > >As of FreeBSD 6.3 dhclient supports RFC3442, the classless static route > >option. If your DHCP server is including this option but not encoding > >the default route using the option you'll have no default route. > > Thanks for the answer; this is in fact my case. > It would be great news if I could get it to work properly! Obviously > repeating the static routes in rc.conf was an hack due to lack of this > support. > > > Now I fiddled with my dhcpd.conf and came up with this: > > option local-route code 121 = string; > option local-route 00:0a:01:02:7f; > option local-route 18:c0:A8:65:0a:01:02:0d; > option local-route 18:c0:A8:67:0a:01:02:0f; > option local-routew code 249 = string; > option local-routew 00:0a:01:02:7f; > option local-routew 18:c0:A8:65:0a:01:02:0d; > option local-routew 18:c0:A8:67:0a:01:02:0f; Yes, the problem is that your local-route option overrides the previous one each time, so only the last one takes effect. You need to put them all together as a single option, probably like option local-route 18:c0:A8:65:0a:01:02:0d:18:c0:A8:67:0a:01:02:0f:00:0a:01:02:7f; and the same for the Windows code 249 version of the option. -Ed ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: 6.3 DHCP and static_routes
On Sat, Feb 23, 2008 at 01:34:54PM +0100, Andrea Venturoli wrote: > This used to work fine with 6.2, with the default route set up by the > DHCP servers. > > After I upgraded to 6.3, I get no default route anymore. This is the > relevant part of my logfile: As of FreeBSD 6.3 dhclient supports RFC3442, the classless static route option. If your DHCP server is including this option but not encoding the default route using the option you'll have no default route. Quoted from RFC 3442: > If the DHCP server returns both a Classless Static Routes option and > a Router option, the DHCP client MUST ignore the Router option. This is my guess as to what you're seeing. If this doesn't solve the issue for you, I'd suggest looking at the DHCP packets with e.g. wireshark. -Ed ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Asus eee (was Re: G4 Quicksilver as Web Server?)
On Tue, Jan 01, 2008 at 06:20:22PM +, James Jeffery wrote: > Before i end the toipic, anyone got any feeback on the Asus Eee (mini > laptops) with FreeBSD? It works, but no drivers exist for the wireless or wired Ethernet ports. The wireless is a newer Atheros part and ath(4) should gain support for it, but I have no idea what the timeline will be. The wired Ethernet is an Atheros (formerly Attansic) L2 10/100, and I'm not aware of any concrete plans for a driver for it. I've used a Linksys USB200M USB ethernet (axe(4) driver) with mine and that works well. -Ed ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Repeated PXE jumpstart
On Fri, Sep 21, 2007 at 09:02:04PM +0100, Jan Grant wrote: > The alternative is to put PXE ahead of the HD in the boot order, and > call back to the deployment host at the end of installation (prior to > reboot) to signal a DHCP reconfiguration. > > It adds a PXE timeout to each boot; the upside is that replacing a > wedging or otherwise broken install is just a matter of reconfiguring a > DHCP server. You could instead load pxegrub and have it boot from the disk instead of waiting for the PXE timeout. Or, if you're willing to accept a network-booted loader, how about just having it load and boot the kernel from the disk? -Ed ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: aaccli doesn't work with AOC-LPZCR2 (Supermicro)
On Tue, Mar 13, 2007 at 10:44:58AM +0100, Thomas Vogt wrote: > FreeBSD (6.2 and Current) boots and works perfectly. Only the storage > control program from port/sysutils/aaccli doesn't work with this > controller. > > aaccli open aac0: > Command Error: current controller software.> Adaptec has a new tool called 'arcconf' that supports the newer firmware and devices. The interface is different to aaccli, and it lacks a few capabilities of aaccli, but should be usable for normal RAID monitoring. Have a look at: http://www.adaptec.com/en-US/speed/raid/storage_manager/arcconf_freebsd_5_6_x86_b16806_tar_gz.htm -Ed Maste ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
