Bug#615397: linux-image-2.6.37-1-amd64: segfault in multiple apps when using this kernel
On Sat, 2011-02-26 at 21:06 +0000, Ben Hutchings wrote:
> On Sat, 2011-02-26 at 18:27 +0100, Matthew Smith wrote:
> > Package: linux-2.6
> > Version: 2.6.37-1
> > Severity: important
> >
> > Running this kernel I can log into gnome fine, but running dselect gives:
> > A error occurred during the signature verification. The repository is not
> > updated and the previous index files will be used. GPG error:
> > http://ftp.nl.debian.org unstable InRelease: Internal error: Good signature,
> > but could not determine key fingerprint?!
> >
> > and the following line is reported in syslog
> >
> > gpgv[5221]: segfault at ffffffff89480143 ip 0000000000404000 sp
> > 00007fff3dd925f8 error 6 in gpgv[400000+55000]
> >
> > Attempting to decompress good archive files results in crc errors less than
> > halfway through the set. Extracting the same archive in 2.6.32 works just fine.
> > (4.4GB zipped or rar'ed ISO files)
> >
> > Also the adobe flash player crashes immediately, I can only send a bug report
> > to adobe by clicking in the window, adobe restarts after sending the report (no
> > idea what is in it, I get to see nothing) and crashes again immediately.. As in
> > the above 2 problems it works fine in 2.6.32.
> >
> > Eventually the machine grinds to a halt, X freezes, the hard disk reports that
> > it is trying to access beyond the "end" of the device or something and all I
> > can do is hit the reset buttone and go back the kernel 2.6.32.
> >
> > I'll stop here before it crashes again...
> [...]
> > ** Tainted: P (1)
> > * Proprietary module has been loaded.
> [...]
>
> Please remove fglrx and try again.
>
> Ben.
>
OK, I removed all fglrx packages and told X to use the radeon driver.
After rebooting, gnome starts as usual (slightly different resolution,
as is the console, fglrx being my usual driver) and I can log in. The
segfaults look to be gone (it could be me but was fglrx and radeon
loaded at the same time causing that?) but just logging into gnome and
doing youtube, dvd's and hellanzb gives this fairly quickly:
Feb 27 07:38:08 chaosx kernel: [ 364.051626] ata1: soft resetting link
Feb 27 07:38:08 chaosx kernel: [ 364.345013] ata1.00: configured for
UDMA/133
Feb 27 07:38:08 chaosx kernel: [ 364.345034] ata1: EH complete
Feb 27 07:38:36 chaosx kernel: [ 392.968383] ata1: soft resetting link
Feb 27 07:38:37 chaosx kernel: [ 393.148459] ata1.00: configured for
UDMA/133
Feb 27 07:38:37 chaosx kernel: [ 393.148481] ata1: EH complete
Feb 27 07:38:38 chaosx kernel: [ 394.561224] ata1: soft resetting link
Feb 27 07:38:38 chaosx kernel: [ 394.740458] ata1.00: configured for
UDMA/133
Feb 27 07:38:38 chaosx kernel: [ 394.740478] ata1: EH complete
Feb 27 07:38:41 chaosx kernel: [ 397.001613] ata1.00: limiting speed to
UDMA/100:PIO4
Feb 27 07:38:41 chaosx kernel: [ 397.001663] ata1: soft resetting link
I've done a few reboots and tests now. Sometimes I've been dumped to the
maintenance shell due to filesystem damage, but answering Yes to all the
prompts that fsck.ext3 gives when rebooting back to 2.6.32 seems to work
fine.
In any case, the longer I leave it booted with 2.6.37, the unstabler it
gets, under 2.6.32, no instability.
Thanks
Matthew
Reply to: