setting fix realased
** Changed in: mdadm (Ubuntu)
Status: Confirmed => Fix Released
--
mdadm SEGFAULT
https://bugs.launchpad.net/bugs/108553
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bug
This no longer happens for me, as of Jaunty release.
--
mdadm SEGFAULT
https://bugs.launchpad.net/bugs/108553
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.
I am seeing this as well under 9.04 as of this posting. The array seems
to be okay once the machine is booted, at which point the array no
longer reports itself as degraded.
$ dmesg | grep -B 2 -A 2 md
[3.687708] scsi6 : pata_jmicron
[3.687769] scsi7 : pata_jmicron
[3.688223] ata7: PA
Freshly installed & then updated to latest packages Intrepid 64 bit
(8.10) gives the same segfault error.
2x 1TB Seagate SATA-2 drives in hotswap bays that form a RAID-1
partition.
[0.00] Command line: root=/dev/md0 ro quiet splash
[0.00] Kernel command line: root=/dev/md0 ro quie
Seems to recover from the core:
$ lsb_release -rd
Description:Ubuntu 8.10
Release:8.10
$ sudo apt-cache policy mdadm
mdadm:
Installed: 2.6.7-3ubuntu8
Candidate: 2.6.7-3ubuntu8
Version table:
*** 2.6.7-3ubuntu8 0
500 http://archive.ubuntu.com intrepid/main Packages
I also get mdadm segfaults during boot, but my RAID1 array (2
partitions) works just fine for about a week now; /proc/mdstat shows no
errors
setup: Hardy with all updates as of Dec. 19th
/ is a normal partition
/data is /dev/md0 (RAID1)
> dmesg | grep md
[ 19.663740] md: linear personality
For what it is worth i'll add a me too.
Using mdadm RAID 1 (mirroring) a pair of drives both samsungs drives are
on seperate IDE channels (one on primary one on secondary). mdadm
configured under 8.04.
While its not nice to paste directly it heaps easier then having to open
attachements, so here
I just noticed - the segfault is not related to the raid 1 coming up or
not. Got it configured correctly and the segfault is still showing up
(although it does not seem to have any consequence!?)
--
mdadm SEGFAULT
https://bugs.launchpad.net/bugs/108553
You received this bug notification because y
Same here on 8.10.
I have 2 raids running - the root filesystem as raid 0 and a data mount as raid
1.
The raid 0 is coming up fine - just the raid 1 screws up.
Strangely starting it manually works like a charm!?
** Attachment added: "md output of dmesg"
http://launchpadlibrarian.net/20416185/m
I have this problem on 8.10 i386.
If you want context, read below, otherwise, this is the line in question:
Dec 10 22:04:23 daedalus kernel: [ 12.175868] mdadm[2342]: segfault at 4 ip
08062dbc sp bf8efc50 error 4 in mdadm[8048000+2c000]
Dec 10 22:04:23 daedalus kernel: [ 11.929983] Driver '
I have this problem on 8.10 amd64.
mdadm[2345]: segfault at 4 ip 00418d7d sp 7fff643653e0 error
4 in mdadm[40+2a000]
Most of the time i didn't notice until my system did not want to mount anything
during boot.
I could not resolve problem by stopping and starting the raid arrays i
Daniel T Chen wrote:
> Is this symptom still reproducible in 8.10 beta?
On the machine where I did see this I am now running 8.04, still
running mdadm, but haven't seen this issue for a while.
Erik
--
-
Erik de Castro Lopo
Is this symptom still reproducible in 8.10 beta?
** Changed in: mdadm (Ubuntu)
Status: New => Incomplete
--
mdadm SEGFAULT
https://bugs.launchpad.net/bugs/108553
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mai
Hi folks,
I'm the same problem in 3 boxes, 2 with amd64, and 1 with 32 bits kernels.
Every time I start, I get:
[ 26.898212] mdadm[2911]: segfault at 4 rip 41751c rsp 7fffee98ba50
error 4
Maybe is not related, but about 1 of 30 times, the system goes to busybox on
startup saying "md1 device b
I'm seeing this in current hardy too:
Jun 30 08:56:54 grace kernel: [ 135.750773] ACPI: PCI Interrupt
:00:1d.7[A] -> GSI 23 (level, low) -> IRQ 19
Jun 30 08:56:54 grace kernel: [ 135.750787] PCI: Setting latency timer of
device :00:1d.7 to 64
Jun 30 08:56:54 grace kernel: [ 135.750791
Hi there!
The bug is still here in the current hardy development version.
(but this kernel is really buggy for me
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/204064)
Attached my dmesg.
** Attachment added: "dmesg"
http://launchpadlibrarian.net/13029827/dmesg
--
mdadm SEGFAULT
http
mdadm segfaults for me using software RAID1 with this error:
mdadm[2888]: segfault at 0004 rip 0041724c rsp
7fff2e59e6a0 error 4
All seems fine in operation though...
--
mdadm SEGFAULT
https://bugs.launchpad.net/bugs/108553
You received this bug notification because you
I'm using raid1 (three separate volumes) and I get this:
[6.833270] mdadm[2473]: segfault at 0004 rip
0041724c rsp 7fffc4787940 error 4
Top part of my dmesg output:
[0.00] Linux version 2.6.19-4-generic-amd64 ([EMAIL PROTECTED]) (gcc
version 4.1.2 (Ubuntu 4.1
hi
i have nearly the same hardware and software setup and also gets this segfault
[ 27.274021] mdadm[2560]: segfault at 0004 rip
0041724c rsp 7fffc35d0730 error 4
--
mdadm SEGFAULT
https://bugs.launchpad.net/bugs/108553
You received this bug notification because you are
** Attachment added: "Full dmesg output"
http://librarian.launchpad.net/7380853/dmesg
--
mdadm SEGFAULT
https://bugs.launchpad.net/bugs/108553
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-
20 matches
Mail list logo
