I continue to see freezes at random intervals on my Chromebook PIxel
(2013). The X UI freezes completely for anywhere from a fraction of a
second to several minutes but always eventually resumes. When it
resumes there's normally nothing in dmesg or any other logs and no
indication of exactly what e
Andrew Morton <[EMAIL PROTECTED]> writes:
> Greg Stark <[EMAIL PROTECTED]> wrote:
> >
> > Andrew Morton <[EMAIL PROTECTED]> writes:
> >
> > > Herbert tells me that this might be fixed in 2.6.11. Did you try that?
> >
> > Nope. I&#x
When you guys go on these "make needlessly global code static" kicks you
should maybe consider that even functions that aren't currently used by any
other area of the tree might be useful for module writers.
Instead of just checking which functions are currently used by other parts of
the kernel
Linus Torvalds <[EMAIL PROTECTED]> writes:
> And those occasional people are often not going to eb very good at
> reporting bugs. If they don't see anything happening, they'll just give up
> rather than bother to report it. So I do think we want the fairly verbose
> thing enabled by default. You
Andrew Morton <[EMAIL PROTECTED]> writes:
> Herbert tells me that this might be fixed in 2.6.11. Did you try that?
Nope. I'll try that.
(Though I'm skeptical. It went from 2.6.6 to 2.6.10 without being noticed but
now it's fixed without any reports?)
--
greg
-
To unsubscribe from this list
> Greg Stark <[EMAIL PROTECTED]> writes:
>
> > Andrew Morton <[EMAIL PROTECTED]> writes:
> >
> > > Are you able to narrow it down to something more fine grained than
> > > "between
> > > 2.6.6 and 2.6.9-rc1"?
> >
> &
Andrew Morton <[EMAIL PROTECTED]> writes:
> The 2.6.6 i810_audio.c compiles OK in current kernels with the below patch
> applied.
This would be a good time to learn the right way to do this: how do I build a
driver from a kernel tree without building the whole tree?
Like, if I copy the 2.6.6 d
Greg Stark <[EMAIL PROTECTED]> writes:
> Andrew Morton <[EMAIL PROTECTED]> writes:
>
> > Are you able to narrow it down to something more fine grained than "between
> > 2.6.6 and 2.6.9-rc1"?
>
> Er, I suppose I would have to build some more kernels.
Andrew Morton <[EMAIL PROTECTED]> writes:
> I would agree with that. If it's in the tree and the config system offers
> it, it should work. And if it _used_ to work, and no longer does so then
> double bad.
Er, yeah, it's not like this is a new card that some crufty old driver never
supported w
Alistair John Strachan <[EMAIL PROTECTED]> writes:
> The intel8x0 driver is probably one of the most widely used ALSA drivers, so
> I'd hope it wasn't broken!
I would have hoped so too at the time. Reporting it to the list didn't get any
response since it was already fixed upstream, but it took
Patrick McFarland <[EMAIL PROTECTED]> writes:
> On Saturday 12 March 2005 01:31 pm, Greg Stark wrote:
> > OSS Audio doesn't work properly for Quake3 in 2.6.10 but it worked in
> > 2.6.6. In fact I have the same problems in 2.6.9-rc1 so I assume 2.6.9 is
> > af
OSS Audio doesn't work properly for Quake3 in 2.6.10 but it worked in 2.6.6.
In fact I have the same problems in 2.6.9-rc1 so I assume 2.6.9 is affected as
well. This is with the Intel i810 drivers.
Quake3 just prints "dropping sound" over and over again and doesn't output any
sound in the actua
Jens Axboe <[EMAIL PROTECTED]> writes:
> > What about a non-journaled fs, or at least a meta-data-only-journaled fs?
> > Journaled FS's don't mix well with transaction based databases since they're
> > basically doing their own journaling anyways.
>
> Only works on ext3 and reiserfs currently.
D
Jens Axboe <[EMAIL PROTECTED]> writes:
> fsync has been working all along, since the initial barrier support for
> ide. only ext3 and reiserfs support it.
Really? That's huge news. Since what kernel version(s) is that?
What about a non-journaled fs, or at least a meta-data-only-journaled fs?
Jo
Jens Axboe <[EMAIL PROTECTED]> writes:
> For the longest time, only the old PATA drivers supported barrier writes
> with journalled file systems.
What about for fsync(2)? One of the most frequent sources of data loss on the
postgres mailing list has to do with users with IDE drives where fsync
William <[EMAIL PROTECTED]> writes:
> In my opinion, in order for linux to be trully user friendly, "a umount()
> should NEVER fail" (even if the device containing the filesystem is no
> longuer attached to the system). The kernel should do it's best to satisfy
> the umount request and cleanup.
16 matches
Mail list logo
