On Friday 06 June 2008 14:25, Bruce Evans wrote:
> On Fri, 6 Jun 2008, Marc [iso-8859-1] Lörner wrote:
> > On Friday 06 June 2008 09:52, Peter Jeremy wrote:
> >> I gather from this comment that you have some code using struct tcphdr
> >> that is getting alignment errors. struct tcphdr is extensive
Marc Lörner wrote:
off0 is 0x14 => no problem with that
but address of ip is 0xe00021c8706e => not correct aligned to 32-bits
Can anyone tell me, where ip is allocated, so I can do a little bit more
research?
It really depends on the context! That's a very wide ranging question.
It de
Current FreeBSD problem reports
Critical problems
Serious problems
S Tracker Resp. Description
o kern/27474 net[ipf] [ppp] Interactive use of user PPP and ipfilter c
o kern/35442 net[sis]
The current vimage code adds a handful of new include files..
e.g.
vnet.h for vimage related defines that are related to general
networking stuff
vinet for vimage related defines that are related to inet.
however eventually these defines would move to other files.
For example I think every s
Jun 9 18:23:59 ... kernel: em0: port 0x2000-0x201f mem 0xd802-0xd803,0xd800
-0xd801 irq 18 at device 0.0 on pci4
Jun 9 18:23:59 ... kernel: em0: Using MSI interrupt
Jun 9 18:23:59 ... kernel: em0: Setup of Shared code failed
Jun 9 18:23:59 ... kernel: device_attach: em0 atta
Paul Saab has seen the same. What hardware are you using?
-Kip
On Mon, Jun 9, 2008 at 3:34 PM, <[EMAIL PROTECTED]> wrote:
>
>
>
> Jun 9 18:23:59 ... kernel: em0: Version - 6.7.3> port 0x2000-0x201f mem 0xd802-0xd803,0xd800
> -0xd801 irq 18 at device 0.0 on pci4
> Jun 9 18:23:
[EMAIL PROTECTED] wrote:
Jun 9 18:23:59 ... kernel: em0: port 0x2000-0x201f mem 0xd802-0xd803,0xd800
-0xd801 irq 18 at device 0.0 on pci4
Jun 9 18:23:59 ... kernel: em0: Using MSI interrupt
Jun 9 18:23:59 ... kernel: em0: Setup of Shared code failed
Jun 9 18:23:59 ... kernel
Just a "me, too." Also on a Supermicro board, and it happens on some
boots, but not all.
I used to have this problem, but it went away after upgrading FreeBSD
version (7-stable)
- Andrew
___
freebsd-net@freebsd.org mailing list
http://lists.freebsd
There is more than one problem that results in the same error in the
core driver, the more common one is actually fixed, as Andrew notes,
in the shared code in the latest driver. However, this is a more obscure
bug that occurs on some hardware, and it seems to require that you have
a management BMC
http://yogurt.org/FreeBSD/em.diff
On Mon, Jun 9, 2008 at 6:11 PM, Jack Vogel <[EMAIL PROTECTED]> wrote:
> There is more than one problem that results in the same error in the
> core driver, the more common one is actually fixed, as Andrew notes,
> in the shared code in the latest driver. However,
Bruce M. Simpson wrote:
Archimedes S. Gaviola wrote:
Hi! I have just read from the FreeBSD-7.0 release notes
http://www.freebsd.org/releases/7.0R/relnotes.html that the mrouted
multicast routing protocol (DVMRP implementation) has been removed
from the base system. I want to know what multicas
Just so people understand, you can try this change and if it
eliminates the init failure then use it temporarily.
What the code is, is a way that the driver and BMC have
agreed to use to keep out of eachother's way, but at the
moment the code is flawed, its being actively worked and
I expect new
-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
By default, IPv6 stateless autoconfiguration creates a 64 bit hostid
for each interface based on the mac address (for ethernet, but for us
that's the common case). This is convenient since if you're using RA
neither the user nor the admin has to
13 matches
Mail list logo
