Hello Eric , Fyi , linux-2.6.21-rc4 + mpt-fusion(*) patches from
Andrew Morton's patch tree . Still gives me the ever looping reset . But I
have just found sometrhing of interest one of the Powersuplies in the cabiinet
'May be' failing . I have to test that to be satisfied that is the case
With libata converted to use sdev->manage_start_stop for suspend and
resume, sht->suspend/resume() has no user left and low level
suspend/ressume should be taken care of by low level driver's
suspend/resume callbacks (e.g. PCI or PCMCIA driver callbacks). This
patch removes sht->suspend/resume() c
James Bottomley wrote:
> On Wed, 2007-03-21 at 02:08 +0900, Tejun Heo wrote:
>> I got too comfortable with libata-dev#upstream and forgot to verify
>> patches against scsi-misc-2.6. Sorry about that. If you don't have
>> objection against the content, I'll resubmit the SCSI part against
>> scsi-m
Hello, Douglas.
Douglas Gilbert wrote:
> Tejun,
> I note at this point that the IMMED bit in the
> START STOP UNIT cdb is clear. [The code might
> note that as well.] All SCSI disks that I have
> seen, implement the IMMED bit and according to
> the SAT standard, so should SAT layers like the
> one
This teaches scsi devices how to support "new style" hotplug/coldplug:
using a modalias sysfs attribute for coldplug, and MODALIAS environment
variable for hotplug.
It also updates the CH, SD, SR, and ST drivers with the aliases needed to
drive them by that mechanism. (Older OnStream devices use
On Tue, 20 Mar 2007, James Bottomley wrote:
> On Tue, 2007-03-20 at 14:32 -0500, James Bottomley wrote:
> > Is MODULE set to 'n'? It looks like the symbol export is guarded by
> > #ifdef MODULE for some reason ... other than that, I can't explain this.
>
> In fact, that's the bug ... the modular
On Tue, 2007-03-20 at 14:32 -0500, James Bottomley wrote:
> Is MODULE set to 'n'? It looks like the symbol export is guarded by
> #ifdef MODULE for some reason ... other than that, I can't explain this.
In fact, that's the bug ... the modular config is MODULES not MODULE.
Can you try this:
James
On Tue, 20 Mar 2007, James Bottomley wrote:
> On Tue, 2007-03-20 at 12:19 -0700, Andrew Vasquez wrote:
> > SCSI_SCAN_ASYNC was compiled non-modularly before merging the latest
> > scsi-misc-2.6.git tree. After the merge, and a rebuild of the kernel,
> > was getting 'unknown symbol' failures durin
On Tue, 2007-03-20 at 12:19 -0700, Andrew Vasquez wrote:
> SCSI_SCAN_ASYNC was compiled non-modularly before merging the latest
> scsi-misc-2.6.git tree. After the merge, and a rebuild of the kernel,
> was getting 'unknown symbol' failures during link as SCSI_WAIT_SCAN
> was now forced to be built
On Tue, 20 Mar 2007, James Bottomley wrote:
> On Tue, 2007-03-20 at 11:56 -0700, Andrew Vasquez wrote:
> > Commit 840c2835a1c867281d27158378a9d34f593a7664 ([SCSI] make
> > scsi_wait_scan always modular) broke configurations where
> > SCSI_SCAN_ASYNC is selected for non-modular builds.
> >
> > Sig
On Tue, 2007-03-20 at 11:56 -0700, Andrew Vasquez wrote:
> Commit 840c2835a1c867281d27158378a9d34f593a7664 ([SCSI] make
> scsi_wait_scan always modular) broke configurations where
> SCSI_SCAN_ASYNC is selected for non-modular builds.
>
> Signed-off-by: Andrew Vasquez <[EMAIL PROTECTED]>
> ---
>
>
Commit 840c2835a1c867281d27158378a9d34f593a7664 ([SCSI] make
scsi_wait_scan always modular) broke configurations where
SCSI_SCAN_ASYNC is selected for non-modular builds.
Signed-off-by: Andrew Vasquez <[EMAIL PROTECTED]>
---
diff --git a/drivers/scsi/Kconfig b/drivers/scsi/Kconfig
index f3bc0f4..
On Tue, 2007-03-20 at 13:58 -0400, Douglas Gilbert wrote:
> I note at this point that the IMMED bit in the
> START STOP UNIT cdb is clear. [The code might
> note that as well.] All SCSI disks that I have
> seen, implement the IMMED bit and according to
> the SAT standard, so should SAT layers like
Tejun Heo wrote:
> Implement SBC START/STOP management. sdev->mange_start_stop is added.
> When it's set to one, sd STOPs the device on suspend and shutdown and
> STARTs it on resume. sdev->manage_start_stop defaults is in sdev
> instead of scsi_disk cdev to allow ->slave_config() override the
>
On Wed, 2007-03-21 at 02:08 +0900, Tejun Heo wrote:
> I got too comfortable with libata-dev#upstream and forgot to verify
> patches against scsi-misc-2.6. Sorry about that. If you don't have
> objection against the content, I'll resubmit the SCSI part against
> scsi-misc-2.6. Once it's in scsi-m
James Bottomley wrote:
> On Wed, 2007-03-21 at 00:13 +0900, Tejun Heo wrote:
>> Implement SBC START/STOP management. sdev->mange_start_stop is added.
>> When it's set to one, sd STOPs the device on suspend and shutdown and
>> STARTs it on resume. sdev->manage_start_stop defaults is in sdev
>> ins
On Wed, 2007-03-21 at 00:13 +0900, Tejun Heo wrote:
> Implement SBC START/STOP management. sdev->mange_start_stop is added.
> When it's set to one, sd STOPs the device on suspend and shutdown and
> STARTs it on resume. sdev->manage_start_stop defaults is in sdev
> instead of scsi_disk cdev to all
Am Dienstag, 20. März 2007 17:39 schrieb Alan Cox:
> > * sdev->manage_start_stop is set to 1 in ata_scsi_slave_config().
> > This fixes spindown on shutdown and suspend-to-disk.
>
> Yay
Which kernel version is this?
Regards
Oliver
-
To unsubscribe from this list: se
Stefan Priebe wrote:
> Hello!
>
> With the sysrq i've found the function with is the problem:
> inode.c => nfs_getattr => nfs_sync_mapping_range
>
> I've also found the attached patch - which is not included in any stable
> release nor in 2.6.21.X but is public since 20.02.07
>
> I think this is
Now that libata uses sd->manage_start_stop, libata spins down disk on
shutdown. In an attempt to compensate libata's previous shortcoming,
shutdown(8) syncs and spins down disks attached via libata. Some
disks spin back up just to spin down again on STANDBYNOW1 if the
command is issued when the d
> * DPM is dropped. This also simplifies code a lot. Suspend/resume
> status is port-wide now.
Makes sense
> * sdev->manage_start_stop is set to 1 in ata_scsi_slave_config().
> This fixes spindown on shutdown and suspend-to-disk.
Yay
> Signed-off-by: Tejun Heo <[EMAIL PROTECTED]>
Ac
On Wed, Mar 21, 2007 at 12:25:33AM +0900, Tejun Heo wrote:
> Reimplement suspend/resume support using sdev->manage_start_stop.
>
> * Device suspend/resume is now SCSI layer's responsibility and the
> code is simplified a lot.
Finally. I've been telling people to do it this way forever.
Can yo
Reimplement suspend/resume support using sdev->manage_start_stop.
* Device suspend/resume is now SCSI layer's responsibility and the
code is simplified a lot.
* DPM is dropped. This also simplifies code a lot. Suspend/resume
status is port-wide now.
* ata_scsi_device_suspend/resume() and a
Implement SBC START/STOP management. sdev->mange_start_stop is added.
When it's set to one, sd STOPs the device on suspend and shutdown and
STARTs it on resume. sdev->manage_start_stop defaults is in sdev
instead of scsi_disk cdev to allow ->slave_config() override the
default configuration but i
sd_sync_cache() should return -errno on error, fix it.
Signed-off-by: Tejun Heo <[EMAIL PROTECTED]>
---
drivers/scsi/sd.c |4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
Index: work/drivers/scsi/sd.c
===
--- work.orig/dr
This patch binds bsg devices to request_queue instead of gendisk. Any
objects (like transport entities) can define own request_handler and
create own bsg device.
Signed-off-by: FUJITA Tomonori <[EMAIL PROTECTED]>
---
block/bsg.c| 37 +
block/ll_rw
bsg uses scsi_cmd_ioctl() for some SCSI/sg ioctl
commands. scsi_cmd_ioctl() gets a request queue from a gendisk
arguement. This prevents bsg being bound to SCSI devices that don't
have a gendisk (like OSD). This adds a request_queue argument to
scsi_cmd_ioctl(). The SCSI/sg ioctl commands doesn't u
This patch binds bsg to all SCSI devices (their request queues) like
the current sg driver does. We can send SCSI commands to non disk and
cdrom scsi devices like OSD via bsg.
This patch removes bsg_register_queue from blk_register_queue so bsg
devices aren't bound to non SCSI block devices. If th
Hello!
With the sysrq i've found the function with is the problem:
inode.c => nfs_getattr => nfs_sync_mapping_range
I've also found the attached patch - which is not included in any stable
release nor in 2.6.21.X but is public since 20.02.07
I think this is very important.
Stefan Priebe
comm
> - on a 2.6.20 system, try "dd if=/dev/sdb of=/dev/null bs=4k count=1" or
>something like this (with NFS root) - does this crash, too?
no it does not crash it is also no problem to set the count= to 1 or
so or change the bs to 16k ...
> - do you have ACLs on files in /dev?
no
> - e
Hello!
Here a some more information:
- sometimes the whole systems crash - sometimes they are still alive
- if they are alive fdisk consumes 99% CPU
- fdisk cannot be killed also not with kill -9
- the same happens with a cat on /dev/sdX
- no problem when trying to access /dev/hdX
Stefan
Olaf K
Hello!
It runs with nfsroot
# mount
192.168.0.100:/PXE/debian on / type nfs (rw)
Kernel command line: nfs root=/dev/nfs nfsroot=192.168.0.100:/PXE/debian
ip=dhcp
Stefan
Olaf Kirch schrieb:
On Tuesday 20 March 2007 11:33, Stefan Priebe wrote:
1.) I've bootet these systems through NFS and w
On Tuesday 20 March 2007 11:33, Stefan Priebe wrote:
> 1.) I've bootet these systems through NFS and would like to access
> /dev/sda or /dev/sdb then. For example via fdisk and this does not work.
What do you mean by "booted through NFS"? Do you mean the machine
runs with the root file system moun
Hello!
Here are more informations... the problem seems to be a little bit more
special.
1.) I've bootet these systems through NFS and would like to access
/dev/sda or /dev/sdb then. For example via fdisk and this does not work.
2.) I've now tested the following kernels -
2.6.18.8 - works
2.
34 matches
Mail list logo
