On Tue, 2010-02-09 at 12:19 +, Bryn M. Reeves wrote:
> On Sun, 2010-02-07 at 17:32 -0430, Patrick O'Callaghan wrote:
> > After reducing my RAM to 2GB via the mem= boot option (see parallel
> > branch of this thread) I don't seem to be getting memory errors, but I
> > still have problems, appare
On Sun, 2010-02-07 at 17:32 -0430, Patrick O'Callaghan wrote:
> After reducing my RAM to 2GB via the mem= boot option (see parallel
> branch of this thread) I don't seem to be getting memory errors, but I
> still have problems, apparently with NFS. I've posted a trace from
> dmesg to http://fpaste.
On Sun, 2010-02-07 at 17:32 -0430, Patrick O'Callaghan wrote:
[...]
> After reducing my RAM to 2GB via the mem= boot option (see parallel
> branch of this thread) I don't seem to be getting memory errors, but I
> still have problems, apparently with NFS. I've posted a trace from
> dmesg to http://f
s you've some other reason to suspect
> sysfs is related I'd doubt there's anything to connect the two.
>
>
> > Here goes. Looks like PA may be involved (I've had it crash a lot
> > lately).
>
> PA looks like an innocent victim (or if it is in any
On Sun, 2010-02-07 at 10:07 -0600, Mikkel wrote:
> On 02/07/2010 03:42 AM, Gilboa Davara wrote:
> >
> > poc,
> >
> > mem=2000m may not help, as your BIOS/chipset might be interleaving
> > memory from multiple banks.
> > I'd know more if you post your hardware configuration. (CPU,
> > Motherboard,
On Sun, 2010-02-07 at 11:42 +0200, Gilboa Davara wrote:
> On Fri, 2010-02-05 at 19:30 -0430, Patrick O'Callaghan wrote:
> > On Fri, 2010-02-05 at 17:51 +, Bryn M. Reeves wrote:
> > > > [] path_put+0x1a/0x27
> > > > [] audit_free_names+0x5b/0x7a
> > > > [] audit_syscall_exit+0xb3/0x14c
> > >
On 02/07/2010 03:42 AM, Gilboa Davara wrote:
>
> poc,
>
> mem=2000m may not help, as your BIOS/chipset might be interleaving
> memory from multiple banks.
> I'd know more if you post your hardware configuration. (CPU,
> Motherboard, number of DIMMs, etc.)
>
> In general, you should disable inter
On Fri, 2010-02-05 at 19:30 -0430, Patrick O'Callaghan wrote:
> On Fri, 2010-02-05 at 17:51 +, Bryn M. Reeves wrote:
> > > [] path_put+0x1a/0x27
> > > [] audit_free_names+0x5b/0x7a
> > > [] audit_syscall_exit+0xb3/0x14c
> > > [] sysret_audit+0x14/0x1e
> >
> > Are the crashes you're seeing
On Fri, 2010-02-05 at 17:51 +, Bryn M. Reeves wrote:
> > [] path_put+0x1a/0x27
> > [] audit_free_names+0x5b/0x7a
> > [] audit_syscall_exit+0xb3/0x14c
> > [] sysret_audit+0x14/0x1e
>
> Are the crashes you're seeing always in this set of functions (same
> backtrace) or are you getting variat
s you've some other reason to suspect
> sysfs is related I'd doubt there's anything to connect the two.
>
>
> > Here goes. Looks like PA may be involved (I've had it crash a lot
> > lately).
>
> PA looks like an innocent victim (or if it is in any
to connect the two.
> Here goes. Looks like PA may be involved (I've had it crash a lot
> lately).
PA looks like an innocent victim (or if it is in any direct way
implicated it is just triggering a kernel bug that was already there -
userspace should not be able to make the kernel GP
On Fri, 2010-02-05 at 19:12 +0200, Gilboa Davara wrote:
> On Fri, 2010-02-05 at 11:45 -0430, Patrick O'Callaghan wrote:
> > I've had several of these is the past few days. They all seem related
> > to /sys/devices/platform/coretemp.1/temp1_input, but my machine isn't
> > running particularly hot (a
On Fri, 2010-02-05 at 11:45 -0430, Patrick O'Callaghan wrote:
> I've had several of these is the past few days. They all seem related
> to /sys/devices/platform/coretemp.1/temp1_input, but my machine isn't
> running particularly hot (at least according to ksensors). It's around
> 60 on both cpus.
>
I've had several of these is the past few days. They all seem related
to /sys/devices/platform/coretemp.1/temp1_input, but my machine isn't
running particularly hot (at least according to ksensors). It's around
60 on both cpus.
Intel(R) Core(TM)2 CPU 6400 @ 2.13GHz on an Intel 965 mobo.
Fedora 2.6
14 matches
Mail list logo
