|

»

general issue with suspend/resume with iwn(4)/bge(4)

View: New views

11 Messages — Rating Filter: Alert me

	general issue with suspend/resume with iwn(4)/bge(4) by Bernhard Schmidt-4 :: Rate this Message: Reply to Author \| View Threaded \| Show Only this Message Hi, I hope this is the correct list for an issue like that, if not, a pointer would be appreciated. I've been in contact with Mykola Dzham quite some time now and we are trying to figure out a resume issue on his iwn(4) device. It does seem that this device does not come up correctly after suspend. The interesting part is, that even pciconf -l -bcv ist not able to get all information. Before suspend: iwn0@pci0:6:0:0: class=0x028000 card=0x13018086 chip=0x42328086 rev=0x00 hdr=0x00 vendor = 'Intel Corporation' device = 'Carte Intel WiFi Link 5100 AGN (Intel WiFi Link 5100)' class = network bar [10] = type Memory, range 64, base 0xec800000, size 8192, enabled cap 01[c8] = powerspec 3 supports D0 D3 current D0 cap 05[d0] = MSI supports 1 message, 64 bit enabled with 1 message cap 10[e0] = PCI-Express 1 endpoint max data 128(128) link x1(x1) After resume: iwn0@pci0:6:0:0: class=0x028000 card=0x13018086 chip=0x42328086 rev=0x00 hdr=0x00 vendor = 'Intel Corporation' device = 'Carte Intel WiFi Link 5100 AGN (Intel WiFi Link 5100)' class = network Note the last 4 missing lines. After a bit of searching i stumbled across kern/136876 which described a very similar (same?) issue for a bge(4) device. The question now is, might there be any special "power management" feature which prevents proper resume? How might a solution look like? Thanks. -- Bernhard _______________________________________________ freebsd-acpi@... mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-acpi To unsubscribe, send any mail to "freebsd-acpi-unsubscribe@..."
	Re: general issue with suspend/resume with iwn(4)/bge(4) by John Baldwin :: Rate this Message: Reply to Author \| View Threaded \| Show Only this Message On Sunday 08 November 2009 6:19:09 am Bernhard Schmidt wrote: > Hi, > > I hope this is the correct list for an issue like that, if not, a pointer > would be appreciated. > > I've been in contact with Mykola Dzham quite some time now and we are trying > to figure out a resume issue on his iwn(4) device. It does seem that this > device does not come up correctly after suspend. The interesting part is, that > even pciconf -l -bcv ist not able to get all information. > > Before suspend: > iwn0@pci0:6:0:0: class=0x028000 card=0x13018086 chip=0x42328086 > rev=0x00 hdr=0x00 > vendor = 'Intel Corporation' > device = 'Carte Intel WiFi Link 5100 AGN (Intel WiFi Link 5100)' > class = network > bar [10] = type Memory, range 64, base 0xec800000, size 8192, enabled > cap 01[c8] = powerspec 3 supports D0 D3 current D0 > cap 05[d0] = MSI supports 1 message, 64 bit enabled with 1 message > cap 10[e0] = PCI-Express 1 endpoint max data 128(128) link x1(x1) > > After resume: > iwn0@pci0:6:0:0: class=0x028000 card=0x13018086 chip=0x42328086 > rev=0x00 hdr=0x00 > vendor = 'Intel Corporation' > device = 'Carte Intel WiFi Link 5100 AGN (Intel WiFi Link 5100)' > class = network Are you sure you didn't forget the extra options to pciconf here? The bar should definitely not disappear since we save that state in software, not in hardware. Also, the capability pointer register is set by the hardware, software never changes it. -- John Baldwin _______________________________________________ freebsd-acpi@... mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-acpi To unsubscribe, send any mail to "freebsd-acpi-unsubscribe@..."
	Re: general issue with suspend/resume with iwn(4)/bge(4) by Mykola Dzham :: Rate this Message: Reply to Author \| View Threaded \| Show Only this Message John Baldwin wrote: > On Sunday 08 November 2009 6:19:09 am Bernhard Schmidt wrote: > > Hi, > > > > I hope this is the correct list for an issue like that, if not, a pointer > > would be appreciated. > > > > I've been in contact with Mykola Dzham quite some time now and we are trying > > to figure out a resume issue on his iwn(4) device. It does seem that this > > device does not come up correctly after suspend. The interesting part is, that > > even pciconf -l -bcv ist not able to get all information. > > > > Before suspend: > > iwn0@pci0:6:0:0: class=0x028000 card=0x13018086 chip=0x42328086 > > rev=0x00 hdr=0x00 > > vendor = 'Intel Corporation' > > device = 'Carte Intel WiFi Link 5100 AGN (Intel WiFi Link 5100)' > > class = network > > bar [10] = type Memory, range 64, base 0xec800000, size 8192, enabled > > cap 01[c8] = powerspec 3 supports D0 D3 current D0 > > cap 05[d0] = MSI supports 1 message, 64 bit enabled with 1 message > > cap 10[e0] = PCI-Express 1 endpoint max data 128(128) link x1(x1) > > > > After resume: > > iwn0@pci0:6:0:0: class=0x028000 card=0x13018086 chip=0x42328086 > > rev=0x00 hdr=0x00 > > vendor = 'Intel Corporation' > > device = 'Carte Intel WiFi Link 5100 AGN (Intel WiFi Link 5100)' > > class = network > > Are you sure you didn't forget the extra options to pciconf here? The bar > should definitely not disappear since we save that state in software, not > in hardware. Also, the capability pointer register is set by the hardware, > software never changes it. Sure. I saved all pciconf -l -bcv (all devices). Difference is only in this lines and in on unuased cardbus: --- pciconf.before.txt 2009-11-07 21:38:21.000000000 +0200 +++ pciconf.after.txt 2009-11-07 21:38:21.000000000 +0200 @@ -180,16 +180,12 @@ vendor = 'Intel Corporation' device = 'Carte Intel WiFi Link 5100 AGN (Intel WiFi Link 5100)' class = network - bar [10] = type Memory, range 64, base 0xec800000, size 8192, enabled - cap 01[c8] = powerspec 3 supports D0 D3 current D0 - cap 05[d0] = MSI supports 1 message, 64 bit enabled with 1 message - cap 10[e0] = PCI-Express 1 endpoint max data 128(128) link x1(x1) none1@pci0:11:4:0: class=0x060700 card=0x9025104d chip=0x04761180 rev=0xba hdr=0x02 vendor = 'Ricoh Company, Ltd.' device = 'Ricoh R/RL/5C476(II) (unknown)' class = bridge subclass = PCI-CardBus - bar [10] = type Memory, range 32, base 0xe8000000, size 4096, enabled + bar [10] = type Memory, range 32, base 0xe8000000, size 4096, disabled cap 01[dc] = powerspec 2 supports D0 D1 D2 D3 current D0 fwohci0@pci0:11:4:1: class=0x0c0010 card=0x9025104d chip=0x08321180 rev=0x04 hdr=0x00 vendor = 'Ricoh Company, Ltd.' -- LEFT-(UANIC\|RIPE) JID: levsha@... PGP fingerprint: 1BCD 7C80 2E04 7282 C944 B0E0 7E67 619E 4E72 9280 _______________________________________________ freebsd-acpi@... mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-acpi To unsubscribe, send any mail to "freebsd-acpi-unsubscribe@..."
	Re: general issue with suspend/resume with iwn(4)/bge(4) by Bernhard Schmidt-4 :: Rate this Message: Reply to Author \| View Threaded \| Show Only this Message On Monday 09 November 2009 13:43:48 John Baldwin wrote: > On Sunday 08 November 2009 6:19:09 am Bernhard Schmidt wrote: > > Hi, > > > > I hope this is the correct list for an issue like that, if not, a pointer > > would be appreciated. > > > > I've been in contact with Mykola Dzham quite some time now and we are > > trying to figure out a resume issue on his iwn(4) device. It does seem > > that this device does not come up correctly after suspend. The > > interesting part is, that even pciconf -l -bcv ist not able to get all > > information. > > > > Before suspend: > > iwn0@pci0:6:0:0: class=0x028000 card=0x13018086 chip=0x42328086 > > rev=0x00 hdr=0x00 > > vendor = 'Intel Corporation' > > device = 'Carte Intel WiFi Link 5100 AGN (Intel WiFi Link 5100)' > > class = network > > bar [10] = type Memory, range 64, base 0xec800000, size 8192, > > enabled cap 01[c8] = powerspec 3 supports D0 D3 current D0 > > cap 05[d0] = MSI supports 1 message, 64 bit enabled with 1 message > > cap 10[e0] = PCI-Express 1 endpoint max data 128(128) link x1(x1) > > > > After resume: > > iwn0@pci0:6:0:0: class=0x028000 card=0x13018086 chip=0x42328086 > > rev=0x00 hdr=0x00 > > vendor = 'Intel Corporation' > > device = 'Carte Intel WiFi Link 5100 AGN (Intel WiFi Link 5100)' > > class = network > > Are you sure you didn't forget the extra options to pciconf here? The bar > should definitely not disappear since we save that state in software, not > in hardware. Also, the capability pointer register is set by the hardware, > software never changes it. The complete pciconf before suspend: http://techwires.net/~bschmidt/pciconf.before.txt The complete pciconf after resume: http://techwires.net/~bschmidt/pciconf.after.txt Comparing both yields exactly those 4 lines missing. -- Bernhard _______________________________________________ freebsd-acpi@... mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-acpi To unsubscribe, send any mail to "freebsd-acpi-unsubscribe@..."
	Re: general issue with suspend/resume with iwn(4)/bge(4) by Serge Semenenko :: Rate this Message: Reply to Author \| View Threaded \| Show Only this Message John Baldwin wrote: On Sunday 08 November 2009 6:19:09 am Bernhard Schmidt wrote: Hi, I hope this is the correct list for an issue like that, if not, a pointer would be appreciated. I've been in contact with Mykola Dzham quite some time now and we are trying to figure out a resume issue on his iwn(4) device. It does seem that this device does not come up correctly after suspend. The interesting part is, that even pciconf -l -bcv ist not able to get all information. Before suspend: iwn0@pci0:6:0:0: class=0x028000 card=0x13018086 chip=0x42328086 rev=0x00 hdr=0x00 vendor = 'Intel Corporation' device = 'Carte Intel WiFi Link 5100 AGN (Intel WiFi Link 5100)' class = network bar [10] = type Memory, range 64, base 0xec800000, size 8192, enabled cap 01[c8] = powerspec 3 supports D0 D3 current D0 cap 05[d0] = MSI supports 1 message, 64 bit enabled with 1 message cap 10[e0] = PCI-Express 1 endpoint max data 128(128) link x1(x1) After resume: iwn0@pci0:6:0:0: class=0x028000 card=0x13018086 chip=0x42328086 rev=0x00 hdr=0x00 vendor = 'Intel Corporation' device = 'Carte Intel WiFi Link 5100 AGN (Intel WiFi Link 5100)' class = network Are you sure you didn't forget the extra options to pciconf here? The bar should definitely not disappear since we save that state in software, not in hardware. Also, the capability pointer register is set by the hardware, software never changes it. It looks similar to PR [1]http://www.freebsd.org/cgi/query-pr.cgi?pr=135070 for me. And if I understood right you're already working on the solution... References 1. http://www.freebsd.org/cgi/query-pr.cgi?pr=135070 _______________________________________________ freebsd-acpi@... mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-acpi To unsubscribe, send any mail to "freebsd-acpi-unsubscribe@..."
	Re: general issue with suspend/resume with iwn(4)/bge(4) by Rui Paulo-3 :: Rate this Message: Reply to Author \| View Threaded \| Show Only this Message On 9 Nov 2009, at 17:03, Bernhard Schmidt wrote: > On Monday 09 November 2009 13:43:48 John Baldwin wrote: >> On Sunday 08 November 2009 6:19:09 am Bernhard Schmidt wrote: >>> Hi, >>> >>> I hope this is the correct list for an issue like that, if not, a >>> pointer >>> would be appreciated. >>> >>> I've been in contact with Mykola Dzham quite some time now and we >>> are >>> trying to figure out a resume issue on his iwn(4) device. It does >>> seem >>> that this device does not come up correctly after suspend. The >>> interesting part is, that even pciconf -l -bcv ist not able to get >>> all >>> information. >>> >>> Before suspend: >>> iwn0@pci0:6:0:0: class=0x028000 card=0x13018086 >>> chip=0x42328086 >>> rev=0x00 hdr=0x00 >>> vendor = 'Intel Corporation' >>> device = 'Carte Intel WiFi Link 5100 AGN (Intel WiFi Link >>> 5100)' >>> class = network >>> bar [10] = type Memory, range 64, base 0xec800000, size 8192, >>> enabled cap 01[c8] = powerspec 3 supports D0 D3 current D0 >>> cap 05[d0] = MSI supports 1 message, 64 bit enabled with 1 >>> message >>> cap 10[e0] = PCI-Express 1 endpoint max data 128(128) link x1(x1) >>> >>> After resume: >>> iwn0@pci0:6:0:0: class=0x028000 card=0x13018086 >>> chip=0x42328086 >>> rev=0x00 hdr=0x00 >>> vendor = 'Intel Corporation' >>> device = 'Carte Intel WiFi Link 5100 AGN (Intel WiFi Link >>> 5100)' >>> class = network >> >> Are you sure you didn't forget the extra options to pciconf here? >> The bar >> should definitely not disappear since we save that state in >> software, not >> in hardware. Also, the capability pointer register is set by the >> hardware, >> software never changes it. > > The complete pciconf before suspend: > http://techwires.net/~bschmidt/pciconf.before.txt > The complete pciconf after resume: > http://techwires.net/~bschmidt/pciconf.after.txt > > Comparing both yields exactly those 4 lines missing. We should check if the device driver is doing something evil on suspend/resume. Can you boot without iwn loaded and suspend/resume ? -- Rui Paulo _______________________________________________ freebsd-acpi@... mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-acpi To unsubscribe, send any mail to "freebsd-acpi-unsubscribe@..."
	Re: general issue with suspend/resume with iwn(4)/bge(4) by John Baldwin :: Rate this Message: Reply to Author \| View Threaded \| Show Only this Message On Monday 09 November 2009 1:14:18 pm Serge Semenenko wrote: > John Baldwin wrote: > On Sunday 08 November 2009 6:19:09 am Bernhard Schmidt wrote: > > Hi, > > I hope this is the correct list for an issue like that, if not, a pointer > would be appreciated. > > I've been in contact with Mykola Dzham quite some time now and we are trying > to figure out a resume issue on his iwn(4) device. It does seem that this > device does not come up correctly after suspend. The interesting part is, that > even pciconf -l -bcv ist not able to get all information. > > Before suspend: > iwn0@pci0:6:0:0: class=0x028000 card=0x13018086 chip=0x42328086 > rev=0x00 hdr=0x00 > vendor = 'Intel Corporation' > device = 'Carte Intel WiFi Link 5100 AGN (Intel WiFi Link 5100)' > class = network > bar [10] = type Memory, range 64, base 0xec800000, size 8192, enabled > cap 01[c8] = powerspec 3 supports D0 D3 current D0 > cap 05[d0] = MSI supports 1 message, 64 bit enabled with 1 message > cap 10[e0] = PCI-Express 1 endpoint max data 128(128) link x1(x1) > > After resume: > iwn0@pci0:6:0:0: class=0x028000 card=0x13018086 chip=0x42328086 > rev=0x00 hdr=0x00 > vendor = 'Intel Corporation' > device = 'Carte Intel WiFi Link 5100 AGN (Intel WiFi Link 5100)' > class = network > > > Are you sure you didn't forget the extra options to pciconf here? The bar > should definitely not disappear since we save that state in software, not > in hardware. Also, the capability pointer register is set by the hardware, > software never changes it. > > > > It looks similar to PR http://www.freebsd.org/cgi/query-pr.cgi?pr=135070 for me. And if I understood right you're already working on the solution... No, having the capability registers and a BAR disappear after they were programmed is entirely different. That PR is about being able to allocate space for the BAR on boot, not about losing it entirely after resume. -- John Baldwin _______________________________________________ freebsd-acpi@... mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-acpi To unsubscribe, send any mail to "freebsd-acpi-unsubscribe@..."
	Re: general issue with suspend/resume with iwn(4)/bge(4) by Bernhard Schmidt-4 :: Rate this Message: Reply to Author \| View Threaded \| Show Only this Message On Monday 09 November 2009 19:33:53 Rui Paulo wrote: > On 9 Nov 2009, at 17:03, Bernhard Schmidt wrote: > > On Monday 09 November 2009 13:43:48 John Baldwin wrote: > >> On Sunday 08 November 2009 6:19:09 am Bernhard Schmidt wrote: > >>> Hi, > >>> > >>> I hope this is the correct list for an issue like that, if not, a > >>> pointer > >>> would be appreciated. > >>> > >>> I've been in contact with Mykola Dzham quite some time now and we > >>> are > >>> trying to figure out a resume issue on his iwn(4) device. It does > >>> seem > >>> that this device does not come up correctly after suspend. The > >>> interesting part is, that even pciconf -l -bcv ist not able to get > >>> all > >>> information. > >>> > >>> Before suspend: > >>> iwn0@pci0:6:0:0: class=0x028000 card=0x13018086 > >>> chip=0x42328086 > >>> rev=0x00 hdr=0x00 > >>> vendor = 'Intel Corporation' > >>> device = 'Carte Intel WiFi Link 5100 AGN (Intel WiFi Link > >>> 5100)' > >>> class = network > >>> bar [10] = type Memory, range 64, base 0xec800000, size 8192, > >>> enabled cap 01[c8] = powerspec 3 supports D0 D3 current D0 > >>> cap 05[d0] = MSI supports 1 message, 64 bit enabled with 1 > >>> message > >>> cap 10[e0] = PCI-Express 1 endpoint max data 128(128) link x1(x1) > >>> > >>> After resume: > >>> iwn0@pci0:6:0:0: class=0x028000 card=0x13018086 > >>> chip=0x42328086 > >>> rev=0x00 hdr=0x00 > >>> vendor = 'Intel Corporation' > >>> device = 'Carte Intel WiFi Link 5100 AGN (Intel WiFi Link > >>> 5100)' > >>> class = network > >> > >> Are you sure you didn't forget the extra options to pciconf here? > >> The bar > >> should definitely not disappear since we save that state in > >> software, not > >> in hardware. Also, the capability pointer register is set by the > >> hardware, > >> software never changes it. > > > > The complete pciconf before suspend: > > http://techwires.net/~bschmidt/pciconf.before.txt > > The complete pciconf after resume: > > http://techwires.net/~bschmidt/pciconf.after.txt > > > > Comparing both yields exactly those 4 lines missing. > > We should check if the device driver is doing something evil on > suspend/resume. Can you boot without iwn loaded and suspend/resume ? I'm sorry if it might came out wrong in my first email. It's Mykola Dzham's system which has those issue, I'm posting all information on prior discussions with him. I can suspend/resume with iwn loaded, device works after resume as its supposed to. For him kldload/kldunload does work too, those issues just come up after suspend. Based on that I had doubts that it is a general issue with the iwn driver. -- Bernhard _______________________________________________ freebsd-acpi@... mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-acpi To unsubscribe, send any mail to "freebsd-acpi-unsubscribe@..."
	Re: general issue with suspend/resume with iwn(4)/bge(4) by Serge Semenenko :: Rate this Message: Reply to Author \| View Threaded \| Show Only this Message John Baldwin wrote: > On Monday 09 November 2009 1:14:18 pm Serge Semenenko wrote: > >> John Baldwin wrote: >> On Sunday 08 November 2009 6:19:09 am Bernhard Schmidt wrote: >> >> Hi, >> >> I hope this is the correct list for an issue like that, if not, a pointer >> would be appreciated. >> >> I've been in contact with Mykola Dzham quite some time now and we are trying >> to figure out a resume issue on his iwn(4) device. It does seem that this >> device does not come up correctly after suspend. The interesting part is, >> > that > >> even pciconf -l -bcv ist not able to get all information. >> >> Before suspend: >> iwn0@pci0:6:0:0: class=0x028000 card=0x13018086 chip=0x42328086 >> rev=0x00 hdr=0x00 >> vendor = 'Intel Corporation' >> device = 'Carte Intel WiFi Link 5100 AGN (Intel WiFi Link 5100)' >> class = network >> bar [10] = type Memory, range 64, base 0xec800000, size 8192, enabled >> cap 01[c8] = powerspec 3 supports D0 D3 current D0 >> cap 05[d0] = MSI supports 1 message, 64 bit enabled with 1 message >> cap 10[e0] = PCI-Express 1 endpoint max data 128(128) link x1(x1) >> >> After resume: >> iwn0@pci0:6:0:0: class=0x028000 card=0x13018086 chip=0x42328086 >> rev=0x00 hdr=0x00 >> vendor = 'Intel Corporation' >> device = 'Carte Intel WiFi Link 5100 AGN (Intel WiFi Link 5100)' >> class = network >> >> >> Are you sure you didn't forget the extra options to pciconf here? The bar >> should definitely not disappear since we save that state in software, not >> in hardware. Also, the capability pointer register is set by the hardware, >> software never changes it. >> >> >> >> It looks similar to PR http://www.freebsd.org/cgi/query-pr.cgi?pr=135070 >> > for me. And if I understood right you're already working on the solution... > > No, having the capability registers and a BAR disappear after they were > programmed is entirely different. That PR is about being able to allocate > space for the BAR on boot, not about losing it entirely after resume. > > Not sure about nature of things happened but on my system resources programmed with mentioned in PR hack are also disappears on resume and to get things working the hack should be applied both on attach and on resume. _______________________________________________ freebsd-acpi@... mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-acpi To unsubscribe, send any mail to "freebsd-acpi-unsubscribe@..."
	Re: general issue with suspend/resume with iwn(4)/bge(4) by Mykola Dzham :: Rate this Message: Reply to Author \| View Threaded \| Show Only this Message Rui Paulo wrote: > On 9 Nov 2009, at 17:03, Bernhard Schmidt wrote: > > > On Monday 09 November 2009 13:43:48 John Baldwin wrote: > >> On Sunday 08 November 2009 6:19:09 am Bernhard Schmidt wrote: > >>> Hi, > >>> > >>> I hope this is the correct list for an issue like that, if not, a > >>> pointer > >>> would be appreciated. > >>> > >>> I've been in contact with Mykola Dzham quite some time now and we > >>> are > >>> trying to figure out a resume issue on his iwn(4) device. It does > >>> seem > >>> that this device does not come up correctly after suspend. The > >>> interesting part is, that even pciconf -l -bcv ist not able to get > >>> all > >>> information. > >>> > >>> Before suspend: > >>> iwn0@pci0:6:0:0: class=0x028000 card=0x13018086 > >>> chip=0x42328086 > >>> rev=0x00 hdr=0x00 > >>> vendor = 'Intel Corporation' > >>> device = 'Carte Intel WiFi Link 5100 AGN (Intel WiFi Link > >>> 5100)' > >>> class = network > >>> bar [10] = type Memory, range 64, base 0xec800000, size 8192, > >>> enabled cap 01[c8] = powerspec 3 supports D0 D3 current D0 > >>> cap 05[d0] = MSI supports 1 message, 64 bit enabled with 1 > >>> message > >>> cap 10[e0] = PCI-Express 1 endpoint max data 128(128) link x1(x1) > >>> > >>> After resume: > >>> iwn0@pci0:6:0:0: class=0x028000 card=0x13018086 > >>> chip=0x42328086 > >>> rev=0x00 hdr=0x00 > >>> vendor = 'Intel Corporation' > >>> device = 'Carte Intel WiFi Link 5100 AGN (Intel WiFi Link > >>> 5100)' > >>> class = network > >> > >> Are you sure you didn't forget the extra options to pciconf here? > >> The bar > >> should definitely not disappear since we save that state in > >> software, not > >> in hardware. Also, the capability pointer register is set by the > >> hardware, > >> software never changes it. > > > > The complete pciconf before suspend: > > http://techwires.net/~bschmidt/pciconf.before.txt > > The complete pciconf after resume: > > http://techwires.net/~bschmidt/pciconf.after.txt > > > > Comparing both yields exactly those 4 lines missing. > > We should check if the device driver is doing something evil on > suspend/resume. Can you boot without iwn loaded and suspend/resume ? Same result. Before: none1@pci0:6:0:0: class=0x028000 card=0x13018086 chip=0x42328086 rev=0x00 hdr=0x00 vendor = 'Intel Corporation' device = 'Carte Intel WiFi Link 5100 AGN (Intel WiFi Link 5100)' class = network bar [10] = type Memory, range 64, base 0xec800000, size 8192, enabled cap 01[c8] = powerspec 3 supports D0 D3 current D0 cap 05[d0] = MSI supports 1 message, 64 bit cap 10[e0] = PCI-Express 1 endpoint max data 128(128) link x1(x1) After: none1@pci0:6:0:0: class=0x028000 card=0x13018086 chip=0x42328086 rev=0x00 hdr=0x00 vendor = 'Intel Corporation' device = 'Carte Intel WiFi Link 5100 AGN (Intel WiFi Link 5100)' class = network -- LEFT-(UANIC\|RIPE) JID: levsha@... PGP fingerprint: 1BCD 7C80 2E04 7282 C944 B0E0 7E67 619E 4E72 9280 _______________________________________________ freebsd-acpi@... mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-acpi To unsubscribe, send any mail to "freebsd-acpi-unsubscribe@..."
	Re: general issue with suspend/resume with iwn(4)/bge(4) by Mykola Dzham :: Rate this Message: Reply to Author \| View Threaded \| Show Only this Message Mykola Dzham wrote: > Rui Paulo wrote: > > On 9 Nov 2009, at 17:03, Bernhard Schmidt wrote: > > > > > On Monday 09 November 2009 13:43:48 John Baldwin wrote: > > >> On Sunday 08 November 2009 6:19:09 am Bernhard Schmidt wrote: > > >>> Hi, > > >>> > > >>> I hope this is the correct list for an issue like that, if not, a > > >>> pointer > > >>> would be appreciated. > > >>> > > >>> I've been in contact with Mykola Dzham quite some time now and we > > >>> are > > >>> trying to figure out a resume issue on his iwn(4) device. It does > > >>> seem > > >>> that this device does not come up correctly after suspend. The > > >>> interesting part is, that even pciconf -l -bcv ist not able to get > > >>> all > > >>> information. > > >>> > > >>> Before suspend: > > >>> iwn0@pci0:6:0:0: class=0x028000 card=0x13018086 > > >>> chip=0x42328086 > > >>> rev=0x00 hdr=0x00 > > >>> vendor = 'Intel Corporation' > > >>> device = 'Carte Intel WiFi Link 5100 AGN (Intel WiFi Link > > >>> 5100)' > > >>> class = network > > >>> bar [10] = type Memory, range 64, base 0xec800000, size 8192, > > >>> enabled cap 01[c8] = powerspec 3 supports D0 D3 current D0 > > >>> cap 05[d0] = MSI supports 1 message, 64 bit enabled with 1 > > >>> message > > >>> cap 10[e0] = PCI-Express 1 endpoint max data 128(128) link x1(x1) > > >>> > > >>> After resume: > > >>> iwn0@pci0:6:0:0: class=0x028000 card=0x13018086 > > >>> chip=0x42328086 > > >>> rev=0x00 hdr=0x00 > > >>> vendor = 'Intel Corporation' > > >>> device = 'Carte Intel WiFi Link 5100 AGN (Intel WiFi Link > > >>> 5100)' > > >>> class = network > > >> > > >> Are you sure you didn't forget the extra options to pciconf here? > > >> The bar > > >> should definitely not disappear since we save that state in > > >> software, not > > >> in hardware. Also, the capability pointer register is set by the > > >> hardware, > > >> software never changes it. > > > > > > The complete pciconf before suspend: > > > http://techwires.net/~bschmidt/pciconf.before.txt > > > The complete pciconf after resume: > > > http://techwires.net/~bschmidt/pciconf.after.txt > > > > > > Comparing both yields exactly those 4 lines missing. > > > > We should check if the device driver is doing something evil on > > suspend/resume. Can you boot without iwn loaded and suspend/resume ? > > Same result. > Before: > > none1@pci0:6:0:0: class=0x028000 card=0x13018086 chip=0x42328086 rev=0x00 hdr=0x00 > vendor = 'Intel Corporation' > device = 'Carte Intel WiFi Link 5100 AGN (Intel WiFi Link 5100)' > class = network > bar [10] = type Memory, range 64, base 0xec800000, size 8192, enabled > cap 01[c8] = powerspec 3 supports D0 D3 current D0 > cap 05[d0] = MSI supports 1 message, 64 bit > cap 10[e0] = PCI-Express 1 endpoint max data 128(128) link x1(x1) > > After: > > none1@pci0:6:0:0: class=0x028000 card=0x13018086 chip=0x42328086 rev=0x00 hdr=0x00 > vendor = 'Intel Corporation' > device = 'Carte Intel WiFi Link 5100 AGN (Intel WiFi Link 5100)' > class = network I tested possible pciconf output changes on em ethernet card on my notebook (without if_iwn loaded) before and after suspend/resume. On ethernet card no changes in output, same output before and after: none0@pci0:0:25:0: class=0x020000 card=0x9025104d chip=0x10f58086 rev=0x03 hdr=0x00 vendor = 'Intel Corporation' device = 'Intel 82567LM-2 Gigabit Network Connection (82567LM)' class = network subclass = ethernet bar [10] = type Memory, range 32, base 0xee900000, size 131072, enabled bar [14] = type Memory, range 32, base 0xee924000, size 4096, enabled bar [18] = type I/O Port, range 32, base 0x8100, size 32, enabled cap 01[c8] = powerspec 2 supports D0 D3 current D0 cap 05[d0] = MSI supports 1 message, 64 bit cap 13[e0] = PCI Advanced Features: FLR TP -- LEFT-(UANIC\|RIPE) JID: levsha@... PGP fingerprint: 1BCD 7C80 2E04 7282 C944 B0E0 7E67 619E 4E72 9280 _______________________________________________ freebsd-acpi@... mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-acpi To unsubscribe, send any mail to "freebsd-acpi-unsubscribe@..."