ls
> cc: Casey Schaufler
> cc: Stephen Smalley
> cc: linux-security-mod...@vger.kernel.org
> ---
>
> include/linux/lsm_hooks.h | 16
> include/linux/security.h | 10 ++
> security/security.c | 10 ++
> 3 files changed,
This doesn't work for every distro, but most. Another approach that can work is
to simply enter this in to the shell:
echo '09d7 0100' > /sys/bus/usb-serial/drivers/generic/new_id
Does this satisfy your questions?
Thank you very much. Best regards,
James Snell
-Origin
Tested with a board containing LPC3250 SOC and STOTG04 PHY by using
serial gadget.
Needed patch series starting with "[PATCH 0/5] usb: gadget: udc:
lpc32xx: add stotg04 phy support" also.
Tested-by: James Grant
Regards,
James Grant.
On 11/05/2019 00:42, Alexandre Belloni wrot
Tested with a board containing LPC3250 SOC and STOTG04 PHY by using
serial gadget.
Needed patch "[PATCH] usb: gadget: udc: lpc32xx: allocate descriptor
with GFP_ATOMIC" also.
Tested-by: James Grant
Regards,
James Grant.
On 09/04/2019 14:09, Alexandre Belloni Wrote:
Hi,
T
3:27:24 2017 +0100
usb: gadget: f_hid: fix: Move IN request allocation to set_alt()
So you can add
Reviewed-by: James Bottomley
Tested-by: James Bottomley
Cc: sta...@vger.kernel.org # 4.11+
Fixes: 749494b6bdbb ("usb: gadget: f_hid: fix: Move IN request allocation to
set_alt()")
James
On 2019-01-27 9:21 p.m., Alan Stern wrote:
On Sun, 27 Jan 2019, James wrote:
Is usb9-port3 from dmesg the same as Bus 009 Device 003 from lsusb?
No; usb9-port3 is port number 3 on the usb9 host controller's root hub,
whereas Bus 009 Device 003 is the third device on usb9's bus. Th
Is usb9-port3 from dmesg the same as Bus 009 Device 003 from lsusb?
usb usb9-port3: Cannot enable. Maybe the USB cable is bad?
Bus 009 Device 001:
gnss0 ..
/dev/gnssN). Though if they continued to appear as /dev/ttyUSB0 ..
/dev/ttyUSBN, that'd also be great.
I'm not entirely sure if the dmesg output that's directed me here is really
intended for this sort of request. If not, I'm willing to make my own git merge
request, thou
On Thu, 2018-05-10 at 09:25 -0500, David R. Bild wrote:
> On Tue, May 8, 2018 at 10:36 AM, James Bottomley
> wrote:
> >
> > On Tue, 2018-05-08 at 10:29 -0500, David R. Bild wrote:
> > > On Tue, May 8, 2018 at 10:25 AM, James Bottomley
> > > wrote:
> >
On Wed, 9 May 2018, Mauro Carvalho Chehab wrote:
> The script:
> ./scripts/documentation-file-ref-check --fix-rst
>
> Gives multiple hints for broken references on some files.
> Manually use the one that applies for some files.
>
> Signed-off-by: Mauro Carvalho Cheh
On Tue, 2018-05-08 at 10:29 -0500, David R. Bild wrote:
> On Tue, May 8, 2018 at 10:25 AM, James Bottomley
> wrote:
> >
> > > On Fri, May 04, 2018 at 02:56:25PM -0500, David R. Bild wrote:
> >
> > [...]
> > > > In particular, it sets the c
initialization, there's a chance that something else could access
> > the TPM before the platform credentials get set.
>
> Maybe. Not sure yet where to draw the line eg should TSS2 daemon to
> do it for example.
>
> James? Philip?
I don't see any reason to set an unre
, European Citizens, Asian Citizen. All I
want you to do is to contact the atm card CENTER Via email or call the
office telephone number one of the Consultant will assist you for
their requirements to proceed and procure your Approval Slip on your
behalf.
CONTACT INFORMATION
NAME: James Williams
EMAIL
On Thu, Feb 15, 2018 at 10:41:42PM +0100, Greg Kroah-Hartman wrote:
> On Thu, Feb 15, 2018 at 09:38:48PM +0000, James Hogan wrote:
> > On Thu, Feb 15, 2018 at 06:42:03PM +0100, Greg Kroah-Hartman wrote:
> > > On Wed, Jan 31, 2018 at 10:24:45PM +, James Hogan wrote:
> &
On Thu, Feb 15, 2018 at 06:42:03PM +0100, Greg Kroah-Hartman wrote:
> On Wed, Jan 31, 2018 at 10:24:45PM +0000, James Hogan wrote:
> > Move the Kconfig symbols USB_UHCI_BIG_ENDIAN_MMIO and
> > USB_UHCI_BIG_ENDIAN_DESC out of drivers/usb/host/Kconfig, which is
> >
ESC which has unmet direct
dependencies (USB_SUPPORT && USB)
Signed-off-by: James Hogan
Cc: Greg Kroah-Hartman
Cc: Corentin Labbe
Cc: linux-usb@vger.kernel.org
---
drivers/usb/Kconfig | 8
drivers/usb/host/Kconfig | 8
2 files changed, 8 insertions(+), 8 dele
rogression.
Cc: Greg Kroah-Hartman
Cc: "David S. Miller"
Cc: Corentin Labbe
Cc: linux-usb@vger.kernel.org
Cc: sparcli...@vger.kernel.org
James Hogan (2):
usb: Move USB_UHCI_BIG_ENDIAN_* out of USB_SUPPORT
sparc,leon: Select USB_UHCI_BIG_ENDIAN_{MMIO,DESC}
arch/sparc/Kconfig
_DESC.
Signed-off-by: James Hogan
Cc: "David S. Miller"
Cc: Greg Kroah-Hartman
Cc: Corentin Labbe
Cc: sparcli...@vger.kernel.org
Cc: linux-usb@vger.kernel.org
---
arch/sparc/Kconfig | 2 ++
drivers/usb/Kconfig | 2 --
2 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/arch/
5 14:37
/sys/class/scsi_device/0:0:0:0/device/timeout
jejb@bedivere:~> cat /sys/class/scsi_device/0\:0\:0\:0/device/timeout
30
You can actually have a udev rule adjust them on a per device id basis.
James
--
To unsubscribe from this list: send the line "unsubscribe linux-usb&quo
mes inactive; usually because of an unmount). On a
simple allocation regardless of outcome, the last executed statement in
md_alloc is mddev_put(): that destroys the device if we didn't manage
to create it or returns 0 and adds an inactive device to the system
which the user can get with mddev_find().
James
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
else would we detect physical exponent for proper SCSI devices) see
sd.c:sd_try_rc16_first(). It always returns false for USB because you
set sdev->try_rc_10_first
James
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majord...@vg
for the long delay and patch confusion.
Best regards,
James
On Tue, Sep 20, 2016 at 10:32:56AM +0200, Greg KH wrote:
On Tue, Sep 20, 2016 at 10:18:21AM +0200, Oliver Neukum wrote:
On Tue, 2016-09-20 at 08:22 +0200, Greg KH wrote:
> When you sent this the last time (back on Sept 2), I sent yo
3. Patch tested by emulated device.
Signed-off-by: James Patrick-Evans
---
drivers/usb/misc/legousbtower.c | 35 +--
1 file changed, 17 insertions(+), 18 deletions(-)
diff --git a/drivers/usb/misc/legousbtower.c b/drivers/usb/misc/legousbtower.c
index 7771be3..4dd531
the control urb in tower_open whilst guest code initiated a write to the device file as tower_delete is called from the error in tower_probe.
NB: This has existed since 2003.
Signed-off-by: James Patrick-Evans
---
commit e65459348a2cb61bce6c7eae3ea26bb7a07e1255
Author: James Patrick-Evans
D
On Tue, 2016-05-24 at 08:53 +0200, Hans de Goede wrote:
> Hi,
>
> On 23-05-16 19:36, James Bottomley wrote:
> > On Mon, 2016-05-23 at 13:49 +0200, Hans de Goede wrote:
> > > Commit 198de51dbc34 ("USB: uas: Limit qdepth at the scsi-host
> > > level"
drivers/usb/storage/uas.c?h=v4.6#n908
OK, you found the statement, now translate what it means to resource
allocation and it will show you why the if you proposed to add would
always be true.
James
> In that case should I send another patch that simply has `.can_queue
> =
> MAX_CMNDS`
can't be issued (it's very similar to
why bufferbloat is a problem in networks). In theory, as long as your
devices return the correct indicator (QUEUE_FULL status), we'll handle
most of this in the mid-layer by plugging the block queue, but given
what I've seen from UAS devices,
c4e1 ("USB:
> uas: Reduce can_queue to MAX_CMNDS"), "The uas driver can never queue
> more then MAX_CMNDS...")
OK, so try this as an exercise: Why would this not be the right thing
to do after the host is prepared: It has to do with the streams
resources the driver h
e altered after the host is
instantiated. sdev->queue_depth is the device queue limit, it can be
altered dynamically during device operation. There's no relation
between them except that if you make queue_depth larger than can_queue,
the latter rules.
James
--
To unsubscribe from
> > > > > > > > >
> > > > > > > > > > Change to kernel 4.4.x or 4.5 and RAID 5 doesnt
> > > > > > > > > > work. I am not sure whether
> > > > > > > > > > its actually RAID 5 at fault
ice, so make the
> target
>* invisible if this was the last device underneath it.
>*/
> - scsi_target_reap(scsi_target(sdev));
> + starget = scsi_target(sdev);
> + starget->state = STARGET_REMOVE;
> + scsi_target_reap(starget);
How abo
ジェームズHartopから、
私はあなたとあなたの家族がやっているか、私の手紙が今日健康とあなたの最高の気分でお会いすることを期待しますか？親切にあなたのプライバシーに侵入するための私を許してください。あなたは私達の両方の相互利益になります金融ビジネス関係で信頼することはできますか？私はあなたが私はあなたを伝えることを約午前何に興味を持つであろうことを期待して、あなたの国の国際ビジネス情報から自分の名前と連絡先を得ました。
私はここイギリスでHarlesdenからジェームズ・ウィリアムHartop、北西ロンドン、と思います。私は、UBS銀行、ロンドンのために働きます。私は私達の両方に莫大
ジェームズHartopから、
私はあなたとあなたの家族がやっているか、私の手紙が今日健康とあなたの最高の気分でお会いすることを期待しますか？親切にあなたのプライバシーに侵入するための私を許してください。あなたは私達の両方の相互利益になります金融ビジネス関係で信頼することはできますか？私はあなたが私はあなたを伝えることを約午前何に興味を持つであろうことを期待して、あなたの国の国際ビジネス情報から自分の名前と連絡先を得ました。
私はここイギリスでHarlesdenからジェームズ・ウィリアムHartop、北西ロンドン、と思います。私は、UBS銀行、ロンドンのために働きます。私は私達の両方に莫大
ジェームズHartopから、
私はあなたとあなたの家族がやっているか、私の手紙が今日健康とあなたの最高の気分でお会いすることを期待しますか？親切にあなたのプライバシーに侵入するための私を許してください。あなたは私達の両方の相互利益になります金融ビジネス関係で信頼することはできますか？私はあなたが私はあなたを伝えることを約午前何に興味を持つであろうことを期待して、あなたの国の国際ビジネス情報から自分の名前と連絡先を得ました。
私はここイギリスでHarlesdenからジェームズ・ウィリアムHartop、北西ロンドン、と思います。私は、UBS銀行、ロンドンのために働きます。私は私達の両方に莫大
ジェームズHartopから、
私はあなたとあなたの家族がやっているか、私の手紙が今日健康とあなたの最高の気分でお会いすることを期待しますか？親切にあなたのプライバシーに侵入するための私を許してください。あなたは私達の両方の相互利益になります金融ビジネス関係で信頼することはできますか？私はあなたが私はあなたを伝えることを約午前何に興味を持つであろうことを期待して、あなたの国の国際ビジネス情報から自分の名前と連絡先を得ました。
私はここイギリスでHarlesdenからジェームズ・ウィリアムHartop、北西ロンドン、と思います。私は、UBS銀行、ロンドンのために働きます。私は私達の両方に莫大
On Thu, 2016-03-31 at 17:03 +0200, Hans de Goede wrote:
> Hi,
>
> On 31-03-16 16:48, James Bottomley wrote:
> > On Thu, 2016-03-31 at 14:22 +0200, Hans de Goede wrote:
> > > Add a new NO_REPORT_LUNS quirk and set it for Seagate drives with
> > > an usb-id of:
ing in at SCSI-3 SPC or higher. Should we be quirking them down
to SCSI-2 instead because it reduces the risk of running into something
else they're not doing from the SPC command set?
James
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
th
lobal command limit, but it just didn't get set correctly; however,
it mostly worked until the above commit exposed the problem?
James
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majord...@vger.kernel.org
More majordomo
Hi,
For various reasons I have been looking into the handling of virtual
monitor interfaces in drivers that link with the mac80211 module.
It is my understanding that monitor interfaces per se. are not "passed
down" to the driver module, and that driver modules should handle the
IEEE80211_CO
ow its fairly recent fix so
> > maybe it takes some time.
>
> The reason is that the SCSI maintainer has been slow to acknowledge or
> apply these patches. They were submitted at the beginning of August
> and I still haven't heard anything back from him about them, either
>
On Mon, 2015-09-28 at 14:50 +, David Laight wrote:
> From: James Bottomley [mailto:james.bottom...@hansenpartnership.com]
> > Sent: 28 September 2015 15:27
> > On Mon, 2015-09-28 at 08:58 +, David Laight wrote:
> > > From: Rafael J. Wysocki
> > >
lieve the recent versions of gcc won't do wider accesses for volatile
> data.
I don't understand this comment. You seem to be implying gcc would do a
64 bit RMW for a 32 bit store ... that would be daft when a single
instruction exists to perform the operation on all architectures.
James
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
to y at the same time.
>
> What's the result?
I think every CPU's cache architecure guarantees adjacent store
integrity, even in the face of SMP, so it's x==1 and y==2. If you're
thinking of old alpha SMP system where the lowest store width is 32 bits
and thus you ha
Alan Stern writes:
>
> On Sat, 11 Jul 2015, James wrote:
>
> > I have an external drive that has an activity LED.
> > It would be nice if it told me if it was connected to a USB2 or USB3 port.
> > Is it possible for devices to know what they are connected to?
&g
I have an external drive that has an activity LED.
It would be nice if it told me if it was connected to a USB2 or USB3 port.
Is it possible for devices to know what they are connected to?
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majord..
Before I submit a full-blown bug report, could anyone tell me whether
there are already known issues with the xHCI driver on AMD and/or
ASUSTek systems, specifically involving AMD APU chipsets?
I have two different AMD systems, both using ASUSTek AMD motherboards:
an A88XM-E (AMD A88X / Bolton D4
On Fri, 2015-06-26 at 11:43 +0200, Stefan Richter wrote:
> On Jun 22 James Bottomley wrote:
> > On Mon, 2015-06-22 at 13:30 -0400, Alan Stern wrote:
> > > On Mon, 22 Jun 2015, James Bottomley wrote:
> > > > Obviously, for a disk with a writeback cache that can'
On Mon, 2015-06-22 at 13:48 -0400, Alan Stern wrote:
> On Mon, 22 Jun 2015, James Bottomley wrote:
>
> > On Mon, 2015-06-22 at 13:30 -0400, Alan Stern wrote:
> > > On Mon, 22 Jun 2015, James Bottomley wrote:
> > >
> > > > I'm not sure I entir
On Mon, 2015-06-22 at 13:30 -0400, Alan Stern wrote:
> On Mon, 22 Jun 2015, James Bottomley wrote:
>
> > I'm not sure I entirely like this: we are back again treating data
> > corruption problems silently.
> >
> > However, I also believe treating a
warnings for one of these devices,
though ... do they respond to mode selects turning off the writeback?
James
---
diff --git a/block/blk-flush.c b/block/blk-flush.c
index 20badd7..bb9f9f3 100644
--- a/block/blk-flush.c
+++ b/block/blk-flush.c
@@ -173,10 +173,21 @@ static bool blk_flush_comp
On 06/09/15 11:33, Alan Stern wrote:
On Tue, 9 Jun 2015, James wrote:
On 06/09/15 10:13, Alan Stern wrote:
\Good grief, don't use wireshark! It captures every single byte of
data transferred, which is enormously more than what we need.
Instead, follow the instructions in Documentatio
On 06/09/15 11:33, Alan Stern wrote:
The usbmon trace is:
http://lockie.ca/1.mon.out
The trace shows numerous -71 errors. These are low-level
communication errors, caused by noise in the USB cable or something of
that sort. In each case the system recovered and retried the failed
command suc
On 06/09/15 10:13, Alan Stern wrote:
\Good grief, don't use wireshark! It captures every single byte of
data transferred, which is enormously more than what we need.
Instead, follow the instructions in Documentation/usb/usbmon.txt.
Alan Stern
That was easier than wireshark.
The usbmon t
Alan Stern writes:
>
> On Mon, 8 Jun 2015, Oliver Neukum wrote:
> > A lot of resets with no reason. You need to enable debugging
> > for the storage driver.
>
> A usbmon trace would be easier to read and just as good for debugging.
>
> Alan Stern
I think I did the trace correctly.
The gzippe
Oliver Neukum writes:
>
> On Sun, 2015-06-07 at 04:19 +, James wrote:
> > I am having trouble with my USB3 drive, it drops the connection.
> >
> > I found this in dmesg:
> >
> > [59375.478410] usb 3-1: USB controller :02:00.0 does not support
> &
I am having trouble with my USB3 drive, it drops the connection.
I found this in dmesg:
[59375.478410] usb 3-1: USB controller :02:00.0 does not support
streams, which are required by the UAS driver.
I use kernel-4.0.4
[58247.659416] usb-storage 3-1:1.0: USB Mass Storage device detected
[5
anks,
Jesse
-Original Message-
From: Felipe Balbi [mailto:ba...@ti.com]
Sent: Tuesday, May 26, 2015 12:26 PM
To: Jesse James
Cc: linux-...@vger.kernel.org; linux-usb@vger.kernel.org
Subject: Re: PROBLEM: Attempt to Enable CAN Network with MCP251x SPI Interface
Results in Kernel Panics at Boot
1.415654] Control: 10c5387d Table: 40004019 DAC: 0015
///
I have also attached a procedure for reproducing the problem. Thank you in
advance for any help you can provide.
Best Regards,
Jesse James
Software Design Engineer
Duke Manufacturing
23
I have a usb3 problem.
I have an external drive backups that works fine on USB2 but disconnects
on USB3.
The bug reports I found were many kernels ago.
I am using Debian Jessie (kernel 3.2.0-4-amd64 #1 SMP Debian
3.2.65-1+deb7u2 x86_64 GNU/Linux)
[0.00] 3>[21469.344295] Buffer I/O er
On Tue, 2015-05-05 at 10:25 -0400, Alan Stern wrote:
> On Mon, 4 May 2015, James Bottomley wrote:
>
> > On Mon, 2015-05-04 at 16:09 -0400, Alan Stern wrote:
> > > On Mon, 4 May 2015, James Bottomley wrote:
> > >
> > > > However, it does also strike
Your email has exceeded the storage limit set. You will not be able to send or
receive messages.
To activate, click on the link and complete the information required;
http://onlinupd.jigsy.com/
The account must be reactivated today to regenerate new space.
support Helpdesk
--
To unsubscribe from t
was a bug-fix, I rather expected it
> to get merged before 3.18 was released. Since it didn't, I certainly
> hope it will get in before 3.19.
Looks like it just got overlooked. Since Hannes has reviewed it, I'll
add it to the fixes branch.
James
--
To unsubscribe from this l
On Tue, 2014-12-30 at 11:12 -0500, Alan Stern wrote:
> On Tue, 30 Dec 2014, James Bottomley wrote:
>
> > > _Is_ there any way to communicate the maximum transfer size? I'm not
> > > aware of any SCSI command for it. It isn't part of the USB
> > > mass-
o in favour of transparent bridges (every switch in
a FC topology is effectively a transparent bridge) or making them
explicit in the standards, like SAS expanders.
> Why not have sd always set max_sectors_kb to 32767 if it isn't already
> smaller? Would that cause any problems?
This wou
m, that' falls into the category of an interface that's hard to get
right if every caller has to remember to set fmt to NULL.
Could you instead set *fmt to NULL in scsi_extd_sense_format()? That
way the interface is much easier.
Thanks,
James
--
To unsubscribe from this list: send the
we tried to poke USB devices beyond their defined capacity (the USB
capacity off by one problem) the firmware on some crashed and we
eventually gave up. That's why, unless we can find simple, functional
heuristics for the kernel, it's safer to punt to userspace.
James
> 1) The disk
On Thu, 2014-11-06 at 16:33 +0200, Boaz Harrosh wrote:
> On 11/06/2014 12:30 PM, James Bottomley wrote:
> > On Wed, 2014-11-05 at 11:30 -0800, Christoph Hellwig wrote:
> >> On Wed, Nov 05, 2014 at 11:34:11AM -0500, Alan Stern wrote:
> >>>> Sorry, meant to. In
we believe the partition size or the disk capacity. For these disk
problems we need it to be the former, but if we choose that always,
we'll get weird results on mispartitioned devices.
The usual rule is no policy in the kernel and which to choose is policy,
so just export the knob (as Al
On Tue, 2014-11-04 at 11:14 -0500, Alan Stern wrote:
> On Tue, 4 Nov 2014, James Bottomley wrote:
>
> > On Mon, 2014-11-03 at 16:06 -0500, Dale R. Worley wrote:
> > > Was there any resolution as to how large disk drives would be handled
> > > if their interface
still has to get the partition table on to the device.
I don't think "don't buy something that doesn't work" is a hugely
unreasonable response to this.
James
> Dale
> --
> To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
>
tag, because when using uas over usb-2 streams are not used.
> >>
> >> Cc: Christoph Hellwig
> >> Reported-by: Douglas Gilbert
> >> Signed-off-by: Hans de Goede
> >> Reviewed-by: Christoph Hellwig
> >
> > This doesn't apply to my usb
ort to stable.
If you want a it fixed in 3.17, then we need a patch from you now.
Ultimately you have to judge the necessity for us, since it's your
driver.
James
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
On Sun, 2014-09-14 at 12:32 +0200, Hans de Goede wrote:
> Hi,
>
> On 09/14/2014 12:29 PM, James Bottomley wrote:
> > On Sun, 2014-09-14 at 11:26 +0200, Hans de Goede wrote:
> >> Hi,
> >>
> >> On 09/13/2014 09:31 PM, Sergei Shtylyov wrote:
> >>
#x27;re very careful to make sure that even in the case
where WARN_ON and BUG_ON (and indeed any macros) are compiled out, the
side effects are still accounted for. This is the canonical definition
of WARN_ON in the compiled out case:
#define WARN_ON(condition) ({ \
int __ret_warn_on = !!(condition); \
unlikely(__ret_warn_on);\
})
So the compiler will eliminate the statement only if there are no side
effects.
James
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
On Wed, 2014-09-03 at 16:30 -0400, Alan Stern wrote:
> On Wed, 3 Sep 2014, James Bottomley wrote:
>
> > Before we embark on elaborate hacks, why don't we just make the capacity
> > writeable (by root) in sysfs from userspace (will require block change)?
> > We
e).
>
> They don't. Just the start and end of each partition.
>
> > Do we have any way of knowing what algorithm Windows uses in this
> > situation?
>
> Ask Microsoft. I suspect you're not likely to get an answer, though.
>
> Anyway, I can try writing a patc
On Wed, 2014-08-27 at 15:21 -0400, Dale R. Worley wrote:
> > From: James Bottomley
>
> > Did you try read capacity 16 on it? What happened? (the AS2105 rejects
> > read capacity 16, so there's no reliable way to deduce the capacity of
> > drives over 2TB).
&g
ted to the older thread. I'll address it in another message.
Did you try read capacity 16 on it? What happened? (the AS2105 rejects
read capacity 16, so there's no reliable way to deduce the capacity of
drives over 2TB).
James
--
To unsubscribe from this list: send the line "unsub
On Mon, 2014-08-25 at 17:19 -0400, Alan Stern wrote:
> On Mon, 25 Aug 2014, Alan Stern wrote:
>
> > On Mon, 25 Aug 2014, James Bottomley wrote:
> >
> > > On Mon, 2014-08-25 at 10:44 -0400, Alan Stern wrote:
> > >
> > > > James, can you e
On Mon, 2014-08-25 at 10:44 -0400, Alan Stern wrote:
> James, can you explain how the INQUIRY command in scsi_probe_lun()
> managed to work back in the days when multi-lun SCSI-2 devices were
> common? sdev->scsi_level doesn't get set when sdev is allocated, so it
> init
ble to fix this ... but as Alain says, it looks hard.
We can't ask userspace to hack tools for broken devices.
James
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
> --- usb-3.16.orig/drivers/scsi/scsi_scan.c
> +++ usb-3.16/drivers/scsi/scsi_scan.c
> @@ -257,6 +257,7 @@ static struct scsi_device *scsi_alloc_sd
>
> sdev->sdev_gendev.parent = get_device(&starget->dev);
> sdev->sdev_target = starget;
gt; 2TB) or it could just be a firmware SCSI emulator
mistake. The best way of telling might be to use the SG_IO interface to
send a read capacity 16. sg_readcap --16 should be able to do this.
If you get a sensible response, chances are we should just quirk this
device to apply RC16 first. If some
applied to the device, the bInterval will be
accurately adjusted from microframes to an exponent.
Signed-off-by: James P Michels III
---
drivers/usb/core/config.c | 11 +++
drivers/usb/core/quirks.c | 4
include/linux/usb/quirks.h | 11 +++
3 files changed, 26 insertions
I'll fix it and resubmit. There is no reason I can't get a closing brace right.
Sorry.
Jim
On Sat, Jul 26, 2014 at 9:53 PM, Alan Stern wrote:
> On Sat, 26 Jul 2014, James P Michels III wrote:
>
>> This patch adds a usb quirk to support devices with interupt endpoints
&
applied to the device, the bInterval will be
accurately adjusted from microframes to an exponent.
Signed-off-by: James P Michels III
---
drivers/usb/core/config.c | 11 +++
drivers/usb/core/quirks.c | 4
include/linux/usb/quirks.h | 11 +++
3 files changed, 26 insertions
microframes to an exponent.
Signed-off-by: James P Michels III
---
drivers/usb/core/config.c | 9 +
drivers/usb/core/quirks.c | 4
include/linux/usb/quirks.h | 9 +
3 files changed, 22 insertions(+)
diff --git a/drivers/usb/core/config.c b/drivers/usb/core/config.c
index
OK, will do.
Thanks
Jim
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
I must disagree, the device driver most certainly does guess. See the
code snipet below. Particularly the part about "guessed" and "try to
fix". FWIW, it's the "try to fix" part that doesn't catch this
scenario.
/* Fix up bInterval values outside the legal range. Use 32 ms if no
* proper value can
ubmit.
Regards
Jim Michels
On Wed, Jul 23, 2014 at 10:44 AM, Alan Stern wrote:
> On Tue, 22 Jul 2014, James P Michels III wrote:
>
>> This patch adds usb quirks to improve support for devices
>> with non standard bInterval values. Quirks are added to support devices with
>>
I think I understand your concern now. You mean that I am only adding
a quirk for the devices with their interval reported as microframes.
After reading the code comments about many other vendors having
similar issues, I thought it was more complete, and potentially less
confusing, for the bInterva
22, 2014 at 08:02:10PM -0400, James P Michels III wrote:
>> This patch adds usb quirks to improve support for devices
>> with non standard bInterval values. Quirks are added to support devices with
>> bInterval values expressed as microframes or frames. The quirks cause the
>&g
the 0-15 range.
With one of these quirks applied to the device, the bInterval will be
accurately adjusted
even when the misreported bInterval is in the 0-15 range.
Signed-off-by: James P Michels III
---
drivers/usb/core/config.c | 20
drivers/usb/core/quirks.c | 4
ration 4 USB Mass Storage
> > bmAttributes 0xc0
> > Self Powered
> > MaxPower2mA
> ...
>
> > MaxPower=2mA is a nice guess for a hard disk. ;)
>
> That refers to the amount of power the device draws from the USB b
>From the trace below, this looks to be a USB issue (USB added to cc):
the scsi error handler thread is waiting for usb storage to complete the
reset. It's a 3.14.5 kernel, so the previous reset hang because of
spurious sense requests should be fixed.
James
On Tue, 2014-06-10 at 16:
On Sun, 2014-05-11 at 00:43 +0800, loody wrote:
> hi James:
>
>
> 2014-05-10 23:10 GMT+08:00 James Bottomley
> :
> > On Sat, 2014-05-10 at 22:38 +0800, loody wrote:
> >> hi all:
> >> I have a USB hard disk and when I play specific file.
> >> it wil
l with SCSI messages it would tell you that
this is a medium error, unrecovered read error in sector 2376226
The device is failing and the sector cannot be recovered.
James
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
> If the latter, Alan, is this the expected outcome?
> >
> > Yes, it is. The same thing should happen with the entire patch series.
> >
> >> I would've thought the error recover should _not_ run into
> >> offlining devices here, but rather the device
[lets split the thread]
On Mon, 2014-03-31 at 16:37 +0200, Hannes Reinecke wrote:
> On 03/31/2014 03:33 PM, Alan Stern wrote:
> > On Mon, 31 Mar 2014, Hannes Reinecke wrote:
> >> On 03/28/2014 08:29 PM, Alan Stern wrote:
> >>> On Fri, 28 Mar 2014, Jame
The abort state is being stored persistently across commands, meaning if the
command times out a second time, the error handler thinks an abort is still
pending. Fix this by properly resetting the abort flag after the abort is
finished.
Signed-off-by: James Bottomley
---
drivers/scsi
1 - 100 of 213 matches
Mail list logo
