Welcome to Tesla Motors Club
Discuss Tesla's Model S, Model 3, Model X, Model Y, Cybertruck, Roadster and More.
Register

Tessie won't start

This site may earn commission on affiliate links.
Log just dumps a couple of errors; I think they are the same ones that appear on the screen.

What did you Unix system "messages" file look like? That has the kernel and filesystem related messages. When you untar the logfile its in: ./logs/flash

There's a messages file and a messages.0 file, both are log messages and the one with the 0 is the older archived one. Here's what it looks like inside:

ct 22 17:43:27 kernel: scsi1 : SCSI emulation for USB Mass Storage devices
Oct 22 17:43:27 kernel: usb-storage: device found at 70
Oct 22 17:43:27 kernel: usb-storage: waiting for device to settle before scanning
Oct 22 17:43:32 kernel: Vendor: Kingston Model: DataTraveler 2.0 Rev: PMAP
Oct 22 17:43:32 kernel: Type: Direct-Access ANSI SCSI revision: 04
Oct 22 17:43:34 kernel: SCSI device sda: 15240576 512-byte hdwr sectors (7803 MB)
Oct 22 17:43:34 kernel: sda: assuming Write Enabled
Oct 22 17:43:34 kernel: sda: assuming drive cache: write through
Oct 22 17:43:34 kernel: SCSI device sda: 15240576 512-byte hdwr sectors (7803 MB)
Oct 22 17:43:34 kernel: sda: assuming Write Enabled
Oct 22 17:43:34 kernel: sda: assuming drive cache: write through
Oct 22 17:43:34 kernel: sda: sda1
Oct 22 17:43:34 kernel: Attached scsi removable disk sda at scsi1, channel 0, id 0, lun 0
Oct 22 17:43:34 kernel: usb-storage: device scan complete
 
