Another environment where this happens is multi-seat using a USB-to-VGA
display controllers.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1293384
Title:
Compiz CPU usage dramatically increased in
It is insane. One user logged in and out. And 2G of memory is data-
resident?
PID TTY STAT TIME MAJFL TRS DRS RSS %MEM COMMAND
2155 ?Sl 0:00 1 0 2091744 4012 0.1
/usr/sbin/console-kit-daemon --no-daemon
--
You received this bug notification because you
I think somebody should take a serious look at this. Have a look at this from
the c-k-d status:
VmPeak: 2091776 kB
VmSize: 2091744 kB
VmLck: 0 kB
VmPin: 0 kB
VmHWM: 4012 kB
VmRSS: 4012 kB
VmData: 2052720 kB
VmStk: 136 kB
VmExe: 136 kB
VmLib: 5820 kB
Public bug reported:
The hybrid_power script turns on the laptop display, even if the lid is
closed.
I dock my laptop and leave it closed, there's an external (VGA) monitor
connected. When I run the hybrid_power script, it correctly turns on the
external display and incorrectly turns on the
Me too. Using nvidia-319-updates on regular 13.10, Dell Latitude E6530,
01:00.0 VGA compatible controller: NVIDIA Corporation GF108GLM [NVS
5200M] (rev a1)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
*** This bug is a duplicate of bug 1056381 ***
https://bugs.launchpad.net/bugs/1056381
Public bug reported:
I have a virtual machine that uses kvm-spice with quantal in it (up to
date with today). The login screen does not appear and the lightdm
logfile shows a failed assertion.
In
*** This bug is a duplicate of bug 1056381 ***
https://bugs.launchpad.net/bugs/1056381
** Attachment added: from /var/log/lightdm/
https://bugs.launchpad.net/bugs/1057713/+attachment/3349385/+files/x-0.log
--
You received this bug notification because you are a member of Ubuntu
Bugs,
*** This bug is a duplicate of bug 1056381 ***
https://bugs.launchpad.net/bugs/1056381
** Attachment added: lightdm greeter logfile
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1057713/+attachment/3349386/+files/x-0-greeter.log
--
You received this bug notification
*** This bug is a duplicate of bug 1056381 ***
https://bugs.launchpad.net/bugs/1056381
** Attachment added: lightdm main logfile
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1057713/+attachment/3349387/+files/lightdm.log
--
You received this bug notification because you
*** This bug is a duplicate of bug 1056381 ***
https://bugs.launchpad.net/bugs/1056381
** Attachment added: related Xorg.log
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1057713/+attachment/3349388/+files/Xorg.0.log
--
You received this bug notification because you are a
*** This bug is a duplicate of bug 1056381 ***
https://bugs.launchpad.net/bugs/1056381
** Attachment added: crash report from /var/crash
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1057713/+attachment/3349389/+files/_usr_bin_Xorg.0.crash
** Summary changed:
- in
*** This bug is a duplicate of bug 1056381 ***
https://bugs.launchpad.net/bugs/1056381
The patch here might actually fix it.
http://www.mail-archive.com/spice-devel@lists.freedesktop.org/msg10334.html
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
*** This bug is a duplicate of bug 1056381 ***
https://bugs.launchpad.net/bugs/1056381
So it seems the bug is actually in the qxl driver.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1057713
*** This bug is a duplicate of bug 1056381 ***
https://bugs.launchpad.net/bugs/1056381
Seems to be the same issue as
https://bugzilla.redhat.com/show_bug.cgi?id=844463
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
*** This bug is a duplicate of bug 1056381 ***
https://bugs.launchpad.net/bugs/1056381
Ah, so it is a duplicate of 1056381
** This bug has been marked a duplicate of bug 1056381
error on x startup
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Serge,
This container I created with oneiric with the lxc-sshd template. It worked
there reasonably well (only needed to add a default route, which is missing).
I've compared (visually) what oneiric created for mounting and what precise
would have created. It seems there is only 1 difference.
Serge,
This container I created with oneiric with the lxc-sshd template. It worked
there reasonably well (only needed to add a default route, which is missing).
I've compared (visually) what oneiric created for mounting and what precise
would have created. It seems there is only 1 difference.
For me this seems not fixed.
ii apparmor 2.7.102-0ubuntu3 User-space
parser utility for AppArmor
ii lxc 0.7.5-3ubuntu56 Linux
containers userspace tools
root@kira:~# lxc-start -n jake
lxc-start: failed to mount rootfs
After the workaround, my container is running.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/947617
Title:
After update, lxc does not start
To manage notifications about this bug go
For me this seems not fixed.
ii apparmor 2.7.102-0ubuntu3 User-space
parser utility for AppArmor
ii lxc 0.7.5-3ubuntu56 Linux
containers userspace tools
root@kira:~# lxc-start -n jake
lxc-start: failed to mount rootfs
After the workaround, my container is running.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/947617
Title:
After update, lxc does not start
To manage notifications about this bug go to:
Architecture: amd64
ArecordDevices:
List of CAPTURE Hardware Devices
card 0: PCH [HDA Intel PCH], device 0: STAC92xx Analog [STAC92xx Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: janevert 3312 F
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/983712
Title:
WARNING: at
/build/buildd/linux-3.2.0/drivers/net/wireless/brcm80211/brcmsmac/main.c:8234
To manage notifications about this bug go to:
Joseph,
I was actually looking into why my kvm virtual machine was crashing and looked
in the host dmesg and noticed the trace.
At least in oneiric this didn't happen. I also don't know whether this happens
regularly, but I will keep an eye on it.
--
You received this bug notification because
Had some time over x-mas. Adding --noudevsync fixes it for me. 5
consecutive reboots all worked.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/802626
Title:
vgchange may deadlock in initramfs when
Serge, I've got the stock lvm2 package. So if that --noudevsync is in the stock
package, then yes, it usually fails.
The lvm2 is 2.02.66-4ubuntu3.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/802626
A me too.
I have /var and /home on two lvm partitions. /home only needs one of the two
partitions, /var was recently extended and now needs both. It fails in most
boots, more than 9 out of 10.
The comment from #34 also applies for me, no problem with the 3.0.0-13
kernel.
The thing I can add is
This happens to an Acer Aspire 3650 laptop as well. But apparently the
problem is that the driver does not handle interrupts well. So each time
I load the ath5k module it gets 20001 interrupts and then dmesg reports
about an unhandled interrupt.
--
[Linux] ath5k disconnect and become unusable
Can you comment if you've tested installing linux-backports-modules-
intrepid? If you haven't, please test. Thanks
Yes, I have installed it. Until now it has been behaving just fine (i.e.
no more rmmod/sleep/modprobe needed).
As far as I'm concerned, this is a good workaround for the bug.
I should note, though, that I had to manually blacklist the ath_pci
driver. Otherwise that still got loaded first.
--
Atheros wireless doesn't work on boot
https://bugs.launchpad.net/bugs/254946
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Leann,
Thanks for the attention.
** Attachment added: lspci-vvnn.log
http://launchpadlibrarian.net/22809355/lspci-vvnn.log
--
Atheros wireless doesn't work on boot
https://bugs.launchpad.net/bugs/254946
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Not at all. Unfortunately.
Sean McRobbie wrote:
Did you get anywhere with this? Having the same problem and finding it
hard to fix.
--
kernel BUG when using USB in domU (xen)
https://bugs.launchpad.net/bugs/273616
You received this bug notification because you are a member of Ubuntu
Bugs,
I've upgraded the laptop to Intrepid. This is still an issue.
I'll attach the intrepid dmesg.
With Intrepid the bug is more problematic than before because now sometimes
this only happens once NetworkManager wakes up after the interface re-apears.
--
Atheros wireless doesn't work on boot
** Attachment added: dmesg.txt
http://launchpadlibrarian.net/21683891/dmesg.txt
--
Atheros wireless doesn't work on boot
https://bugs.launchpad.net/bugs/254946
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing
sta...@stas:~$ cat /proc/version_signature
Ubuntu 2.6.27-9.19-generic
--
Atheros wireless doesn't work on boot
https://bugs.launchpad.net/bugs/254946
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
Rich,
If somebody could catch the bug in the debugger then at least the full text can
be found.
It does not necessarily need to come from the g-p-m binary. It could be from
any of the loaded libs or even have been loaded from configuration.
But if this is text then one possible option how it
me too.
--
package motion 3.2.9-6 failed to install/upgrade: subprocess post-installation
script returned error exit status 1
https://bugs.launchpad.net/bugs/280438
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
Also as said before, somewhere, the engine pointer sent to
gpm_cell_array_charge_low_cb (where the segfault occurs). Strange thing
is athat the pointer Mike's valgrind log complains about
(0x3a54494d45202a2a) is exactly the same as the pointer it complains
about when I test it..
It is
Public bug reported:
Binary package hint: samba
I've got win2k in a qemu vm and I'm using '-smb' with my home directory. When I
try to reach that network drive, smbd crashes. The log is below. And w2k
reports that the network path was not found.
Smbd reports that it is dumping core in
Please note that there's a simple 'chmod g+rw /var/run/samba/message.tbd' fixes
the access denied and thus prevents the whole stacktrace.
But I just thought that I should report it anyways.
--
3.2.3 and qemu: could not init smb messaging context
https://bugs.launchpad.net/bugs/278712
You
Public bug reported:
Binary package hint: samba
I've got win2k in a qemu vm and I'm using '-smb' with my home directory. When I
try to reach that network drive, smbd crashes. The log is below. And w2k
reports that the network path was not found.
Smbd reports that it is dumping core in
Please note that there's a simple 'chmod g+rw /var/run/samba/message.tbd' fixes
the access denied and thus prevents the whole stacktrace.
But I just thought that I should report it anyways.
--
3.2.3 and qemu: could not init smb messaging context
https://bugs.launchpad.net/bugs/278712
You
Public bug reported:
I've got a pci USB hub exported to a domU (to have cups drive it). As you can
see below, it doesn't work very well.
It's an single CPU amd64 machine with linux-image 2.6.24-21.42.
Although the kernel is Ubuntu, the rest of this domU is debian testing (the
combination
I've checked for that 'comm: usb'. I can't seem to locate its executable
(/proc/3490/exe exists, but ls reports 'cannot read symbolic link exe:
No such file or directory')
Anything else I can add?
--
kernel BUG when using USB in domU (xen)
https://bugs.launchpad.net/bugs/273616
You received
It's actually linux-image-2.6.24-21-xen. Not just 'linux-image' as I
wrote before.
--
kernel BUG when using USB in domU (xen)
https://bugs.launchpad.net/bugs/273616
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing
Public bug reported:
Binary package hint: multisync0.90
When I start multisync0.90, it prints the below when I attempt to add a member
to a new group.
(multisync0.90:446): Gtk-CRITICAL **: gtk_tree_store_get_path: assertion
`iter-user_data != NULL' failed
The user interface pops up the (empty)
Hi, no progress for a while.
With the backtrace, is this still incomplete?
I've moved on to intrepid (which uses the -intel driver instead of
-i810), so it'll be hard to test, confirm or check things.
--
[i915] GL screensaver crashes X server (using mergedFB)
Public bug reported:
Binary package hint: fontconfig
My laptop is intrepid (currently alpha). I noticed during upgrade of
fontconfig that the cache was updated four times. See the output during
apt-get below.
Is it really necessary to do this four times?
And that is even without
Public bug reported:
My wifes laptop has this wlan interface
09:02.0 Ethernet controller: Atheros Communications Inc. AR2413 802.11bg NIC
(rev 01)
On most boots it doesn't work right after boot and a rmmod/modprobe of
ath_pci makes it works again (sometimes needs to be repeated).
The dmesg
** Attachment added: dmesg.log
http://launchpadlibrarian.net/16559544/dmesg.log
--
Atheros wireless doesn't work on boot
https://bugs.launchpad.net/bugs/254946
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing
** Attachment added: interrupts.log
http://launchpadlibrarian.net/16559547/interrupts.log
--
Atheros wireless doesn't work on boot
https://bugs.launchpad.net/bugs/254946
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
** Attachment added: lspci-vvnn.log
http://launchpadlibrarian.net/16559549/lspci-vvnn.log
--
Atheros wireless doesn't work on boot
https://bugs.launchpad.net/bugs/254946
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
** Attachment added: uname-a.log
http://launchpadlibrarian.net/16559554/uname-a.log
--
Atheros wireless doesn't work on boot
https://bugs.launchpad.net/bugs/254946
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
** Attachment added: version.log
http://launchpadlibrarian.net/16559555/version.log
--
Atheros wireless doesn't work on boot
https://bugs.launchpad.net/bugs/254946
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
My guess is that, because it works after an rmmd/modprobe, trying the
suggestions in https://help.ubuntu.com/community/DebuggingIRQProblems is
no longer necessary.
--
Atheros wireless doesn't work on boot
https://bugs.launchpad.net/bugs/254946
You received this bug notification because you are a
** Changed in: linux (Ubuntu)
Assignee: (unassigned) = Ubuntu Kernel Team (ubuntu-kernel-team)
Status: New = Confirmed
--
Atheros wireless doesn't work on boot
https://bugs.launchpad.net/bugs/254946
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Hi Kay,
There are a couple of things you could check and/or add here as you
provide very little information.
First of all, your kernel, -4, is relatively old. At the moment -16 is
the released kernel and -19 is the latest security update. Could you
please test with that one?
Could you please
Umm, should've been more clear perhaps...
Grep for PREEMPT on the ubuntu and redhat kernel configurations (usually
located in /boot/config*). Also of interest are then the various HZ related
config items (hint grep HZ /boot/config-..).
And a diff between the redhat dmesg and ubuntu dmesg could
I've got this problem as well. I can't (using hardy 2.6.24-19) associate
with an ad-hoc network that consists of 2.4 and 2.6.early systems.
(don't know how to connect wpa-supplicant)
** Changed in: linux (Ubuntu)
Assignee: (unassigned) = Ubuntu Kernel Team (ubuntu-kernel-team)
** Tags added: cherry-pick
--
Please backport kernel fix for ad-hoc networks
https://bugs.launchpad.net/bugs/252573
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
Kay,
With RHEL 1000Hz I would expect 1ms delays. So there's something funny
as well.
As for ppol using ns precision to specify the timeout is the future.
Otherwise you end up changing the interface every 2 years (due to Moores
law).
As for your unique key, you could simply use the uptime. That
The reporter is having expectations from the kernel which are not satisfied.
In this case that (realttime) behavior is for a large part defined by the
kernel configuration. And that has consciously been decided upon by the kernel
team.
As such not a bug.
However, we do not need to let the
Bryce,
It is hardy already. What makes you think otherwise?
To start with these are the package versions (I guess I forgot them)...
ii xserver-xgl 1:1.1.99.1~git20080115-0ubuntu1
GL-based X server
ii xserver-xorg 1:7.3+10ubuntu10.2
There seems to be no dbg package for the i810 driver.
Here's a gdb trace:
#0 0x7f3bd6d43ddb in __glXDRIleaveServer (rendering=value optimized out)
at ../../../GL/glx/glxdri.c:151
pGlxPix = (__GLXpixmap *) 0x4720676e6967616d
j = 0
screen = (__GLXDRIscreen * const)
I'm seeing this both on dom0 and domU with ...-19.34.
As far as I can tell, there's no relation between seeing this on dom0 and domU.
However, there seem to be no side-effects.
(this is an amd64 install on both dom0 and domU and xen 3.2.1 from debian)
dom0:
Jun 26 14:02:06 quark kernel:
** Attachment added: xorg.conf
http://launchpadlibrarian.net/15639514/xorg.conf
** Changed in: gnome-screensaver (Ubuntu)
Sourcepackagename: None = gnome-screensaver
--
screensaver ignores mouse action on second display
https://bugs.launchpad.net/bugs/243449
You received this bug
Public bug reported:
I've got a dual-monitor system without xinerama. So there are two displays,
:0.0 and :0.1.
Whenever I'm working for longer periods on the .1 display using only the mouse
then screensaver kicks in just as if it didn't notice the mouse usage.
This is a x86_64 gutsy install
Since there are two people having this problem and there appears to be a
patch...
** Changed in: openoffice.org (Ubuntu)
Status: New = Confirmed
--
OOo 2.4 opens documents semi readonly
https://bugs.launchpad.net/bugs/225223
You received this bug notification because you are a member of
I also checked the dmesg. It appears to contain just one line that *might* be
related:
[ 6832.432571] [drm:i915_wait_irq] *ERROR* i915_wait_irq: EBUSY -- rec: 11
emitted: 16
I don't think this appears each time the X server crashes, which is the
reason for the 'might'.
--
GL screensaver
** Attachment added: Xorg.0.log.old
http://launchpadlibrarian.net/15533719/Xorg.0.log.old
--
GL screensaver crashes X server
https://bugs.launchpad.net/bugs/242330
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
** Attachment added: xorg.conf
http://launchpadlibrarian.net/15533718/xorg.conf
--
GL screensaver crashes X server
https://bugs.launchpad.net/bugs/242330
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
Public bug reported:
I recently started using a new X configuration (is it called mergedFB?). And
since then the screen saver crashes the X server with this trace:
Backtrace:
0: /usr/bin/X(xf86SigHandler+0x6a) [0x48402a]
1: /lib/libc.so.6 [0x7f84cb773100]
2:
Forgot to add... this is hardy but x86_64.
It's the same openoffice version.
The document that has the problem uses a TOC and outline numbering.
There are no frames or pictures. And there are some tables in there as
well.
What else can I do to help investigate?
--
OOo 2.4 opens documents semi
me too. Sometimes.
A simple, three word, document does not have this. But a larger, 8 page one,
does.
These two are stored side by side in the same directory...
--
OOo 2.4 opens documents semi readonly
https://bugs.launchpad.net/bugs/225223
You received this bug notification because you are a
@Tim, Hirano,
I believe that Hiranos last comment (comment 19) is that 17.31 only contains a
partial fix.
Any idea when 17.32 with the correct fix is coming?
(BTW, Hirano is right about the line with BUG being incorrect. Original
has [i] and fix has [j]. This BUG is producing the traces at
Chris, Wolfgang, Roger,
I'm not entirely sure about this, but it might be necessary to turn off
checksum offload in all doms on the same machine. If I remember
correctly, it is required to turn off the offload in dom0 as well. I
know I have it off in all domUs and dom0.
--
xen guest kernel
Chris has a point there, about checksumming.
I have no problems with the 17.31 kernel on an amd64 domU. And dom0 is running
the hardy kernel (-16.xx), also amd64. I'm using debians hypervisor
(3.2.0-3~bpo4+2).
And I DO have checksumming offload off (as described using
/etc/network/interfaces).
After the workaround I did, samba started and was usable from a w2k in qemu.
(I did start chmodding only one file and manually starting smbd and then it
complained about another one and then another one...)
I don't know what's incomplete about this bug and I can confirm that it
still exists with
After the workaround I did, samba started and was usable from a w2k in qemu.
(I did start chmodding only one file and manually starting smbd and then it
complained about another one and then another one...)
I don't know what's incomplete about this bug and I can confirm that it
still exists with
Me too.
As a really ugly workaround I thought about this...
(1) disable samba to run as daemon (add 'exit' in /etc/default/samba)
(2) sudo chmod a+rw /var/run/samba/*.tdb /var/lib/samba/*.tdb
This totally ruins the samba security, I expect. That's why I disabled
samba to start as a daemon.
--
Me too.
As a really ugly workaround I thought about this...
(1) disable samba to run as daemon (add 'exit' in /etc/default/samba)
(2) sudo chmod a+rw /var/run/samba/*.tdb /var/lib/samba/*.tdb
This totally ruins the samba security, I expect. That's why I disabled
samba to start as a daemon.
--
Russell,
what kernel are you currently using? I.e. does that domU work with a
different kernel?
Thanks.
--
xen guest kernel bug: 'kernel BUG at
/build/buildd/linux-2.6.24/debian/build/custom-source-xen/drivers/xen/netfront/netfront.c:785'
https://bugs.launchpad.net/bugs/218126
You received
kibe,
it would be really useful to have the full trace. I suspect that it is present
in 'dmesg'.
Because it is now cut-off by the prompt.
Thanks.
--
xen guest kernel bug: 'kernel BUG at
/build/buildd/linux-2.6.24/debian/build/custom-source-xen/drivers/xen/netfront/netfront.c:785'
For me the image from proposed (17.31) works for and amd64 domU. I can
ssh into the domU.
(note that this debian etch/testing domU previously worked ok using
2.6.18 and I only replaced the kernel)
--
xen guest kernel bug: 'kernel BUG at
Did you try the debug parameter of ndiswrapper?
Also the output of 'ndiswrapper -v' and 'ndiswrapper -l' would be interesting.
Also, your problem might have been fixed in ndiswrapper 1.51:
http://sourceforge.net/project/shownotes.php?release_id=562382group_id=93482
Perhaps somewhere you can find
It appears that your initrd is incomplete.
Would you please check that there is enough disk space in /boot? (try df -h
/boot)
And also check the size of the initrd: ls -l /boot/initrd*; compare it with
other versions.
You can try recreating the initrd with 'update-initramfs -u
Matthias,
Matthias Andersson wrote:
I ran the command update-initramfs -vu 2.6.24-16-386 and it seems to
have hit the spot.
What could had corrupted the old configuration, some error on shutdown or?
//Matthias
I've occaisionally had this as well. The ones I could trace were all
caused by
Given that there are two reports that there's a setup where other kernel
versions work but this one does not, I'd say it is confirmed that
there's a bug in this kernel.
** Also affects: linux-source-2.6.24 (Ubuntu)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu)
Perhaps someboby should try a redhat kernel. Their status page
(http://fedoraproject.org/wiki/Features/XenPvops) says it works...
After that it just the same game: spot the difference.
--
networking not working
https://bugs.launchpad.net/bugs/204010
You received this bug notification because
So I tried it myself. It took actually a lot less effort than I
expected!
I downloaded the current xen kernel from (1), search for kernel-xen, and used
alien to extract it (alien -g).
The package also contains xen itself, I think, so don't convert and install!
I manually copied part of /boot
I just realized that this bug is on xen-3.2. But I guess this is wrong.
I have a etch(64) domU with 2.6.18-5 on it.
I have another domU with eth(64) userspace which I use for playing and testing.
I've used this with the eth kernel (2.6.18), the feisty or gutsy 2.6.22 and now
the hardy 2.6.24.
Gareth, me too.
I just tried (on my domU to fool around with) the latest rawhide kernel-xen.
Runs just fine (for the last 30 or minutes and there's a lockdep warning early
in dmesg -- so there's not much trust).
[EMAIL PROTECTED]:~$ uname -r
2.6.25-0.18.rc8.fc9.x86_64.xen
--
Time went
So it was not really a bug, just that the block access is now as a module
instead of built-in.
So I'm setting it to invalid (that's about the best I can guess).
Also in 2.6.24.-16 it is back to built-in.
And the networking is better handled in #204010.
** Changed in: linux (Ubuntu)
I upgraded my laptop to hardy (which is due in some 12days).
This is no longer a problem. GL based screensavers only show on one screen, but
at least don't crash the session.
--
[gutsy] dualhead + locking system xorg crashes (915GM) (i810 driver)
https://bugs.launchpad.net/bugs/153878
You
With hardy (due in 12 days) this is no longer a problem.
--
wav file doesn't play properly on gusty-64
https://bugs.launchpad.net/bugs/190876
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
Another me too.
Deti, in -16 they finally decided to make the front- and backends into the
kernel instead of modules.
So the /etc/initramfs/modules workaround is no longer needed.
--
networking not working
https://bugs.launchpad.net/bugs/204010
You received this bug notification because you
MaurÃcio Magalhães wrote:
Ignore my previous post, because it worked
Workaround:
add to /etc/initramfs-tools/modules:
xenblk
blktap
blkbck
and launch update-initramfs -u
Tanks
Actually you only need xenblk in a domU.
I am interested whether you get the network operational.
I'm not so bold as to re-open this bug. But I really want you people to
seriously consider my case.
I've got this amd64 box with xen on it (running amd64 arch). The dom0 crashes
exactly as Jorge Juan shows above (in
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/26119/comments/30).
Up
2.6.24-12 still has the same network problem. It appears to drop all received
packets on the floor.
Without any explanation.
--
2.6.24-7 does not start as xen domU
https://bugs.launchpad.net/bugs/190870
You received this bug notification because you are a member of Ubuntu
Bugs, which is
The workaround described by Lionel works.
Only xenblk is needed to make a domU boot.
Next stop: getting the network interface operational...
It first does this:
Synthesizing the initial hotplug events...done.
Waiting for /dev to be fully populated...[ 17.336715] netfront: Initialising
virtual
1 - 100 of 108 matches
Mail list logo
