hie
__
Archie Cobbs *Halloo Communications* http://www.halloo.com
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
dr.rcvif' being updated to point to the gif interface.
-Archie
__________
Archie Cobbs * Packet Design * http://www.packetdesign.com
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-stable" in the body of the message
wo
underscores (but I could be wrong about that).
Also, it removes a bunch of backslash contiunations that are not needed.
FYI, this is not an issue in -current.
Thanks,
-Archie
______
Archie Cobbs * Packet Design *
l on
Ack! You're right.. must be brain-dead today.. libpdel hasn't been
rebuilt since upgrading this particular machine to -stable.
Thanks & sorry for the noise...
-Archie
__
Archie Cobbs * Packet Design * http://www.packetdesign.com
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-stable" in the body of the message
oming from.
Any ideas what the problem is?
Thanks,
-Archie
__________
Archie Cobbs * Packet Design * http://www.packetdesign.com
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-stable" in the body of the message
-Archie
______
Archie Cobbs * Packet Design * http://www.packetdesign.com
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-stable" in the body of the message
ly
ignored (although the packet is still dropped).
Try the patch below and see if it helps any..
-Archie
______
Archie Cobbs * Packet Design * http://www.packet
Hi,
Any comments positive or negative to the patch in bin/37614 ?
I'd like to commit this soon...
http://www.freebsd.org/cgi/query-pr.cgi?pr=37614
Thanks,
-Archie
__
Archie Cobbs * Packet Design *
Check
your logs for something like ``"enable chap" required for MPPE''
on one side.
As a workaround, if you are doing CHAP in both directions, try
turning it off in one direction.
-Archie
__
Archie Cobbs
e variable/register for
both 'ifp' and 'node'. So 'node' is NULL, which indicates that
ether_ifattach() was probably never called on this interface.
-Archie
______
Archie Cobbs * Packet Design
rface), yet ether_ifattach()
was never called.. so ng_ether crashes because there's no
node associated with the interface (which there would be had
ether_ifattach() been called).
Maybe a VLAN expert can shed some light?
-Archie
_________
s modules in a different way. The
> much more simple fix which doesn't break binary compatibility is attached.
Great! What's the commit strategy for these?
Would you mind submitting the patch as a followup to ports/21584?
http://www.freebsd.org/cgi/query-pr.cgi?pr=21584
-Archie
__
ue (unless you have an unreasonably
> low maxusers).
Mmm.. I don't understand that.. can you explain?
-Archie
______
Archie Cobbs * Packet Design * http://www.packetdesign.com
To Unsubscribe: send mail to [EMAI
Archie Cobbs writes:
> > I am receiving kernel panics under 4.3-RC #0 when trying to bring up PPPoE.
> > A copy of the kernel debug, the start up and the actual PPP configuration are
> > attached. It appears to be something in the subroutine called fxp_start of
> >
, they would get fragmented.
-Archie
______
Archie Cobbs * Packet Design * http://www.packetdesign.com
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-stable" in the body of the message
indication of
> potential problems...
Another person suggested adding 'reset 1000' and options PNPBIOS.
That seemed to make it work, though not sure which.
By the way, 'reset 1000' is not documented in pccard.conf(5)..
Thanks,
-Archie
___
Archie Cobbs * Whistle Communications, Inc. * http://www.whistle.com
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-stable" in the body of the message
quot;)
pccardd[66]: Assign sio1, io 0x2f8-0x2ff, mem 0x0, 0 bytes, irq 3, flags 0
/kernel: sio1 at port 0x2f8-0x2ff irq 3 slot 1 on pccard1
/kernel: sio1: type 8250
pccard:sio1: U.S. Robotics XJ/CC1336 inserted
Thanks,
-Archie
___
oblem happens with the
3.4-REL GENERIC kernel.
Before this, it was running fine with a 3.0++ kernel and never
had this problem after many power cycles.
Is there any hope in getting this machine to work again??
Howabout disabling DMA? Is there some way to do that?
Thanks for any pointers..
-Archi
18 matches
Mail list logo