general protection fault: 0000 [#1] PREEMPT SMP

laughing_man77 · November 1, 2010, 1:31am

Hi Guys,

I’m a beginner-intermediate suse user, and I’ve just updated hardware on my machine, and this involved removing the old opensuse 11.3 x86 OS, and installing opensuse x64, because I now have 8GB RAM. But ran into a problem, with mounting the old RAID disks.

For some reason, the OS would not see the partitions correctly, and no matter what I tried, I could not remount them. Luckily, I had made a prior backup of all the data on separate disks, and decided to wipe the existing RAID 5 disks, remount them as a new RAID 5 volume and then copy the data from the backup. But then ran into a new problem…

I can create the FD partitions on each of the 4 disks, no problem. But as soon as I try to create the RAID 5 volume, and attach these partitions to the volume, suse throws an error. Below is the dump from the syslog:

Nov 2 09:04:15 linux-ynag kernel: 855.908213] async_tx: api initialized (async)
Nov 2 09:04:15 linux-ynag kernel: 855.924268] xor: automatically using best checksumming function: generic_sse
Nov 2 09:04:15 linux-ynag kernel: 855.929002] generic_sse: 13084.000 MB/sec
Nov 2 09:04:15 linux-ynag kernel: 855.929003] xor: using function: generic_sse (13084.000 MB/sec)
Nov 2 09:04:15 linux-ynag kernel: 855.961191] raid6: int64x1 2906 MB/s
Nov 2 09:04:15 linux-ynag kernel: 855.978356] raid6: int64x2 3957 MB/s
Nov 2 09:04:15 linux-ynag kernel: 855.995322] raid6: int64x4 3019 MB/s
Nov 2 09:04:15 linux-ynag kernel: 856.012238] raid6: int64x8 2742 MB/s
Nov 2 09:04:15 linux-ynag kernel: 856.029189] raid6: sse2x1 4539 MB/s
Nov 2 09:04:15 linux-ynag kernel: 856.046430] raid6: sse2x2 7703 MB/s
Nov 2 09:04:15 linux-ynag kernel: 856.063087] raid6: sse2x4 8808 MB/s
Nov 2 09:04:15 linux-ynag kernel: 856.063088] raid6: using algorithm sse2x4 (8808 MB/s)
Nov 2 09:04:15 linux-ynag kernel: 856.085315] md: raid6 personality registered for level 6
Nov 2 09:04:15 linux-ynag kernel: 856.085316] md: raid5 personality registered for level 5
Nov 2 09:04:15 linux-ynag kernel: 856.085317] md: raid4 personality registered for level 4
Nov 2 09:04:16 linux-ynag kernel: 856.229397] md: bind<sdb1>
Nov 2 09:04:16 linux-ynag kernel: 856.229647] md: bind<sdc1>
Nov 2 09:04:16 linux-ynag kernel: 856.236986] md: bind<sdd1>
Nov 2 09:04:16 linux-ynag kernel: 856.237713] general protection fault: 0000 #1] PREEMPT SMP
Nov 2 09:04:16 linux-ynag kernel: 856.237715] last sysfs file: /sys/module/raid456/initstate
Nov 2 09:04:16 linux-ynag kernel: 856.237717] CPU 0
Nov 2 09:04:16 linux-ynag kernel: 856.237718] Modules linked in: raid456 async_raid6_recov async_pq raid6_pq async_xor xor async_memcpy async_tx st sr_mod cdrom ip6t_LOG xt_tcpudp xt_pkttype ipt_LOG xt_limit snd_pcm_oss snd_mixer_oss snd_seq snd_seq_device edd af_packet mperf ip6t_REJECT nf_conntrack_ipv6 ip6table_raw xt_NOTRACK ipt_REJECT xt_state iptable_raw iptable_filter ip6table_mangle nf_conntrack_netbios_ns nf_conntrack_ipv4 nf_conntrack nf_defrag_ipv4 ip_tables ip6table_filter ip6_tables x_tables fuse loop dm_mod snd_hda_codec_atihdmi snd_hda_codec_via firewire_ohci firewire_core crc_itu_t snd_hda_intel snd_hda_codec snd_hwdep snd_pcm ohci1394 asus_atk0110 joydev serio_raw edac_core edac_mce_amd snd_timer k10temp pcspkr snd wmi sg i2c_piix4 ieee1394 button xhci_hcd sky2 soundcore snd_page_alloc ext4 jbd2 crc16 radeon ttm drm_kms_helper sd_mod drm i2c_algo_bit fan processor ata_generic pata_atiixp pata_jmicron thermal thermal_sys ahci libata scsi_mod [last unloaded: preloadtrace]
Nov 2 09:04:16 linux-ynag kernel: 856.237745]
Nov 2 09:04:16 linux-ynag kernel: 856.237747] Pid: 8682, comm: mdadm Not tainted 2.6.34.7-0.5-desktop #1 Crosshair IV Formula/System Product Name
Nov 2 09:04:16 linux-ynag kernel: 856.237748] RIP: 0010:<ffffffff81077078>] <ffffffff81077078>] raw_notifier_chain_register+0x18/0x40
Nov 2 09:04:16 linux-ynag kernel: 856.237753] RSP: 0018:ffff8801fd1e5c00 EFLAGS: 00010286
Nov 2 09:04:16 linux-ynag kernel: 856.237754] RAX: 8b4c08246c8b4824 RBX: ffff8801fd1da120 RCX: 0000000000000001
Nov 2 09:04:16 linux-ynag kernel: 856.237755] RDX: 0000000000000000 RSI: ffff8801fd1da120 RDI: ffffffffa04af3f8
Nov 2 09:04:16 linux-ynag kernel: 856.237756] RBP: ffffffff81b197a0 R08: ffffffff81b197e0 R09: 0000000000000200
Nov 2 09:04:16 linux-ynag kernel: 856.237757] R10: ffff88022c7e4400 R11: 0000000000000010 R12: 0000000000000200
Nov 2 09:04:16 linux-ynag kernel: 856.237759] R13: ffff8801fd1da000 R14: 0000000000000003 R15: ffff88022d717000
Nov 2 09:04:16 linux-ynag kernel: 856.237760] FS: 00007f50f0536700(0000) GS:ffff880001e00000(0000) knlGS:00000000f6893860
Nov 2 09:04:16 linux-ynag kernel: 856.237761] CS: 0010 DS: 0000 ES: 0000 CR0: 000000008005003b
Nov 2 09:04:16 linux-ynag kernel: 856.237762] CR2: 00007ff1dad4b5b0 CR3: 000000020406b000 CR4: 00000000000006f0
Nov 2 09:04:16 linux-ynag kernel: 856.237763] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
Nov 2 09:04:16 linux-ynag kernel: 856.237765] DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
Nov 2 09:04:16 linux-ynag kernel: 856.237766] Process mdadm (pid: 8682, threadinfo ffff8801fd1e4000, task ffff8801fd074840)
Nov 2 09:04:16 linux-ynag kernel: 856.237767] Stack:
Nov 2 09:04:16 linux-ynag kernel: 856.237768] ffffffff8148ddc8 ffff8801fd1da000 ffffffffa050c5c1 ffff8801fd1da000
Nov 2 09:04:16 linux-ynag kernel: 856.237769] <0> ffff88022b584c00 0000000000000003 ffffffffa0510573 0000000015d50dff
Nov 2 09:04:16 linux-ynag kernel: 856.237771] <0> ffff88022fc22440 0000000000000000 ffffffffffffffff ffff8801fd1e5c98
Nov 2 09:04:16 linux-ynag kernel: 856.237773] Call Trace:
Nov 2 09:04:16 linux-ynag kernel: 856.237779] <ffffffff8148ddc8>] register_cpu_notifier+0x18/0x30
Nov 2 09:04:16 linux-ynag kernel: 856.237783] <ffffffffa050c5c1>] raid5_alloc_percpu+0xe1/0x110 [raid456]
Nov 2 09:04:16 linux-ynag kernel: 856.237794] <ffffffffa0510573>] setup_conf+0x203/0x640 [raid456]
Nov 2 09:04:16 linux-ynag kernel: 856.237800] <ffffffffa051102e>] run+0x47e/0x7c0 [raid456]
Nov 2 09:04:16 linux-ynag kernel: 856.237806] <ffffffff8137430c>] do_md_run+0x3dc/0x830
Nov 2 09:04:16 linux-ynag kernel: 856.237809] <ffffffff81375ec1>] md_ioctl+0x581/0x6a0
Nov 2 09:04:16 linux-ynag kernel: 856.237813] <ffffffff8121fd6d>] blkdev_ioctl+0x20d/0x7b0
Nov 2 09:04:16 linux-ynag kernel: 856.237816] <ffffffff8115328c>] block_ioctl+0x3c/0x50
Nov 2 09:04:16 linux-ynag kernel: 856.237819] <ffffffff81134d99>] vfs_ioctl+0x39/0xc0
Nov 2 09:04:16 linux-ynag kernel: 856.237821] <ffffffff81135330>] do_vfs_ioctl+0x70/0x3d0
Nov 2 09:04:16 linux-ynag kernel: 856.237823] <ffffffff81135710>] sys_ioctl+0x80/0xa0
Nov 2 09:04:16 linux-ynag kernel: 856.237826] <ffffffff81002ffb>] system_call_fastpath+0x16/0x1b
Nov 2 09:04:16 linux-ynag kernel: 856.237830] <00007f50f009ce87>] 0x7f50f009ce87
Nov 2 09:04:16 linux-ynag kernel: 856.237831] Code: 00 48 8b 74 24 08 89 c5 eb d1 90 90 90 90 90 90 90 90 90 48 8b 07 48 85 c0 74 22 8b 56 10 3b 50 10 7e 0d eb 18 66 0f 1f 44 00 00 <39> 50 10 7c 0d 48 8d 78 08 48 8b 40 08 48 85 c0 75 ee 48 89 46
Nov 2 09:04:16 linux-ynag kernel: 856.237842] RIP <ffffffff81077078>] raw_notifier_chain_register+0x18/0x40
Nov 2 09:04:16 linux-ynag kernel: 856.237844] RSP <ffff8801fd1e5c00>
Nov 2 09:04:16 linux-ynag kernel: 856.237846] — end trace 06e9f0c0a0fa1fd8 ]—

