mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Alex Tomas <bzzz@bzzz.linuxhacker.ru>
To: "Martin J. Bligh" <mbligh@aracnet.com>
Cc: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [Bug 1430] New: SysFS oops when rmmod'ing uhci-hcd	after resuming from suspend
Date: Mon, 27 Oct 2003 19:59:11 +0300	[thread overview]
Message-ID: <20031027195911.1ee22642.bzzz@bzzz.linuxhacker.ru> (raw)
In-Reply-To: <605230000.1067269839@[10.10.2.4]>

there is very similar problem with
echo "scsi remove-single-divice ..." >/proc/scsi/scsi


On Mon, 27 Oct 2003 07:50:39 -0800
"Martin J. Bligh" <mbligh@aracnet.com> wrote:

> http://bugme.osdl.org/show_bug.cgi?id=1430
> 
>            Summary: SysFS oops when rmmod'ing uhci-hcd after resuming from
>                     suspend
>     Kernel Version: 2.6.0-test9
>             Status: NEW
>           Severity: normal
>              Owner: mochel@osdl.org
>          Submitter: felipe_alfaro@linuxmail.org
> 
> 
> Distribution: 
> ------------- 
> Fedora Core Test 3. 
> Nothing special with it, since the problems is reproducible by booting with 
> "init=/bin/bash" kernel command line parameter. 
>  
> Hardware Environment: 
> --------------------- 
> Packard Bell Chrom@ laptop: 
> Pentium III 700 Mhz 
> Intel 440BX chipset 
> Texas Instruments PCI4450 CardBus bridge 
> ATI RAGE Mobility M1 AGP video card with 8MB of DRAM 
> 3Com 3CCFE575CT 10/100 CardBus NIC 
> Microsoft Intellimouse Explorer USB mouse 
>  
> Please, see attached "lspci" file for more details. 
>  
> Software Environment: 
> --------------------- 
> Nothing special 
>  
> Problem Description: 
> -------------------- 
> After resuming my laptop from APM suspend, running "rmmod uhci-hcd" causes the 
> following oops: 
>  
> Unable to handle kernel NULL pointer dereference at virtual address 00000000 
>  printing eip: 
> c017fba6 
> *pde = 00000000 
> Oops: 0000 [#1] 
> CPU:    0 
> EIP:    0060:[<c017fba6>]    Not tainted 
> EFLAGS: 00010292 
> EIP is at sysfs_get_dentry+0x16/0x70 
> eax: 00000000   ebx: cf885acc   ecx: ffffffff   edx: 00000000 
> esi: cf8f8280   edi: 00000000   ebp: cf885c24   esp: cf54be38 
> ds: 007b   es: 007b   ss: 0068 
> Process rmmod (pid: 454, threadinfo=cf54a000 task=cf54d900) 
> Stack: c015df9d cf54be54 00000000 00000000 c017fbf5 cf810580 cf885acc cf885c00 
>        c017fc2a cf8f8280 00000000 cf885acc d0879ec0 c01c33f8 cf8f8280 00000000 
>        cf885acc cf885ccc c01c3575 cf885acc cf885b28 cf885acc cf885ccc c01c244d 
> Call Trace: 
>  [<c015df9d>] lookup_hash+0x1d/0x30 
>  [<c017fbf5>] sysfs_get_dentry+0x65/0x70 
>  [<c017fc2a>] sysfs_hash_and_remove+0x2a/0x7d 
>  [<c01c33f8>] device_release_driver+0x28/0x70 
>  [<c01c3575>] bus_remove_device+0x55/0xa0 
>  [<c01c244d>] device_del+0x5d/0xa0 
>  [<c01c24a3>] device_unregister+0x13/0x30 
>  [<d0863d28>] usb_disconnect+0xd8/0xf0 [usbcore] 
>  [<d086c119>] usb_hcd_pci_remove+0x89/0x180 [usbcore] 
>  [<c01a2acb>] pci_device_remove+0x3b/0x40 
>  [<c01c3436>] device_release_driver+0x66/0x70 
>  [<c01c346b>] driver_detach+0x2b/0x40 
>  [<c01c36ad>] bus_remove_driver+0x3d/0x80 
>  [<c01c3ab3>] driver_unregister+0x13/0x28 
>  [<c01a2ca6>] pci_unregister_driver+0x16/0x30 
>  [<d085506f>] uhci_hcd_cleanup+0xf/0x5e [uhci_hcd] 
>  [<c0130299>] sys_delete_module+0x139/0x1b0 
>  [<c0144000>] do_munmap+0x80/0x190 
>  [<c0109339>] sysenter_past_esp+0x52/0x71 
>  
> Code: f2 ae f7 d1 49 89 4c 24 0c 31 db 89 d7 49 83 f9 ff 74 24 8d 
>  
> Steps to reproduce: 
> ------------------- 
> This problem can be always reproduced by performing the following steps: 
>  
> 0. Make sure the Intellimouse USB mouse is plugged. 
> 1. Boot into 2.6.0-test9 with "init=/bin/bash" 
> 2. Run "apm -s" 
> 3. Let the system suspend, then resume it from suspension. 
> 4. On the command line, run "rmmod uhci-hcd" 
> 5. The previously described oops will be triggered. 
>  
> Additional information: 
> ----------------------- 
> Please, see the attached "config" file for information on the configuration 
> used to build the kernel.
> 
> 
> 
> 
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/

      reply	other threads:[~2003-10-27 16:55 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-10-27 15:50 Martin J. Bligh
2003-10-27 16:59 ` Alex Tomas [this message]

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=20031027195911.1ee22642.bzzz@bzzz.linuxhacker.ru \
    --to=bzzz@bzzz.linuxhacker.ru \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mbligh@aracnet.com \
    /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®