dingly. I don't think any code eventuated from this discussion
though ...
Letting kacpid run during suspend appeared to be a good compromise
(but still racy if GPEs were to occur at exactly the right instant
- just before the atomic copy). Implementing suspend/resume support
for GPEs wou
get a less ugly name one
of these days :)
Bernard.
--
Bernard Blackham
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
s actually done, I've a
few questions:
- Should this be considered dangerous?
- Why was it taken from 3 to 1?
- Is CARM_MAX_Q a number defined (or limited) by the hardware?
Thanks in advance,
Bernard.
--
Bernard Blackham
-
To unsubscribe from this list: send the line "unsubscri
down and up anyway, so there were no regressions there, just
bugs. Software Suspend 2 passed "4" as the power state which
ide-disk.c treated as "flush caches, but don't spin down". This is
what broke when the new typedefs went in, but would be fixed when
they're c
ear). Alternately (or additionally), you could examine
the signature when sys_swapon is called on a swap partition (though
the code couldn't be __init then).
These together I want to claim would catch many of these cases, and
any effort to avoid severe filesystem corruption is a good thing.
The hibernate script
available from the Software Suspend 2 homepage already has options
to reconfigure LILO/GRUB upon suspending. I'd forgotten about them!
Bernard.
--
Bernard Blackham
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a mess
t know the Nigel's
> > patch before :-)).
>
> I should clarify credit. I didn't work on that code. I don't recall now
> whether it was Michael Frank or Bernard Blackham that came up with this
> version. (This was about a year ago IIRC).
Definitely not me, sorry
sly.
I'll give those a workout over the weekend and let you know the
results.
Thanks,
Bernard.
--
Bernard Blackham
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
page write due to I/O error on sx80_0p1
end_request: I/O error, dev sx80_2, sector 389167
It's been thrashing away with various tests most of today with
CARM_MAX_Q = 16, and it hasn't missed a beat.
Thanks must go to Matt Johnston who actually did all the work of
giving the card and dri
ion
(amd64 machine) also with fsx, we encountered a kernel panic who's
backtrace looked like:
ext3_discard_reservation
ext3_truncate
.
.
.
do_truncate
sys_ftruncate
Could this same change (which was in ext3 also) be responsible for
this?
Bernard.
[1] http://matt.ucc.asn.au/ext2bad
10 matches
Mail list logo
