dt1:uname -a
Linux dt1 3.19.0-33-generic #38~14.04.1-Ubuntu SMP Fri Nov 6 18:17:28
UTC 2015 x86_64 x86_64 x86_64 GNU/Linux
See attached for relevant kernel log.
I have the error:
blk_update_request: critical target error, dev sdb, sector 0
JBD2: recovery failed
EXT4-fs (sdb): error loading jou
Thanks! That worked. I was able to read & write. How to make that
permanent?
On 12/03/2015 10:00 AM, Alan Stern wrote:
On Thu, 3 Dec 2015, brad wrote:
dt1:uname -a
Linux dt1 3.19.0-33-generic #38~14.04.1-Ubuntu SMP Fri Nov 6 18:17:28
UTC 2015 x86_64 x86_64 x86_64 GNU/Linux
See atta
It seems to be permanent? After reboot I still have this and I can
mount the drive
dt1:cat /sys/block/sdb/device/scsi_disk/4\:0\:0\:0/cache_type
write through
On 12/03/2015 10:17 AM, brad wrote:
Thanks! That worked. I was able to read & write. How to make that
permanent?
On 1
mesg shows this now:
... [sdb] Assuming drive cache: write through
when before it always had this:
... [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO
or FUA
On 12/03/2015 11:30 AM, Alan Stern wrote:
On Thu, 3 Dec 2015, brad wrote:
It seems to be permanent? After
On Tue, Jan 22, 2013 at 02:51:08PM +0100, Jiri Kosina wrote:
> On Tue, 22 Jan 2013, Brad Tilley wrote:
>
> > > Could you please provide dmesg output from both working and non-working
> > > case?
> >
> > See attached. Two dmesgs from the same machine. One fro
it/balbi/usb into usb-testing").
Cc: # 4.19
Suggested-by: Christian Hewitt
Signed-off-by: Martin Blumenstingl
Fixed the issue on the Odroid C2 sbc with amlogic meson gxbb soc,
devices are now detected when connected after boot
Tested-by: Brad Harper
---
drivers/usb/dwc2/params.c | 1 +
1
Hey Sean,
On 13/08/2019 04.10, Sean Young wrote:
> Hi Brad,
>
> On Mon, Aug 12, 2019 at 10:21:39AM -0300, Ezequiel Garcia wrote:
>> On Sun, 2019-08-11 at 06:11 +0100, Sean Young wrote:
>>> syzbot reports an error on flush_request_modules() for the second device.
>
