Re: Katmai w/ DENX git - init has generated signal 4 error
I'm using the Denx linux-2.6-denx.git repository with a Katmai board. I want to boot off a disk (initialized w/ Debian 4.0). I've installed a Promise Ultra133 Tx2 IDE controller card in the PCI slot, and configured it in the kernel.I boot this same disk w/ IDE card on other 4xx boards without a problem (Bamboo w/ Denx 4.1 for example). I am getting an error init has generated signal 4 but has no handler for it. I believe the problem may be due to lack of HW FP on the processor(?). Copying an embedded 440 RFS on disk works OK. ___ Linuxppc-embedded mailing list Linuxppc-embedded@ozlabs.org https://ozlabs.org/mailman/listinfo/linuxppc-embedded
Re: Katmai w/ DENX git - init has generated signal 4 error
Josh Boyer [EMAIL PROTECTED] wrote on 06/26/2007 01:12:38 PM: Signal 4 is SIGILL, which could be returned for float instructions I suppose. Try turning on CONFIG_MATH_EMULATION in your kernel config for Katmai and see if the problem goes away. Thanks Josh - that actually did the trick w/ the original distro (which apparently generates some FP ops). Valentine Barshak [EMAIL PROTECTED] wrote on 06/26/2007 01:58:23 PM: Looks like 440SPe entry is missing in the arch/ppc/kernel/cputable.c I'm using a git snapshot version of the DENX kernel - is there some effort underway to start to merge this platform support into the public tree? ___ Linuxppc-embedded mailing list Linuxppc-embedded@ozlabs.org https://ozlabs.org/mailman/listinfo/linuxppc-embedded
Katmai w/ DENX git - init has generated signal 4 error
I'm using the Denx linux-2.6-denx.git repository with a Katmai board. I want to boot off a disk (initialized w/ Debian 4.0). I've installed a Promise Ultra133 Tx2 IDE controller card in the PCI slot, and configured it in the kernel.I boot this same disk w/ IDE card on other 4xx boards without a problem (Bamboo w/ Denx 4.1 for example). I am getting an error init has generated signal 4 but has no handler for it. ## Booting image at 0020 ... Image Name: Linux-2.6.22-rc5-gc8144983-dirty Image Type: PowerPC Linux Kernel Image (gzip compressed) Data Size:1328285 Bytes = 1.3 MB Load Address: Entry Point: Verifying Checksum ... OK Uncompressing Kernel Image ... OK Linux version 2.6.22-rc5-gc8144983-dirty ([EMAIL PROTECTED]) (gcc ve rsion 4.0.0 (DENX ELDK 4.1 4.0.0)) #4 Mon Jun 25 13:59:54 EDT 2007 AMCC PowerPC 440SPe Katmai Platform Zone PFN ranges: DMA 0 - 131072 Normal 131072 - 131072 early_node_map[1] active PFN ranges 0:0 - 131072 Built 1 zonelists. Total pages: 130048 Kernel command line: console=ttyS0,115200 root=/dev/hde3 rw ip=dhcp PID hash table entries: 2048 (order: 11, 8192 bytes) Dentry cache hash table entries: 65536 (order: 6, 262144 bytes) Inode-cache hash table entries: 32768 (order: 5, 131072 bytes) Memory: 516864k available (2008k kernel code, 676k data, 160k init, 0k highmem) Mount-cache hash table entries: 512 NET: Registered protocol family 16 PCI: Probing PCI hardware SCSI subsystem initialized NET: Registered protocol family 2 IP route cache hash table entries: 16384 (order: 4, 65536 bytes) TCP established hash table entries: 65536 (order: 7, 524288 bytes) TCP bind hash table entries: 65536 (order: 6, 262144 bytes) TCP: Hash tables configured (established 65536 bind 65536) TCP reno registered io scheduler noop registered io scheduler anticipatory registered (default) io scheduler deadline registered io scheduler cfq registered Generic RTC Driver v1.07 Serial: 8250/16550 driver $Revision: 1.90 $ 4 ports, IRQ sharing enabled serial8250: ttyS0 at MMIO 0x0 (irq = 0) is a 16550A serial8250: ttyS1 at MMIO 0x0 (irq = 1) is a 16550A serial8250: ttyS2 at MMIO 0x0 (irq = 37) is a 16550A RAMDISK driver initialized: 16 RAM disks of 4096K size 1024 blocksize xsysace xsysace.0: Xilinx SystemACE revision 1.0.12 xsysace xsysace.0: capacity: 256512 sectors xsa: xsa1 Intel(R) PRO/1000 Network Driver - version 7.3.20-k2 Copyright (c) 1999-2006 Intel Corporation. PPC 4xx OCP EMAC driver, version 3.54 mal0: initialized, 1 TX channels, 1 RX channels eth0: emac0, MAC 00:01:73:77:55:27 eth0: found Generic MII PHY (0x01) e100: Intel(R) PRO/100 Network Driver, 3.5.17-k4-NAPI e100: Copyright(c) 1999-2006 Intel Corporation Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2 ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx PDC20269: IDE controller at PCI slot :00:01.0 PDC20269: chipset revision 2 PDC20269: ROM enabled at 0x000dc000 PDC20269: PLL input clock is 33309 kHz PDC20269: 100% native mode on irq 52 ide2: BM-DMA at 0xffd0-0xffd7, BIOS settings: hde:pio, hdf:pio ide3: BM-DMA at 0xffd8-0xffdf, BIOS settings: hdg:pio, hdh:pio hde: FUJITSU MHT2040AH, ATA DISK drive hde: host side 80-wire cable detection failed, limiting max speed to UDMA33 ide2 at 0xfff8-0x,0xfff6 on irq 52 hde: max request size: 128KiB hde: 78140160 sectors (40007 MB) w/8192KiB Cache, CHS=65535/16/63, UDMA(33) hde: cache flushes supported hde: hde1 hde2 hde3 i2c /dev entries driver IBM IIC driver v2.1 ibm-iic0: using standard (100 kHz) mode ds1307 1-0068: rtc core: registered ds1307 as rtc0 ibm-iic1: using standard (100 kHz) mode TCP cubic registered NET: Registered protocol family 1 NET: Registered protocol family 17 ds1307 1-0068: setting the system clock to 2000-04-30 08:13:25 (957082405) eth0: link is up, 100 FDX Sending DHCP requests ., OK IP-Config: Got DHCP answer from 255.255.255.255, my address is 9.27.218.226 IP-Config: Complete: device=eth0, addr=9.27.218.226, mask=255.255.255.128, gw=9.27.218.129, host=9.27.218.226, domain=raleigh.ibm.com, nis-domain=(none), bootserver=255.255.255.255, rootserver=255.255.255.255, rootpath= kjournald starting. Commit interval 5 seconds EXT3 FS on hde3, internal journal EXT3-fs: mounted filesystem with ordered data mode. VFS: Mounted root (ext3 filesystem). Freeing unused kernel memory: 160k init init has generated signal 4 but has no handler for it Kernel panic - not syncing: Attempted to kill init! Rebooting in 180 seconds.. Not sure if I'm missing something obvious - any help appreciated. Thanks, Steve ___ Linuxppc-embedded mailing list Linuxppc-embedded@ozlabs.org https://ozlabs.org/mailman/listinfo/linuxppc-embedded
USB support for Bamboo/440EP (Yosemite/440EPx)
Is there an intention to add the configuration for the USB host controller for Bamboo/Yosemite to the mainline kernel? drivers/usb/host contains ohci-ppc-soc.c/h, but the Kconfig isn't updated to include it for 440EP/EPx? I noticed it is configured in the Denx 4.1 2.6.19.2 kernel. When I updated the 2.6.21 drivers/usb/host/Kconfig to include the controller support for 440EP for some reason I couldn't get the kernel to recognize the controller or devices when it boots - not sure if there is something else I am missing here? One thing I noticed was that in the 2.6.19.2 kernel CONFIG_USB_OHCI_BIG_ENDIAN gets defined - in 2.6.21 there is both CONFIG_USB_OHCI_BIG_ENDIAN_DESC and CONFIG_USB_OHCI_BIG_ENDIAN_MMIO - assume I want both defined? Wondering also if anyone has much experience using the USB interface on Bamboo - and if any reliability issues have been observed? I have a Bamboo system where we've added graphics card init capability to PIBS and are using the DENX 2.6.19.2 kernel and booting X (Xorg 7.1.1 - Debian 4.0 system on hard disk) with a USB keyboard and mouse - and sometimes the mouse/keyboard are not detected properly by either the kernel on boot, or by X during its initialization (sometimes even after the kernel seems to detect everything fine). I did play a bit with a memory stick on the interface and that seemed reliable for the little I did with it. I am using an Apple keyboard plugged into the USB port on the board, with an IBM Scrollpoint USB mouse plugged into one of the ports on the keyboard. An excerpt of the kernel boot when it finds everything OK: ... IBM mouse - input driver mouse interface hde: cache flushes supported hde: hde1 hde2 hde3 ppc-soc-ohci ppc-soc-ohci.0: USB Host Controller ppc-soc-ohci ppc-soc-ohci.0: new USB bus registered, assigned bus number 1 ppc-soc-ohci ppc-soc-ohci.0: irq 40, io mem 0xef601000 usb usb1: Product: USB Host Controller usb usb1: Manufacturer: Linux 2.6.19.2 ohci_hcd usb usb1: SerialNumber: PPC-SOC USB usb usb1: configuration #1 chosen from 1 choice hub 1-0:1.0: USB hub found hub 1-0:1.0: 2 ports detected Initializing USB Mass Storage driver... usbcore: registered new interface driver usb-storage USB Mass Storage support registered. usbcore: registered new interface driver usbhid drivers/usb/input/hid-core.c: v2.6:USB HID core driver pegasus: v0.6.14 (2006/09/27), Pegasus/Pegasus II USB Ethernet driver usbcore: registered new interface driver pegasus i8042.c: No controller found. mice: PS/2 mouse device common for all mice TCP cubic registered NET: Registered protocol family 1 NET: Registered protocol family 17 usb 1-1: new full speed USB device using ppc-soc-ohci and address 2 usb 1-1: Product: Hub in Apple Extended USB Keyboard usb 1-1: Manufacturer: Mitsumi Electric usb 1-1: configuration #1 chosen from 1 choice hub 1-1:1.0: USB hub found hub 1-1:1.0: 3 ports detected eth0: link is up, 100 FDX, pause enabled eth1: link is down usb 1-1.1: new low speed USB device using ppc-soc-ohci and address 3 usb 1-1.1: configuration #1 chosen from 1 choice input: HID 04b3:3100 as /class/input/input0 input: USB HID v1.00 Mouse [HID 04b3:3100] on usb-PPC-SOC USB-1.1 usb 1-1.3: new full speed USB device using ppc-soc-ohci and address 4 usb 1-1.3: Product: Apple Extended USB Keyboard usb 1-1.3: Manufacturer: Mitsumi Electric usb 1-1.3: configuration #1 chosen from 1 choice input: Mitsumi Electric Apple Extended USB Keyboard as /class/input/input1 input: USB HID v1.10 Keyboard [Mitsumi Electric Apple Extended USB Keyboard] on usb-PPC-SOC USB-1.3 input: Mitsumi Electric Apple Extended USB Keyboard as /class/input/input2 input: USB HID v1.10 Device [Mitsumi Electric Apple Extended USB Keyboard] on us b-PPC-SOC USB-1.3 Sending DHCP requests .,. OK ... Sometimes though it does not find the mouse: ... hde: 78140160 sectors (40007 MB) w/8192KiB Cache, CHS=65535/16/63 hde: cache flushes supported hde: hde1 hde2 hde3 ppc-soc-ohci ppc-soc-ohci.0: USB Host Controller ppc-soc-ohci ppc-soc-ohci.0: new USB bus registered, assigned bus number 1 ppc-soc-ohci ppc-soc-ohci.0: irq 40, io mem 0xef601000 usb usb1: Product: USB Host Controller usb usb1: Manufacturer: Linux 2.6.19.2 ohci_hcd usb usb1: SerialNumber: PPC-SOC USB usb usb1: configuration #1 chosen from 1 choice hub 1-0:1.0: USB hub found hub 1-0:1.0: 2 ports detected Initializing USB Mass Storage driver... usbcore: registered new interface driver usb-storage USB Mass Storage support registered. usbcore: registered new interface driver usbhid drivers/usb/input/hid-core.c: v2.6:USB HID core driver pegasus: v0.6.14 (2006/09/27), Pegasus/Pegasus II USB Ethernet driver usb 1-1: new full speed USB device using ppc-soc-ohci and address 2 usb 1-1: Product: Hub in Apple Extended USB Keyboard usb 1-1: Manufacturer: Mitsumi Electric usb 1-1: configuration #1 chosen from 1 choice hub 1-1:1.0: USB hub found hub 1-1:1.0: 3 ports detected usb 1-1.1: new low speed USB device using ppc-soc-ohci and address 3
Re: USB support for Bamboo/440EP (Yosemite/440EPx)
Gerhard Jaeger [EMAIL PROTECTED] wrote on 05/14/2007 10:31:04 AM:
Hi Stephen,
I also played with Bamboo and Yosemite USB and found out, that the OHCI
ISR contains an assumption that makes the 440 OHCI implementation
sometimes
stop when having a timeout condition. Find the following sequence @
function
ohci_irq() (in file ohci-hcd.c) and disable the following code:
if ((ohci-hcca-done_head != 0)
! (hc32_to_cpup (ohci,
ohci-hcca-done_head)
0x01)) {
ints = OHCI_INTR_WDH;
}
This should make the USB host work reliably on the 440s.
Thanks Gerhard. This definitely makes things work better - I have had
100% success in both the kernel and X recognizing the devices and having X
boot with this update.
However, I am occasionally still having an issue after X comes up with the
keyboard not working (mouse working fine). Just to be clear - I only want
to comment out the code you indicated above - not also any/either of the
else/if clauses, correct?
So has this never been formally reported/patched? Do you know also why
the USB support has not been configured in the mainline kernel for these
platforms - is it due to known existing issues?
___
Linuxppc-embedded mailing list
Linuxppc-embedded@ozlabs.org
https://ozlabs.org/mailman/listinfo/linuxppc-embedded
Fw: Configuring PCI w/ 44x
Eugene Surovegin ebs at ebshome.net wrote on 05/02/2006 07:49:16 PM: On Tue, May 02, 2006 at 04:58:32PM -0400, Stephen Winiecki wrote: I have a question regarding configuring PCI with 44x. Using 2.6.17-rc3 as a reference, PCI_CONFIG is defined for the 44x defconfigs, and Kconfig is not enabled to reflect/change the setting for 44x. When I update arch/ppc/Kconfig to enable configuring or not configuring PCI with 44x, and then don't configure it, the kernel won't compile: Hmm, you cannot disable PCI for 44x in the current 2.6. It's always enabled. If you changed Konfig to be able to do so, why are you complaining here? It's not enough to just change Konfig, you have to modify Ocotea port as well. Look for example how this is handled for 85xx. Patches are welcome. -- Eugene I was first wondering if for some reason defaulting/forcing PCI to always be configured for 44x was intentional. I was second reporting the fact that if a change is made to not configure PCI for 44x, the kernel will not compile. Steve -- next part -- An HTML attachment was scrubbed... URL: http://ozlabs.org/pipermail/linuxppc-embedded/attachments/20060503/a78f022f/attachment.htm
Configuring PCI w/ 44x
I have a question regarding configuring PCI with 44x. Using 2.6.17-rc3 as a reference, PCI_CONFIG is defined for the 44x defconfigs, and Kconfig is not enabled to reflect/change the setting for 44x. When I update arch/ppc/Kconfig to enable configuring or not configuring PCI with 44x, and then don't configure it, the kernel won't compile: arch/ppc/kernel/built-in.o: In function `__dma_alloc_coherent': arch/ppc/kernel/dma-mapping.c:231: undefined reference to `pci_dram_offset' arch/ppc/kernel/dma-mapping.c:231: undefined reference to `pci_dram_offset' arch/ppc/mm/built-in.o: In function `ioport_map': arch/ppc/mm/pgtable.c:265: undefined reference to `isa_io_base' arch/ppc/mm/pgtable.c:265: undefined reference to `isa_io_base' arch/ppc/mm/built-in.o: In function `__ioremap': arch/ppc/mm/pgtable.c:187: undefined reference to `isa_mem_base' arch/ppc/mm/pgtable.c:187: undefined reference to `isa_mem_base' arch/ppc/mm/pgtable.c:187: undefined reference to `isa_mem_base' arch/ppc/mm/pgtable.c:187: undefined reference to `isa_mem_base' arch/ppc/syslib/built-in.o: In function `outb': include/asm/io.h:299: undefined reference to `isa_io_base' arch/ppc/syslib/built-in.o: In function `todc_m48txx_write_val': include/asm/io.h:299: undefined reference to `isa_io_base' arch/ppc/syslib/built-in.o: In function `outb': include/asm/io.h:299: undefined reference to `isa_io_base' arch/ppc/syslib/built-in.o: In function `todc_mc146818_read_val': include/asm/io.h:299: undefined reference to `isa_io_base' arch/ppc/syslib/built-in.o: In function `outb': include/asm/io.h:299: undefined reference to `isa_io_base' arch/ppc/syslib/built-in.o:include/asm/io.h:299: more undefined references to `isa_io_base' follow arch/ppc/syslib/built-in.o: In function `pciauto_setup_bars': arch/ppc/syslib/pci_auto.c:56: undefined reference to `early_write_config_dword' arch/ppc/syslib/pci_auto.c:61: undefined reference to `early_read_config_dword' arch/ppc/syslib/pci_auto.c:93: undefined reference to `early_write_config_dword' arch/ppc/syslib/pci_auto.c:108: undefined reference to `early_write_config_dword' arch/ppc/syslib/built-in.o: In function `pciauto_prescan_setup_bridge': arch/ppc/syslib/pci_auto.c:130: undefined reference to `early_write_config_byte' arch/ppc/syslib/pci_auto.c:135: undefined reference to `early_write_config_byte' arch/ppc/syslib/pci_auto.c:140: undefined reference to `early_write_config_byte' arch/ppc/syslib/pci_auto.c:155: undefined reference to `early_write_config_word' arch/ppc/syslib/pci_auto.c:160: undefined reference to `early_write_config_byte' arch/ppc/syslib/pci_auto.c:165: undefined reference to `early_write_config_word' arch/ppc/syslib/pci_auto.c:172: undefined reference to `early_write_config_dword' arch/ppc/syslib/pci_auto.c:177: undefined reference to `early_write_config_dword' arch/ppc/syslib/built-in.o: In function `pciauto_postscan_setup_bridge': arch/ppc/syslib/pci_auto.c:194: undefined reference to `early_write_config_byte' arch/ppc/syslib/pci_auto.c:208: undefined reference to `early_write_config_word' arch/ppc/syslib/pci_auto.c:215: undefined reference to `early_write_config_word' arch/ppc/syslib/pci_auto.c:223: undefined reference to `early_write_config_word' arch/ppc/syslib/pci_auto.c:234: undefined reference to `early_write_config_byte' arch/ppc/syslib/pci_auto.c:239: undefined reference to `early_write_config_word' arch/ppc/syslib/pci_auto.c:246: undefined reference to `early_read_config_dword' arch/ppc/syslib/pci_auto.c:251: undefined reference to `early_write_config_dword' arch/ppc/syslib/built-in.o: In function `pciauto_prescan_setup_cardbus_bridge': arch/ppc/syslib/pci_auto.c:269: undefined reference to `early_write_config_byte' arch/ppc/syslib/pci_auto.c:274: undefined reference to `early_write_config_byte' arch/ppc/syslib/pci_auto.c:279: undefined reference to `early_write_config_byte' arch/ppc/syslib/pci_auto.c:294: undefined reference to `early_write_config_dword' arch/ppc/syslib/pci_auto.c:299: undefined reference to `early_write_config_dword' arch/ppc/syslib/built-in.o: In function `pciauto_postscan_setup_cardbus_bridge': arch/ppc/syslib/pci_auto.c:321: undefined reference to `early_write_config_byte' arch/ppc/syslib/pci_auto.c:347: undefined reference to `early_write_config_dword' arch/ppc/syslib/pci_auto.c:355: undefined reference to `early_write_config_dword' arch/ppc/syslib/pci_auto.c:362: undefined reference to `early_read_config_dword' arch/ppc/syslib/pci_auto.c:367: undefined reference to `early_write_config_dword' arch/ppc/syslib/built-in.o: In function `pciauto_bus_scan': arch/ppc/syslib/pci_auto.c:403: undefined reference to `early_read_config_byte' arch/ppc/syslib/pci_auto.c:413: undefined reference to `early_read_config_word' arch/ppc/syslib/pci_auto.c:420: undefined reference to `early_read_config_dword' arch/ppc/syslib/pci_auto.c:493: undefined reference to `early_read_config_dword' arch/ppc/syslib/pci_auto.c:498: undefined reference to `early_write_config_dword'
