[lkml]   [2005]   [Aug]   [22]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: rc5 seemed to kill a disk that rc4-mm1 likes. Also some X trouble.
On Mon, 2005-08-22 at 10:44 -0700, Linus Torvalds wrote:
> On Mon, 22 Aug 2005, Rolf Eike Beer wrote:
> > >It's a PII-350 with more or less SuSE 9.3. The machine has no net access, so
> > > I can only try to narrow it down to one rc at the weekend.
> >
> > 2.6.12 works fine, everything since 2.6.13-rc1 breaks it.
> Gaah. I don't see anything really obvious in that range. However, I notice
> that pci_mmap_resource() (in drivers/pci/pci-sysfs.c) now has
> + if (i >= PCI_ROM_RESOURCE)
> + return -ENODEV;
> which seems a big bogus. Why wouldn't we allow the ROM resource to be
> mapped? I could imagine that the X server would very much like to mmap it,
> although I don't know if modern X actually does that. The fact that it
> works when root runs the X server and causes problems for normal users
> does seem like there's something that root can do that users can't do, and
> doing a mmap() on /dev/mem might be just that.
> Eike, maybe you could change the ">=" to just ">" instead?
> PS. The patch that introduced this was billed as "no change for anything
> but ppc". Tssk.

X uses /dev/mem, it doesn't use sysfs nor proc on x86, though it does
use proc for config space access (and that only) on ppc. Do you have the
sha1 ID of the above change at hand btw ?

(And yes, X should/will be fixed)

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

 \ /
  Last update: 2005-08-22 23:04    [W:0.121 / U:0.424 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site