On Wed, Oct 18, 2000 at 07:59:23AM +0200, Arkadiusz Miskiewicz wrote / Dnia Wed, Oct 18, 2000 at 07:59:23AM +0200, Arkadiusz Miskiewicz napisał(a):
> Oct 18 09:51:09 dark kernel: invalid operand: 0000
> Oct 18 09:51:09 dark kernel: CPU: 0
> Oct 18 09:51:09 dark kernel: EIP: 0010:[ne2k-pci:__insmod_ne2k-pci_O/lib/modules/2.4.0-test9/kernel/drivers/+-789199/96]
...
that was IMHO caused by some corruption caused on fat32 partition. Now for example
I got errors such as:
Oct 21 01:02:48 arm kernel: attempt to access beyond end of device
Oct 21 01:02:48 arm kernel: 03:01: rw=0, want=11047331, limit=9912136
Oct 21 01:02:48 arm kernel: Directory sread (sector 0x1512345) failed
Oct 21 01:02:48 arm kernel: attempt to access beyond end of device
Oct 21 01:02:48 arm kernel: 03:01: rw=0, want=11047331, limit=9912136
Oct 21 01:02:48 arm kernel: Directory sread (sector 0x1512345) failed
Oct 21 01:02:48 arm kernel: attempt to access beyond end of device
Oct 21 01:02:48 arm kernel: 03:01: rw=0, want=11047331, limit=9912136
I think that is problem with linux fat32 support because usually
when I write something on fat32 (under Linux) using long file names
then in Norton Disc Doctor (v2001) almost always complains to long
names (truncate these long names).... while under windoze everything seems
be ok.
Any ideas ? (kernel 2.4.0-test9)
btw. who is linux fat32 fs maintainer ?
-- Arkadiusz Mi¶kiewicz http://www.misiek.eu.org/ipv6/ PLD GNU/Linux [IPv6 enabled] http://www.pld.org.pl/ - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Mon Oct 23 2000 - 21:00:17 EST