The patch is in my bzr branch, waiting to be merged in to the ubuntu-
core-dev branch. I've also sent the patch to the upstream freedesktop
bug tracker: https://bugs.freedesktop.org/show_bug.cgi?id=21603
--
hald segfault when using a raid volume
https://bugs.launchpad.net/bugs/361689
You received
To the main Ubuntu repos or to your PPA?
--
hald segfault when using a raid volume
https://bugs.launchpad.net/bugs/361689
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://l
Now I understand it properly, I've re-written the patch, tested it and
sent upstream.
** Branch linked: lp:~chrisccoulson/hal/bug361689
** Changed in: hal (Ubuntu)
Status: In Progress => Triaged
--
hald segfault when using a raid volume
https://bugs.launchpad.net/bugs/361689
You received
** Changed in: hal
Status: Unknown => Confirmed
--
hald segfault when using a raid volume
https://bugs.launchpad.net/bugs/361689
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
** Bug watch added: freedesktop.org Bugzilla #21603
https://bugs.freedesktop.org/show_bug.cgi?id=21603
** Also affects: hal via
https://bugs.freedesktop.org/show_bug.cgi?id=21603
Importance: Unknown
Status: Unknown
--
hald segfault when using a raid volume
https://bugs.launchpad.
Thanks for your help mobrien118 and Russell (who also contacted me
privately with some help). I've managed to recreate the crash now.
** Changed in: hal (Ubuntu)
Status: Confirmed => In Progress
** Changed in: hal (Ubuntu)
Assignee: (unassigned) => Chris Coulson (chrisccoulson)
--
h
I think I can get you started.
I mean, the first step to creating a RAID volume is to think it out.
Where do you need redundancy? Where do you need speed? Then map out your
partitions (especially if you have different sized disks).
Remember that RAID will cause a slight (in the case of RAID0 or R
I've not had much time to look any further at this, and I haven't
proposed my patch as a fix yet because I don't know if it is the right
way to fix it. What I need to do really is send this bug report
upstream, and also have a play around with a mdraid setup myself, but I
don't have a clue how to s
Mobrien118, I agree that there should be some consideration of its
importance. Maybe it isn't that big of a deal since few people have raid
sets on their computers. It cost me several hours of rebooting and
googling before I thought to boot into recovery console, install openssh
and then log in wit
FYI, it looks like Chris's PPA packages fixed it, though.
Thank goodness! If I had been remote from this machine (which I will be
for the next few months) it would have been a nightmare!
--
hald segfault when using a raid volume
https://bugs.launchpad.net/bugs/361689
You received this bug notifi
How is it possible that this bug is only listed as "Medium"
importance?!?!?
I discovered what I think is this bug when I upgraded my system using
system update. Upon a later reboot I found that I had no access to the
system whatsoever. After trying multiple things to get back in from the
root reco
Chris's HAL builds helped for me too. I think that the bug status should
be 'In progress' instead of 'Incomplete'.
--
hald segfault when using a raid volume
https://bugs.launchpad.net/bugs/361689
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ub
I can confirm this when using a RAID 10 array. Chris's HAL builds also
fixed the problem for me.
** Attachment added: "lshal.log"
http://launchpadlibrarian.net/26144390/lshal.log
--
hald segfault when using a raid volume
https://bugs.launchpad.net/bugs/361689
You received this bug notificatio
One more: I also used the hald supplied by Chris and it fixed it. Same
symptom - md's causing hal to crash.
--
hald segfault when using a raid volume
https://bugs.launchpad.net/bugs/361689
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Also used the hald supplied by Chris and the keyboard and mouse work
again.
--
hald segfault when using a raid volume
https://bugs.launchpad.net/bugs/361689
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubu
Hi,
I upgraded today from Intrepid to Jaunty, and had the same problem with
no mouse/keyboard in X, and a message in system log about a segfault
with HAL. I am using software raid.
I downloaded and installed the package supplied by Chris and it works. I
hope this patch will be applied to the offi
Works for me too. Good work, many thanks! :)
--
hald segfault when using a raid volume
https://bugs.launchpad.net/bugs/361689
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
Here's my lshal.log. As I said, your updated package is working for me
(RAID1)
I hope this helps.
** Attachment added: "lshal.log"
http://launchpadlibrarian.net/25789432/lshal.log
--
hald segfault when using a raid volume
https://bugs.launchpad.net/bugs/361689
You received this bug notifica
I have no output when assembling my array.
--
hald segfault when using a raid volume
https://bugs.launchpad.net/bugs/361689
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:/
Would you mind running "lshal -m", assembling your array and then
posting any output?
Thanks
--
hald segfault when using a raid volume
https://bugs.launchpad.net/bugs/361689
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bug
The result of lshal is the same before and after the raid array.
--
hald segfault when using a raid volume
https://bugs.launchpad.net/bugs/361689
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@li
Thanks Noumayos. That was before you assembled your raid array though
wasn't it?
--
hald segfault when using a raid volume
https://bugs.launchpad.net/bugs/361689
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing lis
Please find the log attached.
** Attachment added: "lshal.log"
http://launchpadlibrarian.net/25665774/lshal.log
--
hald segfault when using a raid volume
https://bugs.launchpad.net/bugs/361689
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to U
If you can provide the output, then it would be appreciated (from both
kernels).
--
hald segfault when using a raid volume
https://bugs.launchpad.net/bugs/361689
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing lis
Your patch is working for me.
I'll leave it to the original poster to post his lshal.log unless you'd
like mine as well.
This bug only manifested on 2.6.28-11 - booting 2.6.27-11 on Jaunty beta
was fine.
--
hald segfault when using a raid volume
https://bugs.launchpad.net/bugs/361689
You receiv
Thanks. I don't know if my patch is the right way to fix it. With my
build, could you also please run "lshal > lshal.log" after assembling
the raid volume, and attaching "lshal.log" to the bug report. Once that
is done, I will send all this upstream.
Thanks
** Changed in: hal (Ubuntu)
Importan
Your build seems to work.
** Attachment added: "hald-chriscoulson.log"
http://launchpadlibrarian.net/25592252/hald-chriscoulson.log
--
hald segfault when using a raid volume
https://bugs.launchpad.net/bugs/361689
You received this bug notification because you are a member of Ubuntu
Bugs, whic
Please find attached the requested log
** Attachment added: "hald.log"
http://launchpadlibrarian.net/25591739/hald.log
--
hald segfault when using a raid volume
https://bugs.launchpad.net/bugs/361689
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscrib
** Summary changed:
- hald segfault when using a raid 0 volume
+ hald segfault when using a raid volume
--
hald segfault when using a raid volume
https://bugs.launchpad.net/bugs/361689
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
29 matches
Mail list logo
