Re: 2.4.18-pre9-xfs-shawn4

public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed

* Re: 2.4.18-pre9-xfs-shawn4  -  hpfs bug
       [not found] <20020212140036.A223@dagb>
@ 2002-02-12 14:16 ` Shawn Starr
  2002-02-12 14:17   ` Pozsar Balazs
  2002-02-13 10:09   ` Dag Bakke
  0 siblings, 2 replies; 6+ messages in thread
From: Shawn Starr @ 2002-02-12 14:16 UTC (permalink / raw)
  To: Dag Bakke; +Cc: Linux, xfs

Some others have reported problems with superblock reading on boot.
There may be some code that has changed superblock reading but this
might be different.

Shawn.


On Tue, 2002-02-12 at 08:00, Dag Bakke wrote:
> Hi.
> 
> Compiling in support for hpfs in 2.4.18-pre9-xfs-shawn4 causes panic on
> boot.
> (I do have a some devicedriver patches added to your patch, but nothing related to
> core, vfs or hpfs.)
> 
> Thanks,
> 
> Dag B
> 
> 
> root@dagb:~# ksymoops -L -m /boot/System.map -K <~dagb/kernelcrash.txt 
> ksymoops 2.4.3 on i686 2.4.18-pre9-xfs-shawn4.  Options used
>      -V (default)
>      -K (specified)
>      -L (specified)
>      -o /lib/modules/2.4.18-pre9-xfs-shawn4/ (default)
>      -m /boot/System.map (specified)
> 
> No modules in ksyms, skipping objects
> invalid operand:        0000
> CPU:    0
> EIP:  0010:[<c0136d10>] Not tainted
> Using defaults from ksymoops -t elf32-i386 -a i386
> EFLAGS: 00010286
> Warning (Oops_read): Code line not seen, dumping what data is available
> 
> >>EIP; c0136d10 <grow_buffers+50/100>   <=====
> 
> Stack:  00000302  00000000  00000000  c13a91c0  00002240  c0134eb7  00000302  00000000
>         00000000  cffe7ed8  cfe6a000  cfe6a044  c01350aa  00000302  00000000  00000000
>         cffe7ed8  cfe6a000  c13a91c0  c019e96c  00000302  00000000  00000000  00000000
> Call Trace: [<c0134eb7>] [<c01350aa>] [<c019e96e>] [<c01a7a8d>] [<c01378a9>] [<c0137c27>] [<c010503a>] [<c010504c>] [<c01054e8>]
> Code: 0f 0b b9 ff ff ff ff 89 fa b6 00 90 8d 74 26 06 8b 44 24 20
> 
> Trace; c0134eb6 <getblk+26/40>
> Trace; c01350aa <bread+1a/c0>
> Trace; c019e96e <hpfs_map_sector+1e/40>
> Trace; c01a7a8c <hpfs_read_super+15c/730>
> Trace; c01378a8 <insert_super+38/40>
> Trace; c0137c26 <read_super+56/b0>
> Trace; c010503a <prepare_namespace+a/10>
> Trace; c010504c <init+c/110>
> Trace; c01054e8 <kernel_thread+28/40>
> Code;  c0136d10 <grow_buffers+50/100>
> 00000000 <_EIP>:
> Code;  c0136d10 <grow_buffers+50/100>
>    0:   0f 0b                     ud2a   
> Code;  c0136d12 <grow_buffers+52/100>
>    2:   b9 ff ff ff ff            mov    $0xffffffff,%ecx
> Code;  c0136d16 <grow_buffers+56/100>
>    7:   89 fa                     mov    %edi,%edx
> Code;  c0136d18 <grow_buffers+58/100>
>    9:   b6 00                     mov    $0x0,%dh
> Code;  c0136d1a <grow_buffers+5a/100>
>    b:   90                        nop    
> Code;  c0136d1c <grow_buffers+5c/100>
>    c:   8d 74 26 06               lea    0x6(%esi,1),%esi
> Code;  c0136d20 <grow_buffers+60/100>
>   10:   8b 44 24 20               mov    0x20(%esp,1),%eax
> 
> 
> 1 warning issued.  Results may not be reliable.
> 



^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: 2.4.18-pre9-xfs-shawn4  -  hpfs bug
  2002-02-12 14:16 ` 2.4.18-pre9-xfs-shawn4 - hpfs bug Shawn Starr