Has anyone seen anything like this before? I’ve searched through the net and forums, and found similar reports of this kind of error, but nothing that I could make sense of.

I’m assuming that this is an x64 issue, because these disks were working fine before, on 32-bit opensuse, unless it’s because this is a relatively new motherboards and chipset.

laughing_man77 · November 3, 2010, 10:30am

cough actually, better make my status newb, lol. Has anyone got an idea about this, is this the right forum for this question?

laughing_man77 · November 4, 2010, 10:37pm

help, anyone? Lots of people reading the thread, but no suggestions for help…

laughing_man77 · November 6, 2010, 7:13am

FWIW and anyone else facing this issue, when I used bash line to create the raid volume, I had no issues at all (an excellent guide is on Quick HOWTO : Ch26 : Linux Software RAID - Linux Home Networking).

I still had issues with creating raid volume from the partitions I had created in Yast, although perhaps something was corrupted by the aborted attempt in Yast. So I had used fdisk to recreate the fd partitions, then mdadm to create the volume.

To recreate the ptoblem:

Yast -> Partitioner
Click on Hard Disks, then each raid disk in turn and create a Linux Raid Partition (no mount and no format)
Finish, and all looks fine and ready for raid volume creation
Click on Raid -> add Raid. Assign all disks for raid (in my case it was x4 1.5TB disks), (options: format to ext3, mount to /media/raid)

