Re: current git breaks resume

On Friday 09 February 2007 14:03, Jens Axboe wrote:
> Hi,
> 
> Unfortunately I'm a little short on time as I'll be travelling tomorrow,
> but of course preparing a new kernel for the laptop is something you
> want to do right before leaving. So I discovered that the current (well
> as of yesterday, HEAD is 5986a2ec35836a878350c54af4bd91b1de6abc59)
> doesn't resume on my x60. 2.6.20 works fine, so something broke since
> then.

resume from RAM, or resume from disk?

-
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/

Follow-Ups:
- Re: current git breaks resume
  - From: Jens Axboe <[email protected]>
- Re: current git breaks resume
  - From: Alexey Starikovskiy <[email protected]>

References:
- current git breaks resume
  - From: Jens Axboe <[email protected]>

Prev by Date: Re: -mm merge plans for 2.6.21
Next by Date: Re: [PATCH] iomap: make PCI iomap stuff excluded when PCI isn't configured
Previous by thread: Re: current git breaks resume
Next by thread: Re: current git breaks resume
Index(es):
- Date
- Thread

[Index of Archives] [Kernel Newbies] [Netfilter] [Bugtraq] [Photo] [Stuff] [Gimp] [Yosemite News] [MIPS Linux] [ARM Linux] [Linux Security] [Linux RAID] [Video 4 Linux] [Linux for the blind] [Linux Resources]