Re: [PATCH]: pcmcia - spot slave decode flaws (for testing)

2007-02-24 Thread Eric D. Mudama
On 2/23/07, Alan <[EMAIL PROTECTED]> wrote: > Code looks OK. Not applied due to "for testing" note. > > General comment: it might be nice to do this in the core, just as a > sanity check for a variety of problems, past, present and future. We tried that with old IDE and all hell broke loose.

Re: [PATCH]: pcmcia - spot slave decode flaws (for testing)

2007-02-24 Thread Eric D. Mudama
On 2/23/07, Alan [EMAIL PROTECTED] wrote: Code looks OK. Not applied due to for testing note. General comment: it might be nice to do this in the core, just as a sanity check for a variety of problems, past, present and future. We tried that with old IDE and all hell broke loose. Lots of

Re: [PATCH 1/1] filesystem: Disk Errors at boot-time caused by probe of partitions

2007-02-01 Thread Eric D. Mudama
On 2/1/07, TJ <[EMAIL PROTECTED]> wrote: short extract --- DC202XX: Primary channel reset. ide2: reset: success hde: task_in_intr: status=0x59 { DriveReady SeekComplete DataRequest Error } hde: task_in_intr: error=0x04 { DriveStatusError } ide: failed opcode was: unknown end_request: I/O

Re: [PATCH 1/1] filesystem: Disk Errors at boot-time caused by probe of partitions

2007-02-01 Thread Eric D. Mudama
On 2/1/07, Andrew Morton <[EMAIL PROTECTED]> wrote: Also, from reading the replies I think we'd like to see some more explanation of why this is necessary: are you really really sure that those disks were incorrectly handling illegal sector numbers? Knowing the IBM and Maxtor model numbers

Re: [PATCH 1/1] filesystem: Disk Errors at boot-time caused by probe of partitions

2007-02-01 Thread Eric D. Mudama
On 2/1/07, Andrew Morton [EMAIL PROTECTED] wrote: Also, from reading the replies I think we'd like to see some more explanation of why this is necessary: are you really really sure that those disks were incorrectly handling illegal sector numbers? Knowing the IBM and Maxtor model numbers might

Re: [PATCH 1/1] filesystem: Disk Errors at boot-time caused by probe of partitions

2007-02-01 Thread Eric D. Mudama
On 2/1/07, TJ [EMAIL PROTECTED] wrote: short extract --- DC202XX: Primary channel reset. ide2: reset: success hde: task_in_intr: status=0x59 { DriveReady SeekComplete DataRequest Error } hde: task_in_intr: error=0x04 { DriveStatusError } ide: failed opcode was: unknown end_request: I/O

Re: SATA hotplug from the user side ?

2007-01-25 Thread Eric D. Mudama
On 1/24/07, Henrique de Moraes Holschuh <[EMAIL PROTECTED]> wrote: Tejun, is it feasible to teach libata to check the device power management state before issuing any of the sleep, head unload and spin-down commands? libata would need to block its EH from resetting a channel for this check

Re: SATA hotplug from the user side ?

2007-01-25 Thread Eric D. Mudama
On 1/24/07, Henrique de Moraes Holschuh [EMAIL PROTECTED] wrote: Tejun, is it feasible to teach libata to check the device power management state before issuing any of the sleep, head unload and spin-down commands? libata would need to block its EH from resetting a channel for this check

Re: SATA exceptions with 2.6.20-rc5

2007-01-22 Thread Eric D. Mudama
On 1/15/07, Jeff Garzik <[EMAIL PROTECTED]> wrote: Jens Axboe wrote: > On Mon, Jan 15 2007, Jeff Garzik wrote: >> Jens Axboe wrote: >>> I'd be surprised if the device would not obey the 7 second timeout rule >>> that seems to be set in stone and not allow more dirty in-drive cache >>> than it

Re: SATA exceptions with 2.6.20-rc5

2007-01-22 Thread Eric D. Mudama
On 1/15/07, Jeff Garzik [EMAIL PROTECTED] wrote: Jens Axboe wrote: On Mon, Jan 15 2007, Jeff Garzik wrote: Jens Axboe wrote: I'd be surprised if the device would not obey the 7 second timeout rule that seems to be set in stone and not allow more dirty in-drive cache than it could flush out

Re: ahci, SActive flag, and the HD activity LED

2005-08-04 Thread Eric D. Mudama
On 8/3/05, Jens Axboe <[EMAIL PROTECTED]> wrote: > On Wed, Aug 03 2005, Martin Wilck wrote: > > Have you (or has anybody else) also seen the wrong behavior of the > > activity LED? > > No, but I have observed that SActive never gets cleared by the device > for non-NCQ commands (which is probably

Re: [PATCH] IDE disks show invalid geometries in /proc/ide/hd*/geometry

2005-08-04 Thread Eric D. Mudama
On 8/4/05, Jan Engelhardt <[EMAIL PROTECTED]> wrote: > All of these numbers are virtual, since CHS is not really used anymore, as > we know. But, which of these fake CHS values (16383/16/63 | 65535/16/63 | > 1023/255/63) is the right one? 255/63/4982 is another matter, since it > [almost] matches

Re: [PATCH] IDE disks show invalid geometries in /proc/ide/hd*/geometry

2005-08-04 Thread Eric D. Mudama
On 8/4/05, Jan Engelhardt [EMAIL PROTECTED] wrote: All of these numbers are virtual, since CHS is not really used anymore, as we know. But, which of these fake CHS values (16383/16/63 | 65535/16/63 | 1023/255/63) is the right one? 255/63/4982 is another matter, since it [almost] matches the

Re: ahci, SActive flag, and the HD activity LED

2005-08-04 Thread Eric D. Mudama
On 8/3/05, Jens Axboe [EMAIL PROTECTED] wrote: On Wed, Aug 03 2005, Martin Wilck wrote: Have you (or has anybody else) also seen the wrong behavior of the activity LED? No, but I have observed that SActive never gets cleared by the device for non-NCQ commands (which is probably which gets

Re: Call to atention about using hash functions as content indexers (SCM saga)

2005-04-14 Thread Eric D. Mudama
I hold my breath for weeks at a time, just incase something like this happens! I thought I was the only one! On 4/12/05, Theodore Ts'o <[EMAIL PROTECTED]> wrote: > So past a certain point, there is a probability that all of molecules > of oxygen in the room will suddenly migrate outdoors, and

Re: Call to atention about using hash functions as content indexers (SCM saga)

2005-04-14 Thread Eric D. Mudama
I hold my breath for weeks at a time, just incase something like this happens! I thought I was the only one! On 4/12/05, Theodore Ts'o [EMAIL PROTECTED] wrote: So past a certain point, there is a probability that all of molecules of oxygen in the room will suddenly migrate outdoors, and you

Re: Kernel SCM saga..

2005-04-09 Thread Eric D. Mudama
On Apr 8, 2005 4:52 PM, Roman Zippel <[EMAIL PROTECTED]> wrote: > The problem is you pay a price for this. There must be a reason developers > were adding another GB of memory just to run BK. > Preserving the complete merge history does indeed make repeated merges > simpler, but it builds up

Re: Kernel SCM saga..

2005-04-09 Thread Eric D. Mudama
On Apr 8, 2005 4:52 PM, Roman Zippel [EMAIL PROTECTED] wrote: The problem is you pay a price for this. There must be a reason developers were adding another GB of memory just to run BK. Preserving the complete merge history does indeed make repeated merges simpler, but it builds up complex