public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Sandino Araico Sánchez" <sandino@sandino.net>
To: Juan Quintela <quintela@mandrakesoft.com>
Cc: Greg KH <greg@kroah.com>, Richard Gooch <rgooch@ras.ucalgary.ca>,
	linux-kernel@vger.kernel.org
Subject: Re: 2.4.17,2.4.18 ide-scsi+usb-storage+devfs Oops
Date: Wed, 03 Apr 2002 18:52:59 -0600	[thread overview]
Message-ID: <3CABA3EB.E8ED7D04@sandino.net> (raw)
In-Reply-To: <3C7EA7CB.C36D0211@sandino.net> <20020302075847.GE20536@kroah.com> <3C84294C.AE1E8CE9@sandino.net> <200203060528.g265Sh502430@vindaloo.ras.ucalgary.ca> <20020306053355.GA13072@kroah.com> <200203060545.g265jwL02756@vindaloo.ras.ucalgary.ca> <20020306181956.GC16003@kroah.com> <3C868302.31C7BBC4@sandino.net> <m2ofhsij2z.fsf@trasno.mitica>

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

Juan Quintela wrote:

> >>>>> "sandino" == Sandino Araico Sánchez <sandino@sandino.net> writes:
>
> sandino> I had to copy the Oops trace by hand to a paper. Gpm is not working correctly
> sandino> on my machine. Is there another way to send the Oops trace to a file?
>
> dmesg > file
>

Sorry about being so late, but I have another ksymoops.

This time the Oops was reproduced as follows:

1. I ran this script
#!/bin/sh
killall -9 wmcdplay
rmmod sr_mod
rmmod ide-scsi
modprobe ide-cd
ls -la /dev/cdroms/cdrom0
/etc/rc.d/init.d/usbmgr start

2. I ran this script
#!/bin/sh
/etc/rc.d/init.d/usbmgr stop
killall -9 wmcdplay
rmmod ide-cd
modprobe ide-scsi
modprobe sr_mod
ls -la /dev/cdroms/cdrom0

lr-xr-xr-x    1 root     root           34 dic 31  1969 /dev/cdroms/cdrom0 ->
../scsi/host2/bus0/target0/lun0/cd

3. I mounted the cdrom
mount  /dev/scsi/host2/bus0/target0/lun0/cd /mnt/cdrom

4. I started the usbmgr

5. I inserted the zip drive in the usb port

6. I don't remember when the Oops happened, when I unmounted the CD or after unmounting
it when I ran eject.


This time I'm sure the ksymoops is correct because I did dmesg > file and after rebooting
ksymoops < file > file.ksymoops.

--
Sandino Araico Sánchez
>drop table internet;
OK, 135454265363565609860398636678346496 rows affected.
"oh fuck" --fluxrad



