bug in 2.6.0test2

bug in 2.6.0test2

[Nico Schottelius]

[-- Attachment #1.1: Type: text/plain, Size: 423 bytes --]

Hello again!

When trying to boot from a cryptoloop we get the attached error.
Details:
   modules loop,cryptoloop,aes (in this order) are loaded with insmod
   (from initrd)
   then mounting proc

Any suggestions / solutions ?

Nico

ps: please cc me and scholz AT wdt.de

-- 
echo God bless America | sed 's/.*\(A.*$\)/Why \1?/'
pgp: new id: 0x8D0E27A4 | ftp.schottelius.org/pub/familiy/nico/pgp-key.new

[-- Attachment #1.2: BASTIAN-LOG --]
[-- Type: text/plain, Size: 8300 bytes --]

Linux version 2.6.0-test2 (root@debian.dummy) (gcc-Version 3.3.1 20030722 (Debian prerelease)) #3 Mon Jul 28 13:50:46 CEST 2003

Video mode to be used for restore is 317

BIOS-provided physical RAM map:

 BIOS-e820: 0000000000000000 - 000000000009fc00 (usable)

 BIOS-e820: 000000000009fc00 - 00000000000a0000 (reserved)

 BIOS-e820: 0000000000100000 - 000000000ffdb000 (usable)

 BIOS-e820: 000000000ffdb000 - 0000000010000000 (reserved)

 BIOS-e820: 00000000100a0000 - 0000000010100000 (reserved)

 BIOS-e820: 00000000ffe00000 - 0000000100000000 (reserved)

255MB LOWMEM available.

On node 0 totalpages: 65499

  DMA zone: 4096 pages, LIFO batch:1

  Normal zone: 61403 pages, LIFO batch:14

  HighMem zone: 0 pages, LIFO batch:1

ACPI: RSDP (v000 DELL                       ) @ 0x000f4040

ACPI: RSDT (v001 DELL    CPi R   10194.01308) @ 0x0fff0000

ACPI: FADT (v001 DELL    CPi R   10194.01308) @ 0x0fff0400

ACPI: DSDT (v001 INT430 SYSFexxx 00000.04097) @ 0x00000000

ACPI: BIOS passes blacklist

Building zonelist for node : 0

Kernel command line: BOOT_IMAGE=2.6.0-test2 ro root=700 console=ttyS0,9600 console=tty0

Initializing CPU#0

PID hash table entries: 1024 (order 10: 8192 bytes)

Detected 498.550 MHz processor.

Console: colour dummy device 80x25

Calibrating delay loop... 985.08 BogoMIPS

Memory: 254084k/261996k available (2409k kernel code, 7212k reserved, 726k data, 136k init, 0k highmem)

Dentry cache hash table entries: 32768 (order: 5, 131072 bytes)

Inode-cache hash table entries: 16384 (order: 4, 65536 bytes)

Mount-cache hash table entries: 512 (order: 0, 4096 bytes)

-> /dev

-> /dev/console

-> /root

CPU: L1 I cache: 16K, L1 D cache: 16K

CPU: L2 cache: 256K

Intel machine check architecture supported.

Intel machine check reporting enabled on CPU#0.

CPU: Intel Pentium III (Coppermine) stepping 03

Enabling fast FPU save and restore... done.

Enabling unmasked SIMD FPU exception support... done.

Checking 'hlt' instruction... OK.

POSIX conformance testing by UNIFIX

Initializing RT netlink socket

PCI: PCI BIOS revision 2.10 entry at 0xfc0ae, last bus=1

PCI: Using configuration type 1

mtrr: v2.0 (20020519)

BIO: pool of 256 setup, 15Kb (60 bytes/bio)

biovec pool[0]:   1 bvecs: 256 entries (12 bytes)

biovec pool[1]:   4 bvecs: 256 entries (48 bytes)

biovec pool[2]:  16 bvecs: 256 entries (192 bytes)

biovec pool[3]:  64 bvecs: 256 entries (768 bytes)

biovec pool[4]: 128 bvecs: 256 entries (1536 bytes)

biovec pool[5]: 256 bvecs: 256 entries (3072 bytes)

ACPI: Subsystem revision 20030714

ACPI: Interpreter enabled

ACPI: Using PIC for interrupt routing

ACPI: PCI Root Bridge [PCI0] (00:00)

PCI: Probing PCI hardware (bus 00)

ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 5 6 7 9 10 *11 12 14 15)

ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 *5 6 7 9 10 11 12 14 15)

ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 5 6 7 9 10 11 12 14 15, disabled)

ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 5 6 7 9 10 *11 12 14 15)

ACPI: Power Resource [PADA] (on)

Linux Plug and Play Support v0.96 (c) Adam Belay

ACPI: PCI Interrupt Link [LNKC] enabled at IRQ 10

PCI: Using ACPI for IRQ routing

PCI: if you experience problems, try using option 'pci=noacpi' or even 'acpi=off'

vesafb: framebuffer at 0xfd000000, mapped to 0xd0807000, size 8128k

vesafb: mode is 1024x768x16, linelength=2048, pages=4

vesafb: protected mode interface info at c000:5044

vesafb: scrolling: redraw

vesafb: directcolor: size=0:5:6:5, shift=0:11:5:0

fb0: VESA VGA frame buffer device

Console: switching to colour frame buffer device 128x48

pty: 256 Unix98 ptys configured

Enabling SEP on CPU 0

udf: registering filesystem

SGI XFS for Linux 2.6.0-test2 with ACLs, no debug enabled

Initializing Cryptographic API

Limiting direct PCI/PCI transfers.

Serial: 8250/16550 driver $Revision: 1.90 $ IRQ sharing disabled

ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A

ttyS2 at I/O 0x3e8 (irq = 4) is a 16550A

RAMDISK driver initialized: 16 RAM disks of 4096K size 1024 blocksize

Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2

ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx

PIIX4: IDE controller at PCI slot 0000:00:07.1

PIIX4: chipset revision 1

PIIX4: not 100% native mode: will probe irqs later

    ide0: BM-DMA at 0x0860-0x0867, BIOS settings: hda:DMA, hdb:pio

    ide1: BM-DMA at 0x0868-0x086f, BIOS settings: hdc:pio, hdd:pio

