From: James Cutler (bnuqlfl.btzysgkoyo@citta-america.com)
Date: Thu Apr 25 2002 - 03:54:52 EEST
Is there anything special that needs to be done to configure for the
2.4.18 kernel? I'm using the following commands to configure it and it
doesn't seem to be doing the trick (though they work under 2.4.17)
insmod parport
insmod parport_pc io=0x378 irq=7
modprobe baycom_par mode="picpar" iobase=0x378
sethdlc -i bcp0 -p mode "picpar" io 0x378
axparms -setcall bcp0 kf6rfx-1
ifconfig bcp0 192.168.2.2 up
On Tue, 23 Apr 2002, Jeroen Vreeken wrote:
> On 2002.04.23 06:04:32 +0200 James Cutler wrote:
> > We're having some problems using a BayPac 9600 with Linux 2.4.17.
> >
> > On one machine it works just fine until we start X. As soon as we
> > start X, the machine will crash as soon as we send an AX.25 packet
> > (we were testing with "beacon"). The only way to recover from the
> > crash is to power cycle or press the reset button. This is
> > repeatable. We beacon, we work, we start X, we beacon, we crash.
> > It does output the packet before it crashes.
> >
> > On a second machine that doesn't (can't) run X, we've noticed a
> > similar crash. It's a small embedded 486 (the Prometheus). After
> > several beacons, from 5-20, it will crash in the same hard manner.
> > Only a power cycle will fix it.
> >
> > Has anyone else seen similar behavior? Any ideas?
>
> Every 2.4.x kernel up to 2.4.18 has this problem, it should be fixed now...
> It was a problem with ax25 not using sock_orphan()
>
> Jeroen
>
>
>
-
To unsubscribe from this list: send the line "unsubscribe linux-hams" in
the body of a message to nqrzmpe.pcirv@udallas.edu
More majordomo info at http://vger.kernel.org/majordomo-info.html
This archive was generated by hypermail 2b30 : Thu Apr 25 2002 - 04:16:07 EEST