All of lore.kernel.org
 help / color / mirror / Atom feed
From: Didier Moens <moensd@xs4all.be>
To: Nicolas Aspert <Nicolas.Aspert@epfl.ch>
Cc: Marcelo Tosatti <marcelo@conectiva.com.br>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH]Re: OOPS in APM 2.4.18-pre4 with i830MP agpgart
Date: Sat, 19 Jan 2002 22:50:57 +0100	[thread overview]
Message-ID: <3C49EA41.6010105@xs4all.be> (raw)
In-Reply-To: <3C487E68.1000404@xs4all.be> <3C4931DA.5020703@epfl.ch>

Nicolas Aspert wrote:

> Didier Moens wrote:
>
>> Dear all,
>>
>> On november 27th, Nicolas Aspert was so kind as to post a 
>> modification to agpgart, which catters for detection of the Intel 
>> i830MP.
>>
>> The patch was included in 2.4.18-pre2.
>>
>> Unfortunately, loading agpgart yields an oops when APM ("apm -s") is 
>> invoked, both in terminal and in X. APM functions perfectly when 
>> agpgart is absent.
>>
>>
>>
>
> Hello all
>
> Here is a patch that fixes the APM/suspend/resume issues in agpgart 
> (for 820 and 830MP chipsets).
> The patch is against 2.4.18-pre4
>
> Have a nice week-end. 


Patch functions OK for me (patch applied to 2.4.18-pre4) : I can enter 
and resume from APM with agpgart loaded.



Unfortunately, since moving from RedHat Rawhide 2.4.16-0.9 to vanilla 
2.4.18-pre4, I'm regularly confronted with the "ide_dmaproc : chipset 
supported ide_dma_lostirq func only : 13"-error when resuming from APM 
(see lkml-thread "DMA woes", 2001-12-07, with interventions from Andre 
Hedrick), but I verified this is unrelated to the presence of the 
agpgart module.


Sincerely,

Didier




      reply	other threads:[~2002-01-19 20:51 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-01-18 19:58 OOPS in APM 2.4.18-pre4 with i830MP agpgart Didier Moens
2002-01-18 20:25 ` Alan Cox
2002-01-18 20:25   ` Nicolas Aspert
2002-01-18 20:28   ` Dave Jones
2002-01-18 20:40     ` Didier Moens
2002-01-18 20:39 ` Nicolas Aspert
2002-01-19  8:44 ` [PATCH]Re: " Nicolas Aspert
2002-01-19 21:50   ` Didier Moens [this message]

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=3C49EA41.6010105@xs4all.be \
    --to=moensd@xs4all.be \
    --cc=Nicolas.Aspert@epfl.ch \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marcelo@conectiva.com.br \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.