Lombard hard freeze (update: mem>64MB)

Lombard hard freeze (update: mem>64MB)

[Bernhard Reiter]

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

Got one step forward with the hard freeze problem.

My local Apple shop (ProDatenTechnik in Osnabrück),
was to kind to let me check through a new memory module.

When I had only 64MB the system was stable!
I managed to compile GRASS (which is among the biggest free software
projects) and other things.

Plugging in a different 128MB and a different 64MB, both in the first
slot, made the system unstable each time.

This explains why Micheal has a stable system.
Sadly it is still a big problem.

To answer some of the suggestions:
The problem is there, even when I never start X11 and work
from the virtual console. There is absolutly no output.
No ethernet network ping, no memory monitor, no kernel panic, nothing. 
The cursor stops blinking (and everything else moving) and it is over.

As about the power consumption and the heat: It is my understanding that
the fan should start up when there is too much heat controlled by
hardware. But the fan does not start. And freezes also occur when the 
machine itself it cold. I also do not quite understand how the power
consumption could be a problem here. 

It would so nice to have a person who can debug it.
I will test two things: 
	Setting mem=64M and see if it makes it stable.

	Maybe a development line kernel has some fixes for this stuff, 
	I shall try one. 

Maybe we should ask for Lombard users which have a stable system 
with more as 64MB memory. Can they do huge compiles?
Somebody should have a lombard the symptom and the guts to debug it.

	Bernhard
ps.: Please remember that I am not on the dev list.

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

Re: Lombard hard freeze (update: mem>64MB)

[Tim Wojtulewicz]

>It would so nice to have a person who can debug it.
>I will test two things:
>	Setting mem=64M and see if it makes it stable.
>
>	Maybe a development line kernel has some fixes for this stuff,
>	I shall try one.
>
>Maybe we should ask for Lombard users which have a stable system
>with more as 64MB memory. Can they do huge compiles?
>Somebody should have a lombard the symptom and the guts to debug it.
>
>	Bernhard

I've been paying attention to this thread for a while since I have a
Pismo and mine is exhibiting the same problems that yours is.  I have
128M of RAM in mine (one stick).  This is memory straight from Apple.
I also see kernel panics/lockups during large compiles.  I managed to
make it through KDevelop 1.2, but it will ALWAYS die during XFree 4.0.

Tim

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

Re: Lombard hard freeze (update: mem>64MB)

[David A. Gatwood]

On Wed, 10 May 2000, Bernhard Reiter wrote:

> When I had only 64MB the system was stable!
> I managed to compile GRASS (which is among the biggest free software
> projects) and other things.
>
> Plugging in a different 128MB and a different 64MB, both in the first
> slot, made the system unstable each time.

So it worked with your original 64 megs, but it fails with a different 64
meg part and a 128 meg part?  I don't see how that can be anything but bad
hardware, either something wrong with the motherboard or a pair of bad
SIMM/DIMM parts or dirty contacts or incorrectly seated RAM.

Had the strangest thing the other day... 8100 clone wouldn't boot up.  I
figured the PRAM battery was dead, so bought a new one and swapped it, no
luck.  Started pulling nubus cards, etc.  Had it all down to the mobo and
nothing.  Yanked the RAM and it came back up.  Reseated the RAM, and it
has been fine since.  :-/  Weird....


> As about the power consumption and the heat: It is my understanding that
> the fan should start up when there is too much heat controlled by
> hardware. But the fan does not start. And freezes also occur when the
> machine itself it cold. I also do not quite understand how the power
> consumption could be a problem here.

Me either.  I think the fan is started automagically in hardware anyway.
At least I'm pretty sure it was on the wallstreet....


David

---------------------------------------------------------------------
A brief Haiku:

Microsoft is bad.
It seems secure at first glance.
Then you read your mail.


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

Re: Lombard hard freeze (update: mem>64MB)

[Bernhard Reiter]

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

On Wed, May 10, 2000 at 10:53:52AM -0700, David A. Gatwood wrote:
> On Wed, 10 May 2000, Bernhard Reiter wrote:

> > When I had only 64MB the system was stable!
> > I managed to compile GRASS (which is among the biggest free software
> > projects) and other things.
> > 
> > Plugging in a different 128MB and a different 64MB, both in the first
> > slot, made the system unstable each time.
> 
> So it worked with your original 64 megs, but it fails with a different 64
> meg part and a 128 meg part?  

It was stalbe with my original 64 megs.
Putting additional RAM in made it unstable.
The symptom occurred with three differnent addition RAM simms.
128,128,64 megs.

> I don't see how that can be anything but bad
> hardware, either something wrong with the motherboard or a pair of bad
> SIMM/DIMM parts or dirty contacts or incorrectly seated RAM.

The problem is that a simple RAM stress test under MacOS would certainly
reveal that. (If it is a simple hardware problem, like you suggested.)

But the RAM tests were passed in MacOS so far.
(I have another one running right now. It will take a bit.)

	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 --]

Re: Lombard hard freeze (update: mem>64MB)

[Bernhard Reiter]

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

On Wed, May 10, 2000 at 10:43:41AM -0700, Tim Wojtulewicz wrote:
> >It would so nice to have a person who can debug it.
> >I will test two things:
> >	Setting mem=64M and see if it makes it stable.
> >
> >	Maybe a development line kernel has some fixes for this stuff,
> >	I shall try one.
> >
> >Maybe we should ask for Lombard users which have a stable system
> >with more as 64MB memory. Can they do huge compiles?
> >Somebody should have a lombard the symptom and the guts to debug it.
> >
> >	Bernhard
> 
> I've been paying attention to this thread for a while since I have a 
> Pismo and mine is exhibiting the same problems that yours is.  I have 
> 128M of RAM in mine (one stick).  This is memory straight from Apple. 
> I also see kernel panics/lockups during large compiles.  I managed to 
> make it through KDevelop 1.2, but it will ALWAYS die during XFree 4.0.

Uh if you really have the hard freeze with one simm that might point
into the kernel problem corner.

On the other hand the Pismo has different hardware and might have other
problems.

Thanks for helping us with your input.
	Bernhard

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

Re: Lombard hard freeze (update: mem>64MB)

[David A. Gatwood]

On Wed, 10 May 2000, Bernhard Reiter wrote:

> > > When I had only 64MB the system was stable!
> > > I managed to compile GRASS (which is among the biggest free software
> > > projects) and other things.
> > >
> > > Plugging in a different 128MB and a different 64MB, both in the first
> > > slot, made the system unstable each time.
> >
> > So it worked with your original 64 megs, but it fails with a different 64
> > meg part and a 128 meg part?
>
> It was stalbe with my original 64 megs.
> Putting additional RAM in made it unstable.

Oh, so that 64 megs was in addition to the original 64 megs.  Guess I
misread that.  So this problem only occurs on the Lombard?


David

---------------------------------------------------------------------
A brief Haiku:

Microsoft is bad.
It seems secure at first glance.
Then you read your mail.


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

Re: Lombard hard freeze (update: mem>64MB)

[Michael Schmitz]

> It would so nice to have a person who can debug it.

Send me a memory module :-)

