From: lambert.quentin@gmail.com (Quentin Lambert)
To: kernelnewbies@lists.kernelnewbies.org
Subject: Unable to boot linux-next build
Date: Fri, 9 Sep 2016 10:17:31 +0200 [thread overview]
Message-ID: <055c318b-d8eb-52ec-3f8e-6a934a511ed7@gmail.com> (raw)
In-Reply-To: <CANc+2y7wtM1OqhmwnbG1enDYKUqpapYrPL1rqXVFzu6sFkPhyw@mail.gmail.com>
On 09/09/2016 09:33, PrasannaKumar Muralidharan wrote:
> On 8 September 2016 at 18:16, Quentin Lambert <lambert.quentin@gmail.com> wrote:
>> I have been trying to build and boot the last version available on linux-next.
>> During the build I am being prompted with "has no CRC!" warnings for a bunch
>> of modules.
>>
>> Has a result I get the following lines in the Module.symvers:
>>
>> [qlambert at sloth linux-next]$ grep 0x00000 Module.symvers
>> 0x00000000 phys_base vmlinux EXPORT_SYMBOL
>> 0x00000000 memmove vmlinux EXPORT_SYMBOL
>> 0x00000000 __copy_user_nocache vmlinux EXPORT_SYMBOL
>> 0x00000000 __get_user_4 vmlinux EXPORT_SYMBOL
>> 0x00000000 __put_user_4 vmlinux EXPORT_SYMBOL
>> 0x00000000 __memcpy vmlinux EXPORT_SYMBOL
>> 0x00000000 __fentry__ vmlinux EXPORT_SYMBOL
>> 0x00000000 memset vmlinux EXPORT_SYMBOL
>> 0x00000000 __sw_hweight64 vmlinux EXPORT_SYMBOL
>> 0x00000000 __sw_hweight32 vmlinux EXPORT_SYMBOL
>> 0x00000000 memcpy_mcsafe_unrolled vmlinux EXPORT_SYMBOL_GPL
>> 0x00000000 memcpy vmlinux EXPORT_SYMBOL
>> 0x00000000 copy_user_enhanced_fast_string vmlinux EXPORT_SYMBOL
>> 0x00000000 clear_page vmlinux EXPORT_SYMBOL
>> 0x00000000 __put_user_2 vmlinux EXPORT_SYMBOL
>> 0x00000000 __get_user_2 vmlinux EXPORT_SYMBOL
>> 0x00000000 copy_page vmlinux EXPORT_SYMBOL
>> 0x00000000 copy_user_generic_string vmlinux EXPORT_SYMBOL
>> 0x00000000 _copy_to_user vmlinux EXPORT_SYMBOL
>> 0x00000000 ___preempt_schedule vmlinux EXPORT_SYMBOL
>> 0x00000000 __memmove vmlinux EXPORT_SYMBOL
>> 0x00000000 empty_zero_page vmlinux EXPORT_SYMBOL
>> 0x00000000 __get_user_8 vmlinux EXPORT_SYMBOL
>> 0x00000000 __put_user_8 vmlinux EXPORT_SYMBOL
>> 0x00000000 _copy_from_user vmlinux EXPORT_SYMBOL
>> 0x00000000 native_load_gs_index vmlinux EXPORT_SYMBOL
>> 0x00000000 __memset vmlinux EXPORT_SYMBOL
>> 0x00000000 ___preempt_schedule_notrace vmlinux EXPORT_SYMBOL
>> 0x00000000 __put_user_1 vmlinux EXPORT_SYMBOL
>> 0x00000000 __get_user_1 vmlinux EXPORT_SYMBOL
>> 0x00000000 copy_user_generic_unrolled vmlinux EXPORT_SYMBOL
>>
>> If I ignore these and go on to boot the resulting kernel. I am left with:
>>
>> ERROR: Unable to find root device 'UUID=<omitted>'
>>
>> I am then dropped to a recovery shell where the keyboard is not answering.
>>
>> The UUID is valid and is the same being used when I boot the HEAD of the linux
>> tree. Prior to failing to find the root device, the kernel prints a series of
>> message for each of the above symbol:
>>
>> scsi_mod: no symbol version for <foo>
>> scsi_mod: Unknown symbol <foo> (err -22)
>>
>> Therefore, I suspect that the missing CRC messages are linked to the issue.
>>
>> I have git bisected this behavior to the patch 784d5699edd.
> You can just provide the details and the git bisect result. I think it
> should be fine.
OK
> But before that make sure your root device is
> detected. If scsi module did not work most likely that your hard disk
> is not detected.
So, I am going to look into properly making sure that my hard disk is
detected but
I thought that it being detected by other build was the proof I
required. I am sending
this message from a build more recent than 4.8.0-rc5 and I successfully
booted a
build of the kernel at the commit that directly precede 784d5699edd.
next prev parent reply other threads:[~2016-09-09 8:17 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-08 12:46 Unable to boot linux-next build Quentin Lambert
2016-09-09 7:33 ` PrasannaKumar Muralidharan
2016-09-09 8:17 ` Quentin Lambert [this message]
2016-09-09 8:24 ` PrasannaKumar Muralidharan
2016-09-09 8:31 Quentin Lambert
2016-09-11 18:00 ` Quentin Lambert
2016-10-19 15:15 ` Alban Browaeys
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=055c318b-d8eb-52ec-3f8e-6a934a511ed7@gmail.com \
--to=lambert.quentin@gmail.com \
--cc=kernelnewbies@lists.kernelnewbies.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.