I missed @eenuep's comment above (#18), that worked a lot better than
installing an older kernel!
Simply run: sudo apt install linux-oem-24.04
Then restart. Thanks so much!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs
I was having the same issue on Ubuntu 24.04 on a 2024 XPS 13 (9340) with Ultra
7. Downgrading to an older kernel seems to fix the screen tearing / system
freezing. In case it's helpful for someone, you can downgrade the kernel with
the following steps:
1. Open a terminal and type: sudo apt insta
Public bug reported:
lambda function that is failing. See attachment.
** Affects: gcc-4.7 (Ubuntu)
Importance: Undecided
Status: New
** Attachment added: "generate by the gcc"
https://bugs.launchpad.net/bugs/1313182/+attachment/4097832/+files/bug1.txt
--
You received this bug
Enabling the lucid-proposed repos and updating gnome-system-tools worked
for me. Thanks!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/574046
Title:
shares-admin doesn't "see" NFS and SMB installed
This same scenario has happened to me as well.
--
mdadm cannot resume array reshape
https://bugs.launchpad.net/bugs/25
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://
I've had this problem a few times and finally diagnosed it as stale NFS file
locks. The workaround was to make a fresh copy of my profile directory. For
example:
mv zlpvr32r.default foo
cp -a foo zlpvr32r.default
I determined that one or more of the sqlite files were locked. My home
direc
At the time it didn't seem as though a solution would be forthcoming, so
I abandoned the idea of mirrored root fs.
--
corruption when using md raid1 as root fs on amd64
https://bugs.launchpad.net/bugs/129260
You received this bug notification because you are a member of Ubuntu
Bugs, which is subs
Public bug reported:
Binary package hint: texlive-base-bin
I'm currently doing an update-manager upgrade from Gutsy to 8.04 and the
setting up of the texlive-lang-danish (and other) packages is taking
virtually forever due to an infinite recursion in directory traversal.
I also experienced this w
Public bug reported:
Binary package hint: vlc
[0349] main audio output debug: found a filter for the whole conversion
[0349] alsa audio output debug: recovered from buffer underrun
[0345] main video output warning: late picture skipped (29389)
[0349] main audio output warning: com
I've experienced a similar issue together with the iommu bug, but
iommu=soft doesn't resolve it: https://bugs.launchpad.net/ubuntu/+source
/linux-source-2.6.15/+bug/129260
--
from bugzilla.kernel.org - data corruption with Opteron CPUs and nvidia
chipsets//memory hole mapping / iommu related bug
** Summary changed:
- corruption when using md raid1 as root fs on amd64 smp
+ corruption when using md raid1 as root fs on amd64
** Description changed:
Binary package hint: linux-image-2.6.15-28-amd64-server
md5sum returns inconsistent results when run repeatedly on a large text
file
** Description changed:
Binary package hint: linux-image-2.6.15-28-amd64-server
md5sum returns inconsistent results when run repeatedly on a large text
- file stored on a linux software (md) raid1 volume (ext3). md5sum works
- fine when using a single standalone disk (also ext3).
+ file st
I reinstalled Ubuntu 6.06 LTS on the problem system. Now the root fs is
on a single drive, and I made a separate raid1 (using md) on a pair of
WD5000's, mounted on /test. So far, I haven't seen any corruption
issues.
I'll let it keep running for now, and if by tomorrow I don't see any
corruption
** Summary changed:
- opteron amd64 data corruption
+ corruption when using md raid1 on amd64 smp
** Description changed:
Binary package hint: linux-image-2.6.15-28-amd64-server
md5sum returns inconsistent results when run repeatedly on a large text
- file stored on a linux software (md)
** Description changed:
Binary package hint: linux-image-2.6.15-28-amd64-server
- When trying to load a large (5GB) sql file into mysql, mysql errors out,
- segfaults, or the entire system locks up hard.
+ md5sum returns inconsistent results when run repeatedly on a large text
+ file stored o
iommu=soft appears to have fixed the corruption on one system, but
another is still having problems. The key difference between the fixed
and broken systems is that the broken system has its root filesystem on
a linux (md) raid1 disk pair.
I installed a single extra drive in the broken system and
More info:
The two systems in question have the following specs:
System 1 ("murray"):
Tyan Transport B2891G24S4H
Motherboard: Thunder K8SRE S2891 (nForce Professional 2200)
8x1GB of Corsair CM72SD1024RLP-3200/S (S = Samsung)
Disks: root fs on two WD3200RE using linux raid1, SATA
System 2 ("morga
In the interest of complete clarity here's the kernel version string:
2.6.22.1-custom #3 SMP Tue Jul 31 22:58:43 CDT 2007 x86_64 GNU/Linux
I've attached output of /proc/cpuinfo and dmesg.
** Attachment added: "dmesg and /proc/cpuinfo"
http://launchpadlibrarian.net/8646364/cpuinfo-and-dmesg.tx
OK, I compiled 2.6.22 from kernel.org and the error still appears. I
ran:
while (true) ; do md5sum bigfile.sql ; done
bigfile.sql is around 16GB, and I ran that loop for about an hour, and
here's the results:
cb5714b4050178096ee5d7ebade86364 bigfile.sql
f199dc20003be8f5913d38d92d0b99e3 bigfil
I've tried 2.6.15-50 from dapper-proposed with no luck. According to
kernel.bugzilla.org, a fix was merged more than two months ago. Is
there some way for me to obtain this fix through the dapper
repositories?
** Summary changed:
- large files become temporarily corrupt
+ opteron amd64 data cor
After reading this thread:
http://www.nvnews.net/vbulletin/showthread.php?t=81716 I'm beginning to
think the problem I am experiencing may be the same as what krader
reports. Specifically, see
http://www.nvnews.net/vbulletin/showpost.php?p=1117843&postcount=46
iommu=soft doesn't fix it for me.
dd if=/dev/zero doesn't reproduce the bug. This might mean that the
corruption results from data being transposed from one location in the
file to another. I'm now trying again with dd if=/dev/urandom, results
coming in 12-16 hours.
--
large files become temporarily corrupt
https://bugs.launchp
Now I'm using md5sum on a large (16GB) sql file, and seeing different
results each time. I'm going to try md5sum'ing some large files created
with dd if=/dev/zero to see if the problem appears. That will make it
easy for others to try to reproduce.
--
large files become temporarily corrupt
http
Using the iommu=soft boot option does not fix the problem. Although,
curiously, the corruption is no longer visible in the dump file after
attemptiong to load it with mysql. mysql still errors out but
everything looks fine in the dump file at that location. This is nuts!
--
large files become
This bug MAY be related to https://bugs.launchpad.net/ubuntu/+source
/linux-source-2.6.15/+bug/128568
--
large files become temporarily corrupt
https://bugs.launchpad.net/bugs/129260
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
Public bug reported:
Binary package hint: linux-image-2.6.15-28-amd64-server
When trying to load a large (5GB) sql file into mysql, mysql errors out,
segfaults, or the entire system locks up hard.
In the error or segfault case, examining the input file at the location
where mysql crashed reveals
26 matches
Mail list logo
