kernel: vga16fb is broken (at least on vmware)

[Debian Bug Importer]

Automatically imported from Debian bug report #251861
http://bugs.debian.org/251861

[Kenshi Muto (kmuto)]

# Automatically generated email from bts, devscripts version 2.7.95.1
reassign 251861 kernel-source-2.6.6

[Kenshi Muto (kmuto)]

Hi,

I tried on another machine, and found same problem happened.
I believe vga16fb is corrupted.

Here is revert patch.
It works good on my test environment.

--- kernel-source-2.6.6/drivers/video/vga16fb.c 2004-05-10 18:48:01.000000000 +0900
+++ kernel-source-2.6.5/drivers/video/vga16fb.c 2004-02-19 17:55:41.000000000 +0900
@@ -1347,7 +1347,7 @@

        /* XXX share VGA_FB_PHYS and I/O region with vgacon and others */

- vga16fb.screen_base = ioremap(VGA_MAP_MEM(VGA_FB_PHYS), VGA_FB_PHYS_LEN);
+ vga16fb.screen_base = ioremap(VGA_FB_PHYS, VGA_FB_PHYS_LEN);
        if (!vga16fb.screen_base) {
                printk(KERN_ERR "vga16fb: unable to map device\n");
                ret = -ENOMEM;
@@ -1372,8 +1372,6 @@
        vga16fb.par = &vga16_par;
        vga16fb.flags = FBINFO_FLAG_DEFAULT;

- vga16fb.fix.smem_start = VGA_MAP_MEM(vga16fb.fix.smem_start);
-
        i = (vga16fb_defined.bits_per_pixel == 8) ? 256 : 16;
        ret = fb_alloc_cmap(&vga16fb.cmap, i, 0);
        if (ret) {

[Herbert Xu (herbert-gondor)]

On Tue, Jun 01, 2004 at 01:00:52AM +0900, Kenshi Muto wrote:
>
> I tried on another machine, and found same problem happened.
> I believe vga16fb is corrupted.
>
> Here is revert patch.
> It works good on my test environment.

Thanks. This is already fixed in BK by the following patch.
--
Visit Openswan at http://www.openswan.org/
Email: Herbert Xu ~{PmV>HI~} <email address hidden>
Home Page: http://gondor.apana.org.au/~herbert/
PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt

[Kenshi Muto (kmuto)]

Hi Herbert,

> > I tried on another machine, and found same problem happened.
> > I believe vga16fb is corrupted.
> >
> > Here is revert patch.
> > It works good on my test environment.

> Thanks. This is already fixed in BK by the following patch.

Ah..., I've already tried this patch. Unfortunately, this patch
doesn't solve a problem at least on my test environment. Herbert, did
you succeed by BK patch?

On my observation, problem is not from patched point, but is from:
--------------------
vga16fb.fix.smem_start = VGA_MAP_MEM(vga16fb.fix.smem_start);
--------------------

When I remove this from code, vga16fb works. I heard this line is for
ARM architecture...

GOTO Masanori and I are trying to find a problem, and Masanori knows more
about such kernel problem than me. Can you describe more details, Masanori?

Thanks,
--
Kenshi Muto
<email address hidden>

[Herbert Xu (herbert-gondor)]

On Mon, Jun 07, 2004 at 06:37:22PM +0900, Kenshi Muto wrote:
>
> Ah..., I've already tried this patch. Unfortunately, this patch
> doesn't solve a problem at least on my test environment. Herbert, did
> you succeed by BK patch?

Yes my vmware setup is broken before the patch and it works afterwards.

> On my observation, problem is not from patched point, but is from:
> --------------------
> vga16fb.fix.smem_start = VGA_MAP_MEM(vga16fb.fix.smem_start);
> --------------------
>
> When I remove this from code, vga16fb works. I heard this line is for
> ARM architecture...

Hmm, I can't see how this can make a difference. VGA_MAP_MEM should
be a noop for the values in question. Can you please do a printk
before/after that line to see if that's not the case?
--
Visit Openswan at http://www.openswan.org/
Email: Herbert Xu ~{PmV>HI~} <email address hidden>
Home Page: http://gondor.apana.org.au/~herbert/
PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt

[Kenshi Muto (kmuto)]

Hi Herbert,

At Mon, 7 Jun 2004 20:11:13 +1000,
Herbert Xu wrote:
> > Ah..., I've already tried this patch. Unfortunately, this patch
> > doesn't solve a problem at least on my test environment. Herbert, did
> > you succeed by BK patch?
>
> Yes my vmware setup is broken before the patch and it works afterwards.

Ah, sorry I forgot some explainations.

- BK patch fixes screen lock up when I load fbcon.
- But, when I launch framebuffer application (such as console),
  screen still locks up.

Could you install jfbterm and unifont package, and try to run
'jfbterm -q other,EUC-JP,iconv,UTF-8'?

> > On my observation, problem is not from patched point, but is from:
> > --------------------
> > vga16fb.fix.smem_start = VGA_MAP_MEM(vga16fb.fix.smem_start);
> > --------------------
> >
> > When I remove this from code, vga16fb works. I heard this line is for
> > ARM architecture...
>
> Hmm, I can't see how this can make a difference. VGA_MAP_MEM should
> be a noop for the values in question. Can you please do a printk
> before/after that line to see if that's not the case?

I tried to add printk in vga16fb.c l.1375.

+ printk(KERN_INFO "vga16fb: DEBUG: smem_start %lx\n", vga16fb.fix.smem_start);
          vga16fb.fix.smem_start = VGA_MAP_MEM(vga16fb.fix.smem_start);
+ printk(KERN_INFO "vga16fb: DEBUG: smem_start %lx\n", vga16fb.fix.smem_start);

Result:

vga16fb: initializing
vga16fb: mapped to 0xc00a0000
vga16fb: DEBUG: smem_start a0000
vga16fb: DEBUG: smem_start c00a0000
fb0: VGA16 VGA frame buffer device
Console: switching to colour frame buffer device 80x30

Thanks,
--
Kenshi Muto
<email address hidden>

[Herbert Xu (herbert-gondor)]

On Tue, Jun 08, 2004 at 05:14:15AM +0900, Kenshi Muto wrote:
>
> I tried to add printk in vga16fb.c l.1375.
>
> + printk(KERN_INFO "vga16fb: DEBUG: smem_start %lx\n", vga16fb.fix.smem_start);
> vga16fb.fix.smem_start = VGA_MAP_MEM(vga16fb.fix.smem_start);
> + printk(KERN_INFO "vga16fb: DEBUG: smem_start %lx\n", vga16fb.fix.smem_start);
>
> Result:
>
> vga16fb: initializing
> vga16fb: mapped to 0xc00a0000
> vga16fb: DEBUG: smem_start a0000
> vga16fb: DEBUG: smem_start c00a0000
> fb0: VGA16 VGA frame buffer device
> Console: switching to colour frame buffer device 80x30

Yes that's completely bogus. I've asked Andrew Morton to remove this
change.

Debian should definitely revert this in the next release.

Cheers,
--
Visit Openswan at http://www.openswan.org/
Email: Herbert Xu ~{PmV>HI~} <email address hidden>
Home Page: http://gondor.apana.org.au/~herbert/
PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt

[Joey Hess (joeyh)]

# Automatically generated email from bts, devscripts version 2.7.95.1
reassign 251902 kernel-source-2.6.6
merge 251902 251861

[Joey Hess (joeyh)]

# Automatically generated email from bts, devscripts version 2.7.95.1
tags 251861 d-i

[Joey Hess (joeyh)]

# Automatically generated email from bts, devscripts version 2.7.95.1
severity 251861 serious

[Joey Hess (joeyh)]

severity 251861 grave
thanks

This bug is release crticial: it makes it impossible to install debian
with the 2.6 kernel.

We have a patch for the bug, but I don't know if Herbert will be
avilable to release it. Didn't he quit? So can someone step up and get a
fixed package into the archive?

An alternative fix would be to remove kernel-image-2.6.6-1-386 (et al)
from testing. The 2.6.5 version is still available in testing, and
works. Since this bug *is* RC, that would be an appropriate response,
IMHO.

(I see a slightly different bug with this kernel and my test laptop.
When the frame buffer is turned on just before base-config starts, the
laptop simply turns off. I suspect it's the same bug, different failure
mode.)

--
see shy jo

[Steve Langasek (vorlon)]

On Fri, Jun 11, 2004 at 03:46:29PM -0400, Joey Hess wrote:
> severity 251861 grave
> thanks

> This bug is release crticial: it makes it impossible to install debian
> with the 2.6 kernel.

> We have a patch for the bug, but I don't know if Herbert will be
> avilable to release it. Didn't he quit? So can someone step up and get a
> fixed package into the archive?

> An alternative fix would be to remove kernel-image-2.6.6-1-386 (et al)
> from testing. The 2.6.5 version is still available in testing, and
> works. Since this bug *is* RC, that would be an appropriate response,
> IMHO.

==> remove kernel-image-2.6.6-i386/2.6.6-1

Easily done. The above hint should take effect with tomorrow's britney
run, with the effect that the 2.6.6 kernel-image packages for i386 will
be removed from sarge at dinstall on the 14th, and will be held out
pending resolution of this RC bug.

Are there any RC issues with the 2.6.5 kernels that warrant keeping a
close watch on this issue going forward? Are there other architectures
that would be affected by this bug?

Thanks,
--
Steve Langasek
postmodern programmer

[William Lee Irwin III (wli)]

This has been fixed upstream. I recommend removing 2.6.6 from the
archive, as this fix and a number of others have been incorporated
upstream for 2.6.7.

-- wli

[Joey Hess (joeyh)]

Steve Langasek wrote:
> ==> remove kernel-image-2.6.6-i386/2.6.6-1
>
> Easily done. The above hint should take effect with tomorrow's britney
> run, with the effect that the 2.6.6 kernel-image packages for i386 will
> be removed from sarge at dinstall on the 14th, and will be held out
> pending resolution of this RC bug.

Ok, we'll have to rebuild the netinst CDs to take advantage of it.
I'm leaning toward calling that tc2 and fixing the sparc64 issue at the
same time.

> Are there any RC issues with the 2.6.5 kernels that warrant keeping a
> close watch on this issue going forward? Are there other architectures
> that would be affected by this bug?

2.6.5 seemed good when d-i was using it. Unlike 2.6.3, it doesn't crash
on boot after the initial install. Of course it probably has lots of
problems, and 2.6.6 probably fixes lots of problems, adds better SATA
support etc. You just can't win. Unless someone applies the patch to
2.6.6, that is..

--
see shy jo

[William Lee Irwin III (wli)]

This is fixed in 2.6.7-final and various other fixes from the Debian
sources are also included there.

I'm preparing a 2.6.7-final -based package to address this.

-- wli

[Kenshi Muto (kmuto)]

Hi,

At Sat, 19 Jun 2004 15:01:38 -0700,
William Lee Irwin III wrote:
> This is fixed in 2.6.7-final and various other fixes from the Debian
> sources are also included there.
>
> I'm preparing a 2.6.7-final -based package to address this.

I see, thank you!
We, Debian Installer team, hope that you upload 2.6.7 in the near
future :-)

Thanks,
--
Kenshi Muto
<email address hidden>

[Debian Bug Importer (debzilla)]

Automatically imported from Debian bug report #251861
http://bugs.debian.org/251861

[Debian Bug Importer (debzilla)]

Message-Id: <20040531121030.6CF5521410D@hellhound>
Date: Mon, 31 May 2004 21:10:30 +0900 (JST)
From: Kenshi Muto <email address hidden>
To: Debian Bug Tracking System <email address hidden>
Cc: <email address hidden>, <email address hidden>
Subject: kernel: vga16fb is broken (at least on vmware)

Package: kernel-source-2.6.6-1
Severity: important

Hi,
I have a problem with kernel 2.6.6 about vga16fb.
When I (or debian-installer 2nd stage) load vga16fb and fbcon, screen
goes corrupted after loading fbcon on at least VMware.

debian-installer (using kernel 2.6.5) hasn't this problem.

Well, this is critical problem for debian-installer 2nd stage when
user (some languages) choices linux 2.6.6 as install kernel at 1st
stage.

Thanks,
--
Kenshi Muto
<email address hidden>

[Debian Bug Importer (debzilla)]

Message-Id: <20040531125422.4EDAB21410D@hellhound>
Date: Mon, 31 May 2004 21:54:22 +0900
From: Kenshi Muto <email address hidden>
To: <email address hidden>
Subject: reassign 251861 to kernel-source-2.6.6

# Automatically generated email from bts, devscripts version 2.7.95.1
reassign 251861 kernel-source-2.6.6

[Debian Bug Importer (debzilla)]

Message-Id: <email address hidden>
Date: Tue, 01 Jun 2004 01:00:52 +0900
From: Kenshi Muto <email address hidden>
To: <email address hidden>
Subject: kernel: vga16fb is broken (at least on vmware)

Hi,

I tried on another machine, and found same problem happened.
I believe vga16fb is corrupted.

Here is revert patch.
It works good on my test environment.

--- kernel-source-2.6.6/drivers/video/vga16fb.c 2004-05-10 18:48:01.000000000 +0900
+++ kernel-source-2.6.5/drivers/video/vga16fb.c 2004-02-19 17:55:41.000000000 +0900
@@ -1347,7 +1347,7 @@

        /* XXX share VGA_FB_PHYS and I/O region with vgacon and others */

- vga16fb.screen_base = ioremap(VGA_MAP_MEM(VGA_FB_PHYS), VGA_FB_PHYS_LEN);
+ vga16fb.screen_base = ioremap(VGA_FB_PHYS, VGA_FB_PHYS_LEN);
        if (!vga16fb.screen_base) {
                printk(KERN_ERR "vga16fb: unable to map device\n");
                ret = -ENOMEM;
@@ -1372,8 +1372,6 @@
        vga16fb.par = &vga16_par;
        vga16fb.flags = FBINFO_FLAG_DEFAULT;

- vga16fb.fix.smem_start = VGA_MAP_MEM(vga16fb.fix.smem_start);
-
        i = (vga16fb_defined.bits_per_pixel == 8) ? 256 : 16;
        ret = fb_alloc_cmap(&vga16fb.cmap, i, 0);
        if (ret) {

[Debian Bug Importer (debzilla)]

Message-ID: <email address hidden>
Date: Tue, 1 Jun 2004 20:17:16 +1000
From: Herbert Xu <email address hidden>
To: Kenshi Muto <email address hidden>, <email address hidden>
Subject: Re: Bug#251861: kernel: vga16fb is broken (at least on vmware)

--ikeVEW9yuYc//A+q
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline

On Tue, Jun 01, 2004 at 01:00:52AM +0900, Kenshi Muto wrote:
>
> I tried on another machine, and found same problem happened.
> I believe vga16fb is corrupted.
>
> Here is revert patch.
> It works good on my test environment.

Thanks. This is already fixed in BK by the following patch.
--
Visit Openswan at http://www.openswan.org/
Email: Herbert Xu ~{PmV>HI~} <email address hidden>
Home Page: http://gondor.apana.org.au/~herbert/
PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt

--ikeVEW9yuYc//A+q
Content-Type: text/plain; charset=us-ascii
Content-Disposition: attachment; filename=p

===== drivers/video/vga16fb.c 1.36 vs 1.38 =====
--- 1.36/drivers/video/vga16fb.c 2004-04-14 01:46:49 +10:00
+++ 1.38/drivers/video/vga16fb.c 2004-05-22 18:18:20 +10:00
@@ -1347,7 +1347,7 @@

  /* XXX share VGA_FB_PHYS and I/O region with vgacon and others */

- vga16fb.screen_base = ioremap(VGA_MAP_MEM(VGA_FB_PHYS), VGA_FB_PHYS_LEN);
+ vga16fb.screen_base = (void *)VGA_MAP_MEM(VGA_FB_PHYS);
  if (!vga16fb.screen_base) {
   printk(KERN_ERR "vga16fb: unable to map device\n");
   ret = -ENOMEM;

--ikeVEW9yuYc//A+q--

[Debian Bug Importer (debzilla)]

Message-Id: <email address hidden>
Date: Mon, 07 Jun 2004 18:37:22 +0900
From: Kenshi Muto <email address hidden>
To: <email address hidden>
Cc: <email address hidden>
Subject: Re: Bug#251861: kernel: vga16fb is broken (at least on vmware)

Hi Herbert,

> > I tried on another machine, and found same problem happened.
> > I believe vga16fb is corrupted.
> >
> > Here is revert patch.
> > It works good on my test environment.

> Thanks. This is already fixed in BK by the following patch.

Ah..., I've already tried this patch. Unfortunately, this patch
doesn't solve a problem at least on my test environment. Herbert, did
you succeed by BK patch?

On my observation, problem is not from patched point, but is from:
--------------------
vga16fb.fix.smem_start = VGA_MAP_MEM(vga16fb.fix.smem_start);
--------------------

When I remove this from code, vga16fb works. I heard this line is for
ARM architecture...

GOTO Masanori and I are trying to find a problem, and Masanori knows more
about such kernel problem than me. Can you describe more details, Masanori?

Thanks,
--
Kenshi Muto
<email address hidden>

[Debian Bug Importer (debzilla)]

Message-ID: <email address hidden>
Date: Mon, 7 Jun 2004 20:11:13 +1000
From: Herbert Xu <email address hidden>
To: Kenshi Muto <email address hidden>, <email address hidden>
Cc: <email address hidden>
Subject: Re: Bug#251861: kernel: vga16fb is broken (at least on vmware)

On Mon, Jun 07, 2004 at 06:37:22PM +0900, Kenshi Muto wrote:
>
> Ah..., I've already tried this patch. Unfortunately, this patch
> doesn't solve a problem at least on my test environment. Herbert, did
> you succeed by BK patch?

Yes my vmware setup is broken before the patch and it works afterwards.

> On my observation, problem is not from patched point, but is from:
> --------------------
> vga16fb.fix.smem_start = VGA_MAP_MEM(vga16fb.fix.smem_start);
> --------------------
>
> When I remove this from code, vga16fb works. I heard this line is for
> ARM architecture...

Hmm, I can't see how this can make a difference. VGA_MAP_MEM should
be a noop for the values in question. Can you please do a printk
before/after that line to see if that's not the case?
--
Visit Openswan at http://www.openswan.org/
Email: Herbert Xu ~{PmV>HI~} <email address hidden>
Home Page: http://gondor.apana.org.au/~herbert/
PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt

[Debian Bug Importer (debzilla)]

Message-Id: <email address hidden>
Date: Tue, 08 Jun 2004 05:14:15 +0900
From: Kenshi Muto <email address hidden>
To: Herbert Xu <email address hidden>
Cc: <email address hidden>, <email address hidden>
Subject: Re: Bug#251861: kernel: vga16fb is broken (at least on vmware)

Hi Herbert,

At Mon, 7 Jun 2004 20:11:13 +1000,
Herbert Xu wrote:
> > Ah..., I've already tried this patch. Unfortunately, this patch
> > doesn't solve a problem at least on my test environment. Herbert, did
> > you succeed by BK patch?
>
> Yes my vmware setup is broken before the patch and it works afterwards.

Ah, sorry I forgot some explainations.

- BK patch fixes screen lock up when I load fbcon.
- But, when I launch framebuffer application (such as console),
  screen still locks up.

Could you install jfbterm and unifont package, and try to run
'jfbterm -q other,EUC-JP,iconv,UTF-8'?

> > On my observation, problem is not from patched point, but is from:
> > --------------------
> > vga16fb.fix.smem_start = VGA_MAP_MEM(vga16fb.fix.smem_start);
> > --------------------
> >
> > When I remove this from code, vga16fb works. I heard this line is for
> > ARM architecture...
>
> Hmm, I can't see how this can make a difference. VGA_MAP_MEM should
> be a noop for the values in question. Can you please do a printk
> before/after that line to see if that's not the case?

I tried to add printk in vga16fb.c l.1375.

+ printk(KERN_INFO "vga16fb: DEBUG: smem_start %lx\n", vga16fb.fix.smem_start);
          vga16fb.fix.smem_start = VGA_MAP_MEM(vga16fb.fix.smem_start);
+ printk(KERN_INFO "vga16fb: DEBUG: smem_start %lx\n", vga16fb.fix.smem_start);

Result:

vga16fb: initializing
vga16fb: mapped to 0xc00a0000
vga16fb: DEBUG: smem_start a0000
vga16fb: DEBUG: smem_start c00a0000
fb0: VGA16 VGA frame buffer device
Console: switching to colour frame buffer device 80x30

Thanks,
--
Kenshi Muto
<email address hidden>

[Debian Bug Importer (debzilla)]

Message-ID: <email address hidden>
Date: Tue, 8 Jun 2004 20:06:23 +1000
From: Herbert Xu <email address hidden>
To: Kenshi Muto <email address hidden>, <email address hidden>
Cc: <email address hidden>
Subject: Re: Bug#251861: kernel: vga16fb is broken (at least on vmware)

On Tue, Jun 08, 2004 at 05:14:15AM +0900, Kenshi Muto wrote:
>
> I tried to add printk in vga16fb.c l.1375.
>
> + printk(KERN_INFO "vga16fb: DEBUG: smem_start %lx\n", vga16fb.fix.smem_start);
> vga16fb.fix.smem_start = VGA_MAP_MEM(vga16fb.fix.smem_start);
> + printk(KERN_INFO "vga16fb: DEBUG: smem_start %lx\n", vga16fb.fix.smem_start);
>
> Result:
>
> vga16fb: initializing
> vga16fb: mapped to 0xc00a0000
> vga16fb: DEBUG: smem_start a0000
> vga16fb: DEBUG: smem_start c00a0000
> fb0: VGA16 VGA frame buffer device
> Console: switching to colour frame buffer device 80x30

Yes that's completely bogus. I've asked Andrew Morton to remove this
change.

Debian should definitely revert this in the next release.

Cheers,
--
Visit Openswan at http://www.openswan.org/
Email: Herbert Xu ~{PmV>HI~} <email address hidden>
Home Page: http://gondor.apana.org.au/~herbert/
PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt

[Debian Bug Importer (debzilla)]

Message-Id: <email address hidden>
Date: Fri, 11 Jun 2004 15:38:54 -0400
From: Joey Hess <email address hidden>
To: <email address hidden>
Subject: reassign 251902 to kernel-source-2.6.6, merging 251902 251861

# Automatically generated email from bts, devscripts version 2.7.95.1
reassign 251902 kernel-source-2.6.6
merge 251902 251861

[Debian Bug Importer (debzilla)]

Message-Id: <email address hidden>
Date: Fri, 11 Jun 2004 15:39:30 -0400
From: Joey Hess <email address hidden>
To: <email address hidden>
Subject: tagging 251861

# Automatically generated email from bts, devscripts version 2.7.95.1
tags 251861 d-i

[Debian Bug Importer (debzilla)]

Message-Id: <email address hidden>
Date: Fri, 11 Jun 2004 15:40:28 -0400
From: Joey Hess <email address hidden>
To: <email address hidden>
Subject: severity of 251861 is serious

# Automatically generated email from bts, devscripts version 2.7.95.1
severity 251861 serious

[Debian Bug Importer (debzilla)]

Message-ID: <email address hidden>
Date: Fri, 11 Jun 2004 15:46:29 -0400
From: Joey Hess <email address hidden>
To: <email address hidden>, <email address hidden>,
 <email address hidden>, <email address hidden>
Subject: this bug is RC

--X1bOJ3K7DJ5YkBrT
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

severity 251861 grave
thanks

This bug is release crticial: it makes it impossible to install debian
with the 2.6 kernel.

We have a patch for the bug, but I don't know if Herbert will be
avilable to release it. Didn't he quit? So can someone step up and get a
fixed package into the archive?

An alternative fix would be to remove kernel-image-2.6.6-1-386 (et al)
=66rom testing. The 2.6.5 version is still available in testing, and
works. Since this bug *is* RC, that would be an appropriate response,
IMHO.

(I see a slightly different bug with this kernel and my test laptop.
When the frame buffer is turned on just before base-config starts, the
laptop simply turns off. I suspect it's the same bug, different failure
mode.)

--=20
see shy jo

--X1bOJ3K7DJ5YkBrT
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Digital signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)

iD8DBQFAygwVd8HHehbQuO8RAuwfAJ4jklLcgQDUeH4p8jCaXmDFtYnRgwCdHveL
PxBmzWLhiiHk6hey54CwxaU=
=R8Uz
-----END PGP SIGNATURE-----

--X1bOJ3K7DJ5YkBrT--

[Debian Bug Importer (debzilla)]

Message-ID: <email address hidden>
Date: Sat, 12 Jun 2004 00:11:46 -0500
From: Steve Langasek <email address hidden>
To: <email address hidden>, <email address hidden>,
 <email address hidden>
Subject: Re: this bug is RC

--H+4ONPRPur6+Ovig
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Fri, Jun 11, 2004 at 03:46:29PM -0400, Joey Hess wrote:
> severity 251861 grave
> thanks

> This bug is release crticial: it makes it impossible to install debian
> with the 2.6 kernel.

> We have a patch for the bug, but I don't know if Herbert will be
> avilable to release it. Didn't he quit? So can someone step up and get a
> fixed package into the archive?

> An alternative fix would be to remove kernel-image-2.6.6-1-386 (et al)
> from testing. The 2.6.5 version is still available in testing, and
> works. Since this bug *is* RC, that would be an appropriate response,
> IMHO.

=3D=3D> remove kernel-image-2.6.6-i386/2.6.6-1

Easily done. The above hint should take effect with tomorrow's britney
run, with the effect that the 2.6.6 kernel-image packages for i386 will
be removed from sarge at dinstall on the 14th, and will be held out
pending resolution of this RC bug.

Are there any RC issues with the 2.6.5 kernels that warrant keeping a
close watch on this issue going forward? Are there other architectures
that would be affected by this bug?

Thanks,
--=20
Steve Langasek
postmodern programmer

--H+4ONPRPur6+Ovig
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Digital signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (GNU/Linux)

iD8DBQFAypCRKN6ufymYLloRAookAKCjmeSHS8rf6d1J3QXHq6gab0LPMACgtB/S
B9bLvC0WglcQlto4WMLhxv0=
=EZip
-----END PGP SIGNATURE-----

--H+4ONPRPur6+Ovig--

[Debian Bug Importer (debzilla)]

Message-ID: <email address hidden>
Date: Sat, 12 Jun 2004 00:25:03 -0700
From: William Lee Irwin III <email address hidden>
To: Martin Michlmayr <email address hidden>
Cc: <email address hidden>
Subject: Re: [<email address hidden>: this bug is RC]

This has been fixed upstream. I recommend removing 2.6.6 from the
archive, as this fix and a number of others have been incorporated
upstream for 2.6.7.

-- wli

[Debian Bug Importer (debzilla)]

Message-ID: <email address hidden>
Date: Sat, 12 Jun 2004 12:53:23 -0400
From: Joey Hess <email address hidden>
To: <email address hidden>, <email address hidden>,
 <email address hidden>
Subject: Re: this bug is RC

--7cm2iqirTL37Ot+N
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

Steve Langasek wrote:
> =3D=3D> remove kernel-image-2.6.6-i386/2.6.6-1
>=20
> Easily done. The above hint should take effect with tomorrow's britney
> run, with the effect that the 2.6.6 kernel-image packages for i386 will
> be removed from sarge at dinstall on the 14th, and will be held out
> pending resolution of this RC bug.

Ok, we'll have to rebuild the netinst CDs to take advantage of it.
I'm leaning toward calling that tc2 and fixing the sparc64 issue at the
same time.

> Are there any RC issues with the 2.6.5 kernels that warrant keeping a
> close watch on this issue going forward? Are there other architectures
> that would be affected by this bug?

2.6.5 seemed good when d-i was using it. Unlike 2.6.3, it doesn't crash
on boot after the initial install. Of course it probably has lots of
problems, and 2.6.6 probably fixes lots of problems, adds better SATA
support etc. You just can't win. Unless someone applies the patch to
2.6.6, that is..

--=20
see shy jo

--7cm2iqirTL37Ot+N
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Digital signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)

iD8DBQFAyzUDd8HHehbQuO8RAtOeAKDFvJSgxmV1tQ1Je2EQbxBNJxFYewCePczz
t1d897/k1/j2BWP55ChDou0=
=mr5U
-----END PGP SIGNATURE-----

--7cm2iqirTL37Ot+N--

[Debian Bug Importer (debzilla)]

Message-ID: <email address hidden>
Date: Sat, 19 Jun 2004 15:01:38 -0700
From: William Lee Irwin III <email address hidden>
To: <email address hidden>
Subject: fixed in 2.6.7-final

This is fixed in 2.6.7-final and various other fixes from the Debian
sources are also included there.

I'm preparing a 2.6.7-final -based package to address this.

-- wli

[Debian Bug Importer (debzilla)]

Message-Id: <email address hidden>
Date: Sun, 20 Jun 2004 09:18:20 +0900
From: Kenshi Muto <email address hidden>
To: <email address hidden>, <email address hidden>
Subject: Re: Bug#251861: fixed in 2.6.7-final

Hi,

At Sat, 19 Jun 2004 15:01:38 -0700,
William Lee Irwin III wrote:
> This is fixed in 2.6.7-final and various other fixes from the Debian
> sources are also included there.
>
> I'm preparing a 2.6.7-final -based package to address this.

I see, thank you!
We, Debian Installer team, hope that you upload 2.6.7 in the near
future :-)

Thanks,
--
Kenshi Muto
<email address hidden>

[Matt Zimmerman (mdz)]

*** Bug 6813 has been marked as a duplicate of this bug. ***

[Matt Zimmerman (mdz)]

Remove myself from all these CCs now that we have the warty-bugs mailing list

[Matt Zimmerman (mdz)]

This bug can be closed when we import kernel 2.6.7+ from Debian

[Matt Zimmerman (mdz)]

d-i now uses 2.6.7 in Warty

[Joey Hess (joeyh)]

I'm closing this bug since it's fixed in 2.6.7 which d-i now uses, and
anyway, kernel-image-2.6.6-1-386 is no longer in the archive.

--
see shy jo

[Debian Bug Importer (debzilla)]

Message-ID: <email address hidden>
Date: Fri, 6 Aug 2004 22:47:55 -0300
From: Joey Hess <email address hidden>
To: <email address hidden>
Subject: closing

--RnlQjJ0d97Da+TV1
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

I'm closing this bug since it's fixed in 2.6.7 which d-i now uses, and
anyway, kernel-image-2.6.6-1-386 is no longer in the archive.

--=20
see shy jo

--RnlQjJ0d97Da+TV1
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Digital signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.5 (GNU/Linux)

iD8DBQFBFDTKd8HHehbQuO8RAgtOAKDc1re1zeY+Q8dMBxg/rAadLp9h5gCgz3jw
ICfd2vDoMlesLDqTwNyOI/M=
=QxTa
-----END PGP SIGNATURE-----

--RnlQjJ0d97Da+TV1--