[Bug 241011] New: kernel panic in VIA VT6102 [Rhine-II]
https://bugzilla.novell.com/show_bug.cgi?id=241011 Summary: kernel panic in VIA VT6102 [Rhine-II] Product: openSUSE 10.2 Version: Final Platform: x86 URL: http://tigress.com/nobs/kernelpanic.jpeg OS/Version: SuSE Other Status: NEW Severity: Major Priority: P5 - None Component: Kernel AssignedTo: kernel-maintainers@forge.provo.novell.com ReportedBy: nobs@tigress.com QAContact: qa@suse.de machine crashes randomly in normal operation running Suse 10.2 every some days a test with heavy CPU load (make -j5) and heavy network traffic in/out crashes the machine in minutes (seconds sometimes) memtest runs for hours with no errors the network is onboard of a VIA-mainboard CPU is Celeron (F/M/S=15/2/7) machine is not getting warm photo of screen shot from kernel panic is in URL attached 00:00.0 Host bridge: VIA Technologies, Inc. P4M266 Host Bridge 00:01.0 PCI bridge: VIA Technologies, Inc. VT8633 [Apollo Pro266 AGP] 00:12.0 Ethernet controller: VIA Technologies, Inc. VT6102 [Rhine-II] (rev 74) Subsystem: VIA Technologies, Inc. VT6102 [Rhine II] Embeded Ethernet Controller on VT8235 Flags: bus master, medium devsel, latency 32, IRQ 11 I/O ports at e400 [size=256] Memory at e3802000 (32-bit, non-prefetchable) [size=256] Capabilities: [40] Power Management version 2 -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=241011 jbenc@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO Info Provider| |nobs@tigress.com ------- Comment #2 from jbenc@novell.com 2007-02-01 06:27 MST ------- Could you reproduce the crash with debug=5 parameter to via_rhine module? Be aware that this debug level produces a heavy load of kernel messages so it's possible you'll experience some problems. I recommend to kill klogd and setting logging to a console - something like: klogconsole -l 9 -r 1 echo '9 4 1 7' > /proc/sys/kernel/printk Then switching to tty1 and starting the test from a remote machine. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=241011 ------- Comment #3 from jbenc@novell.com 2007-02-01 06:29 MST ------- Created an attachment (id=116821) --> (https://bugzilla.novell.com/attachment.cgi?id=116821&action=view) Screen shot from the URL mentioned -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=241011 nobs@tigress.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW Info Provider|nobs@tigress.com | ------- Comment #4 from nobs@tigress.com 2007-02-01 09:06 MST ------- This time machine just freezed, so I don't got a kernel panic screen. If I get another screen I send it. This is the last lines in syslog with debug=5 Feb 1 16:52:32 backup kernel: eth0: Transmit frame #3105071 queued in slot 15. Feb 1 16:52:32 backup kernel: eth0: Transmit frame #3105072 queued in slot 0. Feb 1 16:52:32 backup kernel: eth0: Interrupt, status 00000002. Feb 1 16:52:32 backup kernel: eth0: exiting interrupt, status=00000000. Feb 1 16:52:32 backup kernel: eth0: Interrupt, status 00000002. Feb 1 16:52:32 backup kernel: eth0: exiting interrupt, status=00000000. Feb 1 16:52:32 backup kernel: eth0: Interrupt, status 00000003. Feb 1 16:52:32 backup kernel: eth0: exiting interrupt, status=00000000. Feb 1 16:52:32 backup kernel: eth0: rhine_rx(), entry 35 status 00468f00. Feb 1 16:52:32 backup kernel: rhine_rx() status is 00468f00. Feb 1 16:52:32 backup kernel: eth0: Interrupt, status 00000001. Feb 1 16:52:32 backup kernel: eth0: exiting interrupt, status=00000000. Feb 1 16:52:32 backup kernel: eth0: rhine_rx(), entry 36 status 00468f00. Feb 1 16:52:32 backup kernel: rhine_rx() status is 00468f00. Feb 1 16:52:32 backup kernel: eth0: Transmit frame #3105073 queued in slot 1. Feb 1 16:52:32 backup kernel: eth0: Transmit frame #3105074 queued in slot 2. Feb 1 16:52:32 backup kernel: eth0: Transmit frame #3105075 queued in slot 3. Feb 1 16:52:32 backup kernel: eth0: Interrupt, status 00000002. Feb 1 16:52:32 backup kernel: eth0: exiting interrupt, status=00000000. Feb 1 16:52:32 backup kernel: eth0: Interrupt, status 00000002. Feb 1 16:52:32 backup kernel: eth0: exiting interrupt, status=00000000. Feb 1 16:52:32 backup kernel: eth0: Interrupt, status 00000002. Feb 1 16:52:32 backup kernel: eth0: exiting interrupt, status=00000000. Feb 1 16:52:32 backup kernel: eth0: Interrupt, status 00000001. Feb 1 16:52:32 backup kernel: eth0: exiting interrupt, status=00000000. Feb 1 16:52:32 backup kernel: eth0: rhine_rx(), entry 37 status 00468f00. Feb 1 16:52:32 backup kernel: rhine_rx() status is 00468f00. Feb 1 16:52:32 backup kernel: eth0: Transmit frame #3105076 queued in slot 4. Feb 1 16:52:32 backup kernel: eth0: Transmit frame #3105077 queued in slot 5. Feb 1 16:52:32 backup kernel: eth0: Transmit frame #3105078 queued in slot 6. Feb 1 16:52:32 backup kernel: eth0: Interrupt, status 00000002. Feb 1 16:52:32 backup kernel: eth0: exiting interrupt, status=00000000. Feb 1 16:52:32 backup kernel: eth0: Interrupt, status 00000002. Feb 1 16:52:32 backup kernel: eth0: exiting interrupt, status=00000000. Feb 1 16:52:32 backup kernel: eth0: Interrupt, status 00000001. Feb 1 16:52:32 backup kernel: eth0: Interrupt, status 00000002. Feb 1 16:52:32 backup kernel: eth0: exiting interrupt, status=00000000. Feb 1 16:52:32 backup kernel: eth0: rhine_rx(), entry 38 status 00468f00. Feb 1 16:52:32 backup kernel: rhine_rx() status is 00468f00. Feb 1 16:52:32 backup kernel: eth0: Interrupt, status 00000001. Feb 1 16:52:32 backup kernel: eth0: exiting interrupt, status=00000000. Feb 1 16:52:32 backup kernel: eth0: rhine_rx(), entry 39 status 00468f00. Feb 1 16:52:32 backup kernel: rhine_rx() status is 00468f00. Feb 1 16:57:46 backup syslog-ng[2562]: syslog-ng version 1.6.11 starting -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=241011 jbenc@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO Info Provider| |nobs@tigress.com ------- Comment #5 from jbenc@novell.com 2007-02-02 03:24 MST ------- I'm afraid last kernel messages were not caught by klogd (or not written by syslog) when the machine freezed. Please try with logging to the console as described above (preferably with framebuffer switched off by passing vga=1 to the kernel during boot). -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=241011 ------- Comment #6 from nobs@tigress.com 2007-02-05 07:22 MST ------- Currently I don't have a machine for that test. I will provide more info as soon as I have the machine back. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=241011#c7
Thomas Scholz
https://bugzilla.novell.com/show_bug.cgi?id=241011#c8
Stephan Kulow
participants (1)
-
bugzilla_noreply@novell.com