On 18/07/12 10:55, Tom Gundersen wrote:
> Linus,
>
>> The point I'm slowly getting to is that I would actually love to have
>> *distro* Kconfig-files, where the distribution would be able to say
>> "These are the minimums I *require* to work". So we'd have a "Distro"
>> submenu, where you could pi
Michael Tokarev wrote:
> Justin Piszcz wrote:
>> On Sun, 4 Nov 2007, Michael Tokarev wrote:
> []
>>> The next time you come across something like that, do a SysRq-T dump and
>>> post that. It shows a stack trace of all processes - and in particular,
>>> where exactly each task is stuck.
>
>> Yes
[EMAIL PROTECTED] wrote:
Would this just be relevant to network devices or would it improve
support for jostled usb and sata hot-plugging I wonder?
good question, I suspect that some of the error handling would be
similar (for devices that are unreachable not haning the system for
example), b
[EMAIL PROTECTED] wrote:
per the message below MD (or DM) would need to be modified to work
reasonably well with one of the disk components being over an unreliable
link (like a network link)
are the MD/DM maintainers interested in extending their code in this
direction? or would they prefer
Paul Clements wrote:
Well, if people would like to see a timeout option, I actually coded up
a patch a couple of years ago to do just that, but I never got it into
mainline because you can do almost as well by doing a check at
user-level (I basically ping the nbd connection periodically and if
James wrote:
I don't know the original order of the array before all the problems
started.
Is there a way to determine the original order?
No, unless you have some old kernel logs of the last time it assembled
the array properly.
The one thing that "--create" does destroy is the information ab
Bruce Allen wrote:
Hi David,
http://www.mail-archive.com/linux-kernel@vger.kernel.org/msg164863.html
This is mine and although it's a 'real' problem, it is something
that's easy to hack around by having the suspend script turn on smart
after it is resumed. (Of course I can't use resume unti
Hi Bruce
From some of the earlier threads that I missed (below) I have the
impression that the problem may be a very simple one, namely that
starting with 2.6.22 one needs to run a command to enable SMART when a
box is first booted -- the kernel no longer does this as part of the
init/setup of
Rafael J. Wysocki wrote:
On Monday, 2 July 2007 16:32, David Greaves wrote:
Rafael J. Wysocki wrote:
On Monday, 2 July 2007 12:56, Tejun Heo wrote:
David Greaves wrote:
Tejun Heo wrote:
It's really weird tho. The PHY RDY status changed events are coming
from the device which is NOT
Rafael J. Wysocki wrote:
On Monday, 2 July 2007 12:56, Tejun Heo wrote:
David Greaves wrote:
Tejun Heo wrote:
It's really weird tho. The PHY RDY status changed events are coming
from the device which is NOT used while resuming
There is an obvious problem there though Tejun (the errors
Rafael J. Wysocki wrote:
On Friday, 29 June 2007 09:54, David Greaves wrote:
David Chinner wrote:
On Fri, Jun 29, 2007 at 08:40:00AM +0100, David Greaves wrote:
What happens if a filesystem is frozen and I hibernate?
Will it be thawed when I resume?
If you froze it yourself, then you'll
David Greaves wrote:
been away, back now...
again...
David Greaves wrote:
When I move the swap/resume partition to a different controller (ie when
I broke the / mirror and used the freed space) the problem seems to go
away.
No, it's not gone away - but it's taking longer to show
David Chinner wrote:
On Fri, Jun 29, 2007 at 08:40:00AM +0100, David Greaves wrote:
What happens if a filesystem is frozen and I hibernate?
Will it be thawed when I resume?
If you froze it yourself, then you'll have to thaw it yourself.
So hibernate will not attempt to re-freeze a froz
David Chinner wrote:
On Fri, Jun 29, 2007 at 12:16:44AM +0200, Rafael J. Wysocki wrote:
There are two solutions possible, IMO. One would be to make these workqueues
freezable, which is possible, but hacky and Oleg didn't like that very much.
The second would be to freeze XFS from within the hib
Bill Davidsen wrote:
David Greaves wrote:
[EMAIL PROTECTED] wrote:
On Fri, 22 Jun 2007, David Greaves wrote:
If you end up 'fiddling' in md because someone specified
--assume-clean on a raid5 [in this case just to save a few minutes
*testing time* on system with a heavily choked
[EMAIL PROTECTED] wrote:
On Fri, 22 Jun 2007, David Greaves wrote:
That's not a bad thing - until you look at the complexity it brings -
and then consider the impact and exceptions when you do, eg hardware
acceleration? md information fed up to the fs layer for xfs? simple
long
Neil Brown wrote:
On Thursday June 21, [EMAIL PROTECTED] wrote:
I didn't get a comment on my suggestion for a quick and dirty fix for
-assume-clean issues...
Bill Davidsen wrote:
How about a simple solution which would get an array on line and still
be safe? All it would take is a flag which
been away, back now...
Tejun Heo wrote:
David Greaves wrote:
Tejun Heo wrote:
How reproducible is the problem? Does the problem go away or occur more
often if you change the drive you write the memory image to?
I don't think there should be activity on the sda drive during resume
i
[EMAIL PROTECTED] wrote:
On Thu, 21 Jun 2007, David Chinner wrote:
one of the 'killer features' of zfs is that it does checksums of every
file on disk. so many people don't consider the disk infallable.
several other filesystems also do checksums
both bitkeeper and git do checksums of files t
Neil Brown wrote:
This isn't quite right.
Thanks :)
Firstly, it is mdadm which decided to make one drive a 'spare' for
raid5, not the kernel.
Secondly, it only applies to raid5, not raid6 or raid1 or raid10.
For raid6, the initial resync (just like the resync after an unclean
shutdown) reads
Rafael J. Wysocki wrote:
This is on 2.6.22-rc5
Is the Tejun's patch
http://www.sisk.pl/kernel/hibernation_and_suspend/2.6.22-rc5/patches/30-block-always-requeue-nonfs-requests-at-the-front.patch
applied on top of that?
2.6.22-rc5 includes it.
(but, when I was testing rc4, I did apply this
Tejun Heo wrote:
Hello,
again...
David Greaves wrote:
Good :)
Now, not so good :)
Oh, crap. :-)
So I hibernated last night and resumed this morning.
Before hibernating I froze and sync'ed. After resume I thawed it. (Sorry
Dave)
Here are some photos of the screen during resume.
David Greaves wrote:
I'm going to have to do some more testing...
done
David Chinner wrote:
On Mon, Jun 18, 2007 at 08:49:34AM +0100, David Greaves wrote:
David Greaves wrote:
So doing:
xfs_freeze -f /scratch
sync
echo platform > /sys/power/disk
echo disk > /sys/power/sta
David Chinner wrote:
> FWIW, I'm on record stating that "sync" is not sufficient to quiesce an XFS
> filesystem for a suspend/resume to work safely and have argued that the only
> safe thing to do is freeze the filesystem before suspend and thaw it after
> resume.
Whilst testing a potential bug i
at 08:49:34AM +0100, David Greaves wrote:
David Greaves wrote:
So doing:
xfs_freeze -f /scratch
sync
echo platform > /sys/power/disk
echo disk > /sys/power/state
# resume
xfs_freeze -u /scratch
Works (for now - more usage testing tonight)
Verrry interesting.
Good :)
What you were seeing
David Greaves wrote:
David Robinson wrote:
David Greaves wrote:
This isn't a regression.
I was seeing these problems on 2.6.21 (but 22 was in -rc so I waited
to try it).
I tried 2.6.22-rc4 (with Tejun's patches) to see if it had improved -
no.
Note this is a different (desktop)
Rafael J. Wysocki wrote:
On Saturday, 16 June 2007 21:56, David Greaves wrote:
This isn't a regression.
I was seeing these problems on 2.6.21 (but 22 was in -rc so I waited to try it).
I tried 2.6.22-rc4 (with Tejun's patches) to see if it had improved - no.
Note this is a differen
David Robinson wrote:
David Greaves wrote:
This isn't a regression.
I was seeing these problems on 2.6.21 (but 22 was in -rc so I waited
to try it).
I tried 2.6.22-rc4 (with Tejun's patches) to see if it had improved - no.
Note this is a different (desktop) machine to that i
This isn't a regression.
I was seeing these problems on 2.6.21 (but 22 was in -rc so I waited to try it).
I tried 2.6.22-rc4 (with Tejun's patches) to see if it had improved - no.
Note this is a different (desktop) machine to that involved my recent bugs.
The machine will work for days (continu
[EMAIL PROTECTED] wrote:
On Sat, 16 Jun 2007, Neil Brown wrote:
I want to test several configurations, from a 45 disk raid6 to a 45 disk
raid0. at 2-3 days per test (or longer, depending on the tests) this
becomes a very slow process.
Are you suggesting the code that is written to enhance data
Neil Brown wrote:
On Friday June 15, [EMAIL PROTECTED] wrote:
As I understand the way
raid works, when you write a block to the array, it will have to read all
the other blocks in the stripe and recalculate the parity and write it out.
Your u
Krzysztof Halasa wrote:
David Greaves <[EMAIL PROTECTED]> writes:
How hard would it be to reprogramm the flash?
The flash contains hashes signed by the companies private key.
The kernel contains the public key. It can decrypt the hashes but the
private key isn't available to encry
Krzysztof Halasa wrote:
David Greaves <[EMAIL PROTECTED]> writes:
This 5 minute design undoubtedly has flaws but it shows a direction:
A basically standard 'De11' PC with some flash.
A Tivoised boot system so only signed kernels boot.
A modified kernel that only runs (FOSS) e
I've started a new thread here since the old one got somewhat hijacked.
Rafael J. Wysocki wrote:
> On Friday, 1 June 2007 23:23, David Greaves wrote:
>> Not a regression though, it does it in 2.6.21
>>
>> If I cause the system to save state to disk then whilst off it
Linus Torvalds wrote:
On Fri, 15 Jun 2007, David Greaves wrote:
Surely it's more:
bad == go away and don't use future improvements to our software anymore
please.
??
Well, with the understanding that I don't think that what Tivo did was bad
in the first place, let me tackl
David, please test this. Jens, does it look okay?
Phew!
Works for me.
I applied it to 2.6.22-rc4 (along with
sata_promise_use_TF_interface_for_polling_NODATA_commands.patch) hibernate and
resume worked.
Thanks for digging it out Tejun (and everyone else!) :)
David
-
To unsubscribe from t
Daniel Hazelton wrote:
Now for a different PoV:
Do I think Tivoisation is bad for the community ?
Of course I think it is but your mileage may vary.
And I happen to agree with you. What I disagree with is taking steps to
make "bad == illegal". I also have a problem with doing things that force
Tejun Heo wrote:
They're waiting for the commands they issued to complete. ata_aux is
trying to revalidate the scsi device after libata EH finished waking up
the port and hibernate is trying to resume scsi disk device. ata_aux is
issuing either TEST UNIT READY or START STOP. hibernate is issui
Linus Torvalds wrote:
On Wed, 13 Jun 2007, David Greaves wrote:
git-bisect bad
9666f4009c22f6520ac3fb8a19c9e32ab973e828 is first bad commit
commit 9666f4009c22f6520ac3fb8a19c9e32ab973e828
Author: Tejun Heo <[EMAIL PROTECTED]>
Date: Fri May 4 21:27:47 2007 +0200
libata: reimp
Pavel Machek wrote:
Hi!
cu:~# mount -oremount,ro /huge
cu:~# /usr/net/bin/hibernate
[this works and resumes]
cu:~# mount -oremount,rw /huge
cu:~# /usr/net/bin/hibernate
[this works and resumes too !]
cu:~# touch /huge/tst
cu:~# /usr/net/bin/hibernate
[but this doesn't even hibernate]
This is
[RESEND since I sent this late last friday and it's probably been buried by
now.]
I had this as a PS, then I thought, we could all be wasting our time...
I don't like these "Section mismatch" warnings but that's because I'm paranoid
rather than because I know what they mean. I'll be happier whe
I had this as a PS, then I thought, we could all be wasting our time...
I don't like these "Section mismatch" warnings but that's because I'm paranoid
rather than because I know what they mean. I'll be happier when someone says
"That's OK, I know about them, they're not the problem"
WARNING:
Mark Lord wrote:
Tejun Heo wrote:
Can you setup serial console and/or netconsole (not sure whether this
would work tho)?
Since he has good console output already, capturable by digicam,
I think a better approach might be to provide a patch with extra
instrumentation..
You know.. progress me
David Chinner wrote:
On Thu, Jun 07, 2007 at 11:30:05AM +0100, David Greaves wrote:
Tejun Heo wrote:
Hello,
David Greaves wrote:
Just to be clear. This problem is where my system won't resume after s2d
unless I umount my xfs over raid6 filesystem.
This is really weird. I don't s
Duane Griffin wrote:
On 07/06/07, David Greaves <[EMAIL PROTECTED]> wrote:
> How hard does the machine freeze? Can you use sysrq? If so, please
> dump sysrq-t.
I suspect there is a problem writing to the consoles...
I recompiled (rc4+patch) with sysrq support, suspended, resum
Tejun Heo wrote:
Hello,
David Greaves wrote:
Just to be clear. This problem is where my system won't resume after s2d
unless I umount my xfs over raid6 filesystem.
This is really weird. I don't see how xfs mount can affect this at all.
Indeed.
It does :)
How hard does the mach
Tejun Heo wrote:
Hello,
David Greaves wrote:
Linus Torvalds wrote:
It would be interesting to see what triggered it, since it apparently
worked before. So yes, a bisection would be great.
Tejun, all the problematic patches are yours - so adding you.
Ouch
that's what everyone
Linus Torvalds wrote:
> So -rc4 is out there now, hopefully shrinking the regression list further.
> I'd ask that people involved with the known regressions please test
> whether they got fixed, and if you wrote a patch and it's still pending,
> please make sure to push it upstream..
[Tejun, J
Linus Torvalds wrote:
> So -rc4 is out there now, hopefully shrinking the regression list further.
>
> The diffstat (for those that look at those kinds of things) tells the
> story: lots of small stuff to random files. I think the single biggest
> file change was the patch-checking script, alon
Mark Lord wrote:
> That's odd. Could you try that again,
> with the latest (either v7.3 or v7.4) version of hdparm
> (from sourceforge) ?
Using Debian's 7.3 via apt-get experimental - is that OK or would you like me to
compile the upstream?
2.6.21.1
cu:~# hdparm -V
hdparm v7.3
cu:~# hdparm -K1
Mark Lord wrote:
> David Greaves wrote:
>> I have 2 ide disks. If I enable SMART and hibernate/suspend2disk,
>> SMART is
>> disabled when I resume.
>
> Just a thought: This *may* be fixable at the drive, with "hdparm -K1".
Thanks Mark, good idea.
Just tried
Linus Torvalds wrote:
> It would be interesting to see what triggered it, since it apparently
> worked before. So yes, a bisection would be great.
Tejun, all the problematic patches are yours - so adding you.
Neil, since the problem only occurs whilst an xfs filesystem is mounted on a
raid6 array
This started as a non-regression bug-report about wakeonlan
During tests I found a real regression and this email is only about 2.6.22-rc3
without Rafael's patches - which I'll happily come back to later :)
Rafael J. Wysocki wrote:
> On Saturday, 2 June 2007 00:37, David Greaves wro
Tejun Heo wrote:
> David Greaves wrote:
>> I have 2 ide disks. If I enable SMART and hibernate/suspend2disk, SMART is
>> disabled when I resume.
>>
>> Same as in 2.6.21.1
>
> According to the ATA standard, the device (drive) itself is responsible
> for preser
Rafael J. Wysocki wrote:
> On Friday, 1 June 2007 23:23, David Greaves wrote:
>> Not a regression though, it does it in 2.6.21
>>
>> If I cause the system to save state to disk then whilst off it no longer
>> responds to g-wol.
>
> Can you please try with the hib
I have 2 ide disks. If I enable SMART and hibernate/suspend2disk, SMART is
disabled when I resume.
Same as in 2.6.21.1
cu:~# smartctl -son /dev/hda
smartctl version 5.36 [i686-pc-linux-gnu] Copyright (C) 2002-6 Bruce Allen
Home page is http://smartmontools.sourceforge.net/
=== START OF ENABLE/DI
Not a regression though, it does it in 2.6.21
If I cause the system to save state to disk then whilst off it no longer
responds to g-wol.
bug report:
# wakeonlan cu
Sending magic packet to 255.255.255.255:9 with 00:0C:6E:F6:47:EE
Nothing happens
cu:~# ethtool eth0
Settings for eth0:
S
Bill Davidsen wrote:
> David Greaves wrote:
>> Bill Davidsen wrote:
>>> Anyway, I pulled the plug on the UPS, and the system shut down. But when
>>> it powered up, it booted the default kernel rather than the test kernel,
>>> decided that it couldn't resume
Bill Davidsen wrote:
> Anyway, I pulled the plug on the UPS, and the system shut down. But when
> it powered up, it booted the default kernel rather than the test kernel,
> decided that it couldn't resume, and then did a cold boot.
Booting the machine isn't the kernel's job, it's the bootloader's
Kyle Moffett wrote:
> On May 03, 2007, at 11:10:47, Pavel Machek wrote:
>> How mature is freezing filesystems -- will it work on at least ext2/3
>> and vfat?
>
> I'm pretty sure it works on ext2/3 and xfs and possibly others, I don't
> know either way about VFAT though. Essentially the "freeze" p
[EMAIL PROTECTED] wrote:
> On Wed, 2 May 2007, Miguel Sousa Filipe wrote:
>
>> On 5/2/07, Diego Calleja <[EMAIL PROTECTED]> wrote:
>>> El Wed, 2 May 2007 20:18:55 +0100, "Miguel Sousa Filipe"
>>> <[EMAIL PROTECTED]> escribió:
>>>
>>> > I find it high irritanting having two kernel interfaces and
Loye Young wrote:
> Basically, I need the scanner to act like another keyboard. Scan a code, see
> the numbers.
Depends, do you want to get the job done or play with drivers?
If the former then get yourself to eBay and buy a brand new PS/2 barcode reader
for circa $10-$20 that plugs between the
Doug Warzecha wrote:
>This patch adds the Dell Systems Management Base Driver with sysfs support.
>
>This patch incorporates changes based on comments from the previous posting.
>
>Summary of changes:
>
>* Changed permissions on sysfs files so that only owner can read.
>* Changed to use __uNN/__sN
Jeff Garzik wrote:
>
> True enough :/
>
> It's been feature-complete for a while, but the reports from testers
> in the field have made me too nervous to push it into the upstream
> kernel.
>
> I might push it upstream, but disable it by default, which would allow
> for a wider test audience.
Cou
Bill Davidsen wrote:
Matt Mackall wrote:
In your world, do you want to do:
cp -rl linux-2.6.11 linux-2.6.11.5
cd linux-2.6.11.5
bzcat ../Patches/patch-2.6.11.1.bz2 | patch -p1
bzcat ../Patches/patch-2.6.11.2.bz2 | patch -p1
bzcat ../Patches/patch-2.6.11.3.bz2 | patch -p1
bzcat ../Patches/patch-2.6.
Greg KH wrote:
On Tue, Mar 15, 2005 at 04:15:54PM +, David Greaves wrote:
Old thread (!) but this is the last time I could find patch-kernel updated.
Why not just use ketchup instead?
OK - should patch-kernel be deprecated?
Should ketchup go in scripts/
David
-
To unsubscribe from
Old thread (!) but this is the last time I could find patch-kernel updated.
Sam Ravnborg wrote:
On Wed, Aug 18, 2004 at 01:57:51PM -0700, Randy.Dunlap wrote:
Update 'scripts/patch-kernel' to support EXTRAVERSION.
I saw no complains, so applied.
FYI
$ ./scripts/patch-kernel . /everything/
Richard Purdie wrote:
Writing instructions for setting up oe to build it may be the best
option.
As it happens I was editing that exact page in the wiki t'other day:
http://openembedded.org/cgi-bin/moin.cgi/GettingStarted
I actually only wanted a toolchain but oe and scratchbox[1] seemed the
rat
-rc just means "please start testing", not "deploy me on your corporate
database server".
Does it? Where on www.kernel.org does it say that?
Since people's trust was lost (a bit) when the -rc convention was
"embraced and extended", it seems like it would be a good idea to
_explicitly publish_
Linus Torvalds wrote:
On Thu, 3 Mar 2005, Horst von Brand wrote:
[I'm pulling bk daily, and have it mixed with the ipw tree too, so I'm just
the kind of tester you are looking for... haven't seen any of the
showstopper bugs everybody is talking about, or I'd have screamed.]
Yeah, I wish eve
Matt Mackall wrote:
On Wed, Mar 02, 2005 at 02:21:38PM -0800, Linus Torvalds wrote:
This is an idea that has been brewing for some time: Andrew has mentioned
it a couple of times, I've talked to some people about it, and today Davem
sent a suggestion along similar lines to me for 2.6.12.
Namely
Hi
Just had a crash on 2.6.10rc2
xfs,nfs,lvm2,raid5 server doing fairly low level I/O with fairly big
(2-3Gb) files.
I'm aware of 2.6.11-rc1-mm1 - but as reported previously that's not
working right now.
So, just in case this may be useful.
David
Jan 18 22:36:48 cu kernel: c016d577
Jan 18 22:36
72 matches
Mail list logo
