Re: BUG in dma-mapping.h:218 // MESH SCSI driver not working
From: Stef Simoens <hidden>
Date: 2009-08-02 08:53:10
Hey Benjamin, Benjamin Herrenschmidt schreef:
On Thu, 2009-07-30 at 01:42 +0200, Stef Simoens wrote:quoted
What would be the best approach? - if the kernel boots, it's obviously 'good' - but what if the kernel hits the 'BUG', should I apply your patch then? If it doesn't work with your patch, would it be 'bad' then?
A few reboots later...
As you said, during my bisecting, at a certain moment I needed your
patch (I booted, got a problem, patched the tree with your patch,
rebooted, it worked).
Then, git says:
f078727b250c2653fc9a564f15547c17ebac3f99 is first bad commit
commit f078727b250c2653fc9a564f15547c17ebac3f99
Author: FUJITA Tomonori [off-list ref]
Date: Sun Dec 14 01:23:45 2008 +0900
[SCSI] remove scsi_req_map_sg
No one uses scsi_execute_async with data transfer now. We can remove
scsi_req_map_sg.
Only scsi_eh_lock_door uses scsi_execute_async. scsi_eh_lock_door
doesn't handle sense and the callback. So we can remove
scsi_io_context too.
Signed-off-by: FUJITA Tomonori [off-list ref]
Signed-off-by: James Bottomley [off-list ref]
:040000 040000 c4621d866c1ee5fd8d30e44f702a4966b8ebdc44
3ffca800399e52ef12f1001721c0c7ff431efafd M drivers
:040000 040000 805c02c4ad3c63c45dffa18f413e92bfca99caf6
6fb58bb5fb19c4198fa7d626d6241086655c6307 M include
At this moment, the reason for the crash is different then in v2.6.30
I noted the following (I hope to have written the most important stuff).
driver 'sd' needs update
mesh: lost arbitration
sd 0:0:0:0 sda read CAPACITY failed
sd ...
sd 0:0:0:0 sdb read CAPACITY failed
sd ...
mice
sd ...
mice: PS/2 ...
TCP cubic ...
Initializing XFRM ...
NET ... protcol 17
XFS ...
VFS : unable to mount root FS
If you want more input ... please let me know.
--
Kr,
Stef Simoens