From: Jan-Benedict Glaw <jbglaw@lug-owl.de>
To: parisc-linux@lists.parisc-linux.org
Subject: [parisc-linux] Oops on 2.4.20-pa33
Date: Mon, 5 May 2003 22:02:51 +0200 [thread overview]
Message-ID: <20030505200251.GS27494@lug-owl.de> (raw)
[-- Attachment #1: Type: text/plain, Size: 1612 bytes --]
Hi!
I've tried to compile/boot current 2.4.x CVS, but it Oopsed. I noted
down what looked really important (this is, IAOQ, r02 and kernel
addresses from stack). This is what I resolved out of System.map:
IAOQ: 10224658 __canonicalize_funcptr_for_compare
r02: 101229d4 do_sigaction
Kernel addresses on stack:
1013a278 dentry_open
10131a38 __kmem_cache_alloc
101229d4 do_sigaction
10102a9c handle_interruption
10122dc8 sys_rt_sigaction
10107f90 syscall_exit
10107084 intr_check_sig
10106cf4 _switch_to_ret
1013be10 chrdev_open
1013a278 dentry_open
1014aba8 locate_fd
1011b530 it_real_fn
Seems I cannot really find it:)
b132l-1:~# gcc -v
Reading specs from /usr/lib/gcc-lib/hppa-linux/3.2.3/specs
Configured with: ../src/configure -v --enable-languages=c,c++,f77,objc,ada --prefix=/usr --mandir=/usr/share/man --infodir=/usr/share/info --with-gxx-include-dir=/usr/include/c++/3.2 --enable-shared --with-system-zlib --enable-nls --without-included-gettext --enable-__cxa_atexit --enable-clocale=gnu --enable-objc-gc hppa-linux
Thread model: posix
gcc version 3.2.3
MfG, JBG
--
Jan-Benedict Glaw jbglaw@lug-owl.de . +49-172-7608481
"Eine Freie Meinung in einem Freien Kopf | Gegen Zensur | Gegen Krieg
fuer einen Freien Staat voll Freier Bürger" | im Internet! | im Irak!
ret = do_actions((curr | FREE_SPEECH) & ~(IRAQ_WAR_2 | DRM | TCPA));
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next reply other threads:[~2003-05-05 20:02 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-05 20:02 Jan-Benedict Glaw [this message]
2003-05-05 20:05 ` [parisc-linux] Oops on 2.4.20-pa33 Randolph Chung
2003-05-05 21:05 ` [parisc-linux] [PATCH-2.4] DIVA serial build error (was: Oops on 2.4.20-pa33) Jan-Benedict Glaw
2003-05-06 15:20 ` Jan-Benedict Glaw
2003-05-07 16:27 ` Paul Bame
2003-05-06 6:04 ` [parisc-linux] Oops on 2.4.20-pa33 Joel Soete
2003-05-06 14:04 ` Randolph Chung
2003-05-06 15:04 ` Joel Soete
2003-05-06 15:08 ` Randolph Chung
2003-05-06 16:34 ` Joel Soete
2003-05-06 16:42 ` John David Anglin
2003-05-06 17:56 ` Joel Soete
2003-05-07 15:48 ` Jan-Benedict Glaw
2003-05-07 16:09 ` Joel Soete
2003-05-07 17:17 ` Randolph Chung
2003-05-07 17:51 ` Jan-Benedict Glaw
2003-05-09 2:37 ` Andrew Shugg
2003-05-09 22:04 ` Jan-Benedict Glaw
2003-05-08 5:52 ` Joel Soete
2003-05-08 6:12 ` [parisc-linux] [PATCH-linux-2.5] sa_handler compare with cast Jan-Benedict Glaw
2003-05-10 20:31 ` [parisc-linux] Yet another '__canonicalize_funcptr_for_compare' pb Joel Soete
2003-05-10 20:25 ` Jan-Benedict Glaw
2003-05-10 21:08 ` Grant Grundler
2003-05-10 21:32 ` John David Anglin
2003-05-10 21:33 ` Joel Soete
2003-05-10 21:38 ` [parisc-linux] Yet another '__canonicalize_funcptr_for_compare' John David Anglin
2003-05-10 21:21 ` [parisc-linux] Re: Yet another '__canonicalize_funcptr_for_compare' pb John David Anglin
2003-05-05 20:10 ` [parisc-linux] Oops on 2.4.20-pa33 John David Anglin
-- strict thread matches above, loose matches on Subject: below --
2003-05-06 17:33 Joel Soete
2003-05-06 17:40 ` Randolph Chung
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=20030505200251.GS27494@lug-owl.de \
--to=jbglaw@lug-owl.de \
--cc=parisc-linux@lists.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