Re: 2.4.1-ac5 - The loopback hang saga continues (not me ?)

2001-02-07 Thread Pascal Brisset

FYI following hints from the linux-crypto mailing-list archives, I am
using the following configuration :

linux-2.4.0
patch-int-2.4.0.3
http://www.kernel.org/pub/linux/kernel/people/axboe/patches/2.4.0/loop-1.gz
http://www.kernel.org/pub/linux/kernel/people/axboe/patches/2.4.0/loop-bdev-inc-1.gz
util-linux-2.10o
Documentation/crypto/util-linux-2.10o.patch

I setup an encrypted 2097152000 byte loopback partition and moved
800MB of data there, including a 90MB file.

My only problems are:
- rc.d/init.d/S01reboot sometimes fails to unmount partitions with
  loop files on them (this already happened with 2.2.17).
- losetup after losetup -d sometimes fails.

-- Pascal

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.tux.org/lkml/



[oops] Yenta on 2.4.0-test11 laptop (worked with test9)

2000-11-25 Thread Pascal Brisset

Is anyone using Yenta on a sony vaio laptop (PII-400) with 2.4.0-test11 ?

I can't even follow my own printk()s through the call to exca_writew()
in the trace below, so the system might be getting corrupted earlier
(possibly not in the cardbus code).

The same .config works on this machine with test9.


Unable to handle kernel NULL pointer dereference at virtual address 0008
c4828050
*pde = 
Oops: 0002
CPU:0
EIP:0010:[]
Using defaults from ksymoops -t elf32-i386 -a i386
EFLAGS: 00010246
eax: 0008   ebx:    ecx: 0040   edx: 003c
esi:    edi: c482a3a0   ebp: c113bf24   esp: c113bee4
ds: 0018   es: 0018   ss: 0018
Process eventd (pid: 3, stackpage=c113b000)
Stack: c48288b3 c482a3a0 0008   c113bf24 c482a3a0 c482a300 
   c482a340 b22f c482911b c482a3a0 c113bf24 c482a3a0  c3ae5000 
    0001   0fff  c48292ad c482a3a0 
Call Trace: [] [] [] [] [] 
[] [] 
   [] [] [] [] [] [] 
[] [] 
   [] [] [] [] [] [] 
[] [] 
   [] [] [] [] [] [] 
[] 
Code: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 82 c4 8b 5c 

>>EIP; c4828050 <[yenta_socket]exca_writew+0/4c>   <=
Trace; c48288b3 <[yenta_socket]yenta_set_io_map+8f/148>
Trace; c482a3a0 <[yenta_socket]__kstrtab_yenta_operations+0/0>
Trace; c482a3a0 <[yenta_socket]__kstrtab_yenta_operations+0/0>
Trace; c482a300 <[yenta_socket]pci_socket_operations+0/30>
Trace; c482a340 <[yenta_socket]cardbus_table+10/38>
Trace; c482911b <[yenta_socket]yenta_clear_maps+6b/9c>
Trace; c482a3a0 <[yenta_socket]__kstrtab_yenta_operations+0/0>
Trace; c482a3a0 <[yenta_socket]__kstrtab_yenta_operations+0/0>
Trace; c48292ad <[yenta_socket]yenta_init+11/18>
Trace; c482a3a0 <[yenta_socket]__kstrtab_yenta_operations+0/0>
Trace; c482a3a0 <[yenta_socket]__kstrtab_yenta_operations+0/0>
Trace; c482a3a0 <[yenta_socket]__kstrtab_yenta_operations+0/0>
Trace; c4829727 <[yenta_socket]ricoh_init+b/68>
Trace; c482a3a0 <[yenta_socket]__kstrtab_yenta_operations+0/0>
Trace; c482989a <[yenta_socket]pci_init_socket+2a/38>
Trace; c482a3a0 <[yenta_socket]__kstrtab_yenta_operations+0/0>
Trace; c481fef8 <[pcmcia_core]init_socket+28/2c>
Trace; c481ffc0 <[pcmcia_core]pcmcia_register_socket+c4/128>
Trace; c482a3a0 <[yenta_socket]__kstrtab_yenta_operations+0/0>
Trace; c482a3a0 <[yenta_socket]__kstrtab_yenta_operations+0/0>
Trace; c4829bc6 <[yenta_socket]cardbus_register+22/2c>
Trace; c482a300 <[yenta_socket]pci_socket_operations+0/30>
Trace; c482a3a0 <[yenta_socket]__kstrtab_yenta_operations+0/0>
Trace; c482909b <[yenta_socket]yenta_open_bh+93/a8>
Trace; c482a3a0 <[yenta_socket]__kstrtab_yenta_operations+0/0>
Trace; c4829e40 <[yenta_socket].rodata.start+180/310>
Trace; c01168cd 
Trace; c482a3a0 <[yenta_socket]__kstrtab_yenta_operations+0/0>
Trace; c0105000 
Trace; c01089ff 
Code;  c4828050 <[yenta_socket]exca_writew+0/4c>   <=
 <_EIP>:   <=
Code;  c4828060 <[yenta_socket]exca_writew+10/4c>
  10:   82(bad)  
Code;  c4828061 <[yenta_socket]exca_writew+11/4c>
  11:   c4 8b 5c 00 00 00 les0x5c(%ebx),%ecx


1 warning issued.  Results may not be reliable.



Linux version 2.4.0-test11 (root@pcg) (gcc version egcs-2.91.66 19990314/Linux 
(egcs-1.1.2 release)) #1 Sat Nov 25 11:34:01 MET 2000
BIOS-provided physical RAM map:
 BIOS-e820: 0009f800 @  (usable)
 BIOS-e820: 0800 @ 0009f800 (reserved)
 BIOS-e820: 00017800 @ 000e8800 (reserved)
 BIOS-e820: 03ef @ 0010 (usable)
 BIOS-e820: f800 @ 03ff (ACPI data)
 BIOS-e820: 0800 @ 03fff800 (ACPI NVS)
 BIOS-e820: 0008 @ fff8 (reserved)
On node 0 totalpages: 16368
zone(0): 4096 pages.
zone(1): 12272 pages.
zone(2): 0 pages.
Kernel command line: BOOT_IMAGE=linux-2.4.0 ro root=302 1 ro
Initializing CPU#0
Detected 397.002 MHz processor.
Console: colour VGA+ 80x25
Calibrating delay loop... 792.99 BogoMIPS
Memory: 62696k/65472k available (882k kernel code, 2388k reserved, 53k data, 172k 
init, 0k highmem)
Dentry-cache hash table entries: 8192 (order: 4, 65536 bytes)
Buffer-cache hash table entries: 1024 (order: 0, 4096 bytes)
Page-cache hash table entries: 16384 (order: 4, 65536 bytes)
Inode-cache hash table entries: 4096 (order: 3, 32768 bytes)
CPU: Before vendor init, caps: 0183f9ff  , vendor = 0
CPU: L2 cache: 256K
Intel machine check architecture supported.
Intel machine check reporting enabled on CPU#0.
CPU: After vendor init, caps: 0183f9ff   
CPU: After generic, caps: 0183f9ff   
CPU: Common caps: 0183f9ff   
CPU: Intel Mobile Pentium II stepping 0d
Checking 'hlt' instruction... OK.
POSIX conformance testing by UNIFIX
mtrr: v1.37 (20001109) Richard Gooch ([EMAIL PROTECTED])
mtrr: detected mtrr type: Intel
PCI: PCI BIOS revision 2.10 entry at 0xfd99e, last bus=1
PCI: