2.6.8-rc2 crash(s)?

2.6.8-rc2 crash(s)?

[Gene Heskett]

Greetings;

Machine is a new Biostar M7NCD-Pro mobo, with an athlon
2800 XP that says its a 2800 in the bootup so it not
overclocked, nor is it too warm, showing 125F right now.
It did take some non-default bios settings to achieve that,
the default running the memory as DDR333, but the cpu as
a 3200+, which understandably didn't always want to post!

Kernel is 2.6.8-rc2, with the forcedeth driver using the
builtin ethernet on this board.  The mobo has a Gig of ram
which signs on in the bios as
"DDR400 Dual Channel Mode Enabled (etc)"

I just re-entered the room from a few hours of other work,
and found this machine had apparently crashed.  I was not
able to ssh into it from the firewall, or make it respond
to the vulcan nerve pinch, so I hit the reset button and
waited for about 120G of hard drives to fsck.

This is the 2nd, or maybe the third time this has happened
since I put in this new mobo, which passes a half a days run
on memtest86 with no errors.  I *think* I've got the APIC
stuff turned off in the bios, and I'm not using it in the
kernel as I want this box to run 24/7.

The only screen blanker is a blank, black screen.

This is the only log entries made at what must have been its
untimely demise:
----------------------
Jul 24 15:37:39 coyote kernel: Unable to handle kernel paging request at virtual address 5f697461
Jul 24 15:37:39 coyote kernel:  printing eip:
Jul 24 15:37:39 coyote kernel: c0164376
Jul 24 15:37:39 coyote kernel: *pde = 00000000
Jul 24 15:37:39 coyote kernel: Oops: 0002 [#1]
Jul 24 15:37:39 coyote kernel: PREEMPT
Jul 24 15:37:39 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 8139too forcedeth sg
Jul 24 15:37:39 coyote kernel: CPU:    0
Jul 24 15:37:39 coyote kernel: EIP:    0060:[<c0164376>]    Not tainted
Jul 24 21:25:59 coyote syslogd 1.4.1: restart.
-----------------------
Previously, there was nothing in the logs at all, so this
trail is a first.

Is there anything of interest here?  What else can I supply
that might help aim a finger at something besides the operator,
who wasn't even in the room at the time :)

-- 
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 crash(s)?

[Gene Heskett]

On Saturday 24 July 2004 18:16, Denis Vlasenko wrote:
>On Sunday 25 July 2004 04:56, Gene Heskett wrote:
>> Greetings;
>>
>> Machine is a new Biostar M7NCD-Pro mobo, with an athlon
>> 2800 XP that says its a 2800 in the bootup so it not
>> overclocked, nor is it too warm, showing 125F right now.
>> It did take some non-default bios settings to achieve that,
>> the default running the memory as DDR333, but the cpu as
>> a 3200+, which understandably didn't always want to post!
>>
>> Kernel is 2.6.8-rc2, with the forcedeth driver using the
>> builtin ethernet on this board.  The mobo has a Gig of ram
>> which signs on in the bios as
>> "DDR400 Dual Channel Mode Enabled (etc)"
>>
>> I just re-entered the room from a few hours of other work,
>> and found this machine had apparently crashed.  I was not
>> able to ssh into it from the firewall, or make it respond
>> to the vulcan nerve pinch, so I hit the reset button and
>> waited for about 120G of hard drives to fsck.
>>
>> This is the 2nd, or maybe the third time this has happened
>> since I put in this new mobo, which passes a half a days run
>> on memtest86 with no errors.  I *think* I've got the APIC
>> stuff turned off in the bios, and I'm not using it in the
>> kernel as I want this box to run 24/7.
>>
>> The only screen blanker is a blank, black screen.
>>
>> This is the only log entries made at what must have been its
>> untimely demise:
>> ----------------------
>> Jul 24 15:37:39 coyote kernel: Unable to handle kernel paging
>> request at virtual address 5f697461 Jul 24 15:37:39 coyote kernel:
>>  printing eip: Jul 24 15:37:39 coyote kernel: c0164376
>> Jul 24 15:37:39 coyote kernel: *pde = 00000000
>> Jul 24 15:37:39 coyote kernel: Oops: 0002 [#1]
>> Jul 24 15:37:39 coyote kernel: PREEMPT
>> Jul 24 15:37:39 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 8139too forcedeth sg Jul 24
>> 15:37:39 coyote kernel: CPU:    0 Jul 24 15:37:39 coyote kernel:
>> EIP:    0060:[<c0164376>]    Not tainted Jul 24 21:25:59 coyote
>> syslogd 1.4.1: restart.
>> -----------------------
>> Previously, there was nothing in the logs at all, so this
>> trail is a first.
>>
>> Is there anything of interest here?  What else can I supply
>> that might help aim a finger at something besides the operator,
>> who wasn't even in the room at the time :)
>
>Not much... at least you can look up that EIP in System.map.
>Also, do you really need all that sound stuff?

It seems to all come in with the main driver for the ALC650.  And it 
works pretty good once i got it figured out.  Everything but the 
bt878 audio, which is so far down the s/s+n isn't more than 30 db.

>Also, try to slightly underclock your system and see whether
>that will help.

>--
>vda
c0164376 isn't a label, but its in between these two in the System.map
c0164340 t prune_dcache
c0164500 T shrink_dcache_sb

But thats all I can deduce from here.

I CC:'d this back to the list in case those two labels might mean 
something to someone else.

Thanks

-- 
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 crash(s)?

[Gene Heskett]

On Sunday 25 July 2004 00:12, Gene Heskett wrote:
>On Saturday 24 July 2004 18:16, Denis Vlasenko wrote:
>>On Sunday 25 July 2004 04:56, Gene Heskett wrote:
>>> Greetings;
>>>
>>> Machine is a new Biostar M7NCD-Pro mobo, with an athlon
>>> 2800 XP that says its a 2800 in the bootup so it not
>>> overclocked, nor is it too warm, showing 125F right now.
>>> It did take some non-default bios settings to achieve that,
>>> the default running the memory as DDR333, but the cpu as
>>> a 3200+, which understandably didn't always want to post!
>>>
>>> Kernel is 2.6.8-rc2, with the forcedeth driver using the
>>> builtin ethernet on this board.  The mobo has a Gig of ram
>>> which signs on in the bios as
>>> "DDR400 Dual Channel Mode Enabled (etc)"
>>>
[snip crash details]
>>>
>>> This is the only log entries made at what must have been its
>>> untimely demise:
>>> ----------------------
>>> Jul 24 15:37:39 coyote kernel: Unable to handle kernel paging
>>> request at virtual address 5f697461 Jul 24 15:37:39 coyote
>>> kernel: printing eip: Jul 24 15:37:39 coyote kernel: c0164376
>>> Jul 24 15:37:39 coyote kernel: *pde = 00000000
>>> Jul 24 15:37:39 coyote kernel: Oops: 0002 [#1]
>>> Jul 24 15:37:39 coyote kernel: PREEMPT
>>> Jul 24 15:37:39 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 8139too forcedeth sg Jul 24
>>> 15:37:39 coyote kernel: CPU:    0 Jul 24 15:37:39 coyote kernel:
>>> EIP:    0060:[<c0164376>]    Not tainted Jul 24 21:25:59 coyote
>>> syslogd 1.4.1: restart.
>>> -----------------------
>>> Previously, there was nothing in the logs at all, so this
>>> trail is a first.
>>>
>>> Is there anything of interest here?  What else can I supply
>>> that might help aim a finger at something besides the operator,
>>> who wasn't even in the room at the time :)
>>
>>Not much... at least you can look up that EIP in System.map.
>>Also, do you really need all that sound stuff?
>
>It seems to all come in with the main driver for the ALC650.  And it
>works pretty good once i got it figured out.  Everything but the
>bt878 audio, which is so far down the s/s+n isn't more than 30 db.
>
>>Also, try to slightly underclock your system and see whether
>>that will help.
>>
>>--
>>vda
>
>c0164376 isn't a label, but its in between these two in the
> System.map c0164340 t prune_dcache
>c0164500 T shrink_dcache_sb
>
>But thats all I can deduce from here.
>
>I CC:'d this back to the list in case those two labels might mean
>something to someone else.
>
>Thanks

Update, it looks as if this new mobo is a bit much for the 350 watt 
supply in this case, the +5 volt line is wandering around a couple of 
hundred millivolts, centered on about 4.86 volts.  IMO thats not 
enough, particularly since its wandering around under load.

Would everyone agree?


-- 
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 crash(s)?

[William Lee Irwin III]

On Sun, Jul 25, 2004 at 12:37:51AM -0400, Gene Heskett wrote:
> Update, it looks as if this new mobo is a bit much for the 350 watt 
> supply in this case, the +5 volt line is wandering around a couple of 
> hundred millivolts, centered on about 4.86 volts.  IMO thats not 
> enough, particularly since its wandering around under load.
> Would everyone agree?

This is a somewhat intense audit of potential hardware-related issues.
What behavior have you observed that has led you to believe there may
be hardware problems affecting your situation?


-- wli

Re: 2.6.8-rc2 crash(s)?

[Gene Heskett]

On Wednesday 28 July 2004 20:12, William Lee Irwin III wrote:
>On Sun, Jul 25, 2004 at 12:37:51AM -0400, Gene Heskett wrote:
>> Update, it looks as if this new mobo is a bit much for the 350
>> watt supply in this case, the +5 volt line is wandering around a
>> couple of hundred millivolts, centered on about 4.86 volts.  IMO
>> thats not enough, particularly since its wandering around under
>> load. Would everyone agree?
>
>This is a somewhat intense audit of potential hardware-related
> issues. What behavior have you observed that has led you to believe
> there may be hardware problems affecting your situation?
>
This message is now a bit old, William. 

I was watching the psu voltages via gkrellm, and was seeing the 5 volt 
line go from 4.89, down to 4.73 in consecutive readings.  The new 420 
watt Antec, seems to be steadier at 4.87 +- 0.03 or so.

I suspect the tap point for the xx83627 chips input may not be right 
at the psu connector on the mobo cause I suspect the supply itself is 
probably doing 5.05 or so, although I haven't dropped my DVM on the 
line to test, its rather buried behind the drive cage.  But lemme go 
hit a drive power connector since there are spares on this psu, brb.  

Yeah, at a drive cables middle connector, with a small load on the 
end, its sitting at 5.00 volts, solid as a rock.  This supply has 
seperate regulators for the 5 volt, and 3.3 volt lines where the 
older one regulated everything against the 5 volt by turns ratios on 
the transformer, and was only a 300 watter, with 2 hd's, 2 floppy's 
and a dvd writer in addition to the motherboard load.

Anything else a C.E.T. can get for you?

-- 
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 crash(s)?

[William Lee Irwin III]

On Wed, Jul 28, 2004 at 08:59:03PM -0400, Gene Heskett wrote:
> This message is now a bit old, William. 
> I was watching the psu voltages via gkrellm, and was seeing the 5 volt 
> line go from 4.89, down to 4.73 in consecutive readings.  The new 420 
> watt Antec, seems to be steadier at 4.87 +- 0.03 or so.
> I suspect the tap point for the xx83627 chips input may not be right 
> at the psu connector on the mobo cause I suspect the supply itself is 
> probably doing 5.05 or so, although I haven't dropped my DVM on the 
> line to test, its rather buried behind the drive cage.  But lemme go 
> hit a drive power connector since there are spares on this psu, brb.  
> Yeah, at a drive cables middle connector, with a small load on the 
> end, its sitting at 5.00 volts, solid as a rock.  This supply has 
> seperate regulators for the 5 volt, and 3.3 volt lines where the 
> older one regulated everything against the 5 volt by turns ratios on 
> the transformer, and was only a 300 watter, with 2 hd's, 2 floppy's 
> and a dvd writer in addition to the motherboard load.
> Anything else a C.E.T. can get for you?

The question is really whether all this is actually causing observable
kernel/cpu/device failures.


-- wli

Re: 2.6.8-rc2 crash(s)?

[Gene Heskett]

On Wednesday 28 July 2004 21:03, William Lee Irwin III wrote:
>On Wed, Jul 28, 2004 at 08:59:03PM -0400, Gene Heskett wrote:
>> This message is now a bit old, William.
>> I was watching the psu voltages via gkrellm, and was seeing the 5
>> volt line go from 4.89, down to 4.73 in consecutive readings.  The
>> new 420 watt Antec, seems to be steadier at 4.87 +- 0.03 or so.
>> I suspect the tap point for the xx83627 chips input may not be
>> right at the psu connector on the mobo cause I suspect the supply
>> itself is probably doing 5.05 or so, although I haven't dropped my
>> DVM on the line to test, its rather buried behind the drive cage. 
>> But lemme go hit a drive power connector since there are spares on
>> this psu, brb. Yeah, at a drive cables middle connector, with a
>> small load on the end, its sitting at 5.00 volts, solid as a rock.
>>  This supply has seperate regulators for the 5 volt, and 3.3 volt
>> lines where the older one regulated everything against the 5 volt
>> by turns ratios on the transformer, and was only a 300 watter,
>> with 2 hd's, 2 floppy's and a dvd writer in addition to the
>> motherboard load.
>> Anything else a C.E.T. can get for you?
>
>The question is really whether all this is actually causing
> observable kernel/cpu/device failures.
>
Well, at this point, I've 'shotgunned' just about everything.  Mobo, 
cpu, memory and psu now.    And a fresh ATI (Xtacy made) 9200SE video 
card, the old nvidia failed and apparently compromised something on 
the old Biostar M7VIB mobo as it was going.  Its now a Biostar 
M7NCD-Pro, with a 2800XP athlon replaceing the 1400XP on the old 
board.   The new memory, 2 sticks of 512Mb, is DDR400 rated.  And I 
just built, and am booted to, 2.6.7.  I'll see how long it stays up.

And despite all this trouble, I'm once again slowly climbing in the 
seti@home ranks :-)

>-- wli

-- 
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 crash(s)?

[Gene Heskett]

On Sunday 25 July 2004 02:09, Denis Vlasenko wrote:
>On Sunday 25 July 2004 07:12, Gene Heskett wrote:
>> >Not much... at least you can look up that EIP in System.map.
>> >Also, do you really need all that sound stuff?
>>
>> It seems to all come in with the main driver for the ALC650.  And
>> it works pretty good once i got it figured out.  Everything but
>> the bt878 audio, which is so far down the s/s+n isn't more than 30
>> db.
>
>I meant "do not use it and see whether that helps".
>
>> c0164376 isn't a label, but its in between these two in the
>> System.map c0164340 t prune_dcache
>> c0164500 T shrink_dcache_sb
>>
>> But thats all I can deduce from here.
>
>Of course, it points _inside_ prune_dcache(), not at the very
>first instruction of it.
>
>Do:
>
>objdump -d <file containing prune_dcache>.o >file.objdump

Humm, maybe I missunderstand you:
[root@coyote linux-2.6.8-rc2-nf2]# objdump -d 
</boot/vmlinuz-2.6.8-rc2-nf2>.o >file.objdump
objdump: a.out: No such file or directory

So I grepped to locate dcache.o (its in the fs subdir) but its still 
an error:
----------------
[root@coyote fs]# objdump -d <dcache.o >file.objdump
objdump: a.out: No such file or directory
------------------
and it (dcache.o) does exist.  What am I doing wrong?

>and
>make path/to/<file containing prune_dcache>.s
>
>and using resulting .objdump and .s files, find exact
>instruction and C code line where it died.
>--
>vda

-- 
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 crash(s)?

[Kyle Moffett]

On Jul 25, 2004, at 09:43, Gene Heskett wrote:
> Humm, maybe I missunderstand you:
> [root@coyote linux-2.6.8-rc2-nf2]# objdump -d
> </boot/vmlinuz-2.6.8-rc2-nf2>.o >file.objdump
> objdump: a.out: No such file or directory

Heh.  You aren't supposed to put the angle-brackets around the file.
The shell reads this like thie following:
# cat '/boot/vmlinux-2.6.8-rc2-nfs>.o' | objdump -d >file.objdump..
Then objdump doesn't get an input file, so it looks for the default
input file, "a.out", which it can't find.  Just write it like the 
following:
# objdump -d /boot/vmlinux-2.6.8-rc2-nf2 >file.objdump
Or the following:
# objdump -d dcache.o >file.objdump

Cheers,
Kyle Moffett

-----BEGIN GEEK CODE BLOCK-----
Version: 3.12
GCM/CS/IT/U d- s++: a17 C++++>$ UB/L/X/*++++(+)>$ P+++(++++)>$
L++++(+++) E W++(+) N+++(++) o? K? w--- O? M++ V? PS+() PE+(-) Y+
PGP+++ t+(+++) 5 X R? tv-(--) b++++(++) DI+ D+ G e->++++$ h!*()>++$ r  
!y?(-)
------END GEEK CODE BLOCK------

Re: 2.6.8-rc2 crash(s)?

[Gene Heskett]

On Sunday 25 July 2004 12:38, Kyle Moffett wrote:
>On Jul 25, 2004, at 09:43, Gene Heskett wrote:
>> Humm, maybe I missunderstand you:
>> [root@coyote linux-2.6.8-rc2-nf2]# objdump -d
>> </boot/vmlinuz-2.6.8-rc2-nf2>.o >file.objdump
>> objdump: a.out: No such file or directory
>
>Heh.  You aren't supposed to put the angle-brackets around the file.
>The shell reads this like thie following:
># cat '/boot/vmlinux-2.6.8-rc2-nfs>.o' | objdump -d >file.objdump..
>Then objdump doesn't get an input file, so it looks for the default
>input file, "a.out", which it can't find.  Just write it like the
>following:
># objdump -d /boot/vmlinux-2.6.8-rc2-nf2 >file.objdump
>Or the following:
># objdump -d dcache.o >file.objdump

I'll do the latter, the result should be a heck of a lot smaller.  
But, after I've chased the lawn mower around for a couple of hours 
while a new psu gets the stink blown out of it and all over the 
house.  This yard place is beginning to look like a tarzan 
movie.  :-)

>
>Cheers,
>Kyle Moffett
>
>-----BEGIN GEEK CODE BLOCK-----
>Version: 3.12
>GCM/CS/IT/U d- s++: a17 C++++>$ UB/L/X/*++++(+)>$ P+++(++++)>$
>L++++(+++) E W++(+) N+++(++) o? K? w--- O? M++ V? PS+() PE+(-) Y+
>PGP+++ t+(+++) 5 X R? tv-(--) b++++(++) DI+ D+ G e->++++$ h!*()>++$
> r !y?(-)
>------END GEEK CODE BLOCK------

-- 
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 crash(s)?

[Gene Heskett]

On Sunday 25 July 2004 02:09, Denis Vlasenko wrote:
>On Sunday 25 July 2004 07:12, Gene Heskett wrote:
>> >Not much... at least you can look up that EIP in System.map.
>> >Also, do you really need all that sound stuff?
>>
>> It seems to all come in with the main driver for the ALC650.  And
>> it works pretty good once i got it figured out.  Everything but
>> the bt878 audio, which is so far down the s/s+n isn't more than 30
>> db.
>
>I meant "do not use it and see whether that helps".
>
>> c0164376 isn't a label, but its in between these two in the
>> System.map c0164340 t prune_dcache
>> c0164500 T shrink_dcache_sb
>>
>> But thats all I can deduce from here.
>
>Of course, it points _inside_ prune_dcache(), not at the very
>first instruction of it.
>
>Do:
>
>objdump -d <file containing prune_dcache>.o >file.objdump

This worked rather nicely and I have a rather large dcacheDOTo.txt 
file now.

>and
>make path/to/<file containing prune_dcache>.s

But this ones still being difficult.  Make does want to generate it.  
At best it claims that dcache.o is uptodate. I don't figure one file 
is worth much without the other, so whats wrong with my syntax?
[root@coyote fs]# make dcache.c>.s
[root@coyote fs]# less .s
Which contains "make: Nothing to be done for `dcache.c'."

The vanishing post contained my .config for a 2.6.7 kernel, which had 
a log snip of a very similar Oops but without the total crash.  That 
at least is a quite measureable improvement.

So obviously I'm not understanding your use of the <> arrows yet.

Now, since my last post, which so far in about 8 hours, has not come 
back from the list, I've run memtest86-3.1a for 12 full passes thru 
this gigabyte of ram with no errors reported.  I've also gone thru 
the init.d directory shutting off things that it doesn't appear are 
of any use to me.

And, I've got a tail running on the log in another window.

>and using resulting .objdump and .s files, find exact
>instruction and C code line where it died.

-- 
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 crash(s)?

[Randy.Dunlap]

On Thu, 29 Jul 2004 18:22:47 -0400 Gene Heskett wrote:

| On Sunday 25 July 2004 02:09, Denis Vlasenko wrote:
| >On Sunday 25 July 2004 07:12, Gene Heskett wrote:
| >> >Not much... at least you can look up that EIP in System.map.
| >> >Also, do you really need all that sound stuff?
| >>
| >> It seems to all come in with the main driver for the ALC650.  And
| >> it works pretty good once i got it figured out.  Everything but
| >> the bt878 audio, which is so far down the s/s+n isn't more than 30
| >> db.
| >
| >I meant "do not use it and see whether that helps".
| >
| >> c0164376 isn't a label, but its in between these two in the
| >> System.map c0164340 t prune_dcache
| >> c0164500 T shrink_dcache_sb
| >>
| >> But thats all I can deduce from here.
| >
| >Of course, it points _inside_ prune_dcache(), not at the very
| >first instruction of it.
| >
| >Do:
| >
| >objdump -d <file containing prune_dcache>.o >file.objdump
| 
| This worked rather nicely and I have a rather large dcacheDOTo.txt 
| file now.
| 
| >and
| >make path/to/<file containing prune_dcache>.s
| 
| But this ones still being difficult.  Make does want to generate it.  
| At best it claims that dcache.o is uptodate. I don't figure one file 
| is worth much without the other, so whats wrong with my syntax?
| [root@coyote fs]# make dcache.c>.s
| [root@coyote fs]# less .s
| Which contains "make: Nothing to be done for `dcache.c'."

This should be (without < > brackets):

make fs/dcache.s

or whatever directory it (dcache.c) is in.

| The vanishing post contained my .config for a 2.6.7 kernel, which had 
| a log snip of a very similar Oops but without the total crash.  That 
| at least is a quite measureable improvement.
| 
| So obviously I'm not understanding your use of the <> arrows yet.

They just bracket metadata or descriptive terms.  Take out the
angle brackets when you substitute live words there.

| Now, since my last post, which so far in about 8 hours, has not come 
| back from the list, I've run memtest86-3.1a for 12 full passes thru 
| this gigabyte of ram with no errors reported.  I've also gone thru 
| the init.d directory shutting off things that it doesn't appear are 
| of any use to me.
| 
| And, I've got a tail running on the log in another window.
| 
| >and using resulting .objdump and .s files, find exact
| >instruction and C code line where it died.


--
~Randy

Re: 2.6.8-rc2 crash(s)?

[Gene Heskett]

On Thursday 29 July 2004 18:14, Randy.Dunlap wrote:
[...]
I've gone clear back to a 2.6.7 kernel because thats the newest one 
that has a diff when cmp'ing fs/dcache.c files to whats in 2.6.8-rc2.

I've had one Oops, virtually the same one, but it didn't kill the 
machine like it would have if I was running 2.6.8-rc2.
>| >and
>| >make path/to/<file containing prune_dcache>.s
>|
>| But this ones still being difficult.  Make does want to generate
>| it. At best it claims that dcache.o is uptodate. I don't figure
>| one file is worth much without the other, so whats wrong with my
>| syntax? [root@coyote fs]# make dcache.c>.s
>| [root@coyote fs]# less .s
>| Which contains "make: Nothing to be done for `dcache.c'."
>
>This should be (without < > brackets):
>
>make fs/dcache.s

Aha!  Voila!! It doesn't work in the "fs" subdir, but back out to the 
top of the src tree and it works just fine.  Duh...

Now, I must confess that what I'm looking at in those two files is 
the .s is the source assembly that would normally be fed to gas, and 
the objdump'ed version is the dissed object translated back to gas 
source.  If no mistakes, they should be pretty close to the same I'd 
think.  Am I on the right track?  Or full of it?

Here's the theory thats gradually formed in whats left of my mind:
--------------
5 things changed in the kernel soft when I changed the mobo.
1. The ide driver, from via686a to the nforce2 version.
2. The video driver, because the old card failed and took the mobo 
with it.
3. Ethernet driver is now forcedeth instead of rtl-8139too
4. A different alsa driver, from via8233 to intel-8x0
5. The 4Gb switch is turned on in the kernel now as theres a gig of 
ram on this board.
--------------

I can't do anything about the first 2, but I can do without the last 
200 megs of ram long enough to test that, and I can switch back to 
the rtl-8139too card for ethernet, and I can turn off alsasound.

In the meantime I turned a bunch of stuff the logs were complaining 
about off, like sgi_fam (what the heck is that?), some ups daemons 
for brands I don't have, that sort of thing, and have a tail running 
on the log.  So far, its clean since the restart of xinetd.  Another 
16 hours will tell most of the tale for this particular instant 
configuration.

One final question if I may:  What do I turn off (or on) in the video 
dept of the kernel so that my screen doesn't go black after vmlinuz 
is unpacked, and not come back on till "init" is run, at which point 
the screen comes back on in what looks to be exactly the same mode?

Anything that goes on in that time period must be read 
from /var/log/dmesg later if I want to see it.

>--
>~Randy

-- 
Cheers Randy, 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 crash(s)?

[Randy.Dunlap]

On Thu, 29 Jul 2004 21:47:21 -0400 Gene Heskett wrote:

| On Thursday 29 July 2004 18:14, Randy.Dunlap wrote:
| [...]
| I've gone clear back to a 2.6.7 kernel because thats the newest one 
| that has a diff when cmp'ing fs/dcache.c files to whats in 2.6.8-rc2.
| 
| I've had one Oops, virtually the same one, but it didn't kill the 
| machine like it would have if I was running 2.6.8-rc2.

Yeah, oopsen often don't kill the entire machine.

| >make fs/dcache.s
| 
| Aha!  Voila!! It doesn't work in the "fs" subdir, but back out to the 
| top of the src tree and it works just fine.  Duh...

Right, it needs the top-level makfile and kbuild machinery to do that.

| Now, I must confess that what I'm looking at in those two files is 
| the .s is the source assembly that would normally be fed to gas, and 
| the objdump'ed version is the dissed object translated back to gas 
| source.  If no mistakes, they should be pretty close to the same I'd 
| think.  Am I on the right track?  Or full of it?

Yes, right.

| Here's the theory thats gradually formed in whats left of my mind:
| --------------
| 5 things changed in the kernel soft when I changed the mobo.
| 1. The ide driver, from via686a to the nforce2 version.
| 2. The video driver, because the old card failed and took the mobo 
| with it.
| 3. Ethernet driver is now forcedeth instead of rtl-8139too
| 4. A different alsa driver, from via8233 to intel-8x0
| 5. The 4Gb switch is turned on in the kernel now as theres a gig of 
| ram on this board.
| --------------

You can easily use a non-high-memory enabled kernel.  It will still
use 896 MB of RAM (IIRC).  Enabling highmem gets you another 128 MB.

IDE and video are somewhat important, no?
But the ethernet and ALSA drivers should be optional, at least for some
testing... Ha, you said that below!

| I can't do anything about the first 2, but I can do without the last 
| 200 megs of ram long enough to test that, and I can switch back to 
| the rtl-8139too card for ethernet, and I can turn off alsasound.
| 
| In the meantime I turned a bunch of stuff the logs were complaining 
| about off, like sgi_fam (what the heck is that?), some ups daemons 

FAM is File Alteration Monitor, from SGI:
  http://oss.sgi.com/projects/fam/

| for brands I don't have, that sort of thing, and have a tail running 
| on the log.  So far, its clean since the restart of xinetd.  Another 
| 16 hours will tell most of the tale for this particular instant 
| configuration.
| 
| One final question if I may:  What do I turn off (or on) in the video 
| dept of the kernel so that my screen doesn't go black after vmlinuz 
| is unpacked, and not come back on till "init" is run, at which point 
| the screen comes back on in what looks to be exactly the same mode?

Hm, do you have a serial console enabled (in the kernel config and in your
kernel command line)?  If not, please send your .config file (your probably
did, but I'm lost in the maze of emails).

| Anything that goes on in that time period must be read 
| from /var/log/dmesg later if I want to see it.

--
~Randy

Re: 2.6.8-rc2 crash(s)?

[Gene Heskett]

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

On Thursday 29 July 2004 23:36, Randy.Dunlap wrote:
>On Thu, 29 Jul 2004 21:47:21 -0400 Gene Heskett wrote:
>| On Thursday 29 July 2004 18:14, Randy.Dunlap wrote:
>| [...]
>| I've gone clear back to a 2.6.7 kernel because thats the newest
>| one that has a diff when cmp'ing fs/dcache.c files to whats in
>| 2.6.8-rc2.
>|
>| I've had one Oops, virtually the same one, but it didn't kill the
>| machine like it would have if I was running 2.6.8-rc2.
>
>Yeah, oopsen often don't kill the entire machine.

Running 2.6.8-rc2 it sure did, deader than a doornail.  X's clock 
stopped, the whole maryann.  Keyboard leds off.  Had to use the reset 
button, and once or twice I had to do a full powerdown before it 
would enter post and reboot.  Then sit thru 20+ minutes of e2fscking 
all the drives of course.

>| >make fs/dcache.s
>|
>| Aha!  Voila!! It doesn't work in the "fs" subdir, but back out to
>| the top of the src tree and it works just fine.  Duh...
>
>Right, it needs the top-level makfile and kbuild machinery to do
> that.
>
>| Now, I must confess that what I'm looking at in those two files is
>| the .s is the source assembly that would normally be fed to gas,
>| and the objdump'ed version is the dissed object translated back to
>| gas source.  If no mistakes, they should be pretty close to the
>| same I'd think.  Am I on the right track?  Or full of it?
>
>Yes, right.

Which?

Right track, or full of it? :-)

In any event, I could send those two files along if you'd like, I'm 
not an assembly guru on "amd/intel" chips, not even in my wildest 
dreams .

>| Here's the theory thats gradually formed in whats left of my mind:
>| --------------
>| 5 things changed in the kernel soft when I changed the mobo.
>| 1. The ide driver, from via686a to the nforce2 version.
>| 2. The video driver, because the old card failed and took the mobo
>| with it.
>| 3. Ethernet driver is now forcedeth instead of rtl-8139too
>| 4. A different alsa driver, from via8233 to intel-8x0
>| 5. The 4Gb switch is turned on in the kernel now as theres a gig
>| of ram on this board.
>| --------------
>
>You can easily use a non-high-memory enabled kernel.  It will still
>use 896 MB of RAM (IIRC).  Enabling highmem gets you another 128 MB.
>
>IDE and video are somewhat important, no?
>But the ethernet and ALSA drivers should be optional, at least for
> some testing... Ha, you said that below!
>
>| I can't do anything about the first 2, but I can do without the
>| last 200 megs of ram long enough to test that, and I can switch
>| back to the rtl-8139too card for ethernet, and I can turn off
>| alsasound.
>|
>| In the meantime I turned a bunch of stuff the logs were
>| complaining about off, like sgi_fam (what the heck is that?), some
>| ups daemons
>
>FAM is File Alteration Monitor, from SGI:
>  http://oss.sgi.com/projects/fam/

So I should start it back up?  Its a security tool?, or a system 
watchdog (or both?)

>| for brands I don't have, that sort of thing, and have a tail
>| running on the log.  So far, its clean since the restart of
>| xinetd.  Another 16 hours will tell most of the tale for this
>| particular instant configuration.

I just had mozilla try to display an rpm or tgz file, killed X, so the 
log got filled up a bit.  Odd, I haven't had to step on the shift key 
before clicking a download link in ages.  Trying to get a newer 
version of ymessenger.  I have an old beta version and yahoo says its 
too old.
 
>| One final question if I may:  What do I turn off (or on) in the
>| video dept of the kernel so that my screen doesn't go black after
>| vmlinuz is unpacked, and not come back on till "init" is run, at
>| which point the screen comes back on in what looks to be exactly
>| the same mode?
>
>Hm, do you have a serial console enabled (in the kernel config and
> in your kernel command line)?  If not, please send your .config
> file (your probably did, but I'm lost in the maze of emails).

Not that I can find, and I'm restricted to a make menuconfig, xconfig 
is broken because its not seeing the correct libqt-mt library.  Its 
complaining about the version in kde3.2.3, but all the env stuff now 
points it to kde3.3-beta2.  How can I cause that to get refreshed for 
the newer libraries now installed?

I'll attach the 2.6.7 .config.

>
>| Anything that goes on in that time period must be read
>| from /var/log/dmesg later if I want to see it.
>
>--
>~Randy

-- 
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

Re: 2.6.8-rc2 crash(s)?

[Randy.Dunlap]

On Fri, 30 Jul 2004 00:50:53 -0400 Gene Heskett wrote:

| On Thursday 29 July 2004 23:36, Randy.Dunlap wrote:
| >On Thu, 29 Jul 2004 21:47:21 -0400 Gene Heskett wrote:
| >| On Thursday 29 July 2004 18:14, Randy.Dunlap wrote:
| >| [...]
| >| I've gone clear back to a 2.6.7 kernel because thats the newest
| >| one that has a diff when cmp'ing fs/dcache.c files to whats in
| >| 2.6.8-rc2.
| >|
| >| I've had one Oops, virtually the same one, but it didn't kill the
| >| machine like it would have if I was running 2.6.8-rc2.
| >
| >Yeah, oopsen often don't kill the entire machine.
| 
| Running 2.6.8-rc2 it sure did, deader than a doornail.  X's clock 
| stopped, the whole maryann.  Keyboard leds off.  Had to use the reset 
| button, and once or twice I had to do a full powerdown before it 
| would enter post and reboot.  Then sit thru 20+ minutes of e2fscking 
| all the drives of course.
| 
| >| >make fs/dcache.s
| >|
| >| Aha!  Voila!! It doesn't work in the "fs" subdir, but back out to
| >| the top of the src tree and it works just fine.  Duh...
| >
| >Right, it needs the top-level makfile and kbuild machinery to do
| > that.
| >
| >| Now, I must confess that what I'm looking at in those two files is
| >| the .s is the source assembly that would normally be fed to gas,
| >| and the objdump'ed version is the dissed object translated back to
| >| gas source.  If no mistakes, they should be pretty close to the
| >| same I'd think.  Am I on the right track?  Or full of it?
| >
| >Yes, right.
| 
| Which?
| 
| Right track, or full of it? :-)

Right track.  ;)

| In any event, I could send those two files along if you'd like, I'm 
| not an assembly guru on "amd/intel" chips, not even in my wildest 
| dreams .
| 
| >| Here's the theory thats gradually formed in whats left of my mind:
| >| --------------
| >| 5 things changed in the kernel soft when I changed the mobo.
| >| 1. The ide driver, from via686a to the nforce2 version.
| >| 2. The video driver, because the old card failed and took the mobo
| >| with it.
| >| 3. Ethernet driver is now forcedeth instead of rtl-8139too
| >| 4. A different alsa driver, from via8233 to intel-8x0
| >| 5. The 4Gb switch is turned on in the kernel now as theres a gig
| >| of ram on this board.
| >| --------------
| >
| >You can easily use a non-high-memory enabled kernel.  It will still
| >use 896 MB of RAM (IIRC).  Enabling highmem gets you another 128 MB.
| >
| >IDE and video are somewhat important, no?
| >But the ethernet and ALSA drivers should be optional, at least for
| > some testing... Ha, you said that below!
| >
| >| I can't do anything about the first 2, but I can do without the
| >| last 200 megs of ram long enough to test that, and I can switch
| >| back to the rtl-8139too card for ethernet, and I can turn off
| >| alsasound.
| >|
| >| In the meantime I turned a bunch of stuff the logs were
| >| complaining about off, like sgi_fam (what the heck is that?), some
| >| ups daemons
| >
| >FAM is File Alteration Monitor, from SGI:
| >  http://oss.sgi.com/projects/fam/
| 
| So I should start it back up?  Its a security tool?, or a system 
| watchdog (or both?)

No, you probably don't need it.  Depends on your apps/usage,
but it's certainly not _required_.

| >| for brands I don't have, that sort of thing, and have a tail
| >| running on the log.  So far, its clean since the restart of
| >| xinetd.  Another 16 hours will tell most of the tale for this
| >| particular instant configuration.
| 
| I just had mozilla try to display an rpm or tgz file, killed X, so the 
| log got filled up a bit.  Odd, I haven't had to step on the shift key 
| before clicking a download link in ages.  Trying to get a newer 
| version of ymessenger.  I have an old beta version and yahoo says its 
| too old.
|  
| >| One final question if I may:  What do I turn off (or on) in the
| >| video dept of the kernel so that my screen doesn't go black after
| >| vmlinuz is unpacked, and not come back on till "init" is run, at
| >| which point the screen comes back on in what looks to be exactly
| >| the same mode?
| >
| >Hm, do you have a serial console enabled (in the kernel config and
| > in your kernel command line)?  If not, please send your .config
| > file (your probably did, but I'm lost in the maze of emails).
| 
| Not that I can find, and I'm restricted to a make menuconfig, xconfig 
| is broken because its not seeing the correct libqt-mt library.  Its 
| complaining about the version in kde3.2.3, but all the env stuff now 
| points it to kde3.3-beta2.  How can I cause that to get refreshed for 
| the newer libraries now installed?

Dunno, I've seen some similar problems.

| I'll attach the 2.6.7 .config.

I'll check it, but I don't have a quick answer for you on that one.

--
~Randy

Re: 2.6.8-rc2 crash(s)?

[Denis Vlasenko]

> | >Yeah, oopsen often don't kill the entire machine.
> |
> | Running 2.6.8-rc2 it sure did, deader than a doornail.  X's clock
> | stopped, the whole maryann.  Keyboard leds off.  Had to use the reset
> | button, and once or twice I had to do a full powerdown before it
> | would enter post and reboot.  Then sit thru 20+ minutes of e2fscking
> | all the drives of course.

  +-----------------+
  | I love ReiserFS |
  +-----------------+
          | |
          | | 

-- 
vda

Re: 2.6.8-rc2 crash(s)?

[Randy.Dunlap]

On Thu, 29 Jul 2004 22:03:42 -0700 Randy.Dunlap wrote:

| On Fri, 30 Jul 2004 00:50:53 -0400 Gene Heskett wrote:
| 
| | On Thursday 29 July 2004 23:36, Randy.Dunlap wrote:
| | >On Thu, 29 Jul 2004 21:47:21 -0400 Gene Heskett wrote:
| | >| On Thursday 29 July 2004 18:14, Randy.Dunlap wrote:
| | >| [...]
| | >| I've gone clear back to a 2.6.7 kernel because thats the newest
| | >| one that has a diff when cmp'ing fs/dcache.c files to whats in
| | >| 2.6.8-rc2.
| | >|
| | >| I've had one Oops, virtually the same one, but it didn't kill the
| | >| machine like it would have if I was running 2.6.8-rc2.
| | >
| | >Yeah, oopsen often don't kill the entire machine.
| | 
| | Running 2.6.8-rc2 it sure did, deader than a doornail.  X's clock 
| | stopped, the whole maryann.  Keyboard leds off.  Had to use the reset 
| | button, and once or twice I had to do a full powerdown before it 
| | would enter post and reboot.  Then sit thru 20+ minutes of e2fscking 
| | all the drives of course.
| | 
| | >| >make fs/dcache.s
| | >|
| | >| Aha!  Voila!! It doesn't work in the "fs" subdir, but back out to
| | >| the top of the src tree and it works just fine.  Duh...
| | >
| | >Right, it needs the top-level makfile and kbuild machinery to do
| | > that.
| | >
| | >| Now, I must confess that what I'm looking at in those two files is
| | >| the .s is the source assembly that would normally be fed to gas,
| | >| and the objdump'ed version is the dissed object translated back to
| | >| gas source.  If no mistakes, they should be pretty close to the
| | >| same I'd think.  Am I on the right track?  Or full of it?
| | >
| | >Yes, right.
| | 
| | Which?
| | 
| | Right track, or full of it? :-)
| 
| Right track.  ;)
| 
| | In any event, I could send those two files along if you'd like, I'm 
| | not an assembly guru on "amd/intel" chips, not even in my wildest 
| | dreams .
| | 
| | >| Here's the theory thats gradually formed in whats left of my mind:
| | >| --------------
| | >| 5 things changed in the kernel soft when I changed the mobo.
| | >| 1. The ide driver, from via686a to the nforce2 version.
| | >| 2. The video driver, because the old card failed and took the mobo
| | >| with it.
| | >| 3. Ethernet driver is now forcedeth instead of rtl-8139too
| | >| 4. A different alsa driver, from via8233 to intel-8x0
| | >| 5. The 4Gb switch is turned on in the kernel now as theres a gig
| | >| of ram on this board.
| | >| --------------
| | >
| | >You can easily use a non-high-memory enabled kernel.  It will still
| | >use 896 MB of RAM (IIRC).  Enabling highmem gets you another 128 MB.
| | >
| | >IDE and video are somewhat important, no?
| | >But the ethernet and ALSA drivers should be optional, at least for
| | > some testing... Ha, you said that below!
| | >
| | >| I can't do anything about the first 2, but I can do without the
| | >| last 200 megs of ram long enough to test that, and I can switch
| | >| back to the rtl-8139too card for ethernet, and I can turn off
| | >| alsasound.
| | >|
| | >| In the meantime I turned a bunch of stuff the logs were
| | >| complaining about off, like sgi_fam (what the heck is that?), some
| | >| ups daemons
| | >
| | >FAM is File Alteration Monitor, from SGI:
| | >  http://oss.sgi.com/projects/fam/
| | 
| | So I should start it back up?  Its a security tool?, or a system 
| | watchdog (or both?)
| 
| No, you probably don't need it.  Depends on your apps/usage,
| but it's certainly not _required_.
| 
| | >| for brands I don't have, that sort of thing, and have a tail
| | >| running on the log.  So far, its clean since the restart of
| | >| xinetd.  Another 16 hours will tell most of the tale for this
| | >| particular instant configuration.
| | 
| | I just had mozilla try to display an rpm or tgz file, killed X, so the 
| | log got filled up a bit.  Odd, I haven't had to step on the shift key 
| | before clicking a download link in ages.  Trying to get a newer 
| | version of ymessenger.  I have an old beta version and yahoo says its 
| | too old.
| |  
| | >| One final question if I may:  What do I turn off (or on) in the
| | >| video dept of the kernel so that my screen doesn't go black after
| | >| vmlinuz is unpacked, and not come back on till "init" is run, at
| | >| which point the screen comes back on in what looks to be exactly
| | >| the same mode?
| | >
| | >Hm, do you have a serial console enabled (in the kernel config and
| | > in your kernel command line)?  If not, please send your .config
| | > file (your probably did, but I'm lost in the maze of emails).
| | 
| | Not that I can find, and I'm restricted to a make menuconfig, xconfig 
| | is broken because its not seeing the correct libqt-mt library.  Its 
| | complaining about the version in kde3.2.3, but all the env stuff now 
| | points it to kde3.3-beta2.  How can I cause that to get refreshed for 
| | the newer libraries now installed?
| 
| Dunno, I've seen some similar problems.
| 
| | I'll attach the 2.6.7 .config.
| 
| I'll check it, but I don't have a quick answer for you on that one.

Well, I managed to whack an ext3 partition (/) and have to reinstall it.

Just from looking at your .config, I suggest turning off some/all/most
of these to see if it will boot and run for awhile:

CONFIG_HPET_TIMER=y
CONFIG_HPET_EMULATE_RTC=y

CONFIG_PREEMPT=y
CONFIG_INPUT_EVBUG=y

CONFIG_IPMI_HANDLER=y
CONFIG_IPMI_DEVICE_INTERFACE=y

CONFIG_4KSTACKS=y

--
~Randy

Re: 2.6.8-rc2 crash(s)?

[Denis Vlasenko]

> >| >make fs/dcache.s
> >|
> >| Aha!  Voila!! It doesn't work in the "fs" subdir, but back out to
> >| the top of the src tree and it works just fine.  Duh...
> >
> >Right, it needs the top-level makfile and kbuild machinery to do
> > that.
> >
> >| Now, I must confess that what I'm looking at in those two files is
> >| the .s is the source assembly that would normally be fed to gas,
> >| and the objdump'ed version is the dissed object translated back to
> >| gas source.  If no mistakes, they should be pretty close to the
> >| same I'd think.  Am I on the right track?  Or full of it?
> >
> >Yes, right.
>
> Which?
>
> Right track, or full of it? :-)
>
> In any event, I could send those two files along if you'd like, I'm
> not an assembly guru on "amd/intel" chips, not even in my wildest
> dreams .

Send them, along with oops.

BTW, compile 'oops-hunting' kernels with frame pointers in the future
(I just compile all my kernels with it).
--
vda

Re: 2.6.8-rc2 crash(s)?

[Gene Heskett]

On Sunday 01 August 2004 11:58, Denis Vlasenko wrote:
>On Sunday 01 August 2004 15:09, Gene Heskett wrote:
>> >But I digress. OOPS happened in dentry_iput(), which is
>> > (surprise!) an inline function:
>
This looks as if its as far as we can get Denis, so I'm
just going to post the whole thing to lkml, after snipping
the last Opps out of what is now last weeks log (its
sunday, and so far this log is clean) and inserting it also.

Many thanks for all your help, Denis.  I've learned a bit
about troubleshooting things like this.

To the lkml:  I can supply the dcache.txt objdumps, and the
dcache-w-nops.s files to whomever requests them so that they
can draw their own conclusions.  My uptimes here are generally
less than 24 hours because of this Oops.

>> >You need to do more of asm()ing.

>> Ok, I now have them attached.  I did add a pair of curlies to
>> contain another example of the H syndrome.
[...]
>asm("nop #O");
>                if (dentry->d_op && dentry->d_op->d_iput)
>                    ^^^^^^^^^^^^    ^^^^^^^^^^^^^^^^^^^^
>{
>asm("nop #P");
>                        dentry->d_op->d_iput(dentry, inode);
>                        ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
>}
>                else
>{
>asm("nop #Q");
>                        iput(inode);
>asm("nop #R");
>
[... to the objdump]
>
>        nop #O
>        movl    68(%ebx), %eax
>        testl   %eax, %eax <--- this is dentry->d_op. %eax ==
> 00000e00 here. this is bad. pointer can't have such a value
>        je      .L532
>        movl    20(%eax), %edx   <=== it tries to fetch
>				dentry->d_op->d_iput
>				at 00000e20, which is bogus address. OOPS
>        testl   %edx, %edx
>        jne     .L594      <--*
>.L532:
>        nop #Q
>        movl    %esi, (%esp)
>        call    iput
>        nop #R
>.L565:
>        nop #E
>        movl    12(%ebx), %esi
>        nop #F
>        movl    %ebx, (%esp)
>        call    d_free
>        nop #G
>        cmpl    %ebx, %esi
>        je      .L566
>        movl    %esi, (%esp)
>        call    dput
>.L566:
>        nop #I
>        incl    20(%edi)
>        nop #J
>        jmp     .L445
>.L594:                     <--*
>        nop #P
>        movl    %ebx, (%esp)
>        movl    %esi, 4(%esp)
>        call    *20(%eax)   <---- calls dentry->d_op->d_iput(dentry,
> inode) (just checking that I indeed properly matched C to asm) jmp 
>    .L565
>.L593:
>
>Where that dentry came from?
>
>void prune_dcache(int count)
>{
>        for (; count ; count--) {
>                struct dentry *dentry;
>                struct list_head *tmp;
>                tmp = dentry_unused.prev;
>                if (tmp == &dentry_unused) break;
>                list_del_init(tmp);
>                dentry_stat.nr_unused--;
>                dentry = list_entry(tmp, struct dentry, d_lru);
>                /*
>                 * We found an inuse dentry which was not removed
> from * dentry_unused because of laziness during lookup.  Do not
> free * it - just keep it off the dentry_unused list. */
>                if (atomic_read(&dentry->d_count)) continue;
>                }
>                /* If the dentry was recently referenced, don't free
> it. */ if (dentry->d_flags & DCACHE_REFERENCED) {
>			...
>                        continue;
>                }
>                prune_one_dentry(dentry);
>		...
>
>prune_one_dentry(dentry) {
>	...
>        dentry_iput(dentry)
>	...
>}
>
>Heh. I don't know where to go now. At least we can post complete
>bug report on lkml.
>
>You can trace other oopses in a similar way. Maybe there is some
>patterm in them.

This 'pattern' has been pretty consistent, and even attacks kernels
as late as 2.6.8-rc2, with the difference being that from 2.6.7-mm1
on, the Oops is 99% fatal to the machine, as in a total lockup,
reset or power switch to recover.  With 2.6.7, the worst its done
(generally, there have been exceptions) is to screw up the reboot,
eventually needing the reset switch about 5% of the time to get
back to post & get rebooting under way.

Without further prattle, The Oops, from yesterday afternoon:
-------------
Jul 31 13:55:12 coyote kernel: Unable to handle kernel NULL pointer dereference at virtual address 00000e14
Jul 31 13:55:12 coyote kernel:  printing eip:
Jul 31 13:55:12 coyote kernel: c0162887
Jul 31 13:55:12 coyote kernel: *pde = 00000000
Jul 31 13:55:12 coyote kernel: Oops: 0000 [#1]
Jul 31 13:55:12 coyote kernel: PREEMPT
Jul 31 13:55:12 coyote kernel: Modules linked in: 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 31 13:55:12 coyote kernel: CPU:    0
Jul 31 13:55:12 coyote kernel: EIP:    0060:[<c0162887>]    Not tainted
Jul 31 13:55:12 coyote kernel: EFLAGS: 00010206   (2.6.7-nf2)
Jul 31 13:55:12 coyote kernel: EIP is at prune_dcache+0x147/0x1c0
Jul 31 13:55:12 coyote kernel: eax: 00000e00   ebx: d1bde050   ecx: f1b3c050   edx: f1b3ac50
Jul 31 13:55:12 coyote kernel: esi: f1b3ac40   edi: c1973000   ebp: 00000036   esp: c1973ef8
Jul 31 13:55:12 coyote kernel: ds: 007b   es: 007b   ss: 0068
Jul 31 13:55:12 coyote kernel: Process kswapd0 (pid: 65, threadinfo=c1973000 task=c1986050)
Jul 31 13:55:12 coyote kernel: Stack: d7721178 c1973ef8 0000007a 00000000 c1973000 f7ffea48 c0162d1f 0000007a
Jul 31 13:55:12 coyote kernel:        c0139a2b 0000007a 000000d0 00025528 049dbb00 00000000 000001fa 00000000
Jul 31 13:55:12 coyote kernel:        c0364564 00000001 0000000a c0364440 c013add1 00000080 000000d0 00000000
Jul 31 13:55:12 coyote kernel: Call Trace:
Jul 31 13:55:12 coyote kernel:  [<c0162d1f>] shrink_dcache_memory+0x1f/0x30
Jul 31 13:55:12 coyote kernel:  [<c0139a2b>] shrink_slab+0x14b/0x190
Jul 31 13:55:12 coyote kernel:  [<c013add1>] balance_pgdat+0x1b1/0x200
Jul 31 13:55:12 coyote kernel:  [<c013aee7>] kswapd+0xc7/0xe0
Jul 31 13:55:12 coyote kernel:  [<c0114270>] autoremove_wake_function+0x0/0x60
Jul 31 13:55:12 coyote kernel:  [<c0103e9e>] ret_from_fork+0x6/0x14
Jul 31 13:55:12 coyote kernel:  [<c0114270>] autoremove_wake_function+0x0/0x60
Jul 31 13:55:12 coyote kernel:  [<c013ae20>] kswapd+0x0/0xe0
Jul 31 13:55:12 coyote kernel:  [<c01021d1>] kernel_thread_helper+0x5/0x14
Jul 31 13:55:12 coyote kernel:
Jul 31 13:55:12 coyote kernel: Code: 8b 50 14 85 d2 75 27 89 34 24 e8 4a 2b 00 00 8b 73 0c 89 1c
------------------------

-- 
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.

2.6.7 and 2.6.8-rc2 have similar Oops

[Gene Heskett]

This is a resend with a new subject, the first one apparently didn't 
get there.

On Sunday 01 August 2004 11:58, Denis Vlasenko wrote:
>On Sunday 01 August 2004 15:09, Gene Heskett wrote:
>> >But I digress. OOPS happened in dentry_iput(), which is
>> > (surprise!) an inline function:

This looks as if its as far as we can get Denis, so I'm
just going to post the whole thing to lkml, after snipping
the last Opps out of what is now last weeks log (its
sunday, and so far this log is clean) and inserting it also.

Many thanks for all your help, Denis.  I've learned a bit
about troubleshooting things like this.

To the lkml:  Currently running 2.6.7 because for 2.6.7, its not 
generally fatal.  With 2.8.6-rc2 its nearly 100% fatal.
This data was developed from the 2.6.7 srcs.

I can supply the dcache.txt objdumps, and the
dcache-w-nops.s files to whomever requests them so that they
can draw their own conclusions.  My uptimes here are generally
less than 24 hours because of this Oops.

>> >You need to do more of asm()ing.

>> Ok, I now have them attached.  I did add a pair of curlies to
>> contain another example of the H syndrome.
[...]
>asm("nop #O");
>                if (dentry->d_op && dentry->d_op->d_iput)
>                    ^^^^^^^^^^^^    ^^^^^^^^^^^^^^^^^^^^
>{
>asm("nop #P");
>                        dentry->d_op->d_iput(dentry, inode);
>                        ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
>}
>                else
>{
>asm("nop #Q");
>                        iput(inode);
>asm("nop #R");
>
[... to the objdump]
>
>        nop #O
>        movl    68(%ebx), %eax
>        testl   %eax, %eax <--- this is dentry->d_op. %eax ==
> 00000e00 here. this is bad. pointer can't have such a value
>        je      .L532
>        movl    20(%eax), %edx   <=== it tries to fetch
>				dentry->d_op->d_iput
>				at 00000e20, which is bogus address. OOPS
>        testl   %edx, %edx
>        jne     .L594      <--*
>.L532:
>        nop #Q
>        movl    %esi, (%esp)
>        call    iput
>        nop #R
>.L565:
>        nop #E
>        movl    12(%ebx), %esi
>        nop #F
>        movl    %ebx, (%esp)
>        call    d_free
>        nop #G
>        cmpl    %ebx, %esi
>        je      .L566
>        movl    %esi, (%esp)
>        call    dput
>.L566:
>        nop #I
>        incl    20(%edi)
>        nop #J
>        jmp     .L445
>.L594:                     <--*
>        nop #P
>        movl    %ebx, (%esp)
>        movl    %esi, 4(%esp)
>        call    *20(%eax)   <---- calls dentry->d_op->d_iput(dentry,
> inode) (just checking that I indeed properly matched C to asm) jmp 
>    .L565
>.L593:
>
>Where that dentry came from?
>
>void prune_dcache(int count)
>{
>        for (; count ; count--) {
>                struct dentry *dentry;
>                struct list_head *tmp;
>                tmp = dentry_unused.prev;
>                if (tmp == &dentry_unused) break;
>                list_del_init(tmp);
>                dentry_stat.nr_unused--;
>                dentry = list_entry(tmp, struct dentry, d_lru);
>                /*
>                 * We found an inuse dentry which was not removed
> from * dentry_unused because of laziness during lookup.  Do not
> free * it - just keep it off the dentry_unused list. */
>                if (atomic_read(&dentry->d_count)) continue;
>                }
>                /* If the dentry was recently referenced, don't free
> it. */ if (dentry->d_flags & DCACHE_REFERENCED) {
>			...
>                        continue;
>                }
>                prune_one_dentry(dentry);
>		...
>
>prune_one_dentry(dentry) {
>	...
>        dentry_iput(dentry)
>	...
>}
>
>Heh. I don't know where to go now. At least we can post complete
>bug report on lkml.
>
>You can trace other oopses in a similar way. Maybe there is some
>patterm in them.

This 'pattern' has been pretty consistent, and even attacks kernels
as late as 2.6.8-rc2, with the difference being that from 2.6.7-mm1
on, the Oops is 99% fatal to the machine, as in a total lockup,
reset or power switch to recover.  With 2.6.7, the worst its done
(generally, there have been exceptions) is to screw up the reboot,
eventually needing the reset switch about 5% of the time to get
back to post & get rebooting under way.

Without further prattle, The Oops, from yesterday afternoon:
-------------
Jul 31 13:55:12 coyote kernel: Unable to handle kernel NULL pointer 
dereference at virtual address 00000e14
Jul 31 13:55:12 coyote kernel:  printing eip:
Jul 31 13:55:12 coyote kernel: c0162887
Jul 31 13:55:12 coyote kernel: *pde = 00000000
Jul 31 13:55:12 coyote kernel: Oops: 0000 [#1]
Jul 31 13:55:12 coyote kernel: PREEMPT
Jul 31 13:55:12 coyote kernel: Modules linked in: 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 31 13:55:12 coyote kernel: CPU:    0
Jul 31 13:55:12 coyote kernel: EIP:    0060:[<c0162887>]    Not 
tainted
Jul 31 13:55:12 coyote kernel: EFLAGS: 00010206   (2.6.7-nf2)
Jul 31 13:55:12 coyote kernel: EIP is at prune_dcache+0x147/0x1c0
Jul 31 13:55:12 coyote kernel: eax: 00000e00   ebx: d1bde050   ecx: 
f1b3c050   edx: f1b3ac50
Jul 31 13:55:12 coyote kernel: esi: f1b3ac40   edi: c1973000   ebp: 
00000036   esp: c1973ef8
Jul 31 13:55:12 coyote kernel: ds: 007b   es: 007b   ss: 0068
Jul 31 13:55:12 coyote kernel: Process kswapd0 (pid: 65, 
threadinfo=c1973000 task=c1986050)
Jul 31 13:55:12 coyote kernel: Stack: d7721178 c1973ef8 0000007a 
00000000 c1973000 f7ffea48 c0162d1f 0000007a
Jul 31 13:55:12 coyote kernel:        c0139a2b 0000007a 000000d0 
00025528 049dbb00 00000000 000001fa 00000000
Jul 31 13:55:12 coyote kernel:        c0364564 00000001 0000000a 
c0364440 c013add1 00000080 000000d0 00000000
Jul 31 13:55:12 coyote kernel: Call Trace:
Jul 31 13:55:12 coyote kernel:  [<c0162d1f>] 
shrink_dcache_memory+0x1f/0x30
Jul 31 13:55:12 coyote kernel:  [<c0139a2b>] shrink_slab+0x14b/0x190
Jul 31 13:55:12 coyote kernel:  [<c013add1>] balance_pgdat+0x1b1/0x200
Jul 31 13:55:12 coyote kernel:  [<c013aee7>] kswapd+0xc7/0xe0
Jul 31 13:55:12 coyote kernel:  [<c0114270>] 
autoremove_wake_function+0x0/0x60
Jul 31 13:55:12 coyote kernel:  [<c0103e9e>] ret_from_fork+0x6/0x14
Jul 31 13:55:12 coyote kernel:  [<c0114270>] 
autoremove_wake_function+0x0/0x60
Jul 31 13:55:12 coyote kernel:  [<c013ae20>] kswapd+0x0/0xe0
Jul 31 13:55:12 coyote kernel:  [<c01021d1>] 
kernel_thread_helper+0x5/0x14
Jul 31 13:55:12 coyote kernel:
Jul 31 13:55:12 coyote kernel: Code: 8b 50 14 85 d2 75 27 89 34 24 e8 
4a 2b 00 00 8b 73 0c 89 1c
------------------------

-- 
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.