From mboxrd@z Thu Jan 1 00:00:00 1970 From: Joern Quillman Subject: Re: Spinup of SCSI Disks: allow_restart won't work on 2.6.18 Date: Mon, 20 Nov 2006 23:32:21 +0100 Message-ID: <45622CF5.507@fbihome.de> References: <455DF39A.6090209@fbihome.de> <455E2D44.5030903@gmx.de> <455E4703.3080005@s5r6.in-berlin.de> <456188FD.3020108@fbihome.de> <45619611.5020502@s5r6.in-berlin.de> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-15; format=flowed Content-Transfer-Encoding: 7bit Return-path: Received: from moutng.kundenserver.de ([212.227.126.186]:19138 "EHLO moutng.kundenserver.de") by vger.kernel.org with ESMTP id S966409AbWKTWet (ORCPT ); Mon, 20 Nov 2006 17:34:49 -0500 In-Reply-To: <45619611.5020502@s5r6.in-berlin.de> Sender: linux-scsi-owner@vger.kernel.org List-Id: linux-scsi@vger.kernel.org To: Stefan Richter Cc: linux-scsi@vger.kernel.org Stefan Richter wrote >> One problem left. I still can't set or unset the flag with echo even on >> 2.6.19-rc6 (as root). Always getting a write error. Not that I care much >> about this, 'cause I for sure don't want it disabled. >> But it's strange nonethless. >> > > But the attribute has write permission set? (ls -l) > It is writable on the last kernel I tried, which is -rc4. > Yep Permissions of the file are -rw-r--r--. Owner is of course root. As I wrote before I can set/unset the flag without any problems when I connect a dumb USB<->IDE converter with kernel 2.6.18. Same with 2.6.19-rc6. The complete error message (sorry it's in german here) is: "-bash: echo: write error: Das Argument ist ungueltig" Is there a way to do some debug on the internals to see why the attribute isn't actually writeable? Do you need parts of the kernel log? A new problem just arised: When I switch on the external enclosure with 3 bridges and 3 disks a few seconds "before" I plug the firewire connector into the PC everything works. But when I first plug in the connector and turn on the external enclosure later, 2.6.19-rc6 hangs on the first disk and throws a BUG message. I have to reboot the PC then and I reproduced it serveral times. ------------------snip---------------------------------- ieee1394: Error parsing configrom for node 0-00:1023 ieee1394: Error parsing configrom for node 0-01:1023 ieee1394: Error parsing configrom for node 0-02:1023 ieee1394: Node changed: 0-00:1023 -> 0-03:1023 ieee1394: Node added: ID:BUS[0-00:1023] GUID[0001d20000091ab2] ieee1394: Node added: ID:BUS[0-01:1023] GUID[0001d20000093c4d] ieee1394: Error parsing configrom for node 0-02:1023 scsi0 : SBP-2 IEEE-1394 ieee1394: sbp2: Logged into SBP-2 device ieee1394: Node 0-00:1023: Max speed [S400] - Max payload [1024] scsi 0:0:0:0: Direct-Access-RBC Maxtor 4 D080H4 DAK0 PQ: 0 ANSI: 4 scsi1 : SBP-2 IEEE-1394 SCSI device sda: 160086528 512-byte hdwr sectors (81964 MB) sda: Write Protect is off sda: Mode Sense: 11 00 00 00 SCSI device sda: drive cache: write back SCSI device sda: 160086528 512-byte hdwr sectors (81964 MB) sda: Write Protect is off sda: Mode Sense: 11 00 00 00 SCSI device sda: drive cache: write back sda: sda1 sd 0:0:0:0: Attached scsi disk sda ieee1394: sbp2: Error logging into SBP-2 device - timed out sbp2: probe of 0001d20000093c4d-0 failed with error -16 ------------[ cut here ]------------ kernel BUG at fs/sysfs/file.c:460! invalid opcode: 0000 [#1] SMP Modules linked in: sd_mod nfs nfsd exportfs lockd nfs_acl sunrpc button ac battery ipv6 de4x5 dm_snapshot dm_mirror dm_mod sr_mod sbp2 scsi_mod ehci_hcd ohci_hcd tulip joydev tsdev pcmcia firmware_class evdev i810_audio ac97_codec psmouse serio_raw floppy snd_intel8x0 yenta_socket snd_ac97_codec snd_ac97_bus rsrc_nonstatic pcmcia_core snd_pcm snd_timer snd soundcore snd_page_alloc parport_pc parport i2c_piix4 pcspkr i2c_core rtc ext3 jbd mbcache ide_generic ide_cd cdrom ide_disk uhci_hcd piix generic ide_core usbcore ohci1394 ieee1394 thermal processor fan CPU: 0 EIP: 0060:[] Not tainted VLI EFLAGS: 00010202 (2.6.19-rc6 #1) EIP is at sysfs_create_file+0x19/0x31 eax: c7d03800 ebx: cc85f12c ecx: c7d038b0 edx: cc85f101 esi: cc85f12c edi: 00000000 ebp: c7d03800 esp: cb5f1eb8 ds: 007b es: 007b ss: 0068 Process knodemgrd_0 (pid: 549, ti=cb5f0000 task=cb595ab0 task.ti=cb5f0000) Stack: c7d03838 c021ed64 c7d03838 00000001 c7d03994 cc84f029 c7d03a14 00000014 cc853f32 cae3f0f4 00000000 cae3f000 fffffffc c7d03800 ccc6b000 00000000 00000000 cc84f45c fffffffc ccafd058 cae3f000 cb65d3f8 00000000 01afd058 Call Trace: [] device_create_file+0x1c/0x2b [] nodemgr_register_device+0xd0/0x150 [ieee1394] [] nodemgr_process_unit_directory+0x333/0x348 [ieee1394] [] nodemgr_probe_ne+0x183/0x37a [ieee1394] [] nodemgr_host_thread+0x827/0x970 [ieee1394] [] nodemgr_host_thread+0x0/0x970 [ieee1394] [] kthread+0xc2/0xf0 [] kthread+0x0/0xf0 [] kernel_thread_helper+0x7/0x10 ======================= Code: 83 c0 74 e8 65 08 10 00 89 e8 83 c4 10 5b 5e 5f 5d c3 85 c0 89 c1 53 89 d3 74 10 83 78 30 00 0f 94 c2 85 db 0f 94 c0 08 c2 74 08 <0f> 0b cc 01 d0 56 2b c0 8b 41 30 89 da b9 04 00 00 00 5b e9 5e EIP: [] sysfs_create_file+0x19/0x31 SS:ESP 0068:cb5f1eb8 ------------------------snip------------------------------------------------ Joern