On 20/10/2015 16:27, Boris Ostrovsky wrote:
> On 10/20/2015 09:43 AM, Jan Beulich wrote:
> On 20.10.15 at 15:22, wrote:
>>> The reason I think its this commit is that RAX, RDX and RCX look very
>>> much like arguments to xsetbv (which xstate_enable_boot_cpu() executes)
>>> and RAX value is 0x1
>>> On 20.10.15 at 16:27, wrote:
> On 10/20/2015 09:43 AM, Jan Beulich wrote:
> On 20.10.15 at 15:22, wrote:
>>> The reason I think its this commit is that RAX, RDX and RCX look very
>>> much like arguments to xsetbv (which xstate_enable_boot_cpu() executes)
>>> and RAX value is 0x1f, which h
On 10/20/2015 09:43 AM, Jan Beulich wrote:
On 20.10.15 at 15:22, wrote:
The reason I think its this commit is that RAX, RDX and RCX look very
much like arguments to xsetbv (which xstate_enable_boot_cpu() executes)
and RAX value is 0x1f, which has two new bits that this commit defined.
That wou
>>> On 20.10.15 at 15:22, wrote:
> The reason I think its this commit is that RAX, RDX and RCX look very
> much like arguments to xsetbv (which xstate_enable_boot_cpu() executes)
> and RAX value is 0x1f, which has two new bits that this commit defined.
That would be the two MPX related bits, ye
On 10/20/2015 08:11 AM, John Doe wrote:
On 20/10/2015 11:51, Jan Beulich wrote:
On 19.10.15 at 18:25, wrote:
On 10/19/2015 06:16 AM, John Doe wrote:
[0.00] general protection fault: [#1] SMP
[0.00] Modules linked in:
[0.00] CPU: 0 PID: 0 Comm: swapper Not tainted
On 20/10/2015 11:51, Jan Beulich wrote:
On 19.10.15 at 18:25, wrote:
>> On 10/19/2015 06:16 AM, John Doe wrote:
> [0.00] general protection fault: [#1] SMP
> [0.00] Modules linked in:
> [0.00] CPU: 0 PID: 0 Comm: swapper Not tainted
>> 4.1.9-6.pvops.q
>>> On 19.10.15 at 18:25, wrote:
> On 10/19/2015 06:16 AM, John Doe wrote:
[0.00] general protection fault: [#1] SMP
[0.00] Modules linked in:
[0.00] CPU: 0 PID: 0 Comm: swapper Not tainted
> 4.1.9-6.pvops.qubes.x86_64 #1
[0.00] Hardware na
On 10/19/2015 06:16 AM, John Doe wrote:
[0.00] general protection fault: [#1] SMP
[0.00] Modules linked in:
[0.00] CPU: 0 PID: 0 Comm: swapper Not tainted
4.1.9-6.pvops.qubes.x86_64 #1
[0.00] Hardware name: To Be Filled By O.E.M. To Be Filled By
O.E.M./Z170
On 19/10/2015 09:56, Ingo Molnar wrote:
>
> Please Cc: the Xen maintainers as this appears to be Xen specific. Also,
> please
> Cc: linux-kernel@vger.kernel.org.
>
> Thanks,
>
> Ingo
>
> * John Doe wrote:
>
>> Hello,
>> I get a kernel panic on QubesOS 3.0 during boot with kernels newe
Ok, I'll do that
Thanks
Sent from my iPhone
On Oct 14, 2007, at 2:32 PM, Trond Myklebust
<[EMAIL PROTECTED]> wrote:
On Sun, 2007-10-14 at 14:00 -0700, Scott Petler wrote:
Doug,
I thought that might do it, it does seem to work. I edited the
driver
line in my xorg.conf
from nvidia
On Sun, 2007-10-14 at 14:00 -0700, Scott Petler wrote:
> Doug,
>
> I thought that might do it, it does seem to work. I edited the driver
> line in my xorg.conf
> from nvidia to nv and then,
> F1
> login as root
> /etc/init.d/gdm stop
> /etc/init.d/gdm start
>
> It came back up with the same f
Doug,
I thought that might do it, it does seem to work. I edited the driver
line in my xorg.conf
from nvidia to nv and then,
F1
login as root
/etc/init.d/gdm stop
/etc/init.d/gdm start
It came back up with the same flashing crap on the second monitor, so I
did it again with
the 2nd monitor
On Oct 14, 2007, at 1:44 PM, Scott Petler wrote:
Trond,
I'm not exactly sure how to go back to not using the nvidia driver
and select the xorg one. I do know that I wasn't able to use both
monitors with the xorg driver, but I'm willing to try that to
isolate the problem.
If memory serv
Trond,
I'm not exactly sure how to go back to not using the nvidia driver and
select the xorg one. I do know that I wasn't able to use both monitors
with the xorg driver, but I'm willing to try that to isolate the problem.
Scott
Output from /proc/mounts:
rootfs / rootfs rw 0 0
none /sys sys
On Sat, 2007-10-13 at 15:48 -0700, Scott Petler wrote:
> Machine lockup with caps lock/num lock flashing or complete reboot/panic.
>
> I get various lockup issues with this kernel, (2.6.23 also similar
> problem). I had problems getting e1000 lan module to work (it was fine
> in 2.6.21.5). I
Machine lockup with caps lock/num lock flashing or complete reboot/panic.
I get various lockup issues with this kernel, (2.6.23 also similar
problem). I had problems getting e1000 lan module to work (it was fine
in 2.6.21.5). I disabled it and installed a different lan card that
seems to wo
Summary Info:
Kernel halts with a kernel panic when a member of a RAID1 failed.
Detail Info:
I hope it's due to one of the drives failing, but I'm not sure. I've had
endless issues with this machine. Any help would be appreciated.
Jun 27 05:22:27 sabertooth kernel: ata1: handling error/timeout
I put the Oops on my web site (see Section 5 for links). BTW, tell me
if I did not do the ksymoops ok !
Jf.
--
[1.] One line summary of the problem:
kernel panic while copying files
[2.] Full description of the problem/report:
When I copy a 450 MB file from one partition (/usr) to
Ok, I'll get back with the oops information ASAP !
Tigran Aivazian wrote:
>
> Jean-Francois,
>
> You are reporting a panic but missing the most important ingredient:
>
> On Wed, 1 Nov 2000, Jean-Francois Patenaude wrote:
> > [5.] Output of Oops.. message (if applicable) with symbolic infor
Jean-Francois,
You are reporting a panic but missing the most important ingredient:
On Wed, 1 Nov 2000, Jean-Francois Patenaude wrote:
> [5.] Output of Oops.. message (if applicable) with symbolic information
> resolved (see Documentation/oops-tracing.txt)
>
> xx
>
If "xx" means "kiss-k
[1.] One line summary of the problem:
kernel panic while copying files
[2.] Full description of the problem/report:
When I copy a 450 MB file from one partition (/usr) to another (/tmp) I
get a kernel panic. It happens everytime I copy that file. The amount
of data copied before the
21 matches
Mail list logo
