Your message dated Fri, 23 Apr 2021 18:50:50 +0200 with message-id <YIL66jQL0q7/[email protected]> and subject line Re: Bug#671895: [sparc] Kernel NULL pointer dereference in sungem/gem_poll() (Re: updates) has caused the Debian Bug report #671895, regarding Kernel NULL pointer dereference in sungem/gem_poll() to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [email protected] immediately.) -- 671895: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=671895 Debian Bug Tracking System Contact [email protected] with problems
--- Begin Message ---Package: linux-2.6 Version: 3.2.16-1 Severity: important Reported today on debian-sparc, kernel hits NULL pointer dereference with the d-i netboot daily while trying to bring the network up (machine is Netra T1 200), sungem driver seems to be the culprit. ------ ┌───────────────┤ Detecting link on eth0; please wait... ├────────────────┐ │ │ │ 100% [ 243.520556] Unable to handle kernel NULL pointer dereference 243.601245] tsk->{mm,active_mm}->context = 00000000000001a0 │ 14;10H[ 243.691289] tsk->{mm,active_mm}->pgd = fffff8001d2c6000 │ [ 243.767267] Kernel panic - not syncing: Aiee, killing interrupt handler! │ [ 243.855403] Call Trace: │ [ 243.887548] [000000000045dcd4] do_exit+0x94/0x708 │ [ 243.950577] [0000000000427550] die_if_kernel+0x2a0/0x2c8────────────────┘ [ 244.021620] [0000000000768c84] unhandled_fault+0x8c/0x98 [ 244.092659] [000000000076936c] do_sparc64_fault+0x6dc/0x780 [ 244.167130] [0000000000407880] sparc64_realfault_common+0x10/0x20 [ 244.248476] [0000000010015680] gem_poll+0x9fc/0x1328 [sungem] [ 244.325234] [0000000000697110] net_rx_action+0x9c/0x234 [ 244.395124] [00000000004607f0] __do_softirq+0xdc/0x1c4 [ 244.463891] [000000000042a76c] do_softirq+0x54/0x80 [ 244.529196] [0000000000460a6c] irq_exit+0x38/0x94 [ 244.592231] [000000000042df38] timer_interrupt+0x90/0xa8 [ 244.663271] [00000000004209d4] tl0_irq14+0x14/0x20 [ 244.727450] [000000000043772c] touch_nmi_watchdog+0x0/0x34 [ 244.800780] [00000000008f07e4] start_kernel+0x390/0x3a0 [ 244.870674] [0000000000750b88] tlb_fixup_done+0x80/0x88 [ 244.940562] [0000000000000000] (null) [ 245.001307] Press Stop-A (L1-A) to return to the boot prom i've boot with diag-switch? = true and hw looks good box is running 2.6.28, i will apply the same config to 3.2 and check if it boots ------ I poked around and can't find any recent similar reports (in Debian or elsewhere). Best regards, -- Jurij Smakov [email protected] Key: http://www.wooyd.org/pgpkey/ KeyID: C99E03CC
--- End Message ---
--- Begin Message ---Hi, On Tue, Aug 20, 2013 at 06:08:24PM +0200, Moritz Muehlenhoff wrote: > reassign 671895 src:linux > thanks > > On Tue, May 22, 2012 at 07:26:22PM -0300, gustavo panizzo <gfa> wrote: > > On Fri, May 11, 2012 at 11:04:22PM +0100, Jurij Smakov wrote: > > [snip] > > > > > > > > Only two non-trivial things here: execution of ethtool_lite(if_name) > > > and invocation of arping. I would put my money on the former (defined > > > in ethtool_lite.c), because it uses low-level ioctls to query the > > > interface state. > > > > > > You can test whether running it would trigger a failure on your > > > machine by downloading ethtool_lite.c and building it as a standalone > > > binary, the following commands appear to do the trick: > > > > > > $ sudo apt-get build-dep netcfg > > > [...] > > > $ gcc -o ethtool-lite -DTEST ethtool-lite.c -ldebconfclient > > > -ldebian-installer > > > $ sudo ./ethtool-lite eth0 > > > ethtool-lite: eth0 is connected. > > > $ > > > > > > If that triggers a null pointer exception on your machine (try it both > > > with and without network brought up and check dmesg afterwards), we > > > will be in a very good position to report it upstream for fixing. > > i cannot repeat the issue using ethtool-lite (or arping) while booting > > from disk, i can repeat the issue booting from network (22/05/2012 > > image) running netcfg or udhcp > > > > > > also i can repeat the issue running > > ~ # ip link set dev eth0 up > > while the cable is plugged in, or running the command and plugging the > > cable later > > > > if i (after getting the netimage) remove the link on eth0 and plug > > eth1, installer works fine > > Does this still occur with current kernels? Assuming the issue is not anymore reproducible on recent kernels I'm going to close this bugreport by now to clean up the list of src:linux bugs from very old issues. In case you can reproduce the issue feel free to reopen the bug. Regards, Salvatore
--- End Message ---