Does this mean I was lucky to get only 64 MB, or to get a working 64MB
module?

How much RAM does Paul have in his Lombard?

	Michael


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

Re: Lombard hard freeze (update: mem>64MB)

[Michael Schmitz]

> > As about the power consumption and the heat: It is my understanding that
> > the fan should start up when there is too much heat controlled by
> > hardware. But the fan does not start. And freezes also occur when the
> > machine itself it cold. I also do not quite understand how the power
> > consumption could be a problem here.
>
> Me either.  I think the fan is started automagically in hardware anyway.
> At least I'm pretty sure it was on the wallstreet....

It's supposed to start automagically. I've never noticed that happen
though. Maybe this summer :-)

	Michael


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

Re: Lombard hard freeze (update: mem>64MB)

[jeramy b smith]

Bernhard Reiter <bernhard@intevation.de> wrote:
> When I had only 64MB the system was stable!
> I managed to compile GRASS (which is among the biggest free software
> projects) and other things.
>
> Plugging in a different 128MB and a different 64MB, both in the first
> slot, made the system unstable each time.
>
> This explains why Micheal has a stable system.
> Sadly it is still a big problem.
>

I guess I am just lucky then. I went to a Fry's Electronics while I was in the
valley area. Not only was I lucky enough to get the right module for my
lombard but I was also lucky enough to have it give me no problems in linux or
macos. Running silky smooth here at 192MB and I am already considering maxing
it out just for bragging rights.

-Jeramy

PS: If you have never heard of the infamous "Fry's", just ask anyone who lives
in the valley. I'm sure they'll have at least one horror story.


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

Re: Lombard hard freeze (update: mem>64MB)

[David A. Gatwood]

On 10 May 2000, jeramy b smith wrote:

> PS: If you have never heard of the infamous "Fry's", just ask anyone who
> lives in the valley. I'm sure they'll have at least one horror story.

$299 ethernet cable.  Reversed two digits of the number and rang it up as
a sound system.  Or the $30 ATA/66 cable that I found on the 'net for $3.
Infamous is perhaps a little too kind.  ;-)


Later,
David

---------------------------------------------------------------------
A brief Haiku:

Microsoft is bad.
It seems secure at first glance.
Then you read your mail.


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

Re: Lombard hard freeze (update: mem>64MB)

[chris mccraw]

On Mon, Jun 16, 2036 at 10:53:05PM -0500, jeramy b smith wrote:
>
> I guess I am just lucky then. I went to a Fry's Electronics while I was in the
> valley area. Not only was I lucky enough to get the right module for my
> lombard but I was also lucky enough to have it give me no problems in linux or
> macos. Running silky smooth here at 192MB and I am already considering maxing
> it out just for bragging rights.

just to add fuel to the fire,

i bought a 64M SO-DIMM from viking for $cheap when i got my lombard a year
ago.  in addition to the stock 64M, i've had no stability problems in linux.
macos is another story, of course...

i've done some reasonably big compiles and run seti@home at the same time.
however i've never kept at it for excessive periods of time...i'll leave a
kernel make looping tonight building off an nfs disk to the local disk
and see if anything turns up by morning...

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

Re: Lombard hard freeze (update: mem>64MB)

[Gabriel Ricard]

Well, I've got a lombard and I'm having issues, and
I'll do whatever I can to help some hackers get it
working. I'm also looking to upgrade my memory
(preferably from powerbookguy.com) so I'll have the
64MB default module on the side, which I could easily
send to you if it'd really help debug the problem.

Anything else?

--- Michael Schmitz
<schmitz@opal.biophys.uni-duesseldorf.de> wrote:
>
> > It would so nice to have a person who can debug
> it.
>
> Send me a memory module :-)
>
> Does this mean I was lucky to get only 64 MB, or to
> get a working 64MB
> module?
>
> How much RAM does Paul have in his Lombard?
>
> 	Michael
>
>
>


=====
Gabriel Ricard
g_ricard@yahoo.com


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

Re: Lombard hard freeze (update: mem>64MB)

[jeramy b smith]

chris mccraw <chrism@ticam.utexas.edu> wrote:
> i bought a 64M SO-DIMM from viking for $cheap when i got my lombard a year
> ago.  in addition to the stock 64M, i've had no stability problems in
linux.
> macos is another story, of course...
>
> i've done some reasonably big compiles and run seti@home at the same time.
> however i've never kept at it for excessive periods of time...i'll leave a
> kernel make looping tonight building off an nfs disk to the local disk
> and see if anything turns up by morning...

I have left my lombard running for 4 days in a row which included several
sleeps. During this period I did a 6 hour stint playing with the development
kernel code and did about 20 makes. No problems and this was after I bumped it
up to 192. I could try building GRASS just to empirical though.

-Jeramy


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

Re: Lombard hard freeze (update: mem>64MB)

[Michael Schmitz]

> > i've done some reasonably big compiles and run seti@home at the same time.
> > however i've never kept at it for excessive periods of time...i'll leave a
> > kernel make looping tonight building off an nfs disk to the local disk
> > and see if anything turns up by morning...
>
> I have left my lombard running for 4 days in a row which included several
> sleeps. During this period I did a 6 hour stint playing with the development
> kernel code and did about 20 makes. No problems and this was after I bumped it
> up to 192. I could try building GRASS just to empirical though.

Seems there's more people successfully running >64M in their Lombard here
than it first seemed. Someone pointed to the kernel problem corner, so
what kernel versions were these success stories run on?

