public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Nigel Cunningham <ncunningham@linuxmail.org>
To: Linus Torvalds <torvalds@osdl.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Linux v2.6.18-rc1
Date: Thu, 6 Jul 2006 22:44:40 +1000	[thread overview]
Message-ID: <200607062244.51814.ncunningham@linuxmail.org> (raw)
In-Reply-To: <Pine.LNX.4.64.0607052115210.12404@g5.osdl.org>

[-- Attachment #1: Type: text/plain, Size: 811 bytes --]

Hi.

On Thursday 06 July 2006 14:26, Linus Torvalds wrote:
> Ok,
>  the merge window for 2.6.18 is closed, and -rc1 is out there (git trees
> updated, the tar-ball and patches are still uploading over my pitiful DSL
> line - and as usual it may take a short while before mirroring takes
> place and distributes things across the globe).

On my amd64 based laptop, I had a failures with both suspend implementations 
(swsusp and suspend2) when I had iommu debugging on. The same config worked 
fine with 2.6.17. I guess something in the delta didn't like iommu usage 
being forced on a Turion. I'm not sure how much time I'll find for further 
debugging, so I'll report it now.

Regards,

Nigel
-- 
Nigel, Michelle and Alisdair Cunningham
5 Mitchell Street
Cobden 3266
Victoria, Australia

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

  parent reply	other threads:[~2006-07-06 12:44 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-06  4:26 Linux v2.6.18-rc1 Linus Torvalds
2006-07-06  9:44 ` Matt Keenan
2006-07-06 12:49   ` Jonathan Corbet
2006-07-06 16:22   ` Linus Torvalds
2006-07-06 12:34 ` Alistair John Strachan
2006-07-07  0:11   ` Andrew Morton
2006-07-06 12:44 ` Nigel Cunningham [this message]
2006-07-06 19:44 ` David R
2006-07-06 22:17   ` Greg KH
2006-07-07 21:11     ` David R
2006-07-08  8:14       ` Borislav Petkov
2006-07-08 14:19       ` Kay Sievers
2006-07-08 14:44         ` Andi Kleen
2006-07-08 14:44     ` Andi Kleen
2006-07-08 16:02       ` Greg KH
2006-07-09 23:17         ` Andi Kleen
2006-07-09 23:36           ` Greg KH
2006-07-07  1:05   ` Hervé Fache
2006-07-07 15:41 ` Steve Fox
2006-07-09 10:34   ` Benjamin Herrenschmidt
2006-07-10 13:21     ` Will Schmidt
2006-07-10 14:40       ` Alan Cox
2006-07-10 21:17         ` Benjamin Herrenschmidt
2006-07-11 17:00           ` Steve Fox
2006-07-10 21:16       ` Benjamin Herrenschmidt
2006-07-10 16:38     ` Steve Fox
2006-07-10 18:30       ` Steve Fox
2006-07-07 17:52 ` lost cpufreq (Re: Linux v2.6.18-rc1) Tomasz Torcz
2006-07-07 19:07   ` Dave Jones
2006-07-07 20:27     ` Tomasz Torcz
2006-07-07 20:35       ` Dave Jones
2006-07-10 10:03   ` Takashi Iwai
2006-07-08 14:09 ` [patchset 0/3 -2.6.18-rc1] pc8736x_gpio: fix re-modprobe errors Jim Cromie
2006-07-08 14:16   ` [patchset 1/3 -2.6.18-rc1] pc8736x_gpio: fix re-modprobe errors - define and use constants Jim Cromie
2006-07-08 14:29   ` [patchset 2/3 -2.6.18-rc1] pc8736x_gpio: fix re-modprobe errors - undo region reservation Jim Cromie
2006-07-08 14:34   ` [patchset 3/3 -2.6.18-rc1] pc8736x_gpio: fix re-modprobe errors - fix/finish cdev-init Jim Cromie
  -- strict thread matches above, loose matches on Subject: below --
2006-07-06 19:25 Linux v2.6.18-rc1 Moore, Robert

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=200607062244.51814.ncunningham@linuxmail.org \
    --to=ncunningham@linuxmail.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@osdl.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox