public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "linux" <kernel@wired-net.gr>
To: "lkml" <linux-kernel@vger.kernel.org>
Subject: 2.4 kernel threads
Date: Thu, 19 May 2005 13:24:20 +0300	[thread overview]
Message-ID: <00e301c55c5c$eb83d7c0$0101010a@dioxide> (raw)
In-Reply-To: 20050519094517.GD5112@stusta.de

While attempting to unload the kernel module which has created a kernel
thread whoch runs perfectly i get this oops:
Unable to handle kernel paging request at virtual address d08f364c
 printing eip:
c011d6ff
*pde = 01af0067
*pte = 00000000
Oops: 0002
parport_pc lp parport autofs pcnet_cs 8390 crc32 ds yenta_socket pcmcia_core
floppy microcode ext3 jbd
CPU:    0
EIP:    0060:[<c011d6ff>]    Not tainted
EFLAGS: 00010092

EIP is at interruptible_sleep_on_timeout [kernel] 0x4f (2.4.21-4.EL)
eax: d08f3648   ebx: 00000286   ecx: 00000286   edx: d08f3648
esi: 000001c3   edi: 00000000   ebp: cc445fdc   esp: cc445fb4
ds: 0068   es: 0068   ss: 0068
Process enigma (pid: 1622, stackpage=cc445000)
Stack: 00000000 cc444000 d08f3648 d08f3648 00000000 00000003 00000656
00000656
       d08f3060 00000000 cc445fec d08f310d 00000004 cc444000 00000000
c010945d
       d08f363c 00000000 00000000
Call Trace:   [<c010945d>] kernel_thread_helper [kernel] 0x5 (0xcc445ff0)

Code: 89 50 04 89 02 c7 45 e4 00 00 00 00 c7 45 e0 00 00 00 00 53

Kernel panic: Fatal exception



The module is being unloaded with the following procedure:
lock_kernel();
flag=1; /* This flag does a break in the for(;;) loop of the thread after
the interruptible_sleep_on_timeout , after the break current=NULL;*/
mb();
kill_proc(pid_thread,SIGKILL,1);
unlock_kernel();
kill_proc(2,SIGCHLD,1); /* assuming that keventd is running with PID 2 */


  reply	other threads:[~2005-05-19 10:25 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-18 22:33 [RFC] [PATCH] OCFS2 Mark Fasheh
2005-05-18 23:35 ` Hans Reiser
2005-05-18 23:40 ` Adrian Bunk
2005-05-19  1:26   ` [Ocfs2-devel] " Manish Singh
2005-05-19  9:45     ` Adrian Bunk
2005-05-19 10:24       ` linux [this message]
2005-05-19 10:39         ` 2.4 kernel threads Arjan van de Ven
2005-05-19 16:19         ` Jesse Barnes
2005-05-19  2:30 ` [RFC] [PATCH] OCFS2 Kyle Moffett
2005-05-19  4:30   ` Mark Fasheh
2005-05-19  6:30 ` Daniel Phillips
2005-05-19  6:54   ` Mark Fasheh
2005-05-19 16:23     ` Daniel Phillips
2005-05-19 10:26   ` Jeff Garzik
2005-05-19 15:20     ` Lee Revell
2005-05-19 15:25       ` Jeff Garzik
2005-06-23 18:03 ` James Morris
2005-06-23 18:29   ` Mark Fasheh
2005-06-24  3:05   ` Paul Jackson
2005-06-24  3:29     ` Paul Jackson
2005-06-24  3:59     ` Mark Fasheh
2005-06-24  4:17       ` Paul Jackson
  -- strict thread matches above, loose matches on Subject: below --
2005-05-13 19:31 [PATCH 0/8] ppc64: Introduce Cell/BPA platform, v2 Arnd Bergmann
2005-05-18 12:40 ` [PATCH] libfs: add simple attribute files Arnd Bergmann
2005-05-18 20:24   ` Greg KH
2005-05-19  8:29     ` Arnd Bergmann
2005-05-19  9:18       ` 2.4 Kernel threads linux

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='00e301c55c5c$eb83d7c0$0101010a@dioxide' \
    --to=kernel@wired-net.gr \
    --cc=linux-kernel@vger.kernel.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