Below is the content of the messages file (with the a whole whack of 1 input overrun(s) messages deleted at the top. There are also messages.0 through messages.4 files, all containing just the repeating overrun message.

May 4 05:48:36 kernel: ttyS1: 1 input overrun(s)
May 4 05:53:13 kernel: ttyS1: 1 input overrun(s)
May 4 06:00:10 kernel: ttyS1: 1 input overrun(s)
May 4 06:01:01 kernel: ttyS1: 1 input overrun(s)
May 4 06:01:50 kernel: ttyS1: 1 input overrun(s)
May 4 06:02:42 kernel: ttyS1: 1 input overrun(s)
May 4 06:02:50 kernel: ttyS1: 1 input overrun(s)
May 4 06:03:30 kernel: ttyS1: 1 input overrun(s)
May 4 06:07:01 kernel: ttyS1: 1 input overrun(s)
May 4 06:07:52 kernel: ttyS1: 1 input overrun(s)
May 4 06:10:08 kernel: ttyS1: 1 input overrun(s)
May 4 06:11:09 kernel: ttyS1: 1 input overrun(s)
May 4 06:14:50 kernel: ttyS1: 1 input overrun(s)
May 4 06:18:57 kernel: ttyS1: 1 input overrun(s)
May 4 06:28:41 kernel: ttyS1: 1 input overrun(s)
May 4 06:33:38 kernel: ttyS1: 1 input overrun(s)
May 4 06:36:02 kernel: ttyS1: 1 input overrun(s)
May 4 06:45:38 kernel: ttyS1: 1 input overrun(s)
May 4 06:45:51 kernel: oom-killer: gfp_mask=0x4d0
May 4 06:45:51 kernel: DMA per-cpu:
May 4 06:45:51 kernel: cpu 0 hot: low 4, high 12, batch 2
May 4 06:45:51 kernel: cpu 0 cold: low 0, high 4, batch 2
May 4 06:45:51 kernel: Normal per-cpu: empty
May 4 06:45:51 kernel: HighMem per-cpu: empty
May 4 06:45:51 kernel:
May 4 06:45:51 kernel: Free pages: 792kB (0kB HighMem)
May 4 06:45:51 kernel: Active:159 inactive:119 dirty:0 writeback:0 unstable:0 free:198 slab:0 mapped:0 pagetables:0
May 4 06:45:51 kernel: DMA free:792kB min:724kB low:904kB high:1084kB active:636kB inactive:476kB present:32768kB pages_scanned:1349 all_unreclaimable? yes
May 4 06:45:51 kernel: lowmem_reserve[]: 0 0 0
May 4 06:45:51 kernel: Normal free:0kB min:0kB low:0kB high:0kB active:0kB inactive:0kB present:0kB pages_scanned:0 all_unreclaimable? no
May 4 06:45:51 kernel: lowmem_reserve[]: 0 0 0
May 4 06:45:51 kernel: HighMem free:0kB min:128kB low:160kB high:192kB active:0kB inactive:0kB present:0kB pages_scanned:0 all_unreclaimable? no
May 4 06:45:51 kernel: lowmem_reserve[]: 0 0 0
May 4 06:45:52 kernel: DMA: 56*4kB 1*8kB 1*16kB 1*32kB 0*64kB 0*128kB 0*256kB 1*512kB 0*1024kB 0*2048kB 0*4096kB = 792kB
May 4 06:45:52 kernel: Normal: empty
May 4 06:45:52 kernel: HighMem: empty
May 4 06:45:52 kernel: Out of Memory: Killed process 249 (vms).
May 4 06:45:52 kernel: Out of Memory: Killed process 250 (vms).
May 4 06:45:52 kernel: Out of Memory: Killed process 251 (vms).
May 4 06:45:52 kernel: Out of Memory: Killed process 252 (vms).
May 4 06:45:52 kernel: Out of Memory: Killed process 253 (vms).
May 4 06:45:52 kernel: Out of Memory: Killed process 254 (vms).
May 4 06:45:52 kernel: Out of Memory: Killed process 255 (vms).
May 4 06:45:52 kernel: Out of Memory: Killed process 256 (vms).
May 4 06:45:53 kernel: Out of Memory: Killed process 257 (vms).
May 4 06:45:53 kernel: Out of Memory: Killed process 258 (vms).
May 4 06:45:53 kernel: Out of Memory: Killed process 259 (vms).
May 4 06:45:53 kernel: Out of Memory: Killed process 260 (vms).
May 4 06:45:53 kernel: Out of Memory: Killed process 261 (vms).
May 4 06:45:54 kernel: Out of Memory: Killed process 262 (vms).
May 4 06:45:54 kernel: Out of Memory: Killed process 263 (vms).
May 4 06:45:54 kernel: Out of Memory: Killed process 264 (vms).
May 4 06:45:55 kernel: Out of Memory: Killed process 265 (vms).
May 4 06:46:48 syslogd started: BusyBox v1.00 (2011.04.26-01:24+0000)
May 4 06:46:48 init: ^MStarting pid 131, console /dev/console: '/sbin/ifconfig'
May 4 06:46:52 init: ^MStarting pid 135, console /dev/console: '/bin/mv'
May 4 06:46:53 kernel: klogd started: BusyBox v1.00 (2011.04.26-01:24+0000)
May 4 06:46:53 kernel: Linux version 2.6.11.8-2.1.0 ([email protected]) (gcc version 3.4.3) #296 Mon Mar 23 13:50:14 PDT 2009
May 4 06:46:53 kernel: CPU: Philips-LPC2294 [fff00000] (ARMv3)
May 4 06:46:53 kernel: Machine: LPC2294
May 4 06:46:53 kernel: On node 0 totalpages: 8192
May 4 06:46:53 kernel: DMA zone: 8192 pages, LIFO batch:2
May 4 06:46:53 kernel: Normal zone: 0 pages, LIFO batch:1
May 4 06:46:54 kernel: HighMem zone: 0 pages, LIFO batch:1
May 4 06:46:54 kernel: Built 1 zonelists
May 4 06:46:54 kernel: Kernel command line: panic=5 console=can3 initrd=yes
May 4 06:46:54 kernel: PID hash table entries: 256 (order: 8, 4096 bytes)
May 4 06:46:54 kernel: Dentry cache hash table entries: 8192 (order: 3, 32768 bytes)
May 4 06:46:54 kernel: Inode-cache hash table entries: 4096 (order: 2, 16384 bytes)
May 4 06:46:54 kernel: Memory: 32MB = 32MB total
May 4 06:46:54 kernel: Memory: 29888KB available (1273K code, 292K data, 8K init)
May 4 06:46:55 kernel: Calibrating delay loop... 4.23 BogoMIPS (lpj=21184)
May 4 06:46:56 kernel: Mount-cache hash table entries: 512 (order: 0, 4096 bytes)
May 4 06:46:56 kernel: checking if image is initramfs... it is
May 4 06:46:56 kernel: Freeing initrd memory: 884K
May 4 06:46:56 kernel: NET: Registered protocol family 16
May 4 06:46:56 kernel: SCSI subsystem initialized
May 4 06:46:56 kernel: usbcore: registered new driver usbfs
May 4 06:46:56 kernel: usbcore: registered new driver hub
May 4 06:46:56 kernel: Real Time Clock Driver v1.12
May 4 06:46:56 kernel: LPC2xxx Watchdog Driver
May 4 06:46:56 kernel: LPC2xxx ADC Driver
May 4 06:46:56 kernel: Serial: 8250/16550 driver $Revision: 1.90 $ 2 ports, IRQ sharing disabled
May 4 06:46:56 kernel: ttyS0 at MMIO 0x0 (irq = 6) is a 16550A
May 4 06:46:57 kernel: ttyS1 at MMIO 0x0 (irq = 7) is a 16550A
May 4 06:46:57 kernel: io scheduler noop registered
May 4 06:46:57 kernel: io scheduler anticipatory registered
May 4 06:46:57 kernel: io scheduler deadline registered
May 4 06:46:57 kernel: io scheduler cfq registered
May 4 06:46:57 kernel: RAMDISK driver initialized: 1 RAM disks of 4096K size 1024 blocksize
May 4 06:46:57 kernel: PPP generic driver version 2.4.2
May 4 06:46:57 kernel: PPP Deflate Compression module registered
May 4 06:46:57 kernel: tun: Universal TUN/TAP device driver, 1.6
May 4 06:46:57 kernel: tun: (C) 1999-2004 Max Krasnyansky <[email protected]>
May 4 06:46:58 kernel: NAND device: Manufacturer ID: 0xec, Chip ID: 0xdc (Samsung NAND 512MiB 3,3V 8-bit)
May 4 06:46:58 kernel: Creating 1 MTD partitions on "NAND 512MiB 3,3V 8-bit":
May 4 06:46:58 kernel: 0x00000000-0x20000000 : "NAND filesystem"
May 4 06:46:58 kernel: sl811: driver sl811-hcd, 15 Dec 2004
May 4 06:46:58 kernel: sl811: SL811HS v1.5, irq 16
May 4 06:46:58 kernel: sl811-hcd sl811-hcd: new USB bus registered, assigned bus number 1
May 4 06:46:58 kernel: hub 1-0:1.0: USB hub found
May 4 06:46:58 kernel: hub 1-0:1.0: 1 port detected
May 4 06:46:58 kernel: Initializing USB Mass Storage driver...
May 4 06:46:58 kernel: usbcore: registered new driver usb-storage
May 4 06:46:58 kernel: USB Mass Storage support registered.
May 4 06:46:58 kernel: usbcore: registered new driver usbserial
May 4 06:46:59 kernel: drivers/usb/serial/usb-serial.c: USB Serial Driver core v2.0
May 4 06:46:59 kernel: drivers/usb/serial/usb-serial.c: USB Serial support registered for FTDI SIO
May 4 06:46:59 kernel: drivers/usb/serial/usb-serial.c: USB Serial support registered for FTDI 8U232AM Compatible
May 4 06:46:59 kernel: drivers/usb/serial/usb-serial.c: USB Serial support registered for FTDI FT232BM Compatible
May 4 06:46:59 kernel: drivers/usb/serial/usb-serial.c: USB Serial support registered for FTDI FT2232C Compatible
May 4 06:46:59 kernel: drivers/usb/serial/usb-serial.c: USB Serial support registered for USB-UIRT Infrared Tranceiver
May 4 06:46:59 kernel: drivers/usb/serial/usb-serial.c: USB Serial support registered for Home-Electronics TIRA-1 IR Transceiver
May 4 06:46:59 kernel: usbcore: registered new driver ftdi_sio
May 4 06:46:59 kernel: drivers/usb/serial/ftdi_sio.c: v1.4.1:USB FTDI Serial Converters Driver
May 4 06:46:59 kernel: drivers/usb/serial/usb-serial.c: USB Serial support registered for PL-2303
May 4 06:47:00 kernel: usbcore: registered new driver pl2303
May 4 06:47:00 kernel: drivers/usb/serial/pl2303.c: Prolific PL2303 USB to serial adaptor driver v0.12
May 4 06:47:00 kernel: i2c /dev entries driver
May 4 06:47:00 kernel: LPC2xxx I2C Driver
May 4 06:47:00 kernel: LPC2xxx CAN Driver
May 4 06:47:00 kernel: LPC2xxx CAN Console Driver
May 4 06:47:00 kernel: NET: Registered protocol family 2
May 4 06:47:00 kernel: IP: routing cache hash table of 512 buckets, 4Kbytes
May 4 06:47:00 kernel: TCP established hash table entries: 2048 (order: 2, 16384 bytes)
May 4 06:47:00 kernel: TCP bind hash table entries: 2048 (order: 1, 8192 bytes)
May 4 06:47:02 kernel: TCP: Hash tables configured (established 2048 bind 2048)
May 4 06:47:02 kernel: NET: Registered protocol family 1
May 4 06:47:02 kernel: NET: Registered protocol family 17
May 4 06:47:03 init: ^MStarting pid 139, console /dev/console: '/bin/iptables'
May 4 06:47:05 init: ^MStarting pid 142, console /dev/console: '/bin/iptables'
May 4 06:47:09 init: ^MStarting pid 144, console /dev/null: '/bin/watchdog'
May 4 06:47:09 init: ^MStarting pid 145, console /dev/null: '/bin/inetd'
May 4 06:47:09 init: ^MStarting pid 146, console /dev/null: '/bin/obd'
May 4 06:47:09 init: ^MStarting pid 147, console /dev/null: '/bin/pppconnect'
May 4 06:47:09 init: ^MStarting pid 148, console /dev/null: '/bin/logd'
May 4 06:47:10 init: ^MStarting pid 149, console /dev/console: '/bin/minder'
May 4 06:47:16 syslog: VMS: VMS restarted - version 15.1.0
May 4 06:47:16 kernel: serial8250: too much work for irq7
May 4 06:47:21 syslog: VMS: Watchdog reset 1 4291
May 7 23:05:34 kernel: usb 1-1: new full speed USB device using sl811-hcd and address 2
May 7 23:05:34 kernel: scsi0 : SCSI emulation for USB Mass Storage devices
May 7 23:05:34 kernel: usb-storage: device found at 2
May 7 23:05:34 kernel: usb-storage: waiting for device to settle before scanning
May 7 23:05:40 kernel: Vendor: USB Model: Flash Disk Rev: 1100
May 7 23:05:40 kernel: Type: Direct-Access ANSI SCSI revision: 04
May 7 23:05:40 kernel: SCSI device sda: 3915776 512-byte hdwr sectors (2005 MB)
May 7 23:05:40 kernel: sda: assuming Write Enabled
May 7 23:05:40 kernel: sda: assuming drive cache: write through
May 7 23:05:40 kernel: SCSI device sda: 3915776 512-byte hdwr sectors (2005 MB)
May 7 23:05:40 kernel: sda: assuming Write Enabled
May 7 23:05:40 kernel: sda: assuming drive cache: write through
May 7 23:05:40 kernel: sda1
May 7 23:05:40 kernel: Attached scsi removable disk sda at scsi0, channel 0, id 0, lun 0
May 7 23:05:41 kernel: usb-storage: device scan complete
May 7 23:11:03 kernel: ttyS1: 1 input overrun(s)
May 7 23:11:42 kernel: ttyS1: 1 input overrun(s)
May 7 23:13:19 kernel: ttyS1: 1 input overrun(s)
 
Somehow all your memory is being used, out of memory killer is kicking in to keep the system up:
Out of memory: Kill process or sacrifice child – Plumbr

I'd try pulling the VMS plug and plugging it back in, triggering a cold reboot. Something seems stuck eating up all the memory creating this loop. The cold reboot will break might break it out of the cycle.

Flash appeared to be initialized by kernel fine, I also didn't see any issues with corruption.
 
Last edited:
  • Helpful
Reactions: brianman
Man, I'm so sorry to read this. Flat-bedding a car 200km can't be cheap (I assume Tesla isn't paying?)

You could pick up some wheel dollies- I've even seen them rented before - to help you move the car out of it's current position. There are ones that go around a wheel and then lift as you step on a lever. (Repo men use these to get cars out of tight spots so they can tow them away) They are often called positioning dollies or jacks.

vp.jpg
 
It looks like there are several connectors on there ... did you try re-seating all the other connectors to make sure they hadn't come a little loose? I don't pretend to be a Roadster expert but I've had a tape deck stop working simply because the wiring harness fell off the back. Of course the simple fix required taking off several pieces of trim from the shifter to midway up the dash though! :)
 
Well Tesla is saying that it isn't a firmware issue at all, that it's an isolation fault. LOL maybe the error message is wrong.

Anyway it's off to Montreal for service. If you want to see pics of the rather tricky loading procedure (it was parked in my garage nose-in, which made it rather difficult to pull out), I've posted some pics here: Poor old Essie towed again
 
What would cause firmware corruption? I'm trying to think what I could do to help prevent this. The only thing I can think is don't go waving magnets over anything...:)
A rogue write command pointed at the wrong address?
 
What would cause firmware corruption? I'm trying to think what I could do to help prevent this. The only thing I can think is don't go waving magnets over anything...:)
A rogue write command pointed at the wrong address?

You can't prevent it, filesystem corruptions are inevitable unless you design your filesystem to be redundant and to fix itself with the backup copy while its up and running. Some corruptions are recoverable others are not. Filesystem corruption can occur from a bug in the filesystem, bug in the eMMC / flash firmware, and at times from a non-fatal error with the eMMC / flash memory (hardware) itself. Typically in the latter, the eMMC firmware identifies areas that are bad and marks them as not writeable / readable, it keeps a list of the areas that are bad so that it doesn't write to them. And you can have a fatal eMMC/flash issue, but that typically isn't recoverable and you need to swap out the part. And yes Henry, you're correct, the OS and/or application software can write to the wrong address and also cause a corruption.

Doug, you should dump your logs again and view your 'messages' file. I'm curious if you have or don't have the out of memory errors. If you don't then that's one confirming sign that the firmware has been corrupted which others in the future may need to reference.