Betr.: Re: [parisc-linux] Trace/breakpoint trap

Betr.: Re: [parisc-linux] Trace/breakpoint trap

[Jurriaan Kalkman]

>On Tue, Sep 25, 2001 at 06:18:57PM -0600, Matt Taggart wrote:
>>=20
>> Richard Allen writes...
>>=20
>> > Here's a wild one:
>> >=20
>> > bofh:~/rpm-4.0.3/rpmdb# make
>> > Trace/breakpoint trap
>> > bofh:~/rpm-4.0.3/rpmdb# echo $?
>> > 133
>> > bofh:~/rpm-4.0.3/rpmdb#
>>=20
<snip>

>[pid  4249] close(4)                    =3D 0
>[pid  4249] close(1)                    =3D 0
>[pid  4249] exit(0)                     =3D ?
><... read resumed> "mut_fcntl.lo client.lo db_server"..., 200) =3D 200
>--- SIGCHLD (Child exited) ---
>rt_sigreturn(0)                         =3D 200
>rt_sigreturn(0)                         =3D 200
<snip>

I have exactly the same on my C200+, since 2.4.9-<who knows>, but it went
away when I didn't compile the kernel for PA8x00, but for the default =
value
of PA7100. That means it may be something in the kernel, or some gcc bug.
In my case, a 'make mrproper' in the kernel source directory triggered it.

I have posted it to this list, some weeks ago (under much the same =
subject).

Perhaps recompiling your kernel also fixes it?

Good luck,
Jurriaan

Re: Betr.: Re: [parisc-linux] Trace/breakpoint trap

[Richard Allen]

On Wed, Sep 26, 2001 at 08:05:23AM +0200, Jurriaan Kalkman wrote:

> I have exactly the same on my C200+, since 2.4.9-<who knows>, but it went
> away when I didn't compile the kernel for PA8x00, but for the default value
> of PA7100. That means it may be something in the kernel, or some gcc bug.
> In my case, a 'make mrproper' in the kernel source directory triggered it.
> 
> I have posted it to this list, some weeks ago (under much the same subject).
> 
> Perhaps recompiling your kernel also fixes it?

LOL! :)  

bofh:~# cd /usr/src/linux 
bofh:/usr/src/linux# make menuconfig
Trace/breakpoint trap

Mmm :)    The .config I used contains:

CONFIG_PARISC=y
CONFIG_PA8X00=y
CONFIG_PA20=y
CONFIG_GSC=y
CONFIG_IOMMU_CCIO=y
CONFIG_GSC_LASI=y
CONFIG_GSC_WAX=y
CONFIG_PCI=y
CONFIG_GSC_DINO=y
CONFIG_PCI_LBA=y
CONFIG_WAX_EISA=y
CONFIG_SUPERIO=y
CONFIG_IOSAPIC=y
CONFIG_IOMMU_SBA=y
CONFIG_PCI_NAMES=y
CONFIG_CHASSIS_LCD_LED=y


Im going to try this.   I'll simply get rid of CONFIG_PA8X00 and CONFIG_PA20.

-- 
Rikki.         --  HP Technical Support, RHCE, RHCX, HP-UX Certified Admin.
               --  Solaris 7 Certified Systems and Network Administrator.
Bell Labs Unix --  Reach out and grep someone.
Those who do not understand Unix are condemned to reinvent it, poorly.

Re: Betr.: Re: [parisc-linux] Trace/breakpoint trap

[Richard Allen]

On Wed, Sep 26, 2001 at 08:05:23AM +0200, Jurriaan Kalkman wrote:

> Perhaps recompiling your kernel also fixes it?

Damn...    I edited .config by hand, but Im still in a damn mess.

bofh:/usr/src/linux# make clean
Trace/breakpoint trap
bofh:/usr/src/linux# make oldconfig
Trace/breakpoint trap
bofh:/usr/src/linux# make dep
Trace/breakpoint trap


bofh:/usr/src/linux# cat /etc/palo.conf
# obsolete with palo-0.94 # --bootloader=/boot/iplboot
--commandline=2/vmlinux-2.4.9 root=/dev/sda4 HOME=/
--recoverykernel=/boot/vmlinux-2.4.0
--init-partitioned=/dev/sda

bofh:/usr/src/linux# ls -l /boot
total 7083
-rw-r--r--    1 root     root       593072 Sep 21 15:04 System.map-2.4.0
-rw-r--r--    1 root     disk       561861 Sep 21 21:12 System.map-2.4.9
-rw-r--r--    1 root     root         3949 Sep 21 15:04 config-2.4.0
drwxr-xr-x    2 root     root        12288 Sep 21 15:02 lost+found
-rw-r--r--    1 root     root      2853588 Sep 21 15:04 vmlinux-2.4.0
-rwxr-xr-x    1 root     disk      3191078 Sep 21 21:12 vmlinux-2.4.9


I still have the old kernel in there. How do I get palo to boot it ?


-- 
Rikki.         --  HP Technical Support, RHCE, RHCX, HP-UX Certified Admin.
               --  Solaris 7 Certified Systems and Network Administrator.
Bell Labs Unix --  Reach out and grep someone.
Those who do not understand Unix are condemned to reinvent it, poorly.

Re: Betr.: Re: [parisc-linux] Trace/breakpoint trap

[Jurriaan Kalkman]

>bofh:/usr/src/linux# ls -l /boot
>total 7083
>-rw-r--r--    1 root     root       593072 Sep 21 15:04 System.map-2.4.0
>-rw-r--r--    1 root     disk       561861 Sep 21 21:12 System.map-2.4.9
>-rw-r--r--    1 root     root         3949 Sep 21 15:04 config-2.4.0
>drwxr-xr-x    2 root     root        12288 Sep 21 15:02 lost+found
>-rw-r--r--    1 root     root      2853588 Sep 21 15:04 vmlinux-2.4.0
>-rwxr-xr-x    1 root     disk      3191078 Sep 21 21:12 vmlinux-2.4.9
>
>
>I still have the old kernel in there. How do I get palo to boot it ?
>
The easiest way to do it once is to interrupt the booting right at the =
start,
interrupting the automatic boot, then type

BOOT
and when asked if you want to interact with the IPL, answer Y.

Then edit the parameter where your kernel-name is. I have to use ^H to =
delete characters.

Good luck,
Jurriaan