@ 2002-02-12 14:17   ` Pozsar Balazs
  2002-02-12 14:32     ` Shawn Starr
  2002-02-12 15:13     ` Alan Cox
  2002-02-13 10:09   ` Dag Bakke
  1 sibling, 2 replies; 6+ messages in thread
From: Pozsar Balazs @ 2002-02-12 14:17 UTC (permalink / raw)
  To: Shawn Starr; +Cc: Dag Bakke, Linux, xfs


I also get an oops with 2.4.18-pre9-ac1, pnpbios compiled in, but no xfs.
So I think this is a pnpbios problem.


On 12 Feb 2002, Shawn Starr wrote:

> Some others have reported problems with superblock reading on boot.
> There may be some code that has changed superblock reading but this
> might be different.
>
> Shawn.
>
>
> On Tue, 2002-02-12 at 08:00, Dag Bakke wrote:
> > Hi.
> >
> > Compiling in support for hpfs in 2.4.18-pre9-xfs-shawn4 causes panic on
> > boot.
> > (I do have a some devicedriver patches added to your patch, but nothing related to
> > core, vfs or hpfs.)
> >
> > Thanks,
> >
> > Dag B
> >
> >
> > root@dagb:~# ksymoops -L -m /boot/System.map -K <~dagb/kernelcrash.txt
> > ksymoops 2.4.3 on i686 2.4.18-pre9-xfs-shawn4.  Options used
> >      -V (default)
> >      -K (specified)
> >      -L (specified)
> >      -o /lib/modules/2.4.18-pre9-xfs-shawn4/ (default)
> >      -m /boot/System.map (specified)
> >
> > No modules in ksyms, skipping objects
> > invalid operand:        0000
> > CPU:    0
> > EIP:  0010:[<c0136d10>] Not tainted
> > Using defaults from ksymoops -t elf32-i386 -a i386
> > EFLAGS: 00010286
> > Warning (Oops_read): Code line not seen, dumping what data is available
> >
> > >>EIP; c0136d10 <grow_buffers+50/100>   <=====
> >
> > Stack:  00000302  00000000  00000000  c13a91c0  00002240  c0134eb7  00000302  00000000
> >         00000000  cffe7ed8  cfe6a000  cfe6a044  c01350aa  00000302  00000000  00000000
> >         cffe7ed8  cfe6a000  c13a91c0  c019e96c  00000302  00000000  00000000  00000000
> > Call Trace: [<c0134eb7>] [<c01350aa>] [<c019e96e>] [<c01a7a8d>] [<c01378a9>] [<c0137c27>] [<c010503a>] [<c010504c>] [<c01054e8>]
> > Code: 0f 0b b9 ff ff ff ff 89 fa b6 00 90 8d 74 26 06 8b 44 24 20
> >
> > Trace; c0134eb6 <getblk+26/40>
> > Trace; c01350aa <bread+1a/c0>
> > Trace; c019e96e <hpfs_map_sector+1e/40>
> > Trace; c01a7a8c <hpfs_read_super+15c/730>
> > Trace; c01378a8 <insert_super+38/40>
> > Trace; c0137c26 <read_super+56/b0>
> > Trace; c010503a <prepare_namespace+a/10>
> > Trace; c010504c <init+c/110>
> > Trace; c01054e8 <kernel_thread+28/40>
> > Code;  c0136d10 <grow_buffers+50/100>
> > 00000000 <_EIP>:
> > Code;  c0136d10 <grow_buffers+50/100>
> >    0:   0f 0b                     ud2a
> > Code;  c0136d12 <grow_buffers+52/100>
> >    2:   b9 ff ff ff ff            mov    $0xffffffff,%ecx
> > Code;  c0136d16 <grow_buffers+56/100>
> >    7:   89 fa                     mov    %edi,%edx
> > Code;  c0136d18 <grow_buffers+58/100>
> >    9:   b6 00                     mov    $0x0,%dh
> > Code;  c0136d1a <grow_buffers+5a/100>
> >    b:   90                        nop
> > Code;  c0136d1c <grow_buffers+5c/100>
> >    c:   8d 74 26 06               lea    0x6(%esi,1),%esi
> > Code;  c0136d20 <grow_buffers+60/100>
> >   10:   8b 44 24 20               mov    0x20(%esp,1),%eax
> >
> >
> > 1 warning issued.  Results may not be reliable.
> >
>
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/
>

