Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Created attachment 482942 [details] SCreen shot with panic message Description of problem: Kernel panic occurs quite often, right after mdadm -Ss command is invoked. Seems, that raid is correctly stopped (all devices are exported correctly) Version-Release number of selected component (if applicable): Output from uname -a: Linux gklab-128-053 2.6.32-118.el6.x86_64 #1 SMP Tue Feb 22 11:15:55 EST 2011 x86_64 x86_64 x86_64 GNU/Linux How reproducible: (often) Steps to Reproduce: eg. use this script: #!/bin/bash -x Create any container and raid: #create container (optional) mdadm -C /dev/md/imsm0 -e imsm -n 3 /dev/sd[a-c] -R #create array mdadm -C /dev/md/raid5 -l 5 -c 64 -z max -n 3 /dev/sd[a-c] -R # create simple config file mdadm -Esb > /etc/mdadm.conf #stop array mdadm -Ss while true ; do # assemble mdadm -As # wait a moment sleep 1 # stop mdadm -Ss # uncomment # echo "press any key" # read -n 1 done exit 0 Actual results: Console hangs with kernel panic (see attached screenshot) Expected results: Raid is stopped and no kernel panic occurs Additional info: mdadm 3.2 is used.