From: CarlosRomero <caberome@bellsouth.net>
To: linux-kernel@vger.kernel.org
Subject: Re: simple pnp bios io resources bug makes system unusable
Date: Tue, 01 Jul 2003 01:54:10 -0400 [thread overview]
Message-ID: <3F012202.4010303@bellsouth.net> (raw)
my one line patch just skips an io registration with a simple sanity check.
never once have i heard a device with an ioport of 0x0.
question is why it happens and only once.
tested with
ISA Plug and Play:
U.S. Robotics Sportster 33600 FAX/Voice Int
Creative ViBRA16C PnP
Crystal Codec
Host/PCI Bridge:
VIA Technologies, In VT82C585VP [Apollo V
VIA Technologies, In VT82C586/A/B PCI-to-
VIA Technologies, In VT82C586/B/686A/B PI
VIA Technologies, In USB
VIA Technologies, In VT82C586B ACPI
(also noticing cutoff in /sys/devices/pci0/*/name)
>Yes, I also ran into this problem, Adam is was also working on a fix
>although I wonder if it's the same fix?
>Shawn S.
>>List: linux-kernel
>>Subject: simple pnp bios io resources bug makes system unusable
>>From: CarlosRomero <caberome () bellsouth ! net>
>>Date: 2003-07-01 3:38:17
>>cat /sys/devices/pnp0/00\:0c/name
>>Reserved Motherboard Resources
>>cat /sys/devices/pnp0/00\:0c/resources
>>state = active
>>io 0x4d0-0x4d1
>>io 0xcf8-0xcff
>>io 0x3f7-0x3f7
>>io 0x401-0x407
>>io 0x298-0x298
>>io 0x00000000-0xffffffff
>>mem 0xfffe0000-0xffffffff
>>mem 0x100000-0x7ffffff
>>fixup: check for null io base, other devices are now able to initialize.
next reply other threads:[~2003-07-01 8:30 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-01 5:54 CarlosRomero [this message]
2003-07-01 22:37 ` simple pnp bios io resources bug makes system unusable Adam Belay
-- strict thread matches above, loose matches on Subject: below --
2003-07-01 21:33 Shawn Starr
2003-07-01 7:30 Shawn Starr
2003-07-01 3:38 CarlosRomero
2003-07-01 22:30 ` Adam Belay
2003-07-02 17:20 ` Linus Torvalds
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=3F012202.4010303@bellsouth.net \
--to=caberome@bellsouth.net \
--cc=linux-kernel@vger.kernel.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