ge. Whether that's your
problem or not, I have no idea. As for the other architectures, I
have no idea about them either.
--
.''`. Stephen Powell
: :' :
`. `'`
`-
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
On Thu, 25 Mar 2010 11:03:01 -0400 (EDT), Jonathan Nieder wrote:
> Stephen Powell wrote:
>> The only thing I know of that changed recently is the switch
>> to a 64-bit kernel by the build server for s390. (I am just a regular
>> Joe Schmoe user. I'm not a Debian
a couple of weeks ago? (See BR 573887.)
--
.''`. Stephen Powell
: :' :
`. `'`
`-
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
d)
http://www.wowway.com/~zlinuxman/initramfs/post-update.d/bootloader
(for installation in /etc/initramfs/post-update.d)
--
.''`. Stephen Powell
: :' :
`. `'`
`-
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subje
/postrm.d/zz-bootloader
initramfs hook:
http://www.wowway.com/~zlinuxman/initramfs/post-update.d/bootloader
If they are of any use to you, help yourself.
--
.''`. Stephen Powell
: :' :
`. `'`
`-
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lis
CC me.
--
.''`. Stephen Powell
: :' :
`. `'`
`-
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
On Sat, 07 Aug 2010 11:02:21 -0400 (EDT), Moritz Muehlenhoff wrote:
> On Tue, Jul 27, 2010 at 09:11:16AM -0400, Stephen Powell wrote:
>> Hello, Bastian. Sorry to bother you. I reopened this bug log because
>> it appears to be installable only on the amd64 architecture. I tried
&
On Mon, 09 Aug 2010 13:37:45 -0400 (EDT), Adam D. Barratt wrote:
> On Mon, 2010-08-09 at 11:10 -0400, Stephen Powell wrote:
>> On Sat, 07 Aug 2010 11:02:21 -0400 (EDT), Moritz Muehlenhoff wrote:
>>> non-free is no longer autobuilt.
>>
>> I hadn't heard that,
On Mon, 09 Aug 2010 15:49:14 -0400 (EDT), Adam D. Barratt wrote:
> On Mon, 2010-08-09 at 14:54 -0400, Stephen Powell wrote:
>> It seems to me that something needs
>> to be done to get these packages to autobuild again somehow. What needs to
>> be done to make that happen?
things: (1) it guarantees the correspondence of
Linux devices names to s390 device numbers as follows:
Device
0200 /dev/dasda
0201 /dev/dasdb
0202 /dev/dasdc
0203 /dev/dasdd
and (2) it specifies the device driver used for each disk as follows:
--
.''`.
need to be
loaded as "essential drivers" if this file is not present?
A new kernel, linux-image-2.6.32-5-s390x, was also included in the upgrade;
so perhaps this is part of the problem as well. Previously, I was using
linux-image-2.6.32-3-s390x.
--
.''`. Stephen Powell
: :
l wouldn't boot either.
So this is not related to the kernel. It is definitely related to the
new version of initramfs-tools.
--
.''`. Stephen Powell
: :' :
`. `'`
`-
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject
I solved the mystery. Now someone on the kernel team actually has
to fix it.
--
.''`. Stephen Powell
: :' :
`. `'`
`-
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
kernel maintainer scripts to invoke the bootloader. See also, for example,
linux-image-2.6.26-2-s390.postinst, where zipl is assigned as the bootloader
on line 38. This really is an "open and shut case", if only I can the kernel
people to actually look at it! Please l
On Tue, 08 Jun 2010 07:39:58 -0400 (EDT), Vincent Danjean wrote:
> On 07/06/2010 17:37, Stephen Powell wrote:
>> But for a kernel install or reconfigure, it is the responsibility of the
>> kernel maintainer scripts to invoke the bootloader. See also, for example,
>> linu
/lilo.conf
or use
MODULES=dep
in /etc/initramfs-tools/conf.d/driver-policy. But chances are
that manually running lilo is all you need to do.
--
.''`. Stephen Powell
: :' :
`. `'`
`-
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.o
verything works, then we can be sure that this is a duplicate of
505609.
--
.''`. Stephen Powell
: :' :
`. `'`
`-
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
On Tue, 15 Jun 2010 23:25:45 -0400 (EDT), Ben Hutchings wrote:
> On Tue, 2010-06-08 at 09:43 -0400, Stephen Powell wrote:
>>
>>do_bootloader = yes
>>
>> in /etc/kernel-img.conf means "run the historic boot loader for this
>> platform".
>> Fo
On Thu, 17 Jun 2010 18:11:04 -0400 (EDT), Ben Hutchings wrote:
> On Thu, Jun 17, 2010 at 12:33:58PM -0400, Stephen Powell wrote:
>> [...]
>> I can maybe accept your proposal for Squeeze. But for Lenny, I believe
>> that the maintainer scripts should be changed back they
rical' bootloader
> setting should be restored in an update to lenny.
Great! What about Squeeze? It still supports creating the initial RAM
file system and updating symlinks via variables in /etc/kernel-img.conf.
Doesn't it make sense to allow the historical boot loader code to work
On Fri, 18 Jun 2010 04:25:38 -0400 (EDT), Joachim Wiedorn wrote:
> Ben Hutchings wrote on 2010-06-18 02:02:
>> On Thu, 2010-06-17 at 20:37 -0400, Stephen Powell wrote:
>>> And how would one go about setting this "loader" variable?
>>> The "loader"
On Fri, 18 Jun 2010 11:51:11 -0400 (EDT), maximilian attems wrote:
> On Fri, Jun 18, 2010 at 10:55:35AM -0400, Stephen Powell wrote:
>> As for "update-initramfs -u", it *will* invoke lilo if lilo is installed
>> and "do_bootloader = yes" is specified in /etc
n using a custom kernel.
If you have any further questions about this lilo problem, please post
to this bug log (585856).
--
.''`. Stephen Powell
: :' :
`. `'`
`-
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
in the step after kernel installation:
I am not a package maintainer for s390-tools; I am a user who is an interested
party to this bug report. This bug is related to bug number 599931, and the
hook script templates provided in the body of bug report 599931 will fix both
that problem and this one.
od measure.
--
.''`. Stephen Powell
: :' :
`. `'`
`-
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
upgrade the rest of
your database.
apt-get upgrade
apt-get clean
apt-get --purge dist-upgrade
apt-get clean
apt-get --purge autoremove
aptitude forget-new
aptitude keep-all
I hope this helps someone.
--
.''`. Stephen Powell
: :' :
`. `'`
`-
ior to the
zipl menu being written out. The system is unbootable. This may
be related to the "general brokenness" of C on s390x in jessie/sid.
--
.''`. Stephen Powell
: :' :
`. `'`
`-
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.d
rary
(zipl/boot/libc.c), which the 1.17.1 version doesn't need.
Yes, this bug has C breakage written all over it.
--
.''`. Stephen Powell
: :' :
`. `'`
`-
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
d Machine check interruptions are all disabled,
and the instruction address (i.e. disabled wait state code) is set
to X'32EE'.
--
.''`. Stephen Powell
: :' :
`. `'`
`-
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.or
On Fri, 15 Aug 2014 19:12:24 -0400 (EDT), Stephen Powell wrote:
>
> The full PSW is as follows:
>
>0002 8000 32EE
By the way, Hercules has an instruction tracing facility, similar to
the CP TRACE command on z/VM. The "T" command, along with the
ruction"
starts at storage address 32EC, and is two bytes long, that means that
the updated instruction address in the PSW at the time of the program
interruption will be 32EE, which is the value used in the disabled wait
PSW.
--
.''`. Stephen Powell
: :' :
`.
a: a7 f4 00 01 j 32ec
32ee: 07 07 nopr%r7
-
Obviously bad code. Something is terribly wrong here. The complete eckd2.list
file is available for download at
http://users.wowway.com/~zlinuxman/zipl/eckd2.list
It was compiled w
ne the external
interruption code.
I do worry, though, about this being a more general problem. What about
the interrupt handler in the Linux kernel? Or any other portion of the
kernel that needs to examine (or change) data in real page 0 for
whatever reason?
--
.'&#
Package: linux-image-2.6.26-2-s390
Version: 2.6.26-15
Severity: critical
This particular Linux kernel image will not boot on a virtual machine in ESA
mode under z/VM. I have not tried other platforms (LPAR, for example).
Here is the boot log:
--
Booting default (debian)...
[0.
34 matches
Mail list logo
