On Thu, 15 Mar 2007 07:54:14 -0700 Greg KH wrote:
> On Thu, Mar 15, 2007 at 11:19:20AM +0100, Mike Galbraith wrote:
> > On Thu, 2007-03-15 at 01:06 -0700, Greg KH wrote:
> >
> > > That's good. But why don't we have a module name for this driver?
> > >
> > > And if we don't have a module name,
On Thu, 15 Mar 2007 07:54:14 -0700 Greg KH wrote:
On Thu, Mar 15, 2007 at 11:19:20AM +0100, Mike Galbraith wrote:
On Thu, 2007-03-15 at 01:06 -0700, Greg KH wrote:
That's good. But why don't we have a module name for this driver?
And if we don't have a module name, why would
On Thu, Mar 15, 2007 at 11:19:20AM +0100, Mike Galbraith wrote:
> On Thu, 2007-03-15 at 01:06 -0700, Greg KH wrote:
>
> > That's good. But why don't we have a module name for this driver?
> >
> > And if we don't have a module name, why would there be a symlink to
> > remove? That's what is
On Thu, 2007-03-15 at 09:32 +0100, Mike Galbraith wrote:
> On Thu, 2007-03-15 at 01:06 -0700, Greg KH wrote:
>
> > That's good. But why don't we have a module name for this driver?
> >
> > And if we don't have a module name, why would there be a symlink to
> > remove? That's what is keeping
On Thu, 2007-03-15 at 01:06 -0700, Greg KH wrote:
> That's good. But why don't we have a module name for this driver?
>
> And if we don't have a module name, why would there be a symlink to
> remove? That's what is keeping your module from unloading, right?
Ya got me, but according to my
On Thu, Mar 15, 2007 at 08:53:07AM +0100, Mike Galbraith wrote:
> On Wed, 2007-03-14 at 22:27 -0700, Greg KH wrote:
>
> > But can you try this version instead?
>
> It exploded in strcmp(). Unfortunately, the full oops didn't make it to
> either console or serial console.
>
> [ 30.783048]
On Wed, 2007-03-14 at 22:27 -0700, Greg KH wrote:
> But can you try this version instead?
It exploded in strcmp(). Unfortunately, the full oops didn't make it to
either console or serial console.
[ 30.783048] ipmi message handler version 39.1
[ 30.787632] ipmi device interface
[
On Wed, 2007-03-14 at 22:27 -0700, Greg KH wrote:
But can you try this version instead?
It exploded in strcmp(). Unfortunately, the full oops didn't make it to
either console or serial console.
[ 30.783048] ipmi message handler version 39.1
[ 30.787632] ipmi device interface
[
On Thu, Mar 15, 2007 at 08:53:07AM +0100, Mike Galbraith wrote:
On Wed, 2007-03-14 at 22:27 -0700, Greg KH wrote:
But can you try this version instead?
It exploded in strcmp(). Unfortunately, the full oops didn't make it to
either console or serial console.
[ 30.783048] ipmi message
On Thu, 2007-03-15 at 01:06 -0700, Greg KH wrote:
That's good. But why don't we have a module name for this driver?
And if we don't have a module name, why would there be a symlink to
remove? That's what is keeping your module from unloading, right?
Ya got me, but according to my debug
On Thu, 2007-03-15 at 09:32 +0100, Mike Galbraith wrote:
On Thu, 2007-03-15 at 01:06 -0700, Greg KH wrote:
That's good. But why don't we have a module name for this driver?
And if we don't have a module name, why would there be a symlink to
remove? That's what is keeping your module
On Thu, Mar 15, 2007 at 11:19:20AM +0100, Mike Galbraith wrote:
On Thu, 2007-03-15 at 01:06 -0700, Greg KH wrote:
That's good. But why don't we have a module name for this driver?
And if we don't have a module name, why would there be a symlink to
remove? That's what is keeping your
On Sat, Mar 10, 2007 at 04:44:06PM +0100, Mike Galbraith wrote:
> On Wed, 2007-03-07 at 06:39 +0100, Mike Galbraith wrote:
> > On Tue, 2007-03-06 at 13:04 -0800, Greg KH wrote:
> > > On Tue, Mar 06, 2007 at 06:43:22AM +0100, Mike Galbraith wrote:
> > > > On Mon, 2007-03-05 at 16:25 -0800, Greg KH
On Sat, Mar 10, 2007 at 04:44:06PM +0100, Mike Galbraith wrote:
On Wed, 2007-03-07 at 06:39 +0100, Mike Galbraith wrote:
On Tue, 2007-03-06 at 13:04 -0800, Greg KH wrote:
On Tue, Mar 06, 2007 at 06:43:22AM +0100, Mike Galbraith wrote:
On Mon, 2007-03-05 at 16:25 -0800, Greg KH wrote:
P.S. forgot to include diagnostic log. Kobject c0644890 is the source
of my woes. Printk's come below WARN_ON(is_ipmi_si_kobj). Post-tinker
log is huge, and probably not interesting.
[ 30.397160] kobject ipmi_devintf: registering. parent: , set: module
[ 30.404033] kobject_uevent_env
[
On Wed, 2007-03-07 at 06:39 +0100, Mike Galbraith wrote:
> On Tue, 2007-03-06 at 13:04 -0800, Greg KH wrote:
> > On Tue, Mar 06, 2007 at 06:43:22AM +0100, Mike Galbraith wrote:
> > > On Mon, 2007-03-05 at 16:25 -0800, Greg KH wrote:
> > >
> > > > Mike, I've reverted this patch, and I don't see
On Wed, 2007-03-07 at 06:39 +0100, Mike Galbraith wrote:
On Tue, 2007-03-06 at 13:04 -0800, Greg KH wrote:
On Tue, Mar 06, 2007 at 06:43:22AM +0100, Mike Galbraith wrote:
On Mon, 2007-03-05 at 16:25 -0800, Greg KH wrote:
Mike, I've reverted this patch, and I don't see any references
P.S. forgot to include diagnostic log. Kobject c0644890 is the source
of my woes. Printk's come below WARN_ON(is_ipmi_si_kobj). Post-tinker
log is huge, and probably not interesting.
[ 30.397160] kobject ipmi_devintf: registering. parent: NULL, set: module
[ 30.404033] kobject_uevent_env
On Tue, 2007-03-06 at 13:04 -0800, Greg KH wrote:
> On Tue, Mar 06, 2007 at 06:43:22AM +0100, Mike Galbraith wrote:
> > On Mon, 2007-03-05 at 16:25 -0800, Greg KH wrote:
> >
> > > Mike, I've reverted this patch, and I don't see any references leaking.
> > > And, as your patch released the
On Tue, Mar 06, 2007 at 06:43:22AM +0100, Mike Galbraith wrote:
> On Mon, 2007-03-05 at 16:25 -0800, Greg KH wrote:
>
> > Mike, I've reverted this patch, and I don't see any references leaking.
> > And, as your patch released the reference on the driver, and the
> > module_add_driver() call would
On (05/03/07 16:25), Greg KH didst pronounce:
> On Fri, Mar 02, 2007 at 12:58:33AM -0800, Andrew Morton wrote:
> >
> > -mm has a debugging patch which warns when atomic_dec_and_test() takes an
> > atomic_t negative
> >
On (05/03/07 16:25), Greg KH didst pronounce:
On Fri, Mar 02, 2007 at 12:58:33AM -0800, Andrew Morton wrote:
-mm has a debugging patch which warns when atomic_dec_and_test() takes an
atomic_t negative
On Tue, Mar 06, 2007 at 06:43:22AM +0100, Mike Galbraith wrote:
On Mon, 2007-03-05 at 16:25 -0800, Greg KH wrote:
Mike, I've reverted this patch, and I don't see any references leaking.
And, as your patch released the reference on the driver, and the
module_add_driver() call would not
On Tue, 2007-03-06 at 13:04 -0800, Greg KH wrote:
On Tue, Mar 06, 2007 at 06:43:22AM +0100, Mike Galbraith wrote:
On Mon, 2007-03-05 at 16:25 -0800, Greg KH wrote:
Mike, I've reverted this patch, and I don't see any references leaking.
And, as your patch released the reference on the
On Mon, 2007-03-05 at 16:25 -0800, Greg KH wrote:
> Mike, I've reverted this patch, and I don't see any references leaking.
> And, as your patch released the reference on the driver, and the
> module_add_driver() call would not grab a reference to the driver, only
> the module kobject, I don't
On Fri, Mar 02, 2007 at 12:58:33AM -0800, Andrew Morton wrote:
>
> -mm has a debugging patch which warns when atomic_dec_and_test() takes an
> atomic_t negative
> (ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.20/2.6.20-mm2/broken-out/detect-atomic-counter-underflows.patch).
>
On Fri, Mar 02, 2007 at 12:58:33AM -0800, Andrew Morton wrote:
-mm has a debugging patch which warns when atomic_dec_and_test() takes an
atomic_t negative
(ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.20/2.6.20-mm2/broken-out/detect-atomic-counter-underflows.patch).
On Mon, 2007-03-05 at 16:25 -0800, Greg KH wrote:
Mike, I've reverted this patch, and I don't see any references leaking.
And, as your patch released the reference on the driver, and the
module_add_driver() call would not grab a reference to the driver, only
the module kobject, I don't see
On Fri, Mar 02, 2007 at 12:58:33AM -0800, Andrew Morton wrote:
>
> -mm has a debugging patch which warns when atomic_dec_and_test() takes an
> atomic_t negative
> (ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.20/2.6.20-mm2/broken-out/detect-atomic-counter-underflows.patch).
>
-mm has a debugging patch which warns when atomic_dec_and_test() takes an
atomic_t negative
(ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.20/2.6.20-mm2/broken-out/detect-atomic-counter-underflows.patch).
When it is applied to current mainline, a simple `rmmod ipw2200'
-mm has a debugging patch which warns when atomic_dec_and_test() takes an
atomic_t negative
(ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.20/2.6.20-mm2/broken-out/detect-atomic-counter-underflows.patch).
When it is applied to current mainline, a simple `rmmod ipw2200'
On Fri, Mar 02, 2007 at 12:58:33AM -0800, Andrew Morton wrote:
-mm has a debugging patch which warns when atomic_dec_and_test() takes an
atomic_t negative
(ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.20/2.6.20-mm2/broken-out/detect-atomic-counter-underflows.patch).
32 matches
Mail list logo
