Well,
Hardcoding of block size to 512 bytes for disk devices is what currently
either the block device driver or the sd driver is doing. Because, if
I run dd to the same device using the corresponding block device (sde)
it runs fine. So, I feel that either the sg driver or the block device
dri
Hi List,
I am trying to use sg_dd which goes through the scsi generic driver.
This is how use it.
sg_dd if=/dev/zero of=/dev/sg5 bs=4096 count=1
And sg5 is actually a disk.
The question that I have is, does the scsi generic driver have a knowledge
about what kind of device it is dealing with
So where can find the whole docbook ? I could not find under
linux/Documentation directory.
Regards,
-hiren
(408)970-3062
[EMAIL PROTECTED]
> -Original Message-
> From: Erik Mouw [mailto:[EMAIL PROTECTED]]
> Sent: Wednesday, May 30, 2001 1:36 PM
> To: Tim Waugh
> Cc: Linux kernel mailin
Hi LIst,
In the linux kernel there is a limitation on the
amount of contiguous DMAable memory that can be allocated
(I guess about 128K). Does anobody know what is the reason
for such a restriction ? Is there any plan to remove
this restriction in the future releases of kernel ?
Regards,
-hiren
Hi List,
I saw this in the archive. And I guess, I am also seeing this
problem on 2.4.4. But I am not sure. Has this problem of
rw_semaphore been fixed in 2.4.4 ? If not any idea, when
will this be fixed ?
Regards,
-hiren
(408)970-3062
[EMAIL PROTECTED]
-
To unsubscribe from this list: send the
Hi List,
I tried to do dd to a bunch of scsi drives running in background.
e.g. dd if=/dev/zero of=/dev/sdb bs=1024 &
dd if=/dev/zero of=/dev/sdc bs=1024 &
dd if=/dev/zero of=/dev/sdd bs=1024 &
Then I tried to kill the first dd process writing to /dev/sdb
and it freezes up the system.
dropping the io_request_lock around vmalloc worked great.
Thanks for all the help. I really appreciate it.
Thanks
-hiren
> -Original Message-
> From: Alan Cox [mailto:[EMAIL PROTECTED]]
> Sent: Wednesday, April 04, 2001 5:29 PM
> To: [EMAIL PROTECTED]
> Cc: [EMAIL PROTECTED]; [EMAIL PRO
I am calling during initialization only from detect() entry point.
But I guess, before the detect() is called, scsi layer acquires
the io_request_lock. So, you mean to say that I need to release it
before calling vmalloc() ? I was doing the same thing on 2.2.x
and even on 2.4.0 and it was working
Can we call vmalloc() or get_free_pages() from scsi low-level driver
(HBA driver) ? The reason why I am asking is because, I am calling
vmalloc from scsi low-level driver and I tried this on 2.4.2 on
ia32 as well as ia64 and on both the systems, it is hanging.
on ia64 it happens everytime whereas
That is what I said. I am using vmalloc only. But the call to
vmalloc is hanging.
-hiren
> -Original Message-
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
> Sent: Monday, April 02, 2001 6:26 PM
> To: [EMAIL PROTECTED]
> Subject: RE: vmalloc on 2.4.x on ia64
>
>
> kmalloc() has
Hi,
Is it possible to download a drive firmware to a fibre channel
drive (or even a scsi drive) through linux ? I know that on
NT (or 98) they use WNASPI and a utility provided by the
drive manufacturer to download the firmware. I was wondering
if this is possible through linux scsi interface. F
Hi,
barrier() is defined in kernel.h as follows :
#define barrier() __asm__ __volatile__("": : :"memory")
what does this mean ? is this like "nop" ?
TIA,
-hiren
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordo
Hi
on UP system, if we call cli(), then after that what all
interrupts can occur ? Does the timer interrupt also get blocked
when we call cli() ? I read that, cli() disables all non-maskable
interrupts.
Thanks
-hiren
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
t
Hi,
I am trying to compile devfsd on my system running RedHat linux 7.0
(kernel 2.2.16-22). I get the error "RTLD_NEXT" undefined. I am not
sure where this symbol is defined. Is there anything that I am missing
on my system.
Also, I applied the devfs patch to the kernel, installed the new
kern
That is what I was guessing. But insmod does not need all symbols
present in the .o.
I need to do this because when I release the driver to the customer,
I don't want them to be aware of some of the symbols. I understand
that this is against the open source policy. But that's how it is
and it is
It looks like, those patches are for the test kernels.
I could not find one that can be used for the final released 2.4.0 kernel.
I am not sure which one should I use. So far I was using test10
kernel and then corresponding ia64 patch for test10 on my ia64 system.
Is it that I can apply any pat
Hi All,
Now that 2.4.0 kernel is officially released, does it run
or ia64 as it is or do we need to apply any patches to make
it run on ia64 ?
Thanks and regards,
-hiren
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please
Hi All,
Can somebody tell me how to create a driver disk for redhat linux or
send me a URL where I can find the information on this ? On redhat linux
I started installation using "export mode" so that I can use my own
driver to install the linux on the hard disks connected to my SCSI
adapter and
I looked at the IO-mapping.txt file. It says that
on x86 architecture it should not make any difference.
It also says that "on x86 it _is_ the same memory space. So
on x86 it actually works to just dereference a pointer".
Any inputs on this ?
Thanks and regards,
-hiren
> -Original Message--
Hi All,
I built the kernel on RedHat Linux 7 after configuring
the build (make menuconfig) for SMP kernel.
After installing the kernel (copy bzImage to /boot directory
and run lilo) I rebooted the system to run the new kernel.
Then I looked at the /proc/ksyms file to see if the
symbol names are p
Hi All,
I have one process hung on my linux smp system (2 processors) running
RedHat Linux 7.
The command
% ps -eo fname,tty,pid,stat,pcpu,nwchan,wchan
gives the following information about the command :
COMMAND TT PID STAT %CPU WCHAN WCHAN
rm tty2 21760R99.8
Hi All,
Just 2 days back I bought RedHat Linux7. And I was trying to build
the kernel (make bzImage). But the build failed. It looks like
the compiler issue. But I am not sure and hence, I have posted this
on this list.
Well, I tried one more thing. The RedHat Linux7 came with gcc package
gcc-2
Hi All,
I am testing my scsi driver. I started the test, and down
the line, the I/O processes (cp/rm) are hung. It looks
like they are hung on completion of some I/O. How do I
find out, for which I/O they are waiting ? Is there any
way to look at the kernel data structures ?
Thanks and regards,
Hi All,
Where can I find complete in-depth information about the
structure of the linux ext2 file system ?
Please copy your replies to [EMAIL PROTECTED] as I
am not on the linux-kernel list.
Regards,
-hiren
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of
24 matches
Mail list logo