Re: Linux 3.10-2-m68k FPU support

2013-10-20 Thread Ingo Jürgensmann
Am 20.10.2013 um 01:46 schrieb Thorsten Glaser :

> Geert Uytterhoeven dixit:
>> FPU emulation should be fine, AFAIK (never used it myself, though).
> Michael Schmitz dixit:
>> The docs are quite clearly out of date. From memory, there may be the odd FPU
> […]
>> Seeing as this code is crucial, I'd opt for putting it back in, and finding
> These two statements are “it should be fine but I don’t really know”
> and “this is important so put it back in, but I don’t remember details”.
> Together with what *is* currently in the documentation, this is
> *not* reassuring, and I *know* that FPU emulation code all across
> OSes (kernels and not) is a sore topic (even being kicked from
> some of them).
> My request for a clear statement still stands.

... and there's the statement from Adrian that it works without problems so 
far. 

> On the other hand, I cannot help but wonder how well it compares
> to whatever ARAnyM passes as FPU. I know ARAnyM doesn’t handle the
> 80/64bit precision switch at all (which is why we opted to not use
> that for Python), but I smell some sort of knob here… if the knob
> can be used to tweak between speed and correctness, I’d opt for
> correctness. (OK, BSD user speaking.) It’d probably be faster at
> runtime to fix ARAnyM instead but that’s a different upstream.


Hmmm... if Aranym is the problematic part in this story, then Aranym should be 
changed to reflect how real hardware works. There were a lot of Amiga 
accelerator cards built & sold without an FPU, although most of them have a 
socket for a 68881/2. It's been a matter of money back then and FPUs weren't 
widely used under AmigaOS. Except when you were doing 3D graphics and such. But 
then again one had no A1200 for this purpose but a A2/3/4000 with 68040 or 
68060s. But the majority of sold accelerator cards, I believe, was for A1200 
and 68030 just for the reason of money. 

At least I opt for providing a FPU enabled kernel. It doesn't need to be the 
default kernel, but we shouldn't exclude a number of users just because an 
emulator might have problems with FPU emulation. It's easier to change that 
piece of software than to change the piece of hardware. 

-- 
Ciao...//  Fon: 0381-2744150
  Ingo   \X/   http://blog.windfluechter.net


gpg pubkey:  http://www.juergensmann.de/ij_public_key.asc


--
To UNSUBSCRIBE, email to debian-68k-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/47287d89-8a3d-4377-a789-d6aed46b3...@2013.bluespice.org



Re: Linux 3.10-2-m68k FPU support

2013-10-20 Thread Geert Uytterhoeven
On Sun, Oct 20, 2013 at 10:04 AM, Ingo Jürgensmann
 wrote:
> Am 20.10.2013 um 01:46 schrieb Thorsten Glaser :
>> Geert Uytterhoeven dixit:
>>> FPU emulation should be fine, AFAIK (never used it myself, though).
>> Michael Schmitz dixit:
>>> The docs are quite clearly out of date. From memory, there may be the odd 
>>> FPU
>> […]
>>> Seeing as this code is crucial, I'd opt for putting it back in, and finding
>> These two statements are “it should be fine but I don’t really know”
>> and “this is important so put it back in, but I don’t remember details”.
>> Together with what *is* currently in the documentation, this is
>> *not* reassuring, and I *know* that FPU emulation code all across
>> OSes (kernels and not) is a sore topic (even being kicked from
>> some of them).
>> My request for a clear statement still stands.
>
> ... and there's the statement from Adrian that it works without problems so 
> far.

Indeed. The emulation may be incomplete, but for most people it's useable,
and definitely better than nothing.

Furthermore, for people running Debian on their FPU-less machines before,
the new kernel image is definitely a regression, so it warrants re-enabling
FPU emulation to fix this.

>> On the other hand, I cannot help but wonder how well it compares
>> to whatever ARAnyM passes as FPU. I know ARAnyM doesn’t handle the
>> 80/64bit precision switch at all (which is why we opted to not use
>> that for Python), but I smell some sort of knob here… if the knob
>> can be used to tweak between speed and correctness, I’d opt for
>> correctness. (OK, BSD user speaking.) It’d probably be faster at
>> runtime to fix ARAnyM instead but that’s a different upstream.
>
> Hmmm... if Aranym is the problematic part in this story, then Aranym should 
> be changed to reflect how real hardware works. There were a lot of Amiga 
> accelerator cards built & sold without an FPU, although most of them have a 
> socket for a 68881/2. It's been a matter of money back then and FPUs weren't 
> widely used under AmigaOS. Except when you were doing 3D graphics and such. 
> But then again one had no A1200 for this purpose but a A2/3/4000 with 68040 
> or 68060s. But the majority of sold accelerator cards, I believe, was for 
> A1200 and 68030 just for the reason of money.
>
> At least I opt for providing a FPU enabled kernel. It doesn't need to be the 
> default kernel, but we shouldn't exclude a number of users just because an 
> emulator might have problems with FPU emulation. It's easier to change that 
> piece of software than to change the piece of hardware.

Nevertheless, FPU emulation in ARAnyM is something different. ARAnyM
is an emulator that emulates a full 68040, incl. FPU. So as far as the Linux
kernel is concerned, no in-kernel FPU emulation is involved.

Gr{oetje,eeting}s,

Geert

--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- ge...@linux-m68k.org

In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds


--
To UNSUBSCRIBE, email to debian-68k-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/camuhmdxfgnscptmote+pt-xg2dshguv4dapjtjhg60epu7y...@mail.gmail.com



Linux 3.1-2-m68k config (was: Re: Linux 3.10-2-m68k FPU support)

2013-10-20 Thread Geert Uytterhoeven
On Sat, Oct 19, 2013 at 6:13 PM, Geert Uytterhoeven
 wrote:
> Doh, I really should have an in-depth look at your .config, and compare it to
> multi_defconfig (which does need more stripping!), to catch these things.

This is the difference between my multi_defconfig and config-3.10-2-m68k.
Big differences are due to many drivers being modular in the initrd for the
Debian kernel, which I want to avoid for my defconfigs, for hassle-free
testing.

What sticks out:
  - Lack of FPU emulation support in the Debian kernel,
  - CONFIG_COMPAT_BRK is not enabled in the Debian kernel, which
is needed if you want to boot the good old filesys-ELF-2.0.x-1400K-2.gz
ramdisk (probably not with the Debian kernel, as all your drivers are in
modules?)

I have to look a bit more at it, but all help is welcome.

Apart from that, (probably both) configs need more stripping in the common
part. I want to have bootable (i.e. < 4 MiB) defconfig kernels.

