<?xml version="1.0" encoding="utf-8"?>
<!--  RSS generated by Flaimo.com RSS Builder [2012-02-08 20:01:59]  --> <rss version="2.0" xmlns:im="http://purl.org/rss/1.0/item-images/" xmlns:sy="http://purl.org/rss/1.0/modules/syndication/" >
<channel>
<docs>http://bugs.linux-xtensa.org/</docs>
<description>Mantis - ISSUES</description>
<link>http://bugs.linux-xtensa.org/</link>
<title>Mantis - ISSUES</title>
<image>
<title>Mantis - ISSUES</title>
<url>http://bugs.linux-xtensa.org/images/mantis_logo_button.gif</url>
<link>http://bugs.linux-xtensa.org/</link>
<description>Mantis - ISSUES</description>
</image>
<category>All Projects</category>
<ttl>10</ttl>
<sy:updatePeriod>hourly</sy:updatePeriod>
<sy:updateFrequency>1</sy:updateFrequency>
<sy:updateBase>2012-02-08T20:01:59-08:00</sy:updateBase>
<item>
<title>0000005: linux-xtensa-20080711.tar.gz is not available in web page</title>
<link>http://bugs.linux-xtensa.org/view.php?id=5</link>
<description>linux-xtensa-20080711.tar.gz is not available in web page</description>
<guid>http://bugs.linux-xtensa.org/view.php?id=5</guid>
<author>nimrodz &lt;nimrodz@example.com&gt;</author>
<comments>http://bugs.linux-xtensa.org/view.php?id=5#bugnotes</comments>
</item>
<item>
<title>0000004: crashme program causes kernel to crash</title>
<link>http://bugs.linux-xtensa.org/view.php?id=4</link>
<description>Running the crashme program (see enclosure) causes the kernel to crash.  The amount of time required to hit the crash depends on unknown factors.  As of this writing, this was only tested on the test_mmuhifi_b processor variant (used for testing).  In an OpenEmbedded environment, the following crashes in about 5 minutes:&lt;br /&gt;
&lt;br /&gt;
  ./crashme +2000 666 50 00:30:00 2&lt;br /&gt;
&lt;br /&gt;
In a buildroot environment, the following crashed after a much longer time (between 30 and 270 minutes):&lt;br /&gt;
&lt;br /&gt;
  ./crashme +2000 666 50 08:30:00 2&lt;br /&gt;
&lt;br /&gt;
In both cases the program was invoked from the root prompt, logged in via serial console.&lt;br /&gt;
&lt;br /&gt;
In the latter case the output on the console looked like this (the only relevant line being the last one):&lt;br /&gt;
&lt;br /&gt;
[...]&lt;br /&gt;
Illegal Instruction in 'crashme' (pid = 1416, pc = 0x0040c768)&lt;br /&gt;
Illegal Instruction in 'crashme' (pid = 1416, pc = 0x0040cf40)&lt;br /&gt;
Illegal Instruction in 'crashme' (pid = 1416, pc = 0x0040d718)&lt;br /&gt;
Illegal Instruction in 'crashme' (pid = 1416, pc = 0x0040def0)&lt;br /&gt;
Illegal Instruction in 'crashme' (pid = 1416, pc = 0x0040cb22)&lt;br /&gt;
Kernel panic - not syncing: Double exception sys_sigreturn&lt;br /&gt;
&lt;br /&gt;
Initial brief analysis shows that the double exception occurred in the window overflow handler, which happened because some page where the handler tried to store (which is normally in the stack) was not accessible.</description>
<guid>http://bugs.linux-xtensa.org/view.php?id=4</guid>
<author>marc &lt;marc@example.com&gt;</author>
<comments>http://bugs.linux-xtensa.org/view.php?id=4#bugnotes</comments>
</item>
</channel>
</rss>