It got to 40-50% each time, and would spit out the above failure and dump notice. clicking on abort (or continue) would cause the process to hang. You could not get back in to Partitioner to see what had happened, because some process had a lock on it (presumably the previous partitioner). So had to restart system, cos I wasn’t brave enough to start killing Yast processes.

Is this a bug, should I report it?

laughing_man77 · November 17, 2010, 11:52pm

More woes…

Somehow, while browsing the filesystem through HandBrake explorer, the raid5 broke. I have no idea why this happened, but think perhaps this might be linked to my previous issues, because all I was doing was browsing and looking for a file.

Anyway, the system refused to reboot correctly, complaining about corrupted superblock. So I had commented out the /dev/md0 line in fstab to get the system up and running. This worked, showing the issue was with the raid array.

Looking at the partitions on the 4 disks, Yast recognises them correctly as Linux Raid Partition. So I’m assuming and hoping that no data has been lost. When I try and add the raid in Yast (adding all 4 disks, no format, no mount) as a test, I get the following error:

Failure occurred during the following action:
Creating software RAID /dev/mdo from /dev/sda1 /dev/sdb1 /dev/sdc1 /dev/sdd1

System error code was -6008

ls -l --full-time ‘/dev/sda1’ ‘/dev/sdb1’ ‘/dev/sdc1’ ‘/dev/sdd1’;/sbin/modprobe raid5;/sbin/mdadm --create ‘/dev/md0’ --run --level=5 -e 1.0 -b internal --chunk=128 --parity=left-asymmetric --raid-devices=4 ‘/dev/sda1’ ‘/dev/sdb1’ ‘/dev/sdc1’ ‘/dev/sdd1’:
mdadm:/dev/sda1 appears to contain an ext2fs file system
size=100440512K mtime=Sat Nov 6 16:08:21 2010
mdadm:/dev/sda1 appears to be part of a raid array:
level=5 devices=4 ctime=Thu Nov 18 00:59:09 2010
mdadm:/dev/sdb1 appears to be part of a raid array:
level=5 devices=4 ctime=Thu Nov 18 00:59:09 2010
mdadm:/dev/sdc1 appears to be part of a raid array:
level=5 devices=4 ctime=Thu Nov 18 00:59:09 2010
mdadm:/dev/sda1 appears to contain an ext2fs file system
size=368873920K mtime=Sat Nov 6 16:11:20 2010
mdadm:/dev/sdd1 appears to be part of a raid array:
level=5 devices=4 ctime=Thu Nov 18 00:59:09 2010
/bin/sh: line1: 8731 Segmentation fault /sbin/mdadm --create ‘/dev/md0’ --run --level=5 -e 1.0 -b internal --chunk=128 --parity=left-asymmetric --raid-devices=4 ‘/dev/sda1’ ‘/dev/sdb1’ ‘/dev/sdc1’ ‘/dev/sdd1’