hda: FUJITSU MHR2030AT, ATA DISK drive

Using anticipatory scheduling elevator

ide0 at 0x1f0-0x1f7,0x3f6 on irq 14

ide2: I/O resource 0x3EE-0x3EE not free.

ide2: ports already in use, skipping probe

hda: max request size: 1024KiB

hda: host protected area => 1

hda: 58605120 sectors (30006 MB) w/2048KiB Cache, CHS=3648/255/63, UDMA(33)

 hda: hda1 hda2 hda3 hda4

Console: switching to colour frame buffer device 128x48

mice: PS/2 mouse device common for all mice

input: PS/2 Generic Mouse on isa0060/serio1

serio: i8042 AUX port at 0x60,0x64 irq 12

input: AT Set 2 keyboard on isa0060/serio0

serio: i8042 KBD port at 0x60,0x64 irq 1

Advanced Linux Sound Architecture Driver Version 0.9.4 (Mon Jun 09 12:01:18 2003 UTC).

es1968: clocking to 48000

ALSA device list:

  #0: ESS ES1978 (Maestro 2E) at 0xd800, irq 5

NET4: Linux TCP/IP 1.0 for NET4.0

IP: routing cache hash table of 2048 buckets, 16Kbytes

TCP: Hash tables configured (established 16384 bind 32768)

NET4: Unix domain sockets 1.0/SMP for Linux NET4.0.

IPv6 v0.8 for NET4.0

IPv6 over IPv4 tunneling driver

BIOS EDD facility v0.09 2003-Jan-22, 1 devices found

RAMDISK: Compressed image found at block 0

Freeing initrd memory: 1158k freed

EXT2-fs warning: mounting unchecked fs, running e2fsck is recommended

VFS: Mounted root (ext2 filesystem).

loop: loaded (max 8 devices)

bio too big device loop0 (2 > 0)

EXT2-fs: unable to read superblock

bio too big device loop0 (4 > 0)

bio too big device loop0 (4 > 0)

bio too big device loop0 (4 > 0)

UDF-fs: No partition found (1)

------------[ cut here ]------------

kernel BUG at drivers/block/ll_rw_blk.c:2120!

