[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

Re: Problems with kernel-2.6.26 and 2.6.27-0.x.rc2



2008/8/29 Tom London <selinux gmail com>:
> On Thu, Aug 28, 2008 at 3:13 PM, Joshua C. <joshuacov googlemail com> wrote:
>> I have a strange problem with the 2.6.26 series kernel. 2.6.27-rc1
>> branch is ok but the same thing happens with 2.6.27.rc2 and the
>> following. 2.6.25 branch is ok.
>> I filed a bug report here https://bugzilla.redhat.com/show_bug.cgi?id=458901.
>>
>> The kernel loads fine until showing "starting udev". then it just
>> stops and cannot continue. on the 2.6.26 branch i need to keep pressed
>> atleast one key for it to continue. Then it goes further and
>> everything freezes when no key is pressed.
>> 2.6.27.rc1 was ok but the same thing showed in 2.6.27.rc2 onwards.
>> with the lastes kernel-2.6.27-0.287.rc4.git7.fc10 after "startig udev"
>> I get black and white stripps on my screen and only hardware reset
>> helps. This makes me think it is something connected with the kernel
>> modesetting and my radeon gpu. It could also be udev but it is fine
>> with 2.6.25 and if i keep at least one key pressed then 2.6.26 works
>> fine. in everycase dmesg shows nothing. What could it be? How can I
>> see where the problem is?
>>
> Could this be your problem: https://bugzilla.redhat.com/show_bug.cgi?id=455595
>
> If so, adding "modprobedebug" to the boot parameters seems to help on
> my system (not radeon).
>
> tom
> --
> Tom London
>
> --
> fedora-devel-list mailing list
> fedora-devel-list redhat com
> https://www.redhat.com/mailman/listinfo/fedora-devel-list
>

Yes, both look the same. I tried (here
https://bugzilla.redhat.com/show_bug.cgi?id=458901#c5 )
wait_for_queue() to return true immediately and it helped me to speed
up the things. but at the end some devices didn't work.This is what i
get with the 2.6.26 after passing modprobedebug to command line:

Starting udev and then
loading drivers:
-ac.ko
-battery.ko
-wmi.ko
-i2c-core
-i2c-piix4.ko
cdrom.ko
sr_mod.ko
---------- first stop-----------after ~ 30 secs.----------
-sound/core/***.ko
---------second stop--------- after ~15 secs.-------
pcmcia.ko
mmc.ko
-----------------final stop/freeze-------------------
if i press any key i got
Triggering Resset
and then starting udev returns true and goes on. It stops only if i
release the pressed key.

When I pass udevdebug to the 2.6.26 kernel I get thousands of messages
and it stops periodically showing the following:
**********pass environment to socket "@/org/kernel/udev/monitor"
**********passed -1 bytes to socket "@/org/kernel/udev/monitor"

some of the messages on the screen return something like
"udev_rules_iter_label" and "checking selinux=1"

With 2.6.27 version it looks the same way but after loading the
cdrom.ko module the screen disappers (shows the black/white sripps)
and cannot see anything.

I suspect that udev is trying to configure my monitor using something
comming from the kernel code (modesetting for the ati cards) that
results in an error. and therefore the "@/org/kernel/udev/monitor"
messages are shown. I cannot explain it otherwise.


[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]