From: vda <vda@port.imtp.ilyichevsk.odessa.ua>
To: Robert Love <rml@tech9.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] fully preemptible kernel
Date: Mon, 10 Dec 2001 14:08:03 -0200 [thread overview]
Message-ID: <01121014080300.09281@manta> (raw)
In-Reply-To: <1007930466.11789.2.camel@phantasy> <1007967834.878.30.camel@phantasy> <01121010295102.01013@manta>
In-Reply-To: <01121010295102.01013@manta>
Hi Robert,
I just installed 2.4.17pre7+preempt and it still shows the bug.
No oops yet (oops doesn't show up frequently).
2.4.17pre7 without preempt is being compiled right now.
> > > I reported a problem with preemptible 2.4.13 and Samba server (oops,
> > > problems with creation of files from win clients).
> > > Is this issue addressed?
> >
> > No, because I could not reproduce it. Could you see if it occurs on the
> > current kernel with the current patch? If so, send me the relevant
> > information.
...
...
> I have ksymoops compiled from sources and it does not work right
> ("Error (Oops_bfd_perror): set_section_contents Section has no contents").
> Can you enlighten me why I'm getting ths message?
> Or just send me working ksymoops binary, we can sort out this later.
In preparation for oops I need ksymoops binary. Mine is not ok:
> Unable to handle kernel paging request at virtual address 4008e6ed
> *pde = 01100067
> Oops: 0003
> CPU: 0
> EIP: 0010:[<c010655b>]
> Using defaults from ksymoops -t elf32-i386 -a i386
> EFLAGS: 00010246
> eax: 00000000 ebx: 4008e76d ecx: 4008e6cd edx: 0000e865
> esi: 00000000 edi: 00000128 ebp: 4008e6c9 esp: c1c5bf74
> ds: 0018 es: 0018 ss: 0018
> Process smbd (pid: 213, stackpage=c1c5b000)
> Stack: 5650faf0 c1c5a000 c029afd0 00000128 c01068d0 4008e6cd 4008e76d
> c1c5bf94 c02a23b2 55c3c85e ec83e589 4000bcd9 40015f67 4000bcd9 40015f67
> c1c5a000 00000000 00000000 bfffea74 c0107603 00000000 bfffe6a3 00000001
> 00000000 Call Trace: [<c01068d0>] [<c0107603>]
> Code: 89 51 20 31 c0 66 8b 53 0c 81 e2 ff ff 00 00 09 c6 89 51 1c
> Error (Oops_bfd_perror): set_section_contents Section has no contents
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Dunno is it a result of miscompiled ksymoops or what...
--
vda
next prev parent reply other threads:[~2001-12-10 12:10 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-09 20:41 [PATCH] fully preemptible kernel Robert Love
2001-12-10 10:54 ` vda
2001-12-10 7:03 ` Robert Love
2001-12-10 12:29 ` vda
2001-12-10 16:08 ` vda [this message]
2001-12-10 17:25 ` vda
2001-12-10 13:55 ` Wilson
2001-12-26 20:02 ` Steve Bergman
2001-12-26 20:13 ` Robert Love
2001-12-31 13:29 ` Heinz Diehl
2001-12-31 16:14 ` ncw
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=01121014080300.09281@manta \
--to=vda@port.imtp.ilyichevsk.odessa.ua \
--cc=linux-kernel@vger.kernel.org \
--cc=rml@tech9.net \
/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