Continue despite the error?

&lt;Continue&gt;     &lt;Abort&gt;

Yast partitioner progress bar showed that it was 50% through Preparing disks and had not started to create the raid. Clicking on Abort caused Yast to hang there. All other processes were available, but Yast had a lock on the process and could not be restarted.

This was exactly the message I was receiving last time while trying to create a raid 5 array in Yast , before.

Message appeared on the console I had open:

Message from syslogd@linux-ynag at Nov 18 09:13:24 …
kernel: 2020.739090] general protection fault: 0000 #1] PREEMPT SMP

Message from syslogd@linux-ynag at Nov 18 09:13:24 …
kernel: 2020.739093] last sysfs file: /sys/module/raid456/initstate

Message from syslogd@linux-ynag at Nov 18 09:13:24 …
kernel: 2020.739155] Stack:

Message from syslogd@linux-ynag at Nov 18 09:13:24 …
kernel: 2020.739163] Call Trace:

Message from syslogd@linux-ynag at Nov 18 09:13:24 …
kernel: 2020.739234] Code: 00 48 8b 74 24 08 89 c5 eb d1 90 90 90 90 90 90 90 90 90 48 8b 07 48 85 c0 74 22 8b 56 10 3b 50 10 7e 0d eb 18 66 0f 1f 44 00 00 <39> 50 10 7c 0d 48 8d 78 08 48 8b 40 08 48 85 c0 75 ee 48 89 46
/var/log/messages shows:

