> > Unfortunately, after starting cpuspeed daemon, I get this:
>
> It looks like it's happening sometime after cpuspeed starts.
> Could you disable cpuspeed and see if the problem still
> occurs?
If anything it must be something in the kernel (except someone
does very strange stuff in /dev/mem)
>
> > Starting cpuspeed: [ OK ]
> > Starting pcmcia: Starting PCMCIA services:
> > CPU 6: Machine Check Exception: 4 Bank 4:
> > b200000000070f0f
> > TSC 4129a3d70d
>
> > Code: Bad RIP value.
> > RIP [<00000000000000ff>] RSP <ffff81003fe63fa0>
> > CR2: 00000000000000ff
> > <0>Kernel panic - not syncing: Oops
>
> Andi said that "Something tried to access a physical memory
> address that was not mapped in the CPU." Andi, is this
> related to the bug that you thought might have been fixed
> in 2.6.12-rc6-git4?
No, I don't think so. In that bug something would be mapped
twice, not nothing. Also nobody reported watchdog timeouts
for that one.
-Andi
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