! multi_defconfig -+
! config-3.10-2-m68k + |
!| |
! CONFIG_9P_FS : m .
! CONFIG_9P_FSCACHE: y .
! CONFIG_9P_FS_POSIX_ACL   : y .
! CONFIG_A2065 : m y
! CONFIG_A2091_SCSI: m y
! CONFIG_A3000_SCSI: m y
! CONFIG_ADB_MACIISI   : y n
! CONFIG_AMD_PHY   : m .
! CONFIG_AMIGA_FLOPPY  : m y
! CONFIG_APNE  : m y
! CONFIG_ARIADNE   : m y
! CONFIG_ASYNC_RAID6_TEST  : n m
! CONFIG_AT803X_PHY: m .
! CONFIG_ATARILANCE: m y
! CONFIG_ATARI_FLOPPY  : m y
! CONFIG_ATARI_SCSI: m y
! CONFIG_AUFS_BDEV_LOOP: y .
! CONFIG_AUFS_BRANCH_MAX_127   : y .
! CONFIG_AUFS_BR_FUSE  : y .
! CONFIG_AUFS_BR_HFSPLUS   : y .
! CONFIG_AUFS_EXPORT   : y .
! CONFIG_AUFS_FS   : m .
! CONFIG_AUFS_POLL : y .
! CONFIG_AUFS_SBILIST  : y .
! CONFIG_BATMAN_ADV: n m
! CONFIG_BATMAN_ADV_BLA: . y
! CONFIG_BATMAN_ADV_DAT: . y
! CONFIG_BATMAN_ADV_NC : . y
! CONFIG_BCACHE: m n
! CONFIG_BCM87XX_PHY   : m .
! CONFIG_BLK_DEV_BUDDHA: m y
! CONFIG_BLK_DEV_CRYPTOLOOP: n m
! CONFIG_BLK_DEV_DRBD  : n m
! CONFIG_BLK_DEV_FALCON_IDE: m y
! CONFIG_BLK_DEV_GAYLE : m y
! CONFIG_BLK_DEV_IDECD : m y
! CONFIG_BLK_DEV_IDETAPE   : m n
! CONFIG_BLK_DEV_LOOP  : m y
! CONFIG_BLK_DEV_MAC_IDE   : m y
! CONFIG_BLK_DEV_OSD   : m .
! CONFIG_BLK_DEV_PLATFORM  : m n
! CONFIG_BLK_DEV_Q40IDE: m y
! CONFIG_BLK_DEV_RAM   : m y
! CONFIG_BLK_DEV_SD: m y
! CONFIG_BLK_DEV_SR: m y
! CONFIG_BONDING   : m n
! CONFIG_BOOTPARAM_HUNG_TASK_PANIC_VALUE   : 0 .
! CONFIG_BOOTPARAM_SOFTLOCKUP_PANIC_VALUE  : 0 .
! CONFIG_BOOT_PRINTK_DELAY : y .
! CONFIG_BRIDGE: m n
! CONFIG_BRIDGE_EBT_802_3  : m .
! CONFIG_BRIDGE_EBT_AMONG  : m .
! CONFIG_BRIDGE_EBT_ARP: m .
! CONFIG_BRIDGE_EBT_ARPREPLY   : m .
! CONFIG_BRIDGE_EBT_BROUTE : m .
! CONFIG_BRIDGE_EBT_DNAT   : m .
! CONFIG_BRIDGE_EBT_IP : m .
! CONFIG_BRIDGE_EBT_IP6: m .
! CONFIG_BRIDGE_EBT_LIMIT  : m .
! CONFIG_BRIDGE_EBT_LOG: m .
! CONFIG_BRIDGE_EBT_MARK   : m .
! CONFIG_BRIDGE_EBT_MARK_T : m .
! CONFIG_BRIDGE_EBT_NFLOG  : m .
! CONFIG_BRIDGE_EBT_PKTTYPE: m .
! CONFIG_BRIDGE_EBT_REDIRECT   : m .
! CONFIG_BRIDGE_EBT_SNAT   : m .
! CONFIG_BRIDGE_EBT_STP: m .
! CONFIG_BRIDGE_EBT_T_FILTER   : m .
! CONFIG_BRIDGE_EBT_T_NAT  : m .
! CONFIG_BRIDGE_EBT_ULOG   : m .
! CONFIG_BRIDGE_EBT_VLAN   : m .
! CONFIG_BRIDGE_IGMP_SNOOPING  : y .
! CONFIG_BRIDGE_NETFILTER  : y .
! CONFIG_BRIDGE_NF_EBTABLES: m .
! CONFIG_BRIDGE_VLAN_FILTERING : y .
! CONFIG_BROADCOM_PHY  : m .
! CONFIG_BTRFS_FS  : m n
! CONFIG_BTRFS_FS_POSIX_ACL: y .
! CONFIG_BVME6000_NET  : m y
! CONFIG_BVME6000_SCSI 

zsh vs. zsh-common version mismatch

2013-10-20 Thread Dirk Heinrichs
Hi,

there's a version mismatch between zsh (5.0.2-3) and its dependency zsh-common 
(5.0.2-5) which prevents zsh installation on m68k:

# LC_ALL=C apt-get install zsh
Reading package lists... Done
Building dependency tree   
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 zsh : Depends: zsh-common (= 5.0.2-3) but it is not going to be installed
E: Unable to correct problems, you have held broken packages.

Bye...

Dirk
-- 
Dirk Heinrichs 
Tel: +49 (0)2471 209385 | Mobil: +49 (0)176 34473913
GPG Public Key C2E467BB | Jabber: dirk.heinri...@altum.de


signature.asc
Description: This is a digitally signed message part.


Re: Linux 3.1-2-m68k config (was: Re: Linux 3.10-2-m68k FPU support)

2013-10-20 Thread Laurent Vivier

Le 20/10/2013 10:52, Geert Uytterhoeven a écrit :

On Sat, Oct 19, 2013 at 6:13 PM, Geert Uytterhoeven
 wrote:
[...]

Apart from that, (probably both) configs need more stripping in the common
part. I want to have bootable (i.e. < 4 MiB) defconfig kernels.

Moreover, a compressed kernel fitting on a floppy would be better : 
there is no USB port on this kind of machine, and the floppy is the 
easiest way to boot a kernel.


Do you think it is possible ?

(With 2.2 kernel we were able to put kernel AND ramdisk on the SAME 
floppy !)


Regards,
Laurent


--
To UNSUBSCRIBE, email to debian-68k-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/5263a185.1040...@vivier.eu



Re: Linux 3.1-2-m68k config (was: Re: Linux 3.10-2-m68k FPU support)

2013-10-20 Thread Geert Uytterhoeven
On Sun, Oct 20, 2013 at 11:25 AM, Laurent Vivier  wrote:
> Le 20/10/2013 10:52, Geert Uytterhoeven a écrit :
>>
>> On Sat, Oct 19, 2013 at 6:13 PM, Geert Uytterhoeven
>>  wrote:
>> [...]
>>
>>
>> Apart from that, (probably both) configs need more stripping in the common
>> part. I want to have bootable (i.e. < 4 MiB) defconfig kernels.
>>
> Moreover, a compressed kernel fitting on a floppy would be better : there is
> no USB port on this kind of machine, and the floppy is the easiest way to
> boot a kernel.
>
> Do you think it is possible ?

With a custom kerel, that should still be possible.
For a v3.12-rc6 mac_defconfig kernel, the figures are:

-rwxr-xr-x 1 geert geert 4873408 okt 20 11:31 /tmp/vmlinux*
-rwxr-xr-x 1 geert geert 2333743 okt 20 11:31 /tmp/vmlinux.gz*
-rwxr-xr-x 1 geert geert 2190667 okt 20 11:31 /tmp/vmlinux.bz2*
-rwxr-xr-x 1 geert geert 1802956 okt 20 11:31 /tmp/vmlinux.xz*

With some stripping, you should be able to fit (at least the xz version of)
the kernel on a floppy again.

> (With 2.2 kernel we were able to put kernel AND ramdisk on the SAME floppy
> !)

I know.

I even booted Linux with X and twm on an Amiga with 2 MiB chip RAM and
2 MiB Fast RAM (+ swap, of course). The uncompressed kernel fit
easily in 2 MiB.

Gr{oetje,eeting}s,

Geert

--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- ge...@linux-m68k.org

In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds


--
To UNSUBSCRIBE, email to debian-68k-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/camuhmdwdekfuhwz1gzh4h3ubt41vlvq0xys_mvpfrdrtbd6...@mail.gmail.com



Zero Divide in Kernel 3.12-rc4

2013-10-20 Thread Ingo Jürgensmann

Hi!

I'm testing the ESP SCSI driver port by Tuomas and Michael to 3.12-rc4 
and got now this kernel panic during heavy disk activity (apt-get 
dist-upgrade and parallel a rsync backup by BackupPC):


Debian GNU/Linux jessie/sid spice ttyS0

spice login: [77568.07] *** ZERO DIVIDE ***   FORMAT=2
[77568.08] Current process id is 0
[77568.09] BAD KERNEL TRAP: 
[77568.10] Modules linked in: xt_multiport iptable_filter ip_tables 
x_tables ipv6 8390 loop evdev dmasound_paula mac_hid dmasound_core 
parport_amiga soundcore parport amimouse ext3 mbcache jbd dm_mod nbd sg 
sd_mod zorro7xx 53c700 hydra amiflop a3000

[77568.32] PC: [<0484c33a>] sd_completed_bytes+0x90/0xe8 [sd_mod]
[77568.33] SR: 2000  SP: 00277e58  a2: 0027e2e4
[77568.34] d0: d1: 007735a0d2: d3: 
0001
[77568.35] d4: d5: 007735a8a0: 024dd000a1: 
024a0ea0

[77568.36] Process swapper (pid: 0, task=0027e2e4)
[77568.37] Frame format=2 instr addr=0484c336
[77568.39] Stack from 00277e90:
 0812  0001 00200028 0004 0249d120 
02be3090
0272c9e0  007735a0 00277f04 0484c5f8 0249d120 00277f30 
000a
00276000 0100 0020 0004 0249d120 1000 02460614 
002b9480
2002 0bb8 0249d100 70040200  024dd400 0013f838 
0249d120
00277f30 002b9480 00276000 001d38e2 000e1cec 0249d120 0001 
00276000
00277f30 00277f30 0002c8da 002b9480 00272704 000f 2598 
08031470

