我刚刚更新了包：
2013-05-23 11:15:34 startup archives unpack
2013-05-23 11:15:35 upgrade locales:all 2.13-38 2.17-3
2013-05-23 11:15:35 status half-configured locales:all 2.13-38
2013-05-23 11:15:35 status unpacked locales:all 2.13-38
2013-05-23 11:15:35 status half-installed locales:all 2.13-38
2013-05-23 11:15:35 status triggers-pending man-db:amd64 2.6.3-3
2013-05-23 11:15:35 status half-installed locales:all 2.13-38
2013-05-23 11:15:38 status half-installed locales:all 2.13-38
2013-05-23 11:15:38 status unpacked locales:all 2.17-3
2013-05-23 11:15:39 status unpacked locales:all 2.17-3
2013-05-23 11:15:39 upgrade libc6:i386 2.13-38 2.17-3
2013-05-23 11:15:39 status half-configured libc6:i386 2.13-38
2013-05-23 11:15:40 status unpacked libc6:i386 2.13-38
2013-05-23 11:15:40 status half-configured libc6:amd64 2.13-38
2013-05-23 11:15:40 status half-installed libc6:i386 2.13-38
2013-05-23 11:15:47 status half-installed libc6:i386 2.13-38
2013-05-23 11:15:47 status unpacked libc6:i386 2.17-3
2013-05-23 11:15:48 status unpacked libc6:i386 2.17-3
2013-05-23 11:15:48 upgrade libc6:amd64 2.13-38 2.17-3
2013-05-23 11:15:48 status half-configured libc6:amd64 2.13-38
2013-05-23 11:15:48 status unpacked libc6:amd64 2.13-38
2013-05-23 11:15:48 status half-installed libc6:amd64 2.13-38
2013-05-23 11:15:53 status half-installed libc6:amd64 2.13-38
2013-05-23 11:15:53 status unpacked libc6:amd64 2.17-3
2013-05-23 11:15:54 status unpacked libc6:amd64 2.17-3
2013-05-23 11:15:54 trigproc man-db:amd64 2.6.3-3 2.6.3-3
2013-05-23 11:15:54 status half-configured man-db:amd64 2.6.3-3
2013-05-23 11:16:00 status installed man-db:amd64 2.6.3-3
2013-05-23 11:16:01 startup packages configure
2013-05-23 11:16:01 configure libc6:amd64 2.17-3 <none>
2013-05-23 11:16:01 status unpacked libc6:amd64 2.17-3
2013-05-23 11:16:02 status unpacked libc6:amd64 2.17-3
2013-05-23 11:16:02 status half-configured libc6:amd64 2.17-3
2013-05-23 11:16:57 status installed libc6:amd64 2.17-3
2013-05-23 11:16:57 configure libc6:i386 2.17-3 <none>
2013-05-23 11:16:57 status unpacked libc6:i386 2.17-3
2013-05-23 11:16:57 status unpacked libc6:i386 2.17-3
2013-05-23 11:16:57 status half-configured libc6:i386 2.17-3
2013-05-23 11:16:57 configure locales:all 2.17-3 <none>
2013-05-23 11:16:57 status unpacked locales:all 2.17-3
2013-05-23 11:16:57 status unpacked locales:all 2.17-3
2013-05-23 11:16:57 status half-configured locales:all 2.17-3
Debian GNU/Linux jessie/sid \n \l
从那时起，我的计算机就给我带来了内核恐慌。 :/
更准确地说是这样的：
在里面13f ip 处出现段错误.. [我不记得其余的消息了]
内核恐慌不同步。试图杀死 init。
初始未泰特..
我该如何处理？
我发现了这样的事情： http://forums.debian.net/viewtopic.php?f=10&t=96879 据我记得（或者也许我错了）某种 libc 已更新..我尝试根据评论 21但我没有：
/lib/libc.so.6
文件。
添加了启动停止时的图片。
从 /var/log/apt/term.log 添加日志：
Log started: 2013-05-23 09:57:05
Selecting previously unselected package less.
(Reading database ...
(Reading database ... 5%
(Reading database ... 10%
(Reading database ... 15%
(Reading database ... 20%
(Reading database ... 25%
(Reading database ... 30%
(Reading database ... 35%
(Reading database ... 40%
(Reading database ... 45%
(Reading database ... 50%
(Reading database ... 55%
(Reading database ... 60%
(Reading database ... 65%
(Reading database ... 70%
(Reading database ... 75%
(Reading database ... 80%
(Reading database ... 85%
(Reading database ... 90%
(Reading database ... 95%
(Reading database ... 100%
(Reading database ... 320906 files and directories currently installed.)
Unpacking less (from .../archives/less_458-1_amd64.deb) ...
Processing triggers for mime-support ...
Processing triggers for man-db ...
Setting up less (458-1) ...
Log ended: 2013-05-23 09:57:16
Log started: 2013-05-23 11:15:33
(Reading database ...
(Reading database ... 5%
(Reading database ... 10%
(Reading database ... 15%
(Reading database ... 20%
(Reading database ... 25%
(Reading database ... 30%
(Reading database ... 35%
(Reading database ... 40%
(Reading database ... 45%
(Reading database ... 50%
(Reading database ... 55%
(Reading database ... 60%
(Reading database ... 65%
(Reading database ... 70%
(Reading database ... 75%
(Reading database ... 80%
(Reading database ... 85%
(Reading database ... 90%
(Reading database ... 95%
(Reading database ... 100%
(Reading database ... 320928 files and directories currently installed.)
Preparing to replace locales 2.13-38 (using .../locales_2.17-3_all.deb) ...
Unpacking replacement locales ...
Preparing to replace libc6:i386 2.13-38 (using .../archives/libc6_2.17-3_i386.deb) ...
De-configuring libc6:amd64 ...
Checking for services that may need to be restarted...
Checking init scripts...
Unpacking replacement libc6:i386 ...
Preparing to replace libc6:amd64 2.13-38 (using .../libc6_2.17-3_amd64.deb) ...
Checking for services that may need to be restarted...
Checking init scripts...
Unpacking replacement libc6:amd64 ...
Processing triggers for man-db ...
Setting up libc6:amd64 (2.17-3) ...
Checking for services that may need to be restarted...
Checking init scripts...
Restarting services possibly affected by the upgrade:
samba: restarting...done.
mysql: restarting...done.
cron: restarting...done.
atd: restarting...done.
apache2: restarting...done.
Services restarted successfully.
Setting up libc6:i386 (2.17-3) ...
dpkg: error processing libc6:i386 (--configure):
subprocess installed post-installation script was killed by signal (Segmentation fault)
Setting up locales (2.17-3) ...
Installing new version of config file /etc/locale.alias ...
dpkg: error processing locales (--configure):
subprocess installed post-installation script was killed by signal (Segmentation fault)
Errors were encountered while processing:
libc6:i386
locales
日志结束: 2013-05-23 11:16:59
答案1
我做了沙伊巴 说， 所以：
- 备份您的敏感内容（仅限我/home 目录）
- 重新安装操作系统
答案2
所有发行版都会保留一些内核，以应对（不太可能）内核安装失败或上次更新严重中断的情况。启动较旧的。
大多数发行版的安装介质兼作救援介质。用它启动，并修复系统。
它可能由于某种硬件错误（发生在我身上......）。使用安装介质的诊断工具（或其他工具）检查系统。损坏的文件系统也可能是原因（慷慨的帮助fsck可能会解决这个问题）。文件可能已损坏（一种流行的方法是，如果机器在错误的时间崩溃，则用空文件替换），find /etc -empty或者这样会将它们排除）。对已安装的软件包运行诊断，在基于 RPM 的系统上运行诊断rpm -Va会报告不一致的情况（但由于某种原因，即使在许多新安装的软件包上，RPM 也会抱怨，不要惊慌）。检查是否有重复的包和其他不一致的情况。重新安装任何看起来可疑的软件包。