Ming Lei wrote:
> On Thu, Apr 12, 2018 at 09:43:02PM -0400, Wakko Warner wrote:
> > Ming Lei wrote:
> > > On Tue, Apr 10, 2018 at 08:45:25PM -0400, Wakko Warner wrote:
> > > > Sorry for the delay. I reverted my change, added this one. I didn't
> > > &
Ming Lei wrote:
> On Tue, Apr 10, 2018 at 08:45:25PM -0400, Wakko Warner wrote:
> > Sorry for the delay. I reverted my change, added this one. I didn't
> > reboot, I just unloaded and loaded this one.
> > Note: /dev/sr1 as seen from the initiator is /dev/sr0 (physic
Wakko Warner wrote:
> Ming Lei wrote:
> > Sure, thanks for your sharing.
> >
> > Wakko, could you test the following patch and see if there is any
> > difference?
> >
> > --
> > diff --git a/drivers/target/target_core_pscsi.c
> > b/driver
Ming Lei wrote:
> Sure, thanks for your sharing.
>
> Wakko, could you test the following patch and see if there is any
> difference?
>
> --
> diff --git a/drivers/target/target_core_pscsi.c
> b/drivers/target/target_core_pscsi.c
> index 0d99b242e82e..6147178f1f37 100644
> --- a/drivers/target/ta
Ming Lei wrote:
> On Mon, Apr 09, 2018 at 09:30:11PM +, Bart Van Assche wrote:
> > Hello Ming,
> >
> > Can you have a look at this? The start of this e-mail thread is available at
> > https://www.mail-archive.com/linux-scsi@vger.kernel.org/msg72574.html.
>
> Sure, thanks for your sharing.
>
Wakko Warner wrote:
> Bart Van Assche wrote:
> > Have you tried to modify the kernel Makefile as indicated in the following
> > e-mail? This should make the kernel build:
> >
> > https://lists.ubuntu.com/archives/kernel-team/2016-May/077178.html
>
> Thanks. That
Bart Van Assche wrote:
> On Sat, 2018-04-07 at 12:53 -0400, Wakko Warner wrote:
> > Bart Van Assche wrote:
> > > On Thu, 2018-04-05 at 22:06 -0400, Wakko Warner wrote:
> > > > I know now why scsi_print_command isn't doing anything. cmd->cmnd is
> &g
Wakko Warner wrote:
> Bart Van Assche wrote:
> > On Thu, 2018-04-05 at 22:06 -0400, Wakko Warner wrote:
> > > I know now why scsi_print_command isn't doing anything. cmd->cmnd is
> > > null.
> > > I added a dev_printk in scsi_print_command where t
Bart Van Assche wrote:
> On Thu, 2018-04-05 at 22:06 -0400, Wakko Warner wrote:
> > I know now why scsi_print_command isn't doing anything. cmd->cmnd is null.
> > I added a dev_printk in scsi_print_command where the 2 if statements return.
> > Logs:
> > [ 29.86
Bart Van Assche wrote:
> On Thu, 2018-04-05 at 22:06 -0400, Wakko Warner wrote:
> > I know now why scsi_print_command isn't doing anything. cmd->cmnd is null.
> > I added a dev_printk in scsi_print_command where the 2 if statements return.
> > Logs:
> > [ 29.86
Bart Van Assche wrote:
> On Thu, 2018-04-05 at 22:06 -0400, Wakko Warner wrote:
> > I know now why scsi_print_command isn't doing anything. cmd->cmnd is null.
> > I added a dev_printk in scsi_print_command where the 2 if statements return.
> > Logs:
> > [ 29.86
Wakko Warner wrote:
> Bart Van Assche wrote:
> > On Sun, 2018-04-01 at 14:27 -0400, Wakko Warner wrote:
> > > Wakko Warner wrote:
> > > > Wakko Warner wrote:
> > > > > I tested 4.14.32 last night with the same oops. 4.9.91 works fine.
> > > &g
Bart Van Assche wrote:
> On Sun, 2018-04-01 at 14:27 -0400, Wakko Warner wrote:
> > Wakko Warner wrote:
> > > Wakko Warner wrote:
> > > > I tested 4.14.32 last night with the same oops. 4.9.91 works fine.
> > > > From the initiator, if I do cat /dev/sr1
Bart Van Assche wrote:
> On Sun, 2018-04-01 at 14:27 -0400, Wakko Warner wrote:
> > Wakko Warner wrote:
> > > Wakko Warner wrote:
> > > > I tested 4.14.32 last night with the same oops. 4.9.91 works fine.
> > > > From the initiator, if I do cat /dev/sr1
Wakko Warner wrote:
> Wakko Warner wrote:
> > Bart Van Assche wrote:
> > > On Sat, 2018-03-31 at 18:12 -0400, Wakko Warner wrote:
> > > > Richard Weinberger wrote:
> > > > > On Sat, Mar 31, 2018 at 3:59 AM, Wakko Warner
> > > > > w
Wakko Warner wrote:
> Bart Van Assche wrote:
> > On Sat, 2018-03-31 at 18:12 -0400, Wakko Warner wrote:
> > > Richard Weinberger wrote:
> > > > On Sat, Mar 31, 2018 at 3:59 AM, Wakko Warner
> > > > wrote:
> > > > > I reported this be
Bart Van Assche wrote:
> On Sun, 2018-04-01 at 07:37 -0400, Wakko Warner wrote:
> > Bart Van Assche wrote:
> > > On Sat, 2018-03-31 at 18:12 -0400, Wakko Warner wrote:
> > > > Richard Weinberger wrote:
> > > > > On Sat, Mar 31, 2018 at 3:59 AM,
Bart Van Assche wrote:
> On Sat, 2018-03-31 at 18:12 -0400, Wakko Warner wrote:
> > Richard Weinberger wrote:
> > > On Sat, Mar 31, 2018 at 3:59 AM, Wakko Warner wrote:
> > > > I reported this before but noone responded.
> > >
> > > Because you
Richard Weinberger wrote:
> On Sat, Mar 31, 2018 at 3:59 AM, Wakko Warner wrote:
> > I reported this before but noone responded.
>
> Because you're sending only to LKML.
> CC'ing storage folks.
Thank you. I wasn't sure who I needed to send it to.
Tim Small wrote:
> Fix performance burning or extracting audio etc. from multiple optical
> drives.
I know this is a bit late and is still not in 4.3. I applied 2 of the
patches. I did not apply the ide-cd, the paride nor the gdrom since I don't
have any of those.
> Patches are against 3.18.0-r
Tim Small wrote:
> I've got a big box of audio CDs to read, so I hooked up a load of SATA
> CDROM drives to a machine (Intel motherboard AHCI, and SATA SiI3124
> controllers - in this example one was attached to each host controller),
> so that I could read them in parallel.
>
> I'm using kernel 3
Peter Chang wrote:
> 2013/12/12 Wakko Warner :
> > Kernel: vanilla 3.7.2.
> >
> > I have 2 mpt2sas controllers. I'm running a md check on the 2 arrays that I
> > have (one per card). I'm seeing this in my kernel log (last 4 lines):
> > 2013-12-10 19:
Kernel: vanilla 3.7.2.
I have 2 mpt2sas controllers. I'm running a md check on the 2 arrays that I
have (one per card). I'm seeing this in my kernel log (last 4 lines):
2013-12-10 19:52:10 kame kernel:[1558186.193904] mpt2sas0:
log_info(0x3108): originator(PL), code(0x08), sub_code(0x)
Stefan Richter wrote:
> On Jan 04 Otto Meta wrote:
> > Otto Meta wrote:
> > > The single mutex for the sr module, introduced as a BKL replacement,
> > > globally serialises all sr ioctls, which hurts multi-drive performance.
> > >
> > > This patch replaces sr_mutex with per-device mutexes in struc
Please keep me in the CC.
I was attempting to send an INQUIRY to a scsi device using /dev/sg* and
SG_IO. My first attempt hard locked the machine.
My code was:
memset(&sg_io, 0, sizeof(sg_io));
sg_io.interface_id='S';
sg_io.dxfer_direction=SG_DXFER_FROM_DEV;
sg_io.cmd_len=sizeof(cmd);
sg_io
NOTE: I am not on the list, please always keep me in CC.
Can anyone tell me what this means:
Apr 28 22:50:42 vegeta kernel: [179467.422680] scsi0: device overrun (status a)
on 0:0:0
Apr 28 22:50:42 vegeta kernel: [179467.479433] scsi0: device overrun (status a)
on 0:0:0
Apr 28 22:50:42 vegeta ke
Keep me in CC, I'm not on the list.
James Bottomley wrote:
> On Fri, 2007-02-02 at 19:42 -0500, Wakko Warner wrote:
> > [ 40.154122] ACPI: PCI Interrupt :05:01.1[B] -> GSI 17 (level,
> > low) -> IRQ 22
> > [ 40.158190] scsi4: PCI error Interrupt at seqaddr
Please keep me in CC, I'm not on the list.
Mark Rustad wrote:
> On Feb 2, 2007, at 6:42 PM, Wakko Warner wrote:
> >The PC is a suprtmicro x5da8 with an onboard dual channel AHA-39320
> >u320
> >controller. I have a dual channel AHA-39160 u160 and a dual channel
> &
NOTE: I am not on the linux-scsi list, keep me in CC.
Andrew Morton wrote:
> On Tue, 30 Jan 2007 07:18:20 -0500
> Wakko Warner <[EMAIL PROTECTED]> wrote:
> > Andrew Morton wrote:
> > > Yes, getting the oops traces will help, thanks. And confirmation on a
> > &g
NOTE: I am not on the linux-scsi list, keep me in CC.
Andrew Morton wrote:
> On Sun, 28 Jan 2007 14:46:20 -0500
> Wakko Warner <[EMAIL PROTECTED]> wrote:
>
> > I have 2 machine that oops with these cards.
> >
> > 1) The bios has the option to enable/disa
30 matches
Mail list logo