[77568.95] Call Trace: [<0484c5f8>] sd_done+0x1d6/0x2aa [sd_mod]
[77568.97]  [<1000>] kernel_pg_dir+0x0/0x1000
[77568.98]  [<2002>] _start+0x2/0x8
[77568.99]  [<0013f838>] scsi_finish_command+0x8e/0xb2
[77569.00]  [<001d38e2>] printk+0x0/0x24
[77569.01]  [<000e1cec>] blk_done_softirq+0x90/0x9c
[77569.02]  [<0002c8da>] __do_softirq+0xa2/0x12a
[77569.03]  [<2598>] badsys+0x6/0xa
[77569.04]  [<00012b08>] slognd+0x74/0x8a
[77569.05]  [<>] res_func+0x101f/0x141a
[77569.06]  [<001d6944>] schedule_preempt_disabled+0x0/0xe
[77569.07]  [<0002ca04>] do_softirq+0x2c/0x32
[77569.08]  [<264c>] ret_from_exception+0x0/0xc
[77569.09]  [<2598>] badsys+0x6/0xa
[77569.10]  [<000454d6>] cpu_startup_entry+0x74/0xd6
[77569.11]  [<0002721c>] kernel_thread+0x0/0x24
[77569.12]  [<000f0abc>] strlen+0x0/0x14
[77569.13]  [<001d307a>] rest_init+0x5e/0x66
[77569.14]  [<002ca6e6>] start_kernel+0x38c/0x398
[77569.15]  [<37ee>] setup_rt_frame+0x400/0x4be
[77569.16]  [<37ee>] setup_rt_frame+0x400/0x4be
[77569.17]  [<002c8854>] _sinittext+0x854/0x11ac
[77569.18]
[77569.19] Code: 4a80 6704 4c42 0001 2c01 2207 4c42 1406 <2c00> 2e01 
2004 2204 6704 4c42 0001 2801 2205 4c42 1404 2800 2a01 202e fff8 222e

[77569.35] Disabling lock debugging due to kernel taint
[77569.36] Kernel panic - not syncing: Aiee, killing interrupt 
handler!

[77611.97] amikbd: Ctrl-Amiga-Amiga reset warning!!


I don't know whether this is related to the ESP driver or not, but maybe 
someone is better at reading this kind of output and can judge on 
this... :-)


--
Ciao...  //Fon: 0381-2744150
. Ingo \X/ http://blog.windfluechter.net

gpg pubkey: http://www.juergensmann.de/ij_public_key.


--
To UNSUBSCRIBE, email to debian-68k-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/dbbdc369c25c9eea7abc4ca331128...@muaddib.hro.localnet



Re: zsh vs. zsh-common version mismatch

2013-10-20 Thread Christian T. Steigies
Moin,
On Sun, Oct 20, 2013 at 11:05:43AM +0200, Dirk Heinrichs wrote:
> 
> there's a version mismatch between zsh (5.0.2-3) and its dependency 
> zsh-common 
> (5.0.2-5) which prevents zsh installation on m68k:

http://buildd.debian-ports.org/status/package.php?p=zsh&suite=sid

It has not been built yet. I don't know if the needs-build list is sorted
alphabetically, but right now there are "only" 579 packages to build, and
zsh should in that list somewhere.

Christian


-- 
To UNSUBSCRIBE, email to debian-68k-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20131020094433.ga...@chumley.earth.sol



Re: zsh vs. zsh-common version mismatch

2013-10-20 Thread Dirk Heinrichs
Am Sonntag 20 Oktober 2013, 11:44:33 schrieb Christian T. Steigies:

> On Sun, Oct 20, 2013 at 11:05:43AM +0200, Dirk Heinrichs wrote:
> > there's a version mismatch between zsh (5.0.2-3) and its dependency
> > zsh-common
> > (5.0.2-5) which prevents zsh installation on m68k:
> http://buildd.debian-ports.org/status/package.php?p=zsh&suite=sid
> 
> It has not been built yet. I don't know if the needs-build list is sorted
> alphabetically, but right now there are "only" 579 packages to build, and
> zsh should in that list somewhere.

I could try to apt-get source, build the package myself and upload it 
somewhere. Or is the buildd system the only way to get packages into debian.

Bye...

Dirk
-- 
Dirk Heinrichs 
Tel: +49 (0)2471 209385 | Mobil: +49 (0)176 34473913
GPG Public Key C2E467BB | Jabber: dirk.heinri...@altum.de


signature.asc
Description: This is a digitally signed message part.


Re: Zero Divide in Kernel 3.12-rc4

2013-10-20 Thread Geert Uytterhoeven
On Sun, Oct 20, 2013 at 11:37 AM, Ingo Jürgensmann
 wrote:
> I'm testing the ESP SCSI driver port by Tuomas and Michael to 3.12-rc4 and
> got now this kernel panic during heavy disk activity (apt-get dist-upgrade
> and parallel a rsync backup by BackupPC):
>
> Debian GNU/Linux jessie/sid spice ttyS0
>
> spice login: [77568.07] *** ZERO DIVIDE ***   FORMAT=2
> [77568.08] Current process id is 0
> [77568.09] BAD KERNEL TRAP: 
> [77568.10] Modules linked in: xt_multiport iptable_filter ip_tables
> x_tables ipv6 8390 loop evdev dmasound_paula mac_hid dmasound_core
> parport_amiga soundcore parport amimouse ext3 mbcache jbd dm_mod nbd sg
> sd_mod zorro7xx 53c700 hydra amiflop a3000
> [77568.32] PC: [<0484c33a>] sd_completed_bytes+0x90/0xe8 [sd_mod]
> [77568.33] SR: 2000  SP: 00277e58  a2: 0027e2e4
> [77568.34] d0: d1: 007735a0d2: d3: 0001
> [77568.35] d4: d5: 007735a8a0: 024dd000a1: 024a0ea0
> [77568.36] Process swapper (pid: 0, task=0027e2e4)
> [77568.37] Frame format=2 instr addr=0484c336
> [77568.39] Stack from 00277e90:
>  0812  0001 00200028 0004 0249d120
> 02be3090
> 0272c9e0  007735a0 00277f04 0484c5f8 0249d120 00277f30
> 000a
> 00276000 0100 0020 0004 0249d120 1000 02460614
> 002b9480
> 2002 0bb8 0249d100 70040200  024dd400 0013f838
> 0249d120
> 00277f30 002b9480 00276000 001d38e2 000e1cec 0249d120 0001
> 00276000
> 00277f30 00277f30 0002c8da 002b9480 00272704 000f 2598
> 08031470
> [77568.95] Call Trace: [<0484c5f8>] sd_done+0x1d6/0x2aa [sd_mod]

My first guess was that commit ea077b1b96e073eac5c3c5590529e964767fc5f7
("m68k: Truncate base in do_div()") was missing, but this is 3.12-rc4, so it
should be included.

BIG FAT WARNING for Thorsten: 3.10.7 does _not_ have this fix!
It was only backported ase5a16a446ef5bdb37214b100b93e59ac75e8a445 in
3.10.8.

> [77569.19] Code: 4a80 6704 4c42 0001 2c01 2207 4c42 1406 <2c00> 2e01 2004 
> 2204 6704 4c42 0001 2801 2205 4c42 1404 2800 2a01 202e fff8 222e

However, the addresses and the code above don't match the kernel image in
linux-3.12.0-rc4-amiga-m68k.tar.gz?

Can we get the image somewhere?

Apart from that, since the division is:

/* be careful ... don't want any overflows */
u64 factor = scmd->device->sector_size / 512;
do_div(start_lba, factor);
do_div(end_lba, factor);

