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

» Linux Archive

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


» Sponsor

» Partners

» Sponsor

Go Back   Linux Archive > Debian > Debian User

 
 
LinkBack Thread Tools
 
Old 07-17-2008, 01:39 PM
Ron Johnson
 
Default Help filing bug report; can't use automated tool, does this report look OK?

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 07/17/08 07:57, Arthur A wrote:
[snip]

Why can't you use reportbug?

- --
Ron Johnson, Jr.
Jefferson LA USA

"Kittens give Morbo gas. In lighter news, the city of New New
York is doomed."
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)

iEYEARECAAYFAkh/S5sACgkQS9HxQb37XmfBAwCfbDalms5CmshRKoKuJj2qlEdE
sSoAoNSnFcDxaulLSdr7MZXRT7QVFnpB
=JDgc
-----END PGP SIGNATURE-----


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
 
Old 07-17-2008, 01:53 PM
"Eugene V. Lyubimkin"
 
Default Help filing bug report; can't use automated tool, does this report look OK?

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Ron Johnson wrote:
> On 07/17/08 07:57, Arthur A wrote:
> [snip]
>
> Why can't you use reportbug?
>
May be, he is behind proxy?
- --
Eugene V. Lyubimkin aka JackYF
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEARECAAYFAkh/TscACgkQchorMMFUmYyctQCfYwPVtuVtUlgI7w7qwjgCziu0
Y2kAoIj53ZujSn26n+j6z6ItTmbrdgCL
=9glg
-----END PGP SIGNATURE-----


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
 
Old 07-17-2008, 01:59 PM
Ron Johnson
 
Default Help filing bug report; can't use automated tool, does this report look OK?

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 07/17/08 08:53, Eugene V. Lyubimkin wrote:
> Ron Johnson wrote:
>> On 07/17/08 07:57, Arthur A wrote:
>> [snip]
>
>> Why can't you use reportbug?
>
> May be, he is behind proxy?

There are ways around that, but yes, it takes some knowledge.

- --
Ron Johnson, Jr.
Jefferson LA USA

"Kittens give Morbo gas. In lighter news, the city of New New
York is doomed."
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)

iEYEARECAAYFAkh/UDQACgkQS9HxQb37Xme36gCff6dM1WLp0OzdN0UB45MjyzHJ
bjwAoMO2JEz/nd2NrIL3JwrTfG+onk1Q
=Mhsr
-----END PGP SIGNATURE-----


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
 
Old 07-17-2008, 03:44 PM
Arthur A
 
Default Help filing bug report; can't use automated tool, does this report look OK?

Ron Johnson wrote:

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 07/17/08 07:57, Arthur A wrote:
[snip]

Why can't you use reportbug?

- --
Ron Johnson, Jr.
Jefferson LA USA

"Kittens give Morbo gas. In lighter news, the city of New New
York is doomed."
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)

iEYEARECAAYFAkh/S5sACgkQS9HxQb37XmfBAwCfbDalms5CmshRKoKuJj2qlEdE
sSoAoNSnFcDxaulLSdr7MZXRT7QVFnpB
=JDgc
-----END PGP SIGNATURE-----


Thanks, as for why, I'm not entirely sure. It gets setup ok, seems to run fine,
but it always fails at the end before even trying to send the report. I can
sometimes find a temporary file with the report, but sometimes not.


More than likely I'm doing something wrong, but rather than spend time figuring
it out I figure it would be easier to just gather the info myself.


Best,
AA


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
 
Old 07-17-2008, 03:58 PM
Ron Johnson
 
Default Help filing bug report; can't use automated tool, does this report look OK?

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 07/17/08 10:44, Arthur A wrote:
> Ron Johnson wrote:
> On 07/17/08 07:57, Arthur A wrote:
> [snip]
>
> Why can't you use reportbug?
>
>>
>>
> Thanks, as for why, I'm not entirely sure. It gets setup ok, seems to
> run fine, but it always fails at the end before even trying to send the
> report. I can sometimes find a temporary file with the report, but
> sometimes not.

Send the contents of your ~/.reportbugrc file.

For example:
$ grep -v # ~/.reportbugrc
reportbug_version "3.17"
mode standard
ui text
email "ron.l.johnson@cox.net"
smtphost "smtp.east.cox.net"


> More than likely I'm doing something wrong, but rather than spend time
> figuring it out I figure it would be easier to just gather the info myself.

That's... well, that's the Windows Way.

- --
Ron Johnson, Jr.
Jefferson LA USA

"Kittens give Morbo gas. In lighter news, the city of New New
York is doomed."
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)

iEYEARECAAYFAkh/bBsACgkQS9HxQb37Xme1MACeMGMv7nqNu0du6wLteMPjFM4G
2twAn3NTibmyGp3eCb36GTWdeT5+RPSI
=zZTv
-----END PGP SIGNATURE-----


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
 
Old 07-19-2008, 01:07 AM
"s. keeling"
 
Default Help filing bug report; can't use automated tool, does this report look OK?

Ron Johnson <ron.l.johnson@cox.net>:
> On 07/17/08 10:44, Arthur A wrote:
> > Ron Johnson wrote:
> > >
> > > Why can't you use reportbug?
> >
> > Thanks, as for why, I'm not entirely sure. It gets setup ok, seems to
> > run fine, but it always fails at the end before even trying to send the
> > report. I can sometimes find a temporary file with the report, but
> > sometimes not.
>
> Send the contents of your ~/.reportbugrc file.
>
> For example:
> $ grep -v # ~/.reportbugrc
> reportbug_version "3.17"
> mode standard
> ui text
> email "ron.l.johnson@cox.net"
> smtphost "smtp.east.cox.net"

That's so ancient!?! You're a dinosaur! :-) [inside joke].

(0) phreaque /home/keeling_ grep -v # ~/.reportbugrc
reportbug_version "3.31"
mode standard
ui text
realname "s. keeling"
email "keeling@nucleus.com"

> > More than likely I'm doing something wrong, but rather than spend time
> > figuring it out I figure it would be easier to just gather the info myself.
>
> That's... well, that's the Windows Way.

It's the (l)user way. We should always be trying to find a way for
the machine to do the heavy lifting. That way, we'll have more time
to think, and room to breath. Between all of us, we've handed him the
solution on a silver platter. It should be a matter config tweaks and
tests. I know, (l)users don't do that sort of thing, but we can hope.


--
Any technology distinguishable from magic is insufficiently advanced.
(*) http://blinkynet.net/comp/uip5.html Linux Counter #80292
- - http://www.faqs.org/rfcs/rfc1855.html Please, don't Cc: me.


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
 
Old 07-19-2008, 02:17 AM
Ron Johnson
 
Default Help filing bug report; can't use automated tool, does this report look OK?

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 07/18/08 20:07, s. keeling wrote:
> Ron Johnson <ron.l.johnson@cox.net>:
>> On 07/17/08 10:44, Arthur A wrote:
>>> Ron Johnson wrote:
>>>> Why can't you use reportbug?
>>> Thanks, as for why, I'm not entirely sure. It gets setup ok, seems to
>>> run fine, but it always fails at the end before even trying to send the
>>> report. I can sometimes find a temporary file with the report, but
>>> sometimes not.
>> Send the contents of your ~/.reportbugrc file.
>>
>> For example:
>> $ grep -v # ~/.reportbugrc
>> reportbug_version "3.17"
>> mode standard
>> ui text
>> email "ron.l.johnson@cox.net"
>> smtphost "smtp.east.cox.net"
>
> That's so ancient!?! You're a dinosaur! :-) [inside joke].

Why thank you! But that's just the version I started using rb at.

But actually, I'm rather current.

$ reportbug --version
reportbug 3.41

>
> (0) phreaque /home/keeling_ grep -v # ~/.reportbugrc
> reportbug_version "3.31"
> mode standard
> ui text
> realname "s. keeling"
> email "keeling@nucleus.com"
>
>>> More than likely I'm doing something wrong, but rather than spend time
>>> figuring it out I figure it would be easier to just gather the info myself.
>> That's... well, that's the Windows Way.
>
> It's the (l)user way. We should always be trying to find a way for
> the machine to do the heavy lifting. That way, we'll have more time
> to think, and room to breath. Between all of us, we've handed him the
> solution on a silver platter. It should be a matter config tweaks and
> tests. I know, (l)users don't do that sort of thing, but we can hope.

Be nice. Not everyone was able to cut their teeth on UNIX V6.

- --
Ron Johnson, Jr.
Jefferson LA USA

"Kittens give Morbo gas. In lighter news, the city of New New
York is doomed."
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)

iEYEARECAAYFAkiBTqgACgkQS9HxQb37XmcscgCcDjX1mG2RAZ T95r8mfOyK2a9g
B6IAoO4HAK/LOpOHo8feFpdJCbR1XzR0
=AWuv
-----END PGP SIGNATURE-----


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
 
Old 07-20-2008, 06:52 AM
Celejar
 
Default Help filing bug report; can't use automated tool, does this report look OK?

On Thu, 17 Jul 2008 15:57:52 +0300
Arthur A <arthur.machlas@gmail.com> wrote:

...

> Briefly, what happens is the 'X' randomly crashes without warning, and it is
> irrecoverable. Any open work is lost. A reboot is required. There is an error in
> the xorg.log about rng expecting one number, getting another, then fatal server
> error.
>
> Here is the bug report I want to file, you comments are appreciated.
>
> Regards,
> AA
> ================================================== ===========================
> To:submit@bugs.debian.org
> Subject: xserver-xorg-video-intel causes X to crash irrecoverably and without
> warning (fatal server error: lockup)
> Package: xserver-xorg-video-intel
> Version: 2:2.3.2-2
> Severity: important
>
> Seemingly at random, and infrequently, X will crash and I will often lose all
> open work. After a number of attempts to automatically restart I will be given a
> message saying that X has crashed and cannot be restarted. Switching to a
> different terminal killing all Xsessions and GDM and attempting to restart them
> does not work. A reboot is seemingly required.
>
> Adding the option "NoDRI" to xorg.conf appears to prevent this from happening?
> This is not a good option for me as suspend/resume does not work with this
> option enabled.
>
> It occurs infrequently, perhaps once every 30 or 40 hours of use, and I have
> been unable to find any pattern. I believe iceweasel has been open for all
> crashes, though this has occured over an upgrade to version 3.0, and has also
> persisted over recent updates to xorg and the intel driver.
>
> The xorg.log seems to contain a relevant and hopefully useful error at the end
> of the log.
>
> I set the severity to important because it currently causes a loss of data.
>
> Please advise if I can provide more information. Reportbug was not working for
> me and I have filed this manually.
>
> Below you will find my xorg.log, xorg.conf, kernel version, libc version. I am
> running Lenny.
>
> Regards,
> AA
>
> # ============================
> # cat /var/log/Xorg.0.log.old
> # ============================

...

[This is where the reports related to the bug begin.]

> Error in I830WaitLpRing(), timeout for 2 seconds
> pgetbl_ctl: 0x3ffc0001 getbl_err: 0x00000003
> ipeir: 0x00000000 iphdr: 0x7d000006
> LP ring tail: 0x0000e490 head: 0x0000e49c len: 0x0001f001 start 0x00000000
> eir: 0x0000 esr: 0x0010 emr: 0xffff
> instdone: 0xfa41 instpm: 0x0000
> memmode: 0x0000010f instps: 0x800f04c4
> hwstam: 0xfffe ier: 0x0002 imr: 0x0000 iir: 0x0070
> Ring at virtual 0xa782f000 head 0xe49c tail 0xe490 count 32765

...

> Ring end
> space: 4 wanted 32
> (II) intel(0): [drm] removed 1 reserved context for kernel
> (II) intel(0): [drm] unmapping 8192 bytes of SAREA 0xf8d41000 at 0xb7ef3000
> (II) intel(0): [drm] Closed DRM master.
>
> Fatal server error:
> lockup

...

I have reported a version of this to upstream (as per a request by one of the DDs in a similar bug log:

http://bugs.freedesktop.org/show_bug.cgi?id=16262

See also:

http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=465694
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=432110

Celejar
--
mailmin.sourceforge.net - remote access via secure (OpenPGP) email
ssuds.sourceforge.net - A Simple Sudoku Solver and Generator


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
 
Old 07-20-2008, 12:28 PM
Arthur A
 
Default Help filing bug report; can't use automated tool, does this report look OK?

Celejar wrote:

On Thu, 17 Jul 2008 15:57:52 +0300
Arthur A <arthur.machlas@gmail.com> wrote:

...

Briefly, what happens is the 'X' randomly crashes without warning, and it is
irrecoverable. Any open work is lost. A reboot is required. There is an error in
the xorg.log about rng expecting one number, getting another, then fatal server
error.


Here is the bug report I want to file, you comments are appreciated.

Regards,
AA
================================================== ===========================
To:submit@bugs.debian.org
Subject: xserver-xorg-video-intel causes X to crash irrecoverably and without
warning (fatal server error: lockup)

Package: xserver-xorg-video-intel
Version: 2:2.3.2-2
Severity: important

Seemingly at random, and infrequently, X will crash and I will often lose all
open work. After a number of attempts to automatically restart I will be given a
message saying that X has crashed and cannot be restarted. Switching to a
different terminal killing all Xsessions and GDM and attempting to restart them
does not work. A reboot is seemingly required.


Adding the option "NoDRI" to xorg.conf appears to prevent this from happening?
This is not a good option for me as suspend/resume does not work with this
option enabled.


It occurs infrequently, perhaps once every 30 or 40 hours of use, and I have
been unable to find any pattern. I believe iceweasel has been open for all
crashes, though this has occured over an upgrade to version 3.0, and has also
persisted over recent updates to xorg and the intel driver.


The xorg.log seems to contain a relevant and hopefully useful error at the end
of the log.


I set the severity to important because it currently causes a loss of data.

Please advise if I can provide more information. Reportbug was not working for
me and I have filed this manually.


Below you will find my xorg.log, xorg.conf, kernel version, libc version. I am
running Lenny.


Regards,
AA

# ============================
# cat /var/log/Xorg.0.log.old
# ============================


...

[This is where the reports related to the bug begin.]


Error in I830WaitLpRing(), timeout for 2 seconds
pgetbl_ctl: 0x3ffc0001 getbl_err: 0x00000003
ipeir: 0x00000000 iphdr: 0x7d000006
LP ring tail: 0x0000e490 head: 0x0000e49c len: 0x0001f001 start 0x00000000
eir: 0x0000 esr: 0x0010 emr: 0xffff
instdone: 0xfa41 instpm: 0x0000
memmode: 0x0000010f instps: 0x800f04c4
hwstam: 0xfffe ier: 0x0002 imr: 0x0000 iir: 0x0070
Ring at virtual 0xa782f000 head 0xe49c tail 0xe490 count 32765


...


Ring end
space: 4 wanted 32
(II) intel(0): [drm] removed 1 reserved context for kernel
(II) intel(0): [drm] unmapping 8192 bytes of SAREA 0xf8d41000 at 0xb7ef3000
(II) intel(0): [drm] Closed DRM master.

Fatal server error:
lockup


...

I have reported a version of this to upstream (as per a request by one of the DDs in a similar bug log:

http://bugs.freedesktop.org/show_bug.cgi?id=16262

See also:

http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=465694
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=432110

Celejar
--
mailmin.sourceforge.net - remote access via secure (OpenPGP) email
ssuds.sourceforge.net - A Simple Sudoku Solver and Generator




I took at look at those bugs, thanks for the info. It's difficult to say much,
given how vaguely we're able to describe the problem. Although, I too wondered
whether or not a suspend/resume cycle was required.


I can tell you that the noexacomposite option made things much worse. Crashed
four times in one day.


Since then I've removed that line from xorg.conf and removed the libflash.so
plugin (I'd be using 10 beta). I've installed gnash, but really, I'm just doing
without flash. I've no reason to suspect flash is at fault, it's just something
I can try while I wait to here more or get asked to try other things.


Regards,


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
 
Old 07-22-2008, 01:18 AM
"s. keeling"
 
Default Help filing bug report; can't use automated tool, does this report look OK?

Arthur A <arthur.machlas@gmail.com>:
> Celejar wrote:
> > [snip]
> > I have reported a version of this to upstream (as per a request by one of the DDs in a similar bug log:
> >
> > http://bugs.freedesktop.org/show_bug.cgi?id=16262
> >
> > See also:
> >
> > http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=465694
> > http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=432110
> [snip]
> Since then I've removed that line from xorg.conf and removed the libflash.so
> plugin (I'd be using 10 beta). I've installed gnash, but really, I'm just doing
> without flash. I've no reason to suspect flash is at fault, it's just something

Really? You don't consider flash a horribly buggy, poorly implemented
disaster? Huh. "This Shockwave Flash file type is known to ..."

Finding it to actually work is a surprise, here. Usually it's kill
-HUP $(pidof swf), and I get my browser back.

Admittedly, this is etch.


--
Any technology distinguishable from magic is insufficiently advanced.
(*) http://blinkynet.net/comp/uip5.html Linux Counter #80292
- - http://www.faqs.org/rfcs/rfc1855.html Please, don't Cc: me.


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
 

Thread Tools




All times are GMT. The time now is 08:29 AM.

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