Verified to also occur on 2.6.33.4-95.fc13.x86_64.

This oops triggers every time I run mdadm -S /dev/md127.

If X is up, then the keyboard/mouse/X are unresponsive (however at least part of the kernel and userspace is still up, I have successfully ssh-ed in (authentication successful) although I did not get a shell prompt).
Unresponsive here means: no caps lock light toggle on caps lock key press, no seconds passing on X clock.

However if X is not up, then apparently besides the oops being logged nothing else happens (no hang).

I'm pretty sure this didn't happen with 2.6.32.13-120.fc12.x86_64.


May 28 20:29:14 nike kernel: md: md127 stopped.
May 28 20:29:14 nike kernel: md: unbind<dm-5>
May 28 20:29:14 nike kernel: md: export_rdev(dm-5)
May 28 20:29:14 nike kernel: md127: detected capacity change from 8589930496 to 0
May 28 20:29:14 nike kernel: BUG: unable to handle kernel paging request at 0000000000fffff8
May 28 20:29:14 nike kernel: IP: [<ffffffff811566f4>] sysfs_remove_group+0x8c/0xc5
May 28 20:29:14 nike kernel: PGD ac02d067 PUD a483f067 PMD 0 
May 28 20:29:14 nike kernel: Oops: 0000 [#1] SMP 
May 28 20:29:14 nike kernel: last sysfs file: /sys/devices/virtual/block/md127/uevent
May 28 20:29:14 nike kernel: CPU 0 
May 28 20:29:14 nike kernel: Pid: 9, comm: events/0 Not tainted 2.6.33.5-112.fc13.x86_64 #1 Mac-F42C89C8/MacBookPro4,1
May 28 20:29:14 nike kernel: RIP: 0010:[<ffffffff811566f4>]  [<ffffffff811566f4>] sysfs_remove_group+0x8c/0xc5
May 28 20:29:14 nike kernel: RSP: 0018:ffff88013bae9de0  EFLAGS: 00010206
May 28 20:29:14 nike kernel: RAX: 0000000000000013 RBX: ffff8801399e1a00 RCX: 0000000000000000
May 28 20:29:14 nike kernel: RDX: 0000000000000064 RSI: 0000000000000000 RDI: ffff88013a3be448
May 28 20:29:14 nike kernel: RBP: ffff88013bae9e00 R08: ffff88013bae8000 R09: ffff8800a4865db8
May 28 20:29:14 nike kernel: R10: ffff88013912bc30 R11: ffff880137f723c8 R12: ffff8801393b17d0
May 28 20:29:14 nike kernel: R13: 0000000000fffff8 R14: ffff8801393b17d0 R15: ffff880005818248
May 28 20:29:14 nike kernel: FS:  0000000000000000(0000) GS:ffff880005800000(0000) knlGS:0000000000000000
May 28 20:29:14 nike kernel: CS:  0010 DS: 0000 ES: 0000 CR0: 000000008005003b
May 28 20:29:14 nike kernel: CR2: 0000000000fffff8 CR3: 00000000a84e5000 CR4: 00000000000006f0
May 28 20:29:14 nike kernel: DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
May 28 20:29:14 nike kernel: DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
May 28 20:29:14 nike kernel: Process events/0 (pid: 9, threadinfo ffff88013bae8000, task ffff88013bad5d40)
May 28 20:29:14 nike kernel: Stack:
May 28 20:29:14 nike kernel: ffff88013a3be650 ffff88013a3be400 ffff88013a3be448 ffff88013bad5d40
May 28 20:29:14 nike kernel: <0> ffff88013bae9e30 ffffffff813413a9 ffff88013bad5d40 ffff880005818240
May 28 20:29:14 nike kernel: <0> ffff88013bad5d40 ffff88013bad5d40 ffff88013bae9ee0 ffffffff81060d31
May 28 20:29:14 nike kernel: Call Trace:
May 28 20:29:14 nike kernel: [<ffffffff813413a9>] mddev_delayed_delete+0x4a/0x98
May 28 20:29:14 nike kernel: [<ffffffff81060d31>] worker_thread+0x1a4/0x232
May 28 20:29:14 nike kernel: [<ffffffff8134135f>] ? mddev_delayed_delete+0x0/0x98
May 28 20:29:14 nike kernel: [<ffffffff8106480b>] ? autoremove_wake_function+0x0/0x34
May 28 20:29:14 nike kernel: [<ffffffff81060b8d>] ? worker_thread+0x0/0x232
May 28 20:29:14 nike kernel: [<ffffffff810643bb>] kthread+0x7a/0x82
May 28 20:29:14 nike kernel: [<ffffffff8100a924>] kernel_thread_helper+0x4/0x10
May 28 20:29:14 nike kernel: [<ffffffff81064341>] ? kthread+0x0/0x82
May 28 20:29:14 nike kernel: [<ffffffff8100a920>] ? kernel_thread_helper+0x0/0x10
May 28 20:29:14 nike kernel: Code: 00 00 00 48 c7 c7 23 dc 77 81 e8 8c 4e ef ff f0 41 ff 06 4d 89 f4 4c 8b 6b 10 eb 0f 48 8b 30 4c 89 e7 49 83 c5 08 e8 b9 d1 ff ff <49> 8b 45 00 48 85 c0 75 e8 48 83 3b 00 74 08 4c 89 e7 e8 50 ed 
May 28 20:29:14 nike kernel: RIP  [<ffffffff811566f4>] sysfs_remove_group+0x8c/0xc5
May 28 20:29:14 nike kernel: RSP <ffff88013bae9de0>
May 28 20:29:14 nike kernel: CR2: 0000000000fffff8
May 28 20:29:14 nike kernel: ---[ end trace 2d0095a978b29fec ]---

Oh, forgot to mention this: the background sync of other raid arrays is irrelevant.

I've verified I can stop a normal raid array just fine, thus:

Current theory is that this is related to either:
- an (linear) md raid array with partitions,
or to
- a 1 disk linear md raid array on lvm on top of raid1.

This message is a reminder that Fedora 13 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 13.  It is Fedora's policy to close all
bug reports from releases that are no longer maintained.  At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '13'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 13's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 13 is end of life.  If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora please change the 'version' of this 
bug to the applicable version.  If you are unable to change the version, 
please add a comment here and someone will do it for you.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events.  Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Fedora 13 changed to end-of-life (EOL) status on 2011-06-25. Fedora 13 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.