headers
George Harvey | 4 Dec 2006 21:13

Re: Building perl hangs on -current

On Thu, 30 Nov 2006 22:37:36 +0000
George Harvey <fr30 <at> dial.pipex.com> wrote:

> On Wed, 29 Nov 2006 16:28:01 +0000
> George Harvey <fr30 <at> dial.pipex.com> wrote:
> 
> > On Tue, 28 Nov 2006 00:33:26 -0500
> > "Stephen M. Rumble" <stephen.rumble <at> utoronto.ca> wrote:
> > 
> > > Quoting George Harvey <fr30 <at> dial.pipex.com>:
> > > 
> [ snip ]
> 
> > Tried a local build and got a seg fault after about 2hrs building,
> > no hang though. Since I had no problems on an O2 running 3.1, I
> > think I'll re-install the Challenge S with 3.1 userland and try the
> > local build again with that.
> 
> I had a hunt in my disk collection and found a Seagate drive that
> would allow the 3.1 install kernel to boot on my Challenge S without
> locking up on the SCSI probe. Instead, it panics while creating mfs.
> The last lines on the console are included below. I've been trying
> various kernels on this machine and that's the first time I've seen an
> amap_wipeout. Now that I've found a disk that allows 3.1 to boot, I
> think I'll try attaching it to my O2, do the 3.1 install on that, and
> then try it back in the Challenge S.

[ snip ]

After several disk swaps, re-installs and Perl builds, I think I'm
(Continue reading)

Permalink | Reply | 2 comments |
headers
Stephen M. Rumble | 5 Dec 2006 04:03
Picon
Picon
Favicon

Re: Building perl hangs on -current

Quoting George Harvey <fr30 <at> dial.pipex.com>:

> On Thu, 30 Nov 2006 22:37:36 +0000
> George Harvey <fr30 <at> dial.pipex.com> wrote:
> [ snip ]
>
> After several disk swaps, re-installs and Perl builds, I think I'm
> finally getting somewhere. The combination that's currently working is
> 3.1 userland with a -current (4.99.3) kernel. I've successfully built
> Perl 5.8.8 from pkgsrc, with pkgsrc NFS mounted over the G130 100Mb
> Ethernet interface, and I'm currently building a number of other
> packages that I need. Looks like it was the combination of a 4.0 BETA
> userland (before the recent re-branch) and a -current kernel that was
> causing the kernel hangs.

Glad to hear that you're having success. Now if only we knew why, exactly.

I was hoping that somebody more knowledgable would comment regarding  
the "amap_wipeout" panic you saw, but I imagine the right eyes aren't  
watching this quiet list. When you get a chance, could you send the  
R5000 revision? It should be in the dmesg. Also, is your O2 an R5000  
as well? I'm wondering if our kernel or toolchain has any problems  
with possibly older revisions of those parts.

When I get a chance in a few weeks I'll have to run some builds and  
see if I can reproduce these problems on my R4400 machines.

Regards,
Steve
(Continue reading)

Permalink | Reply | 1 comment |
headers
George Harvey | 5 Dec 2006 21:39

Re: Building perl hangs on -current

On Mon,  4 Dec 2006 22:03:03 -0500
"Stephen M. Rumble" <stephen.rumble <at> utoronto.ca> wrote:

> Quoting George Harvey <fr30 <at> dial.pipex.com>:
> 
> > On Thu, 30 Nov 2006 22:37:36 +0000
> > George Harvey <fr30 <at> dial.pipex.com> wrote:
> > [ snip ]
> >
> > After several disk swaps, re-installs and Perl builds, I think I'm
> > finally getting somewhere. The combination that's currently working
> > is 3.1 userland with a -current (4.99.3) kernel. I've successfully
> > built Perl 5.8.8 from pkgsrc, with pkgsrc NFS mounted over the G130
> > 100Mb Ethernet interface, and I'm currently building a number of
> > other packages that I need. Looks like it was the combination of a
> > 4.0 BETA userland (before the recent re-branch) and a -current
> > kernel that was causing the kernel hangs.
> 
> Glad to hear that you're having success. Now if only we knew why,
> exactly.

My guess would be something different in the shared libraries but I know
that doesn't help much.

> I was hoping that somebody more knowledgable would comment regarding  
> the "amap_wipeout" panic you saw, but I imagine the right eyes aren't 
>  watching this quiet list. When you get a chance, could you send the  
> R5000 revision? It should be in the dmesg. Also, is your O2 an R5000  
> as well? I'm wondering if our kernel or toolchain has any problems  
> with possibly older revisions of those parts.
(Continue reading)

Permalink | Reply | 0 comments |
headers
Rodolphe De Saint Leger | 10 Dec 2006 00:20
Picon

Re: Boot freeze on IP22

