Jeff Garzik wrote:
1) To make it easier for people to review and test the driver, I would
suggest posting a diff against 2.6.24-rc7 (or 2.6.23), ignoring my
original code. Thus, it would result in a patch
Er, that sentence was incomplete. Continuing...
Thus it would result in a patch that
Ke Wei wrote:
The 88SE6440 driver :
The driver is based on bare code from Jeff Garzik. And it can work
under linux kernel 2.6.23.
By far, Can discover and find SAS HDD, but SATA is currently
unsupported. Command queue depth can be above 1.
Most error handling, and some phy handling code is notab
The 88SE6440 driver :
The driver is based on bare code from Jeff Garzik. And it can work
under linux kernel 2.6.23.
By far, Can discover and find SAS HDD, but SATA is currently
unsupported. Command queue depth can be above 1.
Most error handling, and some phy handling code is notably missing.
co
Matthew Wilcox wrote:
On Wed, Jan 09, 2008 at 12:36:26PM -0800, Jon Watte wrote:
Stefan Richter wrote:
Those systems (servers) typically have enough memory to tolerate a few
extra KB of code without problems. In fact most PCs these days have.
It would be a stupid solution nevertheless.
(
Matthew Hall wrote:
ACPI: PCI Interrupt Link [LT3D] enabled at IRQ 46
ACPI: PCI Interrupt :80:07.0[A] -> Link [LT3D] -> GSI 46 (level,
low) -> IRQ 46
sata_nv :80:07.0: Using ADMA mode
PCI: Unable to reserve mem region #6:[EMAIL PROTECTED] for device
:80:07.0
ACPI: PCI interrupt for de
On Thu, Jan 10, 2008 at 02:47:33AM +, Matthew Hall wrote:
> I am using the Supermicro H8DCE motherboard. Some (not all) of the SATA
> channels quit working due to some kind of resource conflict when I
> upgrade to any kernel above 2.6.20.xx series, in my case I am running
> 2.6.20.21 SMP x86
Hello Storage Controller Experts,
I am writing this mail to you to request your assistance in resolving a
functionality regression in my sata_nv controller driver in recent Linux
kernels. I am hoping you can assist me in finding a solution to this
because my TV tuner card is dependent on some f
On Thursday 10 January 2008 09:10:37 James Bottomley wrote:
> On Tue, 2008-01-08 at 11:39 +1100, Rusty Russell wrote:
> > On Tuesday 08 January 2008 02:48:23 James Bottomley wrote:
> > > We're always open to new APIs (or more powerful and expanded old ones).
> > > The way we've been doing the sg_ch
Andi Kleen wrote:
> On Thu, Jan 10, 2008 at 12:03:59AM +0100, Stefan Richter wrote:
>>> Kconfig is also not an educational facility or high level
>>> design description of the code, but a pragmatic tool to get the job
>>> done.
>> I did not talk about education or design decription. I did talk abo
On Thu, Jan 10, 2008 at 12:03:59AM +0100, Stefan Richter wrote:
> Andi Kleen wrote:
> > On Wed, Jan 09, 2008 at 10:41:59PM +0100, Stefan Richter wrote:
> >> However, this further obfuscates the fact that libata uses Linux' SCSI
> >> midlayer and highlevel. Which is a bad thing. For example, there
On Wed, 2008-01-09 at 23:59 +0100, Krzysztof Helt wrote:
> From: Krzysztof Helt <[EMAIL PROTECTED]>
>
> This patch fixes two bugs pointed by James Bottomley:
>
> 1. the if (!sym_data->io_reset). That variable is only ever filled
> by a stack based completion. If we find it non empty it me
Stefan Richter wrote:
> The Kconfig menu layouts, prompts, and help texts are there to inform/
> "educate"/ guide the user when configuring the build environment, with
> the goal that he safely and efficiently gets to a working software
> configuration.
It might have been not entirely clear from m
Andi Kleen wrote:
> On Wed, Jan 09, 2008 at 10:41:59PM +0100, Stefan Richter wrote:
>> However, this further obfuscates the fact that libata uses Linux' SCSI
>> midlayer and highlevel. Which is a bad thing. For example, there are
>
> People are not interested in how libata is implemented interna
From: Krzysztof Helt <[EMAIL PROTECTED]>
This patch fixes two bugs pointed by James Bottomley:
1. the if (!sym_data->io_reset). That variable is only ever filled
by a stack based completion. If we find it non empty it means
this code has been entered twice and we have a severe problem,
On Wed, Jan 09, 2008 at 10:44:49PM +0100, Hans de Goede wrote:
> First of all sorry for the somewhat massive cross-posting, I've spend a
> significant amount of time hunting down this bug, and so far the response
> has been less the overwhelming.
> The cardreader of the multi function printers
Thank you all for responding. While I agree that the scsi stack in linux should
be capable of supporting many targets, I still see this problem all the time.
It seemed to consistently happen on /dev/sdbm which corresponds to the 65th lun
or target.
My SAN configuration consists of: 4 targets wi
On Wed, Jan 09, 2008 at 10:41:59PM +0100, Stefan Richter wrote:
> Matthew Wilcox wrote:
> > OK, how about this?
> >
> > config BLK_DEV_ATA_SD
> > tristate "ATA disc support"
> > select BLK_DEV_SD
> >
> > config BLK_DEV_ATA_SR
> > tristate "ATA CDROM support"
> > select BLK_DEV_SR
On Tue, 2008-01-08 at 11:39 +1100, Rusty Russell wrote:
> On Tuesday 08 January 2008 02:48:23 James Bottomley wrote:
> > We're always open to new APIs (or more powerful and expanded old ones).
> > The way we've been doing the sg_chain conversion is to slide API layers
> > into the drivers so sg_ch
Hi All,
First of all sorry for the somewhat massive cross-posting, I've spend a
significant amount of time hunting down this bug, and so far the response has
been less the overwhelming.
The problem is with the HP PSC 1350 (my printer and confirmed by 2 others) and
atleast also the HP PSC 161
Matthew Wilcox wrote:
> OK, how about this?
>
> config BLK_DEV_ATA_SD
> tristate "ATA disc support"
> select BLK_DEV_SD
>
> config BLK_DEV_ATA_SR
> tristate "ATA CDROM support"
> select BLK_DEV_SR
It's probably OK for many uses.
However, this further obfuscates the fact
On Wed, Jan 09, 2008 at 12:36:26PM -0800, Jon Watte wrote:
> Stefan Richter wrote:
> >>Those systems (servers) typically have enough memory to tolerate a few
> >>extra KB of code without problems. In fact most PCs these days have.
> >>
> >
> >It would be a stupid solution nevertheless.
> >
> >
Hello,
is there a way to distinguish calls to sd_open() from mount() from
calls to open() ?
Regards
Oliver
-
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/m
On Wed, 9 Jan 2008, Oliver Neukum wrote:
> Am Mittwoch, 9. Januar 2008 18:22:51 schrieb Alan Stern:
> > On Wed, 9 Jan 2008, Oliver Neukum wrote:
> >
> > > This has an interesting implication. As the storage driver can share
> > > a device with in principle any other usb driver, we must audit all
Stefan Richter wrote:
Those systems (servers) typically have enough memory to tolerate a few
extra KB of code without problems. In fact most PCs these days have.
It would be a stupid solution nevertheless.
(We also don't "select EXT3".)
It's not the prettiest solution, but it would
The shared tag issue was not fixed yet. Kernel panic
happened while running I/O test in kernel 2.6.23
(information attached). After applying the patch I posted
(or the version James modified), panic disappeared.
Switch back to standard kernel, panic again.
Please reconsider this issue. Thanks.
E
>On Wed, Oct 24 2007, James Bottomley wrote:
>> On Wed, 2007-10-24 at 12:17 -0700, Andrew Morton wrote:
>> > On Wed, 24 Oct 2007 11:59:30 -0700 "Ed Lin" <[EMAIL PROTECTED]> wrote:
>> >
>> > > The shared tag issue was not fixed yet. Kernel panic
>> > > happened while running I/O test in kernel 2.6
Stefan Richter wrote:
> The "select SCSI" in libata's Kconfig option is not of great
> help with that issue and is misguided and unnecessary as well.
+comment "Serial and Parallel ATA need SCSI command sets"
+ depends on SCSI=n
menuconfig ATA
tristate "Serial ATA (prod) and Paralle
On Tue, 2008-01-08 at 23:07 +0900, FUJITA Tomonori wrote:
> CC'ed Jes,
>
> On Tue, 8 Jan 2008 14:15:53 +0300
> Evgeniy Dushistov <[EMAIL PROTECTED]> wrote:
>
> > On Sun, Nov 25, 2007 at 01:24:25PM +0200, James Bottomley wrote:
> > > This is a bit of a rash of bug fixes. The qla1280 is actually
Stefan Richter wrote:
>>> On Wed, 2008-01-09 at 09:21 -0800, Jon Watte wrote:
>>> > I wonder if it's possible to magically turn that on when selecting
>>> > AHCI support in menuconfig? That way, it'd be harder for someone else
>>> > to make the same mistake.
> (We also don't "select EXT3".)
Perha
Andi Kleen wrote:
> On Wed, Jan 09, 2008 at 11:29:26AM -0600, James Bottomley wrote:
>> On Wed, 2008-01-09 at 09:21 -0800, Jon Watte wrote:
>> > Yes, that turns out to be the case. Thanks for the quick sanity check!
>> > I wonder if it's possible to magically turn that on when selecting
>> > AHCI s
On Wed, Jan 09, 2008 at 11:29:26AM -0600, James Bottomley wrote:
>
> On Wed, 2008-01-09 at 09:21 -0800, Jon Watte wrote:
> > Yes, that turns out to be the case. Thanks for the quick sanity check!
> > I wonder if it's possible to magically turn that on when selecting
> > AHCI support in menuconfig?
Am Mittwoch, 9. Januar 2008 18:22:51 schrieb Alan Stern:
> On Wed, 9 Jan 2008, Oliver Neukum wrote:
>
> > This has an interesting implication. As the storage driver can share
> > a device with in principle any other usb driver, we must audit all usb
> > drivers if we wish to adopt this patch.
> >
On Wed, 2008-01-09 at 09:21 -0800, Jon Watte wrote:
> Yes, that turns out to be the case. Thanks for the quick sanity check!
> I wonder if it's possible to magically turn that on when selecting
> AHCI support in menuconfig? That way, it'd be harder for someone else
> to make the same mistake.
We'
On Wed, 9 Jan 2008, Oliver Neukum wrote:
> This has an interesting implication. As the storage driver can share
> a device with in principle any other usb driver, we must audit all usb
> drivers if we wish to adopt this patch.
> All a device's interfaces must be resumed when the storage interface
Yes, that turns out to be the case. Thanks for the quick sanity check!
I wonder if it's possible to magically turn that on when selecting
AHCI support in menuconfig? That way, it'd be harder for someone else
to make the same mistake.
Cheers,
/ h+
On Jan 9, 2008 8:45 AM, Andi Kleen <[EMA
"Jon Watte" <[EMAIL PROTECTED]> writes:
>
> Any help or pointers to self-help would be appreciated!
The usual mistake is to not enable CONFIG_BLK_DEV_SD
-Andi
-
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to [EMAIL PROTECTED]
More majordomo info
Am Montag, 7. Januar 2008 20:42:23 schrieb Alan Stern:
> When all the devices under a host are suspended, the LLD is informed
> (via a new "autosuspend" method in the host template) so that it can
> put the host adapter in a low-power state. Likewise, a new
> "autoresume" method is called when
On Wed, 09 Jan 2008, Matthew Wilcox wrote:
> On Wed, Jan 09, 2008 at 09:05:52AM -0600, James Bottomley wrote:
> > On Tue, 2008-01-08 at 19:22 -0700, Matthew Wilcox wrote:
> > > On Tue, Jan 08, 2008 at 04:55:46PM -0800, Vinay Venkataraghavan wrote:
> > > > Is there a limit on the number of devices
On Wed, Jan 09, 2008 at 09:05:52AM -0600, James Bottomley wrote:
> On Tue, 2008-01-08 at 19:22 -0700, Matthew Wilcox wrote:
> > On Tue, Jan 08, 2008 at 04:55:46PM -0800, Vinay Venkataraghavan wrote:
> > > Is there a limit on the number of devices that SCSI supports. In other
> > > words, I have a
On Tue, 8 Jan 2008, Pavel Machek wrote:
> > In fact suspend methods already do take an argument specifying the
> > reason they were called. It wouldn't be hard to add a couple of extra
> > PM_EVENT_* values for manual suspend and autosuspend. The problem is
> > that resume methods don't take a
On Wed, 2008-01-09 at 14:13 +0900, Tejun Heo wrote:
> James Bottomley wrote:
> >> Also, DMA alignment at
> >> block layer isn't enough for ATA. ATA needs drain buffers for ATAPI
> >> commands with variable length response. :-(
> >
> > OK, where is this in the libata code? The dma_pad size is
On Tue, 2008-01-08 at 19:22 -0700, Matthew Wilcox wrote:
> On Tue, Jan 08, 2008 at 04:55:46PM -0800, Vinay Venkataraghavan wrote:
> > Is there a limit on the number of devices that SCSI supports. In other
> > words, I have a QLogic HBA card, and I am connecting to a SAN which has 64
> > targets.
You will want to check the BIOS settings on the Qlogic HBA, if you are running
into a problem. Also, there may be limitations that are inherent to the
storage to which you are connecting.
Regards,
Frank
-Original Message-
From: [EMAIL PROTECTED] on behalf of Matthew Wilcox
Sent: Tue
43 matches
Mail list logo
