On Mon, 2010-11-29 at 02:52 +, Ben Hutchings wrote:
On Sun, 2010-11-28 at 18:12 +, Ian Campbell wrote:
On Sun, 2010-11-28 at 16:58 +, Ben Hutchings wrote:
On Tue, 2010-11-23 at 12:56 +0100, Lionel Elie Mamane wrote:
On Tue, Nov 23, 2010 at 10:41:57AM +0100, Alexander Kurtz
Hi,
after a system upgrade to the current state of Debian Testing - which
included an upgrade
of the linux-image-2.6.32-5-amd64 package to the version 2.6.32.28 - a
kernel failure occured.
The failure message has been sent to kerneloops.com and is also shown below.
Don't know if this has to
Moin Bjørn,
On Tue, 23 Nov 2010 15:25:44 +0100, Bjørn Mork bj...@mork.no wrote:
Please see if this is fixed by the patch I recently posted to the
linux-scsi list: http://permalink.gmane.org/gmane.linux.ide/47847
I believe you are seeing another symptom of the same bug: The driver
happily
I found a possible solution here:
http://forums.debian.net/viewtopic.php?f=17t=54715
I do not know if it is a good solution, but I thought to report it to
you.
Ciao and thank you very much,
Domenico
--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of
On Mon, Nov 29, 2010 at 12:50:09AM -0600, Jonathan Nieder wrote:
The sync_file_range call has been available since Linux 2.6.17.
On non-Linux systems we can skip it.
It still should check for ENOSYS instead of bailing out.
Bastian
--
No problem is insoluble.
-- Dr. Janet
Marc-Christian Petersen m@gmx.de writes:
On Tue, 23 Nov 2010 15:25:44 +0100, Bjørn Mork bj...@mork.no wrote:
Please see if this is fixed by the patch I recently posted to the
linux-scsi list: http://permalink.gmane.org/gmane.linux.ide/47847
I believe you are seeing another symptom of
On Mon, 2010-11-29 at 11:04 +0100, hu...@online.de wrote:
Hi,
after a system upgrade to the current state of Debian Testing - which
included an upgrade
of the linux-image-2.6.32-5-amd64 package to the version 2.6.32.28 - a
kernel failure occured.
The failure message has been sent to
Moin Bjørn,
On Mon, 29 Nov 2010 11:55:01 +0100, Bjørn Mork bj...@mork.no wrote:
Does the selftest actually work? Artem Bokhan reports that the patch
fixes the visible error, but that the selftest does not start. I really
don't understand why, as AFAICS the patch does not change or modify
On Sun, 2010-11-28 at 20:14 +, Ben Hutchings wrote:
[0.856002] Pid: 2, comm: kthreadd Not tainted 2.6.32-5-amd64 #1
W1100z/2100z
What's in that kernel? is that simply the latest .32-stable?
[0.536554] CPU0 attaching sched-domain:
[0.540004] domain 0: span 0-1 level MC
[
On Mon, 29 Nov 2010, Jonathan Nieder wrote:
Guillem Jover wrote:
Hmm, ok so what about posix_fadvise(fd, 0, 0, POSIX_FADV_DONTNEED)
instead, skimming over the kernel source seems to indicate it might
end up doing more or less the same thing but in a portable way?
Probably a silly
On Nov 29, 2010, at 1:48 AM, Jonathan Nieder wrote:
Results (on ext4) suggest that patches 1 and 4 matter and the rest are
within noise. Timings are rough; sometimes replicates vary by as much
as a second. Numbers are cold cache (i.e., after running sync and
echo 3.../drop_caches), best
Olaf van der Spek writes (Re: Bug#605009: serious performance regression with
ext4):
On Fri, Nov 26, 2010 at 10:52 PM, Ted Ts'o ty...@mit.edu wrote:
I am guessing you are doing (a) today --- am I right? =C2=A0(c) or (d)
would be best.
Are there any plans to provide an API for atomic
On Mon, 29 Nov 2010, Theodore Tso wrote:
BTW, if you had opened the file handle in subsequent passes using
O_RDONLY|O_NOATIME, the use of fdatasync() instead of fsync() might not
have been necessary. And as far as the comments in patch #4 was
Hum, fsync()/fdatasync() require a fd opened for
On Mon, Nov 29, 2010 at 01:22:25PM +, Ian Jackson wrote:
Olaf van der Spek writes (Re: Bug#605009: serious performance regression
with ext4):
Are there any plans to provide an API for atomic (non-durable) file
updates, not involving fsync?
Yes. Such an API has already been defined by
On Mon, 2010-11-29 at 12:50 +0100, Peter Zijlstra wrote:
On Sun, 2010-11-28 at 20:14 +, Ben Hutchings wrote:
[0.856002] Pid: 2, comm: kthreadd Not tainted 2.6.32-5-amd64 #1
W1100z/2100z
What's in that kernel? is that simply the latest .32-stable?
It was the latest stable .32
On 29.11.2010 07:18, Guillem Jover wrote:
Could someone with ext4/btrfs/xfs/etc test w/ and w/o the attached patch
against dpkg?
I'm using ext4 (as already mentioned), my small benchmark is (re)installing
vim-runtime using dpkg -i
1.15.8.5:
real0m9.259s
user0m4.212s
sys 0m0.752s
On Mon, Nov 29, 2010 at 02:46:11PM +0100, Raphael Hertzog wrote:
On Mon, 29 Nov 2010, Theodore Tso wrote:
BTW, if you had opened the file handle in subsequent passes using
O_RDONLY|O_NOATIME, the use of fdatasync() instead of fsync() might not
have been necessary. And as far as the
On Mon, Nov 29, 2010 at 02:16:02PM +0100, Raphael Hertzog wrote:
It means we don't need to keep it in RAM since we're not going to
read/modifiy it again in the near future. Thus the writeback can be
started right now since delaying it will not save us anything.
At least that's the way I
On Mon, Nov 29, 2010 at 2:22 PM, Ian Jackson
ijack...@chiark.greenend.org.uk wrote:
Olaf van der Spek writes (Re: Bug#605009: serious performance regression
with ext4):
Are there any plans to provide an API for atomic (non-durable) file
updates, not involving fsync?
Yes. Such an API has
On Mon, Nov 29, 2010 at 2:56 PM, Bastian Blank wa...@debian.org wrote:
Again: Please quote the standard instead of crying. Your view of things
disallows many of the recent improvements in filesystems, so you have to
show evidence. All the databases and other reliable data handing tools
uses
Theodore Tso wrote:
So Patch #2 wasn't quite what I talked about doing; patch #2 is adding
SYNC_FILE_RANGE_WAIT_BEFORE for each file immediately after writing the file.
So it's the equivalent of:
extract(a)
sync_file_range(SYNC_FILE_RANGE_WRITE)
Olaf van der Spek writes (Re: Bug#605009: serious performance regression with
ext4):
Probably not an issue for dpkg, but in general:
Don't you reset meta-data that way?
Yes. If you want to keep the metadata you must copy it.
Require a second file (name), permission to write to it and assume
On Mon, Nov 29, 2010 at 3:58 PM, Ian Jackson
ijack...@chiark.greenend.org.uk wrote:
Olaf van der Spek writes (Re: Bug#605009: serious performance regression
with ext4):
Probably not an issue for dpkg, but in general:
Don't you reset meta-data that way?
Yes. If you want to keep the metadata
Ted Ts'o wrote:
On Mon, Nov 29, 2010 at 02:16:02PM +0100, Raphael Hertzog wrote:
It means we don't need to keep it in RAM since we're not going to
read/modifiy it again in the near future. Thus the writeback can be
started right now since delaying it will not save us anything.
At least
On Mon, Nov 29, 2010 at 02:58:16PM +, Ian Jackson wrote:
This is the standard way that ordinary files for which reliability was
important have been updated on Unix for decades. fsync is for files
which need synchronisation with things external to the computer (or at
least, external to
On Mon, Nov 29, 2010 at 4:18 PM, Ted Ts'o ty...@mit.edu wrote:
Lots of users have complained about the desktop performance problem,
but the reality is we can't really solve that without also taking away
the magic that made (c) happen. Whether you solve it by using
data=writeback and stick
Package: linux-2.6
Version: 2.6.32-28
Severity: important
dmesg becomes completely filled with this message with only a couple of hours
uptime, the messages start to appear immediately after boot, sometimes whilst
booting.
If booting to a command prompt, the messages just keep filling up the
On Mon, Nov 29, 2010 at 09:21:44AM -0600, Jonathan Nieder wrote:
That explanation helps a lot. Thanks, both. (Guillem, I like your
patch very much then. Most files being unpacked in a dpkg run aren't
going to be read back again soon. Perhaps some other kernels will
also interpret it as a
On Mon, Nov 29, 2010 at 10:32:44AM -0500, Ted Ts'o wrote:
Most files won't, but consider a postinstall script which needs to
scan/index a documentation file, or simply run one or more binaries
that was just installed. I can definitely imagine situations where
using POSIX_FADV_DONTNEED could
Ted Ts'o wrote:
Most files won't, but consider a postinstall script which needs to
scan/index a documentation file, or simply run one or more binaries
that was just installed. I can definitely imagine situations where
using POSIX_FADV_DONTNEED could actually hurt performance.
Hmm. Maybe
On Mon, Nov 29, 2010 at 12:50:25PM +0100, Peter Zijlstra wrote:
On Sun, 2010-11-28 at 20:14 +, Ben Hutchings wrote:
[0.856002] Pid: 2, comm: kthreadd Not tainted 2.6.32-5-amd64 #1
W1100z/2100z
What's in that kernel? is that simply the latest .32-stable?
No, we have quite a few
.. snip of back-history..
Thanks for the pointers.
I agree with Bastian that some of these changes are really quite nasty.
Do you and other Xen developers have any plan for how to fix the GART
and TTM mapping problems in a cleaner way as Xen dom0 support goes
upstream?
I know that
Processing commands for cont...@bugs.debian.org:
found 423562 2.6.32-28
Bug #423562 [linux-2.6] linux-image-2.6-ixp4xx: XFS-filesystem crashes
There is no source info for the package 'linux-2.6' at version '2.6.32-28' with
architecture ''
Unable to make a source version for version '2.6.32-28'
Devin, did you report this issue upstream?
Since you have the hardware, it makes sense to work with upstream
directly.
If you're not interested in reporting it upstream, I'll close this bug
report. (Note that this is my 3rd ping.)
* Martin Michlmayr t...@cyrius.com [2010-02-22 21:49]:
* Devin
Processing commands for cont...@bugs.debian.org:
reassign 590105 linux-2.6
Bug #590105 [sata-modules-2.6.32-5-orion5x-di] SATA drive not detected during
squeeze installation on Buffalo LinkStation (squeeze)
Bug reassigned from package 'sata-modules-2.6.32-5-orion5x-di' to 'linux-2.6'.
Bug No
Sébastien,
You have a LS-CHL, right? The LS-CHL is currently not supported by
the kernel. The logs show that you're booting the kernel for
Linkstation Pro/Live and I suspect that doesn't properly work on the
LS-CHL.
ARM Orion: added Buffalo LS-CHL support
FWIW, Arnaud Patard tried to reproduce this issue on QEMU (with 128
MB) and a SheevaPlug but couldn't.
Robert, can you send the boot log when booting Debian on your device?
--
Martin Michlmayr
http://www.cyrius.com/
--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a
* Sebastian Reichel elektra...@gmail.com [2010-11-23 09:42]:
The config does not disable the support for other OMAP devices. It
should support most of the OMAP devices available (but they
probably need some more drivers). The only limitation is, that
it must use an OMAP2 processor or later
Your message dated Mon, 29 Nov 2010 18:55:07 +
with message-id 20101129185507.gi7...@jirafa.cyrius.com
and subject line Re: Bug#567098: linux-image-2.6.26-2-ixp4xx: adm8511/pegasus
usb ethernet device loses mac on nslu2 when cold-plugged
has caused the Debian Bug report #567098,
regarding
(Dropping bug report)
On Mon, 29 Nov 2010, Olaf van der Spek wrote:
Hence the fact that all file system developers, whether they were
btrfs developers or XFS developers or ext4 developers, made the joke
at the file system developers summit two years ago, that what the
application
* Ben Hutchings b...@decadent.org.uk wrote:
On Mon, Nov 29, 2010 at 12:50:25PM +0100, Peter Zijlstra wrote:
On Sun, 2010-11-28 at 20:14 +, Ben Hutchings wrote:
[0.856002] Pid: 2, comm: kthreadd Not tainted 2.6.32-5-amd64 #1
W1100z/2100z
What's in that kernel? is that
* Adrian von Bidder avbid...@fortytwo.ch [2009-12-11 10:44]:
Trying to build my 2.6.32 for my QNAP (as documented in README.Debian)
fails because the config is not generated:
IOError: [Errno 2] No such file or directory:
'debian/build/config.armel_none_kirkwood'
make[1]: ***
On Mon, Nov 29, 2010 at 8:23 PM, Raphael Hertzog hert...@debian.org wrote:
(Dropping bug report)
On Mon, 29 Nov 2010, Olaf van der Spek wrote:
Hence the fact that all file system developers, whether they were
btrfs developers or XFS developers or ext4 developers, made the joke
at the file
Hi!
I have just installed Debian 6 and Xen, and i cant use Xserver (nvidia) in
my Dom0 2.6.32-5-xen-686 . So i cant use this pc for personal user , just
for servers =(
Is the same bug? Can i use another kernel? Which one?
Thank you.
On Mon, Nov 29, 2010 at 06:17:59PM +, Martin Michlmayr wrote:
* Sebastian Reichel elektra...@gmail.com [2010-11-23 09:42]:
The config does not disable the support for other OMAP devices. It
should support most of the OMAP devices available (but they
probably need some more drivers). The
Nice to know ! Hope this patch will be accepted soon :)
2010/11/29 Martin Michlmayr t...@cyrius.com
Sébastien,
You have a LS-CHL, right? The LS-CHL is currently not supported by
the kernel. The logs show that you're booting the kernel for
Linkstation Pro/Live and I suspect that doesn't
On Tue, Nov 02, 2010 at 09:43:13AM -0600, dann frazier wrote:
Maks I discussed this on IRC and drafted the following text which we
believe is ready for inclusion:
(...)
Thanks for the information, I have included it in the Release Notes:
On Mon, 2010-11-29 at 20:01 -0200, Jorge Eduardo Birck wrote:
Hi!
I have just installed Debian 6 and Xen, and i cant use Xserver
(nvidia) in my Dom0 2.6.32-5-xen-686 . So i cant use this pc for
personal user , just for servers =(
Is the same bug? Can i use another kernel? Which one?
On 29.11.2010 14:41, Michael Biebl wrote:
I'm using ext4 (as already mentioned), my small benchmark is (re)installing
vim-runtime using dpkg -i
1.15.8.5:
real0m9.259s
user0m4.212s
sys 0m0.752s
1.15.8.6:
real0m41.766s
user0m4.248s
sys 0m1.028s
1.15.8.6
On Tue, 30 Nov 2010 00:33:34 +0100
Francois Romieu rom...@fr.zoreil.com wrote:
hayeswang hayesw...@realtek.com :
Excuse me, I have some questions about the firmware patch.
1. I should convert the data into the binary files (.bin). Is it right?
You may do it.
Fwiw I have cooked
Sorry, strike the info I gave earlier, I got confused.
The express cards I tried earlier were both dual port cards, it's just
that one was xpress54 and one 34, they both have the same id. and both
exhibit the same problem I guess because they are basically the same card.
The single port card
Package: linux-image-2.6.32-5-xen-amd64
Version: 2.6.32-28
Severity: normal
If Xen dom0 or domU kernel shuts down for halt or reboot it just sits
there trying to issue hw reboot/halt.
likely https://lkml.org/lkml/2010/11/26/197
-- System Information:
Debian Release: squeeze/sid
Architecture:
Notes:
Mapping stable-security to proposed-updates.
Accepted:
linux-2.6_2.6.26-26lenny1.diff.gz
to main/l/linux-2.6/linux-2.6_2.6.26-26lenny1.diff.gz
linux-2.6_2.6.26-26lenny1.dsc
to main/l/linux-2.6/linux-2.6_2.6.26-26lenny1.dsc
linux-doc-2.6.26_2.6.26-26lenny1_all.deb
to
Notes:
Mapping stable-security to proposed-updates.
Accepted:
linux-headers-2.6.26-2-all-hppa_2.6.26-26lenny1_hppa.deb
to main/l/linux-2.6/linux-headers-2.6.26-2-all-hppa_2.6.26-26lenny1_hppa.deb
linux-headers-2.6.26-2-all_2.6.26-26lenny1_hppa.deb
to
Package: linux-2.6
Version: 2.6.32-28
Severity: normal
Tags: patch
Hi,
Current Linux-2.6 package does not work multitouch device of Macbookpro 7,1.
This is because driver does not support a multitouch protocol of Macbookpro.
The patch revising this problem is already taken in by upstream.
Richard Mittendorfer del...@gmx.net writes:
Version: 2.6.32-28
likely https://lkml.org/lkml/2010/11/26/197
Does this mean that you tested 2.6.32-27 and that works?
--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact
Hi Romieu,
Let me explain that not all of the phy settings are the ram code (or firmware).
Some of them are the initialization sequence. Only the Low pass filter
DLY_CAP fine tune from uC is the firmware. And there is no firmware before
RTL8111D. That is, except 8111DP, the chips which have
Hi,
On Tue, 30 Nov 2010, Michael Biebl wrote:
Something interesting I noticed:
I created the ext4 file system on a spare partition and installed a chroot.
After running the test, I exited the chroot, immediately unmounted the
partition
and measured how long it took:
1.15.8.5: 0.4s
58 matches
Mail list logo
