[Bug 655215] New: mdadm --create --verbose /dev/md0 --level=5 --raid-devices=3 ... gives general protection fault: 0000 [#1] PREEMPT SMP
https://bugzilla.novell.com/show_bug.cgi?id=655215 https://bugzilla.novell.com/show_bug.cgi?id=655215#c0 Summary: mdadm --create --verbose /dev/md0 --level=5 --raid-devices=3 ... gives general protection fault: 0000 [#1] PREEMPT SMP Classification: openSUSE Product: openSUSE 11.3 Version: Final Platform: 64bit OS/Version: openSUSE 11.3 Status: NEW Severity: Normal Priority: P5 - None Component: Kernel AssignedTo: kernel-maintainers@forge.provo.novell.com ReportedBy: laughing_man77@hotmail.com QAContact: qa@suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-GB; rv:1.9.2.12) Gecko/20101026 SUSE/3.6.12-0.7.1 Firefox/3.6.12 Cannot create a raid5 array on my new system. Partitions create ok, but mdadm --create always results in a general protection fault: 0000 [#1] PREEMPT SMP New hardware: mobo: Asus Crosshair IV Formula cpu: AMD Phenom II x6 Disks for data raid5: WDC WD20EARS-00M OS: new install of openSUSE 11.3 I've tested this with my old raid disks and also these new ones, and get the same error. I'm a bit of a newb, and many apologies if this isn't as bug, but the OS is a fresh install and I cannot find the reason for this error Reproducible: Always Steps to Reproduce: 1. fdisk /dev/sda WARNING: DOS-compatible mode is deprecated. It's strongly recommended to switch off the mode (command 'c') and change display units to sectors (command 'u'). Command (m for help): c DOS Compatibility flag is not set Command (m for help): p Disk /dev/sda: 2000.4 GB, 2000398934016 bytes 255 heads, 63 sectors/track, 243201 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk identifier: 0x2b156edd Device Boot Start End Blocks Id System Command (m for help): n Command action e extended p primary partition (1-4) p Partition number (1-4): 1 First cylinder (1-243201, default 1): Using default value 1 Last cylinder, +cylinders or +size{K,M,G} (1-243201, default 243201): Using default value 243201 Command (m for help): t Selected partition 1 Hex code (type L to list codes): fd Changed system type of partition 1 to fd (Linux raid autodetect) Command (m for help): w The partition table has been altered! Calling ioctl() to re-read partition table. Syncing disks. 2. Repeat for all disks for raid 3. mdadm --create --verbose /dev/md0 --level=5 --raid-devices=3 /dev/sda1 /dev/sdb1 /dev/sdc1 Actual Results: konsole shows: # Message from syslogd@linux-ynag at Nov 22 19:23:45 ... kernel:[ 599.802309] Stack: Message from syslogd@linux-ynag at Nov 22 19:23:45 ... kernel:[ 599.802325] Call Trace: Message from syslogd@linux-ynag at Nov 22 19:23:45 ... kernel:[ 599.802402] 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 and then konsole locks (and the disksk are also locked until I reboot). Opening up a new konsole: #vi /var/log/messages Nov 22 19:21:17 linux-ynag kernel: [ 451.641023] sda: sda1 Nov 22 19:21:46 linux-ynag kernel: [ 481.354601] sdb: sdb1 Nov 22 19:22:09 linux-ynag kernel: [ 504.159279] sdc: sdc1 Nov 22 19:23:45 linux-ynag kernel: [ 599.579904] md: bind<sda1> Nov 22 19:23:45 linux-ynag kernel: [ 599.580004] md: bind<sdb1> Nov 22 19:23:45 linux-ynag kernel: [ 599.609869] md: bind<sdc1> Nov 22 19:23:45 linux-ynag kernel: [ 599.624891] async_tx: api initialized (async) Nov 22 19:23:45 linux-ynag kernel: [ 599.641102] xor: automatically using best checksumming function: generic_sse Nov 22 19:23:45 linux-ynag kernel: [ 599.645914] generic_sse: 12236.000 MB/sec Nov 22 19:23:45 linux-ynag kernel: [ 599.645915] xor: using function: generic_sse (12236.000 MB/sec) Nov 22 19:23:45 linux-ynag kernel: [ 599.668998] raid6: int64x1 2714 MB/s Nov 22 19:23:45 linux-ynag kernel: [ 599.685922] raid6: int64x2 3671 MB/s Nov 22 19:23:45 linux-ynag kernel: [ 599.702941] raid6: int64x4 2820 MB/s Nov 22 19:23:45 linux-ynag kernel: [ 599.719993] raid6: int64x8 2761 MB/s Nov 22 19:23:45 linux-ynag kernel: [ 599.737000] raid6: sse2x1 4445 MB/s Nov 22 19:23:45 linux-ynag kernel: [ 599.753997] raid6: sse2x2 7238 MB/s Nov 22 19:23:45 linux-ynag kernel: [ 599.770993] raid6: sse2x4 8593 MB/s Nov 22 19:23:45 linux-ynag kernel: [ 599.770994] raid6: using algorithm sse2x4 (8593 MB/s) Nov 22 19:23:45 linux-ynag kernel: [ 599.801915] md: raid6 personality registered for level 6 Nov 22 19:23:45 linux-ynag kernel: [ 599.801917] md: raid5 personality registered for level 5 Nov 22 19:23:45 linux-ynag kernel: [ 599.801917] md: raid4 personality registered for level 4 Nov 22 19:23:45 linux-ynag kernel: [ 599.802184] general protection fault: 0000 [#1] PREEMPT SMP Nov 22 19:23:45 linux-ynag kernel: [ 599.802189] last sysfs file: /sys/devices/pci0000:00/0000:00:11.0/host2/target2:0:0/2:0:0:0/model Nov 22 19:23:45 linux-ynag kernel: [ 599.802191] CPU 5 Nov 22 19:23:45 linux-ynag kernel: [ 599.802192] Modules linked in: raid456 async_raid6_recov async_pq raid6_pq async_xor xor async_memcpy async_tx 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_multiport xt_NOTRACK ipt_REJECT xt_state xt_tcpudp 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 snd_hda_intel snd_hda_codec snd_hwdep snd_pcm sr_mod snd_timer joydev ohci1394 pcspkr k10temp serio_raw snd soundcore asus_atk0110 i2c_piix4 cdrom edac_core xhci_hcd sky2 edac_mce_amd sg snd_page_alloc 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 22 19:23:45 linux-ynag kernel: [ 599.802276] Nov 22 19:23:45 linux-ynag kernel: [ 599.802278] Pid: 8215, comm: mdadm Not tainted 2.6.34.7-0.5-desktop #1 Crosshair IV Formula/System Product Name Nov 22 19:23:45 linux-ynag kernel: [ 599.802281] RIP: 0010:[<ffffffff81077078>] [<ffffffff81077078>] raw_notifier_chain_register+0x18/0x40 Nov 22 19:23:45 linux-ynag kernel: [ 599.802287] RSP: 0018:ffff88022e791c00 EFLAGS: 00010286 Nov 22 19:23:45 linux-ynag kernel: [ 599.802289] RAX: 8b4c08246c8b4824 RBX: ffff88022dd59b20 RCX: 0000000000000006 Nov 22 19:23:45 linux-ynag kernel: [ 599.802291] RDX: 0000000000000000 RSI: ffff88022dd59b20 RDI: ffffffffa04af3f8 Nov 22 19:23:45 linux-ynag kernel: [ 599.802292] RBP: ffffffff81b197a0 R08: ffffffff81b197e0 R09: 0000000000000200 Nov 22 19:23:45 linux-ynag kernel: [ 599.802294] R10: ffff88022be23400 R11: 0000000000000010 R12: 0000000000000200 Nov 22 19:23:45 linux-ynag kernel: [ 599.802296] R13: ffff88022dd59a00 R14: 0000000000000003 R15: ffff880229356000 Nov 22 19:23:45 linux-ynag kernel: [ 599.802298] FS: 00007fcf768d3700(0000) GS:ffff880001f40000(0000) knlGS:0000000000000000 Nov 22 19:23:45 linux-ynag kernel: [ 599.802300] CS: 0010 DS: 0000 ES: 0000 CR0: 000000008005003b Nov 22 19:23:45 linux-ynag kernel: [ 599.802302] CR2: 00007fcf7643d0d0 CR3: 000000022d8ab000 CR4: 00000000000006e0 Nov 22 19:23:45 linux-ynag kernel: [ 599.802304] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 Nov 22 19:23:45 linux-ynag kernel: [ 599.802306] DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400 Nov 22 19:23:45 linux-ynag kernel: [ 599.802308] Process mdadm (pid: 8215, threadinfo ffff88022e790000, task ffff88022e760300) Nov 22 19:23:45 linux-ynag kernel: [ 599.802309] Stack: Nov 22 19:23:45 linux-ynag kernel: [ 599.802311] ffffffff8148ddc8 ffff88022dd59a00 ffffffffa04f25c1 ffff88022dd59a00 Nov 22 19:23:45 linux-ynag kernel: [ 599.802315] <0> ffff88022ba26800 0000000000000003 ffffffffa04f6573 0000000000000001 Nov 22 19:23:45 linux-ynag kernel: [ 599.802320] <0> ffff88022fc22440 0000000000000001 0000000000000001 ffffffff81373fff Nov 22 19:23:45 linux-ynag kernel: [ 599.802325] Call Trace: Nov 22 19:23:45 linux-ynag kernel: [ 599.802332] [<ffffffff8148ddc8>] register_cpu_notifier+0x18/0x30 Nov 22 19:23:45 linux-ynag kernel: [ 599.802338] [<ffffffffa04f25c1>] raid5_alloc_percpu+0xe1/0x110 [raid456] Nov 22 19:23:45 linux-ynag kernel: [ 599.802351] [<ffffffffa04f6573>] setup_conf+0x203/0x640 [raid456] Nov 22 19:23:45 linux-ynag kernel: [ 599.802358] [<ffffffffa04f702e>] run+0x47e/0x7c0 [raid456] Nov 22 19:23:45 linux-ynag kernel: [ 599.802366] [<ffffffff8137430c>] do_md_run+0x3dc/0x830 Nov 22 19:23:45 linux-ynag kernel: [ 599.802370] [<ffffffff81375ec1>] md_ioctl+0x581/0x6a0 Nov 22 19:23:45 linux-ynag kernel: [ 599.802375] [<ffffffff8121fd6d>] blkdev_ioctl+0x20d/0x7b0 Nov 22 19:23:45 linux-ynag kernel: [ 599.802380] [<ffffffff8115328c>] block_ioctl+0x3c/0x50 Nov 22 19:23:45 linux-ynag kernel: [ 599.802384] [<ffffffff81134d99>] vfs_ioctl+0x39/0xc0 Nov 22 19:23:45 linux-ynag kernel: [ 599.802388] [<ffffffff81135330>] do_vfs_ioctl+0x70/0x3d0 Nov 22 19:23:45 linux-ynag kernel: [ 599.802391] [<ffffffff81135710>] sys_ioctl+0x80/0xa0 Nov 22 19:23:45 linux-ynag kernel: [ 599.802396] [<ffffffff81002ffb>] system_call_fastpath+0x16/0x1b Nov 22 19:23:45 linux-ynag kernel: [ 599.802401] [<00007fcf7643be87>] 0x7fcf7643be87 Nov 22 19:23:45 linux-ynag kernel: [ 599.802402] 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 22 19:23:45 linux-ynag kernel: [ 599.802457] RIP [<ffffffff81077078>] raw_notifier_chain_register+0x18/0x40 Nov 22 19:23:45 linux-ynag kernel: [ 599.802460] RSP <ffff88022e791c00> Nov 22 19:23:45 linux-ynag kernel: [ 599.802520] ---[ end trace 9a8fff311c77b9df ]--- -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=655215 https://bugzilla.novell.com/show_bug.cgi?id=655215#c Jeff Mahoney <jeffm@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jeffm@novell.com AssignedTo|kernel-maintainers@forge.pr |nfbrown@novell.com |ovo.novell.com | -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=655215 https://bugzilla.novell.com/show_bug.cgi?id=655215#c1 Neil Brown <nfbrown@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO InfoProvider| |laughing_man77@hotmail.com --- Comment #1 from Neil Brown <nfbrown@novell.com> 2010-11-23 12:31:13 UTC --- As part of initialisation, raid5 registers a 'CPU notifier'. As it sets the priority to 0, raw_notifier_chain_register must walk all the way to the end of the list to add the notifier. So if there is any corruption on the list, this will find it. And it does. The value in RAX: 8b4c08246c8b4824, should be the address of the next notifier on the list, but it is garbage. Hence the crash. So it could be something else that is corrupting this list, or it could be raid - it is hard to tell which. If you reboot, can you then create a raid5? Or does it always fail reliably on the first attempt? If it does fail on the first attempt it is unlikely to be raid corrupting the list, as it won't have had a chance to corrupt it yet. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=655215 https://bugzilla.novell.com/show_bug.cgi?id=655215#c2 --- Comment #2 from laughing man <laughing_man77@hotmail.com> 2010-11-23 20:57:47 UTC --- On reboot, it is the same - I cannot create the raid and get the same error. However, it does not reboot correctly and hangs at the point of "unmounting filesystems". I have to press the reset button at this point. But the system starts correctly after this. There is one other thing that I have noticed, that may be linked to this issue... in the normal shutdown/restart process (without the raid shenanigans, ie. not restarting because there has been an error), restart works fine. But shutdown hangs after logging: sending all process the TERM signal The system will be halted immediately general protection fault: 0000 [#1] PREEMPT SMP the last sysfs file is ... scsidisk/2:0:0:0/manage_start_stop cpu1 . . . Segmentation fault Master resource control: runlevel 0 has been reachd stopped services in runlevel 0: SuSefirewall2_setup This is transcribed by hand, and I may have missed out important information for you. I had thought it was a separate issue, but while copying the text down, I had noticed reference to scsi disks. In addition, I noticed further logging of errors, when I did standard shutdown/reboot: Nov 24 07:30:33 linux-ynag kernel: imklog 5.4.0, log source = /proc/kmsg started. Nov 24 07:30:33 linux-ynag rsyslogd: [origin software="rsyslogd" swVersion="5.4.0" x-pid="1901" x-info="http://www.rsyslog.com"] start Nov 24 07:30:33 linux-ynag kernel: [ 9.349838] type=1505 audit(1290544227.866:2): operation="profile_load" pid=1436 name=/bin/ping Nov 24 07:30:33 linux-ynag kernel: [ 9.377997] type=1505 audit(1290544227.895:3): operation="profile_load" pid=1437 name=/sbin/klogd Nov 24 07:30:33 linux-ynag kernel: [ 9.433001] type=1505 audit(1290544227.950:4): operation="profile_load" pid=1438 name=/sbin/syslog-ng Nov 24 07:30:33 linux-ynag kernel: [ 9.487674] type=1505 audit(1290544228.004:5): operation="profile_load" pid=1439 name=/sbin/syslogd Nov 24 07:30:33 linux-ynag kernel: [ 9.547009] type=1505 audit(1290544228.064:6): operation="profile_load" pid=1440 name=/usr/sbin/avahi-daemon Nov 24 07:30:33 linux-ynag kernel: [ 9.596172] type=1505 audit(1290544228.113:7): operation="profile_load" pid=1441 name=/usr/sbin/identd Nov 24 07:30:33 linux-ynag kernel: [ 9.650274] type=1505 audit(1290544228.167:8): operation="profile_load" pid=1442 name=/usr/sbin/mdnsd Nov 24 07:30:33 linux-ynag kernel: [ 9.713413] type=1505 audit(1290544228.230:9): operation="profile_load" pid=1443 name=/usr/sbin/nscd Nov 24 07:30:33 linux-ynag kernel: [ 9.802839] type=1505 audit(1290544228.319:10): operation="profile_load" pid=1444 name=/usr/sbin/ntpd Nov 24 07:30:33 linux-ynag kernel: [ 9.851684] type=1505 audit(1290544228.368:11): operation="profile_load" pid=1445 name=/usr/sbin/traceroute Nov 24 07:30:33 linux-ynag kernel: [ 11.529786] ip6_tables: (C) 2000-2006 Netfilter Core Team Nov 24 07:30:33 linux-ynag kernel: [ 12.889519] ip_tables: (C) 2000-2006 Netfilter Core Team Nov 24 07:30:33 linux-ynag kernel: [ 12.950624] nf_conntrack version 0.5.0 (16384 buckets, 65536 max) Nov 24 07:30:33 linux-ynag SuSEfirewall2: Firewall rules set to CLOSE. Nov 24 07:30:34 linux-ynag kernel: [ 15.971840] powernow-k8: Found 1 AMD Phenom(tm) II X6 1055T Processor (6 cpu cores) (version 2.20.00) Nov 24 07:30:34 linux-ynag kernel: [ 15.971849] powernow-k8: Core Performance Boosting: on. Nov 24 07:30:34 linux-ynag kernel: [ 15.971858] [Firmware Bug]: powernow-k8: No compatible ACPI _PSS objects found. Nov 24 07:30:34 linux-ynag kernel: [ 15.971859] [Firmware Bug]: powernow-k8: Try again with latest BIOS. This may not be linked at all, but perhaps it's contributory (you mentioned there could be something else corrupting the list). -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=655215 https://bugzilla.novell.com/show_bug.cgi?id=655215#c3 --- Comment #3 from laughing man <laughing_man77@hotmail.com> 2010-11-23 21:13:27 UTC --- Addendum: I noted that BIOS version is 0802, and latest version for this mobo is 1102. I'll do a BIOS flush and update and get back to you with a little further testing (I could have sworn I had updated the BIOS). -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=655215 https://bugzilla.novell.com/show_bug.cgi?id=655215#c4 --- Comment #4 from laughing man <laughing_man77@hotmail.com> 2010-11-23 23:24:19 UTC --- I remember now, I had to exchange the motherboard, due to a faulty DIMM socket, and had forgotten to update the BIOS on the new motherboard. Anyway, BIOS version is now latest (1102), and the results are the same (this is testing with my old disks, because I wanted to preserve data transferred onto the new disks): # fdisk -l Disk /dev/sda: 1500.3 GB, 1500301910016 bytes 255 heads, 63 sectors/track, 182401 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk identifier: 0x0004ed31 Device Boot Start End Blocks Id System /dev/sda1 1 182401 1465135008+ fd Linux raid autodetect Disk /dev/sdb: 1500.3 GB, 1500301910016 bytes 255 heads, 63 sectors/track, 182401 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk identifier: 0x000d7fb0 Device Boot Start End Blocks Id System /dev/sdb1 1 182401 1465135008+ fd Linux raid autodetect Disk /dev/sdc: 1500.3 GB, 1500301910016 bytes 255 heads, 63 sectors/track, 182401 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk identifier: 0x0001c481 Device Boot Start End Blocks Id System /dev/sdc1 1 182401 1465135008+ fd Linux raid autodetect Disk /dev/sdd: 300.1 GB, 300069052416 bytes 255 heads, 63 sectors/track, 36481 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk identifier: 0x69205244 Device Boot Start End Blocks Id System /dev/sdd1 1 262 2103296 82 Linux swap / Solaris Partition 1 does not end on cylinder boundary. /dev/sdd2 * 262 2873 20972544 83 Linux /dev/sdd3 2873 36482 269959168 83 Linux # mdadm --create --verbose /dev/md0 --level=5 --raid-devices=3 /dev/sda1 /dev/sdb1 /dev/sdc1 mdadm: layout defaults to left-symmetric mdadm: chunk size defaults to 64K mdadm: layout defaults to left-symmetric mdadm: layout defaults to left-symmetric mdadm: layout defaults to left-symmetric mdadm: size set to 1465134912K Segmentation fault # Message from syslogd@linux-ynag at Nov 24 10:07:59 ... kernel:[ 115.091004] general protection fault: 0000 [#1] PREEMPT SMP Message from syslogd@linux-ynag at Nov 24 10:07:59 ... kernel:[ 115.091006] last sysfs file: /sys/devices/pci0000:00/0000:00:11.0/host1/target1:0:0/1:0:0:0/model Message from syslogd@linux-ynag at Nov 24 10:07:59 ... kernel:[ 115.091071] Stack: Message from syslogd@linux-ynag at Nov 24 10:07:59 ... kernel:[ 115.091078] Call Trace: Message from syslogd@linux-ynag at Nov 24 10:07:59 ... kernel:[ 115.091144] 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 NNov 24 10:07:59 linux-ynag kernel: [ 114.895792] md: bind<sda1> Nov 24 10:07:59 linux-ynag kernel: [ 114.897194] md: bind<sdb1> Nov 24 10:07:59 linux-ynag kernel: [ 114.897457] md: bind<sdc1> Nov 24 10:07:59 linux-ynag kernel: [ 114.922021] async_tx: api initialized (async) Nov 24 10:07:59 linux-ynag kernel: [ 114.938214] xor: automatically using best checksumming function: generic_sse Nov 24 10:07:59 linux-ynag kernel: [ 114.943419] generic_sse: 13760.000 MB/sec Nov 24 10:07:59 linux-ynag kernel: [ 114.943420] xor: using function: generic_sse (13760.000 MB/sec) Nov 24 10:07:59 linux-ynag kernel: [ 114.966438] raid6: int64x1 2851 MB/s Nov 24 10:07:59 linux-ynag kernel: [ 114.983422] raid6: int64x2 3902 MB/s Nov 24 10:07:59 linux-ynag kernel: [ 115.000428] raid6: int64x4 3007 MB/s Nov 24 10:07:59 linux-ynag kernel: [ 115.017423] raid6: int64x8 2742 MB/s Nov 24 10:07:59 linux-ynag kernel: [ 115.034428] raid6: sse2x1 4488 MB/s Nov 24 10:07:59 linux-ynag kernel: [ 115.051420] raid6: sse2x2 7250 MB/s Nov 24 10:07:59 linux-ynag kernel: [ 115.068423] raid6: sse2x4 8652 MB/s Nov 24 10:07:59 linux-ynag kernel: [ 115.068424] raid6: using algorithm sse2x4 (8652 MB/s) Nov 24 10:07:59 linux-ynag kernel: [ 115.090809] md: raid6 personality registered for level 6 Nov 24 10:07:59 linux-ynag kernel: [ 115.090810] md: raid5 personality registered for level 5 Nov 24 10:07:59 linux-ynag kernel: [ 115.090811] md: raid4 personality registered for level 4 Nov 24 10:07:59 linux-ynag kernel: [ 115.091004] general protection fault: 0000 [#1] PREEMPT SMP Nov 24 10:07:59 linux-ynag kernel: [ 115.091006] last sysfs file: /sys/devices/pci0000:00/0000:00:11.0/host1/target1:0:0/1:0:0:0/model Nov 24 10:07:59 linux-ynag kernel: [ 115.091008] CPU 3 Nov 24 10:07:59 linux-ynag kernel: [ 115.091009] Modules linked in: raid456 async_raid6_recov async_pq raid6_pq async_xor xor async_memcpy async_tx 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_NOTRACK ipt_REJECT xt_tcpudp xt_multiport 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 snd_hda_intel snd_hda_codec snd_hwdep edac_core snd_pcm pcspkr edac_mce_amd asus_atk0110 k10temp joydev ohci1394 i2c_piix4 snd_timer sg sky2 snd serio_raw soundcore wmi snd_page_alloc xhci_hcd ieee1394 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 24 10:07:59 linux-ynag kernel: [ 115.091041] Nov 24 10:07:59 linux-ynag kernel: [ 115.091047] Pid: 7341, comm: mdadm Not tainted 2.6.34.7-0.5-desktop #1 Crosshair IV Formula/System Product Name Nov 24 10:07:59 linux-ynag kernel: [ 115.091049] RIP: 0010:[<ffffffff81077078>] [<ffffffff81077078>] raw_notifier_chain_register+0x18/0x40 Nov 24 10:07:59 linux-ynag kernel: [ 115.091055] RSP: 0018:ffff88022d6a3c00 EFLAGS: 00010286 Nov 24 10:07:59 linux-ynag kernel: [ 115.091056] RAX: 8b4c08246c8b4824 RBX: ffff88022e96ed20 RCX: 0000000000000006 Nov 24 10:07:59 linux-ynag kernel: [ 115.091057] RDX: 0000000000000000 RSI: ffff88022e96ed20 RDI: ffffffffa049c3f8 Nov 24 10:07:59 linux-ynag kernel: [ 115.091058] RBP: ffffffff81b197a0 R08: ffffffff81b197e0 R09: 0000000000000200 Nov 24 10:07:59 linux-ynag kernel: [ 115.091060] R10: ffff88022be18800 R11: 0000000000000010 R12: 0000000000000200 Nov 24 10:07:59 linux-ynag kernel: [ 115.091061] R13: ffff88022e96ec00 R14: 0000000000000003 R15: ffff88022b290000 Nov 24 10:07:59 linux-ynag kernel: [ 115.091063] FS: 00007f805b92a700(0000) GS:ffff880001ec0000(0000) knlGS:0000000000000000 Nov 24 10:07:59 linux-ynag kernel: [ 115.091064] CS: 0010 DS: 0000 ES: 0000 CR0: 000000008005003b Nov 24 10:07:59 linux-ynag kernel: [ 115.091065] CR2: 00007f3652966000 CR3: 000000022b928000 CR4: 00000000000006e0 Nov 24 10:07:59 linux-ynag kernel: [ 115.091067] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 Nov 24 10:07:59 linux-ynag kernel: [ 115.091068] DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400 Nov 24 10:07:59 linux-ynag kernel: [ 115.091070] Process mdadm (pid: 7341, threadinfo ffff88022d6a2000, task ffff8801d6fea680) Nov 24 10:07:59 linux-ynag kernel: [ 115.091071] Stack: Nov 24 10:07:59 linux-ynag kernel: [ 115.091072] ffffffff8148ddc8 ffff88022e96ec00 ffffffffa04df5c1 ffff88022e96ec00 Nov 24 10:07:59 linux-ynag kernel: [ 115.091074] <0> ffff88022e6f0000 0000000000000003 ffffffffa04e3573 0000000000000001 Nov 24 10:07:59 linux-ynag kernel: [ 115.091076] <0> ffff88022fc22440 0000000000000001 0000000000000001 ffffffff81373fff Nov 24 10:07:59 linux-ynag kernel: [ 115.091078] Call Trace: Nov 24 10:07:59 linux-ynag kernel: [ 115.091085] [<ffffffff8148ddc8>] register_cpu_notifier+0x18/0x30 Nov 24 10:07:59 linux-ynag kernel: [ 115.091090] [<ffffffffa04df5c1>] raid5_alloc_percpu+0xe1/0x110 [raid456] Nov 24 10:07:59 linux-ynag kernel: [ 115.091102] [<ffffffffa04e3573>] setup_conf+0x203/0x640 [raid456] Nov 24 10:07:59 linux-ynag kernel: [ 115.091109] [<ffffffffa04e402e>] run+0x47e/0x7c0 [raid456] Nov 24 10:07:59 linux-ynag kernel: [ 115.091115] [<ffffffff8137430c>] do_md_run+0x3dc/0x830 Nov 24 10:07:59 linux-ynag kernel: [ 115.091119] [<ffffffff81375ec1>] md_ioctl+0x581/0x6a0 Nov 24 10:07:59 linux-ynag kernel: [ 115.091123] [<ffffffff8121fd6d>] blkdev_ioctl+0x20d/0x7b0 Nov 24 10:07:59 linux-ynag kernel: [ 115.091127] [<ffffffff8115328c>] block_ioctl+0x3c/0x50 Nov 24 10:07:59 linux-ynag kernel: [ 115.091130] [<ffffffff81134d99>] vfs_ioctl+0x39/0xc0 Nov 24 10:07:59 linux-ynag kernel: [ 115.091132] [<ffffffff81135330>] do_vfs_ioctl+0x70/0x3d0 Nov 24 10:07:59 linux-ynag kernel: [ 115.091135] [<ffffffff81135710>] sys_ioctl+0x80/0xa0 Nov 24 10:07:59 linux-ynag kernel: [ 115.091139] [<ffffffff81002ffb>] system_call_fastpath+0x16/0x1b Nov 24 10:07:59 linux-ynag kernel: [ 115.091143] [<00007f805b492e87>] 0x7f805b492e87 Nov 24 10:07:59 linux-ynag kernel: [ 115.091144] 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 24 10:07:59 linux-ynag kernel: [ 115.091159] RIP [<ffffffff81077078>] raw_notifier_chain_register+0x18/0x40 Nov 24 10:07:59 linux-ynag kernel: [ 115.091161] RSP <ffff88022d6a3c00> Nov 24 10:07:59 linux-ynag kernel: [ 115.091163] ---[ end trace 2100e01820c091a2 ]--- It is also the same with the shutdown hanging at unmount filesystems issue, and also the powernow-k8 firmware bug that I listed before. Hope this helps. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=655215 https://bugzilla.novell.com/show_bug.cgi?id=655215#c5 --- Comment #5 from Neil Brown <nfbrown@novell.com> 2010-11-24 00:17:04 UTC --- Yes, it helps. The problem is the powernow-k8 module. It registers a cpu notifier before printing int "Firmware Bug" message, and then fails, but doesn't clean up properly. So the cpu notifier is still registered, but the memory holding it gets used for something else. You can easily check this by removing (or moving to somewhere safe) the powernow-k8.ko module. e.g. mv /lib/modules/2.6.3*/kernel/arch/x86/kernel/cpu/cpufreq/powernow-k8.ko /root or something like that. Then reboot. There is probably a way to blacklist this module in /etc/modprobe.d Possibly echo blacklist powernow-k8 > /etc/modprobe.d/no-powernow.conf would do it, but I'm not certain. I'll see what I can discover about fixing the kernel. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=655215 https://bugzilla.novell.com/show_bug.cgi?id=655215#c6 --- Comment #6 from laughing man <laughing_man77@hotmail.com> 2010-11-24 02:48:36 UTC --- Did a bit of googling, and was able to resolve the issue by turning on cool 'n' quiet in the bios. that made the _pss table available to the kernel. Now system performs shutdown correctly, boots up without firmware bug warning, and what's more: # mdadm --create --verbose /dev/md0 --level=5 --raid-devices=3 /dev/sda1 /dev/sdb1 /dev/sdc1 mdadm: layout defaults to left-symmetric mdadm: chunk size defaults to 64K mdadm: layout defaults to left-symmetric mdadm: /dev/sda1 appears to be part of a raid array: level=raid5 devices=3 ctime=Wed Nov 24 10:07:59 2010 mdadm: layout defaults to left-symmetric mdadm: /dev/sdb1 appears to be part of a raid array: level=raid5 devices=3 ctime=Wed Nov 24 10:07:59 2010 mdadm: layout defaults to left-symmetric mdadm: /dev/sdc1 appears to be part of a raid array: level=raid5 devices=3 ctime=Wed Nov 24 10:07:59 2010 mdadm: size set to 1465134912K Continue creating array? y mdadm: array /dev/md0 started. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=655215 https://bugzilla.novell.com/show_bug.cgi?id=655215#c7 --- Comment #7 from laughing man <laughing_man77@hotmail.com> 2010-11-24 02:52:36 UTC --- Thanks a lot for the help. If there's anything else I can do, let me know. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=655215 https://bugzilla.novell.com/show_bug.cgi?id=655215#c8 Neil Brown <nfbrown@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |RESOLVED InfoProvider|laughing_man77@hotmail.com | Resolution| |FIXED --- Comment #8 from Neil Brown <nfbrown@novell.com> 2010-11-24 04:36:06 UTC --- Thanks. That confirms the problem analysis that the bug as in the powernow-k8 driver. I have sent a patch upstream and committed a patch for future maintenance releases for the openSUSE-11.3 kernel. This problem does not affect SLES11-SP1 or earlier kernels, so we are done. Thanks for the report and confirmation of a fix. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=655215 https://bugzilla.novell.com/show_bug.cgi?id=655215#c9 Swamp Workflow Management <swamp@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status Whiteboard| |maint:released:11.3:37798 --- Comment #9 from Swamp Workflow Management <swamp@suse.com> 2011-01-03 08:31:54 UTC --- Update released for: kernel-debug, kernel-debug-base, kernel-debug-base-debuginfo, kernel-debug-debuginfo, kernel-debug-debugsource, kernel-debug-devel, kernel-debug-devel-debuginfo, kernel-default, kernel-default-base, kernel-default-base-debuginfo, kernel-default-debuginfo, kernel-default-debugsource, kernel-default-devel, kernel-default-devel-debuginfo, kernel-desktop, kernel-desktop-base, kernel-desktop-base-debuginfo, kernel-desktop-debuginfo, kernel-desktop-debugsource, kernel-desktop-devel, kernel-desktop-devel-debuginfo, kernel-devel, kernel-ec2, kernel-ec2-base, kernel-ec2-base-debuginfo, kernel-ec2-debuginfo, kernel-ec2-debugsource, kernel-ec2-devel, kernel-ec2-devel-debuginfo, kernel-ec2-extra, kernel-ec2-extra-debuginfo, kernel-pae, kernel-pae-base, kernel-pae-base-debuginfo, kernel-pae-debuginfo, kernel-pae-debugsource, kernel-pae-devel, kernel-pae-devel-debuginfo, kernel-source, kernel-source-vanilla, kernel-syms, kernel-trace, kernel-trace-base, kernel-trace-base-debuginfo, kernel-trace-debuginfo, kernel-trace-debugsource, kernel-trace-devel, kernel-trace-devel-debuginfo, kernel-vanilla, kernel-vanilla-base, kernel-vanilla-base-debuginfo, kernel-vanilla-debuginfo, kernel-vanilla-debugsource, kernel-vanilla-devel, kernel-vanilla-devel-debuginfo, kernel-vmi, kernel-vmi-base, kernel-vmi-base-debuginfo, kernel-vmi-debuginfo, kernel-vmi-debugsource, kernel-vmi-devel, kernel-vmi-devel-debuginfo, kernel-xen, kernel-xen-base, kernel-xen-base-debuginfo, kernel-xen-debuginfo, kernel-xen-debugsource, kernel-xen-devel, kernel-xen-devel-debuginfo, preload-kmp-default, preload-kmp-desktop Products: openSUSE 11.3 (debug, i586, x86_64) -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply＠novell.com