invalid operand: 0000 [#1]

CPU:    0

EIP:    0060:[<c0263797>]    Not tainted

EFLAGS: 00010246

EIP is at submit_bio+0x67/0x80

eax: 00000000   ebx: 00000000   ecx: 00000000   edx: cffb5aa0

esi: 00000000   edi: 00002a05   ebp: 00000200   esp: cff91c20

ds: 007b   es: 007b   ss: 0068

Process swapper (pid: 1, threadinfo=cff90000 task=c129b840)

Stack: 00002a05 cffb5aa0 c0203db4 00000000 cffb5aa0 00001000 00000000 00000000 

       00000000 00000000 00000000 000000d0 00000000 00000000 cf91fd80 c126d248 

       c0202cb8 cf928d6c 00000000 000000d0 c0441474 00000000 cff90000 00000000 

Call Trace:

 [<c0203db4>] pagebuf_iorequest+0x3d4/0x400

 [<c0202cb8>] _pagebuf_lookup_pages+0x398/0x3e0

 [<c0203858>] pagebuf_iostart+0x88/0xc0

 [<c02030b2>] pagebuf_get+0x142/0x150

 [<c01ef2a3>] xfs_readsb+0x53/0x240

 [<c01f834c>] xfs_mount+0x29c/0x600

 [<c020dd13>] vfs_mount+0x43/0x50

 [<c020daff>] linvfs_fill_super+0xaf/0x240

 [<c0219d07>] snprintf+0x27/0x30

 [<c0180c7f>] disk_name+0xaf/0xc0

 [<c0157c25>] sb_set_blocksize+0x25/0x60

 [<c0157604>] get_sb_bdev+0x124/0x160

 [<c020dcbf>] linvfs_get_sb+0x2f/0x40

 [<c020da50>] linvfs_fill_super+0x0/0x240

 [<c015786f>] do_kern_mount+0x5f/0xe0

 [<c016cfc8>] do_add_mount+0x78/0x160

 [<c016d2d4>] do_mount+0x134/0x180

 [<c021aa00>] __copy_from_user_ll+0x70/0x80

 [<c016d190>] copy_mount_options+0xe0/0xf0

 [<c016d69f>] sys_mount+0xbf/0x140

 [<c0412bef>] do_mount_root+0x2f/0xa0

 [<c0412cb4>] mount_block_root+0x54/0x130

 [<c010ae4b>] syscall_call+0x7/0xb

 [<c0412f27>] mount_root+0x47/0x50

 [<c0413ca5>] handle_initrd+0x1f5/0x300

 [<c0413e33>] initrd_load+0x83/0x90

 [<c0412f62>] prepare_namespace+0x32/0x110

 [<c01050a4>] init+0x34/0x1c0

 [<c0105070>] init+0x0/0x1c0

 [<c0108d75>] kernel_thread_helper+0x5/0x10



Code: 0f 0b 48 08 78 96 37 c0 eb aa eb 0d 90 90 90 90 90 90 90 90 

 <0>Kernel panic: Attempted to kill init!


[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

Re: bug in 2.6.0test2

[Steve Lord]

On Mon, 2003-07-28 at 06:59, Nico Schottelius wrote:
> Hello again!
> 
> When trying to boot from a cryptoloop we get the attached error.
> Details:
>    modules loop,cryptoloop,aes (in this order) are loaded with insmod
>    (from initrd)
>    then mounting proc
> 
> Any suggestions / solutions ?
> 
> Nico
> 
> ps: please cc me and scholz AT wdt.de

Something else went wrong before you crashed:

bio too big device loop0 (2 > 0)

This means you cannot use any bio larger than zero to this device,
which is probably why ext2 said this, since it caught the error when
building the bio.

EXT2-fs: unable to read superblock

XFS didn't catch the error building the bio and submitted it, at
which point the I/O tripped the BUG. I can fix this part, but
the original problem is something I know nothing about.

Steve

-- 

Steve Lord                                      voice: +1-651-683-3511
Principal Engineer, Filesystem Software         email: lord@sgi.com

Re: bug in 2.6.0test2

[Nico Schottelius]

Steve Lord [Mon, Jul 28, 2003 at 03:47:30PM -0500]:
> On Mon, 2003-07-28 at 06:59, Nico Schottelius wrote:
> > Hello again!
> > 
> > When trying to boot from a cryptoloop we get the attached error.
> > Details:
> >    modules loop,cryptoloop,aes (in this order) are loaded with insmod
> >    (from initrd)
> >    then mounting proc
> > 
> > Any suggestions / solutions ?
> > 
> > Nico
> > 
> > ps: please cc me and scholz AT wdt.de
> 
> Something else went wrong before you crashed:
> 
> bio too big device loop0 (2 > 0)
> 
> This means you cannot use any bio larger than zero to this device,

assume i didn't understand very much you told me..what is a bio?
how do I use it? and why is it too big here?

> which is probably why ext2 said this, since it caught the error when
> building the bio.

ext2? I am wondering..afai understood that, the root wasn't even
decrypted, how can the kernel try to ext2-mount it?

> EXT2-fs: unable to read superblock
> 
> XFS didn't catch the error building the bio and submitted it, at
> which point the I/O tripped the BUG. I can fix this part, but
> the original problem is something I know nothing about.

..or better why does it start mounting/before decrypt?


Nico

-- 
echo God bless America | sed 's/.*\(A.*$\)/Why \1?/'
pgp: new id: 0x8D0E27A4 | ftp.schottelius.org/pub/familiy/nico/pgp-key.new

Re: bug in 2.6.0test2

[Steve Lord]

On Mon, 2003-07-28 at 17:26, Nico Schottelius wrote:
> Steve Lord [Mon, Jul 28, 2003 at 03:47:30PM -0500]:
> > 
> > Something else went wrong before you crashed:
> > 
> > bio too big device loop0 (2 > 0)
> > 
> > This means you cannot use any bio larger than zero to this device,
> 
> assume i didn't understand very much you told me..what is a bio?
> how do I use it? and why is it too big here?

It looks like the loop device may not be correctly initialized yet,
no I/O is possible to it yet.

> 
> > which is probably why ext2 said this, since it caught the error when
> > building the bio.
> 
> ext2? I am wondering..afai understood that, the root wasn't even
> decrypted, how can the kernel try to ext2-mount it?
> 
> > EXT2-fs: unable to read superblock
> > 
> > XFS didn't catch the error building the bio and submitted it, at
> > which point the I/O tripped the BUG. I can fix this part, but
> > the original problem is something I know nothing about.
> 
> ..or better why does it start mounting/before decrypt?
> 

I have never used a crypto loop device, so I cannot what is really
going on. Some initialization step may be missing in the loop device
which means it is not usable, the mount it happening because the
kernel was told to mount it. If you are not specifying a filesystem
type, then possibly what is happening is it is attempting to open
the device as different filesystems, these all fail, until xfs
which does not detect the underlying error on the loop device,
and issues the IO which causes the BUG.

So, we caused the crash, but you were on your way to one anyway,
eventually it would have failed to find a root device and given
up that way.

Steve

2.6.0-test2 usb stack crashed was: Re: bug in 2.6.0test2

[Wiktor Wodecki]

[-- Attachment #1: Type: text/plain, Size: 10834 bytes --]

Hello,

On Tue, Jul 29, 2003 at 06:43:17AM -0500, Steve Lord wrote:
> On Mon, 2003-07-28 at 17:26, Nico Schottelius wrote:
> > Steve Lord [Mon, Jul 28, 2003 at 03:47:30PM -0500]:
> > > 
> > > Something else went wrong before you crashed:
> > > 
> > > bio too big device loop0 (2 > 0)
> > > 
> > > This means you cannot use any bio larger than zero to this device,
> > 
> > assume i didn't understand very much you told me..what is a bio?
> > how do I use it? and why is it too big here?
> 
> It looks like the loop device may not be correctly initialized yet,
> no I/O is possible to it yet.
> 
> > 
> > > which is probably why ext2 said this, since it caught the error when
> > > building the bio.
> > 
> > ext2? I am wondering..afai understood that, the root wasn't even
> > decrypted, how can the kernel try to ext2-mount it?
> > 
> > > EXT2-fs: unable to read superblock
> > > 
> > > XFS didn't catch the error building the bio and submitted it, at
> > > which point the I/O tripped the BUG. I can fix this part, but
> > > the original problem is something I know nothing about.
> > 
> > ..or better why does it start mounting/before decrypt?
> > 
> 
> I have never used a crypto loop device, so I cannot what is really
> going on. Some initialization step may be missing in the loop device
> which means it is not usable, the mount it happening because the
> kernel was told to mount it. If you are not specifying a filesystem
> type, then possibly what is happening is it is attempting to open
> the device as different filesystems, these all fail, until xfs
> which does not detect the underlying error on the loop device,
> and issues the IO which causes the BUG.

I just experienced a similar bug.
I disconnected by accident the usb hob from power and the write crashed:

Jul 29 17:00:38 kakerlak kernel: SCSI error : <1 0 0 0> return code =
0x70000
Jul 29 17:00:38 kakerlak kernel: end_request: I/O error, dev sda, sector
11218
Jul 29 17:00:38 kakerlak kernel: Buffer I/O error on device sda1,
logical block 11155
Jul 29 17:00:38 kakerlak kernel: error on device sda1, logical block
52829
Jul 29 17:00:38 kakerlak kernel: Buffer I/O error on device sda1,
logical block 52830
Jul 29 17:00:38 kakerlak kernel: Buffer I/O error on device sda1,
logical block 52831
Jul 29 17:00:38 kakerlak kernel: Buffer I/O error on device sda1,
logical block 52832
Jul 29 17:00:38 kakerlak kernel: Buffer I/O error on device sda1,
logical block 52833
...
Jul 29 17:00:39 kakerlak kernel: Buffer I/O error on device sda1,
logical block 52882
Jul 29 17:00:39 kakerlak kernel: scsi1 (0:0): rejecting I/O to offline
device
Jul 29 17:00:39 kakerlak kernel: Buffer I/O error on device sda1,
logical block 52883
...
ul 29 17:00:40 kakerlak kernel: FAT: Filesystem panic (dev sda1)
Jul 29 17:00:40 kakerlak kernel:     unable to read i-node block (i_pos
7987)
Jul 29 17:00:40 kakerlak kernel:     File system has been set read-only
Jul 29 17:00:40 kakerlak kernel: usb 1-2.3: USB disconnect, address 3
Jul 29 17:00:40 kakerlak kernel: usb 1-2.4: USB disconnect, address 4
Jul 29 17:00:40 kakerlak kernel: bio too big device sda1 (1 > 0)
Jul 29 17:00:40 kakerlak kernel: FAT: bread(block 52) in fat_access
failed
Jul 29 17:00:40 kakerlak kernel: bio too big device sda1 (1 > 0)

nothing wrong here, was my fault
After powering on the usb hub again:

Jul 29 17:00:41 kakerlak kernel: hub 1-0:0: debounce: port 2: delay
100ms stable 4 status 0x101
Jul 29 17:00:41 kakerlak kernel: hub 1-0:0: new USB device on port 2,
assigned address 6
Jul 29 17:00:41 kakerlak kernel: hub 1-2:0: USB hub found
Jul 29 17:00:41 kakerlak kernel: hub 1-2:0: 4 ports detected
Jul 29 17:00:41 kakerlak kernel: hub 1-2:0: debounce: port 1: delay
100ms stable 4 status 0x101
Jul 29 17:00:41 kakerlak kernel: hub 1-2:0: new USB device on port 1,
assigned address 7
Jul 29 17:00:41 kakerlak kernel: scsi2 : SCSI emulation for USB Mass
Storage devices
Jul 29 17:00:41 kakerlak kernel:   Vendor: 3SYSTEM   Model: USB FLASH
DISK    Rev: 1.00
Jul 29 17:00:41 kakerlak kernel:   Type:   Direct-Access
ANSI SCSI revision: 02
Jul 29 17:00:41 kakerlak kernel: SCSI device sda: 256000 512-byte hdwr
sectors (131 MB)
Jul 29 17:00:41 kakerlak kernel: sda: Write Protect is off
Jul 29 17:00:41 kakerlak kernel: sda: Mode Sense: 00 0e 00 00
Jul 29 17:00:41 kakerlak kernel: sda: cache data unavailable
Jul 29 17:00:41 kakerlak kernel: sda: assuming drive cache: write
through
Jul 29 17:00:41 kakerlak kernel: Unable to handle kernel NULL pointer
dereference at virtual address 00000000
Jul 29 17:00:41 kakerlak kernel:  printing eip: 
Jul 29 17:00:41 kakerlak kernel: c026cc89
Jul 29 17:00:41 kakerlak kernel: *pde = 00000000
Jul 29 17:00:41 kakerlak kernel: Oops: 0000 [#1]
Jul 29 17:00:41 kakerlak kernel: CPU:    0
Jul 29 17:00:41 kakerlak kernel: EIP:    0060:[scsi_device_get+25/112]
Not tainted
Jul 29 17:00:41 kakerlak kernel: EFLAGS: 00010292
Jul 29 17:00:41 kakerlak kernel: EIP is at scsi_device_get+0x19/0x70
Jul 29 17:00:41 kakerlak kernel: eax: 00000000   ebx: ca35d800   ecx:
cc2fb200   edx: c933b380
Jul 29 17:00:41 kakerlak kernel: esi: 00000001   edi: d3423840   ebp:
cc2fb200   esp: d3e01aec
Jul 29 17:00:41 kakerlak kernel: ds: 007b   es: 007b   ss: 0068
Jul 29 17:00:42 kakerlak kernel: Process khubd (pid: 5, threadinfo=d3e00000 task=d3f8e040)
Jul 29 17:00:42 kakerlak kernel: Stack: d3e00000 ca35d800 c02908c2 ca35d800 d3c4d400 d3e00000 c0290880 d3c64140
Jul 29 17:00:42 kakerlak kernel:        00000000 c015b7bc cc2fb200 d3e01c14 d3e00000 d3ccd800 c0108260 d3c64158
Jul 29 17:00:42 kakerlak kernel:        d3e00000 00000000 d3c64140 00000001 d3e01c14 d3c4d400 c015b89d d3c64140
Jul 29 17:00:42 kakerlak kernel: Call Trace: 
Jul 29 17:00:42 kakerlak kernel:  [sd_open+66/288] sd_open+0x42/0x120
Jul 29 17:00:42 kakerlak kernel:  [sd_open+0/288] sd_open+0x0/0x120
Jul 29 17:00:42 kakerlak kernel:  [do_open+908/1008] do_open+0x38c/0x3f0
Jul 29 17:00:42 kakerlak kernel:  [__up_wakeup+8/40] __up_wakeup+0x8/0x28
Jul 29 17:00:42 kakerlak kernel:  [blkdev_get+125/160] blkdev_get+0x7d/0xa0
Jul 29 17:00:42 kakerlak kernel:  [register_disk+191/352] register_disk+0xbf/0x160
Jul 29 17:00:42 kakerlak kernel:  [add_disk+78/96] add_disk+0x4e/0x60
Jul 29 17:00:42 kakerlak kernel:  [exact_match+0/16] exact_match+0x0/0x10
Jul 29 17:00:42 kakerlak kernel:  [exact_lock+0/32] exact_lock+0x0/0x20
Jul 29 17:00:42 kakerlak kernel:  [sd_probe+456/720] sd_probe+0x1c8/0x2d0
Jul 29 17:00:42 kakerlak kernel:  [bus_match+69/128] bus_match+0x45/0x80
Jul 29 17:00:42 kakerlak kernel:  [device_attach+67/128] device_attach+0x43/0x80
Jul 29 17:00:42 kakerlak kernel:  [bus_add_device+100/176] bus_add_device+0x64/0xb0
Jul 29 17:00:42 kakerlak kernel:  [device_add+205/256] device_add+0xcd/0x100
Jul 29 17:00:42 kakerlak kernel:  [scsi_device_register+213/464] scsi_device_register+0xd5/0x1d0
Jul 29 17:00:42 kakerlak kernel:  [_end+389556744/1068411384] slave_configure+0x0/0x10 [usb_storage]
Jul 29 17:00:42 kakerlak kernel:  [scsi_add_lun+675/928] scsi_add_lun+0x2a3/0x3a0
Jul 29 17:00:42 kakerlak kernel:  [scsi_probe_and_add_lun+157/304] scsi_probe_and_add_lun+0x9d/0x130
Jul 29 17:00:42 kakerlak kernel:  [scsi_scan_target+80/208] scsi_scan_target+0x50/0xd0
Jul 29 17:00:42 kakerlak kernel:  [scsi_scan_host+57/96] scsi_scan_host+0x39/0x60
Jul 29 17:00:42 kakerlak kernel:  [_end+389567101/1068411384] storage_probe+0x125/0x190 [usb_storage]
Jul 29 17:00:42 kakerlak kernel:  [sysfs_create+113/160] sysfs_create+0x71/0xa0
Jul 29 17:00:42 kakerlak kernel:  [usb_device_probe+118/160] usb_device_probe+0x76/0xa0
Jul 29 17:00:42 kakerlak kernel:  [bus_match+69/128] bus_match+0x45/0x80
Jul 29 17:00:42 kakerlak kernel:  [device_attach+67/128] device_attach+0x43/0x80
Jul 29 17:00:42 kakerlak kernel:  [bus_add_device+100/176] bus_add_device+0x64/0xb0
Jul 29 17:00:42 kakerlak kernel:  [device_add+205/256] device_add+0xcd/0x100
Jul 29 17:00:42 kakerlak kernel:  [usb_new_device+980/1312] usb_new_device+0x3d4/0x520
Jul 29 17:00:42 kakerlak kernel:  [hub_port_connect_change+436/800] hub_port_connect_change+0x1b4/0x320
Jul 29 17:00:42 kakerlak kernel:  [hub_events+720/848] hub_events+0x2d0/0x350
Jul 29 17:00:42 kakerlak kernel:  [hub_thread+45/240] hub_thread+0x2d/0xf0
Jul 29 17:00:42 kakerlak kernel:  [ret_from_fork+6/20] ret_from_fork+0x6/0x14
Jul 29 17:00:42 kakerlak kernel:  [default_wake_function+0/48] default_wake_function+0x0/0x30
Jul 29 17:00:42 kakerlak kernel:  [hub_thread+0/240] hub_thread+0x0/0xf0
Jul 29 17:00:42 kakerlak kernel:  [kernel_thread_helper+5/12] kernel_thread_helper+0x5/0xc
Jul 29 17:00:42 kakerlak kernel: 
Jul 29 17:00:42 kakerlak kernel: Code: 8b 10 85 d2 74 2f b8 00 e0 ff ff 21 e0 ff 40 14 83 3a 02 74 
Jul 29 17:01:47 kakerlak kernel: bio too big device sda1 (1 > 0) 
Jul 29 17:01:47 kakerlak kernel: FAT: Directory bread(block 499) failed
Jul 29 17:01:47 kakerlak kernel: bio too big device sda1 (1 > 0)
Jul 29 17:01:47 kakerlak kernel: FAT: Directory bread(block 500) failed
...
Jul 29 17:01:57 kakerlak kernel: buffer layer error at fs/buffer.c:2800
Jul 29 17:01:57 kakerlak kernel: Call Trace: 
Jul 29 17:01:57 kakerlak kernel:  [drop_buffers+179/192] drop_buffers+0xb3/0xc0
Jul 29 17:01:57 kakerlak kernel:  [try_to_free_buffers+71/208] try_to_free_buffers+0x47/0xd0
Jul 29 17:01:57 kakerlak kernel:  [block_invalidatepage+174/224] block_invalidatepage+0xae/0xe0
Jul 29 17:01:57 kakerlak kernel:  [do_invalidatepage+39/48] do_invalidatepage+0x27/0x30
Jul 29 17:01:57 kakerlak kernel:  [truncate_complete_page+123/128] truncate_complete_page+0x7b/0x80
Jul 29 17:01:57 kakerlak kernel:  [truncate_inode_pages+240/656] truncate_inode_pages+0xf0/0x290
Jul 29 17:01:57 kakerlak kernel:  [invalidate_inode_buffers+17/112] invalidate_inode_buffers+0x11/0x70
Jul 29 17:01:57 kakerlak kernel:  [dispose_list+151/160] dispose_list+0x97/0xa0
Jul 29 17:01:57 kakerlak kernel:  [invalidate_inodes+154/192] invalidate_inodes+0x9a/0xc0
Jul 29 17:01:57 kakerlak kernel:  [generic_shutdown_super+121/400] generic_shutdown_super+0x79/0x190
Jul 29 17:01:57 kakerlak kernel:  [kill_block_super+29/80] kill_block_super+0x1d/0x50
Jul 29 17:01:57 kakerlak kernel:  [deactivate_super+94/192] deactivate_super+0x5e/0xc0
Jul 29 17:01:57 kakerlak kernel:  [sys_umount+63/144] sys_umount+0x3f/0x90
Jul 29 17:01:57 kakerlak kernel:  [sys_oldumount+23/32] sys_oldumount+0x17/0x20
Jul 29 17:01:57 kakerlak kernel:  [syscall_call+7/11] syscall_call+0x7/0xb
... (repeating a couple of times)

Maybe my error can help to trace that down. I cannot reproduce, tho

After that the usb stack was dead. It's not a module, so I didn't tried
to unload it.

-- 
Regards,

Wiktor Wodecki

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

Re: 2.6.0-test2 usb stack crashed was: Re: bug in 2.6.0test2

[Nico Schottelius]

[-- Attachment #1: Type: text/plain, Size: 11516 bytes --]

We've some more information, but tomorrow. My co-worker
is too tired now :)

Nico

Wiktor Wodecki [Tue, Jul 29, 2003 at 05:52:51PM +0200]:
> Hello,
> 
> On Tue, Jul 29, 2003 at 06:43:17AM -0500, Steve Lord wrote:
> > On Mon, 2003-07-28 at 17:26, Nico Schottelius wrote:
> > > Steve Lord [Mon, Jul 28, 2003 at 03:47:30PM -0500]:
> > > > 
> > > > Something else went wrong before you crashed:
> > > > 
> > > > bio too big device loop0 (2 > 0)
> > > > 
> > > > This means you cannot use any bio larger than zero to this device,
> > > 
> > > assume i didn't understand very much you told me..what is a bio?
> > > how do I use it? and why is it too big here?
> > 
> > It looks like the loop device may not be correctly initialized yet,
> > no I/O is possible to it yet.
> > 
> > > 
> > > > which is probably why ext2 said this, since it caught the error when
> > > > building the bio.
> > > 
> > > ext2? I am wondering..afai understood that, the root wasn't even
> > > decrypted, how can the kernel try to ext2-mount it?
> > > 
> > > > EXT2-fs: unable to read superblock
> > > > 
> > > > XFS didn't catch the error building the bio and submitted it, at
> > > > which point the I/O tripped the BUG. I can fix this part, but
> > > > the original problem is something I know nothing about.
> > > 
> > > ..or better why does it start mounting/before decrypt?
> > > 
> > 
> > I have never used a crypto loop device, so I cannot what is really
> > going on. Some initialization step may be missing in the loop device
> > which means it is not usable, the mount it happening because the
> > kernel was told to mount it. If you are not specifying a filesystem
> > type, then possibly what is happening is it is attempting to open
> > the device as different filesystems, these all fail, until xfs
> > which does not detect the underlying error on the loop device,
> > and issues the IO which causes the BUG.
> 
> I just experienced a similar bug.
> I disconnected by accident the usb hob from power and the write crashed:
> 
> Jul 29 17:00:38 kakerlak kernel: SCSI error : <1 0 0 0> return code =
> 0x70000
> Jul 29 17:00:38 kakerlak kernel: end_request: I/O error, dev sda, sector
> 11218
> Jul 29 17:00:38 kakerlak kernel: Buffer I/O error on device sda1,
> logical block 11155
> Jul 29 17:00:38 kakerlak kernel: error on device sda1, logical block
> 52829
> Jul 29 17:00:38 kakerlak kernel: Buffer I/O error on device sda1,
> logical block 52830
> Jul 29 17:00:38 kakerlak kernel: Buffer I/O error on device sda1,
> logical block 52831
> Jul 29 17:00:38 kakerlak kernel: Buffer I/O error on device sda1,
> logical block 52832
> Jul 29 17:00:38 kakerlak kernel: Buffer I/O error on device sda1,
> logical block 52833
> ...
> Jul 29 17:00:39 kakerlak kernel: Buffer I/O error on device sda1,
> logical block 52882
> Jul 29 17:00:39 kakerlak kernel: scsi1 (0:0): rejecting I/O to offline
> device
> Jul 29 17:00:39 kakerlak kernel: Buffer I/O error on device sda1,
> logical block 52883
> ...
> ul 29 17:00:40 kakerlak kernel: FAT: Filesystem panic (dev sda1)
> Jul 29 17:00:40 kakerlak kernel:     unable to read i-node block (i_pos
> 7987)
> Jul 29 17:00:40 kakerlak kernel:     File system has been set read-only
> Jul 29 17:00:40 kakerlak kernel: usb 1-2.3: USB disconnect, address 3
> Jul 29 17:00:40 kakerlak kernel: usb 1-2.4: USB disconnect, address 4
> Jul 29 17:00:40 kakerlak kernel: bio too big device sda1 (1 > 0)
> Jul 29 17:00:40 kakerlak kernel: FAT: bread(block 52) in fat_access
> failed
> Jul 29 17:00:40 kakerlak kernel: bio too big device sda1 (1 > 0)
> 
> nothing wrong here, was my fault
> After powering on the usb hub again:
> 
> Jul 29 17:00:41 kakerlak kernel: hub 1-0:0: debounce: port 2: delay
> 100ms stable 4 status 0x101
> Jul 29 17:00:41 kakerlak kernel: hub 1-0:0: new USB device on port 2,
> assigned address 6
> Jul 29 17:00:41 kakerlak kernel: hub 1-2:0: USB hub found
> Jul 29 17:00:41 kakerlak kernel: hub 1-2:0: 4 ports detected
> Jul 29 17:00:41 kakerlak kernel: hub 1-2:0: debounce: port 1: delay
> 100ms stable 4 status 0x101
> Jul 29 17:00:41 kakerlak kernel: hub 1-2:0: new USB device on port 1,
> assigned address 7
> Jul 29 17:00:41 kakerlak kernel: scsi2 : SCSI emulation for USB Mass
> Storage devices
> Jul 29 17:00:41 kakerlak kernel:   Vendor: 3SYSTEM   Model: USB FLASH
> DISK    Rev: 1.00
> Jul 29 17:00:41 kakerlak kernel:   Type:   Direct-Access
> ANSI SCSI revision: 02
> Jul 29 17:00:41 kakerlak kernel: SCSI device sda: 256000 512-byte hdwr
> sectors (131 MB)
> Jul 29 17:00:41 kakerlak kernel: sda: Write Protect is off
> Jul 29 17:00:41 kakerlak kernel: sda: Mode Sense: 00 0e 00 00
> Jul 29 17:00:41 kakerlak kernel: sda: cache data unavailable
> Jul 29 17:00:41 kakerlak kernel: sda: assuming drive cache: write
> through
> Jul 29 17:00:41 kakerlak kernel: Unable to handle kernel NULL pointer
> dereference at virtual address 00000000
> Jul 29 17:00:41 kakerlak kernel:  printing eip: 
> Jul 29 17:00:41 kakerlak kernel: c026cc89
> Jul 29 17:00:41 kakerlak kernel: *pde = 00000000
> Jul 29 17:00:41 kakerlak kernel: Oops: 0000 [#1]
> Jul 29 17:00:41 kakerlak kernel: CPU:    0
> Jul 29 17:00:41 kakerlak kernel: EIP:    0060:[scsi_device_get+25/112]
> Not tainted
> Jul 29 17:00:41 kakerlak kernel: EFLAGS: 00010292
> Jul 29 17:00:41 kakerlak kernel: EIP is at scsi_device_get+0x19/0x70
> Jul 29 17:00:41 kakerlak kernel: eax: 00000000   ebx: ca35d800   ecx:
> cc2fb200   edx: c933b380
> Jul 29 17:00:41 kakerlak kernel: esi: 00000001   edi: d3423840   ebp:
> cc2fb200   esp: d3e01aec
> Jul 29 17:00:41 kakerlak kernel: ds: 007b   es: 007b   ss: 0068
> Jul 29 17:00:42 kakerlak kernel: Process khubd (pid: 5, threadinfo=d3e00000 task=d3f8e040)
> Jul 29 17:00:42 kakerlak kernel: Stack: d3e00000 ca35d800 c02908c2 ca35d800 d3c4d400 d3e00000 c0290880 d3c64140
> Jul 29 17:00:42 kakerlak kernel:        00000000 c015b7bc cc2fb200 d3e01c14 d3e00000 d3ccd800 c0108260 d3c64158
> Jul 29 17:00:42 kakerlak kernel:        d3e00000 00000000 d3c64140 00000001 d3e01c14 d3c4d400 c015b89d d3c64140
> Jul 29 17:00:42 kakerlak kernel: Call Trace: 
> Jul 29 17:00:42 kakerlak kernel:  [sd_open+66/288] sd_open+0x42/0x120
> Jul 29 17:00:42 kakerlak kernel:  [sd_open+0/288] sd_open+0x0/0x120
> Jul 29 17:00:42 kakerlak kernel:  [do_open+908/1008] do_open+0x38c/0x3f0
> Jul 29 17:00:42 kakerlak kernel:  [__up_wakeup+8/40] __up_wakeup+0x8/0x28
> Jul 29 17:00:42 kakerlak kernel:  [blkdev_get+125/160] blkdev_get+0x7d/0xa0
> Jul 29 17:00:42 kakerlak kernel:  [register_disk+191/352] register_disk+0xbf/0x160
> Jul 29 17:00:42 kakerlak kernel:  [add_disk+78/96] add_disk+0x4e/0x60
> Jul 29 17:00:42 kakerlak kernel:  [exact_match+0/16] exact_match+0x0/0x10
> Jul 29 17:00:42 kakerlak kernel:  [exact_lock+0/32] exact_lock+0x0/0x20
> Jul 29 17:00:42 kakerlak kernel:  [sd_probe+456/720] sd_probe+0x1c8/0x2d0
> Jul 29 17:00:42 kakerlak kernel:  [bus_match+69/128] bus_match+0x45/0x80
> Jul 29 17:00:42 kakerlak kernel:  [device_attach+67/128] device_attach+0x43/0x80
> Jul 29 17:00:42 kakerlak kernel:  [bus_add_device+100/176] bus_add_device+0x64/0xb0
> Jul 29 17:00:42 kakerlak kernel:  [device_add+205/256] device_add+0xcd/0x100
> Jul 29 17:00:42 kakerlak kernel:  [scsi_device_register+213/464] scsi_device_register+0xd5/0x1d0
> Jul 29 17:00:42 kakerlak kernel:  [_end+389556744/1068411384] slave_configure+0x0/0x10 [usb_storage]
> Jul 29 17:00:42 kakerlak kernel:  [scsi_add_lun+675/928] scsi_add_lun+0x2a3/0x3a0
> Jul 29 17:00:42 kakerlak kernel:  [scsi_probe_and_add_lun+157/304] scsi_probe_and_add_lun+0x9d/0x130
> Jul 29 17:00:42 kakerlak kernel:  [scsi_scan_target+80/208] scsi_scan_target+0x50/0xd0
> Jul 29 17:00:42 kakerlak kernel:  [scsi_scan_host+57/96] scsi_scan_host+0x39/0x60
> Jul 29 17:00:42 kakerlak kernel:  [_end+389567101/1068411384] storage_probe+0x125/0x190 [usb_storage]
> Jul 29 17:00:42 kakerlak kernel:  [sysfs_create+113/160] sysfs_create+0x71/0xa0
> Jul 29 17:00:42 kakerlak kernel:  [usb_device_probe+118/160] usb_device_probe+0x76/0xa0
> Jul 29 17:00:42 kakerlak kernel:  [bus_match+69/128] bus_match+0x45/0x80
> Jul 29 17:00:42 kakerlak kernel:  [device_attach+67/128] device_attach+0x43/0x80
> Jul 29 17:00:42 kakerlak kernel:  [bus_add_device+100/176] bus_add_device+0x64/0xb0
> Jul 29 17:00:42 kakerlak kernel:  [device_add+205/256] device_add+0xcd/0x100
> Jul 29 17:00:42 kakerlak kernel:  [usb_new_device+980/1312] usb_new_device+0x3d4/0x520
> Jul 29 17:00:42 kakerlak kernel:  [hub_port_connect_change+436/800] hub_port_connect_change+0x1b4/0x320
> Jul 29 17:00:42 kakerlak kernel:  [hub_events+720/848] hub_events+0x2d0/0x350
> Jul 29 17:00:42 kakerlak kernel:  [hub_thread+45/240] hub_thread+0x2d/0xf0
> Jul 29 17:00:42 kakerlak kernel:  [ret_from_fork+6/20] ret_from_fork+0x6/0x14
> Jul 29 17:00:42 kakerlak kernel:  [default_wake_function+0/48] default_wake_function+0x0/0x30
> Jul 29 17:00:42 kakerlak kernel:  [hub_thread+0/240] hub_thread+0x0/0xf0
> Jul 29 17:00:42 kakerlak kernel:  [kernel_thread_helper+5/12] kernel_thread_helper+0x5/0xc
> Jul 29 17:00:42 kakerlak kernel: 
> Jul 29 17:00:42 kakerlak kernel: Code: 8b 10 85 d2 74 2f b8 00 e0 ff ff 21 e0 ff 40 14 83 3a 02 74 
> Jul 29 17:01:47 kakerlak kernel: bio too big device sda1 (1 > 0) 
> Jul 29 17:01:47 kakerlak kernel: FAT: Directory bread(block 499) failed
> Jul 29 17:01:47 kakerlak kernel: bio too big device sda1 (1 > 0)
> Jul 29 17:01:47 kakerlak kernel: FAT: Directory bread(block 500) failed
> ...
> Jul 29 17:01:57 kakerlak kernel: buffer layer error at fs/buffer.c:2800
> Jul 29 17:01:57 kakerlak kernel: Call Trace: 
> Jul 29 17:01:57 kakerlak kernel:  [drop_buffers+179/192] drop_buffers+0xb3/0xc0
> Jul 29 17:01:57 kakerlak kernel:  [try_to_free_buffers+71/208] try_to_free_buffers+0x47/0xd0
> Jul 29 17:01:57 kakerlak kernel:  [block_invalidatepage+174/224] block_invalidatepage+0xae/0xe0
> Jul 29 17:01:57 kakerlak kernel:  [do_invalidatepage+39/48] do_invalidatepage+0x27/0x30
> Jul 29 17:01:57 kakerlak kernel:  [truncate_complete_page+123/128] truncate_complete_page+0x7b/0x80
> Jul 29 17:01:57 kakerlak kernel:  [truncate_inode_pages+240/656] truncate_inode_pages+0xf0/0x290
> Jul 29 17:01:57 kakerlak kernel:  [invalidate_inode_buffers+17/112] invalidate_inode_buffers+0x11/0x70
> Jul 29 17:01:57 kakerlak kernel:  [dispose_list+151/160] dispose_list+0x97/0xa0
> Jul 29 17:01:57 kakerlak kernel:  [invalidate_inodes+154/192] invalidate_inodes+0x9a/0xc0
> Jul 29 17:01:57 kakerlak kernel:  [generic_shutdown_super+121/400] generic_shutdown_super+0x79/0x190
> Jul 29 17:01:57 kakerlak kernel:  [kill_block_super+29/80] kill_block_super+0x1d/0x50
> Jul 29 17:01:57 kakerlak kernel:  [deactivate_super+94/192] deactivate_super+0x5e/0xc0
> Jul 29 17:01:57 kakerlak kernel:  [sys_umount+63/144] sys_umount+0x3f/0x90
> Jul 29 17:01:57 kakerlak kernel:  [sys_oldumount+23/32] sys_oldumount+0x17/0x20
> Jul 29 17:01:57 kakerlak kernel:  [syscall_call+7/11] syscall_call+0x7/0xb
> ... (repeating a couple of times)
> 
> Maybe my error can help to trace that down. I cannot reproduce, tho
> 
> After that the usb stack was dead. It's not a module, so I didn't tried
> to unload it.
> 
> -- 
> Regards,
> 
> Wiktor Wodecki



-- 
echo God bless America | sed 's/.*\(A.*$\)/Why \1?/'
pgp: new id: 0x8D0E27A4 | ftp.schottelius.org/pub/familiy/nico/pgp-key.new

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

Re: bug in 2.6.0test2

[Nico Schottelius]

[-- Attachment #1: Type: text/plain, Size: 2753 bytes --]

Steve Lord [Tue, Jul 29, 2003 at 06:43:17AM -0500]:
> On Mon, 2003-07-28 at 17:26, Nico Schottelius wrote:
> > Steve Lord [Mon, Jul 28, 2003 at 03:47:30PM -0500]:
> > > 
> > > Something else went wrong before you crashed:
> > > 
> > > bio too big device loop0 (2 > 0)
> > > 
> > > This means you cannot use any bio larger than zero to this device,
> > 
> > assume i didn't understand very much you told me..what is a bio?
> > how do I use it? and why is it too big here?
> 
> It looks like the loop device may not be correctly initialized yet,
> no I/O is possible to it yet.

...we tried and experiement some more, here the results:
   - first we had old modutils (now: module-init-tools 0.9.13pre)
   - all modules are able to load now (loaded: aes,loop,cryptoloop)
   - losetup -e aes /dev/hda1 /dev/loop0 
      --> ioctl: LOOP_SET_FD: invalid argument
   - mount /dev/hda1 / -o loop,encryption=aes
      --> asks for pass, but doesn't unencrypt it
         --> it fails to mount the xfs filesystem below
            --> "mount: you must specify fs type..."

the filesystem on hda1 is encrypted with a 128 bit key / aes.

> > > which is probably why ext2 said this, since it caught the error when
> > > building the bio.
> > 
> > ext2? I am wondering..afai understood that, the root wasn't even
> > decrypted, how can the kernel try to ext2-mount it?

oh..btw, the ramdisk is ext2..

> > > EXT2-fs: unable to read superblock
> > > 
> > > XFS didn't catch the error building the bio and submitted it, at
> > > which point the I/O tripped the BUG. I can fix this part, but
> > > the original problem is something I know nothing about.
> > 
> > ..or better why does it start mounting/before decrypt?
> > 
> 
> I have never used a crypto loop device, so I cannot what is really
> going on. Some initialization step may be missing in the loop device
> which means it is not usable,

looks like the losetup is the problem...

> the mount it happening because the
> kernel was told to mount it. If you are not specifying a filesystem
> type, then possibly what is happening is it is attempting to open
> the device as different filesystems, these all fail, until xfs
> which does not detect the underlying error on the loop device,
> and issues the IO which causes the BUG.

..which you are gonna fix ? :)

> So, we caused the crash, but you were on your way to one anyway,
> eventually it would have failed to find a root device and given
> up that way.

hopefully we'll get it soon..
my co-worker has to switch between 2.4 and 2.6 daily now..

Nico

-- 
echo God bless America | sed 's/.*\(A.*$\)/Why \1?/'
pgp: new id: 0x8D0E27A4 | ftp.schottelius.org/pub/familiy/nico/pgp-key.new

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

Re: bug in 2.6.0test2

[Andries Brouwer]

On Thu, Jul 31, 2003 at 01:14:18PM +0200, Nico Schottelius wrote:

> ...we tried and experiment some more, here the results:
>    - first we had old modutils (now: module-init-tools 0.9.13pre)
>    - all modules are able to load now (loaded: aes,loop,cryptoloop)
>    - losetup -e aes /dev/hda1 /dev/loop0 
>       --> ioctl: LOOP_SET_FD: invalid argument

You interchange the parameters. Call is
	losetup [options] loop_device file