Re: problem with ending requests asynchronously in my block device driver

On Sat, 2007-12-15 at 12:52 -0800, a_kumar wrote:

> I've a block device driver which does the following, 

Why not send the actual code?

> This code works fine with most of the kernel versions, but fails on some
> like , Linux 2.6.18-8.el5-xen 

You've provided no information. What we need:

*). A well formed report, complete with oops, panic, other output.
*). Description of how it "fails".

Note also that there is no upstream Linux "2.6.18-8.el5-xen" kernel.

There is a Red Hat Enterprise Linux kernel release with that revision
(this is the one that shipped in the GA RHEL5.0 kernel). You should
contact your vendor for support with their kernel if you are unable to
provide a well-formed bug report against an upstream kernel release.

Jon.


--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

---

• References:
  • problem with ending requests asynchronously in my block device driver
    • From: a_kumar <[email protected]>

• Prev by Date: Re: [PATCH 3/3] net: wireless: bcm43xx: big_buffer_sem semaphore to mutex
• Next by Date: Re: [PATCH] x86_64: fix problems due to use of "outb" to port 80 on some AMD64x2 laptops, etc.
• Previous by thread: problem with ending requests asynchronously in my block device driver
• Next by thread: problem with ending requests asynchronously in my block device driver
• Index(es):
  • Date
  • Thread

[Index of Archives]     [Kernel Newbies]     [Netfilter]     [Bugtraq]     [Photo]     [Stuff]     [Gimp]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Video 4 Linux]     [Linux for the blind]     [Linux Resources]