Pavel Machek wrote:
I assume it is in -rc6, too; it is long-standing bug and I am not
aware of any attempts at fixing it. Please file bug report, assign to
me.
I've filed it as Bug 5018.
Michal
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
Cal Peake wrote:
> On Fri, 5 Aug 2005, Andreas Steinmetz wrote:
>
>
>>AFAIK it works when agp is built into the kernel. You will get problems
>>when it is built as a module. In the module case you may want to try if
>>loading the module before resuming helps.
>
>
> Strange. I've had it built as
On Fri, 5 Aug 2005, Andreas Steinmetz wrote:
> AFAIK it works when agp is built into the kernel. You will get problems
> when it is built as a module. In the module case you may want to try if
> loading the module before resuming helps.
Strange. I've had it built as a module from day one and neve
Cal Peake wrote:
> On Thu, 4 Aug 2005, Andrew Morton wrote:
>
>
>>Michal Schmidt <[EMAIL PROTECTED]> wrote:
>>
>>>Does resuming from swsuspend work for anyone with amd64-agp loaded?
>>
>>It would seem not ;)
>
>
> Must have missed the OP. Yes I can resume fine from swsusp with amd64-agp.
>
> S
Hi!
> > Does resuming from swsuspend work for anyone with amd64-agp loaded?
>
> It would seem not ;)
>
> > On my system when I suspend with amd64-agp loaded, I get a spontaneous
> > reboot on resume. It reboots immediately after reading the saved image
> > from disk.
> > This is 100% reproduci
On Thu, 4 Aug 2005, Andrew Morton wrote:
> Michal Schmidt <[EMAIL PROTECTED]> wrote:
> >
> > Does resuming from swsuspend work for anyone with amd64-agp loaded?
>
> It would seem not ;)
Must have missed the OP. Yes I can resume fine from swsusp with amd64-agp.
System is an Averatec 3270 (Mobile
Michal Schmidt <[EMAIL PROTECTED]> wrote:
>
> Hello,
>
> Does resuming from swsuspend work for anyone with amd64-agp loaded?
It would seem not ;)
> On my system when I suspend with amd64-agp loaded, I get a spontaneous
> reboot on resume. It reboots immediately after reading the saved image
>
On Thursday, 21 of July 2005 17:24, Michal Schmidt wrote:
> Pavel Machek wrote:
> >>I'm trying to do something similar for x86_64. See the attached patch.
> >>Unfortunately, it doesn't help. The behaviour seems unchanged (resume
> >>still works iff amd64-agp wasn't loaded before suspend).
> >
> >
Pavel Machek wrote:
I'm trying to do something similar for x86_64. See the attached patch.
Unfortunately, it doesn't help. The behaviour seems unchanged (resume
still works iff amd64-agp wasn't loaded before suspend).
Are you sure problem is on level4_pgt? We probably use constant
level4_pgt
Hi!
> >Long time ago there were i386 problems because we assumed that kernel
> >is mapped in one big mapping and agp broke that assumption. Copying
> >pages backwards "fixed" it (and then we done proper fix). It should
> >not be, but it seems similar to this problem
>
> Do you mean this patch
Pavel Machek wrote:
Long time ago there were i386 problems because we assumed that kernel
is mapped in one big mapping and agp broke that assumption. Copying
pages backwards "fixed" it (and then we done proper fix). It should
not be, but it seems similar to this problem
Do you mean this pat
On Thursday, 21 of July 2005 03:25, Michal Schmidt wrote:
> Rafael J. Wysocki wrote:
> > On Thursday, 21 of July 2005 00:07, Michal Schmidt wrote:
> >>I also tried putting a printk before restore_processor_state(), but I'm
> >>not sure if it is safe to use printk there.
> >
> >
> > Yes, it is, b
Hi!
> >>I have rebuilt agpgart and amd64-agp into the kernel and now it has
> >>resumed successfully for the first time. Thank you for the hint!
> >>
> >>But I still wonder, why that makes a difference.
> >
> >
> >Before resume the module is not present. When it gets loaded from the
> >image it
Rafael J. Wysocki wrote:
On Thursday, 21 of July 2005 00:07, Michal Schmidt wrote:
I also tried putting a printk before restore_processor_state(), but I'm
not sure if it is safe to use printk there.
Yes, it is, but you may be unable to see the message if the box reboots before
it can be displ
On Thursday, 21 of July 2005 00:07, Michal Schmidt wrote:
> Rafael J. Wysocki wrote:
> > On Tuesday, 19 of July 2005 23:26, Michal Schmidt wrote:
> >>I have rebuilt agpgart and amd64-agp into the kernel and now it has
> >>resumed successfully for the first time. Thank you for the hint!
> >>
> >>Bu
Rafael J. Wysocki wrote:
On Tuesday, 19 of July 2005 23:26, Michal Schmidt wrote:
I have rebuilt agpgart and amd64-agp into the kernel and now it has
resumed successfully for the first time. Thank you for the hint!
But I still wonder, why that makes a difference.
Before resume the module is
Hi,
On Tuesday, 19 of July 2005 23:26, Michal Schmidt wrote:
> Andreas Steinmetz wrote:
> > Michal Schmidt wrote:
> >>Does resuming from swsuspend work for anyone with amd64-agp loaded?
> >>
> >>On my system when I suspend with amd64-agp loaded, I get a spontaneous
> >>reboot on resume. It reboots
Andreas Steinmetz wrote:
Michal Schmidt wrote:
Does resuming from swsuspend work for anyone with amd64-agp loaded?
On my system when I suspend with amd64-agp loaded, I get a spontaneous
reboot on resume. It reboots immediately after reading the saved image
from disk.
This is 100% reproducible.
Michal Schmidt wrote:
> Hello,
>
> Does resuming from swsuspend work for anyone with amd64-agp loaded?
>
> On my system when I suspend with amd64-agp loaded, I get a spontaneous
> reboot on resume. It reboots immediately after reading the saved image
> from disk.
> This is 100% reproducible.
>
>
19 matches
Mail list logo
