From: J M Cerqueira Esteves <jmce@artenumerica.com>
To: Andrew Morton <akpm@osdl.org>
Cc: linux-kernel@vger.kernel.org, support@artenumerica.com,
ngalamba@fc.ul.pt, axboe@suse.de,
"Randy.Dunlap" <rdunlap@xenotime.net>
Subject: Re: oom-killer: gfp_mask=0xd1 with 2.6.15.4 on EM64T [previously 2.6.12]
Date: Mon, 06 Mar 2006 10:45:46 +0000 [thread overview]
Message-ID: <440C12DA.6010302@artenumerica.com> (raw)
In-Reply-To: <20060306012854.581423ec.akpm@osdl.org>
[-- Attachment #1: Type: text/plain, Size: 1364 bytes --]
Andrew Morton wrote:
> I've not been following the saga of atapi-versus-libata at all closely.
> Booting with libata.atapi_enabled=1 might make things work. I think Randy
> should know what happened here?
>
> You were testing 2.6.16-rc5, yes? What did you expect to see and what were
> you seeing in earlier kernels (which versions?) (IOW: what did we break
> this time?)
Yes, this was with 2.6.16-rc5 with the suggested patch.
I haven't tried libata.atapi_enabled=1 yet (I'll do it on the first
reboot after this set of tests with Gaussian).
Under both 2.6.12 (as supplied with Ubuntu Breezy) and 2.6.15 (as
supplied with the current Ubuntu Dapper, incorporating 2.6.15.4) we had:
ata1: PATA max UDMA/100 cmd 0x1F0 ctl 0x3F6 bmdma 0x18F0 irq 14
ata1: dev 0 cfg 49:0f00 82:0218 83:4000 84:4000 85:0218 86:0000 87:4000
88:041f
ata1: dev 0 ATAPI, max UDMA/66
ata1: dev 0 configured for UDMA/33
scsi0 : ata_piix
isa bounce pool size: 16 pages
Vendor: ASUS Model: DRW-1608P2S Rev: 1.37
Type: CD-ROM ANSI SCSI revision: 05
But we didn't use the drive much until now (mostly just for Linux
installation, without CD reading problems) so I have no additional data
on possible issues with previous kernels...
Best regards
J Esteves
--
+351 939838775 Skype:jmcerqueira http://del.icio.us/jmce
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 256 bytes --]
next prev parent reply other threads:[~2006-03-06 10:45 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-01 17:01 oom-killer: gfp_mask=0xd1 with 2.6.12 on EM64T J M Cerqueira Esteves
2006-03-02 9:17 ` Andrew Morton
2006-03-03 15:50 ` J M Cerqueira Esteves
2006-03-04 15:57 ` oom-killer: gfp_mask=0xd1 with 2.6.15.4 on EM64T [previously 2.6.12] J M Cerqueira Esteves
2006-03-05 0:15 ` Andrew Morton
2006-03-05 2:55 ` J M Cerqueira Esteves
2006-03-05 10:07 ` J M Cerqueira Esteves
2006-03-06 8:47 ` J M Cerqueira Esteves
2006-03-06 9:02 ` Andrew Morton
2006-03-06 18:03 ` Jun'ichi Nomura
2006-03-17 9:47 ` J M Cerqueira Esteves
2006-03-06 9:19 ` J M Cerqueira Esteves
2006-03-06 9:28 ` Andrew Morton
2006-03-06 10:45 ` J M Cerqueira Esteves [this message]
2006-03-06 15:56 ` Randy.Dunlap
2006-03-05 0:12 ` oom-killer: gfp_mask=0xd1 with 2.6.12 on EM64T Andrew Morton
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=440C12DA.6010302@artenumerica.com \
--to=jmce@artenumerica.com \
--cc=akpm@osdl.org \
--cc=axboe@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=ngalamba@fc.ul.pt \
--cc=rdunlap@xenotime.net \
--cc=support@artenumerica.com \
/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