Confirmed, same problem here, Thunderbird 3 segfaults if you use an ldap
account.
--
[lucid] thunderbird on lucid 64 bit doesn't work: Segmentation fault (core
dumped)
https://bugs.launchpad.net/bugs/532128
You received this bug notification because you are a member of Ubuntu
Bugs, which is sub
Some comments for the new Ubuntu 9.04 version:
Placing module options in modprobe.d isn't supported any longer so the options
has no effect and once again the disk arrays appears broken after updating to
9.0.4. The easiest solution is to add libata.ignore_hpa=0 in your grub
configuration.
Examp
There was never a problem, a default value of a module option got
changed (libata ignore_hpa). I just missed to addd the original value
(ignore_hpa=0) to modprobe.d.
(What is the correct status for that bug report, I hope that invalid is
fine?)
** Changed in: linux-source-2.6.22 (Ubuntu)
S
I found a solution for my initial problem, see
http://ubuntuforums.org/showthread.php?p=4859992.
In fact, there was never a problem for me, I just missed the module
option. :)
--
Cannot start from dmraid device anymore
https://bugs.launchpad.net/bugs/141435
You received this bug notification bec
Could you explain in detail what you changed where? My only solution was
so far to rebuild the kernel with static int ata_ignore_hpa = 0; as
decribed above.
--
Cannot start from dmraid device anymore
https://bugs.launchpad.net/bugs/141435
You received this bug notification because you are a membe
ups, the line numbers are still from the diff file and not from the real
diff. So please don't apply this patch directly...
--
Cannot start from dmraid device anymore
https://bugs.launchpad.net/bugs/141435
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bu
Yes, I can confirm that:
linux-source-2.6.22 (2.6.22-11.33) gutsy; urgency=low
[Ben Collins]
* libata: Default to hpa being overridden
broke the kernel for us. I did a custom kernel build from the latest
ubuntu linux-source-2.6.22 (2.6.22-12.39) with the default configuration
and the proble
mmh, I'm not sure. I haven't installed dmsetup at all (and certainly
wont install it now :) ). The new updates of libdevmapper and udev
didn't broke my 11.32 kernel (but didn't help the 12.39 kernel to do a
good startup either). My situation hasn't changed yesterday.
--
Cannot start from dmraid d
I got the message that isw device is broken, not unknown, so not sure.
But the rest looks indeed identical, I'm using an Intel ICH9 fake raid
to.
(Btw, I wrote two comments earlier that the problems started with 11.34,
what I meant to say is that it started when I updated directly from
11.32 to 11
** Changed in: linux-source-2.6.22 (Ubuntu)
Sourcepackagename: None => linux-source-2.6.22
--
Cannot start from dmraid device anymore
https://bugs.launchpad.net/bugs/141435
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu
I just reverted the kernel to version 2.6.22-11.32. Now I can do a
normal startup again. As I remember the problems started with version
11.34, thus some change between these two version screwed it up... Can
somebody point me to the exact change which could break a startup from a
dmraid partition?
Ah, this isn't new:
https://bugs.launchpad.net/ubuntu/+source/linux-source-2.6.20/+bug/110245
--
Cannot start from dmraid device anymore
https://bugs.launchpad.net/bugs/141435
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubu
I just updated to kernel version 2.6.22-12.36-generic (boot from lice cd
and chroot into my dmraid partition), but nothing changes during the
next real startup :(
--
Cannot start from dmraid device anymore
https://bugs.launchpad.net/bugs/141435
You received this bug notification because you are a
Public bug reported:
Since one of the last (kernel ) updates I cannot start my Gutsy anymore.
The message I got is:
device-mapper: ioctl: 4.11.0-ioctl (2006-10-12) initialised: [EMAIL PROTECTED]
ERROR: isw device for volume "Volume0" broken on /dev/sdb in RAID set
"isw_dfgjhjfjai_Volume0"
ERROR:
14 matches
Mail list logo