-- 
Balazs Pozsar


^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: 2.4.18-pre9-xfs-shawn4  -  hpfs bug
  2002-02-12 14:17   ` Pozsar Balazs
@ 2002-02-12 14:32     ` Shawn Starr
  2002-02-12 15:13     ` Alan Cox
  1 sibling, 0 replies; 6+ messages in thread
From: Shawn Starr @ 2002-02-12 14:32 UTC (permalink / raw)
  To: Pozsar Balazs; +Cc: Linux

I have not applied -pre9-ac1 to my tree. This is suspect then. I will
attempt to reproduce today.

Shawn.

On Tue, 2002-02-12 at 09:17, Pozsar Balazs wrote:
> 
> I also get an oops with 2.4.18-pre9-ac1, pnpbios compiled in, but no xfs.
> So I think this is a pnpbios problem.
> 
> 
> On 12 Feb 2002, Shawn Starr wrote:
> 
> > Some others have reported problems with superblock reading on boot.
> > There may be some code that has changed superblock reading but this
> > might be different.
> >
> > Shawn.
> >
> >
> > On Tue, 2002-02-12 at 08:00, Dag Bakke wrote:
> > > Hi.
> > >
> > > Compiling in support for hpfs in 2.4.18-pre9-xfs-shawn4 causes panic on
> > > boot.
> > > (I do have a some devicedriver patches added to your patch, but nothing related to
> > > core, vfs or hpfs.)
> > >
> > > Thanks,
> > >
> > > Dag B
> > >
> > >
> > > root@dagb:~# ksymoops -L -m /boot/System.map -K <~dagb/kernelcrash.txt
> > > ksymoops 2.4.3 on i686 2.4.18-pre9-xfs-shawn4.  Options used
> > >      -V (default)
> > >      -K (specified)
> > >      -L (specified)
> > >      -o /lib/modules/2.4.18-pre9-xfs-shawn4/ (default)
> > >      -m /boot/System.map (specified)
> > >
> > > No modules in ksyms, skipping objects
> > > invalid operand:        0000
> > > CPU:    0
> > > EIP:  0010:[<c0136d10>] Not tainted
> > > Using defaults from ksymoops -t elf32-i386 -a i386
> > > EFLAGS: 00010286
> > > Warning (Oops_read): Code line not seen, dumping what data is available
> > >
> > > >>EIP; c0136d10 <grow_buffers+50/100>   <=====
> > >
> > > Stack:  00000302  00000000  00000000  c13a91c0  00002240  c0134eb7  00000302  00000000
> > >         00000000  cffe7ed8  cfe6a000  cfe6a044  c01350aa  00000302  00000000  00000000
> > >         cffe7ed8  cfe6a000  c13a91c0  c019e96c  00000302  00000000  00000000  00000000
> > > Call Trace: [<c0134eb7>] [<c01350aa>] [<c019e96e>] [<c01a7a8d>] [<c01378a9>] [<c0137c27>] [<c010503a>] [<c010504c>] [<c01054e8>]
> > > Code: 0f 0b b9 ff ff ff ff 89 fa b6 00 90 8d 74 26 06 8b 44 24 20
> > >
> > > Trace; c0134eb6 <getblk+26/40>
> > > Trace; c01350aa <bread+1a/c0>
> > > Trace; c019e96e <hpfs_map_sector+1e/40>
> > > Trace; c01a7a8c <hpfs_read_super+15c/730>
> > > Trace; c01378a8 <insert_super+38/40>
> > > Trace; c0137c26 <read_super+56/b0>
> > > Trace; c010503a <prepare_namespace+a/10>
> > > Trace; c010504c <init+c/110>
> > > Trace; c01054e8 <kernel_thread+28/40>
> > > Code;  c0136d10 <grow_buffers+50/100>
> > > 00000000 <_EIP>:
> > > Code;  c0136d10 <grow_buffers+50/100>
> > >    0:   0f 0b                     ud2a
> > > Code;  c0136d12 <grow_buffers+52/100>
> > >    2:   b9 ff ff ff ff            mov    $0xffffffff,%ecx
> > > Code;  c0136d16 <grow_buffers+56/100>
> > >    7:   89 fa                     mov    %edi,%edx
> > > Code;  c0136d18 <grow_buffers+58/100>
> > >    9:   b6 00                     mov    $0x0,%dh
> > > Code;  c0136d1a <grow_buffers+5a/100>
> > >    b:   90                        nop
> > > Code;  c0136d1c <grow_buffers+5c/100>
> > >    c:   8d 74 26 06               lea    0x6(%esi,1),%esi
> > > Code;  c0136d20 <grow_buffers+60/100>
> > >   10:   8b 44 24 20               mov    0x20(%esp,1),%eax
> > >
> > >
> > > 1 warning issued.  Results may not be reliable.
> > >
> >
> >
> > -
> > To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> > the body of a message to majordomo@vger.kernel.org
> > More majordomo info at  http://vger.kernel.org/majordomo-info.html
> > Please read the FAQ at  http://www.tux.org/lkml/
> >
> 
> -- 
> Balazs Pozsar
> 
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/
> 



^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: 2.4.18-pre9-xfs-shawn4  -  hpfs bug
  2002-02-12 14:17   ` Pozsar Balazs
  2002-02-12 14:32     ` Shawn Starr
@ 2002-02-12 15:13     ` Alan Cox
  1 sibling, 0 replies; 6+ messages in thread
