This is the mail archive of the ecos-discuss@sources.redhat.com mailing list for the eCos project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: crash in tftp_client_test.c


> > It appears that the interrupts where not set correctly. The
> > hal_intc_translation_table in variant.inc did not route all the
interrupts
> > correctly (some but not all) . The HAL_PCI_TRANSLATE_INTERRUPT was not
> > routing the interrupts to the correct vector for that pci chip. The
> > experimental observations of the problem where confusing.
>
> Can you contribute a patch?

No problem , I will contribute the board port once it is tested. The 2 items
changed
are specific to that board and which interrupt was wired to the pci chip.
>


> Its not the tftp program thats at fault. Its probably your HAL or the
> ethernet device driver. You need to debug this further to see what is
> going on. It's is not a problem anyone else has seen before, so there
> is no package, enhancement, workaround etc.....

I would have suspected the stack or the application , the driver should
pass all packets received ?????.

>
> How old is the redboot on your device? A year ago there was a problem
> with NTP Broadcast's killing redboot, but i expect you have a more
> recent version.
yes

>
> I would try reproducing the problem with a low bandwidth test, eg
> pings. Once you can get the system crashing with this, then put some
> breakpoints in which are called when broadcast packets are received
> and then trace it through to see why it crashes.
>
I will try your suggestion

thank you

Henri



-- 
Before posting, please read the FAQ: http://sources.redhat.com/fom/ecos
and search the list archive: http://sources.redhat.com/ml/ecos-discuss


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]