From: "Toralf Förster" <toralf.foerster@gmx.de>
To: linux-ext4@vger.kernel.org
Subject: Re: found a scenario for BUG at fs/ext4/super.c:804!
Date: Sat, 01 Jun 2013 15:48:26 +0200 [thread overview]
Message-ID: <51A9FBAA.2050906@gmx.de> (raw)
In-Reply-To: <51A7951C.5020300@gmx.de>
On 05/30/2013 08:06 PM, Toralf Förster wrote:
> On 05/30/2013 07:58 PM, Toralf Förster wrote:
>> 11. if that attempt fails stop the nfs service and run the umount command again - it segfaults now
>
> forgot to mention that after that just sysrq+b thelps me to reboot the
> machine, a "sync" does not come back nor can be interrupted with Ctrl-C,
> "reboot" don't work too - OTOH I'm able to write an email and save it as
> a draft.
>
sysrq+w gave :
2013-06-01T15:30:25.825+02:00 n22 kernel: SysRq : Show Blocked State
2013-06-01T15:30:25.825+02:00 n22 kernel: task PC stack pid father
2013-06-01T15:30:25.825+02:00 n22 kernel: kworker/0:1 D f08f7db0 0 29 2 0x00000000
2013-06-01T15:30:25.825+02:00 n22 kernel: Workqueue: events do_sync_work
2013-06-01T15:30:25.825+02:00 n22 kernel: f22b9e88 00000046 00000000 f08f7db0 00000008 e7a9080b 00000a16 f22b9e34
2013-06-01T15:30:25.825+02:00 n22 kernel: c16b1400 c104ec08 c16b1400 f37ba400 f21b8d50 ef1a39b0 00000296 b9b6e892
2013-06-01T15:30:25.825+02:00 n22 kernel: f22b9eb0 7fffffff f22b9eac f22b9e78 c14803f3 f21b8d50 00000001 f21b8d50
2013-06-01T15:30:25.825+02:00 n22 kernel: Call Trace:
2013-06-01T15:30:25.825+02:00 n22 kernel: [<c104ec08>] ? try_to_grab_pending+0x98/0x130
2013-06-01T15:30:25.825+02:00 n22 kernel: [<c14803f3>] ? wait_for_completion+0x83/0xc0
2013-06-01T15:30:25.826+02:00 n22 kernel: [<c1062410>] ? try_to_wake_up+0x220/0x220
2013-06-01T15:30:25.826+02:00 n22 kernel: [<c1480453>] schedule+0x23/0x60
2013-06-01T15:30:25.826+02:00 n22 kernel: [<c1480d15>] rwsem_down_read_failed+0x75/0xb2
2013-06-01T15:30:25.826+02:00 n22 kernel: [<c12da18f>] call_rwsem_down_read_failed+0x7/0xc
2013-06-01T15:30:25.826+02:00 n22 kernel: [<c147f24c>] ? down_read+0x1c/0x1f
2013-06-01T15:30:25.826+02:00 n22 kernel: [<c11208d2>] iterate_supers+0x62/0xc0
2013-06-01T15:30:25.826+02:00 n22 kernel: [<c1144fa0>] ? fdatawrite_one_bdev+0x20/0x20
2013-06-01T15:30:25.826+02:00 n22 kernel: [<c1144f22>] do_sync_work+0x22/0x80
2013-06-01T15:30:25.826+02:00 n22 kernel: [<c104e62e>] process_one_work+0x10e/0x390
2013-06-01T15:30:25.826+02:00 n22 kernel: [<c104f602>] worker_thread+0x102/0x320
2013-06-01T15:30:25.827+02:00 n22 kernel: [<c104f500>] ? manage_workers.isra.24+0x290/0x290
2013-06-01T15:30:25.827+02:00 n22 kernel: [<c1054b74>] kthread+0x94/0xa0
2013-06-01T15:30:25.827+02:00 n22 kernel: [<c1481a37>] ret_from_kernel_thread+0x1b/0x28
2013-06-01T15:30:25.827+02:00 n22 kernel: [<c1054ae0>] ? flush_kthread_worker+0x90/0x90
2013-06-01T15:30:25.827+02:00 n22 kernel: sync D f08f7db0 0 27190 27033 0x00000000
2013-06-01T15:30:25.827+02:00 n22 kernel: ef57ff38 00000082 00000000 f08f7db0 00000008 c7f4f883 00000a15 ef57fee4
2013-06-01T15:30:25.827+02:00 n22 kernel: c16b1400 c104ec08 c16b1400 f37c7400 eeed4fe0 ef1a39b0 00000296 2a2f912a
2013-06-01T15:30:25.827+02:00 n22 kernel: ef57ff60 7fffffff ef57ff5c ef57ff28 c14803f3 eeed4fe0 00000001 eeed4fe0
2013-06-01T15:30:25.827+02:00 n22 kernel: Call Trace:
2013-06-01T15:30:25.827+02:00 n22 kernel: [<c104ec08>] ? try_to_grab_pending+0x98/0x130
2013-06-01T15:30:25.827+02:00 n22 kernel: [<c14803f3>] ? wait_for_completion+0x83/0xc0
2013-06-01T15:30:25.827+02:00 n22 kernel: [<c1062410>] ? try_to_wake_up+0x220/0x220
2013-06-01T15:30:25.827+02:00 n22 kernel: [<c1480453>] schedule+0x23/0x60
2013-06-01T15:30:25.827+02:00 n22 kernel: [<c1480d15>] rwsem_down_read_failed+0x75/0xb2
2013-06-01T15:30:25.827+02:00 n22 kernel: [<c12da18f>] call_rwsem_down_read_failed+0x7/0xc
2013-06-01T15:30:25.827+02:00 n22 kernel: [<c147f24c>] ? down_read+0x1c/0x1f
2013-06-01T15:30:25.827+02:00 n22 kernel: [<c11208d2>] iterate_supers+0x62/0xc0
2013-06-01T15:30:25.827+02:00 n22 kernel: [<c1144fa0>] ? fdatawrite_one_bdev+0x20/0x20
2013-06-01T15:30:25.827+02:00 n22 kernel: [<c11450d1>] sys_sync+0x31/0x80
2013-06-01T15:30:25.827+02:00 n22 kernel: [<c1481ac1>] sysenter_do_call+0x12/0x22
2013-06-01T15:30:25.828+02:00 n22 kernel: kworker/0:0 D f08f7db0 0 27191 2 0x00000000
2013-06-01T15:30:25.828+02:00 n22 kernel: Workqueue: events do_sync_work
2013-06-01T15:30:25.828+02:00 n22 kernel: ea5e9e88 00000046 00000000 f08f7db0 00000008 42845398 00000a17 eeed0336
2013-06-01T15:30:25.828+02:00 n22 kernel: c16b1400 c104ec08 c16b1400 f37ba400 eeed4290 eeed0000 00000296 c1535c4d
2013-06-01T15:30:25.828+02:00 n22 kernel: ea5e9eb0 7fffffff ea5e9eac ea5e9e78 c14803f3 eeed4290 00000001 eeed4290
2013-06-01T15:30:25.828+02:00 n22 kernel: Call Trace:
2013-06-01T15:30:25.828+02:00 n22 kernel: [<c104ec08>] ? try_to_grab_pending+0x98/0x130
2013-06-01T15:30:25.828+02:00 n22 kernel: [<c14803f3>] ? wait_for_completion+0x83/0xc0
2013-06-01T15:30:25.828+02:00 n22 kernel: [<c1062410>] ? try_to_wake_up+0x220/0x220
2013-06-01T15:30:25.828+02:00 n22 kernel: [<c1480453>] schedule+0x23/0x60
2013-06-01T15:30:25.829+02:00 n22 kernel: [<c1480d15>] rwsem_down_read_failed+0x75/0xb2
2013-06-01T15:30:25.829+02:00 n22 kernel: [<c12da18f>] call_rwsem_down_read_failed+0x7/0xc
2013-06-01T15:30:25.829+02:00 n22 kernel: [<c147f24c>] ? down_read+0x1c/0x1f
2013-06-01T15:30:25.829+02:00 n22 kernel: [<c11208d2>] iterate_supers+0x62/0xc0
2013-06-01T15:30:25.829+02:00 n22 kernel: [<c1144fa0>] ? fdatawrite_one_bdev+0x20/0x20
2013-06-01T15:30:25.829+02:00 n22 kernel: [<c1144f22>] do_sync_work+0x22/0x80
2013-06-01T15:30:25.829+02:00 n22 kernel: [<c104e62e>] process_one_work+0x10e/0x390
2013-06-01T15:30:25.829+02:00 n22 kernel: [<c104f602>] worker_thread+0x102/0x320
2013-06-01T15:30:25.829+02:00 n22 kernel: [<c104f500>] ? manage_workers.isra.24+0x290/0x290
2013-06-01T15:30:25.829+02:00 n22 kernel: [<c1054b74>] kthread+0x94/0xa0
2013-06-01T15:30:25.829+02:00 n22 kernel: [<c1481a37>] ret_from_kernel_thread+0x1b/0x28
2013-06-01T15:30:25.829+02:00 n22 kernel: [<c1054ae0>] ? flush_kthread_worker+0x90/0x90
2013-06-01T15:30:58.399+02:00 n22 kernel: SysRq : Emergency Sync
--
MfG/Sincerely
Toralf Förster
pgp finger print: 7B1A 07F4 EC82 0F90 D4C2 8936 872A E508 7DB6 9DA3
--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2013-06-01 13:48 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-30 17:58 found a scenario for BUG at fs/ext4/super.c:804! Toralf Förster
2013-05-30 18:06 ` Toralf Förster
2013-06-01 13:48 ` Toralf Förster [this message]
2013-06-01 15:00 ` Eric Sandeen
2013-06-01 15:27 ` Toralf Förster
2013-06-01 18:02 ` Toralf Förster
2013-07-06 9:38 ` Toralf Förster
2013-07-06 9:38 ` Toralf Förster
2013-08-03 14:44 ` Toralf Förster
2013-08-03 15:36 ` Toralf Förster
2013-08-03 15:36 ` Toralf Förster
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=51A9FBAA.2050906@gmx.de \
--to=toralf.foerster@gmx.de \
--cc=linux-ext4@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.