Bug#865746: Fixed with new kernel
Fixed for us with the kernel announced here: https://lists.debian.org/debian-security-announce/2017/msg00160.html which fixes bug 865303 Thanks! Jon
Bug#865311:
C programs which start a jvm using jni also segfault. This smells like fundamentally the same issue. I added a "me too" to debian bug 865746 (collectd), with links to info about the issue at Ubuntu - including a test program to reproduce. See https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=865746#15 and #16.
Bug#865746: See also related Ubuntu kernel-package bug
On Mon, 26 Jun 2017 11:09:29 +0200 =?UTF-8?Q?Jon_K=c3=a5re_Hellan?=wrote: > This Ubuntu bug report shows how to reproduce > > https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1700270 > > Example program in comments 1, 2 and 3. > > It is filed against their kernel-package. Apparently, anything that uses > jni to instantiate a jvm will fail. > And their bug https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1699772 shows a lot of software affected by the bug. This is probably the same issue as inDebian src:linux bug 865303, although the workaround discussed there isn't applicable. I'll add a pointer from that bug to this one.
Bug#865746: See also related Ubuntu kernel-package bug
This Ubuntu bug report shows how to reproduce https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1700270 Example program in comments 1, 2 and 3. It is filed against their kernel-package. Apparently, anything that uses jni to instantiate a jvm will fail.
Bug#865746: Same bug on jessie
We see the same segfault on jessie with collectd 5.4.1-6+deb8u1 Jon Kåre Hellan UNINETT AS - Trondheim - Norway
Bug#377539: Summarizing our IRC session
We discussed this on IRC. Here's what we came up with. PnP support for nsc-ircc is new in 2.6.17. The dmesg log shows the following: nsc_ircc_pnp_probe() : From PnP, found firbase 0x2F8 ; irq 3 ; dma 3. nsc-ircc, chip-init nsc-ircc, Found chip at base=0x02e nsc-ircc, driver loaded (Dag Brattli) nsc_ircc_open(), can't get iobase of 0x2f8 nsc-ircc, Found chip at base=0x02e nsc-ircc, driver loaded (Dag Brattli) nsc_ircc_open(), can't get iobase of 0x2f8 pnp: Device 00:14 disabled. It looks like PNP is disabling the IR device. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#372468: libgtk-java not installable in sid
Package: libgtk-java Version: 2.8.4-1 Here's what happens when trying to install libgtk-java on sid: $ sudo apt-get install libgtk-java Reading package lists... Done Building dependency tree... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. Since you only requested a single operation it is extremely likely that the package is simply not installable and a bug report against that package should be filed. The following information may help to resolve the situation: The following packages have unmet dependencies: libgtk-java: Depends: libgtk-jni (= 2.8.4-1) but it is not going to be installed Depends: libglib-java but it is not installable Depends: libcairo-java but it is not installable E: Broken packages libglib-java and libcairo-java have no installation candidate. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#345845: When will we see the fix in sid?
Hi, Thanks for telling me how to report this bug upstream: Java applets go blank immediately I reported it as https://bugzilla.mozilla.org/show_bug.cgi?id=322257, which in turn is a duplicate of https://bugzilla.mozilla.org/show_bug.cgi?id=315841. This bug is fixed upstream. The effect of the bug is that java applets don't work if adblock is installed. For me, the consequence is that I have to use another browser to do home banking. That works, but it's getting old :-) Do you know in which version of Firefox the fix will be included? According to mozilla.org bugzilla, target milestone is mozilla1.9alpha, if that means anything. Any wild guesses about when we can expect to see the fix in Debian? For what it's worth, on Fedora Core 4, java applets work in Firefox 1.5.0.1 even with adblock installed. The package version is firefox-1.5.0.1-1. Jon -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#353790: Bug is fixed in 2.6.16
2.6.16 includes the fix to this bug. Please close my bug report. Jon Hellan -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#353790: Bug is being fixed upstream
Hi, The linux-ide developers have worked with Silicon Image and found the cause and a real fix. Yay for open specifications! The fix is expected in version 2.6.16 or 17. See http://comments.gmane.org/gmane.linux.ide/8255 Jon -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#353790: More info
I forgot to tell that I've seen this problem with kernels as far back as 2.6.8. My feeling is that it happens more frequently now than half a year ago. I know this points in the direction of hardware problems, but Windows works, even for large file copies. The vendor mounted two disks and copied a 15 GB dummy file back and forth. Result OK. Test was repeated while system was stressed. Still OK. Finally a continuous 65 hour stress test. May be marginal timings have become more problematic over time. I know this will be hard to track down. Suggestions for workarounds are welcome. Is there anything like hdparm for SATA? Regards Jon -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#353790: Progress
Hi, I googled a bit, and that led me to what I think is the solution. If you read the thread at http://www.linuxquestions.org/questions/showthread.php?threadid=278603, you find that there are known problems with Seagate and the Silicon Image 3112a controller. What you need to do is add your drive model (ex: ST3200822AS) to the blacklist in sata_sil.c (kernel source top dir/drivers/scsi/sata_sil.c). Look for the section with a listing of drives and MOD_15_QUIRK. Needless to say, this involves recompiling the sata_sil kernel module. This quirk flag is named SIL_QUIRK_MOD15WRITE in current kernel sources. It turns out that my disk, Seagate ST3200822AS, is already on the blacklist with the correct quirk flag. However, the quirk fix isn't applied for 3512 controllers, which is what I've got. I changed sata_sil.c like this: --- drivers/scsi/sata_sil.c.orig 2006-02-21 18:10:43.0 +0100 +++ drivers/scsi/sata_sil.c 2006-02-21 19:40:35.0 +0100 @@ -90,7 +90,7 @@ static const struct pci_device_id sil_pci_tbl[] = { { 0x1095, 0x3112, PCI_ANY_ID, PCI_ANY_ID, 0, 0, sil_3112_m15w }, { 0x1095, 0x0240, PCI_ANY_ID, PCI_ANY_ID, 0, 0, sil_3112_m15w }, - { 0x1095, 0x3512, PCI_ANY_ID, PCI_ANY_ID, 0, 0, sil_3112 }, + { 0x1095, 0x3512, PCI_ANY_ID, PCI_ANY_ID, 0, 0, sil_3112_m15w }, { 0x1095, 0x3114, PCI_ANY_ID, PCI_ANY_ID, 0, 0, sil_3114 }, { 0x1002, 0x436e, PCI_ANY_ID, PCI_ANY_ID, 0, 0, sil_3112_m15w }, { 0x1002, 0x4379, PCI_ANY_ID, PCI_ANY_ID, 0, 0, sil_3112_m15w }, I can see from the log that Seagate errata fix is enabled, and haven't seen any more lockups. This removes the last occurrence of sil_3112 in sil_pci_tbl. Regards Jon -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#278392: Looking over outstanding reports sent by me: Can this be closed know.
hi, I'm looking over outstanding reports sent by me and found this one from over a year ago. I would be very surprised if it hasn't been fixed. Can you decide just by looking? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#278392: Looking over outstanding reports sent by me: Can this be closed know.
Frans Pop wrote: On Thursday 19 January 2006 09:53, Jon Kåre Hellan wrote: I'm looking over outstanding reports sent by me and found this one from over a year ago. I would be very surprised if it hasn't been fixed. Can you decide just by looking? SATA support is still under development and there are still issues. However, it is very hard to keep track of individual drivers. I think the general issue is still there in the kernel, but during an installation using the 2.6.15 kernel different initrd generators are used from Sarge and those have better logic for loading ide-generic, so I would guess that with the Etch installer (daily images) you will not see the problem any more. Let us know if we should close your report. Let me put it this way: I have no objection to you closing it. Feel free to let it remain open if you would lose information by closing it.