From: Andreas Klauer <Andreas.Klauer@metamorpher.de>
To: linux-kernel@vger.kernel.org
Subject: Linux 3.2.0 Oops/Recursive fault on shutdown
Date: Mon, 9 Jan 2012 12:37:49 +0100 [thread overview]
Message-ID: <20120109113749.GA4147@EIS> (raw)
Hi,
after upgrading the kernel to 3.2 the system oopsed on shutdown.
Unfortunately there was nothing in the logs so all I have is
a photo of the screen. System is an Intel Desktop (E8400),
using cryptsetup / mdadm / LVM.
I posted it along with kernel config / system.map / lspci here:
http://www.metamorpher.de/kp32/
Function names mentioned in the trace:
(full info please see the screenshot)
? wq_worker_sleeping
? __schedule
? do_exit
? oops_end
? do_invalid_op
? md_write_start
? ata_scsi_simulate
? cpumask_next_and
? find_busiest_group
? invalid_op
? md_write_start
? blkcipher_walk_done
? make_request
? crypto_aes_decrypt_x86
? encrypt
? md_make_request
? crypt_convert
? generic_make_request
? kcryptd_crypt
? kcryptd_async_done
? process_one_work
? worker_thread
? manage_workers.clone.26
? manage_workers.clone.26
? kthread
? kernel_thread_helper
? kthread_worker_fn
? gs_change
? kthread_data
Haven't been able to reproduce the issue so far, but maybe the
screenshot tells someone something that needs fixing.
Regards
Andreas Klauer
reply other threads:[~2012-01-09 11:43 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20120109113749.GA4147@EIS \
--to=andreas.klauer@metamorpher.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.