Data Bus Error Epc
Contents |
data bus error From: Jon Dufresne
Imprecise Data Bus Error
to iomemory. I have written a test function that looks like this: void test_iomem(struct pci_dev *dev) { system returned to rom by bus error at pc 0x0 address 0x0 void __iomem *mem; unsigned long start; unsigned long size; start = pci_resource_start(dev, 0); size = pci_resource_len(dev, 0); printk("start=%08lx size=%08lx\n", start, size); mem = ioremap(start, size); while(1) { printk("memset %p\n",
System Returned To Rom By Address Error At Pc
mem); memset_io(mem, 0, 10000); } } This function is just being used to test the iomemory. If this works, it should just keep writing 0's to the iomemory forever (at least as I understand it). When I run insmod on this device driver I see the following output: start=20000000 size=04000000 memset c0580000 memset c0580000 memset c0580000 ... bus error linux ... ... And this goes on for quite some time. Eventually it will stop, moments later I will see a kernel panic with the following output: > memset c0580000 > memset c0580000 > memset c0580000 > Data bus error, epc == c027a64c, ra == 800aa27c > Oops[#1]: > Cpu 0 > $ 0 : 00000000 10008400 c0363050 00063050 > $ 4 : 00000037 82937800 8109d000 10008401 > $ 8 : 10008400 1000001f 80320000 80320000 > $12 : 80320000 00000001 83133bf8 8031c960 > $16 : 8311c600 00000080 00000001 00000037 > $20 : c02815e8 802e1ae4 c025a000 8008cde4 > $24 : 00000008 00000000 > $28 : 83132000 83133be8 c02815ac 800aa27c > Hi : 00000000 > Lo : 00000800 > epc : c027a64c Tainted: P > ra : 800aa27c Status: 10008403 KERNEL EXL IE > Cause : 1080801c > PrId : 00061200 > Modules linked in: tmman1700(P) mousedev usbhid usb_storage phStbFB(P) > phStbFBRead(P) phStbVideoRenderer(P) phStbVideoRenderer_Layer(P) > phStbStreamingSystem(P) phStbDraw(P) snd_usb_audio snd_usb_lib snd_rawmie > Process insmod (pid: 790, threadinfo=83132000, task=833e1278) > Stack : 801ecd20 801e
failure? Pages 1 You must login or register to post a reply RSS topic feed Posts: 5 1 Topic by alfredio 2008-01-27 16:38:25 alfredio Member Offline Registered: 2008-01-27 Posts: 6 Topic: Data bus error --> Hardware
Last Reload Reason Address Error At Pc
failure? Hi all,I'm very new about openwrt, but I feel I got acquainted soon.I was
Bus Error Cisco
gifted a Netgear WGT634U. Everything is working fine, except sometimes (seems randomly, but frequently, say once in 20 minutes) I get some"Data system was restarted by bus error at pc bus error" on the console, with attached cpu dump, kernel panic and reboot.The cluing thing is that, each time a data bus error occurs, the reported process is different: it may be "swapper", or the SSL https://www.linux-mips.org/archives/linux-mips/2008-02/msg00030.html web tunnel for webif^2, etc.I suspect it may be some hardware failure. Do you have any suggestion?Thanks (If I'm writing in the wrong place, I do apologize. Could you please point me to the right location?) 2 Reply by nbd 2008-01-27 16:40:04 nbd Developer Offline From: Berlin, Germany Registered: 2005-02-03 Posts: 1,000 Re: Data bus error --> Hardware failure? Probably not a hardware failure. Please try compiling the lastest 'trunk' version of https://forum.openwrt.org/viewtopic.php?id=14279 OpenWrt, maybe the driver improvements fix it. 3 Reply by alfredio 2008-01-27 16:44:18 alfredio Member Offline Registered: 2008-01-27 Posts: 6 Re: Data bus error --> Hardware failure? Thank you very much! Such a prompt reply!I'm going to build some trunk images now. I'll keep you updated.Two more clues about my experience:- data bus errors seem to be more frequent while wireless is on- I had "Data bus error" with the original firmware too, with wireless enabled.Thanks again! 4 Reply by alfredio 2008-01-27 19:39:52 alfredio Member Offline Registered: 2008-01-27 Posts: 6 Re: Data bus error --> Hardware failure? Small update:Before uploading a new image from trunk, I tried to change the power adaptor, from a 12V output to a 7.5V output.It seems that the brick is warming a bit less now, while remaining functional. However, no enhancement in stability has been reached.I'm going to flash an image from trunk, I'll let you (and me, since I'm starting talking to myself) know.Cheers 5 Reply by alfredio 2008-01-28 00:23:32 alfredio Member Offline Registered: 2008-01-27 Posts: 6 Re: Data bus error --> Hardware failure? Update:I switched to the trunk revision () of kamikaze, with a 7.5V adapter.Unfortunately, nothing is going better. Stability isn't improved at all. I cannot get uptimes longer than 10/15 minutes.I usually get "data bus error"
Ticket Navigation Ticket #656 (new defect) Opened 10 years ago Last modified 10 years ago mipsel kernel oops on "ifconfig up" http://madwifi-project.org/ticket/656 Reported by: georg@boerde.de Assigned to: Priority: major Milestone: Component: madwifi: HAL Version: Keywords: hal mips Cc: Patch is attached: 0 Pending: Description When bringing up an interface on a MIPSel machine (OpenWrt / Netgear WGT634U), the kernel Oopses in the following reproducible way: root@OpenWrt:/# wlanconfig ath0 destroy root@OpenWrt:/# wlanconfig ath0 create wlandev wifi0 wlanmode sta ath0 root@OpenWrt:/# ifconfig bus error ath0 up Data bus error, epc == c005f2c0, ra == c007ac48 Oops[#1]: Cpu 0 $ 0 : 00000000 10009c00 c00e9930 00000001 $ 4 : 81398000 00009930 81398308 813982c8 $ 8 : 000000c0 80220000 00000008 00000000 $12 : 00401043 00705aac 00000001 00000010 $16 : 8139a8a0 81398000 81398000 81398000 $20 : 00000000 81398308 80260000 00008914 $24 : 00000000 c00b4f08 $28 error at pc : 81cc0000 81cc1cb8 80331174 c007ac48 Hi : 000003c5 Lo : 1eb3f600 epc : c005f2c0 Tainted: P ra : c007ac48 Status: 10009c03 KERNEL EXL IE Cause : 0000001c PrId : 00029007 Modules linked in: ath_pci ath_rate_sample ath_hal wlan_scan_sta wlan_wep wlan Process ifconfig (pid: 390, threadinfo=81cc0000, task=81e8c000) Stack : 00401043 00705aac 00000001 00000010 c005f2b8 80330260 81398000 c00766f0 00000000 80330f1c 80260000 00008914 00000000 c00b4f08 00000000 00000000 00000000 00000001 00000000 02000000 10009c03 00000369 00000000 80330260 81398000 80330000 00000000 80330f1c 80260000 00008914 7fcdac68 c00fe4c0 00008000 00000001 0000003c 00000000 81cc1d50 10009c00 80001400 00002000 ... Call Trace: [