FAQ Search Today's Posts Mark Forums Read
» Video Reviews

» Linux Archive

Linux-archive is a website aiming to archive linux email lists and to make them easily accessible for linux users/developers.


» Sponsor

» Partners

» Sponsor

Go Back   Linux Archive > Redhat > Fedora Development

 
 
LinkBack Thread Tools
 
Old 08-28-2008, 10:38 PM
"Tom London"
 
Default Problems with kernel-2.6.26 and 2.6.27-0.x.rc2

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
 
Old 08-28-2008, 11:52 PM
"Joshua C."
 
Default 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.

--
fedora-devel-list mailing list
fedora-devel-list@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-devel-list
 
Old 08-29-2008, 12:17 AM
"Joshua C."
 
Default 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
>

I suspect it's Intel's GEM that is causing the problems. The kernel
boots fine until it has to initialize the devices. And in my case I
have no display. acpi=off helps me solve the problem but then lots of
devices don't work. Maybe a kernel code that deals with the device
initialisation is what's changed between 2.6.25 and 2.6.26/27 series.

--
fedora-devel-list mailing list
fedora-devel-list@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-devel-list
 
Old 08-29-2008, 10:57 AM
"Joshua C."
 
Default Problems with kernel-2.6.26 and 2.6.27-0.x.rc2

2008/8/29 Joshua C. <joshuacov@googlemail.com>:
> 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
>>
>
> I suspect it's Intel's GEM that is causing the problems. The kernel
> boots fine until it has to initialize the devices. And in my case I
> have no display. acpi=off helps me solve the problem but then lots of
> devices don't work. Maybe a kernel code that deals with the device
> initialisation is what's changed between 2.6.25 and 2.6.26/27 series.
>

With the latest kernel-2.6.27-0.290.rc5 I have just a blank screen, no
stripps anymore. I'd like to help with debuging this GEM.

--
fedora-devel-list mailing list
fedora-devel-list@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-devel-list
 
Old 08-30-2008, 06:31 AM
"Joshua C."
 
Default Problems with kernel-2.6.26 and 2.6.27-0.x.rc2

2008/8/29 Joshua C. <joshuacov@googlemail.com>:
> 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?
>

Any ideas how to debug this? Who/where should I ask?

--
fedora-devel-list mailing list
fedora-devel-list@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-devel-list
 
Old 08-31-2008, 09:36 PM
Dave Airlie
 
Default Problems with kernel-2.6.26 and 2.6.27-0.x.rc2

On Sat, 2008-08-30 at 08:31 +0200, Joshua C. wrote:
> 2008/8/29 Joshua C. <joshuacov@googlemail.com>:
> > 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?

So you have two problems.. one is a kernel module is loading and hanging
the boot process, this is usually blamed on udev, the fact that hitting
a key helps implies some interrupt handling problem maybe..

The other is the graphical boot not working properly on your card, for
that you can boot with nomodeset on the command line, if udev hangs that
is the other problem. For the graphical boot, I'd need to know the
graphics card and type of card, agp pci etc. and type of display plugged
in.

Dave.

--
fedora-devel-list mailing list
fedora-devel-list@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-devel-list
 
Old 09-01-2008, 07:28 AM
Hans de Goede
 
Default Problems with kernel-2.6.26 and 2.6.27-0.x.rc2

Dave Airlie wrote:

<snip>



So you have two problems.. one is a kernel module is loading and hanging
the boot process, this is usually blamed on udev, the fact that hitting
a key helps implies some interrupt handling problem maybe..

The other is the graphical boot not working properly on your card, for
that you can boot with nomodeset on the command line, if udev hangs that
is the other problem. For the graphical boot, I'd need to know the
graphics card and type of card, agp pci etc. and type of display plugged
in.



Hi Dave,

I'm seeing problems with graphical boot too, I haven't been reporting them
sofar as things are still somewhat in flux with regards to kernel mode setting.


But since you asked:

00:0e.0 PCI bridge: nVidia Corporation MCP55 PCI Express bridge (rev a2)
03:00.0 VGA compatible controller: ATI Technologies Inc RV570 [Radeon X1950
Pro] (rev 9a)
03:00.1 Display controller: ATI Technologies Inc RV570 [Radeon X1950 Pro]
(secondary) (rev 9a)


dual core x86_64 system running:
kernel-2.6.27-0.290.rc5.fc10.x86_64

Using an analog vga attached 1280x1024 lcd screen

