Processing commands for [EMAIL PROTECTED]:
> merge 503821 503962
Bug#503821: linux-image-2.6.26-1-xen-amd64: Kernel crash in Dom0 (Eeek!
page_mapcount(page) went negative! (-1))
Bug#503962: linux-image-2.6.26-1-xen-amd64: kernel oops after short on memory
situation
Merged 503821 503962.
> thank
Hello,
On Wed, 29 Oct 2008, Lars Michael Jogback wrote:
> I've done some more tests.
>
> The problem seem to be related to swapping.
Thanks for figuring that out!
I tested this with the following configurations where except for the
kernel everthing else is from lenny (including the xen hypervis
Hey,
do you still reproduce this? I never saw something like this, so it's
kind of weird.
Can your provide complete log for update-initramfs -u -v ?
Cheers,
--
Yves-Alexis
signature.asc
Description: This is a digitally signed message part
Package: linux-image-2.6.26-1-xen-amd64
Version: 2.6.26-8
Severity: important
I can consistently make the kernel oops with the following situation:
If I have a domain (either domU or dom0) that is limited on memory and I start
a program that needs
more memory than available as physical memory,
Hello.
I have a similar problem with my sid and Lenovo T60, but with other
kernel version. After upgrade to latest sid kernel (2.6.26-9) i am not
able to resume from s2ram (i use "s2ram" from uswsusp). After downgrade
(and reboot) to testing version 2.6.26-8 i can suspend and resume again
wit
I've produced a 2.6.26 based kernel with the DMA engine patches from
Intel. Your Thecus N2100 will have considerably better hard drive
performance with this kernel. However, the patches are experimental
and not in the mainline kernel. I haven't seen any data corruption
with the current version o
Processing commands for [EMAIL PROTECTED]:
> reassign 456763 xserver-xorg-core 2:1.4.2-7
Bug#456763: base: keyboard random repeat
Bug reassigned from package `linux-2.6' to `xserver-xorg-core'.
> thanks
Stopping processing here.
Please contact me if you need assistance.
Debian bug tracking syst
On Wed, Oct 29, 2008 at 04:28:55PM +0100, Bastian Blank wrote:
> Please read http://www.debian.org/MailingLists/.
???
> It is a hard dependency, or does virtualbox work without the module?
It does work without a module, but you cannot start a VM. Now this reduces the
functionality significantly
Please read http://www.debian.org/MailingLists/.
On Wed, Oct 29, 2008 at 02:35:56PM +0100, Michael Meskes wrote:
> On Wed, Oct 29, 2008 at 01:52:20PM +0100, Bastian Blank wrote:
> > > Therefore I wonder whether we should add a conflict into the module's
> > > control
> > > file. Comments anyone?
On Wed, Oct 29, 2008 at 01:52:20PM +0100, Bastian Blank wrote:
> > Therefore I wonder whether we should add a conflict into the module's
> > control
> > file. Comments anyone?
>
> No. virtualbox have to make this a dependency. I have no problem in
> producing a virtual package name which describe
Processing commands for [EMAIL PROTECTED]:
> reopen 502346
Bug#502346: virtualbox-ose-modules package older than virtualbox-ose
Bug#502539: virtualbox-ose-modules-2.6.26-1-686 contains outdated module for
VirtualBox
Bug reopened, originator not changed.
> thanks
Stopping processing here.
Please
reopen 502346
thanks
This RC BR was closed silently (using 'close' to control), without giving
any explanation and without the issue being fixed. IMO that's not an
acceptable way to deal with RC bugs.
I'm reopening the BR as the virtualbox-ose kernel modules in testing are
still not usable wit
I've done some more tests.
The problem seem to be related to swapping.
I used this little test program:
#include
/* my amount of ram */
#define TESTSIZE 2048000
struct testchunk {
char name[1048576];
};
main()
{
int *p;
int t;
for (t=0;tLVM->MD-raid1, but just to be sure
I've used a
On Wed, Oct 29, 2008 at 12:17:50PM +0100, Michael Meskes wrote:
> On Tue, Oct 28, 2008 at 11:00:44PM +0100, Bastian Blank wrote:
> > Please describe the version requirements of the dependency vbox
> > application and kernel module. There was reports that a 1.6.2 module
> > does not work with a 1.6.
On Tue, Oct 28, 2008 at 11:00:44PM +0100, Bastian Blank wrote:
> Please describe the version requirements of the dependency vbox
> application and kernel module. There was reports that a 1.6.2 module
> does not work with a 1.6.6 application.
The version has to be the same afaik. It appears that th
Hi!
On Tuesday 28 October 2008 13:27:48 Tomasz Chmielewski wrote:
> Upstream tgt is in a "releasable" state for some time now.
>
> And 0.9.1 version was released quite recently.
I already started working on it, adding iSER support, and trying to find an
FCoE initiator to get that target package
* Thiemo Seufer <[EMAIL PROTECTED]> [2008-09-15 14:11]:
> I am promised to have internet access again at home next weekend,
> working on the SWARM kernels is the highest Debian-related priority
> I have at that point.
Thiemo, what's the status of this?
--
Martin Michlmayr
http://www.cyrius.com/
17 matches
Mail list logo
