On 8/4/05, Con Kolivas <[email protected]> wrote:
> Ok perhaps on the resume side instead. When trying to resume can you try
> booting with 'dyntick=disable'. Note this isn't meant to be a long term fix
> but once we figure out where the problem is we should be able to code around
> it.
Sorry, no luck.
I tried dyntick=disable and dyntick=noapic on resume time. I also
tried suspend and resume after the system has been started with
dyntick=noapic: Same result.
As soon as I tell swsusp2 to discard its image, the system will come
up flawlessly.
Regards,
Jim
-
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]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
| |
 |