reassign 642154 src:linux
thanks
On Tue, Sep 20, 2011 at 01:00:45AM +0300, rush wrote:
Package: linux-2.6
Version: 3.0.0-3
Severity: important
Tags: upstream
Dear Maintainer,
I have some suspicious activities on my server: i've continiously repeated
messages in dmesg about BUG:
OK, I tried it again, but Oops didn't gone.
menuentry 'Debian GNU/Linux, with Xen 4.0-amd64 and Linux
3.0.0-1-amd64' --class debian --class gnu-linux --class gnu --class os
--class xen {
insmod raid
insmod mdraid1x
insmod lvm
insmod part_msdos
insmod
echo'Loading Xen 4.0-amd64 ...'
multiboot /boot/xen-4.0-amd64.gz placeholder
Oops. I meant to try it in the hypervisor - so right after placeholder add
xsave=0
echo'Loading Linux 3.0.0-1-amd64 ...'
module /boot/vmlinuz-3.0.0-1-amd64 placeholder
On Mon, 2011-10-03 at 14:47 -0400, Konrad Rzeszutek Wilk wrote:
echo'Loading Xen 4.0-amd64 ...'
multiboot /boot/xen-4.0-amd64.gz placeholder
Oops. I meant to try it in the hypervisor - so right after placeholder add
xsave=0
Which in grub2 means add
2011/10/1, Jonathan Nieder jrnie...@gmail.com:
Cc-ing the reporter. Rush, are you able to reproduce the oops you
mentioned? Does adding noxsave to the kernel command line help?
I'm sorry, i'm not guru in such questions.
Do I need to specify xsave=0 in grub boot options or there is another
On Sat, 2011-10-01 at 11:01 +0400, rush wrote:
2011/10/1, Jonathan Nieder jrnie...@gmail.com:
Cc-ing the reporter. Rush, are you able to reproduce the oops you
mentioned? Does adding noxsave to the kernel command line help?
I'm sorry, i'm not guru in such questions.
Do I need to
Unfortunately, xsave=0 didn't give any effect. Oops is still here.
[ 21.095558] BUG: unable to handle kernel paging request at 8803bb7c5000
[ 21.095827] IP: [810106db] __sanitize_i387_state+0x23/0xe1
[ 21.096002] PGD 1604067 PUD 3d82d9067 PMD 3d84b5067 PTE 0
[ 21.096355] Oops:
Konrad Rzeszutek Wilk wrote:
There's been some similar looking threads on xen-devel recently but I
haven't paid attention to the details, list Konrad CC'd. Full log is
at http://bugs.debian.org/642154.
Does xsave=0 make a difference?
Cc-ing the reporter. Rush, are you able to reproduce
Hi,
There are several Not tainted lines in old messages file. There are all of them:
Sep 10 22:35:33 xen-dom0 kernel: [24183.985513] Pid: 2605, comm:
debootstrap Not tainted 3.0.0-1-amd64 #1 Intel Corporation
S1200BTL/S1200BTL
Sep 10 22:35:33 xen-dom0 kernel: [24183.985621] RIP:
On Tue, 2011-09-20 at 10:12 +0400, rush wrote:
Hi,
There are several Not tainted lines in old messages file. There are all of
them:
Sep 10 22:35:33 xen-dom0 kernel: [24183.985513] Pid: 2605, comm:
debootstrap Not tainted 3.0.0-1-amd64 #1 Intel Corporation
S1200BTL/S1200BTL
Sep 10
On Tue, 2011-09-20 at 14:20 +0100, Ben Hutchings wrote:
On Tue, 2011-09-20 at 10:12 +0400, rush wrote:
Hi,
There are several Not tainted lines in old messages file. There are all of
them:
Sep 10 22:35:33 xen-dom0 kernel: [24183.985513] Pid: 2605, comm:
debootstrap Not tainted
Package: linux-2.6
Version: 3.0.0-3
Severity: important
Tags: upstream
Dear Maintainer,
I have some suspicious activities on my server: i've continiously repeated
messages in dmesg about BUG: unable to handle kernel paging request, also
there are many messages like
Message from
Hi,
rush wrote:
I have some suspicious activities on my server: i've continiously repeated
messages in dmesg about BUG: unable to handle kernel paging request
Yes, if this server is open to the public (especially if it has
untrusted local users), you should probably take it down. A kernel
13 matches
Mail list logo
