[Bug 149665] Re: when returning from suspend my laptop tries to hibernate
** Attachment added: gpm.log.suspend.working.hardy-64bit http://launchpadlibrarian.net/12920478/gpm.log.suspend.working.hardy-64bit -- when returning from suspend my laptop tries to hibernate https://bugs.launchpad.net/bugs/149665 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 149665] Re: when returning from suspend my laptop tries to hibernate
** Attachment added: dmesg.suspend.hibernate.failing.gutsy-64bit http://launchpadlibrarian.net/12920476/dmesg.suspend.hibernate.failing.gutsy-64bit -- when returning from suspend my laptop tries to hibernate https://bugs.launchpad.net/bugs/149665 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 149665] Re: when returning from suspend my laptop tries to hibernate
** Attachment added: gpm.log.suspend.hibernate-disabled.failing.gutsy-64bit http://launchpadlibrarian.net/12920471/gpm.log.suspend.hibernate-disabled.failing.gutsy-64bit -- when returning from suspend my laptop tries to hibernate https://bugs.launchpad.net/bugs/149665 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 149665] Re: when returning from suspend my laptop tries to hibernate
Ok, I just reread this thread and need to state that I personally have no problems with the swap file. When auto-suspending on Gutsy, my PC hibernates after coming out of that suspendstate, and after restarting, it will correctly come out of hibernation. Today I have tried out the suspend functionality in Hardy 64bit and I did not have any problems. However, in Gutsy I do still have. It looks like GPM has updated/corrected some bugs upstream and those are available for Hardy now. ==GPM verbose== On Linux ***.lan 2.6.22-14-generic #1 SMP Tue Feb 12 02:46:46 UTC 2008 x86_64 GNU/Linux, Gutsy. Suspend AND Hibernate always fails, according to GPM verbose, but in reality it works. Somehow Gutsy's GPM doesn' t record correctly that Suspend did not fail, and therefore moves into hibernation mode, and even that fails when you come out of it according to the log. If you disable hibernation in gconf /apps/gnome-power-manager/general/can_hibernate , and disable the error messages you can use GPM without effective problems, GPM just gives a bunch of errors when returning out of suspend, but the user won' t see them. Relevant sections out of the GPM logs on Gutsy 64bit, NVIDIA 169.12 64bit from Nvidia's site (Gutsy's version did always restart X when coming out of hibernation, so I couldn't get the logs). (Note, the errrors are false, since the suspend did work correctly) gpm_control_suspend] gpm-control.c:451 (12:38:04): emitting sleep-failure [..] [gpm_notify_create] gpm-notify.c:124 (12:38:04): libnotify: Power Manager : Your computer failed to suspend. [..] [idle_do_sleep] gpm-manager.c:736 (12:38:04):cannot suspend, so trying hibernate [..] [gpm_control_hibernate] gpm-control.c:528 (12:41:48):emitting sleep-failure [..] [gpm_notify_create] gpm-notify.c:124 (12:41:48): libnotify: Power Manager : Your computer failed to hibernate. [..] [idle_do_sleep] gpm-manager.c:739 (12:41:48):cannot suspend or hibernate! It also didn't matter if I returned from suspend in 5 seconds or 1 min. ** Attachment added: gpm.log.suspend.hibernate.failing.gutsy-64bit http://launchpadlibrarian.net/12920468/gpm.log.suspend.hibernate.failing.gutsy-64bit -- when returning from suspend my laptop tries to hibernate https://bugs.launchpad.net/bugs/149665 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 149665] Re: when returning from suspend my laptop tries to hibernate
FYI: I removed all the gconf options for gnome-power-manager and did a sudo apt-get install --reinstall gnome-power-manager. All settings are default, only edited the timeouts so it would auto-suspend in 1+1 minutes. -- when returning from suspend my laptop tries to hibernate https://bugs.launchpad.net/bugs/149665 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 149665] Re: when returning from suspend my laptop tries to hibernate
Cannot follow instructions for DebuggingKernelSuspend, since the standard Ubuntu Kernel 64bit somehow doesn't give me a /sys/power/pm_trace file-thingy. So that' s all folks. :) $ ls /sys/power/ disk image_size resume state -- when returning from suspend my laptop tries to hibernate https://bugs.launchpad.net/bugs/149665 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 149665] Re: when returning from suspend my laptop tries to hibernate
** Attachment added: lspci-vvnn.log http://launchpadlibrarian.net/12920521/lspci-vvnn.log -- when returning from suspend my laptop tries to hibernate https://bugs.launchpad.net/bugs/149665 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 207783] [NEW] Hardy kernel fails to boot when the USB controller is enabled (ATA/SATA errors)
Public bug reported: Binary package hint: linux-source-2.6.24 I wanted to try installing hardy on our main-PC by using wubi. This worked, but when I tried to boot it, it hanged and after a while returned me to a busybox, because the rootdrive couldn't be found. After fiddling around I figured out that disabling the usb controller enables the kernel to boot. (note: disabling legacy support did not fix it, I had to disable the complete USB controller in the bios). It looks like the SATA controller somehow fails, and my HD is sata, so that is troublesome. I am currently on windows, since the lack of a mouse is frustrating, but I will try to add the relevant information to this bugreport from out the ubuntu environment. Since I do not know how to recover the dmesg when you get a busybox without disk access, I can only show the dmesg errors that I noted on a piece of paper. ata5: qc timeout (cmd 0x27) ata5: failed to read native max address ata5: failed to recover some devices [..] ata5: revalidation failed ata5: disabled ata5: soft resetting link ata5: EH complete [..] and then it says that it can't find my disk, and gives me busybox. System info: CPU: E6400 MB: MSI MS-7235 NB: Intel P965/G965 rev. C1 SB: Intel 82801HB/HR (ICH8/R) rev. 02 ** Affects: linux (Ubuntu) Importance: Undecided Status: New -- Hardy kernel fails to boot when the USB controller is enabled (ATA/SATA errors) https://bugs.launchpad.net/bugs/207783 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 207783] Re: Hardy kernel fails to boot when the USB controller is enabled (ATA/SATA errors)
** Attachment added: dmesg.log.usbdisabled.hardy64bit http://launchpadlibrarian.net/12922087/dmesg.log.usbdisabled.hardy64bit -- Hardy kernel fails to boot when the USB controller is enabled (ATA/SATA errors) https://bugs.launchpad.net/bugs/207783 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 207783] Re: Hardy kernel fails to boot when the USB controller is enabled (ATA/SATA errors)
** Attachment added: lshw.usbdisabled.hardy64bit http://launchpadlibrarian.net/12922099/lshw.usbdisabled.hardy64bit -- Hardy kernel fails to boot when the USB controller is enabled (ATA/SATA errors) https://bugs.launchpad.net/bugs/207783 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 207783] Re: Hardy kernel fails to boot when the USB controller is enabled (ATA/SATA errors)
** Attachment added: lspci.usbdisabled.hardy64bit http://launchpadlibrarian.net/12922103/lspci.usbdisabled.hardy64bit -- Hardy kernel fails to boot when the USB controller is enabled (ATA/SATA errors) https://bugs.launchpad.net/bugs/207783 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 207783] Re: Hardy kernel fails to boot when the USB controller is enabled (ATA/SATA errors)
Linux peter-desktop 2.6.24-12-generic #1 SMP Wed Mar 12 22:31:43 UTC 2008 x86_64 GNU/Linux -- Hardy kernel fails to boot when the USB controller is enabled (ATA/SATA errors) https://bugs.launchpad.net/bugs/207783 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 207783] Re: Hardy kernel fails to boot when the USB controller is enabled (ATA/SATA errors)
Bios had/has the latest updates (latest available = mid 2007) -- Hardy kernel fails to boot when the USB controller is enabled (ATA/SATA errors) https://bugs.launchpad.net/bugs/207783 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 207783] Re: Hardy kernel fails to boot when the USB controller is enabled (ATA/SATA errors)
another note: I did tried with noapic, nolapic, acpi=off pci=noacpi etc. That all gave errors, most of them ATA/SATA related, and IRQ related. Also made sure that all the usb devices internally and externally were disconnected. It is not caused by a USB Device. -- Hardy kernel fails to boot when the USB controller is enabled (ATA/SATA errors) https://bugs.launchpad.net/bugs/207783 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 207783] Re: Hardy kernel fails to boot when the USB controller is enabled (ATA/SATA errors)
Looks like it is the JMicron AHCI controller on the P965 Neo-F mainboard. https://bugs.launchpad.net/ubuntu/+source/linux-source-2.6.17/+bug/66747 Will try the suggestion mentioned there. However, it is ofcourse very strange that after year Ubuntu is still not able to boot correctly without the user needing to edit the boot parameters. -- Hardy kernel fails to boot when the USB controller is enabled (ATA/SATA errors) https://bugs.launchpad.net/bugs/207783 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 199496] Re: Tomboy.exe crashed with SIGSEGV in exit()
To be complete: The error does occur after launching again, but only shows up in dmesg, so the user sees it as no error. -- Tomboy.exe crashed with SIGSEGV in exit() https://bugs.launchpad.net/bugs/199496 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 204571] Re: f-spot.exe crashed with SIGSEGV
Using newest version of all software in hardy 64bit. F-spot crashes on exit, first time it shows that it crashes, after that when you start and exit the program, it only logs into dmesg that it segfaulted. [ 553.320028] f-spot[9110]: segfault at 41853e00 rip 41853e00 rsp 7fffbfc9ad18 error 14 [ 836.392262] f-spot[9550]: segfault at 401f8020 rip 401f8020 rsp 7fff66b61348 error 14 [ 848.081434] f-spot[9565]: segfault at 417c3e00 rip 417c3e00 rsp 7fffc2e045e8 error 14 [ 879.959222] f-spot[9576]: segfault at 40ea5e00 rip 40ea5e00 rsp 7fff1685b038 error 14 -- f-spot.exe crashed with SIGSEGV https://bugs.launchpad.net/bugs/204571 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 204571] Re: f-spot.exe crashed with SIGSEGV
Cannot get the debugversion, repo version is outdated. If that one is available I can run a backtrace. f-spot-dbgsym: Depends: f-spot (= 0.4.2-0ubuntu4) but 0.4.2-1ubuntu1 is to be installed -- f-spot.exe crashed with SIGSEGV https://bugs.launchpad.net/bugs/204571 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 189506] Re: Normal user can't access USB camera Error (-53: 'Could not claim the USB device')
My accessproblem is fixed as well with the fix. -- Normal user can't access USB camera Error (-53: 'Could not claim the USB device') https://bugs.launchpad.net/bugs/189506 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 149665] Re: when returning from suspend my laptop tries to hibernate
Sorry for the delay. Planning to look at this bug tomorrow for a GPM log for both of the scenarios. -- when returning from suspend my laptop tries to hibernate https://bugs.launchpad.net/bugs/149665 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 189506] Re: Normal user can't access USB camera Error (-53: 'Could not claim the USB device')
Linked the bug to udev, I see more bugs there, also a confirmed one. So this way it will get the right attention I hope. ** Also affects: udev (Ubuntu) Importance: Undecided Status: New -- Normal user can't access USB camera Error (-53: 'Could not claim the USB device') https://bugs.launchpad.net/bugs/189506 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 158119] Re: Photo Import from Canon IXUS 30/Powershot SD200 failed
I am having a similar problem in Hardy Beta 1, x86_64 Camera gets recognized when plugged in (Bus 003 Device 003: ID 04a9:30bb Canon, Inc. PowerShot A95), but no software starts. When I start f-spot, it does recognize the camera, but when I try to import from it by clicking it's name, I get: Error connecting to camera. Received error: Could not claim the USB device while connecting to the camera I also cannot use it in Gutsy, but Hardy is more important I guess. -- Photo Import from Canon IXUS 30/Powershot SD200 failed https://bugs.launchpad.net/bugs/158119 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 189506] Re: Normal user can't access USB camera Error (-53: 'Could not claim the USB device')
Looks like another bug according to the --debug output. The bad parameter error doesn't show up on the bug starters errorlog. -- Normal user can't access USB camera Error (-53: 'Could not claim the USB device') https://bugs.launchpad.net/bugs/189506 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 189506] Re: Normal user can't access USB camera Error (-53: 'Could not claim the USB device')
** Attachment added: dmesg http://launchpadlibrarian.net/12808243/dmesg.txt -- Normal user can't access USB camera Error (-53: 'Could not claim the USB device') https://bugs.launchpad.net/bugs/189506 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 189506] Re: Normal user can't access USB camera Error (-53: 'Could not claim the USB device')
I am still having this issue, even after upgrading all packages in the
current 8.04 dev distribution. Running x86_64.
When using sudo it does work, when just using it as user, it doesn't.
$ gphoto2 --auto-detect
Model Port
--
Canon PowerShot A95 (PTP mode) usb:
$ gphoto2 --get-all-files
*** Error ***
An error occurred in the io-library ('Could not claim the USB device'): Could
not claim interface 0 (Operation not permitted). Make sure no other program or
kernel module (such as sdc2xx, stv680, spca50x) is using the device and you
have read/write access to the device.
*** Error (-53: 'Could not claim the USB device') ***
See attachment for output of it running while --debug is enabled.
Main errors are:
*** Error ***
PTP: Sequence number mismatch 0 vs expected 1.
0.524642 context(0): PTP Error: bad parameter
** Attachment added: --debug output
http://launchpadlibrarian.net/12808232/gphoto2--get-all-files--debug.txt
--
Normal user can't access USB camera Error (-53: 'Could not claim the USB
device')
https://bugs.launchpad.net/bugs/189506
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 189506] Re: Normal user can't access USB camera Error (-53: 'Could not claim the USB device')
Also, this is normal? Doesn't it need to be something like usb:005,008 ? $ gphoto2 --auto-detect Model Port -- Canon PowerShot A95 (PTP mode) usb: -- Normal user can't access USB camera Error (-53: 'Could not claim the USB device') https://bugs.launchpad.net/bugs/189506 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 189506] Re: Normal user can't access USB camera Error (-53: 'Could not claim the USB device')
Ignore the earlier mentioned PTP Error, it was due to using the memory card earlier directly on a windows PC. New debug log shows exactly the same problems as the reporter's. ** Attachment added: env LANG=C gphoto2 --debug --debug-logfile=my-logfile.txt --get-all-files --debug --debug-logfile=gphoto2--get-all-files--debug.txt http://launchpadlibrarian.net/12809042/gphoto2--get-all-files--debug.txt -- Normal user can't access USB camera Error (-53: 'Could not claim the USB device') https://bugs.launchpad.net/bugs/189506 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 149665] Re: when returning from suspend my laptop tries to hibernate
I can confirm the experience of Justin: disabling hibernation in g-p-m leads to no problems with coming back from standby. Also saw that other people found out the same thing. -- when returning from suspend my laptop tries to hibernate https://bugs.launchpad.net/bugs/149665 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 116826] Re: wake up from suspend ends up as hiberate
It looks like gnome-power-manager has two options, one is available as a setting in the menu, the other one is only available in the gconf- editor.In the gnome-power-manager settings dialog, you can set the PC's timeout for initiating hibernate. However, there is also an option in the gconf-editor for gnome-power-manager, that handles the sleep timeout. In my fresh install of Ubuntu, I putt the hibernate function on 11minutes, and the sleep function appears to be sett at 120 seconds. Probably this is going wrong: after 120 seconds, the PC starts sleep mode. When you start it again after the 11 minutes have elapsed, it somehow makes the error that the 11 minutes should be counted too when the system is at sleepmode and thus hibernating needs to be activated.I now have put hibernation to off, and sleep to 180s, will report later if this seems to be working. I would like to know from people that also suffer from this bug: Do you have enabled the hibernate timer in the gnome-power-manager settings menu? If so, do you get the same symptoms if you wakeup before the selected hibernation time ? I really wonder why sleep cannot be configured from the settings menu of gnome-power-manager, and it also really looks like this bug is related to gnome-power-manager, and not a kernel issue. ** Also affects: gnome-power-manager (Ubuntu) Importance: Undecided Status: New -- wake up from suspend ends up as hiberate https://bugs.launchpad.net/bugs/116826 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 149665] Re: when returning from suspend my laptop tries to hibernate
Related bug #116826 https://bugs.launchpad.net/ubuntu/+source/gnome-power-manager/+bug/116826 -- when returning from suspend my laptop tries to hibernate https://bugs.launchpad.net/bugs/149665 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 116826] Re: wake up from suspend ends up as hiberate
@Milan: Thanks, I posted it there on the website too. Will test my experiment with the hibernation to off later. -- wake up from suspend ends up as hiberate https://bugs.launchpad.net/bugs/116826 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 186382] Re: [nvidia 169.xx] gtk window decorator somtimes draws decoration ugly or not at all
I reinstalled gutsy today and the error appears even with the 100.14.19 (the most recent gutsy nvidia-glx-new). Now, the bar doesn't get orange in firefox/thunderbird etc. but gets grey. (using Geforce 7600GS/AGP) -- [nvidia 169.xx] gtk window decorator somtimes draws decoration ugly or not at all https://bugs.launchpad.net/bugs/186382 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 116826] Re: wake up from suspend ends up as hiberate
Unfortunately it appears that the sleep time out key is the key where the hibernation timeout gets stored. So my guess was not true: there are not 2 timers available, so their interference is not possible. -- wake up from suspend ends up as hiberate https://bugs.launchpad.net/bugs/116826 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 194933] Re: Compiz + 169-series NVIDIA drivers: frequent visual corruption of window title bars upon various title bar events
*** This bug is a duplicate of bug 186382 *** https://bugs.launchpad.net/bugs/186382 I have this problem too, extremely annoying! On 2 pc's with geforce 7 cards and standard ubuntu compiz on gutsy. -- Compiz + 169-series NVIDIA drivers: frequent visual corruption of window title bars upon various title bar events https://bugs.launchpad.net/bugs/194933 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 186382] Re: [nvidia 169.xx] gtk window decorator somtimes draws decoration ugly or not at all
See it also very often on Gutsy with the 169.12. On 2 pc's with GF7. -- [nvidia 169.xx] gtk window decorator somtimes draws decoration ugly or not at all https://bugs.launchpad.net/bugs/186382 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 199657] [NEW] frequency scaling for overclocked core 2 duo uses original frequencies
Public bug reported: Binary package hint: powernowd I have a e4300 Core 2 Duo processor. Original speed is 1.8Ghz. When I enable speedstep in the bios, the processor clocks back to 1.2 ghz depending on the load. This is all ok. When I overclock my processor to 2.2 Ghz and have speedstep DISABLED, Ubuntu reports a 2.2Ghz processor. However, when speedstep is ENABLED: Ubuntu just keeps saying that the 2.2Ghz OC'd processor runs at 1.8Ghz and only allows for 1.2Ghz/1.8Ghz frequency. I thought this was just the limitation of the motherboard or the speedstep technology: śpeedstep does not work when OC'ing. This appears to be NOT TRUE. I have a Windows XP installation on the same PC and when I boot into it with the 2.2Ghz OC and speedstep ENABLED, it gives me the full 2.2Ghz with a working speedstep that clocks back to 1.6Ghz. So, this is definitely a bug in the way linux handles speedstep: OC'd Core 2 Duo speeds are not handled correctly. (Hope this is the right package for the bugreport) = Using 7.10 x86_64, with the 8.04 kernel = ** Affects: powernowd (Ubuntu) Importance: Undecided Status: New ** Description changed: Binary package hint: powernowd I have a e4300 Core 2 Duo processor. Original speed is 1.8Ghz. When I enable speedstep in the bios, the processor clocks back to 1.2 ghz depending on the load. This is all ok. - However, when I overclock my processor to 2.2 Ghz and have speedstep DISABLED, Ubuntu reports a 2.2Ghz processor. + When I overclock my processor to 2.2 Ghz and have speedstep DISABLED, Ubuntu reports a 2.2Ghz processor. However, when speedstep is ENABLED: Ubuntu just keeps saying that the processor runs at 1.8Ghz and only allows for 1.2Ghz/1.8Ghz frequency. I thought this was just the limitation of the motherboard or the speedstep technology: śpeedstep does not work when OC'ing. This appears to be NOT TRUE. I have a Windows XP installation on the same PC and when I boot into it with the 2.2Ghz OC and speedstep ENABLED, it gives me the full 2.2Ghz with a working speedstep that clocks back to 1.6Ghz. So, this is definitely a bug in the way linux handles speedstep: OC'd Core 2 Duo speeds are not handled correctly. (Hope this is the right package for the bugreport) = Using 7.10 x86_64, with the 8.04 kernel = ** Description changed: Binary package hint: powernowd I have a e4300 Core 2 Duo processor. Original speed is 1.8Ghz. When I enable speedstep in the bios, the processor clocks back to 1.2 ghz depending on the load. This is all ok. When I overclock my processor to 2.2 Ghz and have speedstep DISABLED, Ubuntu reports a 2.2Ghz processor. - However, when speedstep is ENABLED: Ubuntu just keeps saying that the processor runs at 1.8Ghz and only allows for 1.2Ghz/1.8Ghz frequency. + However, when speedstep is ENABLED: Ubuntu just keeps saying that the 2.2Ghz processor runs at 1.8Ghz and only allows for 1.2Ghz/1.8Ghz frequency. I thought this was just the limitation of the motherboard or the speedstep technology: śpeedstep does not work when OC'ing. This appears to be NOT TRUE. I have a Windows XP installation on the same PC and when I boot into it with the 2.2Ghz OC and speedstep ENABLED, it gives me the full 2.2Ghz with a working speedstep that clocks back to 1.6Ghz. So, this is definitely a bug in the way linux handles speedstep: OC'd Core 2 Duo speeds are not handled correctly. (Hope this is the right package for the bugreport) = Using 7.10 x86_64, with the 8.04 kernel = ** Description changed: Binary package hint: powernowd I have a e4300 Core 2 Duo processor. Original speed is 1.8Ghz. When I enable speedstep in the bios, the processor clocks back to 1.2 ghz depending on the load. This is all ok. When I overclock my processor to 2.2 Ghz and have speedstep DISABLED, Ubuntu reports a 2.2Ghz processor. - However, when speedstep is ENABLED: Ubuntu just keeps saying that the 2.2Ghz processor runs at 1.8Ghz and only allows for 1.2Ghz/1.8Ghz frequency. + However, when speedstep is ENABLED: Ubuntu just keeps saying that the 2.2Ghz OC'd processor runs at 1.8Ghz and only allows for 1.2Ghz/1.8Ghz frequency. I thought this was just the limitation of the motherboard or the speedstep technology: śpeedstep does not work when OC'ing. This appears to be NOT TRUE. I have a Windows XP installation on the same PC and when I boot into it with the 2.2Ghz OC and speedstep ENABLED, it gives me the full 2.2Ghz with a working speedstep that clocks back to 1.6Ghz. So, this is definitely a bug in the way linux handles speedstep: OC'd Core 2 Duo speeds are not handled correctly. (Hope this is the right package for the bugreport) = Using 7.10 x86_64, with the 8.04 kernel = -- frequency scaling for overclocked core 2 duo uses original frequencies
[Bug 132403] Re: Cpu frequency scaling is limited to stock speeds
This bug still exists in the hardy alpha 5 kernel Frequency scaling on over clocked Core 2 Duo processors does not use the reported speed, but the original stockspeeds, while the Windows implementation of speedstep does work right. Any comments of the dev's ? -- Cpu frequency scaling is limited to stock speeds https://bugs.launchpad.net/bugs/132403 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 192023] [NEW] distccmon not displaying threads because DISTCC_DIR is not defined
Public bug reported: Binary package hint: distcc Ubuntu 7.10 Gutsy distccmon-gnome 2.18.3-4.1ubuntu1 I have several PC's where I run distccd on. When compiling a job on a machine, it distributes correctly to the other machines. However, distccmon-gnome and distccmon-text do not display any distribution/information/threads. This is true on both machines. Because one of them is a completely fresh install of ubuntu, it has to be a bug. I found out that to enable the monitoring the DISTCC_DIR environment variable needs to be set to ~/.distcc or /root/.distcc (not sure about which one, because both are available in my ubuntu. Currently while compiling a kernel as root it uses /root/.distcc) When the variable is exported distccmon works correctly. When I used distccmon compiled freshly from the original source there was no such problem. Probably the original version does set the path. It would be very nice if this could be fixed. ** Affects: distcc (Ubuntu) Importance: Undecided Status: New -- distccmon not displaying threads because DISTCC_DIR is not defined https://bugs.launchpad.net/bugs/192023 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 135041] Re: xen-image-create fails with kernel panic
** Attachment added: cat /proc/cpuinfo http://launchpadlibrarian.net/9257209/cpuinfo -- xen-image-create fails with kernel panic https://bugs.launchpad.net/bugs/135041 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 135041] Re: xen-image-create fails with kernel panic
** Attachment added: free -m http://launchpadlibrarian.net/9257214/free%20-m -- xen-image-create fails with kernel panic https://bugs.launchpad.net/bugs/135041 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 135041] Re: xen-image-create fails with kernel panic
It now comes with another error, possibly related, so I post it here. Message from [EMAIL PROTECTED] at Wed Sep 12 19:41:03 2007 ... TSA kernel: Oops: [#1] Message from [EMAIL PROTECTED] at Wed Sep 12 19:41:03 2007 ... TSA kernel: SMP Message from [EMAIL PROTECTED] at Wed Sep 12 19:41:03 2007 ... TSA kernel: CPU:1 Message from [EMAIL PROTECTED] at Wed Sep 12 19:41:03 2007 ... TSA kernel: EIP:0061:[block_invalidatepage+51/173]Not tainted VLI Message from [EMAIL PROTECTED] at Wed Sep 12 19:41:03 2007 ... TSA kernel: EFLAGS: 00210217 (2.6.22-11-xen #1) Message from [EMAIL PROTECTED] at Wed Sep 12 19:41:03 2007 ... TSA kernel: EIP is at block_invalidatepage+0x33/0xad Message from [EMAIL PROTECTED] at Wed Sep 12 19:41:03 2007 ... TSA kernel: eax: ebx: 00100100 ecx: 0002 edx: c1b9d294 Message from [EMAIL PROTECTED] at Wed Sep 12 19:41:03 2007 ... TSA kernel: esi: c167dbe0 edi: c1b9d294 ebp: esp: c5d7de68 Message from [EMAIL PROTECTED] at Wed Sep 12 19:41:03 2007 ... TSA kernel: ds: 007b es: 007b fs: 00d8 gs: 0033 ss: 0069 Message from [EMAIL PROTECTED] at Wed Sep 12 19:41:03 2007 ... TSA kernel: Process umount (pid: 13614, ti=c5d7c000 task=c5d88ab0 task.ti=c5d7c000) Message from [EMAIL PROTECTED] at Wed Sep 12 19:41:03 2007 ... TSA kernel: Stack: 00100100 c0183948 3586 0002 028a c014d262 c167dbe0 Message from [EMAIL PROTECTED] at Wed Sep 12 19:41:03 2007 ... TSA kernel:c014d523 c167dbe0 c014d5de 000e 0058f4d8 0001 Message from [EMAIL PROTECTED] at Wed Sep 12 19:41:03 2007 ... TSA kernel:c158f4d8 000e c1bb3940 c1bb37a0 c167dbe0 Message from [EMAIL PROTECTED] at Wed Sep 12 19:41:03 2007 ... TSA kernel: Call Trace: Message from [EMAIL PROTECTED] at Wed Sep 12 19:41:03 2007 ... TSA kernel: [block_invalidatepage+0/173] block_invalidatepage+0x0/0xad Message from [EMAIL PROTECTED] at Wed Sep 12 19:41:03 2007 ... TSA kernel: [do_invalidatepage+22/24] do_invalidatepage+0x16/0x18 Message from [EMAIL PROTECTED] at Wed Sep 12 19:41:03 2007 ... TSA kernel: [truncate_complete_page+36/63] truncate_complete_page+0x24/0x3f Message from [EMAIL PROTECTED] at Wed Sep 12 19:41:03 2007 ... TSA kernel: [truncate_inode_pages_range+160/603] truncate_inode_pages_range+0xa0/0x25b Message from [EMAIL PROTECTED] at Wed Sep 12 19:41:03 2007 ... TSA kernel: [truncate_inode_pages+23/26] truncate_inode_pages+0x17/0x1a Message from [EMAIL PROTECTED] at Wed Sep 12 19:41:03 2007 ... TSA kernel: [__blkdev_put+68/259] __blkdev_put+0x44/0x103 Message from [EMAIL PROTECTED] at Wed Sep 12 19:41:03 2007 ... TSA kernel: [deactivate_super+82/101] deactivate_super+0x52/0x65 Message from [EMAIL PROTECTED] at Wed Sep 12 19:41:03 2007 ... TSA kernel: [sys_umount+498/538] sys_umount+0x1f2/0x21a Message from [EMAIL PROTECTED] at Wed Sep 12 19:41:03 2007 ... TSA kernel: [do_page_fault+1913/2976] do_page_fault+0x779/0xba0 Message from [EMAIL PROTECTED] at Wed Sep 12 19:41:03 2007 ... TSA kernel: [unmap_region+239/247] unmap_region+0xef/0xf7 Message from [EMAIL PROTECTED] at Wed Sep 12 19:41:03 2007 ... TSA kernel: [sys_stat64+15/35] sys_stat64+0xf/0x23 Message from [EMAIL PROTECTED] at Wed Sep 12 19:41:03 2007 ... TSA kernel: [remove_vma+54/59] remove_vma+0x36/0x3b Message from [EMAIL PROTECTED] at Wed Sep 12 19:41:03 2007 ... TSA kernel: [do_munmap+403/428] do_munmap+0x193/0x1ac Message from [EMAIL PROTECTED] at Wed Sep 12 19:41:03 2007 ... TSA kernel: [sys_oldumount+23/26] sys_oldumount+0x17/0x1a Message from [EMAIL PROTECTED] at Wed Sep 12 19:41:03 2007 ... TSA kernel: [syscall_call+7/11] syscall_call+0x7/0xb Message from [EMAIL PROTECTED] at Wed Sep 12 19:41:03 2007 ... TSA kernel: [xfrm4_dst_destroy+73/170] xfrm4_dst_destroy+0x49/0xaa Message from [EMAIL PROTECTED] at Wed Sep 12 19:41:03 2007 ... TSA kernel: === Message from [EMAIL PROTECTED] at Wed Sep 12 19:41:03 2007 ... TSA kernel: Code: 08 89 14 24 8b 00 a8 01 75 04 0f 0b eb fe 8b 06 f6 c4 08 0f 84 85 00 00 00 8b 06 f6 c4 08 75 04 0f 0b eb fe 8b 7e 0c 31 c0 89 fb 8b 53 04 89 c5 03 6b 14 39 04 24 89 54 24 04 77 43 e8 70 8e 13 Message from [EMAIL PROTECTED] at Wed Sep 12 19:41:03 2007 ... TSA kernel: EIP: [block_invalidatepage+51/173] block_invalidatepage+0x33/0xad SS:ESP 0069:c5d7de68 -- xen-image-create fails with kernel panic https://bugs.launchpad.net/bugs/135041 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 135041] Re: xen-image-create fails with kernel panic
Message from [EMAIL PROTECTED] at Wed Sep 12 19:41:46 2007 ... TSA kernel: Bad page state in process 'pdflush' Message from [EMAIL PROTECTED] at Wed Sep 12 19:41:46 2007 ... TSA kernel: page:c1b3d1c0 flags:0x0004 mapping: mapcount:0 count:1 Message from [EMAIL PROTECTED] at Wed Sep 12 19:41:46 2007 ... TSA kernel: Trying to fix it up, but a reboot is needed Message from [EMAIL PROTECTED] at Wed Sep 12 19:41:46 2007 ... TSA kernel: Backtrace: -- xen-image-create fails with kernel panic https://bugs.launchpad.net/bugs/135041 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 137595] Re: Networking doesn't Work under Xen 2.6.22-10-xen without ethtool -K eth0 tx off command
Same here, is working now correctly after the kernel update. -- Networking doesn't Work under Xen 2.6.22-10-xen without ethtool -K eth0 tx off command https://bugs.launchpad.net/bugs/137595 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 135041] Re: xen-image-create fails with kernel panic
After some more research and using the latest [..]-11 kernel I found out that the error is most likely due to excessive memory usage. When running xen-create-image all my system memory gets used ( 1GB). When there is no more memory left the pdflush process starts to run, crashes and the kernel hangs. I have tested xen-tools 3.7 and the error also exists in there. So it must be an ubuntu kernel problem. ** Tags added: memory-usage -- xen-image-create fails with kernel panic https://bugs.launchpad.net/bugs/135041 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 137595] Re: Networking doesn't Work under Xen 2.6.22-10-xen without ethtool -K eth0 tx off command
Suddenly found myself also needing to use the ethtool command. Strange, because it did work a few days without it. Problem definitely exists. -- Networking doesn't Work under Xen 2.6.22-10-xen without ethtool -K eth0 tx off command https://bugs.launchpad.net/bugs/137595 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 137595] Re: Networking doesn't Work under Xen 2.6.22-10-xen without ethtool -K eth0 tx off command
With the latest kernelupdate I was able to use the network without any ethtool use. It was present in the kernel from a weeks ago. Are you sure you have the latest kernelupdate? -- Networking doesn't Work under Xen 2.6.22-10-xen without ethtool -K eth0 tx off command https://bugs.launchpad.net/bugs/137595 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 135041] Re: xen-image-create fails with kernel panic
** Changed in: linux-source-2.6.22 (Ubuntu) Sourcepackagename: xen = linux-source-2.6.22 ** Description changed: - During debootstrap the kernel suddenly panics and the installation hangs. + During xen-image-create debootstrap the kernel suddenly gives an OOPS and the installation hangs. Somehow I cannot install any virtual host, which means that the whole Xen purpose is defeated. [..] - I: Extracting python2.5-minimal... + I: Extracting python2.5-minimal... (it happens at random packages) Message from [EMAIL PROTECTED] at Mon Aug 27 12:39:04 2007 ... TSA kernel: [ 1031.856171] Oops: 0002 [#1] Message from [EMAIL PROTECTED] at Mon Aug 27 12:39:04 2007 ... TSA kernel: [ 1031.856198] SMP Message from [EMAIL PROTECTED] at Mon Aug 27 12:39:04 2007 ... TSA kernel: [ 1031.856690] CPU:0 Message from [EMAIL PROTECTED] at Mon Aug 27 12:39:04 2007 ... TSA kernel: [ 1031.856693] EIP:0061:[c16a9d20]Not tainted VLI Message from [EMAIL PROTECTED] at Mon Aug 27 12:39:04 2007 ... TSA kernel: [ 1031.856697] EFLAGS: 00010206 (2.6.22-10-xen #1) Message from [EMAIL PROTECTED] at Mon Aug 27 12:39:04 2007 ... TSA kernel: [ 1031.856771] EIP is at 0xc16a9d20 Message from [EMAIL PROTECTED] at Mon Aug 27 12:39:04 2007 ... TSA kernel: [ 1031.856796] eax: c16a95e0 ebx: c16a95e0 ecx: c03cdd0c edx: Message from [EMAIL PROTECTED] at Mon Aug 27 12:39:04 2007 ... TSA kernel: [ 1031.856831] esi: c242bec4 edi: 0004 ebp: esp: c242be94 Message from [EMAIL PROTECTED] at Mon Aug 27 12:39:04 2007 ... TSA kernel: [ 1031.856860] ds: 007b es: 007b fs: 00d8 gs: ss: 0069 Message from [EMAIL PROTECTED] at Mon Aug 27 12:39:04 2007 ... TSA kernel: [ 1031.856890] Process sed (pid: 8046, ti=c242a000 task=c7373070 task.ti=c242a000) Message from [EMAIL PROTECTED] at Mon Aug 27 12:39:04 2007 ... TSA kernel: [ 1031.856918] Stack: c0154e19 c15e58ac c03cdc80 0006 c242bec4 c142f418 000c c0154eaf Message from [EMAIL PROTECTED] at Mon Aug 27 12:39:04 2007 ... TSA kernel: [ 1031.857022]c15e5480 c03cdc80 c0157d16 000c 000a c15e5660 c15e55a0 Message from [EMAIL PROTECTED] at Mon Aug 27 12:39:04 2007 ... TSA kernel: [ 1031.857127]c15f8360 c15e5960 c15e56e0 c15e5640 c15e5980 c16a95e0 c15e58a0 c15e5480 Message from [EMAIL PROTECTED] at Mon Aug 27 12:39:04 2007 ... TSA kernel: [ 1031.857274] [free_hot_cold_page+393/512] free_hot_cold_page+0x189/0x200 Message from [EMAIL PROTECTED] at Mon Aug 27 12:39:04 2007 ... TSA kernel: [ 1031.857235] Call Trace: Message from [EMAIL PROTECTED] at Mon Aug 27 12:39:04 2007 ... TSA kernel: [ 1031.857325] [__pagevec_free+31/48] __pagevec_free+0x1f/0x30 Message from [EMAIL PROTECTED] at Mon Aug 27 12:39:04 2007 ... TSA kernel: [ 1031.857369] [release_pages+390/496] release_pages+0x186/0x1f0 Message from [EMAIL PROTECTED] at Mon Aug 27 12:39:04 2007 ... TSA kernel: [ 1031.858240] [exit_mmap+225/240] exit_mmap+0xe1/0xf0 Message from [EMAIL PROTECTED] at Mon Aug 27 12:39:04 2007 ... TSA kernel: [ 1031.858187] [free_pages_and_swap_cache+116/160] free_pages_and_swap_cache+0x74/0xa0 Message from [EMAIL PROTECTED] at Mon Aug 27 12:39:04 2007 ... TSA kernel: [ 1031.858381] [do_IRQ+64/112] do_IRQ+0x40/0x70 Message from [EMAIL PROTECTED] at Mon Aug 27 12:39:04 2007 ... TSA kernel: [ 1031.858336] [do_exit+289/2128] do_exit+0x121/0x850 Message from [EMAIL PROTECTED] at Mon Aug 27 12:39:04 2007 ... TSA kernel: [ 1031.858429] [do_munmap+390/480] do_munmap+0x186/0x1e0 Message from [EMAIL PROTECTED] at Mon Aug 27 12:39:04 2007 ... TSA kernel: [ 1031.858291] [mmput+56/160] mmput+0x38/0xa0 Message from [EMAIL PROTECTED] at Mon Aug 27 12:39:04 2007 ... TSA kernel: [ 1031.858515] [syscall_call+7/11] syscall_call+0x7/0xb Message from [EMAIL PROTECTED] at Mon Aug 27 12:39:04 2007 ... TSA kernel: [ 1031.858472] [do_group_exit+38/144] do_group_exit+0x26/0x90 Message from [EMAIL PROTECTED] at Mon Aug 27 12:39:04 2007 ... TSA kernel: [ 1031.858567] === Message from [EMAIL PROTECTED] at Mon Aug 27 12:39:04 2007 ... TSA kernel: [ 1031.859129] EIP: [c16a9d20] 0xc16a9d20 SS:ESP 0069:c242be94 Message from [EMAIL PROTECTED] at Mon Aug 27 12:39:04 2007 ... TSA kernel: [ 1031.858597] Code: 00 00 00 d8 3e 6a c1 38 f6 6a c1 6c 08 00 00 02 00 00 00 ff ff ff ff 90 d3 3f c9 34 ff c8 c8 0d 00 00 00 f8 98 6a c1 58 8a 6b c1 00 02 00 00 01 00 00 00 ff ff ff ff f4 95 6a c1 00 00 00 00 a0 ** Tags added: gutsy xen ** Description changed: + binary-package-hint: linux-image-2.6.22-10-xen + During xen-image-create debootstrap the kernel suddenly gives an OOPS and the installation hangs. Somehow I cannot install any virtual host, which means that the whole Xen purpose is defeated. [..] I: Extracting python2.5-minimal...
[Bug 126369] Re: kernel disables irq after 10 minutes
Just saw this bug, I have been experiencing the same message on a dual p3 800mhz server-system. I initialy thought it had to do with apparmor. -- kernel disables irq after 10 minutes https://bugs.launchpad.net/bugs/126369 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 71362] Re: Unable to connect to network from Xen Linux
When reinstalled today and apt-get dist-upgrade'd the network problems where not existent. Looks like the bug has been solved. -- Unable to connect to network from Xen Linux https://bugs.launchpad.net/bugs/71362 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 135041] xen-image-create fails with kernel panic
Public bug reported: During debootstrap the kernel suddenly panics and the installation hangs. Somehow I cannot install any virtual host, which means that the whole Xen purpose is defeated. [..] I: Extracting python2.5-minimal... Message from [EMAIL PROTECTED] at Mon Aug 27 12:39:04 2007 ... TSA kernel: [ 1031.856171] Oops: 0002 [#1] Message from [EMAIL PROTECTED] at Mon Aug 27 12:39:04 2007 ... TSA kernel: [ 1031.856198] SMP Message from [EMAIL PROTECTED] at Mon Aug 27 12:39:04 2007 ... TSA kernel: [ 1031.856690] CPU:0 Message from [EMAIL PROTECTED] at Mon Aug 27 12:39:04 2007 ... TSA kernel: [ 1031.856693] EIP:0061:[c16a9d20]Not tainted VLI Message from [EMAIL PROTECTED] at Mon Aug 27 12:39:04 2007 ... TSA kernel: [ 1031.856697] EFLAGS: 00010206 (2.6.22-10-xen #1) Message from [EMAIL PROTECTED] at Mon Aug 27 12:39:04 2007 ... TSA kernel: [ 1031.856771] EIP is at 0xc16a9d20 Message from [EMAIL PROTECTED] at Mon Aug 27 12:39:04 2007 ... TSA kernel: [ 1031.856796] eax: c16a95e0 ebx: c16a95e0 ecx: c03cdd0c edx: Message from [EMAIL PROTECTED] at Mon Aug 27 12:39:04 2007 ... TSA kernel: [ 1031.856831] esi: c242bec4 edi: 0004 ebp: esp: c242be94 Message from [EMAIL PROTECTED] at Mon Aug 27 12:39:04 2007 ... TSA kernel: [ 1031.856860] ds: 007b es: 007b fs: 00d8 gs: ss: 0069 Message from [EMAIL PROTECTED] at Mon Aug 27 12:39:04 2007 ... TSA kernel: [ 1031.856890] Process sed (pid: 8046, ti=c242a000 task=c7373070 task.ti=c242a000) Message from [EMAIL PROTECTED] at Mon Aug 27 12:39:04 2007 ... TSA kernel: [ 1031.856918] Stack: c0154e19 c15e58ac c03cdc80 0006 c242bec4 c142f418 000c c0154eaf Message from [EMAIL PROTECTED] at Mon Aug 27 12:39:04 2007 ... TSA kernel: [ 1031.857022]c15e5480 c03cdc80 c0157d16 000c 000a c15e5660 c15e55a0 Message from [EMAIL PROTECTED] at Mon Aug 27 12:39:04 2007 ... TSA kernel: [ 1031.857127]c15f8360 c15e5960 c15e56e0 c15e5640 c15e5980 c16a95e0 c15e58a0 c15e5480 Message from [EMAIL PROTECTED] at Mon Aug 27 12:39:04 2007 ... TSA kernel: [ 1031.857274] [free_hot_cold_page+393/512] free_hot_cold_page+0x189/0x200 Message from [EMAIL PROTECTED] at Mon Aug 27 12:39:04 2007 ... TSA kernel: [ 1031.857235] Call Trace: Message from [EMAIL PROTECTED] at Mon Aug 27 12:39:04 2007 ... TSA kernel: [ 1031.857325] [__pagevec_free+31/48] __pagevec_free+0x1f/0x30 Message from [EMAIL PROTECTED] at Mon Aug 27 12:39:04 2007 ... TSA kernel: [ 1031.857369] [release_pages+390/496] release_pages+0x186/0x1f0 Message from [EMAIL PROTECTED] at Mon Aug 27 12:39:04 2007 ... TSA kernel: [ 1031.858240] [exit_mmap+225/240] exit_mmap+0xe1/0xf0 Message from [EMAIL PROTECTED] at Mon Aug 27 12:39:04 2007 ... TSA kernel: [ 1031.858187] [free_pages_and_swap_cache+116/160] free_pages_and_swap_cache+0x74/0xa0 Message from [EMAIL PROTECTED] at Mon Aug 27 12:39:04 2007 ... TSA kernel: [ 1031.858381] [do_IRQ+64/112] do_IRQ+0x40/0x70 Message from [EMAIL PROTECTED] at Mon Aug 27 12:39:04 2007 ... TSA kernel: [ 1031.858336] [do_exit+289/2128] do_exit+0x121/0x850 Message from [EMAIL PROTECTED] at Mon Aug 27 12:39:04 2007 ... TSA kernel: [ 1031.858429] [do_munmap+390/480] do_munmap+0x186/0x1e0 Message from [EMAIL PROTECTED] at Mon Aug 27 12:39:04 2007 ... TSA kernel: [ 1031.858291] [mmput+56/160] mmput+0x38/0xa0 Message from [EMAIL PROTECTED] at Mon Aug 27 12:39:04 2007 ... TSA kernel: [ 1031.858515] [syscall_call+7/11] syscall_call+0x7/0xb Message from [EMAIL PROTECTED] at Mon Aug 27 12:39:04 2007 ... TSA kernel: [ 1031.858472] [do_group_exit+38/144] do_group_exit+0x26/0x90 Message from [EMAIL PROTECTED] at Mon Aug 27 12:39:04 2007 ... TSA kernel: [ 1031.858567] === Message from [EMAIL PROTECTED] at Mon Aug 27 12:39:04 2007 ... TSA kernel: [ 1031.859129] EIP: [c16a9d20] 0xc16a9d20 SS:ESP 0069:c242be94 Message from [EMAIL PROTECTED] at Mon Aug 27 12:39:04 2007 ... TSA kernel: [ 1031.858597] Code: 00 00 00 d8 3e 6a c1 38 f6 6a c1 6c 08 00 00 02 00 00 00 ff ff ff ff 90 d3 3f c9 34 ff c8 c8 0d 00 00 00 f8 98 6a c1 58 8a 6b c1 00 02 00 00 01 00 00 00 ff ff ff ff f4 95 6a c1 00 00 00 00 a0 ** Affects: xen (Ubuntu) Importance: Undecided Status: New -- xen-image-create fails with kernel panic https://bugs.launchpad.net/bugs/135041 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 134880] ssh xen
Public bug reported: Binary package hint: ubuntu-xen-server I installed Gutsy Tribe 5 Server on a Dual P3 system. SSH connecting to the machine was possible after installing ssh. After installing ubuntu-xen-server and booting into the Xen kernel, ssh stopped working. It just hangs and doesn't give an login prompt. When booting into the standard kernel, ssh works again. It looks like the Xen-kernel somehow interferes with ssh. It cannot be a configuration problem of ssh, cause the only thing that changed was the kernel. SSH into the Xen Kernel: [EMAIL PROTECTED]:~$ ssh -vvv 10.0.0.31 OpenSSH_4.3p2 Debian-8ubuntu1, OpenSSL 0.9.8c 05 Sep 2006 debug1: Reading configuration data /etc/ssh/ssh_config debug1: Applying options for * debug2: ssh_connect: needpriv 0 debug1: Connecting to 10.0.0.31 [10.0.0.31] port 22. debug1: Connection established. debug1: identity file /home/peter/.ssh/identity type -1 debug1: identity file /home/peter/.ssh/id_rsa type -1 debug1: identity file /home/peter/.ssh/id_dsa type -1 ** Affects: xen-meta (Ubuntu) Importance: Undecided Status: New -- ssh xen https://bugs.launchpad.net/bugs/134880 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 134880] Re: ssh xen
After some more testing it looks like the network is failing somehow in the domU. I can't ping other hosts, though I do have a valid IP address and gateway. -- ssh xen https://bugs.launchpad.net/bugs/134880 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 134880] Re: ssh xen
I did indead have that network-bridge thing activated. Looks like the whole network-bridge doesn't work in the xen-kernel of tribe 5. That's quite a major bug I would say... -- ssh xen https://bugs.launchpad.net/bugs/134880 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 71362] Re: Unable to connect to network from Xen Linux
Having the same problem on Gutsy Tribe 5. After booting into the Xen-Kernel can't ping or reach any network address. Quite a big bug I think... -- Unable to connect to network from Xen Linux https://bugs.launchpad.net/bugs/71362 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 71362] Re: Unable to connect to network from Xen Linux
(network-script network-bridge) is enabled by the way. -- Unable to connect to network from Xen Linux https://bugs.launchpad.net/bugs/71362 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 71362] Re: Unable to connect to network from Xen Linux
http://news.gmane.org/find-root.php?message_id=%3cfe9771a80708170311o432fcd35jab5d7e16354c6e1%40mail.gmail.com%3e shows that other users are having the same problem. It also provides a solution, which is referred from the Xen Users Mailing List. From the Xen Users Mailing List: (http://lists.xensource.com/archives/html/xen- users/2006-05/msg00818.html) - That is one bug or resource? It will be corrected? It's a bug. And shortly before 3.0.2 was relesed there were some attempts to fix it. It is intended as an optimisztion, but it failed for some (or IMHO most real world) setups. A solution: I can confirm that disabling tx offloading fixes the problem! For gutsy ( in our case ), just add the following line at the bottom of your /etc/network/interfaces file: up ethtool -K eth0 tx off repeat for every interface ( i only have 1 :) ) Hopes this solves the problem temporarely and I for one hope that a fixed version of Xen will be in Gutsy, otherwise the whole purpose of having Xen in Gutsy is quite defeated. -- Unable to connect to network from Xen Linux https://bugs.launchpad.net/bugs/71362 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 134880] Re: ssh xen
For a solution, see: https://bugs.launchpad.net/bugs/71362 It worked for me. -- ssh xen https://bugs.launchpad.net/bugs/134880 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 74896] Forced bind to 127.0.0.1 is hardcoded' into /etc/default/snmpd instead of option in /etc/snmp/snmpd.conf
Public bug reported: Binary package hint: snmpd I have been struggling to get remote snmp reads from several of my machines. /etc/snmp/snmpd.conf was set up correctly. snmpwalk from localhost did work, a snmpwalk from a remote host however didn't work. After lots of debugging, trying etc. I found out that snmpd binds itself to 127.0.0.1 . Accorder to EVERY faq and manual that I read, the default behaviour of snmpd is to listen on every interface. However, specifying in /etc/snmp/snmpd.conf to force the agent to listen on every socket doesn't work. It crashed the server. It appears that the 127.0.0.1 is hardcoded into /etc/default/snmpd. This script/settings file is used by the /etc/init.d/snmpd init script. The following line is responsible for the 127.0.0.1 bind. SNMPDOPTS='-Lsd -Lf /dev/null -u snmp -I -smux -p /var/run/snmpd.pid 127.0.0.1' After removing the 127.0.0.1 I could finally query the remote machine. Dave Shield, one of the developers of net-snmp, confirmed that this way of starting snmpd indeed binds it to 127.0.0.1 He also confirmed that this is something that probably the Ubuntu Devs changed: It's an defensible configuration, but it's not one that many distributions use. It's certainly not something that we ship ourselves. If it is really necessary to restrict remote snmp acces, I strongly suggest to do this by changing the default configuration of snmpd in /etc/snmp/snmpd.conf by adding: agentaddress 127.0.0.1 This results in the same behaviour as adding the 127.0.0.1 to /etc/default/snmpd This way, users will see that the default option is to bind to 127.0.0.1 and can change this easily. It is very illogical and not user-friendly to expect the user to find out that there is a /etc/defaults/snmpd file that is causing the problem. Since this is a very easy and also elegant way to solve the problem, I really hope this change can be made. It would solve a lot of frustrations for people trying to get snmpd to work. Summary of proposed changes: = /etc/default/snmpd change SNMPDOPTS='-Lsd -Lf /dev/null -u snmp -I -smux -p /var/run/snmpd.pid 127.0.0.1' to SNMPDOPTS='-Lsd -Lf /dev/null -u snmp -I -smux -p /var/run/snmpd.pid' = /etc/snmp/snmpd.conf add agentaddress 127.0.0.1 ** Affects: net-snmp (Ubuntu) Importance: Undecided Status: Unconfirmed -- Forced bind to 127.0.0.1 is hardcoded' into /etc/default/snmpd instead of option in /etc/snmp/snmpd.conf https://launchpad.net/bugs/74896 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 50254] Re: Ctrl-Backspace does not work as expected
I'm so irritated because of this bug. It drives me nut. PLEASE change this, it is a very minor thing, but it's something that is very irritating in daily use. -- Ctrl-Backspace does not work as expected https://launchpad.net/bugs/50254 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 61382] CRC error, not able to boot from md0 (raid)
Public bug reported: I updated yesterday to the latest version of 2.6.15-26-server: 2.6.15-26.47 . When I rebooted today the system didn't boot, but gave a kernel panic: [quote] RAMDISK: Compressed image found at block 0 crc error VFS: cannot open root device md0 or unknown-block(0,0) Please append a correct root= boot option kernel panic - not syncing: VFS: unable to mount root fs on unknown-block(0,0) [/quote] root=/dev/md0 With the other kernel on my system:2-6-15-23 and the same parameters for root etc. The system does boot. So it is not a problem with the syntax in the grub menu entry. It looks like the system can't find the raid md0 drive, possibly doesn't initialize raid properly? This is quite severe, since the only thing I did was sudo apt-get update sudo apt-get dist-upgrade... Fortunately I am running a non-production server, but these things may NEVER occur on a server distro. I reported the bug (60893) and Ben Collins commented: == Looks to me like the initramfs wasn't created correctly. Please boot from an older kernel, and run: sudo update-initramfs -u -k 2.6.15-26-server Make sure this runs without error. Note the message you see in dmesg confirms that the initramfs is not valid. If this appears to be a bug in the creation of this (e.g. not just a failure on the system like running out of disk space), open a target for this bug against initramfs-tools. == The command didn't gave me any errors. I also tried it with the -27 kernel, also no errors with update-initramfs but the same error when booting. FYI: I am booting directly from raid, there is no seperate /boot ext3 partition. ** Affects: initramfs-tools (Ubuntu) Importance: Untriaged Status: Unconfirmed -- CRC error, not able to boot from md0 (raid) https://launchpad.net/bugs/61382 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 61382] Re: CRC error, not able to boot from md0 (raid)
** Description changed: -- CRC error, not able to boot from md0 (raid) https://launchpad.net/bugs/61382 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 61382] Re: CRC error, not able to boot from md0 (raid)
It looks like there are more users experiencing the same problem: See http://ubuntuforums.org/showthread.php?t=259245 -- CRC error, not able to boot from md0 (raid) https://launchpad.net/bugs/61382 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 61382] Re: CRC error, not able to boot from md0 (raid)
Details system: Using GRUB excerpts of menu.lst (1st one doesn't boot, second one does) == title Ubuntu, kernel 2.6.15-26-server root(hd0,0) kernel /boot/vmlinuz-2.6.15-26-server root=/dev/md0 ro quiet splash initrd /boot/initrd.img-2.6.15-26-server savedefault boot [..] title Ubuntu, kernel 2.6.15-23-server root(hd0,0) kernel /boot/vmlinuz-2.6.15-23-server root=/dev/md0 ro quiet splash initrd /boot/initrd.img-2.6.15-23-server savedefault boot === Fstab: == /dev/md0/ reiserfs notail 0 1 /dev/md1/home reiserfs defaults0 2 /dev/md2noneswapsw 0 0 /dev/hdd/media/cdrom0 udf,iso9660 user,noauto 0 0 /dev/fd0/media/floppy0 autorw,user,noauto 0 0 === Diskspace: /dev/md0 19G 728M 18G 4% / varrun506M 72K 506M 1% /var/run varlock 506M 4.0K 506M 1% /var/lock udev 506M 72K 506M 1% /dev devshm506M 0 506M 0% /dev/shm /dev/md1 18G 4.8G 13G 27% /home mem: 1 GB (2x512) -- CRC error, not able to boot from md0 (raid) https://launchpad.net/bugs/61382 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 61214] dpkg: parse error, in file `/var/lib/dpkg/status' near line 660 package `procps'
Public bug reported: Binary package hint: procps I did a sudo apt-get dist-upgrade on Ubuntu Server. It downloaded everything but stopped immediately after that: dpkg: parse error, in file `/var/lib/dpkg/status' near line 660 package `procps' : field name `Installre' must be followed by colon E: Sub-process /usr/bin/dpkg returned an error code (2) This package is broken and blocks the update of the new kernel etc. ** Affects: procps (Ubuntu) Importance: Untriaged Status: Unconfirmed -- dpkg: parse error, in file `/var/lib/dpkg/status' near line 660 package `procps' https://launchpad.net/bugs/61214 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 61214] Re: dpkg: parse error, in file `/var/lib/dpkg/status' near line 660 package `procps'
Version that gives the error: procps 1:3.2.6-2ubuntu4 -- dpkg: parse error, in file `/var/lib/dpkg/status' near line 660 package `procps' https://launchpad.net/bugs/61214 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 61214] Re: procps deb package broken!
** Summary changed: - dpkg: parse error, in file `/var/lib/dpkg/status' near line 660 package `procps' + procps deb package broken! ** Description changed: Binary package hint: procps I did a sudo apt-get dist-upgrade on Ubuntu Server. It downloaded everything but stopped immediately after that: dpkg: parse error, in file `/var/lib/dpkg/status' near line 660 package `procps' : field name `Installre' must be followed by colon E: Sub-process /usr/bin/dpkg returned an error code (2) - This package is broken and blocks the update of the new kernel etc. + This package is broken and blocks the update of the new kernel and any + package I want to install -- procps deb package broken! https://launchpad.net/bugs/61214 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 60893] Server Kernel update (47) prevents booting!
Public bug reported: Binary package hint: linux-image-2.6.15-26-server I updated yesterday to the latest version of 2.6.15-26-server: 2.6.15-26.47 . When I rebooted today the system didn't boot, but gave a kernel panic: [quote] RAMDISK: Compressed image found at block 0 crc error VFS: cannot open root device md0 or unknown-block(0,0) Please append a correct root= boot option kernel panic - not syncing: VFS: unable to mount root fs on unknown-block(0,0) [/quote] root=/dev/md0 With the other kernel on my system:2-6-15-23 and the same parameters for root etc. The system does boot. So it is not a problem with the syntax in the grub menu entry. It looks like the system can't find the raid md0 drive, possibly doesn't initialize raid properly? This is quite severe, since the only thing I did was sudo apt-get update sudo apt-get dist-upgrade... Fortunately I am running a non-production server, but these things may NEVER occur on a server distro. ** Affects: linux-source-2.6.15 (Ubuntu) Importance: Untriaged Status: Unconfirmed -- Server Kernel update (47) prevents booting! https://launchpad.net/bugs/60893 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 56053] Re: Can't boot using linux-image-2.6.15-26-server
Can't you boot into recovery mode? If you press ESC during the few seconds that Grub allows you to, you can choose a kernel and if you choose recovery mode, it gives you more output. -- Can't boot using linux-image-2.6.15-26-server https://launchpad.net/bugs/56053 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
