Re: UML tools
On Wed, Mar 28, 2001 at 03:52:50PM +0200, Pawe³ Krupa wrote: > Where can I find UML tools for Debian? dia - the diagram editor has UML support. Try apt-get install dia -- Gopal Narayanan <[EMAIL PROTECTED]> <[EMAIL PROTECTED]> Debian GNU/Linux Developer Dept. of Astronomy, University of Massachusetts, Amherst
ITA: pgplot5
Intent to Adopt: pgplot5 I intend to take over pgplot5 from the previous maintainer, John Lapeyre. I have already informed John about my intention. Gopal. -- Gopal Narayanan Ph #: (413) 545 0925 Five College Radio Astronomy Observatory Fax#: (413) 545 4223 University of Massachusetts e-mail: [EMAIL PROTECTED] Amherst MA 01003 --- pgp29TTYNNzrV.pgp Description: PGP signature
Re: minicom crashes after upgrade
On 26 Apr, Gopal Narayanan wrote: > Miquel van Smoorenburg writes: >> >> In article <[EMAIL PROTECTED]>, >> Gopal Narayanan <[EMAIL PROTECTED]> wrote: >> >I upgraded one of our machines to slink from hamm. The upgrade went >> >well. But after the upgrade I keep getting segmentation violations when >> >I run minicom. We use minicom to talk to another local machine through >> >the serial port. It was working fine before the upgrade. I am running >> >kernal 2.0.34. >> >> Well from the message you are including below (a kernel oops), it >> is clear that it isn't minicom that crashes, it's the kernel that >> crashes! Fortunately only minicom is killed and not the whole machine.. >> >> >When I start up minicom, it is fine until I give it one keystroke, upon >> >which it segfaults. Any help will be much appreciated. Will a kernel >> >upgrade be helpful. If so what kernel should I upgrade to? >> >> Oh yes, that will probbaly help. 2.0.36 is the latest stable kernel >> in the 2.0.x series, try that one. >> > > Thanks for your message. I did upgrade to 2.0.36. Still no luck. Same > problem. > I found the problem. Kernel upgrades did not help as mentioned above. It appears that during the upgrade of the setserial package, I said yes to the installation of a new /etc/rc.boot/0setserial. That seems to break serial port access. When I put back the old 0setserial, and rebooted, minicom worked fine. Inspecting the two scripts, the old and new, I see enough differences. I will try to understand this and turn in a bug report if warranted. Has anyone else had a problem with the 0setserial bootup script in setserial-2.14-3 ? Gopal. -- Gopal Narayanan Ph #: (413) 545 0925 Five College Radio Astronomy Observatory Fax#: (413) 545 4223 University of Massachusetts e-mail: [EMAIL PROTECTED] Amherst MA 01003 ---
Re: minicom crashes after upgrade
Miquel van Smoorenburg writes: > > In article <[EMAIL PROTECTED]>, > Gopal Narayanan <[EMAIL PROTECTED]> wrote: > >I upgraded one of our machines to slink from hamm. The upgrade went > >well. But after the upgrade I keep getting segmentation violations when > >I run minicom. We use minicom to talk to another local machine through > >the serial port. It was working fine before the upgrade. I am running > >kernal 2.0.34. > > Well from the message you are including below (a kernel oops), it > is clear that it isn't minicom that crashes, it's the kernel that > crashes! Fortunately only minicom is killed and not the whole machine.. > > >When I start up minicom, it is fine until I give it one keystroke, upon > >which it segfaults. Any help will be much appreciated. Will a kernel > >upgrade be helpful. If so what kernel should I upgrade to? > > Oh yes, that will probbaly help. 2.0.36 is the latest stable kernel > in the 2.0.x series, try that one. > Thanks for your message. I did upgrade to 2.0.36. Still no luck. Same problem. > > If you are running a recent klogd, then you'll have a decoded oops > in /var/log/kern.log. That is more useful - this raw output isn't > Well here is what kern.log says about it: Apr 26 14:59:31 fcrao kernel: Unable to handle kernel paging request at virtual address c802fd98 Apr 26 14:59:31 fcrao kernel: current->tss.cr3 = 0584d000, %cr3 = 0584d000 Apr 26 14:59:31 fcrao kernel: *pde = 1067 Apr 26 14:59:31 fcrao kernel: *pte = Apr 26 14:59:31 fcrao kernel: Oops: Apr 26 14:59:31 fcrao kernel: CPU:0 Apr 26 14:59:31 fcrao kernel: EIP:0010:[serial:register_serial_R3425f38c+-12 012/324] Apr 26 14:59:31 fcrao kernel: EFLAGS: 00010202 Apr 26 14:59:31 fcrao kernel: eax: 0802fd98 ebx: 0010 ecx: 06ccb434 ed x: 06ccb400 Apr 26 14:59:31 fcrao kernel: esi: fff0 edi: 0010 ebp: 001f91a0 es p: 0586afa4 Apr 26 14:59:31 fcrao kernel: ds: 0018 es: 0018 fs: 002b gs: 002b ss: 00 18 Apr 26 14:59:31 fcrao kernel: Process minicom (pid: 370, process nr: 59, stackpa ge=0586a000) Apr 26 14:59:31 fcrao kernel: Stack: 00118603 05996c0c 0002 080499a0 b90 0 0010a853 0003 b930 Apr 26 14:59:31 fcrao kernel:0001 0002 080499a0 b900 000 1 080a002b 002b 002b Apr 26 14:59:31 fcrao kernel:002b 0004 400b9a94 0023 020 2 b7e8 002b Apr 26 14:59:31 fcrao kernel: Call Trace: [sys_wait4+111/840] [<080499a0>] [hand le_signal+19/144] [<080499a0>] [<080a002b>] Apr 26 14:59:31 fcrao kernel: Code: <1>Unable to handle kernel paging request at virtual address c802fd98 Apr 26 14:59:31 fcrao kernel: current->tss.cr3 = 0584d000, %cr3 = 0584d000 Apr 26 14:59:31 fcrao kernel: *pde = 1067 Apr 26 14:59:31 fcrao kernel: *pte = Apr 26 14:59:31 fcrao kernel: Oops: Apr 26 14:59:31 fcrao kernel: CPU:0 Apr 26 14:59:31 fcrao kernel: EIP:0010:[device_not_available+48/68] Apr 26 14:59:31 fcrao kernel: EFLAGS: 00010212 Apr 26 14:59:31 fcrao kernel: eax: 0010 ebx: 002b ecx: 0802fd98 ed x: 07546414 Apr 26 14:59:31 fcrao kernel: esi: edi: 0586b000 ebp: 0586af68 es p: 0586af0c Apr 26 14:59:31 fcrao kernel: ds: 0018 es: 0018 fs: 0010 gs: 002b ss: 00 18 Apr 26 14:59:31 fcrao kernel: Process minicom (pid: 370, process nr: 59, stackpa ge=0586a000) Apr 26 14:59:31 fcrao kernel: Stack: 001b002b 0002f000 0586af68 05996c0 c 087f 0880 0800 Apr 26 14:59:31 fcrao kernel:05990018 00111bde 001b484f 0586af68 000 0 00111910 fff0 0010 Apr 26 14:59:31 fcrao kernel:001f91a0 001896fd 05912118 05dacb6c 0010aa2 4 0586af68 0010 Apr 26 14:59:31 fcrao kernel: Call Trace: [asc_prt_driver_conf+455/488] [<087f00 00>] [<0880>] [serial:register_serial_R3425f38c+-208004/324] [mca_handle_nmi _slot+114/160] [mca_configure_adapter_status+80/156] [cdrom_read_intr+165/592] Apr 26 14:59:31 fcrao kernel:[do_signal+340/632] [serial:register_serial _R3425f38c+-12012/324] [serial:register_serial_R3425f38c+-12012/324] [sys_wait4+ 111/840] [<080499a0>] [handle_signal+19/144] [<080499a0>] [<080a002b>] Apr 26 14:59:31 fcrao kernel: Code: 64 8a 04 0e 0f a1 88 c2 81 e2 ff 00 00 00 89 54 24 10 52 68 Apr 26 14:59:31 fcrao kernel: Aiee, killing interrupt handler ----- Thanks again for any help!! What now - another kernel upgrade - maybe to 2.1.xx? Gopal. -- Gopal Narayanan Ph #: (413) 545 0925 Five College Radio Astronomy Observatory Fax#: (413) 545 4223 University of Massachusetts e-mail: [EMAIL PROTECTED] Amherst MA 01003 -
minicom crashes after upgrade
I upgraded one of our machines to slink from hamm. The upgrade went well. But after the upgrade I keep getting segmentation violations when I run minicom. We use minicom to talk to another local machine through the serial port. It was working fine before the upgrade. I am running kernal 2.0.34. When I start up minicom, it is fine until I give it one keystroke, upon which it segfaults. Any help will be much appreciated. Will a kernel upgrade be helpful. If so what kernel should I upgrade to? Here is the relevant kernel messages cut and pasted from dmesg: Unable to handle kernel paging request at virtual address c482bd98 current->tss.cr3 = 032de000, %cr3 = 032de000 *pde = 0009e067 *pte = Oops: CPU:0 EIP:0010:[<0482bd98>] EFLAGS: 00010202 eax: 0482bd98 ebx: 0010 ecx: 01f31d34 edx: 01f31d00 esi: fff0 edi: 0010 ebp: 001f47d0 esp: 03089fa4 ds: 0018 es: 0018 fs: 002b gs: 002b ss: 0018 Process minicom (pid: 1758, process nr: 37, stackpage=03089000) Stack: 001181e7 02c41c0c 0001 080499a0 b930 0010a7f7 0003 b960 0001 0001 080499a0 b930 0001 002b 50a8002b 3548002b 002b 0004 400b9a94 0023 0202 b818 002b Call Trace: [<001181e7>] [<0010a7f7>] Code: <1>Unable to handle kernel paging request at virtual address c482bd98 current->tss.cr3 = 032de000, %cr3 = 032de000 *pde = 0009e067 *pte = Oops: CPU:0 EIP:0010:[<0010ad60>] EFLAGS: 00010212 eax: 0010 ebx: 002b ecx: 0482bd98 edx: 03765810 esi: edi: 0308a000 ebp: 03089f68 esp: 03089f0c ds: 0018 es: 0018 fs: 0010 gs: 002b ss: 0018 Process minicom (pid: 1758, process nr: 37, stackpage=03089000) Stack: 001b002b 0002b000 03089f68 02c41c0c 048f 0500 0480 02c40018 001117d6 001ba338 03089f68 00111508 fff0 0010 001f47d0 0018f0b5 04073b98 0063d94c 0010a9c8 03089f68 0010 Call Trace: [<001b002b>] [<048f>] [<0500>] [<0480>] [<001117d6>] [<0 0111508>] [<0018f0b5>] [<0010a9c8>] [<0482bd98>] [<0482bd98>] [<001181e7>] [<0010a7f7>] Code: 64 8a 04 0e 0f a1 88 c2 81 e2 ff 00 00 00 89 54 24 10 52 68 Aiee, killing interrupt handler Thanks Gopal. -- Gopal Narayanan Ph #: (413) 545 0925 Five College Radio Astronomy Observatory Fax#: (413) 545 4223 University of Massachusetts e-mail: [EMAIL PROTECTED] Amherst MA 01003 ---
Re: Problems with ppp server
On 16 Dec, Joe Emenaker wrote: > > My only suggestion would be to try it without the asyncmap option (which > should cause ppp to use the desperate asyncmap of 0x... which you > could also try explicitly). If that works, start trying turning off a bunch > of the bits in the asyncmap to see of the problem returns. Eventually, you > may boil it down to the one or two characters than need to be escaped. > > - Joe > Thank You. That was the trick. Commenting out the asyncmap 0 option worked. I should have realized something was amiss earlier. I am using a digital TAU modem on the server side. It must need some characters to be escaped. I will now try determining which. Gopal. -- -------- Gopal Narayanan Ph #: (413) 545 0925 Five College Radio Astronomy Observatory Fax#: (413) 545 4223 University of Massachusetts e-mail: [EMAIL PROTECTED] Amherst MA 01003 ---
Problems with ppp server
minated by peer (Could not determine local IP address) Dec 16 08:48:41 work-server pppd[3759]: sent [IPCP TermAck id=0x4] Dec 16 08:48:41 work-server pppd[3759]: rcvd [LCP TermReq id=0x2 "No network protocols running"] Dec 16 08:48:41 work-server pppd[3759]: LCP terminated by peer (No network protocols running) Dec 16 08:48:41 work-server pppd[3759]: sent [LCP TermAck id=0x2] Dec 16 08:48:42 work-server pppd[3759]: Hangup (SIGHUP) Dec 16 08:48:42 work-server pppd[3759]: Modem hangup Dec 16 08:48:42 work-server pppd[3759]: Connection terminated. Dec 16 08:48:43 work-server pppd[3759]: Exit. Dec 16 08:50:22 work-server kernel: PPP: ppp line discipline successfully unregistered work-server's /etc/ppp/options : -- asyncmap 0 auth crtscts lock modem silent -detach debug proxyarp lcp-echo-interval 30 lcp-echo-failure 4 noipx work-server's /etc/ppp/options.ttyS0 : --- 192.168.1.54:192.168.1.3 work-server's /etc/mgetty/login.config : - /AutoPPP/ - - /usr/sbin/pppd auth -chap +pap * - - /bin/login @ -- Gopal Narayanan Ph #: (413) 545 0925 Five College Radio Astronomy Observatory Fax#: (413) 545 4223 University of Massachusetts e-mail: [EMAIL PROTECTED] Amherst MA 01003 ---
Strange PPP server problem
t [IPCP ConfReq id=0x2 ] Dec 11 08:32:05 home-client pppd[17719]: rcvd [IPCP ConfRej id=0x2 ] Dec 11 08:32:05 home-client pppd[17719]: sent [IPCP ConfReq id=0x3 ] Dec 11 08:32:06 home-client pppd[17719]: rcvd [IPCP ConfAck id=0x3 ] Dec 11 08:32:06 home-client pppd[17719]: Could not determine local IP address Dec 11 08:32:06 home-client pppd[17719]: sent [IPCP TermReq id=0x4 "Could not determine local IP address"] Dec 11 08:32:06 home-client pppd[17719]: rcvd [IPCP TermAck id=0x4] Dec 11 08:32:06 home-client pppd[17719]: sent [LCP TermReq id=0x2 "No network protocols running"] Dec 11 08:32:06 home-client pppd[17719]: rcvd [LCP TermAck id=0x2] Dec 11 08:32:06 home-client pppd[17719]: Connection terminated. Dec 11 08:32:06 home-client pppd[17719]: Hangup (SIGHUP) Dec 11 08:32:06 home-client pppd[17719]: Exit. work-server syslog - Dec 11 08:31:17 work-server kernel: CSLIP: code copyright 1989 Regents of the University of California Dec 11 08:31:18 work-server kernel: PPP: version 2.2.0 (dynamic channel allocation) Dec 11 08:31:18 work-server kernel: PPP Dynamic channel allocation code copyright1995 Caldera, Inc. Dec 11 08:31:18 work-server kernel: PPP line discipline registered. Dec 11 08:31:18 work-server kernel: registered device ppp0 Dec 11 08:31:18 work-server pppd[31155]: pppd 2.3.5 started by a_ppp, uid 0 Dec 11 08:31:18 work-server pppd[31155]: Using interface ppp0 Dec 11 08:31:18 work-server pppd[31155]: Connect: ppp0 <--> /dev/ttyS0 Dec 11 08:31:18 work-server pppd[31155]: sent [LCP ConfReq id=0x1 ] Dec 11 08:31:18 work-server pppd[31155]: rcvd [LCP ConfAck id=0x1 ] Dec 11 08:31:20 work-server pppd[31155]: rcvd [LCP ConfReq id=0x1] Dec 11 08:31:20 work-server pppd[31155]: sent [LCP ConfAck id=0x1] Dec 11 08:31:20 work-server pppd[31155]: sent [LCP EchoReq id=0x0 magic=0x9142] Dec 11 08:31:20 work-server pppd[31155]: rcvd [LCP EchoReq id=0x0 magic=0x5ddb] Dec 11 08:31:20 work-server pppd[31155]: sent [LCP EchoRep id=0x0 magic=0x9142] Dec 11 08:31:20 work-server pppd[31155]: rcvd [PAP AuthReq id=0x1 user="myname" password="mypassword"] Dec 11 08:33:17 work-server kernel: PPP: ppp line discipline successfully unregistered server debug file: Dec 11 08:31:18 work-server pppd[31155]: sent [LCP ConfReq id=0x1 ] Dec 11 08:31:18 work-server pppd[31155]: rcvd [LCP ConfAck id=0x1 ] Dec 11 08:31:20 work-server pppd[31155]: rcvd [LCP ConfReq id=0x1] Dec 11 08:31:20 work-server pppd[31155]: sent [LCP ConfAck id=0x1] Dec 11 08:31:20 work-server pppd[31155]: sent [LCP EchoReq id=0x0 magic=0x9142] Dec 11 08:31:20 work-server pppd[31155]: rcvd [LCP EchoReq id=0x0 magic=0x5ddb] Dec 11 08:31:20 work-server pppd[31155]: sent [LCP EchoRep id=0x0 magic=0x9142] Dec 11 08:31:20 work-server pppd[31155]: rcvd [PAP AuthReq id=0x1 user="myname" password="mypassword"] home-client /etc/ppp/options --- asyncmap 0 crtscts lock modem lcp-echo-interval 30 lcp-echo-failure 4 # This file was generated by pppconfig. You can edit the following lines # but please do not delete lines or the change the comments or you will # confuse pppconfig. noauth #pppconfig_noauth connect "/usr/sbin/chat -v -f /etc/chatscripts/cut" #pppconfig_connect debug #pppconfig_debug /dev/ttyS1 #pppconfig_dev 115200 #pppconfig_speed defaultroute #pppconfig_route noipdefault #pppconfig_ipdefault user myname #pppconfig_user # End of pppconfig controlled lines. You can add lines below here without # confusing pppconfig. work-server /etc/ppp/options asyncmap 0 auth crtscts lock modem -detach debug proxyarp lcp-echo-interval 30 lcp-echo-failure 4 noipx work-server /etc/ppp/options.ttyS0 - 128.119.xx.yy:128.119.xxx.yyy where the above is correctly server:client IPs. -- Gopal Narayanan Ph #: (413) 545 0925 Five College Radio Astronomy Observatory Fax#: (413) 545 4223 University of Massachusetts e-mail: [EMAIL PROTECTED] Amherst MA 01003 ---
