From: "Steve Kieu" <haiquy@yahoo.com>
To: kernel <linux-kernel@vger.kernel.org>
Cc: Zwane Mwaikambo <zwane@linux.realnet.co.sz>
Subject: Re: OOPS 2.4.19-pre7-ac4 (Was: strange things in kernel 2.4.19-pre7-ac4 + preempt patch)
Date: Tue, 14 May 2002 11:04:22 +1000 (EST) [thread overview]
Message-ID: <20020514010422.58937.qmail@web10402.mail.yahoo.com> (raw)
In-Reply-To: <Pine.LNX.4.44.0205131830080.353-100000@netfinity.realnet.co.sz>
[-- Attachment #1: Type: text/plain, Size: 1051 bytes --]
--- Zwane Mwaikambo <zwane@linux.realnet.co.sz>
wrote: > Could you try this patch, Bill came across it
in
> rmap testing.
>
> Regards,
> Zwane
>
> ---
> linux-2.4.19-pre-ac/drivers/char/drm/i810_dma.c.orig
> Mon May 13 18:27:40 2002
> +++ linux-2.4.19-pre-ac/drivers/char/drm/i810_dma.c
> Mon May 13 18:28:37 2002
> @@ -293,8 +293,8 @@
> {
> if (page) {
> struct page *p = virt_to_page(page);
> - put_page(p);
> UnlockPage(p);
> + put_page(p);
> free_page(page);
> }
> }
> ---
>
linux-2.4.19-pre-ac/drivers/char/drm-4.0/i810_dma.c.orig
> Mon May 13 18:37:37 2002
> +++
> linux-2.4.19-pre-ac/drivers/char/drm-4.0/i810_dma.c
> Mon May 13 18:38:03 2002
> @@ -291,9 +291,9 @@
> struct page * p = virt_to_page(page);
> if(page == 0UL)
> return;
> -
> +
> + UnlockPage(p);
> put_page(p);
> - UnlockPage(p);
> free_page(page);
> return;
> }
>
> --
It doesn't work, I attached the oop log here...
=====
Steve Kieu
http://briefcase.yahoo.com.au - Yahoo! Briefcase
- Save your important files online for easy access!
[-- Attachment #2: oop.log --]
[-- Type: application/octet-stream, Size: 2733 bytes --]
ksymoops 2.4.4 on i686 2.4.19-pre7-ac4. Options used
-V (default)
-k /proc/ksyms (default)
-l /proc/modules (default)
-o /lib/modules/2.4.19-pre7-ac4/ (default)
-m /boot/System.map (default)
Warning: You did not tell me where to find symbol information. I will
assume that the log matches the kernel and modules that are running
right now and I'll use the default options above for symbol resolution.
If the current kernel and/or modules do not match the log, you can get
more accurate output by telling me the kernel version and where to find
map, modules, ksyms etc. ksymoops -h explains the options.
cpu: 0, clocks: 668209, slice: 334104
kernel BUG at filemap.c:851!
invalid operand: 0000
CPU: 0
EIP: 0010:[<c012b497>] Not tainted
Using defaults from ksymoops -t elf32-i386 -a i386
EFLAGS: 00013246
eax: c100000c ebx: c0227640 ecx: 0000001c edx: 00000000
esi: c119ccdc edi: c02792c0 ebp: c66dfed8 esp: c66dfed0
ds: 0018 es: 0018 ss: 0018
Process X (pid: 100, stackpage=c66df000)
Stack: c549c000 c1112fbc c66dfeec c018e4a9 c1112fbc c7d127cc c7d13800 c66dff08
c018e511 c02792c0 c549c000 00000000 bffff968 c02792c0 c66dff68 c018e9e9
c02792c0 00000000 c02792c0 00000002 00000000 00000000 00000000 00000000
Call Trace: [<c018e4a9>] [<c018e511>] [<c018e9e9>] [<c018df04>] [<c0149edb>]
[<c0108c5b>]
Code: 0f 0b 53 03 48 5c 20 c0 8d 46 04 39 46 04 74 11 5b 89 f0 31
>>EIP; c012b497 <unlock_page+47/70> <=====
Trace; c018e4a9 <i810_free_page+29/50>
Trace; c018e511 <i810_dma_cleanup+41/b0>
Trace; c018e9e9 <i810_dma_init+b9/e0>
Trace; c018df04 <i810_ioctl+e4/100>
Trace; c0149edb <sys_ioctl+26b/2b0>
Trace; c0108c5b <system_call+33/38>
Code; c012b497 <unlock_page+47/70>
00000000 <_EIP>:
Code; c012b497 <unlock_page+47/70> <=====
0: 0f 0b ud2a <=====
Code; c012b499 <unlock_page+49/70>
2: 53 push %ebx
Code; c012b49a <unlock_page+4a/70>
3: 03 48 5c add 0x5c(%eax),%ecx
Code; c012b49d <unlock_page+4d/70>
6: 20 c0 and %al,%al
Code; c012b49f <unlock_page+4f/70>
8: 8d 46 04 lea 0x4(%esi),%eax
Code; c012b4a2 <unlock_page+52/70>
b: 39 46 04 cmp %eax,0x4(%esi)
Code; c012b4a5 <unlock_page+55/70>
e: 74 11 je 21 <_EIP+0x21> c012b4b8 <unlock_page+68/70>
Code; c012b4a7 <unlock_page+57/70>
10: 5b pop %ebx
Code; c012b4a8 <unlock_page+58/70>
11: 89 f0 mov %esi,%eax
Code; c012b4aa <unlock_page+5a/70>
13: 31 00 xor %eax,(%eax)
1 warning issued. Results may not be reliable.
next prev parent reply other threads:[~2002-05-14 1:04 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200205101413.g4AEDEX29793@Port.imtp.ilyichevsk.odessa.ua>
2002-05-10 23:58 ` Steve Kieu
2002-05-11 22:40 ` Denis Vlasenko
2002-05-11 22:35 ` Steve Kieu
2002-05-13 10:28 ` Steve Kieu
2002-05-13 19:14 ` Denis Vlasenko
2002-05-13 15:52 ` Zwane Mwaikambo
2002-05-13 16:39 ` Zwane Mwaikambo
2002-05-14 1:04 ` Steve Kieu [this message]
2002-05-14 1:16 ` William Lee Irwin III
2002-05-13 22:57 ` Steve Kieu
2002-05-11 0:45 ` Steve Kieu
2002-05-09 14:35 strange things in kernel 2.4.19-pre7-ac4 + preempt patch Bill Davidsen
2002-05-09 21:59 ` OOPS 2.4.19-pre7-ac4 (Was: strange things in kernel 2.4.19-pre7-ac4 + preempt patch) Steve Kieu
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=20020514010422.58937.qmail@web10402.mail.yahoo.com \
--to=haiquy@yahoo.com \
--cc=linux-kernel@vger.kernel.org \
--cc=zwane@linux.realnet.co.sz \
/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
all inboxes | Powered by JetHome®