Pb with JFFS2 and kernel 2.4.18
Hello, I need help. Context : I use a kernel 2.4.18 from kernel.org adapted to our custom board. The board is based on a MPC860T, has two 8-MBytes AMD29DL323 flash bank and I use a cutsom boot. I have defined a JFFS2 partition on one bank which contains the configuration files and a CRAMFS partition for our root file-system. I use the ELDK-2.0.2 as a distribution. Description : From time to time, on boot, the kernel crashes. The problem seems to be in the physmap_write32() function. A simple test which consists in a succession of creation and destruction of a file in my JFFS2 partition leads to the same crash as well as a succession of mount/umount of the partition. The phenomenon happens when I put a trace level of 0 in both MTD_DEBUG and JFFS2_DEBUG. When I put a trace level of 2 in JFFS2_DEBUG (MTD_DEBUG remaining at 0), the phenomenon seeems to magically disappear. Here is a partial sample of the Oops I got : Oops: kernel access of bad area, sig: 11 NIP: C00B07AC XER: LR: C00AD87C SP: C06F7CF0 REGS: c06f7c40 TRAP: 0300Not tainted MSR: 9032 EE: 1 PR: 0 FP: 0 ME: 1 IR/DR: 11 DAR: C258D00C, DSISR: 8200 TASK = c06f6000[1362] 'touch' Last syscall: 5 last math last altivec GPR00: 0004 C06F7CF0 C06F6000 C01784E8 1985E002 0058000C C06F7D14 0001 GPR08: 0020 C200D000 004C 0001 0010 100210D4 GPR16: C023BECC C06F7DB8 1985E002 C06F7CF8 GPR24: C06F7D08 C019 0001 C023BE90 C023BECC 0058000C C01784E8 C0197990 Call backtrace: 0010 C00AE0C8 C00B0F68 C0081C14 C0081EAC C007C4E8 C003E530 C003E738 C0030E1C C0031278 C000275C 10019264 1E7C 100016F4 0FECED14 Kernel panic: Aiee, killing interrupt handler! In interrupt handler - not syncing Using the ksymoops utility : ksymoops 2.4.4 on i686 2.4.20-8. Options used -v ./vmlinux (specified) -K (specified) -L (specified) -O (specified) -m ./System.map (specified) -t ppc_8xx- -a ppc_8xx- Oops: kernel access of bad area, sig: 11 NIP: C00B07AC XER: LR: C00AD87C SP: C06F7CF0 REGS: c06f7c40 TRAP: 0300Not tainted MSR: 9032 EE: 1 PR: 0 FP: 0 ME: 1 IR/DR: 11 TASK = c06f6000[1362] 'touch' Last syscall: 5 last math last altivec GPR00: 0004 C06F7CF0 C06F6000 C01784E8 1985E002 0058000C C06F7D14 0001 GPR08: 0020 C200D000 004C 0001 0010 100210D4 GPR16: C023BECC C06F7DB8 1985E002 C06F7CF8 GPR24: C06F7D08 C019 0001 C023BE90 C023BECC 0058000C C01784E8 C0197990 Call backtrace: 0010 C00AE0C8 C00B0F68 C0081C14 C0081EAC C007C4E8 C003E530 C003E738 C0030E1C C0031278 C000275C 10019264 1E7C 100016F4 0FECED14 Kernel panic: Aiee, killing interrupt handler! Warning (Oops_read): Code line not seen, dumping what data is available ???; c00b07ac physmap_write32+4/10 = Trace; 0010 Before first symbol Trace; c00ae0c8 cfi_amdstd_write+424/be4 Trace; c00b0f68 part_write+ac/c0 Trace; c0081c14 mtd_fake_writev+68/cc Trace; c0081eac jffs2_write_dnode+10c/224 Trace; c007c4e8 jffs2_create+148/444 Trace; c003e530 vfs_create+b0/10c Trace; c003e738 open_namei+1ac/63c Trace; c0030e1c filp_open+58/84 Trace; c0031278 sys_open+4c/fc Trace; c000275c ret_from_syscall_1+0/b4 Trace; 10019264 Before first symbol Trace; 1e7c Before first symbol Trace; 100016f4 Before first symbol Trace; 0feced14 Before first symbol Trace; Before first symbol 1 warning issued. Results may not be reliable. Furthermore, after the Oops, when I reset the board (short Power Off/Power On), now the boot now the Init process claims not to be able to read the flash :-( Guess : AFAIK, JFFS2 mechanism involves a garbage collector. Is there any misfortune that I got a write cycle while the GC thread tryes to recover the files ? Thus is there any kind of mutual exclusion to be planed in both mechanisms in order to prvent this crash ? Is it (I hope not) a hardware problem ? Thanks in advance Bests regards Boris Buiron Thales Communications France ** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
(Sudo off topic)Simple cheap IDE intrerface for IBM 405
Hi Conn, we attached a CompactFlash socket to the 405's external bus on our CPCI405 CompactPCI board. The board is directly supported by the linuxppc_2_4_devel tree. The tree includes a driver for simple memorymapped CompactFlash cards. Matthias ** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
Denx linuxdevel
Hi, Does the current cvs tree of linuxdev on denx past to 2.4.21 ??? I don't have access to cvs here. Thanks a lot Cedric --- AUBERT Cedric SDEL Controle Commande Service RD rue Nungesser Coli 44860 St Aignan de Grand Lieu Tel : +33 (0)2 40 84 50 00 Poste : 5109 Fax : +33 (0)2 40 84 51 10 E-mail : cedric_aubert at yahoo.fr Web : http://www.controle-commande.sdel.fr ** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
Denx linuxdevel
Dear Cedric, in message 20030626111559.21943.qmail at web41805.mail.yahoo.com you wrote: Does the current cvs tree of linuxdev on denx past to 2.4.21 ??? 2.4.21 is still pretty new - less than two weeks old. I think we will move to 2.4.21 soon, but not within the next few days. Until then you should be able to use our existing 2.4.20 code. I don't have access to cvs here. Please let me know if there is something I can do to help you (providing a snapshot for FTP or similar). Best regards, Wolfgang Denk -- Software Engineering: Embedded and Realtime Systems, Embedded Linux Phone: (+49)-8142-4596-87 Fax: (+49)-8142-4596-88 Email: wd at denx.de As in certain cults it is possible to kill a process if you know its true name. -- Ken Thompson and Dennis M. Ritchie ** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
PCI DMA memory problem
The problem was a wrong PCI configuration of the 405 with two colliding PCI target mappings (PTM1 and PTM2). Oliver To map the data buffers from skb the driver uses pci_map_single(). When starting the kernel with SDRAM size configurations other than 32MByte the device is unable to transfer data (currupted data) - descriptor dword read/write-back works (set up with pci_alloc_consistent()). For the kernel start option mem=32MB everything is fine (descriptor + correct data). My first thought is -- is/are the SDRAM bank(s) configured correctly? I don't know that it'd necessarily be related, but for the 405GP, PPCBoot 1.2.0 doesn't have the PCI bridge setup quite right for all PCI devices (eg. 82559 won't work). I have code to fix the bridge setup if you need it -- although I'm not even certain they exist in the GPR. ** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
pcf8563 and i2c kernel abstarct
Hell there.
I have some toubles using pcf8563_rtc driver. It causes 'kernel panic'
in rtc_rd function. I've done some debugging, ad discoverd what
back-follows:
- i2c_client *clnt is not set on call to rtc_rd
- it was called from pcf8563_rtc_init (by now = pcf8563_get_rtc_time();)
- clnt is created in pcf8563_attach
- prior call to i2c_add_driver(pcf8563_driver) does not call
pcf8563_attach, which should be caled from this part of
i2c-core.c:i2c_add_driver:
/* now look for instances of driver on our adapters
if (driver-flags (I2C_DF_NOTIFY|I2C_DF_DUMMY)) {
for (i=0;iI2C_ADAP_MAX;i++)
if (adapters[i]!=NULL)
/*
Ignore errors */
driver-attach_adapter(adapters[i]);
-this is because adapters[...] are not set
Q:
- did i miss anything adding this driver
- where and how adaptes should be set
?
I need only add support in ppc_md, so I can write my own functions to
implement talking with pcf8563. But... why to reinvent working (or not
?) code?
--
* * * * * * * * * * * *
* per pedes ad astra! *
* * * * * * * * * * * *mailto:krom at dgt-lab.com.pl
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
pcf8563 and i2c kernel abstarct
i've forgot to call si2c_init before, now there is another starnge thig, here is my backtrace #0 add_wait_queue_exclusive (q=0xc01ba738, wait=0xc03f7f28) at linux/include/linux/list.h:44 #1 0xc00095bc in __down (sem=0xc01ba730) at semaphore.c:79 #2 0xc00e83a0 in i2c_add_driver (driver=0xc017d3fc) at linux/include/asm/semaphore.h:94 #3 0xc018deb0 in pcf8563_rtc_init () at pcf8563.c:265 #4 0xc018d92c in misc_init () at misc.c:270 #5 0xc018d1b0 in chr_dev_init () at mem.c:677 #6 0xc01866dc in do_initcalls () at init/main.c:474 #7 0xc0186724 in do_basic_setup () at init/main.c:558 #8 0xc0002294 in init (unused=0x1) at init/main.c:574 #9 0xc0006d24 in kernel_thread () at time.c:447 -- * * * * * * * * * * * * * per pedes ad astra! * * * * * * * * * * * * *mailto:krom at dgt-lab.com.pl ** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
EP405 network interface
Hi all, I cannot get the NIC working on my EP405. I used the ep405_config from the linuxppc_2_4_devel tree. This is a part of the output: ... loop: loaded (max 8 devices) eth0: No PHY device found. removing net dev ... So it seems that the kernel doesn't find the NIC (but it is there, and working, ep-bootloader can use it to download the image). Anybody an idea? I already checked the NIC support, and the onboard-IBM NIC support is enabled. Regards, -- Toni Van Remortel Wetenschappelijk Medewerker - D-science lab Tel: 03 205 61 72 - Fax: 03 205 61 95 E-mail: t.vanremortel at ha.be ** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
flash AMD
At 05:10 PM 6/26/2003 -0400, greggiraud at netcourrier.com wrote: Hi, I try to use my flash on my custom card. It's like a MPC8260ADS. The flash is the AMD AM29DL323GB. I read some source from ppcboot with am29dl323b. And for the moment I just want to ask the flash the manufacturor id. I try the source that I have found, but it doesnt function. When I make the autodelect sequence, and then read the first word, normally I would read the manufacturor ID, but I read the word that is the flash. So is someone has used this flash? Have you got source or ideas about that? Nota: I initialisaze the flash when ppcboot is relocated in the ram. grego greggiraud at netcourrier.com The flash control sequences are merely memory reads and write. I usually use a debugger to do the flash write sequences by hand (per the manufacturer's data sheet) to put the flash in read ID mode and then read it out, again via the debugger. This gives me the best way to try all the potential combinations (bus width, chip width, etc.) and figure out what the proper memory operations are to make it work. Even when I think I know what the configuration is, I usually do the hand operations to verify that it really works (and have been surprised more than once :-). Note that you can very easily test your understanding of the erase and write algorithms this way too. gvb ** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
EP405 network interface
Did you enable the phy in the Board Control Status Register? -Original Message- From: Toni Van Remortel [mailto:[EMAIL PROTECTED] Sent: Thursday, June 26, 2003 10:01 AM To: PPC Mailinglist Subject: EP405 network interface Hi all, I cannot get the NIC working on my EP405. I used the ep405_config from the linuxppc_2_4_devel tree. This is a part of the output: ... loop: loaded (max 8 devices) eth0: No PHY device found. removing net dev ... So it seems that the kernel doesn't find the NIC (but it is there, and working, ep-bootloader can use it to download the image). Anybody an idea? I already checked the NIC support, and the onboard-IBM NIC support is enabled. Regards, -- Toni Van Remortel Wetenschappelijk Medewerker - D-science lab Tel: 03 205 61 72 - Fax: 03 205 61 95 E-mail: t.vanremortel at ha.be ** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
EP405 network interface
I ended up hard-coding the interface since the 2_4_devel tree was shifting on EP405 support quite a bit. Some EP405 boards worked and some didn't. Once you tell it it definitely has one (unconditionally) it sails along smoothly. I also found that booting out of flash does the same thing regardless of the EP405 board. I had to initialize the interface via the firmware before the Linux driver work work. I wasn't able to hard-code around that one. Another point to keep in mind - the linux bootloader code will assume clock rates for everything. They're not always correct and that screwed up a lot of things. You may want to double check those. } Did you enable the phy in the Board Control Status Register? } } -Original Message- } From: Toni Van Remortel [mailto:t.vanremortel at ha.be] } Sent: Thursday, June 26, 2003 10:01 AM } To: PPC Mailinglist } Subject: EP405 network interface } } } } Hi all, } } I cannot get the NIC working on my EP405. I used the ep405_config from } the linuxppc_2_4_devel tree. } } This is a part of the output: } } ... } loop: loaded (max 8 devices) } eth0: No PHY device found. } removing net dev } ... } } So it seems that the kernel doesn't find the NIC (but it is there, and } working, ep-bootloader can use it to download the image). } } Anybody an idea? } } I already checked the NIC support, and the onboard-IBM NIC support is } enabled. } } Regards, } -- }Toni Van Remortel } Wetenschappelijk Medewerker - D-science lab } Tel: 03 205 61 72 - Fax: 03 205 61 95 } E-mail: t.vanremortel at ha.be } } ** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
(Sudo off topic)Simple cheap IDE intrerface for IBM 405
Hello Matthias, Actualy it was a quest for a compact flash interface that started me on this IDE interface saga to begin with. I knew you could build an adapter to access compact flash cheaply/easily. Would it be posssible to give me ( or post ) a list of signal names of what 405 signal connects to what compact flash signal in your interface? I can understand if you say no. Also was the compact flash connected dirrectly to the data and address bus or did you need to buffer it in some way? Matthias Fuchs wrote: Hi Conn, we attached a CompactFlash socket to the 405's external bus on our CPCI405 CompactPCI board. The board is directly supported by the linuxppc_2_4_devel tree. The tree includes a driver for simple memorymapped CompactFlash cards. Matthias Just the fact that I now know it can be done is of great help. Thanks Conn -- * If you live at home long enough, your parents will move out. (Warning they may try to sell their house out from under you.) * Conn Clark Engineering Stooge clark at esteem.com Electronic Systems Technology Inc. www.esteem.com ** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
Using the Linux kgdb-kernel with the Walnut.
Hi, I am trying to boot up the Linux kgdb-kernel.2.4.18 on a Walnut board, but it just freezes after it uncompressed the kernel. Here is a screen shot: .. EMAC0 Ethernet Test OK. ENET Speed is 100 Mbs... FULL duplex connection Booting from [ENET] Ethernet ... Sending bootp request ... Loading file //zImage ... Sending tftp boot request ... Transfer Complete ... Loaded successfully ... Entry point at 0x50 ... loaded at: 0050 005A9238 relocated to: 0040 004A9238 board data at: 004A6168 004A61A8 relocated to: 004A6128 004A6168 zimage at: 004059DC 004A54DA avail ram: 004AA000 0200 Linux/PPC load: root=/dev/nfs ip=192.003.1.5:192.003.1.1::255.255.255.0:walnut:eth0:off nfsroot=192.168.1.1:/home/nfs/walnut Uncompressing Linux...done. Now booting the kernel ... And it just hangs. I think this when it's waiting for input from the serial port 2 from the debugger then proceeds. I hooked up an other session of minicom to the second serial port on the Walnut, but only see garbages, $S04#b7,... . I tried all the baudrates available and got different outputs or blank, all of which are incomprehensible. Has anyone got the Linux kgdb-kernel.2.4.18 to work with the Walnut board? Any help would be appreciated, Andy ** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
flash AMD
Hi, I try to use my flash on my custom card. It's like a MPC8260ADS. The flash is the AMD AM29DL323GB. I read some source from ppcboot with am29dl323b. And for the moment I just want to ask the flash the manufacturor id. I try the source that I have found, but it doesnt function. When I make the autodelect sequence, and then read the first word, normally I would read the manufacturor ID, but I read the word that is the flash. So is someone has used this flash? Have you got source or ideas about that? Nota: I initialisaze the flash when ppcboot is relocated in the ram. grego greggiraud at netcourrier.com ** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
