Re: [2.6.16-gitX] initcall at 0xffffffff804615d1: returned with error code -1

Voluspa <[email protected]> writes:
> 
> Those options are just wish-thinking since the machine doesn't have that kind of timer.
> So the warning should go away when I turn them off. Sorry about the noise.

I fixed it here

-Andi
-
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:
- [2.6.16-gitX] initcall at 0xffffffff804615d1: returned with error code -1
  - From: Voluspa <[email protected]>
- Re: [2.6.16-gitX] initcall at 0xffffffff804615d1: returned with error code -1
  - From: Andrew Morton <[email protected]>
- Re: [2.6.16-gitX] initcall at 0xffffffff804615d1: returned with error code -1
  - From: Voluspa <[email protected]>

Prev by Date: Re: [rfc][patch] improved interactive starvation patch against 2.6.16
Next by Date: Re: [PATCH][RFC] splice support
Previous by thread: Re: [2.6.16-gitX] initcall at 0xffffffff804615d1: returned with error code -1
Next by thread: Hook collie frontlight into sysfs
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]