Mar 15 00:48:27 darkstar kernel: [429513.960360] nouveau :01:00.0: fifo:
read fault at e9a000 engine 15 [PCE0] client 01 [PCOPY0] reason 02
[PAGE_NOT_PRESENT] on channel 0 [001fe74000 DRM]
Mar 15 00:48:27 darkstar kernel: [429513.960367] nouveau :01:00.0: fifo:
ce0 engine fault on ch
I'm now getting this on a daily basis, standard Linux PC with GeForce GT
430, causes machine to lock completely.
Mar 15 00:48:57 darkstar kernel: [429543.957731] [TTM] Buffer eviction failed
Mar 15 00:48:57 darkstar kernel: [429543.957755] nouveau :01:00.0:
chrome[21695]: fail ttm_validate
Ma
Public bug reported:
I suspect this is a bug in Ext4 and it's handling of sparse files,
specifically recent(ish) additions that allow hole punching with
"fallocate". I have an application that makes much use of "fallocate"
and whereas it generally works just fine, it seems that under stress the
k
Just had exactly the same problem;
Jun 8 11:41:39 zope1 kernel: [437547.726512] BUG: unable to handle kernel
paging request at 1b90
Jun 8 11:41:39 zope1 kernel: [437547.736139] IP: []
page_waitqueue+0x6e/0x90
Jun 8 11:41:39 zope1 kernel: [437547.736139] PGD 373af067 PUD 370da067 P
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/998720
Title:
Kernel lockup __ticket_spin_lock
To manage notifications about this
Incidentally, if I try to "view" a report before sending, I get this;
What would you like to do? Your options are:
S: Send report (2.2 MB)
V: View report
K: Keep report file for sending later or copying to somewhere else
I: Cancel and ignore future crashes of this program version
C: Canc
apport information
** Attachment added: "WifiSyslog.txt"
https://bugs.launchpad.net/bugs/998720/+attachment/3144422/+files/WifiSyslog.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/998720
Titl
apport information
** Attachment added: "UdevLog.txt"
https://bugs.launchpad.net/bugs/998720/+attachment/3144421/+files/UdevLog.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/998720
Title:
Ke
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/998720/+attachment/3144420/+files/UdevDb.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/998720
Title:
Kern
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/998720/+attachment/3144419/+files/ProcModules.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/998720
Ti
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/998720/+attachment/3144418/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/9987
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/998720/+attachment/3144417/+files/ProcCpuinfo.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/998720
Ti
apport information
** Attachment added: "PciMultimedia.txt"
https://bugs.launchpad.net/bugs/998720/+attachment/3144416/+files/PciMultimedia.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/998720
apport information
** Attachment added: "Lsusb.txt"
https://bugs.launchpad.net/bugs/998720/+attachment/3144415/+files/Lsusb.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/998720
Title:
Kernel
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/998720/+attachment/3144414/+files/Lspci.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/998720
Title:
Kernel
apport information
** Attachment added: "IwConfig.txt"
https://bugs.launchpad.net/bugs/998720/+attachment/3144413/+files/IwConfig.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/998720
Title:
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/998720/+attachment/3144412/+files/CurrentDmesg.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/998720
apport information
** Attachment added: "Card1.Codecs.codec.0.txt"
https://bugs.launchpad.net/bugs/998720/+attachment/3144411/+files/Card1.Codecs.codec.0.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.n
apport information
** Attachment added: "Card0.Codecs.codec.0.txt"
https://bugs.launchpad.net/bugs/998720/+attachment/3144410/+files/Card0.Codecs.codec.0.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.n
apport information
** Attachment added: "BootDmesg.txt"
https://bugs.launchpad.net/bugs/998720/+attachment/3144409/+files/BootDmesg.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/998720
Title:
apport information
** Attachment added: "AlsaDevices.txt"
https://bugs.launchpad.net/bugs/998720/+attachment/3144408/+files/AlsaDevices.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/998720
Ti
apport information
** Tags added: apport-collected
** Description changed:
Machine will respond to ping and I can log in with ssh, but pretty much
everything else ("top" for example) doesn't work, type in the command and hit
return and nothing happens. kern.log just repeats the following;
Public bug reported:
Machine will respond to ping and I can log in with ssh, but pretty much
everything else ("top" for example) doesn't work, type in the command and hit
return and nothing happens. kern.log just repeats the following;
(all the machine is doing is running two CENTOS VM's under K
Just to expand a little, if I download the same source and compile with
"-fno-stack-protector", the stack smashing issue vanishes but instead
the program dies with a core dump.
..
7fea5a9d-7fea5a9d2000 rw-p 00023000 08:01 269502
/lib/x86_64-linux-gnu/ld-2.15.so
7fff18d5f0
Public bug reported:
#/usr/sbin/hddtemp /dev/sdb
*** stack smashing detected ***: /usr/sbin/hddtemp terminated
=== Backtrace: =
/lib/x86_64-linux-gnu/libc.so.6(__fortify_fail+0x37)[0x7f36902d3007]
/lib/x86_64-linux-gnu/libc.so.6(__fortify_fail+0x0)[0x7f36902d2fd0]
/usr/sbin/hddtemp[0x
Public bug reported:
Someone has introduced the following code into webdav.c, not sure when;
#if NE_VERSION_MINOR > 25
if (!has_if_match_bug && !*exists)
ne_hook_pre_send(session, add_header, none_match_header);
#endif /* NE_VERSION_MINOR > 25 */
If this is activated, it inserts an a
Ok, I tried this patch, improved things slightly but this package still seems
heavily broken in terms of impact in the user. Anyone running aliases (I have
maybe 50 servers that use aliases) who tries to upgrade to 11.10 is likely to
end up with a broken server.
- is there some way we can genera
Just another confirmation, I have the problem too and have been
reporting it elsewhere for over 2 months. It's caused by Xinerama, turn
off Xinerama and you can run multi-screen setups fine for months with no
lockup. Turn it on and you're pushed to survive more than a few hours.
Note; switch user
Hi, just in case anyone thought this has been remotely nailed down /
fixed;
I've been running find for nearly two months after reporting this problem.
My documented fix was to disable xinerama.
I thought I'd try today to see if it was any better, so I ticked
xinerama in my nvidia config, logged o
It's a "mis"-implementation of the Xen kernel patches which typically
are not available for the most recent kernels.
Use a RedHat Xen kernel, this is the only one I've found to work.
2.6.21 is the one I'm using, this is 100% reliable.
--
"Time went backwards" + freeze for domU's with kernel 2.6.
Your post;
>>27 Aug 2007
>>Fix is in my tree.
>>An mcookie is generated for the terminal, and set as an xprop during login.
>>Client must pass correct mcookie for connect to happen.
...
You will forgive me if I'm a little confused.
I know xprop, and I know roughly what X cookies are .. this do
Jordan,
>Not that I know, but I don't think you understand the general process of using
>your (limited) resources as
>effectively as possible under a priority-based system for such an enormous
>project as Ubuntu.
You would be correct, the way in which Ubuntu seem to do things is
beyond me.
>B
Isn't it amazing how some people will still continue to defend the
indefensible, just because their ears hurt.
If Ubuntu were billed as a charity, I might tend to agree that people
working for free shouldn't need to take any sort of hit for shoddy
workmanship. Or, if Ubuntu were billed as "unfit f
Hi,
I think it's a moot point, but for anyone with a working kernel, a
working console looks like this;
>>/boot/grub/menu.lst;
--
serial --unit=0 --speed=115200 --word=8 --parity=no --stop=1 terminal
--timeout=2 serial console
titleXen 3.2.0
root(hd0,0)
kernel
Mmm,
The main fix for me was to turn Xinerama off, but I did experience some
other weird stuff so effects are now off too .. I can confirm that with
Xinerama + Effect I was locking on average every 10 mins .. now, not for
a couple of weeks.
hth
- Original Message -
From: "Antonio C. Cost
This is the same problem .. try turning Xinerama off.
One thing I have noticed, I DO get the lockups still on occasion,
however they only last for 20 seconds and only affect ONE screen.
- Original Message -
From: "Richard" <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Sent: Thursday, 6 Novemb
I only use Gnome, so I think that theory may also have an imperfection
.. (!)
- Original Message -
From: "praveer01" <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Sent: Wednesday, 5 November, 2008 5:50:17 PM GMT +00:00 GMT Britain, Ireland,
Portugal
Subject: [Bug 259808] Re: X Lockup in Intre
I use Gnome ...
- Original Message -
From: "Xavier Gnata" <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Sent: Wednesday, 5 November, 2008 10:55:17 AM GMT +00:00 GMT Britain, Ireland,
Portugal
Subject: [Bug 259808] Re: X Lockup in Intrepid (infinite loop)
Using KDE or gnome?
--
X Lockup in
Hi, please can you verify whether you have Xinerama on or off .. if in
doubt, please add;
Section "ServerFlags"
Option "Xinerama" "0"
EndSection
To /etc/X11/xorg.conf.
I was seeing crashes every few minutes or hours .. I've now gone 48h
without a crash after making this change ..
Ok, I think I've found the cause .. looks like it could be the "Xinerama"
setting.
(i.e. graphics card independent)
This is going to hit anyone with more than one screen.
(anyone who's tried Twinview and Xinerama on a decent graphics card won't be
using twinview!)
I'm running 4 screens here ..
Ok, removed lots of other stuff completely, like vmware .. just had the
problem again and noticed this in the logs;
[mi] EQ overflowing. The server is probably stuck in an infinite loop.
[mi] mieqEnequeue: out-of-order valuator event; dropping.
So .. same problem.
This looks like a show-stopper i
Ok, I'm having what sounds like the same problem - I've used synaptic to
remove compiz (completely) and am still seeing the same issue. I can't
pin it down as nothing appears in the logs when it dies, however it does
seem to be sound related. (i.e. if I play music, I lock up pretty
quickly)
System
Not really.
a. There's a whole list of problems I've come across and have posted details of
on different threads
b. As of 3 weeks ago on Hardy, it wasn't fixed (which was last time I tried it)
--
"Time went backwards" + freeze for domU's with kernel 2.6.22-xen
https://bugs.launchpad.net/bugs/14
I think it could be taken as a general comment prompted by another posting on
this thread.
(which is heading for it's first anniversary)
IMHO Xen should be taken out of the Repo's (for now) , Ubuntu's version
simply does not work.
People read the press and see "Xen is great, Xen is stable", then
So .. yes it's a Xen issue, but it's Ubuntu specific, i.e. Ubuntu's Xen
kernel "doesn't work".
I'm running 30 VM's, all had the problem on various Ubuntu kernels.
I've not had the problem in 8 months since switching the kernel out for the
Redhat/Xen kernel.
.. so if you think Xen are every going
There we go, I knew it wasn't just me getting pissed off with Ubuntu for
no reason ... ;-)
- Original Message -
From: "Johnathon" <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Sent: Thursday, July 24, 2008 8:45:06 PM GMT +00:00 GMT Britain, Ireland,
Portugal
Subject: [Bug 133635] Re: LTSPFS
Mmm,
It is true I am running a non-Ununtu kernel ...
Perhaps because the Ubuntu Xen kernel, certainly upto Gutsy, was simply
too unstable to be of any use. I'm running ~ 20 Xen instances across 4
servers and spent a LONG TIME trying to make raw Ubuntu work. My
eventual solution was to switch to a
I have the exact same problem on Hardy with an integrated Radeon 200XP.
I'd supply more info, but the problem is 100% identical and it's a fresh
install / upgrade from feisty.
--
Display blanking/freezing using PCI/AGP ATI 9250
https://bugs.launchpad.net/bugs/58448
You received this bug notifica
The former, Ubuntu with a RH kernel .. the only issue I see is unwanted
warning messages when using rsync .. apparently there is a discrepancy
between kernel features available on the Ubuntu and RH kernels that
rsync doesn't handle very well .. and one unavailable sysctl entry which
gives an entry
I have a solution I'm employing on 26 Xen instances.
It's called "use the Redhat 2.6.21 kernel which works!"
The Ubuntu Xen kernel has SO MANY problems it really isn't even worth
looking at.
--
"Time went backwards" + freeze for domU's with kernel 2.6.22-xen
https://bugs.launchpad.net/bugs/1469
Ok, I'm using Xen in a production environment as an ISP.
I would strongly recommend anything thinking of using Ubuntu/Xen to
avoid using Ubuntu's kernels in the Dom0, certainly the gutsy kernel is
VERY unstable in a number of areas and will generate oops's, panic's and
will generally crash under h
Well ... if grub-update is going to generate kernel and xen entries, it
should probably create them properly and it should probably add serial
console stuff as anyone running a remote server will be using this. (and
it doesn't , so that's point #1)
As the configuration between standard kernel -> x
Linux nodea 2.6.21-prep #11 SMP Tue Feb 12 19:15:35 UTC 2008 x86_64
GNU/Linux
This is the stock RH kernel with Xen extensions built from source .. you
know why I'm not using the Ubuntu Kernel (!)
--
[hardy] "ip" broken
https://bugs.launchpad.net/bugs/192294
You received this bug notification bec
Public bug reported:
I'm not entirely sure how you've managed it but you've released a broken
version of "ip" in the current incarnation if "hardy".
Sample;
[EMAIL PROTECTED]:~# ./ip link set eth0 up
RTNETLINK answers: Invalid argument
I can't even begin to think about the number of packages th
fyi; this does not happen on a clean Xen 2.6.18.8 kernel.
--
Kernel Ooops using File-backed VBDs
https://bugs.launchpad.net/bugs/184412
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.
Ok, the solution is to add the following to the kernel line;
com1=115200,8n1 console=com1
and the following to the module line;
console=ttyS0
--
Serial Console redirection no longer works properly
https://bugs.launchpad.net/bugs/160455
You received this bug notification because you are a membe
Hi Guys,
I've been doing a LOT of work on Ubuntu XEN over the last couple of weeks and
now have two live stacks which are staying up and doing a lot of work.
(hopefully)
I've found there are three fundamental things you need to make clocks
reliable and not have the system pause under load, these
Public bug reported:
Currently Ubuntu document the use of the "file:" driver for file backed
VBD's .. these are no longer recommended (or supported by the likes of
RH) due to catastrophic data loss in the event the host node fails. The
new recommended method is to use the TAP:AIO driver.
This is
Public bug reported:
Binary package hint: linux-image-2.6.22-14-xen
[48236.924622] [ cut here ]
[48236.924653] kernel BUG at
/build/buildd/linux-source-2.6.22-2.6.22/debian/build/custom-source-xen/fs/inode.c:247!
[48236.924675] invalid opcode: [1] SMP
[48236.924696]
Yes - I get a blank on both consoles.
--
Serial Console redirection no longer works properly
https://bugs.launchpad.net/bugs/160455
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.ubun
If you check the docs, two console parameters are actually 'required'. I know
this because I've tried taking out the "tty1" just to see what happens ..
(the machine does not boot and I get no display anywhere)
During the initial boot, the BIOS redirection works nicely.
When in grub, the kernel r
Public bug reported:
We use multi-port serial console to remote-boot Ubuntu servers and generally
the process seems to work fine. However, once upon a time, when the system
started to boot, information from the startup process was all piped to the
serial console quite happily. Now, although we
Public bug reported:
Oct 26 01:22:39 squizzey kernel: [ 41.418072] nvidia: module license 'NVIDIA'
taints kernel.
Oct 26 01:22:39 squizzey kernel: [ 41.418798] nvidia: Unknown symbol kmap_prot
Oct 26 01:22:39 squizzey kernel: [ 41.419073] nvidia: Unknown symbol
kmap_atomic_prot
Using curr
Same problem here, also reported on gnome.bugs.org.
Long running problem - are they ever going to fix it?
Sounds trivial but it's pretty critical in terms of usability for multi-
screen users ..
--
Notification Area on second screen's panel doesn't work
https://bugs.launchpad.net/bugs/128735
Yo
To reproduce on a random workstation (taken from my Bash session);
sudo apt-get install ltspfsd
modprobe fuse
ltspfs 10.1.0.220:/var/run/drives /mnt/root
df -> ltspfs 45244044452396 1% /mnt/root
ls -la /mnt/root/usbdisk-sdc1
total 384
drwxr-xr-x 2 root root 204
Ok, if I boot a thin client (without logging in or doing anything
clever) on the server (or indeed any intelligent machine on the network)
I can do the following;
ltsp :/var/run/drives /mnt/localdev/mountpoint
And I have full access to the client's device , USB key in this case ...
??
--
LTSPFS
As part of the boot process, the thin client runs;
/usr/bin/ltspfsd -a
At this point, it is listening on 0.0.0.0:9220.
Anyone on the network or the server can then access this port via the
thin client's native IP address.
??
--
LTSPFS security is broken
https://bugs.launchpad.net/
Public bug reported:
By default on Fiesty the ltspfs daemon is started with a "-a" , which
turns off Magic Cookie authentication.
In this mode, ltfsp works fine for me, I can see and mount USB and CDROM's not
problem.
Trouble is, so can anyone else on the server.
If I remove the "-a", mounting
Public bug reported:
I'm running 7.04 with LTSP and thin clients with NVIDIA cards.
Overall working Ok, however machines with widescreens seem not to be getting
the correct resolution.
Further examination reveals that the resolution lines in xorg.conf begin with;
"1440x1440 1280x1024 ..." as o
Ok, I don't know "why" there is an error in the code, but here is an
easy fix.
In the .cgi file (/usr/lib/cgi-bin) find the "graph" routine.
Insert a ");" before the two COMMENT: lines (and remove these lines).
It seems that the script is using a feature of RDD (comments) that is
either not there
Mmm, sure ... just as soon as I "see" it (!)
(3.3 is the my only option in synaptic)
--
Crash on startup
https://launchpad.net/bugs/74244
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Incidentally, this is BEFORE I even get chance to run a Xen instance,
i.e. the machine locks up WHILE I am trying to download nvidia drivers
etc ...
--
Kernel source broken and Nvidia revisions out of sync
https://launchpad.net/bugs/74305
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
Public bug reported:
1. After booting the xen-source kernel, after 2-15 mins, system locks
up. Reports ata1: timeout and everything locks up, I'm guessing it's the
SATA driver.
2. The nvidia drivers in xen-source restricted modules are 2-revisions
away from the nvidia-glx package, hence X won't
Public bug reported:
Finally got past the GLX_EXT_texture_from_pixmap problems by installing
the BETA of the nvidia drivers, so compiz no longer moans when it starts
...
However it now coredumps immediataly when I do;
compiz --replace --use-cow gconf
Ubuntu/Edgy, up-to-date as of Dec 03, apt-get
** Attachment added: "Core dump"
http://librarian.launchpad.net/5239220/_usr_bin_compiz.real.1000.crash
** Description changed:
Finally got past the GLX_EXT_texture_from_pixmap problems by installing
the BETA of the nvidia drivers, so compiz no longer moans when it starts
...
Howev
Public bug reported:
We have a thin client installation with 30 users on one server. We seem
to get a "hang" with (on average) 2 users per day. Evolution just seems
to stop responding and the only way to recover is to manually kill *all*
evolution processes for that users .. so I'm assuming it's t
OK,
This is a new installation, all user configs are LDAP based, each user
is a member of "users,plugdev,audio" and a couple of custom NT domains.
(definitely NOT adm)
The Shutdown and Reboot buttons do NOT appear.
The hibernate button DOES appear.
Not only that, but it allowed me to click on hi
Ok, when the user is a "user", giving them the "hibernate" feature is a
really bad idea. This can be verified by the engineer presently on his
way to site ..
Letting users re-enable the hibernate feature using gconf-editor is
"bad". Is there a way to disable this at system level?
I'm assuming shu
78 matches
Mail list logo
