[Bug 721576] Re: [natty] kernel panic on reboot with (U)EFI
I wanted to report in that I attempted to test mainline but was unable. I tried using the 2.6.38.6 debs from the kernel ppa: http://kernel.ubuntu.com/~kernel-ppa/mainline/v2.6.38.6-natty/ unfortunately when I use these the kernel crashes during boot with a message about plymouthd. I will attach a capture of the stack trace. ** Attachment added: IMG_0048.jpg https://bugs.launchpad.net/ubuntu/+source/linux/+bug/721576/+attachment/2126760/+files/IMG_0048.jpg -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/721576 Title: [natty] kernel panic on reboot with (U)EFI -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 721576] Re: [natty] kernel panic on reboot with (U)EFI
I can confirm this on an Intel DQ57TM motherboard (see bug #773364). As I noted in my duplicate bug report you can easily work around this bug by adding reboot=a,w to the kernel command line. So an easy fix is to push out an update to grub-efi that adds that to the kernel command line in /etc/default/grub. I am pretty sure this is how Windows works as well. EFI systems are required by spec to also have ACPI as a result I think Windows uses the ACPI tables as the reboot vector. It only uses EFI runtime services when booting or using the bcdedit.exe program. Cheers. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/721576 Title: [natty] kernel panic on reboot with (U)EFI -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 773364] [NEW] Kernel crash on reboot
Public bug reported: Just installed Ubuntu 11.04 on an Intel DQ57TM motherboard with the latest BIOS revision. Configured the system to boot using EFI. Ubuntu installed properly on the EFI system but when it came time to reboot the computer the kernel crashes right before the reboot operation is to take place. This happened both from the installer CD as well as the installed system. This happens so late in the process that it is not in any of the log files. So I had to snap pictures with my iphone camera. I will upload them. The fix is easy. All I had to do to remedy the problem was to add the following to the kernel configuration line via grub: reboot=a,w That command tells the kernel to use ACPI and not EFI runtime services to reboot. When using ACPI the kernel reboots perfectly. The bug is either in the kernel or my systems EFI firmware but either way when isntalling grub-efi it might be a good idea to modify /etc/default/grub to add reboot=a,w to the kernel command line. Pictures with crash will follow. ProblemType: Bug DistroRelease: Ubuntu 11.04 Package: linux-image-2.6.38-8-server 2.6.38-8.42 ProcVersionSignature: Ubuntu 2.6.38-8.42-server 2.6.38.2 Uname: Linux 2.6.38-8-server x86_64 AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.23. AplayDevices: List of PLAYBACK Hardware Devices card 0: Intel [HDA Intel], device 3: HDMI 0 [HDMI 0] Subdevices: 1/1 Subdevice #0: subdevice #0 Architecture: amd64 ArecordDevices: List of CAPTURE Hardware Devices AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jarrett1392 F xfce4-volumed CRDA: Error: [Errno 2] No such file or directory Card0.Amixer.info: Card hw:0 'Intel'/'HDA Intel at 0xfe52 irq 43' Mixer name : 'Intel IbexPeak HDMI' Components : 'HDA:80862804,80860038,0010' Controls : 4 Simple ctrls : 1 Card0.Amixer.values: Simple mixer control 'IEC958',0 Capabilities: pswitch pswitch-joined penum Playback channels: Mono Mono: Playback [on] Date: Fri Apr 29 11:42:24 2011 HibernationDevice: RESUME=UUID=b3756254-e1be-4e85-ac07-f3a6bece2650 InstallationMedia: Ubuntu-Server 11.04 Natty Narwhal - Release amd64 (20110426) IwConfig: lono wireless extensions. eth0 no wireless extensions. ProcEnviron: LANGUAGE=en_US:en LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.38-8-server root=UUID=0ce932b6-1cc1-4432-bd8c-d299b272367e ro quiet splash reboot=a,w rootflags=barrier=0,commit=60,user_xattr,acl,data=writeback,noatime,nodiratime vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-2.6.38-8-server N/A linux-backports-modules-2.6.38-8-server N/A linux-firmware 1.52 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/20/2011 dmi.bios.vendor: Intel Corp. dmi.bios.version: TMIBX10H.86A.0044.2011.0420.1427 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: DQ57TM dmi.board.vendor: Intel Corporation dmi.board.version: AAE70931-401 dmi.chassis.type: 3 dmi.modalias: dmi:bvnIntelCorp.:bvrTMIBX10H.86A.0044.2011.0420.1427:bd04/20/2011:svn:pn:pvr:rvnIntelCorporation:rnDQ57TM:rvrAAE70931-401:cvn:ct3:cvr: ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug natty -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/773364 Title: Kernel crash on reboot -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 773364] Re: Kernel crash on reboot
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/773364 Title: Kernel crash on reboot -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 773364] Re: Kernel crash on reboot
part 2 ** Attachment added: crash2.png https://bugs.launchpad.net/ubuntu/+source/linux/+bug/773364/+attachment/2096254/+files/crash2.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/773364 Title: Kernel crash on reboot -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 773364] Re: Kernel crash on reboot
here are the pictures of the console during the crash ** Attachment added: crash1.png https://bugs.launchpad.net/ubuntu/+source/linux/+bug/773364/+attachment/2096253/+files/crash1.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/773364 Title: Kernel crash on reboot -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 595448] Re: Slow boot caused by SATA controller reset
You most certainly have a different issue. Your kernel is not attempting to load ata_piix or pata_acpi modules. Only the SATA link to your SSD gives this error. The original bug this happened for every port in the machine even if a drive is not connected to it. Since you have a brand new cougar point chipset I am guessing the older AHCI driver is the 35 kernel series is to old. You may just need to use a more recent kernel. You could try forcing the link speed to 3gbs as both of your drives are SATA II but it looks like they are connected to the 6gbs STATA3 ports on the chipset. If you edit your grub boot line you can add libata.force=3.0 Not sure if that still works. It used to work on older kernels but I vaguely recall reading that ahci module now uses libahci and no longer relies on libata. or you could try adding libahci.skip_host_reset=1 but I am not sure if setting that parameter has any negative consequences. Anyway you should file a new bug report about your issue as it is different that the one in this bug report. On the plus side I see no reason why you need to rebuild your kernel so you can revert back to the ubuntu supplied packages. Your kernel appears to be correctly discovering all of your devices and loading the proper modules. Cheers -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/595448 Title: Slow boot caused by SATA controller reset -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 595448] Re: Slow boot caused by SATA controller reset
one little post script. you might also want to submit a bug report about the kernel not recognizing AES-NI. Your new Sandy Bridge chip most certainly supports AES-NI but the tail end of your dmesg log says that AES-NI was not detected. This will slow down any AES encryption on your system. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/595448 Title: Slow boot caused by SATA controller reset -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 595448] Re: Slow boot caused by SATA controller reset
sorry it did not work. it sounds like you have a different issue. could you post the following files as they might offer a clue. sudo dmidecode -q dmi.txt sudo lspci -vvv pci.txt sudo lsmod mods.txt P.S. the prearch issue was a typo on my part. the correct target is perarch not prearch. Again sorry about the typo. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/595448 Title: Slow boot caused by SATA controller reset -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 595448] Re: Slow boot caused by SATA controller reset
no I don't think perarch had anything to do with it. I think you have a different problem than the one I created this bug for. Anyway I forgot one more command. When you do get the chance also run sudo dmseg dmesg.txt but make sure you are booted from your custom compiled kernel when you run that command. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/595448 Title: Slow boot caused by SATA controller reset -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 595448] Re: Slow boot caused by SATA controller reset
Sorry the problem still exists in 11.04. You need to build your own kernel to remedy it. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/595448 Title: Slow boot caused by SATA controller reset -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 595448] Re: Slow boot caused by SATA controller reset
You edited it in the wrong place. Sorry I wish I could make this easy so that you could just download a kernel from my PPA but I have not figured out how to upload a kernel to the PPA build service. But here are some instructions that should produce a fixed kernel for you. These instructions are for 10.10. If you want 11.04 you need to modify this procedure slightly. Now before you start I would recommend that you install one of the kernels supplied by Ubuntu that you do not want to use. IOW if you want to use generic install linux-server and linux- headers-server. Or if you want to use server do the opposite. This way you can uninstall the Ubuntu supplied generic kernel so that yours does not have version conflicts with the Ubuntu supplied packages. Once you have installed the server kernel and rebooted then uninstall the Ubuntu supplied generic packages. First install some required software. sudo apt-get install fakeroot build-essential crash kexec-tools makedumpfile kernel-wedge git-core libncurses5 libncurses5-dev libelf-dev asciidoc binutils-dev libqt3-mt-dev next create a new directory to work from lets call it ~/ubuntu but name it what ever you like. now mkdir ~/ubuntu cd ~/ubuntu now clone the Ubuntu kernel git tree: git clone git://kernel.ubuntu.com/ubuntu/ubuntu-maverick.git This will take a while and when done you should have a folder called ubuntu-maverick. it would be a good idea right now to create a tar.gz backup of that folder. That way if you want to start over you don't need to redownload the git tree. You can just delete the ubuntu-maverick folder and then uncompress your clean backup. either way change in to that folder cd ubuntu-maverick now you need to checkout released kernel from the git repository. the git repository contains all of the kernels and by default it is checked out in the state of the kernel that the devs are currently working on but have not yet released. So it may have bugs and you want to go back in time a bit to the most recent public release which should give you a known good kernel source tree to start with. as of right now (4-20-2011) that is 2.6.35-28.50 . typing in the following command will list all of the kernels git tag -l In that list you should see Ubuntu-2.6.35-28.50 which is what we will use for this. So now we need to check that tag out. we can do that with the following command git checkout Ubuntu-2.6.35-28.50 -b fixed That command will check out that taged release and create a new named branch called fixed You now have that revision checked out so we can start the build process. First you need to prep the build tree by running a couple of scripts. so run: fakeroot debian/rules clean debian/rules updateconfigs now you are ready to edit your configs. you should not edit the config files directly. instead you should use the ubuntu kernel configure script. Now you need to know what flavor and platform you want. in these instructions I will use 64 bit generic as that is what I want. To begin the edit process run the following command: debian/rules editconfigs this command will start and interactive process that allows you to properly edit the configurations of all of the various builds of the kernel. The first question it asks is if I want to edit the amd64/config.flavor.generic. Since this is the one I want I will say yes here. This will bring up the NCRUSES based GUI that is used for editing the kernel configs. Now use the arrow keys on your keyboard to navigate to: device drivers - Serial ATA and Parallel ATA Drivers. Next arrow down until AHCI SATA support is highlighted. It should have a M to the left of it. press the space bar repeatedly until that changes to *. This means it will build the AHCI support in to the kernel. Now just press esc repeatedly until it asks you if you want to save your new configuration. Say yes. That will exit you back out to the terminal and the script will be asking you if you want to edit the next flavor. Just say no to all of the flavors you don't care about. You are now ready to build your flavor. So prep the build process by running debian/rules updateconfigs fakeroot debian/rules clean now its time to build. so run the following commands: skipabi=true skipmodule=true fakeroot debian/rules binary-indep skipabi=true skipmodule=true fakeroot debian/rules binary-prearch skipabi=true skipmodule=true fakeroot debian/rules binary-generic that last one will take a while so go grab a coffee. when its all done move up a directory cd ../ now just install the debs. sudo dpkg -i *.deb reboot and you should be good. Make sure its working with cat /boot/config-2.6.35-28-generic | grep AHCI which should show CONFIG_SATA_AHCI=y Cheers and sorry if there are any typos in this. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/595448 Title: Slow boot caused by SATA controller reset -- ubuntu-bugs
[Bug 595448] Re: Slow boot caused by SATA controller reset
Nope. This problem has nothing to do with X. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/595448 Title: Slow boot caused by SATA controller reset -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 595448] Re: Slow boot caused by SATA controller reset
yes you need to rebuild the kernel. The problem is the pata_acpi driver that is built in to the kernel. That driver is meant as a driver of last resort. The kernel developers only load it when all other drivers fail to load. BUT, they way the ubuntu kernel devs build the Lucid kernel they changed the ahci driver to be a loadable module. So prior to lucid ahci.ko was present in the kernel image itself and thus would load just fine and the kernel would never even try to load the dreaded papa_acpi driver. I think they made this change to fix some broken laptops. I search around launchpad and found some folks complain about kernel's prior to lucid because the ahci driver was built in these people could not disable (via blacklisting it). On their systems AHCI caused disk corruption but their BIOS did not allow them to switch back to ATA mode. So I guess the ubuntu devs made this change to accommodate these people and their broken laptops. Anyway you need to build your own kernel. https://help.ubuntu.com/community/Kernel/Compile Just be sure to run: debian/rules editconfigs and then (for either x86 or x86-64 edit your config and change ahci to be built in to the kernel instead of as a loaded module) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/595448 Title: Slow boot caused by SATA controller reset -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 595448] Re: Slow boot caused by SATA controller reset
just tested with 2.6.35-23.40 in ubuntu 10.10 and the bug is still present. Should I just give up at this point? -- Slow boot caused by SATA controller reset https://bugs.launchpad.net/bugs/595448 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 595448] Re: Slow boot caused by SATA controller reset
Just tested with the new 2.6.35-22.34 kernel that was pushed out today. The bug is still present. -- Slow boot caused by SATA controller reset https://bugs.launchpad.net/bugs/595448 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 595448] Re: Slow boot caused by SATA controller reset
This bug still exists in Maverick. Just retested with 2.6.35-22-server. Is anyone out there even tracking this bug or should I just give up? -- Slow boot caused by SATA controller reset https://bugs.launchpad.net/bugs/595448 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 595448] Re: Slow boot caused by SATA controller reset
** Tags added: kconfig -- Slow boot caused by SATA controller reset https://bugs.launchpad.net/bugs/595448 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 627973] Re: Assertion failed at socket.c:629
UPDATE: I did some more testing on this. I found out that the TLS HMAC errors were the fault of an update to Viscosity (Mac OSX OpenVPN client). The program was incorrectly passing '0' for the direction of the ta.key file on the clients. So the good news is that the package in your PPA fixes this issue completely. The TLS HMAC issue was unrelated. -- Assertion failed at socket.c:629 https://bugs.launchpad.net/bugs/627973 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to openvpn in ubuntu. -- 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 367169] Re: GConf Error: Failed to contact configuration server; durring ssh X11 forwarding
I just ran in to this today on a fresh Ubunutu Server 10.04.1 AMD64 install fully patched. Both my ~/.dbus directory and ~/.esd_auth were owned by root:root for some reason. I had not seen the thing about .esd_auth reported so I just wanted to let you know. Maybe that will point to the component that is setting these permissions incorrectly. Cheers -- GConf Error: Failed to contact configuration server; durring ssh X11 forwarding https://bugs.launchpad.net/bugs/367169 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 627973] Re: Assertion failed at socket.c:629
UPDATE: I did some more testing on this. I found out that the TLS HMAC errors were the fault of an update to Viscosity (Mac OSX OpenVPN client). The program was incorrectly passing '0' for the direction of the ta.key file on the clients. So the good news is that the package in your PPA fixes this issue completely. The TLS HMAC issue was unrelated. -- Assertion failed at socket.c:629 https://bugs.launchpad.net/bugs/627973 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 627973] Re: Assertion failed at socket.c:629
I tested the AMD64 build on Lucid today. It fixes the socket assertion failure but still features a regression relative to upstream. With the build from you PPA and the config file I provided I get the following in syslog: TLS: Initial packet from [AF_INET]192.5.38.152:49308, sid=713f6ed1 b48b32c4 Authenticate/Decrypt packet error: packet HMAC authentication failed TLS Error: incoming packet authentication failed from [AF_INET]192.5.38.152:49308 Fatal TLS error (check_tls_errors_co), restarting OpenVPN started by inetd/xinetd cannot restart... Exiting. - To fix it I had to comment out the tls-auth lines in my client and server configuration files. For example I commented this out in my server configuration file: # tls-auth /etc/openvpn/ta.key 0 # This file is secret After doing that it works like upstream, except I am not getting the PSK protection of the TLS negotiation. So its still not working right but at least it no longer produces the socket assertion message. -- Assertion failed at socket.c:629 https://bugs.launchpad.net/bugs/627973 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to openvpn in ubuntu. -- 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 627973] Re: Assertion failed at socket.c:629
Cant't do it. I need multiple clients through one port and each needs their own tap device. We use broadcast/multi-cast and stuff like wireshark. So the scalable tun approach is not for us. Basically everyone needs their own unique MAC address. -- Assertion failed at socket.c:629 https://bugs.launchpad.net/bugs/627973 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to openvpn in ubuntu. -- 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 627973] Re: Assertion failed at socket.c:629
I tested the AMD64 build on Lucid today. It fixes the socket assertion failure but still features a regression relative to upstream. With the build from you PPA and the config file I provided I get the following in syslog: TLS: Initial packet from [AF_INET]192.5.38.152:49308, sid=713f6ed1 b48b32c4 Authenticate/Decrypt packet error: packet HMAC authentication failed TLS Error: incoming packet authentication failed from [AF_INET]192.5.38.152:49308 Fatal TLS error (check_tls_errors_co), restarting OpenVPN started by inetd/xinetd cannot restart... Exiting. - To fix it I had to comment out the tls-auth lines in my client and server configuration files. For example I commented this out in my server configuration file: # tls-auth /etc/openvpn/ta.key 0 # This file is secret After doing that it works like upstream, except I am not getting the PSK protection of the TLS negotiation. So its still not working right but at least it no longer produces the socket assertion message. -- Assertion failed at socket.c:629 https://bugs.launchpad.net/bugs/627973 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 627973] Re: Assertion failed at socket.c:629
Cant't do it. I need multiple clients through one port and each needs their own tap device. We use broadcast/multi-cast and stuff like wireshark. So the scalable tun approach is not for us. Basically everyone needs their own unique MAC address. -- Assertion failed at socket.c:629 https://bugs.launchpad.net/bugs/627973 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 627973] Re: Assertion failed at socket.c:629
I can't test them today due to work conflicts. With any luck I will get them tested on Friday. Cheers -- Assertion failed at socket.c:629 https://bugs.launchpad.net/bugs/627973 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 627973] Re: Assertion failed at socket.c:629
Ok I would be happy to test. Not sure if its an issue but that system is now running Maverick and no longer runs Lucid. So any test won't be apples to apples. -- Assertion failed at socket.c:629 https://bugs.launchpad.net/bugs/627973 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to openvpn in ubuntu. -- 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 627973] Re: Assertion failed at socket.c:629
No worries. I cobbled together a Lucid system to test this so no need to worry about Maverick anymore. I just wanted to thank you for the prompt attention you have shown this bug. Are you a Canonical employee? If so is there anyway I can provide feedback to let your employer know how pleased I am with the service you have provided? I like to make sure hard work is rewarded whenever I can. Cheers -- Assertion failed at socket.c:629 https://bugs.launchpad.net/bugs/627973 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to openvpn in ubuntu. -- 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 627973] Re: Assertion failed at socket.c:629
Ok I would be happy to test. Not sure if its an issue but that system is now running Maverick and no longer runs Lucid. So any test won't be apples to apples. -- Assertion failed at socket.c:629 https://bugs.launchpad.net/bugs/627973 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 627973] Re: Assertion failed at socket.c:629
No worries. I cobbled together a Lucid system to test this so no need to worry about Maverick anymore. I just wanted to thank you for the prompt attention you have shown this bug. Are you a Canonical employee? If so is there anyway I can provide feedback to let your employer know how pleased I am with the service you have provided? I like to make sure hard work is rewarded whenever I can. Cheers -- Assertion failed at socket.c:629 https://bugs.launchpad.net/bugs/627973 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 627973] Re: Assertion failed at socket.c:629
Not using p2p mode. Here is my server config file script-security 3 inetd nowait proto tcp-server tls-server dev tap up /etc/openvpn/per-user-up.sh down /etc/openvpn/per-user-down.sh ca /etc/openvpn/ca.crt cert /etc/openvpn/server.crt key /etc/openvpn/server.key # This file should be kept secret dh /etc/openvpn/dh2048.pem keepalive 10 120 tls-auth /etc/openvpn/ta.key 0 # This file is secret cipher AES-128-CBC # AES comp-lzo user nobody group nogroup verb 4 -- Assertion failed at socket.c:629 https://bugs.launchpad.net/bugs/627973 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to openvpn in ubuntu. -- 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 627973] Re: Assertion failed at socket.c:629
Here are my related config files. Hopefully these will help as well.
per-user-up.sh
#!/bin/bash
#
# Set up Ethernet bridge on Linux
# Requires: bridge-utils
#
# Define Bridge Interface
br=bridge0
#NOTE $1 contains the tap interface name
brctl addif $br $1
ifconfig $1 mtu $2 promisc up
--
per-user-down.sh
--
#!/bin/bash
#
# Tear down Ethernet bridge on Linux
# Requires: bridge-utils
#
# Define Bridge Interface
br=bridge0
# NOTE #1 contains the tap devce name
brctl delif $br $1
ifconfig $1 down
openvpn --rmtun --dev $1
-
/etc/xinet.d/openvpn
service echo
{
disable = no
type= UNLISTED
port= 1194
socket_type = stream
protocol= tcp
user= root
wait= no
server = /usr/sbin/openvpn
server_args = --config /etc/openvpn/tcp-tap.conf.backup
}
-
The funny name for the server_args value is to prevent the SYSVINIT scripts
from trying to start a server that should only be started by xinet.d.
I have a bridge created in my /etc/networking/interfaces file called
bridge0
--
Assertion failed at socket.c:629
https://bugs.launchpad.net/bugs/627973
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to openvpn in ubuntu.
--
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 627973] Re: Assertion failed at socket.c:629
Not using p2p mode. Here is my server config file script-security 3 inetd nowait proto tcp-server tls-server dev tap up /etc/openvpn/per-user-up.sh down /etc/openvpn/per-user-down.sh ca /etc/openvpn/ca.crt cert /etc/openvpn/server.crt key /etc/openvpn/server.key # This file should be kept secret dh /etc/openvpn/dh2048.pem keepalive 10 120 tls-auth /etc/openvpn/ta.key 0 # This file is secret cipher AES-128-CBC # AES comp-lzo user nobody group nogroup verb 4 -- Assertion failed at socket.c:629 https://bugs.launchpad.net/bugs/627973 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 595448] Re: Slow boot caused by SATA controller reset
Ummm So whats the status of this. The problem persists in Maverick Beta 2. Is this fix not going to get incorporated? If not can you at least mark this bug as won't fix so I can move on with my life and setup an internal system for deploying a custom compiled kernel to all of our machines? -- Slow boot caused by SATA controller reset https://bugs.launchpad.net/bugs/595448 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 627973] Re: Assertion failed at socket.c:629
Here are my related config files. Hopefully these will help as well.
per-user-up.sh
#!/bin/bash
#
# Set up Ethernet bridge on Linux
# Requires: bridge-utils
#
# Define Bridge Interface
br=bridge0
#NOTE $1 contains the tap interface name
brctl addif $br $1
ifconfig $1 mtu $2 promisc up
--
per-user-down.sh
--
#!/bin/bash
#
# Tear down Ethernet bridge on Linux
# Requires: bridge-utils
#
# Define Bridge Interface
br=bridge0
# NOTE #1 contains the tap devce name
brctl delif $br $1
ifconfig $1 down
openvpn --rmtun --dev $1
-
/etc/xinet.d/openvpn
service echo
{
disable = no
type= UNLISTED
port= 1194
socket_type = stream
protocol= tcp
user= root
wait= no
server = /usr/sbin/openvpn
server_args = --config /etc/openvpn/tcp-tap.conf.backup
}
-
The funny name for the server_args value is to prevent the SYSVINIT scripts
from trying to start a server that should only be started by xinet.d.
I have a bridge created in my /etc/networking/interfaces file called
bridge0
--
Assertion failed at socket.c:629
https://bugs.launchpad.net/bugs/627973
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 627973] [NEW] Assertion failed at socket.c:629
Public bug reported: Binary package hint: openvpn Description:Ubuntu 10.04.1 LTS Release:10.04 openvpn: Installed: 2.1.0-1ubuntu1.1 Candidate: 2.1.0-1ubuntu1.1 Version table: *** 2.1.0-1ubuntu1.1 0 500 http://us.archive.ubuntu.com/ubuntu/ lucid-updates/main Packages 100 /var/lib/dpkg/status 2.1.0-1ubuntu1 0 500 http://us.archive.ubuntu.com/ubuntu/ lucid/main Packages What I expected: I have open vpn configured for bridged networking off a single port via xinetd over TCP. That is to say each incoming connection on port 22 (I need to use this port). spawns a new instance of /usr/sbin/openvpn with the inet nowait option. What happens instead: xinetd properly spawns openvpn but then openvpn aborts with: Assertion failed at socket.c:629 the following is what shows up in daemon.log: OpenVPN 2.1.0 x86_64-pc-linux-gnu [SSL] [LZO2] [EPOLL] [PKCS11] [MH] [PF_INET6] [eurephia] built on Jul 20 2010 IMPORTANT: OpenVPN's default port number is now 1194, based on an official port number assignment by IANA. OpenVPN 2.0-beta16 and earlier used 5000 as the default port. NOTE: the current --script-security setting may allow this configuration to call user-defined scripts Diffie-Hellman initialized with 2048 bit key /usr/bin/openssl-vulnkey -q -b 2048 -m modulus omitted Control Channel Authentication: using '/etc/openvpn/ta.key' as a OpenVPN static key file Outgoing Control Channel Authentication: Using 160 bit message hash 'SHA1' for HMAC authentication Incoming Control Channel Authentication: Using 160 bit message hash 'SHA1' for HMAC authentication LZO compression initialized Control Channel MTU parms [ L:1592 D:168 EF:68 EB:0 ET:0 EL:0 ] TUN/TAP device tap0 opened TUN/TAP TX queue length set to 100 /etc/openvpn/per-user-up.sh tap0 1500 1592 init Data Channel MTU parms [ L:1592 D:1450 EF:60 EB:135 ET:32 EL:0 AF:3/1 ] Local Options hash (VER=V4): '3d4363c6' Expected Remote Options hash (VER=V4): '29f6c8b2' GID set to nogroup UID set to nobody Assertion failed at socket.c:629 -- This problem does not exist upstream. To fix the problem I simply compiled and installed openvpn-2.1.3 from source and installed it to /usr/local. I then updated my xinetd service file to point to /usr/local/sbin/openvpn and the problem went away. -- ProblemType: Bug DistroRelease: Ubuntu 10.04 Package: openvpn 2.1.0-1ubuntu1.1 [modified: usr/sbin/openvpn] Uname: Linux 2.6.35.4-quick x86_64 Architecture: amd64 Date: Wed Sep 1 06:27:14 2010 ProcEnviron: LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: openvpn ** Affects: openvpn (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug lucid -- Assertion failed at socket.c:629 https://bugs.launchpad.net/bugs/627973 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to openvpn in ubuntu. -- 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 627973] Re: Assertion failed at socket.c:629
** Attachment added: Dependencies.txt https://bugs.launchpad.net/bugs/627973/+attachment/1534064/+files/Dependencies.txt -- Assertion failed at socket.c:629 https://bugs.launchpad.net/bugs/627973 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to openvpn in ubuntu. -- 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 627973] [NEW] Assertion failed at socket.c:629
Public bug reported: Binary package hint: openvpn Description:Ubuntu 10.04.1 LTS Release:10.04 openvpn: Installed: 2.1.0-1ubuntu1.1 Candidate: 2.1.0-1ubuntu1.1 Version table: *** 2.1.0-1ubuntu1.1 0 500 http://us.archive.ubuntu.com/ubuntu/ lucid-updates/main Packages 100 /var/lib/dpkg/status 2.1.0-1ubuntu1 0 500 http://us.archive.ubuntu.com/ubuntu/ lucid/main Packages What I expected: I have open vpn configured for bridged networking off a single port via xinetd over TCP. That is to say each incoming connection on port 22 (I need to use this port). spawns a new instance of /usr/sbin/openvpn with the inet nowait option. What happens instead: xinetd properly spawns openvpn but then openvpn aborts with: Assertion failed at socket.c:629 the following is what shows up in daemon.log: OpenVPN 2.1.0 x86_64-pc-linux-gnu [SSL] [LZO2] [EPOLL] [PKCS11] [MH] [PF_INET6] [eurephia] built on Jul 20 2010 IMPORTANT: OpenVPN's default port number is now 1194, based on an official port number assignment by IANA. OpenVPN 2.0-beta16 and earlier used 5000 as the default port. NOTE: the current --script-security setting may allow this configuration to call user-defined scripts Diffie-Hellman initialized with 2048 bit key /usr/bin/openssl-vulnkey -q -b 2048 -m modulus omitted Control Channel Authentication: using '/etc/openvpn/ta.key' as a OpenVPN static key file Outgoing Control Channel Authentication: Using 160 bit message hash 'SHA1' for HMAC authentication Incoming Control Channel Authentication: Using 160 bit message hash 'SHA1' for HMAC authentication LZO compression initialized Control Channel MTU parms [ L:1592 D:168 EF:68 EB:0 ET:0 EL:0 ] TUN/TAP device tap0 opened TUN/TAP TX queue length set to 100 /etc/openvpn/per-user-up.sh tap0 1500 1592 init Data Channel MTU parms [ L:1592 D:1450 EF:60 EB:135 ET:32 EL:0 AF:3/1 ] Local Options hash (VER=V4): '3d4363c6' Expected Remote Options hash (VER=V4): '29f6c8b2' GID set to nogroup UID set to nobody Assertion failed at socket.c:629 -- This problem does not exist upstream. To fix the problem I simply compiled and installed openvpn-2.1.3 from source and installed it to /usr/local. I then updated my xinetd service file to point to /usr/local/sbin/openvpn and the problem went away. -- ProblemType: Bug DistroRelease: Ubuntu 10.04 Package: openvpn 2.1.0-1ubuntu1.1 [modified: usr/sbin/openvpn] Uname: Linux 2.6.35.4-quick x86_64 Architecture: amd64 Date: Wed Sep 1 06:27:14 2010 ProcEnviron: LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: openvpn ** Affects: openvpn (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug lucid -- Assertion failed at socket.c:629 https://bugs.launchpad.net/bugs/627973 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 627973] Re: Assertion failed at socket.c:629
** Attachment added: Dependencies.txt https://bugs.launchpad.net/bugs/627973/+attachment/1534064/+files/Dependencies.txt -- Assertion failed at socket.c:629 https://bugs.launchpad.net/bugs/627973 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 595489] Re: lvm snapshot causes deadlock in 2.6.35
The Lucid SRU update worked for me. I just tested with the server kernel build on AMD64. I am now to: sudo telinit S lvcreate -L 500m -n rootsnap -s /dev/vg0/root that used to hang but now works as expected. Nice job guys :) I appreciate all the hard work in getting this fixed for Lucid. -- lvm snapshot causes deadlock in 2.6.35 https://bugs.launchpad.net/bugs/595489 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 611877] [NEW] race condition in upstart network-interface.conf
Public bug reported: Binary package hint: ifupdown I think there is an error in the Lucid /etc/init/networking- interfaces.conf file. the pre-start script references /var/run but /var/run is only available after mountall sends the local-filesystems event. So I think that maybe the start on condition in network-interfaces.conf should be: start on (net-device-added and local-filesystems) instead of just start on net-device added Cheers ** Affects: ifupdown (Ubuntu) Importance: Undecided Status: New -- race condition in upstart network-interface.conf https://bugs.launchpad.net/bugs/611877 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 595448] Re: Slow boot caused by SATA controller reset
Just wanted to add a few more details. It appears the problem is that with the Lucid kernel config is that three different drivers are fighting it out for control of my disk controller. The system is configured in the BIOS for AHCI mode. By default in Lucid first ata_piix loads and initializes the controller. Next pata_acpi loads and tries to initialize the controller. Then finally ahci.ko loads and tries to initialize the controller. ata_piix and pata_acpi are built in to the kernel while ahci.ko is a loadable module. getting rid of the boot delay is as simple as rebuilding the kernel with AHCI built in to the kernel. Doing this fixes the bug. however I just wanted to note that the system still appears funny to me. For example disk utility aka palimpest will show my SATA Host Adapter with my hard drives and DVD drive connected to it. But it also shows a secondary ide controller with nothing connected to it that is being driven by ata_piix. This board lacks ide, its pure sata, and with the BIOS configured for AHCI I do not expect to see an ide controller present. To completely remedy this and make the system appear as expected (at least what I expect) I have to also change ata_piix and pata_ahci to be loadable modules and then blacklist them along with ata_generic in /etc/modprobe.conf.d/blacklist.conf. Doing that makes the system function as expected. That is to say only ahci is loaded and controlling the SATA controller. Cheers, Jarrett P.S. I just re-verified all of this today using the lucid git tree and building the Ubuntu-2.6.32-24.38 named tag from git. -- Slow boot caused by SATA controller reset https://bugs.launchpad.net/bugs/595448 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 595448] Re: Slow boot caused by SATA controller reset
One last tidbit. I finally figured out what the IDE controller was and why it was loading and being controlled by ata_piix. This board is an Intel vPro board and it supports IDE redirection over LAN. Basically at the firmware level it lets be remote mount an ISO image as if it was a locally connected CD-ROM drive. This virtual IDE CD-ROM drive is what is connected to the controller that ata_piix is driving. So the system was behaving as expected outside of the very slow boot. So in summary. all that is needed to fix this bug is to change CONFIG_SATA_AHCI= to 'y' from 'm'. I verified it by making the change in debian.master/config/amd64/config/config.flavour.* I then rebuilt the lucid kernel, installed it and I am a happy ubuntu user again. -- Slow boot caused by SATA controller reset https://bugs.launchpad.net/bugs/595448 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 595448] Re: Slow boot caused by SATA controller reset
Its a SATA DVD-RW drive so suggestions 1 and 2 don't make any sense. As for number 3, I stated in my first post the motherboard BIOS is the latest available. The DVD drive firmware is also the most recent available. As for 45, they are not applicable. The boot delay I submitted this bug before occurs well before the initramfs is expanded let alone the root file system mounted. So they just don't apply at all. Let me be very clear here. This pause in boot up occurs very early during kernel initialization before the initramfs is utilized. For example if I boot with a GRUB configuration line that has no initramfs specified the boot delay is still present. Of course the system fails to boot if I do this but I did try it out just to be sure it was not an initramfs issue which is why I submitted the bug against the kernel and not some component of the initramfs bootup system. I am not sure what in general you want me to check for a workaround. As I previously posted I have already provided a solution. The karmic kernel .config file had CONFIG_SATA_AHCI=y specified while lucid specifies CONFIG_SATA_AHCI=m. this is the problem. It is a simple regression from karmic and is why I added the bitesize tag per the instructions on the wiki. -- Slow boot caused by SATA controller reset https://bugs.launchpad.net/bugs/595448 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 595448] Re: Slow boot caused by SATA controller reset
** Tags added: bitesize -- Slow boot caused by SATA controller reset https://bugs.launchpad.net/bugs/595448 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 595448] Re: Slow boot caused by SATA controller reset
YEAH! I have a fix. As soon as I changed a few of the ACHI drivers to be compiled in (like they were in karmic) from being loadable modules (like they are in lucid) the problem went away. for the record here are the changes I made to the config file. diff lucidconfig linux-2.6/.config 3,4c3,4 # Linux kernel version: 2.6.35-rc3 # Thu Jun 24 11:15:51 2010 --- # Linux kernel version: 2.6.35-rc3-ahci # Fri Jun 25 13:21:38 2010 1646c1646 CONFIG_SATA_AHCI=m --- CONFIG_SATA_AHCI=y 1648c1648 CONFIG_SATA_INIC162X=m --- CONFIG_SATA_INIC162X=y 1693c1693 CONFIG_PATA_IT821X=m --- CONFIG_PATA_IT821X=y 1719c1719 CONFIG_PATA_MPIIX=m --- CONFIG_PATA_MPIIX=y So is it possible this change can get integrated in to official Ubuntu kernels or am I going to be stuck compiling kernels from source on this machine? -- Slow boot caused by SATA controller reset https://bugs.launchpad.net/bugs/595448 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 595448] Re: Slow boot caused by SATA controller reset
I now have more info. It is most certainly a kernel config file issue. If I build from linux git tree using the config-2.6.31-0206113-generic as the base config file it produces a good kernel. I tested this with both v2.6.31 and v2.6.35-rc3. If I do the exact same thing but instead use config-2.6.32-22-generic that ships with lucid then I get the big pause during boot. just to be clear the following lists exactly what I am doing: $ git clone git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux-2.6.git $ git checkout v2.6.35-rc3 $ cd linux-2.6 $ cp /boot/config2.6.31-0206113-generic .config $ yes '' | make oldconfig $ make-kpkg clean $ CONCURRENCY_LEVEL=`getconf _NPROCESSORS_ONLN` fakeroot make-kpkg --initrd --append-to-version=-bughunt kernel_image kernel_headers $ cd .. $ sudo dpkg -i *.deb $ sudo update-initramfs -c -k 2.6.35-rc3-bunghunt $ sudo update-grub $ sudo reboot This procedure produces a good kernel If instead I replace line #4 above with cp /boot/config-2.6.32-22-generic .confg then it produces a bad kernel. I will attach a diff of the two kernel config files. -- Slow boot caused by SATA controller reset https://bugs.launchpad.net/bugs/595448 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 595448] Re: Slow boot caused by SATA controller reset
This is a diff of the lucid vs 2.6.31-0206113-generic config files ** Attachment added: 31diff.txt http://launchpadlibrarian.net/50853456/31diff.txt -- Slow boot caused by SATA controller reset https://bugs.launchpad.net/bugs/595448 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 595448] Re: Slow boot caused by SATA controller reset
Ok at this point I have done all the testing I know how to do and I will have to wait for guidance. As far as I an tell this bug affects mainline as far back as 2.6.30. I tested 2.6.30 up to the current rc for 2.6.35 all built from Linus git tree. They all have the problem. However Ubuntu 9.10 did not have this issue nor does the 2.6.31-0206113-generic kernel that is available from the kernel teams ppa archive. So it looks like there is some patch or config difference between Linus 2.6.31 and the 2.6.31-0206113-generic builds. I do not know how to track down such a change. I would be happy to further test the system if someone would give me some guidance in to how to narrow down what is causing the problem. Thanks -- Slow boot caused by SATA controller reset https://bugs.launchpad.net/bugs/595448 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 595448] Re: Slow boot caused by SATA controller reset
Updating progress so far. Seeing as how I tested the 2.6.31-0206113-generic deb file I assumed v2.6.31 of the mainline repo was also good. So I ran a git bisect between 2.6.31 and 2.6.32. Unfortunantly that looks like it was a big waste of time because on a hunch I tested v2.6.31 via mainline git and it also has the problem. So there is some difference between 2.6.31 in the linus git repo and whatever was done to build the 2.6.31-0206113-generic that is provided by the kernel team. I am now testing with v2.6.30 from linus git repo to see the problem is present in that build. If v2.6.30 from the git repo works ok I will bisect between 2.6.30 and 2.6.31. Will report more later. -- Slow boot caused by SATA controller reset https://bugs.launchpad.net/bugs/595448 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 595448] Re: Slow boot caused by SATA controller reset
Just tested with Mainline Kernel 2.6.34-lucid (aka 2.6.34-020634-generic) and the problem still persists. Removing needs- upstream-testing tag per automated instructions. ** Tags removed: needs-upstream-testing -- Slow boot caused by SATA controller reset https://bugs.launchpad.net/bugs/595448 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 595448] Re: Slow boot caused by SATA controller reset
Just for completeness I also just tested with the 2.6.35 current build which as of today is 2.6.35-999.201006151505_amd64.deb and the problem is still present there as well. ** Changed in: linux (Ubuntu) Status: Incomplete = New -- Slow boot caused by SATA controller reset https://bugs.launchpad.net/bugs/595448 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 595448] Re: Slow boot caused by SATA controller reset
I just tested 2.6.31-0206113-generic and the problem is not present in that build. I am now gearing up to run a git bisect. It will be my first time doing a bisect some hopefully it will go well. Any advice would be appreciated. -- Slow boot caused by SATA controller reset https://bugs.launchpad.net/bugs/595448 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 595448] [NEW] Slow boot caused by SATA controller reset
Public bug reported: Ubuntu 10.04 suffers from a very slow boot on due to a 10 second or so pause while the kernel sets up the SATA controller. The problem occurs on every boot at this point in the kernel initialization sequence: ata1: link is slow to respond, please be patient (ready=0) Jun 15 13:51:02 jmvpro kernel: [ 14.780019] ata1: SRST failed (errno=-16) Jun 15 13:51:02 jmvpro kernel: [ 20.330017] ata1: link is slow to respond, please be patient (ready=0) Jun 15 13:51:02 jmvpro kernel: [ 24.830018] ata1: SRST failed (errno=-16) Jun 15 13:51:02 jmvpro kernel: [ 30.380018] ata1: link is slow to respond, please be patient (ready=0) Jun 15 13:51:02 jmvpro kernel: [ 59.840018] ata1: SRST failed (errno=-16) Jun 15 13:51:02 jmvpro kernel: [ 59.840022] ata1: limiting SATA link speed to 1.5 Gbps Jun 15 13:51:02 jmvpro kernel: [ 64.850019] ata1: SRST failed (errno=-16) Jun 15 13:51:02 jmvpro kernel: [ 64.850021] ata1: reset failed, giving up This is an Intel DQ45CB motherboard with the latest bios. I believe ata1 is the eSATA port. I think my hard disks are connected to ata2 and ata3 This problem is also present in the 2.6.35 maverick backport kernel from the kernel-ppa. This problem did not occur with ubuntu 9.10. ProblemType: Bug DistroRelease: Ubuntu 10.04 Package: linux-image-2.6.32-22-generic 2.6.32-22.36 Regression: Yes Reproducible: Yes ProcVersionSignature: Ubuntu 2.6.32-22.36-generic 2.6.32.11+drm33.2 Uname: Linux 2.6.32-22-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: AD198x Analog [AD198x Analog] Subdevices: 2/2 Subdevice #0: subdevice #0 Subdevice #1: subdevice #1 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jarrett1584 F pulseaudio CRDA: Error: [Errno 2] No such file or directory Card0.Amixer.info: Card hw:0 'Intel'/'HDA Intel at 0xe062 irq 22' Mixer name : 'Analog Devices AD1882' Components : 'HDA:11d41882,80861003,00100300' Controls : 41 Simple ctrls : 24 CurrentDmesg: [ 77.952035] e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX/TX [ 77.952836] ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready [ 88.240013] eth0: no IPv6 routers present [ 422.836625] Too many connections Date: Thu Jun 17 06:44:31 2010 HibernationDevice: RESUME=UUID=f8a7aaf0-a741-457b-ab95-2b06f7bc8814 InstallationMedia: Ubuntu 10.04 LTS Lucid Lynx - Release amd64 (20100427.1) IwConfig: lono wireless extensions. eth0 no wireless extensions. ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.32-22-generic root=/dev/mapper/vg0-root ro ProcEnviron: LANG=en_US.utf8 SHELL=/bin/bash RelatedPackageVersions: linux-firmware 1.34 RfKill: SourcePackage: linux dmi.bios.date: 04/12/2010 dmi.bios.vendor: Intel Corp. dmi.bios.version: CBQ4510H.86A.0121.2010.0412.0911 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: DQ45CB dmi.board.vendor: Intel Corporation dmi.board.version: AAE30148-205 dmi.chassis.type: 3 dmi.modalias: dmi:bvnIntelCorp.:bvrCBQ4510H.86A.0121.2010.0412.0911:bd04/12/2010:svn:pn:pvr:rvnIntelCorporation:rnDQ45CB:rvrAAE30148-205:cvn:ct3:cvr: ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug lucid needs-upstream-testing regression-release -- Slow boot caused by SATA controller reset https://bugs.launchpad.net/bugs/595448 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 595448] Re: Slow boot caused by SATA controller reset
** Attachment added: AlsaDevices.txt http://launchpadlibrarian.net/50483916/AlsaDevices.txt ** Attachment added: AplayDevices.txt http://launchpadlibrarian.net/50483917/AplayDevices.txt ** Attachment added: BootDmesg.txt http://launchpadlibrarian.net/50483918/BootDmesg.txt ** Attachment added: Card0.Amixer.values.txt http://launchpadlibrarian.net/50483919/Card0.Amixer.values.txt ** Attachment added: Card0.Codecs.codec.2.txt http://launchpadlibrarian.net/50483920/Card0.Codecs.codec.2.txt ** Attachment added: Dependencies.txt http://launchpadlibrarian.net/50483921/Dependencies.txt ** Attachment added: Lspci.txt http://launchpadlibrarian.net/50483922/Lspci.txt ** Attachment added: Lsusb.txt http://launchpadlibrarian.net/50483923/Lsusb.txt ** Attachment added: PciMultimedia.txt http://launchpadlibrarian.net/50483924/PciMultimedia.txt ** Attachment added: ProcCpuinfo.txt http://launchpadlibrarian.net/50483925/ProcCpuinfo.txt ** Attachment added: ProcInterrupts.txt http://launchpadlibrarian.net/50483926/ProcInterrupts.txt ** Attachment added: ProcModules.txt http://launchpadlibrarian.net/50483927/ProcModules.txt ** Attachment added: UdevDb.txt http://launchpadlibrarian.net/50483928/UdevDb.txt ** Attachment added: UdevLog.txt http://launchpadlibrarian.net/50483929/UdevLog.txt ** Attachment added: WifiSyslog.txt http://launchpadlibrarian.net/50483930/WifiSyslog.txt -- Slow boot caused by SATA controller reset https://bugs.launchpad.net/bugs/595448 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 441416] Re: system does not boot (karmic server install with RAID1)
Same issue here. Dell Dimension 9100 with 4 disks. Created two raid 1 arrays one for /boot and one for swap. produces the same GRUB error. -- system does not boot (karmic server install with RAID1) https://bugs.launchpad.net/bugs/441416 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 463063] [NEW] grub install fails
Public bug reported: Binary package hint: debian-installer Installing Ubuntu 9.10 RC x64 on a Dell Dimension 9200 on a software raid array. created raid 1 md0 for /boot and a raid 1 md1 for swap and a raid10 md2 for /. installation fails with message could not install grub to /dev/md0 this is a fatal error. I forced it through to the end and then manually used install-grub to install each of the four dev/sdX1 paritions that make up my four disk raid 1 md0 array. From what I can tell this installed the old grub because I managed to boot up in to karmic once. I then ran update-manager and it crashed but I noticed the hard disk was busy working so I left it alone and eventually the reboot dialog box appeared so I rebooted and obviously this update installed grub2 because again I can't boot. ** Affects: debian-installer (Ubuntu) Importance: Undecided Status: New -- grub install fails https://bugs.launchpad.net/bugs/463063 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 105195] Re: kvm can not run Windows XP
** Description changed: -- kvm can not run Windows XP https://bugs.launchpad.net/bugs/105195 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to libvirt in ubuntu. -- 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 105195] Re: kvm can not run Windows XP
** Description changed: -- kvm can not run Windows XP https://bugs.launchpad.net/bugs/105195 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 440015] Re: Error starting domain: Unable to deny all devices for vm0: No such file or director
** Attachment added: Dependencies.txt http://launchpadlibrarian.net/32779548/Dependencies.txt -- Error starting domain: Unable to deny all devices for vm0: No such file or director https://bugs.launchpad.net/bugs/440015 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 440015] [NEW] Error starting domain: Unable to deny all devices for vm0: No such file or director
Public bug reported:
Binary package hint: virt-manager
trying to start a virtual machine in the latest karmic results in the error.
here is the traceback:
Traceback (most recent call last):
File /usr/share/virt-manager/virtManager/engine.py, line 493, in run_domain
vm.startup()
File /usr/share/virt-manager/virtManager/domain.py, line 558, in startup
self.vm.create()
File /usr/lib/python2.6/dist-packages/libvirt.py, line 293, in create
if ret == -1: raise libvirtError ('virDomainCreate() failed', dom=self)
libvirtError: Unable to deny all devices for vm0: No such file or directory
This machine did have KVM and virt-manager working just a few days ago so I
assume a recent update broke it.
currently running: 0.7.0-3ubuntu1
Thanks,
Jarrett
ProblemType: Bug
Architecture: amd64
Date: Thu Oct 1 10:14:24 2009
DistroRelease: Ubuntu 9.10
Package: virt-manager 0.7.0-3ubuntu1
ProcEnviron:
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-11.36-generic
SourcePackage: virt-manager
Uname: Linux 2.6.31-11-generic x86_64
** Affects: virt-manager (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug
--
Error starting domain: Unable to deny all devices for vm0: No such file or
director
https://bugs.launchpad.net/bugs/440015
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 108402] 7.04 (fglrx) display corruption and hard lock with X1650 on SIS chipset
Public bug reported: I am running an AGP ATI official branded X1650 on a SIS north bridge. enabling the fglrx driver apears to work initially. That is to say the logon screen appears and then the desktop. However display items are corrupted. The most obvious issue is any kind of scrolling activity just truns that display area to garbage. Also many dialog boxes do not render properly. For example gksudo dialog appears blank, IOW it is just a frame and text box with not buttons, decorations, or fonts. If i do try to use it like this it hard freezes the computer after about 1 minute. By that I mean that tty switching hot keys or ctrl-alt- backspace do not work. I have to hard reset. Because of the card in question I can not try the 'ati' driver. The vesa driver works but looks like awful. It is al blurry. I am guessing this is because of improperly set DVI timmings? ** Affects: linux-restricted-modules-2.6.20 (Ubuntu) Importance: Undecided Status: Unconfirmed -- 7.04 (fglrx) display corruption and hard lock with X1650 on SIS chipset https://bugs.launchpad.net/bugs/108402 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 108402] Re: 7.04 (fglrx) display corruption and hard lock with X1650 on SIS chipset
fixed the blurry issue with vesa driver. It was just a resolution issue. gnome thought I was using 1600x1200 but apparently my vesa bios only has modes up to 1280x1024. changing that control panel setting fixed that issue. The fglrx issue still stands however. -- 7.04 (fglrx) display corruption and hard lock with X1650 on SIS chipset https://bugs.launchpad.net/bugs/108402 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 108402] Re: 7.04 (fglrx) display corruption and hard lock with X1650 on SIS chipset
fixed it. I do not understand how this fixed it but it did. I am now using fglrx without hard freezes or display corruption. 3D does not work but I don't care. I only need 2D as this is a development workstation. I did 3 things. As stated I used the gnome screen res control panel to change to 1280x1024. secondly I manually edited xorg.conf and replaced vesa with fglrx instead of using the restricted manager to do it for me. finally and this seems to be what fixed it (and why I am so puzzled about how this fixed it) I edited my monitor description. I commented out the HorizSync and VertSync lines that came default and replaced them with these lines for my Dell 2001FP HorizSync31 - 80 VertRefresh 56 - 76 DisplaySize 408 306 I then reset the X server and logged in. Switched the resolution in gnome back to 1600x1200 and now all is well. Strangest bug I have ever run in to. I ran in to this same issue with feisty beta and could never resolve it. Went back to edgy at that time. Anyway I hope this helps anyone else who runs in to this bizzare issue. I frankly have no idea how this fixed the problem but all is working fine now. -- 7.04 (fglrx) display corruption and hard lock with X1650 on SIS chipset https://bugs.launchpad.net/bugs/108402 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 108402] Re: 7.04 (fglrx) display corruption and hard lock with X1650 on SIS chipset
opps! I spoke to soon. I have found the cause of the issue. It is DRI!! I had to force ably enable the composite extension. Now this is counter intuitive since ATI does not support composite, however by doing so the xorg log file indicates that the driver detects that composite is on and disables DRI and then everything works fine. However if I set composite to off then I get the screen corruption and hard freezes. Hope this helps. -- 7.04 (fglrx) display corruption and hard lock with X1650 on SIS chipset https://bugs.launchpad.net/bugs/108402 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 94952] xserver-xorg-ati driver fails to find AGP X1650
Public bug reported: Binary package hint: xserver-xorg-video-ati version 1:6.6-3-2ubuntu3 on feisty only vesa driver works for a AGP X1650. ati driver crashes the xserver stating that a device was not found at PCI 1:0:1. This is a card with dual outputs. and lspci lists both 1:0:0 and 1:0:1 as being occupied by my ati card. fglrx driver loads but results in bizzare video corruption. Basically parts of the screen wont redraw properly. Completely unusable. Also if I do try to use it the machine hard locks after a few minutes. the cursor will move but that is it. ctrl-alt-del or backspace do not work. I have to hard reset. This is on a system with a SIS northbridge. ProblemType: Bug Architecture: i386 Date: Thu Mar 22 20:48:49 2007 DistroRelease: Ubuntu 7.04 Uname: Linux pcnix 2.6.20-12-lowlatency #2 SMP PREEMPT Wed Mar 21 20:58:11 UTC 2007 i686 GNU/Linux ** Affects: xserver-xorg-video-ati (Ubuntu) Importance: Undecided Status: Unconfirmed -- xserver-xorg-ati driver fails to find AGP X1650 https://launchpad.net/bugs/94952 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 91012] [apport] hal-device-manager crashed with ImportError in module() App crashed running Hardware Information
Public bug reported: Binary package hint: hal Hardware Information applet crashed. ProblemType: Crash Architecture: i386 Date: Fri Mar 9 19:38:27 2007 DistroRelease: Ubuntu 7.04 ExecutablePath: /usr/bin/hal-device-manager InterpreterPath: /usr/bin/python2.5 Package: hal-device-manager 0.5.8.1-4ubuntu9 PackageArchitecture: all ProcCmdline: /usr/bin/python /usr/bin/hal-device-manager ProcCwd: /home/jarrett ProcEnviron: PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games LANG=en_US.UTF-8 SHELL=/bin/bash PythonArgs: ['/usr/bin/hal-device-manager'] SourcePackage: hal Traceback: Traceback (most recent call last): File /usr/bin/hal-device-manager, line 13, in module import Const ImportError: No module named Const Uname: Linux pcnix 2.6.20-9-lowlatency #2 SMP PREEMPT Mon Feb 26 03:04:39 UTC 2007 i686 GNU/Linux ** Affects: hal (Ubuntu) Importance: Undecided Status: Unconfirmed -- [apport] hal-device-manager crashed with ImportError in module() App crashed running Hardware Information https://launchpad.net/bugs/91012 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 91012] Re: [apport] hal-device-manager crashed with ImportError in module() App crashed running Hardware Information
** Attachment added: Dependencies.txt http://librarian.launchpad.net/6722876/Dependencies.txt ** Attachment added: ProcMaps.txt http://librarian.launchpad.net/6722877/ProcMaps.txt ** Attachment added: ProcStatus.txt http://librarian.launchpad.net/6722878/ProcStatus.txt -- [apport] hal-device-manager crashed with ImportError in module() App crashed running Hardware Information https://launchpad.net/bugs/91012 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 64125] Re: BUG: soft lockup detected on CPU#0!
that command disables the 3945 driver. It saves the script that loads that driver during boot to the root directory in case you need to restore it later. I wish I could use that driver as well but until it's fixed at least I can use the generic kernel which is multi-processor enabled. -- BUG: soft lockup detected on CPU#0! https://launchpad.net/bugs/64125 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 64125] Re: BUG: soft lockup detected on CPU#0!
I have the same problem on a Dell Precision m65. Core 2 Duo. The i386 kernel boot's fine but the generic kernel does not. Mine locks up at the exact same spot. Right after the message about starting EVMS. -- BUG: soft lockup detected on CPU#0! https://launchpad.net/bugs/64125 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 64125] Re: BUG: soft lockup detected on CPU#0!
UPDATE: I found for me it was the Intel 3945abg wireless card that was causing the BUG: soft lockup detected on CPU#0! message to appear. All I did was execute cd /root sudo mv /etc/modprobe.d/ipw3945 . Now the system successfully boots the generic kernel just fine. Again this was a dell precision m65 with a Core 2 duo. -- BUG: soft lockup detected on CPU#0! https://launchpad.net/bugs/64125 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 49012] Re: 6.06 LTS alternative install CD fails to recognize Windows Vista Beta 2
Correct the problem is two fold. (1) The install CD failed to detect that windows vista was installed. I assume because of this the installer never offered me the option of where to install GRUB. It simply automatically installed GRUB to the MBR, just like it would if you were to run through the install on a system that did not have a preexisting OS. (2) This one is probably more of a GRUB bug than an os-prober bug. If you chain load the grub loader after the Windows Vista loader GRUB fails to display anything. It is simply a blank screen. As stated it is functional. I assume this means that GRUB simply has a problem reinitializing the video bios. The system in question is a DELL Optiplex GX620 with the ATI X600 SE video board. This implies it will not be fixed as GRUB 0.7 is no longer accepting bug fixes if I recall correctly. As for the other questions. Vista does use NTFS. The partition I used was formatted NTFS. I did not have XP on the machine. The problem is Vista specific. I could configure GRUB to chain load Vista with no problem by manually modifying the menu.lst file. -- 6.06 LTS alternative install CD fails to recognize Windows Vista Beta 2 https://launchpad.net/bugs/49012 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
