I seem to have this issue too, but related to a different device.
Running 16.04 with 4.4.0-31-generic. New (used) machine so very
concering. It ran fine for about an hour then spontaneously started
spewing this:
Jul 26 13:28:05 twin kernel: [8.837650] pcieport :00:03.0: AER:
Multiple Co
I can confirm precisely these symptoms with 2.6.35-22. I can see the
VLAN packets going out, and I can see the responses leaving a remote
system (ARP in this case), but they (responses) do not appear on the
Maverick box interface according to tcpdump.
Reverting to 2.6.32 (Lucid) solves problem.
What about making the sequence a settable option, defaulting to
ctl+space?
--
"IBus daemon is not started" message unhelpful
https://bugs.launchpad.net/bugs/423525
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing l
Perhaps. My speculation is that Xen provides a work-around by enabling
one to pin the CPUs. But maybe the problem is related to
multiprocessing vis-a-vis X11.
One question to ask is whether this occurs on any single-processor
systems.
Anybody?
--
System freezes : Ubuntu Hardy Heron beta
http
This freeze still occurs on my system which is running Heron/Xen and
current patches.
I seem to have averted it by assigning a single CPU to each VCPU and
pinning them. But Friday I ran for the first time in several months
without that particular CPU restriction in effect, and the keyboard and
mo
Further to the above, see attached lshw output. Anybody wants more
info, I am at your service.
** Attachment added: "hw"
http://launchpadlibrarian.net/16695723/hw
--
System freezes : Ubuntu Hardy Heron beta
https://bugs.launchpad.net/bugs/217573
You received this bug notification because yo
I have the same issue with 8.04, but I'm running XEN, if it matters...
[EMAIL PROTECTED]:~# uname -a
Linux flipper 2.6.24-19-xen #1 SMP Sat Jul 12 00:15:59 UTC 2008 x86_64 GNU/Linux
In my case, I have worked with various combinations of PS/2 and USB
mice/keyboards. I usually work with a USB keyb
I sold a load-balancing scheme to a client. When I moved my scripts
over from my testing (SuSE with 2.6.16.13 kernel) to client production
(Feisty, canned), this chomped at my posterior. Is -j CONNMARK
considered unstable? There seems to be evidenced of topns of folks
using it for quite a while
