Re: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Thanks,
Stan Hoeppner <stan@hardwarefreak.com> writes:
> That's not really much data/evidence to analyze for a solution. If this didn't
> occur _before_, what has changed between _before_ and now? Always look for the
> simplest solution first, using process of elimination.
I know, but I do not have any other clue. Which direction should I
have to investigate in?
>
> If you didn't change any hardware in the system, and this lockup problem didn't
> exist when you were running 2.6.24, then there may be an obscure bug in 2.6.26
> that you've run into, that maybe only surfaces with a specific
> hardware combination.
I directly installed 2.6.26, and this problem happened in the very beginning.
>
> Wild ass guess suggestion given so little to go on: if you're using a USB
> keyboard, switch to a PS/2 keyboard and see if that helps. Sometimes there can
> be IRQ 1 issues when using a USB keyboard due to the hub jump(s) and trickery
> being performed by the system BIOS. A PS/2 KB is hard wired into the 8259 (or
> equivalent) so IRQ 1 is always asserted. If the system still doesn't respond to
> PS/2 KB input, then I'd hazard to say there is something wrong with your kernel,
> or with your hardware.
Unfortunately, I am using a PS/2 KB. I tried unplugging *all* the USB
stuff (thus using a mere config), and the same problem still
happens. I am not using a very complexe hardware config. I do not
understand this problem.
Thanks.
- --
Merciadri Luca
See http://www.student.montefiore.ulg.ac.be/~merciadri/
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Processed by Mailcrypt 3.5.8 <http://mailcrypt.sourceforge.net/>
iEYEARECAAYFAks8ZcAACgkQM0LLzLt8Mhzh1wCfRtHN14V+9EyKLDSOHNExsUsY
uGYAnRXAZO/IO8Vw1UspW6V3ISycLI4Q
=g63Q
-----END PGP SIGNATURE-----
Reply to: