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
> > > > r
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
> > > > r
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 (physical di
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 (physical di
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
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
> ---
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
> ---
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.
>
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
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
> >
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
> >
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 the 2
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 the 2
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.866415]
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.866415]
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.866415]
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.866415]
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.866415]
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.866415]
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
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
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 <wa...@animx.eu.org>
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 <wa...@animx.eu.org>
> > > > 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
> > > > 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, Wakko
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 <wa...@animx.eu.org> wrote:
> > > > I reported this before but noone responded.
> > &g
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're
Richard Weinberger wrote:
> On Sat, Mar 31, 2018 at 3:59 AM, Wakko Warner <wa...@animx.eu.org> 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.
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.
Wakko Warner wrote:
> I reported this before but noone responded.
>
> I have an iscsi target setup with /dev/sr[012] using pscsi. On the
> initiator, I mount only 1 disc. Then I issue find -type f | xargs cat >
> /dev/null Then after a few seconds, I get 2 oops and the syste
Wakko Warner wrote:
> I reported this before but noone responded.
>
> I have an iscsi target setup with /dev/sr[012] using pscsi. On the
> initiator, I mount only 1 disc. Then I issue find -type f | xargs cat >
> /dev/null Then after a few seconds, I get 2 oops and the syste
I reported this before but noone responded.
I have an iscsi target setup with /dev/sr[012] using pscsi. On the
initiator, I mount only 1 disc. Then I issue find -type f | xargs cat >
/dev/null Then after a few seconds, I get 2 oops and the system has to be
hard reset.
I noticed if I cat
I reported this before but noone responded.
I have an iscsi target setup with /dev/sr[012] using pscsi. On the
initiator, I mount only 1 disc. Then I issue find -type f | xargs cat >
/dev/null Then after a few seconds, I get 2 oops and the system has to be
hard reset.
I noticed if I cat
I'm using target to make /dev/sr[012] an iscsi target. Another system is
reading all 3 at the same time. I had 2 VMs running using libvirt (qemu and
kvm module). Less than a minute after starting the read, the kernel oops.
Rebooted the machine and tried again without the VMs running, got
I'm using target to make /dev/sr[012] an iscsi target. Another system is
reading all 3 at the same time. I had 2 VMs running using libvirt (qemu and
kvm module). Less than a minute after starting the read, the kernel oops.
Rebooted the machine and tried again without the VMs running, got
Anyone ?
Wakko Warner wrote:
> Starting with 4.10-rc1, I'm seeing an issue with a VM that boots an old
> kernel. The VM uses kernel 3.3.0 and is booted directly by qemu. This VM
> is a copy of a physical machine.
>
> During boot, it hangs for several seconds on "Using
Anyone ?
Wakko Warner wrote:
> Starting with 4.10-rc1, I'm seeing an issue with a VM that boots an old
> kernel. The VM uses kernel 3.3.0 and is booted directly by qemu. This VM
> is a copy of a physical machine.
>
> During boot, it hangs for several seconds on "Using
Starting with 4.10-rc1, I'm seeing an issue with a VM that boots an old
kernel. The VM uses kernel 3.3.0 and is booted directly by qemu. This VM
is a copy of a physical machine.
During boot, it hangs for several seconds on "Using IPI No-Shortcut mode".
The next line shows something about ata5
Starting with 4.10-rc1, I'm seeing an issue with a VM that boots an old
kernel. The VM uses kernel 3.3.0 and is booted directly by qemu. This VM
is a copy of a physical machine.
During boot, it hangs for several seconds on "Using IPI No-Shortcut mode".
The next line shows something about ata5
I was looking at 3.16 and was going to patch upto the latest with the
incremental patches and noticed there's many missing. Am I using the wrong
ftp site?
Here's an ls from lftp:
lftp ftp.kernel.org:~> cd /pub/linux/kernel/v3.x
cd ok, cwd=/pub/linux/kernel/v3.x
lftp
I was looking at 3.16 and was going to patch upto the latest with the
incremental patches and noticed there's many missing. Am I using the wrong
ftp site?
Here's an ls from lftp:
lftp ftp.kernel.org:~> cd /pub/linux/kernel/v3.x
cd ok, cwd=/pub/linux/kernel/v3.x
lftp
Christoph Hellwig wrote:
> can you try this patch:
> http://www.spinics.net/lists/target-devel/msg13463.html ?
That patch doesn't apply to 4.4.10. The 2nd hunk was rejected.
--
Microsoft has beaten Volkswagen's world record. Volkswagen only created 22
million bugs.
Christoph Hellwig wrote:
> can you try this patch:
> http://www.spinics.net/lists/target-devel/msg13463.html ?
That patch doesn't apply to 4.4.10. The 2nd hunk was rejected.
--
Microsoft has beaten Volkswagen's world record. Volkswagen only created 22
million bugs.
I'm seeing the following message when using the lio iscsi target. This
message is on the machine with the target. I have 1 target with 3 luns.
The luns are /dev/sr0 1 and 2 using pscsi backend. On the initiator, I
issue eject srX for each of the 3 drives and see this message. (NOTE: The
I'm seeing the following message when using the lio iscsi target. This
message is on the machine with the target. I have 1 target with 3 luns.
The luns are /dev/sr0 1 and 2 using pscsi backend. On the initiator, I
issue eject srX for each of the 3 drives and see this message. (NOTE: The
Johan de Jong wrote:
> Hi Wakko,
>
> If I remember correctly I did see you commenting on discussions on
> either the Otto Meta patch, or another that proposed to remove the
> mutex entirely. I was unaware of any others.
I received the last set of patches from Tim more than a year ago. I wasn't
Johan de Jong wrote:
> Hi Wakko,
>
> If I remember correctly I did see you commenting on discussions on
> either the Otto Meta patch, or another that proposed to remove the
> mutex entirely. I was unaware of any others.
I received the last set of patches from Tim more than a year ago. I wasn't
Johan de Jong wrote:
> In the mean time I have applied and tested the 2013 patch by Otto Meta:
>
> http://marc.info/?l=linux-scsi=135705061804384=2
>
> which, in short, replaces mutex_lock(_mutex) (global mutex), that
> was introduced in 2010 to replace lock_kernel(), by per-device mutexes
> and
Johan de Jong wrote:
> In the mean time I have applied and tested the 2013 patch by Otto Meta:
>
> http://marc.info/?l=linux-scsi=135705061804384=2
>
> which, in short, replaces mutex_lock(_mutex) (global mutex), that
> was introduced in 2010 to replace lock_kernel(), by per-device mutexes
> and
Please keep me in CC.
Wakko Warner wrote:
>
> Hannes Frederic Sowa wrote:
> > [full-quote for netdev]
> >
> > Hello,
> >
> > On 16.02.2016 01:08, Wakko Warner wrote:
> > >I've been seeing the following on some of my VMs ran under qemu. The VMs
Please keep me in CC.
Wakko Warner wrote:
>
> Hannes Frederic Sowa wrote:
> > [full-quote for netdev]
> >
> > Hello,
> >
> > On 16.02.2016 01:08, Wakko Warner wrote:
> > >I've been seeing the following on some of my VMs ran under qemu. The VMs
Please keep me in CC.
Hannes Frederic Sowa wrote:
> [full-quote for netdev]
>
> Hello,
>
> On 16.02.2016 01:08, Wakko Warner wrote:
> >I've been seeing the following on some of my VMs ran under qemu. The VMs do
> >not have internet connectivity. This happened wh
Please keep me in CC.
Hannes Frederic Sowa wrote:
> [full-quote for netdev]
>
> Hello,
>
> On 16.02.2016 01:08, Wakko Warner wrote:
> >I've been seeing the following on some of my VMs ran under qemu. The VMs do
> >not have internet connectivity. This happened wh
Please keep me in CC.
Hannes Frederic Sowa wrote:
> [full-quote for netdev]
> On 16.02.2016 01:08, Wakko Warner wrote:
> >I've been seeing the following on some of my VMs ran under qemu. The VMs do
> >not have internet connectivity. This happened when some files were a
Please keep me in CC.
Hannes Frederic Sowa wrote:
> [full-quote for netdev]
> On 16.02.2016 01:08, Wakko Warner wrote:
> >I've been seeing the following on some of my VMs ran under qemu. The VMs do
> >not have internet connectivity. This happened when some files were a
Please keep me in CC.
I've been seeing the following on some of my VMs ran under qemu. The VMs do
not have internet connectivity. This happened when some files were accessed
via NFS to another VM (NOTE: Both VMs throw these warnings. Both VMs are
running the exact same kernel). The host is
Please keep me in CC.
I've been seeing the following on some of my VMs ran under qemu. The VMs do
not have internet connectivity. This happened when some files were accessed
via NFS to another VM (NOTE: Both VMs throw these warnings. Both VMs are
running the exact same kernel). The host is
Dominique Martinet wrote:
> Hi,
Hi.
The following was trimmed.
> > On 01/10/2014 03:03 PM, Wakko Warner wrote:
> > > Wakko Warner wrote:
> > >> Kernel 3.12.7 from kernel.org
> > >> With kmod-16, I'm unable to load any modules on my guest kvm machines
Dominique Martinet wrote:
Hi,
Hi.
The following was trimmed.
On 01/10/2014 03:03 PM, Wakko Warner wrote:
Wakko Warner wrote:
Kernel 3.12.7 from kernel.org
With kmod-16, I'm unable to load any modules on my guest kvm machines.
open(/lib/modules/3.12.7/kernel/crypto/af_alg.ko
Wakko Warner wrote:
> Kernel 3.12.7 from kernel.org
> With kmod-16, I'm unable to load any modules on my guest kvm machines.
> The vm is booted via direct kernel boot. The modules are located on the
> host and is passed to the guest via the fsdev.
>
> I have a mountpoint on th
Wakko Warner wrote:
Kernel 3.12.7 from kernel.org
With kmod-16, I'm unable to load any modules on my guest kvm machines.
The vm is booted via direct kernel boot. The modules are located on the
host and is passed to the guest via the fsdev.
I have a mountpoint on the guest filesystem
Kernel 3.12.7 from kernel.org
With kmod-16, I'm unable to load any modules on my guest kvm machines.
The vm is booted via direct kernel boot. The modules are located on the
host and is passed to the guest via the fsdev.
I have a mountpoint on the guest filesystem located at /kernel. It is
Kernel 3.12.7 from kernel.org
With kmod-16, I'm unable to load any modules on my guest kvm machines.
The vm is booted via direct kernel boot. The modules are located on the
host and is passed to the guest via the fsdev.
I have a mountpoint on the guest filesystem located at /kernel. It is
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)
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)
Please keep me in CC.
CCing Borislav Petkov , intel-...@lists.freedesktop.org,
dri-de...@lists.freedesktop.org as they were on another part of this thread.
Chris Wilson wrote:
> > > I receive a warning in drivers/gpu/drm/i915/intel_display.c:3869. This
> > > happens when I'm on a console, the
Wakko Warner wrote:
> Please keep me in CC.
>
> I receive a warning in drivers/gpu/drm/i915/intel_display.c:3869. This
> happens when I'm on a console, the screen has gone into power save and I
> press a key to wake it up.
>
> This doesn't happen when I'm in X.
>
&g
Wakko Warner wrote:
Please keep me in CC.
I receive a warning in drivers/gpu/drm/i915/intel_display.c:3869. This
happens when I'm on a console, the screen has gone into power save and I
press a key to wake it up.
This doesn't happen when I'm in X.
Kernel is Vanilla 3.11.2.
Tested
Please keep me in CC.
CCing Borislav Petkov b...@alien8.de, intel-...@lists.freedesktop.org,
dri-de...@lists.freedesktop.org as they were on another part of this thread.
Chris Wilson wrote:
I receive a warning in drivers/gpu/drm/i915/intel_display.c:3869. This
happens when I'm on a
Please keep me in CC.
I receive a warning in drivers/gpu/drm/i915/intel_display.c:3869. This
happens when I'm on a console, the screen has gone into power save and I
press a key to wake it up.
This doesn't happen when I'm in X.
Kernel is Vanilla 3.11.2.
# lspci -vns2
00:02.0 0300: 8086:041a
Please keep me in CC.
I receive a warning in drivers/gpu/drm/i915/intel_display.c:3869. This
happens when I'm on a console, the screen has gone into power save and I
press a key to wake it up.
This doesn't happen when I'm in X.
Kernel is Vanilla 3.11.2.
# lspci -vns2
00:02.0 0300: 8086:041a
Jeff Garzik wrote:
> Wakko Warner wrote:
> >Please CC me.
> >I've looked around and the only thing I can find was a git repository for
> >it. I don't know anything about git. I just want to get the driver so I
> >can use the sata drives I have on this controller.
Jeff Garzik wrote:
Wakko Warner wrote:
Please CC me.
I've looked around and the only thing I can find was a git repository for
it. I don't know anything about git. I just want to get the driver so I
can use the sata drives I have on this controller.
I'm currently using 2.6.22.
hum
Jeff Garzik wrote:
> Wakko Warner wrote:
> >Please CC me.
>
> Please don't use
>
> Mail-Followup-To: linux-kernel@vger.kernel.org
>
> in your emails then :)
I'm not sending out that header. Maybe I should with my address?
> >I've looked around and th
Please CC me.
I've looked around and the only thing I can find was a git repository for
it. I don't know anything about git. I just want to get the driver so I
can use the sata drives I have on this controller.
I'm currently using 2.6.22.
--
Lab tests show that use of micro$oft causes
Please CC me.
I've looked around and the only thing I can find was a git repository for
it. I don't know anything about git. I just want to get the driver so I
can use the sata drives I have on this controller.
I'm currently using 2.6.22.
--
Lab tests show that use of micro$oft causes
Jeff Garzik wrote:
Wakko Warner wrote:
Please CC me.
Please don't use
Mail-Followup-To: linux-kernel@vger.kernel.org
in your emails then :)
I'm not sending out that header. Maybe I should with my address?
I've looked around and the only thing I can find was a git repository
Takashi Iwai wrote:
> At Tue, 26 Jun 2007 12:25:16 -0400,
> Wakko Warner wrote:
> > I have a motherboard with an intel chipset and onboard audio. I have a
> > problem with alsa. There's no pcm* files in /proc/asound/card0.
>
> Set CONFIG_SND_VERBOSE_PROCFS=y.
GAH!
Takashi Iwai wrote:
At Tue, 26 Jun 2007 12:25:16 -0400,
Wakko Warner wrote:
I have a motherboard with an intel chipset and onboard audio. I have a
problem with alsa. There's no pcm* files in /proc/asound/card0.
Set CONFIG_SND_VERBOSE_PROCFS=y.
GAH! Thanks, I didn't think I needed
Adrian Bunk wrote:
> On Tue, Jun 26, 2007 at 12:18:05AM +0300, Hannu Savolainen wrote:
> >...
> > What we would like to push is that the old "deprecated" OSS/Free are
> > removed from the kernel. OSS/Free is based on about years old OSS API
> > version which was too limited for many
Adrian Bunk wrote:
On Tue, Jun 26, 2007 at 12:18:05AM +0300, Hannu Savolainen wrote:
...
What we would like to push is that the old deprecated OSS/Free are
removed from the kernel. OSS/Free is based on about years old OSS API
version which was too limited for many applications. Having
[EMAIL PROTECTED] wrote:
> On Mon, 18 Jun 2007, Brendan Conoboy wrote:
>
> >[EMAIL PROTECTED] wrote:
> >> yes, sorry, ultra 320 wide.
> >
> >Exactly how many channels and drives?
>
> one channel, 2 OS drives plus the 45 drives in the array.
Given that the drives only have 4 ID bits, how can you
[EMAIL PROTECTED] wrote:
On Mon, 18 Jun 2007, Brendan Conoboy wrote:
[EMAIL PROTECTED] wrote:
yes, sorry, ultra 320 wide.
Exactly how many channels and drives?
one channel, 2 OS drives plus the 45 drives in the array.
Given that the drives only have 4 ID bits, how can you have 47
dean gaudet wrote:
> On Sun, 17 Jun 2007, Wakko Warner wrote:
>
> > > i use an external write-intent bitmap on a raid1 to avoid this... you
> > > could use internal bitmap but that slows down i/o too much for my tastes.
> > >
> > > i also use an ex
dean gaudet wrote:
> On Sat, 16 Jun 2007, Wakko Warner wrote:
>
> > When I've had an unclean shutdown on one of my systems (10x 50gb raid5) it's
> > always slowed the system down when booting up. Quite significantly I must
> > say. I wait until I can login and chan
dean gaudet wrote:
On Sat, 16 Jun 2007, Wakko Warner wrote:
When I've had an unclean shutdown on one of my systems (10x 50gb raid5) it's
always slowed the system down when booting up. Quite significantly I must
say. I wait until I can login and change the rebuild max speed to slow
dean gaudet wrote:
On Sun, 17 Jun 2007, Wakko Warner wrote:
i use an external write-intent bitmap on a raid1 to avoid this... you
could use internal bitmap but that slows down i/o too much for my tastes.
i also use an external xfs journal for the same reason. 2 disk raid1
Neil Brown wrote:
> On Friday June 15, [EMAIL PROTECTED] wrote:
>
> > As I understand the way
> > raid works, when you write a block to the array, it will have to read all
> > the other blocks in the stripe and recalculate the parity and write it
Neil Brown wrote:
On Friday June 15, [EMAIL PROTECTED] wrote:
As I understand the way
raid works, when you write a block to the array, it will have to read all
the other blocks in the stripe and recalculate the parity and write it out.
Neil Brown wrote:
> On Thursday June 14, [EMAIL PROTECTED] wrote:
> > why does it need to do a rebuild when makeing a new array? couldn't it
> > just zero all the drives instead? (or better still just record most of the
> > space as 'unused' and initialize it as it starts useing it?)
>
> Yes,
Neil Brown wrote:
On Thursday June 14, [EMAIL PROTECTED] wrote:
why does it need to do a rebuild when makeing a new array? couldn't it
just zero all the drives instead? (or better still just record most of the
space as 'unused' and initialize it as it starts useing it?)
Yes, it could
1 - 100 of 280 matches
Mail list logo