(yes, the "u64 factor" is the issue without Andreas's fix), it could still be
an ESP bug, if scmd->device->sector_size turns out to be less than 512
(e.g. 0).

Gr{oetje,eeting}s,

Geert

--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- ge...@linux-m68k.org

In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds


--
To UNSUBSCRIBE, email to debian-68k-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/camuhmdukgqfbg8gjf6xscvj0_civs+hvtysh8ynvaevhp8j...@mail.gmail.com



Re: zsh vs. zsh-common version mismatch

2013-10-20 Thread Christian T. Steigies
On Sun, Oct 20, 2013 at 11:53:02AM +0200, Dirk Heinrichs wrote:
> Am Sonntag 20 Oktober 2013, 11:44:33 schrieb Christian T. Steigies:
> 
> > On Sun, Oct 20, 2013 at 11:05:43AM +0200, Dirk Heinrichs wrote:
> > > there's a version mismatch between zsh (5.0.2-3) and its dependency
> > > zsh-common
> > > (5.0.2-5) which prevents zsh installation on m68k:
> > http://buildd.debian-ports.org/status/package.php?p=zsh&suite=sid
> > 
> > It has not been built yet. I don't know if the needs-build list is sorted
> > alphabetically, but right now there are "only" 579 packages to build, and
> > zsh should in that list somewhere.
> 
> I could try to apt-get source, build the package myself and upload it 
> somewhere. Or is the buildd system the only way to get packages into debian.

The package will be scheduled for building eventually. Is it urgent to get
this built? Of course you can try to build it yourself, but unless you have
upload rights to debian-ports, I doubt you can get it included in
debian-ports. If we could get m68k back into debian propper, it would be
easier.

I'll try to get zsh scheduled for building on crest.

Christian


-- 
To UNSUBSCRIBE, email to debian-68k-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20131020102123.ga8...@chumley.earth.sol



Re: Zero Divide in Kernel 3.12-rc4

2013-10-20 Thread Ingo Jürgensmann
Am 20.10.2013 um 12:10 schrieb Geert Uytterhoeven :

> However, the addresses and the code above don't match the kernel image in
> linux-3.12.0-rc4-amiga-m68k.tar.gz?
> Can we get the image somewhere?

I can give you access to the VM with the (patched) kernel source where I 
crosscompiled the image. Just send me your SSH pubkey... 
When it helps, here's the binary tarball: 
https://silverhaze.org/public.php?service=files&t=4701b07462fbbe06516b9433f3084e4c

> Apart from that, since the division is:
> 
>/* be careful ... don't want any overflows */
>u64 factor = scmd->device->sector_size / 512;
>do_div(start_lba, factor);
>do_div(end_lba, factor);
> 
> (yes, the "u64 factor" is the issue without Andreas's fix), it could still be
> an ESP bug, if scmd->device->sector_size turns out to be less than 512
> (e.g. 0).


At least this time the filesystem survived the kernel crash. Maybe Michael can 
have a look at the source as well when the sun rises in *.nz... ;)

-- 
Ciao...//  Fon: 0381-2744150
  Ingo   \X/   http://blog.windfluechter.net


gpg pubkey:  http://www.juergensmann.de/ij_public_key.asc


--
To UNSUBSCRIBE, email to debian-68k-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/59784485-0680-414f-a9fb-5fdd84c9c...@2013.bluespice.org



Re: Zero Divide in Kernel 3.12-rc4

2013-10-20 Thread Geert Uytterhoeven
On Sun, Oct 20, 2013 at 12:25 PM, Ingo Jürgensmann
 wrote:
>> However, the addresses and the code above don't match the kernel image in
>> linux-3.12.0-rc4-amiga-m68k.tar.gz?
>> Can we get the image somewhere?
>
> I can give you access to the VM with the (patched) kernel source where I 
> crosscompiled the image. Just send me your SSH pubkey...

Will see later, have to cook (food, not code :-) now...
Can you email me the patch?

> When it helps, here's the binary tarball: 
> https://silverhaze.org/public.php?service=files&t=4701b07462fbbe06516b9433f3084e4c

That's the same binary as before, which doesn't match?

Gr{oetje,eeting}s,

Geert

--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- ge...@linux-m68k.org

In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds


--
To UNSUBSCRIBE, email to debian-68k-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/camuhmdu83v3nwfoe0d_zxsmn-xryoqwxvkgzmbkcmf6u0uz...@mail.gmail.com



Re: zsh vs. zsh-common version mismatch

2013-10-20 Thread Dirk Heinrichs
Am Sonntag 20 Oktober 2013, 12:21:23 schrieb Christian T. Steigies:

> The package will be scheduled for building eventually. Is it urgent to get
> this built?

No, it's not urgent.

> I'll try to get zsh scheduled for building on crest.

No need to, I can also wait...

Bye...

Dirk
-- 
Dirk Heinrichs 
Tel: +49 (0)2471 209385 | Mobil: +49 (0)176 34473913
GPG Public Key C2E467BB | Jabber: dirk.heinri...@altum.de


signature.asc
Description: This is a digitally signed message part.


Re: Linux 3.10-2-m68k FPU support

2013-10-20 Thread John Paul Adrian Glaubitz
On 10/20/2013 01:25 AM, Michael Schmitz wrote:
> The docs are quite clearly out of date. From memory, there may be the
> odd FPU instruction that does not work perfectly, but that would be
> limited to 030 type emulation. 040 and 060 use code from the Motorola
> floating-point support package which hasn't been reported to have faults
> as such. Even for 030, I cannot recall specific instructions that are
> unimplemented or dodgy.

I have been testing the FPU emulation code on my 68030/56 with no FPU
and I have seen the kernel complain only once about some unimplemented
FPU instruction. I forgot the exact error message and don't have the
logs anymore.

However, once I see it again, I'll report it.

> Seeing as this code is crucial, I'd opt for putting it back in, and
> finding something else to remove. I appreciate this will be hard, or
> course.

Thank you! As I said before, there are many 68k machines out there which
have enough CPU power and memory to run Linux, but they don't have an
FPU and it's not easily to be added due to lack of an FPU socket.

Adrian

-- 
 .''`.  John Paul Adrian Glaubitz
: :' :  Debian Developer - glaub...@debian.org
`. `'   Freie Universitaet Berlin - glaub...@physik.fu-berlin.de
  `-GPG: 62FF 8A75 84E0 2956 9546  0006 7426 3B37 F5B5 F913


-- 
To UNSUBSCRIBE, email to debian-68k-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/5263b916.7080...@physik.fu-berlin.de



Re: Linux 3.10-2-m68k FPU support

2013-10-20 Thread Finn Thain

On Sun, 20 Oct 2013, Michael Schmitz wrote:

> The docs are quite clearly out of date...

ISTR those docs are older than the most recent work Roman did on the FPU 
emulation code...

> Certain mask revisions of the LC040 have a firmware bug that prevents 
> floating point exceptions to properly work in corner cases (i.e. when 
> the FPU instruction happens to span a page boundary). These LC040 were 
> mostly used in early Macs,

Anecdotally, I've always enabled CONFIG_M68KFPU_EMU in my test builds, and 
I've occasionally booted them on 68030 Macs lacking a 68882/68881 chip and 
also on errata-free, late revision 68LC040 chips.

If there is a test suite with decent coverage of FPU operations somewhere 
in the Debian archive, it might answer the question.

Finn


-- 
To UNSUBSCRIBE, email to debian-68k-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/alpine.LNX.2.00.1310202238520.18727@nippy.intranet



Re: Linux 3.10-2-m68k FPU support

2013-10-20 Thread Andreas Schwab
Thorsten Glaser  writes:

> On the other hand, I cannot help but wonder how well it compares
> to whatever ARAnyM passes as FPU. I know ARAnyM doesn’t handle the
> 80/64bit precision switch at all

It doesn't?

Andreas.

-- 
Andreas Schwab, sch...@linux-m68k.org
GPG Key fingerprint = 58CA 54C7 6D53 942B 1756  01D3 44D5 214B 8276 4ED5
"And now for something completely different."


-- 
To UNSUBSCRIBE, email to debian-68k-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/87fvrwp35u@igel.home



Re: zsh vs. zsh-common version mismatch

2013-10-20 Thread Thorsten Glaser
Christian T. Steigies dixit:

>I'll try to get zsh scheduled for building on crest.

tg@leda:~$ wanna-build -A m68k -d unstable --build-priority=10 zsh_5.0.2-5

Just use the buildd network for this. zsh is now the next
package to be built.

bye,
//mirabilos
PS: Frank is zsh committer…
-- 
FWIW, I'm quite impressed with mksh interactively. I thought it was much
*much* more bare bones. But it turns out it beats the living hell out of
ksh93 in that respect. I'd even consider it for my daily use if I hadn't
wasted half my life on my zsh setup. :-) -- Frank Terbeck in #!/bin/mksh


--
To UNSUBSCRIBE, email to debian-68k-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/pine.bsm.4.64l.1310201416230.19...@herc.mirbsd.org



Re: zsh vs. zsh-common version mismatch

2013-10-20 Thread Dirk Heinrichs
Am Sonntag 20 Oktober 2013, 14:17:48 schrieb Thorsten Glaser:

> Christian T. Steigies dixit:
> >I'll try to get zsh scheduled for building on crest.
> 
> tg@leda:~$ wanna-build -A m68k -d unstable --build-priority=10 zsh_5.0.2-5
> 
> Just use the buildd network for this. zsh is now the next
> package to be built.

Thanks a lot!

Bye...

Dirk
-- 
Dirk Heinrichs 
Tel: +49 (0)2471 209385 | Mobil: +49 (0)176 34473913
GPG Public Key C2E467BB | Jabber: dirk.heinri...@altum.de


signature.asc
Description: This is a digitally signed message part.


Re: Linux 3.10-2-m68k FPU support

2013-10-20 Thread Thorsten Glaser
Andreas Schwab dixit:

