** Changed in: linux (Ubuntu)
Status: Confirmed => Invalid
** Summary changed:
- booting with amd64 kernel and completely i386 userland is unstable during the
system upstart
+ booting with amd64 kernel and completely i386 userland is unstable during the
system upstart on Samsung Phoenix
Similar random reboots with a amd64 kernel in the cases with the same
CPU were reported (quite a long ago,for Ubuntu 9.04) there:
http://ubuntuforums.org/showthread.php?t=1137153
They also say that some other distros also had this problem
(e.g.,Gentoo), but there were successful boots of some
The same CPU means: Intel P7350.
Other found links (under the title "join club"):
http://ubuntuforums.org/showthread.php?t=1137153
--
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
I'll have to see whether there some updates fro my BIOS available.
--
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
Yes, my BIOS is also Phoenix, as in that buggy case! So, it's very
probable that it's the same known problem.
marsmorgana@marsmorgana:~$ cat /sys/devices/virtual/dmi/id/bios_vendor
Phoenix Technologies Ltd.
marsmorgana@marsmorgana:~$ cat /sys/devices/virtual/dmi/id/bios_version
** No longer affects: upstart (Ubuntu)
** No longer affects: udev (Ubuntu)
** No longer affects: systemd (Ubuntu)
--
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
** Changed in: linux (Ubuntu)
Importance: Undecided => Wishlist
** Changed in: systemd (Ubuntu)
Importance: Undecided => Wishlist
** Changed in: udev (Ubuntu)
Importance: Undecided => Wishlist
** Changed in: upstart (Ubuntu)
Importance: Undecided => Wishlist
--
You received this
Perhaps, this combination of hardware and amd64 kernel is simply buggy,
and it would be unstable in a completely amd64 system. I should test
that to be sure.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Some good results: the somewhat offending module was coretemp. (Here, I
have an Intel processor. On the computer, where there is no
crash/reboot, the processor is AMD, and there k10temp or k9temp module
is used. The other computer is fine with 14.04 (Trusty) and 14.10
(Utopic).)
Moving coretemp
And I needed to add "debug" kernel parameter as a workaround, otherwise
the boot was not stable during the early stage.
--
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:
Now, as I have localized the problem, I'm ready to debug the problems of
the coretemp module, if you give me advices.
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
** Changed in: systemd (Ubuntu)
Status: Incomplete => Confirmed
** Changed in: udev (Ubuntu)
** Tags added: wily
--
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
On another similar computer (a Samsung R525, rather than a Samsung R510,
where I got the crash), I was able to do the trick successfully on 14.10
(Trusty) with linux-image-extra-3.13.0-63-generic:amd64 .
Of course, there are differences in the set of devices in these
computers:
* radeon video
I made a typo: I meant *Trusty* (14.04) -- on another computer, this
trick on Trusty was successful.
--
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
A small update on my progress:
On the computer where this crash/reboot occurs, it happens also with
15.10 (Wily) and linux-image-4.2.0-10-generic.
I'm going to use the following the debugging procedure for udev loading
the drivers described at
Hi Martin,
thanks for your suggestions.
Since the system rebooted after such crash usually, I wanted to use
netconsole (as described at
https://wiki.ubuntu.com/Kernel/KernelDebuggingTricks#Network_Console ),
but I didn't see any messages on the network, probably because the
netconsole module has
A longer log from a crash.
** Attachment added: "2015-09-21T19:27+0300-kdebug.txt"
https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/1495116/+attachment/4470651/+files/2015-09-21T19%3A27%2B0300-kdebug.txt
--
You received this bug notification because you are a member of Kernel
Well, I'm not sure that my netconsole got working during the initrd
stage (first, I suspected that the module was not loaded in initrd --
http://askubuntu.com/q/676707/19753 , but then I found out that there is
code for this to happen if there is the "netconsole" kernel parameter
present, so
amd64 kernel with i386 userspace does work in general. But this bug
contains no actual error message -- can you try booting with "debug" in
the kernel command line and drop "quiet splash", then wait for a failed
boot, and make a screenshot (with a camera)? There hopefully is some
indication what's
The problem is also present after an upgrade to 15.04 (Vivid) with:
linux-image-3.19.0-28-generic:amd64
linux-image-extra-3.19.0-28-generic:amd64
systemd-219-7ubuntu6 (i386)
** Also affects: systemd (Ubuntu)
Importance: Undecided
Status: New
** Tags removed: third-party-packages
**
I was able to boot with the amd64 kernel from Vivid and upstart (but I
guess that the successes and failures are just random), and will now
collect the new information (for 15.04 (Vivid) system).
** Description changed:
I wanted to run my 14.10 (Utopic) i386 system with the amd64 kernel, so
With systemd.crash_shell=true systemd.confirm_spawn=true (which is very
inconvenient to use), I've found out that the crash usually happens
somewhere around the start of udev services.
** Also affects: udev (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug
Hi dino99,
I've upgraded to 15.04 (Vivid) and am testing it there (as reflected in
my posts here).
My goal is not multiarch libs/apps. I must not not need them really in
my config: they should stay i386. Only the kernel is amd64.
There are a lot of reports of doing this successfully in various
Soemthing to start with for catching the bug:
I've removed the corresponding linux-image-extra package, and now the
booting is stable.
But I don't have the needed drivers for video (nouveau) and network
then. (And possibly more.)
So loading one of the drivers from -extra caused the crash.
The
hi Ivan,
you are testing an usual config here; but if i can mind you some details:
- utopic has already reached EOL some times ago
- even Wily has not yet a complete multiarch portage; so many libs/apps still
need some work on that side. Of course Utopic status is even worst.
I feel you are
i suggest to upgrade to Wily as it might be easier
As your experiment has catch my curiosity, i've searched around, and
found some threads; they mainly said 'yes that should be possible, with
lot of headaches'
So good luck :) :)
--
You received this bug notification because you are a member
apport information
** Tags added: apport-collected third-party-packages
** Description changed:
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
Is there any more needed logs/information?
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
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
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
** Package changed: linux-meta (Ubuntu) => linux (Ubuntu)
--
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
30 matches
Mail list logo
