kernel-packages team mailing list archive
-
kernel-packages team
-
Mailing list archive
-
Message #134475
[Bug 1495116] Re: booting with amd64 kernel and completely i386 userland is unstable during the system upstart
I've collected this information after a successful system upstart. But
the system upstart procedure fails in 3 cases of 4. That's what I want
to investigate. The system reboots at a random moment during the upstart
procedure, and I can't get the logs probably.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1495116
Title:
booting with amd64 kernel and completely i386 userland is unstable
during the system upstart
Status in linux package in Ubuntu:
Confirmed
Status in upstart package in Ubuntu:
New
Bug description:
I wanted to run my 14.10 (Utopic) i386 system with the amd64 kernel,
so I added that architecture and apt-get-installed the amd64 linux-
image and linux-image-extra (I learned this was possible thanks to the
advice at http://askubuntu.com/a/635774/19753 ).
However, the system upstart procedure more often fails than not: it
fails by rebooting the computer. (Only around 1 time of 4 is
successful.)
A limited system start is (probably, always) successful: either with
init=/bin/bash parameter to the kernel, or choosing the recovery boot
option. (However, if I "resume" from the recovery menu, or run "exec
init" in bash, then the upstart procedure is similarly unstable: it
usually fails/crashes and reboots.)
I checked my suspection that the video driver (nouveau) and X might
be involved, but that turned out not true: the upstart procedure is
similarly unstable with "nomodesetting" kernel parameter and without,
booting into runlevel 3 or the default one.
Perhaps, I'd like to debug the upstart procedure step-by-step to
detect which step makes the system crash and reboot, but I don't know
how. As concerns the timing, the moment the reboot happens can be
different: it can happen rather early (when I see the message about
activating the swap) or much later.
If the system upstart procedure has completed successfully, then it
works in a quite stable manner and doesn't crash/reboot. So, there is
something bad specifically during the system upstart procedure.
ProblemType: Bug
DistroRelease: Ubuntu 14.10
Package: upstart 1.13.2-0ubuntu2
ProcVersionSignature: Ubuntu 3.16.0-44.59-generic 3.16.7-ckt14
Uname: Linux 3.16.0-44-generic x86_64
ApportVersion: 2.14.7-0ubuntu8.5
Architecture: i386
CurrentDesktop: Unity
Date: Sat Sep 12 18:36:28 2015
InstallationDate: Installed on 2014-06-04 (464 days ago)
InstallationMedia: Ubuntu 12.04.4 LTS "Precise Pangolin" - Release i386 (20140204)
ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-3.16.0-44-generic root=UUID=980299a2-fde5-4f39-acb0-189f528b8485 ro nosplash
SourcePackage: upstart
UpgradeStatus: Upgraded to utopic on 2015-09-11 (0 days ago)
UpstartBugCategory: System
UpstartRunningSessionVersion: upstart 1.13.2
UpstartRunningSystemVersion: init (upstart 1.13.2)
modified.conffile..etc.at.deny: [inaccessible: [Errno 13] Отказано в доступе: '/etc/at.deny']
modified.conffile..etc.cron.daily.upstart: [modified]
modified.conffile..etc.cups.cups.browsed.conf: [modified]
modified.conffile..etc.default.apport: [modified]
modified.conffile..etc.default.cups: [modified]
modified.conffile..etc.init.d.binfmt.support: [modified]
mtime.conffile..etc.X11.Xsession.d.99upstart: 2014-09-30T12:21:08
mtime.conffile..etc.cron.daily.upstart: 2014-09-30T12:27:13
mtime.conffile..etc.cups.cups.browsed.conf: 2015-09-06T09:29:16.410097
mtime.conffile..etc.default.apport: 2014-06-05T12:49:10.316398
mtime.conffile..etc.default.cups: 2015-09-06T09:20:49.891585
mtime.conffile..etc.init.d.binfmt.support: 2014-09-30T12:21:08
mtime.conffile..etc.upstart.xsessions: 2014-09-30T12:21:08
---
ApportVersion: 2.14.7-0ubuntu8.5
Architecture: i386
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/controlC0: marsmorgana 1972 F.... pulseaudio
CRDA:
country RU: DFS-UNSET
(2402 - 2482 @ 40), (N/A, 20)
(5735 - 5835 @ 20), (N/A, 30)
CurrentDesktop: Unity
DistroRelease: Ubuntu 14.10
HibernationDevice: RESUME=UUID=9267c811-3a01-4484-b968-c08582280d81
InstallationDate: Installed on 2014-06-04 (464 days ago)
InstallationMedia: Ubuntu 12.04.4 LTS "Precise Pangolin" - Release i386 (20140204)
MachineType: SAMSUNG ELECTRONICS CO., LTD. R510/P510
Package: upstart 1.13.2-0ubuntu2
PackageArchitecture: i386
ProcFB: 0 nouveaufb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-44-generic root=UUID=980299a2-fde5-4f39-acb0-189f528b8485 ro nosplash
ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-3.16.0-44-generic root=UUID=980299a2-fde5-4f39-acb0-189f528b8485 ro nosplash
ProcVersionSignature: Ubuntu 3.16.0-44.59-generic 3.16.7-ckt14
RelatedPackageVersions:
linux-restricted-modules-3.16.0-44-generic N/A
linux-backports-modules-3.16.0-44-generic N/A
linux-firmware 1.138.1
Tags: utopic utopic third-party-packages
Uname: Linux 3.16.0-44-generic x86_64
UpgradeStatus: Upgraded to utopic on 2015-09-11 (0 days ago)
UpstartBugCategory: System
UpstartRunningSessionVersion: upstart 1.13.2
UpstartRunningSystemVersion: init (upstart 1.13.2)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 09/26/2008
dmi.bios.vendor: Phoenix Technologies Ltd.
dmi.bios.version: 07LI.MP00.20080926.SCY
dmi.board.name: R510/P510
dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
dmi.board.version: Not Applicable
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
dmi.chassis.version: N/A
dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvr07LI.MP00.20080926.SCY:bd09/26/2008:svnSAMSUNGELECTRONICSCO.,LTD.:pnR510/P510:pvrNotApplicable:rvnSAMSUNGELECTRONICSCO.,LTD.:rnR510/P510:rvrNotApplicable:cvnSAMSUNGELECTRONICSCO.,LTD.:ct10:cvrN/A:
dmi.product.name: R510/P510
dmi.product.version: Not Applicable
dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.
modified.conffile..etc.at.deny: [inaccessible: [Errno 13] Отказано в доступе: u'/etc/at.deny']
modified.conffile..etc.cups.cups.browsed.conf: [modified]
modified.conffile..etc.default.apport: [modified]
modified.conffile..etc.default.cups: [modified]
modified.conffile..etc.init.d.binfmt.support: [modified]
mtime.conffile..etc.X11.Xsession.d.99upstart: 2014-09-30T12:21:08
mtime.conffile..etc.cron.daily.upstart: 2014-09-30T12:27:13
mtime.conffile..etc.cups.cups.browsed.conf: 2015-09-06T09:29:16.410097
mtime.conffile..etc.default.apport: 2014-06-05T12:49:10.316399
mtime.conffile..etc.default.cups: 2015-09-06T09:20:49.891586
mtime.conffile..etc.init.d.binfmt.support: 2014-09-30T12:21:08
mtime.conffile..etc.upstart.xsessions: 2014-09-30T12:21:08
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1495116/+subscriptions
References