From: Alexey Dobriyan <adobriyan@mail.ru>
To: Dmitry Torokhov <dtor_core@ameritech.net>
Cc: linux-kernel@vger.kernel.org, Vojtech Pavlik <vojtech@suse.cz>
Subject: Re: 2.6.12-rc1-bk2+PREEMPT_BKL: Oops at serio_interrupt
Date: Wed, 30 Mar 2005 13:14:39 +0400 [thread overview]
Message-ID: <200503301314.39575.adobriyan@mail.ru> (raw)
In-Reply-To: <200503300130.12736.dtor_core@ameritech.net>
On Wednesday 30 March 2005 10:30, Dmitry Torokhov wrote:
> On Tuesday 29 March 2005 14:49, Alexey Dobriyan wrote:
> > According to vmlinux, c0202947 is at:
> >
> > c020293e <serport_ldisc_write_wakeup>:
>
> Could you please try this one instead? Thanks!
Still dies in serport_ldisc_write_wakeup (doesn't matter how to trigger)
via:
Unable to handle kernel NULL pointer dereference at virtual address 00000068
EIP: c020294f
tty_wakeup
uart_close
wait_for_completion
release_dev
If you want me to be more specific, wait until I figure out how to print
only parts of oops (to fit them on console).
============================================================================
c0202930 <serport_ldisc_write_wakeup>:
c0202930: push %esi
c0202931: push %ebx
c0202932: mov 0x978(%eax),%ebx
c0202938: pushf
c0202939: pop %esi
c020293a: cli
c020293b: mov $0x1,%eax
c0202940: call c010ecaf <add_preempt_count>
c0202945: mov 0x14(%ebx),%eax
c0202948: test $0x4,%al
c020294a: jne c0202956 <serport_ldisc_write_wakeup+0x26>
c020294c: mov 0xc(%ebx),%eax
c020294f: ==>> mov 0x68(%eax),%edx <<==
c0202952: test %edx,%edx
c0202954: jne c0202973 <serport_ldisc_write_wakeup+0x43>
c0202956: push %esi
c0202957: popf
c0202958: mov $0x1,%eax
c020295d: call c010ece1 <sub_preempt_count>
c0202962: mov $0xfffff000,%eax
c0202967: and %esp,%eax
c0202969: mov 0x8(%eax),%eax
c020296c: test $0x8,%al
c020296e: jne c0202984 <serport_ldisc_write_wakeup+0x54>
c0202970: pop %ebx
c0202971: pop %esi
c0202972: ret
c0202973: mov 0x10(%edx),%edx
c0202976: test %edx,%edx
c0202978: je c0202956 <serport_ldisc_write_wakeup+0x26>
c020297a: lea 0x0(%esi),%esi
c0202980: call *%edx
c0202982: jmp c0202956 <serport_ldisc_write_wakeup+0x26>
c0202984: pop %ebx
c0202985: pop %esi
c0202986: jmp c029ad16 <preempt_schedule>
next prev parent reply other threads:[~2005-03-30 9:14 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-28 17:26 Alexey Dobriyan
2005-03-29 6:27 ` Dmitry Torokhov
2005-03-29 17:28 ` Alexey Dobriyan
2005-03-29 19:02 ` Dmitry Torokhov
2005-03-29 19:49 ` Alexey Dobriyan
2005-03-29 20:20 ` Dmitry Torokhov
2005-03-30 6:30 ` Dmitry Torokhov
2005-03-30 9:14 ` Alexey Dobriyan [this message]
2005-03-30 18:35 ` Dmitry Torokhov
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=200503301314.39575.adobriyan@mail.ru \
--to=adobriyan@mail.ru \
--cc=dtor_core@ameritech.net \
--cc=linux-kernel@vger.kernel.org \
--cc=vojtech@suse.cz \
/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®