[-- Attachment #2: Oops-2002-04-03-cdrom.ksymoops --]
[-- Type: text/plain, Size: 3099 bytes --]

ksymoops 2.3.4 on i686 2.4.18.  Options used
     -V (default)
     -k /proc/ksyms (default)
     -l /proc/modules (default)
     -o /lib/modules/2.4.18/ (default)
     -m /usr/src/linux/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.

Warning (compare_maps): ksyms_base symbol acpi_fadt_R__ver_acpi_fadt not found in System.map.  Ignoring ksyms_base entry
Warning (compare_maps): ksyms_base symbol acpi_gbl_FADT_R__ver_acpi_gbl_FADT not found in System.map.  Ignoring ksyms_base entry
Unable to handle kernel paging request at virtual address 0120000c
c01575bb
*pde = 00000000
Oops: 0002
CPU:    0
EIP:    0010:[<c01575bb>]    Not tainted
Using defaults from ksymoops -t elf32-i386 -a i386
EFLAGS: 00010206
eax: 0120000c   ebx: d40dd8e0   ecx: c1846d60   edx: 00000000
esi: d0820a14   edi: d9e5bbe0   ebp: bfffe4ec   esp: da36ff3c
ds: 0018   es: 0018   ss: 0018
Process rmmod (pid: 3239, stackpage=da36f000)
Stack: d0820a14 e08e4362 d40dd8e0 d0820a00 00000000 e08f13be d0820a14 00000b00 
       00000000 d9e5bbe0 df0ff720 e08f2a80 c01c544a d9e5bbe0 e08f0000 fffffff0 
       e08f0000 c01c555e e08f2a80 e08f1424 00000004 e08f2a80 c011980f e08f0000 
Call Trace: [<e08e4362>] [<e08f13be>] [<e08f2a80>] [<c01c544a>] [<c01c555e>] 
   [<e08f2a80>] [<e08f1424>] [<e08f2a80>] [<c011980f>] [<c0118b12>] [<c0106e23>] 
Code: f0 81 28 00 00 00 01 0f 85 72 22 00 00 53 8b 43 20 50 e8 46 

>>EIP; c01575bb <devfs_unregister+13/38>   <=====
Trace; e08e4362 <[cdrom]unregister_cdrom+8a/bc>
Trace; e08f13be <[ide-cd]cdrom_analyze_sense_data+2c2/31c>
Trace; e08f2a80 <[ide-cd]cdrom_lockdoor+1c/e0>
Trace; c01c544a <scsi_unregister_device+52/d4>
Trace; c01c555e <scsi_unregister_module+36/3c>
Trace; e08f2a80 <[ide-cd]cdrom_lockdoor+1c/e0>
Trace; e08f1424 <[ide-cd]cdrom_queue_request_sense+c/90>
Trace; e08f2a80 <[ide-cd]cdrom_lockdoor+1c/e0>
Trace; c011980f <free_module+17/b4>
Trace; c0118b12 <sys_delete_module+126/234>
Trace; c0106e23 <system_call+33/38>
Code;  c01575bb <devfs_unregister+13/38>
00000000 <_EIP>:
Code;  c01575bb <devfs_unregister+13/38>   <=====
   0:   f0 81 28 00 00 00 01      lock subl $0x1000000,(%eax)   <=====
Code;  c01575c2 <devfs_unregister+1a/38>
   7:   0f 85 72 22 00 00         jne    227f <_EIP+0x227f> c015983a <_text_lock_base+75/12f>
Code;  c01575c8 <devfs_unregister+20/38>
   d:   53                        push   %ebx
Code;  c01575c9 <devfs_unregister+21/38>
   e:   8b 43 20                  mov    0x20(%ebx),%eax
Code;  c01575cc <devfs_unregister+24/38>
  11:   50                        push   %eax
Code;  c01575cd <devfs_unregister+25/38>
  12:   e8 46 00 00 00            call   5d <_EIP+0x5d> c0157618 <devfs_do_symlink+38/17c>


3 warnings issued.  Results may not be reliable.

  reply	other threads:[~2002-04-04  0:54 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-02-28 21:57 2.4.17,2.4.18 ide-scsi+usb-storage+devfs Oops Sandino Araico Sánchez
2002-03-02  7:58 ` Greg KH
2002-03-05  2:11   ` Sandino Araico Sánchez
2002-03-06  5:28     ` Richard Gooch
2002-03-06  5:33       ` Greg KH
2002-03-06  5:45         ` Richard Gooch
2002-03-06 18:19           ` Greg KH
2002-03-06 20:58             ` Sandino Araico Sánchez
2002-03-13 15:27               ` Juan Quintela
2002-04-04  0:52                 ` Sandino Araico Sánchez [this message]
2002-04-04 16:14                   ` Richard Gooch
2002-03-06 20:56       ` Sandino Araico Sánchez

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=3CABA3EB.E8ED7D04@sandino.net \
    --to=sandino@sandino.net \
    --cc=greg@kroah.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=quintela@mandrakesoft.com \
    --cc=rgooch@ras.ucalgary.ca \
    /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