From: Joel Soete <soete.joel@tiscali.be>
To: John David Anglin <dave@hiauly1.hia.nrc.ca>
Cc: carlos@systemhalted.org, parisc-linux@parisc-linux.org
Subject: Re: [parisc-linux] Latest palinux crash
Date: Fri, 22 Jul 2005 13:35:25 +0000 [thread overview]
Message-ID: <42E0F61D.5030001@tiscali.be> (raw)
In-Reply-To: <200507212243.j6LMhhtD010420@hiauly1.hia.nrc.ca>
John David Anglin wrote:
>>just a small note, iirc Bruno's patch also used -ggdb compile option which grow dramaticaly the kernel size.
>>But may be not not absolutely necessary?
>
>
> The option adds debug symbols but they all should be in no-load sections
> (i.e., the option shouldn't change the code and data sections at all).
cool ;-)
> If you are going to use gdb to debug the kernel,
I though that was the goal: grab a coredump to trace it back?
(but I could never experiment it because of it's so big size: iirc about 60Mb for the 2.4 and this time my dump (swap) area was too
small to host the coredump image, now it could be just large enough ;)
> I recommend building
> with -O1 instead of -O2.
>
mmm could it not be too much invasive?
I mean we are going to change completely the insn flow and btw the time diagram as I experiment:
some weeks ago, I was working on ccio-dma for 64bit kernel on a d380 on which I noticed a dramtic slow down of the boot (more then
an hour in place of 5 min for its 32bit twin).
I would so first check the reserved IO addresses by some printk but there are so much that I could never get a login prompt (even
after a long night)?
I so tried to get the only 100 first ones but the kernel still slow down at the same place.
So I so tried to grab the next 200 ones: by miracle it boot near normaly (just slow down by some printk?
(I so presume that there is some race case in this driver, the computed IO adresses wouldn't have to change because I asked to print
it?)
But I changed the time diagram and btw the kernel behaviour, though?
May be in a second stage, when we would have located the hang place with -O2?
Thanks,
Joel
PS: I will check that when I will be back from holidays in 15 days ;-)
_______________________________________________
parisc-linux mailing list
parisc-linux@lists.parisc-linux.org
http://lists.parisc-linux.org/mailman/listinfo/parisc-linux
next prev parent reply other threads:[~2005-07-22 13:35 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-20 12:22 [parisc-linux] Latest palinux crash Matthew Wilcox
2005-07-21 4:36 ` Carlos O'Donell
2005-07-21 11:34 ` Joel Soete
2005-07-21 12:47 ` Grant Grundler
2005-07-21 19:48 ` Joel Soete
2005-07-22 3:14 ` Grant Grundler
2005-07-21 12:30 ` Grant Grundler
2005-07-21 12:48 ` Michael S. Zick
2005-07-21 19:58 ` Joel Soete
2005-07-21 22:43 ` John David Anglin
2005-07-22 13:35 ` Joel Soete [this message]
2005-07-26 16:37 ` John David Anglin
2005-08-08 19:29 ` Joel Soete
2005-08-15 14:40 ` Joel Soete
2005-08-15 19:37 ` Grant Grundler
-- strict thread matches above, loose matches on Subject: below --
2005-08-16 9:30 Joel Soete
2005-07-25 15:04 Joel Soete
2005-06-25 15:09 [parisc-linux] latest " Matthew Wilcox
2005-06-27 17:29 ` Grant Grundler
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=42E0F61D.5030001@tiscali.be \
--to=soete.joel@tiscali.be \
--cc=carlos@systemhalted.org \
--cc=dave@hiauly1.hia.nrc.ca \
--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