Nov 18 09:13:23 linux-ynag kernel: 2020.434664] async_tx: api initialized (async)
Nov 18 09:13:23 linux-ynag kernel: 2020.450855] xor: automatically using best checksumming function: generic_sse
Nov 18 09:13:23 linux-ynag kernel: 2020.454926] generic_sse: 14012.000 MB/sec
Nov 18 09:13:23 linux-ynag kernel: 2020.454927] xor: using function: generic_sse (14012.000 MB/sec)
Nov 18 09:13:23 linux-ynag kernel: 2020.479176] raid6: int64x1 2890 MB/s
Nov 18 09:13:24 linux-ynag kernel: 2020.496177] raid6: int64x2 3843 MB/s
Nov 18 09:13:24 linux-ynag kernel: 2020.513173] raid6: int64x4 2984 MB/s
Nov 18 09:13:24 linux-ynag kernel: 2020.530174] raid6: int64x8 2742 MB/s
Nov 18 09:13:24 linux-ynag kernel: 2020.547181] raid6: sse2x1 4406 MB/s
Nov 18 09:13:24 linux-ynag kernel: 2020.564174] raid6: sse2x2 7613 MB/s
Nov 18 09:13:24 linux-ynag kernel: 2020.581171] raid6: sse2x4 7902 MB/s
Nov 18 09:13:24 linux-ynag kernel: 2020.581172] raid6: using algorithm sse2x4 (7902 MB/s)
Nov 18 09:13:24 linux-ynag kernel: 2020.603616] md: raid6 personality registered for level 6
Nov 18 09:13:24 linux-ynag kernel: 2020.603618] md: raid5 personality registered for level 5
Nov 18 09:13:24 linux-ynag kernel: 2020.603619] md: raid4 personality registered for level 4
Nov 18 09:13:24 linux-ynag kernel: 2020.730234] md: bind<sda1>
Nov 18 09:13:24 linux-ynag kernel: 2020.730487] md: bind<sdb1>
Nov 18 09:13:24 linux-ynag kernel: 2020.730614] md: bind<sdc1>
Nov 18 09:13:24 linux-ynag kernel: 2020.737975] md: bind<sdd1>
Nov 18 09:13:24 linux-ynag kernel: 2020.739090] general protection fault: 0000 #1] PREEMPT SMP
Nov 18 09:13:24 linux-ynag kernel: 2020.739093] last sysfs file: /sys/module/raid456/initstate
Nov 18 09:13:24 linux-ynag kernel: 2020.739095] CPU 0
Nov 18 09:13:24 linux-ynag kernel: 2020.739096] Modules linked in: raid456 async_raid6_recov async_pq raid6_pq async_xor xor async_memcpy async_tx st ip6t_LOG xt_pkttype ipt_LOG xt_limit snd_pcm_oss snd_mixer_oss snd_seq snd_seq_device edd af_packet mperf ip6t_REJECT nf_conntrack_ipv6 ip6table_raw xt_tcpudp xt_multiport xt_NOTRACK ipt_REJECT xt_state iptable_raw iptable_filter ip6table_mangle nf_conntrack_netbios_ns nf_conntrack_ipv4 nf_conntrack nf_defrag_ipv4 ip_tables ip6table_filter ip6_tables x_tables loop dm_mod snd_hda_codec_atihdmi snd_hda_codec_via firewire_ohci firewire_core crc_itu_t edac_core snd_hda_intel serio_raw k10temp snd_hda_codec edac_mce_amd snd_hwdep snd_pcm sr_mod pcspkr cdrom joydev snd_timer snd soundcore i2c_piix4 snd_page_alloc sg asus_atk0110 ohci1394 sky2 xhci_hcd ieee1394 wmi button ext4 jbd2 crc16 radeon ttm drm_kms_helper drm i2c_algo_bit sd_mod fan processor ata_generic pata_atiixp pata_jmicron thermal thermal_sys ahci libata scsi_mod [last unloaded: preloadtrace]
Nov 18 09:13:24 linux-ynag kernel: 2020.739130]
Nov 18 09:13:24 linux-ynag kernel: 2020.739132] Pid: 8731, comm: mdadm Not tainted 2.6.34.7-0.5-desktop #1 Crosshair IV Formula/System Product Name
Nov 18 09:13:24 linux-ynag kernel: 2020.739133] RIP: 0010:<ffffffff81077078>] <ffffffff81077078>] raw_notifier_chain_register+0x18/0x40
Nov 18 09:13:24 linux-ynag kernel: 2020.739139] RSP: 0018:ffff8801a33adc00 EFLAGS: 00010286
Nov 18 09:13:24 linux-ynag kernel: 2020.739140] RAX: 8b4c08246c8b4824 RBX: ffff8801cdb7f920 RCX: 0000000000000006
Nov 18 09:13:24 linux-ynag kernel: 2020.739142] RDX: 0000000000000000 RSI: ffff8801cdb7f920 RDI: ffffffffa04bf3f8
Nov 18 09:13:24 linux-ynag kernel: 2020.739143] RBP: ffffffff81b197a0 R08: ffffffff81b197e0 R09: 0000000000000200
Nov 18 09:13:24 linux-ynag kernel: 2020.739144] R10: ffff88022be24400 R11: 0000000000000010 R12: 0000000000000200
Nov 18 09:13:24 linux-ynag kernel: 2020.739146] R13: ffff8801cdb7f800 R14: 0000000000000004 R15: ffff8801cda5d000
Nov 18 09:13:24 linux-ynag kernel: 2020.739147] FS: 00007fc4dbaef700(0000) GS:ffff880001e00000(0000) knlGS:00000000f6871860
Nov 18 09:13:24 linux-ynag kernel: 2020.739149] CS: 0010 DS: 0000 ES: 0000 CR0: 000000008005003b
Nov 18 09:13:24 linux-ynag kernel: 2020.739150] CR2: 00007ffa28341550 CR3: 000000022955a000 CR4: 00000000000006f0
Nov 18 09:13:24 linux-ynag kernel: 2020.739151] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
Nov 18 09:13:24 linux-ynag kernel: 2020.739153] DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
Nov 18 09:13:24 linux-ynag kernel: 2020.739154] Process mdadm (pid: 8731, threadinfo ffff8801a33ac000, task ffff88022955e6c0)
Nov 18 09:13:24 linux-ynag kernel: 2020.739155] Stack:
Nov 18 09:13:24 linux-ynag kernel: 2020.739156] ffffffff8148ddc8 ffff8801cdb7f800 ffffffffa05025c1 ffff8801cdb7f800
Nov 18 09:13:24 linux-ynag kernel: 2020.739158] <0> ffff88022b098400 0000000000000004 ffffffffa0506573 ffffffff81b19760
Nov 18 09:13:24 linux-ynag kernel: 2020.739160] <0> ffff88022fc22440 0000000000000000 ffffffffffffffff ffff8801a33adc98
Nov 18 09:13:24 linux-ynag kernel: 2020.739163] Call Trace:
Nov 18 09:13:24 linux-ynag kernel: 2020.739169] <ffffffff8148ddc8>] register_cpu_notifier+0x18/0x30
Nov 18 09:13:24 linux-ynag kernel: 2020.739174] <ffffffffa05025c1>] raid5_alloc_percpu+0xe1/0x110 [raid456]
Nov 18 09:13:24 linux-ynag kernel: 2020.739187] <ffffffffa0506573>] setup_conf+0x203/0x640 [raid456]
Nov 18 09:13:24 linux-ynag kernel: 2020.739193] <ffffffffa050702e>] run+0x47e/0x7c0 [raid456]
Nov 18 09:13:24 linux-ynag kernel: 2020.739200] <ffffffff8137430c>] do_md_run+0x3dc/0x830
Nov 18 09:13:24 linux-ynag kernel: 2020.739204] <ffffffff81375ec1>] md_ioctl+0x581/0x6a0
Nov 18 09:13:24 linux-ynag kernel: 2020.739208] <ffffffff8121fd6d>] blkdev_ioctl+0x20d/0x7b0
Nov 18 09:13:24 linux-ynag kernel: 2020.739212] <ffffffff8115328c>] block_ioctl+0x3c/0x50
Nov 18 09:13:24 linux-ynag kernel: 2020.739216] <ffffffff81134d99>] vfs_ioctl+0x39/0xc0
Nov 18 09:13:24 linux-ynag kernel: 2020.739218] <ffffffff81135330>] do_vfs_ioctl+0x70/0x3d0
Nov 18 09:13:24 linux-ynag kernel: 2020.739221] <ffffffff81135710>] sys_ioctl+0x80/0xa0
Nov 18 09:13:24 linux-ynag kernel: 2020.739228] <ffffffff81002ffb>] system_call_fastpath+0x16/0x1b
Nov 18 09:13:24 linux-ynag kernel: 2020.739233] <00007fc4db656e87>] 0x7fc4db656e87
Nov 18 09:13:24 linux-ynag kernel: 2020.739234] Code: 00 48 8b 74 24 08 89 c5 eb d1 90 90 90 90 90 90 90 90 90 48 8b 07 48 85 c0 74 22 8b 56 10 3b 50 10 7e 0d eb 18 66 0f 1f 44 00 00 <39> 50 10 7c 0d 48 8d 78 08 48 8b 40 08 48 85 c0 75 ee 48 89 46
Nov 18 09:13:24 linux-ynag kernel: 2020.739248] RIP <ffffffff81077078>] raw_notifier_chain_register+0x18/0x40
Nov 18 09:13:24 linux-ynag kernel: 2020.739251] RSP <ffff8801a33adc00>
Nov 18 09:13:24 linux-ynag kernel: 2020.739252] — end trace a9faea4baf894a84 ]—
I really am at a loss here. Can anyone help, would this be better posted in another forum?

