Error logging into SBP-2 device - login timed-out

Discuss usability issues, general maintenance, and general support issues for a grsecurity-enabled system.

Error logging into SBP-2 device - login timed-out

Postby BlueSloth » Wed Aug 02, 2006 5:32 am

I have an IDE hard drive in a Firewire external enclosure. When I plug it in, the device node never shows up in /dev, and /var/log/sys.log says
Code: Select all
Jul 28 22:32:57 Shinobu kernel: ieee1394: The root node is not cycle master capable; selecting a new root node and resetting...
Jul 28 22:32:57 Shinobu kernel: ieee1394: Node added: ID:BUS[0-00:1023]  GUID[0030e002e0454b97]
Jul 28 22:32:57 Shinobu kernel: ieee1394: Node changed: 0-00:1023 -> 0-01:1023
Jul 28 22:32:57 Shinobu kernel: ieee1394: sbp2: Driver forced to serialize I/O (serialize_io=1)
Jul 28 22:32:57 Shinobu kernel: ieee1394: sbp2: Try serialize_io=0 for better performance
Jul 28 22:32:57 Shinobu kernel: scsi0 : SBP-2 IEEE-1394
Jul 28 22:33:18 Shinobu kernel: ieee1394: sbp2: Error logging into SBP-2 device - login timed-out
Jul 28 22:33:18 Shinobu kernel: sbp2: probe of 0030e002e0454b97-0 failed with error -16

I first tried it with Linux 2.6.16.19 and grsecurity-2.1.9-2.6.16.19-200606041421, and got the errors.
I got Linux 2.6.17.7 and grsecurity-2.1.9-2.6.17.7-200607261817, and still got the errors.
I turned off all the features in /proc/sys/kernel/grsecurity and /proc/sys/kernel/pax, then reloaded the ieee1394, ohci1394 and sbp2 kernel modules, and still got the errors.
I tried it with the vanilla Linux 2.6.17.7, and it worked. So it must be a problem with grsecurity.

I looked at the news page to see what was fixed in grsecurity-2.1.9-2.6.17.7-200608012135, and my problem isn't mentioned.

Oh yeah, I'm running Linux From Scratch, with udev 096, if that matters.

So.. anyone know what's going wrong? And maybe how to fix it?

BlueSloth
BlueSloth
 
Posts: 2
Joined: Sun Jul 30, 2006 1:00 am

Re: Error logging into SBP-2 device - login timed-out

Postby PaX Team » Wed Aug 02, 2006 6:59 am

BlueSloth wrote:I first tried it with Linux 2.6.16.19 and grsecurity-2.1.9-2.6.16.19-200606041421, and got the errors.
I got Linux 2.6.17.7 and grsecurity-2.1.9-2.6.17.7-200607261817, and still got the errors.
I turned off all the features in /proc/sys/kernel/grsecurity and /proc/sys/kernel/pax, then reloaded the ieee1394, ohci1394 and sbp2 kernel modules, and still got the errors.
I tried it with the vanilla Linux 2.6.17.7, and it worked. So it must be a problem with grsecurity.
PaX disables phys_dma support by default, you can re-enable it by passing phys_dma=1 to ohci1394 or writing to /sys/module/ohci1394/parameters/phys_dma.
PaX Team
 
Posts: 2310
Joined: Mon Mar 18, 2002 4:35 pm

Postby BlueSloth » Wed Aug 02, 2006 2:36 pm

Yay! That was easy

Thanks

BlueSloth
BlueSloth
 
Posts: 2
Joined: Sun Jul 30, 2006 1:00 am


Return to grsecurity support