From: bugzilla-daemon@bugzilla.kernel.org
To: linux-scsi@vger.kernel.org
Subject: [Bug 71231] System unresponsable after a lot of LUNs have been added to the system
Date: Fri, 11 Apr 2014 13:49:51 +0000 [thread overview]
Message-ID: <bug-71231-11613-fz1b2vUs9G@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-71231-11613@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=71231
--- Comment #15 from Alex <alexandernaumann@gmx.de> ---
After disabling ACPI Processor and cpuidle, I get these four different stack
traces (system is working, but not rebooting anymore for example) several
times:
Call Trace:
[<ffffffff8175bafd>] __mutex_lock_slowpath+0x5d/0x1d0
[<ffffffff8175bc48>] ? __mutex_lock_slowpath+0x1a8/0x1d0
[<ffffffff8175b57d>] mutex_lock+0x1d/0x40
[<ffffffff81152645>] sysfs_dentry_revalidate+0x35/0x100
[<ffffffff810fa729>] lookup_fast+0x299/0x2e0
[<ffffffff810fab06>] ? __inode_permission+0x46/0x70
[<ffffffff810fad1a>] link_path_walk+0x19a/0x800
[<ffffffff81027fd9>] ? physflat_send_IPI_mask+0x9/0x10
[<ffffffff810fe604>] path_openat.isra.68+0x94/0x450
[<ffffffff8175bc48>] ? __mutex_lock_slowpath+0x1a8/0x1d0
[<ffffffff810febec>] do_filp_open+0x3c/0x90
[<ffffffff8110a332>] ? __alloc_fd+0x42/0x100
[<ffffffff810eefef>] do_sys_open+0xef/0x1d0
[<ffffffff81002441>] ? do_notify_resume+0x51/0x80
[<ffffffff81135ae6>] compat_SyS_open+0x16/0x20
[<ffffffff81760318>] sysenter_dispatch+0x7/0x25
Call Trace:
[<ffffffff8100a7c9>] default_idle+0x9/0x10
[<ffffffff8100af4a>] arch_cpu_idle+0xa/0x10
[<ffffffff81071eb1>] cpu_startup_entry+0x91/0x180
[<ffffffff81cd9ef7>] start_secondary+0x1a0/0x1a4
Call Trace:
[<ffffffff81112242>] ? simple_read_from_buffer+0x42/0xa0
[<ffffffff81151b73>] sysfs_read_file+0xe3/0x190
[<ffffffff810f02e4>] vfs_read+0xa4/0x180
[<ffffffff810f055d>] SyS_read+0x4d/0x90
[<ffffffff81760318>] sysenter_dispatch+0x7/0x25
Call Trace:
[<ffffffff8175bafd>] __mutex_lock_slowpath+0x5d/0x1d0
[<ffffffff8175b57d>] mutex_lock+0x1d/0x40
[<ffffffff811511db>] sysfs_getattr+0x2b/0x60
[<ffffffff810f45e4>] vfs_getattr+0x24/0x40
[<ffffffff810f4b88>] vfs_fstat+0x38/0x70
[<ffffffff8110a332>] ? __alloc_fd+0x42/0x100
[<ffffffff81036385>] sys32_fstat64+0x15/0x30
[<ffffffff810ef064>] ? do_sys_open+0x164/0x1d0
[<ffffffff81760318>] sysenter_dispatch+0x7/0x25
I have booted this Multiprocessor server with 40 FC-LUNs connected
(multipathing --> 80).
--
You are receiving this mail because:
You are the assignee for the bug.
next prev parent reply other threads:[~2014-04-11 13:49 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-27 17:45 [Bug 71231] New: System unresponsable after a lot of LUNs have been added to the system bugzilla-daemon
2014-02-27 17:46 ` [Bug 71231] " bugzilla-daemon
2014-02-27 17:47 ` bugzilla-daemon
2014-02-28 12:21 ` bugzilla-daemon
2014-02-28 13:09 ` bugzilla-daemon
2014-02-28 16:40 ` bugzilla-daemon
2014-02-28 19:37 ` bugzilla-daemon
2014-03-05 15:56 ` bugzilla-daemon
2014-03-06 9:40 ` bugzilla-daemon
2014-03-19 10:01 ` bugzilla-daemon
2014-03-31 9:57 ` bugzilla-daemon
2014-04-09 10:22 ` bugzilla-daemon
2014-04-09 10:25 ` bugzilla-daemon
2014-04-09 17:50 ` bugzilla-daemon
2014-04-11 8:20 ` bugzilla-daemon
2014-04-11 13:08 ` bugzilla-daemon
2014-04-11 13:15 ` bugzilla-daemon
2014-04-11 13:49 ` bugzilla-daemon [this message]
2021-06-28 7:36 ` bugzilla-daemon
2021-06-28 7:39 ` bugzilla-daemon
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=bug-71231-11613-fz1b2vUs9G@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.kernel.org \
--cc=linux-scsi@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;
as well as URLs for NNTP newsgroup(s).