laughing_man77 · November 17, 2010, 11:55pm

I had a typo in the above post, it should read:

Failure occurred during the following action:
Creating software RAID /dev/mdo from /dev/sda1 /dev/sdb1 /dev/sdc1 /dev/sdd1

System error code was -6008

ls -l --full-time ‘/dev/sda1’ ‘/dev/sdb1’ ‘/dev/sdc1’ ‘/dev/sdd1’;/sbin/modprobe raid5;/sbin/mdadm --create ‘/dev/md0’ --run --level=5 -e 1.0 -b internal --chunk=128 --parity=left-asymmetric --raid-devices=4 ‘/dev/sda1’ ‘/dev/sdb1’ ‘/dev/sdc1’ ‘/dev/sdd1’:
mdadm:/dev/sda1 appears to contain an ext2fs file system
size=100440512K mtime=Sat Nov 6 16:08:21 2010
mdadm:/dev/sda1 appears to be part of a raid array:
level=5 devices=4 ctime=Thu Nov 18 00:59:09 2010
mdadm:/dev/sdb1 appears to be part of a raid array:
level=5 devices=4 ctime=Thu Nov 18 00:59:09 2010
mdadm:/dev/sdc1 appears to be part of a raid array:
level=5 devices=4 ctime=Thu Nov 18 00:59:09 2010
mdadm:/dev/sdd1 appears to contain an ext2fs file system
size=368873920K mtime=Sat Nov 6 16:11:20 2010
mdadm:/dev/sdd1 appears to be part of a raid array:
level=5 devices=4 ctime=Thu Nov 18 00:59:09 2010
/bin/sh: line1: 8731 Segmentation fault /sbin/mdadm --create ‘/dev/md0’ --run --level=5 -e 1.0 -b internal --chunk=128 --parity=left-asymmetric --raid-devices=4 ‘/dev/sda1’ ‘/dev/sdb1’ ‘/dev/sdc1’ ‘/dev/sdd1’