(Mine's some old 2.2.13, 2.2.15pre9, 2.3.48 and 2.3.99pre6)

	Michael


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

Re: Lombard hard freeze (update: mem>64MB)

[chris mccraw]

> Seems there's more people successfully running >64M in their Lombard here
> than it first seemed. Someone pointed to the kernel problem corner, so
> what kernel versions were these success stories run on?
>
> (Mine's some old 2.2.13, 2.2.15pre9, 2.3.48 and 2.3.99pre6)

2.2.12 thru 2.2.15pre20, i think.  no 2.3 here.

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

Re: Lombard hard freeze (update: mem>64MB)

[Bernhard Reiter]

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

On Thu, May 11, 2000 at 11:07:39AM +0200, Michael Schmitz wrote:
> > > i've done some reasonably big compiles and run seti@home at the same time.
> > > however i've never kept at it for excessive periods of time...i'll leave a
> > > kernel make looping tonight building off an nfs disk to the local disk
> > > and see if anything turns up by morning...
> > 
> > I have left my lombard running for 4 days in a row which included several
> > sleeps. During this period I did a 6 hour stint playing with the development
> > kernel code and did about 20 makes. No problems and this was after 
> > I bumped it
> > up to 192. I could try building GRASS just to empirical though.
> 
> Seems there's more people successfully running >64M in their Lombard here
> than it first seemed. Someone pointed to the kernel problem corner, so
> what kernel versions were these success stories run on? 

Yes, we have to gather more data. Than then we have to seperate
the problems and search for similiarties and differences in the 
machines.

There seems to be a significant number of people having this hard freeze
problem with Lombards. Here is my preliminary list, if I counted
correctly:

	Hard Freezes occuring:

Tim Wojtulewicz		Pismo 	128 MB
Bernhard Reiter		Lombard 128,192   2.2.14, 2.2.15pre19
Gabriel Ricard	    	Lombard 192 MB   + other problems
Mario Scarpa	        hard freeze as described?  64 MB + other problems


	Running fine:

jeramy b smith		lombard	192 MB
chris mccraw		lombard 128 MB 		2.2.12 thru 2.2.15pre20



As I have no idea on how to compare the stress tests, I can only say
that in 95% of all my test cases I can trigger a hard freeze within three
runs of:
	rpm -ba gnomehack.spec
(You can get my src.rpm from: ftp://intevation.de/users/bernhard/)

There was one day, when I could run it five times but still a hard
freeze later.


So we should gather more data on how to recreate the bug and then
ask more people to try to trigger it. As you can see from my preliminary
tests, there is no obvious pattern. Maybe we should also check the
different lombard models, if there are any. (At least I have a german
keyboard, e.g.)


Oh and more details from my part:
My RAM test from MacOS was completed fine, reporting no errors.
Adding the mem=64M option to the bootup (I am using bootx, could that
make a difference too?) seems to make the system more stable so far.

Jeramy, Chris: can you tell us which kernel and bootprocess you are using?
	Are you sure that linux uses all the memory?
	Can you build gnomehack three times?


	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 --]

Re: Lombard hard freeze (update: mem>64MB)

[Seanano]

  I've been running a lombard with 192 megs of RAM since it was purchased
without any problem.  I've been running kernels 2.2.14 - 2.2.15-pre20
with almost all of the 2.2.15-preXX kernels coming from the rysnc server
at linuxcare.com.au.  Up until I installed the 9.0.4 upgrade a few weeks
ago I was using bootX, now I've switched over to yaboot.  I usually
compile multiple programs at a time and I've never seen any kernel errors
or freezes.  When the kernel boots it shows Total Memory = 192MB.


[seanano@ip35 seanano]$ cat /proc/cpuinfo
processor       : 0
cpu             : 750
temperature     : 0 C
clock           : 399MHz
revision        : 130.2
bogomips        : 801.18
zero pages      : total 0 (0Kb) current: 0 (0Kb) hits: 0/261 (0%)
machine         : PowerBook1,1
motherboard     : PowerBook1,1 MacRISC Power Macintosh
L2 cache        : 1024K unified
memory          : 192MB
pmac-generation : NewWorld


[seanano@ip35 /proc]$ cat /proc/meminfo
        total:    used:    free:  shared: buffers:  cached:
Mem:  195981312 50966528 145014784 25296896  3297280 22179840
Swap: 268427264        0 268427264
MemTotal:    191388 kB
MemFree:     141616 kB
MemShared:    24704 kB
Buffers:       3220 kB
Cached:       21660 kB
SwapTotal:   262136 kB
SwapFree:    262136 kB


  I'd be happy to run some tests if needed.  My network access on the
lombard is a bit unstable right now so I couldn't download the gnomehack
source...  I should be back to normal in a few days.  I don't even have
gnome installed anyway...


Sean


On Thu, 11 May 2000, Bernhard Reiter wrote:

> On Thu, May 11, 2000 at 11:07:39AM +0200, Michael Schmitz wrote:
> > > > i've done some reasonably big compiles and run seti@home at the same time.
> > > > however i've never kept at it for excessive periods of time...i'll leave a
> > > > kernel make looping tonight building off an nfs disk to the local disk
> > > > and see if anything turns up by morning...
> > >
> > > I have left my lombard running for 4 days in a row which included several
> > > sleeps. During this period I did a 6 hour stint playing with the development
> > > kernel code and did about 20 makes. No problems and this was after
> > > I bumped it
> > > up to 192. I could try building GRASS just to empirical though.
> >
> > Seems there's more people successfully running >64M in their Lombard here
> > than it first seemed. Someone pointed to the kernel problem corner, so
> > what kernel versions were these success stories run on?
>
> Yes, we have to gather more data. Than then we have to seperate
> the problems and search for similiarties and differences in the
> machines.
>
> There seems to be a significant number of people having this hard freeze
> problem with Lombards. Here is my preliminary list, if I counted
> correctly:
>
> 	Hard Freezes occuring:
>
> Tim Wojtulewicz		Pismo 	128 MB
> Bernhard Reiter		Lombard 128,192   2.2.14, 2.2.15pre19
> Gabriel Ricard	    	Lombard 192 MB   + other problems
> Mario Scarpa	        hard freeze as described?  64 MB + other problems
>
>
> 	Running fine:
>
> jeramy b smith		lombard	192 MB
> chris mccraw		lombard 128 MB 		2.2.12 thru 2.2.15pre20
>
>
>
> As I have no idea on how to compare the stress tests, I can only say
> that in 95% of all my test cases I can trigger a hard freeze within three
> runs of:
> 	rpm -ba gnomehack.spec
> (You can get my src.rpm from: ftp://intevation.de/users/bernhard/)
>
> There was one day, when I could run it five times but still a hard
> freeze later.
>
>
> So we should gather more data on how to recreate the bug and then
> ask more people to try to trigger it. As you can see from my preliminary
> tests, there is no obvious pattern. Maybe we should also check the
> different lombard models, if there are any. (At least I have a german
> keyboard, e.g.)
>
>
> Oh and more details from my part:
> My RAM test from MacOS was completed fine, reporting no errors.
> Adding the mem=64M option to the bootup (I am using bootx, could that
> make a difference too?) seems to make the system more stable so far.
>
> Jeramy, Chris: can you tell us which kernel and bootprocess you are using?
> 	Are you sure that linux uses all the memory?
> 	Can you build gnomehack three times?
>
>
> 	Bernhard
> --
> Professional Service around Free Software                (intevation.net)
> The FreeGIS Project				            (freegis.org)
> Association for a Free Informational Infrastructure            (ffii.org)
>


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

Re: Lombard hard freeze (update: mem>64MB)

[Gabriel Ricard]

Well, if we're gonna do some controlled tests we
should all probably start out with the same kernel to
begin with. Which one is the latest greatest stable
version? I suppose we should all test with the exact
same kernel config, so if someone wants to put their
kernel, system.map, and modules up on an ftp site so
we can all start with that kernel, I could start
testing diff. configs on my PB immerdiately. :)


--- Bernhard Reiter <bernhard@intevation.de> wrote:
> On Thu, May 11, 2000 at 11:07:39AM +0200, Michael
> Schmitz wrote:
> > > > i've done some reasonably big compiles and run
> seti@home at the same time.
> > > > however i've never kept at it for excessive
> periods of time...i'll leave a
> > > > kernel make looping tonight building off an
> nfs disk to the local disk
> > > > and see if anything turns up by morning...
> > >
> > > I have left my lombard running for 4 days in a
> row which included several
> > > sleeps. During this period I did a 6 hour stint
> playing with the development
> > > kernel code and did about 20 makes. No problems
> and this was after
> > > I bumped it
> > > up to 192. I could try building GRASS just to
> empirical though.
> >
> > Seems there's more people successfully running
> >64M in their Lombard here
> > than it first seemed. Someone pointed to the
> kernel problem corner, so
> > what kernel versions were these success stories
> run on?
>
> Yes, we have to gather more data. Than then we have
> to seperate
> the problems and search for similiarties and
> differences in the
> machines.
>
> There seems to be a significant number of people
> having this hard freeze
> problem with Lombards. Here is my preliminary list,
> if I counted
> correctly:
>
> 	Hard Freezes occuring:
>
> Tim Wojtulewicz		Pismo 	128 MB
> Bernhard Reiter		Lombard 128,192   2.2.14,
> 2.2.15pre19
> Gabriel Ricard	    	Lombard 192 MB   + other
> problems
> Mario Scarpa	        hard freeze as described?  64
> MB + other problems
>
>
> 	Running fine:
>
> jeramy b smith		lombard	192 MB
> chris mccraw		lombard 128 MB 		2.2.12 thru
> 2.2.15pre20
>
>
>
> As I have no idea on how to compare the stress
> tests, I can only say
> that in 95% of all my test cases I can trigger a
> hard freeze within three
> runs of:
> 	rpm -ba gnomehack.spec
> (You can get my src.rpm from:
> ftp://intevation.de/users/bernhard/)
>
> There was one day, when I could run it five times
> but still a hard
> freeze later.
>
>
> So we should gather more data on how to recreate the
> bug and then
> ask more people to try to trigger it. As you can see
> from my preliminary
> tests, there is no obvious pattern. Maybe we should
> also check the
> different lombard models, if there are any. (At
> least I have a german
> keyboard, e.g.)
>
>
> Oh and more details from my part:
> My RAM test from MacOS was completed fine, reporting
> no errors.
> Adding the mem=64M option to the bootup (I am using
> bootx, could that
> make a difference too?) seems to make the system
> more stable so far.
>
> Jeramy, Chris: can you tell us which kernel and
> bootprocess you are using?
> 	Are you sure that linux uses all the memory?
> 	Can you build gnomehack three times?
>
>
> 	Bernhard
> --
> Professional Service around Free Software
>     (intevation.net)
> The FreeGIS Project				            (freegis.org)
> Association for a Free Informational Infrastructure
>           (ffii.org)
>

> ATTACHMENT part 2 application/pgp-signature



=====
Gabriel Ricard
g_ricard@yahoo.com


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

Re: Lombard hard freeze (update: mem>64MB)

[Gabriel Ricard]

I'm using yaboot too. Does your kernel intialize the
video correctly when you first boot the machine up
from a cold state (as in, it was shutdown, not a
reboot)? I have to go into OF from a cold state, and
boot my macos partition just to the point where the
ROM initializes the video with a grey screen,
otherwise, I get this odd lockup when I boot into
Linux. As the kernel messages scroll down the screen
its fine until it has to scroll the screen up, it just
locks up when it does that. What kernel, yaboot, and
LinuxPPC (or other distro) version are you using?


--- Seanano <sto9013@ksu.edu> wrote:
>
>   I've been running a lombard with 192 megs of RAM
> since it was purchased
> without any problem.  I've been running kernels
> 2.2.14 - 2.2.15-pre20
> with almost all of the 2.2.15-preXX kernels coming
> from the rysnc server
> at linuxcare.com.au.  Up until I installed the 9.0.4
> upgrade a few weeks
> ago I was using bootX, now I've switched over to
> yaboot.  I usually
> compile multiple programs at a time and I've never
> seen any kernel errors
> or freezes.  When the kernel boots it shows Total
> Memory = 192MB.
>
>
> [seanano@ip35 seanano]$ cat /proc/cpuinfo
> processor       : 0
> cpu             : 750
> temperature     : 0 C
> clock           : 399MHz
> revision        : 130.2
> bogomips        : 801.18
> zero pages      : total 0 (0Kb) current: 0 (0Kb)
> hits: 0/261 (0%)
> machine         : PowerBook1,1
> motherboard     : PowerBook1,1 MacRISC Power
> Macintosh
> L2 cache        : 1024K unified
> memory          : 192MB
> pmac-generation : NewWorld
>
>
> [seanano@ip35 /proc]$ cat /proc/meminfo
>         total:    used:    free:  shared: buffers:
> cached:
> Mem:  195981312 50966528 145014784 25296896  3297280
> 22179840
> Swap: 268427264        0 268427264
> MemTotal:    191388 kB
> MemFree:     141616 kB
> MemShared:    24704 kB
> Buffers:       3220 kB
> Cached:       21660 kB
> SwapTotal:   262136 kB
> SwapFree:    262136 kB
>
>
>   I'd be happy to run some tests if needed.  My
> network access on the
> lombard is a bit unstable right now so I couldn't
> download the gnomehack
> source...  I should be back to normal in a few days.
>  I don't even have
> gnome installed anyway...
>
>
> Sean
>
>
> On Thu, 11 May 2000, Bernhard Reiter wrote:
>
> > On Thu, May 11, 2000 at 11:07:39AM +0200, Michael
> Schmitz wrote:
> > > > > i've done some reasonably big compiles and
> run seti@home at the same time.
> > > > > however i've never kept at it for excessive
> periods of time...i'll leave a
> > > > > kernel make looping tonight building off an
> nfs disk to the local disk
> > > > > and see if anything turns up by morning...
> > > >
> > > > I have left my lombard running for 4 days in a
> row which included several
> > > > sleeps. During this period I did a 6 hour
> stint playing with the development
> > > > kernel code and did about 20 makes. No
> problems and this was after
> > > > I bumped it
> > > > up to 192. I could try building GRASS just to
> empirical though.
> > >
> > > Seems there's more people successfully running
> >64M in their Lombard here
> > > than it first seemed. Someone pointed to the
> kernel problem corner, so
> > > what kernel versions were these success stories
> run on?
> >
> > Yes, we have to gather more data. Than then we
> have to seperate
> > the problems and search for similiarties and
> differences in the
> > machines.
> >
> > There seems to be a significant number of people
> having this hard freeze
> > problem with Lombards. Here is my preliminary
> list, if I counted
> > correctly:
> >
> > 	Hard Freezes occuring:
> >
> > Tim Wojtulewicz		Pismo 	128 MB
> > Bernhard Reiter		Lombard 128,192   2.2.14,
> 2.2.15pre19
> > Gabriel Ricard	    	Lombard 192 MB   + other
> problems
> > Mario Scarpa	        hard freeze as described?  64
> MB + other problems
> >
> >
> > 	Running fine:
> >
> > jeramy b smith		lombard	192 MB
> > chris mccraw		lombard 128 MB 		2.2.12 thru
> 2.2.15pre20
> >
> >
> >
> > As I have no idea on how to compare the stress
> tests, I can only say
> > that in 95% of all my test cases I can trigger a
> hard freeze within three
> > runs of:
> > 	rpm -ba gnomehack.spec
> > (You can get my src.rpm from:
> ftp://intevation.de/users/bernhard/)
> >
> > There was one day, when I could run it five times
> but still a hard
> > freeze later.
> >
> >
> > So we should gather more data on how to recreate
> the bug and then
> > ask more people to try to trigger it. As you can
> see from my preliminary
> > tests, there is no obvious pattern. Maybe we
> should also check the
> > different lombard models, if there are any. (At
> least I have a german
> > keyboard, e.g.)
> >
> >
> > Oh and more details from my part:
> > My RAM test from MacOS was completed fine,
> reporting no errors.
> > Adding the mem=64M option to the bootup (I am
> using bootx, could that
> > make a difference too?) seems to make the system
> more stable so far.
> >
> > Jeramy, Chris: can you tell us which kernel and
> bootprocess you are using?
> > 	Are you sure that linux uses all the memory?
> > 	Can you build gnomehack three times?
> >
> >
> > 	Bernhard
> > --
> > Professional Service around Free Software
>       (intevation.net)
> > The FreeGIS Project				            (freegis.org)
> > Association for a Free Informational
> Infrastructure            (ffii.org)
> >
>
>
>


=====
Gabriel Ricard
g_ricard@yahoo.com


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

Re: Lombard hard freeze (update: mem>64MB)

[Tim Wojtulewicz]

At 10:10 AM -0700 5/11/00, Gabriel Ricard wrote:
>I'm using yaboot too. Does your kernel intialize the
>video correctly when you first boot the machine up
>from a cold state (as in, it was shutdown, not a
>reboot)? I have to go into OF from a cold state, and
>boot my macos partition just to the point where the
>ROM initializes the video with a grey screen,
>otherwise, I get this odd lockup when I boot into
>Linux. As the kernel messages scroll down the screen
>its fine until it has to scroll the screen up, it just
>locks up when it does that. What kernel, yaboot, and
>LinuxPPC (or other distro) version are you using?

Yes, my Pismo will initialize the video correctly from a cold boot.
I'm using yaboot with kernel 2.2.15-pre19 I believe.

Tim
--

-------
Tim Wojtulewicz           Tim.Wojtulewicz@nau.edu
(520)523-2543             http://dana.ucc.nau.edu/~tjw4

In the Windows world, you are one click away from
harming yourself -- Elias Levy, Bugtraq

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

Re: Lombard hard freeze (update: mem>64MB)

[Seanano]

  The video initializes fine no matter how I boot into linux.  I'm running
kernel 2.2.15pre20 rsynced from linuxcare.com.au on Linuxppc2000.
Currently booting through yaboot 0.5.  I've posted my current kernel,
System.map, and modules folder on my website at:
  http://www.seanano.org/linux/ppc
Be warned however, that this is not a gerneric kernel.  I don't have a lot
of options enabled.  There is no ppp support, only bmac ethernet driver,
only MESH for scsi, so in other words, I wouldn't use this kernel except
for the lombard.

Sean


On Thu, 11 May 2000, Gabriel Ricard wrote:

>
> I'm using yaboot too. Does your kernel intialize the
> video correctly when you first boot the machine up
> from a cold state (as in, it was shutdown, not a
> reboot)? I have to go into OF from a cold state, and
> boot my macos partition just to the point where the
> ROM initializes the video with a grey screen,
> otherwise, I get this odd lockup when I boot into
> Linux. As the kernel messages scroll down the screen
> its fine until it has to scroll the screen up, it just
> locks up when it does that. What kernel, yaboot, and
> LinuxPPC (or other distro) version are you using?
>
>
> --- Seanano <sto9013@ksu.edu> wrote:
> >
> >   I've been running a lombard with 192 megs of RAM
> > since it was purchased
> > without any problem.  I've been running kernels
> > 2.2.14 - 2.2.15-pre20
> > with almost all of the 2.2.15-preXX kernels coming
> > from the rysnc server
> > at linuxcare.com.au.  Up until I installed the 9.0.4
> > upgrade a few weeks
> > ago I was using bootX, now I've switched over to
> > yaboot.  I usually
> > compile multiple programs at a time and I've never
> > seen any kernel errors
> > or freezes.  When the kernel boots it shows Total
> > Memory = 192MB.
> >
> >
> > [seanano@ip35 seanano]$ cat /proc/cpuinfo
> > processor       : 0
> > cpu             : 750
> > temperature     : 0 C
> > clock           : 399MHz
> > revision        : 130.2
> > bogomips        : 801.18
> > zero pages      : total 0 (0Kb) current: 0 (0Kb)
> > hits: 0/261 (0%)
> > machine         : PowerBook1,1
> > motherboard     : PowerBook1,1 MacRISC Power
> > Macintosh
> > L2 cache        : 1024K unified
> > memory          : 192MB
> > pmac-generation : NewWorld
> >
> >
> > [seanano@ip35 /proc]$ cat /proc/meminfo
> >         total:    used:    free:  shared: buffers:
> > cached:
> > Mem:  195981312 50966528 145014784 25296896  3297280
> > 22179840
> > Swap: 268427264        0 268427264
> > MemTotal:    191388 kB
> > MemFree:     141616 kB
> > MemShared:    24704 kB
> > Buffers:       3220 kB
> > Cached:       21660 kB
> > SwapTotal:   262136 kB
> > SwapFree:    262136 kB
> >
> >
> >   I'd be happy to run some tests if needed.  My
> > network access on the
> > lombard is a bit unstable right now so I couldn't
> > download the gnomehack
> > source...  I should be back to normal in a few days.
> >  I don't even have
> > gnome installed anyway...
> >
> >
> > Sean
> >
> >
> > On Thu, 11 May 2000, Bernhard Reiter wrote:
> >
> > > On Thu, May 11, 2000 at 11:07:39AM +0200, Michael
> > Schmitz wrote:
> > > > > > i've done some reasonably big compiles and
> > run seti@home at the same time.
> > > > > > however i've never kept at it for excessive
> > periods of time...i'll leave a
> > > > > > kernel make looping tonight building off an
> > nfs disk to the local disk
> > > > > > and see if anything turns up by morning...
> > > > >
> > > > > I have left my lombard running for 4 days in a
> > row which included several
> > > > > sleeps. During this period I did a 6 hour
> > stint playing with the development
> > > > > kernel code and did about 20 makes. No
> > problems and this was after
> > > > > I bumped it
> > > > > up to 192. I could try building GRASS just to
> > empirical though.
> > > >
> > > > Seems there's more people successfully running
> > >64M in their Lombard here
> > > > than it first seemed. Someone pointed to the
> > kernel problem corner, so
> > > > what kernel versions were these success stories
> > run on?
> > >
> > > Yes, we have to gather more data. Than then we
> > have to seperate
> > > the problems and search for similiarties and
> > differences in the
> > > machines.
> > >
> > > There seems to be a significant number of people
> > having this hard freeze
> > > problem with Lombards. Here is my preliminary
> > list, if I counted
> > > correctly:
> > >
> > > 	Hard Freezes occuring:
> > >
> > > Tim Wojtulewicz		Pismo 	128 MB
> > > Bernhard Reiter		Lombard 128,192   2.2.14,
> > 2.2.15pre19
> > > Gabriel Ricard	    	Lombard 192 MB   + other
> > problems
> > > Mario Scarpa	        hard freeze as described?  64
> > MB + other problems
> > >
> > >
> > > 	Running fine:
> > >
> > > jeramy b smith		lombard	192 MB
> > > chris mccraw		lombard 128 MB 		2.2.12 thru
> > 2.2.15pre20
> > >
> > >
> > >
> > > As I have no idea on how to compare the stress
> > tests, I can only say
> > > that in 95% of all my test cases I can trigger a
> > hard freeze within three
> > > runs of:
> > > 	rpm -ba gnomehack.spec
> > > (You can get my src.rpm from:
> > ftp://intevation.de/users/bernhard/)
> > >
> > > There was one day, when I could run it five times
> > but still a hard
> > > freeze later.
> > >
> > >
> > > So we should gather more data on how to recreate
> > the bug and then
> > > ask more people to try to trigger it. As you can
> > see from my preliminary
> > > tests, there is no obvious pattern. Maybe we
> > should also check the
> > > different lombard models, if there are any. (At
> > least I have a german
> > > keyboard, e.g.)
> > >
> > >
> > > Oh and more details from my part:
> > > My RAM test from MacOS was completed fine,
> > reporting no errors.
> > > Adding the mem=64M option to the bootup (I am
> > using bootx, could that
> > > make a difference too?) seems to make the system
> > more stable so far.
> > >
> > > Jeramy, Chris: can you tell us which kernel and
> > bootprocess you are using?
> > > 	Are you sure that linux uses all the memory?
> > > 	Can you build gnomehack three times?
> > >
> > >
> > > 	Bernhard
> > > --
> > > Professional Service around Free Software
> >       (intevation.net)
> > > The FreeGIS Project				            (freegis.org)
> > > Association for a Free Informational
> > Infrastructure            (ffii.org)
> > >
> >
> >
> >
>
>
> =====
> Gabriel Ricard
> g_ricard@yahoo.com
>
>
>


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

Re: Lombard hard freeze (update: mem>64MB)

[Gabriel Ricard]

Well I tried this out too and it didn't work. I got
the same lockup as soon as there was enough kernel
output that it had to scroll the screen up. It moves
all the text up one line and then locks up solid. I
wonder if maybe it's something else.

Can you tell me your exact configuration so I can
duplicate it on my lombard and see if it works? Kernel
args, etc.

So, your machine can boot from a cold state, load
yaboot from OF , boot Linux, and it works fine?

I really have to wonder what the difference is.

Do you have the 400MHz model with the 8MB ATI RAGE LT
Pro? Using atyfb?


--- Seanano <sto9013@ksu.edu> wrote:
>
>   The video initializes fine no matter how I boot
> into linux.  I'm running
> kernel 2.2.15pre20 rsynced from linuxcare.com.au on
> Linuxppc2000.
> Currently booting through yaboot 0.5.  I've posted
> my current kernel,
> System.map, and modules folder on my website at:
>   http://www.seanano.org/linux/ppc
> Be warned however, that this is not a gerneric
> kernel.  I don't have a lot
> of options enabled.  There is no ppp support, only
> bmac ethernet driver,
> only MESH for scsi, so in other words, I wouldn't
> use this kernel except
> for the lombard.
>
> Sean
>
>
> On Thu, 11 May 2000, Gabriel Ricard wrote:
>
> >
> > I'm using yaboot too. Does your kernel intialize
> the
> > video correctly when you first boot the machine up
> > from a cold state (as in, it was shutdown, not a
> > reboot)? I have to go into OF from a cold state,
> and
> > boot my macos partition just to the point where
> the
> > ROM initializes the video with a grey screen,
> > otherwise, I get this odd lockup when I boot into
> > Linux. As the kernel messages scroll down the
> screen
> > its fine until it has to scroll the screen up, it
> just
> > locks up when it does that. What kernel, yaboot,
> and
> > LinuxPPC (or other distro) version are you using?
> >
> >
> > --- Seanano <sto9013@ksu.edu> wrote:
> > >
> > >   I've been running a lombard with 192 megs of
> RAM
> > > since it was purchased
> > > without any problem.  I've been running kernels
> > > 2.2.14 - 2.2.15-pre20
> > > with almost all of the 2.2.15-preXX kernels
> coming
> > > from the rysnc server
> > > at linuxcare.com.au.  Up until I installed the
> 9.0.4
> > > upgrade a few weeks
> > > ago I was using bootX, now I've switched over to
> > > yaboot.  I usually
> > > compile multiple programs at a time and I've
> never
> > > seen any kernel errors
> > > or freezes.  When the kernel boots it shows
> Total
> > > Memory = 192MB.
> > >
> > >
> > > [seanano@ip35 seanano]$ cat /proc/cpuinfo
> > > processor       : 0
> > > cpu             : 750
> > > temperature     : 0 C
> > > clock           : 399MHz
> > > revision        : 130.2
> > > bogomips        : 801.18
> > > zero pages      : total 0 (0Kb) current: 0 (0Kb)
> > > hits: 0/261 (0%)
> > > machine         : PowerBook1,1
> > > motherboard     : PowerBook1,1 MacRISC Power
> > > Macintosh
> > > L2 cache        : 1024K unified
> > > memory          : 192MB
> > > pmac-generation : NewWorld
> > >
> > >
> > > [seanano@ip35 /proc]$ cat /proc/meminfo
> > >         total:    used:    free:  shared:
> buffers:
> > > cached:
> > > Mem:  195981312 50966528 145014784 25296896
> 3297280
> > > 22179840
> > > Swap: 268427264        0 268427264
> > > MemTotal:    191388 kB
> > > MemFree:     141616 kB
> > > MemShared:    24704 kB
> > > Buffers:       3220 kB
> > > Cached:       21660 kB
> > > SwapTotal:   262136 kB
> > > SwapFree:    262136 kB
> > >
> > >
> > >   I'd be happy to run some tests if needed.  My
> > > network access on the
> > > lombard is a bit unstable right now so I
> couldn't
> > > download the gnomehack
> > > source...  I should be back to normal in a few
> days.
> > >  I don't even have
> > > gnome installed anyway...
> > >
> > >
> > > Sean
> > >
> > >
> > > On Thu, 11 May 2000, Bernhard Reiter wrote:
> > >
> > > > On Thu, May 11, 2000 at 11:07:39AM +0200,
> Michael
> > > Schmitz wrote:
> > > > > > > i've done some reasonably big compiles
> and
> > > run seti@home at the same time.
> > > > > > > however i've never kept at it for
> excessive
> > > periods of time...i'll leave a
> > > > > > > kernel make looping tonight building off
> an
> > > nfs disk to the local disk
> > > > > > > and see if anything turns up by
> morning...
> > > > > >
> > > > > > I have left my lombard running for 4 days
> in a
> > > row which included several
> > > > > > sleeps. During this period I did a 6 hour
> > > stint playing with the development
> > > > > > kernel code and did about 20 makes. No
> > > problems and this was after
> > > > > > I bumped it
> > > > > > up to 192. I could try building GRASS just
> to
> > > empirical though.
> > > > >
> > > > > Seems there's more people successfully
> running
> > > >64M in their Lombard here
> > > > > than it first seemed. Someone pointed to the
> > > kernel problem corner, so
> > > > > what kernel versions were these success
> stories
> > > run on?
> > > >
> > > > Yes, we have to gather more data. Than then we
> > > have to seperate
> > > > the problems and search for similiarties and
> > > differences in the
> > > > machines.
> > > >
> > > > There seems to be a significant number of
> people
> > > having this hard freeze
> > > > problem with Lombards. Here is my preliminary
> > > list, if I counted
> > > > correctly:
> > > >
> > > > 	Hard Freezes occuring:
> > > >
> > > > Tim Wojtulewicz		Pismo 	128 MB
> > > > Bernhard Reiter		Lombard 128,192   2.2.14,
> > > 2.2.15pre19
> > > > Gabriel Ricard	    	Lombard 192 MB   + other
> > > problems
> > > > Mario Scarpa	        hard freeze as described?
>  64
> > > MB + other problems
> > > >
> > > >
> > > > 	Running fine:
> > > >
> > > > jeramy b smith		lombard	192 MB
> > > > chris mccraw		lombard 128 MB 		2.2.12 thru
> > > 2.2.15pre20
> > > >
> > > >
> > > >
> > > > As I have no idea on how to compare the stress
> > > tests, I can only say
> > > > that in 95% of all my test cases I can trigger
> a
> > > hard freeze within three
> > > > runs of:
> > > > 	rpm -ba gnomehack.spec
> > > > (You can get my src.rpm from:
> > > ftp://intevation.de/users/bernhard/)
> > > >
> > > > There was one day, when I could run it five
> times
> > > but still a hard
> > > > freeze later.
> > > >
> > > >
> > > > So we should gather more data on how to
> recreate
> > > the bug and then
> > > > ask more people to try to trigger it. As you
> can
> > > see from my preliminary
> > > > tests, there is no obvious pattern. Maybe we
> > > should also check the
> > > > different lombard models, if there are any.
> (At
> > > least I have a german
> > > > keyboard, e.g.)
> > > >
> > > >
> > > > Oh and more details from my part:
> > > > My RAM test from MacOS was completed fine,
> > > reporting no errors.
> > > > Adding the mem=64M option to the bootup (I am
> > > using bootx, could that
> > > > make a difference too?) seems to make the
> system
> > > more stable so far.
> > > >
> > > > Jeramy, Chris: can you tell us which kernel
> and
> > > bootprocess you are using?
> > > > 	Are you sure that linux uses all the memory?
> > > > 	Can you build gnomehack three times?
> > > >
> > > >
> > > > 	Bernhard
> > > > --
> > > > Professional Service around Free Software
> > >       (intevation.net)
> > > > The FreeGIS Project
> (freegis.org)
> > > > Association for a Free Informational
> > > Infrastructure            (ffii.org)
> > > >
> > >
> > >
> > >
> >
> >
> > =====
> > Gabriel Ricard
> > g_ricard@yahoo.com
> >
> >
> >
>
>
>


=====
Gabriel Ricard
g_ricard@yahoo.com


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

Re: Lombard hard freeze (update: mem>64MB)

[unit]

hi ..

it should also be noted that the wallstreet is suffering hard crashes
also (at least i am) .. just to complicate the issue.

My particular problem (which i had posted to the group a few weeks
back) relates to ppp (though what exactly locks up the machine i have
no idea).

What happens is this:

I am connected via ppp, my connection drops (which it is know to do
reasonably regularly). I restart the connection (/sbin/ifup ppp0), if i
tail -f */messages it goes through the whole connection procedure and
then once the handshaking has taken place, everything locks.
I've attempted to run pppd via console which works,
but the moment i switch console, again everything locks w/ no possiblity
of switching console. I've had this happen under these exact circumstances
on 20+ occasions, so, at least in my case it is reproducable. This only
happens after a modem hang-up, and i have yet to have one instance of
restarting ppp without this happening.

As far as compiling i have had no problems (mozilla being a recent 'large'
compile that wen't w/out incident.

I'm wondering if prehaps X isn't to blame ..

cal-s

machine info:

Powerbook Wallstreet 233mhz
192mbs RAM
pretty much vanilla lppc 2k install
2.2.15pre19 rsynced from linuxcare (pre9 and above  also effected)
XFree86-3.3.6-8a (using FBDev)
ppp-2.4.0b2-1 (though 2.3 was in use prior w/ the same results as above)


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

Re: Lombard hard freeze (update: mem>64MB)

[Bernhard Reiter]

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

I had a couple of incidents of strange modem or serial port
behaviour. It went away for no aparend reason.
I am not sure if it is a related problem, though.

One of my friend suggested to check on the serial numbers and ask
apple if this was a line of production somehow special
(done with certain chips or on the same week or something.)

The People count, btw is up to  6:2.

Best bet: Try the mem=64M option, if hard freezes cannot be triggered
anymore you might have the same problem.


        Hard Freezes occuring:

Tim Wojtulewicz         Pismo   128 MB
Bernhard Reiter         Lombard 128,192   2.2.14, 2.2.15pre19
Gabriel Ricard          Lombard 192 MB   + other problems
mpas1@nospam.iol.it (Marco Pascucci) 
			Lombard 192 MB	went away with "mem=64M"
Mario Scarpa            hard freeze as described?  64 MB + other problems
unit@panix.com		hard freeze as described? Walstreet 192 MB  ppp problem


        Running fine:

jeramy b smith          lombard 192 MB
chris mccraw            lombard 128 MB          2.2.12 thru 2.2.15pre20


	Bernhard



On Sun, May 14, 2000 at 02:42:15AM -0400, unit@panix.com wrote:
> it should also be noted that the wallstreet is suffering hard crashes
> also (at least i am) .. just to complicate the issue.
> 
> My particular problem (which i had posted to the group a few weeks
> back) relates to ppp (though what exactly locks up the machine i have
> no idea).
> 
> What happens is this:
> 
> I am connected via ppp, my connection drops (which it is know to do
> reasonably regularly). I restart the connection (/sbin/ifup ppp0), if i
> tail -f */messages it goes through the whole connection procedure and
> then once the handshaking has taken place, everything locks. 
> I've attempted to run pppd via console which works,
> but the moment i switch console, again everything locks w/ no possiblity
> of switching console. I've had this happen under these exact circumstances
> on 20+ occasions, so, at least in my case it is reproducable. This only
> happens after a modem hang-up, and i have yet to have one instance of
> restarting ppp without this happening. 
> 
> As far as compiling i have had no problems (mozilla being a recent 'large'
> compile that wen't w/out incident.

-- 
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: Lombard hard freeze (update: mem>64MB)

[Mario Scarpa]

Bernhard Reiter wrote:

> Mario Scarpa            hard freeze as described?  64 MB + other problems

Hi Bernhard,

I was out for a while, now I'm back.
My config is like the following:
Lombard 400MHz with 64MB (from Apple) running 2.2.15pre20 on Debian 2.2.

I'm experiencing (seldom) freezes with this config when I have
some heavy network activity and, even more seldom, when the
system boots up and initialize the serial driver.
My problems started when I compiled the USB driver into the kernel
(or, at least, began to be visible).

No problem during any compilation (and I do quite a lot of this)...

--
Mario Scarpa

Mondonet NOC
Phone: +39 06 52.47.37.02

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

Re: Lombard hard freeze (update: mem>64MB)

[Bernhard Reiter]

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

On Tue, May 16, 2000 at 05:01:08PM +0200, Mario Scarpa wrote:
> Bernhard Reiter wrote:
> > Mario Scarpa            hard freeze as described?  64 MB + other problems

> I was out for a while, now I'm back.
> My config is like the following:
> Lombard 400MHz with 64MB (from Apple) running 2.2.15pre20 on Debian 2.2.
> 
> I'm experiencing (seldom) freezes with this config when I have
> some heavy network activity and, even more seldom, when the
> system boots up and initialize the serial driver.
> My problems started when I compiled the USB driver into the kernel
> (or, at least, began to be visible).
> 
> No problem during any compilation (and I do quite a lot of this)...

Well with 64MB I never had freeses to far.

Chris told me that he has a 333Mhz lombard.
I have the 400 Mhz model, maybe this makes a difference which is
more problematic when the clock speed it higher.

Jeramy, what speed does your lombard run on?
	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 --]

Re: Lombard hard freeze (update: mem>64MB)

[jeramy b smith]

> > I'm experiencing (seldom) freezes with this config when I have
> > some heavy network activity and,
I don't have any ethernet problems except for a dropped frame when trying to
retrieve a dhcp address. Aside from that, I can do ultra-high 500kbps+
sustained network activity with no problems.


> Well with 64MB I never had freeses to far.
>
> Chris told me that he has a 333Mhz lombard.
> I have the 400 Mhz model, maybe this makes a difference which is
> more problematic when the clock speed it higher.
>
> Jeramy, what speed does your lombard run on?
> 	Bernhard

333mhz/192MB of memory. Current uptime:
11:01am  up 14:52,  3 users,  load average: 0.07, 0.09, 0.04


-Jeramy

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

Re: Lombard hard freeze (update: mem>64MB)

[Gabriel Ricard]

I should note that I removed my 128MB SODIMM and still
had problems with freezes. I am going to call the
company I bought my PB from and ask them whether or
not my 128MB SODIMM is low profile or high profile
only, maybe I can figure out whether or not I've got a
bad 64MB SODIMM in the low profile slot.

--- Bernhard Reiter <bernhard@intevation.de> wrote:
> On Tue, May 16, 2000 at 05:01:08PM +0200, Mario
> Scarpa wrote:
> > Bernhard Reiter wrote:
> > > Mario Scarpa            hard freeze as
> described?  64 MB + other problems
>
> > I was out for a while, now I'm back.
> > My config is like the following:
> > Lombard 400MHz with 64MB (from Apple) running
> 2.2.15pre20 on Debian 2.2.
> >
> > I'm experiencing (seldom) freezes with this config
> when I have
> > some heavy network activity and, even more seldom,
> when the
> > system boots up and initialize the serial driver.
> > My problems started when I compiled the USB driver
> into the kernel
> > (or, at least, began to be visible).
> >
> > No problem during any compilation (and I do quite
> a lot of this)...
>
> Well with 64MB I never had freeses to far.
>
> Chris told me that he has a 333Mhz lombard.
> I have the 400 Mhz model, maybe this makes a
> difference which is
> more problematic when the clock speed it higher.
>
> Jeramy, what speed does your lombard run on?
> 	Bernhard
> --
> Professional Service around Free Software
>     (intevation.net)
> The FreeGIS Project				            (freegis.org)
> Association for a Free Informational Infrastructure
>           (ffii.org)
>

> ATTACHMENT part 2 application/pgp-signature



=====
Gabriel Ricard
g_ricard@yahoo.com


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

Re: Lombard hard freeze (update: mem>64MB)

[Gabriel Ricard]

I was doing some transfers like that as well,
(downloading ISOs and the like.. heh) and never had
any problems. I don't think this is a network issue
really.

It seems that those with 3xxMHz CPUs don't have the
same problems that those with the 400MHz CPUs do. Is
this correct? I'm also wondering if there were just
some bad SODIMMs that made it into the Lombards and
that's causing the problems...

--- jeramy b smith <ultrapenguin@netscape.net> wrote:
>
> > > I'm experiencing (seldom) freezes with this
> config when I have
> > > some heavy network activity and,
> I don't have any ethernet problems except for a
> dropped frame when trying to
> retrieve a dhcp address. Aside from that, I can do
> ultra-high 500kbps+
> sustained network activity with no problems.
>
>
> > Well with 64MB I never had freeses to far.
> >
> > Chris told me that he has a 333Mhz lombard.
> > I have the 400 Mhz model, maybe this makes a
> difference which is
> > more problematic when the clock speed it higher.
> >
> > Jeramy, what speed does your lombard run on?
> > 	Bernhard
>
> 333mhz/192MB of memory. Current uptime:
> 11:01am  up 14:52,  3 users,  load average: 0.07,
> 0.09, 0.04
>
>
> -Jeramy
>
>


=====
Gabriel Ricard
g_ricard@yahoo.com


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

Re: Lombard hard freeze (update: mem>64MB)

[Michael Schmitz]

> I was doing some transfers like that as well,
> (downloading ISOs and the like.. heh) and never had
> any problems. I don't think this is a network issue
> really.
>
> It seems that those with 3xxMHz CPUs don't have the
> same problems that those with the 400MHz CPUs do. Is
> this correct? I'm also wondering if there were just
> some bad SODIMMs that made it into the Lombards and
> that's causing the problems...

Can't be correct, mine is a G3-400 (64 MB) and I don't
see any kernel lockups that can't be attributed to known
bugs (testing XFree 4.0 or HFS, currently).
While I haven't downloaded ISO images recently, I've had
the machine running on a 100 Mb network here with quite
some data going in or out.

	Michael


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

Re: Lombard hard freeze (update: mem>64MB)

[Gabriel Ricard]

Ok, so it seems like it must be a RAM issue. Although,
I HAVE tested compiling the kernel, etc with only the
original 64MB installed, and still got lockups. So,
mybe I should have computerware do some RAM tests for
me and see if that is the problem.

--- Michael Schmitz
<schmitz@mail.biophys.uni-duesseldorf.de> wrote:
> > I was doing some transfers like that as well,
> > (downloading ISOs and the like.. heh) and never
> had
> > any problems. I don't think this is a network
> issue
> > really.
> >
> > It seems that those with 3xxMHz CPUs don't have
> the
> > same problems that those with the 400MHz CPUs do.
> Is
> > this correct? I'm also wondering if there were
> just
> > some bad SODIMMs that made it into the Lombards
> and
> > that's causing the problems...
>
> Can't be correct, mine is a G3-400 (64 MB) and I
> don't
> see any kernel lockups that can't be attributed to
> known
> bugs (testing XFree 4.0 or HFS, currently).
> While I haven't downloaded ISO images recently, I've
> had
> the machine running on a 100 Mb network here with
> quite
> some data going in or out.
>
> 	Michael
>
>


=====
Gabriel Ricard
g_ricard@yahoo.com


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