https://bugzilla.novell.com/show_bug.cgi?id=434618
User abittner@stud.fh-heilbronn.de added comment
https://bugzilla.novell.com/show_bug.cgi?id=434618#c10
--- Comment #10 from andreas bittner 2008-10-15 07:27:22 MDT ---
you guys are not making it a tiny bit easier for us non-devs and non-gurus to
report bugs and/or help. :/
i might think this bug would qualify as a memory-management bug or such, but im
not even sure about that in the first place, and then let alone those bazillion
things to select from on the kernel bugzilla.
what tree and what component would that be in memory-management to give some
basic idea where to put this bug?
although, im not even sure if the gart stuff is the main reason, thats at least
some of the fail lines/logs i see during the suse kernels.
does suse use some sort of vanilla (mainline?) kernels for their kernels, or is
that even derived from some "alternate trees" or something?
well i thought some kernel professional would take on this bug, rather than
letting me mess up the kernel bugzilla ;)
i dont know what would cause less trouble and chaos, me creating some bug in
the wrong area of the kernel bugzilla, or somebody who has direct experience in
the kernel development efforts.
and then, there are also these hanging modprobe processes somehow related to
the soundcard startup process during install/boot. i guess that would be
another independant bug, but maybe not, if the gart stuff would work normally,
maybe sound/modprobe would also behave normally? who knows.....
so any basic hints for the gart stuff? i will try my best if i get a little
additional help where to put this initial bug.
thanks.
--
Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.