From jidong.xiao@gmail.com Mon Aug 4 23:35:34 2008 Received: with ECARTIS (v1.0.0; list kdb); Mon, 04 Aug 2008 23:35:44 -0700 (PDT) Received: from cuda.sgi.com (cuda1.sgi.com [192.48.168.28]) by oss.sgi.com (8.12.11.20060308/8.12.11/SuSE Linux 0.7) with ESMTP id m756ZYV2015824 for ; Mon, 4 Aug 2008 23:35:34 -0700 X-ASG-Debug-ID: 1217918207-4d0e00530000-sLlkUa X-Barracuda-URL: http://cuda.sgi.com:80/cgi-bin/mark.cgi Received: from fk-out-0910.google.com (localhost [127.0.0.1]) by cuda.sgi.com (Spam Firewall) with ESMTP id AB9F81246C51 for ; Mon, 4 Aug 2008 23:36:47 -0700 (PDT) Received: from fk-out-0910.google.com (fk-out-0910.google.com [209.85.128.189]) by cuda.sgi.com with ESMTP id Bb9fI4p0IpKMc07o for ; Mon, 04 Aug 2008 23:36:47 -0700 (PDT) Received: by fk-out-0910.google.com with SMTP id 26so2576377fkx.4 for ; Mon, 04 Aug 2008 23:36:46 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:cc:mime-version:content-type:content-transfer-encoding :content-disposition; bh=CMd1TykYP9sgrcTXyS5O1Dr7tBD+cTb49F7s4N4YW1s=; b=Uql2Z2auWKUE1tS0IdxJ8p4P0emeFXbemMXo42Xx/+tVf42V6vD1KV4yiBB+dxLdD8 HYvWhX705gJu4S0VrO6K1zXm9Qw3CSPGfBXVNtpJ6sS7XxHfLy+WV9I4Dq9E9HujruVC pwqoYxC/o00njnAQEqj4QzEekvtUJw0VMp6Us= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:mime-version:content-type :content-transfer-encoding:content-disposition; b=qEmNm876jyJ25CjK5hSa219TmL788U5hqribT/ReTPOuaqx+EkRrjIszE/FBwy3m+a wBIfYHynAqDpEomtsc5XH+xeq2r+LhMKhGD9hTBcdx5Z6C89LrEXsF4JodHmZcT4A+rh 17Qp4lSjR17DfGxdzT86X60Vd9ulSoQ0F1ch4= Received: by 10.125.154.9 with SMTP id g9mr34708mko.40.1217918206257; Mon, 04 Aug 2008 23:36:46 -0700 (PDT) Received: by 10.125.151.11 with HTTP; Mon, 4 Aug 2008 23:36:46 -0700 (PDT) Message-ID: <4104961b0808042336l60e57f1dn6ff89ad3ac4c0ad1@mail.gmail.com> Date: Tue, 5 Aug 2008 14:36:46 +0800 From: "jidong xiao" To: "Jay Lan" X-ASG-Orig-Subj: [PATCH] Check ohci->hcca before dereference it Subject: [PATCH] Check ohci->hcca before dereference it Cc: KDB , "Konstantin Baydarov" , "Aaron Young" , "Alan Stern" MIME-Version: 1.0 Content-type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Content-Disposition: inline X-Barracuda-Connect: fk-out-0910.google.com[209.85.128.189] X-Barracuda-Start-Time: 1217918208 X-Barracuda-Bayes: INNOCENT GLOBAL 0.0000 1.0000 -2.0210 X-Barracuda-Virus-Scanned: by cuda.sgi.com at sgi.com X-Barracuda-Spam-Score: -2.02 X-Barracuda-Spam-Status: No, SCORE=-2.02 using per-user scores of TAG_LEVEL=2.0 QUARANTINE_LEVEL=1000.0 KILL_LEVEL=2.1 tests= X-Barracuda-Spam-Report: Code version 3.2, rules version 3.2.1.1801 Rule breakdown below pts rule name description ---- ---------------------- -------------------------------------------------- X-archive-position: 1430 X-ecartis-version: Ecartis v1.0.0 Sender: kdb-bounce@oss.sgi.com Errors-to: kdb-bounce@oss.sgi.com X-original-sender: jidong.xiao@gmail.com Precedence: bulk X-list: kdb Fix up the NULL pointer deference issue in ohci_kdb_poll_char. Without this fixup, we may encounter Oops while we invoke kdb via ohci usb keyboard. One of my colleagues encountered this while he is using RHEL update1 kernels with kdb patches applied. [root@localhost ~]# Entering kdb (task 0xffff8101338e1100 pid 0) on cpu 1 due to Keyboard Entry [1]kdb> Unable to handle kernel NULL pointer dereference at 0000000000000084 RIP: [] :ohci_hcd:ohci_kdb_poll+0x75/0x18e PGD 1119d8067 PUD 111b5e067 PMD 0 Oops: 0000 [1] SMP last sysfs file: /devices/pci0000:00/0000:00:01.0/irq kdb: Debugger re-entered on cpu 1, new reason = 5 Not executing a kdb command Cannot recover, allowing event to proceed This issue occurs since ohci->hcca is dereferenced while it's NULL pointer. 1017 if (ohci->hcca->done_head) { 1018 dl_done_list_kdb (ohci, urb); 1019 ohci_writel (ohci, OHCI_INTR_WDH, ®s->intrstatus); 1020 // flush the pci write 1021 (void) ohci_readl (ohci, &ohci->regs->control); 1022 1023 return 0; 1024 } Obviously this issue still exists in the latest kdb patches. So I created a patch against 2.6.26-rc9 kernel/kdb patches. Signed-off-by: Jason Xiao (jidong.xiao@gmail.com) Index: linux/drivers/usb/host/ohci-hcd.c =================================================================== --- linux-2.6.26.orig/drivers/usb/host/ohci-hcd.c 2008-08-05 21:53:16.000000000 +0800 +++ linux-2.6.26/drivers/usb/host/ohci-hcd.c 2008-08-05 21:54:36.000000000 +0800 @@ -978,7 +978,7 @@ ohci_kdb_poll_char(struct urb *urb) ohci = (struct ohci_hcd *) hcd_to_ohci(bus_to_hcd(urb->dev->bus)); /* make sure */ - if (!ohci) + if (!ohci || !ohci->hcca) return -1; if (!HC_IS_RUNNING (ohci_to_hcd(ohci)->state)) Regards Jason --------------------------- Use http://oss.sgi.com/ecartis to modify your settings or to unsubscribe. From jlan@sgi.com Tue Aug 5 13:54:43 2008 Received: with ECARTIS (v1.0.0; list kdb); Tue, 05 Aug 2008 13:54:52 -0700 (PDT) Received: from cthulhu.engr.sgi.com (cthulhu.engr.sgi.com [192.26.80.2]) by oss.sgi.com (8.12.11.20060308/8.12.11/SuSE Linux 0.7) with ESMTP id m75KsgfP006372 for ; Tue, 5 Aug 2008 13:54:43 -0700 Received: from [127.0.0.1] (sshgate.corp.sgi.com [198.149.36.12]) by cthulhu.engr.sgi.com (8.12.10/8.12.10/SuSE Linux 0.7) with ESMTP id m75KttR9021915; Tue, 5 Aug 2008 13:55:56 -0700 Message-ID: <4898BE36.5000307@sgi.com> Date: Tue, 05 Aug 2008 13:55:18 -0700 From: Jay Lan User-Agent: Thunderbird 1.5 (X11/20060317) MIME-Version: 1.0 To: jidong xiao CC: KDB , Konstantin Baydarov , Aaron Young , Alan Stern Subject: Re: [PATCH] Check ohci->hcca before dereference it References: <4104961b0808042336l60e57f1dn6ff89ad3ac4c0ad1@mail.gmail.com> In-Reply-To: <4104961b0808042336l60e57f1dn6ff89ad3ac4c0ad1@mail.gmail.com> X-Enigmail-Version: 0.94.0.0 Content-type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit X-archive-position: 1431 X-ecartis-version: Ecartis v1.0.0 Sender: kdb-bounce@oss.sgi.com Errors-to: kdb-bounce@oss.sgi.com X-original-sender: jlan@sgi.com Precedence: bulk X-list: kdb jidong xiao wrote: > Fix up the NULL pointer deference issue in ohci_kdb_poll_char. Hi Jason, Thanks for the patch. I will apply it on next update. Thanks, - jay > > Without this fixup, we may encounter Oops while we invoke kdb via ohci > usb keyboard. One of my colleagues encountered this while he is using > RHEL update1 kernels with kdb patches applied. > > [root@localhost ~]# > Entering kdb (task 0xffff8101338e1100 pid 0) on cpu 1 due to Keyboard Entry > [1]kdb> Unable to handle kernel NULL pointer dereference at 0000000000000084 > RIP: > [] :ohci_hcd:ohci_kdb_poll+0x75/0x18e > PGD 1119d8067 PUD 111b5e067 PMD 0 > Oops: 0000 [1] SMP > last sysfs file: /devices/pci0000:00/0000:00:01.0/irq > kdb: Debugger re-entered on cpu 1, new reason = 5 > Not executing a kdb command > Cannot recover, allowing event to proceed > > This issue occurs since ohci->hcca is dereferenced while it's NULL pointer. > > 1017 if (ohci->hcca->done_head) { > 1018 dl_done_list_kdb (ohci, urb); > 1019 ohci_writel (ohci, OHCI_INTR_WDH, ®s->intrstatus); > 1020 // flush the pci write > 1021 (void) ohci_readl (ohci, &ohci->regs->control); > 1022 > 1023 return 0; > 1024 } > > Obviously this issue still exists in the latest kdb patches. So I > created a patch against 2.6.26-rc9 kernel/kdb patches. > > Signed-off-by: Jason Xiao (jidong.xiao@gmail.com) > Index: linux/drivers/usb/host/ohci-hcd.c > =================================================================== > --- linux-2.6.26.orig/drivers/usb/host/ohci-hcd.c 2008-08-05 > 21:53:16.000000000 +0800 > +++ linux-2.6.26/drivers/usb/host/ohci-hcd.c 2008-08-05 > 21:54:36.000000000 +0800 > @@ -978,7 +978,7 @@ ohci_kdb_poll_char(struct urb *urb) > ohci = (struct ohci_hcd *) hcd_to_ohci(bus_to_hcd(urb->dev->bus)); > > /* make sure */ > - if (!ohci) > + if (!ohci || !ohci->hcca) > return -1; > > if (!HC_IS_RUNNING (ohci_to_hcd(ohci)->state)) > > > Regards > Jason --------------------------- Use http://oss.sgi.com/ecartis to modify your settings or to unsubscribe. From jlan@sgi.com Wed Aug 6 11:27:04 2008 Received: with ECARTIS (v1.0.0; list kdb); Wed, 06 Aug 2008 11:27:11 -0700 (PDT) Received: from kluge.engr.sgi.com (kluge.engr.sgi.com [192.102.96.102]) by oss.sgi.com (8.12.11.20060308/8.12.11/SuSE Linux 0.7) with ESMTP id m76IR4kw006731 for ; Wed, 6 Aug 2008 11:27:04 -0700 Received: from [150.166.8.78] (aware.engr.sgi.com [150.166.8.78]) by kluge.engr.sgi.com (SGI-8.12.5/8.12.5) with ESMTP id m76ISJCD1450928; Wed, 6 Aug 2008 11:28:19 -0700 (PDT) Message-ID: <4899ED43.6060306@sgi.com> Date: Wed, 06 Aug 2008 11:28:19 -0700 From: Jay Lan User-Agent: Thunderbird 2.0.0.6 (X11/20070801) MIME-Version: 1.0 To: KDB Subject: question to those who know x86 irq vectors Content-type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit X-archive-position: 1432 X-ecartis-version: Ecartis v1.0.0 Sender: kdb-bounce@oss.sgi.com Errors-to: kdb-bounce@oss.sgi.com X-original-sender: jlan@sgi.com Precedence: bulk X-list: kdb Hi, KDB defines KDB_VECTOR for x86 machines #define KDB_VECTOR 0xfb for x86_64 systems, and #define KDB_VECTOR 0xf9 for x86_32 systems. In 2.6.27-rc, unfortunately, 0xf9-0xff are all being used. Is it safe for KDB to use 0xf8? The f0-f7 are used for TLB flush. Thanks, - jay --------------------------- Use http://oss.sgi.com/ecartis to modify your settings or to unsubscribe. From hugh@veritas.com Wed Aug 6 11:59:34 2008 Received: with ECARTIS (v1.0.0; list kdb); Wed, 06 Aug 2008 11:59:37 -0700 (PDT) Received: from cuda.sgi.com (cuda2.sgi.com [192.48.168.29]) by oss.sgi.com (8.12.11.20060308/8.12.11/SuSE Linux 0.7) with ESMTP id m76IxY70017140 for ; Wed, 6 Aug 2008 11:59:34 -0700 X-ASG-Debug-ID: 1218049248-536f017b0000-sLlkUa X-Barracuda-URL: http://cuda.sgi.com:80/cgi-bin/mark.cgi Received: from extu-mxob-2.symantec.com (localhost [127.0.0.1]) by cuda.sgi.com (Spam Firewall) with ESMTP id 8D33A365687; Wed, 6 Aug 2008 12:00:48 -0700 (PDT) Received: from extu-mxob-2.symantec.com (extu-mxob-2.symantec.com [216.10.194.135]) by cuda.sgi.com with ESMTP id 6ELXYeuet0vllAXj; Wed, 06 Aug 2008 12:00:48 -0700 (PDT) Received: from tus1opsmtapin01.ges.symantec.com (tus1opsmtapin01.ges.symantec.com [192.168.214.43]) by extu-mxob-2.symantec.com (8.14.1/8.14.1) with ESMTP id m76J0mI4019180 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 6 Aug 2008 12:00:48 -0700 Received: from oni.engba.symantec.com ([10.182.128.240] helo=megami.veritas.com) by tus1opsmtapin01.ges.symantec.com with smtp (Exim 4.67) (envelope-from ) id 1KQoFc-0004Tx-8M; Wed, 06 Aug 2008 12:00:48 -0700 Received: from [172.21.33.127]([172.21.33.127]) (977 bytes) by megami.veritas.com via sendmail with P:esmtp/R:smart_host/T:smtp (sender: ) id for ; Wed, 6 Aug 2008 12:00:47 -0700 (PDT) (Smail-3.2.0.101 1997-Dec-17 #15 built 2001-Aug-30) Date: Wed, 6 Aug 2008 20:01:07 +0100 (BST) From: Hugh Dickins X-X-Sender: hugh@blonde.site To: Jay Lan cc: KDB X-ASG-Orig-Subj: Re: question to those who know x86 irq vectors Subject: Re: question to those who know x86 irq vectors In-Reply-To: <4899ED43.6060306@sgi.com> Message-ID: References: <4899ED43.6060306@sgi.com> MIME-Version: 1.0 Content-type: text/plain; charset=US-ASCII X-Barracuda-Connect: extu-mxob-2.symantec.com[216.10.194.135] X-Barracuda-Start-Time: 1218049249 X-Barracuda-Bayes: INNOCENT GLOBAL 0.1715 1.0000 -0.9812 X-Barracuda-Virus-Scanned: by cuda.sgi.com at sgi.com X-Barracuda-Spam-Score: -0.98 X-Barracuda-Spam-Status: No, SCORE=-0.98 using per-user scores of TAG_LEVEL=2.0 QUARANTINE_LEVEL=1000.0 KILL_LEVEL=2.1 tests= X-Barracuda-Spam-Report: Code version 3.2, rules version 3.2.1.1945 Rule breakdown below pts rule name description ---- ---------------------- -------------------------------------------------- Content-Transfer-Encoding: 8bit X-archive-position: 1433 X-ecartis-version: Ecartis v1.0.0 Sender: kdb-bounce@oss.sgi.com Errors-to: kdb-bounce@oss.sgi.com X-original-sender: hugh@veritas.com Precedence: bulk X-list: kdb On Wed, 6 Aug 2008, Jay Lan wrote: > > KDB defines KDB_VECTOR for x86 machines > #define KDB_VECTOR 0xfb for x86_64 systems, > and #define KDB_VECTOR 0xf9 for x86_32 systems. > > In 2.6.27-rc, unfortunately, 0xf9-0xff are all being used. Is it > safe for KDB to use 0xf8? The f0-f7 are used for TLB flush. I've limited knowledge here, but yes, that works fine. Hugh --------------------------- Use http://oss.sgi.com/ecartis to modify your settings or to unsubscribe. From jlan@sgi.com Wed Aug 6 12:22:06 2008 Received: with ECARTIS (v1.0.0; list kdb); Wed, 06 Aug 2008 12:22:09 -0700 (PDT) Received: from kluge.engr.sgi.com (kluge.engr.sgi.com [192.102.96.102]) by oss.sgi.com (8.12.11.20060308/8.12.11/SuSE Linux 0.7) with ESMTP id m76JM6kD028969 for ; Wed, 6 Aug 2008 12:22:06 -0700 Received: from [150.166.8.78] (aware.engr.sgi.com [150.166.8.78]) by kluge.engr.sgi.com (SGI-8.12.5/8.12.5) with ESMTP id m76JNLCD1461879; Wed, 6 Aug 2008 12:23:21 -0700 (PDT) Message-ID: <4899FA29.2010107@sgi.com> Date: Wed, 06 Aug 2008 12:23:21 -0700 From: Jay Lan User-Agent: Thunderbird 2.0.0.6 (X11/20070801) MIME-Version: 1.0 To: Hugh Dickins CC: KDB Subject: Re: question to those who know x86 irq vectors References: <4899ED43.6060306@sgi.com> In-Reply-To: Content-type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit X-archive-position: 1434 X-ecartis-version: Ecartis v1.0.0 Sender: kdb-bounce@oss.sgi.com Errors-to: kdb-bounce@oss.sgi.com X-original-sender: jlan@sgi.com Precedence: bulk X-list: kdb Hugh Dickins wrote: > On Wed, 6 Aug 2008, Jay Lan wrote: >> KDB defines KDB_VECTOR for x86 machines >> #define KDB_VECTOR 0xfb for x86_64 systems, >> and #define KDB_VECTOR 0xf9 for x86_32 systems. >> >> In 2.6.27-rc, unfortunately, 0xf9-0xff are all being used. Is it >> safe for KDB to use 0xf8? The f0-f7 are used for TLB flush. > > I've limited knowledge here, but yes, that works fine. Thanks for your feedback, Hugh! Mike Travis also wrote me: : Alan Meyer has a new patch going in to assign vectors dynamically. : That might be the way to go (at least for x86_64). That sounds great. I will use 0xf8 for x86_64 for now. Regards, - jay > > Hugh > --------------------------- > Use http://oss.sgi.com/ecartis to modify your settings or to unsubscribe. --------------------------- Use http://oss.sgi.com/ecartis to modify your settings or to unsubscribe. From jlan@sgi.com Fri Aug 15 12:24:39 2008 Received: with ECARTIS (v1.0.0; list kdb); Fri, 15 Aug 2008 12:24:45 -0700 (PDT) Received: from cthulhu.engr.sgi.com (cthulhu.engr.sgi.com [192.26.80.2]) by oss.sgi.com (8.12.11.20060308/8.12.11/SuSE Linux 0.7) with ESMTP id m7FJOd42014036 for ; Fri, 15 Aug 2008 12:24:39 -0700 Received: from [127.0.0.1] (sshgate.corp.sgi.com [198.149.36.12]) by cthulhu.engr.sgi.com (8.12.10/8.12.10/SuSE Linux 0.7) with ESMTP id m7FJPvR9014911; Fri, 15 Aug 2008 12:25:57 -0700 Message-ID: <48A5D821.90100@sgi.com> Date: Fri, 15 Aug 2008 12:25:21 -0700 From: Jay Lan User-Agent: Thunderbird 1.5 (X11/20060317) MIME-Version: 1.0 To: KDB Subject: [PATCH] mm_online_pgdat_export_symbol X-Enigmail-Version: 0.94.0.0 Content-type: text/plain Content-Transfer-Encoding: 8bit X-archive-position: 1435 X-ecartis-version: Ecartis v1.0.0 Sender: kdb-bounce@oss.sgi.com Errors-to: kdb-bounce@oss.sgi.com X-original-sender: jlan@sgi.com Precedence: bulk X-list: kdb The mm symbols, first_online_pgdat and next_online_pgdat, are referenced by kdbm_vm.c for printing a struct pglist_data through a kdb 'pgdat' command. The symbols are referenced for printing only. You need the export if CONFIG_KDB_MODULES=m. This patch was generated against 2.6.27-rc2 and will be integrated into the kdb patchset for 2.6.27-rc3 or later. Signed-off-by Jay Lan -- Attached file included as plaintext by Ecartis -- -- File: mm_online_pgdat_export_symbol The mm symbols, first_online_pgdat and next_online_pgdat, are referenced by kdbm_vm.c for printing a struct pglist_data through a kdb 'pgdat' command. The symbols are referenced for printing only. You need the export if CONFIG_KDB_MODULES=m. This patch was generated against 2.6.27-rc2 and will be integrated into next kdb patchset for 2.6.27-rc3 or later. Signed-off-by Jay Lan --- mm/mmzone.c | 4 ++++ 1 file changed, 4 insertions(+) Index: linux/mm/mmzone.c =================================================================== --- linux.orig/mm/mmzone.c 2008-07-13 14:51:29.000000000 -0700 +++ linux/mm/mmzone.c 2008-08-15 11:47:49.733470596 -0700 @@ -22,6 +22,10 @@ struct pglist_data *next_online_pgdat(st return NULL; return NODE_DATA(nid); } +#ifdef CONFIG_KDB +EXPORT_SYMBOL(first_online_pgdat); +EXPORT_SYMBOL(next_online_pgdat); +#endif /* * next_zone - helper magic for for_each_zone() --------------------------- Use http://oss.sgi.com/ecartis to modify your settings or to unsubscribe. From jlan@sgi.com Fri Aug 15 12:49:14 2008 Received: with ECARTIS (v1.0.0; list kdb); Fri, 15 Aug 2008 12:49:17 -0700 (PDT) Received: from cthulhu.engr.sgi.com (cthulhu.engr.sgi.com [192.26.80.2]) by oss.sgi.com (8.12.11.20060308/8.12.11/SuSE Linux 0.7) with ESMTP id m7FJmmIB014953 for ; Fri, 15 Aug 2008 12:49:13 -0700 Received: from [127.0.0.1] (sshgate.corp.sgi.com [198.149.36.12]) by cthulhu.engr.sgi.com (8.12.10/8.12.10/SuSE Linux 0.7) with ESMTP id m7FJo4R9017108; Fri, 15 Aug 2008 12:50:04 -0700 Message-ID: <48A5DDC5.6090404@sgi.com> Date: Fri, 15 Aug 2008 12:49:25 -0700 From: Jay Lan User-Agent: Thunderbird 1.5 (X11/20060317) MIME-Version: 1.0 To: KDB Subject: [ANNOUNCE] Support 'kdump' command from KDB in 2.6.27-rc2-*-2.bz2 patchset X-Enigmail-Version: 0.94.0.0 Content-type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit X-archive-position: 1436 X-ecartis-version: Ecartis v1.0.0 Sender: kdb-bounce@oss.sgi.com Errors-to: kdb-bounce@oss.sgi.com X-original-sender: jlan@sgi.com Precedence: bulk X-list: kdb Hi, The kdb 2.6.27-rc2-*-2.bz2 patchset contains implementation of 'kdump' command. It was based on the original patch posted by Dan Aloni last year, then modified to provide i386 support by Jason Xiao. I added IA64 support. I also added hooks to intercept and drop to KDB from oops. It looks quite different from your patch, Jason, especially in kdb/kdbmain.c to a style i like better. Sorry about that. This implementation would catch die, panic, MCA, NMI conditions and drop into KDB. After analyze the oops situation and data, you can issue 'kdump' command and a kdump vmcore will be created. I do not intercept 'echo c > /proc/sysrq-trigger' since i see no need to create extra works if users already decide to create a vmcore from user space. Besides, you can use KDB key sequence to break into KDB and do a 'kdump' command to take a dump as well. Doing a 'go' after panic is undefined, and it also depends on the value of CONFIG_KDB_CONTINUE_CATASTROPHIC. So, do 'kdump' after panic if you want take a vmcore. I have tested on IA64 and X86_64 to see a kdump kernel booted up and /proc/vmcore created. Due to bugs of makedumpfile and crash against the latest kernels, i did not run crash to check validity of the vmcore though. Please report any bugs to me. Thanks! Regards, - jay --------------------------- Use http://oss.sgi.com/ecartis to modify your settings or to unsubscribe. From hugh@veritas.com Sun Aug 17 06:32:14 2008 Received: with ECARTIS (v1.0.0; list kdb); Sun, 17 Aug 2008 06:32:24 -0700 (PDT) Received: from cuda.sgi.com (cuda2.sgi.com [192.48.168.29]) by oss.sgi.com (8.12.11.20060308/8.12.11/SuSE Linux 0.7) with ESMTP id m7HDWDT7023338 for ; Sun, 17 Aug 2008 06:32:14 -0700 X-ASG-Debug-ID: 1218980012-1c14004f0000-sLlkUa X-Barracuda-URL: http://cuda.sgi.com:80/cgi-bin/mark.cgi Received: from extu-mxob-2.symantec.com (localhost [127.0.0.1]) by cuda.sgi.com (Spam Firewall) with ESMTP id 7B1397A21B2 for ; Sun, 17 Aug 2008 06:33:32 -0700 (PDT) Received: from extu-mxob-2.symantec.com (extu-mxob-2.symantec.com [216.10.194.135]) by cuda.sgi.com with ESMTP id CZ5yaJDX2Of3P27F for ; Sun, 17 Aug 2008 06:33:32 -0700 (PDT) Received: from tus1opsmtapin01.ges.symantec.com (tus1opsmtapin01.ges.symantec.com [192.168.214.43]) by extu-mxob-2.symantec.com (8.14.1/8.14.1) with ESMTP id m7HDXSsU015383 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sun, 17 Aug 2008 06:33:29 -0700 Received: from oni.engba.symantec.com ([10.182.128.240] helo=megami.veritas.com) by tus1opsmtapin01.ges.symantec.com with smtp (Exim 4.67) (envelope-from ) id 1KUiNc-0002Ui-Ny; Sun, 17 Aug 2008 06:33:12 -0700 Received: from [172.20.17.8]([172.20.17.8]) (5301 bytes) by megami.veritas.com via sendmail with P:esmtp/R:smart_host/T:smtp (sender: ) id for ; Sun, 17 Aug 2008 06:33:10 -0700 (PDT) (Smail-3.2.0.101 1997-Dec-17 #15 built 2001-Aug-30) Date: Sun, 17 Aug 2008 14:33:48 +0100 (BST) From: Hugh Dickins X-X-Sender: hugh@blonde.site To: Satish Eerpini cc: Valdis.Kletnieks@vt.edu, kdb@oss.sgi.com X-ASG-Orig-Subj: Re: patching kdb to Centos kernel : error Subject: Re: patching kdb to Centos kernel : error In-Reply-To: <93655eb70808170413w43e62311i713166beb38a4897@mail.gmail.com> Message-ID: References: <93655eb70808162300i4286eac9p9aa34cf23359ff72@mail.gmail.com> <23408.1218955331@turing-police.cc.vt.edu> <93655eb70808170413w43e62311i713166beb38a4897@mail.gmail.com> MIME-Version: 1.0 Content-type: text/plain; charset=US-ASCII X-Barracuda-Connect: extu-mxob-2.symantec.com[216.10.194.135] X-Barracuda-Start-Time: 1218980013 X-Barracuda-Bayes: INNOCENT GLOBAL 0.0000 1.0000 -2.0209 X-Barracuda-Virus-Scanned: by cuda.sgi.com at sgi.com X-Barracuda-Spam-Score: -2.02 X-Barracuda-Spam-Status: No, SCORE=-2.02 using per-user scores of TAG_LEVEL=2.0 QUARANTINE_LEVEL=1000.0 KILL_LEVEL=2.1 tests= X-Barracuda-Spam-Report: Code version 3.2, rules version 3.2.1.2912 Rule breakdown below pts rule name description ---- ---------------------- -------------------------------------------------- Content-Transfer-Encoding: 8bit X-archive-position: 1437 X-ecartis-version: Ecartis v1.0.0 Sender: kdb-bounce@oss.sgi.com Errors-to: kdb-bounce@oss.sgi.com X-original-sender: hugh@veritas.com Precedence: bulk X-list: kdb Please try kdb@oss.sgi.com (Cc'ed) for such queries, linux-kernel@vger.kernel.org (un-Cc'ed) is the wrong list for questions about KDB patches or Red Hat kernels or Centos kernels. Hugh On Sun, 17 Aug 2008, Satish Eerpini wrote: > i am patching kdb-v4.4-2.6.18-common-1 and kdb-v4.4-2.6.18-i386-1 > > and following are the rejects i got , ... and nowhere could i make > sense for the above mentioned errors , ... am i missing on something > over here ? > > include/linux/sysctl.h.rej from kdb-v4.4-2.6.18-common-1 ( i could fix > this, or so i think , ... by manually adding the macro definitions to > the header file , .... and i agree i am totally unaware of the > consequences ) > > *************** > *** 150,155 **** > KERN_IA64_UNALIGNED=72, /* int: ia64 unaligned userland trap enable */ > KERN_COMPAT_LOG=73, /* int: print compat layer messages */ > KERN_MAX_LOCK_DEPTH=74, > }; > > > --- 150,156 ---- > KERN_IA64_UNALIGNED=72, /* int: ia64 unaligned userland trap enable */ > KERN_COMPAT_LOG=73, /* int: print compat layer messages */ > KERN_MAX_LOCK_DEPTH=74, > + KERN_KDB=75, /* int: kdb on/off */ > }; > > > arch/i386/kernel/traps.c.rej from kdb-v4.4-2.6.18-i386-1 : > > *************** > *** 786,791 **** > printk(" on CPU%d, eip %08lx, registers:\n", > smp_processor_id(), regs->eip); > show_registers(regs); > printk(KERN_EMERG "console shuts up ...\n"); > console_silent(); > spin_unlock(&nmi_print_lock); > --- 797,805 ---- > printk(" on CPU%d, eip %08lx, registers:\n", > smp_processor_id(), regs->eip); > show_registers(regs); > + #ifdef CONFIG_KDB > + kdb(KDB_REASON_NMI, 0, regs); > + #endif /* CONFIG_KDB */ > printk(KERN_EMERG "console shuts up ...\n"); > console_silent(); > spin_unlock(&nmi_print_lock); > > arch/i386/kernel/vmlinux.lds.S.rej from kdb-v4.4-2.6.18-i386-1 : > > *************** > *** 134,139 **** > *(.con_initcall.init) > } > __con_initcall_end = .; > SECURITY_INIT > . = ALIGN(4); > __alt_instructions = .; > --- 134,144 ---- > *(.con_initcall.init) > } > __con_initcall_end = .; > + __kdb_initcall_start = .; > + .kdb_initcall.init : AT(ADDR(.kdb_initcall.init) - LOAD_OFFSET) { > + *(.kdb_initcall.init) > + } > + __kdb_initcall_end = .; > SECURITY_INIT > . = ALIGN(4); > __alt_instructions = .; > > > , .... i seem to be using the correct kdb patch but the rejects seem > to be the result of the fact that redhat guys have a lot of custom > patches which are added to get the redhat/CentOS kernel . Also because > i could patch kernel 2.6.18.4 without any problems what so ever . > > > > Thanks > Satish > > On Sun, Aug 17, 2008 at 12:12 PM, wrote: > > On Sun, 17 Aug 2008 11:30:41 +0530, Satish Eerpini said: > >> hi everyone , i was trying to patch kdb with CentOS 5.0 kernel > >> (2.6.18-8) > > > > You might want to make sure you're using a 2.6.18-vintage kdb patch, as > > trying to fit a 2.6.26 kdb onto a 2.6.18 kernel is unlikely to bring joy. > > > >> resolve) ,.... but apart from the rejects during the kernel > >> compilation i got the following error which does not seem to have > >> anything to do with the rejects ............ > > > > No, the rejects during the patch are almost certainly related to your > > compile errors... > > > >> the code(in kdb/modules/kdbm_pg.c) which is causing the second error > >> is something like this : > >> > >> iaddr += offsetof(struct inode, u); > >> > >> what i am not able to understand is that if 'u' is not a correct > >> member of the inode , .. then what did they( whoever wrote this piece > >> code) intend by 'u' ? , ..... > > > > Your kdb patch probably includes a patch to include/linux/fs.h that adds a > > member 'u' to a 'struct inode'. If this generated a reject, then the member 'u' > > won't be in the struct, and your compile dies... > > > >> and for the first error , ... i just checked out the code .... > >> according to the line no shown in the error .....the code is : > >> > >> kdb_page_flags(page, Checked); > >> > >> and i don't see any function PageChecked ....! so what can the error > >> actually mean ?? > > > > kdb_page_flags is probably a macro that does something like: > > > > #define kdb_page_flags(a,b) (..... Page##b) > > > > The 'implicit declaration' is most likely a missing #include someplace, > > which again hints at the rejects from a misapplied patch... --------------------------- Use http://oss.sgi.com/ecartis to modify your settings or to unsubscribe. From eerpini@gmail.com Sun Aug 17 12:23:35 2008 Received: with ECARTIS (v1.0.0; list kdb); Sun, 17 Aug 2008 12:23:39 -0700 (PDT) Received: from cuda.sgi.com (cuda1.sgi.com [192.48.168.28]) by oss.sgi.com (8.12.11.20060308/8.12.11/SuSE Linux 0.7) with ESMTP id m7HJNYR4017139 for ; Sun, 17 Aug 2008 12:23:35 -0700 X-ASG-Debug-ID: 1219001091-43fe03e20000-sLlkUa X-Barracuda-URL: http://cuda.sgi.com:80/cgi-bin/mark.cgi Received: from yx-out-1718.google.com (localhost [127.0.0.1]) by cuda.sgi.com (Spam Firewall) with ESMTP id BBCB9F5C9A0 for ; Sun, 17 Aug 2008 12:24:52 -0700 (PDT) Received: from yx-out-1718.google.com (yx-out-1718.google.com [74.125.44.155]) by cuda.sgi.com with ESMTP id Si0tWfuGj8DjLlW6 for ; Sun, 17 Aug 2008 12:24:52 -0700 (PDT) Received: by yx-out-1718.google.com with SMTP id 36so962394yxh.32 for ; Sun, 17 Aug 2008 12:24:51 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:in-reply-to:mime-version:content-type :content-transfer-encoding:content-disposition:references; bh=4G6rIR3bNqqgyk5E3O5I00CM6igXmtxhYM5szkThPxo=; b=ahqgZoLzwlhYxGyts3m8UJVJf8svwNf0mG/nRX9jIK0cChsMDitQkQcViWCYBXCb2i ZtG6Q///cYAuQZR4slIzhrC32epEWBFeEoyvyO2MOl1BWzzd8zLgRxCr4gAtpCJE7sI9 Lnd6HsBhaFldjQQuLrnF/+DLWs64mKEwK3iJ8= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:in-reply-to:mime-version :content-type:content-transfer-encoding:content-disposition :references; b=UKaQ9359M2KiCcr9ODIPMHKGD6ksxR+E3CQZHVpicYOkn1cFwR8KIFSgyBV5yVxADq GgYD03/lbaZjsTY7AhphjBIqLiKoibRvhNG0vrklaCdcjg2NZ6XTFa3SOuSN5KTVaXTN E0PZVmFYpxLcjT4V06OQIR3IUaGxXUR3m9ruo= Received: by 10.150.122.13 with SMTP id u13mr8216244ybc.63.1219001091460; Sun, 17 Aug 2008 12:24:51 -0700 (PDT) Received: by 10.151.107.7 with HTTP; Sun, 17 Aug 2008 12:24:51 -0700 (PDT) Message-ID: <93655eb70808171224w7e4d2ce1w7b29ac7238fb06ac@mail.gmail.com> Date: Mon, 18 Aug 2008 00:54:51 +0530 From: "Satish Eerpini" To: kdb@oss.sgi.com X-ASG-Orig-Subj: patching kdb to Centos kernel : error Subject: patching kdb to Centos kernel : error In-Reply-To: <93655eb70808171119m29fa0974tef44caa326352dd0@mail.gmail.com> MIME-Version: 1.0 Content-type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Content-Disposition: inline References: <93655eb70808171119m29fa0974tef44caa326352dd0@mail.gmail.com> X-Barracuda-Connect: yx-out-1718.google.com[74.125.44.155] X-Barracuda-Start-Time: 1219001094 X-Barracuda-Bayes: INNOCENT GLOBAL 0.0000 1.0000 -2.0210 X-Barracuda-Virus-Scanned: by cuda.sgi.com at sgi.com X-Barracuda-Spam-Score: -2.02 X-Barracuda-Spam-Status: No, SCORE=-2.02 using per-user scores of TAG_LEVEL=2.0 QUARANTINE_LEVEL=1000.0 KILL_LEVEL=2.1 tests= X-Barracuda-Spam-Report: Code version 3.2, rules version 3.2.1.2936 Rule breakdown below pts rule name description ---- ---------------------- -------------------------------------------------- X-archive-position: 1438 X-ecartis-version: Ecartis v1.0.0 Sender: kdb-bounce@oss.sgi.com Errors-to: kdb-bounce@oss.sgi.com X-original-sender: eerpini@gmail.com Precedence: bulk X-list: kdb hi everyone , i was trying to patch kdb with CentOS 5.0 kernel (2.6.18-8) , and had a few rejects ( which i am still trying to resolve) ,.... but apart from the rejects during the kernel compilation i got the following error which does not seem to have anything to do with the rejects ............ i have got an error in a kdb module, which has nothing to do with the rejected patches ( or so i guess ) : kdb/modules/kdbm_pg.c: In function 'kdbm_show_page': kdb/modules/kdbm_pg.c:349: error: implicit declaration of function 'PageChecked' kdb/modules/kdbm_pg.c: In function 'kdbm_inode': kdb/modules/kdbm_pg.c:507: error: 'struct inode' has no member named 'u' the code(in kdb/modules/kdbm_pg.c) which is causing the second error is something like this : iaddr += offsetof(struct inode, u); what i am not able to understand is that if 'u' is not a correct member of the inode , .. then what did they( whoever wrote this piece code) intend by 'u' ? , ..... .... and for the first error , ... i just checked out the code .... according to the line no shown in the error .....the code is : kdb_page_flags(page, Checked); and i don't see any function PageChecked ....! so what can the error actually mean ?? Thanks in advance Satish -- http://satish.playdrupal.com -- http://satish.playdrupal.com --------------------------- Use http://oss.sgi.com/ecartis to modify your settings or to unsubscribe. From jidong.xiao@gmail.com Mon Aug 18 01:20:37 2008 Received: with ECARTIS (v1.0.0; list kdb); Mon, 18 Aug 2008 01:20:44 -0700 (PDT) Received: from cuda.sgi.com (cuda1.sgi.com [192.48.168.28]) by oss.sgi.com (8.12.11.20060308/8.12.11/SuSE Linux 0.7) with ESMTP id m7I8KbBm014251 for ; Mon, 18 Aug 2008 01:20:37 -0700 X-ASG-Debug-ID: 1219047716-599803930000-sLlkUa X-Barracuda-URL: http://cuda.sgi.com:80/cgi-bin/mark.cgi Received: from fg-out-1718.google.com (localhost [127.0.0.1]) by cuda.sgi.com (Spam Firewall) with ESMTP id BBEB7F5EFB5 for ; Mon, 18 Aug 2008 01:21:56 -0700 (PDT) Received: from fg-out-1718.google.com (fg-out-1718.google.com [72.14.220.158]) by cuda.sgi.com with ESMTP id bD0o3hglXHtNkEhf for ; Mon, 18 Aug 2008 01:21:56 -0700 (PDT) Received: by fg-out-1718.google.com with SMTP id l26so1596199fgb.8 for ; Mon, 18 Aug 2008 01:21:56 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:cc:in-reply-to:mime-version:content-type :content-transfer-encoding:content-disposition:references; bh=q/jx4bBoCCCR0uaIh4z/9v70VmyhDZphnUTzIByRZVc=; b=NwSeY/mQtWJ1C8E0YVNRZhju7dKc2Xzetv2iPhr/G2z0u2iLC8WxYSEs477VzWnZVq 0xC1lSJ/DWpbdmLQwvVBqxVSOcevzp7A/0I2Lq+qiJlPyGksfL2ekrS5Y8k/mSZVrGdG Uufy5iKU/j72Bq2/jiqz7NGn5gD88NxEyJZCo= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version :content-type:content-transfer-encoding:content-disposition :references; b=AeO36W6xNbyS0x1ShcWPYWq0dWj6H6wU9X3yY2yb6dkMmg/E/8VCdVicWqJlN+r+nY Y2rAh/aCphZhYo7vctELak+4f/wtkw6cdciRE3i9mN/EulYFPh0yPNLkBSzU4PJsdibv G/GIQGbpdM8JvBDpA2lOb7viSIh4tdJmDvY9g= Received: by 10.86.26.11 with SMTP id 11mr4293988fgz.71.1219047715937; Mon, 18 Aug 2008 01:21:55 -0700 (PDT) Received: by 10.86.93.10 with HTTP; Mon, 18 Aug 2008 01:21:55 -0700 (PDT) Message-ID: <4104961b0808180121u54fb092dvfef84aed58a4b53f@mail.gmail.com> Date: Mon, 18 Aug 2008 16:21:55 +0800 From: "jidong xiao" To: "Satish Eerpini" X-ASG-Orig-Subj: Re: patching kdb to Centos kernel : error Subject: Re: patching kdb to Centos kernel : error Cc: kdb@oss.sgi.com In-Reply-To: <93655eb70808171224w7e4d2ce1w7b29ac7238fb06ac@mail.gmail.com> MIME-Version: 1.0 Content-type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Content-Disposition: inline References: <93655eb70808171119m29fa0974tef44caa326352dd0@mail.gmail.com> <93655eb70808171224w7e4d2ce1w7b29ac7238fb06ac@mail.gmail.com> X-Barracuda-Connect: fg-out-1718.google.com[72.14.220.158] X-Barracuda-Start-Time: 1219047717 X-Barracuda-Bayes: INNOCENT GLOBAL 0.0000 1.0000 -2.0208 X-Barracuda-Virus-Scanned: by cuda.sgi.com at sgi.com X-Barracuda-Spam-Score: -2.02 X-Barracuda-Spam-Status: No, SCORE=-2.02 using per-user scores of TAG_LEVEL=2.0 QUARANTINE_LEVEL=1000.0 KILL_LEVEL=2.1 tests= X-Barracuda-Spam-Report: Code version 3.2, rules version 3.2.1.2992 Rule breakdown below pts rule name description ---- ---------------------- -------------------------------------------------- X-archive-position: 1439 X-ecartis-version: Ecartis v1.0.0 Sender: kdb-bounce@oss.sgi.com Errors-to: kdb-bounce@oss.sgi.com X-original-sender: jidong.xiao@gmail.com Precedence: bulk X-list: kdb On Mon, Aug 18, 2008 at 3:24 AM, Satish Eerpini wrote: > hi everyone , i was trying to patch kdb with CentOS 5.0 kernel > (2.6.18-8) , and had a few rejects ( which i am still trying to > resolve) ,.... but apart from the rejects during the kernel > compilation i got the following error which does not seem to have > anything to do with the rejects ............ > i have got an error in a kdb module, which has nothing to do with the > rejected patches ( or so i guess ) : > > kdb/modules/kdbm_pg.c: In function 'kdbm_show_page': > kdb/modules/kdbm_pg.c:349: error: implicit declaration > of function 'PageChecked' > kdb/modules/kdbm_pg.c: In function 'kdbm_inode': > kdb/modules/kdbm_pg.c:507: error: 'struct inode' has no > member named 'u' > > the code(in kdb/modules/kdbm_pg.c) which is causing the second error > is something like this : > > iaddr += offsetof(struct inode, u); > > what i am not able to understand is that if 'u' is not a correct > member of the inode , .. then what did they( whoever wrote this piece > code) intend by 'u' ? , ..... > > .... > and for the first error , ... i just checked out the code .... > according to the line no shown in the error .....the code is : > > kdb_page_flags(page, Checked); > > and i don't see any function PageChecked ....! so what can the error > actually mean ?? > > Thanks in advance > Satish > > -- Well I think people usually don't use KDB modules, so you can simply disable KDB modules by setting CONFIG_KDB_MODULES=n. This can avoid the two errors you mentioned. Regarding your second error, you can replace "u" with "i_private". iaddr += offsetof(struct inode, i_private); As to the first error, you can refer to the definition of kdb_page_flags, which explains your question. #define kdb_page_flags(page, type) if (Page ## type(page)) kdb_printf(" " #type); Regards Jason --------------------------- Use http://oss.sgi.com/ecartis to modify your settings or to unsubscribe. From jlan@sgi.com Mon Aug 18 11:23:03 2008 Received: with ECARTIS (v1.0.0; list kdb); Mon, 18 Aug 2008 11:23:06 -0700 (PDT) Received: from kluge.engr.sgi.com (kluge.engr.sgi.com [192.102.96.102]) by oss.sgi.com (8.12.11.20060308/8.12.11/SuSE Linux 0.7) with ESMTP id m7IIN2pb028038 for ; Mon, 18 Aug 2008 11:23:03 -0700 Received: from [150.166.8.78] (aware.engr.sgi.com [150.166.8.78]) by kluge.engr.sgi.com (SGI-8.12.5/8.12.5) with ESMTP id m7IIOKCD1693543; Mon, 18 Aug 2008 11:24:21 -0700 (PDT) Message-ID: <48A9BE52.5060805@sgi.com> Date: Mon, 18 Aug 2008 11:24:18 -0700 From: Jay Lan User-Agent: Thunderbird 2.0.0.6 (X11/20070801) MIME-Version: 1.0 To: Satish Eerpini CC: kdb@oss.sgi.com Subject: Re: patching kdb to Centos kernel : error References: <93655eb70808171119m29fa0974tef44caa326352dd0@mail.gmail.com> <93655eb70808171224w7e4d2ce1w7b29ac7238fb06ac@mail.gmail.com> In-Reply-To: <93655eb70808171224w7e4d2ce1w7b29ac7238fb06ac@mail.gmail.com> Content-type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit X-archive-position: 1440 X-ecartis-version: Ecartis v1.0.0 Sender: kdb-bounce@oss.sgi.com Errors-to: kdb-bounce@oss.sgi.com X-original-sender: jlan@sgi.com Precedence: bulk X-list: kdb Satish Eerpini wrote: > hi everyone , i was trying to patch kdb with CentOS 5.0 kernel > (2.6.18-8) , and had a few rejects ( which i am still trying to > resolve) ,.... but apart from the rejects during the kernel > compilation i got the following error which does not seem to have > anything to do with the rejects ............ > i have got an error in a kdb module, which has nothing to do with the > rejected patches ( or so i guess ) : Hi Satish, I set up a new build area with upstreams 2.6.18-8 (not CentOS) with kdb-v4.4-2.6.18-common-1 and kdb-v4.4-2.6.18-i386-1. The patches were applied fine (with a few offset lines in two files). I used the linux/arch/i386/defconfig of the kernel source as base, turned on CONFIG_DEBUG_KERNEL, and took all default values in 'make oldconfig'. The kernel was built fine with CONFIG_KDB_MODULES set to either 'y' or 'm'. My guess is that your problem was CentOS specific? Regards, - jay > > kdb/modules/kdbm_pg.c: In function 'kdbm_show_page': > kdb/modules/kdbm_pg.c:349: error: implicit declaration > of function 'PageChecked' > kdb/modules/kdbm_pg.c: In function 'kdbm_inode': > kdb/modules/kdbm_pg.c:507: error: 'struct inode' has no > member named 'u' > > the code(in kdb/modules/kdbm_pg.c) which is causing the second error > is something like this : > > iaddr += offsetof(struct inode, u); > > what i am not able to understand is that if 'u' is not a correct > member of the inode , .. then what did they( whoever wrote this piece > code) intend by 'u' ? , ..... > > .... > and for the first error , ... i just checked out the code .... > according to the line no shown in the error .....the code is : > > kdb_page_flags(page, Checked); > > and i don't see any function PageChecked ....! so what can the error > actually mean ?? > > Thanks in advance > Satish > > -- > http://satish.playdrupal.com > > > --------------------------- Use http://oss.sgi.com/ecartis to modify your settings or to unsubscribe. From jidong.xiao@gmail.com Wed Aug 20 01:03:38 2008 Received: with ECARTIS (v1.0.0; list kdb); Wed, 20 Aug 2008 01:03:43 -0700 (PDT) Received: from cuda.sgi.com (cuda1.sgi.com [192.48.168.28]) by oss.sgi.com (8.12.11.20060308/8.12.11/SuSE Linux 0.7) with ESMTP id m7K83cFf005729 for ; Wed, 20 Aug 2008 01:03:38 -0700 X-ASG-Debug-ID: 1219219496-5e5b004d0000-sLlkUa X-Barracuda-URL: http://cuda.sgi.com:80/cgi-bin/mark.cgi Received: from fg-out-1718.google.com (localhost [127.0.0.1]) by cuda.sgi.com (Spam Firewall) with ESMTP id 4393BF7CFD3 for ; Wed, 20 Aug 2008 01:04:57 -0700 (PDT) Received: from fg-out-1718.google.com (fg-out-1718.google.com [72.14.220.157]) by cuda.sgi.com with ESMTP id x1HEfyfKQFgFUtXQ for ; Wed, 20 Aug 2008 01:04:57 -0700 (PDT) Received: by fg-out-1718.google.com with SMTP id l26so247537fgb.8 for ; Wed, 20 Aug 2008 01:04:56 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:cc:in-reply-to:mime-version:content-type :content-transfer-encoding:content-disposition:references; bh=lQtJKHgDtGxAINzYpUjRcJ8GtMXvQNiKnZmpDXpFFK8=; b=FP8+7z8vnE5CS6EJ6jqsjAtiCj0+N2hmrrZhnjQGg6M/yOpJgTnq8OhmMYOzf0TakH WQG+kbQAZYCfSrT12WEjqT2cK7h0rTeOG5re8vSltnwc7Rthcd5OOIsbS1HYrR3PNsvd v4aZCXuttS4IelQZMesXYuPk5QSeSLmT+4ozc= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version :content-type:content-transfer-encoding:content-disposition :references; b=La8Zb2Sags1pokYxV0QzCyoXK5WMRUCEtBxw9uGOgYgSsnmZKazX74LjqBaohkb6Fx VehVXNnwWPaPY5KOVVHafzocGGAl4jOYa3RdJfhaI6rts0cxNTbHCwBeTFeTQsgUj/AE MWOs1tF9KK9wkXhqepM8JCz53bXhaeQBdpikk= Received: by 10.86.65.11 with SMTP id n11mr6320332fga.64.1219219496313; Wed, 20 Aug 2008 01:04:56 -0700 (PDT) Received: by 10.86.93.10 with HTTP; Wed, 20 Aug 2008 01:04:56 -0700 (PDT) Message-ID: <4104961b0808200104g6cb85709w606da55d6a0738a4@mail.gmail.com> Date: Wed, 20 Aug 2008 16:04:56 +0800 From: "jidong xiao" To: "Jay Lan" X-ASG-Orig-Subj: Re: [ANNOUNCE] Support 'kdump' command from KDB in 2.6.27-rc2-*-2.bz2 patchset Subject: Re: [ANNOUNCE] Support 'kdump' command from KDB in 2.6.27-rc2-*-2.bz2 patchset Cc: KDB , "Zou, Nanhai" In-Reply-To: <48A5DDC5.6090404@sgi.com> MIME-Version: 1.0 Content-type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Content-Disposition: inline References: <48A5DDC5.6090404@sgi.com> X-Barracuda-Connect: fg-out-1718.google.com[72.14.220.157] X-Barracuda-Start-Time: 1219219499 X-Barracuda-Bayes: INNOCENT GLOBAL 0.0000 1.0000 -2.0210 X-Barracuda-Virus-Scanned: by cuda.sgi.com at sgi.com X-Barracuda-Spam-Score: -2.02 X-Barracuda-Spam-Status: No, SCORE=-2.02 using per-user scores of TAG_LEVEL=2.0 QUARANTINE_LEVEL=1000.0 KILL_LEVEL=2.1 tests= X-Barracuda-Spam-Report: Code version 3.2, rules version 3.2.1.3181 Rule breakdown below pts rule name description ---- ---------------------- -------------------------------------------------- X-archive-position: 1441 X-ecartis-version: Ecartis v1.0.0 Sender: kdb-bounce@oss.sgi.com Errors-to: kdb-bounce@oss.sgi.com X-original-sender: jidong.xiao@gmail.com Precedence: bulk X-list: kdb On Sat, Aug 16, 2008 at 3:49 AM, Jay Lan wrote: > Hi, > > The kdb 2.6.27-rc2-*-2.bz2 patchset contains implementation > of 'kdump' command. It was based on the original patch posted > by Dan Aloni last year, then modified to provide i386 support > by Jason Xiao. I added IA64 support. I also added hooks to > intercept and drop to KDB from oops. > > It looks quite different from your patch, Jason, especially > in kdb/kdbmain.c to a style i like better. Sorry about that. > > This implementation would catch die, panic, MCA, NMI conditions > and drop into KDB. After analyze the oops situation and data, > you can issue 'kdump' command and a kdump vmcore will be > created. > > I do not intercept 'echo c > /proc/sysrq-trigger' since i see > no need to create extra works if users already decide to create > a vmcore from user space. Besides, you can use KDB key sequence > to break into KDB and do a 'kdump' command to take a dump as well. > > Doing a 'go' after panic is undefined, and it also depends on > the value of CONFIG_KDB_CONTINUE_CATASTROPHIC. So, do 'kdump' > after panic if you want take a vmcore. > > I have tested on IA64 and X86_64 to see a kdump kernel booted > up and /proc/vmcore created. Due to bugs of makedumpfile and > crash against the latest kernels, i did not run crash to > check validity of the vmcore though. > > Please report any bugs to me. Thanks! > > Regards, > - jay > > Hi,Jay, arch/ia64/kdb/kdba_support.c, void kdba_kdump_prepare(struct pt_regs *fixed_regs) { int i; /* Set on KEXEC bit on all onlinr cpus */ for (i = 1; i < NR_CPUS; ++i) { if (!cpu_online(i)) continue; KDB_STATE_SET_CPU(KEXEC, i); } /* delaying for 5 seconds ... */ udelay(5*1000000); machine_crash_shutdown(fixed_regs); } I wonder why do we need this 5-seconds-delay. Thanks. Regards Jason --------------------------- Use http://oss.sgi.com/ecartis to modify your settings or to unsubscribe. From eerpini@gmail.com Wed Aug 20 11:12:39 2008 Received: with ECARTIS (v1.0.0; list kdb); Wed, 20 Aug 2008 11:12:43 -0700 (PDT) Received: from cuda.sgi.com (cuda2.sgi.com [192.48.168.29]) by oss.sgi.com (8.12.11.20060308/8.12.11/SuSE Linux 0.7) with ESMTP id m7KICcsO021151 for ; Wed, 20 Aug 2008 11:12:38 -0700 X-ASG-Debug-ID: 1219256038-507c00e90000-sLlkUa X-Barracuda-URL: http://cuda.sgi.com:80/cgi-bin/mark.cgi Received: from mail-gx0-f21.google.com (localhost [127.0.0.1]) by cuda.sgi.com (Spam Firewall) with ESMTP id 6F6513B6CFF for ; Wed, 20 Aug 2008 11:13:58 -0700 (PDT) Received: from mail-gx0-f21.google.com (mail-gx0-f21.google.com [209.85.217.21]) by cuda.sgi.com with ESMTP id odLn4QLd7B4lRwHr for ; Wed, 20 Aug 2008 11:13:58 -0700 (PDT) Received: by gxk14 with SMTP id 14so690893gxk.20 for ; Wed, 20 Aug 2008 11:13:58 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:cc:in-reply-to:mime-version:content-type :content-transfer-encoding:content-disposition:references; bh=gj8vHreD57LB8KSe/uRECEULrR/NCMhVLFQTUPXZt4o=; b=JWOJcIBQ6ooYHXXIONfRGMnx5uBaCh1ZwSJNHMC4Asy8hUeTcaUMi01cCT/K+2huqa fYc/UBx4n6eobNz0r2O1zqRsL6+zv6sCN8iEQUuNzk0Pdr80BRX5NxAKecBW9PiF6zY0 cc8Zkxc0RdOL02vliqKFJq+U2jl+2uZ7OCl9k= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version :content-type:content-transfer-encoding:content-disposition :references; b=LU+6vYg5eLHA9nr7hPneI0N6Bedz8atnzeiznG7OfHr6F14yXpHCRQwIQiDZ8eHkaQ KqfYEXBIh5zlcOgXAzgvVqDxOqNOl/zC6PaeBYB6LJlr+IYzppwQ4tNTRVXdd+gUhola DuiZq3LFRwl9NG3BMV0TC0AE1mh1ijErY3pzU= Received: by 10.151.100.17 with SMTP id c17mr517143ybm.2.1219256037166; Wed, 20 Aug 2008 11:13:57 -0700 (PDT) Received: by 10.151.107.7 with HTTP; Wed, 20 Aug 2008 11:13:56 -0700 (PDT) Message-ID: <93655eb70808201113r374cb775k576f064d6060809f@mail.gmail.com> Date: Wed, 20 Aug 2008 23:43:56 +0530 From: "Satish Eerpini" To: "jidong xiao" X-ASG-Orig-Subj: Re: patching kdb to Centos kernel : error Subject: Re: patching kdb to Centos kernel : error Cc: kdb@oss.sgi.com In-Reply-To: <4104961b0808180121u54fb092dvfef84aed58a4b53f@mail.gmail.com> MIME-Version: 1.0 Content-type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Content-Disposition: inline References: <93655eb70808171119m29fa0974tef44caa326352dd0@mail.gmail.com> <93655eb70808171224w7e4d2ce1w7b29ac7238fb06ac@mail.gmail.com> <4104961b0808180121u54fb092dvfef84aed58a4b53f@mail.gmail.com> X-Barracuda-Connect: mail-gx0-f21.google.com[209.85.217.21] X-Barracuda-Start-Time: 1219256039 X-Barracuda-Bayes: INNOCENT GLOBAL 0.0000 1.0000 -2.0210 X-Barracuda-Virus-Scanned: by cuda.sgi.com at sgi.com X-Barracuda-Spam-Score: -2.02 X-Barracuda-Spam-Status: No, SCORE=-2.02 using per-user scores of TAG_LEVEL=2.0 QUARANTINE_LEVEL=1000.0 KILL_LEVEL=2.1 tests= X-Barracuda-Spam-Report: Code version 3.2, rules version 3.2.1.3220 Rule breakdown below pts rule name description ---- ---------------------- -------------------------------------------------- X-archive-position: 1442 X-ecartis-version: Ecartis v1.0.0 Sender: kdb-bounce@oss.sgi.com Errors-to: kdb-bounce@oss.sgi.com X-original-sender: eerpini@gmail.com Precedence: bulk X-list: kdb On 8/18/08, jidong xiao wrote: > On Mon, Aug 18, 2008 at 3:24 AM, Satish Eerpini wrote: >> hi everyone , i was trying to patch kdb with CentOS 5.0 kernel >> (2.6.18-8) , and had a few rejects ( which i am still trying to >> resolve) ,.... but apart from the rejects during the kernel >> compilation i got the following error which does not seem to have >> anything to do with the rejects ............ >> i have got an error in a kdb module, which has nothing to do with the >> rejected patches ( or so i guess ) : >> >> kdb/modules/kdbm_pg.c: In function 'kdbm_show_page': >> kdb/modules/kdbm_pg.c:349: error: implicit declaration >> of function 'PageChecked' >> kdb/modules/kdbm_pg.c: In function 'kdbm_inode': >> kdb/modules/kdbm_pg.c:507: error: 'struct inode' has no >> member named 'u' >> >> the code(in kdb/modules/kdbm_pg.c) which is causing the second error >> is something like this : >> >> iaddr += offsetof(struct inode, u); >> >> what i am not able to understand is that if 'u' is not a correct >> member of the inode , .. then what did they( whoever wrote this piece >> code) intend by 'u' ? , ..... >> >> .... >> and for the first error , ... i just checked out the code .... >> according to the line no shown in the error .....the code is : >> >> kdb_page_flags(page, Checked); >> >> and i don't see any function PageChecked ....! so what can the error >> actually mean ?? >> >> Thanks in advance >> Satish >> >> -- > Well I think people usually don't use KDB modules, so you can simply > disable KDB modules by setting CONFIG_KDB_MODULES=n. This can avoid > the two errors you mentioned. > > Regarding your second error, you can replace "u" with "i_private". > > iaddr += offsetof(struct inode, i_private); > > As to the first error, you can refer to the definition of > kdb_page_flags, which explains your question. > > #define kdb_page_flags(page, type) if (Page ## type(page)) > kdb_printf(" " #type); > > > Regards > Jason > hi jason , i have fixed those errors , .... i changed the u to i_private in the second error and then completely commented out the following line from the kdbm_pg.c file : kdb_page_flags(page, Checked); // on line 349 this solved the first error about the implicit function declaration , ... after this the compilation went on fine , .... but at the stage where the vmlinux file is linked i have some gcc specific errors ( or so it seems from what i have got on google searches ) , ........ here is a short part of the errors : CHK include/linux/version.h CHK include/linux/utsrelease.h CHK include/linux/compile.h GEN .version CHK include/linux/compile.h UPD include/linux/compile.h CC init/version.o LD init/built-in.o LD .tmp_vmlinux1 kernel/built-in.o: In function `timespec_add_ns': /usr/src/redhat/BUILD/kernel-2.6.18/linux-2.6.18.i386/include/linux/time.h:175: undefined reference to `__umoddi3' kernel/built-in.o: In function `do_gettimeofday': /usr/src/redhat/BUILD/kernel-2.6.18/linux-2.6.18.i386/kernel/timer.c:865: undefined reference to `__udivdi3' /usr/src/redhat/BUILD/kernel-2.6.18/linux-2.6.18.i386/kernel/timer.c:866: undefined reference to `__umoddi3' kernel/built-in.o: In function `timespec_add_ns': /usr/src/redhat/BUILD/kernel-2.6.18/linux-2.6.18.i386/include/linux/time.h:170: undefined reference to `__udivdi3' /usr/src/redhat/BUILD/kernel-2.6.18/linux-2.6.18.i386/include/linux/time.h:175: undefined reference to `__umoddi3' ^Cmake: *** Deleting file `.tmp_vmlinux1' make: *** [.tmp_vmlinux1] Interrupt can u make anything out of it ? , ... i checked both time.h and timer.c , something appears to be fussy in struct timesoec , but i am not proficient enough to see what it is ? Thanks Satish -- http://satish.playdrupal.com --------------------------- Use http://oss.sgi.com/ecartis to modify your settings or to unsubscribe. From jlan@sgi.com Wed Aug 20 11:34:45 2008 Received: with ECARTIS (v1.0.0; list kdb); Wed, 20 Aug 2008 11:34:49 -0700 (PDT) Received: from kluge.engr.sgi.com (kluge.engr.sgi.com [192.102.96.102]) by oss.sgi.com (8.12.11.20060308/8.12.11/SuSE Linux 0.7) with ESMTP id m7KIYj8H022529 for ; Wed, 20 Aug 2008 11:34:45 -0700 Received: from [150.166.8.78] (aware.engr.sgi.com [150.166.8.78]) by kluge.engr.sgi.com (SGI-8.12.5/8.12.5) with ESMTP id m7KIa6CD1354434; Wed, 20 Aug 2008 11:36:06 -0700 (PDT) Message-ID: <48AC6415.8080703@sgi.com> Date: Wed, 20 Aug 2008 11:36:05 -0700 From: Jay Lan User-Agent: Thunderbird 2.0.0.6 (X11/20070801) MIME-Version: 1.0 To: jidong xiao CC: KDB , "Zou, Nanhai" Subject: Re: [ANNOUNCE] Support 'kdump' command from KDB in 2.6.27-rc2-*-2.bz2 patchset References: <48A5DDC5.6090404@sgi.com> <4104961b0808200104g6cb85709w606da55d6a0738a4@mail.gmail.com> In-Reply-To: <4104961b0808200104g6cb85709w606da55d6a0738a4@mail.gmail.com> Content-type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit X-archive-position: 1443 X-ecartis-version: Ecartis v1.0.0 Sender: kdb-bounce@oss.sgi.com Errors-to: kdb-bounce@oss.sgi.com X-original-sender: jlan@sgi.com Precedence: bulk X-list: kdb jidong xiao wrote: > On Sat, Aug 16, 2008 at 3:49 AM, Jay Lan wrote: >> Hi, >> >> The kdb 2.6.27-rc2-*-2.bz2 patchset contains implementation >> of 'kdump' command. It was based on the original patch posted >> by Dan Aloni last year, then modified to provide i386 support >> by Jason Xiao. I added IA64 support. I also added hooks to >> intercept and drop to KDB from oops. >> >> It looks quite different from your patch, Jason, especially >> in kdb/kdbmain.c to a style i like better. Sorry about that. >> >> This implementation would catch die, panic, MCA, NMI conditions >> and drop into KDB. After analyze the oops situation and data, >> you can issue 'kdump' command and a kdump vmcore will be >> created. >> >> I do not intercept 'echo c > /proc/sysrq-trigger' since i see >> no need to create extra works if users already decide to create >> a vmcore from user space. Besides, you can use KDB key sequence >> to break into KDB and do a 'kdump' command to take a dump as well. >> >> Doing a 'go' after panic is undefined, and it also depends on >> the value of CONFIG_KDB_CONTINUE_CATASTROPHIC. So, do 'kdump' >> after panic if you want take a vmcore. >> >> I have tested on IA64 and X86_64 to see a kdump kernel booted >> up and /proc/vmcore created. Due to bugs of makedumpfile and >> crash against the latest kernels, i did not run crash to >> check validity of the vmcore though. >> >> Please report any bugs to me. Thanks! >> >> Regards, >> - jay >> >> > Hi,Jay, > > arch/ia64/kdb/kdba_support.c, > > void > kdba_kdump_prepare(struct pt_regs *fixed_regs) > { > int i; > > /* Set on KEXEC bit on all onlinr cpus */ > for (i = 1; i < NR_CPUS; ++i) { > if (!cpu_online(i)) > continue; > > KDB_STATE_SET_CPU(KEXEC, i); > } > > /* delaying for 5 seconds ... */ > udelay(5*1000000); > machine_crash_shutdown(fixed_regs); > } > > I wonder why do we need this 5-seconds-delay. Thanks. I stole the code from ia64_init_handler() of arch/ia64/kernel/mca.c: /* * Wait for a bit. On some machines (e.g., HP's zx2000 and zx6000, INIT can be * generated via the BMC's command-line interface, but since the console is on the * same serial line, the user will need some time to switch out of the BMC before * the dump begins. */ mprintk("Delaying for 5 seconds...\n"); udelay(5*1000000); ia64_wait_for_slaves(cpu, "INIT"); Since i can not test on those machines mentioned above, i can not tell if the delay is really necessary. But it is IA64 specific, i guess. Have you tested the code on x86_32, Jason? I do not have an x86_32 mchine set up for kdump testing... Regards, - jay > > Regards > Jason --------------------------- Use http://oss.sgi.com/ecartis to modify your settings or to unsubscribe. From jidong.xiao@gmail.com Wed Aug 20 22:51:48 2008 Received: with ECARTIS (v1.0.0; list kdb); Wed, 20 Aug 2008 22:51:52 -0700 (PDT) Received: from cuda.sgi.com ([192.48.176.15]) by oss.sgi.com (8.12.11.20060308/8.12.11/SuSE Linux 0.7) with ESMTP id m7L5pmB7007012 for ; Wed, 20 Aug 2008 22:51:48 -0700 X-ASG-Debug-ID: 1219297987-543f02fb0000-sLlkUa X-Barracuda-URL: http://cuda.sgi.com:80/cgi-bin/mark.cgi Received: from fg-out-1718.google.com (localhost [127.0.0.1]) by cuda.sgi.com (Spam Firewall) with ESMTP id 1E5741A1D5E4 for ; Wed, 20 Aug 2008 22:53:07 -0700 (PDT) Received: from fg-out-1718.google.com (fg-out-1718.google.com [72.14.220.153]) by cuda.sgi.com with ESMTP id yeqlgBho5f82xmkX for ; Wed, 20 Aug 2008 22:53:07 -0700 (PDT) Received: by fg-out-1718.google.com with SMTP id l26so510899fgb.8 for ; Wed, 20 Aug 2008 22:53:07 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:cc:in-reply-to:mime-version:content-type :content-transfer-encoding:content-disposition:references; bh=e7EGxfBsXBPnH/eQMsdh0LexUSF5fya/JJu4QI4zue0=; b=nAUj2QtkcUIdw8LgLI8ANssCR6oOUtghCI+4G8amnvEfdGd510lgzK3EbtlXgfrEJf 9xD5fqpayZm6ulNcVssgQekYzULJ0BSRrj4kNSuQnA4oLtH3SRnFk3ujOEdeWs0lu/6T cyE32omiQPuGDAvh3gkJbiZ20nMSVBqwD4wJ0= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version :content-type:content-transfer-encoding:content-disposition :references; b=bHQ6R8zBnW61JrUD6nry1YJ71U/Pj6a9JUMum+AQhUMaYIo/tWyMJBtzdtKzZh7MRt vZJeFHaKhEOGpkm9iDqZi84zoBFXg0zfZMvfguy4rSv39ADo1j8bCAMSZSC5LC0UkKVT KjJKOmZpF3HB0NUKIfgKP5HGFc0MbZ5tg6jCk= Received: by 10.86.96.18 with SMTP id t18mr806657fgb.29.1219297987075; Wed, 20 Aug 2008 22:53:07 -0700 (PDT) Received: by 10.86.93.10 with HTTP; Wed, 20 Aug 2008 22:53:07 -0700 (PDT) Message-ID: <4104961b0808202253r616e5c61v34300f0b7f0c6f2d@mail.gmail.com> Date: Thu, 21 Aug 2008 13:53:07 +0800 From: "jidong xiao" To: "Jay Lan" X-ASG-Orig-Subj: Re: [ANNOUNCE] Support 'kdump' command from KDB in 2.6.27-rc2-*-2.bz2 patchset Subject: Re: [ANNOUNCE] Support 'kdump' command from KDB in 2.6.27-rc2-*-2.bz2 patchset Cc: KDB , "Zou, Nanhai" In-Reply-To: <48AC6415.8080703@sgi.com> MIME-Version: 1.0 Content-type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Content-Disposition: inline References: <48A5DDC5.6090404@sgi.com> <4104961b0808200104g6cb85709w606da55d6a0738a4@mail.gmail.com> <48AC6415.8080703@sgi.com> X-Barracuda-Connect: fg-out-1718.google.com[72.14.220.153] X-Barracuda-Start-Time: 1219297989 X-Barracuda-Bayes: INNOCENT GLOBAL 0.0000 1.0000 -2.0210 X-Barracuda-Virus-Scanned: by cuda.sgi.com at sgi.com X-Barracuda-Spam-Score: -2.02 X-Barracuda-Spam-Status: No, SCORE=-2.02 using per-user scores of TAG_LEVEL=2.0 QUARANTINE_LEVEL=1000.0 KILL_LEVEL=2.1 tests= X-Barracuda-Spam-Report: Code version 3.2, rules version 3.2.1.3268 Rule breakdown below pts rule name description ---- ---------------------- -------------------------------------------------- X-archive-position: 1444 X-ecartis-version: Ecartis v1.0.0 Sender: kdb-bounce@oss.sgi.com Errors-to: kdb-bounce@oss.sgi.com X-original-sender: jidong.xiao@gmail.com Precedence: bulk X-list: kdb On Thu, Aug 21, 2008 at 2:36 AM, Jay Lan wrote: > jidong xiao wrote: >> On Sat, Aug 16, 2008 at 3:49 AM, Jay Lan wrote: >>> Hi, >>> >>> The kdb 2.6.27-rc2-*-2.bz2 patchset contains implementation >>> of 'kdump' command. It was based on the original patch posted >>> by Dan Aloni last year, then modified to provide i386 support >>> by Jason Xiao. I added IA64 support. I also added hooks to >>> intercept and drop to KDB from oops. >>> >>> It looks quite different from your patch, Jason, especially >>> in kdb/kdbmain.c to a style i like better. Sorry about that. >>> >>> This implementation would catch die, panic, MCA, NMI conditions >>> and drop into KDB. After analyze the oops situation and data, >>> you can issue 'kdump' command and a kdump vmcore will be >>> created. >>> >>> I do not intercept 'echo c > /proc/sysrq-trigger' since i see >>> no need to create extra works if users already decide to create >>> a vmcore from user space. Besides, you can use KDB key sequence >>> to break into KDB and do a 'kdump' command to take a dump as well. >>> >>> Doing a 'go' after panic is undefined, and it also depends on >>> the value of CONFIG_KDB_CONTINUE_CATASTROPHIC. So, do 'kdump' >>> after panic if you want take a vmcore. >>> >>> I have tested on IA64 and X86_64 to see a kdump kernel booted >>> up and /proc/vmcore created. Due to bugs of makedumpfile and >>> crash against the latest kernels, i did not run crash to >>> check validity of the vmcore though. >>> >>> Please report any bugs to me. Thanks! >>> >>> Regards, >>> - jay >>> >>> >> Hi,Jay, >> >> arch/ia64/kdb/kdba_support.c, >> >> void >> kdba_kdump_prepare(struct pt_regs *fixed_regs) >> { >> int i; >> >> /* Set on KEXEC bit on all onlinr cpus */ >> for (i = 1; i < NR_CPUS; ++i) { >> if (!cpu_online(i)) >> continue; >> >> KDB_STATE_SET_CPU(KEXEC, i); >> } >> >> /* delaying for 5 seconds ... */ >> udelay(5*1000000); >> machine_crash_shutdown(fixed_regs); >> } >> >> I wonder why do we need this 5-seconds-delay. Thanks. > > I stole the code from ia64_init_handler() of arch/ia64/kernel/mca.c: > > /* > * Wait for a bit. On some machines (e.g., HP's zx2000 and > zx6000, INIT can be > * generated via the BMC's command-line interface, but since the > console is on the > * same serial line, the user will need some time to switch out > of the BMC before > * the dump begins. > */ > mprintk("Delaying for 5 seconds...\n"); > udelay(5*1000000); > ia64_wait_for_slaves(cpu, "INIT"); > > Since i can not test on those machines mentioned above, i can not tell > if the delay is really necessary. But it is IA64 specific, i guess. Okay, I see. Thanks. > > Have you tested the code on x86_32, Jason? I do not have an x86_32 > mchine set up for kdump testing... > I will test the code on x86_32 (and also ia64) soon. Will let you know the result. Regards Jason > Regards, > - jay > >> >> Regards >> Jason > > --------------------------- Use http://oss.sgi.com/ecartis to modify your settings or to unsubscribe. From eerpini@gmail.com Thu Aug 21 00:15:13 2008 Received: with ECARTIS (v1.0.0; list kdb); Thu, 21 Aug 2008 00:15:17 -0700 (PDT) Received: from cuda.sgi.com ([192.48.176.15]) by oss.sgi.com (8.12.11.20060308/8.12.11/SuSE Linux 0.7) with ESMTP id m7L7FCpZ015269 for ; Thu, 21 Aug 2008 00:15:12 -0700 X-ASG-Debug-ID: 1219302992-308d01310000-sLlkUa X-Barracuda-URL: http://cuda.sgi.com:80/cgi-bin/mark.cgi Received: from rv-out-0708.google.com (localhost [127.0.0.1]) by cuda.sgi.com (Spam Firewall) with ESMTP id DEB001A1CF9B for ; Thu, 21 Aug 2008 00:16:32 -0700 (PDT) Received: from rv-out-0708.google.com (rv-out-0708.google.com [209.85.198.251]) by cuda.sgi.com with ESMTP id LluNmQutM2uJsaB9 for ; Thu, 21 Aug 2008 00:16:32 -0700 (PDT) Received: by rv-out-0708.google.com with SMTP id f25so668971rvb.32 for ; Thu, 21 Aug 2008 00:16:31 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:cc:in-reply-to:mime-version:content-type :content-transfer-encoding:content-disposition:references; bh=jLG4DscsDVf8UlFCIrvVbcW8jU9OI3ZLPT5hpQL69EQ=; b=v2I9/i3ILzDEw+0xFZ9WeSVQNi8tSxVVsiZkywm2ADLf4xuKaRvmFoNg816RBi/7OJ 4j9zzMj2JnHdvqaLVVqOXYuU0Tpxxdyleqe8XXw8TaJVqHZOgbSkyDL7x4jXCvkIDJE+ 9iSf5UktoFJuhYeUJ5uKS3qxyUyo8PIV+1L6k= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version :content-type:content-transfer-encoding:content-disposition :references; b=tpeG4ldsYABxjFBR0hVo+MwReSwh1FBgasM/OxoD9ta7xGNHVu+cyqCetL+SCqR8ie fRHXqKHO+pThubKrWnUl3y74fpO8WL7EEf61Wfmx1nrbDwBnjIL4YHqAD0/m2U784A3/ mLtGL7S8XtvHh4CeKKhkateQk6oXub4RwdRG0= Received: by 10.114.171.1 with SMTP id t1mr1085563wae.120.1219302991869; Thu, 21 Aug 2008 00:16:31 -0700 (PDT) Received: by 10.114.125.17 with HTTP; Thu, 21 Aug 2008 00:16:31 -0700 (PDT) Message-ID: <93655eb70808210016n195a60bdl4717784a6cf1ef26@mail.gmail.com> Date: Thu, 21 Aug 2008 12:46:31 +0530 From: "Satish Eerpini" To: "naidu bollineni" X-ASG-Orig-Subj: Re: Fwd: patching kdb to Centos kernel : error Subject: Re: Fwd: patching kdb to Centos kernel : error Cc: kdb@oss.sgi.com In-Reply-To: <93655eb70808201802t488d8301u65db33e4a4b86e21@mail.gmail.com> MIME-Version: 1.0 Content-type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Content-Disposition: inline References: <93655eb70808201214n4c4b0211t747cb8237aaf0bc1@mail.gmail.com> <964949.34797.qm@web54106.mail.re2.yahoo.com> <93655eb70808201802t488d8301u65db33e4a4b86e21@mail.gmail.com> X-Barracuda-Connect: rv-out-0708.google.com[209.85.198.251] X-Barracuda-Start-Time: 1219302992 X-Barracuda-Bayes: INNOCENT GLOBAL 0.0000 1.0000 -2.0210 X-Barracuda-Virus-Scanned: by cuda.sgi.com at sgi.com X-Barracuda-Spam-Score: -2.02 X-Barracuda-Spam-Status: No, SCORE=-2.02 using per-user scores of TAG_LEVEL=2.0 QUARANTINE_LEVEL=1000.0 KILL_LEVEL=2.1 tests= X-Barracuda-Spam-Report: Code version 3.2, rules version 3.2.1.3272 Rule breakdown below pts rule name description ---- ---------------------- -------------------------------------------------- X-archive-position: 1445 X-ecartis-version: Ecartis v1.0.0 Sender: kdb-bounce@oss.sgi.com Errors-to: kdb-bounce@oss.sgi.com X-original-sender: eerpini@gmail.com Precedence: bulk X-list: kdb this problem with using gcc ( the exceptions) seem to be fixed by modifying the KBUILD_CFLAGS , ... i have not tried this yet ... but i found some important clues in the following topic on the ArchLinux forums : http://bbs.archlinux.org/viewtopic.php?id=45882 i will report back if this works ....... Thanks Satish On 8/21/08, Satish Eerpini wrote: > ya sure , ..... > > On Thu, Aug 21, 2008 at 2:06 AM, naidu bollineni wrote: > > OK, here is how software development(this is also a development) works: > > > > when we start a project, marketing will write a requirements document showing what the market wants (engineering or innovation doesn't matter if there is no market to buy the product after all - but innovation can show to and create the market also). This is called MRD (Marketing Requirements Doc). > > > > From that derived is called Product Requirement Document (PRD) which just tells what should be in the product (what is the core, and what features (call them bells and whistles) to be included) > > > > From PRD, Engineering derives its own requirements - like first architecture document (called high level design) showing high level blocks in the system, their interaction, what and how they perform etc. Performance is very important in this stage. For example, you cannot architect a 10Gbps(IEEE 802.AE) ethernet supported motherboard by selecting 33MHz PCI Bus to seat that ethernet card because 33MHz PCI Bus (bus is shared between contending agents not dedicated) has a theoretical transfer of 100MB/s at 32Bit width. > > > > From architecture, you would put a design document putting algorithms, flow of control, detailed interaction, what messages pass how and all those. > > > > Now comes the coding (or actual development). While the development is going on, there is a testing (or QA) team which would take your architecture and design docs, and translate into tests. they will develop their own tests by interacting with development. They need to know "testing strategy" from development. That means how do you want to test the product. > > > > I will write some more later... busy now. > > > > > > > > --- On Wed, 8/20/08, Satish Eerpini wrote: > > > >> From: Satish Eerpini > >> Subject: Re: Fwd: patching kdb to Centos kernel : error > >> To: "naidu bollineni" > >> Date: Wednesday, August 20, 2008, 12:14 PM > >> i did not quite understand "testing strategy" , > >> ... once i compile it > >> i should be able to run the kernel on my lappy right , and > >> should be > >> able to initiate kdb right ?? > >> > >> On Thu, Aug 21, 2008 at 12:35 AM, naidu bollineni > >> wrote: > >> > I wonder if kdb_page_flags may cause trouble later. > >> > > >> > I didn't mean KDB CONFIG options would cause > >> integer computation issue. There may be some other > >> (unrelated) option that is affecting. > >> > > >> > BTW, what is the testing strategy? I am not sure if > >> KDB over USB is now working. If not, the only other is using > >> serial(9-pin) port. > >> > > >> > > >> > --- On Wed, 8/20/08, Satish Eerpini > >> wrote: > >> > > >> >> From: Satish Eerpini > >> >> Subject: Re: Fwd: patching kdb to Centos kernel : > >> error > >> >> To: "naidu bollineni" > >> > >> >> Date: Wednesday, August 20, 2008, 11:57 AM > >> >> CONFIG_KDB=y > >> >> CONFIG_KDB_MODULES=y > >> >> # CONFIG_KDB_OFF is not set > >> >> CONFIG_KDB_CONTINUE_CATASTROPHIC=0 > >> >> CONFIG_KDB_USB=y > >> >> > >> >> > >> >> those are all the kdb config options i set , > >> ...... so are > >> >> we looking > >> >> at some other config option which could affect > >> this . ?? > >> >> > >> >> I am not sure why the guy opted for the absence of > >> modules > >> >> , .... even > >> >> i was thinking on this , ... because anyone would > >> prefer to > >> >> add > >> >> functionality through pluggable modules , if it is > >> >> supported as in the > >> >> case ,..... but i don have the knowledge to judge > >> their use > >> >> so i > >> >> actually did not comment on that part !! > >> >> > >> >> and also about commenting the function > >> kdb_page_flags(page, > >> >> Checked); > >> >> i am not sure what the implications for this are , > >> ... i > >> >> just did this > >> >> to remove the error ! > >> >> > >> >> > >> >> > >> >> On 8/21/08, naidu bollineni > >> > >> >> wrote: > >> >> > those undefined symbols are 64-bit integer > >> handling > >> >> calls. not sure if > >> >> > timespec needed it. so, is there another > >> CONFIG option > >> >> that missed out that > >> >> > caused this undefined symbols? may be. > >> >> > > >> >> > BTW, we do need modules support in KDB. why > >> would this > >> >> guy say we dont use > >> >> > it? I did always with modules I had to deal > >> with. > >> >> > > >> >> > > >> >> > > >> >> > --- On Wed, 8/20/08, Satish Eerpini > >> >> wrote: > >> >> > > >> >> >> From: Satish Eerpini > >> > >> >> >> Subject: Fwd: patching kdb to Centos > >> kernel : > >> >> error > >> >> >> To: bgnaidu@yahoo.com > >> >> >> Date: Wednesday, August 20, 2008, 11:14 > >> AM > >> >> >> ---------- Forwarded message ---------- > >> >> >> From: Satish Eerpini > >> > >> >> >> Date: Wed, 20 Aug 2008 23:43:56 +0530 > >> >> >> Subject: Re: patching kdb to Centos > >> kernel : error > >> >> >> To: jidong xiao > >> > >> >> >> Cc: kdb@oss.sgi.com > >> >> >> > >> >> >> On 8/18/08, jidong xiao > >> >> > >> >> >> wrote: > >> >> >> > On Mon, Aug 18, 2008 at 3:24 AM, > >> Satish > >> >> Eerpini > >> >> >> wrote: > >> >> >> >> hi everyone , i was trying to > >> patch kdb > >> >> with > >> >> >> CentOS 5.0 kernel > >> >> >> >> (2.6.18-8) , and had a few > >> rejects ( > >> >> which i am > >> >> >> still trying to > >> >> >> >> resolve) ,.... but apart from > >> the rejects > >> >> during > >> >> >> the kernel > >> >> >> >> compilation i got the following > >> error > >> >> which does > >> >> >> not seem to have > >> >> >> >> anything to do with the rejects > >> >> ............ > >> >> >> >> i have got an error in a kdb > >> module, > >> >> which has > >> >> >> nothing to do with the > >> >> >> >> rejected patches ( or so i guess > >> ) : > >> >> >> >> > >> >> >> >> > >> kdb/modules/kdbm_pg.c: In > >> >> function > >> >> >> 'kdbm_show_page': > >> >> >> >> > >> kdb/modules/kdbm_pg.c:349: > >> >> error: > >> >> >> implicit declaration > >> >> >> >> of function > >> 'PageChecked' > >> >> >> >> > >> kdb/modules/kdbm_pg.c: In > >> >> function > >> >> >> 'kdbm_inode': > >> >> >> >> > >> kdb/modules/kdbm_pg.c:507: > >> >> error: > >> >> >> 'struct inode' has no > >> >> >> >> member named 'u' > >> >> >> >> > >> >> >> >> the code(in > >> kdb/modules/kdbm_pg.c) which > >> >> is > >> >> >> causing the second error > >> >> >> >> is something like this : > >> >> >> >> > >> >> >> >> iaddr += > >> offsetof(struct inode, > >> >> u); > >> >> >> >> > >> >> >> >> what i am not able to understand > >> is that > >> >> if > >> >> >> 'u' is not a correct > >> >> >> >> member of the inode , .. then > >> what did > >> >> they( > >> >> >> whoever wrote this piece > >> >> >> >> code) intend by 'u' ? , > >> ..... > >> >> >> >> > >> >> >> >> .... > >> >> >> >> and for the first error , ... i > >> just > >> >> checked out > >> >> >> the code .... > >> >> >> >> according to the line no shown > >> in the > >> >> error > >> >> >> .....the code is : > >> >> >> >> > >> >> >> >> kdb_page_flags(page, > >> Checked); > >> >> >> >> > >> >> >> >> and i don't see any function > >> >> PageChecked ....! > >> >> >> so what can the error > >> >> >> >> actually mean ?? > >> >> >> >> > >> >> >> >> Thanks in advance > >> >> >> >> Satish > >> >> >> >> > >> >> >> >> -- > >> >> >> > Well I think people usually > >> don't use KDB > >> >> modules, > >> >> >> so you can simply > >> >> >> > disable KDB modules by setting > >> >> CONFIG_KDB_MODULES=n. > >> >> >> This can avoid > >> >> >> > the two errors you mentioned. > >> >> >> > > >> >> >> > Regarding your second error, you can > >> replace > >> >> >> "u" with "i_private". > >> >> >> > > >> >> >> > iaddr += offsetof(struct inode, > >> i_private); > >> >> >> > > >> >> >> > As to the first error, you can refer > >> to the > >> >> definition > >> >> >> of > >> >> >> > kdb_page_flags, which explains your > >> question. > >> >> >> > > >> >> >> > #define kdb_page_flags(page, type) > >> if (Page > >> >> ## > >> >> >> type(page)) > >> >> >> > kdb_printf(" " #type); > >> >> >> > > >> >> >> > > >> >> >> > Regards > >> >> >> > Jason > >> >> >> > > >> >> >> > >> >> >> hi jason , > >> >> >> > >> >> >> i have fixed those errors , .... i > >> changed the u > >> >> to > >> >> >> i_private in the > >> >> >> second error and then completely > >> commented out the > >> >> >> following line from > >> >> >> the kdbm_pg.c file : > >> >> >> kdb_page_flags(page, Checked); // on > >> line 349 > >> >> >> this solved the first error about the > >> implicit > >> >> function > >> >> >> declaration , > >> >> >> ... after this the compilation went on > >> fine , .... > >> >> but at > >> >> >> the stage > >> >> >> where the vmlinux file is linked i have > >> some gcc > >> >> specific > >> >> >> errors ( or > >> >> >> so it seems from what i have got on > >> google > >> >> searches ) , > >> >> >> ........ here > >> >> >> is a short part of the errors : > >> >> >> > >> >> >> CHK include/linux/version.h > >> >> >> CHK include/linux/utsrelease.h > >> >> >> CHK include/linux/compile.h > >> >> >> GEN .version > >> >> >> CHK include/linux/compile.h > >> >> >> UPD include/linux/compile.h > >> >> >> CC init/version.o > >> >> >> LD init/built-in.o > >> >> >> LD .tmp_vmlinux1 > >> >> >> kernel/built-in.o: In function > >> >> `timespec_add_ns': > >> >> >> > >> >> > >> /usr/src/redhat/BUILD/kernel-2.6.18/linux-2.6.18.i386/include/linux/time.h:175: > >> >> >> undefined reference to `__umoddi3' > >> >> >> kernel/built-in.o: In function > >> >> `do_gettimeofday': > >> >> >> > >> >> > >> /usr/src/redhat/BUILD/kernel-2.6.18/linux-2.6.18.i386/kernel/timer.c:865: > >> >> >> undefined reference to `__udivdi3' > >> >> >> > >> >> > >> /usr/src/redhat/BUILD/kernel-2.6.18/linux-2.6.18.i386/kernel/timer.c:866: > >> >> >> undefined reference to `__umoddi3' > >> >> >> kernel/built-in.o: In function > >> >> `timespec_add_ns': > >> >> >> > >> >> > >> /usr/src/redhat/BUILD/kernel-2.6.18/linux-2.6.18.i386/include/linux/time.h:170: > >> >> >> undefined reference to `__udivdi3' > >> >> >> > >> >> > >> /usr/src/redhat/BUILD/kernel-2.6.18/linux-2.6.18.i386/include/linux/time.h:175: > >> >> >> undefined reference to `__umoddi3' > >> >> >> ^Cmake: *** Deleting file > >> `.tmp_vmlinux1' > >> >> >> make: *** [.tmp_vmlinux1] Interrupt > >> >> >> > >> >> >> can u make anything out of it ? , ... i > >> checked > >> >> both time.h > >> >> >> and > >> >> >> timer.c , something appears to be fussy > >> in struct > >> >> timesoec > >> >> >> , but i am > >> >> >> not proficient enough to see what it is ? > >> >> >> > >> >> >> Thanks > >> >> >> Satish > >> >> >> > >> >> >> -- > >> >> >> http://satish.playdrupal.com > >> >> >> > >> >> >> > >> >> >> > >> >> >> -- > >> >> >> http://satish.playdrupal.com > >> >> > > >> >> > >> >> > >> >> -- > >> >> http://satish.playdrupal.com > >> > > >> > >> > >> > >> -- > >> http://satish.playdrupal.com > > > > > > -- > http://satish.playdrupal.com > -- http://satish.playdrupal.com --------------------------- Use http://oss.sgi.com/ecartis to modify your settings or to unsubscribe. From jlan@sgi.com Thu Aug 21 10:37:43 2008 Received: with ECARTIS (v1.0.0; list kdb); Thu, 21 Aug 2008 10:37:47 -0700 (PDT) Received: from kluge.engr.sgi.com (kluge.engr.sgi.com [192.102.96.102]) by oss.sgi.com (8.12.11.20060308/8.12.11/SuSE Linux 0.7) with ESMTP id m7LHbhlr003135 for ; Thu, 21 Aug 2008 10:37:43 -0700 Received: from [150.166.8.78] (aware.engr.sgi.com [150.166.8.78]) by kluge.engr.sgi.com (SGI-8.12.5/8.12.5) with ESMTP id m7LHd6CD1772252; Thu, 21 Aug 2008 10:39:06 -0700 (PDT) Message-ID: <48ADA838.3080308@sgi.com> Date: Thu, 21 Aug 2008 10:39:04 -0700 From: Jay Lan User-Agent: Thunderbird 2.0.0.6 (X11/20070801) MIME-Version: 1.0 To: jidong xiao CC: KDB , "Zou, Nanhai" Subject: Re: [ANNOUNCE] Support 'kdump' command from KDB in 2.6.27-rc2-*-2.bz2 patchset References: <48A5DDC5.6090404@sgi.com> <4104961b0808200104g6cb85709w606da55d6a0738a4@mail.gmail.com> <48AC6415.8080703@sgi.com> <4104961b0808202253r616e5c61v34300f0b7f0c6f2d@mail.gmail.com> In-Reply-To: <4104961b0808202253r616e5c61v34300f0b7f0c6f2d@mail.gmail.com> Content-type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit X-archive-position: 1446 X-ecartis-version: Ecartis v1.0.0 Sender: kdb-bounce@oss.sgi.com Errors-to: kdb-bounce@oss.sgi.com X-original-sender: jlan@sgi.com Precedence: bulk X-list: kdb jidong xiao wrote: > On Thu, Aug 21, 2008 at 2:36 AM, Jay Lan wrote: >> jidong xiao wrote: >>> On Sat, Aug 16, 2008 at 3:49 AM, Jay Lan wrote: >>>> Hi, >>>> >>>> The kdb 2.6.27-rc2-*-2.bz2 patchset contains implementation >>>> of 'kdump' command. It was based on the original patch posted >>>> by Dan Aloni last year, then modified to provide i386 support >>>> by Jason Xiao. I added IA64 support. I also added hooks to >>>> intercept and drop to KDB from oops. >>>> >>>> It looks quite different from your patch, Jason, especially >>>> in kdb/kdbmain.c to a style i like better. Sorry about that. >>>> >>>> This implementation would catch die, panic, MCA, NMI conditions >>>> and drop into KDB. After analyze the oops situation and data, >>>> you can issue 'kdump' command and a kdump vmcore will be >>>> created. >>>> >>>> I do not intercept 'echo c > /proc/sysrq-trigger' since i see >>>> no need to create extra works if users already decide to create >>>> a vmcore from user space. Besides, you can use KDB key sequence >>>> to break into KDB and do a 'kdump' command to take a dump as well. >>>> >>>> Doing a 'go' after panic is undefined, and it also depends on >>>> the value of CONFIG_KDB_CONTINUE_CATASTROPHIC. So, do 'kdump' >>>> after panic if you want take a vmcore. >>>> >>>> I have tested on IA64 and X86_64 to see a kdump kernel booted >>>> up and /proc/vmcore created. Due to bugs of makedumpfile and >>>> crash against the latest kernels, i did not run crash to >>>> check validity of the vmcore though. >>>> >>>> Please report any bugs to me. Thanks! >>>> >>>> Regards, >>>> - jay >>>> >>>> >>> Hi,Jay, >>> >>> arch/ia64/kdb/kdba_support.c, >>> >>> void >>> kdba_kdump_prepare(struct pt_regs *fixed_regs) >>> { >>> int i; >>> >>> /* Set on KEXEC bit on all onlinr cpus */ >>> for (i = 1; i < NR_CPUS; ++i) { >>> if (!cpu_online(i)) >>> continue; >>> >>> KDB_STATE_SET_CPU(KEXEC, i); >>> } >>> >>> /* delaying for 5 seconds ... */ >>> udelay(5*1000000); >>> machine_crash_shutdown(fixed_regs); >>> } >>> >>> I wonder why do we need this 5-seconds-delay. Thanks. >> I stole the code from ia64_init_handler() of arch/ia64/kernel/mca.c: >> >> /* >> * Wait for a bit. On some machines (e.g., HP's zx2000 and >> zx6000, INIT can be >> * generated via the BMC's command-line interface, but since the >> console is on the >> * same serial line, the user will need some time to switch out >> of the BMC before >> * the dump begins. >> */ >> mprintk("Delaying for 5 seconds...\n"); >> udelay(5*1000000); >> ia64_wait_for_slaves(cpu, "INIT"); >> >> Since i can not test on those machines mentioned above, i can not tell >> if the delay is really necessary. But it is IA64 specific, i guess. > Okay, I see. Thanks. > >> Have you tested the code on x86_32, Jason? I do not have an x86_32 >> mchine set up for kdump testing... >> > I will test the code on x86_32 (and also ia64) soon. Will let you know > the result. I just found out the same KDB patchset that applied to 2.6.27-rc2 worked fine, but it would cause the kdump kernel panic on __free_pages_bootmem on 2.6.27-rc3. It was on ia64. Now in addition to running the kdb sanity test every time i rebase the KDB patchset to a newer release, it seems that i need to test kdump as well. :( Regards, - jay > > Regards > Jason > >> Regards, >> - jay >> >>> Regards >>> Jason >> > --------------------------- > Use http://oss.sgi.com/ecartis to modify your settings or to unsubscribe. --------------------------- Use http://oss.sgi.com/ecartis to modify your settings or to unsubscribe. From jlan@sgi.com Fri Aug 22 08:46:08 2008 Received: with ECARTIS (v1.0.0; list kdb); Fri, 22 Aug 2008 08:46:12 -0700 (PDT) Received: from cthulhu.engr.sgi.com (cthulhu.engr.sgi.com [192.26.80.2]) by oss.sgi.com (8.12.11.20060308/8.12.11/SuSE Linux 0.7) with ESMTP id m7MFk72l009574 for ; Fri, 22 Aug 2008 08:46:08 -0700 Received: from [127.0.0.1] (sshgate.corp.sgi.com [198.149.36.12]) by cthulhu.engr.sgi.com (8.12.10/8.12.10/SuSE Linux 0.7) with ESMTP id m7MFlQWM022943; Fri, 22 Aug 2008 08:47:27 -0700 Message-ID: <48AEDF65.5080106@sgi.com> Date: Fri, 22 Aug 2008 08:46:45 -0700 From: Jay Lan User-Agent: Thunderbird 1.5 (X11/20060317) MIME-Version: 1.0 To: jidong xiao CC: KDB , "Zou, Nanhai" Subject: Re: [ANNOUNCE] Support 'kdump' command from KDB in 2.6.27-rc2-*-2.bz2 patchset References: <48A5DDC5.6090404@sgi.com> <4104961b0808200104g6cb85709w606da55d6a0738a4@mail.gmail.com> <48AC6415.8080703@sgi.com> <4104961b0808202253r616e5c61v34300f0b7f0c6f2d@mail.gmail.com> <48ADA838.3080308@sgi.com> In-Reply-To: <48ADA838.3080308@sgi.com> X-Enigmail-Version: 0.94.0.0 Content-type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit X-archive-position: 1447 X-ecartis-version: Ecartis v1.0.0 Sender: kdb-bounce@oss.sgi.com Errors-to: kdb-bounce@oss.sgi.com X-original-sender: jlan@sgi.com Precedence: bulk X-list: kdb Hi guys, linux-2.6.27-rc3 kernel causes the kdump kernel to panic at __free_pages_bootmem(). It has been fixed in 2.6.27-rc4. So, avoid 2.6.27-rc3 if you want to use the 'kdump' feature of KDB. (Or, kdump without KDB ;)) Regards, - jay Jay Lan wrote: > jidong xiao wrote: >> On Thu, Aug 21, 2008 at 2:36 AM, Jay Lan wrote: >>> jidong xiao wrote: >>>> On Sat, Aug 16, 2008 at 3:49 AM, Jay Lan wrote: >>>>> Hi, >>>>> >>>>> The kdb 2.6.27-rc2-*-2.bz2 patchset contains implementation >>>>> of 'kdump' command. It was based on the original patch posted >>>>> by Dan Aloni last year, then modified to provide i386 support >>>>> by Jason Xiao. I added IA64 support. I also added hooks to >>>>> intercept and drop to KDB from oops. >>>>> >>>>> It looks quite different from your patch, Jason, especially >>>>> in kdb/kdbmain.c to a style i like better. Sorry about that. >>>>> >>>>> This implementation would catch die, panic, MCA, NMI conditions >>>>> and drop into KDB. After analyze the oops situation and data, >>>>> you can issue 'kdump' command and a kdump vmcore will be >>>>> created. >>>>> >>>>> I do not intercept 'echo c > /proc/sysrq-trigger' since i see >>>>> no need to create extra works if users already decide to create >>>>> a vmcore from user space. Besides, you can use KDB key sequence >>>>> to break into KDB and do a 'kdump' command to take a dump as well. >>>>> >>>>> Doing a 'go' after panic is undefined, and it also depends on >>>>> the value of CONFIG_KDB_CONTINUE_CATASTROPHIC. So, do 'kdump' >>>>> after panic if you want take a vmcore. >>>>> >>>>> I have tested on IA64 and X86_64 to see a kdump kernel booted >>>>> up and /proc/vmcore created. Due to bugs of makedumpfile and >>>>> crash against the latest kernels, i did not run crash to >>>>> check validity of the vmcore though. >>>>> >>>>> Please report any bugs to me. Thanks! >>>>> >>>>> Regards, >>>>> - jay >>>>> >>>>> >>>> Hi,Jay, >>>> >>>> arch/ia64/kdb/kdba_support.c, >>>> >>>> void >>>> kdba_kdump_prepare(struct pt_regs *fixed_regs) >>>> { >>>> int i; >>>> >>>> /* Set on KEXEC bit on all onlinr cpus */ >>>> for (i = 1; i < NR_CPUS; ++i) { >>>> if (!cpu_online(i)) >>>> continue; >>>> >>>> KDB_STATE_SET_CPU(KEXEC, i); >>>> } >>>> >>>> /* delaying for 5 seconds ... */ >>>> udelay(5*1000000); >>>> machine_crash_shutdown(fixed_regs); >>>> } >>>> >>>> I wonder why do we need this 5-seconds-delay. Thanks. >>> I stole the code from ia64_init_handler() of arch/ia64/kernel/mca.c: >>> >>> /* >>> * Wait for a bit. On some machines (e.g., HP's zx2000 and >>> zx6000, INIT can be >>> * generated via the BMC's command-line interface, but since the >>> console is on the >>> * same serial line, the user will need some time to switch out >>> of the BMC before >>> * the dump begins. >>> */ >>> mprintk("Delaying for 5 seconds...\n"); >>> udelay(5*1000000); >>> ia64_wait_for_slaves(cpu, "INIT"); >>> >>> Since i can not test on those machines mentioned above, i can not tell >>> if the delay is really necessary. But it is IA64 specific, i guess. >> Okay, I see. Thanks. >> >>> Have you tested the code on x86_32, Jason? I do not have an x86_32 >>> mchine set up for kdump testing... >>> >> I will test the code on x86_32 (and also ia64) soon. Will let you know >> the result. > > I just found out the same KDB patchset that applied to 2.6.27-rc2 worked > fine, but it would cause the kdump kernel panic on __free_pages_bootmem > on 2.6.27-rc3. It was on ia64. > > Now in addition to running the kdb sanity test every time i rebase > the KDB patchset to a newer release, it seems that i need to test > kdump as well. :( > > Regards, > - jay > --------------------------- Use http://oss.sgi.com/ecartis to modify your settings or to unsubscribe. From eerpini@gmail.com Sun Aug 24 19:06:37 2008 Received: with ECARTIS (v1.0.0; list kdb); Sun, 24 Aug 2008 19:06:41 -0700 (PDT) Received: from cuda.sgi.com ([192.48.176.15]) by oss.sgi.com (8.12.11.20060308/8.12.11/SuSE Linux 0.7) with ESMTP id m7P26bcj018325 for ; Sun, 24 Aug 2008 19:06:37 -0700 X-ASG-Debug-ID: 1219630078-040f03ac0000-sLlkUa X-Barracuda-URL: http://cuda.sgi.com:80/cgi-bin/mark.cgi Received: from yw-out-1718.google.com (localhost [127.0.0.1]) by cuda.sgi.com (Spam Firewall) with ESMTP id 6134D1A3F1C7 for ; Sun, 24 Aug 2008 19:07:58 -0700 (PDT) Received: from yw-out-1718.google.com (yw-out-1718.google.com [74.125.46.152]) by cuda.sgi.com with ESMTP id BPXKcdQQqrBGXZkT for ; Sun, 24 Aug 2008 19:07:58 -0700 (PDT) Received: by yw-out-1718.google.com with SMTP id 5so89500ywm.32 for ; Sun, 24 Aug 2008 19:07:58 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:cc:mime-version:content-type:content-transfer-encoding :content-disposition; bh=Vr3kKeaOj+xAV1Vs98rAVHibYuuY+elQsijWlHxEXBw=; b=DB49Ks0SrEAgbzREVJlc6LnU4S/S84La6VR7mqzVfzWgxln7+TAYNXTRE+c3WAVuxs 5DvvQ5wHljZbxbwF43WdNmBF04p4W3PYBx1NP9Z/pvwS4SE9WB53nptOvS90lON0+1CA WlSd1FxE34qLAZAvvuS8umiTFUrZ7LFeqYzqw= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:mime-version:content-type :content-transfer-encoding:content-disposition; b=inhEvetWrcRHzUUHJQbK29Pd93GWTWngJZmm8xAIT8CLdqXt+uKxaZJdF6HdDdRBSR nH6UlzKjzYIWIKRundaEOTmUkePBCYtsjQFX91UOSrk1UNBRibgzOmMUbtKgCvuK8V3Y 9xcdbh4Xq3NAEujrUnSn59voag8XeQd/lRoVU= Received: by 10.150.182.17 with SMTP id e17mr6182297ybf.139.1219630078431; Sun, 24 Aug 2008 19:07:58 -0700 (PDT) Received: by 10.151.147.7 with HTTP; Sun, 24 Aug 2008 19:07:58 -0700 (PDT) Message-ID: <93655eb70808241907w7bf40ef1qd08166cccb64d966@mail.gmail.com> Date: Mon, 25 Aug 2008 07:37:58 +0530 From: "Satish Eerpini" To: kdb@oss.sgi.com X-ASG-Orig-Subj: patching kdb to the Centos Kernel : more errors Subject: patching kdb to the Centos Kernel : more errors Cc: bgnaidu@yahoo.com MIME-Version: 1.0 Content-type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Content-Disposition: inline X-Barracuda-Connect: yw-out-1718.google.com[74.125.46.152] X-Barracuda-Start-Time: 1219630079 X-Barracuda-Bayes: INNOCENT GLOBAL 0.0022 1.0000 -2.0066 X-Barracuda-Virus-Scanned: by cuda.sgi.com at sgi.com X-Barracuda-Spam-Score: -2.01 X-Barracuda-Spam-Status: No, SCORE=-2.01 using per-user scores of TAG_LEVEL=2.0 QUARANTINE_LEVEL=1000.0 KILL_LEVEL=2.1 tests= X-Barracuda-Spam-Report: Code version 3.2, rules version 3.2.1.3632 Rule breakdown below pts rule name description ---- ---------------------- -------------------------------------------------- X-archive-position: 1448 X-ecartis-version: Ecartis v1.0.0 Sender: kdb-bounce@oss.sgi.com Errors-to: kdb-bounce@oss.sgi.com X-original-sender: eerpini@gmail.com Precedence: bulk X-list: kdb i have fixed up errors concerning the previous ones i have mentioned , ... but new errors have appeared , : CHK include/linux/version.h CHK include/linux/utsrelease.h CHK include/linux/compile.h GEN .version CHK include/linux/compile.h UPD include/linux/compile.h CC init/version.o LD init/built-in.o LD .tmp_vmlinux1 kdb/built-in.o: In function `kdb_inittab': /usr/src/redhat/BUILD/kernel-2.6.18/linux-2.6.18.i386/kdb/kdbmain.c:3816: undefined reference to `__kdb_initcall_start' /usr/src/redhat/BUILD/kernel-2.6.18/linux-2.6.18.i386/kdb/kdbmain.c:3822: undefined reference to `__kdb_initcall_end' make: *** [.tmp_vmlinux1] Error 1 i have checked the code which corressponds to the above errors , it is something liket this : /* Any kdb commands that are not in the base code but are required * earlier than normal initcall processing. */ call = & __kdb_initcall_start; while (call < & __kdb_initcall_end) { (*call)(); call++; }; , but i don't understand why it is showing an undefined reference error , __kdb_initcall_start and __kdb_initcall_end are defined in include/linux/kdbprivate.h as follows : #ifdef MODULE #define kdb_module_init(fn) module_init(fn) #define kdb_module_exit(fn) module_exit(fn) #else /* !MODULE */ extern initcall_t __kdb_initcall_start, __kdb_initcall_end; #define kdb_module_init(fn) \ static initcall_t __kdb_initcall_##fn __attribute_used__ __attribute__ ((__section__ (".kdb_initcall.init"))) = fn; #define kdb_module_exit(fn) \ static exitcall_t __kdb_exitcall_##fn __attribute_used__ __attribute__ ((__section__ (".kdb_exitcall.exit"))) = fn; #endif /* MODULE */ then what does the error signify ? Thanks Satish -- http://satish.playdrupal.com --------------------------- Use http://oss.sgi.com/ecartis to modify your settings or to unsubscribe. From jidong.xiao@gmail.com Mon Aug 25 02:16:46 2008 Received: with ECARTIS (v1.0.0; list kdb); Mon, 25 Aug 2008 02:16:54 -0700 (PDT) Received: from cuda.sgi.com (cuda1.sgi.com [192.48.168.28]) by oss.sgi.com (8.12.11.20060308/8.12.11/SuSE Linux 0.7) with ESMTP id m7P9GkQQ025867 for ; Mon, 25 Aug 2008 02:16:46 -0700 X-ASG-Debug-ID: 1219655888-731901450000-sLlkUa X-Barracuda-URL: http://cuda.sgi.com:80/cgi-bin/mark.cgi Received: from fg-out-1718.google.com (localhost [127.0.0.1]) by cuda.sgi.com (Spam Firewall) with ESMTP id 9A065FB0C64 for ; Mon, 25 Aug 2008 02:18:08 -0700 (PDT) Received: from fg-out-1718.google.com (fg-out-1718.google.com [72.14.220.158]) by cuda.sgi.com with ESMTP id ttEn5sec36WiBiOa for ; Mon, 25 Aug 2008 02:18:08 -0700 (PDT) Received: by fg-out-1718.google.com with SMTP id l26so928021fgb.8 for ; Mon, 25 Aug 2008 02:18:07 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:cc:in-reply-to:mime-version:content-type :content-transfer-encoding:content-disposition:references; bh=sASJhGuOnqsXkX9UjaS7gr/PLXm16CKO9DWOJSyZTzE=; b=k3K9ksKNKfCXFe+zj0OKJbTTXseg/HshZgUu6O5Z0U393Kq5+NBW0D423RCrmPTgar ezBrhhr8zvLN5NWEkQ7OkxJ1X2kg9965mZOKtWTOJN4Uxf3f4octQoNRLgzwN3W2o4RY IWnCXlMI3uxoEgBP89XhlcS1z/fnbZZ/Zk1iU= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version :content-type:content-transfer-encoding:content-disposition :references; b=Hiw3oq87V/BwA/ySNvWifhOYUlW+w39GXi7eJ6szPwU06nAevKbcl1JNqK7nz3LnV4 MsRrnRAS7v8gDDod9lMbAcxCN6erNPujhZlF4vQGvqMyCd2rATTwUzuArS6qMSynkG6h Ww+PXzzYkNqcrJ1PP4bS2aWO8LiYtRvHjvcXU= Received: by 10.86.63.19 with SMTP id l19mr3137655fga.77.1219655887548; Mon, 25 Aug 2008 02:18:07 -0700 (PDT) Received: by 10.86.93.10 with HTTP; Mon, 25 Aug 2008 02:18:07 -0700 (PDT) Message-ID: <4104961b0808250218u2e1d6f47obfb39f96261467e4@mail.gmail.com> Date: Mon, 25 Aug 2008 17:18:07 +0800 From: "jidong xiao" To: "Satish Eerpini" X-ASG-Orig-Subj: Re: patching kdb to the Centos Kernel : more errors Subject: Re: patching kdb to the Centos Kernel : more errors Cc: kdb@oss.sgi.com, bgnaidu@yahoo.com In-Reply-To: <93655eb70808241907w7bf40ef1qd08166cccb64d966@mail.gmail.com> MIME-Version: 1.0 Content-type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Content-Disposition: inline References: <93655eb70808241907w7bf40ef1qd08166cccb64d966@mail.gmail.com> X-Barracuda-Connect: fg-out-1718.google.com[72.14.220.158] X-Barracuda-Start-Time: 1219655889 X-Barracuda-Bayes: INNOCENT GLOBAL 0.0000 1.0000 -2.0210 X-Barracuda-Virus-Scanned: by cuda.sgi.com at sgi.com X-Barracuda-Spam-Score: -2.02 X-Barracuda-Spam-Status: No, SCORE=-2.02 using per-user scores of TAG_LEVEL=2.0 QUARANTINE_LEVEL=1000.0 KILL_LEVEL=2.1 tests= X-Barracuda-Spam-Report: Code version 3.2, rules version 3.2.1.3657 Rule breakdown below pts rule name description ---- ---------------------- -------------------------------------------------- X-archive-position: 1449 X-ecartis-version: Ecartis v1.0.0 Sender: kdb-bounce@oss.sgi.com Errors-to: kdb-bounce@oss.sgi.com X-original-sender: jidong.xiao@gmail.com Precedence: bulk X-list: kdb On Mon, Aug 25, 2008 at 10:07 AM, Satish Eerpini wrote: > i have fixed up errors concerning the previous ones i have mentioned > , ... but new errors have appeared , : > > CHK include/linux/version.h > CHK include/linux/utsrelease.h > CHK include/linux/compile.h > GEN .version > CHK include/linux/compile.h > UPD include/linux/compile.h > CC init/version.o > LD init/built-in.o > LD .tmp_vmlinux1 > kdb/built-in.o: In function `kdb_inittab': > /usr/src/redhat/BUILD/kernel-2.6.18/linux-2.6.18.i386/kdb/kdbmain.c:3816: > undefined reference to `__kdb_initcall_start' > /usr/src/redhat/BUILD/kernel-2.6.18/linux-2.6.18.i386/kdb/kdbmain.c:3822: > undefined reference to `__kdb_initcall_end' > make: *** [.tmp_vmlinux1] Error 1 > > i have checked the code which corressponds to the above errors , it is > something liket this : > > /* Any kdb commands that are not in the base code but are required > * earlier than normal initcall processing. > */ > call = & __kdb_initcall_start; > while (call < & __kdb_initcall_end) { > (*call)(); > call++; > }; > > , but i don't understand why it is showing an undefined reference > error , __kdb_initcall_start and __kdb_initcall_end are defined in > include/linux/kdbprivate.h as follows : > > #ifdef MODULE > #define kdb_module_init(fn) module_init(fn) > #define kdb_module_exit(fn) module_exit(fn) > #else /* !MODULE */ > extern initcall_t __kdb_initcall_start, __kdb_initcall_end; > #define kdb_module_init(fn) \ > static initcall_t __kdb_initcall_##fn __attribute_used__ > __attribute__ ((__section__ (".kdb_initcall.init"))) = fn; > #define kdb_module_exit(fn) \ > static exitcall_t __kdb_exitcall_##fn __attribute_used__ > __attribute__ ((__section__ (".kdb_exitcall.exit"))) = fn; > #endif /* MODULE */ > > then what does the error signify ? > First of all, as you are using Cent OS kernel, perhaps there is some difference between your source code and mine, maybe kdbprivate.h is not included correctly. Second of all, I think you can remove the lines. /* Any kdb commands that are not in the base code but are required * earlier than normal initcall processing. */ call = & __kdb_initcall_start; while (call < & __kdb_initcall_end) { (*call)(); call++; }; They are not existing in the latest kdb patches. Regards Jason > > Thanks > Satish > > > -- > http://satish.playdrupal.com > --------------------------- > Use http://oss.sgi.com/ecartis to modify your settings or to unsubscribe. > --------------------------- Use http://oss.sgi.com/ecartis to modify your settings or to unsubscribe. From eerpini@gmail.com Mon Aug 25 07:03:51 2008 Received: with ECARTIS (v1.0.0; list kdb); Mon, 25 Aug 2008 07:03:57 -0700 (PDT) Received: from cuda.sgi.com (cuda2.sgi.com [192.48.168.29]) by oss.sgi.com (8.12.11.20060308/8.12.11/SuSE Linux 0.7) with ESMTP id m7PE3o6s018401 for ; Mon, 25 Aug 2008 07:03:50 -0700 X-ASG-Debug-ID: 1219673111-685603040000-sLlkUa X-Barracuda-URL: http://cuda.sgi.com:80/cgi-bin/mark.cgi Received: from mail-gx0-f21.google.com (localhost [127.0.0.1]) by cuda.sgi.com (Spam Firewall) with ESMTP id A413617D5E8 for ; Mon, 25 Aug 2008 07:05:11 -0700 (PDT) Received: from mail-gx0-f21.google.com (mail-gx0-f21.google.com [209.85.217.21]) by cuda.sgi.com with ESMTP id xA2j9EbOGYJnjdQq for ; Mon, 25 Aug 2008 07:05:11 -0700 (PDT) Received: by gxk14 with SMTP id 14so1972739gxk.20 for ; Mon, 25 Aug 2008 07:05:11 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:cc:in-reply-to:mime-version:content-type :content-transfer-encoding:content-disposition:references; bh=tps4e94CoDUL5rgwTMiqZREKw2fQHnTgdA9k4BvJLXg=; b=CuE3rhO8VzhuaSDmNA83VldK2ESesZG6TozrlULQgMbq2/fn+5IoszaIlR8GrSmbzE /oKz8QJTBcerOXCLYQnDn6b0jdvQiBL9FEraQ1psRwLGWpUuMIU8fzusj1HX+H6FHHui OSF9w0b8bOOYusdQWWFmUY7DVTFgo4wcNlI9A= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version :content-type:content-transfer-encoding:content-disposition :references; b=ImfIc+FyT+0DPA0gSveWFn6EfYGpZGl/5xQYbKTxKioAlen/9VBr7RHP77ULBb3cyl NP2GyBIZjKvT+DdSh8VHP9vjZcSLSqS8cDEh1R3HcET9UEphaRzNSW5CtV7WyexhBOlg 6VhuFgHXOs5RQbmoHlfBOBvqvJV9BFXISgupM= Received: by 10.151.156.12 with SMTP id i12mr7171955ybo.208.1219673111269; Mon, 25 Aug 2008 07:05:11 -0700 (PDT) Received: by 10.151.147.7 with HTTP; Mon, 25 Aug 2008 07:05:11 -0700 (PDT) Message-ID: <93655eb70808250705n432ed044ycd9b9a225a11bcb6@mail.gmail.com> Date: Mon, 25 Aug 2008 19:35:11 +0530 From: "Satish Eerpini" To: "jidong xiao" X-ASG-Orig-Subj: Re: patching kdb to the Centos Kernel : more errors Subject: Re: patching kdb to the Centos Kernel : more errors Cc: kdb@oss.sgi.com, bgnaidu@yahoo.com In-Reply-To: <4104961b0808250218u2e1d6f47obfb39f96261467e4@mail.gmail.com> MIME-Version: 1.0 Content-type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Content-Disposition: inline References: <93655eb70808241907w7bf40ef1qd08166cccb64d966@mail.gmail.com> <4104961b0808250218u2e1d6f47obfb39f96261467e4@mail.gmail.com> X-Barracuda-Connect: mail-gx0-f21.google.com[209.85.217.21] X-Barracuda-Start-Time: 1219673112 X-Barracuda-Bayes: INNOCENT GLOBAL 0.0000 1.0000 -2.0210 X-Barracuda-Virus-Scanned: by cuda.sgi.com at sgi.com X-Barracuda-Spam-Score: -2.02 X-Barracuda-Spam-Status: No, SCORE=-2.02 using per-user scores of TAG_LEVEL=2.0 QUARANTINE_LEVEL=1000.0 KILL_LEVEL=2.1 tests= X-Barracuda-Spam-Report: Code version 3.2, rules version 3.2.1.3680 Rule breakdown below pts rule name description ---- ---------------------- -------------------------------------------------- X-archive-position: 1450 X-ecartis-version: Ecartis v1.0.0 Sender: kdb-bounce@oss.sgi.com Errors-to: kdb-bounce@oss.sgi.com X-original-sender: eerpini@gmail.com Precedence: bulk X-list: kdb yeh i removed that part of the code , .... and now the vmlinux is created successfully, but in the second stage wheer the modules are built , i get the following warnings , : Root device is (8, 2) Boot sector 512 bytes. Setup is 7282 bytes. System is 1900 kB Kernel: arch/i386/boot/bzImage is ready (#8) Building modules, stage 2. MODPOST WARNING: vmlinux - Section mismatch: reference to .init.data:boot_params from .text between '_text' (at offset 0xc0400029) and 'startup_32_smp' WARNING: vmlinux - Section mismatch: reference to .init.data:boot_params from .text between '_text' (at offset 0xc0400037) and 'startup_32_smp' WARNING: vmlinux - Section mismatch: reference to .init.data:init_pg_tables_end from .text between '_text' (at offset 0xc0400099) and 'startup_32_smp' WARNING: vmlinux - Section mismatch: reference to .init.data:new_cpu_data from .text between 'checkCPUtype' (at offset 0xc0400126) and 'is486' WARNING: vmlinux - Section mismatch: reference to .init.data:new_cpu_data from .text between 'checkCPUtype' (at offset 0xc0400130) and 'is486' WARNING: vmlinux - Section mismatch: reference to .init.data:new_cpu_data from .text between 'checkCPUtype' (at offset 0xc040014f) and 'is486' WARNING: vmlinux - Section mismatch: reference to .init.data:new_cpu_data from .text between 'checkCPUtype' (at offset 0xc0400160) and 'is486' WARNING: vmlinux - Section mismatch: reference to .init.data:new_cpu_data from .text between 'checkCPUtype' (at offset 0xc0400166) and 'is486' WARNING: vmlinux - Section mismatch: reference to .init.data:new_cpu_data from .text between 'checkCPUtype' (at offset 0xc040016c) and 'is486' WARNING: vmlinux - Section mismatch: reference to .init.data:new_cpu_data from .text between 'checkCPUtype' (at offset 0xc0400172) and 'is486' WARNING: vmlinux - Section mismatch: reference to .init.data:new_cpu_data from .text between 'checkCPUtype' (at offset 0xc0400188) and 'is486' WARNING: vmlinux - Section mismatch: reference to .init.data:new_cpu_data from .text between 'checkCPUtype' (at offset 0xc0400192) and 'is486' WARNING: vmlinux - Section mismatch: reference to .init.data:new_cpu_data from .text between 'checkCPUtype' (at offset 0xc040019b) and 'is486' WARNING: vmlinux - Section mismatch: reference to .init.data:new_cpu_data from .text between 'checkCPUtype' (at offset 0xc04001a1) and 'is486' WARNING: vmlinux - Section mismatch: reference to .init.data:new_cpu_data from .text between 'check_x87' (at offset 0xc0400210) and 'setup_idt' WARNING: vmlinux - Section mismatch: reference to .init.data:new_cpu_data from .text between 'check_x87' (at offset 0xc040022e) and 'setup_idt' WARNING: vmlinux - Section mismatch: reference to .init.text:start_kernel from .text between 'is386' (at offset 0xc040020a) and 'check_x87' WARNING: vmlinux - Section mismatch: reference to .init.text:smp_prepare_cpus from .text between 'init' (at offset 0xc04002e6) and 'try_name' WARNING: vmlinux - Section mismatch: reference to .init.text:migration_init from .text between 'init' (at offset 0xc04002eb) and 'try_name' WARNING: vmlinux - Section mismatch: reference to .init.text:spawn_ksoftirqd from .text between 'init' (at offset 0xc04002f0) and 'try_name' WARNING: vmlinux - Section mismatch: reference to .init.data: from .text between 'init' (at offset 0xc04002f6) and 'try_name' WARNING: vmlinux - Section mismatch: reference to .init.text:spawn_softlockup_task from .text between 'init' (at offset 0xc04002fe) and 'try_name' WARNING: vmlinux - Section mismatch: reference to .init.text:smp_cpus_done from .text between 'init' (at offset 0xc0400367) and 'try_name' WARNING: vmlinux - Section mismatch: reference to .init.text:sched_init_smp from .text between 'init' (at offset 0xc04003d2) and 'try_name' WARNING: vmlinux - Section mismatch: reference to .init.text:cpuset_init_smp from .text between 'init' (at offset 0xc04003d7) and 'try_name' WARNING: vmlinux - Section mismatch: reference to .init.text:populate_rootfs from .text between 'init' (at offset 0xc04003dc) and 'try_name' WARNING: vmlinux - Section mismatch: reference to .init.text:usermodehelper_init from .text between 'init' (at offset 0xc04003e6) and 'try_name' WARNING: vmlinux - Section mismatch: reference to .init.text:driver_init from .text between 'init' (at offset 0xc04003eb) and 'try_name' WARNING: vmlinux - Section mismatch: reference to .init.text:sysctl_init from .text between 'init' (at offset 0xc04003f0) and 'try_name' WARNING: vmlinux - Section mismatch: reference to .init.data: from .text between 'init' (at offset 0xc0400407) and 'try_name' WARNING: vmlinux - Section mismatch: reference to .init.data: from .text between 'init' (at offset 0xc0400440) and 'try_name' WARNING: vmlinux - Section mismatch: reference to .init.text:prepare_namespace from .text between 'init' (at offset 0xc04004ee) and 'try_name' WARNING: vmlinux - Section mismatch: reference to .init.text:parse_unisys_oem from .text between 'mps_oem_check' (at offset 0xc04014b5) and 'acpi_madt_oem_check' WARNING: vmlinux - Section mismatch: reference to .init.text:find_unisys_acpi_oem_table from .text between 'acpi_madt_oem_check' (at offset 0xc04014ca) and 'enable_apic_mode' WARNING: vmlinux - Section mismatch: reference to .init.text:acpi_get_table_header_early from .text between 'acpi_madt_oem_check' (at offset 0xc04014e3) and 'enable_apic_mode' WARNING: vmlinux - Section mismatch: reference to .init.text:parse_unisys_oem from .text between 'acpi_madt_oem_check' (at offset 0xc0401521) and 'enable_apic_mode' WARNING: vmlinux - Section mismatch: reference to .init.text:setup_unisys from .text between 'acpi_madt_oem_check' (at offset 0xc040152f) and 'enable_apic_mode' WARNING: vmlinux - Section mismatch: reference to .init.text:es7000_sw_apic from .text between 'enable_apic_mode' (at offset 0xc040153b) and 'get_apic_id' WARNING: vmlinux - Section mismatch: reference to .init.text:efi_set_rtc_mmss from .text between 'sync_cmos_clock' (at offset 0xc0407360) and 'get_cmos_time' WARNING: vmlinux - Section mismatch: reference to .init.text:efi_get_time from .text between 'get_cmos_time' (at offset 0xc0407534) and 'timer_resume' WARNING: vmlinux - Section mismatch: reference to .init.text:noirqdebug_setup from .text between 'quirk_intel_irqbalance' (at offset 0xc0409326) and 'i8237A_suspend' WARNING: vmlinux - Section mismatch: reference to .init.text:__alloc_bootmem from .text between 'cpu_init' (at offset 0xc040a313) and 'generic_identify' WARNING: vmlinux - Section mismatch: reference to .init.text:sysenter_setup from .text between 'identify_cpu' (at offset 0xc040a8ee) and 'c_start' WARNING: vmlinux - Section mismatch: reference to .init.text:mtrr_bp_init from .text between 'identify_cpu' (at offset 0xc040a901) and 'c_start' WARNING: vmlinux - Section mismatch: reference to .init.text: from .text between 'cyrix_identify' (at offset 0xc040ac66) and 'centaur_size_cache' WARNING: vmlinux - Section mismatch: reference to .init.data: from .text between 'write_new_vid' (at offset 0xc040e61b) and 'decrease_vid_code_by_step' WARNING: vmlinux - Section mismatch: reference to .init.data: from .text between 'write_new_fid' (at offset 0xc040e795) and 'powernowk8_target' WARNING: vmlinux - Section mismatch: reference to .init.data: from .text between 'powernowk8_target' (at offset 0xc040e9b1) and 'powernowk8_verify' WARNING: vmlinux - Section mismatch: reference to .init.data: from .text between 'powernowk8_target' (at offset 0xc040eb47) and 'powernowk8_verify' WARNING: vmlinux - Section mismatch: reference to .init.data: from .text between 'powernowk8_target' (at offset 0xc040ec00) and 'powernowk8_verify' WARNING: vmlinux - Section mismatch: reference to .init.data: from .text between 'powernowk8_target' (at offset 0xc040ec67) and 'powernowk8_verify' WARNING: vmlinux - Section mismatch: reference to .init.data: from .text between 'powernowk8_target' (at offset 0xc040edfb) and 'powernowk8_verify' WARNING: vmlinux - Section mismatch: reference to .init.data: from .text between 'powernowk8_target' (at offset 0xc040f038) and 'powernowk8_verify' WARNING: vmlinux - Section mismatch: reference to .init.data: from .text between 'powernowk8_init' (at offset 0xc040f1a3) and 'powernowk8_cpu_init' WARNING: vmlinux - Section mismatch: reference to .init.data: from .text between 'powernowk8_cpu_init' (at offset 0xc040faee) and 'longrun_set_policy' WARNING: vmlinux - Section mismatch: reference to .init.data: from .text between 'powernowk8_cpu_init' (at offset 0xc040fc63) and 'longrun_set_policy' WARNING: vmlinux - Section mismatch: reference to .init.data: from .text between 'start_secondary' (at offset 0xc041673d) and '__cpu_die' WARNING: vmlinux - Section mismatch: reference to .init.data: from .text between 'start_secondary' (at offset 0xc0416748) and '__cpu_die' WARNING: vmlinux - Section mismatch: reference to .init.data: from .text between 'start_secondary' (at offset 0xc0416754) and '__cpu_die' WARNING: vmlinux - Section mismatch: reference to .init.data: from .text between 'start_secondary' (at offset 0xc0416763) and '__cpu_die' WARNING: vmlinux - Section mismatch: reference to .init.data: from .text between 'start_secondary' (at offset 0xc0416795) and '__cpu_die' WARNING: vmlinux - Section mismatch: reference to .init.data: from .text between 'start_secondary' (at offset 0xc04167a4) and '__cpu_die' WARNING: vmlinux - Section mismatch: reference to .init.data: from .text between 'MP_processor_info' (at offset 0xc0416e19) and 'mp_register_lapic' WARNING: vmlinux - Section mismatch: reference to .init.data:maxcpus from .text between 'MP_processor_info' (at offset 0xc0416ea0) and 'mp_register_lapic' WARNING: vmlinux - Section mismatch: reference to .init.text:__init_begin from .text between 'free_initmem' (at offset 0xc041af64) and 'mark_rodata_ro' WARNING: vmlinux - Section mismatch: reference to .init.text:_sinittext from .text between 'core_kernel_text' (at offset 0xc0433ed2) and 'kernel_text_address' WARNING: vmlinux - Section mismatch: reference to .init.text:_einittext from .text between 'core_kernel_text' (at offset 0xc0433edc) and 'kernel_text_address' WARNING: vmlinux - Section mismatch: reference to .init.text:_sinittext from .text between 'kernel_text_address' (at offset 0xc0433ef3) and '__kernel_text_address' WARNING: vmlinux - Section mismatch: reference to .init.text:_einittext from .text between 'kernel_text_address' (at offset 0xc0433efa) and '__kernel_text_address' WARNING: vmlinux - Section mismatch: reference to .init.text:_sinittext from .text between '__kernel_text_address' (at offset 0xc0433f23) and 'search_exception_tables' WARNING: vmlinux - Section mismatch: reference to .init.text:_einittext from .text between '__kernel_text_address' (at offset 0xc0433f2a) and 'search_exception_tables' WARNING: vmlinux - Section mismatch: reference to .init.text:_sinittext from .text between 'kallsyms_lookup' (at offset 0xc043f550) and '__print_symbol' WARNING: vmlinux - Section mismatch: reference to .init.text:_einittext from .text between 'kallsyms_lookup' (at offset 0xc043f557) and '__print_symbol' WARNING: vmlinux - Section mismatch: reference to .init.data:initkmem_list3 from .text between 'kmem_cache_create' (at offset 0xc046a1ee) and 'xip_truncate_page' WARNING: vmlinux - Section mismatch: reference to .init.data:initkmem_list3 from .text between 'kmem_cache_create' (at offset 0xc046a200) and 'xip_truncate_page' WARNING: vmlinux - Section mismatch: reference to .init.data:initkmem_list3 from .text between 'kmem_cache_create' (at offset 0xc046a254) and 'xip_truncate_page' WARNING: vmlinux - Section mismatch: reference to .init.data:initkmem_list3 from .text between 'kmem_cache_create' (at offset 0xc046a266) and 'xip_truncate_page' WARNING: vmlinux - Section mismatch: reference to .init.text:__alloc_bootmem from .text between 'vgacon_startup' (at offset 0xc0500142) and 'fbcon_update_softback' WARNING: vmlinux - Section mismatch: reference to .init.data:logo_linux_clut224 from .text between 'fb_find_logo' (at offset 0xc0508ba8) and 'acpi_table_print_madt_entry' WARNING: vmlinux - Section mismatch: reference to .init.text:uart_parse_options from .text between 'serial8250_console_setup' (at offset 0xc054cb2a) and 'serial8250_console_write' WARNING: vmlinux - Section mismatch: reference to .init.text:uart_set_options from .text between 'serial8250_console_setup' (at offset 0xc054cb4d) and 'serial8250_console_write' WARNING: vmlinux - Section mismatch: reference to .init.data:acpi_noirq from .text between 'pcibios_penalize_isa_irq' (at offset 0xc05a85aa) and 'pci_read' WARNING: vmlinux - Section mismatch: reference to .init.data:acpi_noirq from .text between 'pcibios_setup' (at offset 0xc05a88d5) and 'pcibios_scan_root' WARNING: vmlinux - Section mismatch: reference to .init.text: from .pci_fixup between '__pci_fixup_PCI_VENDOR_ID_INTELPCI_DEVICE_ID_INTEL_82454NXquirk_disable_pxb' (at offset 0xc066e280) and '__pci_fixup_PCI_VENDOR_ID_CYRIXPCI_DEVICE_ID_CYRIX_PCI_MASTERquirk_mediagx_master' WARNING: vmlinux - Section mismatch: reference to .init.text: from .pci_fixup between '__pci_fixup_PCI_VENDOR_ID_CYRIXPCI_DEVICE_ID_CYRIX_PCI_MASTERquirk_mediagx_master' (at offset 0xc066e288) and '__pci_fixup_PCI_VENDOR_ID_AMDPCI_DEVICE_ID_AMD_FE_GATE_700Cquirk_amd_ordering' WARNING: vmlinux - Section mismatch: reference to .init.text: from .pci_fixup between '__pci_fixup_PCI_VENDOR_ID_SERVERWORKSPCI_DEVICE_ID_SERVERWORKS_GCNB_LEquirk_svw_msi' (at offset 0xc066e2a0) and '__pci_fixup_PCI_VENDOR_ID_AMDPCI_DEVICE_ID_AMD_8131_BRIDGEquirk_amd_8131_ioapic' WARNING: vmlinux - Section mismatch: reference to .init.text: from .pci_fixup between '__pci_fixup_PCI_VENDOR_ID_AMDPCI_DEVICE_ID_AMD_8131_BRIDGEquirk_amd_8131_ioapic' (at offset 0xc066e2a8) and '__pci_fixup_PCI_VENDOR_ID_SIPCI_ANY_IDquirk_ioapic_rmw' WARNING: vmlinux - Section mismatch: reference to .init.text: from .pci_fixup between '__pci_fixup_PCI_VENDOR_ID_SIPCI_ANY_IDquirk_ioapic_rmw' (at offset 0xc066e2b0) and '__pci_fixup_PCI_VENDOR_ID_AMDPCI_DEVICE_ID_AMD_VIPER_7410quirk_amd_ioapic' WARNING: vmlinux - Section mismatch: reference to .init.text: from .pci_fixup between '__pci_fixup_PCI_VENDOR_ID_ALPCI_DEVICE_ID_AL_M1651quirk_alimagik' (at offset 0xc066e308) and '__pci_fixup_PCI_VENDOR_ID_ALPCI_DEVICE_ID_AL_M1647quirk_alimagik' WARNING: vmlinux - Section mismatch: reference to .init.text: from .pci_fixup between '__pci_fixup_PCI_VENDOR_ID_ALPCI_DEVICE_ID_AL_M1647quirk_alimagik' (at offset 0xc066e310) and '__pci_fixup_PCI_VENDOR_ID_VIAPCI_DEVICE_ID_VIA_82C576quirk_vsfx' WARNING: vmlinux - Section mismatch: reference to .init.text: from .pci_fixup between '__pci_fixup_PCI_VENDOR_ID_INTELPCI_DEVICE_ID_INTEL_EESSCquirk_alder_ioapic' (at offset 0xc066df88) and '__pci_fixup_PCI_VENDOR_ID_ATIPCI_DEVICE_ID_ATI_IXP600_SATAquirk_sb600_sata' WARNING: vmlinux - Section mismatch: reference to .init.text: from .pci_fixup between '__pci_fixup_PCI_VENDOR_ID_SIPCI_DEVICE_ID_SI_LPCquirk_sis_96x_smbus' (at offset 0xc066df98) and '__pci_fixup_PCI_VENDOR_ID_SIPCI_DEVICE_ID_SI_963quirk_sis_96x_smbus' WARNING: vmlinux - Section mismatch: reference to .init.text: from .pci_fixup between '__pci_fixup_PCI_VENDOR_ID_SIPCI_DEVICE_ID_SI_963quirk_sis_96x_smbus' (at offset 0xc066dfa0) and '__pci_fixup_PCI_VENDOR_ID_SIPCI_DEVICE_ID_SI_962quirk_sis_96x_smbus' WARNING: vmlinux - Section mismatch: reference to .init.text: from .pci_fixup between '__pci_fixup_PCI_VENDOR_ID_SIPCI_DEVICE_ID_SI_962quirk_sis_96x_smbus' (at offset 0xc066dfa8) and '__pci_fixup_PCI_VENDOR_ID_SIPCI_DEVICE_ID_SI_961quirk_sis_96x_smbus' WARNING: vmlinux - Section mismatch: reference to .init.text: from .pci_fixup between '__pci_fixup_PCI_VENDOR_ID_SIPCI_DEVICE_ID_SI_961quirk_sis_96x_smbus' (at offset 0xc066dfb0) and '__pci_fixup_PCI_VENDOR_ID_VIAPCI_DEVICE_ID_VIA_8237asus_hides_ac97_lpc' WARNING: vmlinux - Section mismatch: reference to .init.text: from .pci_fixup between '__pci_fixup_PCI_VENDOR_ID_VIAPCI_DEVICE_ID_VIA_8237asus_hides_ac97_lpc' (at offset 0xc066dfb8) and '__pci_fixup_PCI_VENDOR_ID_SIPCI_DEVICE_ID_SI_503quirk_sis_503' WARNING: vmlinux - Section mismatch: reference to .init.text: from .pci_fixup between '__pci_fixup_PCI_VENDOR_ID_SIPCI_DEVICE_ID_SI_503quirk_sis_503' (at offset 0xc066dfc0) and '__pci_fixup_PCI_VENDOR_ID_SIPCI_DEVICE_ID_SI_735quirk_sis_96x_compatible' WARNING: vmlinux - Section mismatch: reference to .init.text: from .pci_fixup between '__pci_fixup_PCI_VENDOR_ID_SIPCI_DEVICE_ID_SI_735quirk_sis_96x_compatible' (at offset 0xc066dfc8) and '__pci_fixup_PCI_VENDOR_ID_SIPCI_DEVICE_ID_SI_651quirk_sis_96x_compatible' WARNING: vmlinux - Section mismatch: reference to .init.text: from .pci_fixup between '__pci_fixup_PCI_VENDOR_ID_SIPCI_DEVICE_ID_SI_651quirk_sis_96x_compatible' (at offset 0xc066dfd0) and '__pci_fixup_PCI_VENDOR_ID_SIPCI_DEVICE_ID_SI_650quirk_sis_96x_compatible' WARNING: vmlinux - Section mismatch: reference to .init.text: from .pci_fixup between '__pci_fixup_PCI_VENDOR_ID_SIPCI_DEVICE_ID_SI_650quirk_sis_96x_compatible' (at offset 0xc066dfd8) and '__pci_fixup_PCI_VENDOR_ID_SIPCI_DEVICE_ID_SI_648quirk_sis_96x_compatible' WARNING: vmlinux - Section mismatch: reference to .init.text: from .pci_fixup between '__pci_fixup_PCI_VENDOR_ID_SIPCI_DEVICE_ID_SI_648quirk_sis_96x_compatible' (at offset 0xc066dfe0) and '__pci_fixup_PCI_VENDOR_ID_SIPCI_DEVICE_ID_SI_646quirk_sis_96x_compatible' WARNING: vmlinux - Section mismatch: reference to .init.text: from .pci_fixup between '__pci_fixup_PCI_VENDOR_ID_SIPCI_DEVICE_ID_SI_646quirk_sis_96x_compatible' (at offset 0xc066dfe8) and '__pci_fixup_PCI_VENDOR_ID_SIPCI_DEVICE_ID_SI_645quirk_sis_96x_compatible' WARNING: vmlinux - Section mismatch: reference to .init.text: from .pci_fixup between '__pci_fixup_PCI_VENDOR_ID_SIPCI_DEVICE_ID_SI_645quirk_sis_96x_compatible' (at offset 0xc066dff0) and '__pci_fixup_PCI_VENDOR_ID_VIAPCI_DEVICE_ID_VIA_8237k8t_sound_hostbridge' WARNING: vmlinux - Section mismatch: reference to .init.text: from .pci_fixup between '__pci_fixup_PCI_VENDOR_ID_VIAPCI_DEVICE_ID_VIA_8237k8t_sound_hostbridge' (at offset 0xc066dff8) and '__pci_fixup_PCI_VENDOR_ID_INTELPCI_DEVICE_ID_INTEL_82375quirk_eisa_bridge' WARNING: vmlinux - Section mismatch: reference to .init.text: from .pci_fixup between '__pci_fixup_PCI_VENDOR_ID_INTELPCI_DEVICE_ID_INTEL_82375quirk_eisa_bridge' (at offset 0xc066e000) and '__pci_fixup_PCI_VENDOR_ID_INTELPCI_DEVICE_ID_INTEL_82801CA_10quirk_ide_samemode' WARNING: vmlinux - Section mismatch: reference to .init.text: from .pci_fixup between '__pci_fixup_PCI_VENDOR_ID_INTELPCI_DEVICE_ID_INTEL_82801CA_10quirk_ide_samemode' (at offset 0xc066e008) and '__pci_fixup_PCI_VENDOR_ID_SERVERWORKSPCI_DEVICE_ID_SERVERWORKS_CSB5IDEquirk_svwks_csb5ide' WARNING: vmlinux - Section mismatch: reference to .init.text: from .pci_fixup between '__pci_fixup_PCI_VENDOR_ID_NVIDIAPCI_DEVICE_ID_NVIDIA_NFORCE2pci_fixup_nforce2' (at offset 0xc066e108) and '__pci_fixup_PCI_VENDOR_ID_INTELPCI_ANY_IDpci_fixup_transparent_bridge' WARNING: vmlinux - Section mismatch: reference to .init.text: from .data between 'apic_summit' (at offset 0xc0687c44) and 'apic_bigsmp' WARNING: vmlinux - Section mismatch: reference to .init.text: from .data between 'apic_bigsmp' (at offset 0xc0687cd0) and 'cpu.4241' WARNING: vmlinux - Section mismatch: reference to .init.text: from .data between 'apic_es7000' (at offset 0xc0687d60) and 'apic_default' WARNING: vmlinux - Section mismatch: reference to .init.text: from .data between 'apic_default' (at offset 0xc0687dec) and 'interrupt' WARNING: vmlinux - Section mismatch: reference to .init.text: from .smp_alternatives between '__smp_alt_begin' (at offset 0xc0730000) and '__smp_locks_end' WARNING: vmlinux - Section mismatch: reference to .init.text: from .smp_alternatives between '__smp_alt_begin' (at offset 0xc0730004) and '__smp_locks_end' WARNING: vmlinux - Section mismatch: reference to .init.text: from .smp_alternatives between '__smp_alt_begin' (at offset 0xc0730008) and '__smp_locks_end' WARNING: vmlinux - Section mismatch: reference to .init.text: from .smp_alternatives between '__smp_alt_begin' (at offset 0xc07300bc) and '__smp_locks_end' WARNING: vmlinux - Section mismatch: reference to .init.text: from .smp_alternatives between '__smp_alt_begin' (at offset 0xc07300c0) and '__smp_locks_end' WARNING: vmlinux - Section mismatch: reference to .init.text: from .smp_alternatives between '__smp_alt_begin' (at offset 0xc07300d8) and '__smp_locks_end' WARNING: vmlinux - Section mismatch: reference to .init.text: from .smp_alternatives between '__smp_alt_begin' (at offset 0xc07300dc) and '__smp_locks_end' WARNING: vmlinux - Section mismatch: reference to .init.text: from .smp_alternatives between '__smp_alt_begin' (at offset 0xc073010c) and '__smp_locks_end' WARNING: vmlinux - Section mismatch: reference to .init.text: from .smp_alternatives between '__smp_alt_begin' (at offset 0xc0730110) and '__smp_locks_end' WARNING: vmlinux - Section mismatch: reference to .init.text: from .smp_alternatives between '__smp_alt_begin' (at offset 0xc0730114) and '__smp_locks_end' WARNING: vmlinux - Section mismatch: reference to .init.text: from .smp_alternatives between '__smp_alt_begin' (at offset 0xc0730118) and '__smp_locks_end' WARNING: vmlinux - Section mismatch: reference to .init.text: from .smp_alternatives between '__smp_alt_begin' (at offset 0xc073011c) and '__smp_locks_end' WARNING: vmlinux - Section mismatch: reference to .init.text: from .smp_alternatives between '__smp_alt_begin' (at offset 0xc0730120) and '__smp_locks_end' WARNING: vmlinux - Section mismatch: reference to .init.text: from .smp_alternatives between '__smp_alt_begin' (at offset 0xc0730124) and '__smp_locks_end' WARNING: vmlinux - Section mismatch: reference to .init.text: from .smp_alternatives between '__smp_alt_begin' (at offset 0xc0730128) and '__smp_locks_end' WARNING: vmlinux - Section mismatch: reference to .init.text: from .smp_alternatives between '__smp_alt_begin' (at offset 0xc073012c) and '__smp_locks_end' WARNING: vmlinux - Section mismatch: reference to .init.text: from .smp_alternatives between '__smp_alt_begin' (at offset 0xc0730130) and '__smp_locks_end' WARNING: vmlinux - Section mismatch: reference to .init.text: from .smp_alternatives between '__smp_alt_begin' (at offset 0xc0730134) and '__smp_locks_end' WARNING: vmlinux - Section mismatch: reference to .init.text: from .smp_alternatives between '__smp_alt_begin' (at offset 0xc0730138) and '__smp_locks_end' WARNING: vmlinux - Section mismatch: reference to .init.text: from .smp_alternatives between '__smp_alt_begin' (at offset 0xc073013c) and '__smp_locks_end' WARNING: vmlinux - Section mismatch: reference to .init.text: from .smp_alternatives between '__smp_alt_begin' (at offset 0xc0730140) and '__smp_locks_end' WARNING: vmlinux - Section mismatch: reference to .init.text: from .smp_alternatives between '__smp_alt_begin' (at offset 0xc0730144) and '__smp_locks_end' WARNING: vmlinux - Section mismatch: reference to .init.text: from .smp_alternatives between '__smp_alt_begin' (at offset 0xc0730148) and '__smp_locks_end' WARNING: vmlinux - Section mismatch: reference to .init.text: from .smp_alternatives between '__smp_alt_begin' (at offset 0xc073014c) and '__smp_locks_end' WARNING: vmlinux - Section mismatch: reference to .init.text: from .smp_alternatives between '__smp_alt_begin' (at offset 0xc0730150) and '__smp_locks_end' WARNING: vmlinux - Section mismatch: reference to .init.text: from .smp_alternatives between '__smp_alt_begin' (at offset 0xc0730154) and '__smp_locks_end' WARNING: vmlinux - Section mismatch: reference to .init.text: from .smp_alternatives between '__smp_alt_begin' (at offset 0xc0730158) and '__smp_locks_end' WARNING: vmlinux - Section mismatch: reference to .init.text: from .smp_alternatives between '__smp_alt_begin' (at offset 0xc0730180) and '__smp_locks_end' WARNING: vmlinux - Section mismatch: reference to .init.text: from .smp_alternatives between '__smp_alt_begin' (at offset 0xc0730248) and '__smp_locks_end' WARNING: vmlinux - Section mismatch: reference to .init.text: from .smp_alternatives between '__smp_alt_begin' (at offset 0xc073024c) and '__smp_locks_end' WARNING: vmlinux - Section mismatch: reference to .init.text: from .smp_alternatives between '__smp_alt_begin' (at offset 0xc0730250) and '__smp_locks_end' WARNING: vmlinux - Section mismatch: reference to .init.text: from .smp_alternatives between '__smp_alt_begin' (at offset 0xc0730254) and '__smp_locks_end' WARNING: vmlinux - Section mismatch: reference to .init.text: from .smp_alternatives between '__smp_alt_begin' (at offset 0xc0730258) and '__smp_locks_end' WARNING: vmlinux - Section mismatch: reference to .init.text: from .smp_alternatives between '__smp_alt_begin' (at offset 0xc073025c) and '__smp_locks_end' WARNING: vmlinux - Section mismatch: reference to .init.text: from .smp_alternatives between '__smp_alt_begin' (at offset 0xc0730260) and '__smp_locks_end' WARNING: vmlinux - Section mismatch: reference to .init.text: from .smp_alternatives between '__smp_alt_begin' (at offset 0xc0730264) and '__smp_locks_end' WARNING: vmlinux - Section mismatch: reference to .init.text: from .smp_alternatives between '__smp_alt_begin' (at offset 0xc0730268) and '__smp_locks_end' WARNING: vmlinux - Section mismatch: reference to .init.text: from .smp_alternatives between '__smp_alt_begin' (at offset 0xc073026c) and '__smp_locks_end' WARNING: vmlinux - Section mismatch: reference to .init.text: from .smp_alternatives between '__smp_alt_begin' (at offset 0xc0730270) and '__smp_locks_end' WARNING: vmlinux - Section mismatch: reference to .init.text: from .smp_alternatives between '__smp_alt_begin' (at offset 0xc0730274) and '__smp_locks_end' WARNING: vmlinux - Section mismatch: reference to .init.text: from .smp_alternatives between '__smp_alt_begin' (at offset 0xc0730278) and '__smp_locks_end' WARNING: vmlinux - Section mismatch: reference to .init.text: from .smp_alternatives between '__smp_alt_begin' (at offset 0xc073027c) and '__smp_locks_end' WARNING: vmlinux - Section mismatch: reference to .init.text: from .smp_alternatives between '__smp_alt_begin' (at offset 0xc0730280) and '__smp_locks_end' WARNING: vmlinux - Section mismatch: reference to .init.text: from .smp_alternatives between '__smp_alt_begin' (at offset 0xc0730284) and '__smp_locks_end' WARNING: vmlinux - Section mismatch: reference to .init.text: from .smp_alternatives between '__smp_alt_begin' (at offset 0xc0730288) and '__smp_locks_end' WARNING: vmlinux - Section mismatch: reference to .init.text: from .smp_alternatives between '__smp_alt_begin' (at offset 0xc073028c) and '__smp_locks_end' WARNING: vmlinux - Section mismatch: reference to .init.text: from .smp_alternatives between '__smp_alt_begin' (at offset 0xc0730290) and '__smp_locks_end' WARNING: vmlinux - Section mismatch: reference to .init.text: from .smp_alternatives between '__smp_alt_begin' (at offset 0xc0730294) and '__smp_locks_end' WARNING: vmlinux - Section mismatch: reference to .init.text: from .smp_alternatives between '__smp_alt_begin' (at offset 0xc0730298) and '__smp_locks_end' WARNING: vmlinux - Section mismatch: reference to .init.text: from .smp_alternatives between '__smp_alt_begin' (at offset 0xc073029c) and '__smp_locks_end' WARNING: vmlinux - Section mismatch: reference to .init.text: from .smp_alternatives between '__smp_alt_begin' (at offset 0xc07302a0) and '__smp_locks_end' WARNING: vmlinux - Section mismatch: reference to .init.text: from .smp_alternatives between '__smp_alt_begin' (at offset 0xc07302a4) and '__smp_locks_end' WARNING: vmlinux - Section mismatch: reference to .init.text: from .smp_alternatives between '__smp_alt_begin' (at offset 0xc07302a8) and '__smp_locks_end' WARNING: vmlinux - Section mismatch: reference to .init.text: from .smp_alternatives between '__smp_alt_begin' (at offset 0xc07302ac) and '__smp_locks_end' WARNING: vmlinux - Section mismatch: reference to .init.text: from .smp_alternatives between '__smp_alt_begin' (at offset 0xc07302b0) and '__smp_locks_end' WARNING: vmlinux - Section mismatch: reference to .init.text: from .smp_alternatives between '__smp_alt_begin' (at offset 0xc07302d0) and '__smp_locks_end' WARNING: vmlinux - Section mismatch: reference to .init.text: from .smp_alternatives between '__smp_alt_begin' (at offset 0xc07302d4) and '__smp_locks_end' WARNING: vmlinux - Section mismatch: reference to .init.text: from .smp_alternatives between '__smp_alt_begin' (at offset 0xc07302d8) and '__smp_locks_end' WARNING: vmlinux - Section mismatch: reference to .init.text: from .smp_alternatives between '__smp_alt_begin' (at offset 0xc07302dc) and '__smp_locks_end' WARNING: vmlinux - Section mismatch: reference to .init.text: from .smp_alternatives between '__smp_alt_begin' (at offset 0xc07302e4) and '__smp_locks_end' WARNING: vmlinux - Section mismatch: reference to .init.text: from .smp_alternatives between '__smp_alt_begin' (at offset 0xc07302f8) and '__smp_locks_end' WARNING: vmlinux - Section mismatch: reference to .init.text: from .smp_alternatives between '__smp_alt_begin' (at offset 0xc07302fc) and '__smp_locks_end' WARNING: vmlinux - Section mismatch: reference to .init.text: from .smp_alternatives between '__smp_alt_begin' (at offset 0xc0730318) and '__smp_locks_end' WARNING: vmlinux - Section mismatch: reference to .init.text: from .smp_alternatives between '__smp_alt_begin' (at offset 0xc0730330) and '__smp_locks_end' WARNING: vmlinux - Section mismatch: reference to .init.text: from .smp_alternatives between '__smp_alt_begin' (at offset 0xc07306cc) and '__smp_locks_end' WARNING: vmlinux - Section mismatch: reference to .init.text: from .smp_alternatives between '__smp_alt_begin' (at offset 0xc07306d0) and '__smp_locks_end' WARNING: vmlinux - Section mismatch: reference to .init.text: from .smp_alternatives between '__smp_alt_begin' (at offset 0xc0730ab4) and '__smp_locks_end' WARNING: vmlinux - Section mismatch: reference to .init.text: from .smp_alternatives between '__smp_alt_begin' (at offset 0xc0730ab8) and '__smp_locks_end' WARNING: vmlinux - Section mismatch: reference to .init.text: from .smp_alternatives between '__smp_alt_begin' (at offset 0xc0730abc) and '__smp_locks_end' WARNING: vmlinux - Section mismatch: reference to .init.text: from .smp_alternatives between '__smp_alt_begin' (at offset 0xc0730b58) and '__smp_locks_end' WARNING: vmlinux - Section mismatch: reference to .init.text: from .smp_alternatives between '__smp_alt_begin' (at offset 0xc07312ec) and '__smp_locks_end' WARNING: vmlinux - Section mismatch: reference to .init.text: from .smp_alternatives between '__smp_alt_begin' (at offset 0xc07312f0) and '__smp_locks_end' WARNING: vmlinux - Section mismatch: reference to .init.text: from .smp_alternatives between '__smp_alt_begin' (at offset 0xc0731d98) and '__smp_locks_end' WARNING: vmlinux - Section mismatch: reference to .init.text: from .smp_alternatives between '__smp_alt_begin' (at offset 0xc0731d9c) and '__smp_locks_end' WARNING: vmlinux - Section mismatch: reference to .init.text: from .smp_alternatives between '__smp_alt_begin' (at offset 0xc0732768) and '__smp_locks_end' WARNING: vmlinux - Section mismatch: reference to .init.text: from .smp_alternatives between '__smp_alt_begin' (at offset 0xc07328f4) and '__smp_locks_end' WARNING: vmlinux - Section mismatch: reference to .init.data: from .exit.text between 'powernowk8_exit' (at offset 0xc07691dc) and 'longrun_exit' WARNING: vmlinux - Section mismatch: reference to .exit.text: from .kdb_exitcall.exit after '__kdb_exitcall_kdbm_task_exit' (at offset 0xc071e3ec) WARNING: vmlinux - Section mismatch: reference to .exit.text: from .smp_alternatives between '__smp_alt_begin' (at offset 0xc0732604) and '__smp_locks_end' WARNING: vmlinux - Section mismatch: reference to .exit.text: from .smp_alternatives between '__smp_alt_begin' (at offset 0xc0732b5c) and '__smp_locks_end' but even after these warnings the modules are still being built , ..... does this have any implications ?, .... i will report back if there is any problem after the modules are built and installed and the kernel image is installed ! Thanks Satish On 8/25/08, jidong xiao wrote: > On Mon, Aug 25, 2008 at 10:07 AM, Satish Eerpini wrote: >> i have fixed up errors concerning the previous ones i have mentioned >> , ... but new errors have appeared , : >> >> CHK include/linux/version.h >> CHK include/linux/utsrelease.h >> CHK include/linux/compile.h >> GEN .version >> CHK include/linux/compile.h >> UPD include/linux/compile.h >> CC init/version.o >> LD init/built-in.o >> LD .tmp_vmlinux1 >> kdb/built-in.o: In function `kdb_inittab': >> /usr/src/redhat/BUILD/kernel-2.6.18/linux-2.6.18.i386/kdb/kdbmain.c:3816: >> undefined reference to `__kdb_initcall_start' >> /usr/src/redhat/BUILD/kernel-2.6.18/linux-2.6.18.i386/kdb/kdbmain.c:3822: >> undefined reference to `__kdb_initcall_end' >> make: *** [.tmp_vmlinux1] Error 1 >> >> i have checked the code which corressponds to the above errors , it is >> something liket this : >> >> /* Any kdb commands that are not in the base code but are required >> * earlier than normal initcall processing. >> */ >> call = & __kdb_initcall_start; >> while (call < & __kdb_initcall_end) { >> (*call)(); >> call++; >> }; >> >> , but i don't understand why it is showing an undefined reference >> error , __kdb_initcall_start and __kdb_initcall_end are defined in >> include/linux/kdbprivate.h as follows : >> >> #ifdef MODULE >> #define kdb_module_init(fn) module_init(fn) >> #define kdb_module_exit(fn) module_exit(fn) >> #else /* !MODULE */ >> extern initcall_t __kdb_initcall_start, __kdb_initcall_end; >> #define kdb_module_init(fn) \ >> static initcall_t __kdb_initcall_##fn __attribute_used__ >> __attribute__ ((__section__ (".kdb_initcall.init"))) = fn; >> #define kdb_module_exit(fn) \ >> static exitcall_t __kdb_exitcall_##fn __attribute_used__ >> __attribute__ ((__section__ (".kdb_exitcall.exit"))) = fn; >> #endif /* MODULE */ >> >> then what does the error signify ? >> > First of all, as you are using Cent OS kernel, perhaps there is some > difference between your source code and mine, maybe kdbprivate.h is > not included correctly. > > Second of all, I think you can remove the lines. > > /* Any kdb commands that are not in the base code but are required > * earlier than normal initcall processing. > */ > call = & __kdb_initcall_start; > while (call < & __kdb_initcall_end) { > (*call)(); > call++; > }; > > They are not existing in the latest kdb patches. > > Regards > Jason >> >> Thanks >> Satish >> >> >> -- >> http://satish.playdrupal.com >> --------------------------- >> Use http://oss.sgi.com/ecartis to modify your settings or to unsubscribe. >> > -- http://satish.playdrupal.com --------------------------- Use http://oss.sgi.com/ecartis to modify your settings or to unsubscribe. From eerpini@gmail.com Mon Aug 25 12:38:39 2008 Received: with ECARTIS (v1.0.0; list kdb); Mon, 25 Aug 2008 12:38:48 -0700 (PDT) Received: from cuda.sgi.com ([192.48.176.15]) by oss.sgi.com (8.12.11.20060308/8.12.11/SuSE Linux 0.7) with ESMTP id m7PJccwf018589 for ; Mon, 25 Aug 2008 12:38:38 -0700 X-ASG-Debug-ID: 1219693199-0b1402d70000-sLlkUa X-Barracuda-URL: http://cuda.sgi.com:80/cgi-bin/mark.cgi Received: from mail-gx0-f21.google.com (localhost [127.0.0.1]) by cuda.sgi.com (Spam Firewall) with ESMTP id 22E371A46908 for ; Mon, 25 Aug 2008 12:39:59 -0700 (PDT) Received: from mail-gx0-f21.google.com (mail-gx0-f21.google.com [209.85.217.21]) by cuda.sgi.com with ESMTP id vZ3iHv0CI4E4u8YC for ; Mon, 25 Aug 2008 12:39:59 -0700 (PDT) Received: by gxk14 with SMTP id 14so2664745gxk.20 for ; Mon, 25 Aug 2008 12:39:59 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:cc:in-reply-to:mime-version:content-type :content-transfer-encoding:content-disposition:references; bh=LBGycM5FVebu+tHFJvKZ3dvm24F5s1g1Z/06GvDQC3E=; b=Ckl6kJvN67d2nR+o0ft4+Zfj4czJ/3e8SrPHq7mEda+Q9TbyCvI5UgCfepVbBYChAu DQWAtQHw2NBAjAJ4SMB768d7eHlfTysubWCROCwynDs4PKb1orPtGuMlRI29nzGSedaq ocMkV9Pcthm74v67xxzjS7m4lXrrf4tbEv9GI= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version :content-type:content-transfer-encoding:content-disposition :references; b=NwyW3uKvcxlEnx5Pp1K2qkJkGf1aQTbzMWbBV0ei6L0tmKrEvdOVHnuYpDsve0MD4x 5z72S3uoOE72T/BVbq3DhaIxNaMdYDj3bU1G/xCK2Z/PwoBpMQn/f1OmkAr1jKQMSld2 bEmlC0mhGgiKbohFTs1g8m27y4K2KYiXakLSU= Received: by 10.150.146.1 with SMTP id t1mr4194714ybd.176.1219693199172; Mon, 25 Aug 2008 12:39:59 -0700 (PDT) Received: by 10.151.147.7 with HTTP; Mon, 25 Aug 2008 12:39:59 -0700 (PDT) Message-ID: <93655eb70808251239q62358502oaeee4c16d8503792@mail.gmail.com> Date: Tue, 26 Aug 2008 01:09:59 +0530 From: "Satish Eerpini" To: "jidong xiao" X-ASG-Orig-Subj: Re: patching kdb to the Centos Kernel : more errors Subject: Re: patching kdb to the Centos Kernel : more errors Cc: kdb@oss.sgi.com, bgnaidu@yahoo.com In-Reply-To: <93655eb70808250705n432ed044ycd9b9a225a11bcb6@mail.gmail.com> MIME-Version: 1.0 Content-type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Content-Disposition: inline References: <93655eb70808241907w7bf40ef1qd08166cccb64d966@mail.gmail.com> <4104961b0808250218u2e1d6f47obfb39f96261467e4@mail.gmail.com> <93655eb70808250705n432ed044ycd9b9a225a11bcb6@mail.gmail.com> X-Barracuda-Connect: mail-gx0-f21.google.com[209.85.217.21] X-Barracuda-Start-Time: 1219693200 X-Barracuda-Bayes: INNOCENT GLOBAL 0.0000 1.0000 -2.0210 X-Barracuda-Virus-Scanned: by cuda.sgi.com at sgi.com X-Barracuda-Spam-Score: -2.02 X-Barracuda-Spam-Status: No, SCORE=-2.02 using per-user scores of TAG_LEVEL=2.0 QUARANTINE_LEVEL=1000.0 KILL_LEVEL=2.1 tests= X-Barracuda-Spam-Report: Code version 3.2, rules version 3.2.1.3702 Rule breakdown below pts rule name description ---- ---------------------- -------------------------------------------------- X-archive-position: 1451 X-ecartis-version: Ecartis v1.0.0 Sender: kdb-bounce@oss.sgi.com Errors-to: kdb-bounce@oss.sgi.com X-original-sender: eerpini@gmail.com Precedence: bulk X-list: kdb i could install the kernel , but the kernel crashes , and enters kdb , ... so that might mean that kdb is functioning well, ... but how do i know whats wrong with the compiled image of the kernel ? On 8/25/08, Satish Eerpini wrote: > yeh i removed that part of the code , .... and now the vmlinux is > created successfully, but in the second stage wheer the modules are > built , i get the following warnings , : > > Root device is (8, 2) > Boot sector 512 bytes. > Setup is 7282 bytes. > System is 1900 kB > Kernel: arch/i386/boot/bzImage is ready (#8) > Building modules, stage 2. > MODPOST > WARNING: vmlinux - Section mismatch: reference to > .init.data:boot_params from .text between '_text' (at offset > 0xc0400029) and 'startup_32_smp' > WARNING: vmlinux - Section mismatch: reference to > .init.data:boot_params from .text between '_text' (at offset > 0xc0400037) and 'startup_32_smp' > WARNING: vmlinux - Section mismatch: reference to > .init.data:init_pg_tables_end from .text between '_text' (at offset > 0xc0400099) and 'startup_32_smp' > WARNING: vmlinux - Section mismatch: reference to > .init.data:new_cpu_data from .text between 'checkCPUtype' (at offset > 0xc0400126) and 'is486' > WARNING: vmlinux - Section mismatch: reference to > .init.data:new_cpu_data from .text between 'checkCPUtype' (at offset > 0xc0400130) and 'is486' > WARNING: vmlinux - Section mismatch: reference to > .init.data:new_cpu_data from .text between 'checkCPUtype' (at offset > 0xc040014f) and 'is486' > WARNING: vmlinux - Section mismatch: reference to > .init.data:new_cpu_data from .text between 'checkCPUtype' (at offset > 0xc0400160) and 'is486' > WARNING: vmlinux - Section mismatch: reference to > .init.data:new_cpu_data from .text between 'checkCPUtype' (at offset > 0xc0400166) and 'is486' > WARNING: vmlinux - Section mismatch: reference to > .init.data:new_cpu_data from .text between 'checkCPUtype' (at offset > 0xc040016c) and 'is486' > WARNING: vmlinux - Section mismatch: reference to > .init.data:new_cpu_data from .text between 'checkCPUtype' (at offset > 0xc0400172) and 'is486' > WARNING: vmlinux - Section mismatch: reference to > .init.data:new_cpu_data from .text between 'checkCPUtype' (at offset > 0xc0400188) and 'is486' > WARNING: vmlinux - Section mismatch: reference to > .init.data:new_cpu_data from .text between 'checkCPUtype' (at offset > 0xc0400192) and 'is486' > WARNING: vmlinux - Section mismatch: reference to > .init.data:new_cpu_data from .text between 'checkCPUtype' (at offset > 0xc040019b) and 'is486' > WARNING: vmlinux - Section mismatch: reference to > .init.data:new_cpu_data from .text between 'checkCPUtype' (at offset > 0xc04001a1) and 'is486' > WARNING: vmlinux - Section mismatch: reference to > .init.data:new_cpu_data from .text between 'check_x87' (at offset > 0xc0400210) and 'setup_idt' > WARNING: vmlinux - Section mismatch: reference to > .init.data:new_cpu_data from .text between 'check_x87' (at offset > 0xc040022e) and 'setup_idt' > WARNING: vmlinux - Section mismatch: reference to > .init.text:start_kernel from .text between 'is386' (at offset > 0xc040020a) and 'check_x87' > WARNING: vmlinux - Section mismatch: reference to > .init.text:smp_prepare_cpus from .text between 'init' (at offset > 0xc04002e6) and 'try_name' > WARNING: vmlinux - Section mismatch: reference to > .init.text:migration_init from .text between 'init' (at offset > 0xc04002eb) and 'try_name' > WARNING: vmlinux - Section mismatch: reference to > .init.text:spawn_ksoftirqd from .text between 'init' (at offset > 0xc04002f0) and 'try_name' > WARNING: vmlinux - Section mismatch: reference to .init.data: from > .text between 'init' (at offset 0xc04002f6) and 'try_name' > WARNING: vmlinux - Section mismatch: reference to > .init.text:spawn_softlockup_task from .text between 'init' (at offset > 0xc04002fe) and 'try_name' > WARNING: vmlinux - Section mismatch: reference to > .init.text:smp_cpus_done from .text between 'init' (at offset > 0xc0400367) and 'try_name' > WARNING: vmlinux - Section mismatch: reference to > .init.text:sched_init_smp from .text between 'init' (at offset > 0xc04003d2) and 'try_name' > WARNING: vmlinux - Section mismatch: reference to > .init.text:cpuset_init_smp from .text between 'init' (at offset > 0xc04003d7) and 'try_name' > WARNING: vmlinux - Section mismatch: reference to > .init.text:populate_rootfs from .text between 'init' (at offset > 0xc04003dc) and 'try_name' > WARNING: vmlinux - Section mismatch: reference to > .init.text:usermodehelper_init from .text between 'init' (at offset > 0xc04003e6) and 'try_name' > WARNING: vmlinux - Section mismatch: reference to > .init.text:driver_init from .text between 'init' (at offset > 0xc04003eb) and 'try_name' > WARNING: vmlinux - Section mismatch: reference to > .init.text:sysctl_init from .text between 'init' (at offset > 0xc04003f0) and 'try_name' > WARNING: vmlinux - Section mismatch: reference to .init.data: from > .text between 'init' (at offset 0xc0400407) and 'try_name' > WARNING: vmlinux - Section mismatch: reference to .init.data: from > .text between 'init' (at offset 0xc0400440) and 'try_name' > WARNING: vmlinux - Section mismatch: reference to > .init.text:prepare_namespace from .text between 'init' (at offset > 0xc04004ee) and 'try_name' > WARNING: vmlinux - Section mismatch: reference to > .init.text:parse_unisys_oem from .text between 'mps_oem_check' (at > offset 0xc04014b5) and 'acpi_madt_oem_check' > WARNING: vmlinux - Section mismatch: reference to > .init.text:find_unisys_acpi_oem_table from .text between > 'acpi_madt_oem_check' (at offset 0xc04014ca) and 'enable_apic_mode' > WARNING: vmlinux - Section mismatch: reference to > .init.text:acpi_get_table_header_early from .text between > 'acpi_madt_oem_check' (at offset 0xc04014e3) and 'enable_apic_mode' > WARNING: vmlinux - Section mismatch: reference to > .init.text:parse_unisys_oem from .text between 'acpi_madt_oem_check' > (at offset 0xc0401521) and 'enable_apic_mode' > WARNING: vmlinux - Section mismatch: reference to > .init.text:setup_unisys from .text between 'acpi_madt_oem_check' (at > offset 0xc040152f) and 'enable_apic_mode' > WARNING: vmlinux - Section mismatch: reference to > .init.text:es7000_sw_apic from .text between 'enable_apic_mode' (at > offset 0xc040153b) and 'get_apic_id' > WARNING: vmlinux - Section mismatch: reference to > .init.text:efi_set_rtc_mmss from .text between 'sync_cmos_clock' (at > offset 0xc0407360) and 'get_cmos_time' > WARNING: vmlinux - Section mismatch: reference to > .init.text:efi_get_time from .text between 'get_cmos_time' (at offset > 0xc0407534) and 'timer_resume' > WARNING: vmlinux - Section mismatch: reference to > .init.text:noirqdebug_setup from .text between > 'quirk_intel_irqbalance' (at offset 0xc0409326) and 'i8237A_suspend' > WARNING: vmlinux - Section mismatch: reference to > .init.text:__alloc_bootmem from .text between 'cpu_init' (at offset > 0xc040a313) and 'generic_identify' > WARNING: vmlinux - Section mismatch: reference to > .init.text:sysenter_setup from .text between 'identify_cpu' (at offset > 0xc040a8ee) and 'c_start' > WARNING: vmlinux - Section mismatch: reference to > .init.text:mtrr_bp_init from .text between 'identify_cpu' (at offset > 0xc040a901) and 'c_start' > WARNING: vmlinux - Section mismatch: reference to .init.text: from > .text between 'cyrix_identify' (at offset 0xc040ac66) and > 'centaur_size_cache' > WARNING: vmlinux - Section mismatch: reference to .init.data: from > .text between 'write_new_vid' (at offset 0xc040e61b) and > 'decrease_vid_code_by_step' > WARNING: vmlinux - Section mismatch: reference to .init.data: from > .text between 'write_new_fid' (at offset 0xc040e795) and > 'powernowk8_target' > WARNING: vmlinux - Section mismatch: reference to .init.data: from > .text between 'powernowk8_target' (at offset 0xc040e9b1) and > 'powernowk8_verify' > WARNING: vmlinux - Section mismatch: reference to .init.data: from > .text between 'powernowk8_target' (at offset 0xc040eb47) and > 'powernowk8_verify' > WARNING: vmlinux - Section mismatch: reference to .init.data: from > .text between 'powernowk8_target' (at offset 0xc040ec00) and > 'powernowk8_verify' > WARNING: vmlinux - Section mismatch: reference to .init.data: from > .text between 'powernowk8_target' (at offset 0xc040ec67) and > 'powernowk8_verify' > WARNING: vmlinux - Section mismatch: reference to .init.data: from > .text between 'powernowk8_target' (at offset 0xc040edfb) and > 'powernowk8_verify' > WARNING: vmlinux - Section mismatch: reference to .init.data: from > .text between 'powernowk8_target' (at offset 0xc040f038) and > 'powernowk8_verify' > WARNING: vmlinux - Section mismatch: reference to .init.data: from > .text between 'powernowk8_init' (at offset 0xc040f1a3) and > 'powernowk8_cpu_init' > WARNING: vmlinux - Section mismatch: reference to .init.data: from > .text between 'powernowk8_cpu_init' (at offset 0xc040faee) and > 'longrun_set_policy' > WARNING: vmlinux - Section mismatch: reference to .init.data: from > .text between 'powernowk8_cpu_init' (at offset 0xc040fc63) and > 'longrun_set_policy' > WARNING: vmlinux - Section mismatch: reference to .init.data: from > .text between 'start_secondary' (at offset 0xc041673d) and '__cpu_die' > WARNING: vmlinux - Section mismatch: reference to .init.data: from > .text between 'start_secondary' (at offset 0xc0416748) and '__cpu_die' > WARNING: vmlinux - Section mismatch: reference to .init.data: from > .text between 'start_secondary' (at offset 0xc0416754) and '__cpu_die' > WARNING: vmlinux - Section mismatch: reference to .init.data: from > .text between 'start_secondary' (at offset 0xc0416763) and '__cpu_die' > WARNING: vmlinux - Section mismatch: reference to .init.data: from > .text between 'start_secondary' (at offset 0xc0416795) and '__cpu_die' > WARNING: vmlinux - Section mismatch: reference to .init.data: from > .text between 'start_secondary' (at offset 0xc04167a4) and '__cpu_die' > WARNING: vmlinux - Section mismatch: reference to .init.data: from > .text between 'MP_processor_info' (at offset 0xc0416e19) and > 'mp_register_lapic' > WARNING: vmlinux - Section mismatch: reference to .init.data:maxcpus > from .text between 'MP_processor_info' (at offset 0xc0416ea0) and > 'mp_register_lapic' > WARNING: vmlinux - Section mismatch: reference to > .init.text:__init_begin from .text between 'free_initmem' (at offset > 0xc041af64) and 'mark_rodata_ro' > WARNING: vmlinux - Section mismatch: reference to > .init.text:_sinittext from .text between 'core_kernel_text' (at offset > 0xc0433ed2) and 'kernel_text_address' > WARNING: vmlinux - Section mismatch: reference to > .init.text:_einittext from .text between 'core_kernel_text' (at offset > 0xc0433edc) and 'kernel_text_address' > WARNING: vmlinux - Section mismatch: reference to > .init.text:_sinittext from .text between 'kernel_text_address' (at > offset 0xc0433ef3) and '__kernel_text_address' > WARNING: vmlinux - Section mismatch: reference to > .init.text:_einittext from .text between 'kernel_text_address' (at > offset 0xc0433efa) and '__kernel_text_address' > WARNING: vmlinux - Section mismatch: reference to > .init.text:_sinittext from .text between '__kernel_text_address' (at > offset 0xc0433f23) and 'search_exception_tables' > WARNING: vmlinux - Section mismatch: reference to > .init.text:_einittext from .text between '__kernel_text_address' (at > offset 0xc0433f2a) and 'search_exception_tables' > WARNING: vmlinux - Section mismatch: reference to > .init.text:_sinittext from .text between 'kallsyms_lookup' (at offset > 0xc043f550) and '__print_symbol' > WARNING: vmlinux - Section mismatch: reference to > .init.text:_einittext from .text between 'kallsyms_lookup' (at offset > 0xc043f557) and '__print_symbol' > WARNING: vmlinux - Section mismatch: reference to > .init.data:initkmem_list3 from .text between 'kmem_cache_create' (at > offset 0xc046a1ee) and 'xip_truncate_page' > WARNING: vmlinux - Section mismatch: reference to > .init.data:initkmem_list3 from .text between 'kmem_cache_create' (at > offset 0xc046a200) and 'xip_truncate_page' > WARNING: vmlinux - Section mismatch: reference to > .init.data:initkmem_list3 from .text between 'kmem_cache_create' (at > offset 0xc046a254) and 'xip_truncate_page' > WARNING: vmlinux - Section mismatch: reference to > .init.data:initkmem_list3 from .text between 'kmem_cache_create' (at > offset 0xc046a266) and 'xip_truncate_page' > WARNING: vmlinux - Section mismatch: reference to > .init.text:__alloc_bootmem from .text between 'vgacon_startup' (at > offset 0xc0500142) and 'fbcon_update_softback' > WARNING: vmlinux - Section mismatch: reference to > .init.data:logo_linux_clut224 from .text between 'fb_find_logo' (at > offset 0xc0508ba8) and 'acpi_table_print_madt_entry' > WARNING: vmlinux - Section mismatch: reference to > .init.text:uart_parse_options from .text between > 'serial8250_console_setup' (at offset 0xc054cb2a) and > 'serial8250_console_write' > WARNING: vmlinux - Section mismatch: reference to > .init.text:uart_set_options from .text between > 'serial8250_console_setup' (at offset 0xc054cb4d) and > 'serial8250_console_write' > WARNING: vmlinux - Section mismatch: reference to > .init.data:acpi_noirq from .text between 'pcibios_penalize_isa_irq' > (at offset 0xc05a85aa) and 'pci_read' > WARNING: vmlinux - Section mismatch: reference to > .init.data:acpi_noirq from .text between 'pcibios_setup' (at offset > 0xc05a88d5) and 'pcibios_scan_root' > WARNING: vmlinux - Section mismatch: reference to .init.text: from > .pci_fixup between > '__pci_fixup_PCI_VENDOR_ID_INTELPCI_DEVICE_ID_INTEL_82454NXquirk_disable_pxb' > (at offset 0xc066e280) and > '__pci_fixup_PCI_VENDOR_ID_CYRIXPCI_DEVICE_ID_CYRIX_PCI_MASTERquirk_mediagx_master' > WARNING: vmlinux - Section mismatch: reference to .init.text: from > .pci_fixup between > '__pci_fixup_PCI_VENDOR_ID_CYRIXPCI_DEVICE_ID_CYRIX_PCI_MASTERquirk_mediagx_master' > (at offset 0xc066e288) and > '__pci_fixup_PCI_VENDOR_ID_AMDPCI_DEVICE_ID_AMD_FE_GATE_700Cquirk_amd_ordering' > WARNING: vmlinux - Section mismatch: reference to .init.text: from > .pci_fixup between > '__pci_fixup_PCI_VENDOR_ID_SERVERWORKSPCI_DEVICE_ID_SERVERWORKS_GCNB_LEquirk_svw_msi' > (at offset 0xc066e2a0) and > '__pci_fixup_PCI_VENDOR_ID_AMDPCI_DEVICE_ID_AMD_8131_BRIDGEquirk_amd_8131_ioapic' > WARNING: vmlinux - Section mismatch: reference to .init.text: from > .pci_fixup between > '__pci_fixup_PCI_VENDOR_ID_AMDPCI_DEVICE_ID_AMD_8131_BRIDGEquirk_amd_8131_ioapic' > (at offset 0xc066e2a8) and > '__pci_fixup_PCI_VENDOR_ID_SIPCI_ANY_IDquirk_ioapic_rmw' > WARNING: vmlinux - Section mismatch: reference to .init.text: from > .pci_fixup between > '__pci_fixup_PCI_VENDOR_ID_SIPCI_ANY_IDquirk_ioapic_rmw' (at offset > 0xc066e2b0) and > '__pci_fixup_PCI_VENDOR_ID_AMDPCI_DEVICE_ID_AMD_VIPER_7410quirk_amd_ioapic' > WARNING: vmlinux - Section mismatch: reference to .init.text: from > .pci_fixup between > '__pci_fixup_PCI_VENDOR_ID_ALPCI_DEVICE_ID_AL_M1651quirk_alimagik' (at > offset 0xc066e308) and > '__pci_fixup_PCI_VENDOR_ID_ALPCI_DEVICE_ID_AL_M1647quirk_alimagik' > WARNING: vmlinux - Section mismatch: reference to .init.text: from > .pci_fixup between > '__pci_fixup_PCI_VENDOR_ID_ALPCI_DEVICE_ID_AL_M1647quirk_alimagik' (at > offset 0xc066e310) and > '__pci_fixup_PCI_VENDOR_ID_VIAPCI_DEVICE_ID_VIA_82C576quirk_vsfx' > WARNING: vmlinux - Section mismatch: reference to .init.text: from > .pci_fixup between > '__pci_fixup_PCI_VENDOR_ID_INTELPCI_DEVICE_ID_INTEL_EESSCquirk_alder_ioapic' > (at offset 0xc066df88) and > '__pci_fixup_PCI_VENDOR_ID_ATIPCI_DEVICE_ID_ATI_IXP600_SATAquirk_sb600_sata' > WARNING: vmlinux - Section mismatch: reference to .init.text: from > .pci_fixup between > '__pci_fixup_PCI_VENDOR_ID_SIPCI_DEVICE_ID_SI_LPCquirk_sis_96x_smbus' > (at offset 0xc066df98) and > '__pci_fixup_PCI_VENDOR_ID_SIPCI_DEVICE_ID_SI_963quirk_sis_96x_smbus' > WARNING: vmlinux - Section mismatch: reference to .init.text: from > .pci_fixup between > '__pci_fixup_PCI_VENDOR_ID_SIPCI_DEVICE_ID_SI_963quirk_sis_96x_smbus' > (at offset 0xc066dfa0) and > '__pci_fixup_PCI_VENDOR_ID_SIPCI_DEVICE_ID_SI_962quirk_sis_96x_smbus' > WARNING: vmlinux - Section mismatch: reference to .init.text: from > .pci_fixup between > '__pci_fixup_PCI_VENDOR_ID_SIPCI_DEVICE_ID_SI_962quirk_sis_96x_smbus' > (at offset 0xc066dfa8) and > '__pci_fixup_PCI_VENDOR_ID_SIPCI_DEVICE_ID_SI_961quirk_sis_96x_smbus' > WARNING: vmlinux - Section mismatch: reference to .init.text: from > .pci_fixup between > '__pci_fixup_PCI_VENDOR_ID_SIPCI_DEVICE_ID_SI_961quirk_sis_96x_smbus' > (at offset 0xc066dfb0) and > '__pci_fixup_PCI_VENDOR_ID_VIAPCI_DEVICE_ID_VIA_8237asus_hides_ac97_lpc' > WARNING: vmlinux - Section mismatch: reference to .init.text: from > .pci_fixup between > '__pci_fixup_PCI_VENDOR_ID_VIAPCI_DEVICE_ID_VIA_8237asus_hides_ac97_lpc' > (at offset 0xc066dfb8) and > '__pci_fixup_PCI_VENDOR_ID_SIPCI_DEVICE_ID_SI_503quirk_sis_503' > WARNING: vmlinux - Section mismatch: reference to .init.text: from > .pci_fixup between > '__pci_fixup_PCI_VENDOR_ID_SIPCI_DEVICE_ID_SI_503quirk_sis_503' (at > offset 0xc066dfc0) and > '__pci_fixup_PCI_VENDOR_ID_SIPCI_DEVICE_ID_SI_735quirk_sis_96x_compatible' > WARNING: vmlinux - Section mismatch: reference to .init.text: from > .pci_fixup between > '__pci_fixup_PCI_VENDOR_ID_SIPCI_DEVICE_ID_SI_735quirk_sis_96x_compatible' > (at offset 0xc066dfc8) and > '__pci_fixup_PCI_VENDOR_ID_SIPCI_DEVICE_ID_SI_651quirk_sis_96x_compatible' > WARNING: vmlinux - Section mismatch: reference to .init.text: from > .pci_fixup between > '__pci_fixup_PCI_VENDOR_ID_SIPCI_DEVICE_ID_SI_651quirk_sis_96x_compatible' > (at offset 0xc066dfd0) and > '__pci_fixup_PCI_VENDOR_ID_SIPCI_DEVICE_ID_SI_650quirk_sis_96x_compatible' > WARNING: vmlinux - Section mismatch: reference to .init.text: from > .pci_fixup between > '__pci_fixup_PCI_VENDOR_ID_SIPCI_DEVICE_ID_SI_650quirk_sis_96x_compatible' > (at offset 0xc066dfd8) and > '__pci_fixup_PCI_VENDOR_ID_SIPCI_DEVICE_ID_SI_648quirk_sis_96x_compatible' > WARNING: vmlinux - Section mismatch: reference to .init.text: from > .pci_fixup between > '__pci_fixup_PCI_VENDOR_ID_SIPCI_DEVICE_ID_SI_648quirk_sis_96x_compatible' > (at offset 0xc066dfe0) and > '__pci_fixup_PCI_VENDOR_ID_SIPCI_DEVICE_ID_SI_646quirk_sis_96x_compatible' > WARNING: vmlinux - Section mismatch: reference to .init.text: from > .pci_fixup between > '__pci_fixup_PCI_VENDOR_ID_SIPCI_DEVICE_ID_SI_646quirk_sis_96x_compatible' > (at offset 0xc066dfe8) and > '__pci_fixup_PCI_VENDOR_ID_SIPCI_DEVICE_ID_SI_645quirk_sis_96x_compatible' > WARNING: vmlinux - Section mismatch: reference to .init.text: from > .pci_fixup between > '__pci_fixup_PCI_VENDOR_ID_SIPCI_DEVICE_ID_SI_645quirk_sis_96x_compatible' > (at offset 0xc066dff0) and > '__pci_fixup_PCI_VENDOR_ID_VIAPCI_DEVICE_ID_VIA_8237k8t_sound_hostbridge' > WARNING: vmlinux - Section mismatch: reference to .init.text: from > .pci_fixup between > '__pci_fixup_PCI_VENDOR_ID_VIAPCI_DEVICE_ID_VIA_8237k8t_sound_hostbridge' > (at offset 0xc066dff8) and > '__pci_fixup_PCI_VENDOR_ID_INTELPCI_DEVICE_ID_INTEL_82375quirk_eisa_bridge' > WARNING: vmlinux - Section mismatch: reference to .init.text: from > .pci_fixup between > '__pci_fixup_PCI_VENDOR_ID_INTELPCI_DEVICE_ID_INTEL_82375quirk_eisa_bridge' > (at offset 0xc066e000) and > '__pci_fixup_PCI_VENDOR_ID_INTELPCI_DEVICE_ID_INTEL_82801CA_10quirk_ide_samemode' > WARNING: vmlinux - Section mismatch: reference to .init.text: from > .pci_fixup between > '__pci_fixup_PCI_VENDOR_ID_INTELPCI_DEVICE_ID_INTEL_82801CA_10quirk_ide_samemode' > (at offset 0xc066e008) and > '__pci_fixup_PCI_VENDOR_ID_SERVERWORKSPCI_DEVICE_ID_SERVERWORKS_CSB5IDEquirk_svwks_csb5ide' > WARNING: vmlinux - Section mismatch: reference to .init.text: from > .pci_fixup between > '__pci_fixup_PCI_VENDOR_ID_NVIDIAPCI_DEVICE_ID_NVIDIA_NFORCE2pci_fixup_nforce2' > (at offset 0xc066e108) and > '__pci_fixup_PCI_VENDOR_ID_INTELPCI_ANY_IDpci_fixup_transparent_bridge' > WARNING: vmlinux - Section mismatch: reference to .init.text: from > .data between 'apic_summit' (at offset 0xc0687c44) and 'apic_bigsmp' > WARNING: vmlinux - Section mismatch: reference to .init.text: from > .data between 'apic_bigsmp' (at offset 0xc0687cd0) and 'cpu.4241' > WARNING: vmlinux - Section mismatch: reference to .init.text: from > .data between 'apic_es7000' (at offset 0xc0687d60) and 'apic_default' > WARNING: vmlinux - Section mismatch: reference to .init.text: from > .data between 'apic_default' (at offset 0xc0687dec) and 'interrupt' > WARNING: vmlinux - Section mismatch: reference to .init.text: from > .smp_alternatives between '__smp_alt_begin' (at offset 0xc0730000) and > '__smp_locks_end' > WARNING: vmlinux - Section mismatch: reference to .init.text: from > .smp_alternatives between '__smp_alt_begin' (at offset 0xc0730004) and > '__smp_locks_end' > WARNING: vmlinux - Section mismatch: reference to .init.text: from > .smp_alternatives between '__smp_alt_begin' (at offset 0xc0730008) and > '__smp_locks_end' > WARNING: vmlinux - Section mismatch: reference to .init.text: from > .smp_alternatives between '__smp_alt_begin' (at offset 0xc07300bc) and > '__smp_locks_end' > WARNING: vmlinux - Section mismatch: reference to .init.text: from > .smp_alternatives between '__smp_alt_begin' (at offset 0xc07300c0) and > '__smp_locks_end' > WARNING: vmlinux - Section mismatch: reference to .init.text: from > .smp_alternatives between '__smp_alt_begin' (at offset 0xc07300d8) and > '__smp_locks_end' > WARNING: vmlinux - Section mismatch: reference to .init.text: from > .smp_alternatives between '__smp_alt_begin' (at offset 0xc07300dc) and > '__smp_locks_end' > WARNING: vmlinux - Section mismatch: reference to .init.text: from > .smp_alternatives between '__smp_alt_begin' (at offset 0xc073010c) and > '__smp_locks_end' > WARNING: vmlinux - Section mismatch: reference to .init.text: from > .smp_alternatives between '__smp_alt_begin' (at offset 0xc0730110) and > '__smp_locks_end' > WARNING: vmlinux - Section mismatch: reference to .init.text: from > .smp_alternatives between '__smp_alt_begin' (at offset 0xc0730114) and > '__smp_locks_end' > WARNING: vmlinux - Section mismatch: reference to .init.text: from > .smp_alternatives between '__smp_alt_begin' (at offset 0xc0730118) and > '__smp_locks_end' > WARNING: vmlinux - Section mismatch: reference to .init.text: from > .smp_alternatives between '__smp_alt_begin' (at offset 0xc073011c) and > '__smp_locks_end' > WARNING: vmlinux - Section mismatch: reference to .init.text: from > .smp_alternatives between '__smp_alt_begin' (at offset 0xc0730120) and > '__smp_locks_end' > WARNING: vmlinux - Section mismatch: reference to .init.text: from > .smp_alternatives between '__smp_alt_begin' (at offset 0xc0730124) and > '__smp_locks_end' > WARNING: vmlinux - Section mismatch: reference to .init.text: from > .smp_alternatives between '__smp_alt_begin' (at offset 0xc0730128) and > '__smp_locks_end' > WARNING: vmlinux - Section mismatch: reference to .init.text: from > .smp_alternatives between '__smp_alt_begin' (at offset 0xc073012c) and > '__smp_locks_end' > WARNING: vmlinux - Section mismatch: reference to .init.text: from > .smp_alternatives between '__smp_alt_begin' (at offset 0xc0730130) and > '__smp_locks_end' > WARNING: vmlinux - Section mismatch: reference to .init.text: from > .smp_alternatives between '__smp_alt_begin' (at offset 0xc0730134) and > '__smp_locks_end' > WARNING: vmlinux - Section mismatch: reference to .init.text: from > .smp_alternatives between '__smp_alt_begin' (at offset 0xc0730138) and > '__smp_locks_end' > WARNING: vmlinux - Section mismatch: reference to .init.text: from > .smp_alternatives between '__smp_alt_begin' (at offset 0xc073013c) and > '__smp_locks_end' > WARNING: vmlinux - Section mismatch: reference to .init.text: from > .smp_alternatives between '__smp_alt_begin' (at offset 0xc0730140) and > '__smp_locks_end' > WARNING: vmlinux - Section mismatch: reference to .init.text: from > .smp_alternatives between '__smp_alt_begin' (at offset 0xc0730144) and > '__smp_locks_end' > WARNING: vmlinux - Section mismatch: reference to .init.text: from > .smp_alternatives between '__smp_alt_begin' (at offset 0xc0730148) and > '__smp_locks_end' > WARNING: vmlinux - Section mismatch: reference to .init.text: from > .smp_alternatives between '__smp_alt_begin' (at offset 0xc073014c) and > '__smp_locks_end' > WARNING: vmlinux - Section mismatch: reference to .init.text: from > .smp_alternatives between '__smp_alt_begin' (at offset 0xc0730150) and > '__smp_locks_end' > WARNING: vmlinux - Section mismatch: reference to .init.text: from > .smp_alternatives between '__smp_alt_begin' (at offset 0xc0730154) and > '__smp_locks_end' > WARNING: vmlinux - Section mismatch: reference to .init.text: from > .smp_alternatives between '__smp_alt_begin' (at offset 0xc0730158) and > '__smp_locks_end' > WARNING: vmlinux - Section mismatch: reference to .init.text: from > .smp_alternatives between '__smp_alt_begin' (at offset 0xc0730180) and > '__smp_locks_end' > WARNING: vmlinux - Section mismatch: reference to .init.text: from > .smp_alternatives between '__smp_alt_begin' (at offset 0xc0730248) and > '__smp_locks_end' > WARNING: vmlinux - Section mismatch: reference to .init.text: from > .smp_alternatives between '__smp_alt_begin' (at offset 0xc073024c) and > '__smp_locks_end' > WARNING: vmlinux - Section mismatch: reference to .init.text: from > .smp_alternatives between '__smp_alt_begin' (at offset 0xc0730250) and > '__smp_locks_end' > WARNING: vmlinux - Section mismatch: reference to .init.text: from > .smp_alternatives between '__smp_alt_begin' (at offset 0xc0730254) and > '__smp_locks_end' > WARNING: vmlinux - Section mismatch: reference to .init.text: from > .smp_alternatives between '__smp_alt_begin' (at offset 0xc0730258) and > '__smp_locks_end' > WARNING: vmlinux - Section mismatch: reference to .init.text: from > .smp_alternatives between '__smp_alt_begin' (at offset 0xc073025c) and > '__smp_locks_end' > WARNING: vmlinux - Section mismatch: reference to .init.text: from > .smp_alternatives between '__smp_alt_begin' (at offset 0xc0730260) and > '__smp_locks_end' > WARNING: vmlinux - Section mismatch: reference to .init.text: from > .smp_alternatives between '__smp_alt_begin' (at offset 0xc0730264) and > '__smp_locks_end' > WARNING: vmlinux - Section mismatch: reference to .init.text: from > .smp_alternatives between '__smp_alt_begin' (at offset 0xc0730268) and > '__smp_locks_end' > WARNING: vmlinux - Section mismatch: reference to .init.text: from > .smp_alternatives between '__smp_alt_begin' (at offset 0xc073026c) and > '__smp_locks_end' > WARNING: vmlinux - Section mismatch: reference to .init.text: from > .smp_alternatives between '__smp_alt_begin' (at offset 0xc0730270) and > '__smp_locks_end' > WARNING: vmlinux - Section mismatch: reference to .init.text: from > .smp_alternatives between '__smp_alt_begin' (at offset 0xc0730274) and > '__smp_locks_end' > WARNING: vmlinux - Section mismatch: reference to .init.text: from > .smp_alternatives between '__smp_alt_begin' (at offset 0xc0730278) and > '__smp_locks_end' > WARNING: vmlinux - Section mismatch: reference to .init.text: from > .smp_alternatives between '__smp_alt_begin' (at offset 0xc073027c) and > '__smp_locks_end' > WARNING: vmlinux - Section mismatch: reference to .init.text: from > .smp_alternatives between '__smp_alt_begin' (at offset 0xc0730280) and > '__smp_locks_end' > WARNING: vmlinux - Section mismatch: reference to .init.text: from > .smp_alternatives between '__smp_alt_begin' (at offset 0xc0730284) and > '__smp_locks_end' > WARNING: vmlinux - Section mismatch: reference to .init.text: from > .smp_alternatives between '__smp_alt_begin' (at offset 0xc0730288) and > '__smp_locks_end' > WARNING: vmlinux - Section mismatch: reference to .init.text: from > .smp_alternatives between '__smp_alt_begin' (at offset 0xc073028c) and > '__smp_locks_end' > WARNING: vmlinux - Section mismatch: reference to .init.text: from > .smp_alternatives between '__smp_alt_begin' (at offset 0xc0730290) and > '__smp_locks_end' > WARNING: vmlinux - Section mismatch: reference to .init.text: from > .smp_alternatives between '__smp_alt_begin' (at offset 0xc0730294) and > '__smp_locks_end' > WARNING: vmlinux - Section mismatch: reference to .init.text: from > .smp_alternatives between '__smp_alt_begin' (at offset 0xc0730298) and > '__smp_locks_end' > WARNING: vmlinux - Section mismatch: reference to .init.text: from > .smp_alternatives between '__smp_alt_begin' (at offset 0xc073029c) and > '__smp_locks_end' > WARNING: vmlinux - Section mismatch: reference to .init.text: from > .smp_alternatives between '__smp_alt_begin' (at offset 0xc07302a0) and > '__smp_locks_end' > WARNING: vmlinux - Section mismatch: reference to .init.text: from > .smp_alternatives between '__smp_alt_begin' (at offset 0xc07302a4) and > '__smp_locks_end' > WARNING: vmlinux - Section mismatch: reference to .init.text: from > .smp_alternatives between '__smp_alt_begin' (at offset 0xc07302a8) and > '__smp_locks_end' > WARNING: vmlinux - Section mismatch: reference to .init.text: from > .smp_alternatives between '__smp_alt_begin' (at offset 0xc07302ac) and > '__smp_locks_end' > WARNING: vmlinux - Section mismatch: reference to .init.text: from > .smp_alternatives between '__smp_alt_begin' (at offset 0xc07302b0) and > '__smp_locks_end' > WARNING: vmlinux - Section mismatch: reference to .init.text: from > .smp_alternatives between '__smp_alt_begin' (at offset 0xc07302d0) and > '__smp_locks_end' > WARNING: vmlinux - Section mismatch: reference to .init.text: from > .smp_alternatives between '__smp_alt_begin' (at offset 0xc07302d4) and > '__smp_locks_end' > WARNING: vmlinux - Section mismatch: reference to .init.text: from > .smp_alternatives between '__smp_alt_begin' (at offset 0xc07302d8) and > '__smp_locks_end' > WARNING: vmlinux - Section mismatch: reference to .init.text: from > .smp_alternatives between '__smp_alt_begin' (at offset 0xc07302dc) and > '__smp_locks_end' > WARNING: vmlinux - Section mismatch: reference to .init.text: from > .smp_alternatives between '__smp_alt_begin' (at offset 0xc07302e4) and > '__smp_locks_end' > WARNING: vmlinux - Section mismatch: reference to .init.text: from > .smp_alternatives between '__smp_alt_begin' (at offset 0xc07302f8) and > '__smp_locks_end' > WARNING: vmlinux - Section mismatch: reference to .init.text: from > .smp_alternatives between '__smp_alt_begin' (at offset 0xc07302fc) and > '__smp_locks_end' > WARNING: vmlinux - Section mismatch: reference to .init.text: from > .smp_alternatives between '__smp_alt_begin' (at offset 0xc0730318) and > '__smp_locks_end' > WARNING: vmlinux - Section mismatch: reference to .init.text: from > .smp_alternatives between '__smp_alt_begin' (at offset 0xc0730330) and > '__smp_locks_end' > WARNING: vmlinux - Section mismatch: reference to .init.text: from > .smp_alternatives between '__smp_alt_begin' (at offset 0xc07306cc) and > '__smp_locks_end' > WARNING: vmlinux - Section mismatch: reference to .init.text: from > .smp_alternatives between '__smp_alt_begin' (at offset 0xc07306d0) and > '__smp_locks_end' > WARNING: vmlinux - Section mismatch: reference to .init.text: from > .smp_alternatives between '__smp_alt_begin' (at offset 0xc0730ab4) and > '__smp_locks_end' > WARNING: vmlinux - Section mismatch: reference to .init.text: from > .smp_alternatives between '__smp_alt_begin' (at offset 0xc0730ab8) and > '__smp_locks_end' > WARNING: vmlinux - Section mismatch: reference to .init.text: from > .smp_alternatives between '__smp_alt_begin' (at offset 0xc0730abc) and > '__smp_locks_end' > WARNING: vmlinux - Section mismatch: reference to .init.text: from > .smp_alternatives between '__smp_alt_begin' (at offset 0xc0730b58) and > '__smp_locks_end' > WARNING: vmlinux - Section mismatch: reference to .init.text: from > .smp_alternatives between '__smp_alt_begin' (at offset 0xc07312ec) and > '__smp_locks_end' > WARNING: vmlinux - Section mismatch: reference to .init.text: from > .smp_alternatives between '__smp_alt_begin' (at offset 0xc07312f0) and > '__smp_locks_end' > WARNING: vmlinux - Section mismatch: reference to .init.text: from > .smp_alternatives between '__smp_alt_begin' (at offset 0xc0731d98) and > '__smp_locks_end' > WARNING: vmlinux - Section mismatch: reference to .init.text: from > .smp_alternatives between '__smp_alt_begin' (at offset 0xc0731d9c) and > '__smp_locks_end' > WARNING: vmlinux - Section mismatch: reference to .init.text: from > .smp_alternatives between '__smp_alt_begin' (at offset 0xc0732768) and > '__smp_locks_end' > WARNING: vmlinux - Section mismatch: reference to .init.text: from > .smp_alternatives between '__smp_alt_begin' (at offset 0xc07328f4) and > '__smp_locks_end' > WARNING: vmlinux - Section mismatch: reference to .init.data: from > .exit.text between 'powernowk8_exit' (at offset 0xc07691dc) and > 'longrun_exit' > WARNING: vmlinux - Section mismatch: reference to .exit.text: from > .kdb_exitcall.exit after '__kdb_exitcall_kdbm_task_exit' (at offset > 0xc071e3ec) > WARNING: vmlinux - Section mismatch: reference to .exit.text: from > .smp_alternatives between '__smp_alt_begin' (at offset 0xc0732604) and > '__smp_locks_end' > WARNING: vmlinux - Section mismatch: reference to .exit.text: from > .smp_alternatives between '__smp_alt_begin' (at offset 0xc0732b5c) and > '__smp_locks_end' > > > but even after these warnings the modules are still being built , > ..... does this have any implications ?, .... i will report back if > there is any problem after the modules are built and installed and the > kernel image is installed ! > > > Thanks > Satish > > On 8/25/08, jidong xiao wrote: >> On Mon, Aug 25, 2008 at 10:07 AM, Satish Eerpini >> wrote: >>> i have fixed up errors concerning the previous ones i have mentioned >>> , ... but new errors have appeared , : >>> >>> CHK include/linux/version.h >>> CHK include/linux/utsrelease.h >>> CHK include/linux/compile.h >>> GEN .version >>> CHK include/linux/compile.h >>> UPD include/linux/compile.h >>> CC init/version.o >>> LD init/built-in.o >>> LD .tmp_vmlinux1 >>> kdb/built-in.o: In function `kdb_inittab': >>> /usr/src/redhat/BUILD/kernel-2.6.18/linux-2.6.18.i386/kdb/kdbmain.c:3816: >>> undefined reference to `__kdb_initcall_start' >>> /usr/src/redhat/BUILD/kernel-2.6.18/linux-2.6.18.i386/kdb/kdbmain.c:3822: >>> undefined reference to `__kdb_initcall_end' >>> make: *** [.tmp_vmlinux1] Error 1 >>> >>> i have checked the code which corressponds to the above errors , it is >>> something liket this : >>> >>> /* Any kdb commands that are not in the base code but are required >>> * earlier than normal initcall processing. >>> */ >>> call = & __kdb_initcall_start; >>> while (call < & __kdb_initcall_end) { >>> (*call)(); >>> call++; >>> }; >>> >>> , but i don't understand why it is showing an undefined reference >>> error , __kdb_initcall_start and __kdb_initcall_end are defined in >>> include/linux/kdbprivate.h as follows : >>> >>> #ifdef MODULE >>> #define kdb_module_init(fn) module_init(fn) >>> #define kdb_module_exit(fn) module_exit(fn) >>> #else /* !MODULE */ >>> extern initcall_t __kdb_initcall_start, __kdb_initcall_end; >>> #define kdb_module_init(fn) \ >>> static initcall_t __kdb_initcall_##fn __attribute_used__ >>> __attribute__ ((__section__ (".kdb_initcall.init"))) = fn; >>> #define kdb_module_exit(fn) \ >>> static exitcall_t __kdb_exitcall_##fn __attribute_used__ >>> __attribute__ ((__section__ (".kdb_exitcall.exit"))) = fn; >>> #endif /* MODULE */ >>> >>> then what does the error signify ? >>> >> First of all, as you are using Cent OS kernel, perhaps there is some >> difference between your source code and mine, maybe kdbprivate.h is >> not included correctly. >> >> Second of all, I think you can remove the lines. >> >> /* Any kdb commands that are not in the base code but are required >> * earlier than normal initcall processing. >> */ >> call = & __kdb_initcall_start; >> while (call < & __kdb_initcall_end) { >> (*call)(); >> call++; >> }; >> >> They are not existing in the latest kdb patches. >> >> Regards >> Jason >>> >>> Thanks >>> Satish >>> >>> >>> -- >>> http://satish.playdrupal.com >>> --------------------------- >>> Use http://oss.sgi.com/ecartis to modify your settings or to unsubscribe. >>> >> > > > -- > http://satish.playdrupal.com > -- http://satish.playdrupal.com --------------------------- Use http://oss.sgi.com/ecartis to modify your settings or to unsubscribe.