On Dec 21, 2007 3:00 PM, Andrew Morton <[EMAIL PROTECTED]> wrote:
> On Fri, 21 Dec 2007 11:06:49 -0500 "Miles Lane" <[EMAIL PROTECTED]> wrote:
>
> > > >
> > > > How do I determine what comes next?
> > > >
> > >
> > > By comparing it with the /proc/iomem from prior to suspending the machine.
> > >
On Fri, 21 Dec 2007 11:06:49 -0500 "Miles Lane" <[EMAIL PROTECTED]> wrote:
> > >
> > > How do I determine what comes next?
> > >
> >
> > By comparing it with the /proc/iomem from prior to suspending the machine.
> >
>
> The offending information seems to be "9000-9fff : Intel Flush Page"
On Dec 21, 2007 1:29 AM, Andrew Morton <[EMAIL PROTECTED]> wrote:
>
> On Fri, 21 Dec 2007 00:58:19 -0500 "Miles Lane" <[EMAIL PROTECTED]> wrote:
>
> > On Dec 20, 2007 12:32 PM, Andrew Morton <[EMAIL PROTECTED]> wrote:
> >
> > > On Thu, 20 Dec 2007 08:38:03 -0500 Miles Lane <[EMAIL PROTECTED]>
> >
On Dec 21, 2007 1:29 AM, Andrew Morton [EMAIL PROTECTED] wrote:
On Fri, 21 Dec 2007 00:58:19 -0500 Miles Lane [EMAIL PROTECTED] wrote:
On Dec 20, 2007 12:32 PM, Andrew Morton [EMAIL PROTECTED] wrote:
On Thu, 20 Dec 2007 08:38:03 -0500 Miles Lane [EMAIL PROTECTED]
wrote:
On
On Fri, 21 Dec 2007 11:06:49 -0500 Miles Lane [EMAIL PROTECTED] wrote:
How do I determine what comes next?
By comparing it with the /proc/iomem from prior to suspending the machine.
The offending information seems to be 9000-9fff : Intel Flush Page
ah-hah.
On Dec 21, 2007 3:00 PM, Andrew Morton [EMAIL PROTECTED] wrote:
On Fri, 21 Dec 2007 11:06:49 -0500 Miles Lane [EMAIL PROTECTED] wrote:
How do I determine what comes next?
By comparing it with the /proc/iomem from prior to suspending the machine.
The offending information
On Fri, 21 Dec 2007 00:58:19 -0500 "Miles Lane" <[EMAIL PROTECTED]> wrote:
> On Dec 20, 2007 12:32 PM, Andrew Morton <[EMAIL PROTECTED]> wrote:
>
> > On Thu, 20 Dec 2007 08:38:03 -0500 Miles Lane <[EMAIL PROTECTED]>
> > wrote:
> >
> > > On further investigation, "cat /proc/iomem" does not
Resending... Curse GMail's HTML messages!
On Dec 21, 2007 12:58 AM, Miles Lane <[EMAIL PROTECTED]> wrote:
>
> On Dec 20, 2007 12:32 PM, Andrew Morton <[EMAIL PROTECTED]> wrote:
>
> > On Thu, 20 Dec 2007 08:38:03 -0500 Miles Lane <[EMAIL PROTECTED]> wrote:
> >
> > > On further investigation, "cat
On Thu, 20 Dec 2007 08:38:03 -0500 Miles Lane <[EMAIL PROTECTED]> wrote:
> On further investigation, "cat /proc/iomem" does not trigger the stack
> trace until after a suspend-to-disk/resume cycle has occurred.
I still can't reproduce this.
Could you please try this?
- cat /proc/iomem
-
On further investigation, "cat /proc/iomem" does not trigger the stack
trace until after a suspend-to-disk/resume cycle has occurred.
I am removing Ingo and Russell from the TO list (as they are apparently
the wrong people) and adding the suspend folks, as suspend is implicated.
My .config
On further investigation, cat /proc/iomem does not trigger the stack
trace until after a suspend-to-disk/resume cycle has occurred.
I am removing Ingo and Russell from the TO list (as they are apparently
the wrong people) and adding the suspend folks, as suspend is implicated.
My .config file
On Thu, 20 Dec 2007 08:38:03 -0500 Miles Lane [EMAIL PROTECTED] wrote:
On further investigation, cat /proc/iomem does not trigger the stack
trace until after a suspend-to-disk/resume cycle has occurred.
I still can't reproduce this.
Could you please try this?
- cat /proc/iomem
-
Resending... Curse GMail's HTML messages!
On Dec 21, 2007 12:58 AM, Miles Lane [EMAIL PROTECTED] wrote:
On Dec 20, 2007 12:32 PM, Andrew Morton [EMAIL PROTECTED] wrote:
On Thu, 20 Dec 2007 08:38:03 -0500 Miles Lane [EMAIL PROTECTED] wrote:
On further investigation, cat /proc/iomem does
On Fri, 21 Dec 2007 00:58:19 -0500 Miles Lane [EMAIL PROTECTED] wrote:
On Dec 20, 2007 12:32 PM, Andrew Morton [EMAIL PROTECTED] wrote:
On Thu, 20 Dec 2007 08:38:03 -0500 Miles Lane [EMAIL PROTECTED]
wrote:
On further investigation, cat /proc/iomem does not trigger the stack
trace
14 matches
Mail list logo