>None of the trigonometric or logarithmic insns are implemented (grep for

OK, decide on whether this should let it be disabled or not.


Ingo J�rgensmann dixit:

>Hmmm... if Aranym is the problematic part in this story, then Aranym

No, it’s not, that’s a totally different story. I was wondering whether
the FPU emulation code worked _better_ than ARAnyM (see below), in
which case we might want to use that instead.


Geert Uytterhoeven dixit:

>Furthermore, for people running Debian on their FPU-less machines before,
>the new kernel image is definitely a regression, so it warrants re-enabling
>FPU emulation to fix this.

Not an argument ;-)

>Indeed. The emulation may be incomplete, but for most people it's useable,
>and definitely better than nothing.

OK, I’ll take your word for it.

>Nevertheless, FPU emulation in ARAnyM is something different. ARAnyM
>is an emulator that emulates a full 68040, incl. FPU. So as far as the Linux

Yes, except it doesn’t emulate the FPU fully.

>kernel is concerned, no in-kernel FPU emulation is involved.

Right.


Andreas Schwab dixit:

>Thorsten Glaser  writes:
>
>> On the other hand, I cannot help but wonder how well it compares
>> to whatever ARAnyM passes as FPU. I know ARAnyM doesn’t handle the
>> 80/64bit precision switch at all
>
>It doesn't?

In my tests, it didn’t, and I later got a mail from someone saying
that it indeed doesn’t do that.

And yes, testing still shows it to fail:

(sid-m68k-sbuild)tg@ara5:/tmp$ gcc -O2 x.c && ./a.out
test#1 fail: 1.0E+00
test#2 fail: 1.00040E+16
changing FPU control word from  to 0080 => 0080
test#1 fail: 1.0E+00
test#2 fail: 1.00040E+16

That with the attached test file I reported to Python upstream.

MirBSD/i386 always runs with 64-bit precision…

tg@blau:~ $ mgcc -O2 x.c && ./a.out
x.c:0: note: someone does not honour COPTS correctly, passed 0 times
test#1 good: 1.00022E+00
test#2 good: 1.00020E+16

… and Linux/i386 is able to change to it:

tg@frozenfish:~ $ gcc -O2 x.c && ./a.out
test#1 fail: 1.0E+00
test#2 fail: 1.00040E+16
changing FPU control word from 037F to 127F => 127F
test#1 good: 1.00022E+00
test#2 good: 1.00020E+16

In Python, we decided to just use the fallback code for systems
whose FPU cannot be switched to 64-bit precision, as the current
ARAnyM code is relatively widespread, and the other code, which
relies on 64(53)-bit precision, has catastrophic failure modes
if the switch doesn’t work, whereas the older code, while not as
“good”, will just always work.

bye,
//mirabilos
-- 
 Beware of ritual lest you forget the meaning behind it.
 yeah but it means if you really care about something, don't
ritualise it, or you will lose it. don't fetishise it, don't
obsess. or you'll forget why you love it in the first place.#include 
#include 
#include 
#ifndef __MirBSD__
#include 
#endif

void runtests(void);

void
runtests(void)
{
volatile double x, y, z;

/* 1./(1-2**-53) -> 1+2**-52 (correct), 1.0 (double rounding) */
x = 0.99989; /* 1-2**-53 */
y = 1./x;
printf("test#1 %s: %.17E\n", (y == 1.) ? "fail" : "good", y);
/* 1e16+2.9 -> 1e16+2. (correct), 1e16+4. (double rounding) */
x = 1e16;
y = 2.9;
z = x + y;
printf("test#2 %s: %.17E\n", z == 1e16+4. ? "fail" : "good", z);
}

int
main(void) {
#ifdef _FPU_SETCW
fpu_control_t cwold, cwnew, cwgot;
#endif

runtests();
#if (defined(__i386__) || defined(__m68k__)) && defined(_FPU_SETCW)
_FPU_GETCW(cwold);
#ifdef __i386__
cwnew = 0x127f;
#else
cwnew = _FPU_RC_NEAREST | _FPU_DOUBLE;
#endif
_FPU_SETCW(cwnew);
_FPU_GETCW(cwgot);
printf("changing FPU control word from %08X to %08X => %08X\n",
cwold, cwnew, cwgot);
runtests();
#endif

return (0);
}


Re: Linux 3.1-2-m68k config

2013-10-20 Thread Thorsten Glaser
Geert Uytterhoeven dixit:

>Big differences are due to many drivers being modular in the initrd for the
>Debian kernel, which I want to avoid for my defconfigs, for hassle-free
>testing.

ACK, but we need that.

>What sticks out:
>  - Lack of FPU emulation support in the Debian kernel,

Hm okay.

>  - CONFIG_COMPAT_BRK is not enabled in the Debian kernel, which
>is needed if you want to boot the good old filesys-ELF-2.0.x-1400K-2.gz

I wonder…

>ramdisk (probably not with the Debian kernel, as all your drivers are in
>modules?)

… yes, we have everything that can be shoved into modules there,
since we bit the bullet and require an initrd now. But I guess
CONFIG_COMPAT_BRK is “not much” code, so I’ll probably add them
both.

Any further suggestions (please in form of "toggle this setting"
because the Debian configs are “minified deltas”) into my general
direction ;-)

>Apart from that, (probably both) configs need more stripping in the common
>part. I want to have bootable (i.e. < 4 MiB) defconfig kernels.

Ours is bootable and decently small. Still could use shaving off
more, but it’s a good start considering I only really worked with
Linux 2.0.3x and later 2.4.3 and otherwise only BSD…

One pet peeve of mine is that I don’t know which of the tristate
options add “common code” (such as hooks) and which, when set to
‘m’, do _not_ add something to vmlinux.

But since Debian is a generic, universal distro, I’ve kept most
of the things Debian uses enabled as modules, in case someone
actually does want to run it.

There are some exceptions, most notably Ceph and the likes.
And LSM and cgroups were removed from the core for obvious
size reasons.


Laurent Vivier dixit:

> Moreover, a compressed kernel fitting on a floppy would be better : there is 
> no

Just use a custom kernel then: you’d want that to be as optimised
to the target machine as possible; multi-platform configs are not
just bigger but also require more (e.g. HDD) drivers.

> USB port on this kind of machine, and the floppy is the easiest way to boot a

This is wrong, I’ve seen Ataris with USB and even a PCI Radeon
graphics card running FreeMiNT IRL.

> (With 2.2 kernel we were able to put kernel AND ramdisk on the SAME floppy !)

Yes, but Linux 3.0 is bigger. SOL.

(Even in MirBSD, I have to squeeze more and more for the boot floppy,
both the one i386 one and the one sparc one, over time.)

bye,
//mirabilos
-- 
Gast: „Ein Bier, bitte!“
Wirt: „Geht auch alkoholfrei?“
Gast: „Geht auch Spielgeld?“


--
To UNSUBSCRIBE, email to debian-68k-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/pine.bsm.4.64l.1310201454250.19...@herc.mirbsd.org



Re: Zero Divide in Kernel 3.12-rc4

2013-10-20 Thread Thorsten Glaser
Geert Uytterhoeven dixit:

>BIG FAT WARNING for Thorsten: 3.10.7 does _not_ have this fix!

Debian 3.10.7-1 does have it (as Debian-specific patch).
Otherwise my buildd couldn’t run that kernel as it uses btrfs.

bye,
//mirabilos
-- 
 Beware of ritual lest you forget the meaning behind it.
 yeah but it means if you really care about something, don't
ritualise it, or you will lose it. don't fetishise it, don't
obsess. or you'll forget why you love it in the first place.


--
To UNSUBSCRIBE, email to debian-68k-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/pine.bsm.4.64l.1310201508100.19...@herc.mirbsd.org



elgar - give-back

2013-10-20 Thread John Paul Adrian Glaubitz
Hi Thorsten,

I had some issues with elgar today with the apt/lists database
in the buildd changeroot being broken. As a result, the following
packages failed to build, have not been given back yet, however:

mafft roaraudio zvbi nginx xmountains

Please give them back :).

Cheers,

Adrian

-- 
 .''`.  John Paul Adrian Glaubitz
: :' :  Debian Developer - glaub...@debian.org
`. `'   Freie Universitaet Berlin - glaub...@physik.fu-berlin.de
  `-GPG: 62FF 8A75 84E0 2956 9546  0006 7426 3B37 F5B5 F913


-- 
To UNSUBSCRIBE, email to debian-68k-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/5263f7cf.5020...@physik.fu-berlin.de



Re: Linux 3.10-2-m68k FPU support

2013-10-20 Thread Andreas Schwab
Thorsten Glaser  writes:

