On Saturday 24 February 2007 06:31, Glauber de Oliveira Costa wrote:
> When a page faults comes from a kernel space, the printed summary
> leaves us clueless about what kind of access was being tried (which
> is encoded in the error_code variable).
>
> Having it promply available may ease
On Saturday 24 February 2007 06:31, Glauber de Oliveira Costa wrote:
When a page faults comes from a kernel space, the printed summary
leaves us clueless about what kind of access was being tried (which
is encoded in the error_code variable).
Having it promply available may ease debugging in
On Sat, Feb 24, 2007 at 02:12:29PM -0500, Chuck Ebbert wrote:
>
> Umm, it's already there, right after the word "Oops".
>
>
> Oops: 0002 [1] SMP
>
Oops! ;-)
--
Glauber de Oliveira Costa
Red Hat Inc.
"Free as in Freedom"
-
To unsubscribe from this list: send the line "unsubscribe
Glauber de Oliveira Costa wrote:
> When a page faults comes from a kernel space, the printed summary
> leaves us clueless about what kind of access was being tried (which
> is encoded in the error_code variable).
>
> Having it promply available may ease debugging in a bunch of
> situations.
>
>
Glauber de Oliveira Costa wrote:
When a page faults comes from a kernel space, the printed summary
leaves us clueless about what kind of access was being tried (which
is encoded in the error_code variable).
Having it promply available may ease debugging in a bunch of
situations.
On Sat, Feb 24, 2007 at 02:12:29PM -0500, Chuck Ebbert wrote:
Umm, it's already there, right after the word Oops.
Oops: 0002 [1] SMP
Oops! ;-)
--
Glauber de Oliveira Costa
Red Hat Inc.
Free as in Freedom
-
To unsubscribe from this list: send the line unsubscribe
6 matches
Mail list logo