public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Dave Jones <davej@redhat.com>
To: "Richard B. Johnson" <linux-os@analogic.com>
Cc: Linux kernel <linux-kernel@vger.kernel.org>
Subject: Re: Linux-2.6.12
Date: Mon, 20 Jun 2005 20:32:04 -0400	[thread overview]
Message-ID: <20050621003203.GB28908@redhat.com> (raw)
In-Reply-To: <Pine.LNX.4.61.0506200857450.5213@chaos.analogic.com>

On Mon, Jun 20, 2005 at 09:07:34AM -0400, Richard B. Johnson wrote:
 > 
 > Attempts to run a driver that worked up to 2.6.11.9 shows that
 > it aparently is no longer possible to nest calls to `down`.
 > In other words, a procedure that has taken a semaphore can't
 > then take another semaphore.
 > 
 > 	down(&first_resource);
 > 	down(&second_resource);
 > 	...
 > 	...
 > 	up(&second_resource);
 > 	up(&first_resource);
 > 
 > 
 > The error is 'sleeping function called from invalid context....'
 > 
 > ------------[ cut here ]------------
 > kernel BUG at mm/memory.c:1112!
 > invalid operand: 0000 [#1]
 > PREEMPT SMP 
 > Modules linked in: HeavyLink parport_pc lp parport autofs4 rfcomm l2cap 
 > bluetooth nfsd exportfs lockd sunrpc e100 mii ipt_REJECT ipt_state 
 > ip_conntrack iptable_filter ip_tables floppy sg sr_mod microcode nls_cp437 
 > msdos fat dm_mod uhci_hcd ehci_hcd video container button battery ac rtc 
 > ipv6 ext3 jbd ata_piix libata aic7xxx scsi_transport_spi sd_mod scsi_mod
 > CPU:    0
 > EIP:    0060:[<c01577f0>]    Not tainted VLI

Where is the source for this HeavyLink module ? The lack of tainting implies
that it is GPL ?  Oh wait, you've been asked this before[1], but
chose to ignore it.

Remind me again, why you expect any help from linux-kernel, when you've
previously gone out of your way to encourage the subversion of the
gpl-checking mechanisms in the kernel[2], and have no aparent intentions
of showing the code at fault.

		Dave

[1] http://www.ussg.iu.edu/hypermail/linux/kernel/0410.0/1690.html
[2] http://www.uwsg.iu.edu/hypermail/linux/kernel/0210.2/0609.html


  parent reply	other threads:[~2005-06-21  0:49 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-20 13:07 Linux-2.6.12 Richard B. Johnson
2005-06-20 13:48 ` Linux-2.6.12 Hugh Dickins
2005-06-20 14:22   ` Linux-2.6.12 Richard B. Johnson
2005-06-20 14:41     ` Linux-2.6.12 Hugh Dickins
2005-06-20 15:32       ` Linux-2.6.12 Richard B. Johnson
2005-06-20 16:02         ` Linux-2.6.12 Hugh Dickins
2005-06-21  0:32 ` Dave Jones [this message]
     [not found]   ` <Pine.LNX.4.61.0506210629110.8815@chaos.analogic.com>
2005-06-21 11:13     ` Linux-2.6.12 Dave Jones
2005-06-21 11:17       ` Linux-2.6.12 Richard B. Johnson
2005-06-21 11:30         ` Linux-2.6.12 Dave Jones
2005-06-21 11:36           ` Linux-2.6.12 Richard B. Johnson
2005-06-21 11:55             ` Linux-2.6.12 Dave Jones
2005-06-21 12:01               ` Linux-2.6.12 Richard B. Johnson
2005-06-21 12:15                 ` Linux-2.6.12 Dave Jones
2005-06-21 12:30                   ` Linux-2.6.12 Richard B. Johnson
2005-06-21 12:46                     ` Linux-2.6.12 Dave Jones
2005-06-21 23:47                     ` Linux-2.6.12 Kurt Wall

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20050621003203.GB28908@redhat.com \
    --to=davej@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-os@analogic.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox