All of lore.kernel.org
 help / color / mirror / Atom feed
From: Martin Schlemmer <azarah@nosferatu.za.org>
To: kde@myrealbox.com
Cc: Linux Kernel Mailing Lists <linux-kernel@vger.kernel.org>,
	Andrew Morton <akpm@osdl.org>
Subject: Re: PPP ooopses on 2.6.0-mm1
Date: Wed, 24 Dec 2003 23:50:58 +0200	[thread overview]
Message-ID: <1072302658.6600.10.camel@nosferatu.lan> (raw)
In-Reply-To: <200312241121.56934.kde@myrealbox.com>

[-- Attachment #1: Type: text/plain, Size: 3736 bytes --]

On Wed, 2003-12-24 at 11:21, ismail 'cartman' dönmez wrote:
> Hi all,
> 
> Here is what I get from syslog :
> 
> 
> Dec 24 11:09:51 southpark kernel: Unable to handle kernel NULL pointer dereference at virtual address 00000065
> Dec 24 11:09:51 southpark kernel: Unable to handle kernel NULL pointer dereference at virtual address 00000065
> Dec 24 11:09:51 southpark kernel:  printing eip:
> Dec 24 11:09:51 southpark kernel: e500dfcb
> Dec 24 11:09:51 southpark kernel: *pde = 00000000
> Dec 24 11:09:51 southpark kernel: *pde = 00000000
> Dec 24 11:09:51 southpark kernel: Oops: 0000 [#1]
> Dec 24 11:09:51 southpark kernel: PREEMPT
> Dec 24 11:09:51 southpark kernel: CPU:    0
> Dec 24 11:09:51 southpark kernel: EIP:    0060:[_end+617343539/1070258792]    Not tainted VLI
> Dec 24 11:09:51 southpark kernel: EFLAGS: 00010002
> Dec 24 11:09:51 southpark kernel: EIP is at process_input_packet+0x6b/0x230 [ppp_async]
> Dec 24 11:09:51 southpark kernel: eax: d5156c00   ebx: 0000007e   ecx: dae99310   edx: 00000000
> Dec 24 11:09:51 southpark kernel: esi: 00000001   edi: dae99710   ebp: d5156c00   esp: e3f8dee8
> Dec 24 11:09:51 southpark kernel: ds: 007b   es: 007b   ss: 0068
> Dec 24 11:09:51 southpark kernel: Process events/0 (pid: 3, threadinfo=e3f8c000 task=c15cecc0)
> Dec 24 11:09:51 southpark kernel: Stack: c02a151c c15cecc0 e3fedc28 dae990bc e3f8df70 0000007e 00000001 dae99710
> Dec 24 11:09:51 southpark kernel:        00000002 e500e34c d5156c00 0000f18b c029fa60 e3f8c000 00000286 d5156c00
> Dec 24 11:09:51 southpark kernel:        dae99000 e500d522 d5156c00 dae99310 dae99710 00000008 dae99000 00000008
> Dec 24 11:09:51 southpark kernel: Call Trace:
> Dec 24 11:09:51 southpark kernel:  [_end+617344436/1070258792] ppp_async_input+0x1bc/0x340 [ppp_async]
> Dec 24 11:09:51 southpark kernel:  [_end+617340810/1070258792] ppp_asynctty_receive+0x52/0xd0 [ppp_async]
> Dec 24 11:09:51 southpark kernel:  [flush_to_ldisc+156/272] flush_to_ldisc+0x9c/0x110
> Dec 24 11:09:51 southpark kernel:  [worker_thread+477/720] worker_thread+0x1dd/0x2d0
> Dec 24 11:09:51 southpark kernel:  [flush_to_ldisc+0/272] flush_to_ldisc+0x0/0x110
> Dec 24 11:09:51 southpark kernel:  [default_wake_function+0/32] default_wake_function+0x0/0x20
> Dec 24 11:09:51 southpark kernel:  [ret_from_fork+6/20] ret_from_fork+0x6/0x14
> Dec 24 11:09:51 southpark kernel:  [default_wake_function+0/32] default_wake_function+0x0/0x20
> Dec 24 11:09:51 southpark kernel:  [worker_thread+0/720] worker_thread+0x0/0x2d0
> Dec 24 11:09:51 southpark kernel:  [kernel_thread_helper+5/16] kernel_thread_helper+0x5/0x10
> Dec 24 11:09:51 southpark kernel:
> Dec 24 11:09:51 southpark kernel: Code: 89 d0 c1 e8 08 32 13 43 0f b6 d2 0f b7 94 12 40 f3 00 e5 31 c2 49 75 e8 81 fa b8 f0 00 00 74 4e c7 45 08 04 00 00 00 85 f6 74 25 <8b> 4e 64 85 c9 74 1e 8b 56 68 85 d2 75 1f c7 46 64 00 00 00 00
> Dec 24 11:09:51 southpark kernel:  <6>note: events/0[3] exited with preempt_count 1
> 
> 
> This somehow freezes X too. Anyone seen similar problems?

Yep, its a patch I have here as:

  ppp_async-callable-from-hard-interrupt.patch

that is prob in -mm as well (Andrew? - sorry, did not check).  I
cant remember where I got it, but I have had it around until yesterday
when at parents and have to use ppp again (in hope of fixing some other
issue that is prob the binary-only drivers problem :/).  I am not sure
if it may be interaction between Greg's latest tty patches (which I
have in my 'tree' as well), or if it is just broken for some setups (usb
modem with binary only driver over here) - I may try to test this theory
tomorrow if somebody do not beat me to it.


Cheers,

-- 
Martin Schlemmer

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

  parent reply	other threads:[~2003-12-24 21:48 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-12-24  9:21 PPP ooopses on 2.6.0-mm1 ismail 'cartman' dönmez
2003-12-24 12:34 ` PPP ooopses on 2.6.0-mm1 (and 2.6.0, but VMware loaded here) Jose Luis Domingo Lopez
2003-12-24 13:25   ` ismail 'cartman' dönmez
2003-12-24 21:50 ` Martin Schlemmer [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-12-24 20:38 PPP ooopses on 2.6.0-mm1 Thomas Babut

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=1072302658.6600.10.camel@nosferatu.lan \
    --to=azarah@nosferatu.za.org \
    --cc=akpm@osdl.org \
    --cc=kde@myrealbox.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.