From: Alan Cox @ 2002-02-12 15:13 UTC (permalink / raw)
  To: Pozsar Balazs; +Cc: Shawn Starr, Dag Bakke, Linux, xfs

> I also get an oops with 2.4.18-pre9-ac1, pnpbios compiled in, but no xfs.
> So I think this is a pnpbios problem.

At the moment there are a couple of pnpbios related problems that need
fixing. One of them is -ac kernel triggered due to the way the pnpbios
docking thread is created, the other is the inability of some bios vendors
to read documentation and may be harder to cure

For the moment assume its the docking thread. I'll fix that soonish

^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: 2.4.18-pre9-xfs-shawn4  -  hpfs bug
  2002-02-12 14:16 ` 2.4.18-pre9-xfs-shawn4 - hpfs bug Shawn Starr
  2002-02-12 14:17   ` Pozsar Balazs
@ 2002-02-13 10:09   ` Dag Bakke
  2002-02-13 15:10     ` Shawn Starr
  1 sibling, 1 reply; 6+ messages in thread
From: Dag Bakke @ 2002-02-13 10:09 UTC (permalink / raw)
  To: Shawn Starr; +Cc: linux-kernel

On Tue, Feb 12, 2002 at 09:16:10AM -0500, Shawn Starr wrote:
> Some others have reported problems with superblock reading on boot.
> There may be some code that has changed superblock reading but this
> might be different.

Booting with BUG() enabled, I get:

kernel BUG at buffer.c:2630! 

The relevant section is:

   2618 static int grow_buffers(kdev_t dev, unsigned long block, int size)
   2619 {
   2620         struct page * page;
   2621         struct block_device *bdev;
   2622         unsigned long index;
   2623         int sizebits;
   2624 
   2625         /* Size must be multiple of hard sectorsize */
   2626         if (size & (get_hardsect_size(dev)-1))
   2627                 BUG();
   2628         /* Size must be within 512 bytes and PAGE_SIZE */
   2629         if (size < 512 || size > PAGE_SIZE)
   2630                 BUG();


My disks are partitioned/formatted as follows:

    hda1        Boot        Primary   Linux ext2                          49.36 
    hda2                    Primary   Linux XFS                        10001.95
    hda3                    Primary   Linux raid autodetect            10001.95
                            Pri/Log   Free Space                       20925.12

    hdc1                    Primary   Linux ext2                          49.36 
    hdc2                    Primary   Linux ext2                       10001.95
    hdc3                    Primary   Linux raid autodetect            10001.95
                            Pri/Log   Free Space                       20925.12

I.e. my hpfs disk is not connected at this time.

I have compiled-in support for:
CONFIG_VIDEO_PROC_FS=y
CONFIG_EXT3_FS=y
CONFIG_FAT_FS=y
CONFIG_MSDOS_FS=y
CONFIG_VFAT_FS=y
CONFIG_TMPFS=y
CONFIG_ISO9660_FS=y
CONFIG_ZISOFS=y
CONFIG_HPFS_FS=y
CONFIG_PROC_FS=y
CONFIG_DEVFS_FS=y
CONFIG_DEVPTS_FS=y
CONFIG_EXT2_FS=y
CONFIG_UDF_FS=y
CONFIG_XFS_FS=y
CONFIG_XFS_DMAPI=y
CONFIG_HAVE_XFS_DMAPI=y
CONFIG_NFS_FS=y
CONFIG_NFS_V3=y
CONFIG_NFSD=y
CONFIG_NFSD_V3=y
CONFIG_ZISOFS_FS=y
CONFIG_ZLIB_FS_INFLATE=y
CONFIG_USB_DEVICEFS=y


Disregarding hpfs for a moment:
I see this during boot with working and non-working kernels:
FAT: bogus logical sector size 0
FAT: bogus logical sector size 0

Not sure what the FAT code complains about, but it could possibly be the
two raid partitions (raid0/xfs). 

Anything else I can provide? kdb appears to require a little bit of
rewiring/replugging. Got no response to keyboardwhacking when I hit the
kdb prompt. Don't know if my USB keyboard makse a difference, but it
probably does.... :-)
If you want kdb stuff, please provide a little roadmap. 

