Hi,friend,
This is Daniel Murray and i am from Sinara Group Co.Ltd Group Co.,LTD in Russia.
We are glad to know about your company from the web and we are interested in
your products.
Could you kindly send us your Latest catalog and price list for our trial order.
Best Regards,
Daniel
ed all these drivers to ensure that all ioctl arguments
> are used as pointers or are ignored, but are not interpreted as integer
> values.
>
> Signed-off-by: Arnd Bergmann
Acked-by: Daniel Vetter
At least for the drm and dma-buf bits.
-Daniel
> ---
> drivers/android/bin
t;>> arm64: implement nospec_ptr()
>>>>>> arm: implement nospec_ptr()
>>>>>
>>>>> So considering the recent publication of [1], how come we all of a sudden
>>>>> don't need the barriers in ___bpf_prog_run(), namely
On Wed, Sep 13, 2017 at 01:02:12PM +0530, Allen Pais wrote:
> Signed-off-by: Allen Pais
Applied to drm-misc-next, thanks.
-Daniel
> ---
> drivers/gpu/drm/gma500/mid_bios.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/gpu/drm/gma500/mid_b
On Sat, Aug 19, 2017 at 01:52:13PM +0530, Bhumika Goyal wrote:
> Make these const as they are only stored in the type field of a device
> structure, which is const.
> Done using Coccinelle.
I can't apply this, it's missing your s-o-b line. You can just replay with
th
On Thu, Apr 13, 2017 at 04:05:18PM -0600, Logan Gunthorpe wrote:
> This is a single straightforward conversion from kmap to sg_map.
>
> Signed-off-by: Logan Gunthorpe
Acked-by: Daniel Vetter
Probably makes sense to merge through some other tree, but please be aware
of the considera
The British National Lottery
P O Box 1010
3b Olympic Way, Sefton Business Park,
Aintree, Liverpool , L30 1RD
(Customer Services)
Ref: UK/9420X2/68
Batch: 074/05/ZY369
Ticket number:56475600545 188
Lucky Numbers: 05,06,17,20,28,42(Bonus33)
WINNING NOTIFICATION:
We wish to congratulate and inf
would mask the
problem for others, so it's not really viable.
Is there a way to detect when you have a device of the type where this
is a serious issue ? This typically happen for USB drives, but seems to
have no effect on them.
Daniel
--
To unsubscribe from this list: send the line "u
From: Daniel Wagner
There is only one waiter for the completion, therefore there is no need
to use complete_all(). Let's make that clear by using complete() instead
of complete_all().
The usage pattern of the completion is:
waiter context waker context
virtscs
From: Daniel Wagner
There is only one waiter for the completion, therefore there is no need
to use complete_all(). Let's make that clear by using complete() instead
of complete_all().
The usage pattern of the completion is:
waiter context waker context
sym_eh_ha
From: Daniel Wagner
Hi,
Using complete_all() is not wrong per se but it suggest that there
might be more than one waiter. For -rt I am reviewing all
complete_all() users and would like to leave only the real ones in the
tree. The main problem for -rt about complete_all() is that it can be
uses
From: Daniel Wagner
The (re)initialzing of the completion object should be done before we
trigger the transfer. Doing this after triggering the hardware opens up
a race window. Without the timeout we would problaly even deadlock. Use
also reinit_completion because we initalize the whole data
is a good approach.
Regards,
Daniel
> This access is encoded in the translation entries that comprise the
> virtual LUN and used by the AFU for load-balancing I/O and handling
> failover scenarios. In a link loss scenario, even though the AFU is
> able to maintain connectivity to th
Hi Uma,
It looks like CXLFLASH_DRIVER_DATE is only used once, on init, and it's
just printed. Is it necessary? It looks like having it will require
sending a patch to update it quite often.
Regards,
Daniel
signature.asc
Description: PGP signature
lding up the series for it.
I also tend to use the form (var == ~0ULL) for tests like this but
that's an aesthetic thing.
Reviewed-by: Daniel Axtens
Regards,
Daniel
signature.asc
Description: PGP signature
its void-like behavior, the function was left with a
> return code for right now in case its behavior needs to be altered again
> in the near future based on testing.
>
Thanks for updating that.
Reviewed-by: Daniel Axtens
Regards,
Daniel
> Signed-off-by: Matthew R. Oc
sion + 1 == 0,
and interface_version is a 64bit unsigned int, that would mean that
afu->interface_version was 0x .
Are you trying to check against all Fs? Is that value significant in the
hardware?
Regards,
Daniel
> + } else
> + pr_debug("%
l deadlock on EEH". Without this fix, you'd end
> up in a similar situation but deadlocked on the context mutex instead
> of the ioctl semaphore.
That makes _much_ more sense. If you could please revise the commit
message to explain that, you can include this in the next version:
Re
MMIO here, so I'm not sure how the all Fs check
> would apply. We're also protected fairly well by the generation bit. I suppose
> we could look at adding some type of 'max iterations' count to protect against
> a runaway handler but that would be in a future patch.
Ah,
ot;,
>>> __func__, port);
As an aside, should this be a bit noisier? It seems like something
a user would probably want to know - especially in the case where
something has actually gone wrong so there's no link state change
interrupt forthcoming regardless of ho
overed or returns a failure if the recovery failed. In
> the event that the adapter reset failed, the failure is simply returned
> as the ioctl would be unable to continue.
Yep, looks good.
Reviewed-by: Daniel Axtens
>
> Reported-by: Brian King
&
require an embedded fops.
Yep, this looks good.
We have discussed adding a private data field to a cxl context, and will
no doubt revisit the question at some point in the future :)
Reviewed-by: Daniel Axtens
>
> Signed-off-by: Matthew R. Ochs
> Signed-off-by: Manoj N. Kumar
> ---
"Matthew R. Ochs" writes:
>> On Sep 28, 2015, at 8:40 PM, Daniel Axtens wrote:
>>
>> -BEGIN PGP SIGNED MESSAGE-
>> Hash: SHA512
>>
>> "Matthew R. Ochs" writes:
>>
>>> From: Manoj Kumar
>>>
>>
that the patch is correct, but this commit message is a bit
confusing. What delay? In what circumstances are you doubling it? Why?
Regards,
Daniel
> Reported-by: Tomas Henzl
> Signed-off-by: Matthew R. Ochs
> Signed-off-by: Manoj N. Kumar
> Reviewed-by: Brian King
> ---
> driv
sly loops due to an
> out of sync generation bit.
>
> To fix, the AFU RRQ in host memory needs to be cleared after each reset.
This looks good. Do you need anything to bail out of cxlflash_rrq_irq if
the data goes stale or to all Fs while that function is running?
Daniel
>
> Signed-off
ng
out. AFAIK there's nothing in eehd and the EEH core that times out if a
driver doesn't respond - indeed, it's pretty easy to hang eehd with a
misbehaving driver.
Are you referring to your own internal timeouts?
cxlflash_wait_for_pci_err_recovery and anything else that uses
CXLFL
r_debug("%s: returning rc=%d\n", __func__, ret);
> + pr_debug("%s: returning rc=%d\n", __func__, rc);
I'm not sure I fully understand the flow of this function, but it looks
like you set rc=0 regardless of how things actually go: is this ever
going to print a return v
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
"Matthew R. Ochs" writes:
Looks good from an EEH point of view: in an error situation, your driver
asks to be reset and then is waiting for CXL and EEH to carry that out,
so 'reset' matches with that as well.
Reviewed-by: Dan
.\n", __func__);
> +
> + /*
> + * Before checking the state, put back the context obtained with
> + * get_context() as it is no longer needed and sleep for a short
> + * period of time (see prolog notes).
> +
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Looks good to me.
Reviewed-by: Daniel Axtens
Regards,
Daniel
"Matthew R. Ochs" writes:
> The context encode mask covers more than 32-bits, making it
> a long integer. This should be noted by appending the ULL
> width
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Looks good to me.
Reviewed-by: Daniel Axtens
Regards,
Daniel
"Matthew R. Ochs" writes:
> Using sizeof(bool) is considered poor form for various reasons and
> sparse warns us of that. Correct by changing type from bool to u8.
&
On Fri, Aug 21, 2015 at 2:58 PM, Alim Akhtar wrote:
> From: Seungwon Jeon
>
> This patch introduces Exynos UFS host controller driver,
> which mainly handles vendor-specific operations including
> link startup, power mode change and hibernation/unhibernation.
>
> Signed-off-by: Seungwon Jeon
> S
On Fri, Aug 21, 2015 at 2:58 PM, Alim Akhtar wrote:
> From: Seungwon Jeon
>
> Behavior of the "powwer mode change" contains vendor specific
s/powwer/power
> operation known as pwr_change_notify. This change adds return
> for pwr_change_notify to find success or failure.
>
> Signed-off-by: Seungwo
On Fri, Aug 21, 2015 at 2:57 PM, Alim Akhtar wrote:
> From: Seungwon Jeon
>
> It can be used in the vendor's driver for the specific purpose.
more description of this log will be useful.
>
> Signed-off-by: Seungwon Jeon
> Signed-off-by: Alim Akhtar
> ---
> drivers/scsi/ufs/ufshcd.c |5 ++--
On Fri, Aug 21, 2015 at 2:57 PM, Alim Akhtar wrote:
> From: Seungwon Jeon
>
> Some host controller needs specific handling before/after
> (un)hibernation, This change adds specific callback function
> to support vendor's implementation.
>
> Signed-off-by: Seungwon Jeon
> Signed-off-by: Alim Akht
Few comments below,
On Fri, Aug 21, 2015 at 2:57 PM, Alim Akhtar wrote:
> From: Seungwon Jeon
>
> Some host controller supports interrupt aggregation, but doesn't
> allow to reset counter and timer by s/w.
>
> Signed-off-by: Seungwon Jeon
> Signed-off-by: Alim Akhtar
> ---
> drivers/scsi/ufs/
Few minor comments below,
On Fri, Aug 21, 2015 at 2:57 PM, Alim Akhtar wrote:
> From: Seungwon Jeon
>
> UTRD(UTP Transfer Request Descriptor)'s field such as offset/length,
> especially response's has DWORD expression. This quirk can be specified
> for host controller not to conform standard.
>
Hi,
Few minor comments,
On Fri, Aug 21, 2015 at 2:57 PM, Alim Akhtar wrote:
> From: Seungwon Jeon
>
> This patch introduces Exynos UFS PHY driver. This driver
> supports to deal with phy calibration and power control
> according to UFS host driver's behavior.
>
> Signed-off-by: Seungwon Jeon
>
On Tue, 2015-08-11 at 16:21 +1000, Daniel Axtens wrote:
> Actually, I forgot one thing:
>
> >
> > config CXLFLASH
> > tristate "Support for IBM CAPI Flash"
> > - depends on PCI && SCSI && CXL
> > + depends on PCI &&
you use CONFIG_CXL_EEH?
>
> +#ifndef CONFIG_CXL_EEH
> +#define cxl_perst_reloads_same_image(_a, _b) do { } while (0)
> +#endif
> +
> #endif /* _CXLFLASH_MAIN_H */
--
Regards,
Daniel
signature.asc
Description: This is a digitally signed message part
not set
STATE_NORMAL. Is that right?
Once you fix that, or explain to me why I'm wrong:
Reviewed-by: Daniel Axtens
--
Regards,
Daniel
signature.asc
Description: This is a digitally signed message part
pr_debug("%s: pdev=%p state=%u\n", __func__, pdev, state);
> +
> + switch (state) {
> + case pci_channel_io_frozen:
> + cfg->eeh_active = EEH_STATE_ACTIVE;
> + udelay(100);
> +
> + term_mc(cfg, UNDO_START);
> + stop_afu(cfg);
> +
> + return PCI_ERS_RESULT_CAN_RECOVER;
I think that should PCI_ERS_RESULT_NEED_RESET.
Apart from that, it's looking pretty good from an EEH perspective.
--
Regards,
Daniel
signature.asc
Description: This is a digitally signed message part
ine instead of
> > duplicating this
> > state information in a private driver definition?
>
> Makes sense, I’ll look into this.
>
I don't think my vPHB code propagates error_state yet. I'll check, and
if necessary, push a patch and fold it into my v3.
Regards
This patch implements raw mode support for AF DASD in ipr driver
which allows for tools to send commands directly to physical
devices which are members of RAID arrays when enabled in the firmware.
Signed-off-by: Wen Xiong
Signed-off-by: Brian King
Reviewed-by: Daniel Kreling
---
drivers/scsi
Bump driver version.
Signed-off-by: Brian King
Reviewed-by: Daniel Kreling
---
drivers/scsi/ipr.h |4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
===
diff -puN drivers/scsi/ipr.h~ipr_version_2_6_1 drivers/scsi/ipr.h
--- linux/drivers/scsi
Re-enable write same support for ipr RAID adapters.
Signed-off-by: Brian King
Reviewed-by: Daniel Kreling
---
drivers/scsi/ipr.c |1 -
1 file changed, 1 deletion(-)
===
diff -puN drivers/scsi/ipr.c~ipr_write_same drivers/scsi/ipr.c
--- linux/drivers
** Adding 'Reviewed-by' tag **
Fixes a possible oops during adapter initialization in some
memory allocation failure error paths scenarios.
Reported-by: Dan Carpenter
Signed-off-by: Brian King
Reviewed-by: Daniel Kreling
---
drivers/scsi/ipr.c | 14 --
1 file
** Adding 'Reviewed-by' tag **
The pci_set_pcie_reset_state has changed semantics to not be callable
from interrupt context, so change ipr's usage of the API to comply with
this change by ensuring this occurs from a workqueue.
Signed-off-by: Brian King
Reviewed-by: Daniel Krelin
configurations with multiple ipr adapters.
Signed-off-by: Brian King
Reviewed-by: Daniel Kreling
---
drivers/scsi/ipr.c | 160
++---
drivers/scsi/ipr.h |6 +
2 files changed, 157 insertions(+), 9 deletions
On 09/16/2014 12:19 PM, Christoph Hellwig wrote:
Hi Daniel,
this should also be fixed with my patch "scsi: clean up S/G table freeing",
can you test if that fixes the issue for you as well?
Yeah, that fixes it, thanks.
Daniel
--
To unsubscribe from this list: send the line &q
the correct fix.
Daniel
From af61bb1f014bb1d034f4e7c3a18067ff3c9acedf Mon Sep 17 00:00:00 2001
From: Daniel Gryniewicz
Date: Tue, 16 Sep 2014 09:44:35 -0400
Subject: [PATCH] Panic accesing freed memory during bidi SCSI
When ending a bi-directionional SCSI request, blk_finish_request()
cleans u
In prandom we have already reseeding mechanisms that trigger
periodically from a much better entropy source than just
feeding in jiffies through lpfc_mbx_cmpl_fcf_scan_read_fcf_rec()
[what a function name 8-)]. Therefore, just remove this.
Signed-off-by: Daniel Borkmann
Cc: James Bottomley
Cc
Replace obsolete strict_strto with more appropriate kstrto calls
Signed-off-by: Daniel Walter
---
drivers/scsi/pmcraid.c| 4 ++--
drivers/scsi/scsi_sysfs.c | 4 ++--
2 files changed, 4 insertions(+), 4 deletions(-)
diff --git a/drivers/scsi/pmcraid.c b/drivers/scsi/pmcraid.c
index be8ce54
From: Daniel Walter
Subject: [PATCH v2 09/11] [drivers/scsi] replace strict_strto calls
Replace obsolete strict_strto with more appropriate kstrto calls
Signed-off-by: Daniel Walter
---
Resubmit to the mailing list (was submitted to MAINTAINER entry
anil_ravindran...@pmc-sierra.com
but it
from going into suspend. Therefore sd_sync_cache()
shouldn't return an error if the device replies with an Invalid
Command ASC.
Signed-off-by: Alan Stern
Reported-by: Sven Neumann
Tested-by: Daniel Mack
CC: Oliver Neukum
CC:
---
Hi,
this patch has been around for awhile, but hasn't g
On 02/05/2014 12:04 PM, Daniel Mack wrote:
> On 01/15/2014 09:37 PM, Alan Stern wrote:
>> Evidently some wacky USB-ATA bridges don't recognize the SYNCHRONIZE
>> CACHE command, as shown in this email thread:
>>
>> http://marc.info/?t=13897835622&r=1&a
ain their caches shouldn't
> prevent the system from going into suspend. Therefore sd_sync_cache()
> shouldn't return an error if the device replies with an Invalid
> Command ASC.
>
> Signed-off-by: Alan Stern
> Reported-by: Sven Neumann
> Tested-by: Daniel Mack
>
Hi Alan,
On 01/15/2014 06:19 PM, Alan Stern wrote:
> On Wed, 15 Jan 2014, Daniel Mack wrote:
>
>> Hi,
>>
>> Sorry for the long, primarily holiday-related delay on this.
>>
>> On 12/18/2013 09:46 PM, Alan Stern wrote:
>>> On Wed, 18 Dec 2013, Daniel Ma
Hi,
Sorry for the long, primarily holiday-related delay on this.
On 12/18/2013 09:46 PM, Alan Stern wrote:
> On Wed, 18 Dec 2013, Daniel Mack wrote:
>> I'm facing an issue putting an embedded system to sleep while a Lacie
>> external USB hard disk is connected. Relevant
from sd_sync_cache()?
I'm open to suggestions and happy to test patches.
Thanks,
Daniel
--
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Hello dear!
Please kindly send us your contact infomations to our email: (dan.f...@aim.com)
to enable us send your voucher.
Kind regards
Daniel F
--
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to majord...@vger.kernel.org
More majordo
It is Private
I am George Daniels, a Banker and credit system programmer (HSBC bank).
I saw your email address while browsing through the bank D.T.C Screen in my
office yesterday so I decided to use this very chance to know you. I believe we
should use every opportunity to know each other bette
at least mention it here.
Cheers
Daniel
Original Message
Subject: Re: New USB storage device, not detected by Ubuntu 12.10 (kernel
3.5.0-17-generic)
Date: Sun, 27 Jan 2013 13:22:42 -0800
From: Matthew Dharm
To: Daniel
I don't know. You would need to ask the linux
On Wed, Dec 5, 2012 at 12:02 PM, Daniel Vacek wrote:
> On Tue, Dec 4, 2012 at 4:54 PM, Tejun Heo wrote:
>> @@ -5190,7 +5188,7 @@ static void
>> megasas_aen_polling(struct work_struct *work)
>> {
>> struct megasas_aen_event *ev =
>> -
On Tue, Dec 4, 2012 at 4:54 PM, Tejun Heo wrote:
> @@ -5190,7 +5188,7 @@ static void
> megasas_aen_polling(struct work_struct *work)
> {
> struct megasas_aen_event *ev =
> - container_of(work, struct megasas_aen_event, hotplug_work);
> + container_of(work, str
or some weird thread
> interaction in linux-next).
>
> The first question would be "does it happen in vanilla 3.6"?
>
> James
So just to CC LKML, works in vanilla 3.6.0, happens in both -next & -mm,
tried compiling with both gcc 4.6.3 & 4.7.1.
Daniel
--
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
ddr);
Daniel
-
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
.
Signed-off-by: Daniel Drake <[EMAIL PROTECTED]>
---
drivers/scsi/arcmsr/arcmsr_hba.c | 26 +++---
1 files changed, 11 insertions(+), 15 deletions(-)
diff --git a/drivers/scsi/arcmsr/arcmsr_hba.c b/drivers/scsi/arcmsr/arcmsr_hba.c
index 4f9ff32..f91f79c 100644
--- a/d
Daniel Drake wrote:
Here is a patch to address your comments.
Joshua, would you mind testing this before I submit it properly? It will
apply cleanly to 2.6.24 on top of the previous patch you tested. I have
compile-tested it.
It would help to include the patch.
>F
James Bottomley wrote:
On Sat, 2008-02-16 at 11:49 +, Daniel Drake wrote:
I assume you're aware that this patch is just a subset of commit
76d78300a6eb8 which you've already pushed up to Linus. Adding Nick Cheng
(commit author) to CC so that he can go over the feedback.
Wel
I assume you're aware that this patch is just a subset of commit
76d78300a6eb8 which you've already pushed up to Linus. Adding Nick Cheng
(commit author) to CC so that he can go over the feedback.
James Bottomley wrote:
diff --git a/drivers/scsi/arcmsr/arcmsr_hba.c b/drivers/scsi/arcmsr/arcmsr
you report success.
Daniel
From: Nick Cheng <[EMAIL PROTECTED]>
Partial backport of 76d78300 ("arcmsr: updates (1.20.00.15)") by
Daniel Drake <[EMAIL PROTECTED]>. Removes pci_alloc_consistent usage, which
should not be used when IRQs are disabled for portability reasons. Fi
James Bottomley wrote:
However, I think you're right, the vanilla TUR does eat NOT_READY for
removable media, which CDs are. Does this fix it?
Works great, thanks!
Daniel
-
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to [
this work for you? I have attached the test
program I am using.
Thanks!
Daniel
#include
#include
#include
#include
#include
#include
int main(void)
{
int fd = open("/dev/sr0", O_RDONLY | O_NONBLOCK);
int ret;
if (fd < 0) {
perror(
estions from the list? Thanks,
--
Daniel Jabbour
Network / Sytems Engineer
Intronis Technologies
Direct: (800) 569-0155 x242
Email: [EMAIL PROTECTED]
www.intronis.com
-
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to [EMAIL
--- adam radford wrote:
> I have one problem with this patch:
>
> You are calling "class_device_create()" from 0 to "TW_MAX_UNITS"
> which is 16...
> shouldn't you be calling this only once per each controller instance
> that is discovered
> via twa_probe() ?
Well, I was just trying to emulate wh
Add tw_sysfs_init() to register 3w- driver with sysfs. This
also causes udev to create /dev/twe* devices with the correct
SELinux security context.
Signed-off-by: Joshua Daniel Franklin <[EMAIL PROTEC
Thanks! bsg now waits for a response.
Dan
FUJITA Tomonori
To
No Phone Info
Greetings to all,
I'm attempting to use the bidi variant of bsg to talk to an OSD target
device. I've run into an undesirable situation.
My application has a free-running receive loop (doing a read() on the bsg
device) waiting for responses to commands sent to bsg by another thread.
The problem
"Martin K. Petersen" <[EMAIL PROTECTED]> writes:
>>>>>> "Daniel" == Daniel J Priem <[EMAIL PROTECTED]> writes:
>
> Daniel> - * http://www.t10.org/lists/asc-num.txt+ */
> Daniel> + * http://www.t10.org/lists/asc-num.txt */
>
"Martin K. Petersen" <[EMAIL PROTECTED]> writes:
> + * The canonical list of T10 Additional Sense Codes is available at:
> + * http://www.t10.org/lists/asc-num.txt+ */
Please do a
- * http://www.t10.org/lists/asc-num.txt+ */
+ * http://www.t10.org/lists/asc-num.txt */
its
le in trying the slowcrc option and
arrange to ramp down the bus speed some time soon as well.
Thanks for your help, and to Sean for moving this to a more correct
location.
Regards,
Daniel
--
Digital Infrastructure Solutions -- making IT simple, stable and secure
Phone: 0401 155 707e
repeatedly poll the device for media change.
This patch demotes the message to a quieter scsi-logging message only.
Signed-off-by: Daniel Drake <[EMAIL PROTECTED]>
--- linux/drivers/scsi/scsi_ioctl.c.orig 2005-09-09 23:10:07.0 +0100
+++ linux/drivers/scsi/scsi_ioctl.c 2005-09-09 23
ages printed out via printk. I have left the procfs name as
"megaraid" as presumably userspace tools rely on this.
Remove hardware ID's from megaraid_legacy which overlap with the newgen
megaraid drivers.
Allow megaraid_legacy to be built alongside the newgen driver.
Signed-off-b
w one alongside it.
I know that this solution is not ideal, but as LSIL are being uncooperative, I
think this is the best compromise we can do for now. Please apply.
Signed-off-by: Daniel Drake <[EMAIL PROTECTED]>
diff -urNp linux-2.6.12/drivers/scsi-orig/megaraid/Kconfig.megaraid linux-2.6.
> First of all: since the request for a working version of this
> driver is not
> longer there at the moment I'll only send out what I
> currently have to get it
> into list archives. Merging this would be fine to decrease
> the amount of bugs
> in this (and the size of it). I removed everyone b
__asm__ __volatile__(
111 "# atomic down operation\n\t"
Any ideas or suggestions?
Thanks,
Daniel
-
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
blkdev layer, in order to be able to
implement a working set up at least. Please allow me another couple of days
to spare a little hacking time. I'll take care of the issue. Promised.
Regards,
Daniel.
--
GNU/Linux Audio Mechanics - http://www.glame.de
Cutting Edge
[1.] One line summary of the problem:
Linux 2.2.19 system crash with Oops in scsi_do_cmd during mirror rebuild
on megaraid
[2.] Full description of the problem/report:
Seconds after starting a rebuild of a mirrored partition on a megaraid
controller, the
system crashed. It might be reproducable
is the direction might be as good as trusting what the
driver thinks is the direction currently. On the other hand, given that
MESH at least locks up hard when the driver guesses wrong, it's
important to verify that the kernel is right at least as often as the
drivers currently are about the di
f drivers is configured in.
However, in light of other email in this thread, it looks like maybe the
table can go altogether, so hopefully this question is now moot.
-Daniel
--
Daniel E. Eisenbud
[EMAIL PROTECTED]
-
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to [EMAIL PROTECTED]
On Tue, Feb 13, 2001 at 09:40:36AM -0500, Douglas Gilbert <[EMAIL PROTECTED]> wrote:
> Daniel Eisenbud wrote:
> >
> > Eight different SCSI drivers have large switch statements to determine
> > the direction in which data will be transferred for a given SCSI
> >
ayer and see if I can
fix this. But in the meantime, this patch prevents the known case that
locks up, and is a cleanup to boot. Please let me know if there's
anything I need to do differently to have a chance of this getting added
to the kernel: I'm rather new to kernel hacking a
93 matches
Mail list logo
