From: Randy Dunlap <randy.dunlap@oracle.com>
To: "werner" <w.landgraf@ru.ru>
Cc: linux-kernel@vger.kernel.org
Subject: Re: max2165 problem / kernel problem 2.6.32-git5
Date: Thu, 10 Dec 2009 22:46:59 -0800 [thread overview]
Message-ID: <20091210224659.cb5877d5.randy.dunlap@oracle.com> (raw)
In-Reply-To: <web-108998906@zbackend1.aha.ru>
On Thu, 10 Dec 2009 22:37:03 -0400 werner wrote:
> ref 2.6.32-git5
>
> 1) max2165 problem:
>
> CC arch/x86/boot/video-bios.o
> LD arch/x86/boot/setup.elf
> OBJCOPY arch/x86/boot/setup.bin
> OBJCOPY arch/x86/boot/vmlinux.bin
> HOSTCC arch/x86/boot/tools/build
> BUILD arch/x86/boot/bzImage
> Root device is (8, 1)
> Setup is 13980 bytes (padded to 14336 bytes).
> System is 8663 kB
> CRC c422073c
> Kernel: arch/x86/boot/bzImage is ready (#1)
> Building modules, stage 2.
> MODPOST 2104 modules
> ERROR: "__fixunsdfsi"
> [drivers/media/common/tuners/max2165.ko] undefined!
> ERROR: "__adddf3" [drivers/media/common/tuners/max2165.ko]
> undefined!
> ERROR: "__floatunsidf"
> [drivers/media/common/tuners/max2165.ko] undefined!
> WARNING: modpost: Found 8 section mismatch(es).
> To see full details build your kernel with:
> 'make CONFIG_DEBUG_SECTION_MISMATCH=y'
> make[1]: [__modpost] Error 1 (ignored)
> CC arch/x86/crypto/crc32c-intel.mod.o
> LD [M] arch/x86/crypto/crc32c-intel.ko
> CC arch/x86/crypto/salsa20-i586.mod.o
>
Patch for this was merged into the v4l/dvb tree today.
It should show up in mainline fairly soon.
>
>
> 2) The kernel problem (s) reported earlier, continue.
> Inclusive the xd out-of-memory error
---
~Randy
prev parent reply other threads:[~2009-12-11 6:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-11 2:37 max2165 problem / kernel problem 2.6.32-git5 werner
2009-12-11 6:46 ` Randy Dunlap [this message]
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=20091210224659.cb5877d5.randy.dunlap@oracle.com \
--to=randy.dunlap@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=w.landgraf@ru.ru \
/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