Regards,

Dag B

 
> On Tue, 2002-02-12 at 08:00, Dag Bakke wrote:
> > Hi.
> > 
> > Compiling in support for hpfs in 2.4.18-pre9-xfs-shawn4 causes panic on
> > boot.
> > (I do have a some devicedriver patches added to your patch, but nothing related to
> > core, vfs or hpfs.)
> > 
> > Thanks,
> > 
> > Dag B
> > 
> > 
> > root@dagb:~# ksymoops -L -m /boot/System.map -K <~dagb/kernelcrash.txt 
> > ksymoops 2.4.3 on i686 2.4.18-pre9-xfs-shawn4.  Options used
> >      -V (default)
> >      -K (specified)
> >      -L (specified)
> >      -o /lib/modules/2.4.18-pre9-xfs-shawn4/ (default)
> >      -m /boot/System.map (specified)
> > 
> > No modules in ksyms, skipping objects
> > invalid operand:        0000
> > CPU:    0
> > EIP:  0010:[<c0136d10>] Not tainted
> > Using defaults from ksymoops -t elf32-i386 -a i386
> > EFLAGS: 00010286
> > Warning (Oops_read): Code line not seen, dumping what data is available
> > 
> > >>EIP; c0136d10 <grow_buffers+50/100>   <=====
> > 
> > Stack:  00000302  00000000  00000000  c13a91c0  00002240  c0134eb7  00000302  00000000
> >         00000000  cffe7ed8  cfe6a000  cfe6a044  c01350aa  00000302  00000000  00000000
> >         cffe7ed8  cfe6a000  c13a91c0  c019e96c  00000302  00000000  00000000  00000000
> > Call Trace: [<c0134eb7>] [<c01350aa>] [<c019e96e>] [<c01a7a8d>] [<c01378a9>] [<c0137c27>] [<c010503a>] [<c010504c>] [<c01054e8>]
> > Code: 0f 0b b9 ff ff ff ff 89 fa b6 00 90 8d 74 26 06 8b 44 24 20
> > 
> > Trace; c0134eb6 <getblk+26/40>
> > Trace; c01350aa <bread+1a/c0>
> > Trace; c019e96e <hpfs_map_sector+1e/40>
> > Trace; c01a7a8c <hpfs_read_super+15c/730>
> > Trace; c01378a8 <insert_super+38/40>
> > Trace; c0137c26 <read_super+56/b0>
> > Trace; c010503a <prepare_namespace+a/10>
> > Trace; c010504c <init+c/110>
> > Trace; c01054e8 <kernel_thread+28/40>
> > Code;  c0136d10 <grow_buffers+50/100>
> > 00000000 <_EIP>:
> > Code;  c0136d10 <grow_buffers+50/100>
> >    0:   0f 0b                     ud2a   
> > Code;  c0136d12 <grow_buffers+52/100>
> >    2:   b9 ff ff ff ff            mov    $0xffffffff,%ecx
> > Code;  c0136d16 <grow_buffers+56/100>
> >    7:   89 fa                     mov    %edi,%edx
> > Code;  c0136d18 <grow_buffers+58/100>
> >    9:   b6 00                     mov    $0x0,%dh
> > Code;  c0136d1a <grow_buffers+5a/100>
> >    b:   90                        nop    
> > Code;  c0136d1c <grow_buffers+5c/100>
> >    c:   8d 74 26 06               lea    0x6(%esi,1),%esi
> > Code;  c0136d20 <grow_buffers+60/100>
> >   10:   8b 44 24 20               mov    0x20(%esp,1),%eax
> > 
> > 
> > 1 warning issued.  Results may not be reliable.
> > 
> 
> 
> 

