Description
Horst Prote
2006-01-18 09:04:11 UTC
Created attachment 77435 [details]
complete dmesg output of 2.6.11-hardened-r15
Created attachment 77436 [details]
complete dmesg output of 2.6.14-hardened-r3
Created attachment 77437 [details]
complete /proc/scsi/aic79xx/0 of 2.6.11-hardened-r15
Created attachment 77438 [details]
complete /proc/scsi/aic79xx/1 of 2.6.11-hardened-r15
Created attachment 77439 [details]
complete /proc/scsi/aic79xx/0 of 2.6.14-hardened-r3
Created attachment 77440 [details]
complete /proc/scsi/aic79xx/1 of 2.6.14-hardened-r3
Created attachment 77441 [details]
kernel-config-x86-2.6.11-hardened-r15
Created attachment 77442 [details]
kernel-config-x86-2.6.14-hardened-r3
Do you rely on any features of the hardened-sources kernel? We really need to get this reported upstream, but that would involve you testing the latest 'vanilla' development kernel first (currently 2.6.16-rc1). (In reply to comment #9) > Do you rely on any features of the hardened-sources kernel? Not really. > We really need to > get this reported upstream, but that would involve you testing the latest > 'vanilla' development kernel first (currently 2.6.16-rc1). OK, I'll test that kernel. But since it's the main server of our workgroup and the colleagues already grumble about me rebooting all the time I'll wait with the reboot until Wednesday 11:30 CET (our time slot for planned reboots). After checking /proc/scsc/aic79xx/0 under kernel 2.6.16-rc1 would you advice me to leave that kernel running (What's about it's stability and secureness?) or boot back to 2.6.11-hardened-r15? (In reply to comment #10) > After checking /proc/scsc/aic79xx/0 under kernel 2.6.16-rc1 would you advice me > to leave that kernel running (What's about it's stability and secureness?) or > boot back to 2.6.11-hardened-r15? This question certainly isn't relevant if the vanilla kernel has the problem too. (In reply to comment #9) > but that would involve you testing the latest > 'vanilla' development kernel first (currently 2.6.16-rc1). I did the test (vanilla-sources-2.6.16_rc1) and the problem remains (I'll attach the logs and kernel-config). So it's an upstream problem. Or could anything of this be the cause: 1) The change from 2.4.28-hardened-r4 to 2.6.11-hardened-r1 kernel I did with this command: genkernel --kernel-config=/etc/kernels/kernel-config-x86-2.4.28-hardened-r4 --menuconfig all But this kernel and 2.6.11-hardened-r13, 2.6.11-hardened-r15 didn't show the problem. 2) The first kernel showing the problem was the first one built after gcc upgrade (3.3.6 -> 3.4.4-r1). Created attachment 78068 [details]
complete dmesg output of vanilla 2.6.16-rc1
Created attachment 78069 [details]
complete /proc/scsi/aic79xx/0 of vanilla 2.6.16-rc1
The differences in the first line of the
"Target 1 Negotiation Settings" in /proc/scsi/aic79xx/0 for
- 2.6.16-rc1:
Target 1 Negotiation Settings
User: 160.000MB/s transfers (80.000MHz RDSTRM|DT|IU|QAS, 16bit)
- 2.6.14-hardened-r3:
Target 1 Negotiation Settings
User: 320.000MB/s transfers (160.000MHz RDSTRM|DT|IU|QAS, 16bit)
- 2.6.11-hardened-r15:
Target 1 Negotiation Settings
User: 160.000MB/s transfers (80.000MHz DT|IU|QAS, 16bit)
are caused by me changing the default for target 1 in the Adaptec BIOS from 320 to 160 (didn't help for 2.6.14-hardened-r3 and 2.6.16-rc1 and 2.6.11-hardened-r15 works with both) and activating CONFIG_AIC79XX_ENABLE_RD_STRM in the kernel.
Created attachment 78070 [details]
kernel-config-x86-2.6.16-rc1
Ok, thanks for testing that. The next step is to report the problem to the Linux SCSI developers. Please file a bug for this against 2.6.16-rc1 at http://bugzilla.kernel.org and post the new bug URL here. (In reply to comment #16) > Please file a bug for this against 2.6.16-rc1 at > http://bugzilla.kernel.org and post the new bug URL here. > Done: http://bugzilla.kernel.org/show_bug.cgi?id=5955 Just a note on my comment #4 in http://bugzilla.kernel.org/show_bug.cgi?id=5955 of today: I also tried 2.6.14-hardened-r8 with the two changes in the Adaptec BIOS but had no success. But that's just for the record since I'm happy now running vanilla kernel 2.6.17-rc5. Fixed, see upstream bug |