> I've got a nice full screen output (black screen and green kernel
> messages), the grtwo driver seems to attach. I'll give a try next week
> for a prom kernel (can't do it before, sorry)
>

Hi,

Unfortunately, the kernel hangs at various places
I thought it was almost there when it asks me for the root device, but
the machine was stopped :(

Regards,
Rodolphe
--

-- 
int main(void){char*a="\n",b=34,*d="int main(void){char*a=",
*c="%s%c%cn%c,b=34,*d=%c%s%c,%s*c=%c%s%c,%s*e=%c%s%c;%s%s;}%s",
*e="printf(c,d,b,92,b,b,d,b,a,b,c,b,a,b,e,b,a,e,a);exit(0)";
printf(c,d,b,92,b,b,d,b,a,b,c,b,a,b,e,b,a,e,a);exit(0);}
Permalink | Reply | 10 comments |
headers
Stephen M. Rumble | 12 Dec 2006 03:10
Picon
Picon
Favicon

Re: Boot freeze on IP22

Quoting Rodolphe De Saint Leger <rdesaintleger <at> gmail.com>:

>> I've got a nice full screen output (black screen and green kernel
>> messages), the grtwo driver seems to attach. I'll give a try next week
>> for a prom kernel (can't do it before, sorry)
>>
>
> Hi,
>
> Unfortunately, the kernel hangs at various places
> I thought it was almost there when it asks me for the root device, but
> the machine was stopped :(

Which various places? Do you mean that after you've specified the boot  
device it freezes, or are you unable to input the boot device at all?

Steve
Permalink | Reply | 9 comments |
headers
Rodolphe De Saint Leger | 12 Dec 2006 09:15
Picon

Re: Boot freeze on IP22

On 12/12/06, Stephen M. Rumble <stephen.rumble <at> utoronto.ca> wrote:
> Quoting Rodolphe De Saint Leger <rdesaintleger <at> gmail.com>:
>
>
> Which various places? Do you mean that after you've specified the boot
> device it freezes, or are you unable to input the boot device at all?
>
The first try, the machine hanged at the same place (int0)
The second try it came to the boot device question, and I was unable
to enter the boot device
The last try it hanged at another place in the dmesg before the boot question.

--

-- 
int main(void){char*a="\n",b=34,*d="int main(void){char*a=",
*c="%s%c%cn%c,b=34,*d=%c%s%c,%s*c=%c%s%c,%s*e=%c%s%c;%s%s;}%s",
*e="printf(c,d,b,92,b,b,d,b,a,b,c,b,a,b,e,b,a,e,a);exit(0)";
printf(c,d,b,92,b,b,d,b,a,b,c,b,a,b,e,b,a,e,a);exit(0);}
Permalink | Reply | 8 comments |
headers
Christopher SEKIYA | 12 Dec 2006 13:11

Re: Boot freeze on IP22

On Tue, Dec 12, 2006 at 09:15:34AM +0100, Rodolphe De Saint Leger wrote:

> The first try, the machine hanged at the same place (int0)
> The second try it came to the boot device question, and I was unable
> to enter the boot device
> The last try it hanged at another place in the dmesg before the boot 
> question.

Smells like a secondary cache problem.
--

-- 

-- Chris
	GPG key FEB9DE7F (91AF 4534 4529 4BCC 31A5  938E 023E EEFB FEB9 DE7F)
Permalink | Reply | 7 comments |
headers
Rodolphe De Saint Leger | 12 Dec 2006 13:20
Picon

Re: Boot freeze on IP22

>
> Smells like a secondary cache problem.
>

Is there a way to help solving this problem ?

--

-- 
int main(void){char*a="\n",b=34,*d="int main(void){char*a=",
*c="%s%c%cn%c,b=34,*d=%c%s%c,%s*c=%c%s%c,%s*e=%c%s%c;%s%s;}%s",
*e="printf(c,d,b,92,b,b,d,b,a,b,c,b,a,b,e,b,a,e,a);exit(0)";
printf(c,d,b,92,b,b,d,b,a,b,c,b,a,b,e,b,a,e,a);exit(0);}
Permalink | Reply | 6 comments |
headers
Christopher SEKIYA | 12 Dec 2006 13:29

Re: Boot freeze on IP22

On Tue, Dec 12, 2006 at 01:20:19PM +0100, Rodolphe De Saint Leger wrote:

> Is there a way to help solving this problem ?

*shrug* You could try making mips_machdep_cache_config() in
sys/arch/sgimips/machdep.c look like this:

	void mips_machdep_cache_config(void)
	{
		mips3_cp0_config_write( (mips3_cp0_config_read()) & ~MIPS3_CONFIG_SE);
		mips_sdcache_size = 0;
		mips_sdcache_line_size = 0;
	}

If that results in a working system, then you've got a faulty CPU module.

--

-- 

-- Chris
	GPG key FEB9DE7F (91AF 4534 4529 4BCC 31A5  938E 023E EEFB FEB9 DE7F)
Permalink | Reply | 5 comments |
headers
Rodolphe De Saint Leger | 12 Dec 2006 13:44
Picon

Re: Boot freeze on IP22

>
> *shrug* You could try making mips_machdep_cache_config() in
> sys/arch/sgimips/machdep.c look like this:
>
>         void mips_machdep_cache_config(void)
>         {
>                 mips3_cp0_config_write( (mips3_cp0_config_read()) & ~MIPS3_CONFIG_SE);
>                 mips_sdcache_size = 0;
>                 mips_sdcache_line_size = 0;
>         }
>

OK, I'll try this weekend when I'll get physical access to the machine

> If that results in a working system, then you've got a faulty CPU module.
>

The machine seems to run fine under IRIX (6.5.22), does that mean the
CPU module has an hardware problem (I ran full diagnostic from the
ARCS prom without any error), or does that mean that the cpu module is
not fully supported ?

The CPU Module is a R5000/180MHz, I've seen some year ago that there
was problems with R5k Indys, is it still right ?

--

-- 
int main(void){char*a="\n",b=34,*d="int main(void){char*a=",
*c="%s%c%cn%c,b=34,*d=%c%s%c,%s*c=%c%s%c,%s*e=%c%s%c;%s%s;}%s",
*e="printf(c,d,b,92,b,b,d,b,a,b,c,b,a,b,e,b,a,e,a);exit(0)";
printf(c,d,b,92,b,b,d,b,a,b,c,b,a,b,e,b,a,e,a);exit(0);}
(Continue reading)

Permalink | Reply | 4 comments |

Gmane