[Bug #10843] Display artifacts on XOrg logout with PAT kernel and VESA framebuffer

[Bug #10843] Display artifacts on XOrg logout with PAT kernel and VESA framebuffer

[Rafael J. Wysocki]

This message has been generated automatically as a part of a report
of recent regressions.

The following bug entry is on the current list of known regressions
from 2.6.25.  Please verify if it still should be listed.


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=10843
Subject		: Display artifacts on XOrg logout with PAT kernel and VESA framebuffer
Submitter	: Frans Pop <elendil@planet.nl>
Date		: 2008-05-31 14:04 (8 days old)

Re: [Bug #10843] Display artifacts on XOrg logout with PAT kernel and VESA framebuffer

[Frans Pop]

On Saturday 07 June 2008, Rafael J. Wysocki wrote:
> The following bug entry is on the current list of known regressions
> from 2.6.25.  Please verify if it still should be listed.

Yes.

> Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=10843
> Subject	: Display artifacts on XOrg logout with PAT kernel and VESA framebuffer
> Submitter	: Frans Pop <elendil@planet.nl> 
> Date		: 2008-05-31 14:04 (8 days old)

[Bug 10843] Display artifacts on XOrg logout with PAT kernel and VESA framebuffer

[Rafael J. Wysocki]

This message has been generated automatically as a part of a report
of recent regressions.

The following bug entry is on the current list of known regressions
from 2.6.25.  Please verify if it still should be listed.


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=10843
Subject		: Display artifacts on XOrg logout with PAT kernel and VESA framebuffer
Submitter	: Frans Pop <elendil@planet.nl>
Date		: 2008-05-31 14:04 (15 days old)
References	: http://lkml.org/lkml/2008/6/7/206

Re: [Bug 10843] Display artifacts on XOrg logout with PAT kernel and VESA framebuffer

[Frans Pop]

On Saturday 14 June 2008, Rafael J. Wysocki wrote:
> The following bug entry is on the current list of known regressions
> from 2.6.25.  Please verify if it still should be listed.
>
> Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=10843
> Subject	: Display artifacts on XOrg logout with PAT kernel and VESA
> 		  framebuffer
> Submitter	: Frans Pop <elendil@planet.nl> 
> Date		: 2008-05-31 14:04 (15 days old)
> References	: http://lkml.org/lkml/2008/6/7/206

Yes. See also: http://lkml.org/lkml/2008/6/13/159

Re: [Bug 10843] Display artifacts on XOrg logout with PAT kernel and VESA framebuffer

[Romano Giannetti]

On Sat, 2008-06-14 at 23:59 +0200, Frans Pop wrote:
> \>
> > Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=10843
> > Subject	: Display artifacts on XOrg logout with PAT kernel and VESA
> > 		  framebuffer
> > Submitter	: Frans Pop <elendil@planet.nl> 
> > Date		: 2008-05-31 14:04 (15 days old)
> > References	: http://lkml.org/lkml/2008/6/7/206
> 
> Yes. See also: http://lkml.org/lkml/2008/6/13/159
> -

It happens to me too. Do you see
http://bugzilla.kernel.org/show_bug.cgi?id=10892 ?

Romano


-- 
Romano Giannetti                            Dep. de Electrónica y Automática
http://www.dea.icai.upcomillas.es/romano    Univ. Pontificia Comillas (MADRID)


--
La presente comunicación tiene carácter confidencial y es para el exclusivo uso del destinatario indicado en la misma. Si Ud. no es el destinatario indicado, le informamos que cualquier forma de distribución, reproducción o uso de esta comunicación y/o de la información contenida en la misma están estrictamente prohibidos por la ley. Si Ud. ha recibido esta comunicación por error, por favor, notifíquelo inmediatamente al remitente contestando a este mensaje y proceda a continuación a destruirlo. Gracias por su colaboración.

This communication contains confidential information. It is for the exclusive use of the intended addressee. If you are not the intended addressee, please note that any form of distribution, copying or use of this communication or the information in it is strictly prohibited by law. If you have received this communication in error, please immediately notify the sender by reply e-mail and destroy this message. Thank you for your cooperation. 

Re: [Bug 10843] Display artifacts on XOrg logout with PAT kernel and VESA framebuffer

[Adrian Bunk]

On Sun, Jun 15, 2008 at 12:22:59PM +0200, Romano Giannetti wrote:
> 
> On Sat, 2008-06-14 at 23:59 +0200, Frans Pop wrote:
> > \>
> > > Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=10843
> > > Subject	: Display artifacts on XOrg logout with PAT kernel and VESA
> > > 		  framebuffer
> > > Submitter	: Frans Pop <elendil@planet.nl> 
> > > Date		: 2008-05-31 14:04 (15 days old)
> > > References	: http://lkml.org/lkml/2008/6/7/206
> > 
> > Yes. See also: http://lkml.org/lkml/2008/6/13/159
> > -
> 
> It happens to me too. Do you see
> http://bugzilla.kernel.org/show_bug.cgi?id=10892 ?

Does disabling CONFIG_X86_PAT also fix it for you?

> Romano

cu
Adrian

-- 

       "Is there not promise of rain?" Ling Tan asked suddenly out
        of the darkness. There had been need of rain for many days.
       "Only a promise," Lao Er said.
                                       Pearl S. Buck - Dragon Seed

Re: [Bug 10843] Display artifacts on XOrg logout with PAT kernel and VESA framebuffer

[Rafael J. Wysocki]

On Sunday, 15 of June 2008, Romano Giannetti wrote:
> 
> On Sat, 2008-06-14 at 23:59 +0200, Frans Pop wrote:
> > \>
> > > Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=10843
> > > Subject	: Display artifacts on XOrg logout with PAT kernel and VESA
> > > 		  framebuffer
> > > Submitter	: Frans Pop <elendil@planet.nl> 
> > > Date		: 2008-05-31 14:04 (15 days old)
> > > References	: http://lkml.org/lkml/2008/6/7/206
> > 
> > Yes. See also: http://lkml.org/lkml/2008/6/13/159
> > -
> 
> It happens to me too. Do you see
> http://bugzilla.kernel.org/show_bug.cgi?id=10892 ?

Do these two bug entries refer to the same problem?

Rafael

Re: [Bug 10843] Display artifacts on XOrg logout with PAT kernel and VESA framebuffer

[Romano Giannetti]

On Sun, 2008-06-15 at 13:39 +0300, Adrian Bunk wrote:
> On Sun, Jun 15, 2008 at 12:22:59PM +0200, Romano Giannetti wrote:
> > 

> > > Yes. See also: http://lkml.org/lkml/2008/6/13/159
> > > -
> > 
> > It happens to me too. Do you see
> > http://bugzilla.kernel.org/show_bug.cgi?id=10892 ?
> 
> Does disabling CONFIG_X86_PAT also fix it for you?

Dunno. Do I need to recompile or there is some boot option to disable
it?

Rmano
-- 
Romano Giannetti                            Dep. de Electrónica y Automática
http://www.dea.icai.upcomillas.es/romano    Univ. Pontificia Comillas (MADRID)


--
La presente comunicación tiene carácter confidencial y es para el exclusivo uso del destinatario indicado en la misma. Si Ud. no es el destinatario indicado, le informamos que cualquier forma de distribución, reproducción o uso de esta comunicación y/o de la información contenida en la misma están estrictamente prohibidos por la ley. Si Ud. ha recibido esta comunicación por error, por favor, notifíquelo inmediatamente al remitente contestando a este mensaje y proceda a continuación a destruirlo. Gracias por su colaboración.

This communication contains confidential information. It is for the exclusive use of the intended addressee. If you are not the intended addressee, please note that any form of distribution, copying or use of this communication or the information in it is strictly prohibited by law. If you have received this communication in error, please immediately notify the sender by reply e-mail and destroy this message. Thank you for your cooperation. 

Re: [Bug 10843] Display artifacts on XOrg logout with PAT kernel and VESA framebuffer

[Frans Pop]

On Sunday 15 June 2008, Rafael J. Wysocki wrote:
> On Sunday, 15 of June 2008, Romano Giannetti wrote:
> > It happens to me too.

Exactly what happens to you to? Do you also see the artifacts?
Do you also use vesafb? Do the artifacts go away if you boot 
with 'video=vfb:off' to disable the framebuffer? Do they go away if you 
compile a kernel without PAT or boot with 'nopat'?

> > Do you see http://bugzilla.kernel.org/show_bug.cgi?id=10892 ?

No. Is that related to PAT being enabled?

> Do these two bug entries refer to the same problem?

Looks unrelated to me.

Cheers,
FJP

Re: [Bug 10843] Display artifacts on XOrg logout with PAT kernel and VESA framebuffer

[Romano Giannetti]

On Sun, 2008-06-15 at 12:40 +0200, Rafael J. Wysocki wrote:
> On Sunday, 15 of June 2008, Romano Giannetti wrote:
> > 
> > On Sat, 2008-06-14 at 23:59 +0200, Frans Pop wrote:
> > > \>
> > > > Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=10843
> > > > Subject	: Display artifacts on XOrg logout with PAT kernel and VESA
> > > > 		  framebuffer
> > > > Submitter	: Frans Pop <elendil@planet.nl> 
> > > > Date		: 2008-05-31 14:04 (15 days old)
> > > > References	: http://lkml.org/lkml/2008/6/7/206
> > > 
> > > Yes. See also: http://lkml.org/lkml/2008/6/13/159
> > > -
> > 
> > It happens to me too. Do you see
> > http://bugzilla.kernel.org/show_bug.cgi?id=10892 ?
> 
> Do these two bug entries refer to the same problem?
> 
> Rafael

I do not know, just a wild guess. I noticed the flashing color when
doing shutdown, and being Intel the common chipset...

-- 
Romano Giannetti                            Dep. de Electrónica y Automática
http://www.dea.icai.upcomillas.es/romano    Univ. Pontificia Comillas (MADRID)


--
La presente comunicación tiene carácter confidencial y es para el exclusivo uso del destinatario indicado en la misma. Si Ud. no es el destinatario indicado, le informamos que cualquier forma de distribución, reproducción o uso de esta comunicación y/o de la información contenida en la misma están estrictamente prohibidos por la ley. Si Ud. ha recibido esta comunicación por error, por favor, notifíquelo inmediatamente al remitente contestando a este mensaje y proceda a continuación a destruirlo. Gracias por su colaboración.

This communication contains confidential information. It is for the exclusive use of the intended addressee. If you are not the intended addressee, please note that any form of distribution, copying or use of this communication or the information in it is strictly prohibited by law. If you have received this communication in error, please immediately notify the sender by reply e-mail and destroy this message. Thank you for your cooperation. 

Re: [Bug 10843] Display artifacts on XOrg logout with PAT kernel and VESA framebuffer

[Romano Giannetti]

On Sun, 2008-06-15 at 13:25 +0200, Frans Pop wrote:

> 
> > > Do you see http://bugzilla.kernel.org/show_bug.cgi?id=10892 ?
> 
> No. Is that related to PAT being enabled?
> 
> > Do these two bug entries refer to the same problem?
> 
> Looks unrelated to me.

Yes, maybe you're right. Could not test too, booting with nopat gave me
two times in a row the black screen. 

Mmhhh....

Romano 
-- 
Romano Giannetti                            Dep. de Electrónica y Automática
http://www.dea.icai.upcomillas.es/romano    Univ. Pontificia Comillas (MADRID)


--
La presente comunicación tiene carácter confidencial y es para el exclusivo uso del destinatario indicado en la misma. Si Ud. no es el destinatario indicado, le informamos que cualquier forma de distribución, reproducción o uso de esta comunicación y/o de la información contenida en la misma están estrictamente prohibidos por la ley. Si Ud. ha recibido esta comunicación por error, por favor, notifíquelo inmediatamente al remitente contestando a este mensaje y proceda a continuación a destruirlo. Gracias por su colaboración.

This communication contains confidential information. It is for the exclusive use of the intended addressee. If you are not the intended addressee, please note that any form of distribution, copying or use of this communication or the information in it is strictly prohibited by law. If you have received this communication in error, please immediately notify the sender by reply e-mail and destroy this message. Thank you for your cooperation. 

Re: [Bug 10843] Display artifacts on XOrg logout with PAT kernel and VESA framebuffer

[Adrian Bunk]

On Sun, Jun 15, 2008 at 01:25:17PM +0200, Romano Giannetti wrote:
> 
> On Sun, 2008-06-15 at 13:39 +0300, Adrian Bunk wrote:
> > On Sun, Jun 15, 2008 at 12:22:59PM +0200, Romano Giannetti wrote:
> > > 
> 
> > > > Yes. See also: http://lkml.org/lkml/2008/6/13/159
> > > > -
> > > 
> > > It happens to me too. Do you see
> > > http://bugzilla.kernel.org/show_bug.cgi?id=10892 ?
> > 
> > Does disabling CONFIG_X86_PAT also fix it for you?
> 
> Dunno. Do I need to recompile or there is some boot option to disable
> it?

There's a nopat boot option.

> Rmano

cu
Adrian

-- 

       "Is there not promise of rain?" Ling Tan asked suddenly out
        of the darkness. There had been need of rain for many days.
       "Only a promise," Lao Er said.
                                       Pearl S. Buck - Dragon Seed

RE: [Bug 10843] Display artifacts on XOrg logout with PAT kernel and VESA framebuffer

[Siddha, Suresh B]

Frans Pop wrote:
> On Saturday 14 June 2008, Rafael J. Wysocki wrote:
> > The following bug entry is on the current list of known regressions
> > from 2.6.25.  Please verify if it still should be listed.
> >
> > Bug-Entry     : http://bugzilla.kernel.org/show_bug.cgi?id=10843
> > Subject       : Display artifacts on XOrg logout with PAT kernel and VESA
> >                 framebuffer
> > Submitter     : Frans Pop <elendil@planet.nl>
> > Date          : 2008-05-31 14:04 (15 days old)
> > References    : http://lkml.org/lkml/2008/6/7/206
>
> Yes. See also: http://lkml.org/lkml/2008/6/13/159

Frans, With or with out pat, in the recent kernels (like 2.6.26-rc4/rc5 etc), ioremap()
uses  UC- and PCI mmap of /sys/devices/pci.../resource (used by X) uses UC-

And fb_mmap() also uses UC-.

It's interesting that you don't see this artifact with "nopat". Essentially with
or with out pat enabled, we use the same memory attributes. So depending on the
MTRR setup (set by X server), effective memory attribute across different mappings
should be same (which is UC- or WC with mtrr).

Can you also check, if there is any impact with kernel boot param for vesafb "mtrr:3"?

thanks,
suresh

Re: [Bug 10843] Display artifacts on XOrg logout with PAT kernel and VESA framebuffer

[Frans Pop]

On Sunday 15 June 2008, Siddha, Suresh B wrote:
> > Bug-Entry     : http://bugzilla.kernel.org/show_bug.cgi?id=10843
> > Subject       : Display artifacts on XOrg logout with PAT kernel
> > and VESA framebuffer
> > Submitter     : Frans Pop <elendil@planet.nl>
> > Date          : 2008-05-31 14:04 (15 days old)
> > References    : http://lkml.org/lkml/2008/6/7/206
>
> Can you also check, if there is any impact with kernel boot param for
> vesafb "mtrr:3"?

Hello Suresh. Thanks for responding.

I've done 4 successive boots with the boot parameters as shown below.
Each boot was basically: set correct parameters in grub -> login to KDE
                         -> reboot and check for artifacts.

1) (none)                      --> clean
2) vga=791                     --> artifacts
3) vga=791 nopat               --> clean
4) vga=791 video=vesafb:mtrr:3 --> artifacts

So the mtrr option did not help (if I passed it correctly; the double ":"
is somewhat non-intuitive). The kernel log also does not show any
difference I can see in the last boot, but I don't know if the mtrr option
is supposed to show up in any way.

>From the kernel log for each boot:
1) x86 PAT enabled: cpu 0, old 0x7040600070406, new 0x7010600070106
   Console: colour VGA+ 80x25
   console [tty0] enabled

2) x86 PAT enabled: cpu 0, old 0x7040600070406, new 0x7010600070106
   Console: colour dummy device 80x25
   console [tty0] enabled
   vesafb: framebuffer at 0x80000000, mapped to 0xffffc20000900000, using 3072k, total 7872k
   vesafb: mode is 1024x768x16, linelength=2048, pages=4
   vesafb: scrolling: redraw
   vesafb: Truecolor: size=0:5:6:5, shift=0:11:5:0
   Console: switching to colour frame buffer device 128x48
   fb0: VESA VGA frame buffer device

3) PAT support disabled
   Console: colour dummy device 80x25
   console [tty0] enabled
   vesafb: framebuffer at 0x80000000, mapped to 0xffffc20000900000, using 3072k, total 7872k
   vesafb: mode is 1024x768x16, linelength=2048, pages=4
   vesafb: scrolling: redraw
   vesafb: Truecolor: size=0:5:6:5, shift=0:11:5:0
   Console: switching to colour frame buffer device 128x48
   fb0: VESA VGA frame buffer device

4) x86 PAT enabled: cpu 0, old 0x7040600070406, new 0x7010600070106
   Console: colour dummy device 80x25
   console [tty0] enabled
   vesafb: framebuffer at 0x80000000, mapped to 0xffffc20000900000, using 3072k, total 7872k
   vesafb: mode is 1024x768x16, linelength=2048, pages=4
   vesafb: scrolling: redraw
   vesafb: Truecolor: size=0:5:6:5, shift=0:11:5:0
   Console: switching to colour frame buffer device 128x48
   fb0: VESA VGA frame buffer device

Hope that helps. If you need any additional information, please ask.

Cheers,
FJP

Re: [Bug 10843] Display artifacts on XOrg logout with PAT kernel and VESA framebuffer

[Suresh Siddha]

On Sun, Jun 15, 2008 at 04:02:10PM -0700, Frans Pop wrote:
> I've done 4 successive boots with the boot parameters as shown below.
> Each boot was basically: set correct parameters in grub -> login to KDE
>                          -> reboot and check for artifacts.
> 
> 1) (none)                      --> clean
> 2) vga=791                     --> artifacts
> 3) vga=791 nopat               --> clean
> 4) vga=791 video=vesafb:mtrr:3 --> artifacts
> 
> So the mtrr option did not help (if I passed it correctly; the double ":"
> is somewhat non-intuitive). The kernel log also does not show any
> difference I can see in the last boot, but I don't know if the mtrr option
> is supposed to show up in any way.