Graphical boot worked a couple of times but the last 2 boots it hanged with a
black screen when the mode got set (I'm now running aan older kernel).


When graphical boot did work, X was slow as molasses, Xorg.log provided no
clues (I could find), but this may be because I was only running the latest
kernel and my xorg and libdrm are about 2 weeks old.


Let me know if you want this in bugzilla and what more I can do to test. I must
say that plymouth looked good when it worked.


Regards,

Hans

--
fedora-devel-list mailing list
fedora-devel-list@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-devel-list
 
Old 09-01-2008, 02:50 PM
"Clyde E. Kunkel"
 
Default Problems with kernel-2.6.26 and 2.6.27-0.x.rc2

Hans de Goede wrote:


<snip>

Graphical boot worked a couple of times but the last 2 boots it hanged
with a black screen when the mode got set (I'm now running aan older
kernel).


When graphical boot did work, X was slow as molasses, Xorg.log provided
no clues (I could find), but this may be because I was only running the
latest kernel and my xorg and libdrm are about 2 weeks old.


Let me know if you want this in bugzilla and what more I can do to test.
I must say that plymouth looked good when it worked.


Regards,

Hans



I reverted gdm to remedy this problem.

--
---------------------------------
Regards,

Old Fart

--
fedora-devel-list mailing list
fedora-devel-list@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-devel-list
 
Old 09-01-2008, 07:44 PM
"Joshua C."
 
Default Problems with kernel-2.6.26 and 2.6.27-0.x.rc2

2008/8/31 Dave Airlie <airlied@redhat.com>:
>
> So you have two problems.. one is a kernel module is loading and hanging
> the boot process, this is usually blamed on udev, the fact that hitting
> a key helps implies some interrupt handling problem maybe..

You were right. the problem with udev concerns the timer broadcast for
the amd processors. the
linux-2.6-x86-32-amd-c1e-force-timer-broadcast-late.patch corrected
this. I tried it with 2.6.26.3-17.fc9 and 2.6.27-0.290.rc5.fc10 and
everything is fine. the udev starts normally. so i can close the first
bug. Now about the kernel modesetting:

>
> The other is the graphical boot not working properly on your card, for
> that you can boot with nomodeset on the command line, if udev hangs that
> is the other problem. For the graphical boot, I'd need to know the
> graphics card and type of card, agp pci etc. and type of display plugged
> in.
>
> Dave.

with the patch applied and nomodeset at the command line the kernel
loads fine until the time for the xserver to start. then i get a blank
screen. just nothing. here are the specs for my card:

integrated Radeon Xpress 1100 on acer aspire laptop.

#lscpi -vvv
01:05.0 VGA compatible controller: ATI Technologies Inc RS485 [Radeon
Xpress 1100 IGP] (prog-if 00 [VGA controller])
Subsystem: Acer Incorporated [ALI] Unknown device 010f
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop-
ParErr- Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=medium
>TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 66 (2000ns min), Cache Line Size: 32 bytes
Interrupt: pin A routed to IRQ 17
Region 0: Memory at c8000000 (32-bit, prefetchable)
[size=128M]
Region 1: I/O ports at 9000 [size=256]
Region 2: Memory at c0100000 (32-bit, non-prefetchable)
[size=64K]
[virtual] Expansion ROM at c0120000 [disabled] [size=128K]
Capabilities: [50] Power Management version 2
Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA
PME(D0-,D1-,D2-,D3hot-,D3cold-)
Status: D0 PME-Enable- DSel=0 DScale=0 PME-
Kernel modules: radeonfb

According to the x.org this should be RS482 card but it is reported as RS485

#lspci -nnn
01:05.0 VGA compatible controller [0300]: ATI Technologies Inc RS485
[Radeon Xpress 1100 IGP] [1002:5975]

It is an integrated display. No external one attached.

here is my xorg.conf
----------------------------------------------------
Section "ServerLayout"
Identifier "Default Layout"
Screen 0 "Screen0" 0 0
InputDevice "Keyboard0" "CoreKeyboard"
InputDevice "Synaptics" "CorePointer"
EndSection

Section "Files"

EndSection

Section "ServerFlags"
Option "AIGLX" "on"
EndSection

Section "InputDevice"
Identifier "Keyboard0"
Driver "kbd"
Option "XkbModel" "pc105"
Option "XkbLayout" "de"
EndSection

Section "InputDevice"
Identifier "Synaptics"
Driver "synaptics"
Option "SendCoreEvents"
Option "TapButton1" "1"
Option "TapButton2" "2"
Option "TapButton3" "3"
Option "Device" "/dev/input/mice"
Option "Protocol" "auto-dev"
Option "Emulate3Buttons" "yes"
Option "MinSpeed" "0.3"
Option "MaxSpeed" "0.4"
Option "MinTapTime" "110"
Option "MaxTapTime" "350"
Option "ClickTime" "0"
EndSection

Section "Device"
Identifier "Videocard0"
Driver "radeon"
Option "AccelMethod" "EXA"
Option "DRI" "True"
EndSection

Section "Module"
Load "ddc"
Load "vbe"
Load "GLcore"
Load "dbe"
Load "dri"
Load "extmod"
Load "glx"
Load "bitmap"
Load "freetype"
EndSection

Section "Screen"
Identifier "Screen0"
Device "Videocard0"
DefaultDepth 24
SubSection "Display"
Viewport 0 0
Depth 24
EndSubSection
EndSection

Section "DRI"
Mode 0666
EndSection

Section "Extensions"
Option "Composite" "Enable"
EndSection
-----------------------------------------------------------

I've attched my Xorg.0.log file to this message.
--
fedora-devel-list mailing list
fedora-devel-list@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-devel-list
 

Thread Tools




All times are GMT. The time now is 09:40 PM.

VBulletin, Copyright ©2000 - 2014, Jelsoft Enterprises Ltd.
Content Relevant URLs by vBSEO ©2007, Crawlability, Inc.
Copyright 2007 - 2008, www.linux-archive.org