public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Oleg Drokin <green@linuxhacker.ru>
To: linux-kernel@vger.kernel.org
Subject: 2.4.5-ac7 SMP crash (hotplug race?)
Date: Sun, 3 Jun 2001 21:23:31 +0400	[thread overview]
Message-ID: <20010603212331.A1619@linuxhacker.ru> (raw)

Hello!

   Today, while playing with sleep mode of USB device I have, I got
   kernel hang on my SMP box (2xP3-667, 386M RAM, Abit VP6).
   Scenario was like this: background mpg123 over esd to
   00:0b.0 Multimedia audio controller: Creative Labs SB Live! EMU10000 (rev 08)
   minicom over ttyS1 to device, USB netlink (usbnet.c) to device over USB.

   I told device to go to sleep, it reported (over serial console that I
   looked at with minicom), that it turned off internal devices
   (including USB client), reported it is going to sleep, and turned
   serial and itself off.
   Suddenly mp3 playing stopped and I got this (decoded) diagnostics
   from kernel:

ksymoops 2.4.0 on i686 2.4.5-ac7.  Options used
     -V (default)
     -k /proc/ksyms (default)
     -l /proc/modules (default)
     -o /lib/modules/2.4.5-ac7/ (default)
     -m /boot/System.map-2.4.5-ac7 (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.

wait_on_irq, CPU 1
irq: 1 [1 0]
bh:  1 [0 1]
CPU 0: <unknown>
CPU 1: c167fe68 c01d805d ... (not recorded full stack)
Call Trace: [<c0108522>] [<c0170f97>] [<c0170f60>] [<c011d706>] [<c011a56c>] [<c011a423>] [<c011a2ab>] [<c0108935>] [<c0108525>] [<c01617e8>] [<c011a67d>] [<c0121c35>] [<c0121670>] [<c0105000>] [<c0105556>] [<c0121670>]
Warning (Oops_read): Code line not seen, dumping what data is available

Trace; c0108522 <__global_cli+e2/170>
Trace; c0170f97 <rs_timer+37/110>
Trace; c0170f60 <rs_timer+0/110>
Trace; c011d706 <timer_bh+256/2b0>
Trace; c011a56c <bh_action+4c/b0>
Trace; c011a423 <tasklet_hi_action+53/90>
Trace; c011a2ab <do_softirq+6b/a0>
Trace; c0108935 <do_IRQ+e5/f0>
Trace; c0108525 <__global_cli+e5/170>
Trace; c01617e8 <flush_to_ldisc+d8/120>
Trace; c011a67d <__run_task_queue+5d/70>
Trace; c0121c35 <context_thread+c5/200>
Trace; c0121670 <exec_usermodehelper+3c0/400>
Trace; c0105000 <prepare_namespace+0/10>
Trace; c0105556 <kernel_thread+26/30>
Trace; c0121670 <exec_usermodehelper+3c0/400>

2 warnings issued.  Results may not be reliable.

Bye,
    Oleg

             reply	other threads:[~2001-06-03 17:24 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-06-03 17:23 Oleg Drokin [this message]
     [not found] <mailman.991678980.18162.linux-kernel2news@redhat.com>
2001-06-04 20:41 ` 2.4.5-ac7 SMP crash (hotplug race?) Pete Zaitcev
2001-06-05  6:27   ` Oleg Drokin

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=20010603212331.A1619@linuxhacker.ru \
    --to=green@linuxhacker.ru \
    --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