# ksymoops-cris < oops_ext3.txt
ksymoops-cris
/usr/bin/nm: os/linux-2.6/vmlinux: cible bfd invalide
ksymoops 2.4.11 on i686 2.6.17-10-generic. Options used
-v os/linux-2.6/vmlinux (specified)
-K (specified)
-L (specified)
-O (specified)
-m os/linux-2.6/System.map (specified)
-t cris -a cris
Error (pclose_local): read_nm_symbols pclose failed 0x100
Warning (read_vmlinux): no kernel symbols in vmlinux, is
os/linux-2.6/vmlinux a valid vmlinux file?
IRP: c014dc4c SRP: c014e090 DCCR: 00000408 USP: 00000000 MOF: 00000000
r0: c01f9a6c r1: c01f9a6c r2: 00000001 r3: c051ceff
r4: b0000028 r5: b0000028 r6: c04f3bc0 r7: 00000000
r8: c0385f4c r9: 000000ff r10: 00000000 r11: b0000028
r12: 00000007 r13: 00000000 oR10: 00000000 sp: c0385ed8
Process ksoftirqd/0 (pid: 2, stackpage=c0379a80)
Code: 00 b0 6f 1e 6c 9a 1f c0 65 46 61 06 (65) b6 61 26 43 94 fc 94 0e
a0 0f 05
Error (Oops_bfd_perror): /tmp/ksymoops.61flkW Invalid bfd target
>>PC; c014dc4c <SPI_io+20/70> <=====
>>IRP; c014dc4c <SPI_io+20/70>
>>SRP; c014e090 <MMC_put_block+88/96>
>>IRP; c014dc4c <SPI_io+20/70>
>>SRP; c014e090 <MMC_put_block+88/96>
>>r0; c01f9a6c <port_g_data_shadow+0/4>
>>r1; c01f9a6c <port_g_data_shadow+0/4>
>>r3; c051ceff <_end+1f535f/1cd8460>
>>r6; c04f3bc0 <_end+1cc020/1cd8460>
>>r8; c0385f4c <_end+5e3ac/1cd8460>
>>sp; c0385ed8 <_end+5e338/1cd8460>
1 warning and 2 errors issued. Results may not be reliable.
Decoding Code: 00 b0 6f 1e 6c 9a 1f c0 65 46 61 06 (65) b6 61 26 43 94
fc 94 0e a0 0f 05
objdump-cris: oops.code: no symbols
oops.code: file format binary
Disassembly of section .data:
00000000 <.data>:
0: 00b0 blt 0x2
2: 6f1e 6c9a 1fc0 move.d 0xc01f9a6c,$r1
8: 6546 move.d $r5,$r4
a: 6106 move.d $r1,$r0
c: 65b6 move.d $r5,$r11
e: 6126 move.d $r1,$r2
10: 4394 movu.b $r3,$r9
12: fc94 btst $r12,$r9
14: 0ea0 bge 0x24
16: 0f05 nop
Disassembly of os/linux-2.6/vmlinux
PC = 0xc014dc4c
Ooops in function c014dc2c T SPI_io
os/linux-2.6/vmlinux: file format elf32-cris
Disassembly of section .text:
c014dc2c <SPI_io>:
SPI_io():
/home/diva/sdk_patched/devboard-R2_01/os/linux-2.6-tag--devboard-R2_01-1/drivers/fox-normal/mmc/mmc_driver.c:147
// write a byte to the spi bus
// data is send MSB first
unsigned char SPI_io(unsigned char byte){
c014dc2c: fce1 ee8f push $r8
c014dc30: 6e86 move.d $sp,$r8
c014dc32: 98e2 subq 24,$sp
c014dc34: fe5b movem $r5,[$sp]
c014dc36: 4a36 move.b $r10,$r3
/home/diva/sdk_patched/devboard-R2_01/os/linux-2.6-tag--devboard-R2_01-1/drivers/fox-normal/mmc/mmc_driver.c:149
int i;
unsigned char byte_out = 0;
c014dc38: 7a06 clear.b $r10
/home/diva/sdk_patched/devboard-R2_01/os/linux-2.6-tag--devboard-R2_01-1/drivers/fox-normal/mmc/mmc_driver.c:150
for(i = 7; i>=0; i--){
c014dc3a: 47c2 moveq 7,$r12
c014dc3c: 6f5e 2800 00b0 move.d b0000028
<__crc_dev_change_flags+0x38088a>,$r5
c014dc42: 6f1e 6c9a 1fc0 move.d c01f9a6c
<port_g_data_shadow>,$r1
c014dc48: 6546 move.d $r5,$r4
c014dc4a: 6106 move.d $r1,$r0
Disassembly of section .exit.text:
Disassembly of section .init.text:
#### OOPS ####
c014dc4c: 65b6 move.d $r5,$r11
c014dc4e: 6126 move.d $r1,$r2
c014dc50: 4394 movu.b $r3,$r9
c014dc52: fc94 btst $r12,$r9
c014dc54: 0ea0 bge c014dc64 <SPI_io+0x38>
c014dc56: 0f05 nop
c014dc58: 619a move.d [$r1],$r9
c014dc5a: 5093 orq 16,$r9
--- In [email protected], John Crispin <[EMAIL PROTECTED]> wrote:
>
> please enable KALLSYMS in the kernel config and then send the oops
output
>
> el8fr wrote:
> > Hi all,
> >
> > I've tested a MMC card with the original (frozen patch) driver and an
> > ext3 filesystem. Everything is ok with kernel 2.4 but I get a kernel
> > OOPS with kernel 2.6.
> > I'll be able to send ksymoops output if needed to debug. But for the
> > moment I'm wondering if someone has tested this with this new
driver ?
> >
> > Regards,
> >
> > Seb.
> >
> >
> > --- In [email protected], d191264it <d191264it@> wrote:
> >
> >> I will test soon I will give you the results.
> >>
> >>
> >> Andre ha scritto:
> >>
> >>> You're right. At this point I focussed on the basic read/write and
> >>> compatibility stuff. Functions like that can be integrated, if
> >>> interest exist.
> >>>
> >>> Right now, I would like to know whether people, who also had issues
> >>> with the existing driver, find this version an improvement.
> >>>
> >>> --- In [email protected] <mailto:foxboard%40yahoogroups.com>,
> >>> d191264it <d191264it@> wrote:
> >>>
> >>>> I worked also on that driver in the past and I found that tools
like
> >>>> e2fsck was not working properly due to some missing calls.
> >>>> So I added functions like this:
> >>>>
/*******************************************************************
> >>>>
> >>> ******/
> >>>
> >>>> static int mmc_getgeo(struct block_device *bdev, struct hd_geometry
> >>>>
> >>> *geo)
> >>>
> >>>> {
> >>>> VOLUME_INFO info;
> >>>> MMC_get_volume_info(&info);
> >>>>
> >>>> geo->heads = 4;
> >>>> geo->sectors = 61;
> >>>> geo->cylinders = (info.size / (512*4*61));
> >>>> return 0;
> >>>> }
> >>>> static int mmc_ioctl(struct inode * inode, struct file * file,
> >>>> unsigned int cmd, unsigned long arg)
> >>>> {
> >>>> VOLUME_INFO info;
> >>>> struct hd_geometry __user *loc = (struct hd_geometry __user
> >>>>
> >>> *) arg;
> >>>
> >>>> struct hd_geometry g;
> >>>>
> >>>> if (cmd != HDIO_GETGEO)
> >>>> return -EINVAL;
> >>>> if (!loc)
> >>>> return -EINVAL;
> >>>>
> >>>> MMC_get_volume_info(&info);
> >>>>
> >>>> g.heads = 4;
> >>>> g.sectors = 61;
> >>>> g.cylinders = (info.size / (512*4*61));
> >>>> g.start = get_start_sect(inode->i_bdev);
> >>>> return copy_to_user(loc, &g, sizeof g) ? -EFAULT : 0;
> >>>> }
> >>>>
> >>>> static struct block_device_operations bdops = {
> >>>> .open = mmc_do_open,
> >>>> .release = mmc_release,
> >>>> .media_changed = mmc_has_media_changed,
> >>>> .revalidate_disk = mmc_revalidate,
> >>>> .ioctl = mmc_ioctl,
> >>>> .getgeo = mmc_getgeo,
> >>>> .owner = THIS_MODULE,
> >>>> };
> >>>>
/*******************************************************************
> >>>>
> >>> ******/
> >>>
> >>>> should be fine to have it also in your driver
> >>>>
> >>>>
> >>>>
> >>>>
> >>>> Andre ha scritto:
> >>>>
> >>>>> Performance was not the primary reason for developing this driver.
> >>>>> I had some issues using large cards which were not recognised,
> >>>>>
> >>> also
> >>>
> >>>>> swapping cards frequently made the Fox unstable.
> >>>>>
> >>>>> Both drivers use the same type software spi, so interface speed
> >>>>>
> >>> is in
> >>>
> >>>>> the same range. I did implement stream mode reading/writing which
> >>>>> makes better use of the card's internal buffers. This typically
> >>>>>
> >>> makes
> >>>
> >>>>> larger transfers more effective.
> >>>>> For full effect, this requires the card to be mounted without any
> >>>>> option. (constantly writing to the fat doesn't sounds like a good
> >>>>> idea anyway)
> >>>>>
> >>>>> This way I get about 100 - 200 kiB/s, (regular SD cards) using
> >>>>>
> >>> Debian
> >>>
> >>>>> ftp client to the Fox ftp server. New or erased cards may perform
> >>>>> somewhat better.
> >>>>>
> >>>>> --- In [email protected]
<mailto:foxboard%40yahoogroups.com>
> >>>>>
> >>> <mailto:foxboard%
> >>> 40yahoogroups.com>,
> >>>
> >>>>> John Crispin <john@> wrote:
> >>>>>
> >>>>>> what is the performance like in comparison to the existing
> >>>>>>
> >>> driver ?
> >>>
> >>>>>> Quoting afmdsgn <afmdsgn@>:
> >>>>>>
> >>>>>>
> >>>>>>> Hi All,
> >>>>>>>
> >>>>>>> As I had some issues with the MMC driver in the SDK, I
> >>>>>>>
> >>> developed
> >>>
> >>>>> a new
> >>>>>
> >>>>>>> version that also supports the 2 GB SD and 4 GB HCSD.
> >>>>>>>
> >>>>>>> People interested can have a look at
> >>>>>>> http://www.afmdesign.net/proj/mmc/mmc.html
> >>>>>>>
> >>> <http://www.afmdesign.net/proj/mmc/mmc.html>
> >>>
> >>>>> <http://www.afmdesign.net/proj/mmc/mmc.html
> >>>>>
> >>> <http://www.afmdesign.net/proj/mmc/mmc.html>>
> >>>
> >>>>>>> Please discuss any issues in this group.
> >>>>>>>
> >>>>>>> Greetings Andre.
> >>>>>>>
> >>>>>>>
> >>>>>>>
> >>>>>
> >>>> Chiacchiera con i tuoi amici in tempo reale!
> >>>> http://it.yahoo.com/mail_it/foot/*http://it.messenger.yahoo.com
> >>>>
> >>> <http://it.yahoo.com/mail_it/foot/*http://it.messenger.yahoo.com>
> >>>
> >>>
> >> Chiacchiera con i tuoi amici in tempo reale!
> >> http://it.yahoo.com/mail_it/foot/*http://it.messenger.yahoo.com
> >>
> >>
> >
> >
> >
> >
>
