Serial driver problem (modem Lombard)

Serial driver problem (modem Lombard)

[Bernhard Reiter]

[-- Attachment #1: Type: text/plain, Size: 917 bytes --]

There is a difference in modem device behaviour
between 2.2.15pre3(coming with LinuxPPC2000) and 2.2.15pre19(after 
Paul M's stable tree, build myself using his .config).

wvdail cannot open /dev/ttyS0 twice with 2.2.51pre19.
After I ctrl-ced wvdial to interrupt the network connection
I get an I/O error when I try to open it again.

Running wvdialconf it started scanning ttyS1 and
then jumped into the system monitor:

vector:200 at pc=d0849344 msr=1030, sp=c7bf3ce0 [c7bf3ce0]
current=c7bf2000, pid 745 comm=insmod

Maybe that is an irport error and unrelated to the first problem.
I have not enquired further, though.

Regards,
	Bernhard
ps: Please carbon copy relevant replies to me.
-- 
Professional Service around Free Software                (intevation.net)  
The FreeGIS Project				            (freegis.org)
Association for a Free Informational Infrastructure            (ffii.org)

[-- Attachment #2: Type: application/pgp-signature, Size: 236 bytes --]

Re: Serial driver problem (modem Lombard)

[Michael Schmitz]

> Running wvdialconf it started scanning ttyS1 and
> then jumped into the system monitor:
>
> vector:200 at pc=d0849344 msr=1030, sp=c7bf3ce0 [c7bf3ce0]
> current=c7bf2000, pid 745 comm=insmod

Looks like it happens when inserting a module. Can you try to compile in
the serial driver, instead of building it as a module?

	Michael


** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

Re: Serial driver problem (modem Lombard)

[Andreas Tobler]

[-- Attachment #1: Type: text/plain, Size: 1836 bytes --]



Bernhard Reiter wrote:
>
> There is a difference in modem device behaviour
> between 2.2.15pre3(coming with LinuxPPC2000) and 2.2.15pre19(after
> Paul M's stable tree, build myself using his .config).
>
Depends on how you got the 2.2.15p19, I had some difficulties due to the
fact that I was too fast. Paul did a backport of ppp-2.4.x to 2.2.x and
I rsynced it with the auvz --delete option; In the wrong moment!!!. But
it wasn't meant for 2.2.x.

So only a clean download helped me. (not all the stuff, only with the -u
disabled (update == looks for date))

Now I can report a clean, more or less, well ppp operation.


> wvdail cannot open /dev/ttyS0 twice with 2.2.51pre19.
> After I ctrl-ced wvdial to interrupt the network connection
> I get an I/O error when I try to open it again.

Do you have the module option in char/devices/serial on? (dumb serial device)
If so, it can tend to a machine check, when you load a module. The patch
below will/could help you maybe. I never got as far to include it into
the kernel stuff....(Paul/Ben?)

>
> Running wvdialconf it started scanning ttyS1 and
> then jumped into the system monitor:

Don't know about a lombard, but a wallstreet has 4 tty's 0,1,2,3
(serial/printer =0, IRDA =1, modem =2; which is not present in my case;
third = 3, the third is unused, I think the lombard has only one SCC so
you can change the SERIAL_DEV_OFFSET to 2 iso 4.
>
> vector:200 at pc=d0849344 msr=1030, sp=c7bf3ce0 [c7bf3ce0]
> current=c7bf2000, pid 745 comm=insmod
>
> Maybe that is an irport error and unrelated to the first problem.
> I have not enquired further, though.

So as for trial and error I'd suggest to disable some serial modules.


> Regards,
>         Bernhard
> ps: Please carbon copy relevant replies to me.

CC? or reply?

Regards,

these are my to RP. (chf exchange.....)

Andreas

[-- Attachment #2: Unknown Document --]
[-- Type: text/plain, Size: 2122 bytes --]

--- linux-pmac-stable/drivers/char/serial.c	Tue Feb  8 00:46:49 2000
+++ linux/drivers/char/serial.c	Mon Feb 14 18:35:47 2000
@@ -150,6 +150,12 @@
 #include <asm/bitops.h>
 #include <asm/serial.h>

+#ifdef CONFIG_MAC_SERIAL
+#define SERIAL_DEV_OFFSET	4
+#else
+#define SERIAL_DEV_OFFSET	0
+#endif
+
 #ifdef SERIAL_INLINE
 #define _INLINE_ inline
 #endif
@@ -3126,7 +3132,7 @@
 	serial_driver.driver_name = "serial";
 	serial_driver.name = "ttyS";
 	serial_driver.major = TTY_MAJOR;
-	serial_driver.minor_start = 64;
+	serial_driver.minor_start = 64 + SERIAL_DEV_OFFSET;
 	serial_driver.num = NR_PORTS;
 	serial_driver.type = TTY_DRIVER_TYPE_SERIAL;
 	serial_driver.subtype = SERIAL_TYPE_NORMAL;
@@ -3190,11 +3196,14 @@
 		state->icount.frame = state->icount.parity = 0;
 		state->icount.overrun = state->icount.brk = 0;
 		state->irq = irq_cannonicalize(state->irq);
+#ifndef CONFIG_PMAC	/* XXX */
 		if (check_region(state->port,8))
 			continue;
 		if (state->flags & ASYNC_BOOT_AUTOCONF)
 			autoconfig(state);
+#endif
 	}
+#ifndef CONFIG_PMAC	/* XXX */
 	/*
 	 * Detect the IRQ only once every port is initialised,
 	 * because some 16450 do not reset to 0 the MCR register.
@@ -3212,6 +3221,7 @@
 		       state->port, state->irq,
 		       uart_config[state->type].name);
 	}
+#endif
 	return 0;
 }

@@ -3264,22 +3274,22 @@
 		state->irq = detect_uart_irq(state);

 	printk(KERN_INFO "tty%02d at 0x%04x (irq = %d) is a %s\n",
-	       state->line, state->port, state->irq,
+	       state->line + SERIAL_DEV_OFFSET, state->port, state->irq,
 	       uart_config[state->type].name);
-	return state->line;
+	return state->line + SERIAL_DEV_OFFSET;
 }

 void unregister_serial(int line)
 {
 	unsigned long flags;
-	struct serial_state *state = &rs_table[line];
+	struct serial_state *state = &rs_table[line + SERIAL_DEV_OFFSET];

 	save_flags(flags);
 	cli();
 	if (state->info && state->info->tty)
 		tty_hangup(state->info->tty);
 	state->type = PORT_UNKNOWN;
-	printk(KERN_INFO "tty%02d unloaded\n", state->line);
+	printk(KERN_INFO "tty%02d unloaded\n", state->line + SERIAL_DEV_OFFSET);
 	restore_flags(flags);
 }

Re: Serial driver problem (modem Lombard)

[unit]

On Sat, 22 Apr 2000, Andreas Tobler wrote:

i've also been having problems with ppp and kernels > 2.2.15pre9
somewhat similar to below .. only with hard crashes. I can't get
ppp to work w/ either prre17 or pre19 .. seems to be line dicipline:

Apr 16 18:34:05 sophix pppd[2541]: Serial connection established.
Apr 16 18:34:05 sophix modprobe: can't locate module tty-ldisc-3
Apr 16 18:34:05 sophix pppd[2541]: ioctl(TIOCSETD): Invalid argument(22)
Apr 16 18:34:05 sophix pppd[2541]: Hangup (SIGHUP)
Apr 16 18:34:05 sophix pppd[2541]: Exit.

w/ 2.2.15pre14 i can connect but if i reconnect linux crashes w/ no
option other than a force reboot (this has happened on three occasions
under the exact same circumstances).

> Bernhard Reiter wrote:
> >
> > There is a difference in modem device behaviour
> > between 2.2.15pre3(coming with LinuxPPC2000) and 2.2.15pre19(after
> > Paul M's stable tree, build myself using his .config).
> >
> Depends on how you got the 2.2.15p19, I had some difficulties due to the
> fact that I was too fast. Paul did a backport of ppp-2.4.x to 2.2.x and
> I rsynced it with the auvz --delete option; In the wrong moment!!!. But
> it wasn't meant for 2.2.x.
>
> So only a clean download helped me. (not all the stuff, only with the -u
> disabled (update == looks for date))

i rsynced the pre19 two days back so i'm not sure where i fall into the
loop. However it would seem the/my problem is further back

> Now I can report a clean, more or less, well ppp operation.

> > wvdail cannot open /dev/ttyS0 twice with 2.2.51pre19.
> > After I ctrl-ced wvdial to interrupt the network connection
> > I get an I/O error when I try to open it again.

> Do you have the module option in char/devices/serial on? (dumb serial device)
> If so, it can tend to a machine check, when you load a module. The patch
> below will/could help you maybe. I never got as far to include it into
> the kernel stuff....(Paul/Ben?)

> > Running wvdialconf it started scanning ttyS1 and
> > then jumped into the system monitor:
>
> Don't know about a lombard, but a wallstreet has 4 tty's 0,1,2,3
> (serial/printer =0, IRDA =1, modem =2; which is not present in my case;
> third = 3, the third is unused, I think the lombard has only one SCC so
> you can change the SERIAL_DEV_OFFSET to 2 iso 4.
> >
> > vector:200 at pc=d0849344 msr=1030, sp=c7bf3ce0 [c7bf3ce0]
> > current=c7bf2000, pid 745 comm=insmod
> >
> > Maybe that is an irport error and unrelated to the first problem.
> > I have not enquired further, though.
>
> So as for trial and error I'd suggest to disable some serial modules.


** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

Re: Serial driver problem (modem Lombard)

[Andreas Tobler]

unit@panix.com wrote:
>
> On Sat, 22 Apr 2000, Andreas Tobler wrote:
>
> i've also been having problems with ppp and kernels > 2.2.15pre9
> somewhat similar to below .. only with hard crashes. I can't get
> ppp to work w/ either prre17 or pre19 .. seems to be line dicipline:
>
> Apr 16 18:34:05 sophix pppd[2541]: Serial connection established.
> Apr 16 18:34:05 sophix modprobe: can't locate module tty-ldisc-3
> Apr 16 18:34:05 sophix pppd[2541]: ioctl(TIOCSETD): Invalid argument(22)
> Apr 16 18:34:05 sophix pppd[2541]: Hangup (SIGHUP)
> Apr 16 18:34:05 sophix pppd[2541]: Exit.

Have you built in ppp support or module support?
If you have mod, then have you added the lines below to
/etc/modules.conf or conf.modules?

alias   ppp-compress-21         bsd_comp
alias   ppp-compress-24         ppp_deflate
alias   ppp-compress-26         ppp_deflate
alias   tty-ldisc-3             ppp

Which ppp-pkg are you using? I use ppp-2.4.0b2, but ppp-2.3.11 should
also work fine.
(ftp.linuxcare.com.au/pub/ppp)

>
> w/ 2.2.15pre14 i can connect but if i reconnect linux crashes w/ no
> option other than a force reboot (this has happened on three occasions
> under the exact same circumstances).

How do you connect? I use netcfg. No problems so far.

> i rsynced the pre19 two days back so i'm not sure where i fall into the
> loop. However it would seem the/my problem is further back

Be sure not having something like ppp_async/ppp_generic in drivers/net/.
If so you may have the same situation I had.
rsync -avz linuxcare.com.au:linux-pmac-stable <dest-dir> should help to
get a clean download.

Otherwise???

Andreas


** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

Re: Serial driver problem (modem Lombard)

[unit]

On Mon, 24 Apr 2000, Andreas Tobler wrote:

> Which ppp-pkg are you using? I use ppp-2.4.0b2, but ppp-2.3.11 should
> also work fine.

 ppp-2.3.10

> > w/ 2.2.15pre14 i can connect but if i reconnect linux crashes w/ no
> > option other than a force reboot (this has happened on three occasions
> > under the exact same circumstances).

> > i rsynced the pre19 two days back so i'm not sure where i fall into the
> > loop. However it would seem the/my problem is further back
>
> Be sure not having something like ppp_async/ppp_generic in drivers/net/.
> If so you may have the same situation I had.
> rsync -avz linuxcare.com.au:linux-pmac-stable <dest-dir> should help to
> get a clean download.

Andreas .. that was indeed the case .. and i've since re synced from an
older tarball. ppp is now working .. however the hard crashes persist ..
always when i disconnect and reconnect .. once the handshaking is done
the machine locks (no console nothing) and a minute or so later the
machine restarts. I'll try updating ppp but i'm thinking it is maybe a
kernel issue

thanks for your responce

cal-s


** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

Re: Serial driver problem (modem Lombard)

[Bernhard Reiter]

[-- Attachment #1: Type: text/plain, Size: 2456 bytes --]

On Sat, Apr 22, 2000 at 06:17:37PM +0200, Andreas Tobler wrote:
> Bernhard Reiter wrote:

> > There is a difference in modem device behaviour
> > between 2.2.15pre3(coming with LinuxPPC2000) and 2.2.15pre19(after
> > Paul M's stable tree, build myself using his .config).
> > 
> Depends on how you got the 2.2.15p19, I had some difficulties due to the
> fact that I was too fast. Paul did a backport of ppp-2.4.x to 2.2.x and
> I rsynced it with the auvz --delete option; In the wrong moment!!!. But
> it wasn't meant for 2.2.x.
> 
> So only a clean download helped me. (not all the stuff, only with the -u
> disabled (update == looks for date))

I used a clean download.

> Now I can report a clean, more or less, well ppp operation.
As I wrote, it always works on the first try.
It sometimes fials on the second and following tries with 2.2.15pre19.
It always works with the 2.2.15pre3 which does not have ir support build
in. 


If wvdialconf scans the ir port ttyS1 on 2.2.15pre19, die machine bombs.

> > wvdail cannot open /dev/ttyS0 twice with 2.2.51pre19.
> > After I ctrl-ced wvdial to interrupt the network connection
> > I get an I/O error when I try to open it again.
> 
> Do you have the module option in char/devices/serial on? (dumb serial device)

Not that I know of. I admit that I have to learn a bit more about
kernel configuration to be sure, though.

> > Running wvdialconf it started scanning ttyS1 and
> > then jumped into the system monitor:
> 
> Don't know about a lombard, but a wallstreet has 4 tty's 0,1,2,3
> (serial/printer =0, IRDA =1, modem =2; which is not present in my case;
> third = 3, the third is unused, I think the lombard has only one SCC so
> you can change the SERIAL_DEV_OFFSET to 2 iso 4.

ttyS0 is the modem under Lombard,
ttyS1 the IR port.

Most interestingly right now I cannot reproduce the I/O error.
So it works, most of the time. I hate this kind of errors.
So a hardware problem is still possible with this machine.

> > ps: Please carbon copy relevant replies to me.
> CC? or reply?
Usually people will reply to the list, I guess. I just wanted to say 
that I am not subscribed, so It need to get a copy of posts which
are interesting.

-- 
Professional Service around Free Software                (intevation.net)  
The FreeGIS Project				            (freegis.org)
Association for a Free Informational Infrastructure            (ffii.org)

[-- Attachment #2: Type: application/pgp-signature, Size: 236 bytes --]

Re: Serial driver problem (modem Lombard)

[Andreas Tobler]

Bernhard Reiter wrote:
>
> > Now I can report a clean, more or less, well ppp operation.
> As I wrote, it always works on the first try.
> It sometimes fials on the second and following tries with 2.2.15pre19.
> It always works with the 2.2.15pre3 which does not have ir support build
> in.

I'm not sure, is it possible to disable IR in the kernel build? worth a try.

> If wvdialconf scans the ir port ttyS1 on 2.2.15pre19, die machine bombs.

have you tried with something other than wvdial? (which I don't know), I
use netcfg.

> > > wvdail cannot open /dev/ttyS0 twice with 2.2.51pre19.
> > > After I ctrl-ced wvdial to interrupt the network connection
> > > I get an I/O error when I try to open it again.
> >
> > Do you have the module option in char/devices/serial on? (dumb serial device)
>
> Not that I know of. I admit that I have to learn a bit more about
> kernel configuration to be sure, though.

This makes only sense when you have a pcmcia/cadbus modem.

> Most interestingly right now I cannot reproduce the I/O error.
> So it works, most of the time. I hate this kind of errors.
> So a hardware problem is still possible with this machine.

:-((

Andreas


** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

Re: Serial driver problem (modem Lombard)

[Bernhard Reiter]

[-- Attachment #1: Type: text/plain, Size: 1465 bytes --]

On Mon, Apr 24, 2000 at 02:33:13PM +0200, Andreas Tobler wrote:
> Bernhard Reiter wrote:
> >  
> > > Now I can report a clean, more or less, well ppp operation.
> > As I wrote, it always works on the first try.
> > It sometimes fials on the second and following tries with 2.2.15pre19.
> > It always works with the 2.2.15pre3 which does not have ir support build
> > in.
> 
> I'm not sure, is it possible to disable IR in the kernel build? worth a try.

Probably.

> > If wvdialconf scans the ir port ttyS1 on 2.2.15pre19, die machine bombs.
> have you tried with something other than wvdial? (which I don't know), I
> use netcfg.

Wvdialconf scans all devices and tries to detect a modem.
For that reason it writes normal modem commands to the device.
So when scanning the ir port in my case, it should not detect a 
modem, because there is none. 

I just like to report the bug that the machine bombs with the
2.2.15pre19 kernel when wvdial writes the nonsense to the IR port.  
A machine should never bomb.

My ppp runs fine with the configured modemport, apart from a couple
of occasion where I could only use it once.

I guess the next step of debuggin would be to try to use the IR for
something useful.
	Bernhard
	 

-- 
Professional Service around Free Software                (intevation.net)  
The FreeGIS Project				            (freegis.org)
Association for a Free Informational Infrastructure            (ffii.org)

[-- Attachment #2: Type: application/pgp-signature, Size: 236 bytes --]