[parisc-linux] Gcc-3.2 beside gcc-3.0: HOWTO?

[parisc-linux] Gcc-3.2 beside gcc-3.0: HOWTO?

[jsoe0708]

Hi all,

I install gcc-3.2 beside default gcc-3.0.

I would like to use gcc-3.2 to compile the latest cvs kernel. HOWTO do this?

Thanks in advance,
    Joel

PS: with gcc-3.1.1 snapshot I reach to obtain a bootable 32bit kernel but
presenting a problem with network connection. Was I alone to observe this?

RE: [parisc-linux] Gcc-3.2 beside gcc-3.0: HOWTO?

[jsoe0708]

>
>Hi all,
>
>I install gcc-3.2 beside default gcc-3.0.
>
>I would like to use gcc-3.2 to compile the latest cvs kernel. HOWTO do this?
>
>Thanks in advance,
>    Joel
>
>PS: with gcc-3.1.1 snapshot I reach to obtain a bootable 32bit kernel but
>presenting a problem with network connection. Was I alone to observe this?
>
I also forget to mentionned that I also applied recommendation in /usr/share/doc/gcc-3.2-base/README.Debian.gz
(ie: CC="gcc-3.2" ; export CC but in the kernel special case there is no
./configure step so may be there is another teaps. And with snapshot gcc
was build in another tree so the problem didn't exists)

Many thanks again for all help,
    Joel

Re: [parisc-linux] Gcc-3.2 beside gcc-3.0: HOWTO?

[Randolph Chung]

> I would like to use gcc-3.2 to compile the latest cvs kernel. HOWTO do this?

edit the toplevel kernel Makefile and change the HOSTCC and CC lines 
so that HOSTCC=gcc-3.2 and CC=$(CROSS_COMPILE)gcc-3.2

randolph
--  
Randolph Chung
Debian GNU/Linux Developer, hppa/ia64 ports
http://www.tausq.org/

Re: [parisc-linux] Gcc-3.2 beside gcc-3.0: HOWTO?

[jsoe0708]

>> I would like to use gcc-3.2 to compile the latest cvs kernel. HOWTO do
>this?
>
>edit the toplevel kernel Makefile and change the HOSTCC and CC lines 
>so that HOSTCC=gcc-3.2 and CC=$(CROSS_COMPILE)gcc-3.2
>

Oops the 32bits kernel which I obtain, boot well on my b2k but ip connection
problem is always there: the system seems to loop somewhere with ssh (heart
bit seems life and no more response neither at serial console, neither at
ssh prompt) and telnet causes an HPMC (bus timeout?)

I try find information on howto run sshd with gdb on the server (MARC ml
archives) but do not found any relevant info. And i don't know if Bruno LKCD
would help if near to be ready.

What can I do?

Joel

PS: this problem was not with gcc-3.2 (now snapshot 3.3) and it is a long
time I play with gcc snapshot to compare.

Re: [parisc-linux] Gcc-3.2 beside gcc-3.0: HOWTO?

[Randolph Chung]

> Oops the 32bits kernel which I obtain, boot well on my b2k but ip connection
> problem is always there: the system seems to loop somewhere with ssh (heart
> bit seems life and no more response neither at serial console, neither at
> ssh prompt) and telnet causes an HPMC (bus timeout?)

looking up the iaoq and gr02 values reported in the hpmc in System.map 
would be the first step...

randolph
--  
Randolph Chung
Debian GNU/Linux Developer, hppa/ia64 ports
http://www.tausq.org/

Re: [parisc-linux] Gcc-3.2 beside gcc-3.0: HOWTO?

[jsoe0708]

Hi Randolph,

>
>> Oops the 32bits kernel which I obtain, boot well on my b2k but ip connection
>> problem is always there: the system seems to loop somewhere with ssh (heart
>> bit seems life and no more response neither at serial console, neither
>at
>> ssh prompt) and telnet causes an HPMC (bus timeout?)
>
>looking up the iaoq and gr02 values reported in the hpmc in System.map 
>would be the first step...
>
Too bad, I forget to mentionned that I just read some HPMC messages on the
LCD display of my b2k and do not get any status dump info on console (which
just stay locked at login prompt). Do you think that kdb works now? (if yes
where can I learn how to get iaoq and gr02 info?)

Thanks a lot,
    Joel

Re: [parisc-linux] Gcc-3.2 beside gcc-3.0: HOWTO?

[Randolph Chung]

> Too bad, I forget to mentionned that I just read some HPMC messages on the
> LCD display of my b2k and do not get any status dump info on console (which
> just stay locked at login prompt). Do you think that kdb works now? (if yes
> where can I learn how to get iaoq and gr02 info?)

at the firmware prompt, 'ser pim' will read the hpmc info that's stored
in pim.

kdb should work, although i haven't tried recently.

randolph

Re: [parisc-linux] Gcc-3.2 beside gcc-3.0: HOWTO?

[jsoe0708]

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

Hello Randolph,

I need additional help.

>
>> Too bad, I forget to mentionned that I just read some HPMC messages on
>the
>> LCD display of my b2k and do not get any status dump info on console (which
>> just stay locked at login prompt). Do you think that kdb works now? (if
>yes
>> where can I learn how to get iaoq and gr02 info?)
>
>at the firmware prompt, 'ser pim' will read the hpmc info that's stored
>in pim.

Here is the pim I get (I do a clearpim before to be sure):

PROCESSOR PIM INFORMATION

-----------------  Processor 0 HPMC Information ------------------

Timestamp = 
  Tue Sep  3 14:26:13 GMT 2002    (20:02:09:03:14:26:13)

HPMC Chassis Codes = 2cbf0  2500b  2cbf4  2cbfc  

General Registers 0 - 31
00-03   0000000000000000  00000000103b7244  0000000010108064  00000000207f8000
04-07   00000000102b6800  00000000207fc940  00000000207f8000  0000000000000008
08-11   00000000107e2e94  00000000103b6e40  0000000000000400  00000000f0408cd8
12-15   00000000f0407ef0  000000001f1f86d0  00000000000020f8  0000000000035cec
16-19   00000000107fcdc0  0000000000017800  0000000000029494  ffffffffffffffff
20-23   000000000000000e  0000000000000000  0000000000004000  00000000102fd810
24-27   0000000000002a4f  00000000107fcdc0  000000000000000f  00000000102ea010
28-31   0000000000000030  0000000011430100  0000000011430340  00000000103bb010

<Press any key to continue (q to quit)> 

Control Registers 0 - 31
00-03   0000000000000000  0000000000000000  0000000000000000  0000000000000000
04-07   0000000000000000  0000000000000000  0000000000000000  0000000000000000
08-11   0000000000000634  0000000000000000  00000000000000c0  0000000000000017
12-15   0000000000000000  0000000000000000  0000000000107000  0000000000000000
16-19   0000007be95ffc60  0000000000000000  0000000010108638  000000000fa11288
20-23   0000000010240224  0000000048030104  000000000004000e  0000000080000000
24-27   0000000000305000  0000000000305000  0000000000044021  00000000f0412000
28-31   0000000055555555  0000000055555555  000000001f1f8000  00000000103a8000
Space Registers 0 - 7

00-03   00000000          0000031a          00000000          0000031a
04-07   00000000          00000000          00000000          00000000

<Press any key to continue (q to quit)> 

IIA Space                    = 0x0000000000000000
IIA Offset                   = 0x000000001010863c
Check Type                   = 0x20000000
CPU State                    = 0x9e000004
Cache Check                  = 0x00000000
TLB Check                    = 0x00000000
Bus Check                    = 0x003010bb
Assists Check                = 0x00000000
Assist State                 = 0x00000000
Path Info                    = 0x00031800
System Responder Address     = 0xfffffffffed10200
System Requestor Address     = 0xfffffffffffa0000

Floating-Point Registers 0 - 31
00-03   0000001f00000000  0000000000000000  0000000000000000  0000000000000000
04-07   00004000102fe810  000000011014cff4  f0000000102fe810  1037a010102de000
08-11   1030402000000002  0000000200000002  00000000102fd810  1039f810102fa810
12-15   103a00001079c000  0000000200000002  000000001039e264  102fa810103a0000
16-19   102fd8100000000b  103b6e4b102fdb28  0000000f103b6810  f00000000000000f
20-23   000000011039e000  f00000001013c70c  0000000000000008  0000000000000000
24-27   0000000a1fff90a0  0000999900000000  1079c00000000001  00001fb6102b6000
28-31   106b46a0102b61a8  1079c0001013e268  102fa810103a0000  100d4000100d45d0

<Press any key to continue (q to quit)> 


'9000/785 B,C,J Workstation Unarchitected (per-CPU)', rev 1, 140 bytes:

Check Summary                = 0xcb81041000000000
Available Memory             = 0x0000000010000000
CPU Diagnose Register 2      = 0x0301000000000004
CPU Status Register 0        = 0x2420c20000000000
CPU Status Register 1        = 0x8080000000000000
SADD LOG                     = 0x000000004e657874
Read Short LOG               = 0xc1af00fffee00f28
ERROR_STATUS                 = 0x0000000000000010
MEM_ADDR                     = 0x000001ff3fffffff
MEM_SYND                     = 0x0000000000000000
MEM_ADDR_CORR                = 0x000001ff3fffffff
MEM_SYND_CORR                = 0x0000000000000000
RUN_DATA_HIGH                = 0xc1bff0fffed08040
RUN_DATA_LOW                 = 0xc1bff0fffed08040
RUN_CTRL                     = 0x0000021c00001418
RUN_ADDR                     = 0xc1bff0fffed08040
System Responder Path        = 0x00ffffffffffffff


HPMC PIM Analysis Information:

Timestamp = 
  Tue Sep  3 14:26:13 GMT 2002    (20:02:09:03:14:26:13)


'9000/785 B,C,J Workstation HPMC PIM Analysis (per-CPU)', rev 0, 1304 bytes:

A Data Miss Timeout occurred while CPU 0 was
requesting information.


Memory/IO Controller Error Analysis Information:

The Memory/IO Controller only observed the Broadcast Error.  It did not log
any additional information about the HPMC.


Memory Error Log Information:

Timestamp = 
  Tue Sep  3 14:26:13 GMT 2002    (20:02:09:03:14:26:13)


'9000/785 B,C,J Workstation Memory Error Log', rev 0, 64 bytes:

   No memory errors logged


I/O Module Error Log Information:

Timestamp = 
  Tue Sep  3 14:26:13 GMT 2002    (20:02:09:03:14:26:13)


'9000/785 B,C,J Workstation IO Error Log', rev 0, 228 bytes:

 Rope     Word1        Word2            Word3
------ ------------ ------------
   0    0x00000000   0x0e0cc009   0x00000000fed30048
   1    0x00000000   0x1e0cc009   0x00000000fed32048
   2    ----------   0x2e0cc009   ------------------
   3    ----------   0x3e0cc009   ------------------
   4    ----------   0x4e0cc009   ------------------
   5    ----------   0x5e0cc009   ------------------
   6    ----------   0x6e0cc009   ------------------
   7    ----------   0x7e0cc009   ------------------
Service Menu: Enter command > 

Well I presume that gr02 is 10108064 (from:
General Registers 0 - 31
00-03   0000000000000000  00000000103b7244  0000000010108064  00000000207f8000)

But where is iaoq (I do not found in linux/Documentation/parisc)?

here is what I got: grep 101080 /boot/System.map-2.4.19-pa9
10108000 T syscall_exit_rfi
10108064 t intr_return
10108078 t intr_check_resched
10108084 t intr_check_sig
10108090 t intr_restore


>
>kdb should work, although i haven't tried recently.
>

I will try later if required.

Thanks in advance for additional help,
    Joel

PS: I try to attached a complete log of the crash sequence b2k.crash.doc


[-- Attachment #2: b2k.crash.doc --]
[-- Type: application/msword, Size: 27057 bytes --]

Re: [parisc-linux] Gcc-3.2 beside gcc-3.0: HOWTO?

[Randolph Chung]

> General Registers 0 - 31
> 00-03   0000000000000000  00000000103b7244  0000000010108064  00000000207f8000
                                              ^^^^^^^^^^^^^^^^ GR02, aka
                                              the return pointer

> Control Registers 0 - 31
> 00-03   0000000000000000  0000000000000000  0000000000000000  0000000000000000
> 04-07   0000000000000000  0000000000000000  0000000000000000  0000000000000000
> 08-11   0000000000000634  0000000000000000  00000000000000c0  0000000000000017
> 12-15   0000000000000000  0000000000000000  0000000000107000  0000000000000000
> 16-19   0000007be95ffc60  0000000000000000  0000000010108638  000000000fa11288
                                                                ^^^^^^^^^^^^^^^^
cr19 is the "IIR", this is the insn that caused the fault
in this case, this insn is stw r1,4(sr0,r29)


> 20-23   0000000010240224  0000000048030104  000000000004000e  0000000080000000
> 24-27   0000000000305000  0000000000305000  0000000000044021  00000000f0412000
> 28-31   0000000055555555  0000000055555555  000000001f1f8000  00000000103a8000
                            ^^^^^^^^^^^^^^^^ which looks quite bogus

> IIA Space                    = 0x0000000000000000
> IIA Offset                   = 0x000000001010863c
this is the "iaoq" -- the instruction pointer

> But where is iaoq (I do not found in linux/Documentation/parisc)?
> 
> here is what I got: grep 101080 /boot/System.map-2.4.19-pa9
> 10108000 T syscall_exit_rfi
> 10108064 t intr_return
> 10108078 t intr_check_resched
> 10108084 t intr_check_sig
> 10108090 t intr_restore

is this the system.map from the kernel you are building?
if it is, then intr_return is the calling function (one up in the
stack). the function that includes 1010863c is the one that one that's
causing the fault. that would be one place to look.

hth
randolph
--  
Randolph Chung
Debian GNU/Linux Developer, hppa/ia64 ports
http://www.tausq.org/

Re: [parisc-linux] Gcc-3.2 beside gcc-3.0: HOWTO?

[jsoe0708]

>> But where is iaoq (I do not found in linux/Documentation/parisc)?
>> 
>> here is what I got: grep 101080 /boot/System.map-2.4.19-pa9
>> 10108000 T syscall_exit_rfi
>> 10108064 t intr_return
>> 10108078 t intr_check_resched
>> 10108084 t intr_check_sig
>> 10108090 t intr_restore
>
>is this the system.map from the kernel you are building?
>if it is, then intr_return is the calling function (one up in the
>stack). the function that includes 1010863c is the one that one that's
>causing the fault. that would be one place to look.
>

Hmm the only entry I found concerning intr_return are content into entry.S.

Sorry for the moment I have not enough time to learn parisc asm, how is it
implemented with gcc and how to interface with C, ...

Thanks anyway for all help,
    Joel


Big Brother Anders  - With Tiscali you will see it all !  Check it up on
 www.tiscali.be/bigbrother