>>> On the other hand, I cannot help but wonder how well it compares
>>> to whatever ARAnyM passes as FPU. I know ARAnyM doesn’t handle the
>>> 80/64bit precision switch at all
>>
>>It doesn't?
>
> In my tests, it didn’t, and I later got a mail from someone saying
> that it indeed doesn’t do that.
>
> And yes, testing still shows it to fail:
>
> (sid-m68k-sbuild)tg@ara5:/tmp$ gcc -O2 x.c && ./a.out
> test#1 fail: 1.0E+00
> test#2 fail: 1.00040E+16
> changing FPU control word from  to 0080 => 0080
> test#1 fail: 1.0E+00
> test#2 fail: 1.00040E+16

That's just double rounding.  But saying that it doesn't handle it at
all is stupid.

Andreas.

-- 
Andreas Schwab, sch...@linux-m68k.org
GPG Key fingerprint = 58CA 54C7 6D53 942B 1756  01D3 44D5 214B 8276 4ED5
"And now for something completely different."


-- 
To UNSUBSCRIBE, email to debian-68k-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/87bo2korgv@igel.home



Re: Linux 3.1-2-m68k config

2013-10-20 Thread Geert Uytterhoeven
On Sun, Oct 20, 2013 at 5:01 PM, Thorsten Glaser  wrote:
> One pet peeve of mine is that I don’t know which of the tristate
> options add “common code” (such as hooks) and which, when set to
> ‘m’, do _not_ add something to vmlinux.

To find code that's compiled if a tristate symbol is "m":

git grep "\"

This is not necessariy code in vmlinux; it can be code in another module.

And in Makefile logic:

git grep "\.*\m=y" -- "*Makefile"

Gr{oetje,eeting}s,

Geert

--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- ge...@linux-m68k.org

In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds


--
To UNSUBSCRIBE, email to debian-68k-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/CAMuHMdWfi4ymGd�+gmuvcbif2pbbpd09kyse8gh6-kzuq...@mail.gmail.com



3.12 won't startup at amiga 1200

2013-10-20 Thread Tuxist
Hi,  

   

i have tried to bootup amiga 1200 + aca1232 without succes.  

   

I got this error message:  


  

Linux version 3.12.0-rc5 (administrator@dibsi) (gcc version 4.8.1 (GCC) ) #11
Sat Oct 19 15:39:45 CEST 2013 console [debug0] enabled [ cut here
] WARNING: CPU: 0 PID: 0 at kernel/printk/printk.c:2233
register_console+0x332/0x35a() console 'debug0' already registered CPU: 0
PID: 0 Comm: swapper Not tainted 3.12.0-rc5 #11 Stack from 00329e98: 00329e98
003163ec 00027f2a 0001 003016d4 0038b9d4 0038b9da 00330f00 0003c0d6
00027f98 003052ea 08b9 0004bc64 0009 00329ed4 003052c7 00329ef0
0038b9de 0004bc64 003052ea 08b9 003052c7 00330f00  0001
00391aa0 0003c0d6 002ac57e 0037b676 00330f00 00379a6e 0038b9da 
 0006 0824 0038b9d4 0003c0d6 0018dd92 0003c210 0038b9d4
0038b9da 00301782 002ac57e 00d2 000662d0 08241db8 0008b9b0 Call Trace:
[<00027f2a>] warn_slowpath_common+0x56/0x6a [<0003c0d6>] parameq+0x0/0x58
[<00027f98>] warn_slowpath_fmt+0x2a/0x32 [<0004bc64>]
register_console+0x332/0x35a [<0004bc64>] register_console+0x332/0x35a
[<0003c0d6>] parameq+0x0/0x58 [<002ac57e>] printk+0x0/0x24 [<0037b676>]
amiga_savekmsg_setup+0x82/0x8c [<00379a6e>] do_early_param+0x62/0x9a
[<0006>] __rmqueue+0x214/0x380 [<0003c0d6>] parameq+0x0/0x58 [<0018dd92>]
skip_spaces+0x0/0x30 [<0003c210>] parse_args+0xe2/0x2ca [<002ac57e>]
printk+0x0/0x24 [<000662d0>] truncate_inode_pages_range+0x3d0/0x4f2
[<0008b9b0>] get_slabinfo+0x82/0x1b2 [<>] sto_res+0x187/0x4f0
[<0018db34>] strlcpy+0x0/0x66 [<835c>] amiga_parse_bootinfo+0x0/0x178
[<00379c86>] parse_early_options+0x1c/0x22 [<00379a0c>]
do_early_param+0x0/0x9a [<00379cb4>] parse_early_param+0x28/0x36 [<0037a932>]
setup_arch+0x186/0x1f8 [<002ac57e>] printk+0x0/0x24 [<00379d32>]
start_kernel+0x6c/0x2c4 [<003792fc>] _sinittext+0x2fc/0x988 ---[ end trace
139ce121c98e96c9 ]--- Amiga hardware found: [A1200] VIDEO BLITTER AUDIO
FLOPPY A1200_IDE KEYBOARD MOUSE SERIAL PARALLEL A2000_CLK CHIP_RAM PAULA LISA
ALICE_PAL PCMCIA ZORRO Ignoring memory chunk at 0xc0:0x10 before the
first chunk Fix your bootloader or use a memfile to make use of this area! On
node 0 totalpages: 32256 free_area_init_node: node 0, pgdat 00343ac4,
node_mem_map 00396000 DMA zone: 315 pages used for memmap DMA zone: 0 pages
reserved DMA zone: 32256 pages, LIFO batch:7 pcpu-alloc: s0 r0 d32768 u32768
alloc=1*32768 pcpu-alloc: [0] 0 Built 1 zonelists in Zone order, mobility
grouping on. Total pages: 31941 Kernel command line: root=/dev/hda4 rw
video=pal-lace devtmpfs.mount=1 debug=ser debug=mem console=ttyS0,9600n8 PID
hash table entries: 512 (order: -1, 2048 bytes) Dentry cache hash table
entries: 16384 (order: 4, 65536 bytes) Inode-cache hash table entries: 8192
(order: 3, 32768 bytes) Sorting __ex_table... Memory: 123936K/129024K
available (2758K kernel code, 325K rwdata, 452K rodata, 104K init, 212K bss,
5088K reserved) Virtual kernel memory layout: vector : 0x003435bc -
0x003439bc ( 1 KiB) kmap : 0xd000 - 0xf000 ( 512 MiB) vmalloc :
0x0800 - 0xd000 (3200 MiB) lowmem : 0x - 0x07e0 ( 126
MiB) .init : 0x00379000 - 0x00393000 ( 104 KiB) .text : 0x1000 -
0x002b2908 (2759 KiB) .data : 0x002b5d40 - 0x00378420 ( 778 KiB) .bss :
0x00343400 - 0x00378420 ( 213 KiB) SLUB: HWalign=16, Order=0-3, MinObjects=0,
CPUs=1, Nodes=8 NR_IRQS:32 Console: colour dummy device 80x25 console [ttyS0]
enabled Calibrating delay loop... 7.88 BogoMIPS (lpj=39424) pid_max: default:
32768 minimum: 301 Mount-cache hash table entries: 512 NET: Registered
protocol family 16 bio: create slab  at 0 NET: Registered protocol
family 2 TCP established hash table entries: 1024 (order: 1, 8192 bytes) TCP
bind hash table entries: 1024 (order: 0, 4096 bytes) TCP: Hash tables
configured (established 1024 bind 1024) TCP: reno registered UDP hash table
entries: 256 (order: 0, 4096 bytes) UDP-Lite hash table entries: 256 (order:
0, 4096 bytes) Data read fault at 0x in Super Data (pc=0x55734) BAD
KERNEL BUSERR Oops:  PC: [<00055734>]
cmpxchg_futex_value_locked+0x14/0x58 SR: 2004 SP: 07837e80 a2: 07838000 d0:
 d1: 0004 d2: 0007 d3: 00391d98 d4: 004f d5: 00379f8a a0:
 a1: 07836000 Process swapper (pid: 1, task=07838000) Frame format=B
ssw=074d isc=4a80 isb=662a daddr= dobuf=0001 baddr=0005573a
dibuf= ver=f Stack from 07837f08: 0037e2b2 07837f1c  
 000551a8 07837f8c 0037a028 0007 00391d98 004f 00379f8a
  0038bad8 0038bab8 0003c12e 004f 00379f8a 
 0038bad4 0038bab8 0003c12e 0018db22 004d64ca 0037a188 00319401
