[Bug 1877523] [NEW] Failed to upgrade to 20.04 because os mirrors non-response
Public bug reported: See attached ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: ubuntu-release-upgrader-core 1:19.10.15.4 ProcVersionSignature: Ubuntu 5.3.0-51.44-generic 5.3.18 Uname: Linux 5.3.0-51-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu8.8 Architecture: amd64 CrashDB: ubuntu Date: Fri May 8 09:56:07 2020 InstallationDate: Installed on 2020-02-20 (77 days ago) InstallationMedia: Ubuntu-MATE 19.10 "Eoan Ermine" - Release amd64 (20191017) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader UpgradeStatus: Upgraded to eoan on 2020-05-08 (0 days ago) VarLogDistupgradeAptlog: Log time: 2020-05-08 09:51:11.099056 Log time: 2020-05-08 09:51:33.449238 Log time: 2020-05-08 09:55:54.675415 Log time: 2020-05-08 09:56:10.445232 VarLogDistupgradeTermlog: ** Affects: ubuntu-release-upgrader (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug dist-upgrade eoan -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1877523 Title: Failed to upgrade to 20.04 because os mirrors non-response To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1877523/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1550950] Re: package openjdk-9-jdk 9~b102-1 failed to install/upgrade: trying to overwrite '/usr/lib/jvm/java-9-openjdk-amd64/include/linux/jawt_md.h', which is also in package openjdk-9-jdk-head
I can confirm that the askubuntu link on #25 worked; but shouldn't this be in a better state now that it is no longer pre-release? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1550950 Title: package openjdk-9-jdk 9~b102-1 failed to install/upgrade: trying to overwrite '/usr/lib/jvm/java-9-openjdk-amd64/include/linux/jawt_md.h', which is also in package openjdk-9-jdk-headless:amd64 9~b107-0ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1550950/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1730030] [NEW] virtualbox-dkms 5.0.40-dfsg-0ubuntu1.16.04.1: virtualbox kernel module failed to build. This occurred when trying to install the hwe-edge kernel. I believe I'll just remove virtual
Public bug reported: This occurred when trying to install the hwe-edge kernel. I believe I'll just remove virtualbox for now. This is likely the fault of virtualbox not supporting this kernel, but figured I'd make it known. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: virtualbox-dkms 5.0.40-dfsg-0ubuntu1.16.04.1 ProcVersionSignature: Ubuntu 4.10.0-38.42~16.04.1-generic 4.10.17 Uname: Linux 4.10.0-38-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 DKMSKernelVersion: 4.13.0-16-generic Date: Fri Nov 3 21:46:44 2017 DuplicateSignature: dkms:virtualbox-dkms:5.0.40-dfsg-0ubuntu1.16.04.1:/var/lib/dkms/virtualbox/5.0.40/build/vboxdrv/r0drv/linux/the-linux-kernel.h:313:47: error: implicit declaration of function ‘set_pages_x’ [-Werror=implicit-function-declaration] InstallationDate: Installed on 2017-08-04 (92 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) PackageArchitecture: all PackageVersion: 5.0.40-dfsg-0ubuntu1.16.04.1 RelatedPackageVersions: dpkg 1.18.4ubuntu1.2 apt 1.2.24 SourcePackage: virtualbox Title: virtualbox-dkms 5.0.40-dfsg-0ubuntu1.16.04.1: virtualbox kernel module failed to build UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: virtualbox (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1730030 Title: virtualbox-dkms 5.0.40-dfsg-0ubuntu1.16.04.1: virtualbox kernel module failed to build. This occurred when trying to install the hwe-edge kernel. I believe I'll just remove virtualbox for now. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/virtualbox/+bug/1730030/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1599884] [NEW] package roundcube-core 1.2~beta+dfsg.1-0ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
Public bug reported: updating from ubuntu 14 to ubuntu 16 (Server) ProblemType: Package DistroRelease: Ubuntu 16.04 Package: roundcube-core 1.2~beta+dfsg.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-52.86-generic 3.13.11-ckt18 Uname: Linux 3.13.0-52-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 Date: Thu Jul 7 15:24:53 2016 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2015-01-03 (550 days ago) InstallationMedia: Ubuntu-Server 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.3) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.12~ubuntu16.04.1 SourcePackage: roundcube Title: package roundcube-core 1.2~beta+dfsg.1-0ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: Upgraded to xenial on 2016-07-07 (0 days ago) ** Affects: roundcube (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1599884 Title: package roundcube-core 1.2~beta+dfsg.1-0ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/roundcube/+bug/1599884/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1423672] Re: ext4_mb_generate_buddy:756: group N, block bitmap and bg descriptor inconsistent: X vs Y
I'm getting this same issue every day 3.2.0-4-amd64 #1 SMP Debian 3.2.68-1+deb7u4 x86_64 GNU/Linux Guest is running under proxmox 3.4 virtio -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1423672 Title: ext4_mb_generate_buddy:756: group N, block bitmap and bg descriptor inconsistent: X vs Y To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1423672/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1317096] [NEW] Mythbuntu during install on 4TB Hitachi drive
Public bug reported: After maybe a minute copying files installation reported an error though it didn't say any more than that. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: ubiquity 2.18.7 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 CasperVersion: 1.340 Date: Wed May 7 14:10:21 2014 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi file=/cdrom/preseed/mythbuntu.seed boot=casper only-ubiquity quiet splash -- LiveMediaBuild: Mythbuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417) ProcEnviron: LANGUAGE=en_GB.UTF-8 TERM=linux PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_GB.UTF-8 SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ubiquity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug mythbuntu trusty ubiquity-2.18.7 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1317096 Title: Mythbuntu during install on 4TB Hitachi drive To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1317096/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 574886] Re: Apt has strange network errors when updating indexes.
I'm having this problem with 12.04, which has been running and updating quite happily for several months. I Eventually applied the workaround described in http://www.linuxquestions.org/questions/linux-newbie-8/apt- get-install-command-is-not-able-to-fetch-packages-from-ubuntu- repositary-806674/, but this is still only a workaround. Some recent update must have changed something and it feels like bug to me. I don't want to get involved in an argument over semantics, but I have a lot of sympathy with Sam Hiatt's last comment, including the one on CLIs and GUIs. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/574886 Title: Apt has strange network errors when updating indexes. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/574886/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 574886] Re: Apt has strange network errors when updating indexes.
Addendum to last comment: For clarity, I should have said that the solution suggested in the link was to set the DNS to 208.67.222.222, 208.67.220.220 directly. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/574886 Title: Apt has strange network errors when updating indexes. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/574886/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1063176] [NEW] Shotwell crashes on startup
Public bug reported: I have been using Shotwell on Ubuntu 12.04 sucessfully for some time. However from this morning it crashes each time I try to start it. When I run it from the command line I get the following error: ERROR:/build/buildd/shotwell-0.12.3/src/Tombstone.vala:38:tombstone_source_collection_real_notify_contents_altered: assertion failed: (_tmp29_) Aborted (core dumped) This happened after I installed Raw Therapee from the Ubuntu software centre. I have now removed Raw Therapee and rebooted but Shotwell continues to crash. ** Affects: shotwell (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1063176 Title: Shotwell crashes on startup To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shotwell/+bug/1063176/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 959722] Re: qtcreator crashes when creating new project
I am getting FIXME: handle dialog start and FIXME: handle dialog end as part of the (debug) console output when running a Qt GUI application I am developing. They seem to appear in pairs and to be benign in that they program behaves as expected and doesn't crash. It looks as though they may simply appear whenever a dialog is opened or closed, but there's no other information to indicate whether there's an issue I should investigate or it's just a bit of stray Qt debugging information. I recently upgraded to Ubuntu 12.04 and Qt 4.8.0 (Qt Creator 2.4.1) and the message did not appear before the upgrade. I am not using accessibility features, qtiplot, or Clementine music player. -- You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to qtcreator in Ubuntu. https://bugs.launchpad.net/bugs/959722 Title: qtcreator crashes when creating new project To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtcreator/+bug/959722/+subscriptions -- kubuntu-bugs mailing list kubuntu-b...@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 609625] Re: kexec-tools 0_kdump
I'd certainly be willing to resolve this issue and provide patches to do so if I knew that someone with developer access had the ability to actually verify they are reasonable patches. I'd hate to provide a fix for this to a bot. -- You received this bug notification because you are a member of Ubuntu Server Team, which is a direct subscriber. https://bugs.launchpad.net/bugs/609625 Title: kexec-tools 0_kdump -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 609625] Re: kexec-tools 0_kdump
I'd certainly be willing to resolve this issue and provide patches to do so if I knew that someone with developer access had the ability to actually verify they are reasonable patches. I'd hate to provide a fix for this to a bot. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/609625 Title: kexec-tools 0_kdump -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 609625] Re: kexec-tools 0_kdump
I agree I think its important to have for server and clustered environments. I'd like to see this fixed and I've done some of the fixing and gave patches. However, seems no one on the Ubuntu side thinks its that important I guess. Thanks, - David Brown On Sat, Mar 12, 2011 at 11:21 AM, Dominik 609...@bugs.launchpad.net wrote: Is there a chance to escalate this? On productional server systems the need for an automatic kernel crash dump is IMO a must have. Enterprise grade Linux distributions like SLES and RHEL have this ready and working. What about the LTS Ubuntu-Server system? Isn't this targeted for enterprise? -- You received this bug notification because you are a direct subscriber of the bug. https://bugs.launchpad.net/bugs/609625 Title: kexec-tools 0_kdump To unsubscribe from this bug, go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/609625/+subscribe -- You received this bug notification because you are a member of Ubuntu Server Team, which is a direct subscriber. https://bugs.launchpad.net/bugs/609625 Title: kexec-tools 0_kdump -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
Re: [Bug 609625] Re: kexec-tools 0_kdump
I agree I think its important to have for server and clustered environments. I'd like to see this fixed and I've done some of the fixing and gave patches. However, seems no one on the Ubuntu side thinks its that important I guess. Thanks, - David Brown On Sat, Mar 12, 2011 at 11:21 AM, Dominik 609...@bugs.launchpad.net wrote: Is there a chance to escalate this? On productional server systems the need for an automatic kernel crash dump is IMO a must have. Enterprise grade Linux distributions like SLES and RHEL have this ready and working. What about the LTS Ubuntu-Server system? Isn't this targeted for enterprise? -- You received this bug notification because you are a direct subscriber of the bug. https://bugs.launchpad.net/bugs/609625 Title: kexec-tools 0_kdump To unsubscribe from this bug, go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/609625/+subscribe -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/609625 Title: kexec-tools 0_kdump -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 609625] Re: kexec-tools 0_kdump
Any updates on this one? -- kexec-tools 0_kdump https://bugs.launchpad.net/bugs/609625 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 609625] Re: kexec-tools 0_kdump
Sorry for taking a while to get back to this. So interestingly the mainline kernel builds you posted don't have vmcoreinfo files to allow the kdump initscript to run properly. So, what do we do next? -- kexec-tools 0_kdump https://bugs.launchpad.net/bugs/609625 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 609625] Re: kexec-tools 0_kdump
So I'm not sure how a scripting error in 0_kdump needs to be tested with the mainline kernel vs the ubuntu provided kernel. But I can do this if need be. Thanks, - David Brown On Mon, Jul 26, 2010 at 10:18 AM, Jeremy Foshee 609...@bugs.launchpad.net wrote: Hi David, If you could also please test the latest upstream kernel available that would be great. It will allow additional upstream developers to examine the issue. Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag. This can be done by clicking on the yellow pencil icon next to the tag located at the bottom of the bug description and deleting the 'needs-upstream-testing' text. Please let us know your results. Thanks in advance. [This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.] ** Tags added: kj-triage ** Changed in: linux (Ubuntu) Status: New = Incomplete -- kexec-tools 0_kdump https://bugs.launchpad.net/bugs/609625 You received this bug notification because you are a direct subscriber of the bug. -- kexec-tools 0_kdump https://bugs.launchpad.net/bugs/609625 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 609625] [NEW] kexec-tools 0_kdump
Public bug reported: So in my effort to debug issues with suspend/resume on my dell laptop I wanted to enable kernel kexec style crash dumps. I found some information on the ubuntu wiki about using linux-crashdump package to set this up. However, my laptop has an encrypted root hard drive and thus needs a separate partition for /boot that is un-encrypted. There's a couple of files installed by kexec-tools to help support the kexec style of crash dump capture. /usr/share/initramfs-tools/scripts/init-bottom/0_kdump is the script that supports kdump and I think there's a couple of issues with it especially in the failure conditions where the tests fail. The initial part of the script looks like this: KVER=`uname -r` INFO=$rootmnt/boot/vmcoreinfo-$KVER CRASHFILE=$rootmnt/var/crash/vmcore MAKEDUMPFILE=$rootmnt/usr/bin/makedumpfile LOG=$rootmnt/var/crash/vmcore.log VMCORE=/proc/vmcore # Check that this is a kexec kernel. grep -q kdump_needed /proc/cmdline || exit 0 # Make sure makedumpfile assumptions are satisfied. test -e $INFO || exit 0 test -x $MAKEDUMPFILE || exit 0 . ./scripts/functions log_begin_msg Saving vmcore from kernel crash mount $rootmnt -o remount,rw There's a couple of issues to get past all the exit zeros. If you have a separate /boot partition it need to be mounted before checking the existence of the vmcoreinfo file for the running kernel. The second is since this failed it continued in the boot process trying to start the rest of the system normally in the 128M I gave the crash kernel environment to use. This confused me for some time. I would recommend changing at least the checks to something as follows. if grep -q kdump_needed /proc/cmdline ; then # we are in a crash dump environment and need to reboot if we can't capture anything test -e $INFO || /sbin/reboot test -x $MAKEDUMPFILE || /sbin/reboot else exit 0 fi . ./scripts/functions log_begin_msg Saving vmcore from kernel crash mount $rootmnt -o remount,rw ... ... This would cause the system to reboot instead of continuing with the boot process in the case where makedumpfile isn't there. Second is the need for the vmcoreinfo file for that kernel. I would recommend copying it into the initramfs instead of trying to mount more than just root. Either would be a workable solution though. My work around was to add a copy_exec /boot/vmcoreinfo-`uname -r` /boot to the makedumpfile initramfs hook. This copied the 1.4k file into the 15Mb initrd so it wasn't that big of an addition. ProblemType: Bug DistroRelease: Ubuntu 10.04 Package: linux-crashdump 2.6.32.24.25 Regression: No Reproducible: Yes ProcVersionSignature: Ubuntu 2.6.32-24.38-generic 2.6.32.15+drm33.5 Uname: Linux 2.6.32-24-generic x86_64 AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.21. Architecture: amd64 ArecordDevices: List of CAPTURE Hardware Devices card 0: Intel [HDA Intel], device 0: STAC92xx Analog [STAC92xx Analog] Subdevices: 2/2 Subdevice #0: subdevice #0 Subdevice #1: subdevice #1 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: dmlb2000 2170 F pulseaudio CRDA: Error: [Errno 2] No such file or directory Card0.Amixer.info: Card hw:0 'Intel'/'HDA Intel at 0xf546 irq 22' Mixer name : 'Intel G45 DEVIBX' Components : 'HDA:111d7605,10280410,00100104 HDA:80862804,80860101,0010' Controls : 22 Simple ctrls : 13 Date: Sat Jul 24 17:19:14 2010 HibernationDevice: RESUME=UUID=414ecb0b-22be-4d37-b67c-918da7f2014b InstallationMedia: Ubuntu 10.04 LTS Lucid Lynx - Release amd64 (20100427.1) Lsusb: Bus 002 Device 003: ID 0a5c:5800 Broadcom Corp. BCM5880 Secure Applications Processor Bus 002 Device 002: ID 8087:0020 Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 002: ID 8087:0020 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Latitude E4310 ProcCmdLine: BOOT_IMAGE=/vmlinuz-2.6.32-24-generic root=/dev/mapper/dmlb2010--lappy-root ro crashkernel=384M-2G:64M,2G-:128M quiet splash ProcEnviron: PATH=(custom, user) LANG=en_US.utf8 SHELL=/bin/bash RelatedPackageVersions: linux-firmware 1.34.1 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux dmi.bios.date: 05/28/2010 dmi.bios.vendor: Dell Inc. dmi.bios.version: A02 dmi.board.name: 04FFNC dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA02:bd05/28/2010:svnDellInc.:pnLatitudeE4310:pvr0001:rvnDellInc.:rn04FFNC:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E4310 dmi.product.version: 0001 dmi.sys.vendor: Dell Inc. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug lucid needs-upstream-testing -- kexec-tools 0_kdump https://bugs.launchpad.net/bugs/609625 You received this bug notification because you are a member of Ubuntu Bugs, which
[Bug 609625] Re: kexec-tools 0_kdump
** Attachment added: AlsaDevices.txt http://launchpadlibrarian.net/52458612/AlsaDevices.txt ** Attachment added: AplayDevices.txt http://launchpadlibrarian.net/52458613/AplayDevices.txt ** Attachment added: BootDmesg.txt http://launchpadlibrarian.net/52458614/BootDmesg.txt ** Attachment added: Card0.Amixer.values.txt http://launchpadlibrarian.net/52458615/Card0.Amixer.values.txt ** Attachment added: Card0.Codecs.codec.0.txt http://launchpadlibrarian.net/52458616/Card0.Codecs.codec.0.txt ** Attachment added: Card0.Codecs.codec.3.txt http://launchpadlibrarian.net/52458617/Card0.Codecs.codec.3.txt ** Attachment added: CurrentDmesg.txt http://launchpadlibrarian.net/52458618/CurrentDmesg.txt ** Attachment added: Dependencies.txt http://launchpadlibrarian.net/52458619/Dependencies.txt ** Attachment added: IwConfig.txt http://launchpadlibrarian.net/52458620/IwConfig.txt ** Attachment added: Lspci.txt http://launchpadlibrarian.net/52458621/Lspci.txt ** Attachment added: PciMultimedia.txt http://launchpadlibrarian.net/52458622/PciMultimedia.txt ** Attachment added: ProcCpuinfo.txt http://launchpadlibrarian.net/52458623/ProcCpuinfo.txt ** Attachment added: ProcInterrupts.txt http://launchpadlibrarian.net/52458624/ProcInterrupts.txt ** Attachment added: ProcModules.txt http://launchpadlibrarian.net/52458625/ProcModules.txt ** Attachment added: UdevDb.txt http://launchpadlibrarian.net/52458626/UdevDb.txt ** Attachment added: UdevLog.txt http://launchpadlibrarian.net/52458627/UdevLog.txt ** Attachment added: WifiSyslog.txt http://launchpadlibrarian.net/52458628/WifiSyslog.txt -- kexec-tools 0_kdump https://bugs.launchpad.net/bugs/609625 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 494815] [NEW] depends on python-tegaki, which is not available
Public bug reported: This package cannot be installed because python-tegaki is not in any of the repos. ** Affects: tegaki-pygtk (Ubuntu) Importance: Undecided Status: New -- depends on python-tegaki, which is not available https://bugs.launchpad.net/bugs/494815 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 455067] Re: [113818.216022] BUG: scheduling while atomic: dosemu.bin/12814/0x10000004
Uhm the patch you posted here doesn't make a lot of sense. This would have been on Karmic and its 2.6.31 based and the patch was applied to 2.6.29-rc1. Also, I verified that its contained in the source when I pull do an apt-get source linux-image-2.6.31-14-generic. So I'm unsure how I'm supposed to try that patch. -- [113818.216022] BUG: scheduling while atomic: dosemu.bin/12814/0x1004 https://bugs.launchpad.net/bugs/455067 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 461678] [NEW] grub-pc Xen dom0 support
*** This bug is a duplicate of bug 216176 ***
https://bugs.launchpad.net/bugs/216176
Public bug reported:
Binary package hint: grub-pc
Okay I know I'm a crazy person for trying this stuff out but I was
curious.
I'm attempting to boot Xen 3.5 unstable with a vanilla 2.6.31.4 with the
xen-pv ops dom0 support enabled.
I started by following instructions found here:
http://wiki.xensource.com/xenwiki/XenParavirtOps
Everything compiled fine but this isn't what the bug is about. For some
reason grub-pc on amd64 seems to strip out the root= commandline
argument to the kernel when loading it after xen.
GRUB-PC CONFIG
r...@uber-gamer:~# cat /etc/grub.d/40_custom
#!/bin/sh
exec tail -n +3 $0
# This file provides an easy way to add custom menu entries. Simply type the
# menu entries you want to add after this comment. Be careful not to change
# the 'exec tail' line above.
menuentry Xen 3.5 / Ubuntu, kernel 2.6.31.4-1-xen {
recordfail=1
if [ -n ${have_grubenv} ]; then save_env recordfail; fi
set quiet=1
insmod ext2
set root=(hd0,1)
search --no-floppy --fs-uuid --set 41102bda-f368-45b9-8066-fa971325b228
multiboot /xen-3.5-unstable.gz
module /vmlinuz-2.6.31.4-1-xen root=/dev/mapper/vg0-root ro quiet splash
module /initrd.img-2.6.31.4-1-xen
}
r...@uber-gamer:~#
===
After booting it eventually drops to the initramfs busybox shell and I
attempt to cat /proc/cmdline and it shows only ro quiet splash somehow
the root= got stripped out. I'm guessing grub-pc did this, since I'm
able to use the exact same kernel and initrd to boot without Xen (since
that works now too) and it didn't happen.
Some of the google searches on grub2 xen mention not having the
multiboot option completed yet. However, the dates were all the way back
in February.
Here's more stuff just in case you want it:
# lsb_release -rd
Description:Ubuntu 9.10
Release:9.10
# apt-cache policy grub-pc
grub-pc:
Installed: 1.97~beta4-1ubuntu3
Candidate: 1.97~beta4-1ubuntu3
Version table:
*** 1.97~beta4-1ubuntu3 0
500 http://mirrors.kernel.org karmic/main Packages
500 http://us.archive.ubuntu.com karmic/main Packages
100 /var/lib/dpkg/status
1.96+20080724-12ubuntu2 0
500 http://mirrors.kernel.org jaunty/main Packages
500 http://us.archive.ubuntu.com jaunty/main Packages
#
This bug isn't a big deal but I thought I'd mention it since you guys
are moving to grub-pc on amd64 systems.
** Affects: grub2 (Ubuntu)
Importance: Undecided
Status: New
--
grub-pc Xen dom0 support
https://bugs.launchpad.net/bugs/461678
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 461678] Re: grub-pc Xen dom0 support
*** This bug is a duplicate of bug 216176 *** https://bugs.launchpad.net/bugs/216176 Oopse this maybe a duplicate of what's going on in bug 216176 ** This bug has been marked a duplicate of bug 216176 Xen entries not working under grub2 -- grub-pc Xen dom0 support https://bugs.launchpad.net/bugs/461678 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 455067] Re: [113818.216022] BUG: scheduling while atomic: dosemu.bin/12814/0x10000004
didn't see a dmesg output log. so I'm posting one just in case. ** Attachment added: dmesg.log http://launchpadlibrarian.net/33919873/dmesg.log -- [113818.216022] BUG: scheduling while atomic: dosemu.bin/12814/0x1004 https://bugs.launchpad.net/bugs/455067 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 455067] [NEW] [113818.216022] BUG: scheduling while atomic: dosemu.bin/12814/0x10000004
Public bug reported: hmmm it was interesting never thought my dosemu would kill the kernel ProblemType: KernelOops Annotation: Your system might become unstable now and might need to be restarted. Architecture: i386 ArecordDevices: List of CAPTURE Hardware Devices card 0: Intel [HDA Intel], device 0: STAC92xx Analog [STAC92xx Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: dmlb2000 2287 F...m pulseaudio /dev/snd/controlC0: dmlb2000 2287 F pulseaudio CRDA: Error: [Errno 2] No such file or directory Card0.Amixer.info: Card hw:0 'Intel'/'HDA Intel at 0xefebc000 irq 21' Mixer name : 'SigmaTel STAC9200' Components : 'HDA:83847690,102801d6,00102201 HDA:14f12bfa,14f100c3,0009' Controls : 12 Simple ctrls : 7 Date: Sun Oct 18 17:15:19 2009 DistroRelease: Ubuntu 9.10 Failure: oops MachineType: Dell Inc. Latitude D420 OopsText: [113818.216022] BUG: scheduling while atomic: dosemu.bin/12814/0x1004 [113818.216033] Modules linked in: tun binfmt_misc ipt_MASQUERADE iptable_nat nf_nat nf_conntrack_ipv4 nf_defrag_ipv4 xt_state nf_conntrack ipt_REJECT xt_tcpudp bridge stp ppdev kvm_intel kvm snd_hda_codec_idt snd_hda_intel snd_hda_codec snd_hwdep snd_pcm_oss snd_mixer_oss snd_pcm snd_seq_dummy snd_seq_oss snd_seq_midi snd_rawmidi snd_seq_midi_event arc4 pcmcia snd_seq ecb yenta_socket snd_timer rsrc_nonstatic iwl3945 snd_seq_device pcmcia_core sdhci_pci iwlcore sdhci snd joydev mac80211 soundcore led_class snd_page_alloc cfg80211 psmouse dell_wmi serio_raw dell_laptop iptable_filter ip_tables lp dcdbas parport irda x_tables crc_ccitt sha256_generic aes_i586 aes_generic cbc dm_crypt fbcon tileblit font bitblit softcursor i915 drm i2c_algo_bit ohci1394 ieee1394 video output intel_agp agpgart tg3 [113818.216224] Pid: 12814, comm: dosemu.bin Not tainted 2.6.31-14-generic #48-Ubuntu [113818.216234] Call Trace: Package: linux-image-2.6.31-14-generic 2.6.31-14.48 PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcCmdLine: root=/dev/mapper/dmlb2010--lappy-root ro quiet splash ProcVersionSignature: Ubuntu 2.6.31-14.48-generic RelatedPackageVersions: linux-backports-modules-2.6.31-14-generic N/A linux-firmware 1.23 SourcePackage: linux Tags: kernel-oops Title: [113818.216022] BUG: scheduling while atomic: dosemu.bin/12814/0x1004 Uname: Linux 2.6.31-14-generic i686 WpaSupplicantLog: dmi.bios.date: 02/02/2008 dmi.bios.vendor: Dell Inc. dmi.bios.version: A06 dmi.board.name: 0XJ578 dmi.board.vendor: Dell Inc. dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA06:bd02/02/2008:svnDellInc.:pnLatitudeD420:pvr:rvnDellInc.:rn0XJ578:rvr:cvnDellInc.:ct8:cvr: dmi.product.name: Latitude D420 dmi.sys.vendor: Dell Inc. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: apport-kerneloops i386 kernel-oops -- [113818.216022] BUG: scheduling while atomic: dosemu.bin/12814/0x1004 https://bugs.launchpad.net/bugs/455067 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 455067] Re: [113818.216022] BUG: scheduling while atomic: dosemu.bin/12814/0x10000004
** Attachment added: AlsaDevices.txt http://launchpadlibrarian.net/33919820/AlsaDevices.txt ** Attachment added: AplayDevices.txt http://launchpadlibrarian.net/33919821/AplayDevices.txt ** Attachment added: BootDmesg.txt http://launchpadlibrarian.net/33919822/BootDmesg.txt ** Attachment added: Card0.Amixer.values.txt http://launchpadlibrarian.net/33919823/Card0.Amixer.values.txt ** Attachment added: Card0.Codecs.codec.0.txt http://launchpadlibrarian.net/33919824/Card0.Codecs.codec.0.txt ** Attachment added: Card0.Codecs.codec.1.txt http://launchpadlibrarian.net/33919825/Card0.Codecs.codec.1.txt ** Attachment added: CurrentDmesg.txt http://launchpadlibrarian.net/33919826/CurrentDmesg.txt ** Attachment added: Dependencies.txt http://launchpadlibrarian.net/33919827/Dependencies.txt ** Attachment added: IwConfig.txt http://launchpadlibrarian.net/33919828/IwConfig.txt ** Attachment added: Lspci.txt http://launchpadlibrarian.net/33919829/Lspci.txt ** Attachment added: Lsusb.txt http://launchpadlibrarian.net/33919830/Lsusb.txt ** Attachment added: PciMultimedia.txt http://launchpadlibrarian.net/33919831/PciMultimedia.txt ** Attachment added: ProcCpuinfo.txt http://launchpadlibrarian.net/33919832/ProcCpuinfo.txt ** Attachment added: ProcInterrupts.txt http://launchpadlibrarian.net/33919833/ProcInterrupts.txt ** Attachment added: ProcModules.txt http://launchpadlibrarian.net/33919834/ProcModules.txt ** Attachment added: RfKill.txt http://launchpadlibrarian.net/33919835/RfKill.txt ** Attachment added: UdevDb.txt http://launchpadlibrarian.net/33919836/UdevDb.txt ** Attachment added: UdevLog.txt http://launchpadlibrarian.net/33919837/UdevLog.txt ** Attachment added: WifiSyslog.txt http://launchpadlibrarian.net/33919838/WifiSyslog.txt -- [113818.216022] BUG: scheduling while atomic: dosemu.bin/12814/0x1004 https://bugs.launchpad.net/bugs/455067 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 455067] Re: [113818.216022] BUG: scheduling while atomic: dosemu.bin/12814/0x10000004
And that post seemed rather useless. So here's all of messages file ** Attachment added: messages http://launchpadlibrarian.net/33919971/messages -- [113818.216022] BUG: scheduling while atomic: dosemu.bin/12814/0x1004 https://bugs.launchpad.net/bugs/455067 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 333632] [NEW] can't build on i686
Public bug reported: r...@dmlb2010-lappy:/usr/src/kvm-84# lsb_release -rd Description:Ubuntu jaunty (development branch) Release:9.04 r...@dmlb2010-lappy:/usr/src/kvm-84# r...@dmlb2010-lappy:/usr/src/kvm-84# apt-cache policy kvm-source kvm-source: Installed: 1:84+dfsg-0ubuntu3 Candidate: 1:84+dfsg-0ubuntu3 Version table: *** 1:84+dfsg-0ubuntu3 0 500 http://archive.ubuntu.com jaunty/universe Packages 100 /var/lib/dpkg/status 1:83+dfsg-0ubuntu1 0 500 http://mirror.emsl.pnl.gov jaunty/universe Packages r...@dmlb2010-lappy:/usr/src/kvm-84# r...@dmlb2010-lappy:~# apt-get install kvm-source Reading package lists... Done Building dependency tree Reading state information... Done kvm-source is already the newest version. The following packages were automatically installed and are no longer required: libartsc0 libportaudio0 libxml-namespacesupport-perl libhtml-template-perl libdns43 libxml-sax-expat-perl libgpod3 libmono-system1.0-cil libxml-sax-perl libxml-simple-perl libartsc0-dev libisc44 Use 'apt-get autoremove' to remove them. 0 upgraded, 0 newly installed, 0 to remove and 1 not upgraded. 1 not fully installed or removed. After this operation, 0B of additional disk space will be used. Setting up kvm-source (1:84+dfsg-0ubuntu3) ... Creating symlink /var/lib/dkms/kvm/84/source - /usr/src/kvm-84 DKMS: add Completed. Kernel preparation unnecessary for this kernel. Skipping... Building module: cleaning build area(bad exit status: 2) make KERNELRELEASE=2.6.28-8-generic KERNELDIR=/lib/modules/2.6.28-8-generic/build(bad exit status: 2) Error! Bad return status for module build on kernel: 2.6.28-8-generic (i686) Consult the make.log in the build directory /var/lib/dkms/kvm/84/build/ for more information. 0 0 dpkg: error processing kvm-source (--configure): subprocess post-installation script returned error exit status 10 Errors were encountered while processing: kvm-source E: Sub-process /usr/bin/dpkg returned an error code (1) What I expected was dpkg to not return an error, so I think it may be doing a 'dkms build -m kvm -v 84' I go in and apply this patch: since uname -r on i386 machine returns i686 not i386 == --- Makefile.orig 2009-02-23 17:22:58.0 -0800 +++ Makefile2009-02-23 17:23:07.0 -0800 @@ -1,7 +1,7 @@ include config.kbuild ARCH=$(shell uname -m) -ARCH_DIR = $(if $(filter $(ARCH),x86_64 i386),x86,$(ARCH)) +ARCH_DIR = $(if $(filter $(ARCH),x86_64 i686),x86,$(ARCH)) ARCH_CONFIG := $(shell echo $(ARCH_DIR) | tr '[:lower:]' '[:upper:]') # NONARCH_CONFIG used for unifdef, and only cover X86 and IA64 now NONARCH_CONFIG = $(filter-out $(ARCH_CONFIG),X86 IA64) == then r...@dmlb2010-lappy:/usr/src/kvm-84# dkms build -m kvm -v 84 Kernel preparation unnecessary for this kernel. Skipping... Building module: cleaning build area make KERNELRELEASE=2.6.28-8-generic KERNELDIR=/lib/modules/2.6.28-8-generic/build.. cleaning build area DKMS: build Completed. ** Affects: kvm (Ubuntu) Importance: Undecided Status: New -- can't build on i686 https://bugs.launchpad.net/bugs/333632 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 312080] Re: xserver-org-video-vmware border rendering problems
** Attachment added: lspci -vvnn output http://launchpadlibrarian.net/21060186/lspciout -- xserver-org-video-vmware border rendering problems https://bugs.launchpad.net/bugs/312080 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 312080] Re: xserver-org-video-vmware border rendering problems
** Attachment added: Xorg.0.log http://launchpadlibrarian.net/21060211/Xorg.0.log -- xserver-org-video-vmware border rendering problems https://bugs.launchpad.net/bugs/312080 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 312080] Re: xserver-org-video-vmware border rendering problems
This particular /etc/X11/xorg.conf has been modified from the default vmware-tools installed version, by adding the higher resolution of my display. However, the problem occurs on other images that have not been modified. ** Attachment added: xorg.conf http://launchpadlibrarian.net/21060240/xorg.conf -- xserver-org-video-vmware border rendering problems https://bugs.launchpad.net/bugs/312080 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 312080] Re: xserver-org-video-vmware border rendering problems
Reattaching, after running as root. ** Attachment added: lspciout http://launchpadlibrarian.net/21060264/lspciout -- xserver-org-video-vmware border rendering problems https://bugs.launchpad.net/bugs/312080 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 312080] [NEW] xserver-org-video-vmware border rendering problems
Public bug reported: Binary package hint: xserver-xorg-video-vmware I believe this is the same as this Fedora bug https://bugzilla.redhat.com/show_bug.cgi?id=464031 I'm running VMWare Fusion 2.0.1, but the other user reports this happening on other VMWare systems. Basically, any window manager that uses XSetWindowBorder to draw window decorations (twm, dwm, xmonad) demonstrate rendering errors drawing the window borders. An exaggerated example is at: http://www.davidb.org/img /bad-border.png where, using xmonad, I've set a large border width and moved windows away from the screen. The easiest way to demonstrate the problem is to install twm, and log in with a failsafe login (terminal only) and run twm manually. Fire up a few more xterm windows, and move the mouse between them to show the improperly rendered borders. I am running xserver-xorg-video-vmware 1:10.16.2-1build2 With Ubuntu 8.10 installed from CD image myself into the VMWare machine. ** Affects: xserver-xorg-video-vmware (Ubuntu) Importance: Undecided Status: New -- xserver-org-video-vmware border rendering problems https://bugs.launchpad.net/bugs/312080 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 312080] Re: xserver-org-video-vmware border rendering problems
** Attachment added: Image capture of rendering error. http://launchpadlibrarian.net/20789437/bad-border.png -- xserver-org-video-vmware border rendering problems https://bugs.launchpad.net/bugs/312080 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 196013] [NEW] A+ crashes on start in x86-64
/lib/libnss_files-2.6.1.so 2b081000-2b0810021000 rw-p 2b081000 00:00 0 2b0810021000-2b081400 ---p 2b0810021000 00:00 0 7fffa0d1a000-7fffa0d3c000 rw-p 7fffa0d1a000 00:00 0 [stack] ff60-ff601000 r-xp 00:00 0 [vdso] Process `a' aborted (core dumped) Thus, A+ never starts. David Brown ** Affects: aplus-fsf (Ubuntu) Importance: Undecided Status: New -- A+ crashes on start in x86-64 https://bugs.launchpad.net/bugs/196013 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 107774] Re: Kernel oops with pata_sis
This may only happen on specific sis hardware, specifically mine is an older pentium4 that uses sdram the newer sis motherboards may not have this issue. On 4/29/07, Cheetahcat [EMAIL PROTECTED] wrote: FYI, i did a clean install of Ubuntu 6.10 on my Gericom Frontman Force, then updated 6.10, afterwards did an dist-upgrade to Feisty. Everything works just fine. -- Kernel oops with pata_sis https://bugs.launchpad.net/bugs/107774 You received this bug notification because you are a direct subscriber of the bug. -- Kernel oops with pata_sis https://bugs.launchpad.net/bugs/107774 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 107774] Re: Kernel oops with pata_sis
You could keep the modified initrd just fine, the way I recommended you modify the initrd should keep across upgrades and such. I experienced this bug with 2.6.20-4-386 and 2.6.20-4-generic, which means by 2.6.20-5-386 and 2.6.20-5-generic it should be fixed. However, I'm not an ubuntu kernel guy, just a regular kernel guy so I don't know what sort of distro policies they have in place for releasing important critical parts of a linux system. 2.6.20 in general was a much better release of the linux kernel than most of the other releases (imho), so any continued work on that version of the kernel should only get better. -- Kernel oops with pata_sis https://bugs.launchpad.net/bugs/107774 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 107774] Re: Kernel oops with pata_sis
well the work around while the kernel is getting built is to go in and change the initramfs package to only use the files listed. I don't have an ubuntu box in front of me so bear with me... edit /etc/initramfs-tools/initramfs.conf (??) and switch the first option to list (iirc). Then edit the /etc/initramfs-tools/modules.list file and add the appropriate ide drivers for the root hard drive, remember to include the filesystem drivers as well. I ended up having something like: sis5513 reiserfs ide-core ide-disk generic Then regenerate the initramfs file (mkinitramfs -o /boot/initrd.img-2.6.20-4-386 2.6.20-4-386 mkinitramfs -o /boot/initrd.img-2.6.20-4-generic 2.6.20-4-generic) and I was able to boot just fine, udev didn't even try to autoload the pata driver so you should be good. -- Kernel oops with pata_sis https://bugs.launchpad.net/bugs/107774 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 107774] Re: Kernel oops with pata_sis
Should the pata drivers not be put into the default initramfs then? I had upgrade issues from 6.10 to 7.04 because the initramfs created tried to load this driver and wouldn't ever get to the root hard-drive. When will this be fixed? eta? I'd like to revert the changes I made to the initramfs package so I can use the default configuration again. -- Kernel oops with pata_sis https://bugs.launchpad.net/bugs/107774 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
