On Jan 27, 2010, at 3:36 AM, Frans Pop wrote:
> Frans Pop wrote:
>> I've packaged the new upstream version. Most debian/patches could be
>> refreshed or updated without too many problems. I've also updated the
>> packaging and fixed some BRs.
>
> I found I'd missed updating the files to be insta
On Mar 18, 2009, at 7:44 AM, Frans Pop wrote:
Adam,
Can you test if the following patch on top of the Debian 2.6.26 kernel
fixes the problem for you?
http://lkml.org/lkml/2009/3/18/79
Please CC me when you reply!
This appears to fix the problem, in that I get much farther and then
get st
Actually, a 100 Hz timer seems to work. Then I hang because I didn't
load the DASD driver, but I think that's very likely just a problem
with my generated RAMDISK. So my recommendation would be to use a
100Hz timer pop for s390 31-bit at least. I wonder if this has
anything to do with tr
Turning off the timer gets slightly farther, but hangs at 038c18,
which is in raise_softirq .
So that's not it.
Next step: turning the timer back down to 100 Hz. Doubt that's going
to help.
Adam
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "un
Well, my custom kernel (in which, on a hunch, I turned off timer
ticks) is still building, but I now have this diagnostic information:
If you (under VM) do a CP D P ALL you see that you're generally in
scheduler_tick, sometimes in account_user_time_scaled, sometimes
tick_switch_to_oneshot.
Fails on released Lenny as well.
I'm installing the kernel sources now to see if I can, in fact, build
a working 2.6.26 in an otherwise-Lenny environment.
If I get something that works on FLEX-ES I'd like for someone to try
it on Hercules.
Adam
--
To UNSUBSCRIBE, email to debian-bugs-d
It fails the same way with Lenny rc2 as previous versions did.
Adam
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
I've tried with the 1/19 nightly build.
I got slightly farther once, in that the last message was that I had
one configured and no standby CPUs, but I'm still getting the hang.
Adam
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Troub
On Jan 9, 2009, at 1:20 PM, Frans Pop wrote:
reassign 511334 linux-2.6 2.6.26-12
thanks
On Friday 09 January 2009, Adam Thornton wrote:
S390 boot fails (sometimes just after detecting memory, sometimes
after
detecting devices) on z/VM 5.2 and a Flex-ES machine.
Since there are reports of
Package: debian-installer
Severity: important
S390 boot fails (sometimes just after detecting memory, sometimes after
detecting devices) on z/VM 5.2 and a Flex-ES machine.
Since there are reports of d-i working on z9 boxes, I suspect the issue
is that the kernel is built to exploit later System z
On Oct 8, 2007, at 10:12 AM, Frans Pop wrote:
Adding the dasd= boot parameter did not help - it seems to be
ignored in our
initrds; changing /etc/fstab to use /dev/disk/by-path devices
consistently
does result in a correct boot.
I'll consult with other Debian people how we want to resolve thi
On Mar 22, 2007, at 1:09 PM, Kapil Hari Paranjape wrote:
On Thu, 22 Mar 2007, Martin Michlmayr wrote:
You can simply start a 2nd connection via SSH and then open a
terminal.
Perhaps I'm mistaken. I did try this as "installer" with password
"install" but I seem to recall that I was logged out.
Package: debian-installer
Severity: important
In earlier versions of the Sarge installer, when you selected a qeth
device which was a HiperSockets transport (Layer 3 only) coupled to a VM
guest LAN (or, probably, to a real HiperSockets trans-LPAR connector,
but I don't have any way to test that),
Package: netinst
Version: base-network
Severity: important
Using etch Beta 2: installation goes OK, but network device is not picked
up on reboot. This seems to be because "alias eth0 qeth" is commented out
in /etc/modules.conf, and although "qeth" is present in /etc/modules, it is
not loaded a
We should probably decide what the cutoff point should be, since it
looks like 1.39 will be a database change from 1.38.
Now, I myself would really like 1.39 since it implements pool
migration, which is important to my installation. However, I think
1.38.2 is really the bottom edge of what
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Dec 22, 2005, at 3:07 PM, Joey Hess wrote:
You don't say what version of the installer you were using.
I imagine that the syslog would tell us why it's choosing the
kernel it
is choosing.
Which was the clue I needed.
CMS search order.
I w
Package: install
Severity: critical
Justification: breaks the whole system
At some point in the last few weeks, Debian-installer has started
installing the s390x kernel on s390 systems; I noticed this today, 22
December; this is the first system I have installed since the 17
December 2005 3.1r1
Package: install
Severity: important
When you install Sarge on a zSeries (64-bit) system, the s390x (64-bit)
kernel is installed by default. Superficially this seems like the right
behavior. However, then the cpint module doesn't work, and more
generally, we don't have a full 64-bit s390x port.
18 matches
Mail list logo
