From: Sachin Sant <sachinp@in.ibm.com>
To: linux-next@vger.kernel.org
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
LKML <linux-kernel@vger.kernel.org>,
Rusty Russell <rusty@rustcorp.com.au>
Subject: [-next June 4] Boot failure on x86_64,PPC64
Date: Fri, 04 Jun 2010 15:03:50 +0530 [thread overview]
Message-ID: <4C08C87E.6030004@in.ibm.com> (raw)
In-Reply-To: <20100604153006.fa15c770.sfr@canb.auug.org.au>
Today's next failed to boot on variety of hardware (x86_64,PPC64)
with following messages :
doing fast boot
scsi_mod: module_layout: kernel tainted.
Disabling lock debugging due to kernel taint
scsi_mod: module license 'unspecified' taints kernel.
scsi_mod: Unknown symbol add_uevent_var (err 0)
scsi_mod: Unknown symbol blk_queue_rq_timed_out (err 0)
scsi_mod: Unknown symbol blk_end_request_err (err 0)
scsi_mod: Unknown symbol device_schedule_callback_owner (err 0)
scsi_mod: Unknown symbol dev_set_name (err 0)
........ <SNIP> ......
WARNING: Error iscsi_transport_sas: Unknown symbol scsi_mode_sense (err 0)
Inserting scsi_moscsi_transport_sas: Unknown symbol dev_set_name (err 0)
d (/lib/modules/scsi_transport_sas: Unknown symbol transport_remove_device (err 0)
2.6.35-rc1-autotscsi_transport_sas: Unknown symbol scsi_get_vpd_page (err 0)
est-next-2010060scsi_transport_sas: Unknown symbol device_initialize (err 0)
4/kernel/driversscsi_transport_sas: Unknown symbol device_for_each_child (err 0)
/scsi/scsi_mod.kscsi_transport_sas: Unknown symbol get_device (err 0)
o): Unknown symbscsi_transport_sas: Unknown symbol bsg_unregister_queue (err 0)
ol in module, orscsi_transport_sas: Unknown symbol transport_setup_device (err 0)
unknown parametscsi_transport_sas: Unknown symbol put_device (err 0)
and many more scsi_mod related messages.
Yesterday's problem of OOPS during init/load_module seem to have disappeared.
Thanks
-Sachin
--
---------------------------------
Sachin Sant
IBM Linux Technology Center
India Systems and Technology Labs
Bangalore, India
---------------------------------
next prev parent reply other threads:[~2010-06-04 9:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-04 5:30 linux-next: Tree for June 4 Stephen Rothwell
2010-06-04 9:33 ` Sachin Sant [this message]
2010-06-04 16:54 ` linux-next: Tree for June 4 (kernel/module.c) Randy Dunlap
[not found] ` <20100604153006.fa15c770.sfr-3FnU+UHB4dNDw9hX6IcOSA@public.gmane.org>
2010-06-04 16:56 ` linux-next: Tree for June 4 (mac80211) Randy Dunlap
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=4C08C87E.6030004@in.ibm.com \
--to=sachinp@in.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=rusty@rustcorp.com.au \
--cc=sfr@canb.auug.org.au \
/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;
as well as URLs for NNTP newsgroup(s).