Opened 2 years ago

Closed 13 months ago

#638 closed System Defect (3rdpartybug)

init:: can't exec getty '/usr/libexec/getty' for port ...

Reported by: harlan Owned by: kris
Priority: major Milestone:
Component: System Configuration Version: 9.1-BETA1
Keywords: Cc: trac-bugs@…

Description

When I upgraded from 9.0 to the 9.1 beta I had the above problem. I just upgraded from the latest beta to RC1.

While the box was applying package updates there was a kernel panic after a fair number of packages were installed.

I rebooted the box and what I get is the system mounts the root filesystem and I immediately get the 'getty' messages described above. The system does not let me log in.

If I boot in to single-user mode I can mount the filesystems just fine, but when I exit single user mode I'm left at an Amnesiac login prompt - the system does not try and go multi-user.

Attachments (2)

pcbsd-reboot-panic.jpg (120.3 KB) - added by harlan 2 years ago.
kernel panic backtrace from "halt
info.0 (478 bytes) - added by harlan 2 years ago.
crashdump info file

Download all attachments as: .zip

Change History (8)

comment:1 Changed 2 years ago by harlan

/etc/rc is 0 bytes long.

comment:2 Changed 2 years ago by harlan

I've discovered that the "reboot" and "halt" command cause the panic - I'll be attaching a screen shot soon.

Changed 2 years ago by harlan

kernel panic backtrace from "halt

Changed 2 years ago by harlan

crashdump info file

comment:3 Changed 2 years ago by harlan

If I issue the reboot command from multi-user mode the kernel panics.

If I 'init 1' then sync and reboot, the box reboots just fine.

Oh, I ran memtest86+ and got 7 completely clean passes.

comment:4 Changed 2 years ago by kris

  • Owner set to kris

comment:5 Changed 2 years ago by kris

If the rc.conf file got removed, then you can grab a fresh copy from here:

http://trac.pcbsd.org/browser/pcbsd/current/overlays/desktop-overlay/etc/rc.conf

The real problem is the issue with the halt / reboot commands causing a kernel panic. When that happens if rc.conf had been recently written to, often it will get corrupted and then this occurs. This issue is being looked into on the FreeBSD end I think.

comment:6 Changed 13 months ago by kenmoore

  • Resolution set to 3rdpartybug
  • Status changed from new to closed
Note: See TracTickets for help on using tickets.