Hello.
X doesn't work under 2.6.10-rc1. i'm using the framebuffer X server.
Kernel 2.6.9 works. How could that be?
with kind regards
Thomas
On Sunday 24 October 2004 11:38, Thomas Meyer wrote:
> Hello.
>
> X doesn't work under 2.6.10-rc1. i'm using the framebuffer X server.
> Kernel 2.6.9 works. How could that be?
Details?
--
vda
Denis Vlasenko wrote:
> On Sunday 24 October 2004 11:38, Thomas Meyer wrote:
>
>>Hello.
>>
>>X doesn't work under 2.6.10-rc1. i'm using the framebuffer X server.
>>Kernel 2.6.9 works. How could that be?
>
>
> Details?
> --
> vda
>
>
Hi.
Signal SIGSEGV happens while doing sys function
"ioctl(5, FBIOBLANK <unfinished ...>"
seems to be some changes between 2.6.9 and 2.6.10-rc1 in file "fbmem.c"
with kind regards
Thomas
On Sun, 24 Oct 2004, Thomas Meyer wrote:
>
> Denis Vlasenko wrote:
> > On Sunday 24 October 2004 11:38, Thomas Meyer wrote:
> >
> >>Hello.
> >>
> >>X doesn't work under 2.6.10-rc1. i'm using the framebuffer X server.
> >>Kernel 2.6.9 works. How could that be?
> >
> >
> > Details?
> > --
> > vda
> >
> >
>
> Hi.
>
> Signal SIGSEGV happens while doing sys function
> "ioctl(5, FBIOBLANK <unfinished ...>"
>
> seems to be some changes between 2.6.9 and 2.6.10-rc1 in file "fbmem.c"
Do you have radeon hardware? Is there any oops in your logs?
It definitely sounds like it's due to this one:
[email protected], 2004-10-19 08:09:17-07:00, [email protected]
[PATCH] rework radeonfb blanking
This patch cleans up some old cruft in the manipulation of the LVDS
interface registers and fixes the blanking code to work with various DVI
flat panels.
Since this is all very sensitive stuff, I'm posting the patch here for
testing before submitting it upstream, though Andrew is welcome to put it
in -mm.
It also fix some problems with getting the right PLL setup on recent Mac
laptops, replacing the old hard coded list of values with cleaner code that
"probes" the PLL setup done by the firmware.
Signed-off-by: Andrew Morton <[email protected]>
Signed-off-by: Linus Torvalds <[email protected]>
Ben, any suggestions for Thomas?
Linus
On Mon, 2004-10-25 at 06:24, Linus Torvalds wrote:
> > Signal SIGSEGV happens while doing sys function
> > "ioctl(5, FBIOBLANK <unfinished ...>"
> >
> > seems to be some changes between 2.6.9 and 2.6.10-rc1 in file "fbmem.c"
>
> Do you have radeon hardware? Is there any oops in your logs?
A Oops log would be useful...
I don't see anything, are you sure he is using radeonfb ? Look at the
fix posted by Tony Dapalas today fixing a possible Oops on blank for
fbdev's that have no blank() callback ...
Ben.
----- Original Nachricht ----
Von: Benjamin Herrenschmidt <[email protected]>
An: Linus Torvalds <[email protected]>
Datum: 25.10.2004 01:00
Betreff: Re: [2.6.10-rc1] Segmentation fault in program "X"
> On Mon, 2004-10-25 at 06:24, Linus Torvalds wrote:
>
> > > Signal SIGSEGV happens while doing sys function
> > > "ioctl(5, FBIOBLANK <unfinished ...>"
> > >
> > > seems to be some changes between 2.6.9 and 2.6.10-rc1 in file "fbmem.c"
> >
> > Do you have radeon hardware? Is there any oops in your logs?
>
> A Oops log would be useful...
>
> I don't see anything, are you sure he is using radeonfb ? Look at the
> fix posted by Tony Dapalas today fixing a possible Oops on blank for
> fbdev's that have no blank() callback ...
>
> Ben.
>
>
>
Hello.
It's a via integrated video card and there is an oops:
Oct 23 09:34:46 hotzenplotz kernel: Unable to handle kernel NULL pointer dereference at virtual address 00000048
Oct 23 09:34:46 hotzenplotz kernel: printing eip:
Oct 23 09:34:46 hotzenplotz kernel: c0202206
Oct 23 09:34:46 hotzenplotz kernel: *pde = 00000000
Oct 23 09:34:46 hotzenplotz kernel: Oops: 0000 [#1]
Oct 23 09:34:46 hotzenplotz kernel: PREEMPT SMP
Oct 23 09:34:46 hotzenplotz kernel: Modules linked in: eth1394 ohci1394 uhci_hcd ehci_hcd i2c_viapro i2c_core snd_via82xx snd_ac97_codec gameport snd_mpu401_uart snd_rawmidi joydev tsdev evdev yenta_socket pcmcia_core ntfs
Oct 23 09:34:46 hotzenplotz kernel: CPU: 0
Oct 23 09:34:46 hotzenplotz kernel: EIP: 0060:[<c0202206>] Not tainted VLI
Oct 23 09:34:46 hotzenplotz kernel: EFLAGS: 00013293 (2.6.10-rc1)
Oct 23 09:34:46 hotzenplotz kernel: EIP is at fb_set_cmap+0x76/0xf0
Oct 23 09:34:46 hotzenplotz kernel: eax: 00000000 ebx: 00000048 ecx: 00000807 edx: c02031a0
Oct 23 09:34:46 hotzenplotz kernel: esi: ebc30008 edi: 00003282 ebp: e1932e20 esp: e1932de0
Oct 23 09:34:46 hotzenplotz kernel: ds: 007b es: 007b ss: 0068
Oct 23 09:34:46 hotzenplotz kernel: Process X (pid: 2366, threadinfo=e1932000 task=e1802a80)
Oct 23 09:34:46 hotzenplotz kernel: Stack: e1932e00 e1932e00 e1932e20 00003246 e1932e28 c03bd0e0 0000ffff e1932e24
Oct 23 09:34:46 hotzenplotz kernel: 083bb950 00000000 00000048 00000000 ebc30000 ebc30000 e1d2de00 00000001
Oct 23 09:34:46 hotzenplotz kernel: e1932e54 c01ff18a 00003282 00003246 00000048 00000000 083bb950 ebc30008
Oct 23 09:34:46 hotzenplotz kernel: Call Trace:
Oct 23 09:34:46 hotzenplotz kernel: [<c0106eaa>] show_stack+0x7a/0x90
Oct 23 09:34:46 hotzenplotz kernel: [<c0107032>] show_registers+0x152/0x1c0
Oct 23 09:34:46 hotzenplotz kernel: [<c010723c>] die+0xfc/0x180
Oct 23 09:34:46 hotzenplotz kernel: [<c0119517>] do_page_fault+0x237/0x5e7
Oct 23 09:34:46 hotzenplotz kernel: [<c0106af9>] error_code+0x2d/0x38
Oct 23 09:34:46 hotzenplotz kernel: [<c01ff18a>] fb_blank+0x6a/0x110
Oct 23 09:34:46 hotzenplotz kernel: [<c01ff4c0>] fb_ioctl+0x290/0x360
Oct 23 09:34:46 hotzenplotz kernel: [<c016add4>] sys_ioctl+0xf4/0x260
Oct 23 09:34:46 hotzenplotz kernel: [<c010606f>] syscall_call+0x7/0xb
Oct 23 09:34:46 hotzenplotz kernel: Code: 75 0d b8 ea ff ff ff 83 c4 34 5b 5e 5f c9 c3 8b 5d d0 c7 45 ec 00 00 00 00 31 c0 3b 43 04 73 78 90 8d 74 26 00 8b 5d e8 8b 45 e4 <0f> b7 1b 83 45 e8 02 89 5d dc 8b 5d e0 0f b7 08 83 c0 02 89 45
with kind regards
Thomas