* blk_dev[93].request_fn == NULL bug is still there
@ 2000-11-30 21:54 Levi Khatskevitch
2000-12-01 7:01 ` David Woodhouse
2000-12-01 10:02 ` David Woodhouse
0 siblings, 2 replies; 5+ messages in thread
From: Levi Khatskevitch @ 2000-11-30 21:54 UTC (permalink / raw)
To: dwmw2; +Cc: linuxbios, mtd
> > I've just tested the new code, the doc2001 use count still gets
>increasingly
> > negative on each access to /dev/mtd0. Like:
>
>Are you sure you rebuilt mtdchar.o?
>
>--
>dwmw2
>
>
Ok, I was wrong I used the old vmlinux file :-). Module use count is correct
now.
Now I've just reproduced the blk_dev[93].request_fn == NULL bug in the
latest code. Here is how:
1) build the kernel with nftl*.o build in and doc*.o as modules.
2) insmod docecc.o; insmod doc2001.o; insmod docprobe.o
you'll see:
M-Systems DiskOnChip driver. (C) 1999 Machine Vision Holdings, Inc.
DiskOnChip Millennium found at address 0xFFFC8000
Flash chip found: Manufacture ID: 98, Chip ID: E6 (Toshiba TC58V64AFT/DC)
1 flash chips found. Total DiskOnChip size: 8 Mbytes
Cannot calculate an NFTL geometry to match size of 0x37c0.
Using C:1019 H:14 S:1 (== 0x37ba sects)
nftla:<3>ll_rw_block: Trying to read nonexistent block-device 5d:00 (0)
unable to read partition table
...
where "ll_rw_block: Trying to read nonexistent block-device 5d:00 (0)" is
caused by blk_dev[0x5d].request_fn == NULL
any subsequent access to /dev/nftla results in the same error.
at the same time nftl *is* registered to MAJOR# 93 according to:
[root@c1000s-dtd /]# cat /proc/devices
Character devices:
1 mem
2 pty
3 ttyp
4 ttyS
5 cua
10 misc
90 mtd
128 ptm
136 pts
Block devices:
1 ramdisk
2 fd
7 loop
93 nftl
^^^^^^^^^
Regards,
- Levi
_____________________________________________________________________________________
Get more from the Web. FREE MSN Explorer download : http://explorer.msn.com
To unsubscribe, send "unsubscribe mtd" to majordomo@infradead.org
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: blk_dev[93].request_fn == NULL bug is still there
2000-11-30 21:54 Levi Khatskevitch
@ 2000-12-01 7:01 ` David Woodhouse
2000-12-01 10:02 ` David Woodhouse
1 sibling, 0 replies; 5+ messages in thread
From: David Woodhouse @ 2000-12-01 7:01 UTC (permalink / raw)
To: Levi Khatskevitch; +Cc: linuxbios, mtd
On Thu, 30 Nov 2000, Levi Khatskevitch wrote:
> Ok, I was wrong I used the old vmlinux file :-). Module use count is correct
> now.
Hehe. I did _exactly_ the same thing :)
> Now I've just reproduced the blk_dev[93].request_fn == NULL bug in the
> latest code. Here is how:
I thought we'd found that this was because we were initialising the MTD
code before device_setup(). So I moved init_mtd() down a couple of lines
in init/main.c.
I'll try to reproduce this myself as soon as I get into the office.
--
dwmw2
To unsubscribe, send "unsubscribe mtd" to majordomo@infradead.org
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: blk_dev[93].request_fn == NULL bug is still there
2000-11-30 21:54 Levi Khatskevitch
2000-12-01 7:01 ` David Woodhouse
@ 2000-12-01 10:02 ` David Woodhouse
1 sibling, 0 replies; 5+ messages in thread
From: David Woodhouse @ 2000-12-01 10:02 UTC (permalink / raw)
To: Levi Khatskevitch; +Cc: linuxbios, mtd
lkhatskevitch@hotmail.com said:
> Now I've just reproduced the blk_dev[93].request_fn == NULL bug in
> the latest code. Here is how:
Works for me now. Check you've rebuilt it all with the latest patch.
Note init/main.c should now look like this:
/* Set up devices .. */
device_setup();
#ifdef CONFIG_MTD
init_mtd();
#endif
--
dwmw2
To unsubscribe, send "unsubscribe mtd" to majordomo@infradead.org
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: blk_dev[93].request_fn == NULL bug is still there
@ 2000-12-01 15:56 Levi Khatskevitch
2000-12-01 16:08 ` David Woodhouse
0 siblings, 1 reply; 5+ messages in thread
From: Levi Khatskevitch @ 2000-12-01 15:56 UTC (permalink / raw)
To: dwmw2; +Cc: linuxbios, mtd
On Fri, 1 Dec 2000, David Woodhouse wrote:
>I thought we'd found that this was because we were initialising the MTD
>code before device_setup(). So I moved init_mtd() down a couple of lines
>in init/main.c.
>
>I'll try to reproduce this myself as soon as I get into the office.
>
>--
>dwmw2
>
>
BTW Initializing MTD before device_setup was different (actially worse), it
caused blk_dev[xxx].plug_tq.routine == NULL, that contition is not checked
by run_task_queue() and was causing kernel to crash.
- Levi
_____________________________________________________________________________________
Get more from the Web. FREE MSN Explorer download : http://explorer.msn.com
To unsubscribe, send "unsubscribe mtd" to majordomo@infradead.org
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: blk_dev[93].request_fn == NULL bug is still there
2000-12-01 15:56 blk_dev[93].request_fn == NULL bug is still there Levi Khatskevitch
@ 2000-12-01 16:08 ` David Woodhouse
0 siblings, 0 replies; 5+ messages in thread
From: David Woodhouse @ 2000-12-01 16:08 UTC (permalink / raw)
To: Levi Khatskevitch; +Cc: linuxbios, mtd
lkhatskevitch@hotmail.com said:
> BTW Initializing MTD before device_setup was different (actially
> worse), it caused blk_dev[xxx].plug_tq.routine == NULL, that
> contition is not checked by run_task_queue() and was causing kernel
> to crash.
Ah. Sorry, I'd misread it and hadn't noticed the difference.
Now I'm confused. Did it not complain about failing to register the blkdev?
--
dwmw2
To unsubscribe, send "unsubscribe mtd" to majordomo@infradead.org
^ permalink raw reply [flat|nested] 5+ messages in thread
end of thread, other threads:[~2000-12-01 16:09 UTC | newest]
Thread overview: 5+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2000-12-01 15:56 blk_dev[93].request_fn == NULL bug is still there Levi Khatskevitch
2000-12-01 16:08 ` David Woodhouse
-- strict thread matches above, loose matches on Subject: below --
2000-11-30 21:54 Levi Khatskevitch
2000-12-01 7:01 ` David Woodhouse
2000-12-01 10:02 ` David Woodhouse
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox