Hi,
I've recently been trying install Linux on to a piece of hardware I picked up
and I've noticed this error in the dmesg output when the kernel is loading. The
error can be produced in version 0.1.36 and 0.1.37 of the pm8001 module. I was
hoping that when I updated it, I might be able to
On 13-12-10 02:32 AM, Newtech Tan wrote:
For example of bsg device node name:
[4:0:0:0]
Each field is Hex or Dec?
[BackGroup]
I am using lsscsi -g command to get SCSI device list as the following.
If bsg device name's target number field is over ten, Will it display
[4:0:10:0] or [4:0:a:0]?
Hi,
The following patch is a fix for the timeout/delay passed to
scheduled_delayed_work.
Regards,
Shivaram U
commit 1e0ea25bb6c834c1f4b2485f49d36a6c314cb7a4
Author: Shivaram U shivara...@quadstor.com
Date: Tue Dec 10 15:38:14 2013 +0530
Fix schedule_delayed_work() timeout calculations
Hi all,
this patchset updates the SCSI stack to support full 64-bit LUNs.
The first patch is a simple fix; the next two patches update
the sequential scan logic to be compliant with SPC.
The last two patches update the SCSI stack and all drivers
to use 64-bit LUNs where appropriate.
The patchset
Sequential scan for more than 256 LUNs is very fragile as
LUNs might not be numbered sequentially after that point.
SAM revisions later than SCSI-3 impose a structure on
LUNs larger than 256, making LUN numbers between 256
and 16384 illegal.
SCSI-3, however allows for plain 64-bit numbers with
no
Obsolete; either use 'max_lun' if the host supports only a
limited number of LUNs or BLIST_NOLUN if the target has
problems addressing more than one LUN.
Signed-off-by: Hannes Reinecke h...@suse.de
---
drivers/scsi/Kconfig | 14 --
drivers/scsi/dc395x.c| 9 +
Now that we're using 64-bit LUNs internally we need to increase
the size of max_luns to 64 bits, too.
Signed-off-by: Hannes Reinecke h...@suse.de
---
drivers/message/i2o/i2o_scsi.c | 2 +-
drivers/scsi/cxgbi/libcxgbi.c| 2 +-
drivers/scsi/cxgbi/libcxgbi.h| 2 +-
Older HBAs are only capable of supporting 16-bit LUNs,
so we need to make sure to adjust the 'ql2xmaxlun'
parameter accordingly.
Cc: Chad Dupuis chad.dup...@qlogic.com
Signed-off-by: Hannes Reinecke h...@suse.de
---
drivers/scsi/qla2xxx/qla_os.c | 5 +
1 file changed, 5 insertions(+)
diff
On 11/28/2013 02:29 PM, Aleksey Dashevsky wrote:
Hannes,
thanks a lot for your detailed response. It would be really great
if you can give access to your local git repository with all these
patches -- I'm mainly interested in 64-bit LUNs stuff right now,
but I'm pretty sure improvements
On Monday, December 09, 2013 8:47 PM Williams, Dan J dan.j.willi...@intel.com
wrote:
Remove an erroneous BUG_ON() in the case of a hard reset timeout. If a
SATA device is unable to restore the link in time we expect the port to
go back to the awaiting link-up state. Since the timeout path
Hi Niall,
Please update the firmware from
http://www.adaptec.com/en-us/support/sas/#sas_raid Adaptec Series 7 SAS/SATA 6
Gb - Host Bus Adapter section based on your card.
What is the current firmware version? You can get from the sys file
fw_version under /sys/devices.
Can you please try
https://bugzilla.kernel.org/show_bug.cgi?id=13783
Alan a...@lxorguk.ukuu.org.uk changed:
What|Removed |Added
Status|NEW |RESOLVED
https://bugzilla.kernel.org/show_bug.cgi?id=14572
Alan a...@lxorguk.ukuu.org.uk changed:
What|Removed |Added
Status|NEW |RESOLVED
https://bugzilla.kernel.org/show_bug.cgi?id=15561
Alan a...@lxorguk.ukuu.org.uk changed:
What|Removed |Added
Status|NEW |RESOLVED
https://bugzilla.kernel.org/show_bug.cgi?id=15567
Alan a...@lxorguk.ukuu.org.uk changed:
What|Removed |Added
Status|NEW |RESOLVED
https://bugzilla.kernel.org/show_bug.cgi?id=15623
Alan a...@lxorguk.ukuu.org.uk changed:
What|Removed |Added
CC||a...@lxorguk.ukuu.org.uk
On Tue, 10 Dec 2013, Hannes Reinecke wrote:
Older HBAs are only capable of supporting 16-bit LUNs,
so we need to make sure to adjust the 'ql2xmaxlun'
parameter accordingly.
Cc: Chad Dupuis chad.dup...@qlogic.com
Signed-off-by: Hannes Reinecke h...@suse.de
---
drivers/scsi/qla2xxx/qla_os.c |
https://bugzilla.kernel.org/show_bug.cgi?id=15950
Alan a...@lxorguk.ukuu.org.uk changed:
What|Removed |Added
Status|NEW |RESOLVED
https://bugzilla.kernel.org/show_bug.cgi?id=15950
ltski...@gmail.com changed:
What|Removed |Added
Status|RESOLVED|REOPENED
Resolution|OBSOLETE
https://bugzilla.kernel.org/show_bug.cgi?id=15950
Alan a...@lxorguk.ukuu.org.uk changed:
What|Removed |Added
Kernel Version|2.6.31 |3.5.3
--
You are
https://bugzilla.kernel.org/show_bug.cgi?id=15950
--- Comment #7 from Alan a...@lxorguk.ukuu.org.uk ---
No need - there is one obscure bug fix in early 2013, but nothing else since
2010. You may be the only person on the planet who still uses one!
--
You are receiving this mail because:
You are
https://bugzilla.kernel.org/show_bug.cgi?id=16547
Alan a...@lxorguk.ukuu.org.uk changed:
What|Removed |Added
Status|NEW |RESOLVED
https://bugzilla.kernel.org/show_bug.cgi?id=18652
Alan a...@lxorguk.ukuu.org.uk changed:
What|Removed |Added
Status|NEW |RESOLVED
https://bugzilla.kernel.org/show_bug.cgi?id=15950
--- Comment #8 from ltski...@gmail.com ---
Could be. Haven't found another inexpensive SCSI adapter.
I say the driver probably needs to get fixed or removed, though. No point in
having it in the kernel giving folks false hope that it'll work!
Jack, Suresh
Thanks for your response! Here's what I get from lspci - 30:00.0 Serial
Attached SCSI controller: PMC-Sierra Inc. Device 8001 (rev 05)
cat /sys/class/scsi_host/host7/version_product
PM8001
cat /sys/class/scsi_host/host7/version_fw
01.12.02.00
The Kernel version is
25 matches
Mail list logo
