Netscape crashing [Fwd: Re: Re: Browser for Multia]
Sites that crash Netscape 4.78 on my Alphas. www.zend.com (uses PHP) www.oceanatlas.org (uses JSP) www.ebay.com (uses static HTML) www.c-span.org Going to these and others results in an instant Netscape crash for me. The source is supposed to available at mozilla.org but I only see Mozilla itself there, not Commuicator. My build of Mozilla 2.6 took up 2 Gig of disk space (wow). It doesn't crash going to those sites, but it is incredibly slow, 50 sec. just to come up on the XP1000. Is the Netscape really open. Sigh, Martin Original Message Subject: Re: Re: Browser for Multia Resent-Date: Sun, 16 Mar 2003 15:35:10 -0600 (CST) Resent-From: debian-alpha@lists.debian.org Date: Sun, 16 Mar 2003 22:18:07 +0100 From: [EMAIL PROTECTED] Organization: http://freemail.web.de/ To: [EMAIL PROTECTED] CC: debian-alpha@lists.debian.org [EMAIL PROTECTED] schrieb am 16.03.03 22:12:39: Go to: http://wp.netscape.com/download/archive/client_archive47x.html Download, then un-tar/gzip, then read README.install which tells you to execute the ns-install script. I use it 99% of the time. But more and more now I find web-pages that load completely empty, though still with the Document: Done. message, and worse: sites that cause Netscape to crash. (Ex: http://www.zend.com) It may be a java thing. For those sites I bring up mozilla or another. ---Martin communicator-v478.alpha-dec-osf4.0 Thanks a lot, Martin. I'll give it a shot. Marc
Re: alpha kernel memory leak
(Please correct me where I'm wrong.) Generally, a memory leak is where an often called piece of code dynamically allocates itself some memory for temporary usage, and then fails to release that memory before being called again. This situation might be indicated by running out of swap space, at which point the machine should grind to a halt (all processes), but the memory usage reflected by the top or free commands won't show it. Swap space should be twice the size of physical memory. ...top reports 505MB used, 5MB free, ... Such memory usage is normal and desirable, and is not an Alpha or a Debian or even a Linux thing. That's what the memory is for: to be used to the max for minimum paging/swaping. Since no process can run until it is loaded into memory, processes are unloaded only when it's time for some other process to run, and if that new process does not already reside in memory. Only a portion of a process's code is loaded as needed, so even if no new processes are started after booting, the memory usage will increase to approach the max, as needed portions are loaded and un-needed blocks are left as is until there is no more memory available (then swaping commences apace). -Martin Bob McElrath wrote: I have noticed that my alphas seems to have a gigantic memory leak. I have two machines, one with 2GB memory and one with 512MB memory. When I first boot up the machines run fine, but over time the amount of memory available decreases steadily to zero. At first I thought it was just poor VM code in linux that caused it, but I ran for a couple of days with the swap turned off, and the results are the same. 'ps' does not correctly report memory information anymore (latest debian unstable -- why?), but using top and summing the VIRT, I get 202MB on the 512MB machine, and top reports 505MB used, 5MB free, and 25MB cached. Clearly something is horribly wrong. The 2GB machine is reporting that almost all memory is full (free + buffers + cached is only different from the sum of VIRT by 150 MB). But it is not used as heavily so presumably it is leaking slower. uptime is 4 days on the 512MB machine, 9 days on the 2GB machine. The kernels on these two machines are 2.4.21-pre7 (2GB) and 2.4.21-rc1-ac1 (512MB), but this is something that I have noticed for more than a year accross many kernels. I have plotted the memory usage every 60 seconds over the last 3 days on the 512MB machine (swap was turned off). On first bootup I can run many xterms, galeon, and xmms with no problem. After 4 days both were killed with OOM, but notice in the plots that the amount of memory available hasn't changed, despite the fact that these (and X) are the largest memory consuming processes running. It is here: http://mcelrath.org/mem.log.ps.gz Cheers, Bob McElrath [Univ. of Wisconsin at Madison, Department of Physics] You measure democracy by the freedom it gives its dissidents, not the freedom it gives its assimilated conformists. -- Abbie Hoffman
Re: alpha kernel memory leak
(Please correct me where I'm wrong.) Generally, a memory leak is where an often called piece of code dynamically allocates itself some memory for temporary usage, and then fails to release that memory before being called again. This situation might be indicated by running out of swap space, at which point the machine should grind to a halt (all processes), but the memory usage reflected by the top or free commands won't show it. Swap space should be twice the size of physical memory. ...top reports 505MB used, 5MB free, ... Such memory usage is normal and desirable, and is not an Alpha or a Debian or even a Linux thing. That's what the memory is for: to be used to the max for minimum paging/swaping. Since no process can run until it is loaded into memory, processes are unloaded only when it's time for some other process to run, and if that new process does not already reside in memory. Only a portion of a process's code is loaded as needed, so even if no new processes are started after booting, the memory usage will increase to approach the max, as needed portions are loaded and un-needed blocks are left as is until there is no more memory available (then swaping commences apace). -Martin Bob McElrath wrote: I have noticed that my alphas seems to have a gigantic memory leak. I have two machines, one with 2GB memory and one with 512MB memory. When I first boot up the machines run fine, but over time the amount of memory available decreases steadily to zero. At first I thought it was just poor VM code in linux that caused it, but I ran for a couple of days with the swap turned off, and the results are the same. 'ps' does not correctly report memory information anymore (latest debian unstable -- why?), but using top and summing the VIRT, I get 202MB on the 512MB machine, and top reports 505MB used, 5MB free, and 25MB cached. Clearly something is horribly wrong. The 2GB machine is reporting that almost all memory is full (free + buffers + cached is only different from the sum of VIRT by 150 MB). But it is not used as heavily so presumably it is leaking slower. uptime is 4 days on the 512MB machine, 9 days on the 2GB machine. The kernels on these two machines are 2.4.21-pre7 (2GB) and 2.4.21-rc1-ac1 (512MB), but this is something that I have noticed for more than a year accross many kernels. I have plotted the memory usage every 60 seconds over the last 3 days on the 512MB machine (swap was turned off). On first bootup I can run many xterms, galeon, and xmms with no problem. After 4 days both were killed with OOM, but notice in the plots that the amount of memory available hasn't changed, despite the fact that these (and X) are the largest memory consuming processes running. It is here: http://mcelrath.org/mem.log.ps.gz Cheers, Bob McElrath [Univ. of Wisconsin at Madison, Department of Physics] You measure democracy by the freedom it gives its dissidents, not the freedom it gives its assimilated conformists. -- Abbie Hoffman
Re: boot problems
file not found seems clear. What do you get with these: boot dqa0 -file 1/vmlinuz -flags root=/dev/hda1 boot dqa0 -file 1/xl -flags root=/dev/hda1 -Martin Donald D. Daniel wrote: My /etc/aboot.conf is as follows: 0:1/vmlinuz ro root=/dev/hda1 1:1/xl ro root=/dev/hda1 In /boot and /boot2 I have identical files including vmlinuz-2.2.22. At / I have vmlinuz and xl, symbolic links to the two identical copies of the kernel. If I boot dqa0 -fl i to get into aboot, I can type 0 and one copy of the kernel will boot. If I type 1, the other copy does not boot, instead I get: read error, lbn 70532881: 0x8000 ext2_iget: read error xl: file not found aboot Why does the other identical copy of the kernel not boot? Donald Daniel
Re: Power Supply Replacement
Try HP's phone number: 1-800-282-6672. Ask for the Custom Order Management Group. It has nothing to do with Alphas that you will most probably need the exact power supply designed for the PW500a. -Martin CiAsA S'Nuey Boark wrote: Hi guys, quick question, Recently my PW500a has died and looks like it needs a replacement power supply. I've tried looking online for information about what type I will need, but the only information I have been able to find is that I will need a 300w supply. Will any 300w power supply work? Or do I need one specifically made for alphas? Right now I'm looking at ones like the following: http://www.newegg.com/app/ViewProduct.asp?description=17-154-009 that usually say 'made for pentium4' or some such. Any recomendations or suggestions? -- I dote on his very absence. -- William Shakespeare, The Merchant of Venice Jonathan Nelson [www.ciasaboark.org/~ciasa/]
Re: Browser for Multia
Go to: http://wp.netscape.com/download/archive/client_archive47x.html Download, then un-tar/gzip, then read README.install which tells you to execute the ns-install script. I use it 99% of the time. But more and more now I find web-pages that load completely empty, though still with the Document: Done. message, and worse: sites that cause Netscape to crash. (Ex: http://www.zend.com) It may be a java thing. For those sites I bring up mozilla or another. ---Martin communicator-v478.alpha-dec-osf4.0 Marc Schlensog wrote: Thanks to all who have replied. I was fooling around with some options without all too much success though. Dillo was quite nice and fast but seemed to be rather unstable. Konqueror and Galeon needed way too much overhead with all that KDE and Gnome stuff and that graphical Links didn't seem to work all too good in FB-Mode. The thing I haven't tried yet is Netscape 4.7. Could anyone tell me, how to get it installed? TIA, Marc
Re: Bahamut ircd
As far as I'm aware it's a compiler oversite. The warning comes when an implicit cast from integer to pointer is found that the compiler doesn't know is OK, because Alpha's have 64 bit pointers and 32 bit integers. The warnings should go away by sticking an explicit cast at every place that you get a warning, but the object code should be identical to that produced before. (As far as I'm aware.) -Martin M Campbell wrote: Well, it definitely caused a problem in this case? And there are a lot more of these in this code I don't know anything about C, but I wouldn't mind trying to clean up the specific warnings that I get on compile. Is this pretty basic stuff, or should I try to bug someone who knows C to do it? Any resources or hints about things to look for? Thank's Mike On Mon, Mar 10, 2003 at 02:41:20AM +0100, Falk Hueffner wrote: [EMAIL PROTECTED] writes: My 2?: It's the very rare source code that compiles without that cast from integer to pointer of different size warning. I quit worrying about it many years ago. It can be harmless in some cases, but it is certainly not a warning that should be ignored, and it is usually easy to fix. -- Falk
Re: Bahamut ircd
My 2ยข: It's the very rare source code that compiles without that cast from integer to pointer of different size warning. I quit worrying about it many years ago. -Martin Has anyone had success with Bahamut ircd on Alpha? It compiles for me with alot of warnings...mostly cast from integer to pointer of different size and some others. The ircd will run, but DNS seems to be completely broken. The reverse dns done on a connecting client fails. Anybody tried this? Thank's Mike -- They that can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety. - Benjamin Franklin (1706-1790), Letter to Josiah Quincy, Sept. 11, 1773. Part 1.2Type: application/pgp-signature
Re: Multia Install problems
Did you try partition a to start at 2 (not 1)? BTW, that swap partition b looks rather huge. (Almost 4 Gig.? A size twice that of physical memory size should be enough.) Also, a probably wants to be ext2, too, and maybe bigger. And, c should maybe start at the end of (a much smaller) b plus 1. I don't think things will work with a filesystem's partition and the swap partition overlapping. -Martin Mark T. Valites wrote: I've been having difficulties installing debian onto my multia through SRM. I'm completely new to alpha, arc srm, so please forgive my ignorance if I leave anything out. I've got the machine doing a tftp install console over serial to an external scsi disk (Kid I got it from had redhat booting from arc) All goes well until the end, when aboot bombs with this output: aboot wasn't able to install. Most likely this is because | | your first partition overlaps the area where aboot was to | | be written. Either repartition your disk and try again, or | | boot the system using the rescue boot method and install| | aboot manually. In my readings along the way, I cam across suggestions that said I might need some extra room at the beginning of the disk one that said I needed to create a disk label the size of the disk, similar to sparc. Neither and both seemed to make a difference. Here's the partitioning scheme I ended up with in the end: # fdisk -l /dev/sda Disk /dev/sda: 66 heads, 62 sectors, 1017 cylinders Units = cylinders of 4092 * 512 bytes 3 partitions: # start end size fstype [fsize bsize cpg] a:1 129 129 unused0 0 b: 130 2033 1904 swap c:1 2033 2033 ext2 # Any ideas or suggestions? TIA, -Mark -- Mark T. Valites Unix Systems Analyst CIT - SUNY Geneseo --)) --))
Re: booting challenges with lx164
Your starting place looks like a line from /etc/aboot.conf which is not applicable. The following two are equivalent, and say to go to SCSI device id 0, partition 1 to load the file /boot/vmlinux. Further, special file /dev/sda1 is the device to mount. My dka0 comes from the show dev command listing. Your devs may vary. The second version is preferred as the variable values are saved between power cycles, and so only need be entered once. -Martin boot dka0 -file 1/boot/vmlinux -flags root=/dev/sda1 set boot_dev dka0 set boot_file 1/boot/vmlinux set boot_osflags root=/dev/sda1 boot Eric S. Johansson wrote: a friend of mine gave me an lx164 and now I'm trying to make it run Debian. I've upgraded the BIOS to the latest arc (5.7) version. I can run milo off of the first Debian CD but I can't get the boot command right. My starting place is: boot sr0:/boot/linux root=/dev/sr0 VFS: can not open root device 00:00 and then I get a kernel panic about not being able to open the root device. I've tried a bunch of different options but I'm not really sure what to do because the documentation doesn't seem to cover the problems I'm experiencing. any help would be most appreciated. ---eric -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
