public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Christian Kujau <evil@g-house.de>
To: linux-kernel@vger.kernel.org
Subject: Re: parport_pc Oops with 2.6.0-test3
Date: Mon, 25 Aug 2003 06:53:12 +0200	[thread overview]
Message-ID: <3F499638.5040105@g-house.de> (raw)
In-Reply-To: <20030824030043.729a5786.akpm@osdl.org>

Andrew Morton wrote:
> Can you retest on 2.6.0-test4?

i have, but with no (?) changes:

prinz:~$ modprobe parport_pc
parport0: PC-style at 0x378 (0x778), irq 7, using FIFO 
[PCSPP,TRISTATE,COMPAT,ECP]
prinz:~$ rmmod parport_pc
Unable to handle kernel paging request at virtual address e1a4f164
  printing eip:
  e1a4757a
  *pde = 1fe2a067
  *pte = 00000000
  Oops: 0000 [#1]
  CPU:    0
  EIP:    0060:[<e1a4757a>]    Tainted: P
  EFLAGS: 00010282
  EIP is at cleanup_module+0xa/0x50 [parport_pc]
  eax: deab8980   ebx: e1a4b2c0   ecx: 00000000   edx: e1a4b2c0
  esi: 00000880   edi: 00000000   ebp: c0320318   esp: dae47f50
  ds: 007b   es: 007b   ss: 0068
  Process rmmod (pid: 618, threadinfo=dae46000 task=dcda4640)
  Stack: dae47f70 e1a4b2c0 00000880 c01346a8 e1a4b2c0 bffffce0 \
         0000003b 00000000
         70726170 5f74726f c0006370 dfd69940 db6be180 dfd60280 \
         40014000 40015000
         40015000 dfd60280 dfd69940 dfd69960 00000000 dae46000 \
         00148634 dfd69940
  Call Trace:
  [<c01346a8>] sys_delete_module+0x138/0x1b0
  [<c010929b>] syscall_call+0x7/0xb

Code: 8b 15 64 f1 a4 e1 89 c3 85 d2 74 29 85 db 74 15 8d b6 00 00
Segmentation fault
prinz:~$

(oh, yes, it's tainted again. the nvidia.ko module. but it oopsed with a 
non-tainted 2.6.0-test3 too: 
http://christian.go4more.de/parport/parport_oops.txt )

thank you for your time,
Christian.
-- 
BOFH excuse #161:

monitor VLF leakage


  parent reply	other threads:[~2003-08-25  2:57 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-08-18 11:20 parport_pc Oops with 2.6.0-test3 Christian Kujau
2003-08-19 22:01 ` Christian Kujau
2003-08-24 10:00 ` Andrew Morton
2003-08-24 14:34   ` Christian
2003-08-25  4:53   ` Christian Kujau [this message]
2003-08-25  3:37     ` Andrew Morton
  -- strict thread matches above, loose matches on Subject: below --
2003-08-16  8:38 increased verbosity in dmesg Gene Heskett
2003-08-16 10:48 ` Martin Schlemmer
2003-08-16 15:07   ` Gene Heskett
2003-08-26  0:17     ` parport_pc Oops with 2.6.0-test3 Christian Kujau
2003-08-26  8:38       ` Andrew Morton
2003-08-26 23:03         ` Christian
2003-08-28  2:41         ` Christian Kujau

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=3F499638.5040105@g-house.de \
    --to=evil@g-house.de \
    --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