Bug 132271

Summary:	kernel null dereference with/by X
Product:	[openSUSE] SUSE LINUX 10.0	Reporter:	Volker Kuhlmann <bugz57>
Component:	Kernel	Assignee:	Takashi Iwai <tiwai>
Status:	RESOLVED FIXED	QA Contact:	E-mail List <qa-bugs>
Severity:	Normal
Priority:	P5 - None	CC:	eich, sndirsch
Version:	Final
Target Milestone:	---
Hardware:	i686
OS:	SuSE Linux 10.0
Whiteboard:
Found By:	Other	Services Priority:
Business Priority:		Blocker:	---
Marketing QA Status:	---	IT Deployment:	---
Attachments:	syslog /etc/X11/xorg.conf /var/log/Xorg.0.log Fix

Description Volker Kuhlmann 2005-11-03 23:46:08 UTC

Not sure whether I should bugzilla this, but I had this kernel problem never before I upgraded to 10.0 recently, and therefore doubt it's a hardware issue. If others see it too the info might help you.

$USER was browsing gmx webmail with konqueror, and logged out from gmx. The logout completed, but the whole desktop froze. Question whether gmx has anything to do with it. The rest of the box kept running fine, but no keyboard/mouse/console. Ssh login allowed to kill all $USER processes except X and (I think) ksmserver), but didn't unlock the screen (not surprisingly, with X a zombie).

Hardware is Duron 600, with
00:00.0 Host bridge: Silicon Integrated Systems [SiS] 730 Host (rev 02)
00:00.1 IDE interface: Silicon Integrated Systems [SiS] 5513 [IDE] (rev d0)
00:01.0 ISA bridge: Silicon Integrated Systems [SiS] SiS85C503/5513 (LPC Bridge)
00:01.1 Ethernet controller: Silicon Integrated Systems [SiS] SiS900 PCI Fast Ethernet (rev 82)
00:02.0 PCI bridge: Silicon Integrated Systems [SiS] Virtual PCI-to-PCI bridge (AGP)
01:00.0 VGA compatible controller: Silicon Integrated Systems [SiS] 630/730 PCI/AGP VGA Display Adapter (rev 31)

syslog attached

Comment 1 Volker Kuhlmann 2005-11-03 23:48:12 UTC

Created attachment 56440 [details]
syslog

Comment 2 Olaf Kirch 2005-11-15 11:11:00 UTC

It seems the SIS driver tries to grab a huge chunk of memory, which
fails, but the driver doesn't check for a NULL return value and happily
dereferences this NULL pointer later.

Comment 3 Stefan Dirsch 2005-11-15 11:55:11 UTC

Could you please attach /etc/X11/xorg.conf and /var/log/Xorg.0.log? Thanks.

Comment 4 Volker Kuhlmann 2005-11-17 05:42:14 UTC

Created attachment 57588 [details]
/etc/X11/xorg.conf

Comment 5 Volker Kuhlmann 2005-11-17 05:45:28 UTC

Created attachment 57589 [details]
/var/log/Xorg.0.log

Not the log file from when the crash happened, that got overwritten ages ago, but I hope it'll give you the same info. Crash hasn't happened again so far.

Comment 6 Stefan Dirsch 2005-11-17 08:13:25 UTC

Ok. The next time it happens, reboot and attach /var/log/Xorg.0.log.old or reboot into runlevel 3 and attach /var/log/Xorg.0.log.

Comment 7 Egbert Eich 2005-11-24 16:33:43 UTC

Created attachment 58622 [details]
Fix

If there isn't anything else after this function broken, too this patch should fix the problem.

Comment 8 Volker Kuhlmann 2005-11-24 21:56:08 UTC

The machine is in daily use, but I haven't had another crash since the first, which makes it difficult to test whether the patch fixes the problem.

Comment 9 Olaf Kirch 2005-11-25 07:43:45 UTC

From my POV, okay to apply to SLES9 branch as well if it has that issue, too.

Comment 10 Olaf Kirch 2005-11-28 13:52:33 UTC

Takashi, can you please apply this patch to the 10.0 branch?

Comment 12 Takashi Iwai 2005-11-28 15:02:45 UTC

I'm working on it.

Linus' git tree doesn't have this fix, too.  Shouldn't we submit to mainstream?

Comment 13 Marcus Meissner 2005-11-29 10:22:06 UTC

definitely submit to mainstream too.

Comment 14 Takashi Iwai 2005-11-30 14:37:34 UTC

OK, submitted to LKML.  Both 10.0 and HEAD include the patch now.

Comment 15 Stefan Dirsch 2005-11-30 14:42:25 UTC

Thanks. Takashi, could you forward the email to LKML to Dave Airlie <airlied@linux.ie>? He's responsible for the DRM drivers. Just to make sure it won't get lost. I think we can close this now.

Comment 16 Takashi Iwai 2005-12-02 17:09:52 UTC

OK, let's close it.  If you still have a similar problem, please reopen.

Comment 17 Volker Kuhlmann 2005-12-05 10:15:55 UTC

Had a lockup with the same symptoms for the second time now, but absolutely nothing in syslog, and a normal Xorg.0.log.old. Perhaps because I pushed the reset button instead of trying to shut the system down cleanly?