Re: Release testing and you
On Mon, May 07, 2012 at 06:00:37PM -0300, gustavo panizzo wrote:
> today's image
>
> ┌───┤ Detecting link on eth0; please wait... ├┐
> │ │
> │ 100% [
> 243.520556] Unable to handle kernel NULL pointer dereference
> 243.601245] tsk->{mm,active_mm}->context = 01a0 │
> 14;10H[ 243.691289] tsk->{mm,active_mm}->pgd = f8001d2c6000│
> [ 243.767267] Kernel panic - not syncing: Aiee, killing interrupt handler! │
> [ 243.855403] Call Trace: │
> [ 243.887548] [0045dcd4] do_exit+0x94/0x708 │
> [ 243.950577] [00427550] die_if_kernel+0x2a0/0x2c8┘
> [ 244.021620] [00768c84] unhandled_fault+0x8c/0x98
> [ 244.092659] [0076936c] do_sparc64_fault+0x6dc/0x780
> [ 244.167130] [00407880] sparc64_realfault_common+0x10/0x20
> [ 244.248476] [10015680] gem_poll+0x9fc/0x1328 [sungem]
> [ 244.325234] [00697110] net_rx_action+0x9c/0x234
> [ 244.395124] [004607f0] __do_softirq+0xdc/0x1c4
> [ 244.463891] [0042a76c] do_softirq+0x54/0x80
> [ 244.529196] [00460a6c] irq_exit+0x38/0x94
> [ 244.592231] [0042df38] timer_interrupt+0x90/0xa8
> [ 244.663271] [004209d4] tl0_irq14+0x14/0x20
> [ 244.727450] [0043772c] touch_nmi_watchdog+0x0/0x34
> [ 244.800780] [008f07e4] start_kernel+0x390/0x3a0
> [ 244.870674] [00750b88] tlb_fixup_done+0x80/0x88
> [ 244.940562] [] (null)
> [ 245.001307] Press Stop-A (L1-A) to return to the boot prom
>
> i've boot with diag-switch? = true and hw looks good
> box is running 2.6.28, i will apply the same config to 3.2 and check
> if it boots
Ok, I can't find anything similar, so I filed
http://bugs.debian.org/671895 for it. Please post the results of your
tests there (by mailing 671...@bugs.debian.org). I'm going to poke
around to see if I can better pinpoint the failure location.
Best regards,
--
Jurij Smakov ju...@wooyd.org
Key: http://www.wooyd.org/pgpkey/ KeyID: C99E03CC
--
To UNSUBSCRIBE, email to debian-sparc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20120507215545.ga5...@wooyd.org
Re: Release testing and you
today's image
┌───┤ Detecting link on eth0; please wait... ├┐
│ │
│ 100% [
243.520556] Unable to handle kernel NULL pointer dereference
243.601245] tsk->{mm,active_mm}->context = 01a0 │
14;10H[ 243.691289] tsk->{mm,active_mm}->pgd = f8001d2c6000│
[ 243.767267] Kernel panic - not syncing: Aiee, killing interrupt handler! │
[ 243.855403] Call Trace: │
[ 243.887548] [0045dcd4] do_exit+0x94/0x708 │
[ 243.950577] [00427550] die_if_kernel+0x2a0/0x2c8┘
[ 244.021620] [00768c84] unhandled_fault+0x8c/0x98
[ 244.092659] [0076936c] do_sparc64_fault+0x6dc/0x780
[ 244.167130] [00407880] sparc64_realfault_common+0x10/0x20
[ 244.248476] [10015680] gem_poll+0x9fc/0x1328 [sungem]
[ 244.325234] [00697110] net_rx_action+0x9c/0x234
[ 244.395124] [004607f0] __do_softirq+0xdc/0x1c4
[ 244.463891] [0042a76c] do_softirq+0x54/0x80
[ 244.529196] [00460a6c] irq_exit+0x38/0x94
[ 244.592231] [0042df38] timer_interrupt+0x90/0xa8
[ 244.663271] [004209d4] tl0_irq14+0x14/0x20
[ 244.727450] [0043772c] touch_nmi_watchdog+0x0/0x34
[ 244.800780] [008f07e4] start_kernel+0x390/0x3a0
[ 244.870674] [00750b88] tlb_fixup_done+0x80/0x88
[ 244.940562] [] (null)
[ 245.001307] Press Stop-A (L1-A) to return to the boot prom
i've boot with diag-switch? = true and hw looks good
box is running 2.6.28, i will apply the same config to 3.2 and check
if it boots
On Mon, May 07, 2012 at 08:34:02PM +0100, Jurij Smakov wrote:
> On Mon, May 07, 2012 at 04:16:49PM -0300, gustavo panizzo wrote:
> > today i take the dust off my netra, to install debian on it
> >
> > i took the daily image of the d-i
> > http://ftp.br.debian.org/debian/dists/testing/main/installer-sparc/20110106+b1/images/netboot/boot.img
>
> As the date in the URL indicates, this is a *very* old image.
>
> In order to get the dailies you should go to
>
> http://www.debian.org/devel/debian-installer/
>
> in particular, for the netboot image:
>
> http://d-i.debian.org/daily-images/sparc/daily/netboot/
>
> Daily installer images are not distributed via mirror network, so this
> is the only place you can download it from.
>
> Thanks for testing, please let me know if you encounter any problems.
>
> And even if it's a success, please file an installation report.
>
> The d-i alpha1 for wheezy should be available in a couple of days, if
> you could test that it would be great as well.
>
> > it boots ok, but at some point the installer throws this
> > exactly after load network and usb storage modules
> >
> > [ 240.615830] Unable to handle kernel NULL pointer dereference
> >
> > [ 240.690242] tsk->{mm,active_mm}->context = 05ce
> > [ 240.763550] tsk->{mm,active_mm}->pgd = f8001d1da000
> > [ 240.832583] Kernel panic - not syncing: Aiee, killing interrupt
> > handler!
> > [ 240.921118] Press Stop-A (L1-A) to return to the boot prom
> >
> > squeeze installer dies on the same point
> >
> > this is the hw
> >
> > Netra T1 200 (UltraSPARC-IIe 500MHz), No Keyboard
> > OpenBoot 4.0, 512 MB memory installed, Serial #507XXX58.
> > Ethernet address 0:X:ba:5:XX:ae, Host ID: 83XXXbae.
> >
> > i will try to boot the old gentoo that box has, then debootstrap to
> > see how it goes
> >
> >
> > On Sat, Apr 28, 2012 at 05:00:57PM +0100, Jurij Smakov wrote:
> > > Hello,
> > >
> > > We still have a bit to go before wheezy release, but I would like to
> > > once again remind of the importance of running testing/unstable to
> > > ensure acceptable quality of upcoming release. The key point is that
> > > if nobody runs wheezy and reports bugs, there is no chance for them to
> > > be fixed before release, so we can happily release with pretty severe
> > > problems (like http://bugs.debian.org/669905, which I accidentally
> > > discovered recently).
> > >
> > > Just to reming how the system works: a new version of the package is
> > > unloaded to unstable (a.k.a. sid), typically spends about 10 days
> > > there, then propagates to testing (a.k.a. wheezy) if no new bugs have
> > > been reported against it (roughly). The version in testing will be
> > > released with wheezy, unless there is a release-critical bug filed
> > > against the package. The list of all release-critical bugs can be seen
> > > here:
> > >
> > > http://udd.debian.org/bugs.cgi?release=wheezy&patch=&pending=&security=ign&wontfix=&upstream=&unreproducible=&forwarded=&claimed=&deferred=¬main=ign¬wheezy=ign&base=&standard=&merged=ign&done=&outdatedwheezy=&outdatedsid=&needmig=&newerubuntu=&fnewer=&fnewerval=7&rc=1&sortby=s
Re: Release testing and you
On Mon, May 07, 2012 at 04:16:49PM -0300, gustavo panizzo wrote:
> today i take the dust off my netra, to install debian on it
>
> i took the daily image of the d-i
> http://ftp.br.debian.org/debian/dists/testing/main/installer-sparc/20110106+b1/images/netboot/boot.img
As the date in the URL indicates, this is a *very* old image.
In order to get the dailies you should go to
http://www.debian.org/devel/debian-installer/
in particular, for the netboot image:
http://d-i.debian.org/daily-images/sparc/daily/netboot/
Daily installer images are not distributed via mirror network, so this
is the only place you can download it from.
Thanks for testing, please let me know if you encounter any problems.
And even if it's a success, please file an installation report.
The d-i alpha1 for wheezy should be available in a couple of days, if
you could test that it would be great as well.
> it boots ok, but at some point the installer throws this
> exactly after load network and usb storage modules
>
> [ 240.615830] Unable to handle kernel NULL pointer dereference
>
> [ 240.690242] tsk->{mm,active_mm}->context = 05ce
> [ 240.763550] tsk->{mm,active_mm}->pgd = f8001d1da000
> [ 240.832583] Kernel panic - not syncing: Aiee, killing interrupt
> handler!
> [ 240.921118] Press Stop-A (L1-A) to return to the boot prom
>
> squeeze installer dies on the same point
>
> this is the hw
>
> Netra T1 200 (UltraSPARC-IIe 500MHz), No Keyboard
> OpenBoot 4.0, 512 MB memory installed, Serial #507XXX58.
> Ethernet address 0:X:ba:5:XX:ae, Host ID: 83XXXbae.
>
> i will try to boot the old gentoo that box has, then debootstrap to
> see how it goes
>
>
> On Sat, Apr 28, 2012 at 05:00:57PM +0100, Jurij Smakov wrote:
> > Hello,
> >
> > We still have a bit to go before wheezy release, but I would like to
> > once again remind of the importance of running testing/unstable to
> > ensure acceptable quality of upcoming release. The key point is that
> > if nobody runs wheezy and reports bugs, there is no chance for them to
> > be fixed before release, so we can happily release with pretty severe
> > problems (like http://bugs.debian.org/669905, which I accidentally
> > discovered recently).
> >
> > Just to reming how the system works: a new version of the package is
> > unloaded to unstable (a.k.a. sid), typically spends about 10 days
> > there, then propagates to testing (a.k.a. wheezy) if no new bugs have
> > been reported against it (roughly). The version in testing will be
> > released with wheezy, unless there is a release-critical bug filed
> > against the package. The list of all release-critical bugs can be seen
> > here:
> >
> > http://udd.debian.org/bugs.cgi?release=wheezy&patch=&pending=&security=ign&wontfix=&upstream=&unreproducible=&forwarded=&claimed=&deferred=¬main=ign¬wheezy=ign&base=&standard=&merged=ign&done=&outdatedwheezy=&outdatedsid=&needmig=&newerubuntu=&fnewer=&fnewerval=7&rc=1&sortby=source&sorto=asc&cpopcon=1&cseverity=1&ctags=1
> >
> > If a particular bug (affecting wheezy) that you are aware of is not on
> > this list, it means that it will be ignored for release purposes, and
> > the buggy version of the package is going to be released when the time
> > comes. So, if you are interested in improving the quality of the next
> > release and have a possibility to run wheezy on some sparc box, please
> > do so and report the bugs that you find, especially the ones which
> > make packages unusable.
> >
> > The debian-boot team is currently in the process of preparing the
> > alpha version of wheezy installer which, I expect, will be made
> > available in the next few days. I would encourage anyone with spare
> > resources to test this installer and file an installation report (see
> > http://d-i.alioth.debian.org/manual/en.i386/ch05s04.html#submit-bug
> > for instructions). Testing daily/weekly installer builds available at
> > http://www.debian.org/devel/debian-installer/ is another excellent way
> > to make sure that it's working for your hardware.
> >
> > Best regards,
> > --
> > Jurij Smakov ju...@wooyd.org
> > Key: http://www.wooyd.org/pgpkey/ KeyID: C99E03CC
> >
> >
> > --
> > To UNSUBSCRIBE, email to debian-sparc-requ...@lists.debian.org
> > with a subject of "unsubscribe". Trouble? Contact
> > listmas...@lists.debian.org
> > Archive: http://lists.debian.org/20120428160057.ga4...@wooyd.org
>
> --
> 1AE0 322E B8F7 4717 BDEA BF1D 44BB 1BA7 9F6C 6333
--
Jurij Smakov ju...@wooyd.org
Key: http://www.wooyd.org/pgpkey/ KeyID: C99E03CC
--
To UNSUBSCRIBE, email to debian-sparc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20120507193402.ga3...@wooyd.org
Re: Release testing and you
today i take the dust off my netra, to install debian on it
i took the daily image of the d-i
http://ftp.br.debian.org/debian/dists/testing/main/installer-sparc/20110106+b1/images/netboot/boot.img
it boots ok, but at some point the installer throws this
exactly after load network and usb storage modules
[ 240.615830] Unable to handle kernel NULL pointer dereference
[ 240.690242] tsk->{mm,active_mm}->context = 05ce
[ 240.763550] tsk->{mm,active_mm}->pgd = f8001d1da000
[ 240.832583] Kernel panic - not syncing: Aiee, killing interrupt
handler!
[ 240.921118] Press Stop-A (L1-A) to return to the boot prom
squeeze installer dies on the same point
this is the hw
Netra T1 200 (UltraSPARC-IIe 500MHz), No Keyboard
OpenBoot 4.0, 512 MB memory installed, Serial #507XXX58.
Ethernet address 0:X:ba:5:XX:ae, Host ID: 83XXXbae.
i will try to boot the old gentoo that box has, then debootstrap to
see how it goes
On Sat, Apr 28, 2012 at 05:00:57PM +0100, Jurij Smakov wrote:
> Hello,
>
> We still have a bit to go before wheezy release, but I would like to
> once again remind of the importance of running testing/unstable to
> ensure acceptable quality of upcoming release. The key point is that
> if nobody runs wheezy and reports bugs, there is no chance for them to
> be fixed before release, so we can happily release with pretty severe
> problems (like http://bugs.debian.org/669905, which I accidentally
> discovered recently).
>
> Just to reming how the system works: a new version of the package is
> unloaded to unstable (a.k.a. sid), typically spends about 10 days
> there, then propagates to testing (a.k.a. wheezy) if no new bugs have
> been reported against it (roughly). The version in testing will be
> released with wheezy, unless there is a release-critical bug filed
> against the package. The list of all release-critical bugs can be seen
> here:
>
> http://udd.debian.org/bugs.cgi?release=wheezy&patch=&pending=&security=ign&wontfix=&upstream=&unreproducible=&forwarded=&claimed=&deferred=¬main=ign¬wheezy=ign&base=&standard=&merged=ign&done=&outdatedwheezy=&outdatedsid=&needmig=&newerubuntu=&fnewer=&fnewerval=7&rc=1&sortby=source&sorto=asc&cpopcon=1&cseverity=1&ctags=1
>
> If a particular bug (affecting wheezy) that you are aware of is not on
> this list, it means that it will be ignored for release purposes, and
> the buggy version of the package is going to be released when the time
> comes. So, if you are interested in improving the quality of the next
> release and have a possibility to run wheezy on some sparc box, please
> do so and report the bugs that you find, especially the ones which
> make packages unusable.
>
> The debian-boot team is currently in the process of preparing the
> alpha version of wheezy installer which, I expect, will be made
> available in the next few days. I would encourage anyone with spare
> resources to test this installer and file an installation report (see
> http://d-i.alioth.debian.org/manual/en.i386/ch05s04.html#submit-bug
> for instructions). Testing daily/weekly installer builds available at
> http://www.debian.org/devel/debian-installer/ is another excellent way
> to make sure that it's working for your hardware.
>
> Best regards,
> --
> Jurij Smakov ju...@wooyd.org
> Key: http://www.wooyd.org/pgpkey/ KeyID: C99E03CC
>
>
> --
> To UNSUBSCRIBE, email to debian-sparc-requ...@lists.debian.org
> with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
> Archive: http://lists.debian.org/20120428160057.ga4...@wooyd.org
--
1AE0 322E B8F7 4717 BDEA BF1D 44BB 1BA7 9F6C 6333
--
To UNSUBSCRIBE, email to debian-sparc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20120507191649.ga31...@io.zumbi.com.ar
Re: GCC 4.7 is now the default for x86 architectures
Matthias Klose dixit: >GCC 4.7 is now the default for x86 architectures for all frontends except the D >frontends, including KFreeBSD and the Hurd. How are the plans for other architectures? The m68k status (which obviously can’t influence the release decisions) is as follows: gcc-4.7 builds, last time I looked gcj-4.7 didn’t but it is currently building again (so let’s see whether it does this time); gcc-4.6 and gnat-4.6 are getting development and bugfixes (I’ve queued up some patches, but am not entirely ready with all of them, plus some for binutils and gdb), and I’ve asked for help re. the gcj-4.4/gcj-4.6 recent problems. But nothing has tested gcj-4.7, and I fear of new and old bugs… so I’d rather not switch default compiler to it anytime soon. As for gcc-4.7 in general: a friend (authoring an ObjC framework _and_ runtime) told me that it dropped support for an old method of doing things while not fulfilling the promise to get the new method of doing it (don’t exactly remember what it was, /msg js on freenode for details) fixed, with the effect that gobjc-4.7 is virtually useless/broken. This is hearsay, but ask him for details, and check them against reality. bye, //mirabilos -- Yay for having to rewrite other people's Bash scripts because bash suddenly stopped supporting the bash extensions they make use of -- Tonnerre Lombard in #nosec -- To UNSUBSCRIBE, email to debian-sparc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/pine.bsm.4.64l.1205071730550.28...@herc.mirbsd.org
Re: GCC 4.7 is now the default for x86 architectures
On 07.05.2012 19:35, Thorsten Glaser wrote: > Matthias Klose dixit: > >> GCC 4.7 is now the default for x86 architectures for all frontends except >> the D >> frontends, including KFreeBSD and the Hurd. > > How are the plans for other architectures? I don't have plans to change any other architectures. If a port is not a release architectures (and port maintainers don't plan to make it a release architecture), people can change the default at any time from my point of view. > As for gcc-4.7 in general: a friend (authoring an ObjC framework _and_ > runtime) told me that it dropped support for an old method of doing > things while not fulfilling the promise to get the new method of doing > it (don’t exactly remember what it was, /msg js on freenode for details) > fixed, with the effect that gobjc-4.7 is virtually useless/broken. > > This is hearsay, but ask him for details, and check them against > reality. I didn't rely on hearsay, but did ask the GNUstep maintainers for feedback. Please join the Debian GNUstep package maintainers ML if you want to add something, or review the past discussion. Matthias -- To UNSUBSCRIBE, email to debian-sparc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4fa80a89.8070...@debian.org
GCC 4.7 is now the default for x86 architectures
GCC 4.7 is now the default for x86 architectures for all frontends except the D frontends, including KFreeBSD and the Hurd. There are still some build failures which need to be addressed. Out of the ~350 bugs filed, more than the half are fixed, another quarter has patches available, and the remaining quarter isn't blocking any other 4.7 build failures. Many thanks to the patch submitters and NMUers, including Cyril Brulebois, Gregor Herrmann, Paul Tagliamonte for the fixes. This will add one more transition for x86 (libobjc3 -> libobjc4), which needs starting with uploads of some GNUstep base packages. The D v2 frontend is likely to be updated to 4.7 before the freeze (no build dependencies). Matthias -- To UNSUBSCRIBE, email to debian-sparc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4fa7ffd8.9010...@debian.org
