This bug needs to be reopened.
Closing it because of some hardware issue when affected hardware clearly could
be driven properly in earlier versions is a cop out.
The reality is, users are affected by the software upgrade adversely. Blaming
it on the hardware is silly. Even if that hardware
Public bug reported:
Binary package hint: criticalmass
criticalmass tries to start (fullscreen), gets my screens (dual-screen setup)
into 640x480 video mode, and then crashes and burns with the following error:
criticalmass: radeon_mipmap_tree.c:420: migrate_image_to_miptree:
Assertion
Startup log.
** Attachment added: critter_output.txt
http://launchpadlibrarian.net/53123421/critter_output.txt
--
Criticalmass crashes at start with the error: radeon_mipmap_tree.c:420:
migrate_image_to_miptree: Assertion mt-mesaFormat == image-base.TexFormat'
failed.
I've added the line: set resolutions = 1280x960,1152x864,1024x768 to
the configuration file in ~/.critter/critter_config.txt before
generating that startup log. That didn't actually fix the crash, but it
did prevent criticalmass from putting my screen in 640x480 first.
--
Criticalmass crashes at
apport information
** Tags added: apport-collected
** Description changed:
Binary package hint: criticalmass
criticalmass tries to start (fullscreen), gets my screens (dual-screen setup)
into 640x480 video mode, and then crashes and burns with the following error:
criticalmass:
apport information
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/53124235/Dependencies.txt
--
Criticalmass crashes at start with the error: radeon_mipmap_tree.c:420:
migrate_image_to_miptree: Assertion mt-mesaFormat == image-base.TexFormat'
failed.
karmic. Me too ;-)
--
gnome-session keeps respawning nautilus when no desktop is drawed
https://bugs.launchpad.net/bugs/325973
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
Public bug reported:
Binary package hint: bootchart
When the bootchart is generated a symbolic link to the latest generated
bootchart in the target directory would be rather nice to have.
This can be accomplished by changing the relevant bits in /etc/init.d
/stop-bootchart into:
---
** Description changed:
Binary package hint: bootchart
When the bootchart is generated a symbolic link to the latest generated
bootchart in the target directory would be rather nice to have.
This can be accomplished by changing the relevant bits in /etc/init.d
/stop-bootchart
On Mon, Apr 27, 2009 at 3:02 PM, Scott James Remnant
sc...@canonical.com wrote:
I'm not sure that I see the point of this.
Oh, it's fairly simple: I'm tweaking a server a bit and want to have
the latest boot posted on a static webpage somewhere.
Since the 'latest boot' is not statically known
On Mon, Apr 27, 2009 at 4:41 PM, Scott James Remnant
sc...@canonical.com wrote:
On Mon, 2009-04-27 at 14:25 +, Randakar wrote:
Oh, it's fairly simple: I'm tweaking a server a bit and want to have
the latest boot posted on a static webpage somewhere.
Bootcharts don't mean anything
This affects Ubuntu 9.04 as well.
The comment OP is referring to can be found in a LKML thread here:
http://kerneltrap.org/mailarchive/linux-kernel/2008/11/20/4215134
Clearly this is a relatively harmless message - especially given the fact that
mainline doesn't even see it.
However, it
** Attachment added: fdisk.log
http://launchpadlibrarian.net/16054211/fdisk.log
--
Unable to mount IDE partition after Kernel upgrade 2.6.20 - 2.6.24 (PATA
driver)
https://bugs.launchpad.net/bugs/248738
You received this bug notification because you are a member of Ubuntu
Bugs, which is
** Attachment added: fstab
http://launchpadlibrarian.net/16054214/fstab
--
Unable to mount IDE partition after Kernel upgrade 2.6.20 - 2.6.24 (PATA
driver)
https://bugs.launchpad.net/bugs/248738
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
On Wed, Jul 16, 2008 at 1:44 AM, Chris Coulson
[EMAIL PROTECTED] wrote:
Thank you for taking the time to report this bug and helping to make
Ubuntu better. Unfortunately we can't fix it, because your description
does not yet have enough information.
Very well.
Please include the following
** Attachment added: lspci-vvnn.log
http://launchpadlibrarian.net/16054220/lspci-vvnn.log
--
Unable to mount IDE partition after Kernel upgrade 2.6.20 - 2.6.24 (PATA
driver)
https://bugs.launchpad.net/bugs/248738
You received this bug notification because you are a member of Ubuntu
Bugs,
On Wed, Jul 16, 2008 at 1:44 AM, Chris Coulson
[EMAIL PROTECTED] wrote:
Thank you for taking the time to report this bug and helping to make
Ubuntu better. Unfortunately we can't fix it, because your description
does not yet have enough information.
Very well.
Please include the following
Reply by email and reply in forum ftw .. ah well that's what you get for being
impatient.
--
Unable to mount IDE partition after Kernel upgrade 2.6.20 - 2.6.24 (PATA
driver)
https://bugs.launchpad.net/bugs/248738
You received this bug notification because you are a member of Ubuntu
Bugs,
Public bug reported:
After upgrading my dinky old firewall to Ubuntu 8.04 the kernel refuses to
mount the /boot partition. Instead I get an error message saying (quoting from
memory) Unable to mount: Already mounted or /dev/sda5 is in use).
Affected package: linux-image-2.6.24-19-server
** Attachment added: another crash dump
http://librarian.launchpad.net/5482239/_usr_bin_python.1000.crash
--
update-manager falls back to disttribution upgrade after python crashes in
apt-check, due to a segfault in pkgcache::VerIterator::Downloadable
https://launchpad.net/bugs/76530
--
That workaround probably should read 'remove linux-image-kdump OR set
#alternatives=false in /boot/grub/menu.list' ;-)
Nonetheless, good work. Thanks.
--
[patch] update-grub is broken
https://launchpad.net/bugs/73966
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
Public bug reported:
Logging in seems to be enough.
The update-notifier crashes, in the crash report it looks like python is
running /usr/lib/update-notifier/apt-check
** Affects: python-defaults (Ubuntu)
Importance: Undecided
Status: Unconfirmed
--
python crashes while running
Ben,
The new kernel did NOT fix this bug.
Running package version 2.6.19-7.11, tested it as follows:
modprobe i82365
BUG: soft lockup detected on CPU#0!
*hang*
--
[feisty][linux-image-2.6.19-7] PCMCIA bridge driver i82365 causes BUG: soft
lockup detected on CPU#0! on Asus motherboards
That teaches me to speak too soon ;-)
2.6.20 landed. Trying to reproduce there, yields:
---
[EMAIL PROTECTED]:~# modprobe i82365
FATAL: Error inserting i82365
(/lib/modules/2.6.20-2-generic/kernel/drivers/pcmcia/i82365.ko): No such device
---
As it should.
Consider this bug swatted.
--
Public bug reported:
Binary package hint: linux-source-2.6.20
When booting in 2.6.20, suddenly /var/log/messages is spammed with:
Dec 18 21:52:45 localhost kernel: [ 163.416320] Intel ISA PCIC probe: not
found.
Dec 18 21:52:45 localhost kernel: [ 163.435252] Intel ISA PCIC probe: not
** Attachment added: /var/log/messages (scroll to the end)
http://librarian.launchpad.net/5445612/messages.log.tar.bz2
--
[Feisty] Linux 2.6.20 spams 'Intel ISA PCIC probe: not found.' all over
/var/log/messages
https://launchpad.net/bugs/76341
--
ubuntu-bugs mailing list
** Attachment added: lspci
http://librarian.launchpad.net/5445615/lspci
--
[Feisty] Linux 2.6.20 spams 'Intel ISA PCIC probe: not found.' all over
/var/log/messages
https://launchpad.net/bugs/76341
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
I appear to be having similar problems. I turned on the 'desktop-effects' stuff
yesterday and it turns my machine into a brick after I login. I get some
interesting 'Xid' messages in syslog (attached).
I already had problems with the screensaver kicking in and hanging the
machine, and of late
Note that I am using a DFP device, as describe in that nv forum comment.
--
nvidia 1.0.9629 crashes X
https://launchpad.net/bugs/74146
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Bug disappears if I remove linux-image-kdump.
(!)
--
[Feisty] update-grub fails mysteriously on feisty
https://launchpad.net/bugs/73966
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
After some research I managed to get some output which should clarify matters:
[EMAIL PROTECTED]:~# sh -x `which update-grub` 2 update-grub.txt
** Attachment added: update-grub.txt
http://librarian.launchpad.net/5248147/update-grub.txt
** Summary changed:
- Postinst script fails running
S13 is pcmciautils alright, but S40 is S40networking. It doesn't sound like a
good idea to remove that to me.
But I'll try this.
--
[feisty] [linux-image-2.6.19-6] BUG: soft lockup detected on CPU#0!
https://launchpad.net/bugs/72895
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
Removed S13pcmciautils, and now it boots!
You were dead right on that one.
It also seems to me that the bug here is definitely in either that
i82365 PCMCIA bridge driver module, or in the code that attempts to find
PCMCIA devices.
My guess is the latter.
One of the things I noticed was that
I can now confirm that running '/etc/init.d/pcmciautils start' as root after
bootup hangs the kernel.
That script sources /etc/default/pcmciautils which lists what hardware
it thinks I have:
--
[EMAIL PROTECTED]:~# cat /etc/default/pcmciautils
# Defaults for PCMCIA (sourced by
Ok, 2.6.19-7 boots for me* so I consider this one resolved.
Please close this bug :-)
*) (with a workaround for
https://bugs.launchpad.net/distros/ubuntu/+source/linux-
source-2.6.19/+bug/72895)
--
linux-image-2.6.19-6 fails to find disks
https://launchpad.net/bugs/73177
--
ubuntu-bugs
** Summary changed:
- [feisty] [linux-image-2.6.19-6] BUG: soft lockup detected on CPU#0!
+ [feisty][linux-image-2.6.19-7] PCMCIA bridge driver i82365 causes BUG: soft
lockup detected on CPU#0! on Asus motherboards
--
[feisty][linux-image-2.6.19-7] PCMCIA bridge driver i82365 causes BUG: soft
Allcolor_g, can you try running a vanilla 2.6.19 kernel and then issuing the
modprobe by hand? I wonder if this affects upstream.
On paper all that is needed to trigger the bug would be:
modprobe pcmcia_core
modprobe i82365
--
[feisty][linux-image-2.6.19-7] PCMCIA bridge driver i82365
Public bug reported:
Binary package hint: grub
The 2.6.19-7 kernel package fails to run update-grub properly. Or perhaps
update-grub fails because somebody broke it ;-).
Both were updated to new versions today (grub version: 0.97-19ubuntu1)
The error message is this:
---
[EMAIL
menu.lst after running update-grub
Definitely no update of any kind ..
--
Postinst script fails running update-grub
https://launchpad.net/bugs/73966
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
** Attachment added: menu.lst
http://librarian.launchpad.net/5218052/menu.lst
--
Postinst script fails running update-grub
https://launchpad.net/bugs/73966
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
No such luck for me. Still getting the lockup on 2.6.19-7.
--
[feisty] [linux-image-2.6.19-6] BUG: soft lockup detected on CPU#0!
https://launchpad.net/bugs/72895
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
On 11/27/06, Ben Collins [EMAIL PROTECTED] wrote:
This has been fixed with an initramfs-tools update.
** Changed in: linux-source-2.6.19 (Ubuntu)
Status: Unconfirmed = Fix Released
Ok, the update landed this morning.
The good news is, I no longer see the problem occurring where the
I can confirm this one. Same thing happening on my box.
Hardware:
AMD Sempron Processor 3400+
Asus mobo K8VXSE
NVidia GeForce FX 5200
1Gb ram
No LVM
No TV card.
In all, pretty similar to the original reporter's hardware.
More importantly the lockup appears to occur directly after the kernel
Ok,
pci=noacpi and acpi=off don't fix the issue. Instead, 'acpi=off' turns
the soft lockup into a full-blown kernel panic.
Removing the nvidia stuff now. Not expecting much of it since the
'tainted' flag wasn't set during that kernel panic, suggesting that it
hadn't loaded yet.
Nonetheless ..
To continue this barrage of comments, I removed the nvidia binary driver
package before I made that trace as well - to no effect, obviously.
--
[feisty] [linux-image-2.6.19-6] BUG: soft lockup detected on CPU#0!
https://launchpad.net/bugs/72895
--
ubuntu-bugs mailing list
Alright, here comes a stack trace:
This trace appears right after it attempts to load the i82365 module.
(some kind of pcmcia bridge device, I gather.)
Be aware this was typed in by hand from a blurry photo, zeroes might be
8's and vice-versa especially near the bottom.
===
Correction, I spotted a typo in there ;-)
===
BUG: soft lockup detected on CPU#0!
[c01047b2] dump_trace+0x192/0x1c0
[c01047f8] show_trace_log_lvl+0x18/0x30
[c0104ecf] show_trace+0xf/0x20
[c0105035] dump_stack+0x15/0x20
[c01521eb] softlockup_tick+0x9b/0xe0
[c012e481]
Added a stack trace for the soft lockup problem to
https://bugs.launchpad.net/distros/ubuntu/+source/linux-source-2.6.19/+bug/72895
As for this bug, from looking at the kernel output it appears this bug
is fixed (looks like we manage to get through USB initialisation now),
though the suspicious
** Attachment added: lspci output
http://librarian.launchpad.net/5198097/lspci
--
[feisty] [linux-image-2.6.19-6] BUG: soft lockup detected on CPU#0!
https://launchpad.net/bugs/72895
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
On 11/27/06, Ben Collins [EMAIL PROTECTED] wrote:
This has been fixed with an initramfs-tools update.
** Changed in: linux-source-2.6.19 (Ubuntu)
Status: Unconfirmed = Fix Released
When does this update land?
As an aside, there is a usability issue here also - the splash screen
gets
Public bug reported:
Binary package hint: linux-source-2.6.19
Upgraded to Feisty today. Upgraded my kernel to 2.6.19-6 in the process.
Unfortunately that kernel version appears to not find any disks.
While booting in recovery mode everything goes fine up until where it
detects my USB hardware
Same problem here. Using binary nvidia drivers.
--
crash on exit
https://launchpad.net/bugs/59810
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Another crash output report..
--
xchat crashes frequently on quit
https://launchpad.net/bugs/57951
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
+1
All the same symptoms.
--
Azureus does not start
https://launchpad.net/bugs/57875
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
54 matches
Mail list logo
