public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Pedro Venda <pjlv-aHmAgkVUFT6Joy8PIJZ9VA@public.gmane.org>
To: acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: CUR-DLS blacklisted? + IRQ trouble
Date: Wed, 18 Feb 2004 19:58:55 +0000	[thread overview]
Message-ID: <4033C3FF.3040809@mega.ist.utl.pt> (raw)
In-Reply-To: <1077079669.4948.24.camel-D2Zvc0uNKG8@public.gmane.org>

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

hi len,

thanks for the reply. i'll file the bug report and say something in this
ml when i do.

thanks again.
regards,
pedro.

Len Brown wrote:

 > Pedro,
 > We got that entry from UnitedLinux last August.
 >
 > It is quite possible that the system is unjustly blacklisted, or that it
 > was blacklisted out of convenience b/c nobody could figure out exactly
 > what was wrong when ACPI on that system failed.
 >
 > I'll be happy to look into it if you're willing to file a bug and help
 > me debug to make a proper diagnosis.
 >
 > thanks,
 > -Len
 > ---
 > How to file a bug against ACPI:
 >
 > http://bugzilla.kernel.org/ Category: Power Management, Component: ACPI
 >
 > Please attach dmesg -s40000 output (or serial console log if dmesg
 > unavailable)
 > Please attach copy of /proc/interrupts if possible
 >
 > Please attach the output from acpidmp, available in /usr/sbin/, or in
 > pmtools:
 > http://ftp.kernel.org/pub/linux/kernel/people/lenb/acpi/utils/
 >
 > Please attach the output from dmidecode, available in /usr/sbin/, or
 > here:
 > http://ftp.kernel.org/pub/linux/kernel/people/lenb/acpi/utils/
 >
 > Please attach the output from lspci -v
 >
 >
 >
 > On Sun, 2004-02-15 at 09:29, Pedro Venda wrote:
 >
> hi everyone,
> 
> i have two questions to which i haven't found answers anywhere, so i am
> asking here.
> 
> - i have an ASUS CUR-DLS motherboard (dual P3) and the 2.4 and 2.6
> kernels both say: "ASUS CUR-DLS detected: force use of acpi=ht" when
> starting disabling ACPI. i must do a acpi=force in order to be able to
> use it, which consequences i don't know. i looked through the acpi
> documentation and this board is NOT on the blacklist. i am asking why
> does the kernel disable ACPI on my mb by default? what's wrong with it?
> are there any known problems?
> 
> - on the same machine, i have 2 nics. one of them is onboard (intel
> eepro/100) and the other is a realtek 8139. they used to work ok with
> some versions of the kernel, but now they only work together without
> ACPI. with acpi, the realtek displays the famous SIOCIFADDR "device is
> busy...". is this normal? what can be happening here?
> 
> thanks for your time.
> regards,
> pedro.

-------------------------------------------------------
SF.Net is sponsored by: Speed Start Your Linux Apps Now.
Build and deploy apps & Web services for Linux with
a free DVD software kit from IBM. Click Now!
http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click
_______________________________________________
Acpi-devel mailing list
Acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
https://lists.sourceforge.net/lists/listinfo/acpi-devel




 > -------------------------------------------------------
 > SF.Net is sponsored by: Speed Start Your Linux Apps Now.
 > Build and deploy apps & Web services for Linux with
 > a free DVD software kit from IBM. Click Now!
 > http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click
 > _______________________________________________
 > Acpi-devel mailing list
 > Acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
 > https://lists.sourceforge.net/lists/listinfo/acpi-devel


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 254 bytes --]

  parent reply	other threads:[~2004-02-18 19:58 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-15 14:29 CUR-DLS blacklisted? + IRQ trouble Pedro Venda
     [not found] ` <402F823D.6070702-aHmAgkVUFT6Joy8PIJZ9VA@public.gmane.org>
2004-02-18  4:47   ` Len Brown
     [not found]     ` <1077079669.4948.24.camel-D2Zvc0uNKG8@public.gmane.org>
2004-02-18 19:58       ` Pedro Venda [this message]
2004-02-22 23:08       ` Pedro Venda
     [not found]         ` <4039365B.6090105-aHmAgkVUFT6Joy8PIJZ9VA@public.gmane.org>
2004-02-23 19:24           ` Randy.Dunlap
     [not found]             ` <20040223112406.116f381e.rddunlap-3NddpPZAyC0@public.gmane.org>
2004-02-24  1:40               ` Pedro Venda
     [not found]                 ` <403AAB98.4050508-aHmAgkVUFT6Joy8PIJZ9VA@public.gmane.org>
2004-02-24 11:21                   ` Stefan Seyfried

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=4033C3FF.3040809@mega.ist.utl.pt \
    --to=pjlv-ahmagkvuft6joy8pijz9va@public.gmane.org \
    --cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.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