* oops in 2.4.6/2.4.5 [not found] <20010716161031Z267445-720+2808@vger.kernel.org> @ 2001-07-16 16:28 ` Victoria W. 2001-07-16 16:45 ` send_sig_info help? samandbuffy 0 siblings, 1 reply; 3+ messages in thread From: Victoria W. @ 2001-07-16 16:28 UTC (permalink / raw) To: linux-kernel; +Cc: volker Hello all, a fax-machine with cyclades-8-card (isa) 256MB, 1GB ext2, 1GB swap, 40GB reiserfs hangs after a period of time (8-48h) with an oops. It seems to hang on a "sync" but the messages are not the same every time. (there was a dead "sync" process in "ps x") the same behaviour occurs in 2.4.5 and 2.4.6. I've tried to reproduce the crash by pushing the load up to >100 - but nothing happens. But within 48h the machine hung again. Do you have any hints or ideas what to do now ? best regards wicki here is one oops-example: Unable to handle kernel NULL pointer dereference at virtual address 00000000 printing eip: c0005bed *pde = 00000000 Oops: 0002 CPU: 0 EIP: 0010:[<c0005bed>] EFLAGS: 00010246 eax: 00000000 ebx: cf3f2690 ecx: c9d80260 edx: c9d80260 esi: cab5dfb8 edi: cab5c000 ebp: 00000000 esp: cab5dfa8 ds: 0018 es: 0018 ss: 0018 Process loop5 (pid: 270, stackpage=cab5d000) Stack: cab5c000 cecd5f28 cf3f258c c77c1500 00000001 cab5c000 cf3f269c cf3f269c c0105ca3 cf3f2690 c77c1500 d08288f6 00000f00 cecd5f28 cf3f258c ffff0303 00000078 c010563b c0105644 cf3f258c 00000078 cf229860 Call Trace: [<c0105ca3>] [<c010563b>] [<c0105644>] Code: 00 00 00 7c 67 13 08 32 00 00 00 21 cc 01 cc 61 cb 41 cb 61 and here an other one from the same machine: kernel: kernel BUG at page_alloc.c:75! kernel: invalid operand: 0000 kernel: CPU: 0 ^ permalink raw reply [flat|nested] 3+ messages in thread
* send_sig_info help? 2001-07-16 16:28 ` oops in 2.4.6/2.4.5 Victoria W. @ 2001-07-16 16:45 ` samandbuffy 2001-07-17 1:01 ` Keith Owens 0 siblings, 1 reply; 3+ messages in thread From: samandbuffy @ 2001-07-16 16:45 UTC (permalink / raw) To: Victoria W., linux-kernel; +Cc: volker Guys, This is my first attempt at writing at the kernel level. I'm working on a device driver, and usually in userspace, I use Kill() to send a signal to a PID I know of. At the kernel level, I don't know of any kill() equivalents (are there any?), except send_sig_info(). Send_sig_info(int, struct siginfo *, struct tasktstruct *) I know the int is the PID from "Understanding the Linux Kernel -Oreilly". The problem I'm experiencing is that I'm not sure how to find the pointer to taskstruct. From what I"ve read, the pointer to taskstruct is a pointer to the target process. How do I find the pointer to the taskstruct of that task I want to send a signal to, if I only know its PID? Thanks, any help would be greatly appreciated. Sam __________________________________________________ Do You Yahoo!? Get personalized email addresses from Yahoo! Mail http://personal.mail.yahoo.com/ ^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: send_sig_info help? 2001-07-16 16:45 ` send_sig_info help? samandbuffy @ 2001-07-17 1:01 ` Keith Owens 0 siblings, 0 replies; 3+ messages in thread From: Keith Owens @ 2001-07-17 1:01 UTC (permalink / raw) To: samandbuffy; +Cc: Victoria W., linux-kernel, volker On Mon, 16 Jul 2001 09:45:46 -0700 (PDT), <samandbuffy@yahoo.com> wrote: >The problem I'm experiencing is that I'm not sure how >to find the pointer to taskstruct. From what I"ve >read, the pointer to taskstruct is a pointer to the >target process. How do I find the pointer to the >taskstruct of that task I want to send a signal to, if >I only know its PID? See drivers/char/sysrq.c::send_sig_all(). ^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2001-07-17 1:03 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
[not found] <20010716161031Z267445-720+2808@vger.kernel.org>
2001-07-16 16:28 ` oops in 2.4.6/2.4.5 Victoria W.
2001-07-16 16:45 ` send_sig_info help? samandbuffy
2001-07-17 1:01 ` Keith Owens
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox