could someone please backport this to jaunty (and possibly intrepid)?
the version carried by ubuntu repos is broken since intrepid, the
breakage was fixed upstream two versions and several months ago.
rkward has been broken for kubuntu users for 6 months now, and will
complete 12 months if no bac
There's a fix released upstream for kde 4.3 and 4.2 branches. see
https://bugs.kde.org/show_bug.cgi?id=190365
** Bug watch added: KDE Bug Tracking System #190365
http://bugs.kde.org/show_bug.cgi?id=190365
** Also affects: kdebase via
http://bugs.kde.org/show_bug.cgi?id=190365
Importance:
I updated the bug desc and title to reflect new findings. The issue is
definitely located in the AHCI driver, as per my previous comments, and
it affects all kernels tested (2.6.27-* and 2.6.28-* on intrepid, jaunty
beta, jaunty release and debian lenny up to now).
The workaround i used works for
** Summary changed:
- ata timeout exception with linux 2.6.28-11
+ ata timeout exception with ahci libata driver (was with 2.6.28-11, but i
confirmed it affewcts previous kernels too)
** Description changed:
Binary package hint: linux-image-2.6.28-11-generic
package: linux-image-2.6.28-1
i can confirm this on intrepid, kde 4.2, amarok 2.0.1
--
Crossfading option causes skipping
https://bugs.launchpad.net/bugs/57789
You received this bug notification because you are a member of Kubuntu
Bugs, which is subscribed to amarok in ubuntu.
--
kubuntu-bugs mailing list
kubuntu-b...@lists
I've had the chance to further examine this bug on my box. I've found
some things that could even make the bug report not applicable, but
i'd like to ask for advice on further testing:
1.- the problem is not exclusive to the kernel versions mentioned
above, it just hadn't appeared before on the on
I can confirm this on Intrepid. Rkward is unusable as packaged in the
repos. The solution proposed by fsando works, but it's an ugly hack to
circumvent a problem that should be a breeze to solve (it's just a path
issue!).
it's been almost six months since this bug was notified, and there has
been
-> ata timeout. (intrepid)
2.6.27-11 -> ok (jaunty)
2.6.28-11 -> ata timeout (jaunty)
So it would seem that the bug appeared somewhere between 2.6.27-11 and
2.6.27-14
The computer is a VAIO VGN-s560p, it has a 120 gb Hitachi driver.
On Wed, Apr 1, 2009 at 9:40 AM, Leann Ogasawara
wrote:
Public bug reported:
Binary package hint: linux-image-2.6.28-11-generic
package: linux-image-2.6.28-11
release: Jaunty Beta
latest version tested: 2.6.28-11.38
Trying to boot the new 2.6.28-11 kernel on Jaunty Beta results in many
ata timeout errors (like the one copied below) that make the syst
I can confirm this crash on kubuntu intrepid, usgin wesnoth 1.4.5.
This bug is caused by a cloaked unit. If AI unit enconunters a cloaked
unit in its path to the optimum destination and the movement fails, it
will attempt to make the very same move with the next available unit,
not taking into acc
sgt-puzzles does not create menu entries in kde. IS there any posibility
of porting the fix mentioned above to work in kde too?
--
No desktop entries
https://bugs.launchpad.net/bugs/61039
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
-
I'm with lars and philiip on this... the debian bug shows erratic
behaviour in regards to wich driver wins over the IRQ race. in this
version, we only seem to have a (wrong) consistent winner...
That does not deny the fact that there is a race going on between the
two drivers for IRQ 16, wich is a
oh, Gorgonzola == José Tomás Atria.
:)
--
sata disk in ide mode with kernel 2.6.20-16-generic (ata_piix broken?)
https://bugs.launchpad.net/bugs/116996
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
just to summarize:
I have an ICH5 chipset.
All my references are made through UUID's, not /dev (this includes
/etc/initramfs-tools/conf.d/resume, /etc/fstab and
/boot/grub/menu.lst)
I do not see any problems with resume images.
I get IRQ timeouts on my devices.
SItsofe reports that with an update
oh, and about the grub consequences:
i don't think they are a problem, as grub uses a completely different
way of referencing disks, (hd0,0) and the like... as far as i know, grub
does not make any difference betwen hd* or sd*, and i would think that
if those references got messed up, it would be
Sitsofe Wheeler :
from what i see in my setup, /etc/initramfs-tools/conf.d/resume references a
resume image by UUID. Fstab has only UUID references, and i do NOT have the
issue with resume images, at least not in that flavor. The boot log says
something about resume, but then produces the IRQ ti
@Sitsofe Wheeler
You are right, my problem is discussed in detail in bug#116996, this discussion
should concentrate on the X server and AGP related versions of the problem.
I'm off to #116996.
Good luck!
--
latest kernel(2.6.20-16.28) update gives boot problems
https://bugs.launchpad.net/bugs/1
it definitely is a more focused version of that one. But i still see two
problmes here (coul'd be that i don't know enough, i am total noob in
regards to kernel workings), one related to the resume images not being
found, and another related to the disks missing their IRQ calls.
Am i wrong or are
@Vajra
Yes, it should have been handled correctly, but there's no indication in your
problem reports that it is caused by a bug in the kernel itself.
i'm not saying that these are not important issues, i was just pointing
out that the original problem reported is related to a rather specific
and
There are various problems reported here.
One of them is related to the relabeling of storage devices form sd** to
hd**, wich produces a IRQ problem, and then an error message about DMA
interrupt and DMA interrupt recovery. This is all related to disks not
been found or not been properly identifie
20 matches
Mail list logo
