Closed Bug 711166 (linux64-ix-slave14) Opened 13 years ago Closed 13 years ago

linux64-ix-slave14 problem tracking

Categories

(Infrastructure & Operations Graveyard :: CIDuty, task, P2)

x86
Linux

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: arich, Unassigned)

References

Details

(Whiteboard: [buildduty][buildslave][capacity])

linux65-ix-slave14 is reporting the following errors and should be debugged (try reseating the RAM) and sent back to iX for repairs if it's still non-functional CPU 0: Machine Check Exception 4 Bank 5: 00000000000000 TSC 0
Ram has been reseated and returned to the rack for testing.
This hasn't been acting up again, so I'm going to close this bug and we can open a new one if the issue occurs again.
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → FIXED
This slave is down again. Let's get it fixed.
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Summary: hardware errors on linux64-ix-slave14 → Please repair linux64-ix-slave14
To be yoinked from scl1, then over to matt to handle the repairs.
colo-trip: --- → scl1
I'll be bringing this to mtv today.
This box is now on Matt's desk for repairs.
Assignee: jwatkins → mlarrain
Please give this machine to desktop for repair.
Assignee: mlarrain → hlangi
Component: Server Operations: RelEng → Server Operations: Desktop Issues
QA Contact: zandr → tfairfield
My bad this should go to iX per me. I guess I thought it was a mini at first. My bad.
Assignee: hlangi → mlarrain
Component: Server Operations: Desktop Issues → Server Operations
QA Contact: tfairfield → cshields
This machine has been given to iX systems for repair.
Assignee: mlarrain → jwatkins
Component: Server Operations → Server Operations: RelEng
QA Contact: cshields → zandr
Assignee: jwatkins → mlarrain
Talked to iX today they will be at SCL1 either Wednesday or Thursday to drop off this system.
this machine is back at scl1 and racked. needs to be imaged once dspc is working again.
Status: REOPENED → ASSIGNED
jake is getting DSPC working again and will get this up and running soon.
Assignee: mlarrain → jwatkins
DSPC is working now. I have re-imaged this slave and it is ready to be setup for production.
Assignee: jwatkins → nobody
Component: Server Operations: RelEng → Release Engineering
QA Contact: zandr → release
Component: Release Engineering → Release Engineering: Machine Management
Priority: -- → P3
Whiteboard: [buildduty][buildslave][capacity]
Alias: linux64-ix-slave14
Summary: Please repair linux64-ix-slave14 → linux64-ix-slave14 problem tracking
Depends on: 734195
I was going to try to bring this back up, but it's not pingable and going in through ipmi won't let me power cycle it.
Status: ASSIGNED → NEW
Depends on: 734909
this didn't come back up, so I clicked the "reset" button on IPMI a bunch of times. The machine came back up, but is inaccessible via the network.
The console preview is also showing a bunch of usb device errors. I'm thinking this needs to go back to ix again.
Depends on: 738418
Depends on: 740070
c&p from 738418: >I didn't have any problems accessing the ipmi or the java remote console although >I did find the eth0 mac did not match what was in inventory/dhcp. Inventory has >been updated and is retrieving the correct IP now. I haven't seen any errors on this slave since I worked on it on Mon 3/26. Usb error may have been from plugging and unplugging the usb kb during the reimaging. We will need more evidence of a hardware failure before we send it back to IX. I think maybe we should put this back into production first and see how it does.
Assignee: nobody → coop
Status: NEW → ASSIGNED
OS: Mac OS X → Linux
Priority: P3 → P2
(In reply to Jake Watkins [:dividehex] from comment #17) > I think maybe we should put this back into production first > and see how it does. It's back in production now.
Status: ASSIGNED → RESOLVED
Closed: 13 years ago13 years ago
Resolution: --- → FIXED
Product: mozilla.org → Release Engineering
Assignee: coop → nobody
Product: Release Engineering → Infrastructure & Operations
Product: Infrastructure & Operations → Infrastructure & Operations Graveyard
You need to log in before you can comment on or make changes to this bug.