If the initlevel is '3', then the mtrr option will show up in /proc/mtrr
otheriwse not. In init level '5', X server will add the mtrr (irrespective
of boot option, if it's not already there) and will remove it when the X process
completes its execution.

Can you also please try if "mtrr:1" makes any difference. This will setup the
mapping as UC during boot. Apart from PAT WC mapping(which we shouldn't be using
in your current setup), UC MTRR should override all the other PAT mappings and
should be consistent across X and VT console mappings. As such, if the
problem is because of improper aliasing, then with this UC MTRR,
my understanding is that we shouldn't see any artifacts with the "mtrr:1".

with this mtrr:1, we should now see a UC mtrr setting in /proc/mtrr.

thanks,
suresh

Re: [Bug 10843] Display artifacts on XOrg logout with PAT kernel and VESA framebuffer

[Frans Pop]

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

On Monday 16 June 2008, Suresh Siddha wrote:
> If the initlevel is '3', then the mtrr option will show up in
> /proc/mtrr otherwise not.

What is this init level and how would I set it? Do I need to?

> In init level '5', X server will add the mtrr 
> (irrespective of boot option, if it's not already there) and will
> remove it when the X process completes its execution.

That was a useful pointer. I do see some differences when I compare
Xorg logs; see below.

> Can you also please try if "mtrr:1" makes any difference. This will
> setup the mapping as UC during boot. Apart from PAT WC mapping(which we
> shouldn't be using in your current setup), UC MTRR should override all
> the other PAT mappings and should be consistent across X and VT console
> mappings. As such, if the problem is because of improper aliasing, then
> with this UC MTRR, my understanding is that we shouldn't see any
> artifacts with the "mtrr:1".
> with this mtrr:1, we should now see a UC mtrr setting in /proc/mtrr.

mtrr:1 still gives the artifacts and no any difference to /proc/mtrr.

Here's /proc/cmdline + /proc/mtrr for three different boots:
root=/dev/mapper/main-root ro vga=791 quiet
reg00: base=0x00000000 (   0MB), size=2048MB: write-back, count=1
reg01: base=0x7f800000 (2040MB), size=   8MB: uncachable, count=1
reg02: base=0x7f700000 (2039MB), size=   1MB: uncachable, count=1
reg03: base=0x80000000 (2048MB), size= 256MB: write-combining, count=1

root=/dev/mapper/main-root ro vga=791 quiet video=vesafb:mtrr:1
reg00: base=0x00000000 (   0MB), size=2048MB: write-back, count=1
reg01: base=0x7f800000 (2040MB), size=   8MB: uncachable, count=1
reg02: base=0x7f700000 (2039MB), size=   1MB: uncachable, count=1
reg03: base=0x80000000 (2048MB), size= 256MB: write-combining, count=1

root=/dev/mapper/main-root ro vga=791 quiet video=vesafb:mtrr:3
reg00: base=0x00000000 (   0MB), size=2048MB: write-back, count=1
reg01: base=0x7f800000 (2040MB), size=   8MB: uncachable, count=1
reg02: base=0x7f700000 (2039MB), size=   1MB: uncachable, count=1
reg03: base=0x80000000 (2048MB), size= 256MB: write-combining, count=1


I do see some differences in Xorg logs, so it does seem that the mtrr
options _are_ being recognized.
Attached my "normal" Xorg log (with 'vga=791') which I used as the base
for the diffs below. Other than shown, the logs are identical.

With mtrr:1 I get (added at the end of the log):
@@ -688,3 +688,11 @@
 (II) evaluating device (Generic Keyboard)
 (II) XINPUT: Adding extended input device "Generic Keyboard" (type: KEYBOARD)
 (II) Configured Mouse: ps2EnableDataReporting: succeeded
+(II) intel(0): xf86UnbindGARTMemory: unbind key 0
+(II) intel(0): xf86UnbindGARTMemory: unbind key 1
+(II) intel(0): xf86UnbindGARTMemory: unbind key 2
+(II) intel(0): xf86UnbindGARTMemory: unbind key 3
+(II) intel(0): xf86UnbindGARTMemory: unbind key 4
+(II) intel(0): [drm] removed 1 reserved context for kernel
+(II) intel(0): [drm] unmapping 8192 bytes of SAREA 0x2efff000 at 0x7f2788ab9000
+(II) intel(0): [drm] Closed DRM master.

And with mtrr:3 (added in the middle):
@@ -577,6 +577,7 @@
 (II) intel(0): [drm] Initialized kernel agp heap manager, 33554432
 (II) intel(0): [dri] visual configs initialized
 (II) intel(0): Page Flipping disabled
+(==) intel(0): Removed MMIO write-combining range (0x80000000,0x400000)
 (==) intel(0): Write-combining range (0x80000000,0x10000000)
 (II) intel(0): vgaHWGetIOBase: hwp->IOBase is 0x03d0, hwp->PIOOffset is 0x0000
 (II) EXA(0): Offscreen pixmap area of 39321600 bytes


I've also checked with 'nopat'. That gives no differences in /proc/mtrr,
and also no differences in the Xorg log when compared with my normal boot
(vga=791).

Cheers,
FJP


[-- Attachment #2: Xorg.0.log.gz --]
[-- Type: application/x-gzip, Size: 7129 bytes --]

Re: [Bug 10843] Display artifacts on XOrg logout with PAT kernel and VESA framebuffer

[Frans Pop]

On Monday 16 June 2008, Frans Pop wrote:
> I do see some differences in Xorg logs, so it does seem that the mtrr
> options _are_ being recognized.
> Attached my "normal" Xorg log (with 'vga=791') which I used as the base
> for the diffs below. Other than shown, the logs are identical.
>
> With mtrr:1 I get (added at the end of the log):
> @@ -688,3 +688,11 @@
>  (II) evaluating device (Generic Keyboard)
>  (II) XINPUT: Adding extended input device "Generic Keyboard" (type:
> KEYBOARD)
> (II) Configured Mouse: ps2EnableDataReporting: succeeded 
> +(II) intel(0): xf86UnbindGARTMemory: unbind key 0
> +(II) intel(0): xf86UnbindGARTMemory: unbind key 1
> +(II) intel(0): xf86UnbindGARTMemory: unbind key 2
> +(II) intel(0): xf86UnbindGARTMemory: unbind key 3
> +(II) intel(0): xf86UnbindGARTMemory: unbind key 4
> +(II) intel(0): [drm] removed 1 reserved context for kernel
> +(II) intel(0): [drm] unmapping 8192 bytes of SAREA 0x2efff000 at
> 0x7f2788ab9000
> +(II) intel(0): [drm] Closed DRM master. 

Oops. Just realized that this is completely bogus. I used the .old log for 
this one while I used logs for still running Xorg sessions for the 
others. So this was actually the only one that contains Xorg shutdown 
messages at all.

> And with mtrr:3 (added in the middle):
> @@ -577,6 +577,7 @@
>  (II) intel(0): [drm] Initialized kernel agp heap manager, 33554432
>  (II) intel(0): [dri] visual configs initialized
>  (II) intel(0): Page Flipping disabled
> +(==) intel(0): Removed MMIO write-combining range
> (0x80000000,0x400000)
> (==) intel(0): Write-combining range (0x80000000,0x10000000)
>  (II) intel(0): vgaHWGetIOBase: hwp->IOBase is 0x03d0, hwp->PIOOffset
> is 0x0000
> (II) EXA(0): Offscreen pixmap area of 39321600 bytes 

This is still valid though.

Sorry for the confusion.

2.6.26-rc7-git2: Reported regressions from 2.6.25

[Rafael J. Wysocki]

[Note to bug reporters: If you can, please always add
kernel-testers@vger.kernel.org to the CC lists of your reports, as that will
help to filter them out of the other LKML traffic.  Also, if you report a
regression, please add '[regression]' or something similar to the subject.]

This message contains a list of some regressions from 2.6.25, for which there
are no fixes in the mainline I know of.  If any of them have been fixed already,
please let me know.

If you know of any other unresolved regressions from 2.6.25, please let me know
either and I'll add them to the list.  Also, please let me know if any of the
entries below are invalid.

Each entry from the list will be sent additionally in an automatic reply to
this message with CCs to the people involved in reporting and handling the
issue.


Listed regressions statistics:

  Date          Total  Pending  Unresolved
  ----------------------------------------
  2008-06-22      148       39          28
  2008-06-14      130       37          28
  2008-06-07      125       48          33
  2008-05-31      115       52          31
  2008-05-24       94       47          28
  2008-05-18       80       51          37
  2008-05-11       53       46          34


Unresolved regressions
----------------------

Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=10962
Subject		: 2.6.26-rc2 WARNING from usb-serial, and then my gps is dead
Submitter	: Helge Hafting <helge.hafting@aitel.hist.no>
Date		: 2008-06-22 18:22 (1 days old)
References	: http://marc.info/?l=linux-kernel&m=121415899320685&w=4


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=10961
Subject		: 2.6.26-rc: nfsd hangs for a few sec
Submitter	: Alexander Beregalov <a.beregalov@gmail.com>
Date		: 2008-06-21 12:57 (2 days old)
References	: http://marc.info/?l=linux-kernel&m=121405308328004&w=4
		  http://marc.info/?l=linux-kernel&m=121412880115289&w=4
Handled-By	: Linus Torvalds <torvalds@linux-foundation.org>
		  Mel Gorman <mel@csn.ul.ie>
		  Christoph Lameter <clameter@sgi.com>


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=10960
Subject		: 2.6.26-rc: SPARC: Sun Ultra 10 can not boot
Submitter	: Alexander Beregalov <a.beregalov@gmail.com>
Date		: 2008-06-19 14:07 (4 days old)
References	: http://marc.info/?l=linux-kernel&m=121388456519637&w=4
Handled-By	: David Miller <davem@davemloft.net>


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=10959
Subject		: stuck tcp connections 2.6.26-rc7
Submitter	: Justin Mattock <justinmattock@gmail.com>
Date		: 2008-06-22 18:09 (1 days old)
References	: http://marc.info/?l=linux-kernel&m=121415821219644&w=4


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=10957
Subject		: pata_pcmcia with Sandisk Extreme III 8GB
Submitter	: Komuro <komurojun-mbn@nifty.com>
Date		: 2008-06-07 13:37 (16 days old)
References	: http://marc.info/?l=linux-kernel&m=121284627119861&w=4
Handled-By	: Tejun Heo <htejun@gmail.com>
		  Dominik Brodowski <linux@dominikbrodowski.net>


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=10956
Subject		: v2.6.26-rc7: BUG: unable to handle kernel NULL pointer dereference
Submitter	: Vegard Nossum <vegard.nossum@gmail.com>
Date		: 2008-06-22 12:56 (1 days old)
References	: http://marc.info/?l=linux-kernel&m=121413950227884&w=4


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=10955
Subject		: v2.6.26-rc7: BUG task_struct: Poison overwritten
Submitter	: Vegard Nossum <vegard.nossum@gmail.com>
Date		: 2008-06-21 19:24 (2 days old)
References	: http://marc.info/?l=linux-kernel&m=121407641925121&w=4
Handled-By	: Peter Zijlstra <a.p.zijlstra@chello.nl>


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=10954
Subject		: hda_intel: azx_get_response timeout, switching to polling mode: last cmd=0x011f000c
Submitter	: Justin Mattock <justinmattock@gmail.com>
Date		: 2008-06-21 2:05 (2 days old)
References	: http://marc.info/?l=linux-kernel&m=121401399622190&w=4


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=10951
Subject		: alpha build failure
Submitter	: Adrian Bunk <bunk@kernel.org>
Date		: 2008-06-22 02:13 (1 days old)
References	: http://lkml.org/lkml/2008/6/22/18


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=10923
Subject		: System turns off during wake from S3, Wake Regression from 2.6.25
Submitter	: Dionisus Torimens <djtm@gmx.net>
Date		: 2008-06-15 16:24 (8 days old)


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=10919
Subject		: [regression] display dimming is slow and laggy - Acer Travelmate 661lci
Submitter	: Maximilian Engelhardt <maxi@daemonizer.de>
Date		: 2008-06-14 22:31 (9 days old)
References	: http://marc.info/?l=linux-kernel&m=121348428828320&w=4


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=10912
Subject		: Regressions in the last kernels
Submitter	: werner <werner@sys-linux.yi.org>
Date		: 2008-06-14 18:26 (9 days old)
References	: http://marc.info/?l=linux-kernel&m=121346933911641&w=4
		  http://lkml.org/lkml/2008/6/15/35


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=10906
Subject		: repeatable slab corruption with LTP msgctl08
Submitter	: Andrew Morton <akpm@linux-foundation.org>
Date		: 2008-06-12 5:13 (11 days old)
References	: http://marc.info/?l=linux-kernel&m=121324775927704&w=4
Handled-By	: Pekka J Enberg <penberg@cs.helsinki.fi>
		  Christoph Lameter <clameter@sgi.com>
		  Manfred Spraul <manfred@colorfullife.com>
		  Andi Kleen <andi@firstfloor.org>


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=10892
Subject		: Sometime (often) X come out blank (black screen) on cold boot - Intel chipset
Submitter	: Romano Giannetti <romano.giannetti@gmail.com>
Date		: 2008-06-10 05:33 (13 days old)
References	: http://lkml.org/lkml/2008/6/10/137


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=10872
Subject		: x86_64 boot hang when CONFIG_NUMA=n
Submitter	: Randy Dunlap <randy.dunlap@oracle.com>
Date		: 2008-06-05 21:50 (18 days old)
References	: http://marc.info/?l=linux-kernel&m=121270308607116&w=4
		  http://lkml.org/lkml/2008/6/11/355
		  http://lkml.org/lkml/2008/6/15/117
Handled-By	: Yinghai Lu <yhlu.kernel@gmail.com>


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=10868
Subject		: Oops on loading ipaq module since 2.6.26, prevents use of device
Submitter	: Adam Williamson <awilliamson@mandriva.com>
Date		: 2008-06-05 17:39 (18 days old)
Handled-By	: Alan Cox <alan@redhat.com>


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=10865
Subject		: Oops trying to mount an ntfs partition on thinkpad
Submitter	: Alex Romosan <romosan@sycorax.lbl.gov>
Date		: 2008-06-05 14:47 (18 days old)
References	: http://marc.info/?l=linux-kernel&m=121267834421414&w=4


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=10862
Subject		: forcedeth: lockdep warning on ethtool -s
Submitter	: Tobias Diedrich <ranma+kernel@tdiedrich.de>
Date		: 2008-06-01 8:37 (22 days old)
References	: http://marc.info/?l=linux-kernel&m=121230964032247&w=4


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=10861
Subject		: 2.6.26-rc4-git2 - long pause during boot
Submitter	: Chris Clayton <chris2553@googlemail.com>
Date		: 2008-06-01 4:15 (22 days old)
References	: http://marc.info/?l=linux-kernel&m=121229382917834&w=4


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=10843
Subject		: Display artifacts on XOrg logout with PAT kernel and VESA framebuffer
Submitter	: Frans Pop <elendil@planet.nl>
Date		: 2008-05-31 14:04 (23 days old)
References	: http://lkml.org/lkml/2008/6/7/206
		  http://lkml.org/lkml/2008/6/15/119


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=10827
Subject		: 2.6.26rc4 GFS2 oops.
Submitter	: Dave Jones <davej@redhat.com>
Date		: 2008-05-27 15:44 (27 days old)
References	: http://lkml.org/lkml/2008/5/27/297


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=10826
Subject		: NFS oops in 2.6.26rc4
Submitter	: Dave Jones <davej@redhat.com>
Date		: 2008-05-27 19:04 (27 days old)
References	: http://marc.info/?l=linux-kernel&m=121191548915522&w=4


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=10821
Subject		: rt25xx: lock dependency warning, association failure, and kmalloc corruption
Submitter	: Christian Casteyde <casteyde.christian@free.fr>
Date		: 2008-05-29 14:30 (25 days old)


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=10786
Subject		: parisc: 64bit SMP does not boot on J5600
Submitter	: Domenico Andreoli <cavokz@gmail.com>
Date		: 2008-05-22 16:14 (32 days old)
References	: http://marc.info/?l=linux-kernel&m=121147328028081&w=4


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=10741
Subject		: bug in `tty: BKL pushdown'?
Submitter	: Johannes Weiner <hannes@saeurebad.de>
Date		: 2008-05-18 2:16 (36 days old)
References	: http://marc.info/?l=linux-kernel&m=121107706506181&w=4
		  http://lkml.org/lkml/2008/6/16/104
Handled-By	: Alan Cox <alan@lxorguk.ukuu.org.uk>


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=10725
Subject		: USB Mass storage mount fails: Write protect on
Submitter	: Maciej Rutecki <maciej.rutecki@gmail.com>
Date		: 2008-05-16 14:55 (38 days old)
References	: http://marc.info/?l=linux-kernel&m=121095168003572&w=4


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=10714
Subject		: powerpc: Badness seen on 2.6.26-rc2 with lockdep enabled
Submitter	: Balbir Singh <balbir@linux.vnet.ibm.com>
Date		: 2008-05-14 12:57 (40 days old)
References	: http://marc.info/?l=linux-kernel&m=121076917429133&w=4
Handled-By	: Benjamin Herrenschmidt <benh@kernel.crashing.org>


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=10629
Subject		: 2.6.26-rc1-$sha1: RIP __d_lookup+0x8c/0x160
Submitter	: Alexey Dobriyan <adobriyan@gmail.com>
Date		: 2008-05-05 09:59 (49 days old)
References	: http://lkml.org/lkml/2008/5/5/28
Handled-By	: Paul E. McKenney <paulmck@linux.vnet.ibm.com>


Regressions with patches
------------------------

Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=10958
Subject		: LMSENSORS: 2.6.26-rc, enabling ACPI Termal Zone support costs sensors
Submitter	: Rene Herman <rene.herman@keyaccess.nl>
Date		: 2008-06-22 0:47 (1 days old)
References	: http://marc.info/?l=linux-kernel&m=121409569819064&w=4
Handled-By	: Hans de Goede <j.w.r.degoede@hhs.nl>
		  Rene Herman <rene.herman@keyaccess.nl>
Patch		: http://lkml.org/lkml/2008/6/22/83


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=10927
Subject		: Dell laptops: reboot instead of resume
Submitter	: Kirill A. Shutemov <kirill@shutemov.name>
Date		: 2008-06-16 07:31 (7 days old)
Handled-By	: H. Peter Anvin <hpa@kernel.org>
Patch		: http://bugzilla.kernel.org/attachment.cgi?id=16549&action=view


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=10918
Subject		: 2.6.26-rc5: SLUB debug, lockdep warning...
Submitter	: Daniel J Blueman <daniel.blueman@gmail.com>
Date		: 2008-06-14 10:54 (9 days old)
References	: http://marc.info/?l=linux-kernel&m=121344091109597&w=4
Handled-By	: Vegard Nossum <vegard.nossum@gmail.com>
		  Daniel J Blueman <daniel.blueman@gmail.com>
Patch		: http://bugzilla.kernel.org/show_bug.cgi?id=10918#c2


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=10860
Subject		: total system freeze at boot with 2.6.26-rc
Submitter	: Christian Casteyde <casteyde.christian@free.fr>
Date		: 2008-06-05 12:38 (18 days old)
Handled-By	: Tejun Heo <htejun@gmail.com>
Patch		: http://bugzilla.kernel.org/attachment.cgi?id=16556


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=10830
Subject		: two different oopses with 2.6.26-rc4
Submitter	: Alejandro Riveira Fernández <alejandro.riveira@gmail.com>
Date		: 2008-05-28 9:50 (26 days old)
References	: http://marc.info/?l=linux-kernel&m=121196833026310&w=4
Handled-By	: Johannes Berg <johannes@sipsolutions.net>
		  Andrew Morton <akpm@linux-foundation.org>
		  Peter Zijlstra <a.p.zijlstra@chello.nl>
Patch		: http://lkml.org/lkml/2008/5/20/683


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=10815
Subject		: 2.6.26-rc4: RIP find_pid_ns+0x6b/0xa0
Submitter	: Alexey Dobriyan <adobriyan@gmail.com>
Date		: 2008-05-27 09:23 (27 days old)
References	: http://lkml.org/lkml/2008/5/27/9
		  http://lkml.org/lkml/2008/6/14/87
Handled-By	: Oleg Nesterov <oleg@tv-sign.ru>
		  Linus Torvalds <torvalds@linux-foundation.org>
		  Paul E. McKenney <paulmck@linux.vnet.ibm.com>
Patch		: http://lkml.org/lkml/2008/5/28/16


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=10730
Subject		: build issue #503 for v2.6.26-rc2-433-gf26a398 : undefined reference to `request_firmware'
Submitter	: Toralf Förster <toralf.foerster@gmx.de>
Date		: 2008-05-16 17:06 (38 days old)
References	: http://marc.info/?l=linux-kernel&m=121095777616792&w=4
Handled-By	: James Bottomley <James.Bottomley@HansenPartnership.com>
Patch		: http://marc.info/?l=linux-scsi&m=121101871800303&w=4


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=10726
Subject		: x86-64 NODES_SHIFT compile failure.
Submitter	: Dave Jones <davej@codemonkey.org.uk>
Date		: 2008-05-16 12:54 (38 days old)
References	: http://lkml.org/lkml/2008/5/16/312
Handled-By	: Mike Travis <travis@sgi.com>
Patch		: http://lkml.org/lkml/2008/5/16/343


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=10724
Subject		: ACPI: EC: GPE storm detected, disabling EC GPE
Submitter	: Justin Mattock <justinmattock@gmail.com>
Date		: 2008-05-16 6:17 (38 days old)
References	: http://marc.info/?l=linux-kernel&m=121091875711824&w=4
		  http://lkml.org/lkml/2008/5/18/168
		  http://lkml.org/lkml/2008/5/25/195
Patch		: http://bugzilla.kernel.org/attachment.cgi?id=16364&action=view
		  http://bugzilla.kernel.org/attachment.cgi?id=16365&action=view


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=10493
Subject		: mips BCM47XX compile error
Submitter	: Adrian Bunk <adrian.bunk@movial.fi>
Date		: 2008-04-20 17:07 (64 days old)
References	: http://lkml.org/lkml/2008/4/20/34
		  http://lkml.org/lkml/2008/5/12/30
		  http://lkml.org/lkml/2008/5/18/131
		  http://lkml.org/lkml/2008/5/31/202
		  http://lkml.org/lkml/2008/6/7/154
Patch		: http://marc.info/?l=linux-kernel&m=120876451216558&w=2


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=9791
Subject		: Clock is running too fast^Wslow using acpi_pm clocksource
Submitter	: tosn00j02@sneakemail.com
Date		: 2008-05-03 05:09 (51 days old)
Handled-By	: Maciej W. Rozycki <macro@linux-mips.org>
Patch		: http://bugzilla.kernel.org/attachment.cgi?id=16180


For details, please visit the bug entries and follow the links given in
references.

As you can see, there is a Bugzilla entry for each of the listed regressions.
There also is a Bugzilla entry used for tracking the regressions from 2.6.25,
unresolved as well as resolved, at:

http://bugzilla.kernel.org/show_bug.cgi?id=10492

Please let me know if there are any Bugzilla entries that should be added to
the list in there.

Thanks,
Rafael

[Bug #10493] mips BCM47XX compile error

[Rafael J. Wysocki]

This message has been generated automatically as a part of a report
of recent regressions.

The following bug entry is on the current list of known regressions
from 2.6.25.  Please verify if it still should be listed.


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=10493
Subject		: mips BCM47XX compile error
Submitter	: Adrian Bunk <adrian.bunk@movial.fi>
Date		: 2008-04-20 17:07 (64 days old)
References	: http://lkml.org/lkml/2008/4/20/34
		  http://lkml.org/lkml/2008/5/12/30
		  http://lkml.org/lkml/2008/5/18/131
		  http://lkml.org/lkml/2008/5/31/202
		  http://lkml.org/lkml/2008/6/7/154
Patch		: http://marc.info/?l=linux-kernel&m=120876451216558&w=2

[Bug #10629] 2.6.26-rc1-$sha1: RIP __d_lookup+0x8c/0x160

[Rafael J. Wysocki]

This message has been generated automatically as a part of a report
of recent regressions.

The following bug entry is on the current list of known regressions
from 2.6.25.  Please verify if it still should be listed.


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=10629
Subject		: 2.6.26-rc1-$sha1: RIP __d_lookup+0x8c/0x160
Submitter	: Alexey Dobriyan <adobriyan@gmail.com>
Date		: 2008-05-05 09:59 (49 days old)
References	: http://lkml.org/lkml/2008/5/5/28
Handled-By	: Paul E. McKenney <paulmck@linux.vnet.ibm.com>

[Bug #10714] powerpc: Badness seen on 2.6.26-rc2 with lockdep enabled

[Rafael J. Wysocki]

This message has been generated automatically as a part of a report
of recent regressions.

The following bug entry is on the current list of known regressions
from 2.6.25.  Please verify if it still should be listed.


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=10714
Subject		: powerpc: Badness seen on 2.6.26-rc2 with lockdep enabled
Submitter	: Balbir Singh <balbir@linux.vnet.ibm.com>
Date		: 2008-05-14 12:57 (40 days old)
References	: http://marc.info/?l=linux-kernel&m=121076917429133&w=4
Handled-By	: Benjamin Herrenschmidt <benh@kernel.crashing.org>

[Bug #10724] ACPI: EC: GPE storm detected, disabling EC GPE

[Rafael J. Wysocki]

This message has been generated automatically as a part of a report
of recent regressions.

The following bug entry is on the current list of known regressions
from 2.6.25.  Please verify if it still should be listed.


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=10724
Subject		: ACPI: EC: GPE storm detected, disabling EC GPE
Submitter	: Justin Mattock <justinmattock@gmail.com>
Date		: 2008-05-16 6:17 (38 days old)
References	: http://marc.info/?l=linux-kernel&m=121091875711824&w=4
		  http://lkml.org/lkml/2008/5/18/168
		  http://lkml.org/lkml/2008/5/25/195
Patch		: http://bugzilla.kernel.org/attachment.cgi?id=16364&action=view
		  http://bugzilla.kernel.org/attachment.cgi?id=16365&action=view

[Bug #10725] USB Mass storage mount fails: Write protect on

[Rafael J. Wysocki]

This message has been generated automatically as a part of a report
of recent regressions.

The following bug entry is on the current list of known regressions
from 2.6.25.  Please verify if it still should be listed.


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=10725
Subject		: USB Mass storage mount fails: Write protect on
Submitter	: Maciej Rutecki <maciej.rutecki@gmail.com>
Date		: 2008-05-16 14:55 (38 days old)
References	: http://marc.info/?l=linux-kernel&m=121095168003572&w=4

[Bug #10726] x86-64 NODES_SHIFT compile failure.

[Rafael J. Wysocki]

This message has been generated automatically as a part of a report
of recent regressions.

The following bug entry is on the current list of known regressions
from 2.6.25.  Please verify if it still should be listed.


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=10726
Subject		: x86-64 NODES_SHIFT compile failure.
Submitter	: Dave Jones <davej@codemonkey.org.uk>
Date		: 2008-05-16 12:54 (38 days old)
References	: http://lkml.org/lkml/2008/5/16/312
Handled-By	: Mike Travis <travis@sgi.com>
Patch		: http://lkml.org/lkml/2008/5/16/343

[Bug #10730] build issue #503 for v2.6.26-rc2-433-gf26a398 : undefined reference to `request_firmware'

[Rafael J. Wysocki]

This message has been generated automatically as a part of a report
of recent regressions.

The following bug entry is on the current list of known regressions
from 2.6.25.  Please verify if it still should be listed.


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=10730
Subject		: build issue #503 for v2.6.26-rc2-433-gf26a398 : undefined reference to `request_firmware'
Submitter	: Toralf Förster <toralf.foerster@gmx.de>
Date		: 2008-05-16 17:06 (38 days old)
References	: http://marc.info/?l=linux-kernel&m=121095777616792&w=4
Handled-By	: James Bottomley <James.Bottomley@HansenPartnership.com>
Patch		: http://marc.info/?l=linux-scsi&m=121101871800303&w=4

[Bug #10786] parisc: 64bit SMP does not boot on J5600

[Rafael J. Wysocki]

This message has been generated automatically as a part of a report
of recent regressions.

The following bug entry is on the current list of known regressions
from 2.6.25.  Please verify if it still should be listed.


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=10786
Subject		: parisc: 64bit SMP does not boot on J5600
Submitter	: Domenico Andreoli <cavokz@gmail.com>
Date		: 2008-05-22 16:14 (32 days old)
References	: http://marc.info/?l=linux-kernel&m=121147328028081&w=4

[Bug #10815] 2.6.26-rc4: RIP find_pid_ns+0x6b/0xa0

[Rafael J. Wysocki]

This message has been generated automatically as a part of a report
of recent regressions.

The following bug entry is on the current list of known regressions
from 2.6.25.  Please verify if it still should be listed.


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=10815
Subject		: 2.6.26-rc4: RIP find_pid_ns+0x6b/0xa0
Submitter	: Alexey Dobriyan <adobriyan@gmail.com>
Date		: 2008-05-27 09:23 (27 days old)
References	: http://lkml.org/lkml/2008/5/27/9
		  http://lkml.org/lkml/2008/6/14/87
Handled-By	: Oleg Nesterov <oleg@tv-sign.ru>
		  Linus Torvalds <torvalds@linux-foundation.org>
		  Paul E. McKenney <paulmck@linux.vnet.ibm.com>
Patch		: http://lkml.org/lkml/2008/5/28/16

[Bug #10741] bug in `tty: BKL pushdown'?

[Rafael J. Wysocki]

This message has been generated automatically as a part of a report
of recent regressions.

The following bug entry is on the current list of known regressions
from 2.6.25.  Please verify if it still should be listed.


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=10741
Subject		: bug in `tty: BKL pushdown'?
Submitter	: Johannes Weiner <hannes@saeurebad.de>
Date		: 2008-05-18 2:16 (36 days old)
References	: http://marc.info/?l=linux-kernel&m=121107706506181&w=4
		  http://lkml.org/lkml/2008/6/16/104
Handled-By	: Alan Cox <alan@lxorguk.ukuu.org.uk>

[Bug #10821] rt25xx: lock dependency warning, association failure, and kmalloc corruption

[Rafael J. Wysocki]

This message has been generated automatically as a part of a report
of recent regressions.

The following bug entry is on the current list of known regressions
from 2.6.25.  Please verify if it still should be listed.


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=10821
Subject		: rt25xx: lock dependency warning, association failure, and kmalloc corruption
Submitter	: Christian Casteyde <casteyde.christian@free.fr>
Date		: 2008-05-29 14:30 (25 days old)

[Bug #10827] 2.6.26rc4 GFS2 oops.

[Rafael J. Wysocki]

This message has been generated automatically as a part of a report
of recent regressions.

The following bug entry is on the current list of known regressions
from 2.6.25.  Please verify if it still should be listed.


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=10827
Subject		: 2.6.26rc4 GFS2 oops.
Submitter	: Dave Jones <davej@redhat.com>
Date		: 2008-05-27 15:44 (27 days old)
References	: http://lkml.org/lkml/2008/5/27/297

[Bug #10830] two different oopses with 2.6.26-rc4

[Rafael J. Wysocki]

This message has been generated automatically as a part of a report
of recent regressions.

The following bug entry is on the current list of known regressions
from 2.6.25.  Please verify if it still should be listed.


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=10830
Subject		: two different oopses with 2.6.26-rc4
Submitter	: Alejandro Riveira Fernández <alejandro.riveira@gmail.com>
Date		: 2008-05-28 9:50 (26 days old)
References	: http://marc.info/?l=linux-kernel&m=121196833026310&w=4
Handled-By	: Johannes Berg <johannes@sipsolutions.net>
		  Andrew Morton <akpm@linux-foundation.org>
		  Peter Zijlstra <a.p.zijlstra@chello.nl>
Patch		: http://lkml.org/lkml/2008/5/20/683

[Bug #10826] NFS oops in 2.6.26rc4

[Rafael J. Wysocki]

This message has been generated automatically as a part of a report
of recent regressions.

The following bug entry is on the current list of known regressions
from 2.6.25.  Please verify if it still should be listed.


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=10826
Subject		: NFS oops in 2.6.26rc4
Submitter	: Dave Jones <davej@redhat.com>
Date		: 2008-05-27 19:04 (27 days old)
References	: http://marc.info/?l=linux-kernel&m=121191548915522&w=4

[Bug #10860] total system freeze at boot with 2.6.26-rc

[Rafael J. Wysocki]

This message has been generated automatically as a part of a report
of recent regressions.

The following bug entry is on the current list of known regressions
from 2.6.25.  Please verify if it still should be listed.


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=10860
Subject		: total system freeze at boot with 2.6.26-rc
Submitter	: Christian Casteyde <casteyde.christian@free.fr>
Date		: 2008-06-05 12:38 (18 days old)
Handled-By	: Tejun Heo <htejun@gmail.com>
Patch		: http://bugzilla.kernel.org/attachment.cgi?id=16556

[Bug #10843] Display artifacts on XOrg logout with PAT kernel and VESA framebuffer

[Rafael J. Wysocki]

This message has been generated automatically as a part of a report
of recent regressions.

The following bug entry is on the current list of known regressions
from 2.6.25.  Please verify if it still should be listed.


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=10843
Subject		: Display artifacts on XOrg logout with PAT kernel and VESA framebuffer
Submitter	: Frans Pop <elendil@planet.nl>
Date		: 2008-05-31 14:04 (23 days old)
References	: http://lkml.org/lkml/2008/6/7/206
		  http://lkml.org/lkml/2008/6/15/119

[Bug #10862] forcedeth: lockdep warning on ethtool -s

[Rafael J. Wysocki]

This message has been generated automatically as a part of a report
of recent regressions.

The following bug entry is on the current list of known regressions
from 2.6.25.  Please verify if it still should be listed.


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=10862
Subject		: forcedeth: lockdep warning on ethtool -s
Submitter	: Tobias Diedrich <ranma+kernel@tdiedrich.de>
Date		: 2008-06-01 8:37 (22 days old)
References	: http://marc.info/?l=linux-kernel&m=121230964032247&w=4

[Bug #10872] x86_64 boot hang when CONFIG_NUMA=n

[Rafael J. Wysocki]

This message has been generated automatically as a part of a report
of recent regressions.

The following bug entry is on the current list of known regressions
from 2.6.25.  Please verify if it still should be listed.


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=10872
Subject		: x86_64 boot hang when CONFIG_NUMA=n
Submitter	: Randy Dunlap <randy.dunlap@oracle.com>
Date		: 2008-06-05 21:50 (18 days old)
References	: http://marc.info/?l=linux-kernel&m=121270308607116&w=4
		  http://lkml.org/lkml/2008/6/11/355
		  http://lkml.org/lkml/2008/6/15/117
Handled-By	: Yinghai Lu <yhlu.kernel@gmail.com>

[Bug #10868] Oops on loading ipaq module since 2.6.26, prevents use of device

[Rafael J. Wysocki]

This message has been generated automatically as a part of a report
of recent regressions.

The following bug entry is on the current list of known regressions
from 2.6.25.  Please verify if it still should be listed.


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=10868
Subject		: Oops on loading ipaq module since 2.6.26, prevents use of device
Submitter	: Adam Williamson <awilliamson@mandriva.com>
Date		: 2008-06-05 17:39 (18 days old)
Handled-By	: Alan Cox <alan@redhat.com>

[Bug #10865] Oops trying to mount an ntfs partition on thinkpad

[Rafael J. Wysocki]

This message has been generated automatically as a part of a report
of recent regressions.

The following bug entry is on the current list of known regressions
from 2.6.25.  Please verify if it still should be listed.


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=10865
Subject		: Oops trying to mount an ntfs partition on thinkpad
Submitter	: Alex Romosan <romosan@sycorax.lbl.gov>
Date		: 2008-06-05 14:47 (18 days old)
References	: http://marc.info/?l=linux-kernel&m=121267834421414&w=4

[Bug #10861] 2.6.26-rc4-git2 - long pause during boot

[Rafael J. Wysocki]

This message has been generated automatically as a part of a report
of recent regressions.

The following bug entry is on the current list of known regressions
from 2.6.25.  Please verify if it still should be listed.


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=10861
Subject		: 2.6.26-rc4-git2 - long pause during boot
Submitter	: Chris Clayton <chris2553@googlemail.com>
Date		: 2008-06-01 4:15 (22 days old)
References	: http://marc.info/?l=linux-kernel&m=121229382917834&w=4

[Bug #10906] repeatable slab corruption with LTP msgctl08

[Rafael J. Wysocki]

This message has been generated automatically as a part of a report
of recent regressions.

The following bug entry is on the current list of known regressions
from 2.6.25.  Please verify if it still should be listed.


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=10906
Subject		: repeatable slab corruption with LTP msgctl08
Submitter	: Andrew Morton <akpm@linux-foundation.org>
Date		: 2008-06-12 5:13 (11 days old)
References	: http://marc.info/?l=linux-kernel&m=121324775927704&w=4
Handled-By	: Pekka J Enberg <penberg@cs.helsinki.fi>
		  Christoph Lameter <clameter@sgi.com>
		  Manfred Spraul <manfred@colorfullife.com>
		  Andi Kleen <andi@firstfloor.org>

[Bug #10912] Regressions in the last kernels

[Rafael J. Wysocki]

This message has been generated automatically as a part of a report
of recent regressions.

The following bug entry is on the current list of known regressions
from 2.6.25.  Please verify if it still should be listed.


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=10912
Subject		: Regressions in the last kernels
Submitter	: werner <werner@sys-linux.yi.org>
Date		: 2008-06-14 18:26 (9 days old)
References	: http://marc.info/?l=linux-kernel&m=121346933911641&w=4
		  http://lkml.org/lkml/2008/6/15/35

[Bug #10892] Sometime (often) X come out blank (black screen) on cold boot - Intel chipset

[Rafael J. Wysocki]

This message has been generated automatically as a part of a report
of recent regressions.

The following bug entry is on the current list of known regressions
from 2.6.25.  Please verify if it still should be listed.


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=10892
Subject		: Sometime (often) X come out blank (black screen) on cold boot - Intel chipset
Submitter	: Romano Giannetti <romano.giannetti@gmail.com>
Date		: 2008-06-10 05:33 (13 days old)
References	: http://lkml.org/lkml/2008/6/10/137

[Bug #10919] [regression] display dimming is slow and laggy - Acer Travelmate 661lci

[Rafael J. Wysocki]

This message has been generated automatically as a part of a report
of recent regressions.

The following bug entry is on the current list of known regressions
from 2.6.25.  Please verify if it still should be listed.


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=10919
Subject		: [regression] display dimming is slow and laggy - Acer Travelmate 661lci
Submitter	: Maximilian Engelhardt <maxi@daemonizer.de>
Date		: 2008-06-14 22:31 (9 days old)
References	: http://marc.info/?l=linux-kernel&m=121348428828320&w=4

[Bug #10918] 2.6.26-rc5: SLUB debug, lockdep warning...

[Rafael J. Wysocki]

This message has been generated automatically as a part of a report
of recent regressions.

The following bug entry is on the current list of known regressions
from 2.6.25.  Please verify if it still should be listed.


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=10918
Subject		: 2.6.26-rc5: SLUB debug, lockdep warning...
Submitter	: Daniel J Blueman <daniel.blueman@gmail.com>
Date		: 2008-06-14 10:54 (9 days old)
References	: http://marc.info/?l=linux-kernel&m=121344091109597&w=4
Handled-By	: Vegard Nossum <vegard.nossum@gmail.com>
		  Daniel J Blueman <daniel.blueman@gmail.com>
Patch		: http://bugzilla.kernel.org/show_bug.cgi?id=10918#c2

[Bug #10927] Dell laptops: reboot instead of resume

[Rafael J. Wysocki]

This message has been generated automatically as a part of a report
of recent regressions.

The following bug entry is on the current list of known regressions
from 2.6.25.  Please verify if it still should be listed.


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=10927
Subject		: Dell laptops: reboot instead of resume
Submitter	: Kirill A. Shutemov <kirill@shutemov.name>
Date		: 2008-06-16 07:31 (7 days old)
Handled-By	: H. Peter Anvin <hpa@kernel.org>
Patch		: http://bugzilla.kernel.org/attachment.cgi?id=16549&action=view

[Bug #10923] System turns off during wake from S3, Wake Regression from 2.6.25

[Rafael J. Wysocki]

This message has been generated automatically as a part of a report
of recent regressions.

The following bug entry is on the current list of known regressions
from 2.6.25.  Please verify if it still should be listed.


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=10923
Subject		: System turns off during wake from S3, Wake Regression from 2.6.25
Submitter	: Dionisus Torimens <djtm@gmx.net>
Date		: 2008-06-15 16:24 (8 days old)

[Bug #10951] alpha build failure

[Rafael J. Wysocki]

This message has been generated automatically as a part of a report
of recent regressions.

The following bug entry is on the current list of known regressions
from 2.6.25.  Please verify if it still should be listed.


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=10951
Subject		: alpha build failure
Submitter	: Adrian Bunk <bunk@kernel.org>
Date		: 2008-06-22 02:13 (1 days old)
References	: http://lkml.org/lkml/2008/6/22/18

[Bug #10954] hda_intel: azx_get_response timeout, switching to polling mode: last cmd=0x011f000c

[Rafael J. Wysocki]

This message has been generated automatically as a part of a report
of recent regressions.

The following bug entry is on the current list of known regressions
from 2.6.25.  Please verify if it still should be listed.


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=10954
Subject		: hda_intel: azx_get_response timeout, switching to polling mode: last cmd=0x011f000c
Submitter	: Justin Mattock <justinmattock@gmail.com>
Date		: 2008-06-21 2:05 (2 days old)
References	: http://marc.info/?l=linux-kernel&m=121401399622190&w=4

[Bug #10955] v2.6.26-rc7: BUG task_struct: Poison overwritten

[Rafael J. Wysocki]

This message has been generated automatically as a part of a report
of recent regressions.

The following bug entry is on the current list of known regressions
from 2.6.25.  Please verify if it still should be listed.


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=10955
Subject		: v2.6.26-rc7: BUG task_struct: Poison overwritten
Submitter	: Vegard Nossum <vegard.nossum@gmail.com>
Date		: 2008-06-21 19:24 (2 days old)
References	: http://marc.info/?l=linux-kernel&m=121407641925121&w=4
Handled-By	: Peter Zijlstra <a.p.zijlstra@chello.nl>

[Bug #10956] v2.6.26-rc7: BUG: unable to handle kernel NULL pointer dereference

[Rafael J. Wysocki]

This message has been generated automatically as a part of a report
of recent regressions.

The following bug entry is on the current list of known regressions
from 2.6.25.  Please verify if it still should be listed.


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=10956
Subject		: v2.6.26-rc7: BUG: unable to handle kernel NULL pointer dereference
Submitter	: Vegard Nossum <vegard.nossum@gmail.com>
Date		: 2008-06-22 12:56 (1 days old)
References	: http://marc.info/?l=linux-kernel&m=121413950227884&w=4

[Bug #10957] pata_pcmcia with Sandisk Extreme III 8GB

[Rafael J. Wysocki]

This message has been generated automatically as a part of a report
of recent regressions.

The following bug entry is on the current list of known regressions
from 2.6.25.  Please verify if it still should be listed.


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=10957
Subject		: pata_pcmcia with Sandisk Extreme III 8GB
Submitter	: Komuro <komurojun-mbn@nifty.com>
Date		: 2008-06-07 13:37 (16 days old)
References	: http://marc.info/?l=linux-kernel&m=121284627119861&w=4
Handled-By	: Tejun Heo <htejun@gmail.com>
		  Dominik Brodowski <linux@dominikbrodowski.net>

[Bug #10958] LMSENSORS: 2.6.26-rc, enabling ACPI Termal Zone support costs sensors

[Rafael J. Wysocki]

This message has been generated automatically as a part of a report
of recent regressions.

The following bug entry is on the current list of known regressions
from 2.6.25.  Please verify if it still should be listed.


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=10958
Subject		: LMSENSORS: 2.6.26-rc, enabling ACPI Termal Zone support costs sensors
Submitter	: Rene Herman <rene.herman@keyaccess.nl>
Date		: 2008-06-22 0:47 (1 days old)
References	: http://marc.info/?l=linux-kernel&m=121409569819064&w=4
Handled-By	: Hans de Goede <j.w.r.degoede@hhs.nl>
		  Rene Herman <rene.herman@keyaccess.nl>
Patch		: http://lkml.org/lkml/2008/6/22/83

[Bug #10959] stuck tcp connections 2.6.26-rc7

[Rafael J. Wysocki]

This message has been generated automatically as a part of a report
of recent regressions.

The following bug entry is on the current list of known regressions
from 2.6.25.  Please verify if it still should be listed.


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=10959
Subject		: stuck tcp connections 2.6.26-rc7
Submitter	: Justin Mattock <justinmattock@gmail.com>
Date		: 2008-06-22 18:09 (1 days old)
References	: http://marc.info/?l=linux-kernel&m=121415821219644&w=4

[Bug #10961] 2.6.26-rc: nfsd hangs for a few sec

[Rafael J. Wysocki]

This message has been generated automatically as a part of a report
of recent regressions.

The following bug entry is on the current list of known regressions
from 2.6.25.  Please verify if it still should be listed.


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=10961
Subject		: 2.6.26-rc: nfsd hangs for a few sec
Submitter	: Alexander Beregalov <a.beregalov@gmail.com>
Date		: 2008-06-21 12:57 (2 days old)
References	: http://marc.info/?l=linux-kernel&m=121405308328004&w=4
		  http://marc.info/?l=linux-kernel&m=121412880115289&w=4
Handled-By	: Linus Torvalds <torvalds@linux-foundation.org>
		  Mel Gorman <mel@csn.ul.ie>
		  Christoph Lameter <clameter@sgi.com>

[Bug #10962] 2.6.26-rc2 WARNING from usb-serial, and then my gps is dead

[Rafael J. Wysocki]

This message has been generated automatically as a part of a report
of recent regressions.

The following bug entry is on the current list of known regressions
from 2.6.25.  Please verify if it still should be listed.


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=10962
Subject		: 2.6.26-rc2 WARNING from usb-serial, and then my gps is dead
Submitter	: Helge Hafting <helge.hafting@aitel.hist.no>
Date		: 2008-06-22 18:22 (1 days old)
References	: http://marc.info/?l=linux-kernel&m=121415899320685&w=4

[Bug #10960] 2.6.26-rc: SPARC: Sun Ultra 10 can not boot

[Rafael J. Wysocki]

This message has been generated automatically as a part of a report
of recent regressions.

The following bug entry is on the current list of known regressions
from 2.6.25.  Please verify if it still should be listed.


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=10960
Subject		: 2.6.26-rc: SPARC: Sun Ultra 10 can not boot
Submitter	: Alexander Beregalov <a.beregalov@gmail.com>
Date		: 2008-06-19 14:07 (4 days old)
References	: http://marc.info/?l=linux-kernel&m=121388456519637&w=4
Handled-By	: David Miller <davem@davemloft.net>

[Bug #9791] Clock is running too fast^Wslow using acpi_pm clocksource

[Rafael J. Wysocki]

This message has been generated automatically as a part of a report
of recent regressions.

The following bug entry is on the current list of known regressions
from 2.6.25.  Please verify if it still should be listed.


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=9791
Subject		: Clock is running too fast^Wslow using acpi_pm clocksource
Submitter	: tosn00j02@sneakemail.com
Date		: 2008-05-03 05:09 (51 days old)
Handled-By	: Maciej W. Rozycki <macro@linux-mips.org>
Patch		: http://bugzilla.kernel.org/attachment.cgi?id=16180

Re: 2.6.26-rc7-git2: Reported regressions from 2.6.25

[Rafael J. Wysocki]

On Sunday, 22 of June 2008, Rafael J. Wysocki wrote:
> [Note to bug reporters: If you can, please always add
> kernel-testers@vger.kernel.org to the CC lists of your reports, as that will
> help to filter them out of the other LKML traffic.  Also, if you report a
> regression, please add '[regression]' or something similar to the subject.]

Should be -git1 in the subject, sorry for pushing the time forward. ;-)

Re: [Bug #10951] alpha build failure

[Adrian Bunk]

On Sun, Jun 22, 2008 at 07:54:46PM +0200, Rafael J. Wysocki wrote:
> This message has been generated automatically as a part of a report
> of recent regressions.
> 
> The following bug entry is on the current list of known regressions
> from 2.6.25.  Please verify if it still should be listed.

yes

> Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=10951
> Subject		: alpha build failure
> Submitter	: Adrian Bunk <bunk@kernel.org>
> Date		: 2008-06-22 02:13 (1 days old)
> References	: http://lkml.org/lkml/2008/6/22/18

cu
Adrian

-- 

       "Is there not promise of rain?" Ling Tan asked suddenly out
        of the darkness. There had been need of rain for many days.
       "Only a promise," Lao Er said.
                                       Pearl S. Buck - Dragon Seed

Re: [Bug #10830] two different oopses with 2.6.26-rc4

[Alejandro Riveira Fernández]

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

El dom, 22-06-2008 a las 19:54 +0200, Rafael J. Wysocki escribió:
> This message has been generated automatically as a part of a report
> of recent regressions.
> 
> The following bug entry is on the current list of known regressions
> from 2.6.25.  Please verify if it still should be listed.

No it should not

The oopses disappeared on 2.6.25-rc5 thanks for the time to
all people involved

> 
> 
> Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=10830
> Subject		: two different oopses with 2.6.26-rc4
> Submitter	: Alejandro Riveira Fernández <alejandro.riveira@gmail.com>
> Date		: 2008-05-28 9:50 (26 days old)
> References	: http://marc.info/?l=linux-kernel&m=121196833026310&w=4
> Handled-By	: Johannes Berg <johannes@sipsolutions.net>
> 		  Andrew Morton <akpm@linux-foundation.org>
> 		  Peter Zijlstra <a.p.zijlstra@chello.nl>
> Patch		: http://lkml.org/lkml/2008/5/20/683
> 
> 

[-- Attachment #2: Esta parte del mensaje está firmada digitalmente --]
[-- Type: application/pgp-signature, Size: 197 bytes --]

Re: [Bug #10843] Display artifacts on XOrg logout with PAT kernel and VESA framebuffer

[Frans Pop]

On Sunday 22 June 2008, Rafael J. Wysocki wrote:
> The following bug entry is on the current list of known regressions
> from 2.6.25.  Please verify if it still should be listed.
>
>
> Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=10843
> Subject	: Display artifacts on XOrg logout with PAT kernel and VESA
> 		  framebuffer
> Submitter	: Frans Pop <elendil@planet.nl> 
> Date		: 2008-05-31 14:04 (23 days old)
> References	: http://lkml.org/lkml/2008/6/7/206
> 		  http://lkml.org/lkml/2008/6/15/119

Yes.

Re: [Bug #10493] mips BCM47XX compile error

[Adrian Bunk]

On Sun, Jun 22, 2008 at 07:50:06PM +0200, Rafael J. Wysocki wrote:
> This message has been generated automatically as a part of a report
> of recent regressions.
> 
> The following bug entry is on the current list of known regressions
> from 2.6.25.  Please verify if it still should be listed.

yes

> Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=10493
> Subject		: mips BCM47XX compile error
> Submitter	: Adrian Bunk <adrian.bunk@movial.fi>
> Date		: 2008-04-20 17:07 (64 days old)
> References	: http://lkml.org/lkml/2008/4/20/34
> 		  http://lkml.org/lkml/2008/5/12/30
> 		  http://lkml.org/lkml/2008/5/18/131
> 		  http://lkml.org/lkml/2008/5/31/202
> 		  http://lkml.org/lkml/2008/6/7/154
> Patch		: http://marc.info/?l=linux-kernel&m=120876451216558&w=2


cu
Adrian

Re: [Bug #10830] two different oopses with 2.6.26-rc4

[Rafael J. Wysocki]

On Sunday, 22 of June 2008, Alejandro Riveira Fernández wrote:
> El dom, 22-06-2008 a las 19:54 +0200, Rafael J. Wysocki escribió:
> > This message has been generated automatically as a part of a report
> > of recent regressions.
> > 
> > The following bug entry is on the current list of known regressions
> > from 2.6.25.  Please verify if it still should be listed.
> 
> No it should not
> 
> The oopses disappeared on 2.6.25-rc5 thanks for the time to
> all people involved

Closed.

Thanks,
Rafael

Re: [Bug #10868] Oops on loading ipaq module since 2.6.26, prevents use of device

[Alan Cox]

On Sun, 22 Jun 2008 19:54:46 +0200 (CEST)
"Rafael J. Wysocki" <rjw@sisk.pl> wrote:

> This message has been generated automatically as a part of a report
> of recent regressions.
> 
> The following bug entry is on the current list of known regressions
> from 2.6.25.  Please verify if it still should be listed.
> 
> 
> Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=10868
> Subject		: Oops on loading ipaq module since 2.6.26, prevents use of device
> Submitter	: Adam Williamson <awilliamson@mandriva.com>
> Date		: 2008-06-05 17:39 (18 days old)
> Handled-By	: Alan Cox <alan@redhat.com>

Handed over to Greg as it's not a tty layer bug but something in USB
(actually from the traces I think its a broken gcc/build but we shall)

Re: [Bug #10741] bug in `tty: BKL pushdown'?

[Johannes Weiner]

"Rafael J. Wysocki" <rjw@sisk.pl> writes:

> This message has been generated automatically as a part of a report
> of recent regressions.
>
> The following bug entry is on the current list of known regressions
> from 2.6.25.  Please verify if it still should be listed.

Yup.

> Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=10741
> Subject		: bug in `tty: BKL pushdown'?
> Submitter	: Johannes Weiner <hannes@saeurebad.de>
> Date		: 2008-05-18 2:16 (36 days old)
> References	: http://marc.info/?l=linux-kernel&m=121107706506181&w=4
> 		  http://lkml.org/lkml/2008/6/16/104
> Handled-By	: Alan Cox <alan@lxorguk.ukuu.org.uk>

	Hannes

Re: [Bug #10868] Oops on loading ipaq module since 2.6.26, prevents use of device

[Arjan van de Ven]

On Sun, 22 Jun 2008 21:07:06 +0100
Alan Cox <alan@lxorguk.ukuu.org.uk> wrote:

> On Sun, 22 Jun 2008 19:54:46 +0200 (CEST)
> "Rafael J. Wysocki" <rjw@sisk.pl> wrote:
> 
> > This message has been generated automatically as a part of a report
> > of recent regressions.
> > 
> > The following bug entry is on the current list of known regressions
> > from 2.6.25.  Please verify if it still should be listed.
> > 
> > 
> > Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=10868
> > Subject		: Oops on loading ipaq module since 2.6.26,
> > prevents use of device Submitter	: Adam Williamson
> > <awilliamson@mandriva.com> Date		: 2008-06-05 17:39
> > (18 days old) Handled-By	: Alan Cox <alan@redhat.com>
> 
> Handed over to Greg as it's not a tty layer bug but something in USB
> (actually from the traces I think its a broken gcc/build but we shall)

http://www.kerneloops.org/search.php?search=ipaq_open

has a whole slew of different ones.... surprisingly they're almost all
with pppd...



-- 
If you want to reach me at my work email, use arjan@linux.intel.com
For development, discussion and tips for power savings, 
visit http://www.lesswatts.org

Re: [Bug #10868] Oops on loading ipaq module since 2.6.26, prevents use of device

[Arjan van de Ven]

On Sun, 22 Jun 2008 14:00:44 -0700
Arjan van de Ven <arjan@infradead.org> wrote:

> On Sun, 22 Jun 2008 21:07:06 +0100
> Alan Cox <alan@lxorguk.ukuu.org.uk> wrote:
> 
> > On Sun, 22 Jun 2008 19:54:46 +0200 (CEST)
> > "Rafael J. Wysocki" <rjw@sisk.pl> wrote:
> > 
> > > This message has been generated automatically as a part of a
> > > report of recent regressions.
> > > 
> > > The following bug entry is on the current list of known
> > > regressions from 2.6.25.  Please verify if it still should be
> > > listed.
> > > 
> > > 
> > > Bug-Entry	:
> > > http://bugzilla.kernel.org/show_bug.cgi?id=10868
> > > Subject		: Oops on loading ipaq module since
> > > 2.6.26, prevents use of device Submitter	: Adam Williamson
> > > <awilliamson@mandriva.com> Date		: 2008-06-05 17:39
> > > (18 days old) Handled-By	: Alan Cox <alan@redhat.com>
> > 
> > Handed over to Greg as it's not a tty layer bug but something in USB
> > (actually from the traces I think its a broken gcc/build but we
> > shall)
> 
> http://www.kerneloops.org/search.php?search=ipaq_open
> 
> has a whole slew of different ones.... surprisingly they're almost all
> with pppd...
> 

btw this also shows that this isn't a 2.6.25 regression... 

Re: [Bug #10724] ACPI: EC: GPE storm detected, disabling EC GPE

[Justin Mattock]

On Sun, Jun 22, 2008 at 5:54 PM, Rafael J. Wysocki <rjw@sisk.pl> wrote:
> This message has been generated automatically as a part of a report
> of recent regressions.
>
> The following bug entry is on the current list of known regressions
> from 2.6.25.  Please verify if it still should be listed.
>
>
> Bug-Entry       : http://bugzilla.kernel.org/show_bug.cgi?id=10724
> Subject         : ACPI: EC: GPE storm detected, disabling EC GPE
> Submitter       : Justin Mattock <justinmattock@gmail.com>
> Date            : 2008-05-16 6:17 (38 days old)
> References      : http://marc.info/?l=linux-kernel&m=121091875711824&w=4
>                  http://lkml.org/lkml/2008/5/18/168
>                  http://lkml.org/lkml/2008/5/25/195
> Patch           : http://bugzilla.kernel.org/attachment.cgi?id=16364&action=view
>                  http://bugzilla.kernel.org/attachment.cgi?id=16365&action=view
>
>
>

Yes; setting  if (atomic_read(&ec->irq_count) > 5) { to
	if (atomic_read(&ec->irq_count) > 20) {
in drivers/acpi/ac.c only prolongs the bug, after a period of time(3
to 5 hrs) the the message does appear.
regards;

-- 
Justin P. Mattock

Re: [Bug #10954] hda_intel: azx_get_response timeout, switching to polling mode: last cmd=0x011f000c

[Justin Mattock]

On Sun, Jun 22, 2008 at 5:54 PM, Rafael J. Wysocki <rjw@sisk.pl> wrote:
> This message has been generated automatically as a part of a report
> of recent regressions.
>
> The following bug entry is on the current list of known regressions
> from 2.6.25.  Please verify if it still should be listed.
>
>
> Bug-Entry       : http://bugzilla.kernel.org/show_bug.cgi?id=10954
> Subject         : hda_intel: azx_get_response timeout, switching to polling mode: last cmd=0x011f000c
> Submitter       : Justin Mattock <justinmattock@gmail.com>
> Date            : 2008-06-21 2:05 (2 days old)
> References      : http://marc.info/?l=linux-kernel&m=121401399622190&w=4
>
>
>

I'm up in the air with this one, i.g. one minute this message is
appearing, and then the next it's not.
If nobody else is catching this or seeing this happen, then I'll take
it as a .config problem on my part.
regards;

-- 
Justin P. Mattock

Re: [Bug #10868] Oops on loading ipaq module since 2.6.26, prevents use of device

[Adrian Bunk]

On Sun, Jun 22, 2008 at 02:02:26PM -0700, Arjan van de Ven wrote:
> On Sun, 22 Jun 2008 14:00:44 -0700
> Arjan van de Ven <arjan@infradead.org> wrote:
> 
> > On Sun, 22 Jun 2008 21:07:06 +0100
> > Alan Cox <alan@lxorguk.ukuu.org.uk> wrote:
> > 
> > > On Sun, 22 Jun 2008 19:54:46 +0200 (CEST)
> > > "Rafael J. Wysocki" <rjw@sisk.pl> wrote:
> > > 
> > > > This message has been generated automatically as a part of a
> > > > report of recent regressions.
> > > > 
> > > > The following bug entry is on the current list of known
> > > > regressions from 2.6.25.  Please verify if it still should be
> > > > listed.
> > > > 
> > > > 
> > > > Bug-Entry	:
> > > > http://bugzilla.kernel.org/show_bug.cgi?id=10868
> > > > Subject		: Oops on loading ipaq module since
> > > > 2.6.26, prevents use of device Submitter	: Adam Williamson
> > > > <awilliamson@mandriva.com> Date		: 2008-06-05 17:39
> > > > (18 days old) Handled-By	: Alan Cox <alan@redhat.com>
> > > 
> > > Handed over to Greg as it's not a tty layer bug but something in USB
> > > (actually from the traces I think its a broken gcc/build but we
> > > shall)
> > 
> > http://www.kerneloops.org/search.php?search=ipaq_open
> > 
> > has a whole slew of different ones.... surprisingly they're almost all
> > with pppd...
> 
> btw this also shows that this isn't a 2.6.25 regression... 

That hardly shows it.

And Adam said quite explicitely that 2.6.25 worked for him.

cu
Adrian

-- 

       "Is there not promise of rain?" Ling Tan asked suddenly out
        of the darkness. There had been need of rain for many days.
       "Only a promise," Lao Er said.
                                       Pearl S. Buck - Dragon Seed

Re: [Bug #10959] stuck tcp connections 2.6.26-rc7

[Justin Mattock]

On Sun, Jun 22, 2008 at 5:54 PM, Rafael J. Wysocki <rjw@sisk.pl> wrote:
> This message has been generated automatically as a part of a report
> of recent regressions.
>
> The following bug entry is on the current list of known regressions
> from 2.6.25.  Please verify if it still should be listed.
>
>
> Bug-Entry       : http://bugzilla.kernel.org/show_bug.cgi?id=10959
> Subject         : stuck tcp connections 2.6.26-rc7
> Submitter       : Justin Mattock <justinmattock@gmail.com>
> Date            : 2008-06-22 18:09 (1 days old)
> References      : http://marc.info/?l=linux-kernel&m=121415821219644&w=4
>
>
>

Yes;
As a short work around setting #define TCP_RTO_MAX	((unsigned)(120*HZ)) to
#define TCP_RTO_MAX	((unsigned)(60*HZ)) in include/net/tcp.h does
help, but the problem is still there.
After testing this setting out for a few days, I decided to revert it
back, so I don't mess my tcp packets up, and feel like an internet hog
regards;


-- 
Justin P. Mattock

Re: [Bug #10868] Oops on loading ipaq module since 2.6.26, prevents use of device

[Alan Cox]

> > btw this also shows that this isn't a 2.6.25 regression... 
> 
> That hardly shows it.
> 
> And Adam said quite explicitely that 2.6.25 worked for him.

Nothing much I can do to help. The URB is assigned in setup and is NULL
later. Nothing else I can find touches it.

Alan

Re: [Bug #10868] Oops on loading ipaq module since 2.6.26, prevents use of device

[Alan Cox]

> > http://www.kerneloops.org/search.php?search=ipaq_open
> > 
> > has a whole slew of different ones.... surprisingly they're almost all
> > with pppd...
> > 
> 
> btw this also shows that this isn't a 2.6.25 regression... 

No suprise about the pppd - that would be the usual usage of this driver.

Alan

Re: [Bug #10868] Oops on loading ipaq module since 2.6.26, prevents use of device

[Oliver Neukum]

Am Montag 23 Juni 2008 00:37:20 schrieb Alan Cox:
> > > btw this also shows that this isn't a 2.6.25 regression... 
> > 
> > That hardly shows it.
> > 
> > And Adam said quite explicitely that 2.6.25 worked for him.
> 
> Nothing much I can do to help. The URB is assigned in setup and is NULL
> later. Nothing else I can find touches it.

We need this oops replicated with debug enabled in the usb serial core.

	Regards
		Oliver

Re: [Bug #10892] Sometime (often) X come out blank (black screen)on cold boot - Intel chipset

[Romano Giannetti]

On Sun, 2008-06-22 at 19:54 +0200, Rafael J. Wysocki wrote:

> Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=10892
> Subject		: Sometime (often) X come out blank (black screen) on cold boot - Intel chipset
> Submitter	: Romano Giannetti <romano.giannetti@gmail.com>
> Date		: 2008-06-10 05:33 (13 days old)
> References	: http://lkml.org/lkml/2008/6/10/137

I tried to reproduce it this morning with 2.6.26-rc7, but failed. So, it
seems gone (but this was an Eisenbug, so I am not certain). 

Romano 

-- 
Romano Giannetti <romano.giannetti@gmail.com>

Re: [Bug #10892] Sometime (often) X come out blank (black screen)on cold boot - Intel chipset

[Ingo Molnar]

* Romano Giannetti <romano.giannetti@gmail.com> wrote:

> On Sun, 2008-06-22 at 19:54 +0200, Rafael J. Wysocki wrote:
> 
> > Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=10892
> > Subject		: Sometime (often) X come out blank (black screen) on cold boot - Intel chipset
> > Submitter	: Romano Giannetti <romano.giannetti@gmail.com>
> > Date		: 2008-06-10 05:33 (13 days old)
> > References	: http://lkml.org/lkml/2008/6/10/137
> 
> I tried to reproduce it this morning with 2.6.26-rc7, but failed. So, 
> it seems gone (but this was an Eisenbug, so I am not certain).

there were a number of drivers/char/drm/ and drivers/char/agp/ fixes 
merged into -rc7 which could have resolved this. Please keep an eye on 
it nevertheless.

	Ingo

Re: [Bug 10843] Display artifacts on XOrg logout with PAT kernel and VESA framebuffer

[Frans Pop]

On Sunday 15 June 2008, Siddha, Suresh B wrote:
> Frans Pop wrote:
> > On Saturday 14 June 2008, Rafael J. Wysocki wrote:
> > > Bug-Entry     : http://bugzilla.kernel.org/show_bug.cgi?id=10843
> > > Subject       : Display artifacts on XOrg logout with PAT kernel
> > > and VESA framebuffer
> > > Submitter     : Frans Pop <elendil@planet.nl>
> > > Date          : 2008-05-31 14:04 (15 days old)
> > > References    : http://lkml.org/lkml/2008/6/7/206
> >
> > Yes. See also: http://lkml.org/lkml/2008/6/13/159
>
> Frans, With or without pat, in the recent kernels (like 2.6.26-rc4/rc5
> etc), ioremap() uses  UC- and PCI mmap of /sys/devices/pci.../resource
> (used by X) uses UC-
>
> And fb_mmap() also uses UC-.
>
> It's interesting that you don't see this artifact with "nopat".
> Essentially with or with out pat enabled, we use the same memory
> attributes. So depending on the MTRR setup (set by X server), effective
> memory attribute across different mappings should be same (which is UC-
> or WC with mtrr).

Any progress on this issue? It's still there with -rc7, but I doubt that 
comes as a surprise.

Has anyone tried to reproduce this? I would think that should be trivial.

Just as a summary:
- Intel 82945G/GZ graphics [8086:2772] (ICH7 based system)
- FB_VESA=y, FRAMEBUFFER_CONSOLE=y
- boot with vga=791
- Log in to X and KDE; I do need to really log in there are no artifacts
  if I exit X from the kdm login dialog
- artifacts show on logout

I doubt it's KDE related or even related to my specific graphics card.

It may well be related to what is or has been displayed on the display 
before logging out, so running some apps may make sense. Seems like I do 
see remnants of for example aptitude (Debian apt frontend) after I've run 
it in an X term (KDE's konsole).

Cheers,
FJP

Re: [Bug #10868] Oops on loading ipaq module since 2.6.26, prevents use of device

[Adam Williamson]

On Mon, 2008-06-23 at 09:48 +0200, Oliver Neukum wrote:
> Am Montag 23 Juni 2008 00:37:20 schrieb Alan Cox:
> > > > btw this also shows that this isn't a 2.6.25 regression... 
> > > 
> > > That hardly shows it.
> > > 
> > > And Adam said quite explicitely that 2.6.25 worked for him.
> > 
> > Nothing much I can do to help. The URB is assigned in setup and is NULL
> > later. Nothing else I can find touches it.
> 
> We need this oops replicated with debug enabled in the usb serial core.

Is that just a kernel build option? (As I mentioned earlier, I'm not
much of a kernel hacker, I usually just run packaged kernels).
-- 
adamw

Re: [Bug #10868] Oops on loading ipaq module since 2.6.26, prevents use of device

[Oliver Neukum]

Am Montag 23 Juni 2008 17:46:43 schrieb Adam Williamson:
> On Mon, 2008-06-23 at 09:48 +0200, Oliver Neukum wrote:
> > Am Montag 23 Juni 2008 00:37:20 schrieb Alan Cox:
> > > > > btw this also shows that this isn't a 2.6.25 regression... 
> > > > 
> > > > That hardly shows it.
> > > > 
> > > > And Adam said quite explicitely that 2.6.25 worked for him.
> > > 
> > > Nothing much I can do to help. The URB is assigned in setup and is NULL
> > > later. Nothing else I can find touches it.
> > 
> > We need this oops replicated with debug enabled in the usb serial core.
> 
> Is that just a kernel build option? (As I mentioned earlier, I'm not
> much of a kernel hacker, I usually just run packaged kernels).

It is the module option "debug" for usb-serial.

	Regards
		Oliver

Re: [Bug #10868] Oops on loading ipaq module since 2.6.26, prevents use of device

[Adam Williamson]

On Mon, 2008-06-23 at 20:41 +0200, Oliver Neukum wrote:
> Am Montag 23 Juni 2008 17:46:43 schrieb Adam Williamson:
> > On Mon, 2008-06-23 at 09:48 +0200, Oliver Neukum wrote:
> > > Am Montag 23 Juni 2008 00:37:20 schrieb Alan Cox:
> > > > > > btw this also shows that this isn't a 2.6.25 regression... 
> > > > > 
> > > > > That hardly shows it.
> > > > > 
> > > > > And Adam said quite explicitely that 2.6.25 worked for him.
> > > > 
> > > > Nothing much I can do to help. The URB is assigned in setup and is NULL
> > > > later. Nothing else I can find touches it.
> > > 
> > > We need this oops replicated with debug enabled in the usb serial core.
> > 
> > Is that just a kernel build option? (As I mentioned earlier, I'm not
> > much of a kernel hacker, I usually just run packaged kernels).
> 
> It is the module option "debug" for usb-serial.

Oh, that's easy then. :) Will do that later. Thanks.
-- 
adamw

Re: [Bug 10843] Display artifacts on XOrg logout with PAT kernel and VESA framebuffer

[Suresh Siddha]

On Mon, Jun 23, 2008 at 05:38:59AM -0700, Frans Pop wrote:
> On Sunday 15 June 2008, Siddha, Suresh B wrote:
> > Frans Pop wrote:
> > > On Saturday 14 June 2008, Rafael J. Wysocki wrote:
> > > > Bug-Entry     : http://bugzilla.kernel.org/show_bug.cgi?id=10843
> > > > Subject       : Display artifacts on XOrg logout with PAT kernel
> > > > and VESA framebuffer
> > > > Submitter     : Frans Pop <elendil@planet.nl>
> > > > Date          : 2008-05-31 14:04 (15 days old)
> > > > References    : http://lkml.org/lkml/2008/6/7/206
> > >
> > > Yes. See also: http://lkml.org/lkml/2008/6/13/159
> >
> > Frans, With or without pat, in the recent kernels (like 2.6.26-rc4/rc5
> > etc), ioremap() uses  UC- and PCI mmap of /sys/devices/pci.../resource
> > (used by X) uses UC-
> >
> > And fb_mmap() also uses UC-.
> >
> > It's interesting that you don't see this artifact with "nopat".
> > Essentially with or with out pat enabled, we use the same memory
> > attributes. So depending on the MTRR setup (set by X server), effective
> > memory attribute across different mappings should be same (which is UC-
> > or WC with mtrr).
> 
> Any progress on this issue? It's still there with -rc7, but I doubt that
> comes as a surprise.
> 
> Has anyone tried to reproduce this? I would think that should be trivial.
> 
> Just as a summary:
> - Intel 82945G/GZ graphics [8086:2772] (ICH7 based system)
> - FB_VESA=y, FRAMEBUFFER_CONSOLE=y
> - boot with vga=791
> - Log in to X and KDE; I do need to really log in there are no artifacts
>   if I exit X from the kdm login dialog
> - artifacts show on logout
> 
> I doubt it's KDE related or even related to my specific graphics card.
> 
> It may well be related to what is or has been displayed on the display
> before logging out, so running some apps may make sense. Seems like I do
> see remnants of for example aptitude (Debian apt frontend) after I've run
> it in an X term (KDE's konsole).

FJP, We will try to reproduce this and getback. Your earlier responses did not
give many clues.

thanks,
suresh

Re: [Bug #10868] Oops on loading ipaq module since 2.6.26, prevents use of device

[Adam Williamson]

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

On Mon, 2008-06-23 at 20:41 +0200, Oliver Neukum wrote:

> It is the module option "debug" for usb-serial.

OK, here you go:
-- 
adamw

[-- Attachment #2: 26_untainted_debug.txt --]
[-- Type: text/plain, Size: 8992 bytes --]

usb 3-3: new full speed USB device using ohci_hcd and address 2
usb 3-3: configuration #1 chosen from 1 choice
usb 3-3: New USB device found, idVendor=03f0, idProduct=1016
usb 3-3: New USB device strings: Mfr=0, Product=0, SerialNumber=0
usbcore: registered new interface driver usbserial
drivers/usb/serial/usb-serial.c: Had to override the open usb serial operation with the generic one.
drivers/usb/serial/usb-serial.c: Had to override the write usb serial operation with the generic one.
drivers/usb/serial/usb-serial.c: Had to override the close usb serial operation with the generic one.
drivers/usb/serial/usb-serial.c: Had to override the write_room usb serial operation with the generic one.
drivers/usb/serial/usb-serial.c: Had to override the chars_in_buffer usb serial operation with the generic one.
drivers/usb/serial/usb-serial.c: Had to override the read_bulk_callback usb serial operation with the generic one.
drivers/usb/serial/usb-serial.c: Had to override the write_bulk_callback usb serial operation with the generic one.
usbserial: USB Serial support registered for generic
usbcore: registered new interface driver usbserial_generic
usbserial: USB Serial Driver core
drivers/usb/serial/usb-serial.c: Had to override the resume usb serial operation with the generic one.
usbserial: USB Serial support registered for PocketPC PDA
ipaq: USB PocketPC PDA driver v0.5
drivers/usb/serial/usb-serial.c: static descriptor matches
drivers/usb/serial/usb-serial.c: found bulk in on endpoint 0
drivers/usb/serial/usb-serial.c: found bulk out on endpoint 1
ipaq 3-3:1.0: PocketPC PDA converter detected
drivers/usb/serial/usb-serial.c: usb_serial_probe - setting up 2 port structures for this device
drivers/usb/serial/usb-serial.c: get_free_serial 2
drivers/usb/serial/usb-serial.c: get_free_serial - minor base = 0
drivers/usb/serial/usb-serial.c: usb_serial_probe - registering ttyUSB0
usb 3-3: PocketPC PDA converter now attached to ttyUSB0
drivers/usb/serial/usb-serial.c: usb_serial_probe - registering ttyUSB1
usb 3-3: PocketPC PDA converter now attached to ttyUSB1
usbcore: registered new interface driver ipaq
PPP generic driver version 2.4.2
drivers/usb/serial/usb-serial.c: serial_open
drivers/usb/serial/usb-serial.c: serial_open
BUG: unable to handle kernel NULL pointer dereference at 0000003c
IP: [<e0d878bd>] :ipaq:ipaq_open+0x1c4/0x2fb
*pde = 00000000
Oops: 0002 [#1]
Modules linked in: ppp_generic slhc ipaq usbserial fuse af_packet snd_seq_dummy snd_seq_oss snd_seq_midi_event snd_seq snd_pcm_oss snd_mixer_oss ipv6 binfmt_misc loop dm_mirror dm_log dm_mod floppy cpufreq_ondemand freq_table cpufreq_conservative cpufreq_powersave cpufreq_nforce2 evdev snd_mpu401 snd_cs4232 snd_opl3_lib snd_hwdep snd_cs4231_lib ns558 gameport snd_mpu401_uart parport_pc snd_rawmidi snd_seq_device parport rtc_cmos rtc_core rtc_lib sg snd_pcsp skge osst st thermal processor button usbkbd usbmouse usbhid ff_memless snd_intel8x0 snd_ac97_codec ac97_bus shpchp pci_hotplug snd_pcm snd_timer snd forcedeth i2c_nforce2 i2c_core soundcore nvidia_agp snd_page_alloc agpgart hid ide_generic amd74xx ide_core sbp2 ohci1394 ieee1394 usb_storage sata_sil pata_amd libata dock sd_mod scsi_mod ext3 jbd uhci_hcd ohci_hcd ehci_hcd usbcore [last unloaded: nf_conntrack]

Pid: 4393, comm: pppd Not tainted (2.6.26-0.rc4.1mdv #1)
EIP: 0060:[<e0d878bd>] EFLAGS: 00010246 CPU: 0
EIP is at ipaq_open+0x1c4/0x2fb [ipaq]
EAX: 00000000 EBX: db368ca0 ECX: 00000000 EDX: db3a4000
ESI: 00000000 EDI: db235800 EBP: db3bbe3c ESP: db3bbe1c
 DS: 007b ES: 007b FS: 0000 GS: 0033 SS: 0068
Process pppd (pid: 4393, ti=db3ba000 task=db140700 task.ti=db3ba000)
Stack: db368cb4 db0aa220 00000100 00000064 db235800 00000000 db235800 db0aa220
       db3bbe5c e0da0cd6 db2fb6c0 df9b0000 db235824 ffffffed e0da0bf7 db2fb6c0
       db3bbe84 c022549d 00000802 00000000 0bc00001 00000001 df9b0000 00000000
Call Trace:
 [<e0da0cd6>] ? serial_open+0xdf/0x13d [usbserial]
 [<e0da0bf7>] ? serial_open+0x0/0x13d [usbserial]
 [<c022549d>] ? tty_open+0x184/0x272
 [<c0173364>] ? chrdev_open+0x130/0x147
 [<c016f967>] ? __dentry_open+0x103/0x1f0
 [<c016fadb>] ? nameidata_to_filp+0x1f/0x33
 [<c0173234>] ? chrdev_open+0x0/0x147
 [<c017a8ba>] ? do_filp_open+0x338/0x6b1
 [<c016f733>] ? get_unused_fd_flags+0xc1/0xcb
 [<c016f77d>] ? do_sys_open+0x40/0xbc
 [<c016f83b>] ? sys_open+0x1e/0x26
 [<c010392f>] ? sysenter_past_esp+0x78/0xd9
 =======================
Code: 00 00 00 85 c0 89 87 94 00 00 00 75 16 89 d0 e8 d4 60 3e df c7 87 84 00 00 00 00 00 00 00 e9 11 01 00 00 8b 87 8c 00 00 00 31 f6 <89> 50 3c 8b 87 94 00 00 00 8b 97 9c 00 00 00 89 42 3c 8b 87 8c
EIP: [<e0d878bd>] ipaq_open+0x1c4/0x2fb [ipaq] SS:ESP 0068:db3bbe1c
---[ end trace bb86bb5b50c9ee22 ]---
drivers/usb/serial/usb-serial.c: serial_tiocmset - port 0
drivers/usb/serial/usb-serial.c: serial_ioctl - port 0, cmd 0x5401
drivers/usb/serial/usb-serial.c: serial_ioctl - port 0, cmd 0x5404
drivers/usb/serial/usb-serial.c: serial_chars_in_buffer = port 0
drivers/usb/serial/usb-serial.c: serial_set_termios - port 0
drivers/usb/serial/usb-serial.c: serial_open
drivers/usb/serial/usb-serial.c: serial_close - port 0
drivers/usb/serial/usb-serial.c: serial_write - port 0, 12 byte(s)
drivers/usb/serial/usb-serial.c: serial_tiocmset - port 0
drivers/usb/serial/usb-serial.c: serial_ioctl - port 0, cmd 0x5401
drivers/usb/serial/usb-serial.c: serial_ioctl - port 0, cmd 0x5404
drivers/usb/serial/usb-serial.c: serial_chars_in_buffer = port 0
drivers/usb/serial/usb-serial.c: serial_set_termios - port 0
drivers/usb/serial/usb-serial.c: serial_chars_in_buffer = port 0
drivers/usb/serial/usb-serial.c: usb_serial_port_work - port 0
drivers/usb/serial/usb-serial.c: serial_chars_in_buffer = port 0
drivers/usb/serial/usb-serial.c: serial_ioctl - port 0, cmd 0x80047437
drivers/usb/serial/usb-serial.c: serial_write - port 0, 45 byte(s)
drivers/usb/serial/usb-serial.c: serial_write - port 0, 37 byte(s)
drivers/usb/serial/usb-serial.c: usb_serial_port_work - port 0
drivers/usb/serial/usb-serial.c: usb_serial_port_work - port 0
padlock: VIA PadLock Hash Engine not detected.
PPP MPPE Compression module registered
PPP BSD Compression module registered
PPP Deflate Compression module registered
drivers/usb/serial/usb-serial.c: serial_write - port 0, 26 byte(s)
drivers/usb/serial/usb-serial.c: serial_write - port 0, 33 byte(s)
drivers/usb/serial/usb-serial.c: serial_write - port 0, 15 byte(s)
drivers/usb/serial/usb-serial.c: serial_write - port 0, 21 byte(s)
drivers/usb/serial/usb-serial.c: serial_write - port 0, 25 byte(s)
drivers/usb/serial/usb-serial.c: usb_serial_port_work - port 0
drivers/usb/serial/usb-serial.c: usb_serial_port_work - port 0
drivers/usb/serial/usb-serial.c: serial_write - port 0, 15 byte(s)
drivers/usb/serial/usb-serial.c: usb_serial_port_work - port 0
drivers/usb/serial/usb-serial.c: serial_write - port 0, 21 byte(s)
drivers/usb/serial/usb-serial.c: serial_write - port 0, 9 byte(s)
drivers/usb/serial/usb-serial.c: usb_serial_port_work - port 0
drivers/usb/serial/usb-serial.c: serial_write - port 0, 27 byte(s)
drivers/usb/serial/usb-serial.c: usb_serial_port_work - port 0
mppe_decomp_init[0]: unknown key length
drivers/usb/serial/usb-serial.c: usb_serial_port_work - port 0
drivers/usb/serial/usb-serial.c: usb_serial_port_work - port 0
drivers/usb/serial/usb-serial.c: serial_write - port 0, 33 byte(s)
drivers/usb/serial/usb-serial.c: usb_serial_port_work - port 0
drivers/usb/serial/usb-serial.c: serial_write - port 0, 53 byte(s)
drivers/usb/serial/usb-serial.c: usb_serial_port_work - port 0
drivers/usb/serial/usb-serial.c: serial_write - port 0, 44 byte(s)
drivers/usb/serial/usb-serial.c: usb_serial_port_work - port 0
drivers/usb/serial/usb-serial.c: serial_write - port 0, 44 byte(s)
drivers/usb/serial/usb-serial.c: usb_serial_port_work - port 0
drivers/usb/serial/usb-serial.c: serial_write - port 0, 44 byte(s)
drivers/usb/serial/usb-serial.c: usb_serial_port_work - port 0
drivers/usb/serial/usb-serial.c: serial_write - port 0, 44 byte(s)
drivers/usb/serial/usb-serial.c: usb_serial_port_work - port 0
drivers/usb/serial/usb-serial.c: serial_write - port 0, 44 byte(s)
drivers/usb/serial/usb-serial.c: usb_serial_port_work - port 0
drivers/usb/serial/usb-serial.c: serial_write - port 0, 44 byte(s)
drivers/usb/serial/usb-serial.c: usb_serial_port_work - port 0
drivers/usb/serial/usb-serial.c: serial_write - port 0, 84 byte(s)
drivers/usb/serial/usb-serial.c: usb_serial_port_work - port 0
drivers/usb/serial/usb-serial.c: serial_write - port 0, 44 byte(s)
drivers/usb/serial/usb-serial.c: usb_serial_port_work - port 0
drivers/usb/serial/usb-serial.c: serial_write - port 0, 85 byte(s)
drivers/usb/serial/usb-serial.c: usb_serial_port_work - port 0
drivers/usb/serial/usb-serial.c: serial_write - port 0, 48 byte(s)
drivers/usb/serial/usb-serial.c: usb_serial_port_work - port 0
drivers/usb/serial/usb-serial.c: serial_write - port 0, 44 byte(s)
drivers/usb/serial/usb-serial.c: usb_serial_port_work - port 0

Re: [Bug #10962] 2.6.26-rc2 WARNING from usb-serial, and then my gps is dead

[Helge Hafting]

Rafael J. Wysocki wrote:
> This message has been generated automatically as a part of a report
> of recent regressions.
> 
> The following bug entry is on the current list of known regressions
> from 2.6.25.  Please verify if it still should be listed.
> 
> 
> Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=10962
> Subject		: 2.6.26-rc2 WARNING from usb-serial, and then my gps is dead
> Submitter	: Helge Hafting <helge.hafting@aitel.hist.no>
> Date		: 2008-06-22 18:22 (1 days old)
> References	: http://marc.info/?l=linux-kernel&m=121415899320685&w=4
> 
> 

I can confirm that this problem still happens in 2.6.26-rc8.
When the gps loose connection (probably due to faulty USB cabling), then
the kernel spits out numerous WARNINGs.

I'll try to reproduce with USB debugging later.

Helge Hafting

Re: [Bug #10868] Oops on loading ipaq module since 2.6.26, prevents use of device

[Oliver Neukum]

Am Mittwoch 25 Juni 2008 04:05:13 schrieb Adam Williamson:
> On Mon, 2008-06-23 at 20:41 +0200, Oliver Neukum wrote:
> 
> > It is the module option "debug" for usb-serial.
> 
> OK, here you go:

Please also set the debug module parameter for the ipaq module.

	Regards
		Oliver

Re: [Bug #10872] x86_64 boot hang when CONFIG_NUMA=n

[Randy Dunlap]

On Sun, 22 Jun 2008 19:54:46 +0200 (CEST) Rafael J. Wysocki wrote:

> This message has been generated automatically as a part of a report
> of recent regressions.
> 
> The following bug entry is on the current list of known regressions
> from 2.6.25.  Please verify if it still should be listed.

Yes.

> Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=10872
> Subject		: x86_64 boot hang when CONFIG_NUMA=n
> Submitter	: Randy Dunlap <randy.dunlap@oracle.com>
> Date		: 2008-06-05 21:50 (18 days old)
> References	: http://marc.info/?l=linux-kernel&m=121270308607116&w=4
> 		  http://lkml.org/lkml/2008/6/11/355
> 		  http://lkml.org/lkml/2008/6/15/117
> Handled-By	: Yinghai Lu <yhlu.kernel@gmail.com>


---
~Randy
Linux Plumbers Conference, 17-19 September 2008, Portland, Oregon USA
http://linuxplumbersconf.org/

Re: [Bug #10868] Oops on loading ipaq module since 2.6.26, prevents use of device

[Adam Williamson]

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

On Wed, 2008-06-25 at 17:41 +0200, Oliver Neukum wrote:
> Am Mittwoch 25 Juni 2008 04:05:13 schrieb Adam Williamson:
> > On Mon, 2008-06-23 at 20:41 +0200, Oliver Neukum wrote:
> > 
> > > It is the module option "debug" for usb-serial.
> > 
> > OK, here you go:
> 
> Please also set the debug module parameter for the ipaq module.

OK.
-- 
adamw

[-- Attachment #2: 26_untainted_debug_debug.txt --]
[-- Type: text/plain, Size: 22730 bytes --]

usb 2-3: new full speed USB device using ohci_hcd and address 2
usb 2-3: configuration #1 chosen from 1 choice
usb 2-3: New USB device found, idVendor=03f0, idProduct=1016
usb 2-3: New USB device strings: Mfr=0, Product=0, SerialNumber=0
usbcore: registered new interface driver usbserial
drivers/usb/serial/usb-serial.c: Had to override the open usb serial operation with the generic one.
drivers/usb/serial/usb-serial.c: Had to override the write usb serial operation with the generic one.
drivers/usb/serial/usb-serial.c: Had to override the close usb serial operation with the generic one.
drivers/usb/serial/usb-serial.c: Had to override the write_room usb serial operation with the generic one.
drivers/usb/serial/usb-serial.c: Had to override the chars_in_buffer usb serial operation with the generic one.
drivers/usb/serial/usb-serial.c: Had to override the read_bulk_callback usb serial operation with the generic one.
drivers/usb/serial/usb-serial.c: Had to override the write_bulk_callback usb serial operation with the generic one.
usbserial: USB Serial support registered for generic
usbcore: registered new interface driver usbserial_generic
usbserial: USB Serial Driver core
drivers/usb/serial/usb-serial.c: Had to override the resume usb serial operation with the generic one.
usbserial: USB Serial support registered for PocketPC PDA
ipaq: USB PocketPC PDA driver v0.5
drivers/usb/serial/usb-serial.c: static descriptor matches
drivers/usb/serial/usb-serial.c: found bulk in on endpoint 0
drivers/usb/serial/usb-serial.c: found bulk out on endpoint 1
ipaq 2-3:1.0: PocketPC PDA converter detected
drivers/usb/serial/usb-serial.c: usb_serial_probe - setting up 2 port structures for this device
drivers/usb/serial/ipaq.c: ipaq_startup
drivers/usb/serial/usb-serial.c: get_free_serial 2
drivers/usb/serial/usb-serial.c: get_free_serial - minor base = 0
drivers/usb/serial/usb-serial.c: usb_serial_probe - registering ttyUSB0
usb 2-3: PocketPC PDA converter now attached to ttyUSB0
drivers/usb/serial/usb-serial.c: usb_serial_probe - registering ttyUSB1
usb 2-3: PocketPC PDA converter now attached to ttyUSB1
usbcore: registered new interface driver ipaq
PPP generic driver version 2.4.2
drivers/usb/serial/usb-serial.c: serial_open
drivers/usb/serial/ipaq.c: ipaq_open - port 0
drivers/usb/serial/usb-serial.c: serial_open
drivers/usb/serial/ipaq.c: ipaq_open - port 1
BUG: unable to handle kernel NULL pointer dereference at 0000003c
IP: [<e0d848bd>] :ipaq:ipaq_open+0x1c4/0x2fb
*pde = 00000000
Oops: 0002 [#1]
Modules linked in: ppp_generic slhc ipaq usbserial fuse af_packet snd_seq_dummy snd_seq_oss snd_seq_midi_event snd_seq snd_pcm_oss ipv6 snd_mixer_oss binfmt_misc loop dm_mirror dm_log dm_mod floppy cpufreq_ondemand freq_table cpufreq_conservative cpufreq_powersave cpufreq_nforce2 evdev sg ns558 snd_mpu401 gameport snd_cs4232 snd_opl3_lib snd_hwdep snd_cs4231_lib snd_mpu401_uart snd_rawmidi snd_seq_device skge parport_pc parport rtc_cmos rtc_core rtc_lib snd_pcsp thermal usbkbd usbmouse button processor usbhid ff_memless osst snd_intel8x0 snd_ac97_codec ac97_bus i2c_nforce2 shpchp st i2c_core pci_hotplug snd_pcm forcedeth snd_timer nvidia_agp snd soundcore snd_page_alloc agpgart hid ide_generic amd74xx ide_core sbp2 ohci1394 ieee1394 usb_storage sata_sil pata_amd libata dock sd_mod scsi_mod ext3 jbd uhci_hcd ohci_hcd ehci_hcd usbcore [last unloaded: nf_conntrack]

Pid: 4396, comm: pppd Not tainted (2.6.26-0.rc4.1mdv #1)
EIP: 0060:[<e0d848bd>] EFLAGS: 00010246 CPU: 0
EIP is at ipaq_open+0x1c4/0x2fb [ipaq]
EAX: 00000000 EBX: db37ecc0 ECX: 00000000 EDX: db3ae000
ESI: 00000000 EDI: db305c00 EBP: db3a5e3c ESP: db3a5e1c
 DS: 007b ES: 007b FS: 0000 GS: 0033 SS: 0068
Process pppd (pid: 4396, ti=db3a4000 task=db368560 task.ti=db3a4000)
Stack: db37ecd4 de25d7a0 00000100 00000064 db305c00 00000000 db305c00 de25d7a0
       db3a5e5c e0d9dcd6 db222b00 db35c800 db305c24 ffffffed e0d9dbf7 db222b00
       db3a5e84 c022549d 00000802 00000000 0bc00001 00000001 db35c800 00000000
Call Trace:
 [<e0d9dcd6>] ? serial_open+0xdf/0x13d [usbserial]
 [<e0d9dbf7>] ? serial_open+0x0/0x13d [usbserial]
 [<c022549d>] ? tty_open+0x184/0x272
 [<c0173364>] ? chrdev_open+0x130/0x147
 [<c016f967>] ? __dentry_open+0x103/0x1f0
 [<c016fadb>] ? nameidata_to_filp+0x1f/0x33
 [<c0173234>] ? chrdev_open+0x0/0x147
 [<c017a8ba>] ? do_filp_open+0x338/0x6b1
 [<c016f733>] ? get_unused_fd_flags+0xc1/0xcb
 [<c016f77d>] ? do_sys_open+0x40/0xbc
 [<c016f83b>] ? sys_open+0x1e/0x26
 [<c010392f>] ? sysenter_past_esp+0x78/0xd9
 =======================
Code: 00 00 00 85 c0 89 87 94 00 00 00 75 16 89 d0 e8 d4 90 3e df c7 87 84 00 00 00 00 00 00 00 e9 11 01 00 00 8b 87 8c 00 00 00 31 f6 <89> 50 3c 8b 87 94 00 00 00 8b 97 9c 00 00 00 89 42 3c 8b 87 8c
EIP: [<e0d848bd>] ipaq_open+0x1c4/0x2fb [ipaq] SS:ESP 0068:db3a5e1c
---[ end trace f1d563584ad865f1 ]---
drivers/usb/serial/usb-serial.c: serial_tiocmset - port 0
drivers/usb/serial/usb-serial.c: serial_ioctl - port 0, cmd 0x5401
drivers/usb/serial/usb-serial.c: serial_ioctl - port 0, cmd 0x5404
drivers/usb/serial/usb-serial.c: serial_chars_in_buffer = port 0
drivers/usb/serial/ipaq.c: ipaq_chars_in_buffer - queuelen 0
drivers/usb/serial/usb-serial.c: serial_set_termios - port 0
drivers/usb/serial/usb-serial.c: serial_open
drivers/usb/serial/usb-serial.c: serial_close - port 0
drivers/usb/serial/ipaq.c: ipaq_read_bulk_callback - port 0
ipaq ttyUSB0: ipaq_read_bulk_callback - length = 6, data = 43 4c 49 45 4e 54
drivers/usb/serial/usb-serial.c: serial_write - port 0, 12 byte(s)
drivers/usb/serial/ipaq.c: ipaq_write - port 0
ipaq ttyUSB0: ipaq_write_bulk - length = 12, data = 43 4c 49 45 4e 54 53 45 52 56 45 52
drivers/usb/serial/usb-serial.c: serial_tiocmset - port 0
drivers/usb/serial/usb-serial.c: serial_ioctl - port 0, cmd 0x5401
drivers/usb/serial/usb-serial.c: serial_ioctl - port 0, cmd 0x5404
drivers/usb/serial/usb-serial.c: serial_chars_in_buffer = port 0
drivers/usb/serial/ipaq.c: ipaq_chars_in_buffer - queuelen 0
drivers/usb/serial/usb-serial.c: serial_set_termios - port 0
drivers/usb/serial/usb-serial.c: serial_chars_in_buffer = port 0
drivers/usb/serial/ipaq.c: ipaq_chars_in_buffer - queuelen 0
drivers/usb/serial/ipaq.c: ipaq_write_bulk_callback - port 0
drivers/usb/serial/usb-serial.c: usb_serial_port_work - port 0
drivers/usb/serial/usb-serial.c: serial_chars_in_buffer = port 0
drivers/usb/serial/ipaq.c: ipaq_chars_in_buffer - queuelen 0
drivers/usb/serial/usb-serial.c: serial_ioctl - port 0, cmd 0x80047437
drivers/usb/serial/ipaq.c: ipaq_read_bulk_callback - port 0
ipaq ttyUSB0: ipaq_read_bulk_callback - length = 37, data = 7e ff 7d 23 c0 21 7d 21 7d 20 7d 20 7d 2e 7d 22 7d 26 7d 20 7d 20 7d 20 7d 20 7d 27 7d 22 7d 28 7d 22 dd 31 7e
drivers/usb/serial/usb-serial.c: serial_write - port 0, 46 byte(s)
drivers/usb/serial/ipaq.c: ipaq_write - port 0
ipaq ttyUSB0: ipaq_write_bulk - length = 46, data = 7e ff 7d 23 c0 21 7d 21 7d 21 7d 20 7d 34 7d 22 7d 26 7d 20 7d 20 7d 20 7d 20 7d 25 7d 26 3f f7 32 f7 7d 27 7d 22 7d 28 7d 22 a0 7d 5d 7e
drivers/usb/serial/usb-serial.c: serial_write - port 0, 37 byte(s)
drivers/usb/serial/ipaq.c: ipaq_write - port 0
ipaq ttyUSB0: ipaq_write_bulk - length = 37, data = 7e ff 7d 23 c0 21 7d 22 7d 20 7d 20 7d 2e 7d 22 7d 26 7d 20 7d 20 7d 20 7d 20 7d 27 7d 22 7d 28 7d 22 e3 b2 7e
drivers/usb/serial/ipaq.c: ipaq_write_bulk_callback - port 0
drivers/usb/serial/usb-serial.c: usb_serial_port_work - port 0
drivers/usb/serial/ipaq.c: ipaq_write_bulk_callback - port 0
drivers/usb/serial/usb-serial.c: usb_serial_port_work - port 0
drivers/usb/serial/ipaq.c: ipaq_read_bulk_callback - port 0
ipaq ttyUSB0: ipaq_read_bulk_callback - length = 46, data = 7e ff 7d 23 c0 21 7d 22 7d 21 7d 20 7d 34 7d 22 7d 26 7d 20 7d 20 7d 20 7d 20 7d 25 7d 26 3f f7 32 f7 7d 27 7d 22 7d 28 7d 22 4b 7d 34 7e
drivers/usb/serial/ipaq.c: ipaq_read_bulk_callback - port 0
ipaq ttyUSB0: ipaq_read_bulk_callback - length = 16, data = 7e 80 fd 01 00 00 0a 12 06 00 00 00 01 26 10 7e
drivers/usb/serial/ipaq.c: ipaq_read_bulk_callback - port 0
ipaq ttyUSB0: ipaq_read_bulk_callback - length = 46, data = 7e 80 21 01 00 00 28 02 06 00 2d 0f 01 03 06 00 00 00 00 81 06 00 00 00 00 82 06 00 00 00 00 83 06 00 00 00 00 84 06 00 00 00 00 79 06 7e
drivers/usb/serial/ipaq.c: ipaq_read_bulk_callback - port 0
ipaq ttyUSB0: ipaq_read_bulk_callback - length = 21, data = 7e 80 57 01 00 00 0e 01 0a 86 f1 ae 7d 5e 6d d5 0b 64 a2 cb 7e
padlock: VIA PadLock Hash Engine not detected.
PPP MPPE Compression module registered
PPP BSD Compression module registered
PPP Deflate Compression module registered
drivers/usb/serial/usb-serial.c: serial_write - port 0, 26 byte(s)
drivers/usb/serial/ipaq.c: ipaq_write - port 0
ipaq ttyUSB0: ipaq_write_bulk - length = 26, data = 80 fd 01 01 00 15 12 06 00 00 00 00 1a 04 78 00 18 04 78 00 15 03 2f 95 5f 7e
drivers/usb/serial/usb-serial.c: serial_write - port 0, 33 byte(s)
drivers/usb/serial/ipaq.c: ipaq_write - port 0
ipaq ttyUSB0: ipaq_write_bulk - length = 33, data = 80 21 01 01 00 1c 02 06 00 2d 0f 01 03 06 c0 a8 83 01 81 06 00 00 00 00 83 06 00 00 00 00 75 3d 7e
drivers/usb/serial/usb-serial.c: serial_write - port 0, 15 byte(s)
drivers/usb/serial/ipaq.c: ipaq_write - port 0
ipaq ttyUSB0: ipaq_write_bulk - length = 15, data = 80 fd 04 00 00 0a 12 06 00 00 00 01 9d 8c 7e
drivers/usb/serial/usb-serial.c: serial_write - port 0, 21 byte(s)
drivers/usb/serial/ipaq.c: ipaq_write - port 0
ipaq ttyUSB0: ipaq_write_bulk - length = 21, data = 80 21 04 00 00 10 82 06 00 00 00 00 84 06 00 00 00 00 b7 a2 7e
drivers/usb/serial/usb-serial.c: serial_write - port 0, 26 byte(s)
drivers/usb/serial/ipaq.c: ipaq_write - port 0
ipaq ttyUSB0: ipaq_write_bulk - length = 26, data = c0 21 08 02 00 14 80 57 01 00 00 0e 01 0a 86 f1 ae 7d 5e 6d d5 0b 64 62 e6 7e
drivers/usb/serial/ipaq.c: ipaq_write_bulk_callback - port 0
drivers/usb/serial/ipaq.c: ipaq_read_bulk_callback - port 0
ipaq ttyUSB0: ipaq_read_bulk_callback - length = 21, data = 7e 80 fd 04 01 00 0f 1a 04 78 00 18 04 78 00 15 03 2f a1 c3 7e
drivers/usb/serial/usb-serial.c: serial_write - port 0, 15 byte(s)
drivers/usb/serial/ipaq.c: ipaq_write - port 0
ipaq ttyUSB0: ipaq_write_bulk - length = 15, data = 80 fd 01 02 00 0a 12 06 00 00 00 00 55 9a 7e
drivers/usb/serial/usb-serial.c: usb_serial_port_work - port 0
drivers/usb/serial/ipaq.c: ipaq_write_bulk_callback - port 0
drivers/usb/serial/ipaq.c: ipaq_read_bulk_callback - port 0
ipaq ttyUSB0: ipaq_read_bulk_callback - length = 22, data = 7e 80 21 04 01 00 10 81 06 00 00 00 00 83 06 00 00 00 00 a2 71 7e
drivers/usb/serial/usb-serial.c: serial_write - port 0, 21 byte(s)
drivers/usb/serial/ipaq.c: ipaq_write - port 0
ipaq ttyUSB0: ipaq_write_bulk - length = 21, data = 80 21 01 02 00 10 02 06 00 2d 0f 01 03 06 c0 a8 83 01 4f b2 7e
drivers/usb/serial/usb-serial.c: usb_serial_port_work - port 0
drivers/usb/serial/ipaq.c: ipaq_write_bulk_callback - port 0
drivers/usb/serial/ipaq.c: ipaq_read_bulk_callback - port 0
ipaq ttyUSB0: ipaq_read_bulk_callback - length = 10, data = 7e 80 fd 01 01 00 04 bc 11 7e
drivers/usb/serial/usb-serial.c: serial_write - port 0, 9 byte(s)
drivers/usb/serial/ipaq.c: ipaq_write - port 0
ipaq ttyUSB0: ipaq_write_bulk - length = 9, data = 80 fd 02 01 00 04 71 34 7e
drivers/usb/serial/usb-serial.c: usb_serial_port_work - port 0
drivers/usb/serial/ipaq.c: ipaq_write_bulk_callback - port 0
drivers/usb/serial/ipaq.c: ipaq_read_bulk_callback - port 0
ipaq ttyUSB0: ipaq_read_bulk_callback - length = 34, data = 7e 80 21 01 01 00 1c 02 06 00 2d 0f 01 03 06 00 00 00 00 81 06 00 00 00 00 83 06 00 00 00 00 f1 ac 7e
drivers/usb/serial/usb-serial.c: serial_write - port 0, 27 byte(s)
drivers/usb/serial/ipaq.c: ipaq_write - port 0
ipaq ttyUSB0: ipaq_write_bulk - length = 27, data = 80 21 03 01 00 16 03 06 c0 a8 83 81 81 06 c0 a8 83 01 83 06 c0 a8 83 01 2c 62 7e
drivers/usb/serial/usb-serial.c: usb_serial_port_work - port 0
drivers/usb/serial/ipaq.c: ipaq_write_bulk_callback - port 0
drivers/usb/serial/ipaq.c: ipaq_read_bulk_callback - port 0
ipaq ttyUSB0: ipaq_read_bulk_callback - length = 16, data = 7e 80 fd 02 02 00 0a 12 06 00 00 00 00 3c ee 7e
mppe_decomp_init[0]: unknown key length
drivers/usb/serial/usb-serial.c: usb_serial_port_work - port 0
drivers/usb/serial/ipaq.c: ipaq_write_bulk_callback - port 0
drivers/usb/serial/ipaq.c: ipaq_read_bulk_callback - port 0
ipaq ttyUSB0: ipaq_read_bulk_callback - length = 22, data = 7e 80 21 02 02 00 10 02 06 00 2d 0f 01 03 06 c0 a8 83 01 6e 28 7e
drivers/usb/serial/usb-serial.c: usb_serial_port_work - port 0
drivers/usb/serial/ipaq.c: ipaq_read_bulk_callback - port 0
ipaq ttyUSB0: ipaq_read_bulk_callback - length = 34, data = 7e 80 21 01 02 00 1c 02 06 00 2d 0f 01 03 06 c0 a8 83 81 81 06 c0 a8 83 01 83 06 c0 a8 83 01 a0 29 7e
drivers/usb/serial/usb-serial.c: serial_write - port 0, 33 byte(s)
drivers/usb/serial/ipaq.c: ipaq_write - port 0
ipaq ttyUSB0: ipaq_write_bulk - length = 33, data = 80 21 02 02 00 1c 02 06 00 2d 0f 01 03 06 c0 a8 83 81 81 06 c0 a8 83 01 83 06 c0 a8 83 01 93 73 7e
drivers/usb/serial/ipaq.c: ipaq_write_bulk_callback - port 0
drivers/usb/serial/usb-serial.c: usb_serial_port_work - port 0
drivers/usb/serial/ipaq.c: ipaq_read_bulk_callback - port 0
ipaq ttyUSB0: ipaq_read_bulk_callback - length = 280, data = 7e 21 45 00 01 13 00 00 00 00 80 11 f5 b0 c0 a8 83 81 ff ff ff ff 00 44 00 43 00 ff 00 00 01 08 06 00 12 34 56 78 00 06 00 00 c0 a8 83 81 00 00 00 00 00 00 00 00 00 00 00 00 00 53 45 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 63 82 53 63 35 01 08 37 01 0f ff 6d cb 7e
drivers/usb/serial/ipaq.c: ipaq_read_bulk_callback - port 0
ipaq ttyUSB0: ipaq_read_bulk_callback - length = 280, data = 7e 21 45 00 01 13 00 00 00 00 80 11 f5 b0 c0 a8 83 81 ff ff ff ff 00 44 00 43 00 ff 00 00 01 08 06 00 12 34 56 78 00 06 00 00 c0 a8 83 81 00 00 00 00 00 00 00 00 00 00 00 00 00 53 45 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 63 82 53 63 35 01 08 37 01 0f ff 6d cb 7e
drivers/usb/serial/ipaq.c: ipaq_read_bulk_callback - port 0
ipaq ttyUSB0: ipaq_read_bulk_callback - length = 280, data = 7e 21 45 00 01 13 00 00 00 00 80 11 f5 b0 c0 a8 83 81 ff ff ff ff 00 44 00 43 00 ff 00 00 01 08 06 00 12 34 56 78 00 06 00 00 c0 a8 83 81 00 00 00 00 00 00 00 00 00 00 00 00 00 53 45 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 63 82 53 63 35 01 08 37 01 0f ff 6d cb 7e
drivers/usb/serial/ipaq.c: ipaq_read_bulk_callback - port 0
ipaq ttyUSB0: ipaq_read_bulk_callback - length = 53, data = 7e 21 45 00 00 30 85 a1 40 00 80 06 ed 52 c0 a8 83 81 c0 a8 83 01 05 99 16 2f 84 bb 88 7c 00 00 00 00 70 02 80 00 52 4b 00 00 02 04 05 b4 01 01 04 02 d5 46 7e
drivers/usb/serial/usb-serial.c: serial_write - port 0, 54 byte(s)
drivers/usb/serial/ipaq.c: ipaq_write - port 0
ipaq ttyUSB0: ipaq_write_bulk - length = 54, data = 7e 21 45 00 00 30 00 00 40 00 40 06 b2 f4 c0 a8 83 01 c0 a8 83 81 16 2f 05 99 d9 b4 51 1e 84 bb 88 7d 5d 70 12 16 d0 90 97 00 00 02 04 05 b4 01 01 04 02 c0 dc 7e
drivers/usb/serial/ipaq.c: ipaq_write_bulk_callback - port 0
drivers/usb/serial/usb-serial.c: usb_serial_port_work - port 0
drivers/usb/serial/ipaq.c: ipaq_read_bulk_callback - port 0
ipaq ttyUSB0: ipaq_read_bulk_callback - length = 46, data = 7e 2f 45 00 00 28 85 a2 40 00 80 00 ed 59 c0 a8 83 81 c0 a8 83 01 05 99 16 2f 84 bb 88 7d 5d d9 b4 51 1f 50 10 80 00 54 2b 00 00 a2 e2 7e
drivers/usb/serial/ipaq.c: ipaq_read_bulk_callback - port 0
ipaq ttyUSB0: ipaq_read_bulk_callback - length = 12, data = 7e 2d 10 54 1f 00 00 00 00 e6 b4 7e
drivers/usb/serial/usb-serial.c: serial_write - port 0, 44 byte(s)
drivers/usb/serial/ipaq.c: ipaq_write - port 0
ipaq ttyUSB0: ipaq_write_bulk - length = 44, data = 21 45 00 00 28 ef 15 40 00 40 06 c3 e6 c0 a8 83 01 c0 a8 83 81 16 2f 05 99 d9 b4 51 1f 84 bb 88 81 50 10 16 d0 bd 57 00 00 6d 46 7e
drivers/usb/serial/ipaq.c: ipaq_write_bulk_callback - port 0
drivers/usb/serial/usb-serial.c: usb_serial_port_work - port 0
drivers/usb/serial/ipaq.c: ipaq_read_bulk_callback - port 0
ipaq ttyUSB0: ipaq_read_bulk_callback - length = 12, data = 7e 2d 1f e6 1a 6e 00 00 00 c4 76 7e
drivers/usb/serial/usb-serial.c: serial_write - port 0, 44 byte(s)
drivers/usb/serial/ipaq.c: ipaq_write - port 0
ipaq ttyUSB0: ipaq_write_bulk - length = 44, data = 21 45 00 00 28 ef 16 40 00 40 06 c3 e5 c0 a8 83 01 c0 a8 83 81 16 2f 05 99 d9 b4 51 1f 84 bb 88 85 50 10 16 d0 bd 53 00 00 e0 0e 7e
drivers/usb/serial/ipaq.c: ipaq_write_bulk_callback - port 0
drivers/usb/serial/usb-serial.c: usb_serial_port_work - port 0
drivers/usb/serial/ipaq.c: ipaq_read_bulk_callback - port 0
ipaq ttyUSB0: ipaq_read_bulk_callback - length = 118, data = 7e 2d 1f 19 db 28 00 00 00 04 15 40 04 11 0a 00 00 00 00 00 00 37 63 63 40 00 00 00 00 28 00 00 00 3c 00 00 00 50 00 00 00 00 00 00 00 50 00 6f 00 63 00 6b 00 65 00 74 00 5f 00 50 00 43 00 00 00 50 00 6f 00 63 00 6b 00 65 00 74 00 50 00 43 00 00 00 00 00 68 00 70 00 20 00 69 00 50 00 41 00 51 00 20 00 72 00 7a 00 31 00 37 00 31 00 35 00 00 00 bd 2a 7e
drivers/usb/serial/usb-serial.c: serial_write - port 0, 44 byte(s)
drivers/usb/serial/ipaq.c: ipaq_write - port 0
ipaq ttyUSB0: ipaq_write_bulk - length = 44, data = 21 45 00 00 28 ef 17 40 00 40 06 c3 e4 c0 a8 83 01 c0 a8 83 81 16 2f 05 99 d9 b4 51 1f 84 bb 88 f3 50 10 16 d0 bc e5 00 00 19 f0 7e
drivers/usb/serial/ipaq.c: ipaq_write_bulk_callback - port 0
drivers/usb/serial/usb-serial.c: usb_serial_port_work - port 0
drivers/usb/serial/ipaq.c: ipaq_read_bulk_callback - port 0
ipaq ttyUSB0: ipaq_read_bulk_callback - length = 53, data = 7e 21 45 00 00 30 85 a6 40 00 80 06 ed 4d c0 a8 83 81 c0 a8 83 01 05 9a 1d 0e 84 bc 75 10 00 00 00 00 70 02 80 00 5e d6 00 00 02 04 05 b4 01 01 04 02 4c d0 7e
drivers/usb/serial/usb-serial.c: serial_write - port 0, 45 byte(s)
drivers/usb/serial/ipaq.c: ipaq_write - port 0
ipaq ttyUSB0: ipaq_write_bulk - length = 45, data = 21 45 00 00 28 00 00 40 00 40 06 b2 fc c0 a8 83 01 c0 a8 83 81 1d 0e 05 9a 00 00 00 00 84 bc 75 11 50 14 00 00 0b 87 00 00 7d 5d 00 7e
drivers/usb/serial/ipaq.c: ipaq_write_bulk_callback - port 0
drivers/usb/serial/usb-serial.c: usb_serial_port_work - port 0
drivers/usb/serial/ipaq.c: ipaq_read_bulk_callback - port 0
ipaq ttyUSB0: ipaq_read_bulk_callback - length = 53, data = 7e 21 45 00 00 30 85 a7 40 00 80 06 ed 4c c0 a8 83 81 c0 a8 83 01 05 9a 1d 0e 84 bc 75 10 00 00 00 00 70 02 80 00 5e d6 00 00 02 04 05 b4 01 01 04 02 d7 05 7e
drivers/usb/serial/usb-serial.c: serial_write - port 0, 45 byte(s)
drivers/usb/serial/ipaq.c: ipaq_write - port 0
ipaq ttyUSB0: ipaq_write_bulk - length = 45, data = 21 45 00 00 28 00 00 40 00 40 06 b2 fc c0 a8 83 01 c0 a8 83 81 1d 0e 05 9a 00 00 00 00 84 bc 75 11 50 14 00 00 0b 87 00 00 7d 5d 00 7e
drivers/usb/serial/ipaq.c: ipaq_write_bulk_callback - port 0
drivers/usb/serial/usb-serial.c: usb_serial_port_work - port 0
drivers/usb/serial/ipaq.c: ipaq_read_bulk_callback - port 0
ipaq ttyUSB0: ipaq_read_bulk_callback - length = 53, data = 7e 21 45 00 00 30 85 a8 40 00 80 06 ed 4b c0 a8 83 81 c0 a8 83 01 05 9a 1d 0e 84 bc 75 10 00 00 00 00 70 02 80 00 5e d6 00 00 02 04 05 b4 01 01 04 02 27 5b 7e
drivers/usb/serial/usb-serial.c: serial_write - port 0, 45 byte(s)
drivers/usb/serial/ipaq.c: ipaq_write - port 0
ipaq ttyUSB0: ipaq_write_bulk - length = 45, data = 21 45 00 00 28 00 00 40 00 40 06 b2 fc c0 a8 83 01 c0 a8 83 81 1d 0e 05 9a 00 00 00 00 84 bc 75 11 50 14 00 00 0b 87 00 00 7d 5d 00 7e
drivers/usb/serial/ipaq.c: ipaq_write_bulk_callback - port 0
drivers/usb/serial/usb-serial.c: usb_serial_port_work - port 0
drivers/usb/serial/ipaq.c: ipaq_read_bulk_callback - port 0
ipaq ttyUSB0: ipaq_read_bulk_callback - length = 57, data = 7e 21 45 00 00 34 85 a9 00 00 80 11 2d 3c c0 a8 83 81 c0 a8 83 01 05 9b 00 35 00 20 11 e3 00 f8 01 00 00 01 00 00 00 00 00 00 06 69 73 61 74 61 70 00 00 01 00 01 a1 c6 7e
drivers/usb/serial/usb-serial.c: serial_write - port 0, 84 byte(s)
drivers/usb/serial/ipaq.c: ipaq_write - port 0
ipaq ttyUSB0: ipaq_write_bulk - length = 84, data = 21 45 c0 00 50 71 16 00 00 40 01 81 03 c0 a8 83 01 c0 a8 83 81 03 03 85 02 00 00 00 00 45 00 00 34 85 a9 00 00 80 11 2d 3c c0 a8 83 81 c0 a8 83 01 05 9b 00 35 00 20 11 e3 00 f8 01 00 00 01 00 00 00 00 00 00 06 69 73 61 74 61 70 00 00 01 00 01 82 db 7e
drivers/usb/serial/ipaq.c: ipaq_write_bulk_callback - port 0
drivers/usb/serial/usb-serial.c: usb_serial_port_work - port 0
drivers/usb/serial/ipaq.c: ipaq_read_bulk_callback - port 0
ipaq ttyUSB0: ipaq_read_bulk_callback - length = 53, data = 7e 21 45 00 00 30 85 aa 40 00 80 06 ed 49 c0 a8 83 81 c0 a8 83 01 05 9a 1d 0e 84 bc 75 10 00 00 00 00 70 02 80 00 5e d6 00 00 02 04 05 b4 01 01 04 02 00 f8 7e
drivers/usb/serial/usb-serial.c: serial_write - port 0, 45 byte(s)
drivers/usb/serial/ipaq.c: ipaq_write - port 0
ipaq ttyUSB0: ipaq_write_bulk - length = 45, data = 21 45 00 00 28 00 00 40 00 40 06 b2 fc c0 a8 83 01 c0 a8 83 81 1d 0e 05 9a 00 00 00 00 84 bc 75 11 50 14 00 00 0b 87 00 00 7d 5d 00 7e
drivers/usb/serial/ipaq.c: ipaq_write_bulk_callback - port 0
drivers/usb/serial/usb-serial.c: usb_serial_port_work - port 0

[Bug #10843] Display artifacts on XOrg logout with PAT kernel and VESA framebuffer

[Rafael J. Wysocki]

This message has been generated automatically as a part of a report
of recent regressions.

The following bug entry is on the current list of known regressions
from 2.6.25.  Please verify if it still should be listed.


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=10843
Subject		: Display artifacts on XOrg logout with PAT kernel and VESA framebuffer
Submitter	: Frans Pop <elendil@planet.nl>
Date		: 2008-05-31 14:04 (30 days old)
References	: http://lkml.org/lkml/2008/6/7/206
		  http://lkml.org/lkml/2008/6/15/119
		  http://lkml.org/lkml/2008/6/23/160

Re: [Bug #10843] Display artifacts on XOrg logout with PAT kernel and VESA framebuffer

[Frans Pop]

On Sunday 29 June 2008, you wrote:
> The following bug entry is on the current list of known regressions
> from 2.6.25.  Please verify if it still should be listed.
>
> Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=10843
> Subject	: Display artifacts on XOrg logout with PAT kernel and VESA
> 		  framebuffer

Yes.

Re: [Bug #10868] Oops on loading ipaq module since 2.6.26, prevents use of device

[Oliver Neukum]

Am Freitag 27 Juni 2008 21:28:54 schrieb Adam Williamson:
> On Wed, 2008-06-25 at 17:41 +0200, Oliver Neukum wrote:
> > Am Mittwoch 25 Juni 2008 04:05:13 schrieb Adam Williamson:
> > > On Mon, 2008-06-23 at 20:41 +0200, Oliver Neukum wrote:
> > > 
> > > > It is the module option "debug" for usb-serial.
> > > 
> > > OK, here you go:
> > 
> > Please also set the debug module parameter for the ipaq module.
> 
> OK.

Your device is considered to have two ports but not enough endpoints.
Please provide the output of "lsusb -v"

	Regards
		Oliver

Re: [Bug #10868] Oops on loading ipaq module since 2.6.26, prevents use of device

[Adam Williamson]

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

On Mon, 2008-06-30 at 15:09 +0200, Oliver Neukum wrote:
> Am Freitag 27 Juni 2008 21:28:54 schrieb Adam Williamson:
> > On Wed, 2008-06-25 at 17:41 +0200, Oliver Neukum wrote:
> > > Am Mittwoch 25 Juni 2008 04:05:13 schrieb Adam Williamson:
> > > > On Mon, 2008-06-23 at 20:41 +0200, Oliver Neukum wrote:
> > > > 
> > > > > It is the module option "debug" for usb-serial.
> > > > 
> > > > OK, here you go:
> > > 
> > > Please also set the debug module parameter for the ipaq module.
> > 
> > OK.
> 
> Your device is considered to have two ports but not enough endpoints.
> Please provide the output of "lsusb -v"

Here's the lsusb stanza for the device.
-- 
adamw

[-- Attachment #2: 26_lsusb.txt --]
[-- Type: text/plain, Size: 2091 bytes --]

Bus 003 Device 002: ID 03f0:1016 Hewlett-Packard Jornada 548 / iPAQ HW6515 Pocket PC 
Device Descriptor:
  bLength                18
  bDescriptorType         1
  bcdUSB               1.00
  bDeviceClass          255 Vendor Specific Class
  bDeviceSubClass       255 Vendor Specific Subclass
  bDeviceProtocol       255 Vendor Specific Protocol
  bMaxPacketSize0        16
  idVendor           0x03f0 Hewlett-Packard
  idProduct          0x1016 Jornada 548 / iPAQ HW6515 Pocket PC 
  bcdDevice            0.00
  iManufacturer           0 
  iProduct                0 
  iSerial                 0 
  bNumConfigurations      1
  Configuration Descriptor:
    bLength                 9
    bDescriptorType         2
    wTotalLength           32
    bNumInterfaces          1
    bConfigurationValue     1
    iConfiguration          0 
    bmAttributes         0x80
      (Bus Powered)
    MaxPower               50mA
    Interface Descriptor:
      bLength                 9
      bDescriptorType         4
      bInterfaceNumber        0
      bAlternateSetting       0
      bNumEndpoints           2
      bInterfaceClass       255 Vendor Specific Class
      bInterfaceSubClass    255 Vendor Specific Subclass
      bInterfaceProtocol    255 Vendor Specific Protocol
      iInterface              0 
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x81  EP 1 IN
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0040  1x 64 bytes
        bInterval               0
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x04  EP 4 OUT
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0040  1x 64 bytes
        bInterval               0
Device Status:     0x0000
  (Bus Powered)

Re: [Bug #10868] Oops on loading ipaq module since 2.6.26, prevents use of device

[Oliver Neukum]

Am Mittwoch 02 Juli 2008 22:40:57 schrieb Adam Williamson:
> On Mon, 2008-06-30 at 15:09 +0200, Oliver Neukum wrote:
> > Am Freitag 27 Juni 2008 21:28:54 schrieb Adam Williamson:
> > > On Wed, 2008-06-25 at 17:41 +0200, Oliver Neukum wrote:
> > > > Am Mittwoch 25 Juni 2008 04:05:13 schrieb Adam Williamson:
> > > > > On Mon, 2008-06-23 at 20:41 +0200, Oliver Neukum wrote:
> > > > > 
> > > > > > It is the module option "debug" for usb-serial.
> > > > > 
> > > > > OK, here you go:
> > > > 
> > > > Please also set the debug module parameter for the ipaq module.
> > > 
> > > OK.
> > 
> > Your device is considered to have two ports but not enough endpoints.
> > Please provide the output of "lsusb -v"
> 
> Here's the lsusb stanza for the device.

This is odd. Your device shows one interface with one endpoint bulk and
bulk out respectively. Yet two ports are created. Odd.

	Regards
		Oliver

Re: [Bug #10868] Oops on loading ipaq module since 2.6.26, prevents use of device

[Adam Williamson]

On Wed, 2008-07-02 at 23:33 +0200, Oliver Neukum wrote:

> This is odd. Your device shows one interface with one endpoint bulk and
> bulk out respectively. Yet two ports are created. Odd.

OK. If you mean /dev/ttyUSB0 and /dev/ttyUSB1 are always both created
when the device is plugged in - yep. This is the case in the working
kernel too. From what I've seen in howtos and the like, this seems to be
the case for most such devices. Well, let me know what else you need
from me. :)
-- 
adamw

Re: [Bug #10868] Oops on loading ipaq module since 2.6.26, prevents use of device

[Oliver Neukum]

Am Mittwoch 02 Juli 2008 23:41:40 schrieb Adam Williamson:
> On Wed, 2008-07-02 at 23:33 +0200, Oliver Neukum wrote:
> 
> > This is odd. Your device shows one interface with one endpoint bulk and
> > bulk out respectively. Yet two ports are created. Odd.
> 
> OK. If you mean /dev/ttyUSB0 and /dev/ttyUSB1 are always both created
> when the device is plugged in - yep. This is the case in the working

Now this is very hard to explain. From the code in 2.6.25 it is clear that
only ttyUSB0 will be created. Please verify that indeed you get ttyUSB0
and ttyUSB1 with the kernel working for you.

> kernel too. From what I've seen in howtos and the like, this seems to be
> the case for most such devices. Well, let me know what else you need
> from me. :)

As far as I can tell somebody changed the ipaq driver in 2.6.26-rc6. I cannot
find the exact patch that did it in Greg's directory. As it causes a regression
here's a reversal.

	Regards
		Oliver

Signed-off-by: Oliver Neukum <oneukum@suse.de>

---

--- linux-2.6.26-greg/drivers/usb/serial/ipaq.alt.c	2008-07-03 09:01:37.000000000 +0200
+++ linux-2.6.26-greg/drivers/usb/serial/ipaq.c	2008-07-03 09:01:47.000000000 +0200
@@ -570,7 +570,7 @@ static struct usb_serial_driver ipaq_dev
 	.description =		"PocketPC PDA",
 	.usb_driver = 		&ipaq_driver,
 	.id_table =		ipaq_id_table,
-	.num_ports =		2,
+	.num_ports =		1,
 	.open =			ipaq_open,
 	.close =		ipaq_close,
 	.attach =		ipaq_startup,

Re: [Bug 10868] Oops on loading ipaq module since 2.6.26, prevents use of device

[Adrian Bunk]

On Thu, Jul 03, 2008 at 10:05:57AM +0200, Oliver Neukum wrote:
> Am Mittwoch 02 Juli 2008 23:41:40 schrieb Adam Williamson:
> > On Wed, 2008-07-02 at 23:33 +0200, Oliver Neukum wrote:
> > 
> > > This is odd. Your device shows one interface with one endpoint bulk and
> > > bulk out respectively. Yet two ports are created. Odd.
> > 
> > OK. If you mean /dev/ttyUSB0 and /dev/ttyUSB1 are always both created
> > when the device is plugged in - yep. This is the case in the working
> 
> Now this is very hard to explain. From the code in 2.6.25 it is clear that
> only ttyUSB0 will be created. Please verify that indeed you get ttyUSB0
> and ttyUSB1 with the kernel working for you.
> 
> > kernel too. From what I've seen in howtos and the like, this seems to be
> > the case for most such devices. Well, let me know what else you need
> > from me. :)
> 
> As far as I can tell somebody changed the ipaq driver in 2.6.26-rc6. I cannot
> find the exact patch that did it in Greg's directory. As it causes a regression
> here's a reversal.


It was changed by:


commit e1879b19b0abdb387e4aeb0b935a486cc75042fb
Author: Matthias Geissert <matthias.geissert@web.de>
Date:   Thu Mar 6 22:00:33 2008 +0100

    USB: ipaq: fix devices having more than one endpoint
    
    The ipaq module  supports devices with one endpoint only. Some devices,
    e.g. Yakumo Delta 300, have more than one endpoint.
    
    This patch fixes support for devices having up to 2 endpoints which used
    to work on older kernel versions.
    
    Signed-off-by: Matthias Geissert <matthias.geissert@web.de>
    Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>

diff --git a/drivers/usb/serial/ipaq.c b/drivers/usb/serial/ipaq.c
index 9b38a08..17f2a53 100644
--- a/drivers/usb/serial/ipaq.c
+++ b/drivers/usb/serial/ipaq.c
@@ -571,9 +571,9 @@ static struct usb_serial_driver ipaq_device = {
 	.usb_driver = 		&ipaq_driver,
 	.id_table =		ipaq_id_table,
 	.num_interrupt_in =	NUM_DONT_CARE,
-	.num_bulk_in =		1,
-	.num_bulk_out =		1,
-	.num_ports =		1,
+	.num_bulk_in =		NUM_DONT_CARE,
+	.num_bulk_out =		NUM_DONT_CARE,
+	.num_ports =		2,
 	.open =			ipaq_open,
 	.close =		ipaq_close,
 	.attach =		ipaq_startup,


> 	Regards
> 		Oliver
> 
> Signed-off-by: Oliver Neukum <oneukum@suse.de>
> 
> ---
> 
> --- linux-2.6.26-greg/drivers/usb/serial/ipaq.alt.c	2008-07-03 09:01:37.000000000 +0200
> +++ linux-2.6.26-greg/drivers/usb/serial/ipaq.c	2008-07-03 09:01:47.000000000 +0200
> @@ -570,7 +570,7 @@ static struct usb_serial_driver ipaq_dev
>  	.description =		"PocketPC PDA",
>  	.usb_driver = 		&ipaq_driver,
>  	.id_table =		ipaq_id_table,
> -	.num_ports =		2,
> +	.num_ports =		1,
>  	.open =			ipaq_open,
>  	.close =		ipaq_close,
>  	.attach =		ipaq_startup,
> 

cu
Adrian

-- 

       "Is there not promise of rain?" Ling Tan asked suddenly out
        of the darkness. There had been need of rain for many days.
       "Only a promise," Lao Er said.
                                       Pearl S. Buck - Dragon Seed

Re: [Bug 10868] Oops on loading ipaq module since 2.6.26, prevents use of device

[Oliver Neukum]

Am Donnerstag 03 Juli 2008 10:57:33 schrieb Adrian Bunk:
> On Thu, Jul 03, 2008 at 10:05:57AM +0200, Oliver Neukum wrote:
 
> > As far as I can tell somebody changed the ipaq driver in 2.6.26-rc6. I cannot
> > find the exact patch that did it in Greg's directory. As it causes a regression
> > here's a reversal.
> 
> 
> It was changed by:

Thanks, did you do git magic?

> commit e1879b19b0abdb387e4aeb0b935a486cc75042fb
> Author: Matthias Geissert <matthias.geissert@web.de>
> Date:   Thu Mar 6 22:00:33 2008 +0100
> 
>     USB: ipaq: fix devices having more than one endpoint
>     
>     The ipaq module  supports devices with one endpoint only. Some devices,
>     e.g. Yakumo Delta 300, have more than one endpoint.
>     
>     This patch fixes support for devices having up to 2 endpoints which used
>     to work on older kernel versions.
>     
>     Signed-off-by: Matthias Geissert <matthias.geissert@web.de>
>     Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
> 
> diff --git a/drivers/usb/serial/ipaq.c b/drivers/usb/serial/ipaq.c
> index 9b38a08..17f2a53 100644
> --- a/drivers/usb/serial/ipaq.c
> +++ b/drivers/usb/serial/ipaq.c
> @@ -571,9 +571,9 @@ static struct usb_serial_driver ipaq_device = {
>  	.usb_driver = 		&ipaq_driver,
>  	.id_table =		ipaq_id_table,
>  	.num_interrupt_in =	NUM_DONT_CARE,
> -	.num_bulk_in =		1,
> -	.num_bulk_out =		1,
> -	.num_ports =		1,
> +	.num_bulk_in =		NUM_DONT_CARE,
> +	.num_bulk_out =		NUM_DONT_CARE,

This is good.

> +	.num_ports =		2,

This is fatal.

The patch I sent reverts only this part, so this issue is solved.

	Regards
		Oliver

Re: [Bug 10868] Oops on loading ipaq module since 2.6.26, prevents use of device

[Adrian Bunk]

On Thu, Jul 03, 2008 at 04:08:44PM +0200, Oliver Neukum wrote:
> Am Donnerstag 03 Juli 2008 10:57:33 schrieb Adrian Bunk:
> > On Thu, Jul 03, 2008 at 10:05:57AM +0200, Oliver Neukum wrote:
>  
> > > As far as I can tell somebody changed the ipaq driver in 2.6.26-rc6. I cannot
> > > find the exact patch that did it in Greg's directory. As it causes a regression
> > > here's a reversal.
> > 
> > 
> > It was changed by:
> 
> Thanks, did you do git magic?

I wouldn't call that "magic":

$ git-log v2.6.25.. drivers/usb/serial/ipaq.c

>...
> > --- a/drivers/usb/serial/ipaq.c
> > +++ b/drivers/usb/serial/ipaq.c
> > @@ -571,9 +571,9 @@ static struct usb_serial_driver ipaq_device = {
> >  	.usb_driver = 		&ipaq_driver,
> >  	.id_table =		ipaq_id_table,
> >  	.num_interrupt_in =	NUM_DONT_CARE,
> > -	.num_bulk_in =		1,
> > -	.num_bulk_out =		1,
> > -	.num_ports =		1,
> > +	.num_bulk_in =		NUM_DONT_CARE,
> > +	.num_bulk_out =		NUM_DONT_CARE,
> 
> This is good.

These fields are removed by a later commit in 2.6.26...  8-)

> > +	.num_ports =		2,
> 
> This is fatal.
> 
> The patch I sent reverts only this part, so this issue is solved.
> 
> 	Regards
> 		Oliver

cu
Adrian

-- 

       "Is there not promise of rain?" Ling Tan asked suddenly out
        of the darkness. There had been need of rain for many days.
       "Only a promise," Lao Er said.
                                       Pearl S. Buck - Dragon Seed

Re: [Bug 10868] Oops on loading ipaq module since 2.6.26, prevents use of device

[Oliver Neukum]

Am Donnerstag 03 Juli 2008 16:20:30 schrieb Adrian Bunk:
> On Thu, Jul 03, 2008 at 04:08:44PM +0200, Oliver Neukum wrote:
> > Am Donnerstag 03 Juli 2008 10:57:33 schrieb Adrian Bunk:

> > > --- a/drivers/usb/serial/ipaq.c
> > > +++ b/drivers/usb/serial/ipaq.c
> > > @@ -571,9 +571,9 @@ static struct usb_serial_driver ipaq_device = {
> > >  	.usb_driver = 		&ipaq_driver,
> > >  	.id_table =		ipaq_id_table,
> > >  	.num_interrupt_in =	NUM_DONT_CARE,
> > > -	.num_bulk_in =		1,
> > > -	.num_bulk_out =		1,
> > > -	.num_ports =		1,
> > > +	.num_bulk_in =		NUM_DONT_CARE,
> > > +	.num_bulk_out =		NUM_DONT_CARE,
> > 
> > This is good.
> 
> These fields are removed by a later commit in 2.6.26...  8-)

Well, NUM_DONT_CARE is default, so it makes no difference, but a comment
would have been nice.

	Regards
		Oliver

Re: [Bug 10868] Oops on loading ipaq module since 2.6.26, prevents use of device

[Adrian Bunk]

On Thu, Jul 03, 2008 at 04:26:48PM +0200, Oliver Neukum wrote:
> Am Donnerstag 03 Juli 2008 16:20:30 schrieb Adrian Bunk:
> > On Thu, Jul 03, 2008 at 04:08:44PM +0200, Oliver Neukum wrote:
> > > Am Donnerstag 03 Juli 2008 10:57:33 schrieb Adrian Bunk:
> 
> > > > --- a/drivers/usb/serial/ipaq.c
> > > > +++ b/drivers/usb/serial/ipaq.c
> > > > @@ -571,9 +571,9 @@ static struct usb_serial_driver ipaq_device = {
> > > >  	.usb_driver = 		&ipaq_driver,
> > > >  	.id_table =		ipaq_id_table,
> > > >  	.num_interrupt_in =	NUM_DONT_CARE,
> > > > -	.num_bulk_in =		1,
> > > > -	.num_bulk_out =		1,
> > > > -	.num_ports =		1,
> > > > +	.num_bulk_in =		NUM_DONT_CARE,
> > > > +	.num_bulk_out =		NUM_DONT_CARE,
> > > 
> > > This is good.
> > 
> > These fields are removed by a later commit in 2.6.26...  8-)
> 
> Well, NUM_DONT_CARE is default, so it makes no difference, but a comment
> would have been nice.

They were removed from struct usb_serial_driver in 
include/linux/usb/serial.h since the checks they were used for caused 
more problems than they solved.

But you are right that the effects of the removal are the same as 
NUM_DONT_CARE.

> 	Regards
> 		Oliver

cu
Adrian

-- 

       "Is there not promise of rain?" Ling Tan asked suddenly out
        of the darkness. There had been need of rain for many days.
       "Only a promise," Lao Er said.
                                       Pearl S. Buck - Dragon Seed

Re: [Bug #10868] Oops on loading ipaq module since 2.6.26, prevents use of device

[Adam Williamson]

On Thu, 2008-07-03 at 10:05 +0200, Oliver Neukum wrote:
> Am Mittwoch 02 Juli 2008 23:41:40 schrieb Adam Williamson:
> > On Wed, 2008-07-02 at 23:33 +0200, Oliver Neukum wrote:
> > 
> > > This is odd. Your device shows one interface with one endpoint bulk and
> > > bulk out respectively. Yet two ports are created. Odd.
> > 
> > OK. If you mean /dev/ttyUSB0 and /dev/ttyUSB1 are always both created
> > when the device is plugged in - yep. This is the case in the working
> 
> Now this is very hard to explain. From the code in 2.6.25 it is clear that
> only ttyUSB0 will be created. Please verify that indeed you get ttyUSB0
> and ttyUSB1 with the kernel working for you.

It is possible I'm misremembering on that front. I will check.
-- 
adamw

[Bug #10843] Display artifacts on XOrg logout with PAT kernel and VESA framebuffer

[Rafael J. Wysocki]

This message has been generated automatically as a part of a report
of recent regressions.

The following bug entry is on the current list of known regressions
from 2.6.25.  Please verify if it still should be listed.


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=10843
Subject		: Display artifacts on XOrg logout with PAT kernel and VESA framebuffer
Submitter	: Frans Pop <elendil-EIBgga6/0yRmR6Xm/wNWPw@public.gmane.org>
Date		: 2008-05-31 14:04 (37 days old)
References	: http://lkml.org/lkml/2008/6/7/206
		  http://lkml.org/lkml/2008/6/15/119
		  http://lkml.org/lkml/2008/6/23/160

[Bug #10843] Display artifacts on XOrg logout with PAT kernel and VESA framebuffer

[Rafael J. Wysocki]

This message has been generated automatically as a part of a report
of recent regressions.

The following bug entry is on the current list of known regressions
from 2.6.25.  Please verify if it still should be listed.


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=10843
Subject		: Display artifacts on XOrg logout with PAT kernel and VESA framebuffer
Submitter	: Frans Pop <elendil@planet.nl>
Date		: 2008-05-31 14:04 (37 days old)
References	: http://lkml.org/lkml/2008/6/7/206
		  http://lkml.org/lkml/2008/6/15/119
		  http://lkml.org/lkml/2008/6/23/160

Re: [Bug #10843] Display artifacts on XOrg logout with PAT kernel and VESA framebuffer

[Frans Pop]

On Sunday 06 July 2008, you wrote:
> The following bug entry is on the current list of known regressions
> from 2.6.25.  Please verify if it still should be listed.
>
> Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=10843
> Subject	: Display artifacts on XOrg logout with PAT kernel and VESA
> 		  framebuffer

Yes.

Re: [Bug 10868] Oops on loading ipaq module since 2.6.26, prevents use of device

[Matthias Geissert]

Am Donnerstag, 3. Juli 2008 16:08:44 schrieb Oliver Neukum:


> >  	.num_interrupt_in =	NUM_DONT_CARE,
> > -	.num_bulk_in =		1,
> > -	.num_bulk_out =		1,
> > -	.num_ports =		1,
> > +	.num_bulk_in =		NUM_DONT_CARE,
> > +	.num_bulk_out =		NUM_DONT_CARE,
>
> This is good.
>
> > +	.num_ports =		2,
>
> This is fatal.

I checked what you said with kernel 2.6.26 rc9.  I set num_ports to 5. It 
worked quite well until I tried to connect to a non-existing endpoint. 

However, the problem is that the Yakumo Delta needs to connect to the 2nd 
endpoint. You can connect to the first one but you don't get any data. 

Is there any good way to tell the ipaq driver to use the 2nd endpoint? Maybe 
one could provide a different struct usb_serial_driver ipaq_device depending 
on the usb id or an option which tells the driver to use 2 endpoints.

Regards,
matthias  

Re: [Bug 10868] Oops on loading ipaq module since 2.6.26, prevents use of device

[Oliver Neukum]

Am Montag 07 Juli 2008 20:16:02 schrieb Matthias Geissert:
> Am Donnerstag, 3. Juli 2008 16:08:44 schrieb Oliver Neukum:
> 
> 
> > >  	.num_interrupt_in =	NUM_DONT_CARE,
> > > -	.num_bulk_in =		1,
> > > -	.num_bulk_out =		1,
> > > -	.num_ports =		1,
> > > +	.num_bulk_in =		NUM_DONT_CARE,
> > > +	.num_bulk_out =		NUM_DONT_CARE,
> >
> > This is good.
> >
> > > +	.num_ports =		2,
> >
> > This is fatal.
> 
> I checked what you said with kernel 2.6.26 rc9.  I set num_ports to 5. It 
> worked quite well until I tried to connect to a non-existing endpoint. 
> 
> However, the problem is that the Yakumo Delta needs to connect to the 2nd 
> endpoint. You can connect to the first one but you don't get any data. 
> 
> Is there any good way to tell the ipaq driver to use the 2nd endpoint? Maybe 
> one could provide a different struct usb_serial_driver ipaq_device depending 
> on the usb id or an option which tells the driver to use 2 endpoints.

If only these devices have a second input endpoint, we can detect that
in attach().

	Regards
		Oliver

[Bug #10843] Display artifacts on XOrg logout with PAT kernel and VESA framebuffer

[Rafael J. Wysocki]

This message has been generated automatically as a part of a report
of recent regressions.

The following bug entry is on the current list of known regressions
from 2.6.25.  Please verify if it still should be listed.


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=10843
Subject		: Display artifacts on XOrg logout with PAT kernel and VESA framebuffer
Submitter	: Frans Pop <elendil-EIBgga6/0yRmR6Xm/wNWPw@public.gmane.org>
Date		: 2008-05-31 14:04 (44 days old)
References	: http://lkml.org/lkml/2008/6/7/206
		  http://lkml.org/lkml/2008/6/15/119
		  http://lkml.org/lkml/2008/6/23/160

[Bug #10843] Display artifacts on XOrg logout with PAT kernel and VESA framebuffer

[Rafael J. Wysocki]

This message has been generated automatically as a part of a report
of recent regressions.

The following bug entry is on the current list of known regressions
from 2.6.25.  Please verify if it still should be listed.


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=10843
Subject		: Display artifacts on XOrg logout with PAT kernel and VESA framebuffer
Submitter	: Frans Pop <elendil@planet.nl>
Date		: 2008-05-31 14:04 (44 days old)
References	: http://lkml.org/lkml/2008/6/7/206
		  http://lkml.org/lkml/2008/6/15/119
		  http://lkml.org/lkml/2008/6/23/160

Re: [Bug 10843] Display artifacts on XOrg logout with PAT kernel and VESA framebuffer

[Frans Pop]

Bug-Entry  : http://bugzilla.kernel.org/show_bug.cgi?id=10843

On Wednesday 25 June 2008, Suresh Siddha wrote:
> On Mon, Jun 23, 2008 at 05:38:59AM -0700, Frans Pop wrote:
> > On Sunday 15 June 2008, Siddha, Suresh B wrote:
> > > Frans, With or without pat, in the recent kernels (like
> > > 2.6.26-rc4/rc5 etc), ioremap() uses  UC- and PCI mmap of
> > > /sys/devices/pci.../resource (used by X) uses UC-
> > >
> > > And fb_mmap() also uses UC-.
> > >
> > > It's interesting that you don't see this artifact with "nopat".
> > > Essentially with or with out pat enabled, we use the same memory
> > > attributes. So depending on the MTRR setup (set by X server),
> > > effective memory attribute across different mappings should be same
> > > (which is UC- or WC with mtrr).
> >
> > Any progress on this issue? It's still there with -rc7, but I doubt
> > that comes as a surprise.
> >
> > Has anyone tried to reproduce this? I would think that should be
> > trivial.
> >
> > Just as a summary:
> > - Intel 82945G/GZ graphics [8086:2772] (ICH7 based system)
> > - FB_VESA=y, FRAMEBUFFER_CONSOLE=y
> > - boot with vga=791
> > - Log in to X and KDE; I do need to really log in there are no
> >   artifacts if I exit X from the kdm login dialog
> > - artifacts show on logout
> >
>
> FJP, We will try to reproduce this and getback.

Hello all,

I'd like to bring this issue to your attention once again as it is still 
present in 2.6.27-rc6.

Note also that I can trivially reproduce exactly the same behavior on 
three rather different systems. The artifacts even look similar and in 
all cases they disappear with 'nopat'.

The systems are:
Toshiba Satellite A40 laptop:
- Intel 82852/855GM Integrated Graphics Device [8086:3582]
- ICH4 based
- Mobile Intel Pentium 4 processor, i386 kernel
Intel desktop system:
- Intel 82945G/GZ Integrated Graphics Controller [8086:2772]
- ICH7 based
- Pentium D processor, x86_64 kernel
HP Compaq 2510p laptop:
- Intel Mobile GM965/GL960 Integrated Graphics Controller [8086:2a02]
- ICH8 based
- Core2 Duo processor, x86_64 kernel

Have you had any luck reproducing it?

> Your earlier responses did not give many clues.

Well, unfortunately I can only provide the info you ask for :-)

Cheers,
FJP

RE: [Bug 10843] Display artifacts on XOrg logout with PAT kernel and VESA framebuffer

[Pallipadi, Venkatesh]

>-----Original Message-----
>From: Frans Pop [mailto:elendil@planet.nl]
>Sent: Friday, September 12, 2008 3:54 AM
>To: Siddha, Suresh B
>Cc: Linux Kernel Mailing List; Pallipadi, Venkatesh; Ingo
>Molnar; arjan@linux.intel.com; jbarnes@virtuousgeek.org
>Subject: Re: [Bug 10843] Display artifacts on XOrg logout with
>PAT kernel and VESA framebuffer
>
>Bug-Entry  : http://bugzilla.kernel.org/show_bug.cgi?id=10843
>
>On Wednesday 25 June 2008, Suresh Siddha wrote:
>> On Mon, Jun 23, 2008 at 05:38:59AM -0700, Frans Pop wrote:
>> > On Sunday 15 June 2008, Siddha, Suresh B wrote:
>> > > Frans, With or without pat, in the recent kernels (like
>> > > 2.6.26-rc4/rc5 etc), ioremap() uses  UC- and PCI mmap of
>> > > /sys/devices/pci.../resource (used by X) uses UC-
>> > >
>> > > And fb_mmap() also uses UC-.
>> > >
>> > > It's interesting that you don't see this artifact with "nopat".
>> > > Essentially with or with out pat enabled, we use the same memory
>> > > attributes. So depending on the MTRR setup (set by X server),
>> > > effective memory attribute across different mappings
>should be same
>> > > (which is UC- or WC with mtrr).
>> >
>> > Any progress on this issue? It's still there with -rc7, but I doubt
>> > that comes as a surprise.
>> >
>> > Has anyone tried to reproduce this? I would think that should be
>> > trivial.
>> >
>> > Just as a summary:
>> > - Intel 82945G/GZ graphics [8086:2772] (ICH7 based system)
>> > - FB_VESA=y, FRAMEBUFFER_CONSOLE=y
>> > - boot with vga=791
>> > - Log in to X and KDE; I do need to really log in there are no
>> >   artifacts if I exit X from the kdm login dialog
>> > - artifacts show on logout
>> >
>>
>> FJP, We will try to reproduce this and getback.
>
>Hello all,
>
>I'd like to bring this issue to your attention once again as
>it is still
>present in 2.6.27-rc6.
>
>Note also that I can trivially reproduce exactly the same behavior on
>three rather different systems. The artifacts even look similar and in
>all cases they disappear with 'nopat'.
>
>The systems are:
>Toshiba Satellite A40 laptop:
>- Intel 82852/855GM Integrated Graphics Device [8086:3582]
>- ICH4 based
>- Mobile Intel Pentium 4 processor, i386 kernel
>Intel desktop system:
>- Intel 82945G/GZ Integrated Graphics Controller [8086:2772]
>- ICH7 based
>- Pentium D processor, x86_64 kernel
>HP Compaq 2510p laptop:
>- Intel Mobile GM965/GL960 Integrated Graphics Controller [8086:2a02]
>- ICH8 based
>- Core2 Duo processor, x86_64 kernel
>
>Have you had any luck reproducing it?
>
>> Your earlier responses did not give many clues.
>
>Well, unfortunately I can only provide the info you ask for :-)
>

Hi,

What does the output of x86/pat_memtype_list under debugfs look like?

You may need the following if you are not already mounting debugfs.
mount -t debugfs debugfs /proc/sys/debug
cat /proc/sys/debug/x86/pat_memtype_list

Thanks,
Venki

Re: [Bug 10843] Display artifacts on XOrg logout with PAT kernel and VESA framebuffer

[Frans Pop]

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

On Friday 12 September 2008, Pallipadi, Venkatesh wrote:
> What does the output of x86/pat_memtype_list under debugfs look like?

I've attached that file and dmesg output for two of the machines.

Cheers,
FJP


[-- Attachment #2: pat.tgz --]
[-- Type: application/x-tgz, Size: 260902 bytes --]

RE: [Bug 10843] Display artifacts on XOrg logout with PAT kernel and VESA framebuffer

[Pallipadi, Venkatesh]

>-----Original Message-----
>From: Frans Pop [mailto:elendil@planet.nl]
>Sent: Friday, September 12, 2008 6:34 AM
>To: Pallipadi, Venkatesh
>Cc: Siddha, Suresh B; Linux Kernel Mailing List; Ingo Molnar;
>arjan@linux.intel.com; jbarnes@virtuousgeek.org
>Subject: Re: [Bug 10843] Display artifacts on XOrg logout with
>PAT kernel and VESA framebuffer
>
>On Friday 12 September 2008, Pallipadi, Venkatesh wrote:
>> What does the output of x86/pat_memtype_list under debugfs look like?
>
>I've attached that file and dmesg output for two of the machines.
>

OK. This is the same issue as the one on this thread here
http://www.ussg.iu.edu/hypermail/linux/kernel/0808.2/1532.html


We have too many entires in PAT list due to RAM pages being marked
UC by drivers. Unfortunately, there are no quick fixes that can fix
this for 2.6.27. However, we are aware of the problem here and
working on a more complete fix for this. We should have the patch
for it soon.

Thanks,
Venki

RE: [Bug 10843] Display artifacts on XOrg logout with PAT kernel and VESA framebuffer

[Pallipadi, Venkatesh]

>-----Original Message-----
>From: Pallipadi, Venkatesh
>
>>-----Original Message-----
>>From: Frans Pop [mailto:elendil@planet.nl]
>>Sent: Friday, September 12, 2008 6:34 AM
>>
>>
>>I've attached that file and dmesg output for two of the machines.
>>
>
>OK. This is the same issue as the one on this thread here
>http://www.ussg.iu.edu/hypermail/linux/kernel/0808.2/1532.html
>
>
>We have too many entires in PAT list due to RAM pages being marked
>UC by drivers. Unfortunately, there are no quick fixes that can fix
>this for 2.6.27. However, we are aware of the problem here and
>working on a more complete fix for this. We should have the patch
>for it soon.
>

Can you try the patch here
http://www.ussg.iu.edu/hypermail/linux/kernel/0809.1/2074.html
And report back whether that resolves the issue.

Thanks,
Venki

Re: [Bug 10843] Display artifacts on XOrg logout with PAT kernel and VESA framebuffer

[Frans Pop]

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

On Saturday 13 September 2008, Pallipadi, Venkatesh wrote:
> >We have too many entires in PAT list due to RAM pages being marked
> >UC by drivers. Unfortunately, there are no quick fixes that can fix
> >this for 2.6.27. However, we are aware of the problem here and
> >working on a more complete fix for this. We should have the patch
> >for it soon.
>
> Can you try the patch here
> http://www.ussg.iu.edu/hypermail/linux/kernel/0809.1/2074.html
> And report back whether that resolves the issue.

Yes, that solves the issue. The display is now free of artifacts again, 
both on logout and when I switch users in X.
The pat_memtype_list looks a lot more sane too (see attachment).

So it _was_ a regression caused by pat itself after all, and not the 
result of incorrect memory handling in the framebuffer code.
Could you take over the bug report #10843 in bugzilla (it is currently 
assigned to the framebuffer people) and ensure it gets closed once the 
patch gets accepted in Linus' tree?

I'm glad you were able to get this sorted out.

Feel free to add my:
Tested-by: Frans Pop <elendil@planet.nl>

Thanks,
FJP


[-- Attachment #2: pat_memtype_list --]
[-- Type: text/plain, Size: 1227 bytes --]

PAT memtype list:
uncached-minus @ 0x7f6e2000-0x7f6e3000
uncached-minus @ 0x7f6e4000-0x7f6e5000
uncached-minus @ 0x7f6f6000-0x7f6f7000
uncached-minus @ 0x7f6f6000-0x7f6f7000
uncached-minus @ 0x7f6f6000-0x7f6f7000
uncached-minus @ 0x7f6f6000-0x7f6f7000
uncached-minus @ 0x7f6f7000-0x7f6fc000
uncached-minus @ 0x7f6fc000-0x7f6fd000
uncached-minus @ 0x7f6fc000-0x7f6fd000
uncached-minus @ 0x7f6fc000-0x7f6fd000
uncached-minus @ 0x7f6fd000-0x7f6fe000
uncached-minus @ 0x7f6fd000-0x7f6fe000
uncached-minus @ 0x7f6fd000-0x7f6fe000
uncached-minus @ 0x7f6fd000-0x7f6fe000
uncached-minus @ 0x7f6fd000-0x7f6fe000
uncached-minus @ 0x80000000-0x90000000
uncached-minus @ 0x80000000-0x80020000
uncached-minus @ 0x80000000-0x80300000
uncached-minus @ 0x90100000-0x90120000
uncached-minus @ 0x90200000-0x90280000
uncached-minus @ 0x90200000-0x90280000
uncached-minus @ 0x90200000-0x90280000
uncached-minus @ 0x90280000-0x902c0000
uncached-minus @ 0x90280000-0x902c0000
uncached-minus @ 0x902c0000-0x902c4000
uncached-minus @ 0x902c4000-0x902c5000
uncached-minus @ 0x902c4000-0x902c5000
uncached-minus @ 0xfed00000-0xfed01000
uncached-minus @ 0xfed13000-0xfed14000
uncached-minus @ 0xfed1f000-0xfed20000
uncached-minus @ 0xfed40000-0xfed41000

Re: [Bug 10843] Display artifacts on XOrg logout with PAT kernel and VESA framebuffer

[Ingo Molnar]

* Frans Pop <elendil@planet.nl> wrote:

> On Saturday 13 September 2008, Pallipadi, Venkatesh wrote:
> > >We have too many entires in PAT list due to RAM pages being marked
> > >UC by drivers. Unfortunately, there are no quick fixes that can fix
> > >this for 2.6.27. However, we are aware of the problem here and
> > >working on a more complete fix for this. We should have the patch
> > >for it soon.
> >
> > Can you try the patch here
> > http://www.ussg.iu.edu/hypermail/linux/kernel/0809.1/2074.html
> > And report back whether that resolves the issue.
> 
> Yes, that solves the issue. The display is now free of artifacts 
> again, both on logout and when I switch users in X. The 
> pat_memtype_list looks a lot more sane too (see attachment).
> 
> So it _was_ a regression caused by pat itself after all, and not the 
> result of incorrect memory handling in the framebuffer code. Could you 
> take over the bug report #10843 in bugzilla (it is currently assigned 
> to the framebuffer people) and ensure it gets closed once the patch 
> gets accepted in Linus' tree?

ok, since those patches are only supposed to improve performance, it 
would be nice to know why this fixes the display artifacts. They were a 
rather long-living bug and we'd like to avoid such bug patterns in the 
future.

or is it the timing effect? Too slow programming of the GX chip causes 
artifacts? (but i think this is not very likely)

	Ingo