^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: 2.4.18-pre9-xfs-shawn4  -  hpfs bug
  2002-02-13 10:09   ` Dag Bakke
@ 2002-02-13 15:10     ` Shawn Starr
  0 siblings, 0 replies; 6+ messages in thread
From: Shawn Starr @ 2002-02-13 15:10 UTC (permalink / raw)
  To: Dag Bakke; +Cc: Linux

Well, size is being passed in to grow_buffers, something outside is not
less the 512 and greater then PAGE_SIZE (a constant).

Shawn.

On Wed, 2002-02-13 at 05:09, Dag Bakke wrote:
> On Tue, Feb 12, 2002 at 09:16:10AM -0500, Shawn Starr wrote:
> > Some others have reported problems with superblock reading on boot.
> > There may be some code that has changed superblock reading but this
> > might be different.
> 
> Booting with BUG() enabled, I get:
> 
> kernel BUG at buffer.c:2630! 
> 
> The relevant section is:
> 
>    2618 static int grow_buffers(kdev_t dev, unsigned long block, int size)
>    2619 {
>    2620         struct page * page;
>    2621         struct block_device *bdev;
>    2622         unsigned long index;
>    2623         int sizebits;
>    2624 
>    2625         /* Size must be multiple of hard sectorsize */
>    2626         if (size & (get_hardsect_size(dev)-1))
>    2627                 BUG();
>    2628         /* Size must be within 512 bytes and PAGE_SIZE */
>    2629         if (size < 512 || size > PAGE_SIZE)
>    2630                 BUG();
> 
> 
> My disks are partitioned/formatted as follows:
> 
>     hda1        Boot        Primary   Linux ext2                          49.36 
>     hda2                    Primary   Linux XFS                        10001.95
>     hda3                    Primary   Linux raid autodetect            10001.95
>                             Pri/Log   Free Space                       20925.12
> 
>     hdc1                    Primary   Linux ext2                          49.36 
>     hdc2                    Primary   Linux ext2                       10001.95
>     hdc3                    Primary   Linux raid autodetect            10001.95
>                             Pri/Log   Free Space                       20925.12
> 
> I.e. my hpfs disk is not connected at this time.
> 
> I have compiled-in support for:
> CONFIG_VIDEO_PROC_FS=y
> CONFIG_EXT3_FS=y
> CONFIG_FAT_FS=y
> CONFIG_MSDOS_FS=y
> CONFIG_VFAT_FS=y
> CONFIG_TMPFS=y
> CONFIG_ISO9660_FS=y
> CONFIG_ZISOFS=y
> CONFIG_HPFS_FS=y
> CONFIG_PROC_FS=y
> CONFIG_DEVFS_FS=y
> CONFIG_DEVPTS_FS=y
> CONFIG_EXT2_FS=y
> CONFIG_UDF_FS=y
> CONFIG_XFS_FS=y
> CONFIG_XFS_DMAPI=y
> CONFIG_HAVE_XFS_DMAPI=y
> CONFIG_NFS_FS=y
> CONFIG_NFS_V3=y
> CONFIG_NFSD=y
> CONFIG_NFSD_V3=y
> CONFIG_ZISOFS_FS=y
> CONFIG_ZLIB_FS_INFLATE=y
> CONFIG_USB_DEVICEFS=y
> 
> 
> Disregarding hpfs for a moment:
> I see this during boot with working and non-working kernels:
> FAT: bogus logical sector size 0
> FAT: bogus logical sector size 0
> 
> Not sure what the FAT code complains about, but it could possibly be the
> two raid partitions (raid0/xfs). 
> 
> Anything else I can provide? kdb appears to require a little bit of
> rewiring/replugging. Got no response to keyboardwhacking when I hit the
> kdb prompt. Don't know if my USB keyboard makse a difference, but it
> probably does.... :-)
> If you want kdb stuff, please provide a little roadmap. 
> 
> Regards,
> 
> Dag B
> 
>  
> > On Tue, 2002-02-12 at 08:00, Dag Bakke wrote:
> > > Hi.
> > > 
> > > Compiling in support for hpfs in 2.4.18-pre9-xfs-shawn4 causes panic on
> > > boot.
> > > (I do have a some devicedriver patches added to your patch, but nothing related to
> > > core, vfs or hpfs.)
> > > 
> > > Thanks,
> > > 
> > > Dag B
> > > 
> > > 
> > > root@dagb:~# ksymoops -L -m /boot/System.map -K <~dagb/kernelcrash.txt 
> > > ksymoops 2.4.3 on i686 2.4.18-pre9-xfs-shawn4.  Options used
> > >      -V (default)
> > >      -K (specified)
> > >      -L (specified)
> > >      -o /lib/modules/2.4.18-pre9-xfs-shawn4/ (default)
> > >      -m /boot/System.map (specified)
> > > 
> > > No modules in ksyms, skipping objects
> > > invalid operand:        0000
> > > CPU:    0
> > > EIP:  0010:[<c0136d10>] Not tainted
> > > Using defaults from ksymoops -t elf32-i386 -a i386
> > > EFLAGS: 00010286
> > > Warning (Oops_read): Code line not seen, dumping what data is available
> > > 
> > > >>EIP; c0136d10 <grow_buffers+50/100>   <=====
> > > 
> > > Stack:  00000302  00000000  00000000  c13a91c0  00002240  c0134eb7  00000302  00000000
> > >         00000000  cffe7ed8  cfe6a000  cfe6a044  c01350aa  00000302  00000000  00000000
> > >         cffe7ed8  cfe6a000  c13a91c0  c019e96c  00000302  00000000  00000000  00000000
> > > Call Trace: [<c0134eb7>] [<c01350aa>] [<c019e96e>] [<c01a7a8d>] [<c01378a9>] [<c0137c27>] [<c010503a>] [<c010504c>] [<c01054e8>]
> > > Code: 0f 0b b9 ff ff ff ff 89 fa b6 00 90 8d 74 26 06 8b 44 24 20
> > > 
> > > Trace; c0134eb6 <getblk+26/40>
> > > Trace; c01350aa <bread+1a/c0>
> > > Trace; c019e96e <hpfs_map_sector+1e/40>
> > > Trace; c01a7a8c <hpfs_read_super+15c/730>
> > > Trace; c01378a8 <insert_super+38/40>
> > > Trace; c0137c26 <read_super+56/b0>
> > > Trace; c010503a <prepare_namespace+a/10>
> > > Trace; c010504c <init+c/110>
> > > Trace; c01054e8 <kernel_thread+28/40>
> > > Code;  c0136d10 <grow_buffers+50/100>
> > > 00000000 <_EIP>:
> > > Code;  c0136d10 <grow_buffers+50/100>
> > >    0:   0f 0b                     ud2a   
> > > Code;  c0136d12 <grow_buffers+52/100>
> > >    2:   b9 ff ff ff ff            mov    $0xffffffff,%ecx
> > > Code;  c0136d16 <grow_buffers+56/100>
> > >    7:   89 fa                     mov    %edi,%edx
> > > Code;  c0136d18 <grow_buffers+58/100>
> > >    9:   b6 00                     mov    $0x0,%dh
> > > Code;  c0136d1a <grow_buffers+5a/100>
> > >    b:   90                        nop    
> > > Code;  c0136d1c <grow_buffers+5c/100>
> > >    c:   8d 74 26 06               lea    0x6(%esi,1),%esi
> > > Code;  c0136d20 <grow_buffers+60/100>
> > >   10:   8b 44 24 20               mov    0x20(%esp,1),%eax
> > > 
> > > 
> > > 1 warning issued.  Results may not be reliable.
> > > 
> > 
> > 
> > 
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/
> 



^ permalink raw reply	[flat|nested] 6+ messages in thread

end of thread, other threads:[~2002-02-13 15:07 UTC | newest]

Thread overview: 6+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
     [not found] <20020212140036.A223@dagb>
2002-02-12 14:16 ` 2.4.18-pre9-xfs-shawn4 - hpfs bug Shawn Starr
2002-02-12 14:17   ` Pozsar Balazs
2002-02-12 14:32     ` Shawn Starr
2002-02-12 15:13     ` Alan Cox
2002-02-13 10:09   ` Dag Bakke
2002-02-13 15:10     ` Shawn Starr

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox