Bug#502816: Processed: unarchiving 502816, reopening 502816, found 502816 in 3.1.5-1 ...

12-26-2011, 08:00 AM

Alexander GQ Gerasiov wrote:

> unarchive 502816
> reopen 502816
> found 502816 3.1.5-1
> found 502816 3.2~rc4-1~experimental.1

Do you use a Thinkpad T61, too?

Thanks for writing,
Jonathan

--
To UNSUBSCRIBE, email to debian-kernel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 20111226090031.GA9525@elie.Belkin">http://lists.debian.org/20111226090031.GA9525@elie.Belkin

12-27-2011, 10:32 AM

Mon, 26 Dec 2011 03:00:31 -0600
Jonathan Nieder <jrnieder@gmail.com> wrote:

> Alexander GQ Gerasiov wrote:
>
> > unarchive 502816
> > reopen 502816
> > found 502816 3.1.5-1
> > found 502816 3.2~rc4-1~experimental.1
>
> Do you use a Thinkpad T61, too?
Nope, that was ASUS P1015B.
But I don't think it depends on hardware. That's amd64 kernel + i386
userspace

--
Best regards,
Alexander GQ Gerasiov

Contacts:
e-mail: gq@cs.msu.su Jabber: gq@jabber.ru
Homepage: http://gq.net.ru ICQ: 7272757
PGP fingerprint: 04B5 9D90 DF7C C2AB CD49 BAEA CA87 E9E8 2AAC 33F1

--
To UNSUBSCRIBE, email to debian-kernel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 20111227153233.37d7bcd4@desktopvm.lvknet">http://lists.debian.org/20111227153233.37d7bcd4@desktopvm.lvknet

12-27-2011, 03:50 PM

Alexander GQ Gerasiov wrote:

> Nope, that was ASUS P1015B.

Thanks. Please file a separate report, then. Be sure to mention
what steps you use to reproduce the problem, what the resulting
symptoms are like, and how they differ from what you expected.

> But I don't think it depends on hardware.

If the symptoms in the two reports end up having the same cause, we
can merge them.

Thanks again and sorry for the fuss,
Jonathan

--
To UNSUBSCRIBE, email to debian-kernel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 20111227165003.GA12333@elie.Belkin">http://lists.debian.org/20111227165003.GA12333@elie.Belkin

12-27-2011, 05:35 PM

Tue, 27 Dec 2011 10:50:34 -0600
Jonathan Nieder <jrnieder@gmail.com> wrote:

> Alexander GQ Gerasiov wrote:
>
> > Nope, that was ASUS P1015B.
>
> Thanks. Please file a separate report, then. Be sure to mention
> what steps you use to reproduce the problem, what the resulting
> symptoms are like, and how they differ from what you expected.
>
> > But I don't think it depends on hardware.
>
> If the symptoms in the two reports end up having the same cause, we
> can merge them.
>
> Thanks again and sorry for the fuss,
> Jonathan
Well, the problem is the same as in this report:
s2disk from i386 userspace tries to do ioctl32 in amd64 kernel and fails.

It can be reproduced on any i386 installation with -amd64 flavor.

--
Best regards,
Alexander GQ Gerasiov

Contacts:
e-mail: gq@cs.msu.su Jabber: gq@jabber.ru
Homepage: http://gq.net.ru ICQ: 7272757
PGP fingerprint: 04B5 9D90 DF7C C2AB CD49 BAEA CA87 E9E8 2AAC 33F1

--
To UNSUBSCRIBE, email to debian-kernel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 20111227223544.60e6ef9f@desktopvm.lvknet">http://lists.debian.org/20111227223544.60e6ef9f@desktopvm.lvknet

12-27-2011, 05:53 PM

retitle 502816 [amd64 with i386 userspace] snapshot ioctls lack compat support (s2disk tries to do ioctl32 and fails)
found 502816 linux-2.6/2.6.26-9
quit

Alexander GQ Gerasiov wrote:

> Well, the problem is the same as in this report:
> s2disk from i386 userspace tries to do ioctl32 in amd64 kernel and fails.

Ah, good call. Sorry for my lack of comprehension.

--
To UNSUBSCRIBE, email to debian-kernel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 20111227185347.GB12849@elie.Belkin">http://lists.debian.org/20111227185347.GB12849@elie.Belkin