Even after the downgrade of kernel and of the corresponding files to the version 2.6.32-18 and downgrade of mdadm the problem still persists, so it is not bound specificallz to this package and to this version.
I have identified now (after the downgrades to 2.6.30-18) the following initial stack trace (some lines are missing from the top, I think, they were no longer on the screen): [<....>] ? bio_alloc_bioset+0x45/0xb7 [<....>] ? submit_bio+0xd6/0xf2 [<....>] ? md_super_write+0x84/0xb2 [md_mod] [<....>] ? xen_restore_fl_direct_end+0x0/0x1 [<....>] ? md_update_sb+0x268/0x31e [<....>] ? md_check_recovery+0x1e2/0x4b9 [md_mod] [<....>] ? raid1d+0x42/0xe0b [raid1] [<....>] ? finish_task_switch+0x44/0xaf [<....>] ? schedule_timeout+0x2e/0xdd [<....>] ? xen_restore_fl_direct_end+0x0/0x1 [<....>] ? xen_force_evtchn_callback+0x9/0xa [<....>] ? check_events+0x12/0x20 [<....>] ? xen_restore_fl_direct_end+0x0/0x1 [<....>] ? md_thread+0xf1/0x10f [md_mod] [<....>] ? autoremove_wake_function+0x0/0x2e [<....>] ? md_thread+0x0/0x10f [md_mod] [<....>] ? kthread+0x79/0x01 [<....>] ? child_rip+0xa/0x20 [<....>] ? int_ret_from_szs_call+0x7/0x1b [<....>] ? retinit_restore_args+0x5/0x6 [<....>] ? xen-restore-fl-direct-end+0x0/0x1 [<....>] ? xen-restore-fl-direct-end+0x0/0x1 [<....>] ? child_rip+0x0/0x20 Code: 00 00 c7 46 0c 00 00 00 00 c7 46 10 00 00 00 00 c7 46 14 00 00 00 00 c7 46 18 00 00 00 00 e8 10 63 fa ff 83 f8 00 41 89 c6 7d 04 <0f> 0b eb fe 75 08 45 31 e4 e9 9c 00 00 00 49 8b 7f 58 48 89 eb RIP [<....>] aac_build_sgraw+0x51/0x10a [aacraid] RSP <ffff88003cd998e0> --- [ end trace .... ] --- Now also this stack trace stays on the screen and nothing happens also after very long time (1 hour) -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
