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
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
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
--
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
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
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
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
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.
--
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
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
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
--
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
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
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
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
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.
--
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
** 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
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
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
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
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
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
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
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
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.
--
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
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
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
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
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
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
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
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?
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
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
** 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
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
** 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
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.
--
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
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
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
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
** 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
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
#
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
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
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
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
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
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
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
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
** 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
**
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
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
** 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
** 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
** 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
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
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
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
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
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
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
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
** 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]
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:
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
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
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
72 matches
Mail list logo
