[Bug 1720400] Re: /usr/bin/gnome-control-center:11:update_buffers:image_get_buffers:intel_update_image_buffers:intel_update_renderbuffers:intel_prepare_render
Ditto here for PJSingh5000. I had added a google account as well. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1720400 Title: /usr/bin/gnome-control- center:11:update_buffers:image_get_buffers:intel_update_image_buffers:intel_update_renderbuffers:intel_prepare_render To manage notifications about this bug go to: https://bugs.launchpad.net/gtk/+bug/1720400/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1717340] Re: [artful] Keyboard Logitech G15 doesn't work after logging in to gnome
This issue occurs for Logitech Gaming Keyboard G110 as well. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1717340 Title: [artful] Keyboard Logitech G15 doesn't work after logging in to gnome To manage notifications about this bug go to: https://bugs.launchpad.net/fwupd/+bug/1717340/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1566508] Re: autofs races with sssd on startup
Having this problem with freeipa on xenial. ii sssd-ipa 1.13.4-1ubuntu1.8 amd64System Security Services Daemon -- IPA back end --- client side output --- alvinc@ipa-client-02:~$ sudo systemctl restart autofs [sudo] password for alvinc: alvinc@ipa-client-02:~$ sudo ls -Fla /nethome/acura ls: cannot access '/nethome/acura': No such file or directory --- client side syslog --- Oct 10 07:26:45 ipa-client-02 systemd[1]: Stopping LSB: Automounts filesystems on demand... Oct 10 07:26:45 ipa-client-02 autofs[4315]: * Stopping automount... Oct 10 07:26:45 ipa-client-02 autofs[4315]:...done. Oct 10 07:26:45 ipa-client-02 systemd[1]: Stopped LSB: Automounts filesystems on demand. Oct 10 07:26:45 ipa-client-02 systemd[1]: Starting LSB: Automounts filesystems on demand... Oct 10 07:26:45 ipa-client-02 autofs[4322]: * Starting automount... Oct 10 07:26:45 ipa-client-02 automount[4332]: setautomntent: lookup(sss): setautomntent: No such file or directory Oct 10 07:26:45 ipa-client-02 autofs[4322]:...done. Oct 10 07:26:45 ipa-client-02 systemd[1]: Started LSB: Automounts filesystems on demand. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1566508 Title: autofs races with sssd on startup To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sssd/+bug/1566508/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1567116] Re: unity-settings-daemon crashed with SIGSEGV in gsd_power_manager_stop()
Perhaps you might find it in backports. Not sure what has been decided with it, if it goes to updates or backports. On Tue, Sep 20, 2016 at 6:34 AM, Ken Haasewrote: > I can't quite tell from the report page on launchpad, but is this fix > available in Trusty? Are there plans to make it available? > > Thanks! > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1567116 > > Title: > unity-settings-daemon crashed with SIGSEGV in gsd_power_manager_stop() > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/unity-settings- > daemon/+bug/1567116/+subscriptions > -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1567116 Title: unity-settings-daemon crashed with SIGSEGV in gsd_power_manager_stop() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-settings-daemon/+bug/1567116/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1557686] Re: package linux-image-4.4.0-13-generic 4.4.0-13.29 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 2
Post-reboot, "dpkg --configure -a" worked, and I am able to boot and run the new kernel. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1557686 Title: package linux-image-4.4.0-13-generic 4.4.0-13.29 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1557686/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1557686] [NEW] package linux-image-4.4.0-13-generic 4.4.0-13.29 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 2
Public bug reported: During apt-get dist-upgrade, having already been updated to 16.04. Current: 4.2.0-19-generic #23-Ubuntu SMP Wed Nov 11 11:39:30 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux ProblemType: Package DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-13-generic 4.4.0-13.29 ProcVersionSignature: Ubuntu 4.2.0-19.23-generic 4.2.6 Uname: Linux 4.2.0-19-generic x86_64 NonfreeKernelModules: fglrx ApportVersion: 2.20-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC3: alvinc 1927 F pulseaudio /dev/snd/controlC2: alvinc 1927 F pulseaudio /dev/snd/controlC1: alvinc 1927 F pulseaudio /dev/snd/controlC0: alvinc 1927 F pulseaudio Date: Tue Mar 15 10:51:48 2016 ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 2 HibernationDevice: RESUME=UUID=04466c16-d992-47bf-a017-5874ba5a849a InstallationDate: Installed on 2013-11-16 (850 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) IwConfig: eth0 no wireless extensions. lono wireless extensions. MachineType: System manufacturer System Product Name ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-19-generic root=UUID=af24dc68-49e1-4fc0-8a01-9f4bfe3421de ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: grub-pc 2.02~beta2-36 RfKill: SourcePackage: initramfs-tools Title: package linux-image-4.4.0-13-generic 4.4.0-13.29 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 2 UpgradeStatus: Upgraded to xenial on 2015-11-28 (107 days ago) dmi.bios.date: 10/08/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2701 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: M3A78-EM dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2701:bd10/08/2010:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM3A78-EM:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer ** Affects: initramfs-tools (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package need-duplicate-check xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1557686 Title: package linux-image-4.4.0-13-generic 4.4.0-13.29 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1557686/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 139046] Re: no xm console prompt after debootstrap debian or ubuntu
I notice that this bug has not received any attention. It should be noted that I have not seen this bug in jaunty or karmic, and do not recall if I saw it in hardy or intrepid. -- no xm console prompt after debootstrap debian or ubuntu https://bugs.launchpad.net/bugs/139046 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 538917] Re: xen-tools is not available in lucid
Axel, Please let me know how I can help. - alvinc -- xen-tools is not available in lucid https://bugs.launchpad.net/bugs/538917 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 144631] Re: xen guest hangs after mounting filesystem
I am not seeing this problem on Hardy 8.04.3. Can anyone confirm/deny? -- xen guest hangs after mounting filesystem https://bugs.launchpad.net/bugs/144631 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 475784] [NEW] BUG: unable to handle kernel paging request at 4d535f41
Public bug reported: Dell Precision M65 Laptop 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/controlC0: alvinc 1973 F pulseaudio CRDA: Error: [Errno 2] No such file or directory Card0.Amixer.info: Card hw:0 'Intel'/'HDA Intel at 0xefffc000 irq 21' Mixer name : 'SigmaTel STAC9200' Components : 'HDA:83847690,102801c8,00102201' Controls : 12 Simple ctrls : 7 Date: Thu Nov 5 12:09:37 2009 DistroRelease: Ubuntu 9.10 Failure: oops HibernationDevice: RESUME=UUID=1007f0dc-ddf9-4c7e-83a9-651a6c9a4482 InstallationMedia: Ubuntu 9.10 Karmic Koala - Release i386 (20091028.5) MachineType: Dell Inc. Precision M65 NonfreeKernelModules: nvidia 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: BOOT_IMAGE=/boot/vmlinuz-2.6.31-14-generic root=UUID=6997a295-fdce-4e2f-832d-c42a5db98e8a 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.24 SourcePackage: linux Tags: kernel-oops Title: BUG: unable to handle kernel paging request at 4d535f41 Uname: Linux 2.6.31-14-generic i686 dmi.bios.date: 10/13/2006 dmi.bios.vendor: Dell Inc. dmi.bios.version: A05 dmi.board.name: 0JF242 dmi.board.vendor: Dell Inc. dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA05:bd10/13/2006:svnDellInc.:pnPrecisionM65:pvr:rvnDellInc.:rn0JF242:rvr:cvnDellInc.:ct8:cvr: dmi.product.name: Precision M65 dmi.sys.vendor: Dell Inc. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: apport-kerneloops i386 kernel-oops -- BUG: unable to handle kernel paging request at 4d535f41 https://bugs.launchpad.net/bugs/475784 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 475784] Re: BUG: unable to handle kernel paging request at 4d535f41
** Attachment added: AlsaDevices.txt http://launchpadlibrarian.net/35190113/AlsaDevices.txt ** Attachment added: AplayDevices.txt http://launchpadlibrarian.net/35190114/AplayDevices.txt ** Attachment added: BootDmesg.txt http://launchpadlibrarian.net/35190116/BootDmesg.txt ** Attachment added: Card0.Amixer.values.txt http://launchpadlibrarian.net/35190117/Card0.Amixer.values.txt ** Attachment added: Card0.Codecs.codec.0.txt http://launchpadlibrarian.net/35190118/Card0.Codecs.codec.0.txt ** Attachment added: CurrentDmesg.txt http://launchpadlibrarian.net/35190119/CurrentDmesg.txt ** Attachment added: Dependencies.txt http://launchpadlibrarian.net/35190120/Dependencies.txt ** Attachment added: IwConfig.txt http://launchpadlibrarian.net/35190121/IwConfig.txt ** Attachment added: Lspci.txt http://launchpadlibrarian.net/35190122/Lspci.txt ** Attachment added: Lsusb.txt http://launchpadlibrarian.net/35190123/Lsusb.txt ** Attachment added: OopsText.txt http://launchpadlibrarian.net/35190124/OopsText.txt ** Attachment added: PciMultimedia.txt http://launchpadlibrarian.net/35190125/PciMultimedia.txt ** Attachment added: ProcCpuinfo.txt http://launchpadlibrarian.net/35190126/ProcCpuinfo.txt ** Attachment added: ProcInterrupts.txt http://launchpadlibrarian.net/35190127/ProcInterrupts.txt ** Attachment added: ProcModules.txt http://launchpadlibrarian.net/35190128/ProcModules.txt ** Attachment added: RfKill.txt http://launchpadlibrarian.net/35190129/RfKill.txt ** Attachment added: UdevDb.txt http://launchpadlibrarian.net/35190130/UdevDb.txt ** Attachment added: UdevLog.txt http://launchpadlibrarian.net/35190131/UdevLog.txt ** Attachment added: WifiSyslog.txt http://launchpadlibrarian.net/35190132/WifiSyslog.txt -- BUG: unable to handle kernel paging request at 4d535f41 https://bugs.launchpad.net/bugs/475784 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 357633] Re: Unable to send an S/MIME encrypted message to alternative address to a person who own a certificate with multiple emails
I am seeing this issue in Karmic after an upgrade from Jaunty. Could not create message. Because Cannot find certificat for 'cert name, you may need to select different mail options. Configuration is identical to the working one in Jaunty, except that my certificate expired, and I replaced it. -- Unable to send an S/MIME encrypted message to alternative address to a person who own a certificate with multiple emails https://bugs.launchpad.net/bugs/357633 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 247148] Re: Xen dom0 kernel corrupts software raid (2.6.24-19)
I'm very excited for this to be fixed in Hardy, as I have had quite a bit of trouble with it. I am perhaps not up-to-speed on things. But although I know that KVM is now the preferred virtualization solution, due in part to ease-of-use at the desktop, Xen still has a lot of usefulness at the server. I would, of course, be happy to run my data center on Ubuntu, if all the requirements can be met. At the data center level, support for Xen would be one of them. Is there any chance of keeping builds of Xen binaries in the repositories of intrepid and forward, without changing the direction of KVM as the preferred solution? I don't believe that what I am requesting here is a change. Merely that we continue to build and support what we already used to build and support. Thanks, - alvinc -- Xen dom0 kernel corrupts software raid (2.6.24-19) https://bugs.launchpad.net/bugs/247148 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 160104] Re: iscsitarget kernel module compile fails in event.c:98
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 It would be my honour to work on the SRU of this bug. Alas, I have not looked at it in a while, and it will take me a little bit of time to review the documentation which Emmet referred me to at the beginning. I expect to look at it this weekend (US time) - - alvinc -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (MingW32) Comment: http://getfiregpg.org iEYEARECAAYFAkiZPEoACgkQSkZVoNjHaTzaOgCgpe7g23x9hgAxTt1rzcWKQ4e5 O8AAoMbppI5ytH5UAHrrbIE4dr535E7c =w2PP -END PGP SIGNATURE- -- iscsitarget kernel module compile fails in event.c:98 https://bugs.launchpad.net/bugs/160104 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 135818] Re: Gutsy xen-3.1/kernel-2.6.22 dom0 kernel panic
I was searching through bugs, and found this one un-updated. I am no longer seeing these errors under Hardy 8.04.1 and its xen kernel. Is the right thing to do in this case to do an SRU for Gutsy? The kernel team needs to do this one, correct? - alvinc -- Gutsy xen-3.1/kernel-2.6.22 dom0 kernel panic https://bugs.launchpad.net/bugs/135818 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 216174] Re: mythfrontend.real crashed with SIGSEGV in MythThemedMenuPrivate::keyHandler()
*** This bug is a duplicate of bug 215036 *** https://bugs.launchpad.net/bugs/215036 Removing ~/.mythtv/themecache solved the problem. -- mythfrontend.real crashed with SIGSEGV in MythThemedMenuPrivate::keyHandler() https://bugs.launchpad.net/bugs/216174 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 160106] Re: /etc/init.d/iscsitarget broken with migration to /bin/dash
Thank you Henrik! I will read the SRU process. - alvinc -- /etc/init.d/iscsitarget broken with migration to /bin/dash https://bugs.launchpad.net/bugs/160106 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 160106] Re: /etc/init.d/iscsitarget broken with migration to /bin/dash
I think marking status as Confirmed may have been a mistake on my part? Have these diffs been reviewed? Cheers, - alvinc ** Changed in: iscsitarget (Ubuntu) Status: Confirmed = In Progress -- /etc/init.d/iscsitarget broken with migration to /bin/dash https://bugs.launchpad.net/bugs/160106 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 160106] Re: /etc/init.d/iscsitarget broken with migration to /bin/dash
Confirmed that this issue still occurs in Hardy at version 0.4.15-5. ** Changed in: iscsitarget (Ubuntu) Status: In Progress = Confirmed -- /etc/init.d/iscsitarget broken with migration to /bin/dash https://bugs.launchpad.net/bugs/160106 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 160106] Re: /etc/init.d/iscsitarget broken with migration to /bin/dash
Attached is the diff with fixes for Hardy (on version 0.4.15-5, sync'd from Debian) ** Attachment added: Fix for 0.4.15-5 on hardy http://launchpadlibrarian.net/10681080/iscsitarget_0.4.15-6.diff.gz -- /etc/init.d/iscsitarget broken with migration to /bin/dash https://bugs.launchpad.net/bugs/160106 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 160106] Re: /etc/init.d/iscsitarget broken with migration to /bin/dash
Hi Emmet! Bug #160104 is the kernel module bug. This one is the bug that the initscript in Debian is written for /bin/bash, whereas the diff which I added includes a script which is Bourne Shell virgin, and runs under /bin/dash. -- /etc/init.d/iscsitarget broken with migration to /bin/dash https://bugs.launchpad.net/bugs/160106 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 160106] Re: /etc/init.d/iscsitarget broken with migration to /bin/dash
Fixes are attached. Fixes for Bug #160104 are included in the diff. Hopefully I've become proficient enough at pbuilder and debuild that the data is in the proper format now. :) Cheers, - alvinc ** Attachment added: iscsitarget_0.4.15-3.diff.gz http://launchpadlibrarian.net/10597577/iscsitarget_0.4.15-3.diff.gz -- /etc/init.d/iscsitarget broken with migration to /bin/dash https://bugs.launchpad.net/bugs/160106 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 160104] Re: iscsitarget kernel module compile fails in event.c:98
Fixes are attached. Fixes for Bug #160106 are included in the diff. I put in a control structure to check for kernel version as well. Cheers, - alvinc ** Attachment added: iscsitarget_0.4.15-3.diff.gz http://launchpadlibrarian.net/10597545/iscsitarget_0.4.15-3.diff.gz -- iscsitarget kernel module compile fails in event.c:98 https://bugs.launchpad.net/bugs/160104 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 160104] Re: iscsitarget kernel module compile fails in event.c:98
Hi Brendan, Further up in this bug, I attached a diff of event.c. Changing line 98 of event.c in accordance with the diff will do the trick. This will be fixed in the future, I'm working that out now (learning pbuilder and experimenting with doing things properly). But if you're in patient, you can try to fix it the same way I have. Procedurally, the following: # apt-get install iscsitarget-source # cd /usr/src # tar jxvf iscsitarget.tar.bz2 # vi modules/iscsitarget-module/kernel/event.c make the change to line 98 # mv iscsitarget.tar.bz2 iscsitarget.tar.bz2.ORIG # tar jcvf iscsitarget.tar.bz2 modules/ After this, module assistant will work. # m-a a-i iscsitarget Best regards, - alvinc -- iscsitarget kernel module compile fails in event.c:98 https://bugs.launchpad.net/bugs/160104 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 160104] Re: iscsitarget kernel module compile fails in event.c:98
I have FAI'd an edgy system and done a CD install of a dapper system. iscsitarget is not present in either release, nor is it listed in any of the repositories (updates, security, backports, commercial). Would this then qualify as a backport? Best regards, - alvinc -- iscsitarget kernel module compile fails in event.c:98 https://bugs.launchpad.net/bugs/160104 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 125687] Re: Samba does not start on boot.
Did some searching. Possible similarities to Bug #84537. Also, mlind has a comment in Bug #25931 that sounds somewhat similar. I will run a couple of use tests by tomorrow. -- Samba does not start on boot. https://bugs.launchpad.net/bugs/125687 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 125687] Re: Samba does not start on boot.
This problem is persisting in Gutsy as well. I am suspecting race conditions with upstart as root cause. I will run test cases with sysvinit and see what the results are. -- Samba does not start on boot. https://bugs.launchpad.net/bugs/125687 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 125687] Re: Samba does not start on boot.
Confirmed that replacing upstart with sysvinit eliminates the problem. This is no fix, but it does seem to point at upstart. HOST INFO: # uname -a Linux mpk-acura1 2.6.22-14-generic #1 SMP Sun Oct 14 23:05:12 GMT 2007 i686 GNU/Linux [EMAIL PROTECTED]:/var/log/apt# cat /etc/issue Ubuntu 7.10 \n \l //*** BEGIN APTITUDE LOG [REMOVE, DEPENDENCIES] apparmor [REMOVE, DEPENDENCIES] apparmor-utils [REMOVE, DEPENDENCIES] startup-tasks [REMOVE, DEPENDENCIES] system-services [REMOVE, DEPENDENCIES] ubuntu-minimal [REMOVE, DEPENDENCIES] ubuntu-standard [REMOVE, DEPENDENCIES] upstart [REMOVE, DEPENDENCIES] upstart-compat-sysv [REMOVE, DEPENDENCIES] upstart-logd [HOLD] firefox [HOLD] firefox-gnome-support [HOLD] libc6 [HOLD] libc6-i686 [HOLD] libssl0.9.8 [HOLD] nscd [HOLD] samba [HOLD] tzdata [HOLD] ubufox [HOLD] winbind [INSTALL] sysvinit //*** END APTITUDE LOG //*** BEGIN APT LOG Log started: 2007-11-19 18:28:39 (Reading database ... 169744 files and directories currently installed.) Removing apparmor-utils ... Removing apparmor ... Unloading AppArmor profiles : done. update-initramfs: deferring update (trigger activated) Removing iputils-arping ... Removing librpc-xml-perl ... Removing libterm-readkey-perl ... Removing ubuntu-minimal ... Removing startup-tasks ... Removing system-services ... Removing ubuntu-standard ... Removing upstart-logd ... Removing upstart-compat-sysv ... Removing upstart ... Processing triggers for initramfs-tools ... update-initramfs: Generating /boot/initrd.img-2.6.22-14-rt Selecting previously deselected package sysvinit. (Reading database ... 169539 files and directories currently installed.) Unpacking sysvinit (from .../sysvinit_2.86.ds1-14.1ubuntu31_i386.deb) ... Setting up sysvinit (2.86.ds1-14.1ubuntu31) ... //*** END APT LOG -- Samba does not start on boot. https://bugs.launchpad.net/bugs/125687 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 125687] Re: Samba does not start on boot.
My second test did not fare so well. Even with sysvinit, there seems to be a race condition with samba. I believe the right course it to put logic into the startup script to wait for the network. In my first test case, spanning-tree portfast was set on the switch in question, which leads to faster negotiation times at layer 2 on the network. My second test case did a full auto-negotiate, leading me to believe that having samba wait for network state may be the right thing to do. -- Samba does not start on boot. https://bugs.launchpad.net/bugs/125687 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 160104] Re: iscsitarget kernel module compile fails in event.c:98
With guidance from Emmet, work on evaluating the impact of this bug is proceeding. I configuring dapper and feisty environments, and constructing FAI classes and nfsroot for edgy (as the edgy ISO images are no longer available in any of the mirrors which I have checked). More status will be added this weekend. -- iscsitarget kernel module compile fails in event.c:98 https://bugs.launchpad.net/bugs/160104 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 162731] hybserv initscript not working
Public bug reported: Binary package hint: hybserv /etc/init.d/hybserv does not work on stop. The control structure in the script is looking for a pid file, which the hybserv daemon is not generating. ** Affects: hybserv (Ubuntu) Importance: Undecided Status: New -- hybserv initscript not working https://bugs.launchpad.net/bugs/162731 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 160104] Re: iscsitarget kernel module compile fails in event.c:98
Fixes attached. Also includes fixes for Bug #160106 ** Attachment added: iscsitarget_0.4.15-3.debdiff http://launchpadlibrarian.net/10372626/iscsitarget_0.4.15-3.debdiff -- iscsitarget kernel module compile fails in event.c:98 https://bugs.launchpad.net/bugs/160104 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 160106] Re: /etc/init.d/iscsitarget broken with migration to /bin/dash
Fix attached ** Attachment added: debdiff of fixes http://launchpadlibrarian.net/10372620/iscsitarget_0.4.15-3.debdiff -- /etc/init.d/iscsitarget broken with migration to /bin/dash https://bugs.launchpad.net/bugs/160106 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 160104] Re: iscsitarget kernel module compile fails in event.c:98
Thanks Emmet. For the purposes of staying on top of the issue... What is the target kernel version for hardy? As hardy is slated to be an LTS release, I am very interested that these bugs are fixed by the time hardy releases. iscsitarget is a service which has a lot of usefulness in Production scenarios. Best regards, - alvinc -- iscsitarget kernel module compile fails in event.c:98 https://bugs.launchpad.net/bugs/160104 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 160106] Re: /etc/init.d/iscsitarget broken with migration to /bin/dash
** Changed in: gutsy-backports Assignee: (unassigned) = Alvin Cura (alvinc) ** Changed in: iscsitarget (Ubuntu) Assignee: (unassigned) = Alvin Cura (alvinc) -- /etc/init.d/iscsitarget broken with migration to /bin/dash https://bugs.launchpad.net/bugs/160106 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 160104] Re: iscsitarget kernel module compile fails in event.c:98
** Changed in: iscsitarget (Ubuntu) Assignee: (unassigned) = Alvin Cura (alvinc) ** Changed in: gutsy-backports Assignee: (unassigned) = Alvin Cura (alvinc) -- iscsitarget kernel module compile fails in event.c:98 https://bugs.launchpad.net/bugs/160104 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 135818] Re: Gutsy xen-3.1/kernel-2.6.22 dom0 kernel panic
More bad news. Problem is persisting, even with a different NIC (although also a Realtek, this one a PCI card instead of the onboard): syslog:Nov 11 23:22:17 xen1 kernel: [ 8113.207809] PCI-DMA: Out of SW-IOMMU space for 7222 bytes at device :03:05.0 syslog:Nov 11 23:22:40 xen1 kernel: [ 8136.691486] PCI-DMA: Out of SW-IOMMU space for 7222 bytes at device :03:05.0 syslog:Nov 11 23:23:17 xen1 kernel: [ 8173.209884] PCI-DMA: Out of SW-IOMMU space for 7222 bytes at device :03:05.0 syslog:Nov 11 23:24:17 xen1 kernel: [ 8233.214080] PCI-DMA: Out of SW-IOMMU space for 7222 bytes at device :03:05.0 syslog:Nov 11 23:24:32 xen1 kernel: [ 8248.385552] PCI-DMA: Out of SW-IOMMU space for 7222 bytes at device :03:05.0 03:05.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8169 Gigabit Ethernet (rev 10) - Further research yielded the following thread in xen-devel: http://lists.xensource.com/archives/html/xen-devel/2007-09/msg00138.html However, more bad news, even setting swiotlb at boottime, the problem still occurs. -- Gutsy xen-3.1/kernel-2.6.22 dom0 kernel panic https://bugs.launchpad.net/bugs/135818 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 162147] Xen 3.1/Gutsy: PCI-DMA: Out of SW-IOMMU space
Public bug reported: Binary package hint: ubuntu-xen-server I had been commenting on Bug #135818, however it is marked as fixed. This issue seems related, but is not identical: //**// Alvin Cura wrote on 2007-11-05: (permalink) I'm afraid I'm still seeing this bug. Or something similar. I did not get a kernel panic, but my network died and stayed dead. I was, however, able to reboot. Nov 4 16:44:43 xen1 -- MARK -- Nov 4 17:04:36 xen1 kernel: [19235.154900] PCI-DMA: Out of SW-IOMMU space for 7222 bytes at device :03:00.0 Nov 4 17:04:36 xen1 kernel: [19235.157617] PCI-DMA: Out of SW-IOMMU space for 7222 bytes at device :03:00.0 Nov 4 17:04:36 xen1 kernel: [19235.160469] PCI-DMA: Out of SW-IOMMU space for 7222 bytes at device :03:00.0 Nov 4 17:04:36 xen1 kernel: [19235.163254] PCI-DMA: Out of SW-IOMMU space for 7222 bytes at device :03:00.0 Nov 4 17:04:36 xen1 kernel: [19235.166076] PCI-DMA: Out of SW-IOMMU space for 7222 bytes at device :03:00.0 Nov 4 17:04:36 xen1 kernel: [19235.168897] PCI-DMA: Out of SW-IOMMU space for 7222 bytes at device :03:00.0 Nov 4 17:04:36 xen1 kernel: [19235.171727] PCI-DMA: Out of SW-IOMMU space for 7222 bytes at device :03:00.0 Nov 4 17:04:36 xen1 kernel: [19235.174519] PCI-DMA: Out of SW-IOMMU space for 7222 bytes at device :03:00.0 Nov 4 17:04:36 xen1 kernel: [19235.177666] PCI-DMA: Out of SW-IOMMU space for 7222 bytes at device :03:00.0 7222 bytes is likely dictated by my ethernet interface being set for jumbo frames: 11: eth0: BROADCAST,MULTICAST,UP,1 mtu 7200 qdisc pfifo_fast qlen 1000 link/ether 00:1b:fc:1f:33:40 brd ff:ff:ff:ff:ff:ff this is on the following controller: 03:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168B PCI Express Gigabit Ethernet controller (rev 01) I will proceed with some tests of using different NICs to try to isolate the behaviour. Alvin Cura wrote 1 seconds ago: (permalink) More bad news. Problem is persisting, even with a different NIC (although also a Realtek, this one a PCI card instead of the onboard): syslog:Nov 11 23:22:17 xen1 kernel: [ 8113.207809] PCI-DMA: Out of SW-IOMMU space for 7222 bytes at device :03:05.0 syslog:Nov 11 23:22:40 xen1 kernel: [ 8136.691486] PCI-DMA: Out of SW-IOMMU space for 7222 bytes at device :03:05.0 syslog:Nov 11 23:23:17 xen1 kernel: [ 8173.209884] PCI-DMA: Out of SW-IOMMU space for 7222 bytes at device :03:05.0 syslog:Nov 11 23:24:17 xen1 kernel: [ 8233.214080] PCI-DMA: Out of SW-IOMMU space for 7222 bytes at device :03:05.0 syslog:Nov 11 23:24:32 xen1 kernel: [ 8248.385552] PCI-DMA: Out of SW-IOMMU space for 7222 bytes at device :03:05.0 03:05.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8169 Gigabit Ethernet (rev 10) - Further research yielded the following thread in xen-devel: http://lists.xensource.com/archives/html/xen-devel/2007-09/msg00138.html However, more bad news, even setting swiotlb at boottime, the problem still occurs. ** Affects: xen-meta (Ubuntu) Importance: Undecided Status: New -- Xen 3.1/Gutsy: PCI-DMA: Out of SW-IOMMU space https://bugs.launchpad.net/bugs/162147 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 159536] Re: dpkg seg-fault with fai-nfsroot
I'll look into it and let you know what I find. On Nov 7, 2007 12:16 AM, Castang Jerome [EMAIL PROTECTED] wrote: Alvin Cura a écrit : Jerome, What are you running for xendom0? I am beginning to suspect running gutsy on a feisty xendom0 is part of the issue. Thanks, - alvinc I am running a CentOS 5.0 (with last updates). Looking a this problems shows that there is one another. Sometimes get this message: /dev/mem: Bad addresses (or something like that). Maybe a problem directly linked to Xen. Some mem addresses given by the hypervisor may be corrupted ? -- Jerome Castang Mail: [EMAIL PROTECTED] Tel: +33(0)5 40 00 36 92 -- dpkg seg-fault with fai-nfsroot https://bugs.launchpad.net/bugs/159536 You received this bug notification because you are a direct subscriber of the bug. -- dpkg seg-fault with fai-nfsroot https://bugs.launchpad.net/bugs/159536 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 159536] Re: dpkg seg-fault with fai-nfsroot when used in a Xen DomU
Interestingly, here is the result of fai-setup -v on a Feisty xendomu. It tried to continue past the error, and aborted in a different place than Gutsy: Setting up file (4.19-1ubuntu2) ... Setting up cfengine2 (2.1.20-1) ... Making a key pair for cfengine, please wait, this could take a minute... Writing private key to /var/lib/cfengine2/ppkeys/localhost.priv Writing public key to /var/lib/cfengine2/ppkeys/localhost.pub Segmentation fault dpkg: error processing cfengine2 (--configure): subprocess post-installation script returned error exit status 139 Setting up libapt-pkg-perl (0.1.20ubuntu4) ... dpkg: dependency problems prevent configuration of fai-client: fai-client depends on cfengine2 | cfengine; however: Package cfengine2 is not configured yet. Package cfengine is not installed. dpkg: error processing fai-client (--configure): dependency problems - leaving unconfigured dpkg: dependency problems prevent configuration of fai-nfsroot: fai-nfsroot depends on fai-client; however: Package fai-client is not configured yet. dpkg: error processing fai-nfsroot (--configure): dependency problems - leaving unconfigured Errors were encountered while processing: cfengine2 fai-client fai-nfsroot E: Sub-process /usr/bin/dpkg returned an error code (1) Aborting No diversion `any diversion of /sbin/discover-modprobe', none removed -- dpkg seg-fault with fai-nfsroot when used in a Xen DomU https://bugs.launchpad.net/bugs/159536 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 159536] Re: dpkg seg-fault with fai-nfsroot
Gutsy (Ubuntu 7.10). Host is a Dell 2970. On Nov 6, 2007 1:03 AM, Castang Jerome [EMAIL PROTECTED] wrote: Alvin Cura a écrit : I am in the same situation. I reproduce the same error on a xen domU. Dom0 is a CentOS 5 (last updates). Which OS do you use as Dom0 ? -- dpkg seg-fault with fai-nfsroot https://bugs.launchpad.net/bugs/159536 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 159536] Re: dpkg seg-fault with fai-nfsroot
Further analysis seems to point at a xen-only problem. I have installed Gutsy Server from the CD image on a VMware VM and installed the ppa FAI with no errors: // * // [EMAIL PROTECTED]:~# fai-setup -v Using configuration files from /etc/fai Creating FAI nfsroot in /srv/fai/nfsroot/live/filesystem.dir. By default it needs more than 330 MBytes disk space. This may take a long time. Creating base system using debootstrap version 1.0.3build1 Calling debootstrap gutsy /srv/fai/nfsroot/live/filesystem.dir http://archive.ub untu.com/ubuntu I: Retrieving Release I: Retrieving Packages I: Validating Packages I: Resolving dependencies of required packages... I: Resolving dependencies of base packages... I: Checking component main on http://archive.ubuntu.com/ubuntu... [...] Setting up fai-client (3.2.1-0ubuntu2~ppa2~gutsy1) ... Setting up fai-nfsroot (3.2.1-0ubuntu2~ppa2~gutsy1) ... Processing triggers for libc6 ... ldconfig deferred processing now taking place Reading package lists... Done Building dependency tree Reading state information... Done Reading package lists... Done Building dependency tree Reading state information... Done Calculating upgrade... Done The following packages will be upgraded: libssl0.9.8 1 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. Need to get 2825kB of archives. After unpacking 0B of additional disk space will be used. WARNING: The following packages cannot be authenticated! libssl0.9.8 Authentication warning overridden. Get:1 http://security.ubuntu.com gutsy-security/main libssl0.9.8 0.9.8e-5ubuntu3 .1 [2825kB] kB 1%] 29% [1 libssl0.9.8 838077/2825kB 24%] 54% [1 li 76% [1 libssl0.9.8 2157209/2825kB 68%] 174kB/s 5s 96% [1 libssl0.9.8 2734957/2825kB 96%] 174kB/s 1s Fetched 2825kB in 10s (262kB/s) Preconfiguring packages ... (Reading database ... 10429 files and directories currently installed.) Preparing to replace libssl0.9.8 0.9.8e-5ubuntu3 (using .../libssl0.9.8_0.9.8e-5 ubuntu3.1_i386.deb) ... Unpacking replacement libssl0.9.8 ... Setting up libssl0.9.8 (0.9.8e-5ubuntu3.1) ... Processing triggers for libc6 ... ldconfig deferred processing now taking place install_packages: reading config files from directory /etc/fai Adding additional packages to /srv/fai/nfsroot/live/filesystem.dir: [...] install_packages: executing chroot /srv/fai/nfsroot/live/filesystem.dir dpkg -C install_packages: executing chroot /srv/fai/nfsroot/live/filesystem.dir apt-get clean `/etc/fai/apt' - `/srv/fai/nfsroot/live/filesystem.dir/etc/fai/apt' `/etc/fai/apt/sources.list' - `/srv/fai/nfsroot/live/filesystem.dir/etc/fai/apt/sources.list' `/etc/fai/fai.conf' - `/srv/fai/nfsroot/live/filesystem.dir/etc/fai/fai.conf' `/etc/fai/make-fai-nfsroot.conf' - `/srv/fai/nfsroot/live/filesystem.dir/etc/fai/make-fai-nfsroot.conf' `/etc/fai/menu.lst' - `/srv/fai/nfsroot/live/filesystem.dir/etc/fai/menu.lst' `/etc/fai/NFSROOT' - `/srv/fai/nfsroot/live/filesystem.dir/etc/fai/NFSROOT' Shadow passwords are now on. `/srv/fai/nfsroot/live/filesystem.dir/boot/vmlinuz-2.6.22-14-generic' - `/srv/tftp/fai/vmlinuz-2.6.22-14-generic' `/srv/fai/nfsroot/live/filesystem.dir/boot/initrd.img-2.6.22-14-generic' - `/srv/tftp/fai/initrd.img-2.6.22-14-generic' DHCP environment prepared. If you want to use it, you have to enable the dhcpd and the tftp-hpa daemon. Command mkelf-linux not found. Can not set up BOOTP booting. Please install the package mknbi and rerun fai-setup. Removing `local diversion of /sbin/discover-modprobe to /sbin/discover-modprobe.distrib' make-fai-nfsroot finished properly. Adding line to /etc/exports: /srv/fai/config 192.168.66.229/255.255.255.0(async,ro,no_subtree_check) Adding line to /etc/exports: /srv/fai/nfsroot 192.168.66.229/255.255.255.0(async,ro,no_subtree_check,no_root_squash) * Re-exporting directories for NFS kernel daemon... [ OK ] FAI setup finished. // * // As we know, xendomu is commonly installed using debootstrap, so we may have something missing here. I had hoped to not have to get too far in the guts of it, but I suppose it's unavoidable now. :) -- dpkg seg-fault with fai-nfsroot https://bugs.launchpad.net/bugs/159536 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 159536] Re: dpkg seg-fault with fai-nfsroot
** Changed in: fai (Ubuntu) Assignee: (unassigned) = Ubuntu FAI Developers (fai) -- dpkg seg-fault with fai-nfsroot https://bugs.launchpad.net/bugs/159536 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 159536] Re: dpkg seg-fault with fai-nfsroot
Jerome, What are you running for xendom0? I am beginning to suspect running gutsy on a feisty xendom0 is part of the issue. Thanks, - alvinc -- dpkg seg-fault with fai-nfsroot https://bugs.launchpad.net/bugs/159536 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 156836] Re: broken apt installation dependency for fai-quickstart-3.2.1-0ubuntu2
Thanks siretart. Question: What is the criteria for deciding whether this belongs in universe or multiverse? I'm afraid I don't know how that decision is made. Thanks! -- broken apt installation dependency for fai-quickstart-3.2.1-0ubuntu2 https://bugs.launchpad.net/bugs/156836 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 159536] Re: dpkg seg-fault with fai-nfsroot
I just reproduced it. --- BEGIN CUT-N-PASTE [EMAIL PROTECTED]:/etc/fai# fai-setup -v Using configuration files from /etc/fai Creating FAI nfsroot in /srv/fai/nfsroot/live/filesystem.dir. By default it needs more than 330 MBytes disk space. This may take a long time. Creating base system using debootstrap version 1.0.3build1 Calling debootstrap gutsy /srv/fai/nfsroot/live/filesystem.dir http://archive.ubuntu.com/ubuntu I: Retrieving Release I: Retrieving Packages I: Validating Packages I: Resolving dependencies of required packages... I: Resolving dependencies of base packages... I: Checking component main on http://archive.ubuntu.com/ubuntu... [...] Setting up fai-client (3.2.1-0ubuntu2~ppa2~gutsy1) ... Setting up fai-nfsroot (3.2.1-0ubuntu2~ppa2~gutsy1) ... Segmentation fault dpkg: error processing fai-nfsroot (--configure): subprocess post-installation script returned error exit status 139 Processing triggers for libc6 ... ldconfig deferred processing now taking place Errors were encountered while processing: fai-nfsroot E: Sub-process /usr/bin/dpkg returned an error code (1) Aborting Use of uninitialized value in string eq at /usr/sbin/dpkg-divert line 224. Use of uninitialized value in length at /usr/sbin/dpkg-divert line 224. Use of uninitialized value in length at /usr/sbin/dpkg-divert line 224. Use of uninitialized value in length at /usr/sbin/dpkg-divert line 224. No diversion `any diversion of /sbin/discover-modprobe', none removed --- END CUT-N-PASTE [EMAIL PROTECTED]:/etc/fai# cat /etc/apt/sources.list deb http://us.archive.ubuntu.com/ubuntu gutsy main restricted universe multiverse deb http://ppa.launchpad.net/fai/ubuntu gutsy main restricted universe multiverse [EMAIL PROTECTED]:/etc/fai# dpkg-query -l | grep fai ii fai-client 3.2.1-0ubuntu2~ppa2~gutsy1Fully Automatic Installation client package ii fai-doc3.2.1-0ubuntu2~ppa2~gutsy1Documentation for FAI ii fai-quickstart 3.2.1-0ubuntu2~ppa2~gutsy1Fully Automatic Installation quickstart pack ii fai-server 3.2.1-0ubuntu2~ppa2~gutsy1Fully Automatic Installation server package [EMAIL PROTECTED]:/etc/fai# cat /etc/issue Ubuntu 7.10 \n \l It's a xendomu -- dpkg seg-fault with fai-nfsroot https://bugs.launchpad.net/bugs/159536 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 135818] Re: Gutsy xen-3.1/kernel-2.6.22 dom0 kernel panic
I'm afraid I'm still seeing this bug. Or something similar. I did not get a kernel panic, but my network died and stayed dead. I was, however, able to reboot. Nov 4 16:44:43 xen1 -- MARK -- Nov 4 17:04:36 xen1 kernel: [19235.154900] PCI-DMA: Out of SW-IOMMU space for 7222 bytes at device :03:00.0 Nov 4 17:04:36 xen1 kernel: [19235.157617] PCI-DMA: Out of SW-IOMMU space for 7222 bytes at device :03:00.0 Nov 4 17:04:36 xen1 kernel: [19235.160469] PCI-DMA: Out of SW-IOMMU space for 7222 bytes at device :03:00.0 Nov 4 17:04:36 xen1 kernel: [19235.163254] PCI-DMA: Out of SW-IOMMU space for 7222 bytes at device :03:00.0 Nov 4 17:04:36 xen1 kernel: [19235.166076] PCI-DMA: Out of SW-IOMMU space for 7222 bytes at device :03:00.0 Nov 4 17:04:36 xen1 kernel: [19235.168897] PCI-DMA: Out of SW-IOMMU space for 7222 bytes at device :03:00.0 Nov 4 17:04:36 xen1 kernel: [19235.171727] PCI-DMA: Out of SW-IOMMU space for 7222 bytes at device :03:00.0 Nov 4 17:04:36 xen1 kernel: [19235.174519] PCI-DMA: Out of SW-IOMMU space for 7222 bytes at device :03:00.0 Nov 4 17:04:36 xen1 kernel: [19235.177666] PCI-DMA: Out of SW-IOMMU space for 7222 bytes at device :03:00.0 7222 bytes is likely dictated by my ethernet interface being set for jumbo frames: 11: eth0: BROADCAST,MULTICAST,UP,1 mtu 7200 qdisc pfifo_fast qlen 1000 link/ether 00:1b:fc:1f:33:40 brd ff:ff:ff:ff:ff:ff this is on the following controller: 03:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168B PCI Express Gigabit Ethernet controller (rev 01) I will proceed with some tests of using different NICs to try to isolate the behaviour. -- Gutsy xen-3.1/kernel-2.6.22 dom0 kernel panic https://bugs.launchpad.net/bugs/135818 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 160106] /etc/init.d/iscsitarget broken with migration to /bin/dash
Public bug reported: Binary package hint: iscsitarget Errors are as follows: [EMAIL PROTECTED]:/usr/src# apt-get install iscsitarget Reading package lists... Done Building dependency tree Reading state information... Done The following NEW packages will be installed: iscsitarget 0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded. Need to get 58.6kB of archives. After unpacking 213kB of additional disk space will be used. Get:1 http://us.archive.ubuntu.com gutsy/universe iscsitarget 0.4.15-2 [58.6kB] Fetched 58.6kB in 1s (48.7kB/s) Selecting previously deselected package iscsitarget. (Reading database ... 100337 files and directories currently installed.) Unpacking iscsitarget (from .../iscsitarget_0.4.15-2_amd64.deb) ... Setting up iscsitarget (0.4.15-2) ... Starting iSCSI enterprise target service: [: 142: ==: unexpected operator failed. - Workaround/Cause is pretty straightforward. /bin/sh is a link to /bin/dash now, instead of /bin/sh. rpmstrap had a similar problem (reference bug 64032 for rpmstrap). Workaround is simple, set to #!/bin/bash - Can a MOTU check this out? Thanks! - alvinc ** Affects: gutsy-backports Importance: Undecided Status: New ** Affects: iscsitarget (Ubuntu) Importance: Undecided Status: New ** Also affects: gutsy-backports Importance: Undecided Status: New -- /etc/init.d/iscsitarget broken with migration to /bin/dash https://bugs.launchpad.net/bugs/160106 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 160104] Re: iscsitarget kernel module compile fails in event.c:98
I'm sorry. Running Gutsy: [EMAIL PROTECTED]:/usr/src# uname -a Linux xen1 2.6.22-14-xen #1 SMP Sun Oct 14 23:20:20 GMT 2007 x86_64 GNU/Linux ** Also affects: gutsy-backports Importance: Undecided Status: New -- iscsitarget kernel module compile fails in event.c:98 https://bugs.launchpad.net/bugs/160104 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 160104] iscsitarget kernel module compile fails in event.c:98
Public bug reported: Binary package hint: iscsitarget-source Module build using module assistant m-a a-i iscsitarget - Following are the errors: CC [M] /usr/src/modules/iscsitarget-module/kernel/event.o /usr/src/modules/iscsitarget-module/kernel/event.c: In function âevent_initâ: /usr/src/modules/iscsitarget-module/kernel/event.c:98: warning: passing argument 4 of ânetlink_kernel_createâ from incompatible pointer type /usr/src/modules/iscsitarget-module/kernel/event.c:98: error: too few arguments to function netlink_kernel_create make[3]: *** [/usr/src/modules/iscsitarget-module/kernel/event.o] Error 1 make[2]: *** [_module_/usr/src/modules/iscsitarget-module/kernel] Error 2 make[2]: Leaving directory `/usr/src/linux-headers-2.6.22-14-xen' make[1]: *** [binary-modules] Error 2 make[1]: Leaving directory `/usr/src/modules/iscsitarget-module' make: *** [kdist_build] Error 2 - Here is the workaround: [EMAIL PROTECTED]:/usr/src# diff modules/iscsitarget-module/kernel/event.c modules/iscsitarget-module/kernel/event.c.DISTRIB 98c98 nl = netlink_kernel_create(NETLINK_IET, 1, event_recv, THIS_MODULE, NULL); --- nl = netlink_kernel_create(NETLINK_IET, 1, event_recv, THIS_MODULE); Which I found at this link: http://www.nabble.com/iscsitarget-0.4.15-fails-to-compile-against-2.6.22.1-t4118020.html - Can a MOTU review this please? Thanks! - alvinc ** Affects: gutsy-backports Importance: Undecided Status: New ** Affects: iscsitarget (Ubuntu) Importance: Undecided Status: New -- iscsitarget kernel module compile fails in event.c:98 https://bugs.launchpad.net/bugs/160104 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 156836] broken apt installation dependency for fai-quickstart-3.2.1-0ubuntu2
Public bug reported: Binary package hint: fai-quickstart Broken dependency in fai-quickstart (using PPA): [EMAIL PROTECTED]:~# apt-get install fai-quickstart Reading package lists... Done Building dependency tree Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. Since you only requested a single operation it is extremely likely that the package is simply not installable and a bug report against that package should be filed. The following information may help to resolve the situation: The following packages have unmet dependencies: fai-quickstart: Depends: mkisofs but it is not installable E: Broken packages [EMAIL PROTECTED]:~# cat /etc/apt/sources.list deb http://us.archive.ubuntu.com/ubuntu gutsy main universe deb http://ppa.launchpad.net/fai/ubuntu gutsy main universe ** Affects: gutsy-backports Importance: Undecided Status: Incomplete ** Affects: fai (Ubuntu) Importance: Undecided Assignee: Ubuntu FAI Developers (fai) Status: New ** Changed in: fai (Ubuntu) Assignee: (unassigned) = Ubuntu FAI Developers (fai) ** Also affects: gutsy-backports Importance: Undecided Status: New ** Changed in: gutsy-backports Status: New = Incomplete -- broken apt installation dependency for fai-quickstart-3.2.1-0ubuntu2 https://bugs.launchpad.net/bugs/156836 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 64032] Re: rpmstrap using /bin/sh when it should use /bin/bash
Confirmed: Fix is working with Fedora Core 4 (Stentz) script (with regard to parsing the array of packages). Output is attached. HOWEVER! The rpm installation actions are failing. I have not yet looked into why. If anyone already knows why, I'd appreciate some info rather than spending too much time on it. Environment: [EMAIL PROTECTED]:~$ uname -a ; dpkg-query -l rpmstrap Linux fai 2.6.22-14-xen #1 SMP Sun Oct 14 23:20:20 GMT 2007 x86_64 GNU/Linux Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Installed/Config-f/Unpacked/Failed-cfg/Half-inst/t-aWait/T-pend |/ Err?=(none)/Hold/Reinst-required/X=both-problems (Status,Err: uppercase=bad) ||/ Name VersionDescription +++-==-==- ii rpmstrap 0.5.2-2ubuntu0 bootstrap a basic RPM-based system ** Attachment added: Output of rpmstrap --verbose stentz /tmp/fc4 http://launchpadlibrarian.net/10112027/rpmstrap.log -- rpmstrap using /bin/sh when it should use /bin/bash https://bugs.launchpad.net/bugs/64032 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 64032] Re: rpmstrap using /bin/sh when it should use /bin/bash
Additional info (verifying that the wget on the array works): [EMAIL PROTECTED]:/tmp/rpmstrap.295074023# ls basesystem-8.0-4.noarch.rpm libacl-2.2.23-5.x86_64.rpm bash-3.0-17.x86_64.rpmlibattr-2.4.16-3.i386.rpm chkconfig-1.3.11.1-1.x86_64.rpm libattr-2.4.16-3.x86_64.rpm cracklib-2.7-28.i386.rpm libgcc-3.4.2-6.fc3.i386.rpm cracklib-2.7-28.x86_64.rpmlibgcc-3.4.2-6.fc3.x86_64.rpm cracklib-dicts-2.7-28.x86_64.rpm libselinux-1.17.14-1.i386.rpm db4-4.2.52-6.i386.rpm libselinux-1.17.14-1.x86_64.rpm db4-4.2.52-6.x86_64.rpm libstdc++-3.4.2-6.fc3.i386.rpm e2fsprogs-1.35-11.2.i386.rpm libstdc++-3.4.2-6.fc3.x86_64.rpm e2fsprogs-1.35-11.2.x86_64.rpmlibtermcap-2.0.8-39.x86_64.rpm ethtool-1.8-4.x86_64.rpm mingetty-1.07-3.x86_64.rpm fedora-release-3-9.x86_64.rpm mktemp-1.5-10.x86_64.rpm filesystem-2.3.0-1.x86_64.rpm ncurses-5.4-13.i386.rpm findutils-4.1.20-7.x86_64.rpm ncurses-5.4-13.x86_64.rpm gawk-3.1.3-9.x86_64.rpm net-tools-1.60-37.x86_64.rpm glib-1.2.10-15.x86_64.rpm pcre-4.5-3.x86_64.rpm glib2-2.4.7-1.i386.rpmpopt-1.9.1-21.i386.rpm glib2-2.4.7-1.x86_64.rpm popt-1.9.1-21.x86_64.rpm glibc-2.3.3-74.i686.rpm psmisc-21.4-4.x86_64.rpm glibc-2.3.3-74.x86_64.rpm sed-4.1.2-4.x86_64.rpm glibc-common-2.3.3-74.x86_64.rpm setup-2.5.44-1.noarch.rpm grep-2.5.1-31.x86_64.rpm shadow-utils-4.0.3-37.x86_64.rpm hwdata-0.145-1.noarch.rpm tar-1.14-4.x86_64.rpm info-4.7-5.x86_64.rpm termcap-5.4-3.noarch.rpm iproute-2.6.9-3.x86_64.rpmtzdata-2004e-2.noarch.rpm iputils-20020927-16.x86_64.rpmwords-2-23.noarch.rpm less-382-4.x86_64.rpm zlib-1.2.1.2-1.i386.rpm libacl-2.2.23-5.i386.rpm zlib-1.2.1.2-1.x86_64.rpm Again, it failure is in rpm/alien (or so it seems, I'm not sure yet) -- rpmstrap using /bin/sh when it should use /bin/bash https://bugs.launchpad.net/bugs/64032 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 64032] Re: rpmstrap using /bin/sh when it should use /bin/bash
Hi Cesare! I read your link briefly. The project is dead? I thought there would be new life for it with the use of Xen. -- rpmstrap using /bin/sh when it should use /bin/bash https://bugs.launchpad.net/bugs/64032 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 64032] Re: rpmstrap using /bin/sh when it should use /bin/bash
Would it be worthy then to roll it into a Launchpad team and maintain it from there? -- rpmstrap using /bin/sh when it should use /bin/bash https://bugs.launchpad.net/bugs/64032 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 144631] Re: xen guest hangs after mounting filesystem
I think we may be chasing the wrong problem by pursuing xen-tools for the fix. This problem is also 100% reproducible using manual domain creation. The only working fix I have found is to add extra='xencons=tty1' to the xendomu config file. This would be incorrect behaviour. It should work out-of-the-box. My method for creating the xendomu was using a self-written script as follows: #!/bin/sh ## # $Id: //depot/hosts/xen1/root/mkxenvm#3 $ # $DateTime: 2007/10/16 10:45:21 $ ## usage() { printf USAGE: ${0}\txendom xen volume group\n printf \t\t[root part size] [swap part size]\n exit } if [ -z ${1} ]; then usage; else xendomu=${1}; fi if [ -z ${2} ]; then usage; else xenvg=${2}; fi if [ -z ${3} ]; then rootsize=8G; else rootsize=${3}; fi if [ -z ${4} ]; then swapsize=2G; else swapsize=${4}; fi printf Creating root volume /dev/${xenvg}/${xendomu}_root with size ${rootsize}: lvcreate -L${rootsize} -n${xendomu}_root ${xenvg} printf done.\n printf Creating swap volume /dev/${xenvg}/${xendomu}_swap with size ${swapsize}: lvcreate -L${swapsize} -n${xendomu}_swap ${xenvg} printf done.\n printf Creating ext3 filesystem on /dev/${xenvg}/${xendomu}_root: mkfs.ext3 -L${xendomu}_root /dev/${xenvg}/${xendomu}_root printf done.\n printf Creating swap partition on /dev/${xenvg}/${xendomu}_swap: mkswap /dev/${xenvg}/${xendomu}_swap printf done.\n printf Mounting /dev/${xenvg}/${xendomu}_root on /tmp/${xendomu}: mkdir /tmp/${xendomu} printf Debootstrapping ${xendomu}: debootstrap gutsy /tmp/${xendomu} printf done.\n printf Copying modules to ${xendomu}: cp -r /lib/modules/`uname -r` /tmp/${xendomu}/lib/modules/ printf done.\n printf Setting up fstab: printf /dev/sda1\t/\t\text3\trw,errors=remount-ro\t0\t1\n /tmp/${xendomu}/etc/fstab printf /dev/sda2\tnone\t\tswap\tdefaults\t0\t0\n /tmp/${xendomu}/etc/fstab printf none\t\t/proc\t\tproc\trw,nosuid,noexec\t0\t0\n /tmp/${xendomu}/etc/fstab printf done.\n printf Setting up hostname: echo ${xendomu} /tmp/${xendomu}/etc/hostname printf done.\n printf Setting up hosts: printf 127.0.0.1\tlocalhost\n /tmp/${xendomu}/etc/hosts printf done.\n printf Setting up network interfaces: printf auto lo\n /tmp/${xendomu}/etc/network/interfaces printf iface lo inet loopback\n /tmp/${xendomu}/etc/network/interfaces printf done.\n printf Setting up apt sources: echo deb http://archive.ubuntu.com/ubuntu gutsy main universe /tmp/${xendomu}/etc/apt/sources.list printf done.\n printf Updating apt: chroot /tmp/${xendomu} apt-get update printf done.\n printf Disabling threads: mv /tmp/${xendomu}/lib/tls /tmp/${xendomu}/lib/tls.disabled printf done.\n -- xen guest hangs after mounting filesystem https://bugs.launchpad.net/bugs/144631 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 139046] Re: no xm console prompt after debootstrap debian or ubuntu
I think we may be chasing the wrong problem by pursuing xen-tools for the fix. This problem is also 100% reproducible using manual domain creation. The only working fix I have found is to add extra='xencons=tty1' to the xendomu config file. This would be incorrect behaviour. It should work out-of-the-box. My method for creating the xendomu was using a self-written script as follows: #!/bin/sh ## # $Id: //depot/hosts/xen1/root/mkxenvm#3 $ # $DateTime: 2007/10/16 10:45:21 $ ## usage() { printf USAGE: ${0}\txendom xen volume group\n printf \t\t[root part size] [swap part size]\n exit } if [ -z ${1} ]; then usage; else xendomu=${1}; fi if [ -z ${2} ]; then usage; else xenvg=${2}; fi if [ -z ${3} ]; then rootsize=8G; else rootsize=${3}; fi if [ -z ${4} ]; then swapsize=2G; else swapsize=${4}; fi printf Creating root volume /dev/${xenvg}/${xendomu}_root with size ${rootsize}: lvcreate -L${rootsize} -n${xendomu}_root ${xenvg} printf done.\n printf Creating swap volume /dev/${xenvg}/${xendomu}_swap with size ${swapsize}: lvcreate -L${swapsize} -n${xendomu}_swap ${xenvg} printf done.\n printf Creating ext3 filesystem on /dev/${xenvg}/${xendomu}_root: mkfs.ext3 -L${xendomu}_root /dev/${xenvg}/${xendomu}_root printf done.\n printf Creating swap partition on /dev/${xenvg}/${xendomu}_swap: mkswap /dev/${xenvg}/${xendomu}_swap printf done.\n printf Mounting /dev/${xenvg}/${xendomu}_root on /tmp/${xendomu}: mkdir /tmp/${xendomu} printf Debootstrapping ${xendomu}: debootstrap gutsy /tmp/${xendomu} printf done.\n printf Copying modules to ${xendomu}: cp -r /lib/modules/`uname -r` /tmp/${xendomu}/lib/modules/ printf done.\n printf Setting up fstab: printf /dev/sda1\t/\t\text3\trw,errors=remount-ro\t0\t1\n /tmp/${xendomu}/etc/fstab printf /dev/sda2\tnone\t\tswap\tdefaults\t0\t0\n /tmp/${xendomu}/etc/fstab printf none\t\t/proc\t\tproc\trw,nosuid,noexec\t0\t0\n /tmp/${xendomu}/etc/fstab printf done.\n printf Setting up hostname: echo ${xendomu} /tmp/${xendomu}/etc/hostname printf done.\n printf Setting up hosts: printf 127.0.0.1\tlocalhost\n /tmp/${xendomu}/etc/hosts printf done.\n printf Setting up network interfaces: printf auto lo\n /tmp/${xendomu}/etc/network/interfaces printf iface lo inet loopback\n /tmp/${xendomu}/etc/network/interfaces printf done.\n printf Setting up apt sources: echo deb http://archive.ubuntu.com/ubuntu gutsy main universe /tmp/${xendomu}/etc/apt/sources.list printf done.\n printf Updating apt: chroot /tmp/${xendomu} apt-get update printf done.\n printf Disabling threads: mv /tmp/${xendomu}/lib/tls /tmp/${xendomu}/lib/tls.disabled printf done.\n -- no xm console prompt after debootstrap debian or ubuntu https://bugs.launchpad.net/bugs/139046 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 64032] Re: rpmstrap using /bin/sh when it should use /bin/bash
Will this be fixed in gutsy? I can confirm my own experience with the problem. It has to do the the echo -e statements in /usr/lib/rpmstrap/functions which don't work in dash. -- rpmstrap using /bin/sh when it should use /bin/bash https://bugs.launchpad.net/bugs/64032 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 151654] FAI kernel does not include working bnx2 driver (Broadcom, Dell)
Public bug reported: Binary package hint: fai-kernels Feisty FAI kernel is based on 2.6.17. bnx2 driver is not present. Attempted a rebuild with linux-source-2.6.20. Driver is present in source tree. Gutsy FAI kernel should include this. Should Feisty receive a backport? Perhaps Dapper too? Is it needed to fulfill the requirement for LTS? ** Affects: dapper-backports Importance: Undecided Assignee: Ubuntu FAI Developers (fai) Status: New ** Affects: feisty-backports Importance: Undecided Assignee: Alvin Cura (alvinc) Status: New ** Affects: fai-kernels (Ubuntu) Importance: Undecided Assignee: Ubuntu FAI Developers (fai) Status: New ** Changed in: fai-kernels (Ubuntu) Assignee: (unassigned) = Ubuntu FAI Developers (fai) ** Also affects: feisty-backports Importance: Undecided Status: New ** Also affects: dapper-backports Importance: Undecided Status: New ** Changed in: feisty-backports Assignee: (unassigned) = Ubuntu FAI Developers (fai) ** Changed in: dapper-backports Assignee: (unassigned) = Ubuntu FAI Developers (fai) ** Changed in: feisty-backports Assignee: Ubuntu FAI Developers (fai) = Alvin Cura (alvinc) -- FAI kernel does not include working bnx2 driver (Broadcom, Dell) https://bugs.launchpad.net/bugs/151654 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 123773] Re: 'SIOCSIFFLAGS: Cannot assign requested address' when setting up ip alias
Ah ha! strace -ff -F -o out ifup eth1:1 does the trick. ** Attachment added: zipfile of strace logs http://launchpadlibrarian.net/9574365/strace-ifup.zip -- 'SIOCSIFFLAGS: Cannot assign requested address' when setting up ip alias https://bugs.launchpad.net/bugs/123773 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 123773] Re: 'SIOCSIFFLAGS: Cannot assign requested address' when setting up ip alias
I can also confirm this. This error does not appear during ifdown. ifup shows this in strace: read(3, lo=lo\neth0=eth0\neth1=eth1\n, 4096) = 26 fstat64(4, {st_mode=S_IFREG|0644, st_size=0, ...}) = 0 mmap2(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0xb7f33000 read(3, , 4096) = 0 write(4, lo=lo\neth0=eth0\neth1=eth1\neth1:1..., 40) = 40 close(4)= 0 munmap(0xb7f33000, 4096)= 0 rename(/var/run/network/.ifstate.tmp, /var/run/network/ifstate) = 0 close(3)= 0 munmap(0xb7f34000, 4096)= 0 clone(child_stack=0, flags=CLONE_CHILD_CLEARTID|CLONE_CHILD_SETTID|SIGCHLD, child_tidptr=0xb7df0708) = 15673 waitpid(15673, SIOCSIFFLAGS: Cannot assign requested address [{WIFEXITED(s) WEXITSTATUS(s) == 0}], 0) = 15673 --- SIGCHLD (Child exited) @ 0 (0) --- I see a child exit, but I don't see where it forked. Perhaps I am being blind here? I don't really know what the child was, and didn't catch PID 15673 in the act. -- 'SIOCSIFFLAGS: Cannot assign requested address' when setting up ip alias https://bugs.launchpad.net/bugs/123773 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 111240] Re: Errors output when no firmware is installed
Actually, I see this behaviour during dpkg installation of a custom- built kernel as well. Also it is during update-initramfs. Running depmod. update-initramfs: Generating /boot/initrd.img-2.6.20.3-ubuntu1-sysdudez-fw-live find: /lib/firmware/2.6.20.3-ubuntu1-sysdudez-fw-live: No such file or directory find: /lib/firmware/2.6.20.3-ubuntu1-sysdudez-fw-live: No such file or directory find: /lib/firmware/2.6.20.3-ubuntu1-sysdudez-fw-live: No such file or directory find: /lib/firmware/2.6.20.3-ubuntu1-sysdudez-fw-live: No such file or directory find: /lib/firmware/2.6.20.3-ubuntu1-sysdudez-fw-live: No such file or directory find: /lib/firmware/2.6.20.3-ubuntu1-sysdudez-fw-live: No such file or directory -- Errors output when no firmware is installed https://bugs.launchpad.net/bugs/111240 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