Continue despite the error?

<Continue> <Abort>

laughing_man77 · November 22, 2010, 9:52am

I tried creating the raid with fresh disks, and received the same message in /var/log/messages. So it’s not a hardware fault in the disks. Can anyone help?

DenverD · November 22, 2010, 5:36pm

laughing man77 wrote:

> Can anyone help?

suggest you start over, with a post to the openSUSE mail list…maybe
someone there will be able to help…see:
http://en.opensuse.org/openSUSE:Communication_channels

be SURE to read rules of engagement–the mailing list netiquette
before your first post!

–
DenverD
CAVEAT: http://is.gd/bpoMD [posted via NNTP w/openSUSE 10.3]

laughing_man77 · November 22, 2010, 10:08pm

Thanks for getting back denverD.

be SURE to read rules of engagement–the mailing list netiquette
before your first post!

I hope I didn’t break any ettiquette rules on this forum.

I’ve also been chatting on techsupportforum about this issue and they arrived at the same conclusion as me, and I’ve raised a suspected bug report in openSUSE bugzilla (FYI https://bugzilla.novell.com/show_bug.cgi?id=655215), because it’s a new chipset and not in the HCL lists yet. Thanks again.

DenverD · November 23, 2010, 2:21pm

laughing man77 wrote:

> I hope I didn’t break any ettiquette rules on this forum.

no…that was not my point…my point was that you can follow all the
rules here (and in any distro’s web forum) and not have a clue what is
expected over on the mail list, because they ARE different from all
web fora i’ve seen…

–
DenverD
CAVEAT: http://is.gd/bpoMD [posted via NNTP w/openSUSE 10.3]

laughing_man77 · November 24, 2010, 9:05am

Thanks, that’s all good then. I appreciate the advice

BTW, fyi it was a bug in the kernel (re. the bug report I posted above). the fix will be in future kernel releases.

In the meantime, if anyone else has this error, it was caused by a bug in powernow-k8 module not cleaning up after itself properly and corrupting the cpu notifier list, so when raid5 tried to walk the list to add it’s own cpu notification, it found an address was pointing to nonsense.

The thing that revealed this bug was not having a _pss table for the kernel to process. Ensure that cool ‘n’ quiet is active in the bios until the bugfix is released.

DenverD · November 24, 2010, 2:36pm

> BTW, fyi it was a bug in the kernel (re. the bug report I posted
> above). the fix will be in future kernel releases.

kewl…thanks for contributing…

–
DenverD
CAVEAT: http://is.gd/bpoMD [posted via NNTP w/openSUSE 10.3]

laughing_man77 · November 24, 2010, 9:20pm

Problem solved. It was a bug in the kernel (re the bug report I posted above). the fix will be in future kernel releases.

In the meantime, if anyone else has this error, it was caused by a bug in powernow-k8 module not cleaning up after itself properly and corrupting the cpu notifier list, so when raid5 tried to walk the list to add it’s own cpu notification, it found an address was pointing to nonsense and broke.

The thing that revealed this bug was not having a _pss table for the kernel to process. Ensure that cool ‘n’ quiet is active in the bios until the bugfix is released.