No, I am completely wrong. It still happens all the time. There was a period
when it seemed stable. Here is my kernel panic fwiw on lucid
linux-image-2.6.32-25-server 2.6.32-25.45:
[747393.713739] swapper: page allocation failure. order:0, mode:0x4020
[747393.713743] Pid: 0, comm: swappe
We use vmware ESXi, and we were crippled by this bug (we had to rebuild
several systems back to karmic because they were so unusable).
Somewhere in the past month a kernel upgrade seems to have resolved this
issue for us. We could reproduce this problem easily:
Remote System:
cat /dev/zero | nc -
Agreed. This needs to be on lucid LTS because this basically cripples
webDAV... and webDAV is typically something you use in a server
environment which is more likely to be running the LTS. I can tell you
we're basically SOL on an upgrade from hardy on several servers because
of this. We tried r
It's simple, but incredibly frustrating bugs like this that get ignored
for 10+ months (as of now) that make it incredibly difficult to get non-
linux users using ubuntu as their main desktop. Most users are not
comfortable with gconf-editor, and aren't going to know what to google
for to find thi
Using the attached patch I linked to in bugzilla, it did NOT solve our problem,
we patched against an
Ubuntu Hardy 2.6.24-24 kernel. It may or may not have helped the original way
of reproducing this error (which I could not ever reproduce on the Hardy
kernel), but it does not aid our way of r
We have been regression testing our production environment on Ubuntu
Hardy, and I believe the root cause of an intermittent nfs failure issue
we are seeing on Hardy (but not previous versions of ubuntu) is sourced
from this kernel bug. It took a long time to track the issue down, as
our use case i
(Once a fix is found, I second the nomination to backport it to hardy)
--
ssh -X breaks Xauthority on NFS mounted home dir
https://bugs.launchpad.net/bugs/269954
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing lis
So if you try upgrading to hardy... this issue is still not resolved.
You'll still need to download the driver from qlogic and install it per
my earlier instructions... However!
Good luck getting it to compile. I spent 30 minutes looking through
kernel commits to get it to compile, but was able t
So I've been struggling with LVM snapshot issues for atleast a year or
so (in some form or another)
I'm not sure if the kernel engineers working on this issue have nailed
down the precise cause, but I have made some observations over the past
week that may help.
1) The issue is has a definite pos
So QLogic's most recent driver on their website:
http://support.qlogic.com/support/EULATemplate/Template.aspx?TemplateID=1&path=http://download.qlogic.com/drivers/60676
/qlaiscsi-linux-5.01.00.08-2-install.tgz
will compile against the feisty kernel... and it WILL work properly. It fixed
these i
rdobos:
My workaround to echo "- - -" out to the card didn't help? Or are you
trying to BOOT from the san?
With the driver that's included with the fiesty kernel, the CLI won't
work. It's one of the things that gets broken with the feisty kernel.
--
QLogic 4052C (qla4xxx) controller does scan
Matthias:
Are you referring to what a distributor can do for sun's JVM? The
solution I have put onto my ubuntu servers would require no changes to
Java. It would probably require changing tzconfig to write the timezone
out to a second place (/etc/sysconfig/clock)
--
Java reports time zone inco
People were mentioning writing the correct timezone information to
/etc/sysconfig/clock aswell as an option, here is the format:
ZONE="America/New_York"
UTC=false
ARC=false
This doesn't seem like such a horrible idea. There may be even other
(non-ubuntu pieces of software) that use the /etc/sysc
The system is a HP DL385. (2 CPU Opteron, Single Core). We're using a
promise vtrak M500i for the SAN
--
QLogic 4052C (qla4xxx) controller does scan the iSCSI bus properly in feisty
kernel
https://bugs.launchpad.net/bugs/118846
You received this bug notification because you are a member of Ubu
Even with my workaround... the QLA4xxx driver isn't stable. The
controller seems to die after the server has been up for a few days:
[490752.920691] qla4xxx :05:07.3: scsi(1:0:2:1): ADAPTER RESET ISSUED.
[490752.943274] qla4xxx :05:07.1: scsi(0:0:2:1): ADAPTER RESET ISSUED.
[490782.168479
I got this one today, that is slightly different. Doesn't cause the soft CPU
hang... and the interrupt handler is alive enough for panic=60 to have rebooted
the machine:
[277933.276335] [ cut here ]
[277933.285715] kernel BUG at block/elevator.c:767!
[277933.294920] inval
I can confirm this happens on feisty AMD64.
Linux db-1-snapshot 2.6.20-16-server #2 SMP Wed May 23 00:36:09 UTC 2007
x86_64 GNU/Linux
db-1-snapshot - error creating snapshot lvcreate:Setting chunksize to 16
sectors.
Finding volume group "vg_san_mysql"
Archiving volume group "vg_san_m
Public bug reported:
Binary package hint: linux-source-2.6.20
We have a Qlogic 4052C in a number of servers. It's an iSCSI offloaded,
TCP offloaded iSCSI board. Basically it makes your iSCSI targets show
up as normal /dev/sda devices.
Before the feisty kernel, we had to compile the qlogic driv
I suppose I should mention that I am using the QLogic board entirely as
an iSCSI/TOE offloaded card. They just appear as scsi devices to me.
--
Kernel soft lockup detected on CPU#0 under heavy I/O on AMD64 Feisty, elevator.c
https://bugs.launchpad.net/bugs/118833
You received this bug notificati
** Attachment added: "lspci -vvn"
http://launchpadlibrarian.net/7983124/lspci-vvn
--
Kernel soft lockup detected on CPU#0 under heavy I/O on AMD64 Feisty, elevator.c
https://bugs.launchpad.net/bugs/118833
You received this bug notification because you are a member of Ubuntu
Bugs, which is the
** Attachment added: "lspci -vv"
http://launchpadlibrarian.net/7983119/lspci-vv
--
Kernel soft lockup detected on CPU#0 under heavy I/O on AMD64 Feisty, elevator.c
https://bugs.launchpad.net/bugs/118833
You received this bug notification because you are a member of Ubuntu
Bugs, which is the b
** Attachment added: "lspci -v"
http://launchpadlibrarian.net/7983111/lspci-v
--
Kernel soft lockup detected on CPU#0 under heavy I/O on AMD64 Feisty, elevator.c
https://bugs.launchpad.net/bugs/118833
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug
** Attachment added: "lspci"
http://launchpadlibrarian.net/7983109/lspci
--
Kernel soft lockup detected on CPU#0 under heavy I/O on AMD64 Feisty, elevator.c
https://bugs.launchpad.net/bugs/118833
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug cont
Public bug reported:
Binary package hint: linux-source-2.6.20
I recently upgraded a server from Dapper to Feisty. This server was solid
before the upgrade (no kernel panics), but now it kernel panics very
frequently. It appears to be correlated to heavy I/O. When the system
crashes, even th
** Attachment added: "cpuinfo"
http://launchpadlibrarian.net/7983108/cpuinfo
--
Kernel soft lockup detected on CPU#0 under heavy I/O on AMD64 Feisty, elevator.c
https://bugs.launchpad.net/bugs/118833
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug
If the issue has already been rejected, perhaps I can simply nolonger
use gnumeric as a spreadsheet since this issue has appeared. The work
around to use Text Export (configurable) and selecting format "Preserve"
does not work. It will export ## for datafields which are not
physically exp
Still a problem in Edgy eft:
1.7.0-1ubuntu4
When you save as text, it even asks what Locale you want to save your
file in. Regardless of how you have formatted your cells, or the locale
you select, it still outputs the dates in the wrong format.
This unfortunately makes text format fairly usele
** Also affects: Ubuntu
Importance: Untriaged
Status: Unconfirmed
** Changed in: Ubuntu
Sourcepackagename: None => gnumeric
--
gnumeric does not properly export datetimes to Text format
https://launchpad.net/bugs/40349
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://l
*** This bug is a duplicate of bug 30557 ***
Setting the max_cstate to 1 makes the system usable.
I just upgraded to 1.27 (May 24 2006) and 1.06 (Jun 6 2006), and set the
max_cstate back to default (8). That seems to have made the2.6.12-25
kernel MUCH better. I can't tell if it's totally cured,
*** This bug is a duplicate of bug 30557 ***
Jeff. I got my bios version by going into the bios. While the big IBM
is on the screen after a reboot, hit F1. It should be listed there.
Any chance you can reboot at some point and send over that #?
Thanks,
--
Thinkpad T43 2.6.15-23/25, system sl
So for my own sanities sake let me give numbers to the symptoms
Symptom #1:
CPU spikes, which over time, evenutally turn into a continual stream of user
and system time. Eventually the cpu will never spin down from MAX.
Kernels present in: 2.6.15-23, 2.6.15-25
Kernels NOT present in: 2.6.12-9
S
I should note the lsmod I included is from a bootup with acpi=off
--
Thinkpad T43 2.6.15-23/25, system slow to use due to CPU spikes
https://launchpad.net/bugs/50024
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Perhaps one difference between the working T43 and mine is the bios
revision? Jeff, can you give me your bios revision? Mine is:
1.05
2005-04-28
Embedded Controller Version: 1.03
--
Thinkpad T43 2.6.15-23/25, system slow to use due to CPU spikes
https://launchpad.net/bugs/50024
--
ubuntu-bug
Public bug reported:
Let me apologise in advance for not being able to narrow this one down
further, but it's something in the kernel... so my user space tools
aren't helping me track this down.
I have a thinkpad T43 (1.87GHz P-M). The system ran great when I was
running breezy. When I upgraded
34 matches
Mail list logo
