Re: Bug#630424: Maybe a Problem with "tip22"
On Wed, 2011-07-06 at 18:48 +0200, Guido Günther wrote: > Hi Dann, > On Tue, Jul 05, 2011 at 05:29:04PM -0600, dann frazier wrote: [...] > > 3) Finally, we need to do a d-i rebuild (which we usually do with > > each point release anyway). You can coordinate with me on that. > > Thanks for the heads up, besides 2) it's what Adam suggested: > > http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=631007 That d-i rebuild, including the updated arcboot package, was included in 6.0.3, so I guess we can close this now... Regards, Adam -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1327353109.25541.2.ca...@jacala.jungle.funky-badger.org
Bug#630424: Maybe a Problem with "tip22"
Hi Dann, On Tue, Jul 05, 2011 at 05:29:04PM -0600, dann frazier wrote: > On Sun, Jun 19, 2011 at 01:35:28PM +0200, Guido Günther wrote: > > On Sun, Jun 19, 2011 at 02:39:05AM -0700, Edwin Kwan wrote: > > > Hi Guido, > > > > > > Your package tested out OK. I only have an Indy. So I only tried > > > "tip22". > > Thanks for testing! I've uploaded a new version to unstable. > > > > I'm not sure what's the correct procedure to get the installer images > > rebuilt with that for the next point release though. Can somebody from > > debian-boot shed some light on this? I assume it includes uploading a > > new arcboot version to stable-proposed-updates but is that enough? > > Cheers, > > -- Guido > > I believe what needs to be done is: > 1) Propose an arcboot update for squeeze. You can coordinate this > with the stable release team on debian-release@l.d.o. Please > include a debdiff vs. current squeeze. > 2) Once that's accepted, we need to ask the mips buildd maintainer to > ensure this update gets included in the squeeze chroot(s). > 3) Finally, we need to do a d-i rebuild (which we usually do with > each point release anyway). You can coordinate with me on that. Thanks for the heads up, besides 2) it's what Adam suggested: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=631007 I'll add that to the report. Cheers, -- Guido -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20110706164858.ga7...@bogon.sigxcpu.org
Bug#630424: Maybe a Problem with "tip22"
On Sun, Jun 19, 2011 at 01:35:28PM +0200, Guido Günther wrote: > On Sun, Jun 19, 2011 at 02:39:05AM -0700, Edwin Kwan wrote: > > Hi Guido, > > > > Your package tested out OK. I only have an Indy. So I only tried > > "tip22". > Thanks for testing! I've uploaded a new version to unstable. > > I'm not sure what's the correct procedure to get the installer images > rebuilt with that for the next point release though. Can somebody from > debian-boot shed some light on this? I assume it includes uploading a > new arcboot version to stable-proposed-updates but is that enough? > Cheers, > -- Guido I believe what needs to be done is: 1) Propose an arcboot update for squeeze. You can coordinate this with the stable release team on debian-release@l.d.o. Please include a debdiff vs. current squeeze. 2) Once that's accepted, we need to ask the mips buildd maintainer to ensure this update gets included in the squeeze chroot(s). 3) Finally, we need to do a d-i rebuild (which we usually do with each point release anyway). You can coordinate with me on that. -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20110705232904.ga31...@dannf.org
Bug#630424: Maybe a Problem with "tip22"
On Sun, Jun 19, 2011 at 02:39:05AM -0700, Edwin Kwan wrote: > Hi Guido, > > Your package tested out OK. I only have an Indy. So I only tried > "tip22". Thanks for testing! I've uploaded a new version to unstable. I'm not sure what's the correct procedure to get the installer images rebuilt with that for the next point release though. Can somebody from debian-boot shed some light on this? I assume it includes uploading a new arcboot version to stable-proposed-updates but is that enough? Cheers, -- Guido -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20110619113528.ga24...@bogon.sigxcpu.org
Bug#630424: Maybe a Problem with "tip22"
Hi Guido, Your package tested out OK. I only have an Indy. So I only tried "tip22". Thanks! Edwin Guido Günther wrote: On Thu, Jun 16, 2011 at 02:15:56AM -0700, Edwin Kwan wrote: I don't know whether the "kernel" and "initrd" were released separately. But I could extract them from the bad "netboot-boot.img" using "objdump" and "dd" by just looking for the symbols "__kernel_start", "__kernel_end" and "__rd_start", "__rd_end". I actually modified "ld.script.IP22" by putting "0x89702000" in the start address and built myself a netboot image using the extracted "kernel" and "initrd". I got to the installer screen but I don't need to reinstall right now. :) Geat, could you also try to use http://honk.sigxcpu.org/linux-mips/arcboot/tip22_0.3.14_mips.deb to build that image? This should fix the issue. It also fixes the messed up addresses on IP32. Cheers, -- Guido Guido Günther wrote: Hi, On Tue, Jun 14, 2011 at 02:22:17AM -0700, Edwin Kwan wrote: Hi, The screen shot in Attilio's bug report was done by me on my Indy. I am not experienced in this beginning of the universe kind of code. But I found the following clues which may be useful. I can reproduce the problem here now. A the same kernel+initrd that works with 0.3.12 doesn't with 0.3.13 (unlucky number it seems). I try come up with a patch during the next couple of days. BTW can I directlry fetch the initrd and kernel that was used to build: http://ftp.nl.debian.org/debian/dists/squeeze/main/installer-mips/current/images/r4k-ip22/netboot-boot.img I thought these used to be on the mirrors but can't seem to find them. Cheers, -- Guido -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4dfdc3b9.4080...@stanfordalumni.org
Bug#630424: Maybe a Problem with "tip22"
On Thu, Jun 16, 2011 at 02:15:56AM -0700, Edwin Kwan wrote: > I don't know whether the "kernel" and "initrd" were released > separately. But I could extract them from the bad > "netboot-boot.img" using "objdump" and "dd" by just looking for the > symbols "__kernel_start", "__kernel_end" and "__rd_start", > "__rd_end". I actually modified "ld.script.IP22" by putting > "0x89702000" in the start address and built myself a netboot image > using the extracted "kernel" and "initrd". I got to the installer > screen but I don't need to reinstall right now. :) Geat, could you also try to use http://honk.sigxcpu.org/linux-mips/arcboot/tip22_0.3.14_mips.deb to build that image? This should fix the issue. It also fixes the messed up addresses on IP32. Cheers, -- Guido > > Guido Günther wrote: > >Hi, > >On Tue, Jun 14, 2011 at 02:22:17AM -0700, Edwin Kwan wrote: > >>Hi, > >> > >>The screen shot in Attilio's bug report was done by me on my Indy. > >>I am not experienced in this beginning of the universe kind of code. > >>But I found the following clues which may be useful. > >I can reproduce the problem here now. A the same kernel+initrd that > >works with 0.3.12 doesn't with 0.3.13 (unlucky number it seems). I try > >come up with a patch during the next couple of days. > > > >BTW can I directlry fetch the initrd and kernel that was used to build: > > > > > > http://ftp.nl.debian.org/debian/dists/squeeze/main/installer-mips/current/images/r4k-ip22/netboot-boot.img > > > > > >I thought these used to be on the mirrors but can't seem to find them. > >Cheers, > > -- Guido > > > -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20110616215111.ga8...@bogon.sigxcpu.org
Bug#630424: Maybe a Problem with "tip22"
I don't know whether the "kernel" and "initrd" were released separately. But I could extract them from the bad "netboot-boot.img" using "objdump" and "dd" by just looking for the symbols "__kernel_start", "__kernel_end" and "__rd_start", "__rd_end". I actually modified "ld.script.IP22" by putting "0x89702000" in the start address and built myself a netboot image using the extracted "kernel" and "initrd". I got to the installer screen but I don't need to reinstall right now. :) Guido Günther wrote: Hi, On Tue, Jun 14, 2011 at 02:22:17AM -0700, Edwin Kwan wrote: Hi, The screen shot in Attilio's bug report was done by me on my Indy. I am not experienced in this beginning of the universe kind of code. But I found the following clues which may be useful. I can reproduce the problem here now. A the same kernel+initrd that works with 0.3.12 doesn't with 0.3.13 (unlucky number it seems). I try come up with a patch during the next couple of days. BTW can I directlry fetch the initrd and kernel that was used to build: http://ftp.nl.debian.org/debian/dists/squeeze/main/installer-mips/current/images/r4k-ip22/netboot-boot.img I thought these used to be on the mirrors but can't seem to find them. Cheers, -- Guido -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4df9c9cc.9060...@stanfordalumni.org
Bug#630424: Maybe a Problem with "tip22"
Hi, On Tue, Jun 14, 2011 at 02:22:17AM -0700, Edwin Kwan wrote: > Hi, > > The screen shot in Attilio's bug report was done by me on my Indy. > I am not experienced in this beginning of the universe kind of code. > But I found the following clues which may be useful. I can reproduce the problem here now. A the same kernel+initrd that works with 0.3.12 doesn't with 0.3.13 (unlucky number it seems). I try come up with a patch during the next couple of days. BTW can I directlry fetch the initrd and kernel that was used to build: http://ftp.nl.debian.org/debian/dists/squeeze/main/installer-mips/current/images/r4k-ip22/netboot-boot.img I thought these used to be on the mirrors but can't seem to find them. Cheers, -- Guido -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20110615205556.ga19...@bogon.sigxcpu.org
Bug#630424: Maybe a Problem with "tip22"
Hi,
The screen shot in Attilio's bug report was done by me on my Indy. I
am not experienced in this beginning of the universe kind of code. But
I found the following clues which may be useful.
Please refer to bug 452798
(http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=452798). Here is
message #15 from Guido:
On Sun, Nov 25, 2007 at 01:02:25PM +0100, Martin Michlmayr wrote:
How much work is 64 bit support?
It's not the 64bit support, things are simply not fitting into the
memory segment we use anymore:
Tip22 finds this memory map on my Indy:
1) Free Memory(3) segment found at (0x88002000,0x8874)
2) Free Memory(3) segment found at (0x8880,0x89002000)
3) Free Memory(3) segment found at (0x896f2000,0x9400)
(1) is where the running kernel + initrd goes. (2) is where we tell the
prom to download the tftpboot image to and (3) is lots of free space.
The 64bit kernel (7MB) is just so much bigger than the 32bit one.
Attached is a hack to get things booting again (so installer testing can
proceed). It puts the tftp boot file into (3) and the initrd into (2) -
it succesfully boots a kernel with an initramfs on my R5K Indy. I'll
have to change some of the reservation code so we don't waste so much
ram before I can fix this for real though.
Cheers,
-- Guido
Here is the "objdump -x" output of the "netboot-boot.img" from Lenny:
debbootL.img: file format ecoff-bigmips
debbootL.img
architecture: mips:3000, flags 0x0032:
EXEC_P, HAS_SYMS, HAS_LOCALS
start address 0x897020cc
Sections:
Idx Name Size VMA LMA File off
Algn
0 .text 1e00 89702000 89702000 00d0 2**4
CONTENTS, ALLOC, LOAD, CODE
1 .data 00ad1500 89703e00 89703e00 1ed0 2**4
CONTENTS, ALLOC, LOAD, DATA
2 .bss 0040 8a1d5300 8a1d5300 2**4
ALLOC
SYMBOL TABLE:
[ 0] e 897038b8 st 1 sc 1 indx f strcpy
[ 1] e 89703e00 st 1 sc 2 indx f kernel_load
[ 2] e 89702a30 st 1 sc 1 indx f ArcGetPeer
[ 3] e 897033a8 st 1 sc 1 indx f printf
[ 4] e 89703e34 st 1 sc 2 indx f stdout
[ 5] e 89702de4 st 1 sc 1 indx f vsprintf
[ 6] e 89703e00 st 1 sc 2 indx f _fdata
And here is the objdump -x" output of the "netboot-boot.img" from
Squeeze:
debbootS.img: file format ecoff-bigmips
debbootS.img
architecture: mips:3000, flags 0x0032:
EXEC_P, HAS_SYMS, HAS_LOCALS
start address 0x888020cc
Sections:
Idx Name Size VMA LMA File off
Algn
0 .text 1ea0 88802000 88802000 00d0 2**4
CONTENTS, ALLOC, LOAD, CODE
1 .data 00982140 88803ea0 88803ea0 1f70 2**4
CONTENTS, ALLOC, LOAD, DATA
2 .bss 0040 89185fe0 89185fe0 2**4
ALLOC
SYMBOL TABLE:
[ 0] e 88803914 st 1 sc 1 indx f strcpy
[ 1] e 88803ea0 st 1 sc 2 indx f kernel_load
[ 2] e 88802a30 st 1 sc 1 indx f ArcGetPeer
[ 3] e 888033a8 st 1 sc 1 indx f printf
[ 4] e 88803ed4 st 1 sc 2 indx f stdout
[ 5] e 88802de4 st 1 sc 1 indx f vsprintf
[ 6] e 88803ea0 st 1 sc 2 indx f _fdata
It seems to me that what Guido wanted was done in Lenny but not in
Squeeze. In the screen shot, "initrd" was being copied into 0x8880
by the Squeeze image. Wouldn't it overwrite the loader?
I downloaded the Squeeze "tip22" package, and here is the beginning of
the "ld.script.IP22" script:
OUTPUT_FORMAT("ecoff-bigmips")
OUTPUT_ARCH(mips)
ENTRY(_start)
SECTIONS
{
/* XXX: place the loader after the kernel */
. = 0x88802000;
/* read-only */
_text = .;/* Text and read-only data */
.text : {
_ftext = .;
*(.text .text.*)
*(.rodata*)
} =0
_etext = .; /* End of text section */
PROVIDE (etext = .);
Thanks for your help!
Edwin
--
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/4df72849.1020...@stanfordalumni.org
