Re: 2.6.8-rc2 crashes

Re: 2.6.8-rc2 crashes

[Denis Vlasenko]

On Tuesday 27 July 2004 19:33, Gene Heskett wrote:
> Greetings everybody;
>
> I have now had 4 crashes while running 2.6.8-rc2, the last one
> requiring a full powerdown before the intel-8x0 could
> re-establish control over the sound.
>
> All have had an initial Opps located in prune_dcache, and were
> logged as follows:
> Jul 27 07:58:58 coyote kernel: Unable to handle kernel NULL pointer
> dereference at virtual address 00000000 Jul 27 07:58:58 coyote kernel: 
> printing eip:
> Jul 27 07:58:58 coyote kernel: c0164376
> Jul 27 07:58:58 coyote kernel: *pde = 00000000
> Jul 27 07:58:58 coyote kernel: Oops: 0002 [#1]
> Jul 27 07:58:58 coyote kernel: PREEMPT
> Jul 27 07:58:58 coyote kernel: Modules linked in: tuner tvaudio bttv
> video_buf btcx_risc eeprom snd_seq_oss snd_seq _midi_event snd_seq
> snd_pcm_oss snd_mixer_oss snd_bt87x snd_intel8x0 snd_ac97_codec snd_pcm
> snd_timer snd_page_allo c snd_mpu401_uart snd_rawmidi snd_seq_device snd
> forcedeth sg
> Jul 27 07:58:58 coyote kernel: CPU:    0
> Jul 27 07:58:58 coyote kernel: EIP:    0060:[<c0164376>]    Not tainted
> Jul 27 07:58:58 coyote kernel: EFLAGS: 00010216   (2.6.8-rc2-nf2)
> Jul 27 07:58:58 coyote kernel: EIP is at prune_dcache+0x36/0x1c0
> Jul 27 07:58:58 coyote kernel: eax: c03706f8   ebx: dbbf1090   ecx:
> dbbf5c34   edx: 00000000 Jul 27 07:58:58 coyote kernel: esi: ed1f8990  
> edi: c1989000   ebp: 0000001e   esp: c1989ef8 Jul 27 07:58:58 coyote
> kernel: ds: 007b   es: 007b   ss: 0068
> Jul 27 07:58:58 coyote kernel: Process kswapd0 (pid: 66,
> threadinfo=c1989000 task=c1978050) Jul 27 07:58:58 coyote kernel: Stack:
> ed1f8990 c1989ef8 0000002a 00000000 c1989000 f7ffea20 c016491f 0000002a Jul
> 27 07:58:58 coyote kernel:        c013ab6b 0000002a 000000d0 0001df9e
> 022f2e00 00000000 0000012a 00000000 Jul 27 07:58:58 coyote kernel:       
> c036f6e4 00000002 00000007 c036f5c0 c013bf11 00000020 000000d0 00000000 Jul
> 27 07:58:58 coyote kernel: Call Trace:
> Jul 27 07:58:58 coyote kernel:  [<c016491f>] shrink_dcache_memory+0x1f/0x50
> Jul 27 07:58:58 coyote kernel:  [<c013ab6b>] shrink_slab+0x14b/0x190
> Jul 27 07:58:58 coyote kernel:  [<c013bf11>] balance_pgdat+0x1b1/0x200
> Jul 27 07:58:58 coyote kernel:  [<c013c027>] kswapd+0xc7/0xe0
> Jul 27 07:58:58 coyote kernel:  [<c01146b0>]
> autoremove_wake_function+0x0/0x60 Jul 27 07:58:58 coyote kernel: 
> [<c0103fb2>] ret_from_fork+0x6/0x14 Jul 27 07:58:58 coyote kernel: 
> [<c01146b0>] autoremove_wake_function+0x0/0x60 Jul 27 07:58:58 coyote
> kernel:  [<c013bf60>] kswapd+0x0/0xe0
> Jul 27 07:58:58 coyote kernel:  [<c0102251>] kernel_thread_helper+0x5/0x14
> Jul 27 07:58:58 coyote kernel: Code: 89 02 89 49 04 89 09 a1 fc 06 37 c0 0f
> 18 00 90 ff 0d 04 07 Jul 27 07:58:58 coyote kernel:  <6>note: kswapd0[66]
> exited with preempt_count 1 Jul 27 07:58:58 coyote kernel:
> c_pid_flush+0x17/0x30
> Jul 27 07:58:58 coyote kernel:  [<c011779d>] release_task+0x13d/0x1e0
> Jul 27 07:58:58 coyote kernel:  [<c011923b>] wait_task_zombie+0x15b/0x1c0
> Jul 27 07:58:58 coyote kernel:  [<c0119653>] sys_wait4+0x213/0x260
> Jul 27 07:58:58 coyote kernel:  [<c0113420>] default_wake_function+0x0/0x20
> Jul 27 07:58:58 coyote kernel:  [<c0113420>] default_wake_function+0x0/0x20
> Jul 27 07:58:58 coyote kernel:  [<c01196c7>] sys_waitpid+0x27/0x2b
> Jul 27 07:58:58 coyote kernel:  [<c0104089>] sysenter_past_esp+0x52/0x71
>
> With several iterations of this appended next:
> Jul 27 07:58:58 coyote kernel: bad: scheduling while atomic!
> Jul 27 07:58:58 coyote kernel:  [<c030dc3c>] schedule+0x47c/0x490
> Jul 27 07:58:58 coyote kernel:  [<c01673e4>] __wait_on_inode+0x84/0xa0
> Jul 27 07:58:58 coyote kernel:  [<c0113420>] default_wake_function+0x0/0x20
> Jul 27 07:58:58 coyote kernel:  [<c0113420>] default_wake_function+0x0/0x20
> Jul 27 07:58:58 coyote kernel:  [<c016d7ea>]
> __writeback_single_inode+0x5a/0xc0 Jul 27 07:58:58 coyote kernel: 
> [<c016d9be>] sync_sb_inodes+0x16e/0x290 Jul 27 07:58:58 coyote kernel: 
> [<c016dc4e>] sync_inodes_sb+0x7e/0xa0 Jul 27 07:58:58 coyote kernel: 
> [<c016ddcb>] sync_inodes+0x7b/0xa0 Jul 27 07:58:58 coyote kernel: 
> [<c014e1f4>] do_sync+0x44/0x80
> Jul 27 07:58:58 coyote kernel:  [<c014e23f>] sys_sync+0xf/0x20
> Jul 27 07:58:58 coyote kernel:  [<c011667f>] panic+0xff/0x110
> Jul 27 07:58:58 coyote kernel:  [<c0118e9f>] do_exit+0x3ff/0x420
> Jul 27 07:58:58 coyote kernel:  [<c0111640>] do_page_fault+0x0/0x51b
> Jul 27 07:58:58 coyote kernel:  [<c0104968>] die+0xf8/0x100
> Jul 27 07:58:58 coyote kernel:  [<c011181b>] do_page_fault+0x1db/0x51b
> Jul 27 07:58:58 coyote kernel:  [<c0105e12>] do_IRQ+0x102/0x1a0
> Jul 27 07:58:58 coyote kernel:  [<c030da4e>] schedule+0x28e/0x490
> Jul 27 07:58:58 coyote kernel:  [<c0111640>] do_page_fault+0x0/0x51b
> Jul 27 07:58:58 coyote kernel:  [<c0104285>] error_code+0x2d/0x38
> Jul 27 07:58:58 coyote kernel:  [<c01647d6>] select_parent+0x56/0xb0
> Jul 27 07:58:58 coyote kernel:  [<c0164840>] shrink_dcache_parent+0x10/0x30
> Jul 27 07:58:58 coyote kernel:  [<c017b557>] proc_pid_flush+0x17/0x30
> Jul 27 07:58:59 coyote kernel:  [<c011779d>] release_task+0x13d/0x1e0
> Jul 27 07:58:59 coyote kernel:  [<c011923b>] wait_task_zombie+0x15b/0x1c0
> Jul 27 07:58:59 coyote kernel:  [<c0119653>] sys_wait4+0x213/0x260
> Jul 27 07:58:59 coyote kernel:  [<c0113420>] default_wake_function+0x0/0x20
> Jul 27 07:58:59 coyote kernel:  [<c0113420>] default_wake_function+0x0/0x20
> Jul 27 07:58:59 coyote kernel:  [<c01196c7>] sys_waitpid+0x27/0x2b
> Jul 27 07:58:59 coyote kernel:  [<c0104089>] sysenter_past_esp+0x52/0x71
>
> Now, someone gave me the syntax to do a dis on this, but I'm no intel
> assembly guru.  If someone could repeat that such that I could apply
> it to fs/cache.o, I'd be happy to fwd the results to whomever it might

results of

# objdump -d fs/cache.o

and

# make fs/cache.s

are needed.
-- 
vda

Re: 2.6.8-rc2 crashes

[viro]

On Tue, Jul 27, 2004 at 12:33:04PM -0400, Gene Heskett wrote:
> Greetings everybody;
> 
> I have now had 4 crashes while running 2.6.8-rc2, the last one
> requiring a full powerdown before the intel-8x0 could
> re-establish control over the sound.
> 
> All have had an initial Opps located in prune_dcache, and were
> logged as follows:
> Jul 27 07:58:58 coyote kernel: Unable to handle kernel NULL pointer dereference at virtual address 00000000

... which means that dentry_unused list got corrupted, which doesn't really
help.  Could you try to narrow it down to 2.6.8-rc1-bk<day>?

2.6.8-rc2 crashes

[Gene Heskett]

Greetings everybody;

I have now had 4 crashes while running 2.6.8-rc2, the last one
requiring a full powerdown before the intel-8x0 could
re-establish control over the sound.

All have had an initial Opps located in prune_dcache, and were
logged as follows:
Jul 27 07:58:58 coyote kernel: Unable to handle kernel NULL pointer dereference at virtual address 00000000
Jul 27 07:58:58 coyote kernel:  printing eip:
Jul 27 07:58:58 coyote kernel: c0164376
Jul 27 07:58:58 coyote kernel: *pde = 00000000
Jul 27 07:58:58 coyote kernel: Oops: 0002 [#1]
Jul 27 07:58:58 coyote kernel: PREEMPT
Jul 27 07:58:58 coyote kernel: Modules linked in: tuner tvaudio bttv video_buf btcx_risc eeprom snd_seq_oss snd_seq
_midi_event snd_seq snd_pcm_oss snd_mixer_oss snd_bt87x snd_intel8x0 snd_ac97_codec snd_pcm snd_timer snd_page_allo
c snd_mpu401_uart snd_rawmidi snd_seq_device snd forcedeth sg
Jul 27 07:58:58 coyote kernel: CPU:    0
Jul 27 07:58:58 coyote kernel: EIP:    0060:[<c0164376>]    Not tainted
Jul 27 07:58:58 coyote kernel: EFLAGS: 00010216   (2.6.8-rc2-nf2)
Jul 27 07:58:58 coyote kernel: EIP is at prune_dcache+0x36/0x1c0
Jul 27 07:58:58 coyote kernel: eax: c03706f8   ebx: dbbf1090   ecx: dbbf5c34   edx: 00000000
Jul 27 07:58:58 coyote kernel: esi: ed1f8990   edi: c1989000   ebp: 0000001e   esp: c1989ef8
Jul 27 07:58:58 coyote kernel: ds: 007b   es: 007b   ss: 0068
Jul 27 07:58:58 coyote kernel: Process kswapd0 (pid: 66, threadinfo=c1989000 task=c1978050)
Jul 27 07:58:58 coyote kernel: Stack: ed1f8990 c1989ef8 0000002a 00000000 c1989000 f7ffea20 c016491f 0000002a
Jul 27 07:58:58 coyote kernel:        c013ab6b 0000002a 000000d0 0001df9e 022f2e00 00000000 0000012a 00000000
Jul 27 07:58:58 coyote kernel:        c036f6e4 00000002 00000007 c036f5c0 c013bf11 00000020 000000d0 00000000
Jul 27 07:58:58 coyote kernel: Call Trace:
Jul 27 07:58:58 coyote kernel:  [<c016491f>] shrink_dcache_memory+0x1f/0x50
Jul 27 07:58:58 coyote kernel:  [<c013ab6b>] shrink_slab+0x14b/0x190
Jul 27 07:58:58 coyote kernel:  [<c013bf11>] balance_pgdat+0x1b1/0x200
Jul 27 07:58:58 coyote kernel:  [<c013c027>] kswapd+0xc7/0xe0
Jul 27 07:58:58 coyote kernel:  [<c01146b0>] autoremove_wake_function+0x0/0x60
Jul 27 07:58:58 coyote kernel:  [<c0103fb2>] ret_from_fork+0x6/0x14
Jul 27 07:58:58 coyote kernel:  [<c01146b0>] autoremove_wake_function+0x0/0x60
Jul 27 07:58:58 coyote kernel:  [<c013bf60>] kswapd+0x0/0xe0
Jul 27 07:58:58 coyote kernel:  [<c0102251>] kernel_thread_helper+0x5/0x14
Jul 27 07:58:58 coyote kernel: Code: 89 02 89 49 04 89 09 a1 fc 06 37 c0 0f 18 00 90 ff 0d 04 07
Jul 27 07:58:58 coyote kernel:  <6>note: kswapd0[66] exited with preempt_count 1
Jul 27 07:58:58 coyote kernel: c_pid_flush+0x17/0x30
Jul 27 07:58:58 coyote kernel:  [<c011779d>] release_task+0x13d/0x1e0
Jul 27 07:58:58 coyote kernel:  [<c011923b>] wait_task_zombie+0x15b/0x1c0
Jul 27 07:58:58 coyote kernel:  [<c0119653>] sys_wait4+0x213/0x260
Jul 27 07:58:58 coyote kernel:  [<c0113420>] default_wake_function+0x0/0x20
Jul 27 07:58:58 coyote kernel:  [<c0113420>] default_wake_function+0x0/0x20
Jul 27 07:58:58 coyote kernel:  [<c01196c7>] sys_waitpid+0x27/0x2b
Jul 27 07:58:58 coyote kernel:  [<c0104089>] sysenter_past_esp+0x52/0x71

With several iterations of this appended next:
Jul 27 07:58:58 coyote kernel: bad: scheduling while atomic!
Jul 27 07:58:58 coyote kernel:  [<c030dc3c>] schedule+0x47c/0x490
Jul 27 07:58:58 coyote kernel:  [<c01673e4>] __wait_on_inode+0x84/0xa0
Jul 27 07:58:58 coyote kernel:  [<c0113420>] default_wake_function+0x0/0x20
Jul 27 07:58:58 coyote kernel:  [<c0113420>] default_wake_function+0x0/0x20
Jul 27 07:58:58 coyote kernel:  [<c016d7ea>] __writeback_single_inode+0x5a/0xc0
Jul 27 07:58:58 coyote kernel:  [<c016d9be>] sync_sb_inodes+0x16e/0x290
Jul 27 07:58:58 coyote kernel:  [<c016dc4e>] sync_inodes_sb+0x7e/0xa0
Jul 27 07:58:58 coyote kernel:  [<c016ddcb>] sync_inodes+0x7b/0xa0
Jul 27 07:58:58 coyote kernel:  [<c014e1f4>] do_sync+0x44/0x80
Jul 27 07:58:58 coyote kernel:  [<c014e23f>] sys_sync+0xf/0x20
Jul 27 07:58:58 coyote kernel:  [<c011667f>] panic+0xff/0x110
Jul 27 07:58:58 coyote kernel:  [<c0118e9f>] do_exit+0x3ff/0x420
Jul 27 07:58:58 coyote kernel:  [<c0111640>] do_page_fault+0x0/0x51b
Jul 27 07:58:58 coyote kernel:  [<c0104968>] die+0xf8/0x100
Jul 27 07:58:58 coyote kernel:  [<c011181b>] do_page_fault+0x1db/0x51b
Jul 27 07:58:58 coyote kernel:  [<c0105e12>] do_IRQ+0x102/0x1a0
Jul 27 07:58:58 coyote kernel:  [<c030da4e>] schedule+0x28e/0x490
Jul 27 07:58:58 coyote kernel:  [<c0111640>] do_page_fault+0x0/0x51b
Jul 27 07:58:58 coyote kernel:  [<c0104285>] error_code+0x2d/0x38
Jul 27 07:58:58 coyote kernel:  [<c01647d6>] select_parent+0x56/0xb0
Jul 27 07:58:58 coyote kernel:  [<c0164840>] shrink_dcache_parent+0x10/0x30
Jul 27 07:58:58 coyote kernel:  [<c017b557>] proc_pid_flush+0x17/0x30
Jul 27 07:58:59 coyote kernel:  [<c011779d>] release_task+0x13d/0x1e0
Jul 27 07:58:59 coyote kernel:  [<c011923b>] wait_task_zombie+0x15b/0x1c0
Jul 27 07:58:59 coyote kernel:  [<c0119653>] sys_wait4+0x213/0x260
Jul 27 07:58:59 coyote kernel:  [<c0113420>] default_wake_function+0x0/0x20
Jul 27 07:58:59 coyote kernel:  [<c0113420>] default_wake_function+0x0/0x20
Jul 27 07:58:59 coyote kernel:  [<c01196c7>] sys_waitpid+0x27/0x2b
Jul 27 07:58:59 coyote kernel:  [<c0104089>] sysenter_past_esp+0x52/0x71

Now, someone gave me the syntax to do a dis on this, but I'm no intel
assembly guru.  If someone could repeat that such that I could apply
it to fs/cache.o, I'd be happy to fwd the results to whomever it might
apply to.

I'd revert to rc1, but I'd have to figure out a way to use this .config
in that tree, I've changed motherboards and this is the only version
I've brought into compliance with this new hardware.

-- 
Cheers, Gene
There are 4 boxes to be used in defense of liberty. 
Soap, ballot, jury, and ammo.
Please use in that order, starting now.  -Ed Howdershelt, Author
Additions to this message made by Gene Heskett are Copyright 2004, 
Maurice E. Heskett, all rights reserved.

Re: 2.6.8-rc2 crashes

[Randy.Dunlap]

On Tue, 27 Jul 2004 13:02:41 -0400 Gene Heskett wrote:

| On Tuesday 27 July 2004 10:29, viro@parcelfarce.linux.theplanet.co.uk 
| wrote:
| >On Tue, Jul 27, 2004 at 12:33:04PM -0400, Gene Heskett wrote:
| >> Greetings everybody;
| >>
| >> I have now had 4 crashes while running 2.6.8-rc2, the last one
| >> requiring a full powerdown before the intel-8x0 could
| >> re-establish control over the sound.
| >>
| >> All have had an initial Opps located in prune_dcache, and were
| >> logged as follows:
| >> Jul 27 07:58:58 coyote kernel: Unable to handle kernel NULL
| >> pointer dereference at virtual address 00000000
| >
| >... which means that dentry_unused list got corrupted, which doesn't
| > really help.  Could you try to narrow it down to 2.6.8-rc1-bk<day>?
| 
| I don't have bitkeeper installed.  I get my patches from kernel.org, 
| either from the main Linus tree, or Andrews akpm tree. Is there 
| someplace where I can dl a patchkit that leads up to rc1 by the 
| "daily" snapshot?  Or should I just get the 'broken out' patch after 
| I verify that it also occurs with rc1 of course.  That I haven't 
| done, mainly because rc2 has a lot of usb bugfixes and my mouse 
| hasn't died all by itself on rc2 like it was for at least 2 dozen 
| patches before rc2.  IIRC it did a time or 2 on rc1.

In case you need daily bk snapshots, they are here:
  http://www.kernel.org/pub/linux/kernel/v2.6/snapshots/


| It takes a < 1 day for this to occur usually, but seems to occur after 
| a long session of doing something else that fails. (or maybe causes 
| the fail, of a make install in konstruct/meta/kde)  Thats running 
| now, someplace in kdegraphics-3.2.92 from the looks of it.
| 
| I'l go see if I can get the patch in broken out form.
| 
| Mmmm, no, I guess I won't.  I've just upgraded this machine to FC2, 
| and gftp is one of the many things broken by this, an strace exit of 
| trying to run gftp, most recent release:
| 
| writev(2, [{"/usr/bin/gftp-gtk", 17}, {": ", 2}, {"error while loading 
| shared libra"..., 36}, {": ", 2}, {"/usr/lib/libpangoxft-1.0.so.0", 
| 29}, {": ", 2}, {"undefined symbol: pango_fc_font_"..., 44}, {"", 0}, 
| {"", 0}, {"\n", 1}], 10/usr/bin/gftp-gtk: error while loading shared 
| libraries: /usr/lib/libpangoxft-1.0.so.0: undefined symbol: 
| pango_fc_font_map_get_type
| ) = 133
| exit_group(127)
| 
| And libpangoxft is this:
| [root@coyote root]# locate libpangoxft-1.0.so
| /usr/lib/libpangoxft-1.0.so.0.399.1
| /usr/lib/libpangoxft-1.0.so
| /usr/lib/libpangoxft-1.0.so.0
| 
| with the latter 2 links to the first one.
| 
| So I'd love to find this and fix it.  FC2 broke way more than it fixed 
| on this machine.  And yum update did run just fine once I got some 
| similar problems with libxml2 sorted.  Sorry.  Hints on this also 
| gratefully accepted of course.
| 
| In the meantime I'll cp my .config back to rc1 and see it it happens 
| with rc1.


--
~Randy

Re: 2.6.8-rc2 crashes

[Gene Heskett]

On Tuesday 27 July 2004 10:29, viro@parcelfarce.linux.theplanet.co.uk 
wrote:
>On Tue, Jul 27, 2004 at 12:33:04PM -0400, Gene Heskett wrote:
>> Greetings everybody;
>>
>> I have now had 4 crashes while running 2.6.8-rc2, the last one
>> requiring a full powerdown before the intel-8x0 could
>> re-establish control over the sound.
>>
>> All have had an initial Opps located in prune_dcache, and were
>> logged as follows:
>> Jul 27 07:58:58 coyote kernel: Unable to handle kernel NULL
>> pointer dereference at virtual address 00000000
>
>... which means that dentry_unused list got corrupted, which doesn't
> really help.  Could you try to narrow it down to 2.6.8-rc1-bk<day>?

I don't have bitkeeper installed.  I get my patches from kernel.org, 
either from the main Linus tree, or Andrews akpm tree. Is there 
someplace where I can dl a patchkit that leads up to rc1 by the 
"daily" snapshot?  Or should I just get the 'broken out' patch after 
I verify that it also occurs with rc1 of course.  That I haven't 
done, mainly because rc2 has a lot of usb bugfixes and my mouse 
hasn't died all by itself on rc2 like it was for at least 2 dozen 
patches before rc2.  IIRC it did a time or 2 on rc1.

It takes a < 1 day for this to occur usually, but seems to occur after 
a long session of doing something else that fails. (or maybe causes 
the fail, of a make install in konstruct/meta/kde)  Thats running 
now, someplace in kdegraphics-3.2.92 from the looks of it.

I'l go see if I can get the patch in broken out form.

Mmmm, no, I guess I won't.  I've just upgraded this machine to FC2, 
and gftp is one of the many things broken by this, an strace exit of 
trying to run gftp, most recent release:

writev(2, [{"/usr/bin/gftp-gtk", 17}, {": ", 2}, {"error while loading 
shared libra"..., 36}, {": ", 2}, {"/usr/lib/libpangoxft-1.0.so.0", 
29}, {": ", 2}, {"undefined symbol: pango_fc_font_"..., 44}, {"", 0}, 
{"", 0}, {"\n", 1}], 10/usr/bin/gftp-gtk: error while loading shared 
libraries: /usr/lib/libpangoxft-1.0.so.0: undefined symbol: 
pango_fc_font_map_get_type
) = 133
exit_group(127)

And libpangoxft is this:
[root@coyote root]# locate libpangoxft-1.0.so
/usr/lib/libpangoxft-1.0.so.0.399.1
/usr/lib/libpangoxft-1.0.so
/usr/lib/libpangoxft-1.0.so.0

with the latter 2 links to the first one.

So I'd love to find this and fix it.  FC2 broke way more than it fixed 
on this machine.  And yum update did run just fine once I got some 
similar problems with libxml2 sorted.  Sorry.  Hints on this also 
gratefully accepted of course.

In the meantime I'll cp my .config back to rc1 and see it it happens 
with rc1.

-- 
Cheers, Gene
There are 4 boxes to be used in defense of liberty. 
Soap, ballot, jury, and ammo.
Please use in that order, starting now.  -Ed Howdershelt, Author
Additions to this message made by Gene Heskett are Copyright 2004, 
Maurice E. Heskett, all rights reserved.

Re: 2.6.8-rc2 crashes

[Gene Heskett]

On Tuesday 27 July 2004 10:29, viro@parcelfarce.linux.theplanet.co.uk wrote:
>On Tue, Jul 27, 2004 at 12:33:04PM -0400, Gene Heskett wrote:
>> Greetings everybody;
>>
>> I have now had 4 crashes while running 2.6.8-rc2, the last one
>> requiring a full powerdown before the intel-8x0 could
>> re-establish control over the sound.
>>
>> All have had an initial Opps located in prune_dcache, and were
>> logged as follows:
>> Jul 27 07:58:58 coyote kernel: Unable to handle kernel NULL
>> pointer dereference at virtual address 00000000
>
>... which means that dentry_unused list got corrupted, which doesn't
> really help.  Could you try to narrow it down to 2.6.8-rc1-bk<day>?

I got the bright idea of doing some cmp's on that code module, and 
its identical all the way back to 2.6.7-mm1, (I have them all) but 
differs at 2.6.7:

[root@coyote linux-2.6.8-rc1]# cmp fs/dcache.c ../linux-2.6.7-mm7/fs/dcache.c
[root@coyote linux-2.6.8-rc1]# cmp fs/dcache.c ../linux-2.6.7-mm6/fs/dcache.c
[root@coyote linux-2.6.8-rc1]# cmp fs/dcache.c ../linux-2.6.7-mm5/fs/dcache.c
[root@coyote linux-2.6.8-rc1]# cmp fs/dcache.c ../linux-2.6.7-mm4/fs/dcache.c
[root@coyote linux-2.6.8-rc1]# cmp fs/dcache.c ../linux-2.6.7-mm3/fs/dcache.c
[root@coyote linux-2.6.8-rc1]# cmp fs/dcache.c ../linux-2.6.7-mm2/fs/dcache.c
[root@coyote linux-2.6.8-rc1]# cmp fs/dcache.c ../linux-2.6.7-mm1/fs/dcache.c
[root@coyote linux-2.6.8-rc1]# cmp fs/dcache.c ../linux-2.6.7/fs/dcache.c
fs/dcache.c ../linux-2.6.7/fs/dcache.c differ: byte 768, line 33

Or am I barking up the wrong tree?

-- 
Cheers, Gene
There are 4 boxes to be used in defense of liberty. 
Soap, ballot, jury, and ammo.
Please use in that order, starting now.  -Ed Howdershelt, Author
Additions to this message made by Gene Heskett are Copyright 2004, 
Maurice E. Heskett, all rights reserved.

Re: 2.6.8-rc2 crashes

[Gene Heskett]

On Tuesday 27 July 2004 10:29, viro@parcelfarce.linux.theplanet.co.uk 
wrote:
>On Tue, Jul 27, 2004 at 12:33:04PM -0400, Gene Heskett wrote:
>> Greetings everybody;
>>
>> I have now had 4 crashes while running 2.6.8-rc2, the last one
>> requiring a full powerdown before the intel-8x0 could
>> re-establish control over the sound.
>>
>> All have had an initial Opps located in prune_dcache, and were
>> logged as follows:
>> Jul 27 07:58:58 coyote kernel: Unable to handle kernel NULL
>> pointer dereference at virtual address 00000000
>
>... which means that dentry_unused list got corrupted, which doesn't
> really help.  Could you try to narrow it down to 2.6.8-rc1-bk<day>?

And something else that doesn't help, I just found that 2.6.8-rc1 
doesn't have the reverse engineered nforce2 support, so a remake for 
this mobo probably won't fly past the decompression stage.  But 
2.6.8-rc1-mm1 does have it, but under a different xconfig entry.  Its 
building now.

-- 
Cheers, Gene
There are 4 boxes to be used in defense of liberty. 
Soap, ballot, jury, and ammo.
Please use in that order, starting now.  -Ed Howdershelt, Author
Additions to this message made by Gene Heskett are Copyright 2004, 
Maurice E. Heskett, all rights reserved.

Re: 2.6.8-rc2 crashes

[Randy.Dunlap]

On Tue, 27 Jul 2004 13:43:43 -0400 Gene Heskett wrote:

| On Tuesday 27 July 2004 12:51, Randy.Dunlap wrote:
| >On Tue, 27 Jul 2004 13:02:41 -0400 Gene Heskett wrote:
| >| On Tuesday 27 July 2004 10:29,
| >| viro@parcelfarce.linux.theplanet.co.uk
| >|
| >| wrote:
| >| >On Tue, Jul 27, 2004 at 12:33:04PM -0400, Gene Heskett wrote:
| >| >> Greetings everybody;
| >| >>
| >| >> I have now had 4 crashes while running 2.6.8-rc2, the last one
| >| >> requiring a full powerdown before the intel-8x0 could
| >| >> re-establish control over the sound.
| >| >>
| >| >> All have had an initial Opps located in prune_dcache, and were
| >| >> logged as follows:
| >| >> Jul 27 07:58:58 coyote kernel: Unable to handle kernel NULL
| >| >> pointer dereference at virtual address 00000000
| >| >
| >| >... which means that dentry_unused list got corrupted, which
| >| > doesn't really help.  Could you try to narrow it down to
| >| > 2.6.8-rc1-bk<day>?
| >|
| >| I don't have bitkeeper installed.  I get my patches from
| >| kernel.org, either from the main Linus tree, or Andrews akpm tree.
| >| Is there someplace where I can dl a patchkit that leads up to rc1
| >| by the "daily" snapshot?  Or should I just get the 'broken out'
| >| patch after I verify that it also occurs with rc1 of course.  That
| >| I haven't done, mainly because rc2 has a lot of usb bugfixes and
| >| my mouse hasn't died all by itself on rc2 like it was for at least
| >| 2 dozen patches before rc2.  IIRC it did a time or 2 on rc1.
| >
| >In case you need daily bk snapshots, they are here:
| >  http://www.kernel.org/pub/linux/kernel/v2.6/snapshots/
| 
| Thanks Randy, got all 6 of them.
| 
| >| It takes a < 1 day for this to occur usually, but seems to occur
| >| after a long session of doing something else that fails. (or maybe
| >| causes the fail, of a make install in konstruct/meta/kde)  Thats
| >| running now, someplace in kdegraphics-3.2.92 from the looks of it.
| 
| I take it that I should apply these to a 2.6.7 tarballs tree in this 
| order:
| 1. 2.6.8-rc1
>>>> 2.6.8-rc2 <<<<<

| 2. each of these 'rc2-bk' patches by the day and then run each for a 
| couple days, or should I start in the middle, say the 3rd one and 
| work forward or backwards from there depending on the results?

I'd suggest beginning with -bk3 and doing a binary search.

| Your (and Viro's) call.  I'd imagine you would want to run this to 
| earth as quick as we can.
| 
| Are these patches cumulative?  I presume they are as they grow by the 
| day.

Sorry, I should have mentioned that.  Yes, they are cumulative.

--
~Randy

Re: 2.6.8-rc2 crashes

[Gene Heskett]

On Tuesday 27 July 2004 12:51, Randy.Dunlap wrote:
>On Tue, 27 Jul 2004 13:02:41 -0400 Gene Heskett wrote:
>| On Tuesday 27 July 2004 10:29,
>| viro@parcelfarce.linux.theplanet.co.uk
>|
>| wrote:
>| >On Tue, Jul 27, 2004 at 12:33:04PM -0400, Gene Heskett wrote:
>| >> Greetings everybody;
>| >>
>| >> I have now had 4 crashes while running 2.6.8-rc2, the last one
>| >> requiring a full powerdown before the intel-8x0 could
>| >> re-establish control over the sound.
>| >>
>| >> All have had an initial Opps located in prune_dcache, and were
>| >> logged as follows:
>| >> Jul 27 07:58:58 coyote kernel: Unable to handle kernel NULL
>| >> pointer dereference at virtual address 00000000
>| >
>| >... which means that dentry_unused list got corrupted, which
>| > doesn't really help.  Could you try to narrow it down to
>| > 2.6.8-rc1-bk<day>?
>|
>| I don't have bitkeeper installed.  I get my patches from
>| kernel.org, either from the main Linus tree, or Andrews akpm tree.
>| Is there someplace where I can dl a patchkit that leads up to rc1
>| by the "daily" snapshot?  Or should I just get the 'broken out'
>| patch after I verify that it also occurs with rc1 of course.  That
>| I haven't done, mainly because rc2 has a lot of usb bugfixes and
>| my mouse hasn't died all by itself on rc2 like it was for at least
>| 2 dozen patches before rc2.  IIRC it did a time or 2 on rc1.
>
>In case you need daily bk snapshots, they are here:
>  http://www.kernel.org/pub/linux/kernel/v2.6/snapshots/

Thanks Randy, got all 6 of them.

>| It takes a < 1 day for this to occur usually, but seems to occur
>| after a long session of doing something else that fails. (or maybe
>| causes the fail, of a make install in konstruct/meta/kde)  Thats
>| running now, someplace in kdegraphics-3.2.92 from the looks of it.

I take it that I should apply these to a 2.6.7 tarballs tree in this 
order:
1. 2.6.8-rc1
2. each of these 'rc2-bk' patches by the day and then run each for a 
couple days, or should I start in the middle, say the 3rd one and 
work forward or backwards from there depending on the results?

Your (and Viro's) call.  I'd imagine you would want to run this to 
earth as quick as we can.

Are these patches cumulative?  I presume they are as they grow by the 
day.

-- 
Cheers, Gene
There are 4 boxes to be used in defense of liberty. 
Soap, ballot, jury, and ammo.
Please use in that order, starting now.  -Ed Howdershelt, Author
Additions to this message made by Gene Heskett are Copyright 2004, 
Maurice E. Heskett, all rights reserved.

Re: 2.6.8-rc2 crashes

[Randy.Dunlap]

On Tue, 27 Jul 2004 14:02:59 -0400 Gene Heskett wrote:

| On Tuesday 27 July 2004 13:32, Randy.Dunlap wrote:
| [...]
| Gene Heskett wrote:
| >| I take it that I should apply these to a 2.6.7 tarballs tree in
| >| this order:
| >| 1. 2.6.8-rc1
| >|
| >>>>> 2.6.8-rc2 <<<<<
| 2.6.8-rc2?  These patches I got will need to be reverted then?

Nope, my bad.  I didn't read $Subject... please continue....

| >| 2. each of these 'rc2-bk' patches by the day and then run each for
| >| a couple days, or should I start in the middle, say the 3rd one
| >| and work forward or backwards from there depending on the results?
| >
| >I'd suggest beginning with -bk3 and doing a binary search.
| 
| Ok, as soon as the kde build exits (and it will, bet the whole farm on 
| it)  I'll give it a try.
| 
| >| Your (and Viro's) call.  I'd imagine you would want to run this to
| >| earth as quick as we can.
| >|
| >| Are these patches cumulative?  I presume they are as they grow by
| >| the day.
| >
| >Sorry, I should have mentioned that.  Yes, they are cumulative.
| 
| Well, it was a pretty obvious conclusion :)


--
~Randy

Re: 2.6.8-rc2 crashes

[Gene Heskett]

On Tuesday 27 July 2004 13:32, Randy.Dunlap wrote:
[...]
Gene Heskett wrote:
>| I take it that I should apply these to a 2.6.7 tarballs tree in
>| this order:
>| 1. 2.6.8-rc1
>|
>>>>> 2.6.8-rc2 <<<<<
2.6.8-rc2?  These patches I got will need to be reverted then?
>|
>| 2. each of these 'rc2-bk' patches by the day and then run each for
>| a couple days, or should I start in the middle, say the 3rd one
>| and work forward or backwards from there depending on the results?
>
>I'd suggest beginning with -bk3 and doing a binary search.

Ok, as soon as the kde build exits (and it will, bet the whole farm on 
it)  I'll give it a try.

>| Your (and Viro's) call.  I'd imagine you would want to run this to
>| earth as quick as we can.
>|
>| Are these patches cumulative?  I presume they are as they grow by
>| the day.
>
>Sorry, I should have mentioned that.  Yes, they are cumulative.

Well, it was a pretty obvious conclusion :)

-- 
Cheers, Gene
There are 4 boxes to be used in defense of liberty. 
Soap, ballot, jury, and ammo.
Please use in that order, starting now.  -Ed Howdershelt, Author
Additions to this message made by Gene Heskett are Copyright 2004, 
Maurice E. Heskett, all rights reserved.

Re: 2.6.8-rc2 crashes

[Gene Heskett]

On Tuesday 27 July 2004 13:50, Randy.Dunlap wrote:
>On Tue, 27 Jul 2004 14:02:59 -0400 Gene Heskett wrote:
>| On Tuesday 27 July 2004 13:32, Randy.Dunlap wrote:
>| [...]
>|
>| Gene Heskett wrote:
>| >| I take it that I should apply these to a 2.6.7 tarballs tree in
>| >| this order:
>| >| 1. 2.6.8-rc1
>| >|
>| >>>>> 2.6.8-rc2 <<<<<
>|
>| 2.6.8-rc2?  These patches I got will need to be reverted then?
>
>Nope, my bad.  I didn't read $Subject... please continue....

Oh, mmm, well, for some unexplainable reason it did apply the patches 
on top of rc2 without any fussing, and it is building, ahh scuse me, 
is built.  This athlon 2800 is awesome, my makeit script runs in a 
bit over 6 minutes.  And unrelated of course, by now, the kde build 
has puked all over itself, it now doesn't like the glibc installed by 
FC2.  Go figure...

Anyway, now I'll go make it again using the 2.6.8-rc1 main patch & 
throw this one away.  Not that big a deal when there a 120Gb drive to 
play in.


>| >| 2. each of these 'rc2-bk' patches by the day and then run each
>| >| for a couple days, or should I start in the middle, say the 3rd
>| >| one and work forward or backwards from there depending on the
>| >| results?
>| >
>| >I'd suggest beginning with -bk3 and doing a binary search.
>|
>| Ok, as soon as the kde build exits (and it will, bet the whole
>| farm on it)  I'll give it a try.
>|
>| >| Your (and Viro's) call.  I'd imagine you would want to run this
>| >| to earth as quick as we can.
>| >|
>| >| Are these patches cumulative?  I presume they are as they grow
>| >| by the day.
>| >
>| >Sorry, I should have mentioned that.  Yes, they are cumulative.
>|
>| Well, it was a pretty obvious conclusion :)
>
>--
>~Randy

-- 
Cheers, Gene
There are 4 boxes to be used in defense of liberty. 
Soap, ballot, jury, and ammo.
Please use in that order, starting now.  -Ed Howdershelt, Author
Additions to this message made by Gene Heskett are Copyright 2004, 
Maurice E. Heskett, all rights reserved.

Re: 2.6.8-rc2 crashes

[Gene Heskett]

On Tuesday 27 July 2004 13:50, Randy.Dunlap wrote:
>On Tue, 27 Jul 2004 14:02:59 -0400 Gene Heskett wrote:
>| On Tuesday 27 July 2004 13:32, Randy.Dunlap wrote:
>| [...]
>|
>| Gene Heskett wrote:
>| >| I take it that I should apply these to a 2.6.7 tarballs tree in
>| >| this order:
>| >| 1. 2.6.8-rc1
>| >|
>| >>>>> 2.6.8-rc2 <<<<<
>|
>| 2.6.8-rc2?  These patches I got will need to be reverted then?
>
>Nope, my bad.  I didn't read $Subject... please continue....
>
Humm, I just tried to build it using 2.6.8-rc1 as the main patch to 
2.6.7, but then the 2.6.8-rc2-bk3 patch will not apply as the second 
patch...  I'll go back and redo the rc2 patch first.  Or do I really 
have something totally fubared?

-- 
Cheers, Gene
There are 4 boxes to be used in defense of liberty. 
Soap, ballot, jury, and ammo.
Please use in that order, starting now.  -Ed Howdershelt, Author
Additions to this message made by Gene Heskett are Copyright 2004, 
Maurice E. Heskett, all rights reserved.

Re: 2.6.8-rc2 crashes

[viro]

On Tue, Jul 27, 2004 at 02:42:33PM -0400, Gene Heskett wrote:
> Humm, I just tried to build it using 2.6.8-rc1 as the main patch to 
> 2.6.7, but then the 2.6.8-rc2-bk3 patch will not apply as the second 
> patch...  I'll go back and redo the rc2 patch first.  Or do I really 
> have something totally fubared?

It goes like that:
2.6.7
2.6.7 + 7-bk<n>
2.6.7 + 8-rc1
2.6.7 + 8-rc1 + 8-rc1-bk<n>
2.6.7 + 8-rc2
2.6.7 + 8-rc2 + 8-rc2-bk<n>
...

Since rc1 works and rc2 doesnt, you want 
	linux-2.6.7.tar.bz2 +
	testing/patch-2.6.8-rc1.bz2 +
	snapshots/old/patch-2.6.8-rc1-bk<n>.bz2
(all under /pub/linux/kernel/v2.6 on ftp.kernel.org and mirrors)

Re: 2.6.8-rc2 crashes

[viro]

On Tue, Jul 27, 2004 at 01:15:22PM -0400, Gene Heskett wrote:
> On Tuesday 27 July 2004 10:29, viro@parcelfarce.linux.theplanet.co.uk wrote:
> >On Tue, Jul 27, 2004 at 12:33:04PM -0400, Gene Heskett wrote:
> >> Greetings everybody;
> >>
> >> I have now had 4 crashes while running 2.6.8-rc2, the last one
> >> requiring a full powerdown before the intel-8x0 could
> >> re-establish control over the sound.
> >>
> >> All have had an initial Opps located in prune_dcache, and were
> >> logged as follows:
> >> Jul 27 07:58:58 coyote kernel: Unable to handle kernel NULL
> >> pointer dereference at virtual address 00000000
> >
> >... which means that dentry_unused list got corrupted, which doesn't
> > really help.  Could you try to narrow it down to 2.6.8-rc1-bk<day>?
> 
> I got the bright idea of doing some cmp's on that code module, and 
> its identical all the way back to 2.6.7-mm1, (I have them all) but 
> differs at 2.6.7:

Doesn't help - all we know is that at some point in a cyclic list we'd
got NULL instead of a pointer to the next list element.  Could've happened
for any number of reasons.

What filesystems do you have on that box, BTW?

Re: 2.6.8-rc2 crashes

[Matt Mackall]

On Tue, Jul 27, 2004 at 02:02:59PM -0400, Gene Heskett wrote:
> On Tuesday 27 July 2004 13:32, Randy.Dunlap wrote:
> [...]
> Gene Heskett wrote:
> >| I take it that I should apply these to a 2.6.7 tarballs tree in
> >| this order:
> >| 1. 2.6.8-rc1
> >|
> >>>>> 2.6.8-rc2 <<<<<
> 2.6.8-rc2?  These patches I got will need to be reverted then?

You might find my ketchup script handy for this purpose:

http://selenic.com/ketchup/

You just tell it what version you want and it does all the work.

-- 
Mathematics is the supreme nostalgia of our time.

Re: 2.6.8-rc2 crashes

[Gene Heskett]

On Tuesday 27 July 2004 15:23, viro@parcelfarce.linux.theplanet.co.uk 
wrote:
>On Tue, Jul 27, 2004 at 02:42:33PM -0400, Gene Heskett wrote:
>> Humm, I just tried to build it using 2.6.8-rc1 as the main patch
>> to 2.6.7, but then the 2.6.8-rc2-bk3 patch will not apply as the
>> second patch...  I'll go back and redo the rc2 patch first.  Or do
>> I really have something totally fubared?
>
>It goes like that:
>2.6.7
>2.6.7 + 7-bk<n>
>2.6.7 + 8-rc1
>2.6.7 + 8-rc1 + 8-rc1-bk<n>
>2.6.7 + 8-rc2
>2.6.7 + 8-rc2 + 8-rc2-bk<n>
>...
>
>Since rc1 works and rc2 doesnt, you want

I won't go so far as to say if rc1 worked or not, 2 things were going 
on then, first being that rc2 wasn't that far behind rc1, and 2, I'm 
not sure if the nvidia driver in rc1 can do my hardware as I've 
replaced this mobo, all at the samne time.  mobo is now a Biostar 
M7NCD-Pro.  I had some crashes while running rc1, BUT, I also had a 
bad mobo, something in the buss system being overstressed by a 
failing nvidia gforce2 vidio card, which in turn was leading to 
random memory errors.  That wasn't conducive to my pointing any 
fingers at the kernel until I had fixed the hardware probs with new 
hardware.  In any event, I'm now running 2.6.8-rc2-bk3-nf2, the nf2 
to remind me that it no longer has a via ide chipset in it.  And a 
tail -f running on the log in another window :)

I've been outside, making split rail fencing rails the last 3 hours 
while this was running, sweaty stuff.  Then I have to go see a 
genuinely Grand Old Man I've known for 20 years, and who passed this 
weekend, so the evening is half spent before it even gets dark here.  
It'll be beer thirty before I know it after that.  Yes, I'm an 
alcoholic, a 2 beers a night one.  :-)

Thanks for the help, maybe this will tell us something in a day or so.

>	linux-2.6.7.tar.bz2 +
>	testing/patch-2.6.8-rc1.bz2 +
>	snapshots/old/patch-2.6.8-rc1-bk<n>.bz2
>(all under /pub/linux/kernel/v2.6 on ftp.kernel.org and mirrors)

-- 
Cheers Viro, Gene
There are 4 boxes to be used in defense of liberty. 
Soap, ballot, jury, and ammo.
Please use in that order, starting now.  -Ed Howdershelt, Author
Additions to this message made by Gene Heskett are Copyright 2004, 
Maurice E. Heskett, all rights reserved.

Re: 2.6.8-rc2 crashes

[Gene Heskett]

On Tuesday 27 July 2004 17:40, Matt Mackall wrote:
>On Tue, Jul 27, 2004 at 02:02:59PM -0400, Gene Heskett wrote:
>> On Tuesday 27 July 2004 13:32, Randy.Dunlap wrote:
>> [...]
>>
>> Gene Heskett wrote:
>> >| I take it that I should apply these to a 2.6.7 tarballs tree in
>> >| this order:
>> >| 1. 2.6.8-rc1
>> >|
>> >>>>> 2.6.8-rc2 <<<<<
>>
>> 2.6.8-rc2?  These patches I got will need to be reverted then?
>
>You might find my ketchup script handy for this purpose:
>
>http://selenic.com/ketchup/
>
Its no doubt fancier than mine, but I'm an old dog, and plumb used to 
my pair of scripts, one to make the directory, and one to do the make 
once its configured...

But I'll take a look later, thanks for the offer.

>You just tell it what version you want and it does all the work.

-- 
Cheers, Gene
There are 4 boxes to be used in defense of liberty. 
Soap, ballot, jury, and ammo.
Please use in that order, starting now.  -Ed Howdershelt, Author
Additions to this message made by Gene Heskett are Copyright 2004, 
Maurice E. Heskett, all rights reserved.

Re: 2.6.8-rc2 crashes

[Gene Heskett]

On Tuesday 27 July 2004 15:26, viro@parcelfarce.linux.theplanet.co.uk 
wrote:

>Doesn't help - all we know is that at some point in a cyclic list
> we'd got NULL instead of a pointer to the next list element. 
> Could've happened for any number of reasons.
>
>What filesystems do you have on that box, BTW?

All ext3 (except swap of course)

-- 
Cheers, Gene
There are 4 boxes to be used in defense of liberty. 
Soap, ballot, jury, and ammo.
Please use in that order, starting now.  -Ed Howdershelt, Author
Additions to this message made by Gene Heskett are Copyright 2004, 
Maurice E. Heskett, all rights reserved.

Re: 2.6.8-rc2 crashes

[Gene Heskett]

On Tuesday 27 July 2004 15:26, viro@parcelfarce.linux.theplanet.co.uk 
wrote:
>Doesn't help - all we know is that at some point in a cyclic list
> we'd got NULL instead of a pointer to the next list element. 
> Could've happened for any number of reasons.
>
>What filesystems do you have on that box, BTW?

And I just recalled something else that might have a bearing, theres a 
gig of ram in this box, so the 4Gig item in the config is checked.

-- 
Cheers, Gene
There are 4 boxes to be used in defense of liberty. 
Soap, ballot, jury, and ammo.
Please use in that order, starting now.  -Ed Howdershelt, Author
Additions to this message made by Gene Heskett are Copyright 2004, 
Maurice E. Heskett, all rights reserved.

Re: 2.6.8-rc2 crashes

[Gene Heskett]

Greetings;

I just had another crash/lockup, running 2.6.8-rc2-bk3
At the instant, I was looking thru the menu's of the new
kde3.3-beta2, in the window decoration, themes etc menu,
where it got 14% loaded in a 60 megabyte file and it went
away.

>From the log (the whole Oops section this time):
Jul 28 06:48:50 coyote kernel: Unable to handle kernel NULL pointer dereference at virtual address 00000000
Jul 28 06:48:50 coyote kernel:  printing eip:
Jul 28 06:48:50 coyote kernel: c0164136
Jul 28 06:48:50 coyote kernel: *pde = 3ce74067
Jul 28 06:48:50 coyote kernel: Oops: 0002 [#1]
Jul 28 06:48:50 coyote kernel: PREEMPT
Jul 28 06:48:50 coyote kernel: Modules linked in: eeprom snd_seq_oss snd_seq_midi_event snd_seq snd_pcm_oss snd_mixer_oss snd_bt87x snd_intel8
x0 snd_ac97_codec snd_pcm snd_timer snd_page_alloc snd_mpu401_uart snd_rawmidi snd_seq_device snd forcedeth sg
Jul 28 06:48:50 coyote kernel: CPU:    0
Jul 28 06:48:50 coyote kernel: EIP:    0060:[<c0164136>]    Not tainted
Jul 28 06:48:50 coyote kernel: EFLAGS: 00010216   (2.6.8-rc2-bk3-nf2)
Jul 28 06:48:50 coyote kernel: EIP is at prune_dcache+0x36/0x1c0
Jul 28 06:48:50 coyote kernel: eax: c0364638   ebx: 00000080   ecx: e85fe134   edx: 00000000
Jul 28 06:48:50 coyote kernel: esi: 00000000   edi: c198b000   ebp: 00000080   esp: c198bef8
Jul 28 06:48:50 coyote kernel: ds: 007b   es: 007b   ss: 0068
Jul 28 06:48:50 coyote kernel: Process kswapd0 (pid: 66, threadinfo=c198b000 task=c1978050)
Jul 28 06:48:50 coyote kernel: Stack: c198bef8 c198bef8 00000080 00000000 c198b000 f7ffea60 c01646df 00000080
Jul 28 06:48:50 coyote kernel:        c013a9ab 00000080 000000d0 0001f03f 021edf00 00000000 00000118 00000000
Jul 28 06:48:51 coyote kernel:        c0363624 00000001 00000007 c0363500 c013bd51 00000020 000000d0 00000000
Jul 28 06:48:51 coyote kernel: Call Trace:
Jul 28 06:48:51 coyote kernel:  [<c01646df>] shrink_dcache_memory+0x1f/0x50
Jul 28 06:48:51 coyote kernel:  [<c013a9ab>] shrink_slab+0x14b/0x190
Jul 28 06:48:51 coyote kernel:  [<c013bd51>] balance_pgdat+0x1b1/0x200
Jul 28 06:48:51 coyote kernel:  [<c013be67>] kswapd+0xc7/0xe0
Jul 28 06:48:51 coyote kernel:  [<c0114570>] autoremove_wake_function+0x0/0x60
Jul 28 06:48:52 coyote kernel:  [<c0103f9e>] ret_from_fork+0x6/0x14
Jul 28 06:48:52 coyote kernel:  [<c0114570>] autoremove_wake_function+0x0/0x60
Jul 28 06:48:52 coyote kernel:  [<c013bda0>] kswapd+0x0/0xe0
Jul 28 06:48:52 coyote kernel:  [<c0102251>] kernel_thread_helper+0x5/0x14
Jul 28 06:48:52 coyote kernel: Code: 89 02 89 49 04 89 09 a1 3c 46 36 c0 0f 18 00 90 ff 0d 44 46
Jul 28 06:48:52 coyote kernel:  <6>note: kswapd0[66] exited with preempt_count 1
Jul 28 06:48:52 coyote kernel:
Jul 28 06:48:52 coyote kernel:  [<c030d2fc>] schedule+0x47c/0x490
Jul 28 06:48:52 coyote kernel:  [<c018797e>] ext3_ordered_writepage+0x10e/0x1c0
Jul 28 06:48:52 coyote kernel:  [<c0139d78>] __pagevec_release+0x28/0x40
Jul 28 06:48:52 coyote kernel:  [<c016ece1>] mpage_writepages+0x1b1/0x350
Jul 28 06:48:52 coyote kernel:  [<c0187870>] ext3_ordered_writepage+0x0/0x1c0
Jul 28 06:48:52 coyote kernel:  [<c0135714>] do_writepages+0x44/0x50
Jul 28 06:48:52 coyote kernel:  [<c016d3b1>] __sync_single_inode+0x71/0x210
Jul 28 06:48:52 coyote kernel:  [<c01860f3>] ext3_put_inode+0x13/0x30
Jul 28 06:48:52 coyote kernel:  [<c016d77e>] sync_sb_inodes+0x16e/0x290
Jul 28 06:48:52 coyote kernel:  [<c016da0e>] sync_inodes_sb+0x7e/0xa0
Jul 28 06:48:52 coyote kernel:  [<c016db3b>] sync_inodes+0x2b/0xa0
Jul 28 06:48:52 coyote kernel:  [<c014e034>] do_sync+0x44/0x80
Jul 28 06:48:52 coyote kernel:  [<c014e07f>] sys_sync+0xf/0x20
Jul 28 06:48:52 coyote kernel:  [<c011653f>] panic+0xff/0x110
Jul 28 06:48:52 coyote kernel:  [<c0118d5f>] do_exit+0x3ff/0x420
Jul 28 06:48:52 coyote kernel:  [<c01114f0>] do_page_fault+0x0/0x519
Jul 28 06:48:52 coyote kernel:  [<c0104968>] die+0xf8/0x100
Jul 28 06:48:52 coyote kernel:  [<c01116cb>] do_page_fault+0x1db/0x519
Jul 28 06:48:52 coyote kernel:  [<c0105dd2>] do_IRQ+0x102/0x1a0
Jul 28 06:48:52 coyote kernel:  [<c030d10e>] schedule+0x28e/0x490
Jul 28 06:48:52 coyote kernel:  [<c01114f0>] do_page_fault+0x0/0x519
Jul 28 06:48:52 coyote kernel:  [<c0104271>] error_code+0x2d/0x38
Jul 28 06:48:52 coyote kernel:  [<c0164596>] select_parent+0x56/0xb0
Jul 28 06:48:52 coyote kernel:  [<c0164600>] shrink_dcache_parent+0x10/0x30
Jul 28 06:48:52 coyote kernel:  [<c017b177>] proc_pid_flush+0x17/0x30
Jul 28 06:48:52 coyote kernel:  [<c011765d>] release_task+0x13d/0x1e0
Jul 28 06:48:52 coyote kernel:  [<c01190fb>] wait_task_zombie+0x15b/0x1c0
Jul 28 06:48:52 coyote kernel:  [<c0119513>] sys_wait4+0x213/0x260
Jul 28 06:48:52 coyote kernel:  [<c01132e0>] default_wake_function+0x0/0x20
Jul 28 06:48:52 coyote kernel:  [<c01132e0>] default_wake_function+0x0/0x20
Jul 28 11:00:39 coyote syslogd 1.4.1: restart.
--------------
Note restart time, but my script worked, the system 
time is now properly set later in the bootup.  Nice.

Ok, so which direction do I go, bk2, or bk4, for the next test?

-- 
Cheers, Gene
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
99.23% setiathome rank, not too shabby for a WV hillbilly
Yahoo.com attorneys please note, additions to this message
by Gene Heskett are:
Copyright 2004 by Maurice Eugene Heskett, all rights reserved.

Re: 2.6.8-rc2 crashes

[Andy Whitcroft]

> I just had another crash/lockup, running 2.6.8-rc2-bk3
> At the instant, I was looking thru the menu's of the new
> kde3.3-beta2, in the window decoration, themes etc menu,
> where it got 14% loaded in a 60 megabyte file and it went
> away.

Confused.  Previously (below) you were running 2.6.8-rc2 so the problem was
in that version but not in -rc1 if I read you correctly.  So I would expect
you to be testing 2.6.8-rc1-bkN snapshots to see where your breakage was
introduced.

> I have now had 4 crashes while running 2.6.8-rc2, the last one
> requiring a full powerdown before the intel-8x0 could
> re-establish control over the sound.
[...]
> I'd revert to rc1, but I'd have to figure out a way to use this .config

As viro put it:

>It goes like that:
>2.6.7
>2.6.7 + 7-bk<n>
>2.6.7 + 8-rc1
>2.6.7 + 8-rc1 + 8-rc1-bk<n>
>2.6.7 + 8-rc2
>2.6.7 + 8-rc2 + 8-rc2-bk<n>

-apw

Re: 2.6.8-rc2 crashes

[Gene Heskett]

On Wednesday 28 July 2004 07:38, Andy Whitcroft wrote:
>> I just had another crash/lockup, running 2.6.8-rc2-bk3
>> At the instant, I was looking thru the menu's of the new
>> kde3.3-beta2, in the window decoration, themes etc menu,
>> where it got 14% loaded in a 60 megabyte file and it went
>> away.
>
>Confused.  Previously (below) you were running 2.6.8-rc2 so the
> problem was in that version but not in -rc1 if I read you
> correctly.  So I would expect you to be testing 2.6.8-rc1-bkN
> snapshots to see where your breakage was introduced.

I was having mobo problems back about rc1 times, so I'm not able to 
positively say that rc1 did/did not do it.  I tried to make that 
clear in a later message but must not have been.  Motherboard, cpu, 
memory and psu are all fresh now.

As this mobo contains the nforce2 chipset, now running the reverse 
engineered driver, how far back can I go without running into 
problems with it?

>> I have now had 4 crashes while running 2.6.8-rc2, the last one
>> requiring a full powerdown before the intel-8x0 could
>> re-establish control over the sound.
>
>[...]
>
>> I'd revert to rc1, but I'd have to figure out a way to use this
>> .config
>
>As viro put it:
>>It goes like that:
>>2.6.7
>>2.6.7 + 7-bk<n>
>>2.6.7 + 8-rc1
>>2.6.7 + 8-rc1 + 8-rc1-bk<n>
>>2.6.7 + 8-rc2
>>2.6.7 + 8-rc2 + 8-rc2-bk<n>
>
>-apw

-- 
Cheers, Gene
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
99.23% setiathome rank, not too shabby for a WV hillbilly
Yahoo.com attorneys please note, additions to this message
by Gene Heskett are:
Copyright 2004 by Maurice Eugene Heskett, all rights reserved.

Re: 2.6.8-rc2 crashes

[Gene Heskett]

Greetings all;

I just had another crash, but this one was different.

/dev/hda5 developed an error and was remounted read
only by the system.  As thats /root, everything pretty
much came to a screeching halt several hours ago while
I was out carving the tapered ends on some split rail
fencing, a somewhat dangerous job because its arsenic
treated wood, and I made a large leaf bag of sawdust
and wood chips with bare hands and no resperator filter
device.

Here is the log for the event:
---------------
Jul 28 13:37:00 coyote kernel: EXT3-fs error (device hda5): ext3_free_blocks: bit already
cleared for block 761450
Jul 28 13:37:00 coyote kernel: Aborting journal on device hda5.
Jul 28 13:37:00 coyote kernel: ext3_free_blocks: aborting transaction: Journal has aborted
 in __ext3_journal_get_undo_access<2>EXT3-fs error (device hda5) in ext3_free_blocks: Jour
nal has aborted
Jul 28 13:37:00 coyote last message repeated 16 times
Jul 28 13:37:00 coyote kernel: ext3_reserve_inode_write: aborting transaction: Journal has
 aborted in __ext3_journal_get_write_access<2>EXT3-fs error (device hda5) in ext3_reserve_
inode_write: Journal has aborted
Jul 28 13:37:00 coyote kernel: EXT3-fs error (device hda5) in ext3_truncate: Journal has a
borted
Jul 28 13:37:00 coyote kernel: ext3_reserve_inode_write: aborting transaction: Journal has
 aborted in __ext3_journal_get_write_access<2>EXT3-fs error (device hda5) in ext3_reserve_
inode_write: Journal has aborted
Jul 28 13:37:00 coyote kernel: EXT3-fs error (device hda5) in ext3_orphan_del: Journal has
 aborted
Jul 28 13:37:00 coyote kernel: ext3_reserve_inode_write: aborting transaction: Journal has
 aborted in __ext3_journal_get_write_access<2>EXT3-fs error (device hda5) in ext3_reserve_
inode_write: Journal has aborted
Jul 28 13:37:00 coyote kernel: EXT3-fs error (device hda5) in ext3_delete_inode: Journal h
as aborted
Jul 28 13:37:00 coyote kernel: ext3_abort called.
Jul 28 13:37:00 coyote kernel: EXT3-fs abort (device hda5): ext3_journal_start: Detected a
borted journal
Jul 28 13:37:00 coyote kernel: Remounting filesystem read-only
Jul 28 18:34:29 coyote shutdown: shutting down for system reboot

On the reboot and e2fsck of /dev/hda5, one inode had
zero dtime and was fixed.

This is the third crash today.  I'm now building a plain
2.6.7 to run on this board as thats the newest version that
has a diff in fs/dcache.c, from 2.6.7-mm1 they are all identical.


>On Tuesday 27 July 2004 10:29,
> viro@parcelfarce.linux.theplanet.co.uk
>
>wrote:
>>On Tue, Jul 27, 2004 at 12:33:04PM -0400, Gene Heskett wrote:
>>> Greetings everybody;
>>>
>>> I have now had 4 crashes while running 2.6.8-rc2, the last one
>>> requiring a full powerdown before the intel-8x0 could
>>> re-establish control over the sound.
>>>
>>> All have had an initial Opps located in prune_dcache, and were
>>> logged as follows:
>>> Jul 27 07:58:58 coyote kernel: Unable to handle kernel NULL
>>> pointer dereference at virtual address 00000000
>>
>>... which means that dentry_unused list got corrupted, which
>> doesn't really help.  Could you try to narrow it down to
>> 2.6.8-rc1-bk<day>?
>
>And something else that doesn't help, I just found that 2.6.8-rc1
>doesn't have the reverse engineered nforce2 support, so a remake for
>this mobo probably won't fly past the decompression stage.  But
>2.6.8-rc1-mm1 does have it, but under a different xconfig entry. 
> Its building now.

-- 
Cheers, Gene
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
99.24% setiathome rank, not too shabby for a WV hillbilly
Yahoo.com attorneys please note, additions to this message
by Gene Heskett are:
Copyright 2004 by Maurice Eugene Heskett, all rights reserved.

Re: 2.6.8-rc2 crashes

[Gene Heskett]

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

On Wednesday 28 July 2004 19:26, Gene Heskett wrote:
[snip old message]
Greetings all, the saga continues;

I've had another Oops, but this one was different, I'm not locked up.

Kernel is now 2.6.7, same as I ran for a while before, and the system
feels quite snappy.

The kernel diffs between the old 2.6.7 and this one are:

ide: via driver removed, nforce installed.  Both were builtin
sound: via_8233 removed, intel-8x0 in, as module, sound works fine
eth0: rtl-8139too removed, forcedeth in, as module, networking fine
kernel 4 Gig ram switch is on, I now have a gig of DDR400 ram

System has been "upgraded" from FC1 to FC2, (newer compiler)
but still has libpangoxft problems, I cannot compile things such as gkrellm.

From the log:
--------------
Jul 29 04:02:04 coyote su(pam_unix)[4938]: session opened for user cyrus by (uid=0)
Jul 29 04:02:04 coyote su(pam_unix)[4938]: session closed for user cyrus
Jul 29 04:17:56 coyote nmbd[1690]: [2004/07/29 04:17:56, 0] nmbd/nmbd.c:process(540)
Jul 29 04:17:56 coyote nmbd[1690]:   Got SIGHUP dumping debug info.
Jul 29 04:17:56 coyote nmbd[1690]: [2004/07/29 04:17:56, 0] nmbd/nmbd_workgroupdb.c:dump_workgroups(271)
Jul 29 04:17:56 coyote nmbd[1690]:   dump_workgroups()
Jul 29 04:17:56 coyote nmbd[1690]:    dump workgroup on subnet    192.168.71.3: netmask=  255.255.255.0:
Jul 29 04:17:56 coyote nmbd[1690]:   ^ICOYOTE.DEN(1) current master browser = GENE
Jul 29 04:17:56 coyote nmbd[1690]:   ^I^ICOYOTE 40019a03 (Samba Master Server on Coyote)
Jul 29 04:17:56 coyote nmbd[1690]:   ^I^IGENE 400c9a03 (Samba Server @ Genes Coyotes Den)
---------------------
I'm not sure what thats all about, samba appears to work and
I haven't changed anything in its smb.conf in 2+ years.
 
Back to the log, at the next entry;
--------------------
Jul 29 04:20:17 coyote kernel: Unable to handle kernel paging request at virtual address 00003d14
Jul 29 04:20:17 coyote kernel:  printing eip:
Jul 29 04:20:17 coyote kernel: c0162887
Jul 29 04:20:17 coyote kernel: *pde = 00000000
Jul 29 04:20:17 coyote kernel: Oops: 0000 [#1]
Jul 29 04:20:17 coyote kernel: PREEMPT
Jul 29 04:20:17 coyote kernel: Modules linked in: tuner tvaudio bttv video_buf btcx_risc eeprom snd_seq_oss snd_seq_midi_event snd_seq snd_pcm_oss snd_mixer_oss snd_bt87x snd_intel8x0 snd_ac97_codec snd_pcm snd_timer snd_page_alloc snd_mpu401_uart snd_rawmidi snd_seq_device snd forcedeth sg
Jul 29 04:20:17 coyote kernel: CPU:    0
Jul 29 04:20:17 coyote kernel: EIP:    0060:[<c0162887>]    Not tainted
Jul 29 04:20:17 coyote kernel: EFLAGS: 00010206   (2.6.7-nf2)
Jul 29 04:20:17 coyote kernel: EIP is at prune_dcache+0x147/0x1c0
Jul 29 04:20:17 coyote kernel: eax: 00003d00   ebx: d3ff3050   ecx: e553fab0   edx: e553b7b0
Jul 29 04:20:17 coyote kernel: esi: e553b7a0   edi: c1973000   ebp: 0000003b   esp: c1973ef8
Jul 29 04:20:17 coyote kernel: ds: 007b   es: 007b   ss: 0068
Jul 29 04:20:17 coyote kernel: Process kswapd0 (pid: 65, threadinfo=c1973000 task=c1986050)
Jul 29 04:20:17 coyote kernel: Stack: c26af618 c1973ef8 00000080 00000000 c1973000 f7ffea48 c0162d1f 00000080
Jul 29 04:20:19 coyote kernel:        c0139a2b 00000080 000000d0 0002f053 06033440 00000000 0000020b 00000000
Jul 29 04:20:19 coyote kernel:        c0364564 00000001 0000000a c0364440 c013add1 000000a0 000000d0 00000000
Jul 29 04:20:19 coyote kernel: Call Trace:
Jul 29 04:20:19 coyote kernel:  [<c0162d1f>] shrink_dcache_memory+0x1f/0x30
Jul 29 04:20:19 coyote kernel:  [<c0139a2b>] shrink_slab+0x14b/0x190
Jul 29 04:20:19 coyote kernel:  [<c013add1>] balance_pgdat+0x1b1/0x200
Jul 29 04:20:20 coyote kernel:  [<c013aee7>] kswapd+0xc7/0xe0
Jul 29 04:20:20 coyote kernel:  [<c0114270>] autoremove_wake_function+0x0/0x60
Jul 29 04:20:20 coyote kernel:  [<c0103e9e>] ret_from_fork+0x6/0x14
Jul 29 04:20:20 coyote kernel:  [<c0114270>] autoremove_wake_function+0x0/0x60
Jul 29 04:20:21 coyote kernel:  [<c013ae20>] kswapd+0x0/0xe0
Jul 29 04:20:21 coyote kernel:  [<c01021d1>] kernel_thread_helper+0x5/0x14
Jul 29 04:20:21 coyote kernel:
Jul 29 04:20:21 coyote kernel: Code: 8b 50 14 85 d2 75 27 89 34 24 e8 4a 2b 00 00 8b 73 0c 89 1c
Jul 29 04:20:27 coyote kernel:  <1>Unable to handle kernel paging request at virtual address 0001fa01
Jul 29 04:20:27 coyote kernel:  printing eip:
Jul 29 04:20:27 coyote kernel: c0163350
Jul 29 04:20:27 coyote kernel: *pde = 00000000
Jul 29 04:20:27 coyote kernel: Oops: 0000 [#2]
Jul 29 04:20:27 coyote kernel: PREEMPT
Jul 29 04:20:27 coyote kernel: Modules linked in: tuner tvaudio bttv video_buf btcx_risc eeprom snd_seq_oss snd_seq_midi_event snd_seq snd_pcm_oss snd_mixer_oss snd_bt87x snd_intel8x0 snd_ac97_codec snd_pcm snd_timer snd_page_alloc snd_mpu401_uart snd_rawmidi snd_seq_device snd forcedeth sg
Jul 29 04:20:27 coyote kernel: CPU:    0
Jul 29 04:20:27 coyote kernel: EIP:    0060:[<c0163350>]    Not tainted
Jul 29 04:20:27 coyote kernel: EFLAGS: 00010202   (2.6.7-nf2)
Jul 29 04:20:27 coyote kernel: EIP is at __d_lookup+0x80/0x170
Jul 29 04:20:27 coyote kernel: eax: 0001fa01   ebx: 0001fa01   ecx: 00000011   edx: f7f00000
Jul 29 04:20:27 coyote kernel: esi: f7f0d26c   edi: 3b26a098   ebp: d6beae30   esp: c5119e40
Jul 29 04:20:28 coyote kernel: ds: 007b   es: 007b   ss: 0068
Jul 29 04:20:28 coyote kernel: Process updatedb (pid: 6557, threadinfo=c5119000 task=e4315170)
Jul 29 04:20:28 coyote kernel: Stack: d978c680 d9785740 df58d4bc c5119000 3b26a098 ed251100 00000000 f7f0d26c
Jul 29 04:20:28 coyote kernel:        f7c2b000 0000000c f7c2b000 c5119f28 f7fcd760 c5119ebc c0158f90 dcc64050
Jul 29 04:20:28 coyote kernel:        c5119ec4 dcc64050 f7c2b000 c5119ebc ed251100 c5119ec4 c015950b c5119f28
Jul 29 04:20:27 coyote su(pam_unix)[6563]: session opened for user news by (uid=0)
Jul 29 04:20:28 coyote kernel: Call Trace:
Jul 29 04:20:28 coyote kernel:  [<c0158f90>] do_lookup+0x30/0xb0
Jul 29 04:20:28 coyote kernel:  [<c015950b>] link_path_walk+0x4fb/0x9b0
Jul 29 04:20:28 coyote kernel:  [<c0159c27>] path_lookup+0x77/0x140
Jul 29 04:20:28 coyote su(pam_unix)[6563]: session closed for user news
Jul 29 04:20:28 coyote kernel:  [<c0159eb9>] __user_walk+0x49/0x60
Jul 29 04:20:28 coyote kernel:  [<c0154ddc>] vfs_lstat+0x1c/0x60
Jul 29 04:20:29 coyote kernel:  [<c015550b>] sys_lstat64+0x1b/0x40
Jul 29 04:20:30 coyote kernel:  [<c0103f75>] sysenter_past_esp+0x52/0x71
Jul 29 04:20:30 coyote kernel:
Jul 29 04:20:30 coyote kernel: Code: 8b 03 0f 18 00 90 8d 6b 98 8b 7c 24 10 39 7d 14 74 2a 8b 1b
Jul 29 04:20:30 coyote kernel:  <6>note: updatedb[6557] exited with preempt_count 1
Jul 29 04:20:30 coyote kernel: bad: scheduling while atomic!
Jul 29 04:20:30 coyote kernel:  [<c03092fc>] schedule+0x47c/0x490
Jul 29 04:20:30 coyote kernel:  [<c013cc9b>] unmap_page_range+0x4b/0x80
Jul 29 04:20:30 coyote kernel:  [<c013ce7c>] unmap_vmas+0x1ac/0x1c0
Jul 29 04:20:30 coyote kernel:  [<c01411e3>] exit_mmap+0x83/0x160
Jul 29 04:20:30 coyote kernel:  [<c0114584>] mmput+0x64/0x90
Jul 29 04:20:30 coyote kernel:  [<c01185c2>] do_exit+0x152/0x400
Jul 29 04:20:30 coyote kernel:  [<c0111230>] do_page_fault+0x0/0x4da
Jul 29 04:20:30 coyote kernel:  [<c0104858>] die+0xf8/0x100
Jul 29 04:20:30 coyote kernel:  [<c011140b>] do_page_fault+0x1db/0x4da
Jul 29 04:20:30 coyote kernel:  [<c014c973>] wake_up_buffer+0x13/0x40
Jul 29 04:20:30 coyote kernel:  [<c014cae3>] unlock_buffer+0x13/0x20
Jul 29 04:20:30 coyote kernel:  [<c014e305>] __find_get_block+0x65/0xe0
Jul 29 04:20:30 coyote kernel:  [<c014e3ab>] __getblk+0x2b/0x60
Jul 29 04:20:30 coyote kernel:  [<c01872fa>] ext3_get_inode_loc+0x5a/0x250
Jul 29 04:20:30 coyote kernel:  [<c0111230>] do_page_fault+0x0/0x4da
Jul 29 04:20:30 coyote kernel:  [<c0104171>] error_code+0x2d/0x38
Jul 29 04:20:30 coyote kernel:  [<c0163350>] __d_lookup+0x80/0x170
Jul 29 04:20:30 coyote kernel:  [<c0158f90>] do_lookup+0x30/0xb0
Jul 29 04:20:30 coyote kernel:  [<c015950b>] link_path_walk+0x4fb/0x9b0
Jul 29 04:20:30 coyote kernel:  [<c0159c27>] path_lookup+0x77/0x140
Jul 29 04:20:30 coyote kernel:  [<c0159eb9>] __user_walk+0x49/0x60
Jul 29 04:20:30 coyote kernel:  [<c0154ddc>] vfs_lstat+0x1c/0x60
Jul 29 04:20:30 coyote kernel:  [<c015550b>] sys_lstat64+0x1b/0x40
Jul 29 04:20:30 coyote kernel:  [<c0103f75>] sysenter_past_esp+0x52/0x71
Jul 29 04:20:30 coyote kernel:
----------------
and theres one of these for about 80% of the kmail fetchmail runs:
----------------
Jul 29 04:45:44 coyote fam[2505]: stat on "korgacrc.lock" failed: No such file or directory
----------------
The .config that built this kernel is attached.

While you all are thinking about this, I'm rebooting to my memtest86 disk for
about 4 passes.  Back much later.

-- 
Cheers, Gene
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
99.24% setiathome rank, not too shabby for a WV hillbilly
Yahoo.com attorneys please note, additions to this message
by Gene Heskett are:
Copyright 2004 by Maurice Eugene Heskett, all rights reserved.

[-- Attachment #2: .config --]
[-- Type: text/plain, Size: 28829 bytes --]

#
# Automatically generated make config: don't edit
#
CONFIG_X86=y
CONFIG_MMU=y
CONFIG_UID16=y
CONFIG_GENERIC_ISA_DMA=y

#
# Code maturity level options
#
CONFIG_EXPERIMENTAL=y
# CONFIG_CLEAN_COMPILE is not set
CONFIG_STANDALONE=y
CONFIG_BROKEN=y
CONFIG_BROKEN_ON_SMP=y

#
# General setup
#
CONFIG_SWAP=y
CONFIG_SYSVIPC=y
CONFIG_POSIX_MQUEUE=y
CONFIG_BSD_PROCESS_ACCT=y
CONFIG_SYSCTL=y
# CONFIG_AUDIT is not set
CONFIG_LOG_BUF_SHIFT=14
CONFIG_HOTPLUG=y
CONFIG_IKCONFIG=y
CONFIG_IKCONFIG_PROC=y
# CONFIG_EMBEDDED is not set
CONFIG_KALLSYMS=y
CONFIG_FUTEX=y
CONFIG_EPOLL=y
CONFIG_IOSCHED_NOOP=y
CONFIG_IOSCHED_AS=y
CONFIG_IOSCHED_DEADLINE=y
CONFIG_IOSCHED_CFQ=y
# CONFIG_CC_OPTIMIZE_FOR_SIZE is not set

#
# Loadable module support
#
CONFIG_MODULES=y
CONFIG_MODULE_UNLOAD=y
CONFIG_MODULE_FORCE_UNLOAD=y
CONFIG_OBSOLETE_MODPARM=y
CONFIG_MODVERSIONS=y
CONFIG_KMOD=y

#
# Processor type and features
#
CONFIG_X86_PC=y
# CONFIG_X86_ELAN is not set
# CONFIG_X86_VOYAGER is not set
# CONFIG_X86_NUMAQ is not set
# CONFIG_X86_SUMMIT is not set
# CONFIG_X86_BIGSMP is not set
# CONFIG_X86_VISWS is not set
# CONFIG_X86_GENERICARCH is not set
# CONFIG_X86_ES7000 is not set
# CONFIG_M386 is not set
# CONFIG_M486 is not set
# CONFIG_M586 is not set
# CONFIG_M586TSC is not set
# CONFIG_M586MMX is not set
# CONFIG_M686 is not set
# CONFIG_MPENTIUMII is not set
# CONFIG_MPENTIUMIII is not set
# CONFIG_MPENTIUMM is not set
# CONFIG_MPENTIUM4 is not set
# CONFIG_MK6 is not set
CONFIG_MK7=y
# CONFIG_MK8 is not set
# CONFIG_MCRUSOE is not set
# CONFIG_MWINCHIPC6 is not set
# CONFIG_MWINCHIP2 is not set
# CONFIG_MWINCHIP3D is not set
# CONFIG_MCYRIXIII is not set
# CONFIG_MVIAC3_2 is not set
# CONFIG_X86_GENERIC is not set
CONFIG_X86_CMPXCHG=y
CONFIG_X86_XADD=y
CONFIG_X86_L1_CACHE_SHIFT=6
CONFIG_RWSEM_XCHGADD_ALGORITHM=y
CONFIG_X86_WP_WORKS_OK=y
CONFIG_X86_INVLPG=y
CONFIG_X86_BSWAP=y
CONFIG_X86_POPAD_OK=y
CONFIG_X86_GOOD_APIC=y
CONFIG_X86_INTEL_USERCOPY=y
CONFIG_X86_USE_PPRO_CHECKSUM=y
CONFIG_X86_USE_3DNOW=y
CONFIG_HPET_TIMER=y
CONFIG_HPET_EMULATE_RTC=y
# CONFIG_SMP is not set
CONFIG_PREEMPT=y
# CONFIG_X86_UP_APIC is not set
CONFIG_X86_TSC=y
# CONFIG_X86_MCE is not set
# CONFIG_TOSHIBA is not set
# CONFIG_I8K is not set
# CONFIG_MICROCODE is not set
# CONFIG_X86_MSR is not set
CONFIG_X86_CPUID=y

#
# Firmware Drivers
#
# CONFIG_EDD is not set
# CONFIG_NOHIGHMEM is not set
CONFIG_HIGHMEM4G=y
# CONFIG_HIGHMEM64G is not set
CONFIG_HIGHMEM=y
CONFIG_HIGHPTE=y
# CONFIG_MATH_EMULATION is not set
CONFIG_MTRR=y
CONFIG_HAVE_DEC_LOCK=y
# CONFIG_REGPARM is not set

#
# Power management options (ACPI, APM)
#
CONFIG_PM=y
# CONFIG_SOFTWARE_SUSPEND is not set
# CONFIG_PM_DISK is not set

#
# ACPI (Advanced Configuration and Power Interface) Support
#
# CONFIG_ACPI is not set
CONFIG_ACPI_BOOT=y

#
# APM (Advanced Power Management) BIOS Support
#
CONFIG_APM=y
# CONFIG_APM_IGNORE_USER_SUSPEND is not set
# CONFIG_APM_DO_ENABLE is not set
# CONFIG_APM_CPU_IDLE is not set
# CONFIG_APM_DISPLAY_BLANK is not set
CONFIG_APM_RTC_IS_GMT=y
# CONFIG_APM_ALLOW_INTS is not set
CONFIG_APM_REAL_MODE_POWER_OFF=y

#
# CPU Frequency scaling
#
# CONFIG_CPU_FREQ is not set

#
# Bus options (PCI, PCMCIA, EISA, MCA, ISA)
#
CONFIG_PCI=y
# CONFIG_PCI_GOBIOS is not set
# CONFIG_PCI_GOMMCONFIG is not set
# CONFIG_PCI_GODIRECT is not set
CONFIG_PCI_GOANY=y
CONFIG_PCI_BIOS=y
CONFIG_PCI_DIRECT=y
CONFIG_PCI_MMCONFIG=y
CONFIG_PCI_LEGACY_PROC=y
CONFIG_PCI_NAMES=y
CONFIG_ISA=y
# CONFIG_EISA is not set
# CONFIG_MCA is not set
# CONFIG_SCx200 is not set

#
# PCMCIA/CardBus support
#
# CONFIG_PCMCIA is not set
CONFIG_PCMCIA_PROBE=y

#
# PCI Hotplug Support
#
# CONFIG_HOTPLUG_PCI is not set

#
# Executable file formats
#
CONFIG_BINFMT_ELF=y
CONFIG_BINFMT_AOUT=y
CONFIG_BINFMT_MISC=y

#
# Device Drivers
#

#
# Generic Driver Options
#
# CONFIG_FW_LOADER is not set

#
# Memory Technology Devices (MTD)
#
# CONFIG_MTD is not set

#
# Parallel port support
#
CONFIG_PARPORT=y
CONFIG_PARPORT_PC=y
CONFIG_PARPORT_PC_CML1=y
# CONFIG_PARPORT_SERIAL is not set
# CONFIG_PARPORT_PC_FIFO is not set
# CONFIG_PARPORT_PC_SUPERIO is not set
# CONFIG_PARPORT_OTHER is not set
CONFIG_PARPORT_1284=y

#
# Plug and Play support
#
CONFIG_PNP=y
CONFIG_PNP_DEBUG=y

#
# Protocols
#
CONFIG_ISAPNP=y
CONFIG_PNPBIOS=y
CONFIG_PNPBIOS_PROC_FS=y

#
# Block devices
#
CONFIG_BLK_DEV_FD=y
# CONFIG_BLK_DEV_XD is not set
# CONFIG_PARIDE is not set
# CONFIG_BLK_CPQ_DA is not set
# CONFIG_BLK_CPQ_CISS_DA is not set
# CONFIG_BLK_DEV_DAC960 is not set
# CONFIG_BLK_DEV_UMEM is not set
CONFIG_BLK_DEV_LOOP=y
# CONFIG_BLK_DEV_CRYPTOLOOP is not set
# CONFIG_BLK_DEV_NBD is not set
# CONFIG_BLK_DEV_CARMEL is not set
# CONFIG_BLK_DEV_RAM is not set
# CONFIG_LBD is not set

#
# ATA/ATAPI/MFM/RLL support
#
CONFIG_IDE=y
CONFIG_BLK_DEV_IDE=y

#
# Please see Documentation/ide.txt for help/info on IDE drives
#
# CONFIG_BLK_DEV_HD_IDE is not set
CONFIG_BLK_DEV_IDEDISK=y
# CONFIG_IDEDISK_MULTI_MODE is not set
CONFIG_BLK_DEV_IDECD=y
# CONFIG_BLK_DEV_IDETAPE is not set
# CONFIG_BLK_DEV_IDEFLOPPY is not set
# CONFIG_BLK_DEV_IDESCSI is not set
# CONFIG_IDE_TASK_IOCTL is not set
# CONFIG_IDE_TASKFILE_IO is not set

#
# IDE chipset support/bugfixes
#
# CONFIG_IDE_GENERIC is not set
# CONFIG_BLK_DEV_CMD640 is not set
# CONFIG_BLK_DEV_IDEPNP is not set
CONFIG_BLK_DEV_IDEPCI=y
# CONFIG_IDEPCI_SHARE_IRQ is not set
# CONFIG_BLK_DEV_OFFBOARD is not set
# CONFIG_BLK_DEV_GENERIC is not set
# CONFIG_BLK_DEV_OPTI621 is not set
# CONFIG_BLK_DEV_RZ1000 is not set
CONFIG_BLK_DEV_IDEDMA_PCI=y
# CONFIG_BLK_DEV_IDEDMA_FORCED is not set
CONFIG_IDEDMA_PCI_AUTO=y
# CONFIG_IDEDMA_ONLYDISK is not set
CONFIG_BLK_DEV_ADMA=y
# CONFIG_BLK_DEV_AEC62XX is not set
# CONFIG_BLK_DEV_ALI15X3 is not set
CONFIG_BLK_DEV_AMD74XX=y
# CONFIG_BLK_DEV_ATIIXP is not set
# CONFIG_BLK_DEV_CMD64X is not set
# CONFIG_BLK_DEV_TRIFLEX is not set
# CONFIG_BLK_DEV_CY82C693 is not set
# CONFIG_BLK_DEV_CS5520 is not set
# CONFIG_BLK_DEV_CS5530 is not set
# CONFIG_BLK_DEV_HPT34X is not set
# CONFIG_BLK_DEV_HPT366 is not set
# CONFIG_BLK_DEV_SC1200 is not set
# CONFIG_BLK_DEV_PIIX is not set
# CONFIG_BLK_DEV_NS87415 is not set
# CONFIG_BLK_DEV_PDC202XX_OLD is not set
# CONFIG_BLK_DEV_PDC202XX_NEW is not set
# CONFIG_BLK_DEV_SVWKS is not set
# CONFIG_BLK_DEV_SIIMAGE is not set
# CONFIG_BLK_DEV_SIS5513 is not set
# CONFIG_BLK_DEV_SLC90E66 is not set
# CONFIG_BLK_DEV_TRM290 is not set
# CONFIG_BLK_DEV_VIA82CXXX is not set
# CONFIG_IDE_ARM is not set
# CONFIG_IDE_CHIPSETS is not set
CONFIG_BLK_DEV_IDEDMA=y
CONFIG_IDEDMA_IVB=y
CONFIG_IDEDMA_AUTO=y
# CONFIG_BLK_DEV_HD is not set

#
# SCSI device support
#
CONFIG_SCSI=y
CONFIG_SCSI_PROC_FS=y

#
# SCSI support type (disk, tape, CD-ROM)
#
CONFIG_BLK_DEV_SD=m
CONFIG_CHR_DEV_ST=m
# CONFIG_CHR_DEV_OSST is not set
# CONFIG_BLK_DEV_SR is not set
CONFIG_CHR_DEV_SG=m

#
# Some SCSI devices (e.g. CD jukebox) support multiple LUNs
#
CONFIG_SCSI_MULTI_LUN=y
CONFIG_SCSI_CONSTANTS=y
# CONFIG_SCSI_LOGGING is not set

#
# SCSI Transport Attributes
#
# CONFIG_SCSI_SPI_ATTRS is not set
# CONFIG_SCSI_FC_ATTRS is not set

#
# SCSI low-level drivers
#
# CONFIG_BLK_DEV_3W_XXXX_RAID is not set
# CONFIG_SCSI_7000FASST is not set
# CONFIG_SCSI_ACARD is not set
# CONFIG_SCSI_AHA152X is not set
# CONFIG_SCSI_AHA1542 is not set
# CONFIG_SCSI_AACRAID is not set
# CONFIG_SCSI_AIC7XXX is not set
# CONFIG_SCSI_AIC7XXX_OLD is not set
# CONFIG_SCSI_AIC79XX is not set
# CONFIG_SCSI_DPT_I2O is not set
# CONFIG_SCSI_ADVANSYS is not set
# CONFIG_SCSI_IN2000 is not set
# CONFIG_SCSI_MEGARAID is not set
# CONFIG_SCSI_SATA is not set
# CONFIG_SCSI_BUSLOGIC is not set
# CONFIG_SCSI_CPQFCTS is not set
# CONFIG_SCSI_DMX3191D is not set
# CONFIG_SCSI_DTC3280 is not set
# CONFIG_SCSI_EATA is not set
# CONFIG_SCSI_EATA_PIO is not set
# CONFIG_SCSI_FUTURE_DOMAIN is not set
# CONFIG_SCSI_GDTH is not set
# CONFIG_SCSI_GENERIC_NCR5380 is not set
# CONFIG_SCSI_GENERIC_NCR5380_MMIO is not set
# CONFIG_SCSI_IPS is not set
# CONFIG_SCSI_INITIO is not set
# CONFIG_SCSI_INIA100 is not set
# CONFIG_SCSI_PPA is not set
# CONFIG_SCSI_IMM is not set
# CONFIG_SCSI_NCR53C406A is not set
# CONFIG_SCSI_SYM53C8XX_2 is not set
# CONFIG_SCSI_IPR is not set
# CONFIG_SCSI_PAS16 is not set
# CONFIG_SCSI_PCI2000 is not set
# CONFIG_SCSI_PCI2220I is not set
# CONFIG_SCSI_PSI240I is not set
# CONFIG_SCSI_QLOGIC_FAS is not set
# CONFIG_SCSI_QLOGIC_ISP is not set
# CONFIG_SCSI_QLOGIC_FC is not set
# CONFIG_SCSI_QLOGIC_1280 is not set
CONFIG_SCSI_QLA2XXX=y
# CONFIG_SCSI_QLA21XX is not set
# CONFIG_SCSI_QLA22XX is not set
# CONFIG_SCSI_QLA2300 is not set
# CONFIG_SCSI_QLA2322 is not set
# CONFIG_SCSI_QLA6312 is not set
# CONFIG_SCSI_QLA6322 is not set
# CONFIG_SCSI_SEAGATE is not set
# CONFIG_SCSI_SYM53C416 is not set
# CONFIG_SCSI_DC395x is not set
# CONFIG_SCSI_DC390T is not set
# CONFIG_SCSI_T128 is not set
# CONFIG_SCSI_U14_34F is not set
# CONFIG_SCSI_ULTRASTOR is not set
# CONFIG_SCSI_NSP32 is not set
# CONFIG_SCSI_DEBUG is not set

#
# Old CD-ROM drivers (not SCSI, not IDE)
#
# CONFIG_CD_NO_IDESCSI is not set

#
# Multi-device support (RAID and LVM)
#
# CONFIG_MD is not set

#
# Fusion MPT device support
#
# CONFIG_FUSION is not set

#
# IEEE 1394 (FireWire) support
#
# CONFIG_IEEE1394 is not set

#
# I2O device support
#
# CONFIG_I2O is not set

#
# Networking support
#
CONFIG_NET=y

#
# Networking options
#
CONFIG_PACKET=y
CONFIG_PACKET_MMAP=y
CONFIG_NETLINK_DEV=y
CONFIG_UNIX=y
# CONFIG_NET_KEY is not set
CONFIG_INET=y
# CONFIG_IP_MULTICAST is not set
# CONFIG_IP_ADVANCED_ROUTER is not set
# CONFIG_IP_PNP is not set
# CONFIG_NET_IPIP is not set
# CONFIG_NET_IPGRE is not set
# CONFIG_ARPD is not set
# CONFIG_SYN_COOKIES is not set
# CONFIG_INET_AH is not set
# CONFIG_INET_ESP is not set
# CONFIG_INET_IPCOMP is not set
# CONFIG_IPV6 is not set
# CONFIG_NETFILTER is not set

#
# SCTP Configuration (EXPERIMENTAL)
#
# CONFIG_IP_SCTP is not set
# CONFIG_ATM is not set
# CONFIG_BRIDGE is not set
# CONFIG_VLAN_8021Q is not set
# CONFIG_DECNET is not set
# CONFIG_LLC2 is not set
# CONFIG_IPX is not set
# CONFIG_ATALK is not set
# CONFIG_X25 is not set
# CONFIG_LAPB is not set
# CONFIG_NET_DIVERT is not set
# CONFIG_ECONET is not set
# CONFIG_WAN_ROUTER is not set
# CONFIG_NET_FASTROUTE is not set
# CONFIG_NET_HW_FLOWCONTROL is not set

#
# QoS and/or fair queueing
#
# CONFIG_NET_SCHED is not set

#
# Network testing
#
# CONFIG_NET_PKTGEN is not set
# CONFIG_NETPOLL is not set
# CONFIG_NET_POLL_CONTROLLER is not set
# CONFIG_HAMRADIO is not set
# CONFIG_IRDA is not set
# CONFIG_BT is not set
CONFIG_NETDEVICES=y
CONFIG_DUMMY=y
# CONFIG_BONDING is not set
# CONFIG_EQUALIZER is not set
# CONFIG_TUN is not set
# CONFIG_ETHERTAP is not set
# CONFIG_NET_SB1000 is not set

#
# ARCnet devices
#
# CONFIG_ARCNET is not set

#
# Ethernet (10 or 100Mbit)
#
CONFIG_NET_ETHERNET=y
CONFIG_MII=y
# CONFIG_HAPPYMEAL is not set
# CONFIG_SUNGEM is not set
# CONFIG_NET_VENDOR_3COM is not set
# CONFIG_LANCE is not set
# CONFIG_NET_VENDOR_SMC is not set
# CONFIG_NET_VENDOR_RACAL is not set

#
# Tulip family network device support
#
# CONFIG_NET_TULIP is not set
# CONFIG_AT1700 is not set
# CONFIG_DEPCA is not set
# CONFIG_HP100 is not set
# CONFIG_NET_ISA is not set
CONFIG_NET_PCI=y
# CONFIG_PCNET32 is not set
# CONFIG_AMD8111_ETH is not set
# CONFIG_ADAPTEC_STARFIRE is not set
# CONFIG_AC3200 is not set
# CONFIG_APRICOT is not set
# CONFIG_B44 is not set
CONFIG_FORCEDETH=m
# CONFIG_CS89x0 is not set
# CONFIG_DGRS is not set
# CONFIG_EEPRO100 is not set
# CONFIG_E100 is not set
# CONFIG_FEALNX is not set
# CONFIG_NATSEMI is not set
# CONFIG_NE2K_PCI is not set
# CONFIG_8139CP is not set
# CONFIG_8139TOO is not set
# CONFIG_SIS900 is not set
# CONFIG_EPIC100 is not set
# CONFIG_SUNDANCE is not set
# CONFIG_TLAN is not set
# CONFIG_VIA_RHINE is not set
# CONFIG_NET_POCKET is not set

#
# Ethernet (1000 Mbit)
#
# CONFIG_ACENIC is not set
# CONFIG_DL2K is not set
# CONFIG_E1000 is not set
# CONFIG_NS83820 is not set
# CONFIG_HAMACHI is not set
# CONFIG_YELLOWFIN is not set
CONFIG_R8169=m
# CONFIG_SK98LIN is not set
# CONFIG_TIGON3 is not set

#
# Ethernet (10000 Mbit)
#
# CONFIG_IXGB is not set
# CONFIG_S2IO is not set

#
# Token Ring devices
#
# CONFIG_TR is not set

#
# Wireless LAN (non-hamradio)
#
# CONFIG_NET_RADIO is not set

#
# Wan interfaces
#
# CONFIG_WAN is not set
# CONFIG_FDDI is not set
# CONFIG_HIPPI is not set
# CONFIG_PLIP is not set
# CONFIG_PPP is not set
# CONFIG_SLIP is not set
# CONFIG_NET_FC is not set
# CONFIG_SHAPER is not set
# CONFIG_NETCONSOLE is not set

#
# ISDN subsystem
#
# CONFIG_ISDN is not set

#
# Telephony Support
#
# CONFIG_PHONE is not set

#
# Input device support
#
CONFIG_INPUT=y

#
# Userland interfaces
#
CONFIG_INPUT_MOUSEDEV=y
CONFIG_INPUT_MOUSEDEV_PSAUX=y
CONFIG_INPUT_MOUSEDEV_SCREEN_X=1600
CONFIG_INPUT_MOUSEDEV_SCREEN_Y=1200
# CONFIG_INPUT_JOYDEV is not set
# CONFIG_INPUT_TSDEV is not set
CONFIG_INPUT_EVDEV=y
CONFIG_INPUT_EVBUG=y

#
# Input I/O drivers
#
# CONFIG_GAMEPORT is not set
CONFIG_SOUND_GAMEPORT=y
CONFIG_SERIO=y
CONFIG_SERIO_I8042=y
# CONFIG_SERIO_SERPORT is not set
# CONFIG_SERIO_CT82C710 is not set
# CONFIG_SERIO_PARKBD is not set
# CONFIG_SERIO_PCIPS2 is not set

#
# Input Device Drivers
#
CONFIG_INPUT_KEYBOARD=y
CONFIG_KEYBOARD_ATKBD=y
# CONFIG_KEYBOARD_SUNKBD is not set
# CONFIG_KEYBOARD_LKKBD is not set
# CONFIG_KEYBOARD_XTKBD is not set
# CONFIG_KEYBOARD_NEWTON is not set
CONFIG_INPUT_MOUSE=y
CONFIG_MOUSE_PS2=y
# CONFIG_MOUSE_SERIAL is not set
# CONFIG_MOUSE_INPORT is not set
# CONFIG_MOUSE_LOGIBM is not set
# CONFIG_MOUSE_PC110PAD is not set
# CONFIG_MOUSE_VSXXXAA is not set
# CONFIG_INPUT_JOYSTICK is not set
# CONFIG_INPUT_TOUCHSCREEN is not set
CONFIG_INPUT_MISC=y
CONFIG_INPUT_PCSPKR=y
# CONFIG_INPUT_UINPUT is not set

#
# Character devices
#
CONFIG_VT=y
CONFIG_VT_CONSOLE=y
CONFIG_HW_CONSOLE=y
# CONFIG_SERIAL_NONSTANDARD is not set

#
# Serial drivers
#
CONFIG_SERIAL_8250=y
# CONFIG_SERIAL_8250_CONSOLE is not set
CONFIG_SERIAL_8250_NR_UARTS=2
CONFIG_SERIAL_8250_EXTENDED=y
# CONFIG_SERIAL_8250_MANY_PORTS is not set
CONFIG_SERIAL_8250_SHARE_IRQ=y
# CONFIG_SERIAL_8250_DETECT_IRQ is not set
# CONFIG_SERIAL_8250_MULTIPORT is not set
# CONFIG_SERIAL_8250_RSA is not set

#
# Non-8250 serial port support
#
CONFIG_SERIAL_CORE=y
CONFIG_UNIX98_PTYS=y
CONFIG_LEGACY_PTYS=y
CONFIG_LEGACY_PTY_COUNT=256
CONFIG_PRINTER=y
# CONFIG_LP_CONSOLE is not set
# CONFIG_PPDEV is not set
# CONFIG_TIPAR is not set
# CONFIG_QIC02_TAPE is not set

#
# IPMI
#
CONFIG_IPMI_HANDLER=y
# CONFIG_IPMI_PANIC_EVENT is not set
CONFIG_IPMI_DEVICE_INTERFACE=y
# CONFIG_IPMI_SI is not set
# CONFIG_IPMI_WATCHDOG is not set

#
# Watchdog Cards
#
# CONFIG_WATCHDOG is not set
# CONFIG_HW_RANDOM is not set
# CONFIG_NVRAM is not set
CONFIG_RTC=y
# CONFIG_DTLK is not set
# CONFIG_R3964 is not set
# CONFIG_APPLICOM is not set
# CONFIG_SONYPI is not set

#
# Ftape, the floppy tape device driver
#
# CONFIG_FTAPE is not set
CONFIG_AGP=y
# CONFIG_AGP_ALI is not set
CONFIG_AGP_ATI=y
# CONFIG_AGP_AMD is not set
# CONFIG_AGP_AMD64 is not set
# CONFIG_AGP_INTEL is not set
# CONFIG_AGP_INTEL_MCH is not set
CONFIG_AGP_NVIDIA=y
# CONFIG_AGP_SIS is not set
# CONFIG_AGP_SWORKS is not set
# CONFIG_AGP_VIA is not set
# CONFIG_AGP_EFFICEON is not set
CONFIG_DRM=y
# CONFIG_DRM_TDFX is not set
# CONFIG_DRM_GAMMA is not set
# CONFIG_DRM_R128 is not set
CONFIG_DRM_RADEON=y
# CONFIG_DRM_MGA is not set
# CONFIG_DRM_SIS is not set
# CONFIG_MWAVE is not set
# CONFIG_RAW_DRIVER is not set
# CONFIG_HANGCHECK_TIMER is not set

#
# I2C support
#
CONFIG_I2C=y
CONFIG_I2C_CHARDEV=y

#
# I2C Algorithms
#
CONFIG_I2C_ALGOBIT=y
# CONFIG_I2C_ALGOPCF is not set

#
# I2C Hardware Bus support
#
# CONFIG_I2C_ALI1535 is not set
# CONFIG_I2C_ALI1563 is not set
# CONFIG_I2C_ALI15X3 is not set
# CONFIG_I2C_AMD756 is not set
# CONFIG_I2C_AMD8111 is not set
# CONFIG_I2C_ELEKTOR is not set
# CONFIG_I2C_I801 is not set
# CONFIG_I2C_I810 is not set
CONFIG_I2C_ISA=y
# CONFIG_I2C_NFORCE2 is not set
# CONFIG_I2C_PARPORT is not set
# CONFIG_I2C_PARPORT_LIGHT is not set
# CONFIG_I2C_PIIX4 is not set
# CONFIG_I2C_PROSAVAGE is not set
# CONFIG_I2C_SAVAGE4 is not set
# CONFIG_SCx200_ACB is not set
# CONFIG_I2C_SIS5595 is not set
# CONFIG_I2C_SIS630 is not set
# CONFIG_I2C_SIS96X is not set
# CONFIG_I2C_VIA is not set
# CONFIG_I2C_VIAPRO is not set
# CONFIG_I2C_VOODOO3 is not set

#
# Hardware Sensors Chip support
#
CONFIG_I2C_SENSOR=y
# CONFIG_SENSORS_ADM1021 is not set
# CONFIG_SENSORS_ASB100 is not set
# CONFIG_SENSORS_DS1621 is not set
# CONFIG_SENSORS_FSCHER is not set
# CONFIG_SENSORS_GL518SM is not set
# CONFIG_SENSORS_IT87 is not set
# CONFIG_SENSORS_LM75 is not set
# CONFIG_SENSORS_LM78 is not set
# CONFIG_SENSORS_LM80 is not set
# CONFIG_SENSORS_LM83 is not set
# CONFIG_SENSORS_LM85 is not set
# CONFIG_SENSORS_LM90 is not set
# CONFIG_SENSORS_MAX1619 is not set
# CONFIG_SENSORS_VIA686A is not set
CONFIG_SENSORS_W83781D=y
# CONFIG_SENSORS_W83L785TS is not set
# CONFIG_SENSORS_W83627HF is not set

#
# Other I2C Chip support
#
CONFIG_SENSORS_EEPROM=m
# CONFIG_SENSORS_PCF8574 is not set
# CONFIG_SENSORS_PCF8591 is not set
# CONFIG_SENSORS_RTC8564 is not set
CONFIG_I2C_DEBUG_CORE=y
CONFIG_I2C_DEBUG_ALGO=y
CONFIG_I2C_DEBUG_BUS=y
CONFIG_I2C_DEBUG_CHIP=y

#
# Misc devices
#
# CONFIG_IBM_ASM is not set

#
# Multimedia devices
#
CONFIG_VIDEO_DEV=y

#
# Video For Linux
#

#
# Video Adapters
#
CONFIG_VIDEO_BT848=m
# CONFIG_VIDEO_PMS is not set
# CONFIG_VIDEO_BWQCAM is not set
# CONFIG_VIDEO_CQCAM is not set
# CONFIG_VIDEO_W9966 is not set
# CONFIG_VIDEO_CPIA is not set
# CONFIG_VIDEO_SAA5246A is not set
# CONFIG_VIDEO_SAA5249 is not set
# CONFIG_TUNER_3036 is not set
# CONFIG_VIDEO_STRADIS is not set
# CONFIG_VIDEO_ZORAN is not set
# CONFIG_VIDEO_ZR36120 is not set
# CONFIG_VIDEO_SAA7134 is not set
# CONFIG_VIDEO_MXB is not set
# CONFIG_VIDEO_DPC is not set
# CONFIG_VIDEO_HEXIUM_ORION is not set
# CONFIG_VIDEO_HEXIUM_GEMINI is not set
# CONFIG_VIDEO_CX88 is not set

#
# Radio Adapters
#
# CONFIG_RADIO_CADET is not set
# CONFIG_RADIO_RTRACK is not set
# CONFIG_RADIO_RTRACK2 is not set
# CONFIG_RADIO_AZTECH is not set
# CONFIG_RADIO_GEMTEK is not set
# CONFIG_RADIO_GEMTEK_PCI is not set
# CONFIG_RADIO_MAXIRADIO is not set
# CONFIG_RADIO_MAESTRO is not set
# CONFIG_RADIO_SF16FMI is not set
# CONFIG_RADIO_SF16FMR2 is not set
# CONFIG_RADIO_TERRATEC is not set
# CONFIG_RADIO_TRUST is not set
# CONFIG_RADIO_TYPHOON is not set
# CONFIG_RADIO_ZOLTRIX is not set

#
# Digital Video Broadcasting Devices
#
# CONFIG_DVB is not set
CONFIG_VIDEO_TUNER=m
CONFIG_VIDEO_BUF=m
CONFIG_VIDEO_BTCX=m
CONFIG_VIDEO_IR=m

#
# Graphics support
#
CONFIG_FB=y
# CONFIG_FB_CIRRUS is not set
# CONFIG_FB_PM2 is not set
# CONFIG_FB_CYBER2000 is not set
# CONFIG_FB_ASILIANT is not set
# CONFIG_FB_IMSTT is not set
# CONFIG_FB_VGA16 is not set
# CONFIG_FB_VESA is not set
CONFIG_VIDEO_SELECT=y
# CONFIG_FB_HGA is not set
# CONFIG_FB_RIVA is not set
# CONFIG_FB_MATROX is not set
# CONFIG_FB_RADEON_OLD is not set
CONFIG_FB_RADEON=y
CONFIG_FB_RADEON_I2C=y
# CONFIG_FB_RADEON_DEBUG is not set
# CONFIG_FB_ATY128 is not set
# CONFIG_FB_ATY is not set
# CONFIG_FB_SIS is not set
# CONFIG_FB_NEOMAGIC is not set
# CONFIG_FB_KYRO is not set
# CONFIG_FB_3DFX is not set
# CONFIG_FB_VOODOO1 is not set
# CONFIG_FB_TRIDENT is not set
# CONFIG_FB_PM3 is not set
# CONFIG_FB_VIRTUAL is not set

#
# Console display driver support
#
CONFIG_VGA_CONSOLE=y
# CONFIG_MDA_CONSOLE is not set
CONFIG_DUMMY_CONSOLE=y
# CONFIG_FRAMEBUFFER_CONSOLE is not set

#
# Logo configuration
#
# CONFIG_LOGO is not set

#
# Sound
#
CONFIG_SOUND=y

#
# Advanced Linux Sound Architecture
#
CONFIG_SND=m
CONFIG_SND_TIMER=m
CONFIG_SND_PCM=m
CONFIG_SND_RAWMIDI=m
CONFIG_SND_SEQUENCER=m
# CONFIG_SND_SEQ_DUMMY is not set
CONFIG_SND_OSSEMUL=y
CONFIG_SND_MIXER_OSS=m
CONFIG_SND_PCM_OSS=m
CONFIG_SND_SEQUENCER_OSS=y
CONFIG_SND_RTCTIMER=m
# CONFIG_SND_VERBOSE_PRINTK is not set
# CONFIG_SND_DEBUG is not set

#
# Generic devices
#
CONFIG_SND_MPU401_UART=m
CONFIG_SND_DUMMY=m
CONFIG_SND_VIRMIDI=m
CONFIG_SND_MTPAV=m
# CONFIG_SND_SERIAL_U16550 is not set
CONFIG_SND_MPU401=m

#
# ISA devices
#
# CONFIG_SND_AD1816A is not set
# CONFIG_SND_AD1848 is not set
# CONFIG_SND_CS4231 is not set
# CONFIG_SND_CS4232 is not set
# CONFIG_SND_CS4236 is not set
# CONFIG_SND_ES968 is not set
# CONFIG_SND_ES1688 is not set
# CONFIG_SND_ES18XX is not set
# CONFIG_SND_GUSCLASSIC is not set
# CONFIG_SND_GUSEXTREME is not set
# CONFIG_SND_GUSMAX is not set
# CONFIG_SND_INTERWAVE is not set
# CONFIG_SND_INTERWAVE_STB is not set
# CONFIG_SND_OPTI92X_AD1848 is not set
# CONFIG_SND_OPTI92X_CS4231 is not set
# CONFIG_SND_OPTI93X is not set
# CONFIG_SND_SB8 is not set
# CONFIG_SND_SB16 is not set
# CONFIG_SND_SBAWE is not set
# CONFIG_SND_WAVEFRONT is not set
# CONFIG_SND_ALS100 is not set
# CONFIG_SND_AZT2320 is not set
# CONFIG_SND_CMI8330 is not set
# CONFIG_SND_DT019X is not set
# CONFIG_SND_OPL3SA2 is not set
# CONFIG_SND_SGALAXY is not set
# CONFIG_SND_SSCAPE is not set

#
# PCI devices
#
CONFIG_SND_AC97_CODEC=m
# CONFIG_SND_ALI5451 is not set
# CONFIG_SND_ATIIXP is not set
# CONFIG_SND_AU8810 is not set
# CONFIG_SND_AU8820 is not set
# CONFIG_SND_AU8830 is not set
# CONFIG_SND_AZT3328 is not set
CONFIG_SND_BT87X=m
# CONFIG_SND_CS46XX is not set
# CONFIG_SND_CS4281 is not set
# CONFIG_SND_EMU10K1 is not set
# CONFIG_SND_KORG1212 is not set
# CONFIG_SND_MIXART is not set
# CONFIG_SND_NM256 is not set
# CONFIG_SND_RME32 is not set
# CONFIG_SND_RME96 is not set
# CONFIG_SND_RME9652 is not set
# CONFIG_SND_HDSP is not set
# CONFIG_SND_TRIDENT is not set
# CONFIG_SND_YMFPCI is not set
# CONFIG_SND_ALS4000 is not set
# CONFIG_SND_CMIPCI is not set
# CONFIG_SND_ENS1370 is not set
# CONFIG_SND_ENS1371 is not set
# CONFIG_SND_ES1938 is not set
# CONFIG_SND_ES1968 is not set
# CONFIG_SND_MAESTRO3 is not set
# CONFIG_SND_FM801 is not set
# CONFIG_SND_ICE1712 is not set
# CONFIG_SND_ICE1724 is not set
CONFIG_SND_INTEL8X0=m
# CONFIG_SND_INTEL8X0M is not set
# CONFIG_SND_SONICVIBES is not set
# CONFIG_SND_VIA82XX is not set
# CONFIG_SND_VX222 is not set

#
# ALSA USB devices
#
# CONFIG_SND_USB_AUDIO is not set

#
# Open Sound System
#
# CONFIG_SOUND_PRIME is not set

#
# USB support
#
CONFIG_USB=y
# CONFIG_USB_DEBUG is not set

#
# Miscellaneous USB options
#
CONFIG_USB_DEVICEFS=y
# CONFIG_USB_BANDWIDTH is not set
# CONFIG_USB_DYNAMIC_MINORS is not set

#
# USB Host Controller Drivers
#
CONFIG_USB_EHCI_HCD=y
# CONFIG_USB_EHCI_SPLIT_ISO is not set
# CONFIG_USB_EHCI_ROOT_HUB_TT is not set
CONFIG_USB_OHCI_HCD=y
# CONFIG_USB_UHCI_HCD is not set

#
# USB Device Class drivers
#
# CONFIG_USB_AUDIO is not set
# CONFIG_USB_BLUETOOTH_TTY is not set
# CONFIG_USB_MIDI is not set
# CONFIG_USB_ACM is not set
CONFIG_USB_PRINTER=y
CONFIG_USB_STORAGE=y
# CONFIG_USB_STORAGE_DEBUG is not set
# CONFIG_USB_STORAGE_DATAFAB is not set
# CONFIG_USB_STORAGE_FREECOM is not set
# CONFIG_USB_STORAGE_ISD200 is not set
# CONFIG_USB_STORAGE_DPCM is not set
# CONFIG_USB_STORAGE_HP8200e is not set
# CONFIG_USB_STORAGE_SDDR09 is not set
# CONFIG_USB_STORAGE_SDDR55 is not set
# CONFIG_USB_STORAGE_JUMPSHOT is not set

#
# USB Human Interface Devices (HID)
#
CONFIG_USB_HID=y
CONFIG_USB_HIDINPUT=y
# CONFIG_HID_FF is not set
CONFIG_USB_HIDDEV=y
# CONFIG_USB_AIPTEK is not set
# CONFIG_USB_WACOM is not set
# CONFIG_USB_KBTAB is not set
# CONFIG_USB_POWERMATE is not set
# CONFIG_USB_MTOUCH is not set
# CONFIG_USB_EGALAX is not set
# CONFIG_USB_XPAD is not set
# CONFIG_USB_ATI_REMOTE is not set

#
# USB Imaging devices
#
# CONFIG_USB_MDC800 is not set
# CONFIG_USB_MICROTEK is not set
# CONFIG_USB_HPUSBSCSI is not set

#
# USB Multimedia devices
#
# CONFIG_USB_DABUSB is not set
# CONFIG_USB_VICAM is not set
# CONFIG_USB_DSBR is not set
# CONFIG_USB_IBMCAM is not set
# CONFIG_USB_KONICAWC is not set
# CONFIG_USB_OV511 is not set
# CONFIG_USB_PWC is not set
# CONFIG_USB_SE401 is not set
# CONFIG_USB_STV680 is not set
# CONFIG_USB_W9968CF is not set

#
# USB Network adaptors
#
# CONFIG_USB_CATC is not set
# CONFIG_USB_KAWETH is not set
# CONFIG_USB_PEGASUS is not set
# CONFIG_USB_RTL8150 is not set
# CONFIG_USB_USBNET is not set

#
# USB port drivers
#
# CONFIG_USB_USS720 is not set

#
# USB Serial Converter support
#
CONFIG_USB_SERIAL=y
# CONFIG_USB_SERIAL_DEBUG is not set
# CONFIG_USB_SERIAL_CONSOLE is not set
# CONFIG_USB_SERIAL_GENERIC is not set
# CONFIG_USB_SERIAL_BELKIN is not set
# CONFIG_USB_SERIAL_WHITEHEAT is not set
# CONFIG_USB_SERIAL_DIGI_ACCELEPORT is not set
# CONFIG_USB_SERIAL_EMPEG is not set
# CONFIG_USB_SERIAL_FTDI_SIO is not set
# CONFIG_USB_SERIAL_VISOR is not set
# CONFIG_USB_SERIAL_IPAQ is not set
# CONFIG_USB_SERIAL_IR is not set
# CONFIG_USB_SERIAL_EDGEPORT is not set
# CONFIG_USB_SERIAL_EDGEPORT_TI is not set
# CONFIG_USB_SERIAL_KEYSPAN_PDA is not set
# CONFIG_USB_SERIAL_KEYSPAN is not set
# CONFIG_USB_SERIAL_KLSI is not set
# CONFIG_USB_SERIAL_KOBIL_SCT is not set
# CONFIG_USB_SERIAL_MCT_U232 is not set
CONFIG_USB_SERIAL_PL2303=y
# CONFIG_USB_SERIAL_SAFE is not set
# CONFIG_USB_SERIAL_CYBERJACK is not set
# CONFIG_USB_SERIAL_XIRCOM is not set
# CONFIG_USB_SERIAL_OMNINET is not set

#
# USB Miscellaneous drivers
#
# CONFIG_USB_EMI62 is not set
# CONFIG_USB_EMI26 is not set
# CONFIG_USB_TIGL is not set
# CONFIG_USB_AUERSWALD is not set
# CONFIG_USB_RIO500 is not set
# CONFIG_USB_LEGOTOWER is not set
# CONFIG_USB_LCD is not set
# CONFIG_USB_LED is not set
# CONFIG_USB_CYTHERM is not set
# CONFIG_USB_PHIDGETSERVO is not set
# CONFIG_USB_TEST is not set

#
# USB Gadget Support
#
# CONFIG_USB_GADGET is not set

#
# File systems
#
CONFIG_EXT2_FS=y
# CONFIG_EXT2_FS_XATTR is not set
CONFIG_EXT3_FS=y
# CONFIG_EXT3_FS_XATTR is not set
CONFIG_JBD=y
# CONFIG_JBD_DEBUG is not set
# CONFIG_REISERFS_FS is not set
# CONFIG_JFS_FS is not set
# CONFIG_XFS_FS is not set
# CONFIG_MINIX_FS is not set
# CONFIG_ROMFS_FS is not set
# CONFIG_QUOTA is not set
# CONFIG_AUTOFS_FS is not set
CONFIG_AUTOFS4_FS=y

#
# CD-ROM/DVD Filesystems
#
CONFIG_ISO9660_FS=y
CONFIG_JOLIET=y
CONFIG_ZISOFS=y
CONFIG_ZISOFS_FS=y
CONFIG_UDF_FS=y

#
# DOS/FAT/NT Filesystems
#
CONFIG_FAT_FS=y
CONFIG_MSDOS_FS=y
CONFIG_VFAT_FS=y
# CONFIG_NTFS_FS is not set

#
# Pseudo filesystems
#
CONFIG_PROC_FS=y
CONFIG_PROC_KCORE=y
CONFIG_SYSFS=y
# CONFIG_DEVFS_FS is not set
# CONFIG_DEVPTS_FS_XATTR is not set
# CONFIG_TMPFS is not set
# CONFIG_HUGETLBFS is not set
# CONFIG_HUGETLB_PAGE is not set
CONFIG_RAMFS=y

#
# Miscellaneous filesystems
#
# CONFIG_ADFS_FS is not set
# CONFIG_AFFS_FS is not set
# CONFIG_HFS_FS is not set
# CONFIG_HFSPLUS_FS is not set
# CONFIG_BEFS_FS is not set
# CONFIG_BFS_FS is not set
# CONFIG_EFS_FS is not set
# CONFIG_CRAMFS is not set
# CONFIG_VXFS_FS is not set
# CONFIG_HPFS_FS is not set
# CONFIG_QNX4FS_FS is not set
# CONFIG_SYSV_FS is not set
# CONFIG_UFS_FS is not set

#
# Network File Systems
#
# CONFIG_NFS_FS is not set
# CONFIG_NFSD is not set
# CONFIG_EXPORTFS is not set
CONFIG_SMB_FS=y
# CONFIG_SMB_NLS_DEFAULT is not set
# CONFIG_CIFS is not set
# CONFIG_NCP_FS is not set
# CONFIG_CODA_FS is not set
# CONFIG_AFS_FS is not set

#
# Partition Types
#
# CONFIG_PARTITION_ADVANCED is not set
CONFIG_MSDOS_PARTITION=y

#
# Native Language Support
#
CONFIG_NLS=y
CONFIG_NLS_DEFAULT="iso8859-1"
CONFIG_NLS_CODEPAGE_437=y
CONFIG_NLS_CODEPAGE_737=m
CONFIG_NLS_CODEPAGE_775=m
CONFIG_NLS_CODEPAGE_850=m
CONFIG_NLS_CODEPAGE_852=m
CONFIG_NLS_CODEPAGE_855=m
CONFIG_NLS_CODEPAGE_857=m
CONFIG_NLS_CODEPAGE_860=m
CONFIG_NLS_CODEPAGE_861=m
CONFIG_NLS_CODEPAGE_862=m
CONFIG_NLS_CODEPAGE_863=m
CONFIG_NLS_CODEPAGE_864=m
CONFIG_NLS_CODEPAGE_865=m
CONFIG_NLS_CODEPAGE_866=m
CONFIG_NLS_CODEPAGE_869=m
CONFIG_NLS_CODEPAGE_936=m
CONFIG_NLS_CODEPAGE_950=m
CONFIG_NLS_CODEPAGE_932=m
CONFIG_NLS_CODEPAGE_949=m
CONFIG_NLS_CODEPAGE_874=m
CONFIG_NLS_ISO8859_8=m
CONFIG_NLS_CODEPAGE_1250=m
CONFIG_NLS_CODEPAGE_1251=m
CONFIG_NLS_ISO8859_1=y
CONFIG_NLS_ISO8859_2=m
CONFIG_NLS_ISO8859_3=m
CONFIG_NLS_ISO8859_4=m
CONFIG_NLS_ISO8859_5=m
CONFIG_NLS_ISO8859_6=m
CONFIG_NLS_ISO8859_7=m
CONFIG_NLS_ISO8859_9=m
CONFIG_NLS_ISO8859_13=m
CONFIG_NLS_ISO8859_14=m
CONFIG_NLS_ISO8859_15=m
CONFIG_NLS_KOI8_R=m
CONFIG_NLS_KOI8_U=m
CONFIG_NLS_UTF8=y

#
# Profiling support
#
# CONFIG_PROFILING is not set

#
# Kernel hacking
#
# CONFIG_DEBUG_KERNEL is not set
CONFIG_EARLY_PRINTK=y
# CONFIG_DEBUG_SPINLOCK_SLEEP is not set
# CONFIG_FRAME_POINTER is not set
CONFIG_4KSTACKS=y

#
# Security options
#
CONFIG_SECURITY=y
# CONFIG_SECURITY_NETWORK is not set
CONFIG_SECURITY_CAPABILITIES=y
# CONFIG_SECURITY_ROOTPLUG is not set
# CONFIG_SECURITY_SELINUX is not set

#
# Cryptographic options
#
# CONFIG_CRYPTO is not set

#
# Library routines
#
CONFIG_CRC32=y
CONFIG_LIBCRC32C=y
CONFIG_ZLIB_INFLATE=y
CONFIG_X86_BIOS_REBOOT=y
CONFIG_X86_STD_RESOURCES=y
CONFIG_PC=y