lkml.org 
[lkml]   [2002]   [Feb]   [26]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: 2.5.5-dj1 - ide_set_handler/kernel timer <-- and now dj2 as well

Oh this is the ATOMIC/ATOMIX problem I have been working on and may
finally crushed but at a price! This issue is about FORCED PARTIAL
COMPLETIONS. Basically, I have been restricted by a few policies in the
kernel which invokes ATOMIC Segements for the OS but screws the ATOMIC of
the hardware.

I will lay out the specifics why a patch that adopts portions of the
changes in 2.5.5 and backs out a few until a closer look can be taken.

This patch will include how, who, and why the global ATOMIC in 2.4 is a
problem, and the proper way to address the Hardware Segment of the
transfer. The effect until it is fixed is a FUBAR of you data if and only
if you have an error condition.

As for the PANIC, I spent 10 hours last night from 7pm to 5am this past
morning hunting to kill it, and success.

For now I suggest you move your laptop back to a 2.4 kernel because,
regardless if multmode works in the patch to be submitted. GAWD forbid
you tank an error, and this is not a joke, it is not a bluff.

I am DAMN serious about this data issue.

I bitched about and never had a solution, but now I do have the outline
for a solution and it is dynamic enough to assist all the legacy hardware
that was rudely unsupported, IIRC during the transistion in 2.5.

IMHO, we have shorted BLOCK and the HARDWARE over on policy force upon the
lot. It is the beloved "partial completion update". I will state it can
be accomplished but it shall protect and preserve the granularity of the
hardware segment over the top layer rules above BLOCK.

Cheers,

Andre Hedrick
Linux Disk Certification Project Linux ATA Development

On Wed, 27 Feb 2002, Brett wrote:

>
> Hey,
>
> Subject says it all... still getting these
> Oh, and the kernel just panicked.
>
> Traded some emails with andre about this last time,
> and he was unable to get it to stop.
>
> any ideas ?
>
> / Brett
>
> On Fri, 22 Feb 2002, Dave Jones wrote:
>
> > On Fri, 22 Feb 2002, Brett wrote:
> >
> > > This just popped up a few minutes after boot:
> > > hda: ide_set_handler: handler not null; old=c01c4d30, new=c01c4d30
> > > bug: kernel timer added twice at c01c6197.
> >
> > Argh, I thought things would be less problematic by dropping
> > those ide changes. Looks like I missed something.
> > I'll take a look in the morning.
> >
> >
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
>

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

\
 
 \ /
  Last update: 2005-03-22 13:24    [W:0.036 / U:4.276 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site