004d6470 003264e8 004f 0006 0006 0018db22 0037a19e 0037e29e
0783ba2e  000662d0 08241db8 002abc7a   
002abc84 002abc7a  2730 Call Trace: [<0037e2b2>]
futex_init+0x14/0x44 [<000551a8>] alarm_timer_del+0x0/0x8 [<0037a028>]
do_one_initcall+0x9e/0x13e [<00379

Re: 3.12 won't startup at amiga 1200

2013-10-20 Thread John Paul Adrian Glaubitz
Hello!

On Sun, Oct 20, 2013 at 07:25:02PM +0200, Tuxist wrote:
> i have tried to bootup amiga 1200 + aca1232 without succes.
>
> > I got this error message:
>  
> > Linux version 3.12.0-rc5 (administrator@dibsi) (gcc version 4.8.1 (GCC) ) 
> > #11
> Sat Oct 19 15:39:45 CEST 2013 console [debug0] enabled [ cut here
> ] WARNING: CPU: 0 PID: 0 at kernel/printk/printk.c:2233
> register_console+0x332/0x35a() console 'debug0' already registered CPU: 0

The formatting of your kernel paste is messed up (please check your
email client and try posting plain ASCII instead of HTML), but from
what I can see it looks like you passed the wrong command line options
for the serial console.

I have seen this issue when adding "console=ttyS0,9600n8" to the
kernel command line. Replacing it with "debug=ser" fixed the issue for
me.

Cheers,

Adrian

-- 
 .''`.  John Paul Adrian Glaubitz
: :' :  Debian Developer - glaub...@debian.org
`. `'   Freie Universitaet Berlin - glaub...@physik.fu-berlin.de
  `-GPG: 62FF 8A75 84E0 2956 9546  0006 7426 3B37 F5B5 F913


-- 
To UNSUBSCRIBE, email to debian-68k-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20131020174546.ga26...@physik.fu-berlin.de



Re: 3.12 won't startup at amiga 1200

2013-10-20 Thread Geert Uytterhoeven
On Sun, Oct 20, 2013 at 7:25 PM, Tuxist  wrote:
> Data read fault at 0x in Super Data (pc=0x55734) BAD KERNEL BUSERR
> Oops: 
> PC: [<00055734>] cmpxchg_futex_value_locked+0x14/0x58
> SR: 2004 SP: 07837e80
> a2: 07838000 d0:  d1: 0004 d2: 0007 d3: 00391d98
> d4: 004f d5: 00379f8a a0:  a1: 07836000
> Process swapper (pid: 1, task=07838000)
> Frame format=B ssw=074d isc=4a80 isb=662a daddr= dobuf=0001
> baddr=0005573a dibuf= ver=f
> Stack from 07837f08:
> 0037e2b2 07837f1c    000551a8 07837f8c
> 0037a028 0007 00391d98 004f 00379f8a  
> 0038bad8 0038bab8 0003c12e 004f 00379f8a  
> 0038bad4 0038bab8 0003c12e 0018db22 004d64ca 0037a188 00319401
> 004d6470 003264e8 004f 0006 0006 0018db22 0037a19e
> 0037e29e 0783ba2e  000662d0 08241db8 002abc7a 
>   002abc84 002abc7a  2730
> Call Trace:
> [<0037e2b2>] futex_init+0x14/0x44
> [<000551a8>] alarm_timer_del+0x0/0x8

> Code: 200f 0280  e000 2240 52a9 0010 4280 <0e90> 1000 4a80 662a
> b2af 000c 6718 206f 0004 2081 4280 220f 0281  e000 2041

"0e90 1000" is "movesl %a0@,%d1". So somehow it's trying a NULL pointer
dereference to userspace (which didn't get caught by the upper layer?).
However, __get_user_asm() should catch this through the exception fixup.
Strange...

Gr{oetje,eeting}s,

Geert

--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- ge...@linux-m68k.org

In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds


-- 
To UNSUBSCRIBE, email to debian-68k-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/CAMuHMdU=Q-BBVTLJQzvgwY0NEyHJrh4-fzr6ibFch=bm+j8...@mail.gmail.com



Re: 3.12 won't startup at amiga 1200

2013-10-20 Thread Tuxist
   
>  So Okt 20 2013 07:45:46 CEST von "John Paul Adrian Glaubitz"
>  Betreff: Re: 3.12 won't startup at amiga 1200
>
>  Hello!
> 
> On Sun, Oct 20, 2013 at 07:25:02PM +0200, Tuxist wrote:
>  
>>i have tried to bootup amiga 1200 + aca1232 without succes.
>> 
>>  
>>>I got this error message:
>>> 
>>> Linux version 3.12.0-rc5 (administrator@dibsi) (gcc version 4.8.1 (GCC) )
>>>#11

>>  Sat Oct 19 15:39:45 CEST 2013 console [debug0] enabled [ cut
>>here
>> ] WARNING: CPU: 0 PID: 0 at kernel/printk/printk.c:2233
>> register_console+0x332/0x35a() console 'debug0' already registered CPU: 0
>> 

>  The formatting of your kernel paste is messed up (please check your
> email client and try posting plain ASCII instead of HTML), but from
> what I can see it looks like you passed the wrong command line options
> for the serial console.
> 
> I have seen this issue when adding "console=ttyS0,9600n8" to the
> kernel command line. Replacing it with "debug=ser" fixed the issue for
> me.
> 
> Cheers,
> 
> Adrian
> 
> -- 
> .''`. John Paul Adrian Glaubitz
> : :' : Debian Developer - glaub...@debian.org
> `. `' Freie Universitaet Berlin - glaub...@physik.fu-berlin.de
> `- GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913
> 
>
>  

  

after i have changed start paramter nothing changed.  

http://paste.debian.net/59909


[buildd] /etc/mtab (was Re: Log for attempted build of zsh_5.0.2-5 on m68k (dist=unstable))

2013-10-20 Thread Thorsten Glaser
buildd on ara5 for m68k dixit:
  [NON-Text Body part not included]

The build failed because I mount the buildd chroot noatime of
course. The code has workarounds for this.

I just did the following on my buildd:

tg@ara5:~ $ schroot -u root -c source:sid-m68k-sbuild
(sid-m68k-sbuild)root@ara5:/home/tg# unset HISTFILE
(sid-m68k-sbuild)root@ara5:/home/tg# ln -s /proc/mounts /etc/mtab
(sid-m68k-sbuild)root@ara5:/home/tg# exit

This should have fixed the issue; I’ve give-back’d zsh.

Please do the same on all other buildds, thanks!

bye,
//mirabilos
-- 
[...] if maybe ext3fs wasn't a better pick, or jfs, or maybe reiserfs, oh but
what about xfs, and if only i had waited until reiser4 was ready... in the be-
ginning, there was ffs, and in the middle, there was ffs, and at the end, there
was still ffs, and the sys admins knew it was good. :)  -- Ted Unangst über *fs


--
To UNSUBSCRIBE, email to debian-68k-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/pine.bsm.4.64l.1310201830390.19...@herc.mirbsd.org



Re: 3.12 won't startup at amiga 1200

2013-10-20 Thread John Paul Adrian Glaubitz
On 10/20/2013 08:27 PM, Tuxist wrote:
> after i have changed start paramter nothing changed.
> 
> http://paste.debian.net/59909

What is your exact kernel command line?
And have you tried earlier kernels, like 3.2.0 and 3.10?

If you're using the ACA-1232 accelerator, you will need to use a kernel
with math emulation (also called FPU emulation) enabled since the
ACA-1232 doesn't come with an FPU.

Which ACA-1232 do you have, btw? There versions with and without an
MMU, you need either of the two which comes with an MMU:

> http://www.vesalia.de/e_aca1232%5B8289%5D.htm

Please provide as much as information about your hard- and software
configuration as possible as this will help localizing your problem.

Cheers,

Adrian

-- 
 .''`.  John Paul Adrian Glaubitz
: :' :  Debian Developer - glaub...@debian.org
`. `'   Freie Universitaet Berlin - glaub...@physik.fu-berlin.de
  `-GPG: 62FF 8A75 84E0 2956 9546  0006 7426 3B37 F5B5 F913


-- 
To UNSUBSCRIBE, email to debian-68k-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/52642652.8070...@physik.fu-berlin.de



Re: 3.12 won't startup at amiga 1200

2013-10-20 Thread Tuxist
   
>  So Okt 20 2013 08:52:02 CEST von "John Paul Adrian Glaubitz"
>  Betreff: Re: 3.12 won't startup at amiga 1200
>
>  On 10/20/2013 08:27 PM, Tuxist wrote:
>  
>>after i have changed start paramter nothing changed.
>> 
>> http://paste.debian.net/59909
>> 

>  What is your exact kernel command line?
> And have you tried earlier kernels, like 3.2.0 and 3.10?
> 
> If you're using the ACA-1232 accelerator, you will need to use a kernel
> with math emulation (also called FPU emulation) enabled since the
> ACA-1232 doesn't come with an FPU.
> 
> Which ACA-1232 do you have, btw? There versions with and without an
> MMU, you need either of the two which comes with an MMU:
> 
>  
>>http://www.vesalia.de/e_aca1232%5B8289%5D.htm
>> 

>  Please provide as much as information about your hard- and software
> configuration as possible as this will help localizing your problem.
> 
> Cheers,
> 
> Adrian
> 
> -- 
> .''`. John Paul Adrian Glaubitz
> : :' : Debian Developer - glaub...@debian.org
> `. `' Freie Universitaet Berlin - glaub...@physik.fu-berlin.de
> `- GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913
> 
> 
> -- 
> To UNSUBSCRIBE, email to debian-68k-requ...@lists.debian.org
> with a subject of "unsubscribe". Trouble? Contact
>listmas...@lists.debian.org
> Archive: http://lists.debian.org/52642652.8070...@physik.fu-berlin.de
> 
>
>  

  

i have already sucessfully bootup kernel 3.2. I have the ACA 1232 with mmu
and 34,50 mhz.  

my kernel config http://tuxist.de/config-3.12-rc5  

the kernel http://tuxist.de/vmlinux  

   

   

if you need more information i will give you them.


Re: Linux 3.10-2-m68k FPU support

2013-10-20 Thread Thorsten Glaser
Andreas Schwab dixit:

>That's just double rounding.  But saying that it doesn't handle it at
>all is stupid.

It doesn’t handle the documented way of switching the FPU into
a mode that doesn’t do that.

bye,
//mirabilos
-- 
 Beware of ritual lest you forget the meaning behind it.
 yeah but it means if you really care about something, don't
ritualise it, or you will lose it. don't fetishise it, don't
obsess. or you'll forget why you love it in the first place.


--
To UNSUBSCRIBE, email to debian-68k-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/pine.bsm.4.64l.1310201912070.19...@herc.mirbsd.org



Bug#726969: libarpack2: Please update symbols file to fix FTBFS on m68k

2013-10-20 Thread John Paul Adrian Glaubitz
Package: libarpack2
Version: 3.1.3-4
Severity: normal

Hi,

arpack recently failed to build on one of our m68k builds [1].

Could you please update the symbols file to include the
appropriate lines in the debian/libparpack2.symbols to
reflect the m68k architecture as well?

Cheers,

Adrian

> [1] 
> http://buildd.debian-ports.org/status/fetch.php?pkg=arpack&arch=m68k&ver=3.1.3-4&stamp=1382056609


-- 
To UNSUBSCRIBE, email to debian-68k-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/20131021024450.11992.19887.report...@z6.physik.fu-berlin.de



Re: Linux 3.1-2-m68k config (was: Re: Linux 3.10-2-m68k FPU support)

2013-10-20 Thread Finn Thain

On Sun, 20 Oct 2013, Geert Uytterhoeven wrote:

> This is the difference between my multi_defconfig and 
> config-3.10-2-m68k.

Nice!

> Big differences are due to many drivers being modular in the initrd for 
> the Debian kernel, which I want to avoid for my defconfigs, for 
> hassle-free testing.
> 
> What sticks out:
>   - Lack of FPU emulation support in the Debian kernel,
>   - CONFIG_COMPAT_BRK is not enabled in the Debian kernel, which is 
> needed if you want to boot the good old filesys-ELF-2.0.x-1400K-2.gz 
> ramdisk (probably not with the Debian kernel, as all your drivers 
> are in modules?)
> 
> I have to look a bit more at it, but all help is welcome.
> 

CONFIG_ADB_MACIISI is disabled in -multi due to crashing bugs. Debian 
might want to do the same (until I get a chance to fix it). The serial 
console is a good workaround.

> Apart from that, (probably both) configs need more stripping in the 
> common part. I want to have bootable (i.e. < 4 MiB) defconfig kernels.

Below is the same list after sort -k4 -k5 -k2. Note that some modules in 
-multi are disabled in the Debian config. That may or may not help you 
with the 4 MiB limit (might be worth checking the vmlinux sizes).

Should an end-user file a bug report about missing functionality, I'm sure 
they will understand the difficulty in supporting obscure functionality in 
large generic binaries.

Finn


! multi_defconfig -+
! config-3.10-2-m68k + |
!| |

! CONFIG_LOCALVERSION  : "" "-multi"
! CONFIG_UEVENT_HELPER_PATH: "" "/sbin/hotplug"
! CONFIG_NFS_V4_1_IMPLEMENTATION_ID_DOMAIN : "kernel.org" .
! CONFIG_DEFAULT_IOSCHED   : "noop" "cfq"
! CONFIG_FAT_DEFAULT_IOCHARSET : "utf8" "iso8859-1"
! CONFIG_NLS_DEFAULT   : "utf8" "iso8859-1"
! CONFIG_HP_SDC_RTC: . m
! CONFIG_LRU_CACHE : . m
! CONFIG_OCFS2_FS_O2CB : . m
! CONFIG_OCFS2_FS_USERSPACE_CLUSTER: . m
! CONFIG_RDS_TCP   : . m
! CONFIG_BATMAN_ADV_BLA: . y
! CONFIG_BATMAN_ADV_DAT: . y
! CONFIG_BATMAN_ADV_NC : . y
! CONFIG_DEFAULT_CFQ   : . y
! CONFIG_DIO   : . y
! CONFIG_FB_HP300  : . y
! CONFIG_HIL_MLC   : . y
! CONFIG_HPLANCE   : . y
! CONFIG_HP_SDC: . y
! CONFIG_IP_PNP_BOOTP  : . y
! CONFIG_IP_PNP_DHCP   : . y
! CONFIG_IP_PNP_RARP   : . y
! CONFIG_KEYBOARD_HIL  : . y
! CONFIG_KEYBOARD_HIL_OLD  : . y
! CONFIG_LOGO_LINUX_CLUT224: . y
! CONFIG_LOGO_LINUX_MONO   : . y
! CONFIG_LOGO_LINUX_VGA16  : . y
! CONFIG_LOGO_MAC_CLUT224  : . y
! CONFIG_ROOT_NFS  : . y
! CONFIG_SCTP_COOKIE_HMAC_MD5  : . y
! CONFIG_SCTP_COOKIE_HMAC_SHA1 : . y
! CONFIG_SCTP_DEFAULT_COOKIE_HMAC_MD5  : . y
! CONFIG_SUN3LANCE : . y
! CONFIG_SUN3X_ESP : . y
! CONFIG_BOOTPARAM_HUNG_TASK_PANIC_VALUE   : 0 .
! CONFIG_BOOTPARAM_SOFTLOCKUP_PANIC_VALUE  : 0 .
! CONFIG_MAGIC_SYSRQ_DEFAULT_MASK  : 0x01b6 .
! CONFIG_SCSI_OSD_DPRINT_SENSE : 1 .
! CONFIG_IP_VS_TAB_BITS: 12 .
! CONFIG_DEFAULT_HUNG_TASK_TIMEOUT : 120 .
! CONFIG_NET_EMATCH_STACK  : 32 .
! CONFIG_SERIAL_8250_NR_UARTS  : 4 .
! CONFIG_SERIAL_8250_RUNTIME_UARTS : 4 .
! CONFIG_IP_VS_SH_TAB_BITS : 8 .
! CONFIG_9P_FS : m .
! CONFIG_AMD_PHY   : m .
! CONFIG_AT803X_PHY: m .
! CONFIG_AUFS_FS   : m .
! CONFIG_BCM87XX_PHY   : m .
! CONFIG_BLK_DEV_OSD   : m .
! CONFIG_BRIDGE_EBT_802_3  : m .
! CONFIG_BRIDGE_EBT_AMONG  : m .
! CONFIG_BRIDGE_EBT_ARP: m .
! CONFIG_BRIDGE_EBT_ARPREPLY   : m .
! CONFIG_BRIDGE_EBT_BROUTE : m .
! CONFIG_BRIDGE_EBT_DNAT   : m .
! CONFIG_BRIDGE_EBT_IP : m .
! CONFIG_BRIDGE_EBT_IP6: m .
! CONFIG_BRIDGE_EBT_LIMIT  : m .
! CONFIG_BRIDGE_EBT_LOG: m .
! CONFIG_BRIDGE_EBT_MARK   : m .
! CONFIG_BRIDGE_EBT_MARK_T : m .
! CONFIG_BRIDGE_EBT_NFLOG  : m .
! CONFIG_BRIDGE_EBT_PKTTYPE: m .
! CONFIG_BRIDGE_EBT_REDIRECT   : m .
! CONFIG_BRIDGE_EBT_SNAT   : m .
! CONFIG_BRIDGE_EBT_STP: m .
! CONFIG_BRIDGE_EBT_T_FILTER