Re: kernel panic

Alan Stern <[email protected]>
Newsgroups gmane.linux.usb.devel
Message-ID <[email protected]>
On Thu, 11 Oct 2007, hong zhang wrote:

> List,
> 
> I got kernel panic when I format USB scsi hard disk.
> When I run "mkfs.ext3 -j /dev/sda1" on kernel 2.6.19.2
> but it is no problem on kernel 2.6.10. This also
> occurs sometimes  when boot up. Therefore, I believe
> it is not related to mkfs.ext3 operation. PC conects
> to imx31 based board by means of ethernet/usb cable.
> And board mounts rootfs over nfs.
> 
> My board has two usb hosts, host1 connects PC and
> host2 conects to hard disk.
> 
> Any help will be appreciated!!!
> 
> See following Oops:
> 
> Starting the dropbear ssh server:
> Unable to handle kernel NULL pointer dereference at
> virtual address 00000000
> pgd = c3bb0000
> [00000000] *pgd=83922031, *pte=00000000,
> *ppte=00000000
> Internal error: Oops: 817 [#1]
> Modules linked in:
> CPU: 0
> PC is at start_unlink_async+0x40/0x14c
> LR is at ehci_work+0x13c/0x6b4

You will need to make a disassembly listing of start_unlink_async (use
objdump -d ehci-hcd.o).  Then read through the object code, comparing
it with the source code, to find out what C instruction corresponds to
offset 0x40.  Also figure out which register contains a NULL pointer
and what C variable it corresponds to.

Then when you know what's wrong in terms of the source code, tell us so 
we can try to fix it.

Alan Stern


-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
[email protected]
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.