[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <200902132054.HBF52153.QtLFVOJHSMOFOF@I-love.SAKURA.ne.jp>
Date: Fri, 13 Feb 2009 20:54:50 +0900
From: Tetsuo Handa <penguin-kernel@...ove.SAKURA.ne.jp>
To: frederik.deweerdt@...og.eu, rjw@...k.pl
Cc: linux-kernel@...r.kernel.org, kernel-testers@...r.kernel.org
Subject: Re: [Bug #12409] NULL pointer dereference at get_stats()
Hello.
Tetsuo Handa wrote:
> I think this bug will happen in native environment too.
> http://lkml.org/lkml/2009/1/4/349
> But due to driver initialization failure caused by "nolapic" option,
> I can't reach /sbin/init on native ThinkPad X60 environment.
I don't encounter NULL pointer dereference at get_stats() on native
environment, but I encounter another problem on native environment;
initialization of SATA device fails if "nolapic" is given.
I don't have specific reasons to give "nolapic" option. This problem was
found when I was trying to reproduce [Bug #12409] on native ThinkPad X60
environment.
scsi0 : ahci
scsi1 : ahci
scsi2 : ahci
scsi3 : ahci
ata1: SATA max UDMA/133 abar m1024@...e444400 port 0xee444500 irq 1275
ata2: DUMMY
ata3: DUMMY
ata4: DUMMY
Marking TSC unstable due to TSC halts in idle
usb 3-6: new high speed USB device using ehci_hcd and address 2
usb 3-6: configuration #1 chosen from 1 choice
hub 3-6:1.0: USB hub found
hub 3-6:1.0: 4 ports detected
firewire_core: created device fw0: GUID 000ae40600522014, S400
ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
ata1.00: qc timeout (cmd 0xec)
ata1.00: failed to IDENTIFY (I/O error, err_mask=0x4)
ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
ata1.00: qc timeout (cmd 0xec)
ata1.00: failed to IDENTIFY (I/O error, err_mask=0x4)
ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
ata1.00: qc timeout (cmd 0xec)
ata1.00: failed to IDENTIFY (I/O error, err_mask=0x4)
ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
Full log for 2.6.28.5 without "nolapic" option:
http://I-love.SAKURA.ne.jp/tmp/dmesg-2.6.28.5-native.txt
Full log for 2.6.28.5 with "nolapic" option:
http://I-love.SAKURA.ne.jp/tmp/dmesg-2.6.28.5-native-nolapic.txt
Full log for 2.6.27.16 without "nolapic" option:
http://I-love.SAKURA.ne.jp/tmp/dmesg-2.6.27.16-native.txt
Full log for 2.6.27.16 with "nolapic" option:
http://I-love.SAKURA.ne.jp/tmp/dmesg-2.6.27.16-native-nolapic.txt
Full log for 2.6.26.8 without "nolapic" option:
http://I-love.SAKURA.ne.jp/tmp/dmesg-2.6.26.8-native.txt
Full log for 2.6.26.8 with "nolapic" option:
http://I-love.SAKURA.ne.jp/tmp/dmesg-2.6.26.8-native-nolapic.txt
Config:
http://I-love.SAKURA.ne.jp/tmp/config-2.6.27.16
http://I-love.SAKURA.ne.jp/tmp/config-2.6.28.5
2.6.27.16 and 2.6.28.5 fail with this problem.
2.6.26.8 does not fail with this problem.
Regards.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists