[Bug 375213] Re: New upstream release 0.5.0d
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 backport is provided for jaunty, and possibly intrepid. I for one think this is kinda outrageous... please backport to jaunty at least. -- New upstream release 0.5.0d https://bugs.launchpad.net/bugs/375213 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.com/mailman/listinfo/ubuntu-bugs
[Bug 352673] Re: plasma cpu usage 40% and more
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: Unknown Status: Unknown ** Changed in: kdebase-workspace (Ubuntu) Status: New = Fix Released -- plasma cpu usage 40% and more https://bugs.launchpad.net/bugs/352673 You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to kdebase-workspace in ubuntu. -- kubuntu-bugs mailing list kubuntu-b...@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 352197] Re: ata timeout exception with ahci libata driver (was with 2.6.28-11, but i confirmed it affewcts previous kernels too)
** 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-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 system
unusable. Sounds much more serious than
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/343919, and
different, in as much as it is not an ext4 fs that I am aware of, it is
not an nvidia disk controller, and these errors are many more than ~10,
and trivially easy to reproduce (it happens every time, from the first
disk-reads onward)
dmesg error message:
[ 75.816051] ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6
frozen
[ 75.816135] ata1.00: cmd ca/00:10:50:27:1e/00:00:00:00:00/e9 tag 0 dma
8192 out
[ 75.816137] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4
(timeout)
[ 75.816275] ata1.00: status: { DRDY }
[ 75.816337] ata1: hard resetting link
[ 76.804036] ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
[ 76.806704] ata1.00: configured for UDMA/100
[ 76.806715] ata1: EH complete
- Note that booting 2.6.27 does not produce any disk error. smartctl
- reports no disk health problems, either.
+ Note that booting 2.6.27 does not produce any disk error. smartctl reports no
disk health problems, either.
+ [update] the bug is present in previouos versions too, and it only appears
when using the ahci dirver for libata (see lspci -vv output below).
lspci -vv for IDE controllers:
00:1f.1 IDE interface: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family)
IDE Controller (rev 03) (prog-if 8a [Master SecP PriP])
Subsystem: Sony Corporation Device 81b9
Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR- FastB2B- DisINTx-
Status: Cap- 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium TAbort-
TAbort- MAbort- SERR- PERR- INTx-
Latency: 0
Interrupt: pin B routed to IRQ 18
Region 0: I/O ports at 01f0 [size=8]
Region 1: I/O ports at 03f4 [size=1]
Region 2: I/O ports at 0170 [size=8]
Region 3: I/O ports at 0374 [size=1]
Region 4: I/O ports at 1880 [size=16]
Kernel driver in use: ata_piix
Kernel modules: ata_piix
00:1f.2 IDE interface: Intel Corporation 82801FBM (ICH6M) SATA Controller
(rev 03) (prog-if 8f [Master SecP SecO PriP PriO])
Subsystem: Sony Corporation Device 81ba
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=medium TAbort-
TAbort- MAbort- SERR- PERR- INTx-
Latency: 0
Interrupt: pin B routed to IRQ 18
Region 0: I/O ports at 18c0 [size=8]
Region 1: I/O ports at 18b8 [size=4]
Region 2: I/O ports at 18b0 [size=8]
Region 3: I/O ports at 1894 [size=4]
Region 4: I/O ports at 18a0 [size=16]
Region 5: Memory at
[Bug 352197] Re: ata timeout exception with ahci libata driver (was with 2.6.28-11, but i confirmed it affewcts previous kernels too)
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 2.6.27 kernels, as ahci is loaded as a module and can be blacklisted in /etc/modprobe.d/blacklist. Unfortunately, 2.6.28 kernels in ubuntu (haven't tested with debian again) do not load ahci (or any libata driver, for that matter) as modules, but are now built-in into the kernel, so my workaround is useless. Any help on how to disable ahci when it's built in (ie, force the kernel to use ata_piix anyway) would be greatly appreciated. note that i do not have any intention of recompiling the kernel :) If you need more information, please let me know. -- ata timeout exception with ahci libata driver (was with 2.6.28-11, but i confirmed it affewcts previous kernels too) https://bugs.launchpad.net/bugs/352197 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.com/mailman/listinfo/ubuntu-bugs
[Bug 57789] Re: Crossfading option causes skipping
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.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
Re: [Bug 352197] Re: ata timeout exception with linux 2.6.28-11
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 ones marked ok. I have experienced the same problem with all tested kernels from 2.6.27-7 and above. 2.- i have experienced the same problem with kubuntu hardy, intrepid and jaunty beta install disks, as well as debian lenny. 3.- the problem is completely erratic. sometimes it appears at boot, sometimes it appears on x startup, sometimes only after a few minutes after the session login. It seems to be related to high disk IO, but i could not be certain of this, ie i don't know if the problem appears with the machine idle. 4.- but most important of all, i have solved it, apparently: blacklisting ahci in /etc/modprobe.d/blacklist makes the problem go away, by forcing libata to use the ata_piix driver for all drives (im sure there must be a more elegant way of doing this, but after googling for days on how to disable ahci i gave up and just blacklisted the module to test it). Now, the strange part is that this configuration should be properly supported by ahci, as the ICH6M controller is thoroughly tested, and the Hitachi disk that was causing problems is not particularly esotheric... but i wouldn't know how to test this further, much less change ahci config params to see if i can get this drive on this controller to work (if theres any params that could make the disk behave). In any case, the bug (?) seems to be located in the AHCI module, and it seems to affect this HW configuration only, so i don't know if it makes any sense keepin it open. I'm willing to try anything suggested if it helps to isolate the issue. thanks for your time! On Mon, Apr 6, 2009 at 1:35 PM, Leann Ogasawara leann.ogasaw...@canonical.com wrote: ** Tags added: intrepid regression-release -- ata timeout exception with linux 2.6.28-11 https://bugs.launchpad.net/bugs/352197 You received this bug notification because you are a direct subscriber of the bug. -- entia non sunt multiplicanda praeter necessitatem -- ata timeout exception with linux 2.6.28-11 https://bugs.launchpad.net/bugs/352197 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.com/mailman/listinfo/ubuntu-bugs
[Bug 272527] Re: rkward: 'No (valid) plugins found', therefore no menu items
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 no comment from anyone with the power to fix the packaged version. this is very disappointing. -- rkward: 'No (valid) plugins found', therefore no menu items https://bugs.launchpad.net/bugs/272527 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.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 352197] Re: ata timeout exception with linux 2.6.28-11
Hello Leann: Thanks for your reply. I can now confirm that this bug, on this particular box, affects other kernels previous to 2.6.28. I am now experiencing the same behaviour in a Intrepid install with kernel 2.1.27.14. 2.6.27-7 - ok (intrepid) 2.6.27-11 - ok (intrepid) 2.6.27-14 - 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 leann.ogasaw...@canonical.com wrote: Hi Gorgonzola, Can you comment if any of the previous 2.6.28 Jaunty kernels exhibited this behavior? Care to give the upstream kernel a quick test as well. The Ubuntu kernel team has started packaging the upstream kernels - https://wiki.ubuntu.com/KernelMainlineBuilds . Thanks. ** Changed in: linux (Ubuntu) Importance: Undecided = High ** Changed in: linux (Ubuntu) Status: New = Triaged -- ata timeout exception with linux 2.6.28-11 https://bugs.launchpad.net/bugs/352197 You received this bug notification because you are a direct subscriber of the bug. -- entia non sunt multiplicanda praeter necessitatem -- ata timeout exception with linux 2.6.28-11 https://bugs.launchpad.net/bugs/352197 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.com/mailman/listinfo/ubuntu-bugs
[Bug 352197] [NEW] ata timeout exception with linux 2.6.28-11
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 system
unusable. Sounds much more serious than
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/343919, and
different, in as much as it is not an ext4 fs that I am aware of, it is
not an nvidia disk controller, and these errors are many more than ~10,
and trivially easy to reproduce (it happens every time, from the first
disk-reads onward)
dmesg error message:
[ 75.816051] ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
[ 75.816135] ata1.00: cmd ca/00:10:50:27:1e/00:00:00:00:00/e9 tag 0 dma 8192
out
[ 75.816137] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4
(timeout)
[ 75.816275] ata1.00: status: { DRDY }
[ 75.816337] ata1: hard resetting link
[ 76.804036] ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
[ 76.806704] ata1.00: configured for UDMA/100
[ 76.806715] ata1: EH complete
Note that booting 2.6.27 does not produce any disk error. smartctl
reports no disk health problems, either.
lspci -vv for IDE controllers:
00:1f.1 IDE interface: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family)
IDE Controller (rev 03) (prog-if 8a [Master SecP PriP])
Subsystem: Sony Corporation Device 81b9
Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR- FastB2B- DisINTx-
Status: Cap- 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium TAbort-
TAbort- MAbort- SERR- PERR- INTx-
Latency: 0
Interrupt: pin B routed to IRQ 18
Region 0: I/O ports at 01f0 [size=8]
Region 1: I/O ports at 03f4 [size=1]
Region 2: I/O ports at 0170 [size=8]
Region 3: I/O ports at 0374 [size=1]
Region 4: I/O ports at 1880 [size=16]
Kernel driver in use: ata_piix
Kernel modules: ata_piix
00:1f.2 IDE interface: Intel Corporation 82801FBM (ICH6M) SATA Controller (rev
03) (prog-if 8f [Master SecP SecO PriP PriO])
Subsystem: Sony Corporation Device 81ba
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=medium TAbort-
TAbort- MAbort- SERR- PERR- INTx-
Latency: 0
Interrupt: pin B routed to IRQ 18
Region 0: I/O ports at 18c0 [size=8]
Region 1: I/O ports at 18b8 [size=4]
Region 2: I/O ports at 18b0 [size=8]
Region 3: I/O ports at 1894 [size=4]
Region 4: I/O ports at 18a0 [size=16]
Region 5: Memory at 80004400 (32-bit, non-prefetchable) [size=1K]
Capabilities: access denied
Kernel driver in use: ata_piix
Kernel modules: ahci, ata_piix
** Affects: linux (Ubuntu)
Importance: Undecided
Status: New
--
ata timeout exception with linux 2.6.28-11
https://bugs.launchpad.net/bugs/352197
You received
[Bug 309989] Re: Game crash
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 account the presence of the cloaked unit that produced the first unit's move to fail. This produces an AI error that crashes the game. This bug has been reported as https://gna.org/bugs/?12252 It has been fixed in version 1.4.7, as carried by the jaunty repos. Please backport version 1.4.7 from jaunty to intrepid. -- Game crash https://bugs.launchpad.net/bugs/309989 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.com/mailman/listinfo/ubuntu-bugs
[Bug 61039] Re: No desktop entries
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. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 116996] Re: SATA disk is in PATA mode with kernel 2.6.20-16-generic (piix claiming SATA controller on ICH4/ICH5 boards)
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 at the core of the problem. I must say that i had higher hopes for the ubuntu support chain... it's been five days or so and we haven't moved an inch through the regular process, although it was clear form the start that it was reproduceable and critical. I thought debian and ubuntu were more alike in this respect, now i see that ubuntu has some catching up to do :) ps: incidentally, one would think that a bug with erratic behaviour is much harder to diagnose... kudos to the debian devs on that one! -- SATA disk is in PATA mode with kernel 2.6.20-16-generic (piix claiming SATA controller on ICH4/ICH5 boards) 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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 116996] Re: sata disk in ide mode with kernel 2.6.20-16-generic (ata_piix broken?)
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 timeouts. That leaves two options: 1.- it is the same problem, but the symptoms differ: if you have UUID references, the isue manifests itself as an IRQ timeout. If you have /dev/ references, the issue manifests itself as a resume image not found. 2.- They are two difernt beasts, one related to a bug in the SATA/PATA controller, other related to obsolete /dev/ references produced by the change in behaviour in disk recognition. Purely speculating here, though, i don't know a thing about how resume images are created, referenced or loaded, or why a reference problem could be related to a driver issur, but my guess is that 2 is more correct, at least form what i've see in my box, and form the fact that if you have the resume not found problem, you still seem to be able to boot, wich is not my case: my box hangs dead in those IRQ timeouts when i try to boot with 2.6.20.16. no press enter to boot for me. LarsBjerregaard : I have produced my lspci output and it is now posted in the survey as post #305. i'm bukharin in the ubuntu forums. -- 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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 116996] Re: sata disk in ide mode with kernel 2.6.20-16-generic (ata_piix broken?)
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 impossible to pass beyond grub stage1. I think no one has had that problem, everything seems to be related to the kernel load process, grub work just fine, independently of how the kernel chooses to call its drives, and of course, independently of how it chooses to communicate with them, as it gets its disk information form the BIOS, long before the kernel exists. As a matter of fact... what are the references in /boot/grub/device.map for? grub does not need them, right? who reads those? -- 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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 116996] Re: sata disk in ide mode with kernel 2.6.20-16-generic (ata_piix broken?)
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 updated ICH5 controller, the IRQ's no longer appear (even using dev references?). I have to see if i can confirm this with a BIOS update. I would generalize form the above that 1.- 'IRQ' and 'resume not found' are two different things, 2.- 'IRQ' affects only ICH4 and ICH5 chipsets with older BIOS'es, wich are *quite* common, ICH7 and ICH5 with new BIOS'es work fine. 3.- resume images are a problem with references not being updated after the kernel update. Since this is not *critical* for the kernel boot process, you can still boot by disregarding the resume and doing a clean boot (press enter to boot)... right? Unless i lost some piece of the puzzle around here... ps: i repeat, i have 0 experiencie with kernel things, this is just my take on the matter, i could be totally lost here. -- 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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 116996] Re: sata disk in ide mode with kernel 2.6.20-16-generic (ata_piix broken?)
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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 116996] Re: sata disk in ide mode with kernel 2.6.20-16-generic (ata_piix broken?)
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 these two different issues? @LarsBjerregaard: looks like you are right. i'm not at my box to right now to produce a lspci output, but i can confirm that my box has an ICH5 intel south bridge, on an ASUS p4p800. -- 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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 117314] Re: latest kernel(2.6.20-16.28) update gives boot problems
@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/117314 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-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 117314] Re: latest kernel(2.6.20-16.28) update gives boot problems
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 identified byt eh kernel. Some people have said that they got it to boot by changing the refeernce in menu.lst back to hd** or using uuid's. I can confirm that this does NOT work on my system, as i use only UUID's references for my boot images. The 2.6.20.16 still refuses to load and hangs right there. I can also confirm that this problem affects the normal bot mode as well as the recovery mode. 2.6.20.15 loads fine, no problems at all, using the exact same menu.lst and fstab files. Besides that particular problem, there are people reporting issues with third party drivers, X server not loading and wireless cards failing to work. Please bear in mind that these issues are all related to modified kernel modules, and DO NOT apply to the kernel itself. it is quite normal to ahve to reconfigure yor kernel modules if you have made changes, like installing propietary graphic or wifi drievers. This is NOT the place to report these. Please stay on topic in regards to the bug reported: kernel image fails to load and reports disk issues and DMA interrupts and recovery. ps: i would submit a copy of the boot log, but i don't know how to recover it or reproduce it outside tty1. sorry. -- latest kernel(2.6.20-16.28) update gives boot problems https://bugs.launchpad.net/bugs/117314 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-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 117314] Re: latest kernel(2.6.20-16.28) update gives boot problems
@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 critical aspect of the kernel, as disk recognition and handling wich prevents it from loading and hangs the machine. If your system hangs when loading X server the kernel has already booted and it's up and running. So it's a diferent kind of bug... aparently not in the kernel itself. :) greetings! -- latest kernel(2.6.20-16.28) update gives boot problems https://bugs.launchpad.net/bugs/117314 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-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
