From: Richard Allen <ra@hp.is>
To: Jurriaan Kalkman <Jurriaan.Kalkman@zrt.nl>
Cc: parisc-linux@parisc-linux.org
Subject: Re: Betr.: Re: [parisc-linux] Trace/breakpoint trap
Date: Wed, 26 Sep 2001 10:52:55 +0000 [thread overview]
Message-ID: <20010926105255.A16693@hp.is> (raw)
In-Reply-To: <sbb18da2.041@ms-zrt1>; from Jurriaan.Kalkman@zrt.nl on Wed, Sep 26, 2001 at 08:05:23AM +0200
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.
next parent reply other threads:[~2001-09-26 10:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <sbb18da2.041@ms-zrt1>
2001-09-26 10:52 ` Richard Allen [this message]
2001-09-26 10:57 ` Betr.: Re: [parisc-linux] Trace/breakpoint trap Richard Allen
2001-09-27 6:05 Jurriaan Kalkman
-- strict thread matches above, loose matches on Subject: below --
2001-09-26 6:05 Jurriaan Kalkman
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20010926105255.A16693@hp.is \
--to=ra@hp.is \
--cc=Jurriaan.Kalkman@zrt.nl \
--cc=parisc-linux@parisc-linux.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox