Windsor Dave L. (AdP/TEF7.1)
2011-Mar-24 15:03 UTC
[CentOS] Kernel Panic on HP/Compaq ProLiant G7
Hello Everyone, I recently installed CentOS 5.5 x86_64 on a brand new ProLiant DL380 G7. I have identical OS software running reock-solid on two other DL380 ProLiant servers, but they are G6 models, not G7. On the G7, the installation went perfectly and the machine ran great for about 2 weeks, when it just seemed to "stop". The system stopped responding on the network, and there was no video on the console (or remote console via iLO). It would not reboot or cold boot through iLO, I actually had to hold the power to turn it off and then hit it again to power up. This happened several times within a few days of each other. Each time, there was no evidence in any logs of a problem - the system just seemed to stop or lock up. We did have a CPU problem light appear on the front, so HP came in and replaced the one 4-core CPU. Since then, it has run as long as two weeks, but still crashes randomly. After the last reboot, I left the console in text mode on vt1, and when it crashed again this morning this was displayed on the screen: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: ffff8100dc435cf0 CR3: 000000008a6ca000 CR4: 00000000000006e0 Process smbd (pid: 18970, threadinfo ffff81001529e000, task ffff81011f5347a0) Stack: ffff81011e4e71c0 0000000000000000 ffff8100cf12a015 ffffffff80009c41 ffff81011e4e71c0 0000000100000000 000000030027ea9d ffff8100cf12a011 ffff81011e4e71c0 ffff81010d9cf300 ffff81011e4e71c0 ffff8101044099c0 Call Trace: [<ffffffff80009c41>] __link_path_walk+0x3a6/0xf5b [<ffffffff8000ea4b>] link_path_walk+0x42/0xb2 [<ffffffff8000cd72>] do_path_lookup+0x275/0x2f1 [<ffffffff80012851>] getname+0x15b/0x1c2 [<ffffffff800239d1>] __user_walk_fd+0x37/0x4c [<ffffffff80028905>] vfs_stat_fd+0x1b/0x4a [<ffffffff80039fa2>] fcntl_setlk+0x243/0x273 [<ffffffff80023703>] sys_newstat+0x19/0x31 [<ffffffff8005d229>] tracesys+0x71/0xe0 [<ffffffff8005d28d>] tracesys+0xd5/0xe0 Code: 00 00 00 00 00 00 00 00 70 4d 4f 9d 00 81 ff ff 98 e4 4b dc RIP [<ffff8100dc435cf0>] RSP <ffff81001529fd18> CR2: ffff8100dc435cf0 <0>Kernel panic - not syncing: Fatal exception This suggests that something happened in a Samba process. I have the Samba3x packages installed since we are beginning to introduce Win7 clients into our environment. Googling "Kernel panic - not syncing: Fatal exception" and "CentOS" produced many hits, but nothing that seemed to exactly match my problem. Since this is the only G7 server I have here right now, I can't reproduce the problem on another machine. The G6s I have running the identical version of CentOS have no problems. I am trying to determine if this is pointing to a hardware or software issue. Some of the Google results suggested using a Centosplus kernel - is this a good idea? The server is a HP DL380 G7 Server with 4 GB RAM (1 DIMM 1333 MHz), one 4-core CPU (2133 MHz), 4 built-in Broadcom "NetExtreme II BCM5709 II Gigabit Ethernet" NICs, and a P410 Smart Array Controller. The P410 and the system BIOS have both been updated to the latest levels to see if that fixes the crashes, with no change. Any idea where I should look next? Thanks for any help anyone can provide! Best Regards, Dave Windsor Robert Bosch LLC Team Leader, MES Database Infrastructure Group (AdP/TEF7.1) 4421 Highway 81 North Anderson, SC 29621 USA www.bosch.us Tel: 1 (864) 260-8459 Fax: 1 (864) 260-8422 Dave.Windsor at us.bosch.com
Windsor Dave L. (AdP/TEF7.1) wrote:> Hello Everyone, > > I recently installed CentOS 5.5 x86_64 on a brand new ProLiant DL380 G7. I have identical OS software running reock-solid on two other DL380 ProLiant servers, but they are G6 models, not G7. On the G7, the installation went perfectly and the machine ran great for about 2 weeks, when it just seemed to "stop". The system stopped responding on the network, and there was no video on the console (or remote console via iLO). It would not reboot or cold boot through iLO, I actually had to hold the power to turn it off and then hit it again to power up. > > This happened several times within a few days of each other. Each time, there was no evidence in any logs of a problem - the system just seemed to stop or lock up. We did have a CPU problem light appear on the front, so HP came in and replaced the one 4-core CPU. Since then, it has run as long as two weeks, but still crashes randomly. After the last reboot, I left the console in text mode on vt1, and when it crashed again this morning this was displayed on the screen: > > CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 > CR2: ffff8100dc435cf0 CR3: 000000008a6ca000 CR4: 00000000000006e0 > Process smbd (pid: 18970, threadinfo ffff81001529e000, task ffff81011f5347a0) > Stack: ffff81011e4e71c0 0000000000000000 ffff8100cf12a015 ffffffff80009c41 > ffff81011e4e71c0 0000000100000000 000000030027ea9d ffff8100cf12a011 > ffff81011e4e71c0 ffff81010d9cf300 ffff81011e4e71c0 ffff8101044099c0 > Call Trace: > [<ffffffff80009c41>] __link_path_walk+0x3a6/0xf5b > [<ffffffff8000ea4b>] link_path_walk+0x42/0xb2 > [<ffffffff8000cd72>] do_path_lookup+0x275/0x2f1 > [<ffffffff80012851>] getname+0x15b/0x1c2 > [<ffffffff800239d1>] __user_walk_fd+0x37/0x4c > [<ffffffff80028905>] vfs_stat_fd+0x1b/0x4a > [<ffffffff80039fa2>] fcntl_setlk+0x243/0x273 > [<ffffffff80023703>] sys_newstat+0x19/0x31 > [<ffffffff8005d229>] tracesys+0x71/0xe0 > [<ffffffff8005d28d>] tracesys+0xd5/0xe0 > > > Code: 00 00 00 00 00 00 00 00 70 4d 4f 9d 00 81 ff ff 98 e4 4b dc > RIP [<ffff8100dc435cf0>] > RSP <ffff81001529fd18> > CR2: ffff8100dc435cf0 > <0>Kernel panic - not syncing: Fatal exception > > > This suggests that something happened in a Samba process. I have the Samba3x packages installed since we are beginning to introduce Win7 clients into our environment. > > Googling "Kernel panic - not syncing: Fatal exception" and "CentOS" produced many hits, but nothing that seemed to exactly match my problem. Since this is the only G7 server I have here right now, I can't reproduce the problem on another machine. The G6s I have running the identical version of CentOS have no problems. > > I am trying to determine if this is pointing to a hardware or software issue. Some of the Google results suggested using a Centosplus kernel - is this a good idea? > > The server is a HP DL380 G7 Server with 4 GB RAM (1 DIMM 1333 MHz), one 4-core CPU (2133 MHz), 4 built-in Broadcom "NetExtreme II BCM5709 II Gigabit Ethernet" NICs, and a P410 Smart Array Controller. The P410 and the system BIOS have both been updated to the latest levels to see if that fixes the crashes, with no change. > > Any idea where I should look next? >Run memtest for 48 hours - also check temperature of system - I have seen errors like these from overheating. HTH> Thanks for any help anyone can provide! > > Best Regards, > > Dave Windsor > > Robert Bosch LLC > Team Leader, MES Database Infrastructure Group (AdP/TEF7.1) > 4421 Highway 81 North > Anderson, SC 29621 USA > www.bosch.us > > Tel: 1 (864) 260-8459 > Fax: 1 (864) 260-8422 > Dave.Windsor at us.bosch.com > > > _______________________________________________ > CentOS mailing list > CentOS at centos.org > http://lists.centos.org/mailman/listinfo/centos >-------------- next part -------------- A non-text attachment was scrubbed... Name: rkampen.vcf Type: text/x-vcard Size: 322 bytes Desc: not available URL: <http://lists.centos.org/pipermail/centos/attachments/20110324/85459b00/attachment-0001.vcf>
Le 24/03/2011 16:03, Windsor Dave L. (AdP/TEF7.1) a ?crit :> Hello Everyone, > > I recently installed CentOS 5.5 x86_64 on a brand new ProLiant DL380 G7. I have identical OS software running reock-solid on two other DL380 ProLiant servers, but they are G6 models, not G7. On the G7, the installation went perfectly and the machine ran great for about 2 weeks, when it just seemed to "stop". The system stopped responding on the network, and there was no video on the console (or remote console via iLO). It would not reboot or cold boot through iLO, I actually had to hold the power to turn it off and then hit it again to power up. > > This happened several times within a few days of each other. Each time, there was no evidence in any logs of a problem - the system just seemed to stop or lock up. We did have a CPU problem light appear on the front, so HP came in and replaced the one 4-core CPU. Since then, it has run as long as two weeks, but still crashes randomly. After the last reboot, I left the console in text mode on vt1, and when it crashed again this morning this was displayed on the screen: > > CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 > CR2: ffff8100dc435cf0 CR3: 000000008a6ca000 CR4: 00000000000006e0 > Process smbd (pid: 18970, threadinfo ffff81001529e000, task ffff81011f5347a0) > Stack: ffff81011e4e71c0 0000000000000000 ffff8100cf12a015 ffffffff80009c41 > ffff81011e4e71c0 0000000100000000 000000030027ea9d ffff8100cf12a011 > ffff81011e4e71c0 ffff81010d9cf300 ffff81011e4e71c0 ffff8101044099c0 > Call Trace: > [<ffffffff80009c41>] __link_path_walk+0x3a6/0xf5b > [<ffffffff8000ea4b>] link_path_walk+0x42/0xb2 > [<ffffffff8000cd72>] do_path_lookup+0x275/0x2f1 > [<ffffffff80012851>] getname+0x15b/0x1c2 > [<ffffffff800239d1>] __user_walk_fd+0x37/0x4c > [<ffffffff80028905>] vfs_stat_fd+0x1b/0x4a > [<ffffffff80039fa2>] fcntl_setlk+0x243/0x273 > [<ffffffff80023703>] sys_newstat+0x19/0x31 > [<ffffffff8005d229>] tracesys+0x71/0xe0 > [<ffffffff8005d28d>] tracesys+0xd5/0xe0 > > > Code: 00 00 00 00 00 00 00 00 70 4d 4f 9d 00 81 ff ff 98 e4 4b dc > RIP [<ffff8100dc435cf0>] > RSP<ffff81001529fd18> > CR2: ffff8100dc435cf0 > <0>Kernel panic - not syncing: Fatal exception > > > This suggests that something happened in a Samba process. I have the Samba3x packages installed since we are beginning to introduce Win7 clients into our environment. > > Googling "Kernel panic - not syncing: Fatal exception" and "CentOS" produced many hits, but nothing that seemed to exactly match my problem. Since this is the only G7 server I have here right now, I can't reproduce the problem on another machine. The G6s I have running the identical version of CentOS have no problems. > > I am trying to determine if this is pointing to a hardware or software issue. Some of the Google results suggested using a Centosplus kernel - is this a good idea? > > The server is a HP DL380 G7 Server with 4 GB RAM (1 DIMM 1333 MHz), one 4-core CPU (2133 MHz), 4 built-in Broadcom "NetExtreme II BCM5709 II Gigabit Ethernet" NICs, and a P410 Smart Array Controller. The P410 and the system BIOS have both been updated to the latest levels to see if that fixes the crashes, with no change. > > Any idea where I should look next? > > Thanks for any help anyone can provide! >The fact that it appears after two weeks or so reminds me of a bug I saw on linux PowerEdge mailing list, //the "blocked for more than 120 seconds" timeout bug. I don't know if your problem is related, but if it is the case you should see the message in your logs. Do you have any high IO load, at least at some moments, on your server ? See : http://lists.us.dell.com/pipermail/linux-poweredge/2011-March/044515.html In this case, using a newer kernel would be indeed it seems a good idea. See if it can help... Alain // -- =========================================================Alain P?an - LPP/CNRS Administrateur Syst?me/R?seau Laboratoire de Physique des Plasmas - UMR 7648 Observatoire de Saint-Maur 4, av de Neptune, Bat. A 94100 Saint-Maur des Foss?s Tel : 01-45-11-42-39 - Fax : 01-48-89-44-33 ========================================================= -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.centos.org/pipermail/centos/attachments/20110324/0cda5c77/attachment-0001.html>
On 3/24/2011 12:37 PM, Alain P?an wrote:> Le 24/03/2011 16:03, Windsor Dave L. (AdP/TEF7.1) a ?crit : >> <snipped> >> Code: 00 00 00 00 00 00 00 00 70 4d 4f 9d 00 81 ff ff 98 e4 4b dc >> RIP [<ffff8100dc435cf0>] >> RSP<ffff81001529fd18> >> CR2: ffff8100dc435cf0 >> <0>Kernel panic - not syncing: Fatal exception >> >> <snipped> >> I am trying to determine if this is pointing to a hardware or software issue. Some of the Google results suggested using a Centosplus kernel - is this a good idea? >> >> The server is a HP DL380 G7 Server with 4 GB RAM (1 DIMM 1333 MHz), one 4-core CPU (2133 MHz), 4 built-in Broadcom "NetExtreme II BCM5709 II Gigabit Ethernet" NICs, and a P410 Smart Array Controller. The P410 and the system BIOS have both been updated to the latest levels to see if that fixes the crashes, with no change. >> >> Any idea where I should look next? >> >> Thanks for any help anyone can provide! >> > > The fact that it appears after two weeks or so reminds me of a bug I > saw on linux PowerEdge mailing list, //the "blocked for more than 120 > seconds" timeout bug. > I don't know if your problem is related, but if it is the case you > should see the message in your logs. > > Do you have any high IO load, at least at some moments, on your server ? > > See : > http://lists.us.dell.com/pipermail/linux-poweredge/2011-March/044515.html > > In this case, using a newer kernel would be indeed it seems a good idea. > > See if it can help... > > Alain > // > -- > =========================================================> Alain P?an - LPP/CNRS > Administrateur Syst?me/R?seau > Laboratoire de Physique des Plasmas - UMR 7648 > Observatoire de Saint-Maur > 4, av de Neptune, Bat. A > 94100 Saint-Maur des Foss?s > Tel : 01-45-11-42-39 - Fax : 01-48-89-44-33 > =========================================================Alain,Today, there are not high I/O loads. This server was intended to replace two older HP-UX servers. I had just begun to migrate the workload to the new server when the crashes began to occur. There are some minor, sporadic I/O loads but nothing that I would think could trigger the bug discussed in your link. However, I haven't measured the workload closely yet, so there could be spikes. Best Regards, *Dave Windsor* Robert Bosch LLC Team Leader, MES Database Infrastructure Group (AdP/TEF7.1) 4421 Highway 81 North Anderson, SC 29621 USA _www.bosch.us _ <http://www.bosch.us> Tel: 1 (864) 260-8459 Fax: 1 (864) 260-8422 _Dave.Windsor at us.bosch.com_ <mailto:Dave.Windsor at us.bosch.com>
Rajagopal Swaminathan
2011-Mar-24 19:02 UTC
[CentOS] Kernel Panic on HP/Compaq ProLiant G7
Greetings, On 3/24/11, Windsor Dave L. (AdP/TEF7.1) <Dave.Windsor at us.bosch.com> wrote:> [<ffffffff80028905>] vfs_stat_fd+0x1b/0x4aMy gut feeling would is that its hardware (i/o channel) . imho Regards, Rajagopal
Dave: on 16:03 Thu 24 Mar, Windsor Dave L. (AdP/TEF7.1) (Dave.Windsor at us.bosch.com) wrote:> Hello Everyone, > > I recently installed CentOS 5.5 x86_64 on a brand new ProLiant DL380 > G7. I have identical OS software running reock-solid on two other > DL380 ProLiant servers, but they are G6 models, not G7. On the G7, > the installation went perfectly and the machine ran great for about 2 > weeks, when it just seemed to "stop". The system stopped responding > on the network, and there was no video on the console (or remote > console via iLO). It would not reboot or cold boot through iLO, I > actually had to hold the power to turn it off and then hit it again to > power up. > > This happened several times within a few days of each other. Each > time, there was no evidence in any logs of a problem - the system just > seemed to stop or lock up. We did have a CPU problem light appear on > the front, so HP came in and replaced the one 4-core CPU. Since then, > it has run as long as two weeks, but still crashes randomly. After > the last reboot, I left the console in text mode on vt1, and when it > crashed again this morning this was displayed on the screen: > > CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 > CR2: ffff8100dc435cf0 CR3: 000000008a6ca000 CR4: 00000000000006e0 > Process smbd (pid: 18970, threadinfo ffff81001529e000, task ffff81011f5347a0) > Stack: ffff81011e4e71c0 0000000000000000 ffff8100cf12a015 ffffffff80009c41 > ffff81011e4e71c0 0000000100000000 000000030027ea9d ffff8100cf12a011 > ffff81011e4e71c0 ffff81010d9cf300 ffff81011e4e71c0 ffff8101044099c0 > Call Trace: > [<ffffffff80009c41>] __link_path_walk+0x3a6/0xf5b > [<ffffffff8000ea4b>] link_path_walk+0x42/0xb2 > [<ffffffff8000cd72>] do_path_lookup+0x275/0x2f1 > [<ffffffff80012851>] getname+0x15b/0x1c2 > [<ffffffff800239d1>] __user_walk_fd+0x37/0x4c > [<ffffffff80028905>] vfs_stat_fd+0x1b/0x4a > [<ffffffff80039fa2>] fcntl_setlk+0x243/0x273 > [<ffffffff80023703>] sys_newstat+0x19/0x31 > [<ffffffff8005d229>] tracesys+0x71/0xe0 > [<ffffffff8005d28d>] tracesys+0xd5/0xe0 > > > Code: 00 00 00 00 00 00 00 00 70 4d 4f 9d 00 81 ff ff 98 e4 4b dc > RIP [<ffff8100dc435cf0>] > RSP <ffff81001529fd18> > CR2: ffff8100dc435cf0 > <0>Kernel panic - not syncing: Fatal exception > > > This suggests that something happened in a Samba process.Correct. If this is regularly happening in Samba, that would point to a problem with your samba config (either on that host, something remotely stuffing bad packets at you, or likley in that case, both, as bad data shouldn't crash the host). If this is happening in different programs over time, then the problem is likely /not/ software, but hardware/firmware. The LKML may be able to help you on your panic; please read their bug posting guidelines /BEFORE/ posting.> I have the Samba3x packages installed since we are beginning to > introduce Win7 clients into our environment.What happens if you take the Win7 clients away?> Googling "Kernel panic - not syncing: Fatal exception" and "CentOS"That is the generic kernel panic message. It's going to be spectacularly unspecific.> produced many hits, but nothing that seemed to exactly match my > problem. Since this is the only G7 server I have here right now, I > can't reproduce the problem on another machine. The G6s I have > running the identical version of CentOS have no problems. > > I am trying to determine if this is pointing to a hardware or software > issue. Some of the Google results suggested using a Centosplus kernel > - is this a good idea?Dell have had numerous issues with recent server editions, it's possible HP are as well: - If you haven't, configure the netconsole kernel module for kernel-enabled network logging of panics. - Call HP and find out what the latest recommended BIOS and firmware upgrades for your system are. C-STATE has been a particular issue with Dell, and its' been disabled entirely in recent BIOS versions. I see below you've updated BIOS. - Scan logs for other messages, particularly panics and/or ECC issues. - If you can stand the downtime, run memtest86+ at least overnight on your RAM. A reboot indicates a failed test. - Otherwise: try running with half your RAM swapped. - Check/reseat all DIMMs, sockets, and cables. Some folks caution against this on the basis of connector wear, but if you've got a problem, this may help resolve it, and I've seen boxes shipped with components poorly or even un-cabled. - Does a similarly equipped system exhibit the same problems?> The server is a HP DL380 G7 Server with 4 GB RAM (1 DIMM 1333 MHz), > one 4-core CPU (2133 MHz), 4 built-in Broadcom "NetExtreme II BCM5709 > II Gigabit Ethernet" NICs, and a P410 Smart Array Controller. The > P410 and the system BIOS have both been updated to the latest levels > to see if that fixes the crashes, with no change.Ugh. Broadcom's gotten better but I prefer Intel NICs. Can't speak to the others. And OK, you've updated BIOS. -- Dr. Ed Morbius, Chief Scientist / | Robot Wrangler / Staff Psychologist | When you seek unlimited power Krell Power Systems Unlimited | Go to Krell!
Windsor Dave L. (AdP/TEF7)
2011-Apr-01 17:44 UTC
[CentOS] Kernel Panic on HP/Compaq ProLiant G7
On 3/24/2011 11:03 AM, Windsor Dave L. (AdP/TEF7.1) wrote:> Hello Everyone, > > I recently installed CentOS 5.5 x86_64 on a brand new ProLiant DL380 G7. I have identical OS software running reock-solid on two other DL380 ProLiant servers, but they are G6 models, not G7. On the G7, the installation went perfectly and the machine ran great for about 2 weeks, when it just seemed to "stop". The system stopped responding on the network, and there was no video on the console (or remote console via iLO). It would not reboot or cold boot through iLO, I actually had to hold the power to turn it off and then hit it again to power up. > > This happened several times within a few days of each other. Each time, there was no evidence in any logs of a problem - the system just seemed to stop or lock up. We did have a CPU problem light appear on the front, so HP came in and replaced the one 4-core CPU. Since then, it has run as long as two weeks, but still crashes randomly. After the last reboot, I left the console in text mode on vt1, and when it crashed again this morning this was displayed on the screen: > > CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 > CR2: ffff8100dc435cf0 CR3: 000000008a6ca000 CR4: 00000000000006e0 > Process smbd (pid: 18970, threadinfo ffff81001529e000, task ffff81011f5347a0)<snipped>> <0>Kernel panic - not syncing: Fatal exceptionOK everyone, here is an update: The server crashed again overnight. This time, the following error messages were on the console: HARDWARE ERROR CPU 3: Machine Check Exception: 4 Bank 5: ba00000000400405 TSC 5172b45d44f0a MISC 80 This is not a software problem! Run through mcelog --ascii to decode and contact your hardware vendor HARDWARE ERROR CPU 7: Machine Check Exception: 4 Bank 5: ba00000000400405 TSC 5172b45d45bba MISC 80 This is not a software problem! Run through mcelog --ascii to decode and contact your hardware vendor HARDWARE ERROR CPU 5: Machine Check Exception: 4 Bank 8: 0000000000000000 TSC 0 This is not a software problem! Run through mcelog --ascii to decode and contact your hardware vendor Kernel panic - not syncing: Uncorrected machine check After reboot, running the first error through mcelog --ascii gives CPU 3: Machine Check Exception: 4 Bank 5: ba00000000400405 HARDWARE ERROR. This is *NOT* a software problem! Please contact your hardware vendor mcelog: Unknown Intel CPU type family 6 model 2c CPU 3 BANK 5 MCG status:MCIP MCi status: Uncorrected error Error enabled MCi_MISC register valid Processor context corrupt MCA: Internal unclassified error: 405 STATUS ba00000000400405 MCGSTATUS 4 The second error gives CPU 7: Machine Check Exception: 4 Bank 5: ba00000000400405 HARDWARE ERROR. This is *NOT* a software problem! Please contact your hardware vendor mcelog: Unknown Intel CPU type family 6 model 2c CPU 7 BANK 5 MCG status:MCIP MCi status: Uncorrected error Error enabled MCi_MISC register valid Processor context corrupt MCA: Internal unclassified error: 405 STATUS ba00000000400405 MCGSTATUS 4 And the third gives CPU 3: Machine Check Exception: 4 Bank 5: ba00000000400405 HARDWARE ERROR. This is *NOT* a software problem! Please contact your hardware vendor mcelog: Unknown Intel CPU type family 6 model 2c CPU 3 BANK 5 MCG status:MCIP MCi status: Uncorrected error Error enabled MCi_MISC register valid Processor context corrupt MCA: Internal unclassified error: 405 STATUS ba00000000400405 MCGSTATUS 4 I have been able to move all workloads onto other servers. As at least two people suggested, I booted from the HP SmartStart CD and ran 100 loops of systems diagnostics and tests, especially for the memory and CPU. No problems were found. I think I will run memtest86 over the weekend. We have placed a hardware support call in to HP. Best Regards, Dave Windsor Robert Bosch LLC Team Leader, MES Database Infrastructure Group (AdP/TEF7.1) 4421 Highway 81 North Anderson, SC 29621 USA www.bosch.us